After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 146992 - Nautilus crashes when the Computer icon open
Nautilus crashes when the Computer icon open
Status: RESOLVED DUPLICATE of bug 137654
Product: nautilus
Classification: Core
Component: Desktop
2.6.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-30 14:20 UTC by dhom
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description dhom 2004-07-09 14:21:07 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: nautilus
Severity: normal
Version: GNOME2.6. 2.6.x
Gnome-Distributor: Red Hat, Inc
Synopsis: Nautilus crashes when the Computer icon open
Bugzilla-Product: nautilus
Bugzilla-Component: Desktop
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:
Trying to open "Computer" (click on icon/select location) lead to crash
of Nautilus

Steps to reproduce the crash:
1. Do not know
2. Possible the manual chage of /ets/fstab file content
3. Just open "Computer"

Expected Results:
crush

How often does this happen?
always

Additional Information:
I do check the functionality just after installetion - everything works
fine, then I setup some aditional RPMs and change the /etc/fstab file to
make some devices mount with aditional options. Then I click "Computer"
and the Nautilus has crashed.


Debugging Information:

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/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)...(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 -150289248 (LWP 3853)]
[New Thread 84433840 (LWP 3860)]
[Thread debugging using libthread_db enabled]
[New Thread -150289248 (LWP 3853)]
[New Thread 84433840 (LWP 3860)]
[Thread debugging using libthread_db enabled]
[New Thread -150289248 (LWP 3853)]
[New Thread 84433840 (LWP 3860)]
[New Thread 26618800 (LWP 3859)]
[New Thread 26352560 (LWP 3858)]
[New Thread 89381808 (LWP 3857)]
[New Thread 15342512 (LWP 3856)]
[New Thread 15076272 (LWP 3855)]
[New Thread 26086320 (LWP 3854)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0x00e1f402 in ?? ()

Thread 1 (Thread -150289248 (LWP 3853))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/libc.so.6
  • #5 ??
    from /usr/lib/gnome-vfs-2.0/modules/libcomputer.so
  • #6 ??
  • #7 ??
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 10:21 -------


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 dhom@eximb.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.

Comment 1 Martin Wehner 2004-07-10 18:30:14 UTC
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.
Comment 2 Martin Wehner 2004-09-16 19:54:05 UTC
No new info -> closing.
Comment 3 Matthew Gatto 2004-11-06 03:59:01 UTC
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 bug has been marked as a duplicate of 137654 ***