Bug 1359769 - Compositor is de-activated the second time you log in KDE
Summary: Compositor is de-activated the second time you log in KDE
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kf5-kwindowsystem
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Daniel Vrátil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-25 12:22 UTC by Panos Kavalagios
Modified: 2016-08-03 15:00 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-25 14:50:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 362531 0 None None None 2016-08-03 14:54:33 UTC

Description Panos Kavalagios 2016-07-25 12:22:56 UTC
Description of problem: 
The compositor is de-activated and cannot be re-enabled if you log in for a second time in KDE. The taskbar for example is not transparent. The problem is resolved only if you reboot the system and you log in for the first time.


Version-Release number of selected component (if applicable):
kwin-5.7.1-3.fc24.x86_64


How reproducible:
Log in to KDE for a second time.


Steps to Reproduce:
1. Reboot the system.
2. Log in to KDE.
3. Logout and try to log in again.

Actual results:
The compositor is not enabled. The taskbar is losing its transparent layout (oxygen black theme).


Expected results:
The compositor should have been enabled as the first time you log in to the system.

Additional info:
The graphics card is:
VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)

Comment 1 Rex Dieter 2016-07-25 12:33:24 UTC
I encourage you to report this upstream to bugs.kde.org

Comment 2 Panos Kavalagios 2016-07-25 14:10:25 UTC
I am not using a self compiled KDE version, but the one provided in the repositories.

There is no problem reporting it upstream, but can you at least provide any hint for retrieving better information. The Xorg.0.log does not report any issue.

Comment 3 Rex Dieter 2016-07-25 14:12:17 UTC
Including the output from:

qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation

is probably a good enough start.

Comment 4 Panos Kavalagios 2016-07-25 14:47:34 UTC
Reported upstream:

https://bugs.kde.org/show_bug.cgi?id=366091

Comment 5 Rex Dieter 2016-07-25 14:50:25 UTC
Thanks.   We'll continue tracking upstream.

Comment 6 Panos Kavalagios 2016-08-03 07:48:54 UTC
There seems to be a patch that resolves the issue. Are you going to prepare a patched RPM for testing purposes or should we wait for the official release?

Comment 7 Rex Dieter 2016-08-03 11:25:40 UTC
I was planning on waiting for release, since it's not a critical issue that warrants extra time to backport.

Comment 8 Rex Dieter 2016-08-03 14:54:34 UTC
Adding links to upstream fix for posterity, and in case anyone wanted to work on backports,

http://commits.kde.org/kwindowsystem/4d355569eea2fae76ed67f791db8abeec1e794f0

Comment 9 Rex Dieter 2016-08-03 15:00:17 UTC
Nevermind, according to
https://community.kde.org/Schedules/Frameworks

next frameworks release (that includes kwindowsystem) is scheduled for later this week, may as well wait for it


Note You need to log in before you can comment on or make changes to this bug.