search

UbuntuBudgie / budgie-indicator-applet

Application Indicator Applet for the budgie-desktop
11 stars 4 forks source link

App Icons not shown after updating to Ubuntu 24.04 #30

Closed tomasnorre closed 5 months ago

tomasnorre commented 5 months ago

Hi,

After updating to Ubuntu 24.04 (budgie). I don't have any applications icons in the Indicator Applet. I use to have for slack, variety and so on. I get following errors when trying to debug my indicator-applet.

G_MESSAGES_DEBUG=Indicator-Applet-DEBUG budgie-panel --replace

** (budgie-panel:3030647): WARNING **: 21:17:42.059: PowerIndicator.vala:66: Failed to refresh battery: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method Refresh is not implemented on interface org.freedesktop.UPower.Device

** (budgie-panel:3030647): WARNING **: 21:17:43.980: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0: The ID supplied 53 does not refer to a menu item we have

** (budgie-panel:3030647): WARNING **: 21:17:43.980: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0: The ID supplied 54 does not refer to a menu item we have

** (budgie-panel:3030647): WARNING **: 21:17:43.980: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0: The ID supplied 55 does not refer to a menu item we have

** (budgie-panel:3030647): WARNING **: 21:17:43.980: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0: The ID supplied 56 does not refer to a menu item we have

** (budgie-panel:3030647): WARNING **: 21:17:43.980: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0: The ID supplied 57 does not refer to a menu item we have

** (budgie-panel:3030647): WARNING **: 21:17:43.980: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0: The ID supplied 58 does not refer to a menu item we have

This is the errors I get when starting slack.

Let me know if I can help by providing more information.

fossfreedom commented 5 months ago

Try creating another account and see what happens. This will confirm if its a system wide issue or localised to this one account

tomasnorre commented 5 months ago

Strangely, it didn't work for the newly created user, but after logging in with my primary user again, it worked for that account. I'll close the issue and accept it as a hiccup.