Bug 2292913 - [abrt] xwaylandvideobridge: qAbort(): xwaylandvideobridge killed by SIGABRT
Summary: [abrt] xwaylandvideobridge: qAbort(): xwaylandvideobridge killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xwaylandvideobridge
Version: 40
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact:
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:c915f2d9d8454f1817bbaf8afa6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-06-18 15:24 UTC by IceMoss
Modified: 2025-05-20 09:22 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-20 09:22:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: proc_pid_status (1.46 KB, text/plain)
2024-06-18 15:24 UTC, IceMoss
no flags Details
File: maps (3.97 KB, text/plain)
2024-06-18 15:24 UTC, IceMoss
no flags Details
File: limits (1.29 KB, text/plain)
2024-06-18 15:24 UTC, IceMoss
no flags Details
File: environ (2.08 KB, text/plain)
2024-06-18 15:24 UTC, IceMoss
no flags Details
File: open_fds (609 bytes, text/plain)
2024-06-18 15:24 UTC, IceMoss
no flags Details
File: mountinfo (2.76 KB, text/plain)
2024-06-18 15:24 UTC, IceMoss
no flags Details
File: os_info (699 bytes, text/plain)
2024-06-18 15:24 UTC, IceMoss
no flags Details
File: cpuinfo (3.08 KB, text/plain)
2024-06-18 15:24 UTC, IceMoss
no flags Details
File: core_backtrace (8.14 KB, text/plain)
2024-06-18 15:24 UTC, IceMoss
no flags Details
File: dso_list (711 bytes, text/plain)
2024-06-18 15:24 UTC, IceMoss
no flags Details
File: backtrace (61.01 KB, text/plain)
2024-06-18 15:24 UTC, IceMoss
no flags Details

Description IceMoss 2024-06-18 15:24:00 UTC
Description of problem:
appeared on startup

Version-Release number of selected component:
xwaylandvideobridge-0.4.0-5.fc40

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         xwaylandvideobridge killed by SIGABRT
journald_cursor: s=ee09cff5359f4a839c8ab544382ea21b;i=23ef0;b=feaf09f8d40c49cda73b2354f2edbf5d;m=10455c4;t=61b2b9540b9ad;x=6839d00e49159dfe
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.9.4-200.fc40.x86_64
package:        xwaylandvideobridge-0.4.0-5.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: qAbort
comment:        appeared on startup

Truncated backtrace:
Thread no. 1 (11 frames)
 #4 qAbort at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/global/qglobal.cpp:161
 #5 qt_message_fatal<QString&> at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/global/qlogging.cpp:2025
 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/global/qlogging.cpp:374
 #7 QMessageLogger::fatal at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/global/qlogging.cpp:889
 #8 init_platform at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/gui/kernel/qguiapplication.cpp:1285
 #9 QGuiApplicationPrivate::createPlatformIntegration at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/gui/kernel/qguiapplication.cpp:1533
 #10 QGuiApplicationPrivate::createEventDispatcher at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/gui/kernel/qguiapplication.cpp:1552
 #11 QCoreApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:905
 #12 QGuiApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/gui/kernel/qguiapplication.cpp:1580
 #13 QApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/widgets/kernel/qapplication.cpp:472
 #14 QApplication::QApplication at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/widgets/kernel/qapplication.cpp:460

Comment 1 IceMoss 2024-06-18 15:24:03 UTC
Created attachment 2037688 [details]
File: proc_pid_status

Comment 2 IceMoss 2024-06-18 15:24:05 UTC
Created attachment 2037689 [details]
File: maps

Comment 3 IceMoss 2024-06-18 15:24:06 UTC
Created attachment 2037690 [details]
File: limits

Comment 4 IceMoss 2024-06-18 15:24:07 UTC
Created attachment 2037691 [details]
File: environ

Comment 5 IceMoss 2024-06-18 15:24:08 UTC
Created attachment 2037692 [details]
File: open_fds

Comment 6 IceMoss 2024-06-18 15:24:09 UTC
Created attachment 2037693 [details]
File: mountinfo

Comment 7 IceMoss 2024-06-18 15:24:11 UTC
Created attachment 2037694 [details]
File: os_info

Comment 8 IceMoss 2024-06-18 15:24:12 UTC
Created attachment 2037695 [details]
File: cpuinfo

