SUMMARY After updating to Plasma 6.3 Beta and Qt 6.9.0 Beta 1, Inkscape fails to start with the following error: (org.inkscape.Inkscape:139074): Gdk-WARNING **: 11:24:08.323: Native Windows taller than 65535 pixels are not supported (org.inkscape.Inkscape:139074): Gdk-CRITICAL **: 11:24:08.357: ../gtk/gdk/wayland/gdkdisplay-wayland.c:1353: Truncating shared memory file failed: Invalid argument (org.inkscape.Inkscape:139074): Gdk-WARNING **: 11:24:08.365: Native Windows taller than 65535 pixels are not supported (org.inkscape.Inkscape:139074): Gdk-CRITICAL **: 11:24:08.369: ../gtk/gdk/wayland/gdkdisplay-wayland.c:1433: Unable to create Cairo image surface: invalid value (typically too big) for the size of the input (surface, pattern, etc.) [1] 139074 segmentation fault (core dumped) inkscape I attach the full backtrace. I don't think is an Inkscape bug since it was working just fine with Plasma 6.2 and Qt 6.8. Also, it looks like it crashes because a wrong window size is given. STEPS TO REPRODUCE 1. Update to Plasma 6.3 and Qt 6.9 2. Try to start Inkscape OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.90 KDE Frameworks Version: 6.10.0 Qt Version: 6.9.0 Kernel Version: 6.12.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 22 × Intel® Core™ Ultra 7 155H Memory: 30.9 GiB of RAM Graphics Processor: Intel® Arc Manufacturer: LENOVO Product Name: 21KDS00600 System Version: ThinkPad X1 Carbon Gen 12 ADDITIONAL INFORMATION I'm using a scale of 125%, but exactly same issue happens with 100%.
Created attachment 177316 [details] Backtrace Inkscape crash
Inkscape crashes, but all Gnome apps do not work correctly either. I have tried Gimp and Gnome Console.
Fastest way to reproduce the issue: STEPS TO REPRODUCE 1. Open System Settings -> Colors & Themes -> Application Style -> Configure GNOME/GTK Application Style 2. Click on Preview
If anyone ends up here. This was the actual bug affecting me: https://gitlab.archlinux.org/archlinux/packaging/packages/pango/-/issues/1 Solution was cleaning font cache with: fc-cache -f -v