GNOME Bugzilla – Bug 123084
tried to change themes on freebsd 5.1-current
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Unknown Package: nautilus Severity: normal Version: GNOME2.4.0 2.4.0 Gnome-Distributor: FreeBSD GNOME Project Synopsis: tried to change themes on freebsd 5.1-current Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.4.0 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Tried to change the theme and it crashed Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? 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)...[Switching to Process 675, Thread 1] 0x28db1c5f in poll () from /lib/libc.so.5
+ Trace 40386
Thread 6 (Process 675, Thread 6)
Thread 5 (Process 675, Thread 5)
Thread 4 (Process 675, Thread 4)
Thread 3 (Process 675, Thread 3)
Thread 2 (Process 675, Thread 2)
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-09-23 20:37 ------- Unknown version 2.4.0 in product nautilus. Setting version to the default, "unspecified". The original reporter (tflorman@nilenet.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.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces.
Re-opening, as this is a dup of bug 120601.
Marking as dup. Sorry for the spam. *** This bug has been marked as a duplicate of 120601 ***