budgie-daemon crashed with SIGSEGV in g_object_unref()

Bug #1708816 reported by Justas Malinauskas
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
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/budgie-daemon
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/x86_64-linux-gnu/libwnck-3.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 __libc_start_main (main=0x555c52ad3870, argc=1, argv=0x7ffc42bb3198, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc42bb3188) at ../csu/libc-start.c:291
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

Revision history for this message
Justas Malinauskas (justas6666) wrote :
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 #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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.