Version: (using KDE 4.0.83) Installed from: SuSE RPMs Compiler: gcc 4.3.1 openSUSE 11.0 with only official plasmoids released by kde (clocks, calculator, news ticker) plasma randomly crashed when user was not interacting with the dashboard. Sorry, the backtrace is incompelete as kde bebuginfo packagase for 4.0.83 have not yet been built in the openSUSE build service
Created attachment 25642 [details] backtrace
try to disable the news ticker, and see whether the random crashes go away.
Closing since I am just not able to find any "plasma_applet_knewsticker" anywhere within the KDE-svn. @Bohan Please fell free to point me to the location where the news-ticker is located and reopen the report for the case I was just to blind (and provide probably also a more useful backtrace cause that would allow to fix the issue). Thanks in advance :-)
"plasma_applet_knewsticker" is in kdenetwork.
ahhh... ok, thank you! reopen :)
probably related backtrace; http://bugs.kde.org/attachment.cgi?id=23515&action=view which should be fixed with r824984. But it may the case that this report is about another crash. Not sure there and we can't fix it anyway as long as no backtrace is provided. So, would be great if you can test knewsticker again and provide a backtrace if it still crashes, Bohan (else please close the report). Thanks in advance :)
Is it possible to manually build of download the debug symbols for the opensuse packages? or do I have to manually build all of kde 4.1 to produce a full backtrace?
Well, in that case it should be enough to have kdenetwork-debug packages installed since, as pointed out by Pino at comment #4, knewsticker is in there.
Some more backtraces: Created an attachment (id=25724) plasma.kcrash Created an attachment (id=25725) plasma2.kcrash
Thank you very much for the additional backtraces! The backtrace from attachment #25725 [details] looks exactly like those from attachment #23515 [details] which was fixed ~2 days ago with commit r824984 :) So, let's mark the crash as fixed then. If, for whatever reason, you still run into this with a KDE/knewsticker-release >r824984 (aka newer then 2 days old) what is imho *very* unlikely (but who knows) then please reopen the report. Thank you _very_ much for your feedback and for the help at tracking it down! :-)