Bug 1701037

Summary: [abrt] kwin: qt_message_fatal(): kwin_x11 killed by SIGABRT
Product: [Fedora] Fedora Reporter: Tomas Toth <ttomasz>
Component: kwinAssignee: Daniel Vrátil <me>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: geospyr2001, jgrulich, kde-sig, me, rdieter, stealthcipher, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/01315286206e7a300c70212083ec07cc2566ca2e
Whiteboard: abrt_hash:ae092de2959b7c002f6ffaaf8eacf77cd18dcf87;VARIANT_ID=kde;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-12 14:16:51 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: cgroup
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
dnf history info of the update triggering the issue none

Description Tomas Toth 2019-04-17 21:05:52 UTC
Description of problem:


Version-Release number of selected component:
kwin-5.15.4-1.fc30

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/bin/kwin_x11 -session 10d06d6567000154604483500000013170006_1555450045_992504
crash_function: qt_message_fatal
executable:     /usr/bin/kwin_x11
journald_cursor: s=b8b84ba3f89a4674a918fb5616b14f08;i=881;b=cb3f18edc2e04d488da708d46a6ddf4a;m=70013c9;t=586acb6ace9e0;x=4dcd6506f031833b
kernel:         5.0.7-300.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Potential duplicate: bug 1651001

Comment 1 Tomas Toth 2019-04-17 21:05:55 UTC
Created attachment 1556019 [details]
File: backtrace

Comment 2 Tomas Toth 2019-04-17 21:05:56 UTC
Created attachment 1556020 [details]
File: cgroup

Comment 3 Tomas Toth 2019-04-17 21:05:58 UTC
Created attachment 1556021 [details]
File: core_backtrace

Comment 4 Tomas Toth 2019-04-17 21:05:59 UTC
Created attachment 1556022 [details]
File: cpuinfo

Comment 5 Tomas Toth 2019-04-17 21:06:02 UTC
Created attachment 1556023 [details]
File: dso_list

Comment 6 Tomas Toth 2019-04-17 21:06:03 UTC
Created attachment 1556024 [details]
File: environ

Comment 7 Tomas Toth 2019-04-17 21:06:04 UTC
Created attachment 1556025 [details]
File: limits

Comment 8 Tomas Toth 2019-04-17 21:06:06 UTC
Created attachment 1556026 [details]
File: maps

Comment 9 Tomas Toth 2019-04-17 21:06:08 UTC
Created attachment 1556027 [details]
File: mountinfo

Comment 10 Tomas Toth 2019-04-17 21:06:09 UTC
Created attachment 1556028 [details]
File: open_fds

Comment 11 Tomas Toth 2019-04-17 21:06:10 UTC
Created attachment 1556029 [details]
File: proc_pid_status

Comment 12 Tomas Toth 2019-04-17 21:06:12 UTC
Created attachment 1556030 [details]
File: var_log_messages

Comment 13 Tomas Toth 2019-04-18 00:16:20 UTC
This crash happened once, but I have a count of over 500 of bug #1695374 .

The issue started right after the F30 stable (mega)update among others containing:
  Mesa 19.0.2, Qt5 5.12.1, KDE Plasma 5.15.4.
There was no Kernel update at that time.
For more details see attached dnf history info command log from the discussed update.

My KDE desktop became unusable, often it hangs within seconds after startup.
It can be triggered by any action/movement in the KDE Menu or Task bar.
Only way out is to reboot using SysRq: Alt+SysRq+e s i u b.

Also, /usr/bin/plasmashell often starts to use 100% CPU. If I manage to kill the plasmashell, (I always have an open konsole) konsole, firefox (lanched from konsole), nedit works OK. Background is garbled.

ABRT catches no other crash.
I switched SELInux to permissive mode.

Comment 14 Tomas Toth 2019-04-18 00:21:48 UTC
Created attachment 1556043 [details]
dnf history info of the update triggering the issue

Comment 15 Rex Dieter 2019-04-19 13:41:01 UTC
Appears to be video driver issue,

Apr 16 23:47:04 omega kwin_x11[1584]: Freeze in OpenGL initialization detected
Apr 16 23:47:05 omega kwin_x11[2147]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 178, resource id: 27262983, major code: 20 (GetProperty), minor code: 0
Apr 16 23:47:05 omega kwin_x11[2147]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 179, resource id: 27262983, major code: 20 (GetProperty), minor code: 0
Apr 16 23:47:06 omega kwin_x11[2147]: kwin_core: Compositing is not possible

Comment 16 Tomas Toth 2019-04-20 08:59:47 UTC
In the same time, I also started to hit:
Bug #1695374 - [abrt] nouveau_vma_del: WARNING: CPU: 5 PID: 186 at drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x6a/0x80 [nouveau] [nouveau]
  ABRT count: 809

Bug #1697004 - [abrt] nouveau_vma_del: WARNING: CPU: 5 PID: 3895 at drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x6a/0x80 [nouveau] [nouveau]
  ABRT count: 1

Comment 17 Tomas Toth 2019-05-11 18:19:15 UTC
The latest qt5-qtbase 5.12.1-6 update is a functional workaround.
  https://bodhi.fedoraproject.org/updates/FEDORA-2019-f43ed18461
KDE/Plasmashell does not crash, freezes, etc.

Thank you, Rex!

Comment 18 Rex Dieter 2019-05-12 14:16:51 UTC

*** This bug has been marked as a duplicate of bug 1706420 ***

Comment 19 Ryan 2019-06-01 11:11:21 UTC
*** Bug 1716048 has been marked as a duplicate of this bug. ***

Comment 20 Spyros 2019-10-12 16:49:25 UTC
*** Bug 1761124 has been marked as a duplicate of this bug. ***