Bazaar won’t open after the first update on a fresh Aurora install

[lenny892]

Hello,

I’m running Aurora stable on KDE Plasma (Wayland) and I’m seeing a reproducible Bazaar issue right after a fresh install + first system update. I’ve installed Aurora twice from scratch and hit the same thing both times: Bazaar works immediately after the initial install, but after applying the first rpm-ostree update and rebooting into the updated deployment, Bazaar stops opening. No window appears, and launching it again does nothing. When it was stuck, I also saw: Failed to register: Timeout was reached.

What fixes it immediately is killing the stuck instance and starting Bazaar again:

flatpak kill io.github.kolunmi.Bazaar
flatpak run io.github.kolunmi.Bazaar

Since it happened again after reboot/login, I used a simple system-wide workaround so Bazaar can’t block itself: a systemd user oneshot that runs the same flatpak kill once on every login (for all users). This makes Bazaar usable after every reboot/login:

sudo tee /etc/systemd/user/bazaar-kill-on-login.service >/dev/null <<'EOF'
[Unit]
Description=Kill stuck Bazaar Flatpak instance on login
After=graphical-session.target
Wants=graphical-session.target

[Service]
Type=oneshot
ExecStart=-/usr/bin/flatpak kill io.github.kolunmi.Bazaar

[Install]
WantedBy=default.target
EOF

sudo systemctl --global enable bazaar-kill-on-login.service

System details: Aurora stable 43.20260203 (updated from 43.20260127), KDE Plasma on Wayland, Bazaar Flatpak 0.7.7 from Flathub.

Is this a known regression in the current Aurora image / Bazaar integration? If you tell me what logs you want captured, I can provide them the next time I reproduce the broken state.

Thank you.

[renner0e]

Can you remove your service first and then switch over to a :latest image temporarily to see if the issue still happens?

Or edit the current service you have on your system, sadly this change hasn't made it into a :stable image yet.
get-aurora-dev/common#113

[renner0e]

Is this a known regression in the current Aurora image / Bazaar integration? If you tell me what logs you want captured, I can provide them the next time I reproduce the broken state.

Any issues users reported we couldn't ever reproduce.
Logs were basically all useless that I have seen so far.

We introduced the background service in October of last year but reports of something not working I'm regards to bazaar have been pickup up lately. It wasn't changed since the introduction, other than the change form last week.

[lenny892]

Thanks — I tested this on :latest as well (latest-43.20260209) with my workaround removed, and the issue still reproduces.

Which exact commands/output would you like me to capture when it happens again? I can paste whatever you need.

[renner0e]

journalctl --user -u bazaar, newest output at the bottom, tho this has been pretty useless so far when people had various issues with bazaar. I don't expect it to be different.

It would be nice if someone with this issue dug deeper into this as no developer could ever reproduce this.

[renner0e]

For the time being, just disable it. No need to have autokill services.

systemctl --user disable bazaar.service