Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1065400

Summary: [abrt] kde-workspace: KCrash::defaultCrashHandler(): kwin killed by SIGSEGV
Product: Red Hat Enterprise Linux 7 Reporter: Jeff Bastian <jbastian>
Component: kde-workspaceAssignee: Daniel Vrátil <dvratil>
Status: CLOSED WORKSFORME QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 7.0CC: jbastian, jeischma, jmarko, than
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:5d8de07c846328ea5155c406a771dd4dce5fa926
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-13 17:30:01 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: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: sosreport.tar.xz
none
valgrind on kwin (1/3)
none
valgrind on kwin (2/3)
none
valgrind on kwin (3/3) none

Description Jeff Bastian 2014-02-14 15:03:51 UTC
Description of problem:
I switched the KDE Desktop Effects "Compositing type" and "Qt graphics system" settings from XRender/Native to OpenGL/Raster and hit apply and kwin crashed (but it restarted automatically).

Version-Release number of selected component:
kde-workspace-4.10.5-10.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        kwin
crash_function: KCrash::defaultCrashHandler
executable:     /usr/bin/kwin
kernel:         3.10.0-86.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            12257

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 KCrash::defaultCrashHandler at /usr/src/debug/kdelibs-4.10.5/kdeui/util/kcrash.cpp:346
 #3 XRenderHasDepths at Xrender.c:119
 #4 XRenderExtAddDisplay at Xrender.c:202
 #5 XRenderFindDisplay at Xrender.c:289
 #6 XRenderFreePicture at Picture.c:232
 #7 ~XRenderPictureData at /usr/src/debug/kde-workspace-4.10.5/kwin/libkwineffects/kwinxrenderutils.h:97
 #8 ~KSharedPtr at /usr/include/kde4/ksharedptr.h:90
 #9 KWin::XRenderPicture::~XRenderPicture at /usr/src/debug/kde-workspace-4.10.5/kwin/libkwineffects/kwinxrenderutils.h:76
 #10 __cxa_finalize at cxa_finalize.c:55
 #11 __do_global_dtors_aux at /lib64/libkwineffects.so.1

Comment 1 Jeff Bastian 2014-02-14 15:03:53 UTC
Created attachment 863300 [details]
File: backtrace

Comment 2 Jeff Bastian 2014-02-14 15:03:55 UTC
Created attachment 863301 [details]
File: cgroup

Comment 3 Jeff Bastian 2014-02-14 15:03:56 UTC
Created attachment 863302 [details]
File: core_backtrace

Comment 4 Jeff Bastian 2014-02-14 15:03:58 UTC
Created attachment 863303 [details]
File: dso_list

Comment 5 Jeff Bastian 2014-02-14 15:04:00 UTC
Created attachment 863304 [details]
File: environ

Comment 6 Jeff Bastian 2014-02-14 15:04:02 UTC
Created attachment 863305 [details]
File: limits

Comment 7 Jeff Bastian 2014-02-14 15:04:04 UTC
Created attachment 863306 [details]
File: maps

Comment 8 Jeff Bastian 2014-02-14 15:04:05 UTC
Created attachment 863307 [details]
File: open_fds

Comment 9 Jeff Bastian 2014-02-14 15:04:08 UTC
Created attachment 863308 [details]
File: proc_pid_status

Comment 10 Jeff Bastian 2014-02-14 15:04:12 UTC
Created attachment 863309 [details]
File: var_log_messages

Comment 11 Jeff Bastian 2014-02-14 15:04:25 UTC
Created attachment 863310 [details]
File: sosreport.tar.xz

Comment 13 Daniel Vrátil 2014-02-24 11:54:32 UTC
Can you reliably reproduce the crash? I was not able to reproduce it locally.

What GPU and GPU drivers do you have?

Can you please provide list of activated KWin effects:

qdbus org.kde.kwin /Effects org.kde.kwin.Effects.loadedEffects
qdbus org.kde.kwin /Effects org.kde.kwin.Effects.activeEffects


The backtrace seems it could be a double-free corruption. If you can please try reproducing when running KWin under valgrind.

Comment 14 Daniel Vrátil 2014-02-24 11:56:04 UTC
(Note: to restart KWin, use kwin --replace. Killing KWin will usually steal you focus from console and you won't be able to start it again)

Comment 15 Jeff Bastian 2014-02-24 17:52:50 UTC
I haven't been able to reproduce it either.  I've tried toggling between OpenGL and XRender, and Native and Raster, and various combinations, and I haven't seen it crash again.  I've also enabled and disabled the effects in the various modes and it's behaved properly.

I have an Intel Haswell i7-4600U CPU with the HD Graphics 4400 GPU (this is a Lenovo T440s laptop) and an external Samsung display connected with Mini-DisplayPort to DVI-D connector.

~]$ qdbus org.kde.kwin /Effects org.kde.kwin.Effects.loadedEffects
kwin4_effect_zoom
kwin4_effect_login
kwin4_effect_slidingpopups
kwin4_effect_minimizeanimation
kwin4_effect_translucency
kwin4_effect_screenshot
kwin4_effect_slide
kwin4_effect_desktopgrid
kwin4_effect_maximize
kwin4_effect_fade
kwin4_effect_dialogparent
kwin4_effect_highlightwindow
kwin4_effect_taskbarthumbnail
kwin4_effect_presentwindows
kwin4_effect_blur
kwin4_effect_dashboard
kwin4_effect_outline
kwin4_effect_startupfeedback

~]$ qdbus org.kde.kwin /Effects org.kde.kwin.Effects.activeEffects
kwin4_effect_blur

Comment 16 Jeff Bastian 2014-02-24 18:52:01 UTC
I tried running kwin under valgrind and still no luck reproducing the problem.

valgrind --trace-children=yes \
         --track-origins=yes \
         --log-file=/tmp/kwin-valgrind-%p.out \
         -- \
         /usr/bin/kwin --replace


However, valgrind did find a number of other problems with kwin including uninitialized values, invalid writes, and invalid reads.  I'll attach the valgrind logs.

Comment 17 Jeff Bastian 2014-02-24 18:54:41 UTC
Created attachment 867104 [details]
valgrind on kwin (1/3)

Comment 18 Jeff Bastian 2014-02-24 18:56:00 UTC
Created attachment 867105 [details]
valgrind on kwin (2/3)

This file was 940 KiB, so I compressed it with xz

Comment 19 Jeff Bastian 2014-02-24 18:56:32 UTC
Created attachment 867106 [details]
valgrind on kwin (3/3)

Comment 21 Than Ngo 2014-03-20 12:05:18 UTC
since this bug cannot reproducable, i closed it as "WORKFORME". Feel free to reopen it again if you can reproduce it.

Comment 27 Jeff Bastian 2015-01-13 17:30:01 UTC
I can't reproduce on RHEL 7.1, so I'm going to close this again as WORKSFORME since it only happened one time on RHEL 7.0 Alpha/Beta.