Bug 361692 - Clock doesn't update while compositing is off
Summary: Clock doesn't update while compositing is off
Status: RESOLVED DUPLICATE of bug 353983
Alias: None
Product: plasmashell
Classification: Plasma
Component: Digital Clock (show other bugs)
Version: 5.6.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Martin Klapetek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-12 21:51 UTC by tamius.han
Modified: 2017-11-15 20:57 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tamius.han 2016-04-12 21:51:43 UTC
When I start a game that disables compositing (e.g. CSGO, XCOM:EU/EW, Civ 5), the digital clock stops updating at all. If I launch a game that disables compositing at, say, 18:30, the digital clock in my panel will display 18:30 until the moment I quit game and compositing becomes enabled — regardless of whether I've played for 15 minutes or 6 hours.

Reproducible: Always

Steps to Reproduce:
1. Launch a game that disables compositing (e.g. Counter Strike)
2. Note the time
3. Play the game for some time, e.g. one competitive match (or ten)
4. Tab out of the game (or don't run the game in full screen in the first place)

Actual Results:  
Clock displays time from few hours ago (depends on how long you were playing)

Expected Results:  
Clock displays current time.
Comment 1 David Edmundson 2016-04-12 23:14:51 UTC
Is any of the rest of the panel updating? If you mouse over the "K" does it go lighter?
Comment 2 tamius.han 2016-04-25 20:43:31 UTC
No, the rest of the panel doesn't seem to update either.

Network/cpu/RAM monitor widgets on a different panel are getting updated, though.
Comment 3 Alex Richardson 2016-06-08 12:00:46 UTC
For me the panel also sometimes stops updating (openSuSE Tumbleweed git snapshot packages).
Not sure if it is related to disabling compositing as the only programs I had running at the time were KDevelop, Chromium and Konsole.
Comment 4 J. Daffodil 2016-08-31 21:43:29 UTC
I have this problem. When I disable compositing, my panel stops updating.

Nvidia 970, 367.35 proprietary driver
openSUSE Leap, kernel 4.1.27
Plasma 5.5.5
Two monitors

I doubt much info will be relevant, though, because I've had this issue for years. With KDE4, with a different GPU, different kernel. The only things that have remained constant have been openSUSE (I know I saw it with 13.1, 13.1, and 42.1 at least), a Nvidia GPU (a 460, 660 Ti, and 970) and the proprietary Nvidia driver (all of the versions I've used, I think). I'm not sure about it always being a multi-monitor setup. I'll do some testing on that when I'm home and have some free time.
Comment 5 Ruman Gerst 2016-09-13 02:40:10 UTC
This happens for me on Plasma 5.7.3 ... and not only the clock - everything that is in the panels stop updating (e.g the Teamspeak 3 indicator that shows the microphone status).
The task manager does not update, too and often doesn't even show an entry for the game. It's there - it will react if you click on it. Also menus etc. are working fine.

If I try to restart plasmashell (kquitapp plasmashell; kstart plasmashell), the panel of the secondary monitor flickers quickly between the primary and the secondary monitor. If I start plasmashell in a terminal, it spams following message:
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "preferredWidth"

If I exit the game, the problem persists (even a plasmashell restart doesn't help). Only kwin_x11 --replace fixes the problem. 

So far caused by following games: Starbound and Stardew Valley
HW: Nvidia GTX 660, prorietary drivers (367.44)
OS: Manjaro, Kernel 4.7
Comment 6 Cyrille Dunant 2016-09-14 10:29:46 UTC
I have the reverse problem, with compositing, the panel stops updating after perhaps 1-2 minutes. using opensuse git snapshots.

VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
Comment 7 Ian Whyman (thev00d00) 2017-10-29 17:31:24 UTC
What information do we need to provide to move this along?
Comment 8 Christoph Feck 2017-11-15 20:57:49 UTC

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