[kwin] [Bug 347153] Java app (Netbeans, Intellij IDEA...) window losing focus when switching to another desktop and back
https://bugs.kde.org/show_bug.cgi?id=347153 Roland Pallai changed: What|Removed |Added CC||d...@rock.hu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348569] KWin's timestamp mechanism isn't robust against bogus event times
https://bugs.kde.org/show_bug.cgi?id=348569 Roland Pallai changed: What|Removed |Added CC||d...@rock.hu --- Comment #30 from Roland Pallai --- I hit this issue without cssh today. After the screen was unlocked windows are unmoveable, alt+tab does not work, etc. kwin restart does not help. Xorg session was started at Mar30, 19 days before. Yesterday it was working. As a simple end-user I do not understand your explanation completely, but do you know what is happening here and you proposed a fix here? Can I expect a kwin upgrade will resolve this issue soon..? (In reply to Thomas Lübking from comment #28) > Technically, there's nothing such as a "bad" timestamp. > > Looking at the patch, cssh was buggy for sure - time() returns the time in > seconds since epoch (presently sth. around 1450899519) while the function > expects an X11 server timestamp (msecs since last server start, wraps every > ~50 days) > So to be accurate, your server would (presently) have to be running for 16 > days. > If it's running longer, the grab happened in the past (until you wrap ;-), > but I assume it's more a problem when it's in the far future (ie. the server > recently started or wrapped) > > What will happen is that KWin's as well as Qt's event reader will read that > timestamp from the event queue and update their copy of the server timestamp > with it, then try to perform a future grab and the x11 server denies. > (This is what one gets by "kwinApp()->setX11Time(xTime()+1);" before the > grab) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348569] KWin's timestamp mechanism isn't robust against bogus event times
https://bugs.kde.org/show_bug.cgi?id=348569 --- Comment #31 from Roland Pallai --- (In reply to Roland Pallai from comment #30) > Xorg session was started at Mar30, 19 days before. Oops. So ~50 days before.. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348569] KWin's timestamp mechanism isn't robust against bogus event times
https://bugs.kde.org/show_bug.cgi?id=348569 --- Comment #33 from Roland Pallai --- Thank you, I understand. Some kind of protection against buggy clients would be nice, the session should stay usable at least. I would be pleased even if the workaround involves kwin restart. BTW I do not use clusterssh, not installed. I suspect NetBeans as it has a known timestamp problem (#347153). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348569] KWin's timestamp mechanism isn't robust against bogus event times
https://bugs.kde.org/show_bug.cgi?id=348569 --- Comment #36 from Roland Pallai --- (In reply to Thomas Lübking from comment #35) > Sure you're facing *this* bug then? The particular problem is caused by > clients (cssh in this very case) sending future timestamps around (causing a > failure in grabs and pastes) > The netbeans bug is largely different [...] The first 8 comments _exactly_ described the symptoms, including error messages reported by Miller at #c8, so I commented here, but yes, as I learn more about this issue, I cannot rule out that it might be a different bug with same symptoms. My desktop environment mostly stable, same apps are running all the time and I have never experienced this bug before. X session uptime often reaches 20-30 days but there is a chance that this was the first time when went further than 50 days - first time when the X server's timestamp wrapped. It is suspicious for me. What do you think? Should I open a new report? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349481] konsole session sometimes is not saved into ~/.config/ksmserverrc on logout
https://bugs.kde.org/show_bug.cgi?id=349481 Roland Pallai changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #21 from Roland Pallai --- For the record: it is fixed in Fedora 24. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related
https://bugs.kde.org/show_bug.cgi?id=343661 Roland Pallai changed: What|Removed |Added CC||d...@rock.hu --- Comment #58 from Roland Pallai --- I know this problem well since Fedora 20. Windows with frequent updates are the first to freeze (plasmashell with CPU monitor, pavucontrol, Chrome with open meta refresh page or youtube video). Setting environment variables KWIN_USE_BUFFER_AGE/KWIN_EXPLICIT_SYNC does not help. Shift+Alt+F12 fixes for a while. Recently found that switching compositor to OpenGL 3.1 / EGL over OpenGL 2.0 / EGL modifies the behaviour on Intel video: the whole desktop freezes after 4-8 days instead of the frequent (daily) window content freezes. I can still interact with the last active window but the screen does not refresh anymore. It's not better at all, just different. This way Shift+Alt+F12 does not help and kwin does not respond on D-Bus. I know it is not much info, but nobody mentioned yet.. -- You are receiving this mail because: You are watching all bug changes.
