@David: I have this bug but only with HDMI output from my gfx adapter. #23 works here, so as per your #30 I’m about to file a separate bug, but would the driver at fault in this case be for the underlying (Intel) sound card or for the (Radeon) display adapter? Audio coming through analog (headphones) never crackles.

Ah, it seems I am able to bring up the menu 100 % reliably on the M4A78-EM as well by hitting and holding the shift *immediately after firmware initialization screens* (Asus’ boot graphic and ATA Security eXtension). So holding shift from power-up or from the boot graphic screen won’t work in this setup, but seems to work with others (such as my FS laptop). I’d expect it to work from power-up consistently across different setups.

To be even more Precise: you *can* quit RB when it’s playing, but only by using Ctrl-Q or the corresponding Quit item from the menu. What you *cannot* do is quit RB when it’s playing by clicking the window close button, even if you *don’t use the indicator*.

To be sure, I removed the indicator-sound package so that indicator-sound doesn’t appear in my indicator area at all, and still, RB’s window closing button while playing music just makes the window disappear; the music keeps on playing.

With the broadly defined title that bug #526552 has, I don’t think it’s completely fixed yet: the specification says a ”player’s own settings interface should also have a checkbox for whether the player should be present in the sound menu”, and RB doesn’t have that. I see no no way to disable RB’s sound menu integration.

Also of note is that at least in the Finnish locale, the menu item actually translates to ’Close’ and not ’Quit’, so there it behaves as intended.

Confirming. If the menu item is meant to close the window and not quit the application, it’d be labeled such.

Oh, but I couldn’t reproduce it on a Fujitsu Siemens Amilo M7400 laptop, so it seems to be hardware dependent.

Still present on Precise today. I’m on an Asus M4A78-EM and a PS/2-connected keyboard, if that matters.

Jaaha, saan näitä postauksia näköjään jälkilähetyksenä (syöte toimii, mutta Google Reader näytti tämänkin vasta tänään). Tässä on ilmeisesti sama meemi kuin minkä ite äskön tein, mutta tässä on korjattu kieltä ja muita bugeja. Ja tässä on muutama kohta enemmän.

I suggest that the title be changed to somehow reflect that this is (apparently indirectly) related to g_spawn_async_with_pipes() too. I was about to report a duplicate with the title this bug initially had, and I see others have fallen for it too (Ref: Bug #904899). As it stands, bug reporters have to catch g_spawn_async_with_pipes() from a greyed-out comment made by a bot. I think some confusion could be avoided if Launchpad, when suggesting this, had g_spawn_async_with_pipes() right in the title. How about ”deja-dup-monitor crashed with SIGSEGV in child_setup(), g_spawn_async_with_pipes()”?

The Genre list on the Radio view has genres called ”80’s”, ”90’s” and ”Rock’n’Roll”.

They should be ”The ’80s”, ”The ’90s” and ”Rock ’n’ Roll”, respectively.