Kmail crashes when pasting onto the [To] button/combo

[Michael Geddes]

Binary package hint: kdepim

When creating a new mail, and you accidently paste onto the [TO] (or CC/BCC) button/combo selector instead of the associated edit, the app crashes.

It would be good if this didn't crash.
It might be better if this pasted the email into the edit.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Feb 11 09:27:50 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kmail
Package: kmail 4:4.3.5-0ubuntu1~karmic1
ProcCmdline: kmail -session 106869726f000125956254700000136440028_1264642469_931998
ProcEnviron:
 LANGUAGE=en_AU:en
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-18.55-generic
Signal: 11
SourcePackage: kdepim
StacktraceTop:
 ?? () from /usr/lib/kde4/plugins/styles/oxygen.so
 QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
 QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
 QApplication::notify(QObject*, QEvent*) ()
 KApplication::notify(QObject*, QEvent*) ()
Title: kmail crashed with SIGSEGV in QCoreApplicationPrivate::sendThroughObjectEventFilters()
Uname: Linux 2.6.31-18-generic i686
UserGroups: adm admin audio cdrom common dialout disk floppy lpadmin music mythtv plugdev sambashare sambashare smudge sudo video www-data
XsessionErrors: (polkit-gnome-authentication-agent-1:4299): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
SegvAnalysis:
 Segfault happened at: 0x229cfef: call 0x2281e67
 PC (0x0229cfef) ok
 source "0x2281e67" (0x02281e67) ok
 destination "(%esp)" (0xbee8df90) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA

[Apport retracing service (apport)]

StacktraceTop:OxygenStyle::renderTab (this=0x9273ea0, p=0x0,

[Rohan Garg (rohangarg)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly report the bug on http://bugs.kde.org along with any other information that would be helpful in debugging the issue.