Bug 541160 – crash in Open Folder: renaming a file

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 541160 - crash in Open Folder: renaming a file


Summary:	crash in Open Folder: renaming a file


Status:	RESOLVED DUPLICATE of bug 452894

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.22.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-07-02 03:30 UTC by zhouwanding
Modified:	2008-07-02 08:45 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description zhouwanding 2008-07-02 03:30:57 UTC

Version: 2.22.2

What were you doing when the application crashed?
renaming a file


Distribution: openSUSE 11.0 (i586)
Gnome Release: 2.22.1 2008-06-07 (SUSE)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.5-1.1-default #1 SMP 2008-06-07 01:55:22 +0200 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: Gilouche

Memory status: size: 136437760 vsize: 136437760 resident: 26304512 share: 21024768 rss: 47329280 rss_rlim: 1784058880
CPU usage: start_time: 1214924224 rtime: 131012 utime: 121057 stime: 9955 cutime:2 cstime: 25 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb6ad66d0 (LWP 3295)]
[New Thread 0xafe68b90 (LWP 17317)]
0xffffe430 in __kernel_vsyscall ()

+ Trace 201866

Thread 1 (Thread 0xb6ad66d0 (LWP 3295))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 google_breakpad::ExceptionHandler::HandleException
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#8 <signal handler called>
#9 g_type_check_instance
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_connect_data
from /usr/lib/libgobject-2.0.so.0
#11 set_pending_icon_to_reveal
#12 end_renaming_mode
#13 key_press_event
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_window_propagate_key_event
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#25 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#26 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgdk-x11-2.0.so.0
#33 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#35 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#36 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#37 main
#0 __kernel_vsyscall



----------- .xsession-errors (102 sec old) ---------------------
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
Unknown message: No such IMContext
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-07-02 08:45:09 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 452894 ***