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

            Bug ID: 393788
           Summary: Window rules editing broken
           Product: kwin
           Version: git master
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: rules
          Assignee: kwin-bugs-n...@kde.org
          Reporter: 1i5t5.dun...@cox.net
  Target Milestone: ---

The window rules kcm GUI won't save changes.  It will load existing rules from
kwinrulesrc (as does kwin itself) and changes will appear to save -- hitting
the apply button causes it to go inactive, but:
1) kwin doesn't actually act on them (even after hitting apply).
2) switching to another kcm (say kwin scripts) and back to window rules, the
changes were not saved and I get the same rule as when I loaded it the first
time.
3) kwinrulesrc isn't actually changed (yes, it's appropriate 0600 perms).

Running gentoo/kde's live-git of frameworks and plasma as well.  Currently
running qt-5.11.0_beta4 as plasma-live-git is now requiring > 5.10, and gentoo
doesn't have 5.10 in-tree, only 5.11_beta4.  However, this bug triggered before
that upgrade.

This has apparently been broken in kwin on X at least for months, as when I
unmerged superkaramba (my last kde4 app, so I could unmerge kde4/qt4, still
nothing with superkaramba's full set of features for plasma5 that I can find,
but this bug isn't about that...) and setup ksysguard graphing to replace what
I could of superkaramba, I ended up having to manually edit kwinrulesrc in
ordered to get a working rule for ksysguard, and that was a couple months ago
or so.  I have a somewhat large but reasonably stable set of kwin window rules
and hadn't needed to edit any of them for some time before that, so I've no
idea how long it has actually been broken.

Fortunately, I can still edit the kwinrulesrc file manually and the changes do
take (after restarting kde/plasma, and I think after simply running kwin_x11
--replace, tho I'd have to check that again to be sure), but it'd sure be nice
to have a working GUI editor back again!

(The current trigger to file the bug was full-screening a game that changed the
resolution and left the desktop a mess.  I quit and restarted kde/plasma/X, and
got the desktop back, but firefox restarted at 0,15 which on my multi-monitor
setup is offscreen.  I tried to edit an existing window rule for it to
reposition it onscreen, but found the GUI editor still not saving changes, so
that didn't work.  Fortunately I have wmctrl installed, and a wmctrl -R firefox
did the trick!)

I suppose none of the devs have seen it due to running wayland these days.

(BTW, is plasma-wayland usable now, and can you point me at a good article
describing how to configure it analogous to xorg.conf.d?  Or is the only way to
configure plasma-wayland via the plasma-wayland GUI?  I haven't had much luck
with multi-monitor config GUIs such as kscreen on X/kde/plasma -- while they do
work sometimes, they're often broken bad enough to be unusable (leaving me with
a sufficiently broken desktop that I must restart X/kde/plasma, I had to
studiously avoid that kcm for awhile, as even opening it would screw things
up!), so I tend to avoid them, and while xrandr has at least worked more
consistently, simply configuring the layout in xorg.conf.d and not touching it
from the GUI has been most reliable.  So you can see why I'm hoping there's a
wayland analog to xorg.conf.d, despite my not seeing /anything/ about it in the
various Linux-related news feeds I follow.  So a link to a good article on the
topic would be extremely useful!)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to