Public bug reported:
# Microsoft (and other OAuth2) sign-in hangs: goa-oauth2-handler cannot
forward auth response — D-Bus name "org.gnome.OnlineAccounts.OAuth2" has
no owner
**File against:** `gnome-control-center` on Launchpad
**Submit via:** `ubuntu-bug gnome-control-center` (auto-attaches system info),
then paste the body below into the description field.
---
Adding a Microsoft 365 account via Settings → Online Accounts fails on
Ubuntu 26.04 (GNOME 50). The browser-side OAuth2 flow completes
successfully — Microsoft accepts credentials and redirects to the
goa-oauth2:// callback URI — but the Settings dialog never advances. The
"Continue" button on Microsoft's "Are you trying to sign in to GNOME?"
consent page becomes greyed out after one click and the flow ends
silently.
The journal shows the root-cause failure on the local side of the
callback chain:
org.gnome.OnlineAccounts.OAuth2.desktop[34119]: Failed to forward
authorization response: GDBus.Error:org.freedesktop.DBus.Error.
NameHasNoOwner: Name "org.gnome.OnlineAccounts.OAuth2" does not exist
This message reproduces on every Continue click. The goa-oauth2-handler
binary at /usr/libexec/goa-oauth2-handler IS being launched (URI scheme
registration is correct: x-scheme-handler/goa-oauth2 →
org.gnome.OnlineAccounts.OAuth2.desktop), but the well-known D-Bus
name "org.gnome.OnlineAccounts.OAuth2" cannot be reached when the
handler attempts the forward.
Notably, polling the session bus from a user shell *while the Settings
sign-in is in the waiting state* shows the name IS owned:
$ gdbus call --session --dest org.freedesktop.DBus \
--object-path /org/freedesktop/DBus \
--method org.freedesktop.DBus.NameHasOwner \
org.gnome.OnlineAccounts.OAuth2
(true,)
So gnome-control-center DOES register the name. The failure occurs
specifically on the call originating from goa-oauth2-handler when it
is invoked by the browser via the goa-oauth2:// URI scheme. Possible
explanations: a session-bus mismatch (the handler launched by Chrome
talks to a different bus than the one Settings registered on), a
race where the name is dropped between browser launch and callback,
or the handler is started with an environment that breaks D-Bus
discovery.
## Steps to reproduce
1. Settings → Online Accounts → Microsoft
2. Default browser (Google Chrome native .deb) opens to
login.microsoftonline.com
3. Complete Microsoft sign-in successfully
4. Click "Continue" on the "Are you trying to sign in to GNOME?" page
5. Button greys out, no further UI feedback. Account is never created.
6. Journal shows the NameHasNoOwner error above.
## Expected behavior
Account is added and appears in Settings → Online Accounts.
## Actual behavior
Silent failure with the D-Bus error in the journal.
## Diagnostics performed (none resolved the issue)
- Restarted goa-daemon and goa-identity-service (D-Bus activated, no
systemd unit on this system).
- Verified URI scheme registration:
`xdg-mime query default x-scheme-handler/goa-oauth2`
→ `org.gnome.OnlineAccounts.OAuth2.desktop` (correct)
- Verified .desktop file present and Exec line correct:
`/usr/share/applications/org.gnome.OnlineAccounts.OAuth2.desktop`
`Exec=/usr/libexec/goa-oauth2-handler %u`
- Verified goa-oauth2-handler binary present and executable.
- Browser is native .deb google-chrome-stable, NOT snap/flatpak, so the
D-Bus session bus is the host session bus.
- xdg-desktop-portal-gnome present (50.0-0ubuntu1).
## System information
- Ubuntu 26.04 LTS (resolute)
- Wayland session, ubuntu:GNOME
- gnome-shell 50.1-0ubuntu1
- gnome-control-center 1:50.0-0ubuntu6
- gnome-online-accounts 3.58.0-1
- gnome-keyring 50.0-1
- libsecret-1-0 0.21.7-2build1
- xdg-desktop-portal 1.21.1+ds-1ubuntu3
- xdg-desktop-portal-gnome 50.0-0ubuntu1
- Default browser google-chrome-stable (native .deb)
## Related upstream / Launchpad bugs
Similar but not identical symptoms — none have a fix landed, and none
mention the `NameHasNoOwner` / OAuth2 D-Bus listener registration issue
directly:
- LP #2139396 — Microsoft OAuth completes but account not persisted
(24.04, GOA 3.50)
- LP #2076192 — Cannot add Google or Microsoft account in GOA, popup
closes on Sign In (24.04)
- LP #2095445 — Unable to sign in to MS Exchange with GOA
- gnome-online-accounts!341 — Connecting to Microsoft 365 Account
hangs (Fedora 40, gnome-control-center 46.1)
This appears to be a regression / continuing bug in the OAuth2 callback
listener registered by gnome-control-center's Online Accounts panel.
The .desktop URI handler is correct end-to-end except for the final
D-Bus handoff back into the Settings process.
---
## Confirmed observations on this system
### 1. The OAuth2 D-Bus name IS registered while Settings is waiting
```
$ gdbus call --session --dest org.freedesktop.DBus \
--object-path /org/freedesktop/DBus \
--method org.freedesktop.DBus.NameHasOwner org.gnome.OnlineAccounts.OAuth2
(true,)
```
This rules out the simplest explanation (gnome-control-center never
claiming the name). The failure must be on the goa-oauth2-handler
side of the D-Bus call — different bus, dropped owner mid-callback,
or environment-stripped handler launch.
### 2. Extra journal capture for the report
(Note: the obvious filter `journalctl _COMM=gnome-control-center` does
not work because `_COMM` is truncated to 15 chars in the journal — the
process appears as `gnome-control-c`. Filter by substring instead.)
```
journalctl --user -b -S today | grep -iE 'goa|oauth|onlineaccount|gnome-control'
```
Attach the output. The key line to confirm is reproducing on every
Continue click:
org.gnome.OnlineAccounts.OAuth2.desktop[...]: Failed to forward
authorization response: ... NameHasNoOwner ...
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: gnome-control-center 1:50.0-0ubuntu6
ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0
Uname: Linux 7.0.0-15-generic x86_64
ApportVersion: 2.34.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue May 19 19:41:49 2026
InstallationDate: Installed on 2026-03-09 (71 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to resolute on 2026-05-19 (0 days ago)
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug resolute wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2153268
Title:
goa-oauth2-handler / D-Bus environment
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2153268/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
