[Xfce-bugs] [Bug 16824] New: crash in bulk renamer on repeated rename

[bugzilla-daemon at xfce.org]

https://bugzilla.xfce.org/show_bug.cgi?id=16824

            Bug ID: 16824
           Summary: crash in bulk renamer on repeated rename
    Classification: Xfce Core
           Product: Thunar
           Version: git
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Medium
         Component: Renamer
          Assignee: xfce-bugs at xfce.org
          Reporter: alexxcons at xfce.org
  Target Milestone: 1.8.13

Repeated rename via bulk renamer only works when it is launched via console:
gdb --args /thunar/.libs/thunar -B

In order to trigger the crash, add two files to the bulk renamer and rename
then. Than rename then again.
The way of renaming (numbering, date, etc.) does not matter. 

I can reproduce the bug on master, and on 1.8.0, so it is not related to recent
commits. 

I got the following Error/Backtrace :

thunar:ERROR:thunar-renamer-progress.c:262:thunar_renamer_progress_next_idle:
assertion failed: (g_list_length (renamer_progress->pairs_done) ==
renamer_progress->n_pairs_done)
Bail out!
thunar:ERROR:thunar-renamer-progress.c:262:thunar_renamer_progress_next_idle:
assertion failed: (g_list_length (renamer_progress->pairs_done) ==
renamer_progress->n_pairs_done)

Thread 1 "thunar" received signal SIGABRT, Aborted.
__GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht
gefunden.
(gdb) bt
#0  __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007ffff696355b in __GI_abort () at abort.c:79
#2  0x00007ffff6b40de3 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff6b9c77b in g_assertion_message_expr () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00005555555df748 in thunar_renamer_progress_next_idle
(user_data=<optimized out>) at thunar-renamer-progress.c:262
#5  0x00007ffff6b744de in g_main_context_dispatch () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007ffff6b74890 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007ffff6b74b63 in g_main_loop_run () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x00005555555dfb81 in thunar_renamer_progress_run
(renamer_progress=0x555555f3f9c0, pairs=0x5555558da240 = {...}) at
thunar-renamer-progress.c:376
#9  0x00005555555dc452 in thunar_renamer_dialog_response
(dialog=0x55555592a300, response=<optimized out>) at
thunar-renamer-dialog.c:804
#10 0x00007ffff6c6118e in g_cclosure_marshal_VOID__BOOLEANv () at
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00007ffff6c5f206 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x00007ffff6c7d8d4 in g_signal_emit_valist () at
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
.... I dumped the reimaining backtrace ...  only alot of internal g_signal
stuff and the main / g_application_run

-- 
You are receiving this mail because:
You are the assignee for the bug.