GNOME Bugzilla – Bug 153387
wall paper
Last modified: 2005-01-22 20:54:08 UTC
Distribution: Debian 3.1 Package: nautilus Severity: normal Version: GNOME2.8.0 2.8.0 Gnome-Distributor: Ubuntu Synopsis: wall paper Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.8.0 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: just trying to change the wallpaper, navigating to the file Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...Using host libthread_db library "/lib/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)...(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 16384 (LWP 13085)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 13085)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 13085)] [New Thread 32769 (LWP 13087)] [New Thread 16386 (LWP 13088)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x0f939110 in waitpid () from /lib/libpthread.so.0
+ Trace 50367
Thread 3 (Thread 16386 (LWP 13088))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-22 02:05 ------- Unknown version 2.8.0 in product nautilus. Setting version to "1.0.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". 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 scalvin@nventure.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 a duplicate of bug 153511.
Looks like bug #146075 to me.
probably a duplicate of #1460785 but do you have some details on how to get this bug ? *** This bug has been marked as a duplicate of 146075 ***