Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status icon for GTK3 applications present but not visible. #23

Closed
ArthurBorsboom opened this issue Mar 28, 2014 · 3 comments
Closed

Status icon for GTK3 applications present but not visible. #23

ArthurBorsboom opened this issue Mar 28, 2014 · 3 comments

Comments

@ArthurBorsboom
Copy link

Hi,

Recently I have noticed that two GTK3 applications (Audacious and Xpad) who both use a GtkStatusIcon have the status icon working in the systray (all functionality works), but the icon itself is transparent / invisible.

Before I thought that GTK3, the applications, theme, or Arch environment might be to blame, but maybe it is an lxqt-panel issue.

Please read the bugreport which I started at Audacious for details and a screenshot.
http://redmine.audacious-media-player.org/issues/422

Do you have any idea what could be causing this issue?

@ArthurBorsboom
Copy link
Author

I have noticed a positive change in behavior, due to a recent update to lxqt-config.

Since this commit it is possible to select the Qt widget style. On default my widget style is on GTK+. When I change it to any other style, the GTK3 status icon of Audacious becomes visible. When I change back to GTK+, it stays.

An uneducated guess is that lxqt-panel does not update the Qtree completely. Below the screenshot of the new lxqt-config menu where I change the widget style.

2014-04-08-224115_552x384_scrot

Does this help enough to fix this issue?

PCMan added a commit that referenced this issue Apr 12, 2014
@PCMan
Copy link
Member

PCMan commented Apr 12, 2014

I did some dirty hacks to workaround this bug. It might not be the optimal solution.
However since the notification area (systray) spec is deprecated, spending to much time on it is a waste. So some workaround to make it work is enough, I think.
Please confirm that if this fix your problem. If not, please re-open the bug.

@PCMan PCMan closed this as completed Apr 12, 2014
@ArthurBorsboom
Copy link
Author

I confirm the issue has been resolved.
Thanks mate! Good work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Issues
  
Ancient
Issues
  
Done
Development

No branches or pull requests

2 participants