https://bugs.kde.org/show_bug.cgi?id=429168
Duncan <1i5t5.dun...@cox.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #7 from Duncan <1i5t5.dun...@cox.net> ---
(In reply to David Edmundson from comment #6)
>
> It's a likely guess. Debug of plasmashell should tell you.
"Debug of plasmashell" means?
I did try restarting plasmashell from the terminal to get its output, both with
and without a taskmanager plasmoid. Lots of noise from other stuff (comic
plasmoid seems to be the worst, well, that and complaints about missing
udisks2, see below) that appeared in both. But diffing the output I /did/ see
one different message that /might/ be relevant:
org.kde.kf5.kwindowsystem.kwayland: This compositor does not support the Plasma
Window Management interface
Or did you mean turning on kdebug in kdebugdialog5 or kdebugsettings? If so
which one and which settings, and then do I get the debug info from terminal
output or the journal/syslog or a log file somewhere in /home/?
Or did you mean rebuilding with debug enabled (just plasma-workspace?) and
running gdb?
Or...?
> Our sharing arrangement is done by keys in the .desktop file and matching
> paths. Please confirm if everything is installed to /usr and without any
> other quirks.
It's "installed" to /usr, but there are indeed a few quirks, two of which I
could imagine having some effect here.
The first (since you mentioned /usr) is that I have a "reverse-usr-merge", that
being a /usr -> . symlink so the canonical path for everything normally found
in /usr is / instead (but still findable in /usr via the symlink). But with
the symlink that normally causes no problems and I doubt it is here either.
(I also have $XDG_CONFIG_HOME and $XDG_DATA_HOME set, and $HOME itself is a
non-standard location, but not only are the envvars set but I have symlinks
from the standard locations as well, so that shouldn't be a problem either.)
What I'm more thinking, however, starts with the fact that I have a pretty
"lite" plasma install here, no baloo or semantic-desktop, no polkit, no
udisks2, etc.
In the past I've found that kwalletmanager5 will show me the kwallet settings
but not allow me to edit them in the GUI, presumably because it thinks it needs
polkit, despite the fact that the kwalletrc file it presumably writes to is
perfectly read-writable and thus text-editable by my same user! So I had to
first find that file (luckily not hard as I'm reasonably familiar with kde's
config layout), then ddg/google the settings I wanted to change so as to be
sure I got the format correct when textediting it.
So now that I know plasmashell apparently has access to the window list for
other wayland users, despite that information not normally being available to
wayland apps other than the compositor, I'm wondering if the reason I'm not
seeing it here is a similar polkit-moderated permissions issue for stuff I
really should have access to as my normal user anyway, just as seems to be the
case with kwalletmanager5. But polkit is a rather expensive dep to pull in
just to test a dependency theory, 8 new packages plus rebuilding systemd with
polkit support, including spidermonkey, which IIRC from when I last had it
merged, isn't a trivial build.
--
You are receiving this mail because:
You are watching all bug changes.
