kwin crashed with SIGSEGV in __kernel_vsyscall()

Bug #458903 reported by panf
134
This bug affects 28 people
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kdebase-workspace

kwin crashed with SIGSEGV in __kernel_vsyscall()

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Oct 23 12:04:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kwin
NonfreeKernelModules: nvidia
Package: kde-window-manager 4:4.3.2-0ubuntu6
ProcCmdline: kwin -session 1019715710514d000125438393100000032010000_1256200814_840430
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x237422 <__kernel_vsyscall+2>: ret
 PC (0x00237422) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: kdebase-workspace
Stacktrace:
 #0 0x00237422 in __kernel_vsyscall ()
 No symbol table info available.
 Cannot access memory at address 0xbfc080fc
StacktraceTop: __kernel_vsyscall ()
ThreadStacktrace:
 .
 Thread 1 (Thread 1749):
 #0 0x00237422 in __kernel_vsyscall ()
 No symbol table info available.
 Cannot access memory at address 0xbfc080fc
Title: kwin crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:1939): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
panf (andrei-panfilov) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__kernel_vsyscall ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdebase-workspace (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Unfortunately the backtrace that was autosubmitted is too damaged to be of any use. Thanks for reporting this bug all the same.

visibility: private → public
Changed in kdebase-workspace (Ubuntu):
status: New → Invalid
Revision history for this message
avlas (avlas) wrote :

I think that I have the same issue on 64 bits

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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