3.2.0-17.27 seems to be interchangeable with 3.2.0-17.26 in what I described above, i.e. no change wrt. this bug.

Just to correct myself on my previous-to-last comment: killing might not be necessary after all. I was able to make a stuck launcher start working again by switching between some windows. It definitely doesn’t work with just any two windows (tried this on the other desktop still exhibiting this) but which ones matter, I can’t tell yet.

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.

My Xorg log is flooded with lines about reusing xkmfile:

jani@saegusa:~$ grep ”XKB: reuse xkmfile /var/lib/xkb/server-” /var/log/Xorg.0.log | tail
[ 99.477] (II) XKB: reuse xkmfile /var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
[ 99.480] (II) XKB: reuse xkmfile /var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
[ 99.484] (II) XKB: reuse xkmfile /var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
[ 99.487] (II) XKB: reuse xkmfile /var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
[ 99.491] (II) XKB: reuse xkmfile /var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
[ 99.494] (II) XKB: reuse xkmfile /var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
[ 99.498] (II) XKB: reuse xkmfile /var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
[ 99.502] (II) XKB: reuse xkmfile /var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
[ 99.505] (II) XKB: reuse xkmfile /var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
[ 99.509] (II) XKB: reuse xkmfile /var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
jani@saegusa:~$ grep ”XKB: reuse xkmfile /var/lib/xkb/server-” /var/log/Xorg.0.log | wc -l
1507

Is this normal, caused by something in local configuration, or should I file a bug?

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.