NetworkManager crashed with SIGSEGV in g_slice_alloc()

Bug #277185 reported by azn
42
This bug affects 3 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: network-manager

1)
Description: Ubuntu intrepid (development branch)
Release: 8.10

2)
network-manager:
  Installed: 0.7~~svn20080908t183521+eni0-0ubuntu4
  Candidate: 0.7~~svn20080908t183521+eni0-0ubuntu4
  Version table:
 *** 0.7~~svn20080908t183521+eni0-0ubuntu4 0
        500 http://se.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

3)
I expected it to work

4)
It didn't work

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
NonfreeKernelModules: nvidia
Package: network-manager 0.7~~svn20080908t183521+eni0-0ubuntu4
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/NetworkManager
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 g_slist_append () from /usr/lib/libglib-2.0.so.0
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in g_slice_alloc()
Uname: Linux 2.6.27-4-generic x86_64
UserGroups:

Tags: apport-crash
Revision history for this message
azn (jorgen-hedlund) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_slist_append (list=0x0, data=0x7f7e7e70e810)
schedule_state_handler (self=0x1a7a310,
IA__g_closure_invoke (closure=0x1a92c70, return_value=0x0, n_param_values=3,
signal_emit_unlocked_R (node=0x1a73240, detail=0, instance=0x1a7e830, emission_return=0x0,
IA__g_signal_emit_valist (instance=0x1a7e830, signal_id=<value optimized out>, detail=0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in network-manager:
importance: Undecided → Medium
Revision history for this message
Mackenzie Morgan (maco.m) wrote :

What were you doing when it crashed? Were changing settings, trying to connect to something, inputting a WEP key, ...? We need more information.

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Armindo Silva (deathon2legs) wrote :

Hi!

I had firefox open (1 tab: gmail) and I was doing a dist-upgrade from a gnome-terminal.
I had not touch on NetworkManager on the last few hours. It was connected to an open wireless network.

Revision history for this message
Alex Ruddick (alexrudd0) wrote :

I added a duplicate to get apport's information.

I had firefox, pidgin, and a gnome-terminal open. A minute or two before I had done a dist-upgrade in the terminal, and was browsing gmail when apport came up. I've attached dpkg.log.

Still connected to the Internet, although there's no NM icon in the tray.

Revision history for this message
Wilbur Harvey (wilbur-harvey-spirentcom) wrote :

This morning I ran the updates.
After re-booting, the gnome settings daemon doesn't work, and I got this crash message about the network manager. although there is still a network manager icon.
I am connected to a wired network and didn't change any network settings.
I have an Intel based system with a Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in network-manager:
status: Incomplete → Confirmed
Alexander Sack (asac)
Changed in network-manager:
assignee: nobody → asac
status: Confirmed → Triaged
Martin Pitt (pitti)
Changed in network-manager (Ubuntu):
assignee: Alexander Sack (asac) → nobody
Revision history for this message
Maarten Bezemer (veger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 277185 and any other logs that are relevant for this particular issue.

Changed in network-manager (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
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.