Bug 316899 – nautilus crash on operations with filename that contains "&" (&)

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 316899 - nautilus crash on operations with filename that contains "&" (&)


Summary:	nautilus crash on operations with filename that contains "&" (&)


Status:	RESOLVED DUPLICATE of bug 168695

Product:	nautilus-python
Classification:	Other
Component:	general
Version:	0.3.2
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-09-22 02:17 UTC by Lucas Lommer
Modified:	2005-09-22 11:33 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Description Lucas Lommer 2005-09-22 02:17:27 UTC

Steps to reproduce:
1. Create an file ot directory with name containing &
2. Try to copy using nautilus drag&drop

Stack trace:
=== BugBuddy report ============================================================
Distribution: Ubuntu 5.10 (breezy)
Package: nautilus
Severity: Normal
Version: GNOME2.12.0 2.12.0
Gnome-Distributor: Ubuntu
Synopsis: nautilus crash on operations with filename that contains "&" (&amp;)
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.12.0
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
When operating with file which name contains "&" (&amp; in HTML),
nautilus crashed.

Steps to reproduce the crash:
1. Create an file ot directory with name containing &
2. try to copy using nautilus drag&drop

How often does this happen?
everytime


Debugging Information:

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1225881376 (LWP 30699)]
[New Thread -1238996048 (LWP 30705)]
[New Thread -1238729808 (LWP 30704)]
[New Thread -1238463568 (LWP 30703)]
[New Thread -1228198992 (LWP 30700)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 63129

Thread 1 (Thread -1225807648 (LWP 31159))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 PyErr_Fetch
from /usr/lib/libpython2.4.so.1.0
#5 PyModule_GetWarningsModule
from /usr/lib/libpython2.4.so.1.0
#6 PyErr_Warn
from /usr/lib/libpython2.4.so.1.0
#7 ??
#8 ??
#9 ??
#10 g_log_domain_get_handler_L
at gmessages.c line 225
#11 IA__g_logv
at gmessages.c line 474
#12 IA__g_log
at gmessages.c line 517
#13 gtk_label_recalculate
at gtklabel.c line 1271
#14 nautilus_file_operations_progress_new_file
at nautilus-file-operations-progress.c line 585
#15 progress_dialog_set_to_from_item_text
at nautilus-file-operations.c line 397
#16 handle_transfer_ok
at nautilus-file-operations.c line 486
#17 dispatch_sync_job_callback
at gnome-vfs-job.c line 283
#18 g_idle_dispatch
at gmain.c line 3813
#19 IA__g_main_context_dispatch
at gmain.c line 1934
#20 g_main_context_iterate
at gmain.c line 2565
#21 IA__g_main_loop_run
at gmain.c line 2769
#22 IA__gtk_main
at gtkmain.c line 976
#23 main
at nautilus-main.c line 435
#0 __kernel_vsyscall



Other information:
You can see nautilus crash in action as flash -
http://kdyne.net/temp_drom/gnome-bugs/amp_crash.swf (.swf, 22.5 MB)

Comment 1 Lucas Lommer 2005-09-22 02:52:22 UTC

If any questions - Drom@irc.gnome.org, #gnome, #gnome-art, #i18n

Comment 2 Sebastien Bacher 2005-09-22 11:33:49 UTC

this is a python-nautilus bug

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