Crystalline: +1
Grand Canyon: +1
Vera: +1
Beach: +1
Flow Dark: -1
Altai: -1
Milky Way: -1
Rainy Morning: -1
Slant: -2
Kay: -2
Iridescent Shell: +2

Ironically, if shortcuts are filtered for "hide" or "border", Hide Window border is the only option. I don't use meta+b so we use both meta+B and meta+H as primary and secondary.

I use meta+H to "hide" the borders.

2 laptops and a desktop tested with fw 5.52. All working as expected. Nice job, greatly appreciated.

Works perfect with ppa enabled. Love it.

I had to manually set the wallpaper type to "image" and the default image was available. It's looked great as a lock screen.

Oops, actually closing (resolving) this time.....

Closing this task as it it fixed in 18.04.

Network connected without double password prompt via Ubiquity and from the live boot panel icon (rebooted to test both). All secure networks were correctly marked as "secure".

I tried 3 different ways to reproduce on modern laptop (UEFI BIOS):

• panel
• during install from live
• straight to install.

/me loves the "Set Sail for Adventure" button.

I take that back, one system had a slight issue as I mentioned in Kubuntu:

3 machines upgraded here without issue (just in case we are taking a poll) :)

The plasma team rocks. They have already submitted an update mirroring pavucontrol behavior, but the fix lands in plasma 5.11. Thus, I still vote for including pavucontrol-qt in the iso as it prevents a "paper cut" experience.

I like the list as it meets the needs of both new and experienced users. I personally don't use Kontact or Discover, but they are easy to remove.

mtpfs is now working splendidly on my AA install.

QT 5.9.1 is stable on 2 boxes (real HW) here.

I am working on ksudoku. I successfully built it locally but game does not run correctly: it launches but nothing is drawn in window once game type is selected.

16.04 on real hw upgraded to 5.8.7 without issue.

Upgrade update to backports landing, frameworks 5.34:

• Zesty1 (real hw) required terminal login and startx
• Zesty2 (real hw) no issues
• Zesty3 (real hw) no issues
• Yakkety (real hw) no issues
• Xenial (real hw) required termial login and startx

Apologies for the omission: I updated Zesty. I should be able to test XX, YY and another ZZ box after work.

Updated real HW on an Intel box. When I restarted, sddm failed to start, so I logged in to the terminal and ran startx.

2 real hw 17.04 systems updated to backports landing here without issue. One of these days I will unpack my 16.04 box... maybe tomorrow.