NetworkManager crashed with SIGSEGV in nm_device_get_driver()

Bug #350064 reported by chestnut
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

Crash occurred when pressing key combination for Expose (Compiz), but I think unrelated

Description: Ubuntu jaunty (development branch)
Release: 9.04
(Beta)

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
Package: network-manager 0.7.1~rc3.2.gitb8fc83a7-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/NetworkManager --pid-file /var/run/NetworkManager/NetworkManager.pid
ProcEnviron: PATH=(custom, no user)
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 nm_device_get_driver ()
 nm_system_apply_ip4_config ()
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:

Title: NetworkManager crashed with SIGSEGV in nm_device_get_driver()
Uname: Linux 2.6.28-11-generic i686
UserGroups:

Revision history for this message
chestnut (andrewosborne) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:nm_device_get_driver (self=0x97c3108) at nm-device.c:273
nm_system_apply_ip4_config (iface=0x97bc810 "X�{\t\002",
wait_for_connection_expired (data=0x97bf018)
wpa_selector_to_bitfield (
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
chestnut (andrewosborne)
description: updated
Alexander Sack (asac)
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Do you get the same with Karmic? Thanks in advance.

Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in network-manager (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.