lightdm crashes after opening window in Thunderbird.
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: unity-settings-daemon 15.04.1+15.10.20151029-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jan 6 18:03:07 2016
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2014-08-30 (494 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
SegvAnalysis:
Segfault happened at: 0x7f90f45dd1e9 <malloc_consolidate+329>: cmp 0x18(%r11),%rbx
PC (0x7f90f45dd1e9) ok
source "0x18(%r11)" (0x27521d000000018) not located in a known VMA region (needed readable region)!
destination "%rbx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-settings-daemon
StacktraceTop:
malloc_consolidate (av=av@entry=0x7f90f4922c00 <main_arena>) at malloc.c:4142
_int_malloc (av=av@entry=0x7f90f4922c00 <main_arena>, bytes=bytes@entry=4096) at malloc.c:3417
__libc_calloc (n=<optimized out>, elem_size=<optimized out>) at malloc.c:3213
g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()
UpgradeStatus: Upgraded to wily on 2015-11-05 (62 days ago)
UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse pulse-access sambashare sudo video
upstart.unity-settings-daemon.log:
(unity-settings-daemon:3042): GLib-GIO-CRITICAL **: g_dbus_proxy_get_object_path: assertion 'G_IS_DBUS_PROXY (proxy)' failed
(unity-settings-daemon:3042): GLib-GIO-CRITICAL **: g_dbus_proxy_get_object_path: assertion 'G_IS_DBUS_PROXY (proxy)' failed
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 #1300463, 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.