Flatpak desktop entry launches bazaar-daemon instead of the Bazaar GUI

[altiacpd-ship-it]

Description

The Bazaar menu entry does not open the application window.

The application launches correctly from a terminal with:

flatpak run io.github.kolunmi.Bazaar

However, the desktop/menu entry launches bazaar-daemon instead:

flatpak run --branch=stable --arch=x86_64 \
  --command=bazaar-daemon --file-forwarding \
  io.github.kolunmi.Bazaar @@u %U @@

This fails with:

(bazaar-daemon): Failed to acquire bus name
io.github.kolunmi.Bazaar.SearchProvider:
Transport endpoint is not connected

The installed desktop file contains:

Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=bazaar-daemon --file-forwarding io.github.kolunmi.Bazaar @@u %U @@

Changing the launcher to:

Exec=/usr/bin/flatpak run io.github.kolunmi.Bazaar

makes Bazaar start normally.

System information

• OS: Linux Mint 22.3 Zena
• Desktop: Cinnamon 6.6.9
• Session: X11
• Kernel: 6.17.0-42-generic
• Architecture: x86_64
• Hardware: MSI Modern 15 F1MG
• GPU: Intel Raptor Lake-U integrated graphics
• Flatpak: 1.14.6
• Remote: Flathub
• Bazaar: 0.9.2
• App ID: io.github.kolunmi.Bazaar
• Runtime: org.gnome.Platform/x86_64/50
• Installation: system-wide

Expected behavior

Launching Bazaar from the desktop/menu entry should open the Bazaar GUI.

Actual behavior

The menu entry launches bazaar-daemon, which fails to acquire its D-Bus name and exits without displaying the application window.

Workaround

Launching this command works:

flatpak run io.github.kolunmi.Bazaar

Please check whether the Flatpak desktop entry should launch bazaar instead of bazaar-daemon.

[renner0e]

I'm pretty confident that this is #1798

[mbennette68]

Hello,

I had the same issue in Ubuntu 24.04.4 LTS and changed both Exec lines in the .desktop file to:
Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --file-forwarding io.github.kolunmi.Bazaar @@U %U @@

After that change, launching via GNOME Icon works.

On my system, it also works via the terminal using: flatpak run --verbose io.github.kolunmi.Bazaar

Is the daemon needed for something else, such as background update checks?

Thank you,
MB

[VisualFox]

Ubuntu 24.04.4 LTS

Clicking the icon in GNOME shows nothing, but "flatpak run io.github.kolunmi.Bazaar" works fine.
I can confirm that removing "--command=bazaar-daemon" works.

Created a local override in ~/.local/share/applications/ to survive future update and until a fix came out.

Thank you!

[mbennette68]

Hello,

Confirm that version 0.9.3 as shown below has the same issue with GNOME icon.
The .desktop file has the following entry:

Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=bazaar-daemon --file-forwarding io.github.kolunmi.Bazaar @@U %U @@

I've also added the local override file mentioned above 'til the issue is addressed.

[diogopessoa]

I have the same issue.

System information:

• OS: AlmaLinux 10.1 (Heliotrope Lion) x86_64
• Kernel: Linux 6.12.0-124.45.1.el10_1.x86_64
• DE: GNOME 47.8
• Wayland
• Bazaar: 0.9.3 (vcs=23d97c2)

[Edited]

Now Bazaar doesn't open even with the command in the terminal:

flatpak run io.github.kolunmi.Bazaar

** (process:5774): WARNING **: 11:59:13.884: Invalid message header read
(bazaar-daemon): Failed to acquire bus name io.github.kolunmi.Bazaar.SearchProvider: Transport endpoint is not connected

However, on my Fedora Silverblue 44 GNOME 50, Bazaar opens normally without any adjustments.

[renner0e]

flathub/io.github.kolunmi.Bazaar#154 got merged, is this still an issue after this?

[mbennette68]

Ubuntu 24.04.4 LTS

Took out the io.github.kolunmi.Bazaar.desktop from ~/.local/share/applications which had no --command=bazaar-daemon entry in it. Clicked on GNOME icon which still has that entry in it, Bazaar does not start, just get spinning circle above the Dock. Used the terminal to start Bazaar and got the following error:

