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 421857 - crash in GNOME Commander: browsing folder .macrome...
crash in GNOME Commander: browsing folder .macrome...
Status: RESOLVED DUPLICATE of bug 360175
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: High critical
: 1.2.4
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2007-03-23 11:56 UTC by daymoss
Modified: 2008-01-06 23:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description daymoss 2007-03-23 11:56:25 UTC
Version: 1.2.3

What were you doing when the application crashed?
browsing folder .macromedia/Flash_Player/#SharedObjects


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

Memory status: size: 98635776 vsize: 0 resident: 98635776 share: 0 rss: 21987328 rss_rlim: 0
CPU usage: start_time: 1174649699 rtime: 0 utime: 1200 stime: 0 cutime:658 cstime: 0 timeout: 542 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 -1208588624 (LWP 6189)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1208588624 (LWP 6189))

  • #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 ??
  • #5 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_window_new
    from /usr/lib/libgtk-x11-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_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #11 gtk_drag_finish
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 _gtk_marshal_VOID__BOXED_UINT_UINT
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #17 gtk_selection_data_set
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_selection_convert
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_drag_get_data
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 _gtk_drag_source_handle_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gtk_drag_unhighlight
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 _gtk_drag_dest_handle_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_events_init
    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_check
    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 ??
  • #37 ??
  • #38 ??
  • #39 _IO_stdin_used
  • #40 ??
  • #0 __kernel_vsyscall

Comment 1 epiotr 2008-01-06 23:05:01 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 360175 ***