I was going to report a bug about URL parsing in Launchpad. I found two projects titled to match what I think is what I’m after: https://bugs.launchpad.net/malone is titled ”Bugs in Launchpad Bugs”, while https://bugs.launchpad.net/launchpad is titled ”Bugs in Launchpad itself”.

What is the difference between ”Launchpad itself” and ”Launchpad Bugs”? To me it seems frustratingly vague.

Steps to reproduce:
1. Go to https://launchpad.net/~mozillateam/+archive/firefox-stable
2. Choose Send link…

Expected outcome:
To have ”https://launchpad.net/~mozillateam/+archive/firefox-stable” as the newly opened email message body.

Actual outcome:
Message body reads ”https://launchpad.net/~mozillateam/ archive/firefox-stable”.

Binary package hint: gworldclock

Currently, the list of time zones shown by the application needs to be saved explicitly either by selecting ’Save Zones’ from the File menu, or by choosing to save it when exiting the application. It would be a usability improvement if Gworldclock instead used implicit save, i.e. saving the list automatically each time it’s changed, like Gnome usually does.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gworldclock 1.4.4-7ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
Architecture: amd64
CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Mon Jul 5 10:47:08 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 ”Karmic Koala” – Release amd64 (20091027)
ProcEnviron:
PATH=(custom, user)
LANG=fi_FI.utf8
SHELL=/bin/bash
SourcePackage: gworldclock

I’m in a system running the Netbook Environment, an up-to-date Lucid. In terminator’s settings, I have ’Terminal bell’ set to be shown as ’Window list flash’. This goes nicely together with irssi (which I’m running through ssh on a remote server) being set to ring the bell on messages I want to be informed of.

However, when the window list is flashing, and I bring the terminator window on top, it doesn’t clear the ”URGENT” — i.e. the window list keeps on flashing. Furthermore, in a split terminator window, if I left-click on the segment running irssi, which raised the ”URGENT”, the flashing still won’t stop. I have to type something into the terminal to make the flashing stop.

I’m not too familiar with the inner workings and relations between the different signals involved in here, but I presume the flashing should stop when the window with ”URGENT” is activated, or brought on top, or at least when the segment in question is activated (or left-clicked).

Steps to reproduce:
1. Set ’Terminal bell’ to make ’Window list flash’ in terminator’s settings.
2. Run an app that rings the terminal bell in terminator after a while.
3. De-activate terminator’s window (bring another app on top) and wait for the bell.
4. When terminator flashes in window list, activate it.

Expected result:
Terminator’s flashing in the window list stops.

Actual result:
Terminator keeps flashing in the window list until I type something into its window.

I just switched back to noveau and on a whim, tried disabling hardware acceleration from flash player’s settings (Right click -> Settings…) and lo and behold, fullscreen playback is now smooth again.

• output of dmesg from the affected system (42.7 KiB, text/plain)

I would go further than the original report and say that the icons are pretty useless in themselves: an envelope with an arrow does… what? Email the status to somebody? And a set of gears… huh? Icons ought to be as self-evident as possible, and having to hover over them to see the tooltips to understand their meaning is a failure in the icons’ design IMO.

With most statuses being quite limited in length, there’s plenty of screen real estate available, so why not just use text indicators for each of the icon’s functions, such as ’Reply’ and ’More…’?

(Hope I’m not making this sound too brash, I think Gwibber is an excellent tool and this is a minor annoyance.)

–no-existing-session is is a handy little parameter, as documented by –help:

jani@saegusa:~$ LC_ALL=C totem –help | grep no-existing
–no-existing-session Don’t connect to an already-running
instance

Totem’s man page however fails to mention –no-existing-session altogether.

jani@saegusa:~$ man -P cat totem | grep no-existing
jani@saegusa:~$

–no-existing-session is is a handy little parameter, as documented by –help:

jani@saegusa:~$ LC_ALL=C totem –help | grep no-existing
–no-existing-session Don’t connect to an already-running
instance

Totem’s man page however fails to mention –no-existing-session altogether.

jani@saegusa:~$ man -P cat totem | grep no-existing
jani@saegusa:~$