Bug 159518

Summary:	Plasma crashs during work
Product:	[Plasma] plasma4	Reporter:	Florian Sievert <FlorianSievert>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED NOT A BUG
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Crash log of the described issue.

Description Florian Sievert 2008-03-18 13:50:18 UTC

Version:           KDE 4.0.66 >= 20080313 (using Devel)
Installed from:    Compiled sources
Compiler:          gcc (GCC) 4.1.2 20070925 (Red Hat 4.1.2-33) 
OS:                Linux

During work plasma suddenly crashed without any action that seems related to it (I worked in firefox). Because of this I am not able to reproduce the problem. After plasma died it was possible to launch it again via ALT+F2. I am attaching the crash log.

Comment 1 Florian Sievert 2008-03-18 13:51:22 UTC

Created attachment 23949 [details]
Crash log of the described issue.

Comment 2 Mark Constable 2008-03-18 14:18:22 UTC

I can confirm that I also have had this problem since 2008-03-17 (I build every night) for both i686 and x86_64. I'm using publically available Release builds so I can't provide any useful debug code except to perhaps note that my lower case 'e' character dissapears when using apps via alt-f2. As of around rev 787000 plasma no longer crashes outright but there is no background, rmb or typical desktop behavour other than the panel now works.

Comment 3 Aaron J. Seigo 2008-03-18 18:29:07 UTC

this doesn't even hit any plasma code, and as for "i updated and now it crashes" that'll be BIC changes being made leading up to 4.1

Comment 4 Mark Constable 2008-03-18 21:35:25 UTC

In my case I also tried a completely fresh install with nothing but a base system + xorg then kde packages plus dependencies built from trunk only a few hours earlier. The 2 differences I am aware of are of me using exiv2 1.6 instead of exiv2 1.5 and I did have a huge jpeg (2k x 3k) background image on the dashboard. It's still occurring with the 20080319 build so I will endeavour to rebuild a debug version today and submit a backtrace.