flatpak run io.github.kolunmi.Bazaar

** (process:12048): WARNING **: 12:35:12.146: Invalid message header read
(bazaar-daemon): Failed to acquire bus name io.github.kolunmi.Bazaar.SearchProvider: Transport endpoint is not connected

Tried to put original file back in to ~/.local/share/applications but could not start Bazaar in any form. Also, rebooted and still app refuses to start.

I tried the following:

latpak kill io.github.kolunmi.Bazaar
pkill -f bazaar || true
flatpak update io.github.kolunmi.Bazaar

I tried to run bazaar from the terminal using:
flatpak run --command=bazaar io.github.kolunmi.Bazaar

WARNING: Glycin running without sandbox.

** (bazaar:2): WARNING **: 13:54:43.495: Failed to load malcontent app filter: App filtering is globally disabled

(bazaar:2): Gtk-WARNING **: 13:54:43.531: GtkBox 0x5b6dbec57e60 (box) reported min height 656 and natural height 620 in measure() with for_size=900; natural size must be >= min size

(bazaar:2): Gtk-WARNING **: 13:54:43.649: GtkBox 0x5b6dbec57e60 (box) reported min height 656 and natural height 620 in measure() with for_size=900; natural size must be >= min size

(bazaar:2): Gtk-WARNING **: 13:54:51.520: GtkBox 0x5b6dbec57e60 (box) reported min height 656 and natural height 620 in measure() with for_size=900; natural size must be >= min size

It came up as shown below. Still can't run via icon, however.

[Max-Q]

I have the exactly the same problem as mbennette68 under Ubuntu 24.04 LTS. Even with the newest version of Bazaar 0.94.

[Max-Q]

Giving Bazaar access to the d-bus session bus (via flatseal) seems to fix the problem. At least it starts now for me.

[diogopessoa]

Giving Bazaar access to the d-bus session bus (via flatseal) seems to fix the problem. At least it starts now for me.

Yes, that worked for me! After I granted permission to the D-Bus session, Bazaar now launches without any adjustments to the icon's shortcut command. 👏

[mbennette68]

Bazaar v0.9.4 seems to be working now. I used Flatseal to give Bazaar D-Bus Session access to test if it worked. It did. Then I rescinded access and it still worked, though I have not rebooted the OS just to make sure. I did however remove the altered .desktop file from ~/.local and updated the menu database with xdg-desktop-menu forceupdate it still loads via the GNOME icon. Nope, spoke too soon. After a reboot, Bazaar did not load via ICON. Bazaar definitely needs D-BUS Session permission in my Ubuntu 24.04.4-LTS.

Hopefully this the next update will fix the issue.

With that being said, giving any app access to the D-Bus Session Bus is not a trivial matter from what I understand based on some research done via AI:

The D-Bus session bus (per-user/login session) is not designed as a strong security boundary. Many desktop services assume that any process that can connect to it is already trusted (same UID, same session). They often expose powerful interfaces with little or no extra authorization beyond “you’re on the bus.”

By contrast, the system bus has stricter policies and Polkit checks for privileged operations. The session bus is far more permissive by design.

There is a big list of potential hazards which I don't want to go into, so hopefully any fix that was gets done to Bazaar in the latest next release will not compromise any system :)

[camegone]

On v0.9.4, I still have the same issue. I'm using PoP!_OS 22.04.

$ flatpak run io.github.kolunmi.Bazaar
(bazaar-daemon): Failed to acquire bus name io.github.kolunmi.Bazaar.SearchProvider: Transport endpoint is not connected

[mbennette68]

On v0.9.4, I still have the same issue. I'm using PoP!_OS 22.04.

$ flatpak run io.github.kolunmi.Bazaar
(bazaar-daemon): Failed to acquire bus name io.github.kolunmi.Bazaar.SearchProvider: Transport endpoint is not connected

As a temporary fix, you can download Flatseal then toggle the D-Bus session bus setting to on as shown in the following images but be aware of the potential risks of enabling this setting as I mentioned above.

[ViniciusBRodrigues]

@mbennette68 great tip. Thanks! I had the problem in linux mint 22.3.