bamfdaemon crashed with SIGSEGV in sn_xcb_display_new()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bamf (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
bamfdaemon crashed with SIGSEGV in sn_xcb_
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: bamfdaemon 0.5.3+16.
ProcVersionSign
Uname: Linux 4.10.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity:Unity7
Date: Fri Mar 24 09:16:58 2017
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-02-26 (25 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170226)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f88046a8e39 <sn_xcb_
PC (0x7f88046a8e39) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: bamf
StacktraceTop:
sn_xcb_display_new () from /usr/lib/
sn_display_new () from /usr/lib/
wnck_screen_get () from /usr/lib/
bamf_legacy_
?? ()
Title: bamfdaemon crashed with SIGSEGV in sn_xcb_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
| szabcomp (szabcomp) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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 #1671316, 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.