Project

General

Profile

Bug #422

Tray icon invisible in LXDE-Qt

Added by Arthur Borsboom about 11 years ago. Updated about 11 years ago.

Status:
Rejected
Priority:
Minor
Assignee:
-
Category:
plugins/statusicon
Target version:
-
Start date:
March 27, 2014
Due date:
% Done:

0%

Estimated time:
Affects version:

Description

The audacious tray icon is in the systray and functioning, but not visible, see attachment.
It seems to be exactly the same issue as bug #121, however the offered solutions do not resolve the issue.

Things I have tried, but did not work:
  • Removing directory ~/.config/audacious
  • Rebuilding icon cache with "update-desktop-database -q" and "gtk-update-icon-cache -q -t -f /usr/share/icons/hicolor"
  • Changing to nvidia binary driver (I have a Intel videocard).
Things that are different than in bug #121:
  • I use LXQT instead of KDE (but both are based on Qt)
  • I have an Intel videocard instead of a Nvidia
All my other status icons do work
  • wicd
  • insync
  • xpad (uses GtkStatusIcon too)
  • volume

Using Arch with Lxqt with Audacious 3.5-beta1 (03/27/2014)

My gut feeling says it is an installation issue of Audacious or the Qt/Gtk environment.
Do you have any suggestions other than the above to try to fix this issue?

Thanks in advance!

audacious-missing-tray-icon.png (111 KB) audacious-missing-tray-icon.png Arthur Borsboom, March 27, 2014 21:50

History

#1 Updated by John Lindgren about 11 years ago

So what do you expect Audacious developers to do? It's not like there's a magical gtk_status_icon_show_in_lxqt() function we can call to fix this.

#2 Updated by Arthur Borsboom about 11 years ago

Hi John,

I am not sure if the cause is in Audacious or in the environment. But I do know, that my sticky notes application Xpad, uses the GtkStatusIcon too and it does show up. There is no magic lxqt code involved. :)

Maybe it has something to do with the way the icon theme is set in Audacious?
Here is a piece of 'tray-code' extracted from Xpad, maybe that helps?

static GtkStatusIcon  *docklet = NULL;
static GtkWidget *menu = NULL;

void
xpad_tray_open ()
{
    GtkIconTheme *theme;

    theme = gtk_icon_theme_get_default ();

    if (!gtk_icon_theme_has_icon (theme, PACKAGE)) {
        return;
    }

    if (gtk_icon_theme_has_icon (theme, "xpad-panel"))
    {
        docklet = gtk_status_icon_new_from_icon_name ("xpad-panel");
    }
    else
    {
        docklet = gtk_status_icon_new_from_icon_name (PACKAGE);
    }

    if (docklet)
    {
        g_signal_connect (docklet, "activate", G_CALLBACK (xpad_tray_activate_cb), NULL);
        g_signal_connect (docklet, "popup-menu", G_CALLBACK (xpad_tray_popup_menu_cb), NULL);
    }
}

Does this give you some inspiration for analyzing this issue?

Cheers,
Arthur.

#3 Updated by Arthur Borsboom about 11 years ago

Hi John,

I have an interesting discovery to share.

The Xpad version where the status icon works, is version 4.2. I have developed and released this version. It is based on GTK2.

Now, I had a hunch that GTK3 might be part of the cause of this. I looked up the GTK version of Audacious and it is GTK3. Let's not go into my annoyances of GTK, so ... <forget, darned, forget> :)

I compiled a GTK3 version which I was developing of Xpad, v4.3. And of course you can guess it by now: the status icon has exactly the same behavior as Audacious.

If I have more new information regarding this topic, I will share it.
If something comes up on your mind, please feel free to share.
That can help.

Cheers,
Arthur.

#4 Updated by John Lindgren about 11 years ago

Maybe the GTK3 version is using a newer/incompatible protocol that a Qt-based tray implementation does not like? That's my guess, given that it seems to be the combination of GTK3 and Qt that is the problem.

#5 Updated by Anon Ym about 11 years ago

Confirmed for Debian/Jessie with GTK+ (3.10.7-1) and Audacious (3.4.3-1).

#6 Updated by John Lindgren about 11 years ago

Anon Ym wrote:

