Bug 549144 – Crash when pressing Insert/Space on a directory

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 549144 - Crash when pressing Insert/Space on a directory


Summary:	Crash when pressing Insert/Space on a directory


Status:	RESOLVED DUPLICATE of bug 567404

Product:	gnome-commander
Classification:	Other
Component:	application
Version:	1.2.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	1.2.8
Assigned To:	epiotr
QA Contact:	epiotr

URL:
Whiteboard:

Duplicates:	581104 (view as bug list)
Depends on:
Blocks:

Reported:	2008-08-23 21:00 UTC by Peter Avramucz
Modified:	2009-05-03 21:17 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Peter Avramucz 2008-08-23 21:00:36 UTC

Steps to reproduce:
1. Select a directory, with the cursor
2. Press Insert or Space
3. Notice, that the application crashed


Stack trace:
Program received signal SIGSEGV, Segmentation fault.

+ Trace 205583

Thread 3078039296 (LWP 10986)

#0 strlen
from /lib/libc.so.6
#1 vfprintf
from /lib/libc.so.6
#2 vasprintf
from /lib/libc.so.6
#3 g_vasprintf
from /usr/lib/libglib-2.0.so.0
#4 g_strdup_printf
from /usr/lib/libglib-2.0.so.0
#5 on_list_selection_changed
at gnome-cmd-file-selector.cc line 189
#6 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#11 gnome_cmd_file_list_toggle
at gnome-cmd-file-list.cc line 321
#12 gnome_cmd_file_list_keypressed
at gnome-cmd-file-list.cc line 2348
#13 on_list_key_pressed
at gnome-cmd-file-selector.cc line 1154
#14 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#19 gtk_widget_event_internal
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_window_propagate_key_event
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_window_key_press_event
from /usr/lib/libgtk-x11-2.0.so.0
#22 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 gtk_widget_event_internal
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 gdk_event_dispatch
from /usr/lib/libgdk-x11-2.0.so.0
#32 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#34 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#35 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#36 main
at main.cc line 145


Other information:
I'm using Arch Linux: http://www.archlinux.org/.

Comment 1 Peter Avramucz 2008-08-24 19:15:15 UTC

Forgot to mention: 1.2.3-1.2.5 versions doesn't have this problem, only 1.2.6 and 1.2.7.

Comment 2 Peter Avramucz 2009-04-03 09:57:37 UTC

I have narrowed down the problem:
Starting gcmd with LC_ALL="C" or "en_US.UTF-8" -> no problem.
However my locale is hu_HU.UTF-8. If I start gcmd with this or with "hu_HU", gcmd craches when I press insert on a directory.
Here is the full backtrace:
http://pastebin.com/f3b66d8ae

Comment 3 epiotr 2009-04-03 10:45:10 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 567404 ***

Comment 4 epiotr 2009-05-03 21:17:56 UTC

*** Bug 581104 has been marked as a duplicate of this bug. ***