GNOME Bugzilla – Bug 322358
Netapplet crashed after selecting disconnect
Last modified: 2005-11-29 19:39:35 UTC
Distribution: Unknown Package: gnome-system-tools Severity: Normal Version: GNOME2.12.0 unspecified Gnome-Distributor: SUSE Synopsis: Netapplet crashed after selecting disconnect Bugzilla-Product: gnome-system-tools Bugzilla-Component: network-admin Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Steps to reproduce the crash: 1. System was running with wireless interface (ath0) active. 2. Suspend to RAM. 3. Connect eth0 to cable. 4. Turn on system. 5. Using external HW switch on laptop, turned off wireless interface. 6. System (SUSE 10) did not detect disconnection of ath0 and connection of eth0. 7. Tried to run netapplet, but apparently it was already running, but not showing in system tray panel. 8. Killed running netapplet process. 9. Started netapplet. 10. Right-click on netapplet icon in system tray panel and select disconnect. 11. netapplet crash. Expected Results: I expected ath0 to disconnect. How often does this happen? This is the first time this happened to me. Previously netapplet seemed to work OK. Additional Information: Debugging Information: Backtrace was generated from '/opt/gnome/bin/netapplet' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 1090044000 (LWP 27328)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 64238
Thread 1 (Thread 1090044000 (LWP 27328))
------- Bug moved to this database by unknown@gnome.bugs 2005-11-24 19:33 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was msm3@energetic.com.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report? *** This bug has been marked as a duplicate of 320241 ***