Ask HN: What do you want to see in Ubuntu 17.10?

1374 points by dustinkirkland ↗ HN
Howdy HackerNews!

Dustin Kirkland here, Product Manager for Ubuntu as an OS platform (long time listener, first time caller).

I'm interested in HackerNews feedback and feature requests for the Ubuntu 17.10 development cycle, which opens up at the end of April, and culminates in the 17.10 release in October 2017. This is the first time we've ever posed this question to the garrulous HN crowd, so I'm excited about it, and I'm sure this will be interesting!

Please include in your replies the following bullets:

- FLAVOR: [Ubuntu Desktop, Ubuntu Server, Ubuntu Core]

- HEADLINE: 1-line description of the request

- DESCRIPTION: A lengthier description of the feature. Bonus points for constructive criticism ;-)

- ROLE/AFFILIATION: (Optional, your job role and affiliation)

We're super interested in your feedback! Everything is fair game -- Kernel, Security, Desktop apps, Unity/Mir/Wayland/Gnome, Snap packages, Kubernetes, Docker, OpenStack, Juju, MAAS, Landscape, default installed packages (add or remove), cloud images, and many more I'm sure I've forgotten...

17.10 will be our 3rd and final "developer" release, before we open the 18.04 LTS (long term support, enterprise release) after October 2017 (and release in April 2018), so this is our last chance to pull in any big, substantive changes.

Thanks, HN!

:-Dustin

https://twitter.com/dustinkirkland

1,200 comments

[ 3.1 ms ] story [ 462 ms ] thread
Hi Dustin! - Ubuntu Desktop - Ubuntu Subsystem for Windows :) - An integrated system (Wine is not user friendly imho) to launch windows programs. - linux (and windows) user and developer. @vinnes
I may be wrong, but I don't think Canonical has the engineering resources to pull it off. Even if they did, the main issue is that Microsoft does not publish their API spec which is why Wine and ReactOS devs bend over backwards to be compatible with Windows binaries. It also does not make sense from a business perspective. Considering there is no demand for such a system outside of the very, very small number of hobbyists who run Windows games and software on Wine.
Also I want to add, if you want to use Windows programs using VirtualBox or VMWare (+ lots of RAM) is probably the way to go. The Windows stuff doesn't work on macOS either. (I even bought the CrossOver stuff ;))
The computer is already running Windows, there's no need for Wine. Just the ability to launch a Windows program from within a Linux program would do.
- FLAVOR: Desktop

- HEADLINE: An advanced mode for the file manager

- DESCRIPTION: I find that the default file manager is a bit dumb. There should be a mode to enable advanced features; like 'connect to server' when one can pick sftp. ftp, smb, nfs, vboxsf etc. It's fine if it's hidden in a configuration modal but 'advanced mode' should be an option.

- ROLE/AFFILIATION: user

Related: at the moment when a folder mounted with s3fs (Amazon S3 file system) is opened it downloads all the contents which doesn't really make any sense.
Also doesn't Midnight Commander do what you're after?
There is that already. Click 'Other locations' in the sidebar and at the bottom of the window you have 'Enter server address...' textbox. Put your sftp:// or smb:// url there. Discoverable shares (smb) will be displayed in the window.

Vboxsf is not a network redirector as it is in Windows; look for vboxfs mounts in the /media directory.

If anything, increased stability for general-purpose usage would be very nice. Increased hardware support, especially drivers for some wi-fi cards need a lot of work.

I really love Linux desktops, but they have too many stability issues/crashes to completely switch from Windows to Ubuntu or any other linux distribution.

I've been using Ubuntu as my main OS for a decade now, and I agree. Especially the UI crashes much more often than I'd like, and I always get a "there has been an error" error message at startup. Please make things more stable.
same thing here. its clunky to login and always see an error message.
- FLAVOR: Desktop

- HEADLINE: Increased stability++

I shy away from using my ubuntu laptop (dell xps developer edition, you know, the one you'd expect to be doing this really well) because

a) More often than not when starting up it gives me a "something went wrong, do you want to report it dialogue"? I've stopped bother to report it or look at what's happening because it happens so often, but I think it's X crashing at some point.

b) WiFi frequently fails to connect after hibernation, requiring a reboot.

c) There's also been some worrying threads on HN about lack of support for strong kernel power management on recent intel generations.

> WiFi frequently fails to connect after hibernation, requiring a reboot.

`sudo iwlist scan` fixes it without reboot in my case. But it is very irritating.

That WiFI issue is so annoying for me. Sometimes

`sudo systemctl restart network-manager.service` fixes it without having to reboot, other times even that doesn't work.

Yes agreed. I have this issue too.
I'll concur with the others on wifi network support.

- FLAVOR: Ubuntu Desktop

- HEADLINE: Improved wifi network support

- DESCRIPTION: Most of the time I don't have an issue, but occasionally (ok once a month at the venue that hosts our Java developer group) I have network issues that I never had when this laptop was running windows (7 or 10). Basically at this one location I can't stay hooked up to the network for more than 5 minutes without a disconnect, none of the windows/mac users around me have an issue.

- ROLE/AFFILIATION: Developer.

- FLAVOR: [Ubuntu Desktop]

- HEADLINE: Mouse to work

- DESCRIPTION: I'd like my mouse to work properly in Ubuntu (or any of my mice). When I start my laptop, my USB wireless mouse scrolls super fast. When I take it out and plug it in again, it scrolls super slow. I'd like that not to happen, and also some way of configuring the scroll speed.

Excellent support for Apple laptops.
Apple laptops are known to come with hardware with very shitty open source driver support, there's not alot Canonical can do if they don't get good drivers for the various hardware components.
1) They could improve those open source drivers.

2) They could improve the other aspects of the experience that is crap on Apple hardware, like display connection/disconnection, sleep/wake, battery life adjustments, keyboard layouts, et c. It takes about a full day to make a mac not suck after installing Ubuntu.

Everything works fine on my MBP except that the desktop is a postage stamp and unusable on the retina display. I tried making things scale but different programs pick up different settings from different places and most look atrocious.
... and sometimes they have even better support than macOS. ;-)

E.g. the 2016 Apple MacBook Pro with TouchBar supports DisplayPort-daisy-chaining, while under macOS you can only daisy-chain monitors if they support Thunderbolt.

Wow, I didn't even know DisplayPort daisy-chaining was a thing
- FLAVOR: Desktop

- HEADLINE: More stable and polished desktop

- DESCRIPTION: This one is hard to pin down, but I'd like to see more general polish and stability in the Unity desktop. One example would be around multi-monitor support, it's pretty good, but a bit funky in some places.

For example, if I have a monitor plugged in and I let the laptop screen lock come on, I can sit there and watch while both displays cycle through an On -> Off -> On -> Off loop. I think when one display goes to sleep it sends a signal which wakes the machine back up, or something.

I'd also like to see more options for configuring multiple mice/trackpads/trackballs in the Settings app, general improvements to quality-of-life issues which are very noticable when transitioning from, say, macOs to Ubuntu.

