Bug 1215338 - No icon for bluedevil-monolitic in XFCE
Summary: No icon for bluedevil-monolitic in XFCE
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: bluedevil
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Reznik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-25 15:47 UTC by Jason Montleon
Modified: 2015-04-30 17:17 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-04-27 02:54:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jason Montleon 2015-04-25 15:47:04 UTC
Description of problem:
In Fedora 21 it was possible to run bluedevil-monolithic in XFCE and get an icon in the notification area. In Fedora 22 I get no icon.

Version-Release number of selected component (if applicable):
bluedevil-5.2.2-1.fc22.x86_64
xfce4-session-4.12.1-3.fc22.x86_64
xfce4-panel-4.12.0-3.fc22.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install Fedora 22 with XFCE and bluedevil
2. Run bluedevil in XFCE

Actual results:
No icon

If run from the terminal I get only:
$ bluedevil-monolithic 
service is "org.kde.StatusNotifierItem-10298-1"
Registering a client interface to the KStatusNotifierWatcher
KStatusNotifierWatcher not reachable
QSystemTrayIcon::setVisible: No Icon set
QSystemTrayIcon::setVisible: No Icon set

Expected results:
Icon on the panel.

Additional info:

Comment 1 Rex Dieter 2015-04-25 16:49:22 UTC
Fwiw, the icon it uses is:

preferences-system-bluetooth
and
preferences-system-bluetooth-inactive

perhaps your icon theme doesn't provide those?

do you have oxygen-icon-theme installed?

Comment 2 Rex Dieter 2015-04-25 16:50:26 UTC
Fwiw, it looks like as of plasma-5.3 coming soon that the bluetooth systray applet may switch to using plasma natively (meaning it likely won't be functional outside of a plasma5 environment anymore).

Comment 3 Jason Montleon 2015-04-27 00:02:47 UTC
I do:
$ rpm -q oxygen-icon-theme
oxygen-icon-theme-15.04.0-1.fc22.noarch

I tried selecting the Oxygen icon theme in preferences, saw things change, restarted bluedevil-monolithic, and no difference, still no icon.

That unfortunate, re: needing a plasma5 environment down the road. I think Xfce, MATE, and other non-Gnome/KDE environments have been leaning on bluedevil since blueman went away. 

On the plus side it looks like blueman is getting some love again and I was going to package up the new version before seeing at least a dependency or two also requiring update. Probably not too hard to get done regardless, but I'd love to see a supported package working.

Comment 4 Rex Dieter 2015-04-27 02:54:09 UTC
Just confirmed bluedevil-5.3 indeed moves to a plasma5-native applet.  See:
https://admin.fedoraproject.org/updates/bluedevil-5.3.0-1.fc22

marking CANTFIX, sorry.

Comment 5 João Carlos Mendes Luís 2015-04-30 13:52:45 UTC
Hey, it also does not work on fc21.

I already have oxygen-icon-themes installed.  What is the workaround, if any?

If it is a dependecy rpm, should'nt it be added to bluedevil requirements?

Comment 6 Jason Montleon 2015-04-30 16:45:55 UTC
As Rex explains it can't be fixed.

You can use this blueman repo from COPR. It seems to work:
https://copr.fedoraproject.org/coprs/heikoada/blueman-git/

Comment 7 Rex Dieter 2015-04-30 16:53:00 UTC
it can't be fixed for f22+ true, but f21 could possibly include workarounds like
* possibly using a different icon available in more themes
* include/use it's own icon put into hicolor theme

anyone interested in that, please open a new/separate bug (this one was for f22)

Comment 8 João Carlos Mendes Luís 2015-04-30 17:17:59 UTC
It CAN be fixed, at least on fc21.

After reading that it has been changed to use KDE Plasma, I installed LOTS of kde and plasma related packages, just for fun.  And now, I can see the icon, perfectly.

Anyway, I have opened a new bug, bug 1217573

Thanks.


Note You need to log in before you can comment on or make changes to this bug.