Version: (using Devel) Installed from: Compiled sources OS: Linux These seem to be random crashes, but probably aren't since I have reproduced them several times with great success. The first happens when one tries to remove or add the systray applet or a panel with the systray applet on it. The second and third popped up only after I finally successfully removed the panel and started over so I'm only partially sure that they have something to do with this. Ever since I got the panel removed, re-added, and repopulated plasma crashes almost everytime I log in. I will upload the first backtrace dealing with the systray and then the other two bracktraces from logout. Both logout bracktraces were named '<unkown>.kcrash' (I removed the '<>'), which is odd because it stated that Plasma had the error and usually in names those 'plasma.kcrash' by default. I dunno if that is helpful at all.
Created attachment 25275 [details] First bractrace
Created attachment 25276 [details] Second backtrace
Created attachment 25277 [details] Third backtrace
this looks very much like a bad install where libplasma and the applets are out of sync causing issues. can you please confirm that your builds of kdebase and kdeplasmoids are all up to date? (along with any other plasma plugins you are using?) thanks
Thank you for you reply. Sadly I seemed to have made a mistake in the report. I didn't compile these myself, therefore I can't tell you when they were actually built. I installed these from Kubuntu packages. So is this possibly a packaging issue? Should I take this up with the Kubuntu devs?
Hi JJ, could you please provide a more useful backtrace like explained on http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports - thanks in advance :)
I don't see why exactly you need them, I know of there importance, but answer me this. Aaron Seigo already explained that this is likely not a real bug. I asked the question if I should even be reporting this here? Try to answer the question so I know if I should report this to the Kubuntu devs. I will not be installing any additional, or unnecessary packages until I know if this is the right move. I hope you understand that.
JJ either report to KUbuntu and close here or provide more info with debug info so we can be sure about the issue. The best is as Aaron said to report to your distribution, at least to see if others have the same problems. When there are no debug symbols it's very difficult to make sense of what's really happening. We have many bugs to triage and we would like to fix the most for 4.1 Thanks in advance!
No, thank you Anne-Marie. You're the first one to have actually provided a straight answer. Aaron wouldn't explain if this was a packaging issue (at least not to me) as he assumed that I had compiled this because of an error in reporting the bug. So all I wanted to know is if it was a packaging problem so I could do what you said, close this and report it to the Kubuntu devs. Thank you very much for actually being helpful. At least I can see that there is still hope for the bug triage team here.