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

Bug #814473 reported by Xavier Fung on 2011-07-22
254
This bug affects 44 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon
Fix Released
Critical
gnome-settings-daemon (Ubuntu)
Medium
Unassigned

Bug Description

This comes up after a graphical lock-up. The event is just like a Suspend action and needs to press the power button to resume.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.3-0ubuntu7
ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7
Uname: Linux 3.0.0-6-generic x86_64
Architecture: amd64
Date: Fri Jul 22 16:25:23 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=en_HK:en
 PATH=(custom, no user)
 LANG=en_HK.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1c158c0db7: mov 0x10(%rbx),%ecx
 PC (0x7f1c158c0db7) ok
 source "0x10(%rbx)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 gdk_display_get_event () from /usr/lib/libgdk-3.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in gdk_display_get_event()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Xavier Fung (xavier114fch) wrote :
visibility: private → public

StacktraceTop:
 create_device (device_manager=0xb2e540, dev=0x0, emit_signal=1) at /build/buildd/gtk+3.0-3.1.8/./gdk/x11/gdkdevicemanager-xi2.c:245
 add_device (device_manager=0xb2e540, dev=0x0, emit_signal=1) at /build/buildd/gtk+3.0-3.1.8/./gdk/x11/gdkdevicemanager-xi2.c:310
 handle_hierarchy_changed (translator=0xb2e540, display=<value optimized out>, event=0xbaa1b0, xevent=0x7fff1c17edc0) at /build/buildd/gtk+3.0-3.1.8/./gdk/x11/gdkdevicemanager-xi2.c:586
 gdk_x11_device_manager_xi2_translate_event (translator=0xb2e540, display=<value optimized out>, event=0xbaa1b0, xevent=0x7fff1c17edc0) at /build/buildd/gtk+3.0-3.1.8/./gdk/x11/gdkdevicemanager-xi2.c:1043
 gdk_x11_device_manager_xi2_translate_event (translator=0xb2e540, display=<value optimized out>, event=0xbaa1b0, xevent=0x7fff1c17edc0) at /build/buildd/gtk+3.0-3.1.8/./gdk/x11/gdkdevicemanager-xi2.c:1007

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
tags: added: iso-testing
Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Changed in gnome-settings-daemon (Ubuntu):
assignee: nobody → Pedro Villavicencio (pvillavi)
status: Confirmed → Incomplete
Xavier Fung (xavier114fch) wrote :

I think this is not reproducible as it happens as a graphical lockup, but seems the machine goes into Suspend and I could wake the machine up by pressing the Power button. Just wonder how this could be happened.

Pedro Villavicencio (pedro) wrote :

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=656550

Changed in gnome-settings-daemon (Ubuntu):
status: Incomplete → Triaged
Changed in gnome-settings-daemon (Ubuntu):
assignee: Pedro Villavicencio (pvillavi) → nobody
Changed in gnome-settings-daemon:
importance: Unknown → Critical
status: Unknown → New
Borbinceane Iulian (borby87) wrote :

For me is reproducibile, if I close the lid of the pc and reopen it before it suspends than reclose it and reopen it to wake the pc this error comes out.

Changed in gnome-settings-daemon:
status: New → Incomplete
Robert Roth (evfool) wrote :

Question from upstream bug tracker: Likely fixed with newer versions of GTK+. Can you still reproduce with GTK+
3.1.18?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in gnome-settings-daemon (Ubuntu):
status: Triaged → Incomplete
Stefano Rivera (stefanor) wrote :

I just got another one, dist-upgraded and rebooted this morning

Steffen Röcker (sroecker) wrote :

Just crashed for me with libgtk-3-0 3.2.0-0ubuntu1.

Fayer Michael (fayer012) wrote :

I closed my laptop, then waked it up again and the error occurred.

$ apt-cache policy gnome-settings-daemon
gnome-settings-daemon:
  Installed: 3.2.0-0ubuntu5
  Candidate: 3.2.0-0ubuntu5
  Version table:
 *** 3.2.0-0ubuntu5 0
        500 http://archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
        100 /var/lib/dpkg/status

$ lsb_release -rd
Description: Ubuntu oneiric (development branch)
Release: 11.10

Changed in gnome-settings-daemon:
status: Incomplete → New
Fayer Michael (fayer012) wrote :

I think this bug probably related with sleeping. I closed my laptop, it slept. When I opened it, the error occurred and something became strange, e.g., all icons in file browser (nautilus) were lost, they looked just all same.

Changed in gnome-settings-daemon (Ubuntu):
status: Incomplete → Triaged
Ivan Calderon (neomasterx7) wrote :

i made this gdb backtrace following the steps from https://wiki.ubuntu.com/Backtrace
excuse me if this is not useful.

This exact bug happens quite randomly when unsuspending

Changed in gnome-settings-daemon:
status: New → Confirmed
tags: added: bugpattern-needed
tags: added: precise
Changed in gnome-settings-daemon:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.