One more polish issue: I'd like to see more attention paid to power-drain regressions in the OS. I had an issue recently where a process related to automatic updates was spinning in the background and consuming 100% of a CPU core, and cutting my battery time in half compared to what it should have been. I looked into it and found it was a known issue that wasn't fixed yet, but could be solved by deleting one of the default apps. If I were a less sophisticated user I would have just concluded that battery-life simply sucked on Ubuntu, and frankly I would have been right.

[EDIT: all these issues were encountered on a Thinkpad T460, which should really be one of the best supported machines in the world for this OS. If things are flaky under the best of circumstances, I dread to think what it's like on some weirdo Siemens laptop some user might have] - ROLE/AFFILIATION: Software Developer

I was writing the exact same thing. The apps are not integrated, fancontrol doesnt work on recent desktops (dunno whose fault is this) compared to windows, and its hard to get a bird's eye view of the system settings. A better package manager UI would help.
Better stability is really important! Recently there was an update for the nvidia drivers for 16.04 LTS, this broke our GPU servers on Amazon and ruined desktop login for my grandfather. All because the updated Nvidia driver no longer supported the GPU's.
To Canonical/Nvidia defense, while they do remove support for older chips, they always do that in major updates. You, as the user, can avoid this by using nvidia-<number> package, not the nvidia-current one.

I have a machine, that has GPU supported in nvidia-340, but no later driver. Ubuntu only updates to the newer -340 packages, it does not skip to the highest possible number available.

-FLAVOR: Ubuntu Desktop

-HEADLINE: Network manager that works

-DESCRIPTION: The single thing that would make Ubuntu seem 10x more polished than it now is the horrible state of the network manager.

The little wifi bar in the top right. Sometimes, randomly, after dropping a wifi connection, or going to sleep and waking it will:

1) Stop listing SSIDs except the one I've already configured and want to connect to. (But I know there's more)

or

2) Show the "wired connection" icon. Gray out the entire wifi section of the network manager dropdown menu. All while it is actually connected to some wifi and I can use the internet.

These issues are mostly fixed by a `systemctl restart network-manager`, but sometimes require a full restart.

I'm the kind of person that recommends people to get Ubuntu. "Everything just works nowadays on Ubuntu". Then I get a call a week later and have to explain to them "just type sudo systemctl restart network-manager into terminal" They then give me the "What? That is so stupid."

ROLE/AFFILIATION: Student / Sysadmin / Machine (Deep) Learning Engineer / Memeber of a students' club that organizes an event on every Ubuntu release where we help fellow students dual boot Ubuntu (or another Linux distro, but we recommend Ubuntu)

EDIT: formatting.

A big +1 from me. Network Manager is so bad I wonder how it ever got adopted by the main distros.
Yes. Connman (developed by Intel) is a much more modular design. Network Manager evolved from a Gnome applet.
Good alternatives exist too, like the light and fast connman. I use it on a thinkpad running NixOS and it works beautifully.
Agreed. There are new Network Manager bugs in just about every Ubuntu release.

At one point the NM task bar applet was simply gone.

Then it stopped managing wired connections breaking networking entirely for me.

Now the network no longer works after disconnecting from a VPN, which is an improvement compared to the previous situation where it often showed the VPN as active when it wasn't.

Add the fact that openvpn via Network manager has been broken for ~3-4 years as well.
Yes. Network Manager is horrible.
- FLAVOR: Desktop

- HEADLINE: Bring back gaming support for AMD graphics cards.

-DESCRIPTION: Pipe dream, but: the ability to run games with an AMD graphics card, the way we could with 15.10. Google "Steam AMD Xenial" and you'll see how big of a mess this is.

As of a year ago, gaming on Linux was pretty viable with an AMD graphics card, using fglrx. However, because that was deprecated, it was removed in 16.04, and the open-source drivers can't handle 3D games, at all. Most 2D games are non-starters as well, literally: the graphics freeze before I even get to the opening screen and I have to REISUB. I'm running an R9 390, but this is widespread among basically all AMD cards.

AMDGPU is an option, but only for some cards, and thats only for 16.04 - it won't run on 16.10.

I could go more into the history and the compatibility, but suffice to say, the intersection of the different versions of {the kernel, mesa, opengl, fglrx, open-source drivers} on Ubuntu now means that I have no choice but to boot into Windows to run games.

Please file bug reports for your issues, and not just as blanket statements. Many people find the open-source drivers a viable option for gaming, especially now that OpenGL 4.5 is supported and a lot of performance optimization has happened. Your case sounds unfortunate, but it's certainly the exception rather than the rule.

It's true that the version that comes with the Ubuntu releases tend to be a bit behind, but you can also try the Padoka PPA.

> Please file bug reports for your issues, and not just as blanket statements

I'll admit, it's been a while, but my experience with filing tickets for graphics-related issues like these has not always been particularly positive. Debugging them and actually identifying the root cause is quite difficult, and I end up getting bounced back and forth between different bug reporting tools for different OSS projects that may or may not be ultimately the root of the bug, and each of which thinks that the other is the more likely cause.

I have some sympathy here because I know it's tough to identify, but it's a huge time investment on my part for very little apparent gain, especially since these issues are already reported.

Besides, as I said, these issues are pretty well-documented already. I don't think there's a lack of information about the issue; it's just not an easy one to solve, and there are a lot of different organizations that are responsible for various pieces.

The AMD engineers have decided to only support the open-source amdgpu driver and diverted all resources from fglrx to amdgpu.

Due to this, 16.04 does not have fglrx because the X11 server in 16.04 is not compatible any more with fglrx.

Around this time (end 2016/early 2017) it was supposed for amdgpu to get parity in features with fglrx. I have not checked, are there issues missing from amdgpu? You would need to test, and preferably test with the AMDGPU PRO driver distribution from AMD (has the very latest support that may take a bit of time to make it to the upstream projects).

> I have not checked, are there issues missing from amdgpu? You would need to test, and preferably test with the AMDGPU PRO driver distribution from AMD (has the very latest support that may take a bit of time to make it to the upstream projects).

I don't know. AMDGPU requires an older version of the kernel, so I'd have to downgrade from 16.10 just to try it out.

> AMDGPU requires an older version of the kernel

AMDGPU-PRO requires an older kernel and Xorg. AMDGPU is open source and works great with Linux 4.10.x

- FLAVOR: server / all

- HEADLINE: remove sha1 PPA signatures

- DESCRIPTION: remove the warning "signature by key uses weak digest algorithm (sha1)" and ban sha1 for PPA signatures

- ROLE: user

This needs to be done slowly or you're going to piss a lot of people off with broken shit.
Please see if the Cairo-GL backend can be re-enabled. This backend was disabled a years ago because of an issue with Nvidia drivers.

If it can be re-enabled, it can help enable some interesting future apps.

- FLAVOR: Ubuntu Desktop:

