[power]: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode()

Bug #946124 reported by Amir Zarrin on 2012-03-04
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-desktop3 (Ubuntu)
Medium
Unassigned

Bug Description

it happened any time that i lunch ubuntu,
I have installed it with in the windows.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.3.90-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Sat Mar 3 23:50:18 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb76ef414 <gnome_rr_screen_get_dpms_mode+116>: mov 0xc(%eax),%eax
 PC (0xb76ef414) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 gnome_rr_screen_get_dpms_mode () from /usr/lib/libgnome-desktop-3.so.2
 gnome_rr_screen_set_dpms_mode () from /usr/lib/libgnome-desktop-3.so.2
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 g_cclosure_marshal_VOID(unsigned int0_t) () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: [power]: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Amir Zarrin (amir-zarrin2112) wrote :

StacktraceTop:
 gnome_rr_screen_get_dpms_mode (screen=0x0, mode=0xbfe6909c, error=0xbfe690ec) at gnome-rr.c:1157
 gnome_rr_screen_set_dpms_mode (screen=0x0, mode=GNOME_RR_DPMS_ON, error=0xbfe690ec) at gnome-rr.c:1241
 upower_notify_resume_cb (client=0x8ae3af0, sleep_kind=UP_SLEEP_KIND_SUSPEND, manager=0x8b13860) at gsd-power-manager.c:3611
 g_cclosure_marshal_VOID__UINT (closure=0x8b19d08, return_value=0x0, n_param_values=2, param_values=0x8bdf6a0, invocation_hint=0xbfe69240, marshal_data=0x0) at /build/buildd/glib2.0-2.31.18/./gobject/gmarshal.c:259
 g_closure_invoke (closure=0x8b19d08, return_value=0x0, n_param_values=2, param_values=0x8bdf6a0, invocation_hint=0xbfe69240) at /build/buildd/glib2.0-2.31.18/./gobject/gclosure.c:774

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
affects: gnome-settings-daemon (Ubuntu) → gnome-desktop3 (Ubuntu)
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-desktop3 (Ubuntu):
status: New → Confirmed
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/946124

tags: added: iso-testing
Erick Brunzell (lbsolost) wrote :

I was testing the 20120605.2 i386 QQ image and ubiquity crashed before making any selections. Apport showed duplicate bug 1008818 as the culprit. I'm clueless regarding what other info might be helpful, but the 20120604.2 iso worked OK.

Erick Brunzell (lbsolost) wrote :

Oddly I just decided to see if I could reproduce that installer crash, same iso, same identical procedure and hardware, and things seemed to go just fine. It's installing as I type this.

useResa (rdrijsen) wrote :

I encountered this bug when I quit the installer during in installation of the quantal-desktop-i386.iso in VirtualBox on an Ubuntu 12.04 host. As also indicated in comment #7 also to me it was indicated that bug #1008818 was the issue.

Note 1: The reason to quit the installer was the fact that it indicated I was not connected to the internet. However, when opening Firefox it turned out I was connected.
Note 2: The issue did not appear again when restarting the installer, so maybe quiting it was the cause?

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