Github messages for voidlinux
 help / color / mirror / Atom feed
From: LinArcX <LinArcX@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Critical: Error: No such interface “org.freedesktop.portal.Screenshot” on object at path /org/freedesktop/portal/desktop
Date: Tue, 16 Aug 2022 08:08:48 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38699@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

New issue by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/38699

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.16_1 x86_64 GenuineIntel notuptodate hold rFF

### Package(s) Affected

ksnip-1.9.2, wayfire-0.7.3

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

ksnip should take screenshots properly on wayfire.

### Actual behaviour

whenever i run ksnip from shell and try to capture screenshot, it says:
```
↳ ksnip
Critical: Unknown wayland platform, using default wayland Image Grabber.
Warning: Unable to find any translation files for ksnip.
Warning: Unable to find any translation files for kImageAnnotator.
Warning: Wayland does not support QWindow::requestActivate()
Warning: Wayland does not support QWindow::requestActivate()
Warning: This plugin does not support setting window opacity
Critical: Error: No such interface “org.freedesktop.portal.Screenshot” on object at path /org/freedesktop/portal/desktop
```I

### Steps to reproduce

1. run ksnip from your shell.

             reply	other threads:[~2022-08-16  6:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  6:08 LinArcX [this message]
2022-08-16 19:34 ` paper42
2022-08-16 19:39 ` LinArcX
2022-08-18 10:47 ` vutunganh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38699@inbox.vuxu.org \
    --to=linarcx@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).