All right. Thanks, Jeremy!

Okay, did it! https://gitlab.gnome.org/GNOME/gnome-terminal/issues/30

Some years back (2013/2014 maybe?) the ’New Window’ and ’New Tab’ menu items were combined into a single ’New Terminal’ item.

This apparently met with resistance from users, so Fedora and recently also Ubuntu have chosen to build Gnome terminal with DISUNIFY_NEW_TERMINAL_SECTION to restore the old behavior.

This unfortunately leaves users of those distros, like myself, who actually prefer the simplicity of ’New Terminal’, with no practical way to restore that functionality (beyond rebuilding the package with the compile-time switch reverted).

After hearing me out, the Ubuntu maintainer suggested I file a bug here, asking to turn the compile-time option into a Gsetting so that the behavior could be more easily adjusted per user preferences.

So that is what I’m asking here.

Jeremy: If this is indeed the popular choice then I fully respect that. I just wanted to voice my disgruntlement, since I feel the way this was set by upstream is much simpler. Sorry for being late with it, didn’t realize this was getting overridden before the change already came into effect.

Output from procps’ ps with -e only produces the process name, so grepping for ”cli.js start” fails every time. This change adds (POSIX-compliant) -f to all ps calls to get the full command. AWK print parameter is adjusted accordingly where needed.

Issue #1359 resulted in PR #1370, but only addressed the stop: target. The changes here address the rest of the ps calls the same way.

@droidmonkey That page seems to have been deleted from the wiki, but I think I found the problem, sort of. I’m using the -proposed repository, where the current proposed snapd-xdg-open (2.28.5) is just a transitional package (pointing back to snapd), as they’ve integrated xdg-open into snapd itself.

If I downgrade snapd-xdg-open back to 0.0.0~16.04 from -updates (which also requires a downgrade of snapd back to 2.27.5), the Open URL function in KeepassXC does work (with the fresh 2.2.2 release at least).

So an upcoming change in these packages will break this, unless they do some more juggling before the packages move from -proposed to -updates.

The issue persists for me in 2.2.1 in Ubuntu 16.04. I can get it to work by removing snad-xdg-open from snapcraft.yaml (effectively reverting PR #1011) before building the snap.

Has anyone ever found themselves thinking anything beyond the apps and perhaps the files lenses are useful? Only half /s here, I love Unity as much as the next guy (maybe even more), but perhaps my workflow is just stuck in the past as I never even touch the Dash unless I need an app not currently locked to my Launcher. The first thing I do after installing a recent release is a big apt-get –purge for all other scopes, just to better see those apps which are all I (ever) need.

Note: I’m attaching a video below demonstrating the issue. In it I’m reproducing the problem with the amd64 ISO of 15.04.

Steps to reproduce:
1. Have a (virtual) machine with a clean 10 GB hard disk and 8 GB of RAM.
2. Start the installer, select ”Erase disk and install Ubuntu”, click ”Install now”.

What happens:
A ”Do you want to return to the partitioner?” window pops up, saying ”Some of the partitions you created are too small. Please make the following partitions at least this large:

/ 3.5 GB

If you do not go back to the partitioner and increase the size of these partitions, the installation may fail.”

Selecting Continue then goes on to an installation which fails due to lack of space as promised. This is because the installer has partitioned the disk with a 8+ GB swap partition, and only what remains of the 10 GB after that allocated to /.

What I expect to happen:
I know this is a tricky corner case, but I think there are better ways to deal with it than exhibited by the installer above. Here are some alternative suggestions I came up with:

1) change the way the disk space requirement is calculated for the ”Preparing to install” view: make it require at least the minimum ”/” size + expected swap size, thus notifying the user beforehand if the requirement is not met. (As you see in the video, currently it has the green checkmark even when the installer is about to fail predictably.)

2) have the installer select a partitioning scheme where ”/” is the minimum required and allocate whatever remains for swap; warn the user that swap will be too small to do hibernation.

3) at the very least, have the ”Do you want to return to the partitioner?” window describe the situation better. It was the biggest source of confusion for me because the wording implied I had partitioned the disk (which I hadn’t done) and prompting me to ”return to the partitioner” where I hadn’t been to.

I’d love to have this too, and to have it come down from the top of the screen only once I push the mouse cursor all the way to the top edge. 90% of my menu clicks these days are clicks I meant to hit browser tabs with.