Bug 1395741

Summary: [abrt] plasma-workspace: __bsd_signal(): plasmashell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: bugzilla <bugzilla>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: ajax, jgrulich, kde-sig, me, rdieter, than, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/268ca09fcdaaef3802360f2106b462944ad6a316
Whiteboard: abrt_hash:89271512ea8800c6ba08e32a1b008ccd7e28bfb2;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:16:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description bugzilla@ruault.com 2016-11-16 14:56:32 UTC
Description of problem:
regular usage ... This happens regularly

Version-Release number of selected component:
plasma-workspace-5.7.5-2.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        /usr/bin/plasmashell --shut-up
crash_function: __bsd_signal
executable:     /usr/bin/plasmashell
global_pid:     12841
kernel:         4.7.9-200.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (1 frames)
 #0 __bsd_signal at ../sysdeps/posix/signal.c:48

Comment 1 bugzilla@ruault.com 2016-11-16 14:56:39 UTC
Created attachment 1221230 [details]
File: backtrace

Comment 2 bugzilla@ruault.com 2016-11-16 14:56:40 UTC
Created attachment 1221231 [details]
File: cgroup

Comment 3 bugzilla@ruault.com 2016-11-16 14:56:42 UTC
Created attachment 1221232 [details]
File: core_backtrace

Comment 4 bugzilla@ruault.com 2016-11-16 14:56:43 UTC
Created attachment 1221233 [details]
File: dso_list

Comment 5 bugzilla@ruault.com 2016-11-16 14:56:45 UTC
Created attachment 1221234 [details]
File: environ

Comment 6 bugzilla@ruault.com 2016-11-16 14:56:46 UTC
Created attachment 1221235 [details]
File: limits

Comment 7 bugzilla@ruault.com 2016-11-16 14:56:49 UTC
Created attachment 1221236 [details]
File: maps

Comment 8 bugzilla@ruault.com 2016-11-16 14:56:50 UTC
Created attachment 1221237 [details]
File: mountinfo

Comment 9 bugzilla@ruault.com 2016-11-16 14:56:52 UTC
Created attachment 1221238 [details]
File: namespaces

Comment 10 bugzilla@ruault.com 2016-11-16 14:56:53 UTC
Created attachment 1221239 [details]
File: open_fds

Comment 11 bugzilla@ruault.com 2016-11-16 14:56:54 UTC
Created attachment 1221240 [details]
File: proc_pid_status

Comment 12 bugzilla@ruault.com 2016-11-16 14:56:56 UTC
Created attachment 1221241 [details]
File: var_log_messages

Comment 13 bugzilla@ruault.com 2016-11-16 15:02:14 UTC
The plasmashell process is regularly crashing out of nowhere since I upgraded from FC21 to FC24. 
There is one improvement though since the latest package upgrades, now it restarts automatically, before I had to restart it manually to recover the menu bar at the bottom of the screen.

Comment 14 Rex Dieter 2016-11-16 15:11:38 UTC
From retrace, the backtrace ends up in intel driver code:

brw_workaround_depthstencil_alignment
brw_clear

Reassigning to intel driver


You could consider using the intel modesetting driver instead (easiest way to try that is to simply remove xorg-x11-drv-intel and reboot)

Comment 15 bugzilla@ruault.com 2016-11-17 13:52:28 UTC
I've seen that the intel driver is causing troubles on a lot of distros. 
Do you know if theses issues are being worked on ? I know people on Ubuntu who have a garbled screen because of this driver so I can consider myself lucky here...

Comment 16 Rex Dieter 2016-11-18 12:30:36 UTC
As far as I know, most ongoing work is involved in the intel modesetting driver, which is why I suggested you try it.

Comment 17 bugzilla@ruault.com 2016-11-18 12:31:45 UTC
Thanks, I'll do that !

Comment 18 Fedora End Of Life 2017-07-25 23:54:19 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 19 Fedora End Of Life 2017-08-08 19:16:47 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.