See also: Is there a way to configure Unity’s top bar to autohide?

1. Ubuntu
2. Unity
3. Vim, Gedit
4. Gmail (on the web)
5. Chromium
6. Screen, yes

Astute Antelope.

The ”Filing bugs when off-line” section of the bug reporting community help can be applied here:

First, on the target system, gather the information in a file:

1. For a bug report about a system crash:apport-cli -p <package name> --save bug.crash
2. For a bug report about any other issue:apport-cli -f -p <package name> --save bug.apport

You will need to answer a few questions, which will vary depending on which package the bug report is about. Relevant system information, including the package name, is then saved on the target system, in the current directory. The extension indicates if it is a crash report or another kind of report. If you decide to rename the report file, please keep the .apport or .crashextension.

When the file is ready, copy it to the system you intend to use for filing the report. There you can then file the report:

ubuntu-bug -c <apport_file.extension>

I know I can file a bug report on the local machine by running `ubuntu-bug`. But what about when I have a bug on another computer elsewhere so that it’s not convenient to get to it physically to file a report there? Can I use Ubuntu’s bug reporting tools to gather data about the bug remotely, transfer that data to my local machine and submit a bug report here with the data from the other system?

Nearing 13.04.

Scholarly Skunk
Snappy Snapper
Spiffy Spinner
Sturdy Stoat
Sultry Serval

At least for Ubuntu users, I recommend filing those bugs on Launchpad. The package maintainers are usually able to tell pretty quickly if the issue is an upstream one, in which case you then file it upstream (in Gnome’s bugzilla) and link the two reports (there’s built-in functionality in LP precisely for this purpose). When the distributor’s tracker is your first port of call, you won’t (usually) be bothering upstream unnecessarily with distro-specific issues.

In fact, I sometimes file bugs on LP even when I know the issue is an upstream one, and then just link the reports right away. This way other Ubuntu users, who can’t tell the difference and would file the bug on Launchpad anyway, are saved the trouble.

The kernel parameterizing of allow-discards could be an Archism: apparently in Arch, you notify GRUB of an encrypted root with (e.g.) ”cryptdevice=/dev/mapper/root:root:allow-discards”. This being picked up by Ubuntu users might be due to Arch’s wiki being referred to as ”Best reference” by Ubuntu wiki’s EncryptedFilesystems.

Hi Gary. I now tested this in a VM running up-to-date Precise and am happy to report the problem no longer occurs. I’m thus marking this as being fixed.