Version: 0.0.1 (using 4.0.2 (KDE 4.0.2), Kubuntu packages) Compiler: gcc OS: Linux (i686) release 2.6.22-14-generic KDE 4 is not operated. Dont start. singal 11(SIGSEGV)
not enough information.
I know sorry. This will be enough? (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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 -1247660320 (LWP 8373)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall () [Current thread is 0 (process 8373)] Thread 1 (Thread -1247660320 (LWP 8373)): #0 0xffffe410 in __kernel_vsyscall () #1 0xb7eb6e70 in nanosleep () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7eb6ca7 in sleep () from /lib/tls/i686/cmov/libc.so.6 #3 0xb784b640 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5 #4 0x00000001 in ?? () #5 0x00000000 in ?? () #0 0xffffe410 in __kernel_vsyscall ()
Another times in start kde4 was 1247336763 (LWP 7884)
can you install debbuging symbol with your distribution package...It will help us to find the problem...
Lukasz: Where did you get the KDE4 packages for Kubuntu? Did you install a recent KDE4 Kubuntu Live CD Live CD or did you install KDE4 packages through adept?
yes, unfortunately there are no debugging symbols in that backtract; Alexis has the right idea though (install the debug packages). i'm pretty sure that this is just the same upgrade bug we've already seen before though.
I have kubuntu 7.10. I instal KDE4 from: http://kubuntu.org/announcements/kde-4.0.2.php What mean "install debbuging symbol? How?
You need to install the kde4-packages ending with debug or dbg, not sure, what it is in Kubuntu... Lukas
i was install python-kde4-dbg and i was saw: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1248172320 (LWP 31690)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall () [Current thread is 0 (process 31690)] Thread 1 (Thread -1248172320 (LWP 31690)): #0 0xffffe410 in __kernel_vsyscall () #1 0xb7e39e70 in nanosleep () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7e39ca7 in sleep () from /lib/tls/i686/cmov/libc.so.6 #3 0xb77ce640 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5 #4 0x00000001 in ?? () #5 0x00000000 in ?? () #0 0xffffe410 in __kernel_vsyscall () So u see it's nothing new :( I dont know what to do now?
http://techbase.kde.org/index.php?title=Development/Tutorials/Debugging/How_to_create_useful_crash_reports You should install packages like kde4libs-dbg, kde4base-dbg etc. I think (I don't use Kubuntu). Simply the kde4-packages with -dbg suffix.
i was install kde4libs-dbg, kde4base-dbg etc, and now i saw: Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1247385888 (LWP 2105)] [KCrash handler] #6 0x081639e3 in ?? () #7 0xb7d88f3f in Plasma::Applet::flushUpdatedConstraints (this=0x810d018) at /build/buildd/kdebase-workspace-4.0.2/libs/plasma/applet.cpp:699 #8 0xb7db4b62 in Plasma::Corona::loadApplets (this=0x80ff3a8, configName=@0x81064c0) at /build/buildd/kdebase-workspace-4.0.2/libs/plasma/corona.cpp:224 #9 0xb7db5527 in Plasma::Corona::loadApplets (this=0x80ff3a8) at /build/buildd/kdebase-workspace-4.0.2/libs/plasma/corona.cpp:296 #10 0xb7fd1ddc in PlasmaApp::corona (this=0x8061628) at /build/buildd/kdebase-workspace-4.0.2/plasma/plasma/plasmaapp.cpp:219 #11 0xb7fd4aca in RootWidget (this=0x80fee18) at /build/buildd/kdebase-workspace-4.0.2/plasma/plasma/rootwidget.cpp:49 #12 0xb7fd2786 in PlasmaApp (this=0x8061628, display=0x805b048, visual=134592384, colormap=27262977) at /build/buildd/kdebase-workspace-4.0.2/plasma/plasma/plasmaapp.cpp:156 #13 0xb7fd2f79 in PlasmaApp::self () at /build/buildd/kdebase-workspace-4.0.2/plasma/plasma/plasmaapp.cpp:96 #14 0xb7fd17ac in kdemain (argc=1, argv=0xbfd4b024) at /build/buildd/kdebase-workspace-4.0.2/plasma/plasma/main.cpp:51 #15 0x08048582 in main (argc=1466120, argv=0xb7e66000) at /build/buildd/kdebase-workspace-4.0.2/obj-i486-linux-gnu/plasma/plasma/plasma-qgv_dummy.cpp:3 #16 0xb7e7d050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #17 0x080484f1 in _start () #0 0xffffe410 in __kernel_vsyscall () sommebody help me?
Reopening: we have a backtrace with at least function names, so it might be possible to do something with it. Also, it's been reported again by another user.
*** Bug 159662 has been marked as a duplicate of this bug. ***
It seems, that Kubuntu and KDE 4.0.2 generates troubles. Please try again with KDE 4.0.3 and rename ./kde4 to ./kde4_old and do the same with ./kde. If it works after. Please close the bug.
Like descibed in another bug, try this first: remove your ~/.kde/share/config/plasma-appletsrc and try again.
With 4.1 just around the corner, it's time to close off 4.0 bugs. If you get similar crashes with 4.1 please open a new bug with a full backtrace.