budgie-daemon crashed with SIGSEGV in g_object_unref()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
budgie-desktop (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
-
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: budgie-core 10.3.1-3
ProcVersionSign
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sat Aug 5 12:50:32 2017
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-08-05 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1)
ProcCmdline: budgie-daemon
SegvAnalysis:
Segfault happened at: 0x7f492102d271: movq $0x0,(%rax,%rdx,8)
PC (0x7f492102d271) ok
source "$0x0" ok
destination "(%rax,%rdx,8)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: budgie-desktop
StacktraceTop:
?? () from /usr/lib/
g_object_unref () from /usr/lib/
?? ()
?? ()
__libc_start_main (main=0x555c52a
Title: budgie-daemon crashed with SIGSEGV in g_object_unref()
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 #1704668, 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.