Sorry everyone, the fix is in Bodhi now. I'll be more careful from now on.

Pushing Freon version 36 to F29 was a mistake. As far as I can tell package version numbers aren't allowed to move backward, and it's too late to "unpush" v36 to F29. So I guess I'll need to add an Epoch to the package?

@tomporter518

Oh, shit, you're right.

https://github.com/UshakovVasilii/gnome-shell-extension-freon/issues/131

This update has been unpushed.

Works for me, thanks!

Works for me.

@alciregi Are you using GNOME with Wayland? Another user ran into a similar issue with the previous version of this package, and after some troubleshooting, I suspect the problem might be that Wayland still doesn't support status icons very well.

https://bugzilla.redhat.com/show_bug.cgi?id=1573771

You could try switching to GNOME with Xorg by logging out, and then clicking on the gear icon in the login screen, and see if that helps.

If not, I'd appreciate it if you could look for possible error messages in Looking Glass, GNOME's interactive console. Hit Alt-F2, type "lg" (without the quotation marks), and hit Enter. This will launch the console as a translucent dialog that slides down from the top of the screen. In the top-right corner of the window, click on Extensions. Scroll down until you see TopIcons Plus. At the bottom of its box, at the end of the line of text, click on Show Errors.

Unfortunately, Looking Glass doesn't seem to allow copying the text in the Extensions tab, and you can't interact with other applications while lg is active, so if you see many errors, it might be easier to take a screenshot instead.

You dismiss the lg window by hitting Escape when you're done.

This update has been unpushed.

This update has been unpushed.

Tested in a virtual machine of Fedora 24 Workstation x86_64. Works for me.

Tested in a virtual machine of Fedora 25 Workstation x86_64. Works for me.

Tested in a virtual machine of Fedora 26 Workstation x86_64. Works for me.

I'm also discussing the risk (if any) of using lm_sensors, on the Fedora devel mailing list, if you want to follow along, or if you have any answers.

I'm also discussing the risk (if any) of using lm_sensors, on the Fedora devel mailing list, if you want to follow along, or if you have any answers.

I'm also discussing the risk (if any) of using lm_sensors, on the Fedora devel mailing list, if you want to follow along, or if you have any answers.

I'm also discussing the risk (if any) of using lm_sensors, on the Fedora devel mailing list, if you want to follow along, or if you have any answers.

Tested in a virtual machine of Fedora 26 Workstation x86_64.

You have to run sensors-detect before this extension is usable, which I left as an exercise for the user, for now, since there's supposedly some risk to the system's hardware. Until then, Freon does show a warning about needing to run sensors-detect in a balloon when the user clicks on the extension's button in the top bar. Works for me.

Tested on my desktop, running Fedora 25 Workstation x86_64.

You have to run sensors-detect before this extension is usable, which I left as an exercise for the user, for now, since there's supposedly some risk to the system's hardware. Until then, Freon does show a warning about needing to run sensors-detect in a balloon when the user clicks on the extension's button in the top bar. Works for me.

Tested in a virtual machine of CentOS 7 x86_64.

You have to run sensors-detect before this extension is usable, which I left as an exercise for the user, for now, since there's supposedly some risk to the system's hardware. Until then, Freon does show a warning about needing to run sensors-detect in a balloon when the user clicks on the extension's button in the top bar. Works for me.

Tested in a virtual machine of Fedora 24 Workstation x86_64.

You have to run sensors-detect before this extension is usable, which I left as an exercise for the user, for now, since there's supposedly some risk to the system's hardware. Until then, Freon does show a warning about needing to run sensors-detect in a balloon when the user clicks on the extension's button in the top bar. Works for me.