Bug #1208204 - "indicator-sound no longer functions with xfce4-indicator-plugin"

[P.K.]

Pasi: point taken, but the fix for this particular bug seems very easy to
roll out in an update:

Go to:
/usr/share/dbus-1/services/indicator-sound.service

Change the Exec line into:
Exec=/usr/lib/indicator-sound-gtk2/indicator-sound-service

Reboot and all is fine.

Now I readily admit that I'm no developer and I can't fabricate an update
package that does this, but *it looks* dead simple to do, in my layman's
eyes. And it *would* be a big Public Relations bonus for Xubuntu 13.10.

Regards, Pjotr.


2013/12/5 Pasi Lallinaho <pasi at shimmerproject.org>

>  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 13.10, but at that point of time we
> the patch was relatively untested, wasn't in the repositories and we were
> really short on time.
>
> The other option wasn't trivial either, and would have taken valuable
> developer time as well. In the end, trying to fix the GTK2 indicator stack
> would have meant a lot of work to get it working for 13.10. Whether we
> would have continued with that stack or not for 14.04 had it been done
> can't be evaluated. It's pretty certain that the GTK2 indicator stack would
> have kept on breaking, and we would have had to continue fixing those
> issues.
>
> All this being said, we shall look at backporting the GTK3 indicators to
> 13.10 later when the work on them is done. However, since I don't
> contribute to packaging or code-development, I'm the wrong person to say if
> this is likely or not.
>
> I see how people switching to other distros or back to older versions of
> Xubuntu could be considered a bad thing. From my personal point of view
> (all Xubuntu hats off), I don't think other open source OS's are our
> competitors. People have very different needs and workflows and they should
> use whatever works for them, whether it was Xubuntu, Ubuntu or any of its
> flavors or something completely different.
>
> Ultimately, 13.10 is not an LTS release, and those who want the maximum
> stability should keep with the LTS's. Again, it's unfortunate but things
> are going to break now and then. Now let's try to make 14.04 better; you
> all are welcome to help us with testing and whatever your skills and time
> allow!
>
> Cheers,
> Pasi
>
>
> On 05/12/13 00:18, Lutz Andersohn wrote:
>
> 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 personally feel
> that all distro's spend not enough time on regression testing when any new
> release comes out. New features are good but not at the expense of
> something that used to work.
>
>
>
> *Lutz Andersohn*
>
> lutz.andersohn at gmail.com
> (925) 784 1565
> D-19318, AFF-I
>
> http://www.linkedin.com/pub/1/b65/2b6 Public key ID: 0x9620D1A6
> On 12/04/2013 03:36 PM, Peter Flynn wrote:
>
> On 12/04/2013 05:33 PM, Bruno Benitez wrote:
>
>  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.
>
>  Speaking as a project manager (in a different field), I have every
> sympathy with this point of view...
>
>
>  It is very sad that we have this issue in first place, but control
> over sound was available and lots of tutorials on how to fix it
> where also available, if users would abandon just for this cause
> there is no much else we can do.
>
>  ...speaking as a psychologist, I would say that it may be useful for
> developers to understand that users *do* abandon distros for this kind
> of thing, and for even smaller ones.
>
> Their reasoning is that "if the developers can't get the small things
> right," (and they would view a plugin indicator as a "small thing"),
> "then there is little hope of the big things being right."
>
> It's a frighteningly brutal viewpoint, and when it happens in a
> commercial environment, a damaging one. The British have a phrase for
> it: "to spoil the ship for a pennyworth of tar" (from the days when
> wooden ships needed waterproofing with tar).
>
> On the other hand, it acts as a filter: users who do not have the
> inclination or skill to find a fix will leave the community. In the long
> term this may reduce the demand for support.
>
>
>  In any case the fix for the plugin indicators will be included in
> 14.04 and it will be an LTS, so that would be the recommended
> solution to anyone, just wait a few months.
>
>  A new user probably won't wait a few months to get a sound indicator
> working. They'll give up and install something else.
>
> ///Peter
>
>
>
>
>
>
>
>
>
> --
> Pasi Lallinaho (knome)                      » http://open.knome.fi/
> Leader of Shimmer Project and Xubuntu       » http://shimmerproject.org/
> Graphic artist, webdesigner, Ubuntu member  » http://xubuntu.org/
>
>
> --
> xubuntu-devel mailing list
> xubuntu-devel at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/xubuntu-devel/attachments/20131205/04c00542/attachment.html>