plasma-netbook crashed with SIGSEGV in __kernel_vsyscall()

Bug #410871 reported by Scott Kitterman on 2009-08-08
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kde-workspace (Ubuntu)

Bug Description

Binary package hint: plasma-netbook

Crash when starting plasma-netbook by hand.

ProblemType: Crash
Architecture: i386
Date: Sat Aug 8 18:07:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/plasma-netbook
NonfreeKernelModules: wl
Package: plasma-netbook 0.0~svn1007436-0ubuntu1
ProcCmdline: plasma-netbook
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
Signal: 11
SourcePackage: plasma-netbook
Stacktrace: #0 0x00653422 in __kernel_vsyscall ()
StacktraceTop: __kernel_vsyscall ()
 Thread 1 (Thread 3589):
 #0 0x00653422 in __kernel_vsyscall ()
Title: plasma-netbook crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
 Segfault happened at: 0x653422 <__kernel_vsyscall+2>: ret
 PC (0x00653422) ok
 destination "(%esp)" (0xbfcdee8c) ok
 SP (0xbfcdee8c) ok
 Reason could not be automatically determined. (Unhandled exception in kernel code?)
SegvReason: Reason could not be automatically determined. (Unhandled exception in kernel code?)

Scott Kitterman (kitterman) wrote :

StacktraceTop:__kernel_vsyscall ()

Changed in plasma-netbook (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Artur Souza (MoRpHeUz) (asouza) wrote :

I need a complete backtrace to hunt this one.

Jonathan Thomas (echidnaman) wrote :

Is this still an issue for anybody with the final version of Kubuntu 9.10? (Or better yet, with KDE 4.4 beta?)

Changed in plasma-netbook (Ubuntu):
status: New → Incomplete
Scott Kitterman (kitterman) wrote :

Yes. Dupe is mine with RC1

Changed in plasma-netbook (Ubuntu):
status: Incomplete → Confirmed
tags: added: iso-testing
Kees Cook (kees) on 2010-04-22
description: updated
affects: plasma-netbook (Ubuntu) → ubuntu
Changed in ubuntu:
status: Confirmed → New
status: New → Invalid
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Harald Sitter (apachelogger) wrote :

Still reproducible? if so... drkonqi backtrace pretty please.

affects: kdebase-workspace (Ubuntu) → kde-workspace (Ubuntu)
Changed in kde-workspace (Ubuntu):
status: New → Incomplete
Changed in kde-workspace (Ubuntu):
status: New → Confirmed
Launchpad Janitor (janitor) wrote :

[Expired for kde-workspace (Ubuntu) because there has been no activity for 60 days.]

Changed in kde-workspace (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers