Bug 2361534 - [abrt] plasma-discover-notifier: qAbort(): DiscoverNotifier killed by SIGABRT
Summary: [abrt] plasma-discover-notifier: qAbort(): DiscoverNotifier killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-discover
Version: 42
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:59c7d7f0d07a32aa59fd049ff16...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-21 21:48 UTC by Vilen T
Modified: 2026-06-08 16:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-08 16:57:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: limits (1.29 KB, text/plain)
2025-04-21 21:48 UTC, Vilen T
no flags Details
File: backtrace (64.71 KB, text/plain)
2025-04-21 21:48 UTC, Vilen T
no flags Details
File: open_fds (609 bytes, text/plain)
2025-04-21 21:48 UTC, Vilen T
no flags Details
File: core_backtrace (8.91 KB, text/plain)
2025-04-21 21:48 UTC, Vilen T
no flags Details
File: maps (3.90 KB, text/plain)
2025-04-21 21:48 UTC, Vilen T
no flags Details
File: proc_pid_status (1.48 KB, text/plain)
2025-04-21 21:48 UTC, Vilen T
no flags Details
File: dso_list (896 bytes, text/plain)
2025-04-21 21:48 UTC, Vilen T
no flags Details
File: environ (2.34 KB, text/plain)
2025-04-21 21:48 UTC, Vilen T
no flags Details
File: cpuinfo (3.20 KB, text/plain)
2025-04-21 21:48 UTC, Vilen T
no flags Details
File: mountinfo (2.84 KB, text/plain)
2025-04-21 21:48 UTC, Vilen T
no flags Details
File: os_info (767 bytes, text/plain)
2025-04-21 21:48 UTC, Vilen T
no flags Details

Description Vilen T 2025-04-21 21:48:02 UTC
Description of problem:
Logging in as usual, got crash notification

Version-Release number of selected component:
plasma-discover-notifier-6.3.4-1.fc42

Additional info:
reporter:       libreport-2.17.15
cmdline:        /usr/libexec/DiscoverNotifier --check-delay 20
kernel:         6.14.2-300.fc42.x86_64
journald_cursor: s=c53125e3d04647ac81b05436314e3006;i=31421;b=2092ed34bf994ba2a086e4a6c82e8246;m=182823f;t=633507a7fb7e7;x=eb3c5edd04515e2b
type:           CCpp
executable:     /usr/libexec/DiscoverNotifier
rootdir:        /
crash_function: qAbort
comment:        Logging in as usual, got crash notification
reason:         DiscoverNotifier killed by SIGABRT
backtrace_rating: 4
package:        plasma-discover-notifier-6.3.4-1.fc42
uid:            1000
runlevel:       N 5
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.discover.notifier

Truncated backtrace:
Thread no. 1 (11 frames)
 #4 qAbort at /usr/src/debug/qt6-qtbase-6.8.2-3.fc42.x86_64/src/corelib/global/qassert.cpp:49
 #5 qt_message_fatal<QString&> at /usr/src/debug/qt6-qtbase-6.8.2-3.fc42.x86_64/src/corelib/global/qlogging.cpp:2103
 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc42.x86_64/src/corelib/global/qlogging.cpp:382
 #7 QMessageLogger::fatal at /usr/src/debug/qt6-qtbase-6.8.2-3.fc42.x86_64/src/corelib/global/qlogging.cpp:884
 #8 init_platform at /usr/src/debug/qt6-qtbase-6.8.2-3.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1327
 #9 QGuiApplicationPrivate::createPlatformIntegration at /usr/src/debug/qt6-qtbase-6.8.2-3.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1580
 #10 QGuiApplicationPrivate::createEventDispatcher at /usr/src/debug/qt6-qtbase-6.8.2-3.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1599
 #11 QCoreApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.8.2-3.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:931
 #12 QGuiApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.8.2-3.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1627
 #13 QApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.8.2-3.fc42.x86_64/src/widgets/kernel/qapplication.cpp:474
 #14 QApplication::QApplication at /usr/src/debug/qt6-qtbase-6.8.2-3.fc42.x86_64/src/widgets/kernel/qapplication.cpp:462

Comment 1 Vilen T 2025-04-21 21:48:06 UTC
Created attachment 2086266 [details]
File: limits

Comment 2 Vilen T 2025-04-21 21:48:07 UTC
Created attachment 2086267 [details]
File: backtrace

Comment 3 Vilen T 2025-04-21 21:48:09 UTC
Created attachment 2086268 [details]
File: open_fds

Comment 4 Vilen T 2025-04-21 21:48:10 UTC
Created attachment 2086269 [details]
File: core_backtrace

Comment 5 Vilen T 2025-04-21 21:48:12 UTC
Created attachment 2086270 [details]
File: maps

Comment 6 Vilen T 2025-04-21 21:48:13 UTC
Created attachment 2086271 [details]
File: proc_pid_status

Comment 7 Vilen T 2025-04-21 21:48:15 UTC
Created attachment 2086272 [details]
File: dso_list

Comment 8 Vilen T 2025-04-21 21:48:16 UTC
Created attachment 2086273 [details]
File: environ

Comment 9 Vilen T 2025-04-21 21:48:18 UTC
Created attachment 2086274 [details]
File: cpuinfo

Comment 10 Vilen T 2025-04-21 21:48:19 UTC
Created attachment 2086275 [details]
File: mountinfo

Comment 11 Vilen T 2025-04-21 21:48:21 UTC
Created attachment 2086276 [details]
File: os_info

Comment 12 Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-07-08 17:25:49 UTC
Per https://bugzilla.redhat.com/show_bug.cgi?id=2378661#c0, I invoked this application from an SSH client on postmarketOS. The cause of the problem appears to be that $DISPLAY is unset. It solely appears to affect Qt-based applications (not merely KDE Frameworks-based ones). However, it doesn't affect all, for VLC copes fine. (Likewise, the GTK3-based Chromium and Inkscape cope.)


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasma-discover killed by SIGABRT
journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=864bd4;b=9a2a7e1fe91e4e5bb9e946b734c27a2b;m=1ed970160;t=6396dc7b1afe8;x=7cd3aeb8161af03f
executable:     /usr/bin/plasma-discover
cmdline:        plasma-discover
cgroup:         0::/user.slice/user-1000.slice/session-4.scope
rootdir:        /
uid:            1000
kernel:         6.15.4-200.fc42.x86_64
package:        plasma-discover-6.4.2-1.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: qAbort
comment:        Per https://bugzilla.redhat.com/show_bug.cgi?id=2378661#c0, I invoked this application from an SSH client on postmarketOS. The cause of the problem appears to be that $DISPLAY is unset. It solely appears to affect Qt-based applications (not merely KDE Frameworks-based ones). However, it doesn't affect all, for VLC copes fine. (Likewise, the GTK3-based Chromium and Inkscape cope.)

Comment 13 Fedora Release Engineering 2026-05-06 12:41:30 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 14 Aoife Moloney 2026-06-08 16:57:13 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.


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