Bug 183493 - kmail segfault
Summary: kmail segfault
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-01 15:21 UTC by David Woodhouse
Modified: 2008-03-09 05:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-09 05:37:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Woodhouse 2006-03-01 15:21:00 UTC
When I asked kmail to display the message preview next to the message list
instead of below it, and clicked 'Apply', kmail segfaulted. 

Now it won't start again -- I run 'kmail' from a prompt, and just get the prompt
back again immediately. 

There isn't a kmail process running, so I can't attempt to kill it off. I do see
a 'kio_imap4' process eating CPU though; it's doing this...

--- SIGPIPE (Broken pipe) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
write(3, "    36_66_\0\0\0\30\0\0\0.\0b\0a\0y\0t\0h\0o\0r"..., 64) = -1 EPIPE
(Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
write(3, "    36_66_\0\0\0\30\0\0\0.\0b\0a\0y\0t\0h\0o\0r"..., 64) = -1 EPIPE
(Broken pipe)

Comment 1 Than Ngo 2006-05-03 13:28:01 UTC
Can you start kmail again after removing ~/.kde/share/apps/kmail/imap directory?
Could you please attach the output of a stack trace? Thanks



Comment 2 Than Ngo 2006-05-03 13:30:43 UTC
could you please try new kde-3.5.2 in FC4 update if this bug still appears? Thanks

Comment 4 petrosyan 2008-03-09 05:37:08 UTC
Fedora Core 4 is no longer maintained.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.


Note You need to log in before you can comment on or make changes to this bug.