when using inkscape, as soon I copy any object, inkscape will crash. I don't think it's an upstream bug, rather I think is something related to /gdk/wayland/gdkwindow-wayland.c (see attached GDB trace) plasma-desktop-6.3.0-1.fc41.x86_64 qt 6.8.2 gtk4-4.16.5-2.fc41.x86_64 Reproducible: Always
Created attachment 2076459 [details] gdb trace
It's certainly not an Inkscape bug, since I can't reproduce it in GNOME. I'm just not sure what the correct component is.
Created attachment 2076502 [details] list of packages updated by dnf update 1) I found out that Plasma update from 6.2.5 to 6.3.0 triggered the problem. I am writing a message in fedora-kde development mailing list too. Attached the list of updated packages that triggered the crash. 2) in fedora-devel matrix chat, Daniel Berrangé said "it is dieing in SIGPIPE. Generally libraries should not mess with signal handlers, instead they should leave it up to the application to define signal policy. Setting SIGPIPE to be ignored is something inkscape should probably do, so that GDK gets the opportunity to see the i/o error and handle it gracefully". I am reported this upstream at https://gitlab.com/inkscape/ux/-/issues/303
Thanks, looks like they moved it. https://gitlab.com/inkscape/inbox/-/issues/11724
This message is a reminder that Fedora Linux 41 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15. 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 '41'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 41 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.