gnome-panel crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-panel (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1:
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10
-------
2:
gnome-panel:
Installed: 1:3.24.1-1ubuntu1
Candidate: 1:3.24.1-1ubuntu1
Version table:
*** 1:3.24.1-1ubuntu1 500
500 http://
100 /var/lib/
-------
3:
Login using Gnome Flashback
-------
4:
Getting thrown back to login screen again
Using the dumbed down, geared towards hand held devices, Unity still works.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-panel 1:3.24.1-1ubuntu1
ProcVersionSign
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.5-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Flashback
Date: Fri May 19 06:23:51 2017
ExecutablePath: /usr/bin/
GsettingsChanges:
b'org.
b'org.
InstallationDate: Installed on 2016-10-22 (208 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: gnome-panel
SegvAnalysis:
Segfault happened at: 0x7fe72772b464: mov (%rax),%rdi
PC (0x7fe72772b464) ok
source "(%rax)" (0xddbb7060) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
Title: gnome-panel crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to artful on 2017-05-09 (9 days ago)
UserGroups: adm cdrom dip lpadmin lxd 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 #1689680, 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.