Something went wrong [4ulu5]

Ubuntu 24 (6.17.0-29-generic #29~24.04.1-Ubuntu)

• uninstall intune
• all stale secrets eliminated via seahorse (MSAL etc.)
• other potential remnants of old installations removed:

rm -r ~/.config/microsoft-identity-broker
rm -r ~/.local/state/microsoft-identity-broker
sudo rm -r /var/lib/microsoft-identity-device-broker
sudo rm -r /var/lib/intune
sudo rm -r /var/log/microsoft-identity-device-broker/
sudo rm -r /var/crash/*microsoft_intune*
sudo rm -r /tmp/*microsoft-identity*

• systemctl --user daemon-reload
• fresh installation of intune (using a workaround - older install script version - due to another issue with the install script)
• attempt log in with my usual credentials

.. roughly 3 minutes or so load time, then:

Error Something went wrong. [4ulu5]
Correlation Id: 1a68ed80-988a-42d1-a4dd-22cec3187c1f
Timestamp: 2026-06-10T14:46:56.000Z
DPTI: 4a01a11e7d399655d6b6fdf0cdbb872f0080f20b3a233f29713c84126f8420c9
Message: An unexpected error occurred.
Tag: 4ulu5
Code: 0

Some debug info
journalctl --follow shows some warning messages that might be related

Jun 10 16:49:51 BBNV-0045 gvfsd-wsdd[385100]: Failed to spawn the wsdd daemon: Failed to execute child process “wsdd” (No such file or directory)
Jun 10 16:49:51 BBNV-0045 gvfsd-network[10553]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying wsdd daemon.
Jun 10 16:50:38 BBNV-0045 geoclue[2422]: Failed to query location: Query location SOUP error: Not Found
Jun 10 16:50:40 BBNV-0045 geoclue[2422]: Failed to query location: Query location SOUP error: Not Found
Jun 10 16:50:52 BBNV-0045 intune-portal[384157]: oneauth{tag="5zt6h"}: , error:[101], httpStatus:[0], errorMessage:[(pii)]
Jun 10 16:50:52 BBNV-0045 intune-portal[384157]: oneauth{tag="49ayy"}: Generating description for errorCode 3600 subStatus 0
Jun 10 16:50:52 BBNV-0045 intune-portal[384157]: oneauth{tag="49zlh"}: Navigation flow is being dismissed
Jun 10 16:50:52 BBNV-0045 intune-portal[384157]: oneauth{tag="9zkad"}:
Jun 10 16:50:52 BBNV-0045 intune-portal.desktop[384157]: [intune-portal/src/gtk3/actions.rs:101:29] e = Error {
Jun 10 16:50:52 BBNV-0045 intune-portal.desktop[384157]:     context: "Starting a new login",
Jun 10 16:50:52 BBNV-0045 intune-portal.desktop[384157]:     source: Misconfiguration(
Jun 10 16:50:52 BBNV-0045 intune-portal.desktop[384157]:         0,
Jun 10 16:50:52 BBNV-0045 intune-portal.desktop[384157]:     ),
Jun 10 16:50:52 BBNV-0045 intune-portal.desktop[384157]: }
Jun 10 16:52:16 BBNV-0045 rtkit-daemon[1985]: Supervising 13 threads of 8 processes of 1 users.
Jun 10 16:52:16 BBNV-0045 rtkit-daemon[1985]: Supervising 13 threads of 8 processes of 1 users.
Jun 10 16:52:31 BBNV-0045 rtkit-daemon[1985]: Supervising 13 threads of 8 processes of 1 users.
Jun 10 16:52:31 BBNV-0045 rtkit-daemon[1985]: Supervising 13 threads of 8 processes of 1 users.
Jun 10 16:52:52 BBNV-0045 systemd[2932]: Started app-gnome-x\x2dterminal\x2demulator-385308.scope - Application launched by gsd-media-keys.
Jun 10 16:52:57 BBNV-0045 gvfsd-wsdd[385366]: Failed to spawn the wsdd daemon: Failed to execute child process “wsdd” (No such file or directory)
Jun 10 16:52:57 BBNV-0045 gvfsd-network[10553]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying wsdd daemon.
Jun 10 16:53:26 BBNV-0045 rtkit-daemon[1985]: Supervising 13 threads of 8 processes of 1 users.
Jun 10 16:53:26 BBNV-0045 rtkit-daemon[1985]: Supervising 13 threads of 8 processes of 1 users.
Jun 10 16:54:21 BBNV-0045 wpa_supplicant[1353]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-59 noise=9999 txrate=29200
Jun 10 16:54:24 BBNV-0045 geoclue[2422]: Failed to query location: Query location SOUP error: Not Found
Jun 10 16:54:56 BBNV-0045 geoclue[2422]: Failed to query location: Query location SOUP error: Not Found

Start by reproducing the login attempt on Ubuntu 24 and review the intune-portal entries in journalctl, especially the oneauth error and Misconfiguration source shown here. Compare the installation path with the workaround described in issue #270. Done means identifying the cause of error [4ulu5] or documenting the missing diagnostic information needed to resolve it.