1. HEADLINE: A way to have different scaling for external monitors hooked up to my HiDPI laptop.

Currently I need can only set a single scaling factor, so I need to ajust my laptop screen resolution to match scaling of the external monitor. If that's not possible, a way to automatically set resolution and scale for both screens once you hook one up would already save me a lot of manual switching and restarting lightDM!

2. HEADLINE: "Native" multitouch gestures like 3-finger swipe to change workspace.

There are some programs that can do this already like xSwipe and Fusuma, but I expect this integrated with a nice and easy menu.

3. HEADLINE: Better battery management.

Battery performance under Ubuntu is often much worse in Ubuntu than Windows. TLP helps, but it's not enough.

I have the dual problem of 1.HEADLINE: I've got a HiDPI notebook and suffer when I have to connect it to a common 1080p screen.
(comment deleted)
> 1. HEADLINE: A way to have different scaling for external monitors hooked up to my HiDPI laptop.

This would be awesome. Even when both the laptop and the external screen are 1080p, different scaling could be helpful if you want to use a dual monitor setup effectively.

Unfortunately, it's a tough nut to crack given current desktop behavior. For example, you can have a window that straddles both monitors. What should the scaling be? You need to switch at some point as you're moving a window back and forth - when? So it's a challenge, but solving it would be so worth it!

Widows 10 handles different scaling (zoom) between monitors far better than any Linux distro I have used. A window keeps the zoom of where it came from until it is entirely on the new monitor. Works pretty well.
While I get that it's uncool to like Windows on HN, I really like Windows 10. With WSL, all of the CLI tools I need for development are here along with better hardware support (including suspend / resume, high DPI monitor support, latest GPU drivers / etc).

Plugging two 4K monitors into my laptop (which has a native 1080p display) is an awful experience when booted into Ubuntu. You either have to set the DPI to make the laptop display unusable or set it to make the 4K monitors look like $hit.

Plus... you know... games.

Windows isn't the best at multi-DPI in general though either. Only recently did Firefox on Windows get multi-DPI support - not sure if Chrome does yet because I gave up on it and went to dual 4K because the scaling was easier. If you want to see really good multi-DPI support, OSX is really good at it with most apps supporting it out of the box.

Multi-DPI is kind of a hack in general though and is likely to cause issues unless applications have been tested for it very thoroughly, it causes serious issues on major frameworks like Electron and Qt - though both of their support for it is improving slowly. If you want things to work smoothly for now, try to stick to 1 DPI setting.

I think you're confusing Windows DPI scaling availability vs lack of support from the apps you use.

It's not windows fault the apps don't take advantage of DPI. You can also disable dpi scaling for individual apps.

The problem isn't just scaling between two different resolutions, it's the inconsistencies (yes, apps don't take advantage but that's not the only issue). For example, if I want 200% 4k (my monitor) and 100% 1080p (my 2 side monitors), I have to choose between ultra-tiny text on my 4k with regular text or blurry text on my 1080ps.

http://i.imgur.com/o1S8ZUt.png

Is that Windows 10? On my Windows 10 Ent desktop I'm able to set the scale factor of each display independently.

http://imgur.com/a/5378F

This is Windows 10. How do I enable that option?
Erm...click on the display you want to change (1,2,3) and simply drag the slider?
You're right, but even many builtin Microsoft apps - while they supported DPI scaling - did not support multi-DPI switching and rather than scaling properly just scaled pixels and looked blurry.

It's "not Windows fault", sure but it certainly makes it a worse experience than other platforms like OSX where multi-DPI is much more commonly supported.

I would much prefer the Windows behavior to what I see on Linux. Right now, if I open an app that doesn't support high DPI, it is just unusable because it is so tiny.
Couldn't you just manually reduce your screen resolution? Or is that too drastic to be worth it?
It's worth considering whether there is some flaw with windows multi dpi scaling such that apps don't use it. Firefox and Chrome have scaled properly on Mac for years now, while even Windows 10 ships with first party apps that don't scale right. (E.g. device manager.)
For sure that this has been an issue in the past with Windows. UWP helps make muli-DPI work by default in new applications.
Sure, but 99% of my Windows software isn't UWP. It's all good and well to say it's there, but that doesn't make the experience good for the user. Contrast to KDE and OS X where it just works for 99% of software.

I mean, I get it, same issue as Vista for Microsoft - people expect 100% backwards compatibility, but it turns out that terrible design decisions made many years ago tend to mean you need to break compatibility. Just like UAC, resolution scaling will be an issue that becomes less painful in Windows over time. Right now it's not great, however.

I mean, you say that, but on KDE, for example, every application except one on my system works with DPI scaling (the odd one out is Unity3D) - that's because at the QT level DPI scaling is built-in, so the toolkit supports it and the applications get it for free. Clearly this wasn't the case for the older Windows UI stuff, where they are literally just scaling the image of the window up (which means horrible looking text).
Anything running its own renderer doesn't get to benefit from component scaling since they don't use components.
That was my point - running KDE, this is extremely uncommon, running Windows, it's practically every application.
(comment deleted)
Actually, the really old windows stuff did support scaling - the 'Large fonts (120%)' option was there almost forever. I remember that original Delphi, circa 1995, supported it.

Just most apps chose to ignore it, the developers took the 'anyone uses 96 dpi anyway' attitude and at the end of 90's most applications started to suck at 120 dpi.

Yep, Windows API already had support for logical pixels in the 16 bit days and all good books always preached to convert between logical pixels and physical ones.

I guess people got lazy, as you say.

I think that the monitors stayed more or less the same later pixel density for a very long time. Is only been gradually increasing very slowly for 20 years, until a few years ago.

No point in spending time on logical pixels if it makes almost no relevant difference...

It's

This month's Windows update fixes DPI scaling for old toolkits.
Chrome hast had DPI scaling since 2015 on Windows. I remember having to report lots of initial bugs. Now it works fine.
DPI scaling yes, but not multi-DPI, when dragging from a 100 DPI monitor to a 300 DPI one text should remain sharp and not blurred by scaling pixels. Or even vice versa.
(comment deleted)
Yes, it's true that there are issues. It seems like most Microsoft apps handle multi-DPI well. By comparison, on Fedora 25 (the latest release), the only program I have found that handles multi-DPI is Terminal. Firefox doesn't do it.
Yeah, Windows support is better than Linux for it, but it's still pretty iffy. While IE and a few other things do, even stuff like Windows Explorer and OneNote doesn't handle multi-DPI well or even just runtime DPI changes in general, I'll RDP my box from a 100 DPI system and have my session screwed up when I come back to my system.

If you're making a decision about whether to make a purchase, don't make it unless you're prepared to do it all at once. Stick to ~100 DPI until you can make a commitment to go all at once.

>While I get that it's uncool to like Windows on HN

That has not been my experience here at all. There is a rather active, and sometimes vocal, Windows fan base around here. Misconceptions about the current state of desktop Linux are commonly seen as it seems most people around here only use either Mac or Windows.

