gnome-control-center segfault on vpn changes

Bug #1718006 reported by Jean-Baptiste Lallement
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center
Fix Released
Medium
network-manager (Ubuntu)
Fix Released
High
Iain Lane

Bug Description

Maybe when I was configuring a printer

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 18 20:55:47 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-09-03 (1475 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcCmdline: gnome-control-center printers
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe50b4232cc <g_type_check_instance+60>: testb $0x4,0x16(%rdx)
 PC (0x7fe50b4232cc) ok
 source "$0x4" ok
 destination "0x16(%rdx)" (0x100000016) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libnm.so.0
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0x56251af82340) at ../../../../gobject/gtype.c:4133
 g_signal_emit_valist (instance=0x56251af82340, signal_id=427, detail=0, var_args=var_args@entry=0x7ffead03f3f0) at ../../../../gobject/gsignal.c:3176
 g_signal_emit (instance=instance@entry=0x56251af82340, signal_id=<optimized out>, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447
 vpn_state_changed_proxy (proxy=<optimized out>, vpn_state=7, reason=3, user_data=0x56251af82340) at libnm/nm-vpn-connection.c:114
 ffi_call_unix64 () at ../src/x86/unix64.S:76

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 : Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance()

the stacktrace suggest that it has to do with vpn state change, did you connect to the vpn while you were configuring your printing or something similar?

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

Confirmed, it segfaults when you disconnected from a vpn while it's open, sent upstream to https://bugzilla.gnome.org/show_bug.cgi?id=787893

Changed in gnome-control-center (Ubuntu):
importance: Medium → High
status: New → Triaged
Changed in gnome-control-center:
importance: Unknown → Medium
status: Unknown → Confirmed
summary: - gnome-control-center crashed with SIGSEGV in g_type_check_instance()
+ gnome-control-center segfault on vpn changes
tags: added: rls-a-incoming
tags: added: rls-aa-incoming
removed: rls-a-incoming
Revision history for this message
Sebastien Bacher (seb128) wrote :

there is a working patch upstream now

Changed in gnome-control-center (Ubuntu):
status: Triaged → In Progress
affects: gnome-control-center (Ubuntu) → network-manager (Ubuntu)
Changed in network-manager (Ubuntu):
assignee: nobody → Iain Lane (laney)
status: In Progress → Fix Committed
Changed in gnome-control-center:
status: Confirmed → Fix Released
Revision history for this message
Iain Lane (laney) wrote :

Uploaded, baking in proposed for a bit

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package network-manager - 1.8.4-1ubuntu1

---------------
network-manager (1.8.4-1ubuntu1) artful; urgency=medium

  * debian/patches/manager-Disconnect-from-signals-on-the-proxy-when-we.patch,
    debian/patches/vpn-remote-connection-disconnect-signal-handlers-whe.patch:
    Cherry-pick two patches from upstream. Fix leaked signal connections which
    caused handlers to be called on disposed objects, leading to crashes in
    some situations. (LP: #1704618) (LP: #1718006)
  * Merge with Debian. Remaining changes:
    - Use systemd-resolved instead of dnsmasq
    - debian/control:
      + Depend on isc-dhcp-client instead of recommends
      + Recommend network-manager-pptp
      + Suggest avahi-autoipd for IPv4LL support
    - debian/control, debian/rules:
      + Disable team support since it's in universe
    - debian/rules, debian/network-manager.postinst:
      + Don't restart NetworkManager on upgrade but recommend restarting
        the computer
    - debian/rules, debian/network-manager.postinst:
      + Don't install sysvinit scripts or migrate from sysvinit
    - debian/network-manager.postinst:
      + Don't add the netdev group.
      + Handle upgrades from unmanaged policy
      + drop in an empty override file for NetworkManager to manage all devices
        for upgrade from any version, as long as there is no netplan
        configuration yet. (LP: #1676547)
    - debian/network-manager.maintscript
      + Remove /etc/dbus-1/system.d/nm-ofono.conf
    - debian/default-wifi-powersave-on.conf, debian/rules:
      + Install a config file to enable WiFi powersave
    - Enable build tests
    - Add autopkgtests
    - debian/source_network-manager.py, debian/network-manager.install,
      debian/network-manager.links: Add apport hook
    - Update Vcs links to point to Ubuntu branch
    - debian/patches/*: Add patches. See patch descriptions for more details.
    - dpkg-shlibdeps doesn't parse Version Reference, thus add a manual dep
      on libc6 >= 2.25. LP: #1715641.
    - Add n-m-config-connectivity-ubuntu package (LP: #997200)
    - NetworkManager.conf: disable MAC randomization feature. There is no
      easy way for desktop users to disable this feature yet. And there are
      reports that it doesn't work well with some systems. (LP: #1681513)

network-manager (1.8.4-1) unstable; urgency=medium

  * New upstream version 1.8.4
  * Rebase patches
  * Switch to dh_missing and abort on uninstalled files

 -- Iain Lane <email address hidden> Fri, 22 Sep 2017 18:56:30 +0100

Changed in network-manager (Ubuntu):
status: Fix Committed → Fix Released
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.