[kwin] [Bug 449921] Wayland session doesn't output session logs in Plasma 5.24.0
https://bugs.kde.org/show_bug.cgi?id=449921 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- The logs are in the journal: journalctl --user -u plasma-kwin_wayland Does it log something for you though when you start a second session as described here or does it not? https://community.kde.org/KWin/Wayland#Start_a_Plasma_session_on_Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443271] Kdeconnect hijacks the clipboard when connected to another Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=443271 --- Comment #3 from Roman Gilg --- * For me it puts the clipboard content as second item into the clipboard history, so it still only copies the entry which was before and now is still at the top. I believe though that's through resetting the clipboard back to the previous value. * It also happens to me only on every second paste attempt. * It happens on Wayland and X11. I checked out git commits of KDE Connect up until 12ad4e3e in June and could reproduce the issue also here. Don't know the first bad commit but I never had this issue before so I would assume that this bug was introduced through some other update. @qydwhotmail, when did you first encounter it on your system? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 445167] Text added to second position in list
https://bugs.kde.org/show_bug.cgi?id=445167 Roman Gilg changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #3 from Roman Gilg --- *** This bug has been marked as a duplicate of bug 443271 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443271] Kdeconnect hijacks the clipboard when connected to another Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=443271 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- *** Bug 445167 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 445167] Text added to second position in list
https://bugs.kde.org/show_bug.cgi?id=445167 Roman Gilg changed: What|Removed |Added Component|Clipboard |common Version|master |unspecified Target Milestone|1.0 |--- Assignee|plasma-b...@kde.org |albertv...@gmail.com Product|plasmashell |kdeconnect -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445167] Text added to second position in list
https://bugs.kde.org/show_bug.cgi?id=445167 --- Comment #2 from Roman Gilg --- Thanks for testing it out Nate. I'm debugging the problem at the moment and after killing off processes at random the culprit rather seems to be kdeconnectd. Might be similar to #443271. I'm currently bisecting kdeconnect to find the first bad commit. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445167] New: Text added to second position in list
https://bugs.kde.org/show_bug.cgi?id=445167 Bug ID: 445167 Summary: Text added to second position in list Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: subd...@gmail.com Target Milestone: 1.0 SUMMARY The clipboard selection is added every second time to the second position in the list in Klipper resulting in the selection not changing. STEPS TO REPRODUCE 1. Start X11 or Wayland session 2. Copy some text with ctrl+c 3. See it every second time being added to the second position of the list in Klipper instead of to the front. SOFTWARE/OS VERSIONS Manjaro, KDE software built from master ADDITIONAL INFORMATION That is happening since recently only. Not sure since when. I tried to check out an earlier commit of plasma-workspace, but didn't help. Maybe a Qt update? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436563] KScreen needs to be able to change display configuration of SDDM, too
https://bugs.kde.org/show_bug.cgi?id=436563 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #4 from Roman Gilg --- Disman (https://gitlab.com/kwinft/disman) runs independent of a Plasma workspace. It reuses the configuration data for each session with the same windowing system. If Disman would be launched by SDDM then Disman would do what you want automatically. You can probably try it out yourself through some systemd service hookups. See the section of the README on how to use an independent Disman: https://gitlab.com/kwinft/disman#independent -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 430521] Dolphin doesn't restore to original size after resuming from maximized.
https://bugs.kde.org/show_bug.cgi?id=430521 --- Comment #11 from Roman Gilg --- Can confirm works now with KWinFT. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430521] Dolphin does'nt restore to original size after resuming from maximized.
https://bugs.kde.org/show_bug.cgi?id=430521 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- I noticed this issue too when working on windowing improvements to KWinFT. Dolphin sends for some reason a configure request with a seemingly random size after the compositor already has restored it. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 420073] Umbrello does not show aggregation association
https://bugs.kde.org/show_bug.cgi?id=420073 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- Created attachment 132789 --> https://bugs.kde.org/attachment.cgi?id=132789=edit example-view I have the same issue on master. Could this be looked into? An example is attached. See the Toplevel class aggregating Wrapland::Server::Surface but not showing this connection in the view. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422372] kwin_wayland asserts when overlapping screens
https://bugs.kde.org/show_bug.cgi?id=422372 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #6 from Roman Gilg --- Hey, we also hit this bug in KWinFT: https://gitlab.com/kwinft/kwinft/-/issues/67#note_397290004 I have a MR for it here: https://gitlab.com/kwinft/kwinft/-/merge_requests/36 Should apply cleanly to KWin too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #5 from Roman Gilg --- What's the problem now? a) Xwayland bridge does not exist. b) GTK Wayland clients do not support zwp_primary_selection. Or both? Solution for (a) is adding the bridge, solution for (b) is to talk to someone from Gnome/GTK team to implement it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425190] Improve scaling of the desktop
https://bugs.kde.org/show_bug.cgi?id=425190 --- Comment #20 from Roman Gilg --- Interesting comparison. Linear looks to me even better. Might there be other algorithms improving upon that though? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425190] Improve scaling of the desktop
https://bugs.kde.org/show_bug.cgi?id=425190 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #11 from Roman Gilg --- (In reply to Claudius Ellsel from comment #10) > So when applying fractional scaling, say a factor of 1.25 the icons, mouse > cursor etc. are not upscaled? They are rendered at 2-times the normal size and then downscaled. That's the theory, in practice there can always be issues. I believe sometimes Qt Wayland clients do not update their size when changing the scale factor. And then there is of course Xwayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423067] Improve keyboard shortcuts for window arrangement
https://bugs.kde.org/show_bug.cgi?id=423067 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- I like Meta+Up twice to maximize but would rather go with Meta+Up+Left upper left corner and Meta+Left always left tile. What would you do with minimize? Meta+Down twice for minimizing is difficult because you can't press again Meta+Up to get it unminimized. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 421022] New: Compile-install without sudo not possible
https://bugs.kde.org/show_bug.cgi?id=421022 Bug ID: 421022 Summary: Compile-install without sudo not possible Product: frameworks-bluez-qt Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: subd...@gmail.com Target Milestone: --- Compiling and installing to some location in /opt without sudo is not possible because it tries to install files in system directory unconditionally: CMake Error at cmake_install.cmake:79 (file): file INSTALL cannot copy file "/home/roman/dev/kde/bluez-qt/src/61-kde-bluetooth-rfkill.rules" to "/lib/udev/rules.d/61-kde-bluetooth-rfkill.rules". It should only try to install in the prefix. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 420169] KScreen does not change the screen resolution of QEMU/QXL/Spice VM
https://bugs.kde.org/show_bug.cgi?id=420169 --- Comment #6 from Roman Gilg --- You should post this information in the bug report, that this one has been marked to be a duplicate of, since not many people will read it hear. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 407058] KDE Plasma5 can't change resolution in VM after last update
https://bugs.kde.org/show_bug.cgi?id=407058 Roman Gilg changed: What|Removed |Added CC||bo...@gmx.ru --- Comment #22 from Roman Gilg --- *** Bug 420169 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 420169] KScreen does not change the screen resolution of QEMU/QXL/Spice VM
https://bugs.kde.org/show_bug.cgi?id=420169 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED CC||subd...@gmail.com Resolution|--- |DUPLICATE --- Comment #4 from Roman Gilg --- *** This bug has been marked as a duplicate of bug 407058 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419980] Cannot change relative position of multiple screens
https://bugs.kde.org/show_bug.cgi?id=419980 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk, ||subd...@gmail.com Resolution|--- |FIXED --- Comment #2 from Roman Gilg --- To my knowledge that was fixed in some frameworks patch already in some released version likely >5.62. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419374] Scaling for GTK doesn't work
https://bugs.kde.org/show_bug.cgi?id=419374 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- What new scaling? Is it X11 or Wayland? Please make some screenshots. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414418] Truncated labels on Display and Monitor / Display Configuration page
https://bugs.kde.org/show_bug.cgi?id=414418 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #4 from Roman Gilg --- Could be an issue in Kirigami or QtQuick.Controls. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 418739] tablet mode value is wrong in kded
https://bugs.kde.org/show_bug.cgi?id=418739 Roman Gilg changed: What|Removed |Added Latest Commit||https://commits.kde.org/lib ||kscreen/6ba447e9e59da852a51 ||4101d8f2fa467c972ff8f Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Roman Gilg --- Git commit 6ba447e9e59da852a514101d8f2fa467c972ff8f by Roman Gilg. Committed on 18/03/2020 at 01:44. Pushed by romangilg into branch 'master'. fix: transfer tablet mode properties Summary: I forgot to copy over the tablet-mode-available and -engaged data from one config to the next one. Because of that the data was not available to the daemon. Also serialize the tablet mode properties in the Serializer. The Serializer is not used on Wayland afaik but if at one point for example the RandR backend gains auto rotation support we need to have it in the Serializer. Test Plan: Manually with hard-coded tablet mode availability in KWin. Reviewers: #plasma, bshah Reviewed By: #plasma, bshah Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28106 M +2-0src/config.cpp M +10 -0src/configserializer.cpp https://commits.kde.org/libkscreen/6ba447e9e59da852a514101d8f2fa467c972ff8f -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409688] kwin_wayland aborted when shutting down involving invalid reads and writes, use of uninitialized variables etc.
https://bugs.kde.org/show_bug.cgi?id=409688 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- Thanks for the awesome protocols! But your version of Plasma is super-old. Would you be able to retry with current 5.18? I'm asking this because I'm currently looking into KScreenLocker. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413663] [Wayland] Screens often reversed position after suspend or boot
https://bugs.kde.org/show_bug.cgi?id=413663 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- Still an issue with 5.18? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418836] Ability to tell kscreen that system is a desktop and so not be so dynamic with the monitors
https://bugs.kde.org/show_bug.cgi?id=418836 Roman Gilg changed: What|Removed |Added Assignee|kscreen-bugs-n...@kde.org |kwin-bugs-n...@kde.org Component|common |general Product|KScreen |kwin CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- If one of your screens gets disconnected your windows should stay in the now hidden area? I agree that I feel annoyed at times as well when I connect a screen and suddenly all windows are on the other screen. But today it moved all windows there that used to be before I had shut down the monitor for a moment. And that was really convenient in this case. In any case it's a KWin bug/feature request. Moving. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 418739] tablet mode value is wrong in kded
https://bugs.kde.org/show_bug.cgi?id=418739 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 324657] Chosen position of displays should be remembered even for those which are "off".
https://bugs.kde.org/show_bug.cgi?id=324657 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #4 from Roman Gilg --- Some heuristic can be implemented to try to reposition like before. There is some function stubs in the code not yet complete. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 418244] plasmashell segmentation fault in KScreen::GetConfigOperation::start when logging into Plasma 5.18.2 on Wayland
https://bugs.kde.org/show_bug.cgi?id=418244 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED CC||subd...@gmail.com Resolution|--- |FIXED --- Comment #4 from Roman Gilg --- Closed as fixed as reported -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 417323] iGPU multi-monitor support missing
https://bugs.kde.org/show_bug.cgi?id=417323 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- You are using wayland? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 417490] Plasma 5.18.0 resets display XRandR scaling after logon
https://bugs.kde.org/show_bug.cgi?id=417490 Roman Gilg changed: What|Removed |Added Resolution|NOT A BUG |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #8 from Roman Gilg --- Let's reopen it for feedback and maybe someone finds a simple solution for it. Personally I won't work on a fix though. Could the KScreen daemon binary be diverted / renamed? You won't be able to use the ui afterwards but since you are using xrandr anyway. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416566] kded5 segmentation faults in KWayland::Client::OutputManagement::createConfiguration when logging into Plasma 5.17.90 on Wayland
https://bugs.kde.org/show_bug.cgi?id=416566 --- Comment #4 from Roman Gilg --- Do you have a device with orientation sensor and the iio-sensor-proxy package installed? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416566] kded5 segmentation faults in KWayland::Client::OutputManagement::createConfiguration when logging into Plasma 5.17.90 on Wayland
https://bugs.kde.org/show_bug.cgi?id=416566 Roman Gilg changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #3 from Roman Gilg --- *** Bug 416961 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416961] kde5 crashed immediately after login to Wayland session
https://bugs.kde.org/show_bug.cgi?id=416961 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Roman Gilg --- *** This bug has been marked as a duplicate of bug 416566 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416961] kde5 crashed immediately after login to Wayland session
https://bugs.kde.org/show_bug.cgi?id=416961 --- Comment #4 from Roman Gilg --- m_outputManagement is not yet set when this crash happens. Should not be happening in theory because applyConfig should only be called after it got set. Sometimes it's called before that apparently. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416961] kde5 crashed immediately after login to Wayland session
https://bugs.kde.org/show_bug.cgi?id=416961 --- Comment #3 from Roman Gilg --- Ok, similar backtrace? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416961] kde5 crashed immediately after login to Wayland session
https://bugs.kde.org/show_bug.cgi?id=416961 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- Still a problem after release? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416566] kded5 segmentation faults in KWayland::Client::OutputManagement::createConfiguration when logging into Plasma 5.17.90 on Wayland
https://bugs.kde.org/show_bug.cgi?id=416566 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- After release still happening? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 417490] Plasma 5.18.0 resets display XRandR scaling after logon
https://bugs.kde.org/show_bug.cgi?id=417490 Roman Gilg changed: What|Removed |Added CC||m...@bearsh.org --- Comment #3 from Roman Gilg --- *** Bug 417541 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 417541] kscreen resets per screen scaling factor
https://bugs.kde.org/show_bug.cgi?id=417541 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED CC||subd...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Roman Gilg --- *** This bug has been marked as a duplicate of bug 417490 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 417490] Plasma 5.18.0 resets display XRandR scaling after logon
https://bugs.kde.org/show_bug.cgi?id=417490 Roman Gilg changed: What|Removed |Added Component|xrandr |libkscreen Assignee|kwin-bugs-n...@kde.org |kscreen-bugs-n...@kde.org Product|kwin|KScreen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417490] Plasma 5.18.0 resets display XRandR scaling after logon
https://bugs.kde.org/show_bug.cgi?id=417490 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Roman Gilg --- Transform is set in https://cgit.kde.org/libkscreen.git/tree/backends/xrandr/xrandroutput.cpp#n392. Normally this is set to identity matrix, but if one output is replicated it might be set differently such that the output fits the into the replica. If you have some manual scripting going on you can try to reapply it after KScreen daemon has done its work. In general KScreen can't respect manual scripting and will just override such efforts when it applies its own settings via X11 protocol. What could be a goal is to allow setting the scale individually for outputs in KScreen via transform matrices. But it's not on my priority list right now. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416978] kscreen settings with hashes are not stored correctly for all screens
https://bugs.kde.org/show_bug.cgi?id=416978 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- The positions are saved in the overall configuration files in .local/share/kscreen an not in the subdirectory ../outputs. Can you identify the config file of the triple-setup and share the content before and after reboot? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413109] After I change the screen resolution on Wayland, Kscreen shows the initial resolution on reopening
https://bugs.kde.org/show_bug.cgi?id=413109 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #3 from Roman Gilg --- Thanks for update! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06
https://bugs.kde.org/show_bug.cgi?id=415313 Roman Gilg changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 --- Comment #8 from Roman Gilg --- After deletion of the files the problem is solved or is the configuration still corrupted on reboot? Just to make clear that the screens are "mirrored" is not what you want, right? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416501] Compositing prevents laptop to wake up from sleep state
https://bugs.kde.org/show_bug.cgi?id=416501 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #3 from Roman Gilg --- Can you switch VT via Ctrl+Alt+F# key combination and then check if XServer and/or KWin are running and restart KWin via DISPLAY=:0 kwin_x11? Also try it with Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416430] Plasma 5.18 beta does not save screen layout after reboot
https://bugs.kde.org/show_bug.cgi?id=416430 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #4 from Roman Gilg --- How do the files in $HOME/.local/share/kscreen change before and after reboot? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416475] Display Configuration not saved properly on Wayland with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=416475 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- With X11 you don't have this issue? Settings are saved normally in $HOME/.local/share/kscreen Check there how the files look before and after reboot. Also please create two screenshots of the KCM before and after reboot. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344433] SceneOpenGL::paint() occasionally lasts > 16ms (triple buffering enabled)
https://bugs.kde.org/show_bug.cgi?id=344433 --- Comment #33 from Roman Gilg --- Sorry for not having the patches in 5.18. The patchset is not dead. In my opinion it was fine, but there are organizational issues with KWin development I want to have solved before I commit myself to any more large changes like this that also always induce the risk of breaking things. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416147] kwin_wayland segmentation faults and black screen when logging out of Plasma on Wayland
https://bugs.kde.org/show_bug.cgi?id=416147 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389551] kwin_wayland crash when monitor is switched off (or input is changed)
https://bugs.kde.org/show_bug.cgi?id=389551 Roman Gilg changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/2632e4182c658178af82be175 ||575b094002468af --- Comment #13 from Roman Gilg --- Git commit 2632e4182c658178af82be175575b094002468af by Roman Gilg. Committed on 08/01/2020 at 09:12. Pushed by romangilg into branch 'master'. [platforms/drm] Allow running without outputs Summary: Set outputs enablement also when none outputs are present. This patch is similar to earlier attempt at D17985. Related: bug 402827, bug 398680, bug 413758 Test Plan: Starting without outputs, manual disconnects and DPMS changes. There is still an issue when an output gets disconnected while the DPMS is off. But it's an improvement already. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Maniphest Tasks: T10016 Differential Revision: https://phabricator.kde.org/D26511 M +2-6plugins/platforms/drm/drm_backend.cpp https://commits.kde.org/kwin/2632e4182c658178af82be175575b094002468af -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413758] KWin_wayland crashes when an external display is unplugged
https://bugs.kde.org/show_bug.cgi?id=413758 Roman Gilg changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kwi ||n/2632e4182c658178af82be175 ||575b094002468af Status|REPORTED|RESOLVED --- Comment #6 from Roman Gilg --- Git commit 2632e4182c658178af82be175575b094002468af by Roman Gilg. Committed on 08/01/2020 at 09:12. Pushed by romangilg into branch 'master'. [platforms/drm] Allow running without outputs Summary: Set outputs enablement also when none outputs are present. This patch is similar to earlier attempt at D17985. Related: bug 402827, bug 389551, bug 398680 Test Plan: Starting without outputs, manual disconnects and DPMS changes. There is still an issue when an output gets disconnected while the DPMS is off. But it's an improvement already. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Maniphest Tasks: T10016 Differential Revision: https://phabricator.kde.org/D26511 M +2-6plugins/platforms/drm/drm_backend.cpp https://commits.kde.org/kwin/2632e4182c658178af82be175575b094002468af -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kwi ||n/2632e4182c658178af82be175 ||575b094002468af --- Comment #23 from Roman Gilg --- Git commit 2632e4182c658178af82be175575b094002468af by Roman Gilg. Committed on 08/01/2020 at 09:12. Pushed by romangilg into branch 'master'. [platforms/drm] Allow running without outputs Summary: Set outputs enablement also when none outputs are present. This patch is similar to earlier attempt at D17985. Related: bug 389551, bug 398680, bug 413758 Test Plan: Starting without outputs, manual disconnects and DPMS changes. There is still an issue when an output gets disconnected while the DPMS is off. But it's an improvement already. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Maniphest Tasks: T10016 Differential Revision: https://phabricator.kde.org/D26511 M +2-6plugins/platforms/drm/drm_backend.cpp https://commits.kde.org/kwin/2632e4182c658178af82be175575b094002468af -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398680] Wayland session is unusable (black screen) when monitor is reconnected to hdmi port after energy saving timeout
https://bugs.kde.org/show_bug.cgi?id=398680 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/2632e4182c658178af82be175 ||575b094002468af Resolution|--- |FIXED --- Comment #4 from Roman Gilg --- Git commit 2632e4182c658178af82be175575b094002468af by Roman Gilg. Committed on 08/01/2020 at 09:12. Pushed by romangilg into branch 'master'. [platforms/drm] Allow running without outputs Summary: Set outputs enablement also when none outputs are present. This patch is similar to earlier attempt at D17985. Related: bug 402827, bug 389551, bug 413758 Test Plan: Starting without outputs, manual disconnects and DPMS changes. There is still an issue when an output gets disconnected while the DPMS is off. But it's an improvement already. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Maniphest Tasks: T10016 Differential Revision: https://phabricator.kde.org/D26511 M +2-6plugins/platforms/drm/drm_backend.cpp https://commits.kde.org/kwin/2632e4182c658178af82be175575b094002468af -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396711] Feature request: disable display hotplug (KWin Wayland)
https://bugs.kde.org/show_bug.cgi?id=396711 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #4 from Roman Gilg --- What is meant by "removing input"? This doesn't sound like a bug that is very common. Closing for now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415750] KWin crashes randomly
https://bugs.kde.org/show_bug.cgi?id=415750 Roman Gilg changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from Roman Gilg --- *** Bug 415824 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415824] Assert in composite.cpp
https://bugs.kde.org/show_bug.cgi?id=415824 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED CC||subd...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Roman Gilg --- *** This bug has been marked as a duplicate of bug 415750 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415798] [Wayland] task switcher is black after changing
https://bugs.kde.org/show_bug.cgi?id=415798 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- I think when you restart the session the task manager is not black anymore. Can you confirm? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415750] KWin crashes randomly
https://bugs.kde.org/show_bug.cgi?id=415750 Roman Gilg changed: What|Removed |Added Latest Commit||https://commits.kde.org/kwi ||n/af3fbf343bb234d2205c17451 ||4ddfd61d52ebb5b Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Roman Gilg --- Git commit af3fbf343bb234d2205c174514ddfd61d52ebb5b by Roman Gilg. Committed on 31/12/2019 at 19:34. Pushed by romangilg into branch 'master'. Remove buffer flip pending assert for now The assert is still not always true. M +3-1composite.cpp https://commits.kde.org/kwin/af3fbf343bb234d2205c174514ddfd61d52ebb5b -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 167879] Multihead support is hard to set up
https://bugs.kde.org/show_bug.cgi?id=167879 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||subd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland while numlock is enabled
https://bugs.kde.org/show_bug.cgi?id=400658 Roman Gilg changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.18.0 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kwi ||n/514a95f1e43cb0a694850d946 ||b36c91c3e86fa9d --- Comment #29 from Roman Gilg --- Git commit 514a95f1e43cb0a694850d946b36c91c3e86fa9d by Roman Gilg. Committed on 30/12/2019 at 13:41. Pushed by romangilg into branch 'master'. Set Qt::KeypadModifier depending on current keysym Summary: The Qt::KeypadModifier should only accompany a keysym when this specific keysym originates from the keypad not in general for every keysym while numlock is engaged. FIXED-IN: 5.18.0 Test Plan: Manually with the Thumbnail Grid task switcher and numlock enabled. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D26283 M +1-1xkb.cpp M +7-2xkb_qt_mapping.h https://commits.kde.org/kwin/514a95f1e43cb0a694850d946b36c91c3e86fa9d -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415672] Add D-Bus control interface for Night Color
https://bugs.kde.org/show_bug.cgi?id=415672 Roman Gilg changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- There is already a d-bus interface (in KWin) you can use to control from widget or other apps. That's what the KCM uses as well by the way. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 415683] KSettings > Screen Rotation doesn't rotate touchscreen & generates xinput error
https://bugs.kde.org/show_bug.cgi?id=415683 Roman Gilg changed: What|Removed |Added Keywords||junior-jobs --- Comment #1 from Roman Gilg --- I noticed this as well. I'm currently adding auto rotation support, but that's primarily aimed at Wayland. See series at https://phabricator.kde.org/D26038. To be frank I don't know if I find the time to look into adding the rotation matrix for input devices to libkscreen's RandR backend. If you want to take a look at it feel free to submit a patch. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 415683] KSettings > Screen Rotation doesn't rotate touchscreen & generates xinput error
https://bugs.kde.org/show_bug.cgi?id=415683 Roman Gilg changed: What|Removed |Added Component|kcm_kwintouchscreen |libkscreen CC||subd...@gmail.com Product|systemsettings |KScreen Assignee|kwin-bugs-n...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415286] KWin compositing makes Proton fullscreen games freeze after alt + tab
https://bugs.kde.org/show_bug.cgi?id=415286 --- Comment #14 from Roman Gilg --- (In reply to tempel.julian from comment #12) > Forgot to add: The Proton fullscreen application also freezes with KWin's > default settings when executing "kwin_x11 --replace" while the application > is running. This in contrast is still happening to me. But taking away the compositor while the game is running is quite drastic and handling that is probably not been done correctly in Proton in this case (and I don't think it's worth for them to look into fixing that). On another note: I didn't notice any performance difference between having the compositor block compositing and with full compositing still going on while in-game, what would point to the compositing rework being done right. Can you confirm? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415286] KWin compositing makes Proton fullscreen games freeze after alt + tab
https://bugs.kde.org/show_bug.cgi?id=415286 --- Comment #13 from Roman Gilg --- I tried it out now with https://phabricator.kde.org/D26216 being applied on top of master and alt-tabbing in and out of Dishonored 2 worked without problems for me in the tutorial starting area. System was an AMD RX 5700 XT, MESA (close to) master, Linux kernel 5.4.6. This was independent of me enabling that apps can block compositing or switching on/off compositing mid-game. Could you test if there are still problems for you with the above patch applied? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06
https://bugs.kde.org/show_bug.cgi?id=415313 --- Comment #6 from Roman Gilg --- (In reply to Duncan from comment #5) > FWIW, kwin master as of 054cfc1c8 seems to be /vastly/ improved, altho not > /quite/ back to where it was. I'd say 75-80% (aka 3/4 to 4/5) of the > original regression performance loss has been regained. > > I can run all my usual effects now, but still noticed a bit of slow-down > until I tweaked configs a bit, adjusting the wobbly-windows config for > normal windows and bumping animation speed (workspace behavior, general > behavior, animation speed slider) for plasma (autohide panel showing speed, > panel plasmoid hover popup morphing speed). > > It's fast enough now if I was new to plasma I'd never suspect the regression > and would just tweak things if the default seemed slow until they worked as > I wanted, and it's only that I had it tuned to what I wanted before and it > was still slightly too slow with that config that hints at the far greater > regression before. > > (In reply to Roman Gilg from comment #4) > > Please check out if this solves the problem for you: > > https://phabricator.kde.org/D26216 > > I take it that's not yet applied to master? Do I still need to try it? > And/or would bisecting the commit at which I got most of the performance > back still help? Yea, not yet applied. Would be great if you could try it. I noticed some slow downs as well now after more testing with certain configurations and this patch should help with them. Can you apply it to the top of KWin master? > (While fiddling with the config I noticed the FPS effect once again. Too > bad I didn't think to try enabling it when kwin was lagging out so badly. > It'd have been nice to get real numbers, tho of course I still could by > pinning the bad commit and rebuilding...) The numbers of the FPS effect are not that reliable. Actually currently I test often with: https://www.testufo.com/animation-time-graph https://www.vsynctester.com/ > (My regular updates included a gcc-9.2.0 gentoo patch revision early in the > update sequence, a mesa update from 19.3.0 to 19.3.1, and an llvm and clang > update from 9.0.1-rc3 to 9.0.1 release, of interest given their usage with > amdgpu for shader-compiling, etc. While kwin's 00bf75d06 commit did indeed > regress something, it's possible that it was only as severe as I was seeing > due to a bug in one of the above packages and that updating that package, > not a kwin commit since then-head d72e96802, gave me back most of what I saw > lost in that regression.) > > I've a couple more days off due to Christmas, and (if only for my own > curiosity) may well do some more rebuild testing to pin down exactly what > gave me that performance back, as well as testing D26216, but FWIW it's > definitely workable now and as such I'd be OK with closing the bug, even if > I didn't get 100% of the pre-regression performance back. It's good to hear that it feels better now. Thank you for the feedback. But check out the patch D26216 above if it improves the situation even more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392693] [wayland] - Blur effect isnt applied under wayland
https://bugs.kde.org/show_bug.cgi?id=392693 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #26 from Roman Gilg --- (In reply to Andrius Štikonas from comment #25) > When I upgraded to Plasma 5.17.4 (from Plasma 5.16.5) blur is now applied on > my system. Can you confirm Michail that the issue is gone in most recent version of Plasma for you too? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06
https://bugs.kde.org/show_bug.cgi?id=415313 --- Comment #4 from Roman Gilg --- Hey Duncan, I cleaned up the compositing path a bit more and fixed an oversight in regards to swap events not being received if the buffer age extension is not available. Please check out if this solves the problem for you: https://phabricator.kde.org/D26216 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415262] KWin compositing freezes under certain circumstances since recent overhaul
https://bugs.kde.org/show_bug.cgi?id=415262 Roman Gilg changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/ba2c0324d2ef21a5c42ec182e ||851a435180b51ac --- Comment #10 from Roman Gilg --- Git commit ba2c0324d2ef21a5c42ec182e851a435180b51ac by Roman Gilg. Committed on 23/12/2019 at 22:55. Pushed by romangilg into branch 'master'. Reset buffer swap state on stop Summary: When the compositor is stopped there might still be a buffer swap ongoing, in particular when a client blocks compositing on X11. Depending on the backend the next buffer swap event might be handled in bufferSwapComplete (Wayland) or not be handled (X11 GLX, since a new GLX window will be created while the swap event is sent for the old one). With this patch the buffer swap state is reset on stop such that on later start no outdated data might create errors and instead a new repaint can be triggered with updated data. Test Plan: Manually on X11 and Wayland. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D26090 M +5-6composite.cpp https://commits.kde.org/kwin/ba2c0324d2ef21a5c42ec182e851a435180b51ac -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06
https://bugs.kde.org/show_bug.cgi?id=415313 --- Comment #3 from Roman Gilg --- Thanks for giving detailed information. :) I was testing it with an RX 5700 XT (Navi) on Mesa master. What you could do is running Hotspot to see if there are CPU cycles being burned somewhere unnecessarily: https://github.com/KDAB/hotspot A second tool you could try out is GPUVis to see when the frames actually hit the screen (and insert some debug statements for finer analysis): https://github.com/mikesart/gpuvis But for that you would need to recompile KWin with following wip-patch applied: https://phabricator.kde.org/D23114 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06
https://bugs.kde.org/show_bug.cgi?id=415313 Roman Gilg changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Roman Gilg --- Thanks for your report. I just tried on Intel and AMD graphics and was not able to reproduce the issue with Wobbly Windows or Zoom. Can you give me a step-by-step rundown on how to reproduce it? Do I need to have a certain load on the CPU or GPU? I have a single 4K monitor connected. Do you experience the issue only when both your 4K monitors are connected or also with only one connected? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415262] KWin compositing freezes under certain circumstances since recent overhaul
https://bugs.kde.org/show_bug.cgi?id=415262 --- Comment #8 from Roman Gilg --- I have cleaned up / reformulated the patch. Could you test this patch one more time if it works for you like the previous poc one? Thanks! https://phabricator.kde.org/D26090 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415286] KWin compositing makes Proton fullscreen games freeze after alt + tab
https://bugs.kde.org/show_bug.cgi?id=415286 --- Comment #9 from Roman Gilg --- (In reply to tempel.julian from comment #8) > Found the cause of the issue: It sits in front of my PC. > The issue is caused by setting KWin to always keep window thumbnails, not > just for shown windows. Good find. It's still an issue but this restricts the search area and it might make sense to ignore the issue since it is a rather special case. But does this issue also occur without the recent compositing overhaul? If no, we should try to fix the regression for sure. > At this occasion, I also found out that the Proton fullscreen hack also > automatically tells KWin to resume compositing when minimizing a game. > Though e.g. the native Linux port of Shadow of the Tomb Raider by Feral > doesn't do this. Also interesting. Didn't know that Proton does this automatically but other (major) players like Feral don't. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06
https://bugs.kde.org/show_bug.cgi?id=415313 Roman Gilg changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |subd...@gmail.com CC||subd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415286] KWin compositing makes Proton fullscreen games freeze after alt + tab
https://bugs.kde.org/show_bug.cgi?id=415286 Roman Gilg changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Assignee|kwin-bugs-n...@kde.org |subd...@gmail.com Resolution|NOT A BUG |--- --- Comment #6 from Roman Gilg --- (In reply to tempel.julian from comment #5) > I think you misunderstood: It's unrelated to toggling compositing. It also > breaks as long as compositing is just enabled, compositing is never toggled > during the process. Normally on games composition is auto-toggled (as you know instead of unredirect) so you are sure composition does not get toggled off automatically? Anyway I will investigate a bit more later today. I don't think it's necessarily the game's fault. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 415309] Crash in logout-greeter
https://bugs.kde.org/show_bug.cgi?id=415309 --- Comment #2 from Roman Gilg --- Thanks for looking it up, must update my system apparently. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 415309] New: Crash in logout-greeter
https://bugs.kde.org/show_bug.cgi?id=415309 Bug ID: 415309 Summary: Crash in logout-greeter Product: ksmserver Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ui Assignee: unassigned-b...@kde.org Reporter: subd...@gmail.com Target Milestone: --- Created attachment 124566 --> https://bugs.kde.org/attachment.cgi?id=124566=edit Backtrace Qt 5.14 Assert through Plasma Framework's declarativeimports/core/colorscope is triggered. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415308] New: Default leave option in Desktop Session KCM wrong
https://bugs.kde.org/show_bug.cgi?id=415308 Bug ID: 415308 Summary: Default leave option in Desktop Session KCM wrong Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: subd...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Selecting the "Turn off computer" option actually preselects the "Restart computer" one on the leave screen and vice versa. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415286] KWin compositing makes Proton fullscreen games freeze after alt + tab
https://bugs.kde.org/show_bug.cgi?id=415286 Roman Gilg changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- CC||subd...@gmail.com --- Comment #3 from Roman Gilg --- Info was provided. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415262] KWin compositing freezes under certain circumstances since recent overhaul
https://bugs.kde.org/show_bug.cgi?id=415262 --- Comment #5 from Roman Gilg --- (In reply to tempel.julian from comment #4) > I can confirm that your patch fixes the issue for me. > Finally I'll be able to recommend Plasma without turning off KWin > compositing, thanks for your efforts! :) Thanks for testing! Early feedback like yours is super helpful. Would be great of course if you could stay on master in the future to continue with feedback if something breaks and by that shield inexperienced users from bugs they would not able to recover from on their own. :) I need to look into the code some more for a final patch. The above one was just done rather quickly to test the assumption. > Though I really wished you guys would reconsider implementing fullscreen > unredirect. I've been using it for two years inside Plasma via Compton/Picom > and it works just totally reliably, while it is much more comfortable than > KWin's suspend compositing feature. It also seems to work fine in Gnome. I understand your sentiment but from my perspective I would need to dig into how exactly unredirect is supposed to be implemented and even then to my knowledge there are certain structural constraints of unredirect that make it a subpar experience. On the other side we have the Wayland session where in the future we will be able to do an optimal direct scanout of client buffers and on the other side still have lots of other things to do to make it work on every user install without issues. So I would like our devs to concentrate on improving that rather. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415262] KWin compositing freezes under certain circumstances since recent overhaul
https://bugs.kde.org/show_bug.cgi?id=415262 --- Comment #3 from Roman Gilg --- Created attachment 124538 --> https://bugs.kde.org/attachment.cgi?id=124538=edit poc patch I can reproduce on Intel. The issue lies in the swap event not being registered correctly after compositing went down while a page flip is ongoing (probability for that high when often changing content on the screen like a game). Please compile KWin with the attached proof-of-concept patch and see if that solves the issues for you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344433] SceneOpenGL::paint() occasionally lasts > 16ms (triple buffering enabled)
https://bugs.kde.org/show_bug.cgi?id=344433 --- Comment #28 from Roman Gilg --- (In reply to Michael Marley from comment #27) > So I have done some more testing and I have found that the > frame-rate-halving issue I reported with KWIN_USE_INTEL_SWAP_EVENT earlier > affects only that one system and none of my others. On the others, the > result is actually rather amazing, dramatically reducing input lag and > stuttering and eliminating micro-stuttering. For that one problematic > system, I have also had other frame rate and stuttering-related issues, so I > think there must be something specific to that system. Sorry for the noise, > and again, thanks for the work! Thank you, but if I understood you correctly you were testing it with 5.17 on these systems, right? Or did you test it with KWin from master branch? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415262] KWin compositing freezes under certain circumstances since recent overhaul
https://bugs.kde.org/show_bug.cgi?id=415262 Roman Gilg changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |subd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415262] KWin compositing freezes under certain circumstances since recent overhaul
https://bugs.kde.org/show_bug.cgi?id=415262 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #1 from Roman Gilg --- * Which Vulkan game specifically? * Does the issue persist when you start KWin with the envvar KWIN_USE_INTEL_SWAP_EVENT set to 0, i.e.: > $ KWIN_USE_INTEL_SWAP_EVENT=0 kwin_x11 --replace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344433] SceneOpenGL::paint() occasionally lasts > 16ms (triple buffering enabled)
https://bugs.kde.org/show_bug.cgi?id=344433 --- Comment #25 from Roman Gilg --- (In reply to tempel.julian from comment #24) > Could instantly make it freeze by starting a fullscreen game, turning > compositing off via hotkey and then re-enable it. Thanks for testing! Please open a new bug report for that and mention what hardware you are testing it with. I will try to reproduce it asap. There were a multitude of changes to the compositing pipeline so it might be unrelated to intel swap event. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344433] SceneOpenGL::paint() occasionally lasts > 16ms (triple buffering enabled)
https://bugs.kde.org/show_bug.cgi?id=344433 --- Comment #21 from Roman Gilg --- (In reply to Michael Marley from comment #20) > That sounds awesome, thanks for the work! I do have one question though. I > noticed in there one of the changes you made was to make > KWIN_USE_INTEL_SWAP_EVENT default to 1. I have actually tried this with > 5.17.x and it usually makes my framerate fall to 30 or 40 FPS instead of 60. > Has the rest of your work fixed that, or will I have to force it back off? The compositing pipeline has been fully overhauled so you can't guess from 5.17 behavior to how it will work in 5.18. Of course if you can try it on master and report back if it's fine there or you have a similar problem, that would be very helpful. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344433] SceneOpenGL::paint() occasionally lasts > 16ms (triple buffering enabled)
https://bugs.kde.org/show_bug.cgi?id=344433 --- Comment #19 from Roman Gilg --- Yea, you need other projects to be built from master as well. It's easy for example on KDE Neon Dev Unstable edition and Manjaro with kwin-git package. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344433] SceneOpenGL::paint() occasionally lasts > 16ms (triple buffering enabled)
https://bugs.kde.org/show_bug.cgi?id=344433 Roman Gilg changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||subd...@gmail.com Resolution|--- |FIXED --- Comment #17 from Roman Gilg --- This issue should be solved in 5.18 with patches in: https://phabricator.kde.org/T11071. There will be no more KWin "triple buffering" available, instead everything hopefully just works right away without any configuration necessary. If it doesn't reopen. You can also build KWin from master to test the current state. (there is one patch missing yet though for optimizing the Nvidia case). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland while numlock is enabled
https://bugs.kde.org/show_bug.cgi?id=400658 Roman Gilg changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |subd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 342582] Intel hd 4600 + OpenGL + kwin = can't load
https://bugs.kde.org/show_bug.cgi?id=342582 --- Comment #34 from Roman Gilg --- Git commit e7da4d65ecbd7dea164a86aa355632ffe156e6c4 by Roman Gilg. Committed on 12/12/2019 at 00:57. Pushed by romangilg into branch 'master'. [platforms/x11/standalone] Use intel swap events by default Summary: Activate intel swap events by default if available. They were hidden behind an environmental variable because of some critical release blocking issue years ago. Manual testing indicates that there are no issues anymore with this extension. Since it allows us to use swap events with MESA drivers for optimized repaints enable swap events by default again. For now leave a modified environment variable to switch back to using no swap events easily. Test Plan: i915 Reviewers: #kwin Subscribers: zzag, broulik, kwin Tags: #kwin Maniphest Tasks: T11071 Differential Revision: https://phabricator.kde.org/D25300 M +3-2plugins/platforms/x11/standalone/glxbackend.cpp https://commits.kde.org/kwin/e7da4d65ecbd7dea164a86aa355632ffe156e6c4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413758] KWin_wayland crashes when an external display is unplugged
https://bugs.kde.org/show_bug.cgi?id=413758 --- Comment #5 from Roman Gilg --- Thanks, can you still reproduce? From the backtrace it seems it tries to access in https://cgit.kde.org/kwin.git/tree/plugins/platforms/drm/egl_gbm_backend.cpp?h=Plasma/5.17#n352 an output property, but this output does not exist anymore. Since you have the laptop disabled and the other screen disconnected I guess there is a short time where no output is active and we have the problem as in: https://phabricator.kde.org/T10016 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404710] Segmentation fault at KWin::ModifierOnlyShortcuts::keyEvent
https://bugs.kde.org/show_bug.cgi?id=404710 Roman Gilg changed: What|Removed |Added Platform|Archlinux Packages |Compiled Sources Version|5.15.1 |git master -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404710] Segmentation fault at KWin::ModifierOnlyShortcuts::keyEvent
https://bugs.kde.org/show_bug.cgi?id=404710 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #4 from Roman Gilg --- Created attachment 124433 --> https://bugs.kde.org/attachment.cgi?id=124433=edit Backtrace Had unrelated to that the debugger running and something similar happened on logout. Backtrace attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404710] Segmentation fault at KWin::ModifierOnlyShortcuts::keyEvent
https://bugs.kde.org/show_bug.cgi?id=404710 Roman Gilg changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371877] Support for keyboard_shortcuts_inhibit_unstable_v1 needed
https://bugs.kde.org/show_bug.cgi?id=371877 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #23 from Roman Gilg --- How difficult is implementing this would you say? Maybe it could be a Google Summer of Code project. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406491] [wayland] neither primary selection neither copy paste working
https://bugs.kde.org/show_bug.cgi?id=406491 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #6 from Roman Gilg --- This is still not specific enough. Please name example applications and at best ways a way/path of action to trigger the issue reliably. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389665] Rotating screen doesn't work on wayland
https://bugs.kde.org/show_bug.cgi?id=389665 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com Assignee|kwin-bugs-n...@kde.org |subd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
