GNOME Bugzilla – Bug 102219
Nautlilus Crashing
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: normal Version: 2.0.8 Synopsis: Nautlilus Crashing Bugzilla-Product: nautilus Bugzilla-Component: Backgrounds Emblems and Themes BugBuddy-GnomeVersion: 2.0 (2.0.6) Description: Description of Problem: Nautilus is seg faulting when opening. Freebsd 5.0 RC2 Steps to reproduce the problem: 1. Use Gnome 2.0 with FreeBSD 5.0 RC2 - just opening Nautlus causes a seg fault. 2. 3. Actual Results: Expected Results: How often does this happen? When Nautilus is opened. Additional Information: Debugging Information: Backtrace was generated from '/usr/X11R6/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)...(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)...[Switching to Process 27532, Thread 1] 0x28cb8913 in poll () from /usr/lib/libc.so.5
+ Trace 32146
Thread 2 (Process 27532, Thread 2)
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-12-30 09:24 ------- The original reporter (james@tunasafedolphin.org) 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.
*** This bug has been marked as a duplicate of 100709 ***
I apologize for the spam, but in talking to David Kennedy on #bugs we decided that it might be useful for me to add a comment to a lot of bugs that have nearly identical stack traces that aren't very useful. (It took me a while because I gave up on several bugzilla queries that simply hung). Anyway, I may have caught some bugs with this query that aren't relevant, so I apologize again if this bug is one of those. If not: The following comment from 100709 may be relevant: "It turns out this was an accidental FreeBSD ABI change during the import of gcc-3.2.1. div(), a structure returning function, was the culprit."