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

Bug #1381519 reported by Uldis Kalniņš
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-settings-daemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

Probably same to ​ #1380278 .

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-settings-daemon 14.04.0+14.10.20141010-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4
Uname: Linux 3.16.0-22-lowlatency x86_64
ApportVersion: 2.14.7-0ubuntu6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Oct 15 16:00:02 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2013-10-17 (362 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
SegvAnalysis:
 Segfault happened at: 0x7f964f9953c0: andb $0xfe,0x1(%rax)
 PC (0x7f964f9953c0) ok
 source "$0xfe" ok
 destination "0x1(%rax)" (0x7f9638105001) in non-writable VMA region: 0x7f9638105000-0x7f963c000000 ---p None
SegvReason: writing VMA None
Signal: 11
SourcePackage: unity-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: unity-settings-daemon crashed with SIGSEGV in gdk_display_get_event()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip disk fuse libvirtd lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Uldis Kalniņš (ulcha) wrote :
information type: Private → Public
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 #1380278, 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.

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.