nm-applet crashed with SIGSEGV in g_closure_invoke()

Bug #260975 reported by VinzC
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Network Manager applet crashed as I started a "system" VPN connection.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nm-applet
Package: network-manager-gnome 0.7~~svn20080817t183748-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: nm-applet --sm-disable
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_BE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: network-manager-applet
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-applet crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin cdrom dialout fuse kvm lpadmin plugdev sambashare vboxusers

Revision history for this message
VinzC (v-cadet) 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
?? () 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
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in network-manager-applet:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
VinzC (v-cadet) wrote :

I'm sorry I'm not familiar with this way of reporting bugs. I might have missed a step or two since I think I had selected the biggest report (about 2.5 MB) but I know I have closed my browser too early at times -- my upload speed is quite slow and I might have been caught closing the wrong window.

Next time if it crashes I'll be more careful.

Revision history for this message
Michele Mangili (mangilimic) 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-applet:
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.