[housekeeping]: gnome-settings-daemon crashed with signal 5 in g_main_context_new()

Bug #1629943 reported by Robert Bruce Park
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

Just unlocked my screen and saw this error, sorry I don't know what caused it.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-settings-daemon 3.20.1-2ubuntu1~ubuntu16.04.1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Wed Sep 28 19:15:17 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationDate: Installed on 2015-11-11 (327 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA:en
 XDG_RUNTIME_DIR=<set>
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_dbus_connection_send_message_with_reply_sync () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: [housekeeping]: gnome-settings-daemon crashed with signal 5 in g_main_context_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo

Revision history for this message
Robert Bruce Park (robru) wrote :
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1589294, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.