If you can reproduce it, it would be useful to see the debug messages in Help->Debug Messages and if possible to provide a backtrace.

Issue occured only when there is no or no more occurence or string

Here is a gdb trace:
(gdb) run -v
Starting program: /usr/bin/geany -v
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff4f05700 (LWP 10867)]
[New Thread 0x7fffeffff700 (LWP 10868)]
(geany:10863): GLib-GIO-DEBUG: 08:49:44.358: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
Geany-INFO: 08:49:44.436: Geany 1.35, fr_FR.UTF-8
Geany-INFO: 08:49:44.436: GTK 3.24.12, GLib 2.62.4
Geany-INFO: 08:49:44.436: System data dir: /usr/share/geany
Geany-INFO: 08:49:44.436: User config dir: /home/thierry/.config/geany
[New Thread 0x7fffef7fe700 (LWP 10869)]
[New Thread 0x7fffeeffd700 (LWP 10870)]
Geany-INFO: 08:49:44.549: Loaded GTK+ CSS theme '/usr/share/geany/geany.css'
Geany-INFO: 08:49:44.550: Loaded GTK+ CSS theme '/usr/share/geany/geany-3.20.css'
Geany-INFO: 08:49:44.554: System plugin path: /usr/lib/x86_64-linux-gnu/geany
Geany-INFO: 08:49:44.566: Added filetype Arduino (61).
Geany-INFO: 08:49:44.566: Added filetype Scala (62).
Geany-INFO: 08:49:44.566: Added filetype Clojure (63).
Geany-INFO: 08:49:44.566: Added filetype Genie (64).
Geany-INFO: 08:49:44.566: Added filetype Cython (65).
Geany-INFO: 08:49:44.566: Added filetype JSON (66).
Geany-INFO: 08:49:44.566: Added filetype Graphviz (67).
Geany-INFO: 08:49:44.566: Added filetype CUDA (68).
Geany-INFO: 08:49:44.618: Loaded libvte from libvte-2.91.so.0
---> [SKIP openning my files open in previous session
[New Thread 0x7fffdb98a700 (LWP 10872)]
[Detaching after fork from child process 10873]
[Thread 0x7fffeeffd700 (LWP 10870) exited]
(geany:10863): IBUS-DEBUG: 08:49:53.993: _connection_closed_cb: Underlying GIOStream returned 0 bytes on an async read
[Thread 0x7fffef7fe700 (LWP 10869) exited]

Bold message is displayed when bug occured.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.