Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Context I have just installed Ubuntu 13.10 from an iso on my Asus X202E and everything was working fine so far. However I discovered that the icons from the tray (dropbox, wifi, keyboard, layout, battery and so on) are not working properly.

Problem Description Most of the time when I click on them they show the menu I am expecting to see but in some cases they just do not respond at all. I then move my pointer and re-click and everything is working well. This is not a big deal but I do not understand the cause of that and I would like to fix it for a smoother use.

Note that not all the icons are not working. The three most right buttons are ok: (shutdown-system settings-...) icon, sound options and clock-calendar icons.

Solutions tried I already ran killall unity-panel-service but that did not solve the problem.

As proposed by Angel Salinas Huerta, I enabled the proposed updates in the software center and upgraded the system, but the problem is still there.

After wandering for some times on this site and some googling I hpoe to find some answers from you!

share|improve this question
Do you have problems clicking on anywhere else? – Wilf Nov 17 '13 at 22:49
@wilf Not that I know so far. Everything else is working nicely plus the icons for the (shutdown-system settings-...) menu, the sound options and the clock-calendar option work well all the time, it is only battery, mails, keyboard, wifi, bluetooth and dropbox icons which are not working. I don't have other icons there. – Ludovic C. Nov 17 '13 at 23:04
up vote 1 down vote accepted

You might be refering to this bug, wich fizx was already released but probably hasn't made it to normal updates.

You can however enable Proposed updates in Software Center>Edit>Sources and just update the mentioned packages or update the whole system.

share|improve this answer
After doing what you suggested, the problem was still there but disappeared so far after a reboot of the machine. – Ludovic C. Nov 18 '13 at 18:10

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.