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 360175 - crash in GNOME Commander: entering a dir with %{.....
crash in GNOME Commander: entering a dir with %{.....
Status: RESOLVED FIXED
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: High critical
: 1.2.4
Assigned To: epiotr
epiotr
: 376909 388554 408352 421857 426140 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-06 14:12 UTC by Stephanos Manos
Modified: 2008-01-06 23:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Stephanos Manos 2006-10-06 14:12:23 UTC
Version: 1.2.1

What were you doing when the application crashed?
entering a dir with %{..} in the name


Distribution: Fedora Core release 5.92 (FC6 Test3)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 98840576 vsize: 0 resident: 98840576 share: 0 rss: 14004224 rss_rlim: 0
CPU usage: start_time: 1160134746 rtime: 0 utime: 2620 stime: 0 cutime:2524 cstime: 0 timeout: 96 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208490288 (LWP 4230)]
(no debugging symbols found)
0x00ef2402 in __kernel_vsyscall ()

Thread 1 (Thread -1208490288 (LWP 4230))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /lib/libglib-2.0.so.0
  • #5 g_hash_table_insert
    from /lib/libglib-2.0.so.0
  • #6 g_cclosure_marshal_VOID__VOID
  • #7 g_cclosure_marshal_VOID__VOID
  • #8 g_cclosure_marshal_VOID__VOID
  • #9 g_cclosure_marshal_VOID__VOID
  • #10 g_cclosure_marshal_VOID__VOID
  • #11 g_cclosure_marshal_VOID__VOID
  • #12 g_cclosure_marshal_VOID__VOID
  • #13 g_cclosure_marshal_VOID__VOID
  • #14 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #19 gtk_widget_get_default_style
    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_activate_key
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #24 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #28 gtk_widget_get_default_style
    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_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #32 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #33 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #34 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #35 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 g_cclosure_marshal_VOID__VOID
  • #37 __libc_start_main
    from /lib/libc.so.6
  • #38 g_cclosure_marshal_VOID__VOID
  • #0 __kernel_vsyscall

Comment 1 epiotr 2006-10-07 14:24:36 UTC
Can't repoduce the bug. I've created dir '%{..}' wich can be accessed both via keyboard (ENTER) or mouse (double click) operations. Could send detailed information on how you've encountered this crash?


Piotr
Comment 2 Stephanos Manos 2006-10-08 21:31:19 UTC
Sorry for the delay,

The crash happend when accessind a folder created when building a new rpm with errors in the spec file.

I also can't reproduce the bug. 
I will try to create simmilar conditions and see if the crash happens again.
Comment 3 koos 2006-12-08 10:45:27 UTC
When I enter the directory 'Various Artists - 300% Dynamite' gnome commander crashes.
This happens every time. I started gnome-commander with the command-line option 'gnome-commander -d s'.

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225058624 (LWP 7599)]
[New Thread -1226478672 (LWP 7600)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225058624 (LWP 7599))

  • #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 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_insert
    from /usr/lib/libglib-2.0.so.0
  • #6 gnome_cmd_file_collection_add
    at gnome-cmd-file-collection.c line 127
  • #7 gnome_cmd_file_collection_add_list
    at gnome-cmd-file-collection.c line 137
  • #8 on_list_done
    at gnome-cmd-dir.c line 514
  • #9 dirlist_list
    at dirlist.c line 132
  • #10 gnome_cmd_file_selector_set_directory
    at gnome-cmd-file-selector.c line 1663
  • #11 do_file_specific_action
    at gnome-cmd-file-selector.c line 819
  • #12 gtk_marshal_VOID__POINTER_POINTER
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 gtk_signal_emit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 on_button_press
    at gnome-cmd-file-list.c line 1068
  • #18 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #23 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #27 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #30 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 main
    at main.c line 126
  • #0 __kernel_vsyscall

Comment 4 epiotr 2006-12-22 20:55:38 UTC
*** Bug 388554 has been marked as a duplicate of this bug. ***
Comment 5 Marc-Andre Lureau 2007-02-10 19:57:51 UTC
*** Bug 376909 has been marked as a duplicate of this bug. ***
Comment 6 koos 2007-02-13 15:20:52 UTC
(In reply to comment #1)
> Can't repoduce the bug. I've created dir '%{..}' wich can be accessed both via
> keyboard (ENTER) or mouse (double click) operations. Could send detailed
> information on how you've encountered this crash?
> 
> 
> Piotr
> 

I got some more information on this bug. The crash only happens when the directory with the %-sign contains subdirs or files. This only happens on the local filesystem. When entering the same directory through a smb-share gnome-commander doesn't crash.
When one tries to create a directory or file in the dir with the %-sign gnome-commander crashes as well.
I am not sure,  but I think the filename may be stored not correctly in the GnomeVFSFileInfo structure.

Hope this helps a bit.
Comment 7 koos 2007-02-13 15:28:43 UTC
(In reply to comment #6)

To correct one thing:
creating a subdir in a dir with a %-sign gives a warning: 'invalid parameters'

koos

> I got some more information on this bug. The crash only happens when the
> directory with the %-sign contains subdirs or files. This only happens on the
> local filesystem. When entering the same directory through a smb-share
> gnome-commander doesn't crash.
> When one tries to create a directory or file in the dir with the %-sign
> gnome-commander crashes as well.
> I am not sure,  but I think the filename may be stored not correctly in the
> GnomeVFSFileInfo structure.
> 
> Hope this helps a bit.
> 

Comment 8 epiotr 2007-02-15 23:43:47 UTC
*** Bug 408352 has been marked as a duplicate of this bug. ***
Comment 9 epiotr 2007-04-04 06:56:38 UTC
*** Bug 426140 has been marked as a duplicate of this bug. ***
Comment 10 epiotr 2007-04-28 17:08:26 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
Comment 11 epiotr 2008-01-06 23:05:01 UTC
*** Bug 421857 has been marked as a duplicate of this bug. ***