plasma-netbook crashed with SIGSEGV in __kernel_vsyscall()

Bug #506802 reported by Scott Kitterman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-workspace

Got repeated crashes in rapid succession after manually starting (via systemsettings) plasma-netbook.

Kubuntu Alpha 2, KDE SC 4.3.90

ProblemType: Crash
Architecture: i386
Date: Wed Jan 13 00:29:19 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/plasma-netbook
InstallationMedia: Kubuntu-Netbook 9.10 "Karmic Koala" - Release i386 (20091027)
Package: plasma-netbook 4:4.3.90-0ubuntu2
ProcCmdline: plasma-netbook --nocrashhandler
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0x19c422 <__kernel_vsyscall+2>: ret
 PC (0x0019c422) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: kdebase-workspace
Stacktrace:
 #0 0x0019c422 in __kernel_vsyscall ()
 No symbol table info available.
 Cannot access memory at address 0xbfbac43c
StacktraceTop: __kernel_vsyscall ()
Tags: lucid
Title: plasma-netbook crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.32-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (process:1926): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (process:2119): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #410871, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.