Agreed, while I see some MS/Windows hate... some of it technical, some political, and a mix of founded/fud... There's been a fair amount of counter to that.

I mostly use mac at work, mostly windows at home, and a bit of linux for servers, and my htpc (most of my casual browsing at home)... Each experience is fairly different. And they all have pluses and minuses. That said, more often than not, I prefer the Windows UI desktop/menu, but osx & unity app integration and linux/bash shell environment. I wish that Ubuntu/unity would integrate more of the menu/taskbar features found in windows. (And bring back natural scrolling checkbox)

Windows also gets my vote when it comes to the per-app volume mixer controls which have been awesome since Windows Vista.

https://blogs.msdn.microsoft.com/larryosterman/2005/12/15/vo...

Pulse Audio solves the same thing for Linux.
This feature comes by default with PulseAudio, maybe Ubuntu doesn't expose it well enough in their audio settings. I think Gnome Settings has it, KDE definitely does.
PulseAudio provides this feature and actually provides more features and functionality than Windows. Ubuntu's default mixer isn't the greatest so I recommend this instead:

    sudo apt install pavucontrol
You can then find it in the application menu labeled, "PulseAudio Volume Control". It lets you set the volume for individual applications (and with Chrome, individual tabs!) and also pick which output/input device will be used.

It lets you configure some neat tricks. For example, you can setup an audio device that forwards to another computer running PulseAudio, an RTP receiver, and a few other similar protocols then set say, Spotify to output to that device. So if you have some network-enabled audio receiver somewhere in your house/office/whatever you can send audio from your Linux workstation to it.

You can of course also pass that audio through various filters/plugins to mess with the sound before it goes out to the remote receiver. For example, equalize it, noise removal, etc. PulseAudio supports LADSPA plugins so if you wanted to you could setup a little Raspberry Pi audio receiver at your front door and yell at solicitors in a robotic voice from your desktop. All with a bit of PulseAudio configuration fiddling =)

I still remember the first time I was in a computer lab and I leaned too far away from my computer and my headphones that were blaring music popped out... and the whole room WASN'T subjected to the same loud music. And I opened up the Kubuntu audio controls and plugged in my headphones and the volume slider suddenly jumped up, then I unplugged again and it muted again. "Woah."

I remember trying it on whatever Windows computers were in the lab just to make sure I wasn't crazy and that this wasn't there all along, and sure enough, they kept the same volume no matter whether the headphones were plugged in or not.

One of the first PulseAudio victories I remember, at a time when I vaguely recall that it was a newcomer and people were really pissed at PulseAudio's bugs and recommending just straight ALSA instead.

+1, PA + pavucontrol are very flexible. You don't even need weird protocols to send your audio to another computer, I just used its tunnel module (enable it in the receiver, then configure its IP on the sender) to send my browser's audio output to my home server, which has a decent stereo attached. The latency is quite good too, the delay even over wifi is barely noticeable.
Thanks for the heads-up! This is one thing I miss mightily on my Mac.
I've always resorted to xrander and can get the screen looking pretty good. Though I really think something like this should just work.
My experience (currently running two 27" panels at 3840x2160 and one 27" panel at 2560x1440 in KDE for most stuff, Windows for gaming, and previously had one of the first edition retina MBPs with external non-retina displays):

OS X, years ago when the first retina MBP was released, did everything right. It was seamless from monitor to monitor, scaling done well.

Windows 10, now: OK, ish. Most applications scale badly with blurry text because it's just literally scaling the image afterwards. Newer applications are fine. The actual scaling isn't great - having a window half on one monitor and half on the other leads it to 'picking one' and looking weird on the other.

KDE, now: Pretty good. Correct scaling once you set it up. The autodetection can be dodgy, and the DPI scaling for text isn't linked to the rendering scaling for windows, for some reason. The GUI still only gives you a single scaling option for all monitors, but the autodetection can do different for each monitor, and environment variables can be set to solve it manually. The actual scaling is perfect for the vast majority of things. Things scale correctly and no blurriness. The only application that doesn't handle scaling is Unity3D, so everything is tiny (no fallback to raw image scaling).

In general, it's what you'd expect for interace stuff across the platforms - Linux does it right, but the interfaces around it are bad, Windows does it fine for new stuff, old stuff (which is most stuff) sucks, but the interfaces are OK for doing it, and OS X gets it all right.

Edit: Just to be clear, it's only the Unity3D editor that doesn't do scaling, the actual games work fine, as you'd expect they just get the full space and the game chooses how to render to it. To be fair to Unity about the editor, they support scaling on OS X, and the Linux build is still a beta. It is annoying though.

I use this on Windows 10: http://windows10_dpi_blurry_fix.xpexplorer.com/ and it works fine. If you have blurry text, disable DPI scaling in that app (right-click -> Properties -> Compatibility -> Disable DPI scaling) and this will take over and make it usable. There are a couple of applications that act wrong no matter what (Battle.net for example), but most of the time this fixes it well enough.
I only use Windows 10 for gaming, so fortunately I don't really need to worry. Useful for those who use Windows all the time, though.
I get correct auto scaling-switching like this on Gnome 3 with Wayland, but only for a subset of programs (basically those that are fairly vanilla GTK+3), and at the cost of weird bugs with Wayland and program support thereof that still crop up fairly regularly.
FWIW, macOS changes a window's DPI mode when the cursor that is moving the window passes over from to one screen to another. Just tried that out. :D
That's what happens when "Displays have separate spaces" turned on. (With that setting on, windows are only present on one monitor at a time, and, when dragging a window, that transition happens when the mouse cursor moves between displays.)

With "Displays have separate spaces" turned off (so windows can be present on more than one monitor at a time), it looks like windows take their DPI setting from whichever monitor the majority of the window is on-- with my current two-monitor setup, the DPI transition happens at the halfway point of a window, regardless of where the mouse is as I'm dragging.

Leaving aside the implementation difficulty, the answer to "what should the scaling be" seems obvious? Use the monitor scaling for the part shown on that monitor. The switch should happen on a monitor level, not on a window level.
The painting happens on window level, that's why it handled there. Application paints the window whenever it receives event "paint me" for it and it cannot paint different portions of a window at different DPI - from the applications POV, it is a single canvas. Another thing is, that the window resize and dpi change are separate events, so you cannot really call it twice in a row with different DPI and expect the app not getting confused.

Another approach would be to let the application render at higher DPI and the compositor would downsample the portion on the lower DPI display.

