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

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

Bug Description

Started the computer and i found dropbox updating when i logged on desktop. The desktop freezed periodically for about 15 minutes in which nothing worked. The installation of dropbox didn't remove the older version, i had to close it manually (took some minutes)

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-settings-daemon 15.04.1+16.04.20160209-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Sun Mar 20 21:48:27 2016
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2016-03-10 (10 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
SegvAnalysis:
 Segfault happened at: 0x7f5e64d58e69 <up_exported_daemon_get_lid_is_closed+9>: mov (%rbx),%rdi
 PC (0x7f5e64d58e69) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-settings-daemon
StacktraceTop:
 up_exported_daemon_get_lid_is_closed () from /usr/lib/x86_64-linux-gnu/libupower-glib.so.3
 gsd_power_manager_start () from /usr/lib/unity-settings-daemon-1.0/libpower.so
 ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
 gnome_settings_plugin_info_activate ()
 ?? ()
Title: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
George Chalkitis (chalkitisge) 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 #1546641, 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.