unity-settings-daemon crashed with SIGSEGV in gsd_power_manager_stop()

Bug #1569463 reported by Marius Nuennerich
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-settings-daemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

If no other reports for this come it is probably a flaky machine.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-settings-daemon 15.04.1+16.04.20160209-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Tue Apr 12 17:31:34 2016
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2016-02-13 (59 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160213)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
SegvAnalysis:
 Segfault happened at: 0x7ff0fdd15d01 <gsd_power_manager_stop+561>: mov 0x8(%r13),%ecx
 PC (0x7ff0fdd15d01) ok
 source "0x8(%r13)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-settings-daemon
StacktraceTop:
 gsd_power_manager_stop () from /usr/lib/unity-settings-daemon-1.0/libpower.so
 gnome_settings_plugin_info_deactivate ()
 ?? ()
 g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gnome_settings_manager_stop ()
Title: unity-settings-daemon crashed with SIGSEGV in gsd_power_manager_stop()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Marius Nuennerich (mwrius) wrote :
Revision history for this message
Apport retracing service (apport) 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 #1556284, 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.