gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

Bug #1763530 reported by Frode Nordahl
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

Visited control center multiple times in attempt to remove stuck print job. Not exactly sure which exact action led to crash.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.0-0ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 13 00:40:31 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-03-15 (393 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcCmdline: gnome-control-center --overview
SegvAnalysis:
 Segfault happened at: 0x560be03ae311: mov 0x90(%rbp),%rsi
 PC (0x560be03ae311) ok
 source "0x90(%rbp)" (0x00000090) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to bionic on 2017-12-28 (105 days ago)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo

Revision history for this message
Frode Nordahl (fnordahl) 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 #1754924, 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.

Other bug subscribers

Remote bug watches

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