plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()

Bug #506606 reported by steampoweredlawngnome
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-workspace

Description: Ubuntu lucid (development branch)
Release: 10.04

Since getting the 4:4.3.90-0ubuntu2 packages for Ubuntu Lucid, Plasma is crashing any time I interact with it. It allows me to perform an action, like open a folder from the quick folder access or expand the notification area, but immediately crashes after the action is complete.

ProblemType: Crash
Architecture: i386
Date: Tue Jan 12 13:32:20 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/plasma-desktop
NonfreeKernelModules: nvidia
Package: plasma-desktop 4:4.3.90-0ubuntu2
ProcCmdline: plasma-desktop --nocrashhandler
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0xeae422 <__kernel_vsyscall+2>: ret
 PC (0x00eae422) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: kdebase-workspace
Stacktrace:
 #0 0x00eae422 in __kernel_vsyscall ()
 No symbol table info available.
 Cannot access memory at address 0xbfa1c0ac
StacktraceTop: __kernel_vsyscall ()
Tags: lucid
Title: plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users vboxusers
XsessionErrors:
 (polkit-gnome-authentication-agent-1:20613): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (process:20618): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (exe:21456): Gdk-WARNING **: XID collision, trouble ahead
 (exe:21456): Gdk-WARNING **: XID collision, trouble ahead

Revision history for this message
steampoweredlawngnome (steampoweredlawngnome) wrote :
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
Jonathan Thomas (echidnaman) wrote :

Could you install kdebase-workspace-dbg and get a crash log from the KDE crash handler, which should pop up when plasma-desktop crashes for the first time?

Changed in kdebase-workspace (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
steampoweredlawngnome (steampoweredlawngnome) wrote : Re: [Bug 506606] Re: plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()

I installed all the debug packages, crashed plasma and hit the "developer
information" tab. It said "This crash information is not useful" and
"Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault"

The "Install Debug Symbols" button is greyed out, indicating I have all the
necessary debugging symbols. If I try to re-load the crash information, the
crash handler crashes.

On Tue, Jan 12, 2010 at 4:00 PM, Jonathan Thomas <email address hidden>wrote:

> Could you install kdebase-workspace-dbg and get a crash log from the KDE
> crash handler, which should pop up when plasma-desktop crashes for the
> first time?
>
> ** Changed in: kdebase-workspace (Ubuntu)
> Status: New => Incomplete
>
> ** Visibility changed to: Public
>
> --
> plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()
> https://bugs.launchpad.net/bugs/506606
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “kdebase-workspace” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: kdebase-workspace
>
> Description: Ubuntu lucid (development branch)
> Release: 10.04
>
> Since getting the 4:4.3.90-0ubuntu2 packages for Ubuntu Lucid, Plasma is
> crashing any time I interact with it. It allows me to perform an action,
> like open a folder from the quick folder access or expand the notification
> area, but immediately crashes after the action is complete.
>
> ProblemType: Crash
> Architecture: i386
> Date: Tue Jan 12 13:32:20 2010
> DistroRelease: Ubuntu 10.04
> ExecutablePath: /usr/bin/plasma-desktop
> NonfreeKernelModules: nvidia
> Package: plasma-desktop 4:4.3.90-0ubuntu2
> ProcCmdline: plasma-desktop --nocrashhandler
> ProcEnviron:
> LANGUAGE=
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
> SegvAnalysis:
> Segfault happened at: 0xeae422 <__kernel_vsyscall+2>: ret
> PC (0x00eae422) ok
> Reason could not be automatically determined.
> Signal: 11
> SourcePackage: kdebase-workspace
> Stacktrace:
> #0 0x00eae422 in __kernel_vsyscall ()
> No symbol table info available.
> Cannot access memory at address 0xbfa1c0ac
> StacktraceTop: __kernel_vsyscall ()
> Tags: lucid
> Title: plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()
> Uname: Linux 2.6.31-11-generic i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users
> vboxusers
> XsessionErrors:
> (polkit-gnome-authentication-agent-1:20613): GLib-CRITICAL **:
> g_once_init_leave: assertion `initialization_value != 0' failed
> (process:20618): GLib-CRITICAL **: g_once_init_leave: assertion
> `initialization_value != 0' failed
> (exe:21456): Gdk-WARNING **: XID collision, trouble ahead
> (exe:21456): Gdk-WARNING **: XID collision, trouble ahead
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/506606/+subscribe
>

Revision history for this message
steampoweredlawngnome (steampoweredlawngnome) wrote :

Never mind, creating a new profile solves the problem. Thought it was a bug because it happened on both of the machines I'm testing Lucid on, but if blowing away my profile solves it, it's probably not a bug.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

I guess as long as everything's working fine now, all's well that ends well. :-)

