[power]: gnome-settings-daemon crashed with SIGSEGV

Bug #962926 reported by Erick Brunzell
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Just got this error report after booting to the live desktop using Ubuntu i386 20120323. Other than the apport warning I see nothing actually wrong.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.3.92-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CasperVersion: 1.312
Date: Fri Mar 23 09:36:44 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120323)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=
 TERM=linux
 PATH=(custom, no user)
 LANG=
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
Title: [power]: gnome-settings-daemon crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Erick Brunzell (lbsolost) wrote :
Revision history for this message
Erick Brunzell (lbsolost) wrote :

Just thought to mention that this hardware boots to Unity-2D (P4M800).

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 this software better. This particular crash has already been reported and is a duplicate of bug #962458, 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
visibility: private → public
tags: removed: need-i386-retrace
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/962926

tags: added: iso-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
Revision history for this message
Erick Brunzell (lbsolost) wrote :

I truly believe this is not a duplicate of either bug 965487 or bug 965458.

The first clearly says "Boot a live session and choose to install ubuntu. Wait a few seconds and the message will come up."

The second says "This crash occurs immediately after the parted_server crashes".

Neither of those apply here!!!!!!!!!!!!!!!!

If I boot letting the non-interactive boot screen pass and wait to just choose between trying or installing Ubuntu I end up with a language notification in the menu-bar/top panel, and it's quickly followed by the apport warning that spurred me to report this bug ............... and it still persists with Ubuntu live i386 20120327.1!

But if I press a key when the non-interactive screen appears so I can boot to the actual boot menu, then select my default English, then select Try Ubuntu from the old-style menu all is well ............... no language notification and no apport warning.

Please see this screenshot:

https://launchpadlibrarian.net/98133896/Screenshot%20from%202012-03-24%2010%3A07%3A15.png

Revision history for this message
Erick Brunzell (lbsolost) wrote :

I hope I changed the duplicate status to NO. I've never tried that before.

Revision history for this message
Erick Brunzell (lbsolost) wrote :

I'm not seeing the apport error report with Ubuntu i386 20120328, hopefully this means it's fixed ;^)

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.