[xsettings]: gnome-settings-daemon crashed with SIGSEGV in notify_have_shell()

Bug #1278467 reported by Marc Whitaker
340
This bug affects 54 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Fix Released
Medium
Robert Ancell

Bug Description

This error shows up after each boot.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-settings-daemon 3.8.6.1-0ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Feb 10 07:09:41 2014
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationDate: Installed on 2014-01-29 (11 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140121.1)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7faee44f1b37: mov (%rax),%rdi
 PC (0x7faee44f1b37) ok
 source "(%rax)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Marc Whitaker (marc-leaddogs) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 notify_have_shell (manager=0x17f1500) at gsd-xsettings-manager.c:780
 do_call (client=0x1840c50, call_type=CALL_TYPE_NAME_VANISHED) at /build/buildd/glib2.0-2.39.4/./gio/gdbusnamewatching.c:214
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7fff833a0a00, fn=0x7faef4ed6870 <on_connection_disconnected>, rvalue=0x7fff833a0970, avalue=avalue@entry=0x7fff833a0910) at ../src/x86/ffi64.c:522
 g_cclosure_marshal_generic (closure=0x179f6c0, return_gvalue=0x0, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=0x0) at /build/buildd/glib2.0-2.39.4/./gobject/gclosure.c:1447

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
summary: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in
- ffi_call_unix64()
+ notify_have_shell()
tags: removed: need-amd64-retrace
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
information type: Private → Public
Revision history for this message
Lee Davis (lee-gixxer) wrote :

While running Nvidia-331-updates, I can't reboot normally have to either stop gdm or switch to the first console and reboot from there, then I get this error. I don't seem to have this problem otherwise.

tags: added: bugpattern-needed
Revision history for this message
Sanjeev Gupta (ghane) wrote :

Upon gdm startup, after logging in.

Changed in gnome-settings-daemon (Ubuntu):
assignee: nobody → Wilder Ruiz Castillo (poisoncadc)
Changed in gnome-settings-daemon (Ubuntu):
status: Confirmed → In Progress
status: In Progress → Incomplete
Revision history for this message
Marc (mankongde) wrote :

Running 13.10, I started getting this bug after updating to the 3.13.7 kernel from 3.11.0. On my system it is affecting gnome-control-center 1:3.6.3-0ubuntu45.2.

If I can send anything that'd help resolve this, I'd be happy to.

Marc

Jared Webb (vertexner)
Changed in gnome-settings-daemon (Ubuntu):
status: Incomplete → New
Revision history for this message
Th. Sievers (th-sievers) wrote :

just installed beta 2

after first boot and login

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
Padraig Fahy (fahy) wrote :

Same as above.

Ubuntu GNOME 14.04 LTS Beta 2. After first boot, the message appears.

Revision history for this message
Th. Sievers (th-sievers) wrote :

today installed beta 2

now chrash report appears after dist-upgrade and reboot

Revision history for this message
Christopher (soft-kristal) wrote :

I only and always get this when I log out and back in. There is similar graphic 'garbage' on boot, but logging out and in takes pretty much the same time as rebooting.

Revision history for this message
Mitch Dunaway (midway40) wrote :

Only got this bug twice so far at bootup. The first time I do not remember anything special but the second time was right after I had installed "Ubuntu base" with the Software Updater.

Revision history for this message
Juliusz Kotarski (ko-ta-ba) wrote :

nie mam zdania w tym względzie

Revision history for this message
Joshua Walker (jwjoshuawalker) wrote :

Ubuntu Gnome 14.04
AMD/ATI HD 7770

Using 2 monitors, 1 portrait, 1 landscape.
Forgets display layout settings every reboot & reports this error.

Revision history for this message
Bruce Pieterse (octoquad) wrote :

Marc, please see https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1301513 for any useful information you can find relating to this bug.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

This is currently the #3 bug on https://errors.ubuntu.com/?release=Ubuntu%2014.04&period=month. There is a mistake in debian/patches/90_set_gmenus_xsettings.patch which I think is causing it.

Changed in gnome-settings-daemon (Ubuntu):
assignee: Wilder Ruiz Castillo (poisoncadc) → Robert Ancell (robert-ancell)
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-settings-daemon - 3.8.6.1-0ubuntu11

---------------
gnome-settings-daemon (3.8.6.1-0ubuntu11) trusty; urgency=medium

  [ Jackson Doak ]
  * Add git_micmute.patch to add XF86AudioMicMute as a mic mute key

  [ Robert Ancell ]
  * debian/patches/90_set_gmenus_xsettings.patch:
    - Fix error in patch for watching Shell D-Bus names (LP: #1278467)
 -- Robert Ancell <email address hidden> Wed, 09 Apr 2014 13:38:55 +1200

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