klauncher crashed with SIGSEGV in __kernel_vsyscall()

Bug #174813 reported by Xavier Fung
8
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: kde4libs

After updating to KDE 3.97 package, it simply crash and revert to the login screen after showing the splash screen of KDE. This also happens to other linux distribution which packages KDE 4 RC, and I suspect this is an upstream issue.

ProblemType: Crash
Architecture: i386
Date: Sat Dec 8 11:23:00 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/kde4/lib/kde4/libexec/klauncher
NonfreeKernelModules: cdrom
Package: kdelibs5 4:3.97.0-1ubuntu1
PackageArchitecture: i386
ProcCmdline: klauncher
ProcCwd: /home/xavier
ProcEnviron:
 PATH=/usr/lib/kde4/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=zh_HK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kde4libs
StacktraceTop:
 __kernel_vsyscall ()
 poll () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: klauncher crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux xavier 2.6.24-1-386 #1 Fri Dec 7 21:27:41 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare scanner video

Revision history for this message
Xavier Fung (xavier114fch) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__kernel_vsyscall ()
poll () from /lib/tls/i686/cmov/libc.so.6
?? () from /usr/lib/libglib-2.0.so.0
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in kde4libs:
importance: Undecided → Medium
Revision history for this message
Colin Stark (cstark) wrote :

The last stacktrace posted was running ubuntu 8.04 (hardy) alpha version. i'm alternating between gnome and kde4 right now. the bug reporter didn't pop up until i'd logged into gnome 2 or 3 times after logging in to kde4. not sure why or if that's relevant.

Revision history for this message
Marco Maini (maini10) wrote :

Unfortunately, your backtrace is not complete and it's not possible to determine what exactly happened. However, your bug looks like bug 141418 and I'll mark as duplicate. If you are able to reproduce it, you are strongly invited to post a new backtrace.
Thanks for your help.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.