Quassel IRC

I will add a note for this as I have some experience with this bug. The issue is an incompatibility between the indicator-application package provided by Unity and quassel(client?). This affects Xubuntu and Ubuntu 12.10 and above. 12.04 works flawless. If you remove the indicator-application package, you get a tray icon, but lose all your Indicator stuff (volume control, battery icons, etc). Quassel-team: There have been instances in other bugs I filed on Launchpad for this that get shrugged off as being Canonical's issue, meanwhile Canonical shrugs it off as Quassel's issue... but there are plenty of other applications out there that have functioning tray icons, so I am leaning more towards this being an issue with Quassel and Canonical not playing nice. Unity isn't going anywhere, so I hope that sometime in the future we can get both teams working together towards a resolution. Quassel and Unity are both fantastic, and I would like to use them both together.

The Quassel icon works fine with anything except Unity, so I don't see how it's a Quassel issue. If there's something that's being done differently in Unity that needs a change in quassel, then someone who knows something about Unity will have to provide it. None of the Quassel devs use Ubuntu and it works fine in Kubuntu where it's mostly used.

Seems to be the same bug as https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1299872

shiznix, the patch doesn't seem to fix it for me. Is there anything else required except applying the patch, cmake -DWITH_KDE=ON; make install?

Hi al,

It should 'just work', but I'll post what info I have in the hope it can get things happening at your end.

The available SNI items exported by quassel can be listed by doing the following:
qdbus org.kde.StatusNotifierItem-$(pidof quasselclient)-1 /StatusNotifierItem

The indicator-application-service process expects the following SNI items to be present before it will show an icon and menu:
org.kde.StatusNotifierItem.Menu
org.kde.StatusNotifierItem.Id
org.kde.StatusNotifierItem.Category
org.kde.StatusNotifierItem.Status
org.kde.StatusNotifierItem.IconName

These items are checked in indicator-application package's source file src/application-service-appstore.c
Once indicator-application-service is satisfied these SNI items exist, it shows the Quassel icon as an indicator in the Unity top panel with a basic menu.

Have double checked again the patch works OK and applies to both quassel versions 0.9.3 and 0.10.0.

Hi al,

It should 'just work', but I'll post what info I have in the hope it can get things happening at your end.

The available SNI items exported by quassel can be listed by doing the following:
qdbus org.kde.StatusNotifierItem-$(pidof quasselclient)-1 /StatusNotifierItem

The indicator-application-service process expects the following SNI items to be present before it will show an icon and menu:
org.kde.StatusNotifierItem.Menu
org.kde.StatusNotifierItem.Id
org.kde.StatusNotifierItem.Category
org.kde.StatusNotifierItem.Status
org.kde.StatusNotifierItem.IconName

These items are checked in indicator-application package's source file src/application-service-appstore.c
Once indicator-application-service is satisfied these SNI items exist, it shows the Quassel icon as an indicator in the Unity top panel with a basic menu.

Have double checked again the patch works OK and applies to both quassel versions 0.9.3 and 0.10.0.
Only mandatory cmake build option I can think of is of course '-DWITH_DBUS=ON'.

Still wasn't able to successfully test this, but I guess I'm doing something wrong. At least it doesn't break anything for me, so I'll just merge it. Thanks for the patch!

This not only affects unity, but also other desktop environments like XFCE. Tested on Xubuntu Development release 15.04.

al wrote:

Reopening as I had to revert the fix due to dbus errors:
arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_path (*string_p)" failed in file dbus-message.c line 2680.

Any hints appreciated.

Try as I might, I'm unable to reproduce this.
Al are you getting this error during building or at runtime ?

Patch still applies cleanly and works for versions 0.9, 0.10, 0.11 and 0.12 of Quassel here.

Works fine for me as well, so this patch is coming back as part of the on-going systray refactoring.

Actually, our SNI interface definition had the wrong types for pixmaps. This should be unrelated to this patch, but maybe one of the desktop environments al tested on that ignored Quassel without the new properties then started to support Quassel, and tried to marshall the (empty) pixmaps. KDE/Plasma don't do this, because they check if the argument is empty before trying to deserialize it, but maybe Unity behaves differently...