gnome-settings-daemon crashed with SIGSEGV in idle_is_session_inhibited()

Bug #836014 reported by nvucinic
140
This bug affects 17 people
Affects Status Importance Assigned to Milestone
GNOME Settings Daemon
Fix Released
Critical
gnome-settings-daemon (Ubuntu)
Fix Released
Medium
Rodrigo Moya
Oneiric
Fix Released
Medium
Rodrigo Moya

Bug Description

out of the blue

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.5-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Aug 28 13:45:28 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2a446c3700: mov 0x8(%rax),%rcx
 PC (0x7f2a446c3700) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" 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
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to oneiric on 2011-08-15 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
nvucinic (nvucinic) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 idle_is_session_inhibited (manager=<optimized out>, mask=<optimized out>) at gsd-power-manager.c:2686
 idle_evaluate (manager=0x1586010) at gsd-power-manager.c:2725
 idle_evaluate (manager=0x1586010) at gsd-power-manager.c:2700
 g_closure_invoke (closure=0x159d3b0, return_value=0x0, n_param_values=2, param_values=0x7f2a38040320, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c:773
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=0x155d4c0, emission_return=0x0, instance_and_params=0x7f2a38040320) at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c:3271

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote : Re: gnome-settings-daemon crashed with SIGSEGV in g_closure_invoke()

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=657917

visibility: private → public
Changed in gnome-settings-daemon (Ubuntu):
status: Confirmed → Triaged
Changed in gnome-settings-daemon (Ubuntu Oneiric):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Changed in gnome-settings-daemon:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
Robbie Williamson (robbiew) wrote :

WORKAROUND: I found that this bug only occurs when I boot and login with my laptop unplugged. If I plug in, logout, and then log back in, my desktop environment is correct. Suspend/Resume and unplugging (but not logging out) works thereafter.

SEVERITY QUESTION: I would argue that given this is 100% reproducible for me (and others judging by the dups), that this bug is at least a **High**, as it severely impacts the usability of the system.

Revision history for this message
Jonathan Lange (jml) wrote :

Happens for me even when I'm unplugged. I think. There are a lot of g-s-d crashes and I'm not sure this is the right one.

Revision history for this message
florin (florin-arjocu) wrote :

I'm plugged and it occurs. It's a Virtualbox machine.

Revision history for this message
florin (florin-arjocu) wrote :

I run the freshly installed Oneiric beta 1.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-settings-daemon - 3.1.90-0ubuntu2

---------------
gnome-settings-daemon (3.1.90-0ubuntu2) oneiric; urgency=low

  * debian/patches/01_git_fix_brightness_step_amount.patch:
    - Fix BRIGHTESS_STEP_AMOUNT calculation macro (LP: #827517)
  * debian/patches/01_git_do_power_init_in_start.patch:
    - Do power plugin initialization in _start, not _init, to avoid multiple
      crashes (LP: #836014)
 -- Rodrigo Moya <email address hidden> Thu, 01 Sep 2011 10:33:58 +0200

Changed in gnome-settings-daemon (Ubuntu Oneiric):
status: Triaged → Fix Released
Revision history for this message
ZhengPeng Hou (zhengpeng-hou) wrote :

this bug still can be replicated after beta-1

Changed in gnome-settings-daemon (Ubuntu Oneiric):
status: Fix Released → New
Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
Revision history for this message
ZhengPeng Hou (zhengpeng-hou) wrote :

replicable without AC adapter plugged into laptop

Changed in gnome-settings-daemon:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

is this reproducible with 3.1.91-0ubuntu2 ?

tags: added: bugpattern-needed
Revision history for this message
Jonathan Lange (jml) wrote :

CORRECTION. My earlier comment (no. 7), was made mistakenly. This bug *only* occurs when I log in unplugged. When I log in plugged in, it works.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could somebody get a stacktrace using the current version using gdb (see https://wiki.ubuntu.com/Backtrace)
Could you also run "$ /usr/lib/gnome-settings-daemon/gsd-backlight-helper --get-brightness" and copy the log there?

summary: - gnome-settings-daemon crashed with SIGSEGV in g_closure_invoke()
+ gnome-settings-daemon crashed with SIGSEGV in
+ idle_is_session_inhibited()
Changed in gnome-settings-daemon (Ubuntu Oneiric):
assignee: Canonical Desktop Team (canonical-desktop-team) → Rodrigo Moya (rodrigo-moya)
Revision history for this message
Jonathan Lange (jml) wrote :

OK, maybe a different crash, but it's definitely a crash in g-s-d triggered with no power. Backtrace attached.

Revision history for this message
Jonathan Lange (jml) wrote :

OK, this time with symbols.

tags: removed: bugpattern-needed
tags: added: bugpattern-written
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-settings-daemon - 3.1.91-0ubuntu3

---------------
gnome-settings-daemon (3.1.91-0ubuntu3) oneiric; urgency=low

  * debian/control:
    - Build depend on libgnome-desktop3-dev >= 3.1.5, which is what upstream
      asks for
  * debian/patches/00git_guard_against_division_by_0.patch:
    - Guard against dividing by 0 in ABS_TO_PERCENTAGE macro (LP: #833595)
  * debian/patches/00git_dont_crash_if_session_not_ready.patch:
    - Don't crash if we try to calculate the idle state before connected to
      the session (LP: #836014)
 -- Rodrigo Moya <email address hidden> Wed, 07 Sep 2011 12:07:45 +0200

Changed in gnome-settings-daemon (Ubuntu Oneiric):
status: Confirmed → Fix Released
Changed in gnome-settings-daemon:
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.