As has been pointed out right at the top of the thread, GNOME has very
clear rules and guidelines about how applications should behave in order
to fit in with the rest of the environment:
http://developer.gnome.org/projects/gup/hig/

Currently, Rhythmbox violates those guidelines, as clearly described in
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/38512/comments/12

This thread is getting very vocal about what people do and do not want,
and whether there should be defaults, or options, or plugins.  However,
the above should be all that is necessary to decide whether or not the
behaviour should be changed.

That said, how should Ubuntu react?  People seem to want them to push
out a bugfix update right now, but that just should not happen.  Read
the guidelines on when one can push a Stable Release Update:
https://wiki.ubuntu.com/StableReleaseUpdates

There are very good reasons why we wait for the next version of Ubuntu
before pushing some updates - this one is too trivial to warrant a
distribution update.  So, while I wholeheartedly agree that the problem
needs to be fixed, I also wholeheartedly agree that this thread is
getting out of control - no more "ME TOO THIS BUG SCUKS" comments,
please, everything that needs to be said has been said.  Now we wait.

(On a sidenote: I have attached a simple python script which will toggle
rhythmbox's visibility (launching it if it is not currently running) -
bind one of your hotkeys to run this script, use that hotkey instead of
the close-button or the panel icon - when I started doing this, I
stopped even realising that this bug still existed.)


** Attachment added: "Script to toggle rhythmbox's visibility (launching it if 
it is not currently running)"
   http://launchpadlibrarian.net/15688681/rhythmbox-toggle.py

-- 
Window close should close, not quit
https://bugs.launchpad.net/bugs/38512
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to