gdm3 crashes after installing the 'fuse' package

[Ronzo]

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=23.04
DISTRIB_CODENAME=lunar
DISTRIB_DESCRIPTION="Ubuntu Lunar Lobster (development branch)"
PRETTY_NAME="Ubuntu Lunar Lobster (development branch)"
NAME="Ubuntu"
VERSION_ID="23.04"
VERSION="23.04 (Lunar Lobster)"
VERSION_CODENAME=lunar

After installing the 'fuse' package gdm3 crashes upon login. Happens in Ubuntu 23.04 and 22.10.

apt purge fuse gdm3 && apt install gdm3 renders the system usable again.
---
ProblemType: Bug
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 23.04
InstallationDate: Installed on 2023-03-16 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
Package: gdm3 43.0-3ubuntu2
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=linux
 XDG_RUNTIME_DIR=<set>
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Tags: lunar third-party-packages
Uname: Linux 6.1.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
_MarkForUpload: True

[Ronzo (ronzo)]

gdm3 crash dump

[Daniel van Vugt (vanvugt)]

Please upload the .crash file using the 'ubuntu-bug' or 'apport-cli' commands.

[Ronzo (ronzo)]

Crash file is already uploaded? Could you pls clarify what you are requesting?

[Daniel van Vugt (vanvugt)]

We cannot handle crash files manually, sorry. They must be sent using 'ubuntu-bug' or 'apport-cli' so the robots can process them.

[Ronzo (ronzo)]

apport information

[Ronzo (ronzo)]

apport information

[Ronzo (ronzo)]

Apport seems not to have uploaded the .crash-File. I cannot specify it as an option when trying to update a report. The "-c" option on apport-cli seems only to work when filing new bugs.

[Daniel van Vugt (vanvugt)]

From memory, installing "fuse" can trigger bug 1717878. That's also the only gdm3 crash being reported globally.

[Daniel van Vugt (vanvugt)]

Your system log will confirm if it's bug 1717878. Just run:

  journalctl -b0 > journal.txt
  journalctl -b-1 > prevjournal.txt

and attach the resulting text files here.

[Ronzo (ronzo)]

Please let me know if I can provide more info.

[Daniel van Vugt (vanvugt)]

Thanks. Yes that confirms it is bug 1717878.