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 135749 - Nautilus crashes when I use Image Visualization Mode and I get up to the superior dir
Nautilus crashes when I use Image Visualization Mode and I get up to the supe...
Status: RESOLVED DUPLICATE of bug 128067
Product: nautilus
Classification: Core
Component: general
2.4.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-02-29 11:58 UTC by busnellobruni
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description busnellobruni 2004-02-29 12:05:43 UTC
Distribution: Slackware Slackware 9.1.0
Package: nautilus
Severity: normal
Version: GNOME2.4.0 2.4.0
Gnome-Distributor: GNOME.Org
Synopsis: Nautilus crashes when I use Image Visualization Mode and I get up to the superior dir
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.4.0
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
Nautilus crashes when I use Image Visualization Mode and I get up to the
superior dir

Steps to reproduce the crash:
1. Go to a folder which contains images
2. select Image visualization mode (I've got nautilus in italian, so I
don't know the exact caption...), you'll get an interface with an image
on the center, some information on the right, and the preview of the
other images on the bottom.
3. Try to go to the superior folder

Expected Results:
I get segfault

How often does this happen?
Whenever i try to do that

Additional Information:
I have got nautilus 2.4.0, so I don't know if the bug is only in this
version.


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)...[New Thread 16384 (LWP 1449)]
[New Thread 32769 (LWP 1450)]
[New Thread 16386 (LWP 1451)]
[New Thread 32771 (LWP 1452)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x40b6860c in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 1449))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 gdk_window_set_cursor
    from /usr/lib/libgdk-x11-2.0.so.0
  • #5 nautilus_icon_canvas_item_update_bounds
    from /usr/lib/libnautilus-private.so.2
  • #6 eel_marshal_BOOLEAN__BOXED
    from /usr/lib/libeel-2.so.2
  • #7 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 eel_canvas_new
    from /usr/lib/libeel-2.so.2
  • #13 eel_canvas_new
    from /usr/lib/libeel-2.so.2
  • #14 eel_canvas_new
    from /usr/lib/libeel-2.so.2
  • #15 eel_canvas_new
    from /usr/lib/libeel-2.so.2
  • #16 g_timeout_add
    from /usr/lib/libglib-2.0.so.0
  • #17 unblock_source
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 main
  • #23 __libc_start_main
    from /lib/libc.so.6
  • #0 waitpid
    from /lib/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-02-29 07:05 -------

Unknown version 2.4.0 in product nautilus. Setting version to the default, "unspecified".
The original reporter (busnellobruni@tin.it) 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.

Comment 1 Martin Wehner 2004-02-29 22:41:00 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 128067 ***