This isn't just external monitors! MBP with "retina" screens are also unusable for Ubuntu :(
macOS handles that edge case. It just displays the window in only one screen. The one with the biggest area of the window shown. There is no need to be held back by cases like this.
If you zoom in, you can sort of force parts of one monitor to be shown on the other monitor. You can see how everything's upscaled/downscaled from there.
Weston does multi-DPI really well. When you drag a window between monitors, the half on the HiDPI monitor is scaled and the half on the LoDPI monitor is unscaled. So it looks perfect without windows growing or shrinking when you move them to another monitor like GNOME on wayland.
(comment deleted)
I'd love to read more about how this was done, if you have a link perhaps.
OSX handles this by upsampling/downsampling the parts of windows that are drawn on the other screen.
> This would be awesome. Even when both the laptop and the external screen are 1080p, different scaling could be helpful if you want to use a dual monitor setup effectively.

Actually, this is especially true when both are 1080p, because laptop screens are never as big as desktop monitors, and we also tend to use them closer. I have this exact problem right now but I think I've just adjusted my eyes over time to squinting at 1080p at 14", or perhaps I turned on some display scaling and forgot about it.

> For example, you can have a window that straddles both monitors. What should the scaling be?

Intuitively, I feel like you should use the physical DPI of both screens to make sure that the window has the same physical dimensions on both. But that'd probably lead to weird scaling factors like 1.17 instead of nice round ones, and thus fuzzy scaling, so it probably couldn't quite work. I guess perhaps you'd just snap each display's DPI to the closest predefined value (eg. .25 increments which I think most systems use these days). Then you'd get a similar-sized part on both sides of the boundary.

But yeah, I think overall if you actually use physical DPI for scaling everything should work out close to nicely.

Fedora with Gnome shell on Wayland already handles both 1 and 2, although power managements is about the same as Ubuntu and Wayland comes with its own set of issues.
I switched from Ubuntu to Fedora about a year ago and am quite happy with it.
really, there's a native multitouch support for touchpads? do you have more info about that?
Two-finger scrolling works really well on Fedora with Wayland, in fact at some point it appears to have become default behavior (at least on my machine running the latest version).
Fedora uses libinput. Of course, it is not without issues from those, who would like to tweak every little setting. Libinput is designed to be as automatic and configuration-less as possible.
I can't find much information, but things like scrolling, switching work spaces etc. worked out of the box for me when I was testing Fedora 25 a month or so ago.
Well 1 depends on Wayland actually detecting your external monitor, I normally end up having to drop back to X to get it to detect my secondary 28" 4K monitor :-(
I couldn't figure out where I can change the different scaling for the external monitor on my fedora 25. My 1080p external monitor just looked huge comparing to my dell xps 13 hidpi display.
It requires Wayland features that are used by GNOME 3.24 (so F26).
+1. I recently got an Dell XPS 13 and hooked it up to my external monitor (4K). Icons were way too small so I adjusted those and standard text size. But getting applications (e.g. PyCharm) to run at a reasonable size was frustrating (I had to google it and then modify some configuration file somewhere). With OS X, which I just came from, the external monitor "just worked" when I plugged it into my Macbook Pro.
it really is a mess. i connected a 4k xps 15 to FHD monitor, the only way for it to work is via open source nvidia drivers and using xrandr to scale the external monitor and then use other settings to scale everything to FHD. that and some other things made me return the xps and order the new macbook.
Windows scaling should auto configure and work in any modern application. It always works like that for me, and I only have issues for software written in 2003 in Java or really old versions of QT.
> (I had to google it and then modify some configuration file somewhere)

I even had to do this with Chrome [1]. It's crazy how obscure this was when I was setting things up. Other apps, like Gimp, still look like shit because I can't find a way to do the same thing; their GUI just rends at a tiny scale and is difficult to use.

[1] https://superuser.com/a/1120078/103402

I would absolutely be in favor of #1 and #3.
3. agree with the default WM; no issues (same or better than Win) battery life with i3wm. In my experience ofcourse.
Better out of the box HiDPI support would be great.

Autdetection would Be nice, but just being able to set the scaling option in one place and having it apply not only to my desktop but the login manager as well would be very useful.

Also, afaik there is no documentation on changing the scaling factor in the login manager, or at least not in the official docs.

I would not buy a standard resolution monitor at this point, so having simple support for it in Linux is very important to me.

More work on gesture!

Including the ability to configure what gestures you want in a GUI interface!

On 1.: Seriously, I was gonna write the exact same thing. Just today I researched once again, since it's quite a hassle, and nowadays seems pretty common to have a HiDPI laptop screen in combination with a standard-DPI external screen.
I had the same problem yesterday, I use fedora but we share the same pain missing this feature. It would be awesome to have this setting. Being able to set different scaling for external monitors is a must have feature.
User: I want hi-res apps!

Dev: Sure, here you go.

User: But why is it so small on my new shiny tablet high density screen?

Dev: (SHit it worked okay for me) Okay now it detects the density and scale..

User: But when I move the window to my old good lcd screen it becomes way too big!

Dev: Okay let's see if I can dynamically adapt to a new monitor density, it's just one scale factor.

User: But when I put it on my big tv flat screen it is too small!!

Dev: (Oh shit you gotta be kidding me, the pixels are actually a viewing distance relative unit??!)

If the OS (not an app) could allow you to tweak the native pixel resolution, scale, size of each display, even under "advanced settings" that would go a long way towards helping.

This is at the Operating System level, not like some random one-off application.

For me, the one feature I miss the most is a checkbox option for "Native Scrolling"; Did this really need to be removed?

X11 did — run xdpyinfo and you'll see its idea of screen dimensions and resolution. (It's unlikely they'll have been configured correctly, of course.) If you look hard enough, you can find some ‘outdated’ plain-X software from the workstation era that respects it. It was the ‘Linux desktop’ crowd that threw that away, since they couldn't think beyond building Windows clones for PC clones.

And the vector-based competition to X (e.g. NeWS, Display Postscript) would have done better.

The distance between of the third and fourth formulations of the problem is very small. Once apps can be dynamically redrawn with a scale factor, simply make the scale factor customizable.
Simple answer is don't auto-detect. Allow the user to set the scaling factor per screen and then just auto-apply that when using that screen. This just requires a way to uniquely identify screens and requires the user to set the scaling factor for that screen once when first used.
Initial autodetection and scale-factor setting is ok. Otherwise most regular users would just say "all my icons and text are too small on my new notebook". Windows detects the high dpi in that case and sets the scalefactor to 200%, which gives a good starting point. Of course the user should be able to override this permanently if it isn't his preference.
s/his/their
As someone who loves singular they, I have a request: please don't do this. It is OK if grand parent uses he/him. Thanks!
Simply introduce zoom in/zoom out for the whole desktop separated to each screen like in browser (you can zoom certain tabs/sites and have that memorised). Problem solved.
MacOS actually in my experience seems to handle this all perfectly. Normal-DPI screens you chose resolution and dragging windows between monitors works as you naturally expect (it pops between DPIs).
Does it understand "I want 2x magnification on my 15" 4k laptop display, but not on my 43" 4k monitor"? Windows 10 decidedly does not, so I have to switch manually every time I switch display (just forget using both together), and it then tells me to close all my work and log out and in again to make scaling consistent between UI elements on screen.
Yes it does, sometimes. But you can configure it as well. I think they used predefined lists of hardware though. EG if name contains tv then scale is 1
Yes it does. It even remembers different window sizes and locations for different monitor configs :)
Huh? On Win10Ent I've got both of my displays set to different scaling factors and changes take effect immediately (like, as soon as I release the slider).
It works for me, with one annoying caveat. I have a set of regular 1920x1080 monitors on my desk at 100% scaling. My laptop has a 4k screen, and when I plug it in, I have it set to turn off that screen.

