Bug 295638 - Kmail crash just beginning to compose an email
Summary: Kmail crash just beginning to compose an email
Status: RESOLVED DUPLICATE of bug 295611
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.8
Platform: openSUSE Linux
: NOR critical
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-09 21:30 UTC by Galeffi Christian
Modified: 2012-03-10 19:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
I can't send via DrKonqui (4.30 KB, application/octet-stream)
2012-03-09 21:30 UTC, Galeffi Christian 		Details
New crash information added by DrKonqi (4.70 KB, text/plain)
2012-03-10 13:30 UTC, Galeffi Christian 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Galeffi Christian 2012-03-09 21:30:27 UTC 
Created attachment 69437 [details]
I can't send via DrKonqui

When I try to write a mail, the first charatter I type does kmail crash
Comment 1 Galeffi Christian 2012-03-10 13:30:03 UTC 
Created attachment 69455 [details]
New crash information added by DrKonqi

kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) "release 481" using Qt 4.8.0

- What I was doing when the application crashed: I Start to typing a mail, I happen on two different system with openSUSE 12.1 and KDE4.8.1

-- Backtrace (Reduced):
#6  0x00007f533d500553 in Sonnet::Highlighter::eventFilter(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#7  0x00007f533bd4ea28 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#8  0x00007f533c761e4f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#9  0x00007f533c7673ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#10 0x00007f533d4a6656 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
Comment 2 Galeffi Christian 2012-03-10 19:47:56 UTC 

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