Bug 381934 – crash in GNOME Commander: I was renaming a group o...

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 381934 - crash in GNOME Commander: I was renaming a group o...


Summary:	crash in GNOME Commander: I was renaming a group o...


Status:	RESOLVED DUPLICATE of bug 375704

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

Importance:	High critical
Target Milestone:	1.2.2
Assigned To:	epiotr
QA Contact:	epiotr

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-03 17:13 UTC by Paweł Widera
Modified:	2006-12-05 01:28 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Paweł Widera 2006-12-03 17:13:38 UTC

Version: 1.2.0

What were you doing when the application crashed?
I was renaming a group of files (CTRL+M). Crashed occured while editing a regular expression for text replacement.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 31506432 vsize: 0 resident: 31506432 share: 0 rss: 16207872 rss_rlim: 0
CPU usage: start_time: 1165145503 rtime: 0 utime: 519 stime: 0 cutime:491 cstime: 0 timeout: 28 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-commander'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225460048 (LWP 4851)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 91306

Thread 1 (Thread -1225460048 (LWP 4851))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_free
from /usr/lib/gnome-commander/libgcmd.so.0
#5 gnome_cmd_dialog_new
from /usr/lib/gnome-commander/libgcmd.so.0
#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 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#14 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_chain_from_overridden
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_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#21 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#34 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
#36 ??
#37 ??
#38 _IO_stdin_used
#39 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-12-05 01:28:34 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 375704 ***