Bug 146024 - kde4-3.90.1 crashes on startup and then load with no window manager
Summary: kde4-3.90.1 crashes on startup and then load with no window manager
Status: RESOLVED DUPLICATE of bug 145923
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-27 16:59 UTC by Willem
Modified: 2007-07-17 10:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Willem 2007-05-27 16:59:48 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources

This is my first kde bug report :D

I installed kde4-3.90.1 today on kubutnu i368 I followed this how-to "http://kubuntu.org/announcements/kde4-alpha1.php", when I start kde4 the window manager loads and kde crashes after about 3 seconds (I am not sure if its the window manager that coses this crash) then it reloads without a window manager. The normal "crash popup" (the one with the bom inside of the kde gear) appears telling me:
"The application The KDE Session Manager (ksmserver) crashed and caused the signal 11 (SIHSEGV)" on the backtrace it says:
"(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1242461984 (LWP 6222)]
[KCrash handler]
#5  0xb74cf542 in ?? () from /usr/lib/libQtDBus.so.4
#6  0xb74a18c7 in ?? () from /usr/lib/libQtDBus.so.4
#7  0xb74a5c94 in ?? () from /usr/lib/libQtDBus.so.4
#8  0xb76846dc in QObject::event () from /usr/lib/libQtCore.so.4
#9  0xb6c57ea0 in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#10 0xb6c5a68e in QApplication::notify () from /usr/lib/libQtGui.so.4
#11 0xb7b88230 in KApplication::notify (this=0xbfbc1de8, receiver=0x8078e88, 
    event=0x8081df8)
    at /root/kde4libs/kde4libs-3.90.1/./kdeui/kernel/kapplication.cpp:287
#12 0xb7674a6b in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#13 0xb7676249 in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#14 0xb769ad2e in QEventDispatcherUNIX::processEvents ()
   from /usr/lib/libQtCore.so.4
#15 0xb6cd92bd in ?? () from /usr/lib/libQtGui.so.4
#16 0xb7673f61 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#17 0xb767406a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#18 0xb76765c8 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#19 0xb6c57ab7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#20 0xb7efb385 in kdemain (argc=1, argv=0xbfbc1f14)
    at /root/kde4base/kde4base-3.90.1/./workspace/ksmserver/main.cpp:247
#21 0x080487a2 in _start ()
#0  0xffffe410 in __kernel_vsyscall ()"

I've got:
amd 64bit 939 (remember running in x86), 1024mb hynix ram, xfx 7900gt, colorful nfroce4...
I am running nvidia bindery drivers version 1.0-9631 on xorg 7.2.0 (70200000) on 2.6.20-15-generic
Comment 1 Lubos Lunak 2007-06-01 16:58:42 UTC
I'm afraid the backtrace doesn't show anything useful. Can you reproduce the problem reliably?
Comment 2 Willem 2007-06-01 17:19:40 UTC
I think the problem lies at ksmserver and not kwin but after ksmserver caused a crash kwin doesn't reload, and if I close the error dialog everything disappears. If I load kde4 and quit and load it very quickly again there appears a x dialog saying:
"Could not start kmserver. Check your intallation"
Then kde loads up fine (well except for the missing backround....)

Anyways here it is:
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1242265376 (LWP 19003)]
[KCrash handler]
#5  0xb74ff542 in ?? () from /usr/lib/libQtDBus.so.4
#6  0xb74d18c7 in ?? () from /usr/lib/libQtDBus.so.4
#7  0xb74d5c94 in ?? () from /usr/lib/libQtDBus.so.4
#8  0xb76b46dc in QObject::event () from /usr/lib/libQtCore.so.4
#9  0xb6c87ea0 in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#10 0xb6c8a68e in QApplication::notify () from /usr/lib/libQtGui.so.4
#11 0xb7bb8230 in KApplication::notify (this=0xbfef0908, receiver=0x807f1e8, 
    event=0x80c5758)
    at /root/kde4libs/kde4libs-3.90.1/./kdeui/kernel/kapplication.cpp:287
#12 0xb76a4a6b in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#13 0xb76a6249 in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#14 0xb76cad2e in QEventDispatcherUNIX::processEvents ()
   from /usr/lib/libQtCore.so.4
#15 0xb6d092bd in ?? () from /usr/lib/libQtGui.so.4
#16 0xb76a3f61 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#17 0xb76a406a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#18 0xb76a65c8 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#19 0xb6c87ab7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#20 0xb7f2b385 in kdemain (argc=1, argv=0xbfef0a34)
    at /root/kde4base/kde4base-3.90.1/./workspace/ksmserver/main.cpp:247
#21 0x080487a2 in _start ()
#0  0xffffe410 in __kernel_vsyscall ()

After this crash I can just leave the error dialog open and run kwin via console then kde is usable...
Comment 3 Lubos Lunak 2007-06-04 11:25:49 UTC
I cannot reproduce and the backtrace is the same like the first one, it just says that the crash is possibly in some unknown place in the Qt DBUS library. I'm afraid there's nothing I can do for you with just this information.
Comment 4 Willem 2007-06-04 19:22:02 UTC
I don't know how to get any more information than that (I get the same backtrace each time). Is there thing I can do to give you more information? Thanks for trying though.
Comment 5 Lubos Lunak 2007-06-05 14:02:35 UTC
You could try compiling with debug enabled to improve the backtrace. I'd however suggest first upgrading or recompiling.
Comment 6 Willem 2007-06-06 14:15:55 UTC
I'm a little busy at the moment (exams) maybe in the holidays I'll compile it my self... like I said I followed this howto http://kubuntu.org/announcements/kde4-alpha1.php so I didn't compile it, it was in a deb package...
Comment 7 jos poortvliet 2007-06-06 15:18:30 UTC
if you didn't compile it, look for debug packages. Bram has made this excellent tutorial:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(bugs.kde.org should point to this,  yeah).

Comment 8 Chintalagiri Shashank 2007-06-07 01:18:56 UTC
I can confirm that the same thing happens on more that one system. I;ve had the identical symptoms on a 6 year old laptop (pentium III, 384 MB of ram and intel 815 chipset) as well as my new desktop (Core2Duo E6600, Intel 975x chipset, Gefore 8500gt graphics). Both were nearly pristine installations of ubuntu (note that KDE  3.4 was NOT installed on the same computer .. could this cause issues, perhaps due to missing dependencies in the packaging?)

Thanks
Comment 9 Lubos Lunak 2007-07-17 10:56:05 UTC

*** This bug has been marked as a duplicate of 145923 ***