Hello Jessie,

On 2024-08-16 10:42, Jesse Rhodes wrote:
> Can you clarify exactly what functionality is missing without this
> interface, and how to reproduce the issue? Is there an upstream bug?

I'm not able to reproduce this any more (i.e., I rolled back the change
I made to /usr/share/applications/org.kde.spectacle.desktop, and I can
still take screenshots of the whole desktop).  Moreover, I can reproduce
the original buggy behavior by removing the line

> X-KDE-DBUS-Restricted-Interfaces=org.kde.KWin.ScreenShot2

from the .desktop file for spectacle.

At the time, spectacle was only able to take screen shots using the
"Window Under Cursor" option.  I modified the desktop file as I described
in the original bug report, and the issue was resolved (I guessed the
name from some error output from spectacle, about permission being
denied to acces).

I now no longer believe that patch has any merit, and that it was there
mere act of changing the file that triggered it to be (re)loaded that
resolved the issue.  At the time, I was also experiencing another
unexpected behavior: none of the desktop files seemed to be getting
picked up.  For instance, the "Application Menu" widget had no items in
it.  Additionally, the "default applications" section of systemsettings
had no programs to select, despite, for example, Thunderbird being
installed.

I had upgraded bits and pieces of KDE since that time, and the desktop
files are now apparently being parsed: the menu is now fully populated
and the Default Application section shows, e.g., Firefox and Thunderbird
as options for default web browser and email client.

I will say that I had rebooted the machine before trying to take
the screenshot.  This bug report should probably be closed: my best
guess as to what happened is that some third package was blocking desktop
files from being parsed, but that issue now appears resolved.

> 
> Also, do you have a link to where these options are documented? I'd
> like to make sure we didn't miss anything else.

I was reasoning entirely based off the fact that adding that line
fixed the behavior.  I doubt that alleged interface even exists.

> sney

Best,
Antonio

Attachment: OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to