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?
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.
Here’s why this is broken: logging out != shutting down. Why does the sync block logout instead of continuing in the background, and just blocking any attempts to *actually* shut down? The way it currently is makes it impractical to use U1 to sync my users’ config, because they’re blocked from fast user switching by the wait on every logout.
Still very much an issue in 12.04.
u1sdtool is also affected, and for me setting files_sync_enabled to True also doesn’t fix this.
jani@ritoru:~/.config/ubuntuone$ u1sdtool –status
Oops, an error ocurred:
org.freedesktop.DBus.Error.UnknownMethod:
Ah, that would be the ”UbuntuOne token for https://ubuntuone.com”. Missed it repeatedly among the dozens of website passwords.