Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fuse mount /run/user/1000/doc unavailable after sleep #305

Closed
divoxx opened this issue Feb 22, 2019 · 4 comments
Closed

Fuse mount /run/user/1000/doc unavailable after sleep #305

divoxx opened this issue Feb 22, 2019 · 4 comments

Comments

@divoxx
Copy link

divoxx commented Feb 22, 2019

I'm running Flatpak on Gentoo and it seems like the /run/user/1000/doc fuse mount is unmounted when going into sleep and then not re-mounted after it wakes up.

This is what I see before going into sleep/hibernate, and it's gone after waking up:

/dev/fuse on /run/user/1000/doc type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

I've tried running xdg-document-portal manually with debug logging, to see if there is any error happening when waking up but there is no additional output after the initial output when running the command:

Before sleeping:

$ env G_MESSAGES_DEBUG=all /usr/libexec/xdg-document-portal --replace --verbose
XDP: org.freedesktop.portal.Documents acquired
XDP: xdp_fuse_getattr 1 (fi=(nil))
XDP: xdp_fuse_getattr <- OK
XDP: xdp_fuse_access 1 4
XDP: xdp_fuse_lookup 1/.Trash ->
XDP: xdp_fuse_lookup <- error child ENOENT
XDP: xdp_fuse_lookup 1/.Trash-1000 ->
XDP: xdp_fuse_lookup <- error child ENOENT

After sleep, the output is still the same, no additional output. Restarting that command does fix the problem and the mount is established again.

Let me know if I can provide any additional information.

@bLuka
Copy link

bLuka commented Apr 1, 2019

Heya, I've got the exact same issue when resuming after suspend, needing to reboot after suspends when I want to run any flatpak app. /run/user/1000/doc is empty.

Gentoo with Gnome/OpenRC here; and as mentionned, restarting xdg-document-portal after a suspend did fix the issue.

@ploth
Copy link

ploth commented May 6, 2019

Yep, same here.

@matthiasclasen
Copy link
Contributor

Any idea what is responsible for unmounting fuse fs on suspend/hibernate ?

@matthiasclasen
Copy link
Contributor

This should be fixed in master - the portal now exists when its fuse mount gets unmounted externally.

agx pushed a commit to agx/xdg-desktop-portal that referenced this issue Dec 20, 2023
In GNOME 3.36 the lockscreen is now a blurried version of the
wallpaper. Although the gsetting for setting the lockscreen
background image will persist available, we should be consistent
with GNOME's UX decisions.

The frontend code should keep the "set-on" option, since other
desktop environments such as KDE might still have a separate
lockscreen image.

The "set-on" option will be simply ignored for the GTK backend.

See https://blogs.gnome.org/shell-dev/2020/02/18/login-and-unlock-in-gnome-shell-3-36/
agx pushed a commit to agx/xdg-desktop-portal that referenced this issue Dec 20, 2023
Commit 414adca
("wallpaper: Drop "lockscreen" option (flatpak#305)", 2020-05-29)
had removed the third (gboolean) param from
the 'wallpaper_preview_set_image' function, but this call
site still passed it, so the build failed with

      CC       src/xdg_desktop_portal_gtk-wallpaperdialog.o
    src/wallpaperdialog.c: In function ‘on_image_loaded_cb’:
    src/wallpaperdialog.c:139:3: error: too many arguments to function ‘wallpaper_preview_set_image’
      139 |   wallpaper_preview_set_image (self->desktop_preview,
          |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~
    In file included from src/wallpaperdialog.c:31:
    src/wallpaperpreview.h:33:20: note: declared here
       33 | void               wallpaper_preview_set_image (WallpaperPreview *self,
          |                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants