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 404004 - crash in GNOME Commander: The language of applicat...
crash in GNOME Commander: The language of applicat...
Status: RESOLVED DUPLICATE of bug 349631
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-02-03 17:50 UTC by barna.hajzer
Modified: 2007-02-10 15:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description barna.hajzer 2007-02-03 17:50:45 UTC 
Version: 1.2.0

What were you doing when the application crashed?
The language of application is in hungarian. But I am not sure you can understand there. So I type it in english:
I opened the SMB pane, than try to open MSHOME - the group of my two flatmates' computers. GNOME Commander offered to download this (?) and open with inbuilt editor. "no" was choosen. After that the application tried to do something while I did the same (clicking here & there) then I got this bugreporting pane :) Otherwise using other file explorer I can open SMB... I hope you can fix this bug soon!


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

Memory status: size: 45240320 vsize: 0 resident: 45240320 share: 0 rss: 14192640 rss_rlim: 0
CPU usage: start_time: 1170524706 rtime: 0 utime: 128 stime: 0 cutime:124 cstime: 0 timeout: 4 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 -1225267536 (LWP 22077)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 107709

Thread 1 (Thread -1225267536 (LWP 22077))

  • #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 ??
  • #6 ??
  • #7 ??
  • #8 g_value_peek_pointer
    from /usr/lib/libgobject-2.0.so.0
  • #9 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 _IO_stdin_used
  • #26 ??
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2007-02-10 15:38:50 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 349631 ***