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

[Peter Hurley]

This crash occurs immediately after the parted_server crashes while installing Precise Beta 1 22/03/12 from LiveCD.

See bug# 962455.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.3.92-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-19.31-generic 3.2.12
Uname: Linux 3.2.0-19-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.312
Date: Thu Mar 22 19:12:57 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120322)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=
 TERM=linux
 PATH=(custom, no user)
 LANG=
SegvAnalysis:
 Segfault happened at: 0x7f809f5f0bba: mov 0x8(%rbp),%r11d
 PC (0x7f809f5f0bba) ok
 source "0x8(%rbp)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%r11d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
Title: [power]: gnome-settings-daemon crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 engine_get_icon_priv (manager=0x1fd30b0, device_kind=UP_DEVICE_KIND_BATTERY, warning=WARNING_CRITICAL, use_state=0) at gsd-power-manager.c:596
 engine_get_icon (manager=0x1fd30b0) at gsd-power-manager.c:637
 engine_recalculate_state_icon (manager=0x1fd30b0) at gsd-power-manager.c:690
 engine_recalculate_state (manager=0x1fd30b0) at gsd-power-manager.c:768
 engine_device_changed_cb (client=<optimized out>, device=0x1fbe270, manager=0x1fd30b0) at gsd-power-manager.c:1847

[Launchpad Janitor (janitor)]

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

[Erick Brunzell (lbsolost)]

I have a bit more info regarding duplicate bug 962926, not sure if it'll effect the duplicate status or not. Just a quick recap; I'm using the Ubuntu i386 20120323 image.

I decided to go ahead and use this image to prepare partitions, free space, etc to prepare for iso/upgrade testing on three vastly different sets of hardware:

AMD Sempron Processor LE-1250 @ 2.2 GHz
nVidia C61 [GeForce 7025 / nForce 630a] (rev a2)
nVidia MCP61 High Definition Audio (rev a2)
nVidia MCP61 Ethernet (rev a2)
2GB DDR2 RAM

*********************************************

Intel Atom CPU 230 @ 1.60GHz
Intel 82945G/GZ Integrated Graphics Controller (rev 02)
Intel N10/ICH 7 Family High Definition Audio Controller (rev 01)
Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
2GB DDR2 RAM

*********************************************

VIA C7 CPU @ 1500MHz
VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
1GB DDR2 RAM

The behavior is inconsistent but does NOT seem to be hardware related. The one thing that I do notice is that any time this crash report appears the Ubuntu top panel/aka menu bar shows a language notification just after booting to the live desktop. If no language notification appears then there is no crash report.

As I said, bug 962926 may not be a true duplicate of this bug due to the difference in cause based on the explanation given for this bug relating to parted. But I'm not technically advanced enough to know :^(

Something language related that I have noticed is using either the netboot mini.iso or the Ubuntu alternate images result in bug 931191. I don't see that using recent Xubuntu or Lubuntu alternate images.

I hope I'm not just adding to the confusion.

[Erick Brunzell (lbsolost)]

Once again, this info is in regards to duplicate bug 962926, and I'm unsure about the duplicate status. I'm testing the 20120324 i386 Ubuntu image and upon the intial boot see this behavior so I took a screenshot.

[Erick Brunzell (lbsolost)]

Immediately after posting comment #7 I rebooted and this time I pressed enter when the non-interactive screen appeared, accepted the default English by pressing enter, then selected Try Ubuntu. This time no language notification appeared and there was no crash report.

The first boot that produced the error was done after testing disc integrity and then just letting the boot continue until only the Try or Install options appeared and selecting Try.

[Ubuntu QA Website (ubuntuqa)]

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/962458

[Erick Brunzell (lbsolost)]

I'm still seeing the behavior described in my comments about duplicate bug 962926 with i386 20120325, but if I begin by pressing a key when the non-interactive screen appears, then select language, and then select try Ubuntu all is well.

[RedSingularity (redsingularity)]

Confirmed. I get this every time I boot to the desktop. i386.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[RedSingularity (redsingularity)]

Marking as a duplicate of bug 964654.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Peter Hurley (phurley)]

Bug 964654 may not be a duplicate. That report has no valid stack backtrace to confirm that it even originates from the same function, and it's on a different arch. Please un-duplicate this bug.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Peter Hurley (phurley)]

@Sebastien,

Before I report this upstream, is there a reason why you believe this is an upstream bug and not related to any of the *over 6000 lines* of debian + ubuntu patches?