Jaunty Beta: The new backlight brightness indicator on the display does not work

Hi Christoph, thanks for your bug report! I think this is a duplicate of bug 344385, can you check it out? It should occur if you are using a non-default icon set. It should also be fixed in the latest version of notify-osd (apt-cache policy notify-osd).

If you are using a different icon set and updating fixes the issue for you (run update-manager, check for updates, and install them), let me know and I'll mark this as a duplicate. Otherwise comment with the output of "apt-cache policy notify-osd" and anything else special about your set up!

Michael Rooney, thanks for checking.

Bug 344385: No, it's not a duplicate. I've been using the "human" icon set all the time. I've checked with several other themes (Human-Clearlooks, New Wave, Dust, Dust Sand, Clearlooks, DarkRoom). None of them works.

Everything upgraded:
$ apt-cache policy notify-osd
notify-osd:
  Installed: 0.9.7-0ubuntu1
  Candidate: 0.9.7-0ubuntu1
  Version table:
 *** 0.9.7-0ubuntu1 0
        500 http://ch.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Anything else special about my set up: Hm, I have Scim activated with complex characters, Compiz deactivated, Zattoo installed, Thunderbird instead of Evolution, often a lot of pdfs opened in evince, Kile and Kstars installed (therefore a lot of KDE packages), Wine installed, three accounts active in Pidgin... Is this the kind of information you asked for?

I forgot to give a more detailed information about what's wrong (once I understood it):

a) When I hit either of the two key combinations once, there is no icon at all for about a second. After that, the 100% extra bright icon is displayed for a short second.

b) When I hit either of the two key combinations again (before the extra bright icon disappears), the 100% (maybe 0%?) icon is displayed for about a second, followed by the short extra bright sequence.

This is completely independent of the actual brightness of the screen. It's always the same, even if hitting "up" when the brightness is already at its maximum.

Greetings Christoph! Can you update to notify-osd 0.9.9 and test it again. What you describe sounds like a regression we had for about two days, which I fixed and pushed to trunk last week.

Mirco: Thanks for taking care of this.
$ apt-cache policy notify-osd
notify-osd:
  Installed: 0.9.9-0ubuntu1
  Candidate: 0.9.9-0ubuntu1
  Version table:
 *** 0.9.9-0ubuntu1 0
        500 http://ch.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

It behaves still exactly as I reported.

A. Why is this bug marked "Incomplete"? What extra information do you need?
notify-osd is now:
  Installed: 0.9.11-0ubuntu1
  Candidate: 0.9.11-0ubuntu1
  Version table:
 *** 0.9.11-0ubuntu1 0
        500 http://ch.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

B. Now those indicators have completely vanished for sound and brightness. However, Pidgin can still use them. See Bug 359922.

I'm lost here. On my laptop volume- and screen-brightness-indicators of notify-osd are rendered as expected. Since you mention you're using the Human icon-set, that eliminates a usual error-source.

So it worked for you with notify-osd 0.9.6 and stopped working with 0.9.7?

What exactely does "does not adapt" in your initial bug-report mean? Does notify-osd not render the brightness-indicator all, or does it render the brightness-indicator in an unexpected way?

Can you tell me what versions of notify-osd and gnome-power-manager you have installed right now?

Have you updated your system to the most current versions of those two packages?

> So it worked for you with notify-osd 0.9.6 and stopped working with 0.9.7?
I don't know if it had ever worked properly, with 0.9.6 or before, as the only thing that did not work later was the brightness indicator (and I usually don't change the brightness).

> What exactely does "does not adapt" in your initial bug-report mean? Does notify-osd not render the brightness-indicator all, or does it render the brightness-indicator in an unexpected way?
0.9.7: It rendered the indicator as I described in more detail on 30 of march. https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/351850/comments/3
Later, 0.9.11: No more indicators at all, neither brightness nor volume.

> Can you tell me what versions of notify-osd and gnome-power-manager you have installed right now?
I've just done the general update and rebooted. Still no indicator for brightness and volume. However, Pidgin and the network manager applet do display proper indicators in the new black style.

$ apt-cache policy notify-osd (after the update. before it was ubuntu1)
notify-osd:
  Installed: 0.9.11-0ubuntu2
  Candidate: 0.9.11-0ubuntu2
  Version table:
 *** 0.9.11-0ubuntu2 0
        500 http://ch.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

I upgraded today from intrepid on my T60. Brightness OSD works perfectly with FN-keys, but the Volume OSD doesn't. I've extra sound buttons on my laptop, so it's no FN shortcut. I think my problem could have the same cause then Michael's one, but I also can open a new Ticket.