I have to log out when I plug/unplug or the windows will end up blurry or the wrong size.

Have you ever tried shouting at Microsoft about this?

I know they have a bad track record of not listening, but I think things might be different now, they seem to be a bit more receptive to feedback, particularly with the beta updates.

Or maybe I'm remembering the prerelease "hai where r the bugz halp" back when Win10 was not yet RTM...

Pretty much. Works just fine when I hook my 15" laptop up to my 130" projector.
It's a bit weird to drag things onto my 4k TV through HDMI and try to track my microscopic mouse pointer to the tiny window to maximize my video, but otherwise works well. I suspect I could fix that in settings somehow though.
have you considered swapping out to a BIIIG mouse pointer? that's what I do on my home 65" HTPC/ TVPC :)
On newer macos shaking the mouse back and forth makes the pointer get larger (so you can find it).

https://discussions.apple.com/thread/7583592?start=0&tstart=...

KDE has a similar feature: When you hold Ctrl+Win, it will draw revolving circle segments in black and white around the cursor to allow you to find it. It looks like this: https://imgur.com/a/67wfI (You'll have to imagine the cursor inside these circles. My screenshot utility won't include it in the image for some reason.)
Heh...I think Windows 3.11 already had that feature (Ctrl -> Circle zooming in to mouse) :)
Concerning DPI and trackpad integration, Ubuntu should strive to be as Mac-like as possible, at least imo. Macs absolutely win in the trackpad arena; multitouch works like a dream, configurable gestures aplenty to achieve whatever you want (of course, it could always be more customizable).

DPI scaling between monitors work exactly as you'd expect. Windows stay the same size when moving between high-DPI and regular monitors.

These two problems are two of the biggest reasons I don't use Ubuntu (or any Linux) desktop (I use a macbook with a headless Ubuntu Server box and, when necessary, X11 forwarding over ssh).

I've always thought that arcdegrees should be what we measure UI's in: how much of a user's field of view does this thing consume? After all, what makes text "small" is that how much of my FoV it consumes (or doesn't). Not inches, or points, or pixels.

(Admittedly, "points" are still likely a good measurement for print. Perhaps one can work backwards and fudge point as a measure of angle if you consider 12 point font at a typical viewing distance.)

I assume the real hard piece is figuring out the distance the display is going to be viewed at. Some definite defaults exist (phones are typically about the same distance away, same with desktop monitors) but unique situations certainly can exist. (I'm also assuming that the monitor can report it's physical size and resolution; combined w/ viewing distance, it should be possible to calculate FoV.) If you did this, you should be able to mostly seemlessly split a window between two displays, and have it be equal "size" in the FoV. (of course, some displays have borders, so that fudges it a bit.)

"CSS Pixels" are actually supposed to be based on viewing angles:

    http://inamidst.com/stuff/notes/csspx
> I've always thought that arcdegrees should be what we measure UI's in: how much of a user's field of view does this thing consume? After all, what makes text "small" is that how much of my FoV it consumes (or doesn't). Not inches, or points, or pixels.

That is a good starting point for calculating the default "optimal UI scaling", but there are going to be adjustments needed for the FoV of the whole screen area (not per pixel) too.

With large screens, for example 24-30" on your desk, just the per-pixel FoV measure will probably be good enough. You have plenty of "space" for windows and content, and want to get the optimal scaling.

But once you get to very small screens like phones, there is a tradeoff between keeping font and UI sizes comfortable, and being able to actually fit enough content on the screen without endless scrolling. I am willing to strain my eyes with smaller font sizes on my phone than on my laptop, just so that I can see more than 5 sentences of text at the same time.

Thanks for mentioning TLP - I hadn't heard of it before
HiDPI is still a huge problem in the linux desktop I can't count the number of hours I've spent researching and fiddling with it. Wayland is the answer, but it's slow moving, and Sway currently looks terrible when scaling double.
The biggest issue with Wayland is video drivers. Try getting Wayland to work with any proprietary blob, and see your efforts fail miserably.
One way to solve the scaling issue is to set the external monitor to a virtual higher resolution while still driving it at its native resolution (with scaling down done in GPU).

Actually Linux/Xorg generally support this out of the box, it is just the higher-level software that would need to make use of it. You can try it youself:

xrandr --output <output-name> --scale 2x2

the result should be the given monitor will appear to have twice the resolution, so if applications believe they are running on a high-DPI display, they will look fine on the external monitor as well.

However due to lack of support and awareness in desktops doing just this might leave you with an unsatisfactory configuration, e.g. part of the desktop erroneously shown on both monitors - you might need to use further xrandr commands to setup the regions that each monitor displays.

I use the same approach to solve this issue on a Windows 7 system I am using, it is just slightly more involved (I need to setup a custom resolution in the Nvidia control panel).

Battling xrandr is not for the feint of heart. It is tedious to get the right behavior and differs from one display to the next (the precise dimrnsions, etc..)
Unfortunately, this scales after drawing. The entire point of hiDPI is to have a crisper image. To achieve that, the scaling must be done at the drawing level.
Unity and Gtk would scale everthing up, so things that are properly drawn before being re-scaled.

So quality will be there.

For normal/low-DPI screens instead, you'd scale everything down, so you'd lose some memory CPU power, but you'd still get the quality result.

if multi-monitor support was as solid as it is on macOS, i'd likely switch
#1 is absolutely the biggest one for me and #3 is a solid second.

I have a Macbook Pro with retina and stopped using linux simply because I couldn't get a good resolution on my laptop and monitors. And then when traveling (flights etc), ubuntu chewed through battery probably 3 to 4x as fast as OSX so I wasn't good for that either. As a result, I have been on OSX for a couple years now but would love to be back on ubuntu some day.

Ubuntu Unity Developer Here...

I'm mostly replying at the point 1., as it's closed to what I do...

I know we should offer an UI for that, but waiting for that you can just workaround this.

Well, as said unity supports scaling, although it's not possible to scale toolkits per monitor.

However... There's actually a good workaround for this, that works fine for multiple monitors.

The idea is that you scale everything up to 2x / or your maximum scaling (including window contents), then you scale the non-HiDPI monitors down using xrandr --scale

For example, if you want to use normal resolution there, you just have to do something like:

xrandr --output <OUTPUT> --scale 2x2

In this way it will be scaled down, and everything will be readable and almost 1x1.

You can test this in normal resolution monitor as well, and you'll see things should be pretty good.

I should find some time to implement this directly inside UCC / USD, so that users will get this for free...

