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 375704 - crash in GNOME Commander: Regel im Tool zu Mehrfac...
crash in GNOME Commander: Regel im Tool zu Mehrfac...
Status: RESOLVED DUPLICATE of bug 407418
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: High critical
: 1.2.2
Assigned To: epiotr
epiotr
: 380115 381934 383163 383164 383904 387243 389034 393635 401024 402114 410591 411991 415107 415451 415992 416602 416603 418262 418264 418268 421538 426747 441574 446200 453103 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-15 21:24 UTC by mic
Modified: 2008-01-06 22:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description mic 2006-11-15 21:24:42 UTC
Version: 1.2.0

What were you doing when the application crashed?
Regel im Tool zu Mehrfachumbenennen geändert


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

Memory status: size: 55713792 vsize: 0 resident: 55713792 share: 0 rss: 14749696 rss_rlim: 0
CPU usage: start_time: 1163625647 rtime: 0 utime: 76 stime: 0 cutime:72 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 -1225296208 (LWP 6041)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225296208 (LWP 6041))

  • #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-11-29 00:13:26 UTC
*** Bug 380115 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2006-12-05 01:28:34 UTC
*** Bug 381934 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2006-12-05 01:29:00 UTC
confirming as per duplicates
Comment 4 Baptiste Mille-Mathias 2006-12-06 21:34:57 UTC
*** Bug 383163 has been marked as a duplicate of this bug. ***
Comment 5 Baptiste Mille-Mathias 2006-12-06 21:35:39 UTC
*** Bug 383164 has been marked as a duplicate of this bug. ***
Comment 6 Baptiste Mille-Mathias 2006-12-06 21:37:30 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

You'll also need to add a stack trace with debug information (of gtk+ 2, glib 2 at least); please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!
Comment 7 Baptiste Mille-Mathias 2006-12-06 21:40:22 UTC
grrr, setting to NEW again
Comment 8 André Klapper 2006-12-10 19:24:53 UTC
*** Bug 383904 has been marked as a duplicate of this bug. ***
Comment 9 epiotr 2006-12-20 23:16:46 UTC
*** Bug 387243 has been marked as a duplicate of this bug. ***
Comment 10 André Klapper 2007-01-29 02:14:11 UTC
*** Bug 389034 has been marked as a duplicate of this bug. ***
Comment 11 André Klapper 2007-01-29 02:14:17 UTC
*** Bug 401024 has been marked as a duplicate of this bug. ***
Comment 12 palfrey 2007-02-21 15:45:49 UTC
*** Bug 402114 has been marked as a duplicate of this bug. ***
Comment 13 palfrey 2007-02-22 16:23:35 UTC
*** Bug 410591 has been marked as a duplicate of this bug. ***
Comment 14 Paweł Widera 2007-02-25 20:06:54 UTC
*** Bug 411991 has been marked as a duplicate of this bug. ***
Comment 15 Susana 2007-03-09 13:10:49 UTC
*** Bug 415107 has been marked as a duplicate of this bug. ***
Comment 16 Susana 2007-03-09 13:11:02 UTC
*** Bug 415451 has been marked as a duplicate of this bug. ***
Comment 17 Susana 2007-03-09 13:11:16 UTC
*** Bug 415992 has been marked as a duplicate of this bug. ***
Comment 18 Susana 2007-03-15 13:39:28 UTC
*** Bug 416602 has been marked as a duplicate of this bug. ***
Comment 19 Susana 2007-03-15 13:40:56 UTC
*** Bug 416603 has been marked as a duplicate of this bug. ***
Comment 20 Susana 2007-03-15 13:41:09 UTC
*** Bug 418262 has been marked as a duplicate of this bug. ***
Comment 21 Susana 2007-03-15 13:41:21 UTC
*** Bug 418264 has been marked as a duplicate of this bug. ***
Comment 22 Susana 2007-03-15 13:41:36 UTC
*** Bug 418268 has been marked as a duplicate of this bug. ***
Comment 23 Susana 2007-03-22 20:31:07 UTC
*** Bug 421538 has been marked as a duplicate of this bug. ***
Comment 24 Susana 2007-04-09 14:45:27 UTC
*** Bug 426747 has been marked as a duplicate of this bug. ***
Comment 25 André Klapper 2007-07-30 01:07:47 UTC
*** Bug 441574 has been marked as a duplicate of this bug. ***
Comment 26 André Klapper 2007-07-30 01:17:07 UTC
*** Bug 446200 has been marked as a duplicate of this bug. ***
Comment 27 André Klapper 2007-07-30 01:18:15 UTC
*** Bug 453103 has been marked as a duplicate of this bug. ***
Comment 28 André Klapper 2007-07-30 01:19:14 UTC
*** Bug 393635 has been marked as a duplicate of this bug. ***
Comment 29 André Klapper 2007-07-30 01:21:57 UTC
@epiotr: looks like bug 412031 has a nice stacktrace for this one
Comment 30 epiotr 2008-01-06 22:56:32 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 407418 ***