nm-applet crashed with SIGSEGV in g_main_context_dispatch()

Bug #1455998 reported by Daniel Hahler
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
New
Undecided
Unassigned

Bug Description

failsafeXServer from xdiagnose kicked in, although my window manager (awesomeWM through gnome-session) was still running.

This crash happened in this context then maybe, when chosing "login to graphical console" in the failsafeXServer dialog killed the session.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: network-manager-gnome 0.9.10.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6
Uname: Linux 3.19.0-17-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Awesome
Date: Mon May 18 03:00:57 2015
ExecutablePath: /usr/bin/nm-applet
InstallationDate: Installed on 2012-05-28 (1084 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IpRoute:
 default via 192.168.178.1 dev wlan0 proto static metric 400
 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.46
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
 WimaxEnabled=true
ProcCmdline: nm-applet
SegvAnalysis:
 Segfault happened at: 0x4322e0: mov 0x18(%r14),%rdi
 PC (0x004322e0) ok
 source "0x18(%r14)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nm-applet crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to vivid on 2015-05-14 (3 days ago)
UserGroups: adm cdrom davfs2 dialout dip docker fuse lastfm libvirtd lpadmin plugdev sambashare sudo wireshark www-data
http_proxy: http://localhost:3128/
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
no_proxy: localhost,127.0.0.1

Revision history for this message
Daniel Hahler (blueyed) 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 #1418260, 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.