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

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

Bug Description

Maybe the same as #1718727 but occured when switched to Settings window opened for some time and tried to switch to different tab.

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
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 30 18:03:59 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-01-02 (301 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcCmdline: gnome-control-center wifi
SegvAnalysis:
 Segfault happened at: 0x7f8d1dd23253 <nm_device_filter_connections+35>: mov 0x8(%r12),%eax
 PC (0x7f8d1dd23253) ok
 source "0x8(%r12)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 nm_device_filter_connections () from /usr/lib/x86_64-linux-gnu/libnm.so.0
 net_device_get_valid_connections ()
 ?? ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in nm_device_filter_connections()
UpgradeStatus: Upgraded to artful on 2017-10-24 (6 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

Revision history for this message
Martin Polreich (mpolreich) 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 #1726618, 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.