gnome-control-center crash

Bug #1812753 reported by Prasanna Loganathar
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Unknown

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jan 22 02:10:38 2019
ExecutablePath: /usr/bin/gnome-control-center
ExecutableTimestamp: 1542796176
InstallationDate: Installed on 2019-01-01 (20 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcCmdline: gnome-control-center wifi
ProcCwd: /home/pvl
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-01-15T04:51:59.517661

Revision history for this message
Prasanna Loganathar (pvl) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=type_instance@entry=0x56053c592390, iface_type=94580485547024) at ../../../../gobject/gtype.c:4057
 device_ethernet_refresh_ui (device=0x56053c592390) at ../panels/network/net-device-ethernet.c:208
 g_cclosure_marshal_VOID__BOOLEANv (closure=<optimized out>, return_value=<optimized out>, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x56053bddaa30) at ../../../../gobject/gmarshal.c:978
 _g_closure_invoke_va (closure=0x56053d023d70, return_value=0x0, instance=0x56053d1eac00, args=0x7ffccf1976b0, n_params=1, param_types=0x56053bddaa30) at ../../../../gobject/gclosure.c:873
 g_signal_emit_valist (instance=0x56053d1eac00, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffccf1976b0) at ../../../../gobject/gsignal.c:3300

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
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

information type: Private → Public
Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

Did you restart network-manager or had issue with it? Other similar reports seem to hint those problems usually happen when network-manager becomes unavailable

Revision history for this message
Prasanna Loganathar (pvl) wrote :

Hi Sebastien, I'm afraid I'm not entirely sure. I had this crash dump again and again in a clean installed laptop that's up to date for the last couple of weeks. So, thought I'll file it. Please do feel free to close it if you think it may be redundant.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Closing since it looks like the problem with network-manager hitting an issue which is already reported

Changed in gnome-control-center (Ubuntu):
status: Incomplete → Invalid
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.