User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/11.10 Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19 Build Identifier: Every time I watch a videos in full screen on my kubuntu (also happened on chakra archimedes) I can not click in the youtube's bottom bar (as, for example, play / pause, change volume, change resolution, and exit the full screen too). But if I put the always visible option in the panel, I can change all this things. I use the nvidia proprietary driver. Reproducible: Always Steps to Reproduce: 1.Put the auto hide option in the panel 2.Play a full screen youtube video 3.Try to modify the volume or exit full screen... Actual Results: I'm not able to change the things in youtube's panel My pc is an HP Pavilion DV5-1199el notebook with nVidia GeForce 9600M GT video card.
Please watch the video attached for precisions... http://youtu.be/bayUIh5_ZeU
This bug is still present in the Kubuntu 12.04 LTS release.
Look at https://bugs.kde.org/show_bug.cgi?id=305497 It seems that this is one bug. And my patch fixes your issue too.
Still present in Chakra GNU/linux, with KDE 4.9. Thanks Alexey, but I don't understand how to use your patch?
(In reply to comment #4) > Still present in Chakra GNU/linux, with KDE 4.9. > Thanks Alexey, but I don't understand how to use your patch? It needs to be submitted to reviewboard to be implemented.
*** Bug 305497 has been marked as a duplicate of this bug. ***
(In reply to comment #5) It is submitted already. https://git.reviewboard.kde.org/r/106110/
I'm running Fedora 17 KDE 4.9.1, and this bug has plagued me since I upgraded from Fedora 15. This bug strongly affects my work-flow which involves the use of remote desktops in full-screen mode. All bottom-task-bar operations are not possible in full-screen mode, requiring me to constantly switch between full-screen and window mode. The work-around is to change the panel settings from auto-hide to windows-can-cover. I'm not complaining... just adding my voice on usability.
*** This bug has been marked as a duplicate of bug 217560 ***