Nautilus crash on paste of more than one file in hebrew

[Sagi Zeevi]

Binary package hint: nautilus

Simple to reproduce:
Login to gnome with the Hebrew language.
Select at least 2 files.
Copy them (Ctrl-c), and paste them in some other folder (Ctrl-v).
nautilus crashes.

Note:
Only happens when I login with the Hebrew language.
Works fine when I login with the English language.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.24.1-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: nautilus --no-desktop --browser
ProcCwd: /home/sagi
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=he_IL.UTF-8
 SHELL=/usr/bin/tcsh
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_file_query_info () from /usr/lib/libgio-2.0.so.0
 ?? ()
 eel_strdup_vprintf_with_custom ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_file_query_info()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:g_file_query_info () from /usr/lib/libgio-2.0.so.0
custom_basename_to_string (format=0x9b3c460 "%B",
eel_strdup_vprintf_with_custom (custom=0x818c7a0,
f (format=0xb688eac0 <Address 0xb688eac0 out of bounds>)
report_copy_progress (copy_job=0x98a6fb0,

[Pedro Villavicencio (pedro)]

looks like http://bugzilla.gnome.org/show_bug.cgi?id=554003, linking the report, thanks.

[Sagi Zeevi (sagiz)]

Hey guys, this seems to be fixed now somehow since it doesn't happen anymore.

[Omer Akram (om26er)]

a recent duplicate to this bug report is caused even with english so this is not specific to hebrew. if anyone still face this issue with ubuntu 10.10 please get a backtrace for the crash using this procedure https://wiki.ubuntu.com/Backtrace and attach the logs file to this bug report. this will help us solve the problem

[Omer Akram (om26er)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.