gnome-settings-daemon crashed with SIGSEGV in pa_pdispatch_run()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
New
|
Undecided
|
Unassigned |
Bug Description
I got this bug after upgrade from gnome-shell 3.18 to 3.20 and using Adapta GTK theme
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-settings-
ProcVersionSign
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat May 14 16:57:53 2016
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2016-05-07 (7 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f3f7142364e: cmp %eax,0x174(%rsi)
PC (0x7f3f7142364e) ok
source "%eax" ok
destination "0x174(%rsi)" (0x00000174) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-settings-
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
pa_pdispatch_run () from /usr/lib/
?? () from /usr/lib/
Title: gnome-settings-
UpgradeStatus: Upgraded to xenial on 2016-05-12 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
upstart.
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 #1560622, 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.