gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)

[errors.ubuntu.com bug bridge]

Impact
======
GNOME Remote desktop crashes if fuse3 package is not installed as it provides fusermount3, that fuse_session_mount() implicitly requires.

Test Case
=========
Verify that gnome-remote-desktop has a dependency on fuse3

What Could Go Wrong
==================
This just adds a dependency.

This bug should be very uncommon because a system without fuse3 also wouldn't have xdg-desktop-portal installed meaning Snaps don't work and wouldn't have ubuntu-desktop-minimal installed.

Other Info
=========
libfuse3 is currently suggesting fusermount3, I'm wondering if we should instead recommending it, given that one of the library function relies on that. It's possible for things to use the library without that function so that's why it's proposed to be only a Recommends and not a Depends.

For Ubuntu 22.10, we should see if the kernel can support this natively without needing fusermount3 as suggested in comment 1.

Stack trace:

#0 g_log_structured_array (log_level=<optimized out>, fields=0x7f7859fefdd0, n_fields=3) at ../../../glib/gmessages.c:557
        writer_func = <optimized out>
        writer_user_data = <optimized out>
        recursion = <optimized out>
        depth = <optimized out>
        __func__ = "g_log_structured_array"
        _g_boolean_var_ = <optimized out>
#1 0x00007f79092e2f99 in g_log_default_handler (log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, message=message@entry=0x7f7860000f80 "[FUSE Clipboard] Failed to mount FUSE filesystem", unused_data=unused_data@entry=0x0) at ../../../glib/gmessages.c:3295
        fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 0x7f7860000f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 0x7f790939a109, length = -1}, {key = 0x7f790932a09f <g_private_set+63> "\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 140157821898257}}
        n_fields = <optimized out>
#2 0x00007f79092e43fa in g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=<optimized out>) at ../../../glib/gmessages.c:1387
        domain = 0x0
        data = 0x0
        depth = <optimized out>
        log_func = 0x7f79092e2ee0 <g_log_default_handler>
        domain_fatal_mask = <optimized out>
        masquerade_fatal = 0
        test_level = 6
        was_fatal = <optimized out>
        was_recursion = <optimized out>
        buffer = <optimized out>
        msg = 0x7f7860000f80 "[FUSE Clipboard] Failed to mount FUSE filesystem"
        msg_alloc = 0x7f7860000f80 "[FUSE Clipboard] Failed to mount FUSE filesystem"
        i = 2
        size = <optimized out>
#3 0x00007f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 "[FUSE Clipboard] Failed to mount FUSE filesystem") at ../../../glib/gmessages.c:1456
        args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7f7859ff0000, reg_save_area = 0x7f7859feff40}}
#4 0x00005605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at ../src/grd-rdp-fuse-clipboard.c:1321
        rdp_fuse_clipboard = 0x5605ed301820
        args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
        argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
        result = <optimized out>

Further details:
 - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f

[Marco Trevisan (Treviño) (3v1n0)]

Apparently this is due to ubuntu kernel (only?) not supporting unprivileged fuser mounts:
  - https://sources.debian.org/src/fuse3/3.10.5-1/lib/mount.c/?hl=466#L465

So... While in kinetic this could be handled via Kernel support (as per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906009, so adding kernel here too), I guess we need to address the packages for jammy.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1970411

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Pascal Nowack (pnowack)]

I don't think a package recommendation is the right thing here. Instead, the package containing fuse3 and fusermount3 should here be a package dependency of the gnome-remote-desktop package.

[Marco Trevisan (Treviño) (3v1n0)]

I was saying that for libfuse3, also such reccommends are installed by default in ubuntu installs anyways.

Not all stuff that will need libfuse3 is actually strictly dependent on fusermount3 as g-r-d is.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1

---------------
gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium

  * Merge with Debian. Remaining change:
    - Lower gnome-control-center dependency to 41

gnome-remote-desktop (42.1.1-2) unstable; urgency=high

  * Don't automatically enable the systemd user service (LP: #1973028)
  * Add postinst to remove the automatic enabling of the user service
  * debian/control: Lower mutter dependency so that these fixes reach
    Testing sooner

gnome-remote-desktop (42.1.1-1) unstable; urgency=medium

  * New upstream release (LP: #1970662)
    - Fixes black screen with virtio on qemu (LP: #1971195)
  * Drop all patches: applied in new release
  * Depend on libmutter instead of gnome-shell | budgie-desktop
    - This is a more accurate dependency
  * Require libmutter 42.1 for Nvidia fixes
  * Depend on fuse3 (Closes: #998846) (LP: #1970411)

 -- Jeremy Bicha <email address hidden> Thu, 12 May 2022 15:21:47 -0400

[Brian Murray (brian-murray)]

Hello errors.ubuntu.com, or anyone else affected,

Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote-desktop/42.1.1-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Jeremy Bícha (jbicha)]

I have verified that gnome-remote-desktop 42.1.1-0ubuntu1 depends on fuse3

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for gnome-remote-desktop has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-remote-desktop - 42.1.1-0ubuntu1

---------------
gnome-remote-desktop (42.1.1-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1970662)
    - Fixes black screen with virtio on qemu (LP: #1971195)
  * Drop all patches: applied in new release
  * Depend on libmutter instead of gnome-shell | budgie-desktop
    - This is a more accurate dependency
  * Require libmutter 42.1 for Nvidia fixes
  * Depend on fuse3 (Closes: #998846) (LP: #1970411)
  * Don't automatically enable the systemd user service (LP: #1973028)
  * Add postinst to remove the automatic enabling of the user service

 -- Jeremy Bicha <email address hidden> Tue, 17 May 2022 14:27:16 -0400