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 149759 - Nautilus crash when I move a file to a directory that have a file with the same name (only when the name is in Hebrew)
Nautilus crash when I move a file to a directory that have a file with the sa...
Status: RESOLVED DUPLICATE of bug 149202
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.6.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-08-09 20:05 UTC by Yuval Tanny
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Attachments
My crash log (4.28 KB, text/plain)
2004-08-10 04:40 UTC, Shoshannah Forbes
Details

Description Yuval Tanny 2004-08-09 20:05:48 UTC
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.6.1 2.6.3
Gnome-Distributor: Debian
Synopsis: Nautilus crash when I move a file to a directory that have a file with
the same name (only when the name is in Hebrew)
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.6.3
BugBuddy-GnomeVersion: 2.0 (2.6.1.1)
Description:
Description of the crash:
Nautilus crash when I move a file to a directory that have a file with
the same name (only when the name is in Hebrew), and I think it's
Happened only on desktop.

Steps to reproduce the crash:
1. Create a directory on the desktop.
2. Create a file (or directory) with an Hebrew name (maybe it will work
with other unicode language) on the desktop.
3.  Create a file (or directory) with the SAME Hebrew name (maybe it
will work with other unicode language) in the directory we created at
the first stage.
4. Move (drag & drop) the file we created on the desktop to the
directory we created on the desktop.
5. Instead of ask for overwrite dialog, nautilus crash.

Expected Results:
5. Instead of ask for overwrite dialog, nautilus crash.

How often does this happen?
All the time. I tested it on Gnome 2.6 on Debian Gnu/Linux Sid and
Sarge.

Additional Information:
Keep Up The Good Work!


Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/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 16384 (LWP 19860)]
[New Thread 32769 (LWP 19864)]
[New Thread 16386 (LWP 19866)]
[New Thread 32771 (LWP 19867)]
[New Thread 49156 (LWP 19868)]
[New Thread 65541 (LWP 19869)]
[New Thread 81926 (LWP 19870)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...0x4038fc0b in waitpid () from
/lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 19860))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 ??
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/libpthread.so.0
  • #5 <signal handler called>
  • #6 kill
    from /lib/libc.so.6
  • #7 pthread_kill
    from /lib/libpthread.so.0
  • #8 raise
    from /lib/libpthread.so.0
  • #9 raise
    from /lib/libc.so.6
  • #10 abort
    from /lib/libc.so.6
  • #11 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #12 g_log
    from /usr/lib/libglib-2.0.so.0
  • #13 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #14 eel_pango_layout_set_font_desc_from_string
    from /usr/lib/libeel-2.so.2
  • #15 eel_pango_layout_set_font_desc_from_string
    from /usr/lib/libeel-2.so.2
  • #16 eel_pango_layout_set_text_ellipsized
    from /usr/lib/libeel-2.so.2
  • #17 nautilus_file_operations_progress_resume_timeout
    from /usr/lib/libnautilus-private.so.2
  • #18 nautilus_file_operations_progress_resume_timeout
    from /usr/lib/libnautilus-private.so.2
  • #19 nautilus_file_operations_progress_resume_timeout
    from /usr/lib/libnautilus-private.so.2
  • #20 _gnome_vfs_job_complete
    from /usr/lib/libgnomevfs-2.so.0
  • #21 _gnome_vfs_job_complete
    from /usr/lib/libgnomevfs-2.so.0
  • #22 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 main
  • #0 waitpid
    from /lib/libpthread.so.0

Comment 1 Shoshannah Forbes 2004-08-10 04:35:15 UTC
What is your locale? (the output of the command locale in the shell).
BTW, this bug probably belongs to "file and folder oparations" component. 
Comment 2 Shoshannah Forbes 2004-08-10 04:39:36 UTC
Yep, I am seeing the same crash following the steps outlined above (using gnome
2.6.3 on Gentoo) Attached is my crash report
Comment 3 Shoshannah Forbes 2004-08-10 04:40:32 UTC
Created attachment 30385 [details]
My crash log

The crash I get when I repro this bug
Comment 4 Yuval Tanny 2004-08-10 10:14:15 UTC
I checked this bug and it's occur on locales: he_IL (ISO-8859-8), he_IL.UTF-8
(UTF-8) and en_US.UTF-8 (UTF-8).
Comment 5 Vincent Noel 2004-08-12 14:40:11 UTC

*** This bug has been marked as a duplicate of 149202 ***