I got this comment from the bot in a bug report (bug #907668):

”Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:”

And so on.

Instead of ”an useful” it should say ”a useful”.

I had plugged in my phone via USB (as a mass memory device), after which Nautilus and Miro crashed. I was trying to send a report from Miro when this occurred. Other GUI apps running at the time were Synaptic, Chromium and Transmission.

There are lots of reports with this title already, but they are all from pre-11.10 era, and I believe there’s a bot that’ll tell me if this is a duplicate so no harm done if it is.

I think it’s worse than just that the icon doesn’t convey the program’s purpose: it looks way too much like a flatbed scanner. I appreciate the difficulty in crafting a descriptive visual representation of a BT client, but IMHO an icon should at least be sufficiently unique so as to avoid mistaking it for other apps of completely unrelated purposes. That’s where Vuze’s frog for example is better (as long as you’re not into Frogger clones). I’ve been running Transmission whenever I’m logged in for years now, and I still occasionally wonder why I have a scanning app running, when in fact it’s just Transmission’s… I’m-not-sure-what-it-is.

I realize this is not a very constructive argument so long as I don’t have anything better to suggest in the current icon’s place, but I promise I’ll start thinking of one right now and hopefully come up with ideas some day.

@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.