Bug 2224700

Summary: [abrt] kf5-kded: qt_message_fatal(): kded5 killed by SIGABRT
Product: [Fedora] Fedora Reporter: golgafrincham
Component: kf5-kdedAssignee: KDE SIG <kde-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: golgafrincham, jgrulich, kde-sig, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/71b5851f56efe9526ad9b02b43705d4de514db4
Whiteboard: abrt_hash:d4e5a9b977e6d5f7601ab144c9791e0042d3bfce;VARIANT_ID=kde;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-28 13:34:13 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: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: dso_list
none
File: var_log_messages
none
File: backtrace
none
File: environ none

Description golgafrincham 2023-07-22 07:51:31 UTC 
Description of problem:
After an system upgrade and reboot, this error occured first thing after logging in.

Version-Release number of selected component:
kf5-kded-5.107.0-1.fc38

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         kded5 killed by SIGABRT
journald_cursor: s=b0448b7036be4e09a3e844fd33a8ec29;i=187056;b=8dec7aad72b5400689fdd679bd69d15e;m=33bdb1e1;t=6010df8a20447;x=d548693389927571
executable:     /usr/bin/kded5
cmdline:        /usr/bin/kded5
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.kde.kcookiejar5
rootdir:        /
uid:            1000
kernel:         6.3.12-200.fc38.x86_64
package:        kf5-kded-5.107.0-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: qt_message_fatal
comment:        After an system upgrade and reboot, this error occured first thing after logging in.

Truncated backtrace:
Thread no. 1 (9 frames)
 #4 qt_message_fatal at global/qlogging.cpp:1914
 #5 QMessageLogger::fatal at global/qlogging.cpp:893
 #6 init_platform at kernel/qguiapplication.cpp:1254
 #7 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1477
 #8 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1494
 #9 QCoreApplicationPrivate::init at kernel/qcoreapplication.cpp:835
 #10 QGuiApplicationPrivate::init at kernel/qguiapplication.cpp:1523
 #11 QApplicationPrivate::init at kernel/qapplication.cpp:513
 #12 QApplication::QApplication at kernel/qapplication.cpp:501


Potential duplicate: bug 1619376
Comment 1 golgafrincham 2023-07-22 07:51:34 UTC 
Created attachment 1977016 [details]
File: proc_pid_status
Comment 2 golgafrincham 2023-07-22 07:51:36 UTC 
Created attachment 1977017 [details]
File: maps
Comment 3 golgafrincham 2023-07-22 07:51:37 UTC 
Created attachment 1977018 [details]
File: limits
Comment 4 golgafrincham 2023-07-22 07:51:39 UTC 
Created attachment 1977019 [details]
File: open_fds
Comment 5 golgafrincham 2023-07-22 07:51:40 UTC 
Created attachment 1977020 [details]
File: mountinfo
Comment 6 golgafrincham 2023-07-22 07:51:42 UTC 
Created attachment 1977021 [details]
File: os_info
Comment 7 golgafrincham 2023-07-22 07:51:43 UTC 
Created attachment 1977022 [details]
File: cpuinfo
Comment 8 golgafrincham 2023-07-22 07:51:44 UTC 
Created attachment 1977023 [details]
File: core_backtrace
Comment 9 golgafrincham 2023-07-22 07:51:45 UTC 
Created attachment 1977024 [details]
File: dso_list
Comment 10 golgafrincham 2023-07-22 07:51:47 UTC 
Created attachment 1977025 [details]
File: var_log_messages
Comment 11 golgafrincham 2023-07-22 07:51:48 UTC 
Created attachment 1977026 [details]
File: backtrace
Comment 12 golgafrincham 2023-07-22 07:51:50 UTC 
Created attachment 1977027 [details]
File: environ
Comment 13 Aoife Moloney 2024-05-28 13:34:13 UTC 
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

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