unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This error occurs each time I run Ubuntu(just after login)
$ lsb_release -rd
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
$ apt-cache policy unity-settings-
15.04.1+
$ dmesg | tail
[ 34.006677] unity-settings-
[ 34.006794] unity-settings-
[ 56.476561] usbcore: registered new interface driver snd-usb-audio
[ 771.107737] audit: type=1400 audit(145716202
[ 771.127016] audit: type=1400 audit(145716202
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-settings-
ProcVersionSign
Uname: Linux 4.4.0-10-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sat Mar 5 10:01:31 2016
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2016-02-28 (5 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
SHELL=/bin/bash
LANG=ru_RU.UTF-8
LANGUAGE=ru
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7f815a199e69 <up_exported_
PC (0x7f815a199e69) 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-
StacktraceTop:
up_exported_
gsd_power_
?? () from /usr/lib/
gnome_
?? ()
Title: unity-settings-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.