gnome-control-center crashed SIGSEGV in on_get_job_attributes_cb()

Bug #1725414 reported by Leon Adato
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

I started gtop and the system froze. Eventually I ended up in the login screen again. Problem is repeatable.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 13:14:52 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2016-05-08 (530 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: gnome-control-center printers
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x559ceda90e64: cmpq $0x0,0x8(%r12)
 PC (0x559ceda90e64) ok
 source "$0x0" ok
 destination "0x8(%r12)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing 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
 ?? () 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 artful on 2017-10-20 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Leon Adato (adatole) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 on_get_job_attributes_cb (source_object=<optimized out>, res=<optimized out>, user_data=<optimized out>) at cc-printers-panel.c:346
 g_task_return_now (task=0x7feb180076e0) at ../../../../gio/gtask.c:1145
 complete_in_idle_cb (task=0x7feb180076e0) at ../../../../gio/gtask.c:1159
 g_main_dispatch (context=0x559cee6108e0) at ../../../../glib/gmain.c:3148
 g_main_context_dispatch (context=context@entry=0x559cee6108e0) at ../../../../glib/gmain.c:3813

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: gnome-control-center crashed SIGSEGV in g_main_context_dispatch() after starting gtop

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

The segfault is in the printers configuration page, do you remember what you were doing there?

summary: - gnome-control-center crashed SIGSEGV in g_main_context_dispatch() after
- starting gtop
+ gnome-control-center crashed SIGSEGV in on_get_job_attributes_cb()
information type: Private → Public
Changed in gnome-control-center (Ubuntu):
importance: Medium → Low
Revision history for this message
Rolf Leggewie (r0lf) wrote :

dupe of bug 951570?

Revision history for this message
Sebastien Bacher (seb128) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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