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-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Wed Apr 5 19:32:04 2017
ExecutablePath: /usr/lib/
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=hu_HU.UTF-8
LANGUAGE=hu_HU
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7f0d97f8de39 <sn_xcb_
PC (0x7f0d97f8de39) 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 () at /usr/lib/
sn_display_new () at /usr/lib/
wnck_screen_get () at /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 netdev 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 #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.