gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-remote-desktop (Debian) |
Fix Released
|
Unknown
|
|||
gnome-remote-desktop (Ubuntu) |
Fix Released
|
Low
|
Jeremy Bícha | ||
Jammy |
Fix Released
|
Low
|
Jeremy Bícha | ||
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Impact
======
GNOME Remote desktop crashes if fuse3 package is not installed as it provides fusermount3, that fuse_session_
Test Case
=========
Verify that gnome-remote-
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-
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_structure
writer_func = <optimized out>
recursion = <optimized out>
depth = <optimized out>
__func__ = "g_log_
#1 0x00007f79092e2f99 in g_log_default_
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\
n_fields = <optimized out>
#2 0x00007f79092e43fa in g_logv (log_domain=0x0, log_level=
domain = 0x0
data = 0x0
depth = <optimized out>
log_func = 0x7f79092e2ee0 <g_log_
test_level = 6
was_fatal = <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=
args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7f7859ff0000, reg_save_area = 0x7f7859feff40}}
#4 0x00005605ec5c0920 in fuse_thread_func (data=0x5605ed3
args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
argv = {0x7ffe23912a12 "/usr/libexec/
result = <optimized out>
Further details:
- https:/
summary: |
- /usr/libexec/gnome-remote-desktop- - daemon:5:fuse_thread_func:g_thread_proxy:start_thread:clone3 + gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy + → start_thread: Failed to mount FUSE filesystem (as per missing + fusermount3) |
tags: | added: rls-ff-incoming |
Changed in fuse3 (Ubuntu): | |
status: | New → Incomplete |
Changed in gnome-remote-desktop (Ubuntu): | |
status: | New → Triaged |
description: | updated |
Changed in gnome-remote-desktop (Debian): | |
status: | Unknown → New |
description: | updated |
Changed in gnome-remote-desktop (Ubuntu): | |
importance: | Undecided → Low |
assignee: | nobody → Jeremy Bicha (jbicha) |
Changed in gnome-remote-desktop (Debian): | |
status: | New → Fix Released |
no longer affects: | fuse3 (Ubuntu) |
no longer affects: | fuse3 (Ubuntu Jammy) |
no longer affects: | linux (Ubuntu Jammy) |
Changed in gnome-remote-desktop (Ubuntu Jammy): | |
status: | New → In Progress |
importance: | Undecided → Low |
assignee: | nobody → Jeremy Bicha (jbicha) |
Apparently this is due to ubuntu kernel (only?) not supporting unprivileged fuser mounts: /sources. debian. org/src/ fuse3/3. 10.5-1/ lib/mount. c/?hl=466# L465
- https:/
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.