Notice that there's also a bug in X causing some mouse trapping, so you'd probably also need X to be patched as explained in this bug: https://pad.lv/1580123 (we'd like to include this upstream, but we're waiting for X upstream approval for that)

FLAVOR: Ubuntu Desktop

HEADLINE: Better security processes

DESCRIPTION:

I've been quite disappointed that there wasn't really any public reaction from Ubuntu to a variety of security issues affecting the Linux Desktop in general and Ubuntu in particular.

E.g.:

https://scarybeastsecurity.blogspot.dk/2016/11/0day-exploit-...

https://scarybeastsecurity.blogspot.dk/2016/11/0day-poc-risk...

https://donncha.is/2016/12/compromising-ubuntu-desktop/

https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-E...

Seriously, right now an Ubuntu Desktop isn't a secure choice for users, especially if they have to expect targeted attacks.

Some things I'd propose:

* Dangerous automation features need to be either disabled by default or heavily audited. That includes things like tracker and apport.

* In general I wonder how much auditing happens before something enters Ubuntu. Some basic auditing that could also be automated like testing packages with asan should be a default inclusion criterion for adding packages.

* Currently there are no bug bounties at all in the Linux distribution world. I get that this is a financial challenge, but at least in severe cases where the fault clearly lies within the distribution and not within an external project I'd consider bug bounties appropriate. (Just read Donncha's blog post linked above. He could've gotten $10.000 from a shady exploit dealer and he got nothing, because he did the right thing.)

ROLE: I'm running the Fuzzing Project and I write for IT tech media about security issues.

The first two examples relate to codecs that are not installed by default. Most probably they should not be available for installation at all, but then it's the way that packages are available in the "universe" repository.

The third example is a valid issue, and got fixed. Apport is important to receive feedback from crashes. It is not enabled by default if you use the final versions of the installation ISOs. It is enabled only in the dev versions of Ubuntu.

Bug bounties would be interesting. Should they be monetary or should be something else (nice t-shirt). The issue with monetary bug bounties is that they make sense to money-making software and services.

> not installed by default

They are installed if you click the box during install to "Install third-party software for graphics and Wi-Fi hardware, MP3 and other media"

"Other media" sadly does not include DVDs. As far as I know there is no officially blessed way to play a DVD on Ubuntu, and probably never will be.
Hi Hanno - Ubuntu Security Team member here. Thanks for the feedback!

I wanted to point out that we did have a public response to the four issues that you mentioned. We quickly fixed them! If I'm remembering correctly, we had updates available within 24 hours of the first two issues you mentioned. The second two were privately disclosed to us and we had updates available at the same time the issues became public (thanks again to Donncha O'Cearbhaill and Ilja Van Sprundel for those vulnerability reports!).

https://launchpad.net/ubuntu/+source/gst-plugins-bad0.10/0.1...

https://launchpad.net/ubuntu/+source/gst-plugins-bad0.10/0.1...

https://www.ubuntu.com/usn/usn-3157-1/

https://www.ubuntu.com/usn/usn-3246-1/

Note that the first two issues were in packages that don't receive official security support so we didn't publish Ubuntu Security Notices for them.

I think we did a good job of reactively fixing those issues. You seem to be asking for more of a proactive approach (audits, sandboxing, etc.) and that's a valid suggestion. We are making progress there but not specifically due to the issues you listed.

The security team does proactively review the code of packages, which have an attack surface, just before they move into the "officially supported" state. Sometimes that involves fuzzing depending on what the piece of software does. It is a technique that we're trying to use more often.

We're also heavily employing sandboxes by default in the world of snaps. As more debs turn into snaps, those packages will get the added benefit of strong isolation.

An option in the installation script to not install systemd.
- FLAVOR: Desktop

- HEADLINE: Application Menu search like MacOS

- DESCRIPTION: I usually use macOS but occassionally use Ubuntu and I really miss the ability to lookup functionality in my application by typing the name of a menu entry under help. On macOS this will drop down the relevant drop down menu and show the menu entry I am searching for. I use this a lot. Especially in complex applications this is very useful to have.

- ROLE/AFFILIATION: Software Developer

FLAVOR: Ubuntu Server

HEADLINE: Smaller Docker Images

DESCRIPTION: An official, skinnied down, Ubuntu image for docker and AWS AMIs would be nice. I have some clients that want to maintain some uniformity across host and guest, so they aren't interested in Alpine or Busybox images. But the Ubuntu image is ~200MB or so, where OpenSuse is about half that.

I understand Canonical doesn't build those images, but you would have the expertise to help them thin it out. Some wrapper around debootstrap or similar to make a thin server image?

ROLE: Help various clients with docker and AWS.

Just a heads up that AFAIK these Docker images are built on top of the Ubuntu Core ones (which are ~30MB) so this is likely the overhead of multiple Docker layers that we all know about, see https://github.com/docker-library/repo-info/blob/master/repo... as it apparently explains where the core image comes from. Disclaimer: I am a @canonical.com but not involved directly with that so I also +1'ed it :-)
afaik, canonical does build those images. See here: https://cloud-images.ubuntu.com
Hmm. I assume some transformation happens before they end up as docker images or AMI images.

In any case, what I'm asking for is some conversation between Canonical and Docker, Amazon, etc. To see if there's something obvious either side can do to skinny these down. The ubuntu image is for sure the most popular AMI, and I imagine one of the most popular docker ones. The collective bandwidth and time gain of optimizing the size would be significant. Currently, the ubuntu images are significantly larger than other popular images.

Canonical is absolutely responsible for building those images. And yes, we do work with Amazon, Docker, et al. And yes, we're actively working on reducing image size.

That said, what's "minimal" to one is not "minimal" to another. We can certainly take stuff away, until you end up at Alpine or Busybox size. But then we've stripped away the essence of what's Ubuntu. So it's a very delicate dance!

I switched to alpine because Ubuntu docker containers were massive.
- FLAVOR: Any

- HEADLINE: OpenSSL v1.1.0

- DESCRIPTION: Do it! I really want ChaCha20 and Poly1305.

- ROLE: Server admin / desktop user

- FLAVOR: Desktop

- HEADLINE: Improving developer experience

- DESCRIPTION: Currently installing the Qt relating tooling requires messing around with package sources to install the SDK tools. This shouldn't be required.

Additionally it would be nice if ubuntu-make got a better UX than just remove/install, eventually some nice GUI on top of it.

Finally better 3D hardware support.

- FLAVOR: Ubuntu Server

- HEADLINE: Python 3 as default

- DESCRIPTION: In lieu of a description, I'll just link to this: https://pythonclock.org

- ROLE/AFFILIATION: Developer, sys admin

Wouldn't this mess up a lot of current server installations?
You can't update a major version and expect things like this to not change

(What I mean is: sysadmins are aware of this and won't "just" upgrade to a new major version without considering such factors - at least they shouldn't do that ;) )

