Bug 1401204

Summary: Fedora 25 xfce : crash to login when qt5 apps are involved
Product: [Fedora] Fedora Reporter: mediaklan <mediaklan>
Component: qt5Assignee: Helio Chissini de Castro <helio>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 25CC: fsumsal, helio, mediaklan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Fedora Xfce 4.8.10-300.fc25.x86_64 Nvidia proprietary drivers 375.26
Last Closed: 2017-12-12 10:56:42 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
journalctl
none
journalctl (2) none

Description mediaklan 2016-12-03 13:49:51 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36
Build Identifier: 

Since the upgrade from F24 to F25, switching or restoring apps (alt+tab, or selected from panel etc) will often result in a crash, back to the login. It happens mostly when qt5 apps are involved (smplayer, scribus, etc) but I'm unsure if it's always the case. This behavior do not seem consistent (I mean the crash would not happen for hours but then will happen 2 or 3 times in a row in half an hour).

Reproducible: Sometimes

Steps to Reproduce:
1. Using a qt5 app for a few minutes and pause/minimize the app.
2. Switch to Blender or Chrome, then switch back to the qt5 app.
3. Crash as soon as the app is selected (mouse hover and click) 
Actual Results:  
Back to the login, I enter my desktop again and resume work. I can see coredumps and some kernel segfault in the journal but there's nothing worth mention in Xorg.0.log

Expected Results:  
Prevent a normal desktop usage, since it can happen quite a few times in a row. 

Please see journal attachments if it can help. Don't hesistate to ask for any logs that might be helpful if you lack information from these. Thank you for your help.

Comment 1 mediaklan 2016-12-03 13:52:49 UTC
Created attachment 1227672 [details]
journalctl

Comment 2 mediaklan 2016-12-03 13:53:19 UTC
Created attachment 1227673 [details]
journalctl (2)

Comment 3 mediaklan 2016-12-26 20:40:10 UTC
Note 1 : I'm using Nvidia proprietary drivers 375.26. There are supposedly working with Xorg 1.19 (as far as I remember) 
Note 2 : for now, it seems I can avoid the crash by downgrading to Xorg 1.18 using packages from fedora 24.

Comment 4 Fedora End Of Life 2017-11-16 18:33:18 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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 '25'.

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 25 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 5 Fedora End Of Life 2017-12-12 10:56:42 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.