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 162722 - nautilus crashes after re-"loop-mounting" a CD-image
nautilus crashes after re-"loop-mounting" a CD-image
Status: RESOLVED DUPLICATE of bug 153888
Product: nautilus
Classification: Core
Component: general
2.8.x
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-01-02 13:21 UTC by christian
Modified: 2005-01-02 13:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description christian 2005-01-02 13:21:43 UTC
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.8.1 2.8.2
Gnome-Distributor: Debian
Synopsis: nautilus crashes after re-"loop-mounting" a CD-image
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.8.2
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:

I usually use jigdo-lite to keep my Debian-CD-images up to date.
Therefore, I have old images that should be updated to the most recent
version.

I "loop-mount" the old image for the first CD:
mount -o loop /path/to/image.iso /media/cdrom0
The "CD" respectively the mounted image appears as "cdrom0" on my Gnome
desktop, I open it by clicking, just to check if everything is right

Then, I start jigdo-lite, tell it to scan /media/cdrom0, and soon it
finds many of the files needed, an does its work fine.

The problem appeared when I tried to repeat the procedure for the second
CD-Image:
mount -o loop /path/to/image-for-cd2.iso /media/cdrom0 (without
umounting the old image first!)

Nautilus crashes an cannot be restarted, even a restart of the X-server
does not help. Fortunately, the command line still works fine and I am
able to complete the download auf the image for the second CD.

(Expected) Steps to reproduce the crash:

1. loop-mount a CD-image
(maybe: also open this mounted image with nautilus)
2. re-loop-mount another image to the same mount point without umounting
the other before
3. nautilus crashes an cannot be restarted

Expected Results:

Crash of nautilus, gets unstartable. Other Gnome-components still work.
The problem even remains after umounting the second image.

How often does this happen?

So far, only once, but I guess it is reproduceable.



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)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 -1224207104 (LWP 7049)]
[New Thread -1235416144 (LWP 7061)]
[Thread debugging using libthread_db enabled]
[New Thread -1224207104 (LWP 7049)]
[New Thread -1235416144 (LWP 7061)]
[New Thread -1235154000 (LWP 7060)]
[New Thread -1234891856 (LWP 7059)]
[New Thread -1234629712 (LWP 7058)]
[New Thread -1226228816 (LWP 7052)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7bc0431 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread -1224207104 (LWP 7049))

  • #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 2005-01-02 08:21 -------


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, '---'
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 christian@leitold.info.
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 Olav Vitters 2005-01-02 13:43:36 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 ***