nm-system-settings crashed with SIGSEGV in g_closure_invoke()

Bug #320128 reported by Michael
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: network-manager

This occured after restarting dbus (/etc/init.d/dbus restart). Possible duplicate of #280058 and/or #299557.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/nm-system-settings
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
NonfreeKernelModules: nvidia
Package: network-manager 0.7~~svn20081018t105859-0ubuntu1.8.10.1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/nm-system-settings --config /etc/NetworkManager/nm-system-settings.conf
ProcEnviron:

Signal: 11
SourcePackage: network-manager
StacktraceTop:
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: nm-system-settings crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.27-10-generic x86_64
UserGroups:

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

StacktraceTop:?? ()
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist ()
g_signal_emit () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in network-manager:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) 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:
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.