It already happened, so probably not.
Hard to decipher what you mean. Maybe you want to say, that is already the default, but as this is obviously wrong you probably want to say, that Python 3 is kind of default now. Which might be true for new projects, but this doesn't have anything to do with the default env for servers. So maybe you did already messed up your server with a python version default change and you want to express that this can not happen to you anymore.
It's hard to decipher what you mean, too.

Ubuntu already switched from Python 2 to Python 3 and not many people feel "messed up" by this.

Python 3 is the only Python pre-installed on current versions of Ubuntu. All Ubuntu system utilities that use Python use Python 3. You have to install a separate package to get Python 2.

Opposing view: This would make me stay on 16.04 LTS for a long long time.
Can you explain why? Assuming you could still `apt-get install python27` and `update-alternatives` to symlink that back to the default `python`, no?
The default Python on any system is the only one which is really well tested and works with all the not-trivial-to-compile packages. Making py3 the default is exactly for deprecating py2 support, thus an apt-get install python27 would never have the wide range of apt installed packages, like it does now.
To be honest, new software should not be being developed on the 2.x line, so if it's not battletested now, it should never be.

But thats my opinion of course. We need to move the industry forward eventually and 95% of useful plugins/modules have already been ported.

It's time for py3 as a first class citizen.

Ansible only works with python 2.x (with beta 3.x support).
I don't get the logic behind your battletested thought.

Generally it might be true that finally python 3 is now the default for new projects but that doesn't mean that there will be a switch to python 3 as default enviroment. There are still a lot of base libs which are not ported to python 3. Most often nobody has interest in porting them. Some are, but then often as a complete rewrite, which are not backwards compatible.

Until Python 3 is the default env it will take a few more years.

In 3 years, Python 2 will not be maintained anymore. It should really not be used for anything important in 18.04 LTS anymore, because that'll need to be supported for longer.
I believe python upstream recommends that "python" is python2 and python3.x is "python3"?[1] (Although, that does not jive with official python packages for windows, which is both annoying and confusing - the pep governs "unix like" systems - eg. including linux subsystem for windows, but excluding python on windows...):

[1] https://www.python.org/dev/peps/pep-0394/

trigger warning: mean comment ahead.

Nobody cares about your special-snowflake needs. Python 2 should already be dead and we really need to have major GNU/Linux distribution start dropping it as default.

You can always set it up post-installation.

On a server you are the snowflake with your Python 3 desire. Do you not use venv for applications?
I agree, I usually update defaults so that python => python3. However, PEP has some guidance on how this should be handled[1].

I imagine Ubuntu (Debian, et al) is following these guidelines. It would be cool to have a push for those who still depend not only on Python2 but on `/usr/bin/python` being py2 to update their app - or at least update their packaging :)

[1]: https://www.python.org/dev/peps/pep-0394/

Python 3 is installed by default, and Python 2 is no longer installed by default on Ubuntu Server since 16.04.

Both versions can be installed concurrently. Python 2 is available under /usr/bin/python2 if it is installed. Python 3 is available under /usr/bin/python3 if it is installed.

/usr/bin/python points to Python 2 (or nothing, if Python 2 is not installed). This is the upstream recommendation from PEP 394 (https://www.python.org/dev/peps/pep-0394/) and I don't see Ubuntu diverging from this unless upstream's recommendation changes.

Everything @rlpb just said here is spot on ;-) Definitive +1.
- FLAVOR : Desktop - HEADLINE: Fix UI for file extraction - DESCRIPTION: When I extract zip files, the UI when the extraction is done has all the buttons glued together. It is such a small thing that I feel a bit silly for posting it here, and wish I just had a bit of time to actually dive into this myself. I will take a screenshot of the Archive Manager when I am home later today.

ROLE - Software Engineer

- FLAVOR: Desktop

- HEADLINE: New icons by default!

- DESCRIPTION: There are a lot of good icon sets out there that are easy to install. I think a better default icon set would make the desktop look a lot smoother and cleaner.

Please finally upgrade to opencv 3
- FLAVOR: Ubuntu Phone

- HEADLINE: I want a snap-based Ubuntu Phone now

- DESCRIPTION: Being a click-based Ubuntu Phone supporter from the beginning, do I need to say more? Ubuntu show me some love!

- ROLE/AFFILIATION: beta-tester

Flavor: Desktop

Headline: Surround Sound

Description: If a user has a media file or application that wants to play surround sound audio, 5.1 or higher, it should work properly and automatically. AC3, Dolby Digital, dts, etc. should all function properly with all different hardware configurations.

I'm aware that it is possible to make it work properly with some effort, but it is not elegant or automatic. The user should not have to do anything special. It should "just work".

For example, a user has a surround sound system connected to their computer's optical output. They play a media file or DVD that has a surround sound audio track. That audio track is selected. The surround sound should play properly with no further special configuration. The user should not have to know that pulse audio or whatever even exists.

Flavor: Desktop Headline: Polished and modern Desktop/User experience.

I'm using Ubuntu full time for the past 4 years. Some how it still feels like I am using some what old software although Ubuntu has come a long way since the beginning. I don't mind a release with no new technical improvements but only dedicated to improve all the little details and a polished experience of the overall user experience. Given looks are one of the important factors for an average user to evaluate a desktop, I believe any effort on this front will help a lot if furthering ubuntu adoption.

Role: Web developer and Digital marketer

What, specifically, do you mean by polished? Please give examples.
Polished as in window animations, tastefully done transparent windows by default on hardware that support it, snappy application menu, desktop and file manager icons that conforms to grid, black title bar with white fonts is a too strong to name a few.

In my opinon, There must be one release tailored towards UI improvements among the three releases that leads to LTS preferably as the one that follows LTS because there is a solid platform to build upon and there is enough time to iron out UI bugs in the next LTS.

The theme is also quite dark. Notifications are black, background is dark: It makes me feel claustrophobic compared to a macOS. Maybe, generally, hire more graphic designers.
I get frustrated as hell by the inconsistent dialog boxes! When saving a file, the filename text is highlighted (i.e. selected), but when you start typing it sends the text to a search input box. Like... WTF?!?
FLAVOUR: Server, some desktops

HEADLINE: New command line installer

DESCRIPTION: The cli installer inherited from Debian needs to be modernized. It is ugly, asks too many questions and has some weird behavior, for example when not configuring a network connection at installation, only a cdrom apt mirror is added (even when there's no cdrom drive).

Aren't you in luck!

We have an early preview of this very thing, called the "subiquity" installer, ie, "the server ubiquity" installer. And it's simply fantastic! Ping me on Twitter @dustinkirkland if you'd like to try it out!

- FLAVOR: Ubuntu Desktop

- HEADLINE: XFS + FDE Installer Support

- DESCRIPTION: Full-disk encryption set up is a breeze with the installer, unless you have a few different drives and want to use XFS. I recognize this is not a majority use-case but FDE with multiple drives is challenging to configure.

- ROLE/AFFILIATION: User