GNOME Bugzilla – Bug 110088
Crashed when trying to look at network services
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: normal Version: 2.2.1 Synopsis: Crashed when trying to look at network services Bugzilla-Product: nautilus Bugzilla-Component: File Search Interface BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Nautilus crashed when trying to open network services. Worked fine the first few times then boom. Steps to reproduce the problem: 1. 2. 3. Actual Results: Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (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)...[New Thread 1087994752 (LWP 1821)] [New Thread 1175660736 (LWP 1841)] [New Thread 1167272256 (LWP 1840)] [New Thread 1158883776 (LWP 1839)] [New Thread 1150495296 (LWP 1838)] [New Thread 1142106816 (LWP 1837)] [New Thread 1133718336 (LWP 1836)] [New Thread 1125329856 (LWP 1835)] [New Thread 1116941376 (LWP 1834)] [New Thread 1099635904 (LWP 1833)] (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)...0xffffe002 in ?? ()
+ Trace 35624
Thread 7 (Thread 1133718336 (LWP 1836))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-04-06 00:53 ------- The original reporter (linux@sagebrush.frazmtn.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
The stack trace looks corrupted. Can you try to get us a complete stack trace? (see http://bugzilla.gnome.org/getting-traces.cgi for information on how to do so).
*** This bug has been marked as a duplicate of 107741 ***