Is anyone else seeing an issue with resizing the top panel? As far as I can tell the top panel does not resize between 17 and 28 pixels as seen here:
The bottom panel can be visibly seen to contract from 28 to 17 pixels, something that can be checked for yourself or I can try to make another screen capture of the bottom panel. Does anyone have a fix for this behavior?
In addition to that I’m noticing two other things:
No volume control applet in the system tray, sound works and can be found in the System ->Preferences ->Hardware ->Sound option but no applet for easy administration.
EDIT: Sound applet came back when I reset the panel, this dropped me into the Familiar Layout for some reason instead of Traditional. After several attempts to induce that behavior again I’m acting on the assumption it was a result of the new Layout being added and a one time event unlikely to be experienced by anyone using a final release. I did want to mention it so you have a data point in case it happens to anyone else. Sound applet is there again and that’s great.
No shutdown button. (If this is intentional please disregard.)
EDIT: I see that the shutdown, logoff, and lock options are in the new applet that looks like a KDE icon. Is there any way to shove it on the far right side of the clock\calendar applet so it’s in the correct place? It just seems strange having it there instead of at the far right. I had thought maybe you were getting rid of it altogether and users were to shutdown from the system menu. Anyway to remove the new icon if it cannot be moved? I’d almost rather shutdown from the system menu if it can’t be moved.
Touchpad having extreme sensitivity (or seizures) from being touched. It’s almost like it’s dancing if I rest my finger on it even if I’m about to hit a button or highlight some text. Any idea what changed between Bionic and Xenial that would make this happen? Am I the only one experiencing this?
Video of the touchpad behavior:
EDIT: Thanks to @elcste for explaining what was going on here:
As I noted in that thread, the new driver seems to already have a fix so it’s just a question of time before the issue goes away altogether.
Thanks.