Hi Gerry. Here’s output on my desktop:
jani@saegusa:~$ gsettings get com.canonical.Unity2d.Launcher hide-mode
1

Here’s output on my laptop, which is also affected:
jani@lemmikki:~$ gsettings get com.canonical.Unity2d.Launcher hide-mode
2

(I’ve changed the setting myself using dconf-editor on my desktop but not on my laptop, IIRC.)

Amusingly, it’s as if that query now triggered the issue at hand: launcher is currently stuck visible on both computers as I’m typing this. Let me try… No, unfortunately it was apparently just a coincidence: I couldn’t reproduce it with the gsettings command deliberately again after killing the stuck U2D.

@jsalisbury: Yeah, my Intel hardware’s got its own set of problems. :) I’ll get back to doing tests on those later this week.

Happened when trying to navigate to a parent directory in the directory chooser (which directory to save the screenshot in) using the parent directory button on the path buttons line. I don’t believe it has happened before.

I was looking at a JPEG image and accidentally used the scrolling wheel on my mouse, which caused Gthumb to move to a WMV file. This resulted in the crash at hand. Hasn’t occurred before.

I’ve just had a GPU lockup with 3.3.0-030300rc4-generic. Would this be yet another issue (i.e. not this bug nor bug #938894)? If so, where (if anywhere) should I file it? I’m pasting below here what was in syslog about it.

Feb 26 19:53:38 saegusa kernel: [ 8031.040107] radeon 0000:01:05.0: GPU lockup CP stall for more than 419884msec
Feb 26 19:53:38 saegusa kernel: [ 8031.040113] GPU lockup (waiting for 0x00103023 last fence id 0x00103022)
Feb 26 19:53:38 saegusa kernel: [ 8031.040125] [drm] Disabling audio support
Feb 26 19:53:38 saegusa kernel: [ 8031.041548] radeon 0000:01:05.0: GPU softreset
Feb 26 19:53:38 saegusa kernel: [ 8031.041550] radeon 0000:01:05.0: R_008010_GRBM_STATUS=0xA0003030
Feb 26 19:53:38 saegusa kernel: [ 8031.041551] radeon 0000:01:05.0: R_008014_GRBM_STATUS2=0x00000003
Feb 26 19:53:38 saegusa kernel: [ 8031.041553] radeon 0000:01:05.0: R_000E50_SRBM_STATUS=0x20000040
Feb 26 19:53:38 saegusa kernel: [ 8031.041559] radeon 0000:01:05.0: R_008020_GRBM_SOFT_RESET=0x00007FEE
Feb 26 19:53:38 saegusa kernel: [ 8031.056444] radeon 0000:01:05.0: R_008020_GRBM_SOFT_RESET=0x00000001
Feb 26 19:53:38 saegusa kernel: [ 8031.072335] radeon 0000:01:05.0: R_008010_GRBM_STATUS=0xA0003030
Feb 26 19:53:38 saegusa kernel: [ 8031.072337] radeon 0000:01:05.0: R_008014_GRBM_STATUS2=0x00000003
Feb 26 19:53:38 saegusa kernel: [ 8031.072339] radeon 0000:01:05.0: R_000E50_SRBM_STATUS=0x20008040
Feb 26 19:53:38 saegusa kernel: [ 8031.073333] radeon 0000:01:05.0: GPU reset succeed
Feb 26 19:53:38 saegusa kernel: [ 8031.094096] [drm] PCIE GART of 512M enabled (table at 0x00000000C0040000).
Feb 26 19:53:38 saegusa kernel: [ 8031.094153] radeon 0000:01:05.0: WB enabled
Feb 26 19:53:38 saegusa kernel: [ 8031.094156] [drm] fence driver on ring 0 use gpu addr 0xa0000c00 and cpu addr 0xffff88020f609c00
Feb 26 19:53:38 saegusa kernel: [ 8031.127631] [drm] ring test on 0 succeeded in 1 usecs
Feb 26 19:53:38 saegusa kernel: [ 8031.127656] [drm] ib test on ring 0 succeeded in 1 usecs
Feb 26 19:53:38 saegusa kernel: [ 8031.127659] [drm] Enabling audio support

(For the ”launcher getting stuck despite autohide being set” part, see bug #940590.)

I can confirm this is an issue, though I can’t reproduce it with Nicholas’ recipe. Not sure what double-clicking should do, here it works just as single-clicking does (bringing the group of windows to front in the order I left them). Thus I have no recipe to reproduce the issue, here it seems to happen seemingly at random. It is quite frequent though, happens multiple times a day and after it’s triggered nothing short of killall unity-2d-shell fixes it.

I believe this started with the recentmost big Unity updates, 5.4 I think. It wasn’t present in prior versions.

Confirming the issue of not being able to get rid of indicator-messages apart from uninstalling it system-wide, but not agreeing with stuffing the menu with another item just for solving this. IMHO Indicator-messages should be de-/selectable in Startup Applications preferences (like indicator-multiload for instance is).

According to an answer on Ask Ubuntu [1], blacklisting all message-providers should hide indicator-messages altogether, but this doesn’t seem to work in 12.04, apparently because status-providers (which are different from message-providers) are still using the menu. (U1 Control Panel also seems to still occupy it despite being blacklisted.)

I’ve even tried overriding indicator-messages’ dbus service file with a hackish solution [2], but the envelope still insists on appearing (though without the associated menu).

* [1] http://askubuntu.com/a/15616/34756
* [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544483#42

There are many windows that would benefit from having the maximize button available but don’t. I produced snapshots of the history window, the ’Downloading Package Information’ window and the ’Mark additional required changes’ window. IIRC, the downloading packages and installing packages windows are also affected, though I couldn’t produce snapshots of those right now without installing sh… numerous packages I don’t want. Software sources is also affected, I guess that should be marked separately.

All these windows tend to have huge listings in them, and scrolling through those listings in cramped space is difficult. They’re already resizable (as they should be), so why not allow easy maximizing as well?

Seems to happen every time I update package listings now, right after all downloads have finished. It doesn’t prevent upgrading however, because if I restart Synaptic after the crash, all the listing updates have been applied and downloading the upgraded packages doesn’t crash Synaptic.