Changed in kdebase-workspace (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
steampoweredlawngnome (steampoweredlawngnome) wrote :

When I set my profile back up it does it again. I think it might have something to do with multiple panels because it started crashing again once I added all my panels back.

Changed in kdebase-workspace (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
steampoweredlawngnome (steampoweredlawngnome) wrote :

Attached is a screenshot of the layout of my panels. They right and bottom ones are typically set on auto hide, the top one is set so that windows can cover it. I've unhidden them all for the purpose of the screenshot. Plasma seems to have a lot of problems with multiple panels....

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

How many stars does your crash get in the KDE crash handler? None at all? If it has at least two, then the backtrace might be a bit useful.

Revision history for this message
steampoweredlawngnome (steampoweredlawngnome) wrote :

No stars unfortunately.

On Wed, Jan 13, 2010 at 7:25 AM, Jonathan Thomas <email address hidden>wrote:

> How many stars does your crash get in the KDE crash handler? None at
> all? If it has at least two, then the backtrace might be a bit useful.
>
> --
> plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()
> https://bugs.launchpad.net/bugs/506606
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “kdebase-workspace” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: kdebase-workspace
>
> Description: Ubuntu lucid (development branch)
> Release: 10.04
>
> Since getting the 4:4.3.90-0ubuntu2 packages for Ubuntu Lucid, Plasma is
> crashing any time I interact with it. It allows me to perform an action,
> like open a folder from the quick folder access or expand the notification
> area, but immediately crashes after the action is complete.
>
> ProblemType: Crash
> Architecture: i386
> Date: Tue Jan 12 13:32:20 2010
> DistroRelease: Ubuntu 10.04
> ExecutablePath: /usr/bin/plasma-desktop
> NonfreeKernelModules: nvidia
> Package: plasma-desktop 4:4.3.90-0ubuntu2
> ProcCmdline: plasma-desktop --nocrashhandler
> ProcEnviron:
> LANGUAGE=
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
> SegvAnalysis:
> Segfault happened at: 0xeae422 <__kernel_vsyscall+2>: ret
> PC (0x00eae422) ok
> Reason could not be automatically determined.
> Signal: 11
> SourcePackage: kdebase-workspace
> Stacktrace:
> #0 0x00eae422 in __kernel_vsyscall ()
> No symbol table info available.
> Cannot access memory at address 0xbfa1c0ac
> StacktraceTop: __kernel_vsyscall ()
> Tags: lucid
> Title: plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()
> Uname: Linux 2.6.31-11-generic i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users
> vboxusers
> XsessionErrors:
> (polkit-gnome-authentication-agent-1:20613): GLib-CRITICAL **:
> g_once_init_leave: assertion `initialization_value != 0' failed
> (process:20618): GLib-CRITICAL **: g_once_init_leave: assertion
> `initialization_value != 0' failed
> (exe:21456): Gdk-WARNING **: XID collision, trouble ahead
> (exe:21456): Gdk-WARNING **: XID collision, trouble ahead
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/506606/+subscribe
>

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this still an issue with KDE 4.4.0?

Revision history for this message
steampoweredlawngnome (steampoweredlawngnome) wrote :

No, this issue is resolved.

On Mon, Feb 15, 2010 at 9:04 AM, Jonathan Thomas <email address hidden>wrote:

> Is this still an issue with KDE 4.4.0?
>
> --
> plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()
> https://bugs.launchpad.net/bugs/506606
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “kdebase-workspace” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: kdebase-workspace
>
> Description: Ubuntu lucid (development branch)
> Release: 10.04
>
> Since getting the 4:4.3.90-0ubuntu2 packages for Ubuntu Lucid, Plasma is
> crashing any time I interact with it. It allows me to perform an action,
> like open a folder from the quick folder access or expand the notification
> area, but immediately crashes after the action is complete.
>
> ProblemType: Crash
> Architecture: i386
> Date: Tue Jan 12 13:32:20 2010
> DistroRelease: Ubuntu 10.04
> ExecutablePath: /usr/bin/plasma-desktop
> NonfreeKernelModules: nvidia
> Package: plasma-desktop 4:4.3.90-0ubuntu2
> ProcCmdline: plasma-desktop --nocrashhandler
> ProcEnviron:
> LANGUAGE=
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
> SegvAnalysis:
> Segfault happened at: 0xeae422 <__kernel_vsyscall+2>: ret
> PC (0x00eae422) ok
> Reason could not be automatically determined.
> Signal: 11
> SourcePackage: kdebase-workspace
> Stacktrace:
> #0 0x00eae422 in __kernel_vsyscall ()
> No symbol table info available.
> Cannot access memory at address 0xbfa1c0ac
> StacktraceTop: __kernel_vsyscall ()
> Tags: lucid
> Title: plasma-desktop crashed with SIGSEGV in __kernel_vsyscall()
> Uname: Linux 2.6.31-11-generic i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users
> vboxusers
> XsessionErrors:
> (polkit-gnome-authentication-agent-1:20613): GLib-CRITICAL **:
> g_once_init_leave: assertion `initialization_value != 0' failed
> (process:20618): GLib-CRITICAL **: g_once_init_leave: assertion
> `initialization_value != 0' failed
> (exe:21456): Gdk-WARNING **: XID collision, trouble ahead
> (exe:21456): Gdk-WARNING **: XID collision, trouble ahead
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/506606/+subscribe
>

Changed in kdebase-workspace (Ubuntu):
status: Incomplete → Fix Released
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.