Confirmed for Debian/Jessie with GTK+ (3.10.7-1) and Audacious (3.4.3-1).

What is confirmed?

#7 Updated by John Lindgren about 11 years ago

  • Category set to plugins/statusicon

#8 Updated by Anon Ym about 11 years ago

John Lindgren wrote:

What is confirmed?

The bug of course.

#9 Updated by John Lindgren about 11 years ago

Anon Ym wrote:

The bug of course.

Sorry, but I am still trying to figure out what "the bug" is. If you know more about it than I do, then please write a patch to fix it. Otherwise, give some details about what you are "confirming". Are you also running LXQT? Or do you use KDE on an NVidia graphics card with the nouveau driver, as in #121? Or something else entirely?

#10 Updated by Arthur Borsboom about 11 years ago

Hi John,

... given that it seems to be the combination of GTK3 and Qt that is the problem.

This is my current assumption too.
Do you feel like investigating this issue together?

If no, I will switch audio player and we can close this bug report.
If yes (what I prefer), do you have some suggestions how to approach this?

#11 Updated by John Lindgren about 11 years ago

I would suggest contacting the LXQT developers about the problem first, to see if they are aware of it or can give any additional clues. Also compare the GTK2 and GTK3 status icon code looking for any difference that might cause such a problem. If you have time, you could also install KDE to check whether your GTK-vs.-Qt hunch has any merit.

#12 Updated by Arthur Borsboom about 11 years ago

Okay, that sounds like a plan.
I will go work on it.

This might take some time, though.

Cheers,
Arthur.

#13 Updated by Arthur Borsboom about 11 years ago

Step 1.

Contacting lxqt developers --> done and awaiting answer.
https://github.com/lxde/lxqt-panel/issues/23

#14 Updated by Arthur Borsboom about 11 years ago

Step 2.

Comparing GTK2 and GTK3 statusIcon source code.

I have looked at it, but this one is a bit over my head. I have not enough knowledge of GTK to be able to find a possible cause. Would you mind and look through the code to see if you can find any clues? To make it easier, here are the two different sources.

https://git.gnome.org/browse/gtk+/tree/gtk/gtkstatusicon.c?h=gtk-2-24
https://git.gnome.org/browse/gtk+/tree/gtk/gtkstatusicon.c?h=gtk-3-10

In the mean time, I will go ahead and install KDE on one of my Linux distro's to see if I can replicate the same behavior of Audacious 3.5 and Xpad v4.3 (GTK3).

#15 Updated by John Lindgren about 11 years ago

I don't see any changes in gtkstatusicon.c that should cause a problem. There could still be some subtle difference in a base class (such as GtkWidget) that is causing trouble for LXQT.

#16 Updated by Arthur Borsboom about 11 years ago

Step 3.

Testing in KDE

I have installed on an existing Lubuntu environment (LXDE), the package kubuntu-desktop (KDE). I have logged into KDE and started Audacious with the status icon plugin enabled. The icon was visible, concluding to me that Qt is not the issue. Maybe it is a mix of things, or something currently out of our scope.

What do you suggest next?

#17 Updated by John Lindgren about 11 years ago

  • Subject changed from Tray icon invisible to Tray icon invisible in LXDE-Qt

All right, we know that the icon shows up fine in KDE, XFCE, and old-style LXDE (I tested the last two). So only in LXQT is there a problem. I am therefore inclined to assume that there is a flaw in LXQT -- but we should wait and see what response comes back from the LXQT developers.

#18 Updated by Arthur Borsboom about 11 years ago

Agreed. Thanks John.

#19 Updated by Arthur Borsboom about 11 years ago

Hi John,

I had an interesting discovery regarding this issue.
Please read my comment here.

https://github.com/lxde/lxqt-panel/issues/23

Cheers,
Arthur.

#20 Updated by Arthur Borsboom about 11 years ago

Hi John,

As we started to suspect, the issue was in LXQT.
Yesterday a patch has been released, which resolved this issue.
https://github.com/lxde/lxqt-panel/issues/23#issuecomment-40285673

You can close this bug report.

Cheers,
Arthur.

#21 Updated by John Lindgren about 11 years ago

  • Status changed from New to Rejected

Okay, not a bug in Audacious then. Closing.

Also available in: Atom PDF