https://bugs.kde.org/show_bug.cgi?id=475318
--- Comment #7 from Stephane Travostino <s...@combo.cc> --- The issue I have with RuneLite is with forced window rules, the one with Darkwood is regular game fullscreen mode. In any case, here it is: ``` [$Version] update_info=kwinrules.upd:replace-placement-string-to-enum,kwinrules.upd:use-virtual-desktop-ids [02c47812-75a8-4cc1-a20c-8cb86eb38c2a] Description=Window settings for net-runelite-client-runelite clientmachine=localhost noborder=true noborderrule=3 title=RuneLite titlematch=1 types=1 wmclass=net-runelite-client-runelite wmclassmatch=1 [1] Description=Window settings for net-runelite-client-runelite clientmachine=localhost fullscreen=true fullscreenrule=3 title=RuneLite titlematch=1 types=1 wmclass=net-runelite-client-runelite wmclassmatch=1 [General] count=1 rules=1 ``` On Fri, 13 Oct 2023, at 20:37, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=475318 > > Nate Graham <n...@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Component|general |rules > Summary|Often unable to open |Often unable to open > |application menu, access |application menu, access > |taskbar or switch away from |taskbar, or switch away > |fullscreen application. |from window forced into > | |full screen mode using > | |Window Rules > CC| |isma...@gmail.com > > --- Comment #6 from Nate Graham <n...@kde.org> --- > Can you open up the ~/.config/kwinrulesrc file, find the entry for the window > rule that's forcing one of the problematic windows to be fullscreen, and > copy-and-paste it into here? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
