[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Bug#30004: marked as done (kmail crashes on launch) by Michael =?iso-8859-1?q?H=E4ckel?= <Michael@Ha
From:       owner () bugs ! kde ! org (Stephan Kulow)
Date:       2001-07-30 7:18:04
[Download RAW message or body]

Your message with subj: Bug#30004: kmail crashes on launch

On Monday, 30. July 2001 02:00, matloffm@yahoo.com wrote:
> 
> I selected "forward" from the context menu for an email and kmail crashed
> with a signal 11.  After that, kmail would not launch.  The following is
> the backtrace.

Looks like a known X-server bug, nothing that can be fixed in KMail.
Disable font anti aliasing.

KMail stores information in ~/dead.letter, when it crashes, btw.

Regards,
Michael Häckel


has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 30 Jul 2001 00:00:36 +0000
Received: (qmail 24362 invoked by uid 33); 30 Jul 2001 00:00:36 -0000
Date: 30 Jul 2001 00:00:36 -0000
Message-ID: <20010730000036.24361.qmail@master.kde.org>
To: submit@bugs.kde.org
Subject: kmail crashes on launch
From: matloffm@yahoo.com

Package:           kmail
Version:           KDE 2.1.2 
Severity:          normal
Installed from:    Mandrake RPMs
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

I selected "forward" from the context menu for an email and kmail crashed with a \
signal 11.  After that, kmail would not launch.  The following is the backtrace.

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x41133689 in wait4 () from /lib/libc.so.6
#0  0x41133689 in wait4 () from /lib/libc.so.6
#1  0x411a46ec in __check_rhosts_file () from /lib/libc.so.6
#2  0x408cd188 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.3

#3  0x410a8128 in killpg () from /lib/libc.so.6
#4  0x41228d60 in XftTextExtents16 () from /usr/X11R6/lib/libXft.so.1
#5  0x40b02a74 in QFontMetrics::width () from /usr/lib/libqt.so.2
#6  0x0020003a in ?? ()


It seems like kmail was in the process of updating some stored information (stored \
where???) and left it in a corrupted state.  This would then explain why the \
application will no longer run.

(Submitted via bugs.kde.org)
(Called from KBugReport dialog. Fields Application, KDE Version, OS, Compiler \
manually changed)

_______________________________________________
Kmail Developers mailing list
Kmail@master.kde.org
http://master.kde.org/mailman/listinfo/kmail


[prev in list] [next in list] [prev in thread] [next in thread]