[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
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 Tue, 17 May 2022 14:27:16 -0400
** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970411
Title:
gnome-remote-desktop-daemon crashes on fuse_thread_func →
g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
missing fusermount3)
Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in gnome-remote-desktop source package in Jammy:
Fix Released
Status in gnome-remote-desktop package in Debian:
Fix Released
Bug description:
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=, fields=0x7f7859fefdd0,
n_fields=3) at ../../../glib/gmessages.c:557
writer_func =
writer_user_data =
recursion =
depth =
__func__ = "g_log_structured_array"
_g_boolean_var_ =
#1 0x7f79092e2f99 in g_log_default_handler
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6,
message=message@entry=0x7f786f80 "[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 =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
n_fields =
#2 0x7f79092e43fa in g_logv (log_domain=0x0,
log_level=G_LOG_LEVEL_ERROR, format=, args=) at
../../../glib/gmessages.c:1387
domain = 0x0
data = 0x0
depth =
log_func = 0x7f79092e2ee0
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
buffer =
msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
i = 2
size =
#3 0x7f79092e46e3 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 =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
#4 0x5605ec5c0920 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 =
Further details:
- https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970411/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help
[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
I have verified that gnome-remote-desktop 42.1.1-0ubuntu1 depends on
fuse3
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970411
Title:
gnome-remote-desktop-daemon crashes on fuse_thread_func →
g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
missing fusermount3)
Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in gnome-remote-desktop source package in Jammy:
Fix Committed
Status in gnome-remote-desktop package in Debian:
Fix Released
Bug description:
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=, fields=0x7f7859fefdd0,
n_fields=3) at ../../../glib/gmessages.c:557
writer_func =
writer_user_data =
recursion =
depth =
__func__ = "g_log_structured_array"
_g_boolean_var_ =
#1 0x7f79092e2f99 in g_log_default_handler
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6,
message=message@entry=0x7f786f80 "[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 =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
n_fields =
#2 0x7f79092e43fa in g_logv (log_domain=0x0,
log_level=G_LOG_LEVEL_ERROR, format=, args=) at
../../../glib/gmessages.c:1387
domain = 0x0
data = 0x0
depth =
log_func = 0x7f79092e2ee0
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
buffer =
msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
i = 2
size =
#3 0x7f79092e46e3 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 =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
#4 0x5605ec5c0920 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 =
Further details:
- https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970411/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
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.
** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970411
Title:
gnome-remote-desktop-daemon crashes on fuse_thread_func →
g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
missing fusermount3)
Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in gnome-remote-desktop source package in Jammy:
Fix Committed
Status in gnome-remote-desktop package in Debian:
Fix Released
Bug description:
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=, fields=0x7f7859fefdd0,
n_fields=3) at ../../../glib/gmessages.c:557
writer_func =
writer_user_data =
recursion =
depth =
__func__ = "g_log_structured_array"
_g_boolean_var_ =
#1 0x7f79092e2f99 in g_log_default_handler
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6,
message=message@entry=0x7f786f80 "[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 =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
n_fields =
#2 0x7f79092e43fa in g_logv (log_domain=0x0,
log_level=G_LOG_LEVEL_ERROR, format=, args=) at
../../../glib/gmessages.c:1387
domain = 0x0
data = 0x0
depth =
log_func = 0x7f79092e2ee0
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
buffer =
msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
i = 2
size =
#3 0x7f79092e46e3 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 =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
#4 0x5605ec5c0920 in fuse_thread_func
[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: fuse3 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: gnome-remote-desktop (Ubuntu Jammy)
Importance: Undecided
Status: New
** 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
** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Importance: Undecided => Low
** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Assignee: (unassigned) => Jeremy Bicha (jbicha)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970411
Title:
gnome-remote-desktop-daemon crashes on fuse_thread_func →
g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
missing fusermount3)
Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in gnome-remote-desktop source package in Jammy:
In Progress
Status in gnome-remote-desktop package in Debian:
Fix Released
Bug description:
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=, fields=0x7f7859fefdd0,
n_fields=3) at ../../../glib/gmessages.c:557
writer_func =
writer_user_data =
recursion =
depth =
__func__ = "g_log_structured_array"
_g_boolean_var_ =
#1 0x7f79092e2f99 in g_log_default_handler
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6,
message=message@entry=0x7f786f80 "[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 =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
n_fields =
#2 0x7f79092e43fa in g_logv (log_domain=0x0,
log_level=G_LOG_LEVEL_ERROR, format=, args=) at
../../../glib/gmessages.c:1387
domain = 0x0
data = 0x0
depth =
log_func = 0x7f79092e2ee0
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
buffer =
msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
i = 2
size =
#3 0x7f79092e46e3 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 =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
#4 0x5605ec5c0920 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 =
Further details:
- https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970411/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
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 Thu, 12 May 2022 15:21:47 -0400
** Changed in: gnome-remote-desktop (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970411
Title:
gnome-remote-desktop-daemon crashes on fuse_thread_func →
g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
missing fusermount3)
Status in fuse3 package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Debian:
Fix Released
Bug description:
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=, fields=0x7f7859fefdd0,
n_fields=3) at ../../../glib/gmessages.c:557
writer_func =
writer_user_data =
recursion =
depth =
__func__ = "g_log_structured_array"
_g_boolean_var_ =
#1 0x7f79092e2f99 in g_log_default_handler
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6,
message=message@entry=0x7f786f80 "[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 =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
n_fields =
#2 0x7f79092e43fa in g_logv (log_domain=0x0,
log_level=G_LOG_LEVEL_ERROR, format=, args=) at
../../../glib/gmessages.c:1387
domain = 0x0
data = 0x0
depth =
log_func = 0x7f79092e2ee0
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
buffer =
msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
i = 2
size =
#3 0x7f79092e46e3 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 =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
#4 0x5605ec5c0920 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 =
Further details:
- https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
** Changed in: gnome-remote-desktop (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970411
Title:
gnome-remote-desktop-daemon crashes on fuse_thread_func →
g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
missing fusermount3)
Status in fuse3 package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Debian:
Fix Released
Bug description:
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=, fields=0x7f7859fefdd0,
n_fields=3) at ../../../glib/gmessages.c:557
writer_func =
writer_user_data =
recursion =
depth =
__func__ = "g_log_structured_array"
_g_boolean_var_ =
#1 0x7f79092e2f99 in g_log_default_handler
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6,
message=message@entry=0x7f786f80 "[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 =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
n_fields =
#2 0x7f79092e43fa in g_logv (log_domain=0x0,
log_level=G_LOG_LEVEL_ERROR, format=, args=) at
../../../glib/gmessages.c:1387
domain = 0x0
data = 0x0
depth =
log_func = 0x7f79092e2ee0
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
buffer =
msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
i = 2
size =
#3 0x7f79092e46e3 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 =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
#4 0x5605ec5c0920 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 =
Further details:
- https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1970411/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
** Description changed:
- GNOME Remote desktop crashes if fuse3 package is not installed as it
- provides fusermount3, that fuse_session_mount() implicitly requires.
+ Impact
+ ==
+ GNOME Remote desktop crashes if fuse3 package is not installed as it provides
fusermount3, that fuse_session_mount() implicitly requires.
- libfuse3 is currently suggesting fusermount3, I'm wondering if we should
- instead recommending it, given that one of the library function relies
- on that.
+ Test Case
+ =
+ Verify that gnome-remote-desktop has a dependency on fuse3
- Otherwise, we should probably make the g-r-d dependency stronger.
+ 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=, fields=0x7f7859fefdd0,
n_fields=3) at ../../../glib/gmessages.c:557
- writer_func =
- writer_user_data =
- recursion =
- depth =
- __func__ = "g_log_structured_array"
- _g_boolean_var_ =
+ writer_func =
+ writer_user_data =
+ recursion =
+ depth =
+ __func__ = "g_log_structured_array"
+ _g_boolean_var_ =
#1 0x7f79092e2f99 in g_log_default_handler
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6,
message=message@entry=0x7f786f80 "[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 =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
- n_fields =
+ fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value =
0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
+ n_fields =
#2 0x7f79092e43fa in g_logv (log_domain=0x0,
log_level=G_LOG_LEVEL_ERROR, format=, args=) at
../../../glib/gmessages.c:1387
- domain = 0x0
- data = 0x0
- depth =
- log_func = 0x7f79092e2ee0
- domain_fatal_mask =
- masquerade_fatal = 0
- test_level = 6
- was_fatal =
- was_recursion =
- buffer =
- msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
- msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
- i = 2
- size =
+ domain = 0x0
+ data = 0x0
+ depth =
+ log_func = 0x7f79092e2ee0
+ domain_fatal_mask =
+ masquerade_fatal = 0
+ test_level = 6
+ was_fatal =
+ was_recursion =
+ buffer =
+ msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
+ msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
+ i = 2
+ size =
#3 0x7f79092e46e3 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 =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
+ args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
#4 0x5605ec5c0920 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 =
-
+ rdp_fuse_clipboard = 0x5605ed301820
+ args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
+ argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
+ result =
Further details:
- -
[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
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.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970411
Title:
gnome-remote-desktop-daemon crashes on fuse_thread_func →
g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
missing fusermount3)
Status in fuse3 package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Debian:
New
Bug description:
GNOME Remote desktop crashes if fuse3 package is not installed as it
provides fusermount3, that fuse_session_mount() implicitly requires.
libfuse3 is currently suggesting fusermount3, I'm wondering if we
should instead recommending it, given that one of the library function
relies on that.
Otherwise, we should probably make the g-r-d dependency stronger.
Stack trace:
#0 g_log_structured_array (log_level=, fields=0x7f7859fefdd0,
n_fields=3) at ../../../glib/gmessages.c:557
writer_func =
writer_user_data =
recursion =
depth =
__func__ = "g_log_structured_array"
_g_boolean_var_ =
#1 0x7f79092e2f99 in g_log_default_handler
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6,
message=message@entry=0x7f786f80 "[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 =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
n_fields =
#2 0x7f79092e43fa in g_logv (log_domain=0x0,
log_level=G_LOG_LEVEL_ERROR, format=, args=) at
../../../glib/gmessages.c:1387
domain = 0x0
data = 0x0
depth =
log_func = 0x7f79092e2ee0
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
buffer =
msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
i = 2
size =
#3 0x7f79092e46e3 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 =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
#4 0x5605ec5c0920 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 =
Further details:
- https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1970411/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
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.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970411
Title:
gnome-remote-desktop-daemon crashes on fuse_thread_func →
g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
missing fusermount3)
Status in fuse3 package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Debian:
New
Bug description:
GNOME Remote desktop crashes if fuse3 package is not installed as it
provides fusermount3, that fuse_session_mount() implicitly requires.
libfuse3 is currently suggesting fusermount3, I'm wondering if we
should instead recommending it, given that one of the library function
relies on that.
Otherwise, we should probably make the g-r-d dependency stronger.
Stack trace:
#0 g_log_structured_array (log_level=, fields=0x7f7859fefdd0,
n_fields=3) at ../../../glib/gmessages.c:557
writer_func =
writer_user_data =
recursion =
depth =
__func__ = "g_log_structured_array"
_g_boolean_var_ =
#1 0x7f79092e2f99 in g_log_default_handler
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6,
message=message@entry=0x7f786f80 "[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 =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
n_fields =
#2 0x7f79092e43fa in g_logv (log_domain=0x0,
log_level=G_LOG_LEVEL_ERROR, format=, args=) at
../../../glib/gmessages.c:1387
domain = 0x0
data = 0x0
depth =
log_func = 0x7f79092e2ee0
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
buffer =
msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
i = 2
size =
#3 0x7f79092e46e3 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 =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
#4 0x5605ec5c0920 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 =
Further details:
- https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1970411/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
** Changed in: gnome-remote-desktop (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970411
Title:
gnome-remote-desktop-daemon crashes on fuse_thread_func →
g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
missing fusermount3)
Status in fuse3 package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Debian:
New
Bug description:
GNOME Remote desktop crashes if fuse3 package is not installed as it
provides fusermount3, that fuse_session_mount() implicitly requires.
libfuse3 is currently suggesting fusermount3, I'm wondering if we
should instead recommending it, given that one of the library function
relies on that.
Otherwise, we should probably make the g-r-d dependency stronger.
Stack trace:
#0 g_log_structured_array (log_level=, fields=0x7f7859fefdd0,
n_fields=3) at ../../../glib/gmessages.c:557
writer_func =
writer_user_data =
recursion =
depth =
__func__ = "g_log_structured_array"
_g_boolean_var_ =
#1 0x7f79092e2f99 in g_log_default_handler
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6,
message=message@entry=0x7f786f80 "[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 =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
n_fields =
#2 0x7f79092e43fa in g_logv (log_domain=0x0,
log_level=G_LOG_LEVEL_ERROR, format=, args=) at
../../../glib/gmessages.c:1387
domain = 0x0
data = 0x0
depth =
log_func = 0x7f79092e2ee0
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
buffer =
msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
i = 2
size =
#3 0x7f79092e46e3 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 =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
#4 0x5605ec5c0920 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 =
Further details:
- https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1970411/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
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.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #906009
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906009
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970411
Title:
gnome-remote-desktop-daemon crashes on fuse_thread_func →
g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
missing fusermount3)
Status in fuse3 package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in gnome-remote-desktop package in Debian:
New
Bug description:
GNOME Remote desktop crashes if fuse3 package is not installed as it
provides fusermount3, that fuse_session_mount() implicitly requires.
libfuse3 is currently suggesting fusermount3, I'm wondering if we
should instead recommending it, given that one of the library function
relies on that.
Otherwise, we should probably make the g-r-d dependency stronger.
Stack trace:
#0 g_log_structured_array (log_level=, fields=0x7f7859fefdd0,
n_fields=3) at ../../../glib/gmessages.c:557
writer_func =
writer_user_data =
recursion =
depth =
__func__ = "g_log_structured_array"
_g_boolean_var_ =
#1 0x7f79092e2f99 in g_log_default_handler
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6,
message=message@entry=0x7f786f80 "[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 =
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value =
0x7f790939a109, length = -1}, {key = 0x7f790932a09f
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length =
140157821898257}}
n_fields =
#2 0x7f79092e43fa in g_logv (log_domain=0x0,
log_level=G_LOG_LEVEL_ERROR, format=, args=) at
../../../glib/gmessages.c:1387
domain = 0x0
data = 0x0
depth =
log_func = 0x7f79092e2ee0
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
buffer =
msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE
filesystem"
i = 2
size =
#3 0x7f79092e46e3 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 =
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
#4 0x5605ec5c0920 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 =
Further details:
- https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1970411/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
