plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()

Bug #559916 reported by pol
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-workspace

no more info

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plasma-desktop 4:4.4.2-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sat Apr 10 11:50:43 2010
ExecutablePath: /usr/bin/plasma-desktop
ProcCmdline: plasma-desktop --nocrashhandler
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x3e0422 <__kernel_vsyscall+2>: ret
 PC (0x003e0422) ok
 destination "(%esp)" (0xbfec876c) ok
 SP (0xbfec876c) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: kdebase-workspace
Stacktrace:
 #0 0x003e0422 in __kernel_vsyscall ()
 No symbol table info available.
 Cannot access memory at address 0xbfec876c
StacktraceTop: __kernel_vsyscall ()
Title: plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()
UserGroups: adm admin staff sudo
XsessionErrors: (process:3397): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
pol (xtekhne) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #506606. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Unfortunately the crash log automatically submitted by apport was too damaged to be of use. We thank you for reporting this bug all the same.

Changed in kdebase-workspace (Ubuntu):
status: New → Invalid
visibility: private → public
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.