Too much unreasonable negativism, I think. Xubuntu 13.10 is generally a
fine operating system, of high quality. Stable as a rock and reliable.
The very small group of Xubuntu developers have done a great job, for which
I'm very grateful to them.
If you want an enterprise grade operating system,
PPA with fixed package:
https://launchpad.net/~a-j-buxton/+archive/indicator-sound-gtk2
ppa:a-j-buxton/indicator-sound-gtk2
This doesn't use the workaround from the bug report. It fixes it in a
way which is hopefully compatible with other desktops. It needs
testing though, on systems with both
Altogether this is an unfortunate situation, but there was little we
could do in time to get it fixed.
For 14.04, we're looking to migrate to a panel that has GTK3 support.
This should fix all the indicator issues/breakages that happened in the
last few cycles. This was one of the options for
Hi, Pjtor, I am not a programmer, but I see a huge problem with your very
easy fix, you see, xubuntu shares most and almost all their setting from
mainbuntu, so the file /usr/share/dbus-1/services/indicator-sound.service
belongs to all the *buntu multiverse, changing its content would have
The issues with bug #1208204 are these:
(1) The complaints began in July. As of 70 milliseconds ago, this bug
is not assigned to anyone, with a status of Undecided, and still
marked as New to Ubuntu Studio.
(2) See Peter Flynn's earlier mail. Well-articulated IMO.
(3) If the indicator-sound
I also felt this was a real issue. Between this and a number of other annoying
bugs - like race condition booting from SSD, new users may end up quite
disappointed. Hopefully the LTS will have a much higher quality.
- George
On Dec 5, 2013, at 10:19 AM, Richard Elkins richard.elk...@gmail.com
Hello Richard, as I understand from the meetings we have held , if there is
enough need of it our developers can make a fix through the backport
channel.
http://ubottu.com/meetingology/logs/xubuntu-devel/2013/xubuntu-devel.2013-11-03-22.39.log.html#l-41
It is very sad that we have this issue in
Thumbs up for Peter's sentiment
expressed in his email.
I might add, even for the users skilled enough and willing to dig
down and apply a workaround, it takes time. The situation becomes
even more frustrating if something used to work and got broken! I
