Bug 1882900

Summary: [abrt] plasma-workspace: qt_message_fatal(): plasmashell killed by SIGABRT
Product: [Fedora] Fedora Reporter: Clemens Eisserer <linuxhippy>
Component: plasma-workspaceAssignee: KDE SIG <kde-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: hlovdal, jgrulich, kde-sig, me, oliver, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fcea74fa4247e2737caf1e06a54f73f54e8aa7b6
Whiteboard: abrt_hash:13f5a87e9544503860e06b014d8c84b33bcf223e;VARIANT_ID=kde;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 16:47:49 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: 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 Clemens Eisserer 2020-09-26 11:09:30 UTC
Description of problem:
crashed while logging out & in again

Version-Release number of selected component:
plasma-workspace-5.18.5-2.fc32

Additional info:
reporter:       libreport-2.13.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-1.scope
cmdline:        /usr/bin/plasmashell
crash_function: qt_message_fatal
executable:     /usr/bin/plasmashell
journald_cursor: s=e2705a46cc0b414aadc1f0478aa7e8dd;i=e7ea;b=2ff9f34dd34c4326bb2da8669abedf94;m=16ca1b56;t=5b0353dda7622;x=e3c35c4629362dc6
kernel:         5.8.10-200.fc32.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 ../../include/QtCore/../../src/corelib/tools/qarraydata.h:208
 #5 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1469
 #6 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1486
 #7 QCoreApplicationPrivate::init at kernel/qcoreapplication.cpp:866
 #8 QGuiApplicationPrivate::init at kernel/qguiapplication.cpp:1515
 #9 QApplicationPrivate::init at kernel/qapplication.cpp:539

Potential duplicate: bug 1751182

Comment 1 Clemens Eisserer 2020-09-26 11:09:37 UTC
Created attachment 1716795 [details]
File: backtrace

Comment 2 Clemens Eisserer 2020-09-26 11:09:39 UTC
Created attachment 1716796 [details]
File: core_backtrace

Comment 3 Clemens Eisserer 2020-09-26 11:09:42 UTC
Created attachment 1716797 [details]
File: cpuinfo

Comment 4 Clemens Eisserer 2020-09-26 11:09:45 UTC
Created attachment 1716798 [details]
File: dso_list

Comment 5 Clemens Eisserer 2020-09-26 11:09:48 UTC
Created attachment 1716799 [details]
File: environ

Comment 6 Clemens Eisserer 2020-09-26 11:09:50 UTC
Created attachment 1716800 [details]
File: limits

Comment 7 Clemens Eisserer 2020-09-26 11:09:56 UTC
Created attachment 1716801 [details]
File: maps

Comment 8 Clemens Eisserer 2020-09-26 11:09:58 UTC
Created attachment 1716802 [details]
File: mountinfo

Comment 9 Clemens Eisserer 2020-09-26 11:10:00 UTC
Created attachment 1716803 [details]
File: open_fds

Comment 10 Clemens Eisserer 2020-09-26 11:10:01 UTC
Created attachment 1716804 [details]
File: proc_pid_status

Comment 11 Clemens Eisserer 2020-09-26 11:10:03 UTC
Created attachment 1716805 [details]
File: var_log_messages

Comment 12 Håkon Løvdal 2020-10-20 21:44:17 UTC
Similar problem has been detected:

Background story: "Maximum number of xclients" or some similar message came when trying to start vlc. This resource preassure is mainly triggered by running several docker instances with firefox running inside of them; closing several tabs/windows will eventyally get things "back to normal". As a workaround to closing tabs I switched to a virtual console, logged in as a different user, ran startx and played the video.

After playing the video I pressed Alt-F1 to switch back to the original X session, and at that point there was some "blink" and this automatic crash report occurred.

reporter:       libreport-2.13.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-5000.slice/session-8.scope
cmdline:        /usr/bin/kcminit mouse
crash_function: qt_message_fatal
executable:     /usr/bin/kcminit
journald_cursor: s=ee115a52bae946bdbce6154080f01d55;i=6dfbfbd;b=de0089d5fc844ec29168df94f550a410;m=4b640578567;t=5b21fa7cf6f39;x=b60f3a91ef65ce1
kernel:         5.7.15-200.fc32.x86_64
package:        plasma-workspace-5.18.5-2.fc32
reason:         kcminit killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            5000
xsession_errors:

