Unable to add Icon Task List applet to the panel

[NextAlex]

Description

I wanted to move the applet to the side panel.
So I removed the applet from the bottom and cannot add it any more.

Budgie version

budgie-desktop 10.5.3 (git-26cde8fd300a87aba0d085ca50c89728150138d2)

Operating system

Solus 4.3 Fortitude

Steps to reproduce the issue

• Remove all existing Icon Task List applets from all the panels
• Try to add Icon Task List applet to a panel

Actual result

Screen blinks for a moment, no applet added, no error shown

Expected result

Icon Task List applet added to the panel

Additional information

[guillotjulien]

@NextAlex can you try to run the panel through gdb to see if you got an error (https://github.com/solus-project/budgie-desktop/wiki/Providing-Backtraces)?

[NextAlex]

budgie-panel-gdb.txt

[guillotjulien]

I might be wrong, but from the stack trace it seems that it cannot find Raven dbus interface. Can you print the result of the following command? dbus-send --print-reply --dest=org.budgie_desktop.Raven /org/budgie_desktop/Raven org.budgie_desktop.Raven.ClearNotifications

You can also try to reinstall budgie (sudo eopkg it budgie-desktop --reinstall) and reboot to see if it fixes the issue (I tried with the same version without having the issue)

[NextAlex]

Hi, @guillotjulien

The command ran without error:

alex_v@alexv ~ $ dbus-send --print-reply --dest=org.budgie_desktop.Raven /org/budgie_desktop/Raven org.budgie_desktop.Raven.ClearNotifications

method return time=1633064515.370758 sender=:1.37 -> destination=:1.112 serial=171 reply_serial=2

After that I reinstalled budgie and rebooted laptop, but the issue still present.
I tried to repeat your dbus testing command and result is the same:

method return time=1633064857.710181 sender=:1.101 -> destination=:1.113 serial=161 reply_serial=2

Also I have to tell that the issue appears only when I try to add the Icon Task List applet, others I can add-remove without any troubles. And it behaved so since the moment I installed Solus on this laptop - a couple of days after the 4.3 release (just because only that release added support of my hardware to Solus).