Version: (using KDE Devel) Installed from: Compiled sources OS: Linux (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 -1241904928 (LWP 12231)] [KCrash handler] #6 0xb7557542 in ?? () from /usr/lib/libQtDBus.so.4 #7 0xb75298c7 in ?? () from /usr/lib/libQtDBus.so.4 #8 0xb752dc94 in ?? () from /usr/lib/libQtDBus.so.4 #9 0xb770c6dc in QObject::event () from /usr/lib/libQtCore.so.4 #10 0xb6cdfea0 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #11 0xb6ce268e in QApplication::notify () from /usr/lib/libQtGui.so.4 #12 0xb7c0f230 in KApplication::notify (this=0xbfd20018, receiver=0x807d820, event=0x80dbed0) at /root/kde4libs/kde4libs-3.90.1/./kdeui/kernel/kapplication.cpp:287 #13 0xb76fca6b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #14 0xb76fe249 in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #15 0xb7722d2e in QEventDispatcherUNIX::processEvents () from /usr/lib/libQtCore.so.4 #16 0xb6d612bd in ?? () from /usr/lib/libQtGui.so.4 #17 0xb76fbf61 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #18 0xb76fc06a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #19 0xb76fe5c8 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #20 0xb6cdfab7 in QApplication::exec () from /usr/lib/libQtGui.so.4 #21 0xb7f82385 in kdemain (argc=1, argv=0xbfd20144) at /root/kde4base/kde4base-3.90.1/./workspace/ksmserver/main.cpp:247 #22 0x080487a2 in _start ()
installed from kubuntu repositories, followed the exact instruction on http://kubuntu.org/announcements/kde4-alpha1.php
I think you forgot to provide additional information about the problem other than the backtrace (which doesn't provide any useful information).
what information do you need? I just installed followed the instruction from http://kubuntu.org/announcements/kde4-alpha1.php and when i login with KDE 4 session, that's the first thing pop up, and when i click OK, it will close that session and start over again from KDM.
I don't know. It works fine here and presumably for others as well, otherwise more people would have complained, so there must be something special about your case.
I've got the same error with the alpha packages
I'm having the exact same problem with the alpha packages from the Kubuntu repository and following the provided instructions
*** Bug 146024 has been marked as a duplicate of this bug. ***
Is this bugreport still valid? If yes, I suggest you install debuginfo packages and provide another backtrace - there's nothing to do with this one.
Hi everybody, I'm not the original reporter, but I've just run into a similar issue when I've tried to install the KDE4 packages from Ubuntu on my new laptop: I recently installed the KDE4 packages available from: deb http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu gutsy main I'm having Ubuntu 7.10 (Gutsy Gibbon) obviously. This seems to be KDE 4.0.1. Installation went fine. When I try to login from GDM I always get the same error upon login: - KDE4 splash screen starts - Upon the fourth (or so) icon, I get a crash report behind the splash screen - Clicking into the splash closes it - The crash report informs me that ksmserver crashed - Closing the crash report, logs me out again and brings me back to GDM I installed the appropriate debug packages now and captured a backtrace: ---------- snip ---------- Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1239562560 (LWP 6628)] [KCrash handler] #5 0xb7dd8749 in vfprintf () from /lib/tls/i686/cmov/libc.so.6 #6 0xb7de1902 in fprintf () from /lib/tls/i686/cmov/libc.so.6 #7 0xb7f02a97 in write_iceauth (addfp=0x0, removefp=0x0, entry=0x80c8330) at /build/buildd/kdebase-workspace-4.0.1/ksmserver/server.cpp:346 #8 0xb7f02d8f in SetAuthentication (count=3, listenObjs=0x80c6ea0, authDataEntries=0xb7f20ee8) at /build/buildd/kdebase-workspace-4.0.1/ksmserver/server.cpp:422 #9 0xb7f03d69 in KSMServer (this=0x80c65f0, windowManager=@0xbfcbf5c4, _only_local=false) at /build/buildd/kdebase-workspace-4.0.1/ksmserver/server.cpp:664 #10 0xb7f008c9 in kdemain (argc=1, argv=0xbfcbf754) at /build/buildd/kdebase-workspace-4.0.1/ksmserver/main.cpp:240 #11 0x08048582 in main (argc=-1208891278, argv=0x80c75f0) at /build/buildd/kdebase-workspace-4.0.1/obj-i486-linux-gnu/ksmserver/ksmserver_dummy.cpp:3 #12 0xb7db1050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #13 0x080484f1 in _start () #0 0xffffe410 in __kernel_vsyscall () ---------- snip ---------- Any ideas? Help is greatly appreciated! For your info: I'm running on a Dell XPS M1330 w/ intel x3100 graphics card ("Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller"). Running the "intel" driver. I don't know if this has something to do with this issue, but my hostname was something like "dell-desktop" or so and I changed it to "bartimäus" (note the umlaut). ciao, daniel :)
Hi again, I've done some more testing and was able to log in to KDE 4 now! What I've done: I renamed my machine from "bartimäus" to "bartimaeus". After that, logging in to KDE 4 worked like a charm. I'm typing this from within my KDE 4 session now. So the umlaut in the hostname seems to be the culprit. I don't know whether is is common practice nowadays to support umlauts, I just wanted to try it out w/ my new box. Seems to be not yet supported by every application, I guess... ciao, daniel :)
Daniel: First of all, your problem is not "similar". Just because in both cases ksmserver crashes doesn't mean it's similar. I've fixed the crash, but apparently the underlying system is not ready for such hostnames.
Waiting for a response.
Hi Lubos, you're of course right. I don't know why I've come to the conclusion that my issue is similar, must have been in a hurry. Thanks for fixing this issue nonetheless. I guess you are not waiting for my response, as I am no the original reporter? Anyways, my bug is indeed fixed (running KDE 4.1.2 now).