[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1078791: marked as done (Missing permissions for screen capture)

Your message dated Fri, 16 Aug 2024 22:02:35 -0400
with message-id <CAD_06eUOQasZGp8WRMv=QUetQWvtNhG1gjYjojYQfGZfvZnG1g@mail.gmail.com>
and subject line Re: Bug#1078791: Missing permissions for screen capture
has caused the Debian Bug report #1078791,
regarding Missing permissions for screen capture
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1078791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078791
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kde-spectacle
Version: 24.05.2-1
Severity: normal

Dear Maintainer,

For wayland screen capture, the appropriate "restricted interfaces" must be authorized for use.

This is done in /usr/share/applications/org.kde.spectacle.desktop with the X-KDE-DBUS-Restricted-Interfaces
option.

The "org.kde.KWin.CaptureScreen" interface is used by spectacle to capture the entire screen
(ScreenShot2 is only used to capture a single window).

Please change the line 204 from

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

to

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

Best,
Antonio Russo

Attachment: OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Hi Antonio,

I do think this interface exists, or it did in the past, because I see
it in some old upstream bug reports for previous versions of
spectacle. But it sounds like this was a transient support issue
rather than a bug, and I was unable to produce any permission errors
with spectacle in my test VM so I'm going to close it.

Feel free to reply if the issue appears again, or visit one of our
support resources for help debugging. https://www.debian.org/support

sney

On Fri, Aug 16, 2024 at 7:36 PM Antonio Russo <aerusso@aerusso.net> wrote:
>
> 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

--- End Message ---
Reply to: