GNOME Bugzilla – Bug 159070
NetworkManager crashed on bootup
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: NetworkManager Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: NetworkManager crashed on bootup Bugzilla-Product: NetworkManager Bugzilla-Component: Default Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: GNOME reports that the application NetworkManagerInfo crashed unexpectedly. Clicking on "Restart" only results in the same dialog box reappearing. Steps to reproduce the crash: 1. First time this has happened; unable to confirm whether this is a repeatable bug yet. 2. 3. Expected Results: NetworkManagerInfo should have started. How often does this happen? First time. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/NetworkManagerInfo' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (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 -151176288 (LWP 3744)] (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)...(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)...0x009b57a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52428
Thread 1 (Thread -151176288 (LWP 3744))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-22 09:43 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "NetworkManager". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was rpaiz@simpaticus.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
May be related to bug 151307, or bug 158733 (or bug 158955 or bug 158868...), all of which appear to be prelink problems.
At the time of that crash, eggcups also crashed. Repeated attempts to restart both applications were unsuccessful. However, after rebooting I was unable to reproduce either problem... sorry. Please let me know whether we should close the bug or attempt to diagnose. This has not happened again in 15 or so reboots of the machine, so I think it went away.
Yeah, sounds like the prelink problem. prelink is run automatically, which will fix the problem, as pointed out in bug 151307, comment 13. And also at http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140103. I'll go ahead and mark it as a dupe. *** This bug has been marked as a duplicate of 151307 ***