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 162436 - Nautilus crash when there are multiple nfs mounts on the same mount point
Nautilus crash when there are multiple nfs mounts on the same mount point
Status: RESOLVED DUPLICATE of bug 153888
Product: nautilus
Classification: Core
Component: general
2.8.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-12-29 09:50 UTC by Wouter Cloetens
Modified: 2004-12-29 14:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Wouter Cloetens 2004-12-29 09:51:11 UTC
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.8.1 2.8.2
Gnome-Distributor: Debian
Synopsis: Nautilus crash when mounting nfs drive on command line
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.8.2
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
Nautilus crashed suddenly when I mounted an nfs drive from the command
line. It turns out that the drive was already mounted on that mount
point.

Steps to reproduce the crash:
I'll try to do this again to see if it crashes again.

Expected Results:


How often does this happen?
First time it happened. Will check if it happens systematically.


Additional Information:



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)...[Thread debugging using
libthread_db enabled]
[New Thread 1090729472 (LWP 8475)]
[New Thread 1101728688 (LWP 8479)]
[Thread debugging using libthread_db enabled]
[New Thread 1090729472 (LWP 8475)]
[New Thread 1101728688 (LWP 8479)]
(no debugging symbols found)...[New Thread 1101073328 (LWP 8478)]
(no debugging symbols found)...[New Thread 1100385200 (LWP 8476)]
(no debugging symbols found)...(no debugging symbols found)...(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 1090729472 (LWP 8475)]
[New Thread 1101728688 (LWP 8479)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...0x4044a431 in __waitpid_nocancel
() from /lib/tls/libpthread.so.0

Thread 1 (Thread 1090729472 (LWP 8475))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/tls/libc.so.6
  • #4 ??
    from /lib/tls/libc.so.6
  • #5 ??
  • #6 abort
    from /lib/tls/libc.so.6
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 ??
  • #42 g_free
    from /usr/lib/libglib-2.0.so.0
  • #43 g_log
    from /usr/lib/libglib-2.0.so.0
  • #44 nautilus_directory_are_all_files_seen
    from /usr/lib/libnautilus-private.so.2
  • #45 nautilus_directory_add_file
    from /usr/lib/libnautilus-private.so.2
  • #46 nautilus_desktop_icon_file_new
    from /usr/lib/libnautilus-private.so.2
  • #47 nautilus_desktop_link_get_type
    from /usr/lib/libnautilus-private.so.2
  • #48 nautilus_desktop_link_new_from_volume
    from /usr/lib/libnautilus-private.so.2
  • #49 nautilus_desktop_link_monitor_delete_link
    from /usr/lib/libnautilus-private.so.2
  • #50 nautilus_desktop_link_monitor_delete_link
    from /usr/lib/libnautilus-private.so.2
  • #51 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #52 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #53 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #54 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #55 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #56 nautilus_desktop_link_monitor_get
    from /usr/lib/libnautilus-private.so.2
  • #57 nautilus_application_startup
  • #58 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-29 04:51 -------


Unknown version 2.8.2 in product nautilus.  Setting version to "2.8.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
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 Wouter Cloetens 2004-12-29 10:05:52 UTC
The problem is systematic and reproducible. As long as there are multiple mounts
on the same mount point, Nautilus crashes on start-up.
When the double mount situation drive is resolved, Nautilus starts again.
Comment 2 Vincent Noel 2004-12-29 14:21:34 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 153888 ***