Bug 610195 - kmail crashes after starting it
Summary: kmail crashes after starting it
Status: RESOLVED DUPLICATE of bug 609955
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: KDE4 Applications (show other bugs)
Version: Factory
Hardware: x86-64 openSUSE 11.3
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-30 09:20 UTC by Markus Kriewald
Modified: 2010-05-31 08:00 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
kmail-20100530 (4.67 KB, text/plain)
2010-05-30 09:20 UTC, Markus Kriewald 		Details
konqueror-20100530.kcrash (7.29 KB, text/plain)
2010-05-30 09:26 UTC, Markus Kriewald 		Details
kontact-20100530.kcrash (5.98 KB, text/plain)
2010-05-30 09:35 UTC, Markus Kriewald 		Details
kinfocenter-20100530.kcrash (2.49 KB, text/plain)
2010-05-30 09:41 UTC, Markus Kriewald 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Kriewald 2010-05-30 09:20:08 UTC 
Created attachment 365677 [details]
kmail-20100530

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.4) Gecko/20100513 SUSE/3.6.4-1.13 Firefox/3.6.4

After starting kmail it crashes.

Reproducible: Always

Steps to Reproduce:
1.start kmail
2.
3.
Comment 1 Markus Kriewald 2010-05-30 09:26:24 UTC 
Created attachment 365678 [details]
konqueror-20100530.kcrash
Comment 2 Markus Kriewald 2010-05-30 09:27:22 UTC 
Konqueror also crashes after starting it.
Comment 3 Markus Kriewald 2010-05-30 09:35:08 UTC 
Created attachment 365679 [details]
kontact-20100530.kcrash
Comment 4 Markus Kriewald 2010-05-30 09:41:24 UTC 
Created attachment 365680 [details]
kinfocenter-20100530.kcrash
Comment 5 Christian Trippe 2010-05-31 08:00:53 UTC 
dup, should be fixed with the next rebuild of Factory

*** This bug has been marked as a duplicate of bug 609955 ***