Bug 2361988

Summary: [abrt] xwaylandvideobridge: qAbort(): xwaylandvideobridge killed by SIGABRT
Product: [Fedora] Fedora Reporter: Hoshyar Karimi <baxooshi>
Component: xwaylandvideobridgeAssignee: Neal Gompa <ngompa13>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 42CC: 8ru2u4gz, baxooshi, kde-sig, ngompa13, obipoketbobo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c915f2d9d8454f1817bbaf8afa6e87c4ed87254a;VARIANT_ID=kde;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-06-08 16:58:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: dso_list
none
File: backtrace none

Description Hoshyar Karimi 2025-04-24 05:45:52 UTC
Description of problem:
every time I log into my account it happens

Version-Release number of selected component:
xwaylandvideobridge-0.4.0-9.fc42

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         xwaylandvideobridge killed by SIGABRT
journald_cursor: s=05611db71e274fbdab25847d1e93a797;i=1008e;b=cc66c7f3f9d24b2e8fdff3c57e91ab58;m=2ae82cf;t=6337f99bd27c3;x=e179bbdd7b4abc2c
executable:     /usr/bin/xwaylandvideobridge
cmdline:        /usr/bin/xwaylandvideobridge
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.xwaylandvideobridge
rootdir:        /
uid:            1000
kernel:         6.14.2-300.fc42.x86_64
package:        xwaylandvideobridge-0.4.0-9.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: qAbort
comment:        every time I log into my account it happens

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 qAbort at /usr/src/debug/qt6-qtbase-6.9.0-1.fc42.x86_64/src/corelib/global/qassert.cpp:46
 #5 qt_message_fatal<QString&> at /usr/src/debug/qt6-qtbase-6.9.0-1.fc42.x86_64/src/corelib/global/qlogging.cpp:2122
 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) at /usr/src/debug/qt6-qtbase-6.9.0-1.fc42.x86_64/src/corelib/global/qlogging.cpp:381
 #7 QMessageLogger::fatal at /usr/src/debug/qt6-qtbase-6.9.0-1.fc42.x86_64/src/corelib/global/qlogging.cpp:883
 #8 init_platform at /usr/src/debug/qt6-qtbase-6.9.0-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1345
 #9 QGuiApplicationPrivate::createPlatformIntegration at /usr/src/debug/qt6-qtbase-6.9.0-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1598
 #10 QGuiApplicationPrivate::createEventDispatcher at /usr/src/debug/qt6-qtbase-6.9.0-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1617
 #11 QCoreApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.9.0-1.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:866
 #12 QGuiApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.9.0-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1645
 #13 QApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.9.0-1.fc42.x86_64/src/widgets/kernel/qapplication.cpp:474


Potential duplicate: bug 2292913

Comment 1 Hoshyar Karimi 2025-04-24 05:45:55 UTC
Created attachment 2086838 [details]
File: proc_pid_status

Comment 2 Hoshyar Karimi 2025-04-24 05:45:57 UTC
Created attachment 2086839 [details]
File: maps

Comment 3 Hoshyar Karimi 2025-04-24 05:45:58 UTC
Created attachment 2086840 [details]
File: limits

Comment 4 Hoshyar Karimi 2025-04-24 05:46:01 UTC
Created attachment 2086841 [details]
File: environ

Comment 5 Hoshyar Karimi 2025-04-24 05:46:03 UTC
Created attachment 2086842 [details]
File: open_fds

Comment 6 Hoshyar Karimi 2025-04-24 05:46:06 UTC
Created attachment 2086843 [details]
File: mountinfo

Comment 7 Hoshyar Karimi 2025-04-24 05:46:08 UTC
Created attachment 2086844 [details]
File: os_info

Comment 8 Hoshyar Karimi 2025-04-24 05:46:10 UTC
Created attachment 2086845 [details]
File: cpuinfo

Comment 9 Hoshyar Karimi 2025-04-24 05:46:13 UTC
Created attachment 2086846 [details]
File: core_backtrace

Comment 10 Hoshyar Karimi 2025-04-24 05:46:15 UTC
Created attachment 2086847 [details]
File: dso_list

Comment 11 Hoshyar Karimi 2025-04-24 05:46:17 UTC
Created attachment 2086848 [details]
File: backtrace

Comment 12 Mr Beedell, Roke Julian Lockhart 2025-06-24 13:29:28 UTC
Like https://bugzilla.redhat.com/show_bug.cgi?id=2374575#c0 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed.


reporter:       libreport-2.17.15
type:           CCpp
reason:         xwaylandvideobridge killed by SIGABRT
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=75285b;b=e1bb6ff6b37548a6950c299e12a68ac0;m=4ef26cc;t=63850e97382af;x=6fba81609735e94f
executable:     /usr/bin/xwaylandvideobridge
cmdline:        /usr/bin/xwaylandvideobridge
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.xwaylandvideobridge
rootdir:        /
uid:            1000
kernel:         6.15.3-200.fc42.x86_64
package:        xwaylandvideobridge-0.4.0-9.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: qAbort
comment:        Like https://bugzilla.redhat.com/show_bug.cgi?id=2374575#c0 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed.

Comment 13 Nala R 2025-09-03 18:00:51 UTC
temporarily fixed by creating symlink libxcb-cursor.so to libxcb-cursor.so.0 in both /lib/ and /lib64/

sudo ln -s /usr/lib64/libxcb-cursor.so.0 /usr/lib64/libxcb-cursor.so
sudo ln -s /usr/lib/libxcb-cursor.so.0 /usr/lib/libxcb-cursor.so

could be permanently fixed if xwvb is told to look for libxcb-cursor.so.0

Comment 14 catenaenki 2025-10-22 15:04:40 UTC
I'm running Fedora 42 with KDE. It happens every time I boot up, right after the loading screen â or maybe when I shut down the PC. Strangely, everything still works fine.


reporter:       libreport-2.17.15
type:           CCpp
reason:         xwaylandvideobridge killed by SIGABRT
journald_cursor: s=452ef21a0d7240c98b43dd428719b22b;i=cca73;b=1e301bf1630b4930ad374cb26979d35a;m=19b27c2;t=641c06916314c;x=a6d5d7c614f839bf
executable:     /usr/bin/xwaylandvideobridge
cmdline:        /usr/bin/xwaylandvideobridge
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.xwaylandvideobridge
rootdir:        /
uid:            1000
kernel:         6.17.4-200.fc42.x86_64
package:        xwaylandvideobridge-0.4.0-9.fc42
runlevel:       N 5
comment:        I'm running Fedora 42 with KDE. It happens every time I boot up, right after the loading screen â or maybe when I shut down the PC. Strangely, everything still works fine.
backtrace_rating: 4
crash_function: qAbort

Comment 15 Fedora Release Engineering 2026-05-06 12:43:15 UTC
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.

Comment 16 Mr Beedell, Roke Julian Lockhart 2026-05-08 22:44:04 UTC
If https://bugzilla.redhat.com/show_bug.cgi?id=2361988#c13 remains applicable, this should remain open (and let's file a PR!). Otherwise, considering that this hasn't reproduced for some time, better to mark it as WORKSFORME than EOL?

Comment 17 Aoife Moloney 2026-06-08 16:58:37 UTC
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 18 Red Hat Bugzilla 2026-10-07 04:25:42 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days or the product is inactive and locked