Description of problem: Like [`id=2366277`][2]: : Per [`wiki.gentoo.org/wiki/GPU_passthrough_with_virt-manager,_QEMU,_and_KVM#Windows`][1], I added the undermentioned to my `PRETTY_NAME="Fedora Linux 42 (KDE Plasma Desktop Edition)"` VM in `virt-manager-5.0.0-2.fc42.noarch` in order to gain GPU passthrough. Instead, I lost my display output: > ~~~XML > <hostdev mode="subsystem" type="pci" managed="yes"> > <source> > <address domain="0x0000" bus="0x03" slot="0x00" function="0x0"/> > </source> > <address type="pci" domain="0x0000" bus="0x07" slot="0x00" function="0x0"/> > </hostdev> > ~~~ Consequently, I SSH'd via my smartphone into the superuser account, and initiated a `shutdown`. This appeared to hang, for after a few minutes, it hadn't completed, but I couldn't SSH anymore (because it was, presumably, in the shutdown log). Consequently, I hit the MB's RESET_SW. After an update that was scheduled for that reboot, GNOME Abrt appeared at login with this report. [1]: https://wiki.gentoo.org/index.php?title=GPU_passthrough_with_virt-manager,_QEMU,_and_KVM&oldid=1388212#Windows:~:text=Edit%20the%20VM%20in%20virt%2Dmanager,Attempt%20to%20boot%20the%20VM [2]: https://bugzilla.redhat.com/show_bug.cgi?id=2366277#c0:~:text=2025%2D05%2D14%2017:15:36%20UTC-,Description%20of%20problem:,-Per%20https://wiki.gentoo.org/index.php?title=GPU_passthrough_with_virt%2Dmanager%2C_QEMU%2C_and_KVM%26oldid=1388212%23Windows:~:text=Edit%2520the%2520VM%2520in%2520virt%252Dmanager%2CAttempt%2520to%2520boot%2520the%2520VM%2C%20I Version-Release number of selected component: maliit-keyboard-2.3.1-10.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: maliit-keyboard killed by SIGSEGV journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=4ace06;b=7e481e280690489a81a327c51e9b0665;m=432dc86df;t=6351b77a533f3;x=2a18a994a682209b executable: /usr/bin/maliit-keyboard cmdline: /usr/bin/maliit-keyboard cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-kwin_wayland.service rootdir: / uid: 1000 kernel: 6.14.5-300.fc42.x86_64 package: maliit-keyboard-2.3.1-10.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: QtWaylandClient::QWaylandInputPanelSurface::applyConfigure Truncated backtrace: Thread no. 1 (9 frames) #0 QtWaylandClient::QWaylandInputPanelSurface::applyConfigure at /usr/src/debug/maliit-framework-2.3.0-9.fc42.x86_64/src/qt/plugins/shellintegration/qwaylandinputpanelsurface.cpp:39 #1 QtWaylandClient::QWaylandWindow::doApplyConfigure at /usr/src/debug/qt5-qtwayland-5.15.16-2.fc42.x86_64/src/client/qwaylandwindow.cpp:508 #3 QtWaylandClient::QWaylandWindow::setCanResize at /usr/src/debug/qt5-qtwayland-5.15.16-2.fc42.x86_64/src/client/qwaylandwindow.cpp:523 #4 QSGRenderThread::syncAndRender at scenegraph/qsgthreadedrenderloop.cpp:878 #5 QSGRenderThread::run at scenegraph/qsgthreadedrenderloop.cpp:1051 #6 operator() at thread/qthread_unix.cpp:350 #7 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > at thread/qthread_unix.cpp:287 #8 QThreadPrivate::start at thread/qthread_unix.cpp:310 #10 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Potential duplicate: bug 2277575
Created attachment 2089828 [details] File: proc_pid_status
Created attachment 2089829 [details] File: maps
Created attachment 2089830 [details] File: limits
Created attachment 2089831 [details] File: environ
Created attachment 2089832 [details] File: open_fds
Created attachment 2089833 [details] File: mountinfo
Created attachment 2089834 [details] File: os_info
Created attachment 2089835 [details] File: cpuinfo
Created attachment 2089836 [details] File: core_backtrace
Created attachment 2089837 [details] File: exploitable
Created attachment 2089838 [details] File: dso_list
Created attachment 2089839 [details] File: var_log_messages
Created attachment 2089840 [details] File: backtrace
Mon ordinateur était en veille dans mon sac. Quand je l'ai ouvert, j'ai reçu un avis disant qu'il y a eu une erreur à signaler. reporter: libreport-2.17.15 type: CCpp reason: maliit-keyboard killed by SIGSEGV journald_cursor: s=ad631e7c222f485383d5df33c07935f9;i=3f813a;b=9750eb76479c41aabe96f06ec7c2902c;m=60505122;t=636b6f85cc6c9;x=f159aea252d4df64 executable: /usr/bin/maliit-keyboard cmdline: /usr/bin/maliit-keyboard cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-kwin_wayland.service rootdir: / uid: 1000 kernel: 6.14.9-300.fc42.x86_64 package: maliit-keyboard-2.3.1-10.fc42 runlevel: N 5 dso_list: /usr/bin/maliit-keyboard maliit-keyboard-2.3.1-10.fc42.x86_64 (Fedora Project) 1744847184 backtrace_rating: 4 crash_function: QtWaylandClient::QWaylandInputPanelSurface::applyConfigure comment: Mon ordinateur était en veille dans mon sac. Quand je l'ai ouvert, j'ai reçu un avis disant qu'il y a eu une erreur à signaler.
(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #0) Similar: 1. https://bugzilla.redhat.com/show_bug.cgi?id=2366278#c0 2. https://bugzilla.redhat.com/show_bug.cgi?id=2406401#c0 3. https://bugzilla.redhat.com/show_bug.cgi?id=2373827#c0 --- (In reply to Émile Brunelle from comment #14) > comment: Mon ordinateur était en veille dans mon sac. Quand je l'ai > ouvert, j'ai reçu un avis disant qu'il y a eu une erreur à signaler. That appears to be an example of https://github.com/abrt/gnome-abrt/issues/394#issue-3702703506.
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. 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 '42'. 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 42 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.
*** This bug has been marked as a duplicate of bug 2366278 ***