Ubuntu
kdebase-workspace package

plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()

Bug #709522 reported by Seanbeansea
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-workspace

it happens always when I open Evolution.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: plasma-desktop 4:4.5.1-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Jan 28 22:59:30 2011
ExecutablePath: /usr/bin/plasma-desktop
ProcCmdline: /usr/bin/plasma-desktop --nocrashhandler
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xe5b416 <__kernel_vsyscall+2>: ret
 PC (0x00e5b416) ok
 destination "(%esp)" (0xbf83117c) ok
 SP (0xbf83117c) ok
 Reason could not be automatically determined. (Unhandled exception in kernel code?)
Signal: 11
SourcePackage: kdebase-workspace
Stacktrace:
 #0 0x00e5b416 in __kernel_vsyscall ()
 No symbol table info available.
 Cannot access memory at address 0xbf83117c
StacktraceTop: __kernel_vsyscall ()
Title: plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()
UserGroups: adm admin audio cdrom dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Seanbeansea (seanbeansea) wrote :
Revision history for this message
Seanbeansea (seanbeansea) wrote :

system is uptodate.
After that Evolution is ready for use and desktop is ok.

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

This crash has the same stack trace characteristics as bug #405463. 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
Harald Sitter (apachelogger) wrote :

Seems the crash data is inconclusive, so I'll have to close this as invalid as we'll not be able to find the cause, unfortunately. Thanks for the report though.

visibility: private → public
Changed in kdebase-workspace (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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