There was a new version of notify-osd today:
$ apt-cache policy notify-osd
notify-osd:
  Installed: 0.9.11-0ubuntu3
  Candidate: 0.9.11-0ubuntu3
  Version table:
 *** 0.9.11-0ubuntu3 0
        500 http://ch.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Still no indicator at all for both volume and brightness; it still works for pidgin and network manager.

same for me

same for me no volume/brightness, wireless connection is ok

i have this bug on ASUS eeePC 1000H with final release of ubuntu jaunty 9.04 NetBookRemix

This bug also happens on an HP 6510b notebook. Adjusting brightness works, but no OSD shows up. The notifications for sound volume etc. work, however.
Killing gnome-power-manager and hald has no effect on this - adjusting brightness works, but no OSD.

Sorry for double post, but pressing Fn+F9 or Fn+F10 (the key combination to adjust brightness on my laptop) doesn't seem to affect gnome-power-manager at all.
After killing gnome-power-manager, I ran "gnome-power-manager --verbose --no-daemon" in a console should print out a message when those buttons are pressed, but it doesn't. Pressing Fn+F8 (to show battery usage) says "Button press event type=battery".
So does that mean gnome-power-manager doesn't know about the combination being pressed?!
Could the others experiencing this problem try the same?

This bug also affect me on a Eee PC 900 with Jaunty final.

Question: Should these indicators also be present on Xubuntu (Jaunty final)? I switched to it because the Gnome version did not seem to work much smoother, and Xfce is much faster.
I have $ apt-cache policy notify-osd
notify-osd:
  Installed: (none)
  Candidate: 0.9.11-0ubuntu3
  Version table:
     0.9.11-0ubuntu3 0
        500 http://ch.archive.ubuntu.com jaunty/main Packages
but no on-screen display of any messages whatsoever, be it pidgin messages, volume or brightness.

Do you have this problem in latest Jaunty version? can you try to reproduce this in newer notify-osd versions (0.9.13/0.9.16) and check if this problem is still occurring?

Regards

As I said in comment #17, I'm not on Gnome Ubuntu any more, and in Xfce, there does not seem to be any on screen notification for anything. So I'm sorry I cannot give any feedback, except if you tell me that the package works also with Xfce, and how to activate it. (and how to install the recent versions, the installation candiate from the repositories is 0.9.11-ubuntu3)

Dear Christoph, you may find latest version for Jaunty at https://launchpad.net/~notify-osd-developers/+archive/ppa , instructions for installation are inside this page (same for all ppa repositories) ;) , up to date your version and check if you problem is still ocurring.

Regards

Ok, Kamus, there we are with $ apt-cache policy notify-osd
notify-osd:
  Installed: 0.9.13-0ubuntu0~1
  Candidate: 0.9.13-0ubuntu0~1
  Version table:
 *** 0.9.13-0ubuntu0~1 0
        500 http://ppa.launchpad.net jaunty/main Packages
        100 /var/lib/dpkg/status
     0.9.11-0ubuntu3 0
        500 http://ch.archive.ubuntu.com jaunty/main Packages

But there is still no on screen notification at all for volume, brightness or pidgin. There are some little flags telling me things about the network manager or so, but that's it.
To make sure I'm well understood: There is no gnome here, not even installed, I'm running Xubuntu, i.e. Xfce, and I've never seen the on screen messages I used to get from gnome on the same computer.

to clarify one detail: the little flags I mentioned in the last post had been there before I installed notify-osd (which was not installed before). I assume they come with the Xfce panel.

I have downloaded and installed the new osd-notify from the PPA on Eeepc 1000H and there is no change.
That is to say I have no brightness indicator when adjusting brightness with F keys (it does adjust), however the brightness osd appears when the power supply charge plug is inserted or removed.
Sound osd works, but I mapped a shortcut some time ago to solve this.

BTW forgot to add brightness osd on my Eeepc 1000H with Karmic Alpha 3 works ok.

I found at https://wiki.ubuntu.com/Xubuntu/Specifications/Karmic/NotifyOsd some interesting information, I will focus in exactly these paragraphs:

*Audio notifications
It may be merged in the mixer for XFCE 4.8, but there should be little work.

*The purpose is to replace notification-daemon by notify-osd as a notification server for Karmic, and to ensure the Xubuntu applications are compliant with notify-osd.

PD: note all this changes will be apply in Ubuntu Karmic and I known main problem of this report is with brightness notifications ;)

With with eee-control (http://greg.geekmind.org/eee-control/) the brightness osd is back.

Thanks for the bug report. can anyone please confirm if this is still an issue with ubuntu 10.10

Note: that some(?) systems dont show a notification for brightness changing as I last saw such notification in Karmic I think.