GNOME Bugzilla – Bug 137110
first start
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: 2.4.2 Synopsis: first start Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.4.2 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: first start of nautilus testing after intalling via apt-get Steps to reproduce the crash: 1. open icewm menue 2. klick nautilus 3. failure Expected Results: normal start of nautilus How often does this happen? always 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)...[New Thread 16384 (LWP 17091)] [New Thread 32769 (LWP 17094)] [New Thread 16386 (LWP 17095)] [New Thread 32771 (LWP 17096)] [New Thread 49156 (LWP 17097)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40a0bbfb in waitpid () from /lib/libpthread.so.0
+ Trace 45092
Thread 5 (Thread 49156 (LWP 17097))
Thread 4 (Thread 32771 (LWP 17096))
Thread 3 (Thread 16386 (LWP 17095))
Thread 1 (Thread 16384 (LWP 17091))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-13 17:22 ------- Unknown version 2.4.2 in product nautilus. Setting version to the default, "unspecified". The original reporter (alexander.rose@weirdbyte.de) 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. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. You should check your /etc/fstab for a bad syntax or duplicate mounts, and if you find out what's wrong, add a comment to bug 120222 where all further discussion of this particular problem should reside. *** This bug has been marked as a duplicate of 120222 ***