Comment 13 Håkon Løvdal 2020-10-20 21:54:41 UTC
Example error message from vlc which spews out the following error messages endlessly until it eventually gets terminated by Ctrl-C.

...
[h264 @ 0x7fe620c3f6c0] get_buffer() failed
[h264 @ 0x7fe620c3f6c0] thread_get_buffer() failed
[h264 @ 0x7fe620c3f6c0] decode_slice_header error
[h264 @ 0x7fe620c3f6c0] no frame!
^C^C^C^CMaximum number of clients reachedMaximum number of clients reachedMaximum number of clients reached[0000556dbcb89b20] xcb vout display error: cannot connect to X server (default)
Maximum number of clients reached[0000556dbcb89b20] xcb vout display error: cannot connect to X server (default)
[00007fe61c04ad80] main video output error: video output creation failed
[00007fe620c18110] main decoder error: failed to create video output
[h264 @ 0x7fe620c55680] get_buffer() failed
[h264 @ 0x7fe620c55680] thread_get_buffer() failed
[h264 @ 0x7fe620c55680] decode_slice_header error
[h264 @ 0x7fe620c55680] no frame!
^C^C^C^C^CMaximum number of clients reachedMaximum number of clients reachedMaximum number of clients reached[00007fe620ccebb0] xcb vout display error: cannot connect to X server (default)
Maximum number of clients reached[00007fe620ccebb0] xcb vout display error: cannot connect to X server (default)
[00007fe64408ce00] main video output error: video output creation failed
[00007fe620c18110] main decoder error: failed to create video output
[h264 @ 0x7fe620c2e580] get_buffer() failed
[h264 @ 0x7fe620c2e580] thread_get_buffer() failed
[h264 @ 0x7fe620c2e580] decode_slice_header error
[h264 @ 0x7fe620c2e580] no frame!
^C^C^C^CMaximum number of clients reachedMaximum number of clients reachedMaximum number of clients reached[00007fe61c0ea240] xcb vout display error: cannot connect to X server (default)
Maximum number of clients reached[00007fe61c0ea240] xcb vout display error: cannot connect to X server (default)
[00007fe62406b180] main video output error: video output creation failed
[00007fe620c18110] main decoder error: failed to create video output
[h264 @ 0x7fe620c3f6c0] get_buffer() failed
[h264 @ 0x7fe620c3f6c0] thread_get_buffer() failed
[h264 @ 0x7fe620c3f6c0] decode_slice_header error
[h264 @ 0x7fe620c3f6c0] no frame!
^C^C^C^CMaximum number of clients reachedMaximum number of clients reachedMaximum number of clients reached[00007fe6280535d0] xcb vout display error: cannot connect to X server (default)
Maximum number of clients reached[00007fe6280535d0] xcb vout display error: cannot connect to X server (default)
[00007fe61c096040] main video output error: video output creation failed
^C[00007fe620c18110] main decoder error: failed to create video output
[h264 @ 0x7fe620c55680] get_buffer() failed
[h264 @ 0x7fe620c55680] thread_get_buffer() failed
[h264 @ 0x7fe620c55680] decode_slice_header error
[h264 @ 0x7fe620c55680] no frame!
...

The system is otherwise usable (although at some point opening new tabs in firefox will result in failure as well).

Comment 14 Clemens Eisserer 2020-10-24 16:00:31 UTC
Similar problem has been detected:

crash after login

reporter:       libreport-2.13.1
backtrace_rating: 4
cmdline:        /usr/bin/plasmashell
crash_function: qt_message_fatal
executable:     /usr/bin/plasmashell
journald_cursor: s=61eb37102f4f47c1a33b25a2762d2462;i=1d0ff;b=8cefc45e63824031889934b691b81200;m=321bcf6;t=5b26c46a5035f;x=fd3e4393594a7d1d
kernel:         5.8.15-201.fc32.x86_64
package:        plasma-workspace-5.18.5-2.fc32
reason:         plasmashell killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:

Comment 15 Fedora Program Management 2021-04-29 16:38:58 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 16 Ben Cotton 2021-05-25 16:47:49 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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