Bug 278205

Summary: Plasma crashes every time I launch Thunderbird due to Message Indicator widget (Kubuntu)
Product: [Plasma] plasma4 Reporter: Bilal Akhtar <bilalakhtar>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DOWNSTREAM    
Severity: crash CC: andresbajotierra, ramon.casellas
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: KCrash file generated by KDE crash reporter

Description Bilal Akhtar 2011-07-21 14:38:35 UTC
Created attachment 62048 [details]
KCrash file generated by KDE crash reporter

Version:           unspecified (using Devel) 
OS:                Linux

Every time when I launch Thunderbird 6.0 Beta 1 on my Kubuntu Oneiric Alpha installation with KDE 4.7 RC1, the plasma shell crashes. Plasma doesn't crash immediately on launching Thunderbird, but it crashes around 2-3 seconds after the window pops up. Every time. I wasn't able to reproduce this with Firefox, so its clearly not an issue with all XUL apps, only Thunderbird. 

Do look at the attachment, it contains a backtrace (though that backtrace isn't that good).

Reproducible: Always

Steps to Reproduce:
1) Launch Thunderbird (I've managed to reproduce this with TB 6.0 beta 1, didn't try with any other version).
2) Observe Plasma crash a second or two after the thunderbird window pops on screen.

Actual Results:  
Plasma crashes. The panel goes away for a second along with the desktop, and comes back after another second.

Expected Results:  
Plasma shouldn't crash.

The attachment contains a backtrace.
Comment 1 Dario Andres 2011-07-23 14:20:53 UTC
Hi! 
Plasma is crashing in the Message Indicator widget, which is a Kubuntu development:

[KCrash Handler]
#6  0x00007f2677d9c794 in ?? () from /usr/lib/kde4/plasma_applet_message_indicator.so

Please report this issue to https://bugs.launchpad.net/plasma-widget-message-indicator

Thanks
Comment 2 Dario Andres 2011-07-31 14:28:00 UTC
*** Bug 278654 has been marked as a duplicate of this bug. ***