As I explained in the Edit paragraph I added, the ”solution” was more of the problem as I presented it going away (through related bugs getting fixed) than finding a path of steps to take.
Viestit paikassa Ask Ubuntu
Having just installed one this weekend, I can confirm that at least ML-2165 (the non-wifi, USB-connected one) works under 12.04.3, with suld-driver-4.01.17 installed from the SULD repository.
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:
- For a bug report about a system crash:
apport-cli -p <package name> --save bug.crash
- 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
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?
Okay, thanks for the advice Eric. I do intend to post here if I do come across a solution, so I’ll keep this open for now. Software updater in current releases looks different, so I’ll probably close this in any case once the next LTS comes around and I’ve upgraded.
Uh, except there’s no ”abandoned” alternative in the closing alternatives, and the question is still valid.
Never got Compiz to do the job, so I’m closing this as Eric suggested. FWIW, this devilspie script seems to work: (if (matches (application_name) ”^update-manager$”) (maximize))
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.
This answer is starting to look good. I also found allow_discards in dm-crypt’s current documentation; everything seems to imply it’s not a kernel parameter but an option for the dm-crypt device-mapper target. I’m still trying to find out if those can be passed on the linux command line. That would explain the instructions parroted all over, otherwise it is probably just misinformation.