GNOME Bugzilla – Bug 116715
Browsing the TAO html file "caused" nautilus crash
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: normal Version: 2.2.1 Synopsis: Browsing the TAO html file "caused" nautilus crash Bugzilla-Product: nautilus Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Whle browsing the TAO Install documentation (.html), a message box appeared claiming that Nautilus crashed with a SEGV. Steps to reproduce the problem: 1. Run to xterms with different bg/fg colors (this is probably unrelated) 2. Run the browser after building ACE, but not TAO. 3. Examine the Install html file for TAO (all of this should be unrelated) Actual Results: Browsing continues uninterrupted. Expected Results: Did not expect SEGV. How often does this happen? first time ever Additional Information: ps -aef | grep i naut <snipped out grep> aanderso 1151 1 0 07:53 ? 00:00:01 nautilus --sm-config-prefix /nautilus-yIsb0B/ --sm-client-id 117f000001000105296319500000010880003 --screen 0 --no-default-window 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 1087975744 (LWP 1151)] [New Thread 1142127920 (LWP 1163)] [New Thread 1133735216 (LWP 1162)] [New Thread 1125342512 (LWP 1161)] [New Thread 1116949808 (LWP 1160)] [New Thread 1099636016 (LWP 1159)] (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 38427
Thread 1 (Thread 1087975744 (LWP 1151))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-04 13:44 ------- Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. This appears to be a dup of 105762, which has been marked as a duplicate of 105745. *** This bug has been marked as a duplicate of 105745 ***