Bug 174516 - KDE crash on startup
Summary: KDE crash on startup
Status: CLOSED FIXED
Alias: None
Product: solid
Classification: Unmaintained
Component: powermanagement-daemon (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-07 10:43 UTC by Ruchir Brahmbhatt
Modified: 2010-10-02 12:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
system tray not expanding (33.27 KB, image/png)
2008-11-07 14:10 UTC, Ruchir Brahmbhatt
Details
kde trace (4.69 KB, application/octet-stream)
2008-11-08 13:54 UTC, Ruchir Brahmbhatt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ruchir Brahmbhatt 2008-11-07 10:43:47 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

OS: opensuse 11.0
Kde: 4.1.3 

After upgrade to 4.1.3, I can no longer use KDE. KDED crashes and desktop is unusable. Crash report is as below:

Application: KDE Daemon (kded4), signal SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb61e16d0 (LWP 3268)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb4777eff in PowerDevilDaemon::reloadProfile ()
   from /usr/lib/kde4/kded_powerdevil.so
#7  0xb477914e in PowerDevilDaemon::refreshStatus ()
   from /usr/lib/kde4/kded_powerdevil.so
#8  0xb477a5ca in PowerDevilDaemon::PowerDevilDaemon ()
   from /usr/lib/kde4/kded_powerdevil.so
#9  0xb477ed28 in KPluginFactory::createInstance<PowerDevilDaemon, QObject> ()
   from /usr/lib/kde4/kded_powerdevil.so
#10 0xb79a96c7 in KPluginFactory::create () from /usr/lib/libkdecore.so.5
#11 0xb7f44fcc in ?? () from /usr/lib/libkdeinit4_kded4.so
#12 0xb7f47a02 in ?? () from /usr/lib/libkdeinit4_kded4.so
#13 0xb7f49f52 in ?? () from /usr/lib/libkdeinit4_kded4.so
#14 0xb7b986d6 in ?? () from /usr/lib/libkdeui.so.5
#15 0xb7b968de in ?? () from /usr/lib/libkdeui.so.5
#16 0xb7187dd1 in ?? () from /usr/lib/libQtDBus.so.4
#17 0xb7188f47 in ?? () from /usr/lib/libQtDBus.so.4
#18 0xb7189451 in ?? () from /usr/lib/libQtDBus.so.4
#19 0xb718994a in ?? () from /usr/lib/libQtDBus.so.4
#20 0xb75b8ce9 in QObject::event () from /usr/lib/libQtCore.so.4
#21 0xb75a8c6b in QCoreApplication::event () from /usr/lib/libQtCore.so.4
#22 0xb6931576 in QApplication::event () from /usr/lib/libQtGui.so.4
#23 0xb692bc2c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#24 0xb6933a8e in QApplication::notify () from /usr/lib/libQtGui.so.4
#25 0xb7b8f1fd in KApplication::notify () from /usr/lib/libkdeui.so.5
#26 0xb75a9311 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#27 0xb75a9f85 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#28 0xb75aa17d in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#29 0xb75d3e6f in ?? () from /usr/lib/libQtCore.so.4
#30 0xb64152d9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#31 0xb641885b in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#32 0xb64189d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#33 0xb75d3ab8 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#34 0xb69c4ca5 in ?? () from /usr/lib/libQtGui.so.4
#35 0xb75a79ea in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#36 0xb75a7baa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#37 0xb75aa245 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#38 0xb692baa7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#39 0xb7f48956 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#40 0x08048782 in _start ()
#0  0xffffe430 in __kernel_vsyscall ()
Comment 1 Dario Freddi 2008-11-07 12:49:44 UTC
I would need a better backtrace, probably with debug symbols, to trigger that better. As a first attempt, you can try removing ~/.kde4/share/config/powerdevil* and see if it starts again.

Otherwise, please consider installing debug symbols to allow me to fix that.
Comment 2 Ruchir Brahmbhatt 2008-11-07 14:08:06 UTC
I tried it but still same issue. I'll attach crash report and screenshot. In addition, the system tray is not expanding and not making room for icons.
Which debug symbols I need to install?
Comment 3 Ruchir Brahmbhatt 2008-11-07 14:10:40 UTC
Created attachment 28391 [details]
system tray not expanding
Comment 4 Ruchir Brahmbhatt 2008-11-08 11:55:58 UTC
(In reply to comment #1)
> I would need a better backtrace, probably with debug symbols, to trigger that
> better. As a first attempt, you can try removing
> ~/.kde4/share/config/powerdevil* and see if it starts again.
> 
> Otherwise, please consider installing debug symbols to allow me to fix that.
> 

I installed most of the debug packages but still its not generating proper crash report and shows no debug symbols found.
Can you please guide me which debug packages are essential for this so that I can verify it they're installed properly.
Comment 5 Ruchir Brahmbhatt 2008-11-08 13:54:29 UTC
Created attachment 28410 [details]
kde trace

Finally I managed to get full trace.
Comment 6 Ruchir Brahmbhatt 2008-11-08 13:58:02 UTC
In order to install kdelibs4-debuginfo package, I had to downgrade some qt libraries because of dependency issues. After that I could reproduce the crash as attached but desktop was usable(I'm writing this from kde4 desktop J)

Please let me know if more information is needed. I'll be glad to provide. I have most of the debug packages installed now.
Comment 7 Dario Freddi 2008-11-08 14:16:42 UTC
Thanks for your efforts, now the backtrace defiintely makes more sense.
I need you to do just one more thing: please start KDED4 from terminal, just by issuing "kded4". It will spit out a lot of output before crashing, some of which regards PowerDevil. Please paste it here
Comment 8 Ruchir Brahmbhatt 2008-11-08 14:19:16 UTC
I followed the step and got below info in terminal.

linux-xzu9:~ # kded4
kded(14493): Could not load a polling system!
KCrash: Application 'kded4' crashing...
sock_file=/root/.kde4/socket-linux-xzu9/kdeinit4__0
kded(14492): Communication problem with  "kded" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

linux-xzu9:~ # kded(14499): Could not load a polling system!
kded(14497): Communication problem with  "kded" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "
Comment 9 Dario Freddi 2008-11-08 15:05:50 UTC
Exactly what I expected. You can solve this by installing libxss or libxext (better libxext), in the meanwhile I'll fix it. Thanks for reporting
Comment 10 Ruchir Brahmbhatt 2008-11-08 15:09:44 UTC
xorg-x11-libXext was already installed. I din't find libxss in search.
Note that I'm using opensuse 11.0 and using YAST2 for installing packages.
Comment 11 Dario Freddi 2008-11-08 15:20:59 UTC
So this could be (apart from PowerDevil bug that I'm fixing right now) a bug in OpenSUSE packages. Let me explain you how powerdevil works.

PowerDevil queries the system for idle time through some polling backends. Currently it supports 3 backends: the first one, and most efficient, is based on a X extension called "XSync", the other 2, a bit less efficient, are based on XScreensaver.

PowerDevil, when compiled, searches for both XSync and XScreensaver, and enables compilation of a backend if the library it is based upon is found. So, if PowerDevil was compiled without XSync or XScreensaver support, you should definitely report this to OpenSUSE guys.

Or maybe you don't have XSync and XScreensaver installed. I don't use OpenSUSE so I really can't tell you more about this, you'd better check this out with OpenSUSE support, they surely can point you to correct packages
Comment 12 Dario Freddi 2008-11-08 15:50:00 UTC
Fixed in trunk, I implemented a safe POLLER_CALL so that having no poll system loaded will no longer be an issue
Comment 13 Ruchir Brahmbhatt 2008-11-08 15:56:07 UTC
Thats great. 
xsync was not available so I installed xscreensaver but still issue is there. I think I may have to restart x server. I'll try that and report back.
I've opened bug at opensuse as well.
https://bugzilla.novell.com/show_bug.cgi?id=443124
Comment 14 Ruchir Brahmbhatt 2008-11-08 19:59:44 UTC
Installing xscreensaver didn't help, still kded crashes. Thank god at least desktop is usable. J
Comment 15 Ruchir Brahmbhatt 2008-11-09 10:50:55 UTC
A quick update. The desktop is not always usable. Sometimes it freezes and I have to do hard reboot(can't even restart xdm or login to other terminals). Currently I'm up with kde4 after 3 hard reboots.
Comment 16 Dario Freddi 2008-11-09 22:51:40 UTC
So it turns out it was not OpenSUSE's fault, but a small bug in CMake that didn't trigger XScreensaver backends. I just requested an upload of PowerDevil 1.4.1, that will fix this and other problems. Hold on, and please ask the OpenSUSE guys to upgrade immediately when it will be available :)
Comment 17 Ruchir Brahmbhatt 2008-11-10 06:09:52 UTC
It was already fixed in powerdevil-1.4.0-9.1. I just upgraded to that version and crash is no longer there.