Bug 2125804 - xdg-desktop-portal fails to initialize
Summary: xdg-desktop-portal fails to initialize
Keywords:
Status: CLOSED DUPLICATE of bug 2142385
Alias: None
Product: Fedora
Classification: Fedora
Component: xdg-desktop-portal
Version: 37
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: David King
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-10 15:57 UTC by grumpey0
Modified: 2023-12-06 11:37 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-12-05 23:26:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description grumpey0 2022-09-10 15:57:58 UTC
Description of problem:
Initial observation was being unable to attach files from telegram (flatpak) or element (flatpak) 

xdg-document-portal fails to initialize
[grumpey@grumpey0 /usr/libexec]$ systemctl status --user xdg-document-portal
× xdg-document-portal.service - flatpak document portal service
     Loaded: loaded (/usr/lib/systemd/user/xdg-document-portal.service; static)
     Active: failed (Result: exit-code) since Sat 2022-09-10 11:28:31 EDT; 13min ago
   Duration: 1ms
    Process: 4274 ExecStart=/usr/libexec/xdg-document-portal (code=exited, status=6)
   Main PID: 4274 (code=exited, status=6)
        CPU: 6ms

Sep 10 11:28:31 grumpey0 systemd[1490]: Starting xdg-document-portal.service - flatpak document portal service...
Sep 10 11:28:31 grumpey0 systemd[1490]: Started xdg-document-portal.service - flatpak document portal service.
Sep 10 11:28:31 grumpey0 xdg-document-portal[4280]: fuse: failed to exec fusermount3: No such file or directory
Sep 10 11:28:31 grumpey0 xdg-document-portal[4274]: error: fuse init failed: Can't mount path /run/user/1000/doc
Sep 10 11:28:31 grumpey0 systemd[1490]: xdg-document-portal.service: Main process exited, code=exited, status=6/NOTCO>
Sep 10 11:28:31 grumpey0 systemd[1490]: xdg-document-portal.service: Failed with result 'exit-code'.


Version-Release number of selected component (if applicable):
1.15.0

How reproducible:
systemctl status --user xdg-document-portal-service

Additional info:
This commit changed to fuse 3: 
https://github.com/flatpak/xdg-desktop-portal/commit/ede383e72cd24b609a4b8c271cfd367869474ed0
Spec file needs to be changed: 	
Requires:      /usr/bin/fusermount
to 
Requires:      /usr/bin/fusermount3

Comment 1 Aoife Moloney 2023-11-23 00:22:26 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Aoife Moloney 2023-12-05 23:26:32 UTC
Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Debarshi Ray 2023-12-06 11:37:40 UTC

*** This bug has been marked as a duplicate of bug 2142385 ***


Note You need to log in before you can comment on or make changes to this bug.