Description of problem: I pressed Ctrl+Shift+V on my keyboard. This is now crashing Geany reliably, no matter what's in my clipboard. I don't think I have this set to a custom keyboard shortcut in GNOME. Version-Release number of selected component: geany-1.37.1-2.fc34 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-geany-307818.scope cmdline: geany crash_function: std::__replacement_assert executable: /usr/bin/geany journald_cursor: s=1d7e65438ec54e97af516e95edacf0b4;i=51d0c1;b=ffac6a63afe54977a693535745344d3b;m=6b03d55d2;t=5c23bd9a71db6;x=18484586943281f0 kernel: 5.11.18-300.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1795541 [details] File: backtrace
Created attachment 1795542 [details] File: core_backtrace
Created attachment 1795543 [details] File: cpuinfo
Created attachment 1795544 [details] File: dso_list
Created attachment 1795545 [details] File: environ
Created attachment 1795546 [details] File: limits
Created attachment 1795547 [details] File: maps
Created attachment 1795548 [details] File: mountinfo
Created attachment 1795549 [details] File: open_fds
Created attachment 1795550 [details] File: proc_pid_status
Related issue of geany: https://github.com/geany/geany/issues/2813 This bug comes from vte, and https://gitlab.gnome.org/GNOME/vte/-/commit/0136048d32d29412de3381828bb21f05563c799f is the first bad commit.
*** Bug 1984399 has been marked as a duplicate of this bug. ***
From the post before: Geany crashes when I press "Ctrl + Shift + V" https://github.com/geany/geany/issues/2813
*** Bug 1989854 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.