#30 unable to clear log
cris@ubuntubas:~$ gprename
GLib-GObject-CRITICAL : g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm line 204.
GLib-GObject-CRITICAL : g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm line 204.
GLib-GObject-CRITICAL : g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm line 204.
GLib-GObject-CRITICAL : g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm line 204.
(gprename:5890): Gdk-ERROR **: 12:44:04.986: The program 'gprename' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 7310 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trappe pour point d'arrêt et de trace (core dumped)
cris@ubuntubas:~$
Cannot reproduce here with latest version 20220807. How big is your log file? Check in your home folder in .config/gprename it is called gprename_log. You can safely delete it which will do the same thing.
Thank you for your reply.
The log file is 1.5 MB (but as soon as it reached 1 MB the message appeared to empty the log.
The version is: GPRename 20210415
as recommended, I delete the log.
Good day to you, thank you for your work.
I went up to a 2.4 MB file and was able to succesfully clear the log. It will remain a mystery why you had a "BadAlloc insufficient resources for operation". Closing.