Version: unspecified (using KDE 4.5.5) OS: Linux After fresh install I am experiencing frequent problems which may be related to the same bug (or not). First, often when logging in, a crash in kdeinit is reported, but the desktop shows up pretty much intact. When using KDE, the desktop often crashes. When I restarted plasma-desktop, it ran fairly well until I went to search for new plasma widgets (KDE site) upon which the desktop crashed immediately. The output on the console I had used to start the desktop reported: Couldn't find node center. Skipping rendering. Object::connect: No such signal KPushButton::triggered(QAction*) Object::connect: (sender name: 'installButton') plasma-desktop: symbol lookup error: /usr/lib64/libattica.so.0: undefined symbol: _ZN9QListData11detach_growEPii I restarted, and was able to start to load the Google widgets, and few thumbnails showed up before crashing with the following message: thumbnail.js:104: Thumbnail not modified: http://desktop.google.com/plugins/images/clock_cal_sm.gif KCrash: Attempting to start /usr/bin/plasma-desktop from kdeinit sock_file=/home/kevin/.kde4/socket-linux-t9wr/kdeinit4__0 KCrash: Application 'plasma-desktop' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/home/kevin/.kde4/socket-linux-t9wr/kdeinit4__0 Reproducible: Always Steps to Reproduce: right click on taskbar -> add widgets -> Get new widgets
[Comment from a bug triager] For each crash we need a separate report with a full backtrace (you may need to install some "-debuginfo" packages) About this error: "plasma-desktop: symbol lookup error: /usr/lib64/libattica.so.0: undefined symbol: _ZN9QListData11detach_growEPii" It is caused by some mistmatch between libattica (related to GetHotNewStuff via kde-look) and KDE itself. You probably need to update your KDE related packages as it is a compiling/packaging issue. Regards
Dario, Thanks for the suggestions. I wasn't getting any sort of help from kbugbuster. I do have the debug libraries installed, but the crash didn't seem to set off any sort of alarm bells. Is there a way to run w/ debugging turned on another way or generate a debug trace? (need some handholding, the only coding I am doing these days is OCL and R) I will try putting in libattica from the KDE 4.6 repo, and see what happens. I just got Akonadi and Kontact working again (after upgrading to 4.5) so I am a little loathe to upgrade to KDE 4.6 quite yet. Kevin Kevin M. Coonan, MD Bethesda, MD kevin.coonan {GMail, Skype} Omnes homines liberi aequique dignitate atque juribus nascuntur. Ratione conscientiaque praediti sunt et alii erga alios cum fraternitate se gerere debent. All human beings are born free and equal in dignity and rights. They are endowed with reason and conscience and should act towards one another in a spirit of brotherhood. Article I. Universal Declaration of Human Rights. 1948-12-10, Paris, France On Sunday, February 06, 2011 12:16:04 Dario Andres wrote: > https://bugs.kde.org/show_bug.cgi?id=265558 > > > Dario Andres <andresbajotierra@gmail.com> changed: > > What |Removed |Added > --------------------------------------------------------------------------- > - CC| |andresbajotierra@gmail.com > > > > > --- Comment #1 from Dario Andres <andresbajotierra gmail com> 2011-02-06 > 18:16:00 --- [Comment from a bug triager] > For each crash we need a separate report with a full backtrace (you may > need to install some "-debuginfo" packages) > > About this error: > "plasma-desktop: symbol lookup error: /usr/lib64/libattica.so.0: undefined > symbol: _ZN9QListData11detach_growEPii" > It is caused by some mistmatch between libattica (related to GetHotNewStuff > via kde-look) and KDE itself. You probably need to update your KDE related > packages as it is a compiling/packaging issue. > > Regards
[Comment from a bug triager] Try installing these packages: kdelibs4-debuginfo, libqt4-debuginfo, kdebase4-debuginfo, kdebase4-runtime-debuginfo, kdebase4-workspace-debuginfo DrKonqi (the KDE crash handler) should rate th backtraces you get. if you don't get a good score (and therefore, you can report them); try pasting them here so I can give you more advices. Regards
I am not able to reproduce any crash in KDE 4.7.4 on Fedora 16. Please update your KDE to the latest version and check if it still happens for you. If it does, please feel free to reopen this report with additional information and steps to reproduce the bug. Thanks!