kscreenlocker crashed with SIGSEGV

Bug #566395 reported by chiefgeek
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-workspace

This happens mainly on boot

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: kdebase-workspace-bin 4:4.4.2-0ubuntu13
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Apr 18 21:15:59 2010
ExecutablePath: /usr/lib/kde4/libexec/kscreenlocker
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/kde4/libexec/kscreenlocker --forcelock
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
SegvAnalysis:
 Segfault happened at: 0x6efb36: movl $0x728c40,(%edx)
 PC (0x006efb36) ok
 source "$0x728c40" ok
 destination "(%edx)" (0x753611f4) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: kdebase-workspace
Stacktrace:
 #0 0x006efb36 in ?? () from /usr/lib/nvidia-current/libGL.so.1
 No symbol table info available.
 Cannot access memory at address 0xf
StacktraceTop: ?? () from /usr/lib/nvidia-current/libGL.so.1
ThreadStacktrace:
 .
 Thread 1 (Thread 21032):
 #0 0x006efb36 in ?? () from /usr/lib/nvidia-current/libGL.so.1
 No symbol table info available.
 Cannot access memory at address 0xf
Title: kscreenlocker crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (process:1508): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
chiefgeek (phillip-connor) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x006efb36 in ?? () from /usr/lib/nvidia-current/libGL.so.1
 No symbol table info available.
 Cannot access memory at address 0xf
StacktraceTop: ?? () from /usr/lib/nvidia-current/libGL.so.1
ThreadStacktrace:
 .
 Thread 1 (process 21032):
 #0 0x006efb36 in ?? () from /usr/lib/nvidia-current/libGL.so.1
 No symbol table info available.
 Cannot access memory at address 0xf

tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
affects: kdebase-workspace (Ubuntu) → nvidia-graphics-drivers (Ubuntu)
Bryce Harrington (bryce)
tags: added: kubuntu
visibility: private → public
Changed in nvidia-graphics-drivers (Ubuntu):
status: New → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

Sorry, this seems to be a non-specific crash in kde without a valid stack trace. It cannot be analyzed as reported.

Changed in nvidia-graphics-drivers (Ubuntu):
status: Confirmed → Invalid
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.