From: ohlookitsaaron <ohlookitsaaron@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] xdg-document-portal Segmentation Fault
Date: Sun, 13 Aug 2023 23:51:28 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45591@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
New issue by ohlookitsaaron on void-packages repository
https://github.com/void-linux/void-packages/issues/45591
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.13_1 x86_64-musl GenuineIntel uptodate rFF
### Package(s) Affected
xdg-desktop-portal
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
Yes, on Alpine Linux: https://gitlab.alpinelinux.org/alpine/aports/-/issues/14195
### Expected behaviour
xdg-document-portal should start with flatpak apps or with xdg-desktop-portal (to my knowledge) running in the background.
### Actual behaviour
All flatpak apps cannot save any files regardless of flatpak permissions.
When running /usr/libexec/xdg-document-portal:
error: fuse stat failed: Socket not connected
Segmentation fault
When starting a flatpak app:
F: Can't get document portal: GDBus.Error:org.freedesktop.DBus.Error.Failed: fuse stat failed: Socket not connected
### Steps to reproduce
1. Fresh install of Void Linux musl
2. Install GNOME desktop, enable dbus + gdm services
3. Install flatpak and enable flathub repo
4. Try to download anything from any flatpak web browser or program
next reply other threads:[~2023-08-13 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 21:51 ohlookitsaaron [this message]
2023-08-17 19:35 ` ahesford
2023-08-18 16:09 ` [ISSUE] [CLOSED] " ahesford
2023-08-18 16:09 ` ahesford
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-45591@inbox.vuxu.org \
--to=ohlookitsaaron@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).