NetworkManager crashed with SIGSEGV in <signal handler called>()

Bug #138679 reported by Lothar
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Brian Murray

Bug Description

Binary package hint: network-manager

This crash seems to be new after the last update.
KNetworkmanager applet showed still connected although connection was not available.

ProblemType: Crash
Architecture: amd64
Date: Sun Sep 9 12:32:21 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/sbin/NetworkManager
Package: network-manager 0.6.5-0ubuntu10
PackageArchitecture: amd64
ProcCmdline: /usr/sbin/NetworkManager --pid-file /var/run/NetworkManager/NetworkManager.pid
ProcCwd: /
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 ?? ()
 <signal handler called>
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch ()
Title: NetworkManager crashed with SIGSEGV in <signal handler called>()
Uname: Linux regensburg 2.6.22-11-generic #1 SMP Fri Sep 7 04:31:16 GMT 2007 x86_64 GNU/Linux
UserGroups:

Revision history for this message
Lothar (lothar-tradescape) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:nm_signal_handler (signo=1) at nm-logging.c:165
<signal handler called>
?? ()
g_timeout_dispatch (source=0x2aaab0002f00, callback=0x2aaab0005110, user_data=0x0) at /build/buildd/glib2.0-2.14.0/glib/gmain.c:3488
IA__g_main_context_dispatch (context=0x65bfd0) at /build/buildd/glib2.0-2.14.0/glib/gmain.c:2061

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Alexander Sack (asac) wrote :

do you still see this bug in 0.6.5-0ubuntu13 network-manager

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

Changed in network-manager:
assignee: nobody → brian-murray
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.