Comment 9 IceMoss 2024-06-18 15:24:13 UTC
Created attachment 2037696 [details]
File: core_backtrace

Comment 10 IceMoss 2024-06-18 15:24:14 UTC
Created attachment 2037697 [details]
File: dso_list

Comment 11 IceMoss 2024-06-18 15:24:16 UTC
Created attachment 2037698 [details]
File: backtrace

Comment 12 mark preston 2024-06-25 13:51:48 UTC
occurs after upgrade from fc38 to fc40


reporter:       libreport-2.17.15
type:           CCpp
reason:         xwaylandvideobridge killed by SIGABRT
journald_cursor: s=c0cf7f348d1f481a8d15d255a31021a7;i=10ccfd0;b=464e2cf6010141eca0aa82407c684c51;m=5e3e415;t=61ba80625f55f;x=c6fec91bb852aaf8
executable:     /usr/bin/xwaylandvideobridge
cmdline:        /usr/bin/xwaylandvideobridge
cgroup:         0::/user.slice/user-1500.slice/user/app.slice/app-org.kde.xwaylandvideobridge
rootdir:        /
uid:            1500
kernel:         6.9.5-200.fc40.x86_64
package:        xwaylandvideobridge-0.4.0-5.fc40
runlevel:       N 5
xsession_errors: 
backtrace_rating: 4
crash_function: qAbort
comment:        occurs after upgrade from fc38 to fc40

Comment 13 marcin.p.kowalewski 2024-08-29 09:45:15 UTC
Problem exists in 90% of bootups. Wayland fails to start, Plasma isn't available, and user if forced to use GNOME. After login checking session type shows X11.


reporter:       libreport-2.17.15
type:           CCpp
reason:         xwaylandvideobridge killed by SIGABRT
journald_cursor: s=00d85ddd4737436190f254cd8c1899da;i=34de78;b=4e21dd3918af44c7a28237f711e0e5a1;m=50b0810;t=61fca3733a2da;x=adda813c32ddd8dc
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.10.4-200.fc40.x86_64
package:        xwaylandvideobridge-0.4.0-5.fc40
runlevel:       unknown
backtrace_rating: 4
crash_function: qAbort
comment:        Problem exists in 90% of bootups. Wayland fails to start, Plasma isn't available, and user if forced to use GNOME. After login checking session type shows X11.

Comment 14 Markus Nicolussi 2024-09-30 11:35:32 UTC
this kind of stuff happens on each login, i do not know why or what's wrong with my system. the only thing i can imagine is that enabling the testing branch of all repositories could be the reason.... or me testing various desktop environments and GUI's has something to do with it. it's the only thing that is different to usual installations i figure. there are many many more error reports from many applications. i submit them in the hope it helps.


reporter:       libreport-2.17.15
backtrace_rating: 4
rootdir:        /
kernel:         6.10.9-200.fc40.x86_64
type:           CCpp
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.xwaylandvideobridge
crash_function: qAbort
cmdline:        /usr/bin/xwaylandvideobridge
package:        xwaylandvideobridge-0.4.0-5.fc40
reason:         xwaylandvideobridge killed by SIGABRT
xsession_errors: 
journald_cursor: s=41854e1aed194a0b8b1f6a5b06500603;i=1d56a6;b=6cee6a7e4b894cb2b55cda64b0d862f8;m=17596aa7;t=6225097fe0da7;x=e5e4aa8e18ba68f3
uid:            1000
comment:        this kind of stuff happens on each login, i do not know why or what's wrong with my system. the only thing i can imagine is that enabling the testing branch of all repositories could be the reason.... or me testing various desktop environments and GUI's has something to do with it. it's the only thing that is different to usual installations i figure. there are many many more error reports from many applications. i submit them in the hope it helps.
executable:     /usr/bin/xwaylandvideobridge
runlevel:       N 5

Comment 15 Hoshyar Karimi 2025-04-17 10:07:08 UTC
I have the same bug. F42-KDE

Comment 16 Aoife Moloney 2025-04-25 11:02:52 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-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 '40'.

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 40 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 17 Aoife Moloney 2025-05-20 09:22:07 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 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.


Note You need to log in before you can comment on or make changes to this bug.