Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1939811

Summary: [abrt] kf5-kglobalaccel: qt_message_fatal(): kglobalaccel5 killed by SIGABRT
Product: [Fedora] Fedora Reporter: ByteEnable
Component: kf5-kglobalaccelAssignee: Daniel Vrátil <me>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: bdm, jeremy.linton, jgrulich, kde-sig, me, rdieter, santosh, than
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/97c932ae5c01b70ceeb565e79e9254c4d340eb3e
Whiteboard: abrt_hash:76d31904d5f535cae93a37ac65fd8540003bad58;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 245418    
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description ByteEnable 2021-03-17 05:44:20 UTC 
Description of problem:
Attempting to login via Xvnc and xrdp.

Version-Release number of selected component:
kf5-kglobalaccel-5.80.0-1.fc34

Additional info:
reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/background.slice/plasma-kglobalaccel.service
cmdline:        /usr/bin/kglobalaccel5
crash_function: qt_message_fatal
executable:     /usr/bin/kglobalaccel5
journald_cursor: s=5bc1dce5580c4202ad83e8a5ce173a7e;i=da84;b=bf3fb6b55697428c9ef337a1156e8e57;m=767cc797c;t=5bdb49713a213;x=2e19444df44b90a8
kernel:         5.11.6-300.fc34.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (8 frames)
 #2 qt_message_fatal at global/qlogging.cpp:1914
 #3 QMessageLogger::fatal at global/qlogging.cpp:893
 #4 init_platform at kernel/qguiapplication.cpp:1254
 #5 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1474
 #6 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1491
 #7 QCoreApplicationPrivate::init at kernel/qcoreapplication.cpp:834
 #8 QGuiApplicationPrivate::init at kernel/qguiapplication.cpp:1520
 #9 QGuiApplication::QGuiApplication at kernel/qguiapplication.h:203

Potential duplicate: bug 1720830
Comment 1 ByteEnable 2021-03-17 05:44:23 UTC 
Created attachment 1763890 [details]
File: backtrace
Comment 2 ByteEnable 2021-03-17 05:44:24 UTC 
Created attachment 1763891 [details]
File: core_backtrace
Comment 3 ByteEnable 2021-03-17 05:44:25 UTC 
Created attachment 1763892 [details]
File: cpuinfo
Comment 4 ByteEnable 2021-03-17 05:44:26 UTC 
Created attachment 1763893 [details]
File: dso_list
Comment 5 ByteEnable 2021-03-17 05:44:27 UTC 
Created attachment 1763894 [details]
File: environ
Comment 6 ByteEnable 2021-03-17 05:44:28 UTC 
Created attachment 1763895 [details]
File: limits
Comment 7 ByteEnable 2021-03-17 05:44:29 UTC 
Created attachment 1763896 [details]
File: maps
Comment 8 ByteEnable 2021-03-17 05:44:30 UTC 
Created attachment 1763897 [details]
File: mountinfo
Comment 9 ByteEnable 2021-03-17 05:44:31 UTC 
Created attachment 1763898 [details]
File: open_fds
Comment 10 ByteEnable 2021-03-17 05:44:33 UTC 
Created attachment 1763899 [details]
File: proc_pid_status
Comment 11 ByteEnable 2021-03-17 05:44:33 UTC 
Created attachment 1763900 [details]
File: var_log_messages
Comment 12 Jeremy Linton 2021-04-23 03:50:00 UTC 
Similar problem has been detected:

I was just logging in/out of KDE from gdm after having issues with SDDM.

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-0.slice/user/background.slice/plasma-kglobalaccel.service
cmdline:        /usr/bin/kglobalaccel5
crash_function: qt_message_fatal
executable:     /usr/bin/kglobalaccel5
journald_cursor: s=0cb72eb5aaf24c48942709dbd79110d8;i=ba8;b=bea4ae4acfac480f81b0aabcb47f19c4;m=a523fbd;t=5c09b279b3987;x=7bce158160bfc423
kernel:         5.11.12-300.fc34.aarch64
package:        kf5-kglobalaccel-5.80.0-1.fc34
reason:         kglobalaccel5 killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0
Comment 13 Jeremy Linton 2021-04-23 03:51:39 UTC 
This is just the F34 kde spin on a RPI4 running the PFTF UEFI firmware after switching from sddm->gdm after having issues with sddm.
Comment 14 santosh 2021-04-29 00:30:40 UTC 
*** Bug 1954877 has been marked as a duplicate of this bug. ***
Comment 15 Brian Morrison 2021-07-08 15:07:27 UTC 
Similar problem has been detected:

Log in to GNOME Wayland session, no other action, crash as soon as desktop appears

reporter:       libreport-2.15.2
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/background.slice/plasma-kglobalaccel.service
cmdline:        /usr/bin/kglobalaccel5
crash_function: qt_message_fatal
executable:     /usr/bin/kglobalaccel5
journald_cursor: s=eecc4eda4d99458a9674d8d0315d2275;i=150ed2;b=0b0521e3b8d24b388c619918c7de06a2;m=c01874da2;t=5c69cd96e3740;x=c1dd766f504a6ad0
kernel:         5.12.15-300.fc34.x86_64
package:        kf5-kglobalaccel-5.83.0-1.fc34
reason:         kglobalaccel5 killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000