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 412031 - crash in GNOME Commander: Selected all files in a ...
crash in GNOME Commander: Selected all files in a ...
Status: RESOLVED DUPLICATE of bug 467058
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-25 21:21 UTC by arson
Modified: 2008-01-06 22:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description arson 2007-02-25 21:21:53 UTC 
Version: 1.2.0

What were you doing when the application crashed?
Selected all files in a directory(ctrl-a) and use multi-rename tool(ctrl-t) to rename all files. When I hit ctrl-t a second time after the rename has finished, the crash occurs. Reproducible.


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

Memory status: size: 54235136 vsize: 0 resident: 54235136 share: 0 rss: 15380480 rss_rlim: 0
CPU usage: start_time: 1172438367 rtime: 0 utime: 333 stime: 0 cutime:321 cstime: 0 timeout: 12 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 -1225283920 (LWP 26769)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 113867

Thread 1 (Thread -1225283920 (LWP 26769))

  • #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 ??
  • #9 ??
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2007-02-27 14:54:27 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


Anders Runesson





          2007-02-27 18:40:43 UTC
        



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

Memory status: size: 53714944 vsize: 0 resident: 53714944 share: 0 rss: 14446592 rss_rlim: 0
CPU usage: start_time: 1172601174 rtime: 0 utime: 173 stime: 0 cutime:161 cstime: 0 timeout: 12 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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224927568 (LWP 5900)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    114375






Thread 1
          (Thread -1224927568 (LWP 5900))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/tls/i686/cmov/libpthread.so.0

    

    • 

  • 
#2
libgnomeui_segv_handle

    
                at gnome-ui-init.c
                  line
                  874

    

    • 

  • 
#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
IA__g_cclosure_marshal_VOID__VOID

    
                at gmarshal.c
                  line
                  77

    

    • 

  • 
#7
IA__g_closure_invoke

    
                at gclosure.c
                  line
                  490

    

    • 

  • 
#8
signal_emit_unlocked_R

    
                at gsignal.c
                  line
                  2440

    

    • 

  • 
#9
IA__g_signal_emit_valist

    • 

  • 
#10
IA__g_signal_emit

    
                at gsignal.c
                  line
                  2243

    

    • 

  • 
#11
IA__gtk_button_clicked

    
                at gtkbutton.c
                  line
                  889

    

    • 

  • 
#12
gtk_real_button_released

    
                at gtkbutton.c
                  line
                  1484

    

    • 

  • 
#13
IA__g_cclosure_marshal_VOID__VOID

    
                at gmarshal.c
                  line
                  77

    

    • 

  • 
#14
g_type_class_meta_marshal

    
                at gclosure.c
                  line
                  567

    

    • 

  • 
#15
IA__g_closure_invoke

    
                at gclosure.c
                  line
                  490

    

    • 

  • 
#16
signal_emit_unlocked_R

    
                at gsignal.c
                  line
                  2370

    

    • 

  • 
#17
IA__g_signal_emit_valist

    
                at gsignal.c
                  line
                  2199

    

    • 

  • 
#18
IA__g_signal_emit

    
                at gsignal.c
                  line
                  2243

    

    • 

  • 
#19
IA__gtk_button_released

    
                at gtkbutton.c
                  line
                  881

    

    • 

  • 
#20
gtk_button_button_release

    
                at gtkbutton.c
                  line
                  1377

    

    • 

  • 
#21
_gtk_marshal_BOOLEAN__BOXED

    
                at gtkmarshalers.c
                  line
                  84

    

    • 

  • 
#22
g_type_class_meta_marshal

    
                at gclosure.c
                  line
                  567

    

    • 

  • 
#23
IA__g_closure_invoke

    
                at gclosure.c
                  line
                  490

    

    • 

  • 
#24
signal_emit_unlocked_R

    
                at gsignal.c
                  line
                  2478

    

    • 

  • 
#25
IA__g_signal_emit_valist

    
                at gsignal.c
                  line
                  2209

    

    • 

  • 
#26
IA__g_signal_emit

    
                at gsignal.c
                  line
                  2243

    

    • 

  • 
#27
gtk_widget_event_internal

    
                at gtkwidget.c
                  line
                  3911

    

    • 

  • 
#28
IA__gtk_propagate_event

    
                at gtkmain.c
                  line
                  2211

    

    • 

  • 
#29
IA__gtk_main_do_event

    
                at gtkmain.c
                  line
                  1445

    

    • 

  • 
#30
gdk_event_dispatch

    
                at gdkevents-x11.c
                  line
                  2320

    

    • 

  • 
#31
IA__g_main_context_dispatch

    
                at gmain.c
                  line
                  2045

    

    • 

  • 
#32
g_main_context_iterate

    
                at gmain.c
                  line
                  2677

    

    • 

  • 
#33
IA__g_main_loop_run

    
                at gmain.c
                  line
                  2881

    

    • 

  • 
#34
IA__gtk_main

    
                at gtkmain.c
                  line
                  1024

    

    • 

  • 
#35
??

    • 

  • 
#36
??

    • 

  • 
#37
??

    • 

  • 
#38
_IO_stdin_used

    • 

  • 
#39
??

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 3


Susana





          2007-02-27 20:05:17 UTC
        



That was fast. Thanks Anders :)

(stacktrace unique according to s-d-f)






Comment 4


André Klapper





          2007-07-30 01:21:54 UTC
        



dup of bug 375704?






Comment 5


epiotr





          2008-01-06 22:53:47 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 467058 ***