hi,
first of all, this isn't meant to be a distro trolling discussion, there are better places for that ;-)
several days ago google HO started to fail after updating my debian/sid setup. as discussed on G+ [1] and on googlegroups [2], that seemed to be impacting anyone on debian/sid. when i realized that it was working on debian/testing (Jessie) i decided just use 'testing'... however since last evening update on 'testing', it started to fail too.. leaving me without any working HO at all, which is quite inconvenient at Linaro..
after bisecting my system using snapshot.debian.org, i figured out which package was the culprit:
# apt-cache policy libcairo2 libcairo2: Installed: 1.12.14-4 Candidate: 1.12.14-4 Package pin: 1.12.14-4 Version table: 1.12.16-2 1001 500 http://ftp.fr.debian.org/debian/ testing/main amd64 Packages *** 1.12.14-4 1001 500 http://snapshot.debian.org/archive/debian/20130927T214600Z/testing/main amd64 Packages 100 /var/lib/dpkg/status
Simply downgrading libcairo2 [3] 'fixes' the problem. I know it's not 'fixing' it really, but i hope that this will be enough information so that the real fix is uploaded.
In the mean time, if any of use use Debian , you can use that as a workaround..
cheers
nico
[1] https://plus.google.com/u/0/108790110407014289037/posts/5q22d1ReavG [2] https://productforums.google.com/d/msg/hangouts/vYsaeEnXJXs/hOy2HaW5LKoJ [3] http://snapshot.debian.org/archive/debian/20130927T214600Z/pool/main/c/cairo...
On Tue, 1 Oct 2013 10:44:42 +0200 Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
hi,
first of all, this isn't meant to be a distro trolling discussion, there are better places for that ;-)
several days ago google HO started to fail after updating my debian/sid setup. as discussed on G+ [1] and on googlegroups [2], that seemed to be impacting anyone on debian/sid. when i realized that it was working on debian/testing (Jessie) i decided just use 'testing'... however since last evening update on 'testing', it started to fail too.. leaving me without any working HO at all, which is quite inconvenient at Linaro..
after bisecting my system using snapshot.debian.org, i figured out which package was the culprit:
# apt-cache policy libcairo2 libcairo2: Installed: 1.12.14-4 Candidate: 1.12.14-4 Package pin: 1.12.14-4
Interestingly 1.12.14-5 is *not* a sufficient downgrade, it needs to be 14-4, so it's not the new upstream 1.12.16 which has broken this support.
Simply downgrading libcairo2 [3] 'fixes' the problem. I know it's not 'fixing' it really, but i hope that this will be enough information so that the real fix is uploaded.
In the mean time, if any of use use Debian , you can use that as a workaround..
I'm assuming that this is a "proprietary-blob-linked-to-the-wrong-version" bug, but I've had google-talkplugin force an upgrade on me since this started and that didn't fix it.
google-talkplugin 4.6.3.0-1
However, with libcairo2 1.12.14-4, hangouts now work.
Thanks for this investigation. I'll have to see how long the rest of the desktop continues running with an old version of such a critical library....
The change in libcairo2 at 14-5 was: Add gl/egl support back now that wayland has been multi-archified.
http://ftp-master.metadata.debian.org/changelogs/main/c/cairo/unstable_chang... The change was made to fix: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712022
On 01.10.13 11:34 +0100, Neil Williams wrote:
On Tue, 1 Oct 2013 10:44:42 +0200 Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
[...]
several days ago google HO started to fail after updating my debian/sid setup. as discussed on G+ [1] and on googlegroups [2], that seemed to be impacting anyone on debian/sid. when i realized that it was working on debian/testing (Jessie) i decided just use 'testing'... however since last evening update on 'testing', it started to fail too.. leaving me without any working HO at all, which is quite inconvenient at Linaro..
after bisecting my system using snapshot.debian.org, i figured out which package was the culprit:
# apt-cache policy libcairo2 libcairo2: Installed: 1.12.14-4 Candidate: 1.12.14-4 Package pin: 1.12.14-4
Interestingly 1.12.14-5 is *not* a sufficient downgrade, it needs to be 14-4, so it's not the new upstream 1.12.16 which has broken this support.
Simply downgrading libcairo2 [3] 'fixes' the problem. I know it's not 'fixing' it really, but i hope that this will be enough information so that the real fix is uploaded.
In the mean time, if any of use use Debian , you can use that as a workaround..
I'm assuming that this is a "proprietary-blob-linked-to-the-wrong-version" bug, but I've had google-talkplugin force an upgrade on me since this started and that didn't fix it.
google-talkplugin 4.6.3.0-1
However, with libcairo2 1.12.14-4, hangouts now work.
Thanks for this investigation. I'll have to see how long the rest of the desktop continues running with an old version of such a critical library....
+1, thanks Nicolas!
The magic formula is: $ wget http://snapshot.debian.org/archive/debian/20130927T214600Z/pool/main/c/cairo... $ sudo dpkg -i libcairo2_1.12.14-4_amd64.deb
On Thu, 10 Oct 2013 13:39:27 +0300 Serge Broslavsky serge.broslavsky@linaro.org wrote:
However, with libcairo2 1.12.14-4, hangouts now work.
Thanks for this investigation. I'll have to see how long the rest of the desktop continues running with an old version of such a critical library....
+1, thanks Nicolas!
The magic formula is: $ wget http://snapshot.debian.org/archive/debian/20130927T214600Z/pool/main/c/cairo... $ sudo dpkg -i libcairo2_1.12.14-4_amd64.deb
While it lasts.
Sooner rather than later, an updated package elsewhere in sid/testing is going to need the updated cairo which underpins all of GTK (Gnome, XFCE, LXDE, Mint etc.). The better solution will be a wheezy chroot with a browser installed and using X forwarding.
If we could see the source code for google-talkplugin, it could be fixed....
On Fri, Oct 11, 2013 at 08:17:21AM +0100, Neil Williams wrote:
On Thu, 10 Oct 2013 13:39:27 +0300 Serge Broslavsky serge.broslavsky@linaro.org wrote:
However, with libcairo2 1.12.14-4, hangouts now work.
Thanks for this investigation. I'll have to see how long the rest of the desktop continues running with an old version of such a critical library....
+1, thanks Nicolas!
The magic formula is: $ wget http://snapshot.debian.org/archive/debian/20130927T214600Z/pool/main/c/cairo... $ sudo dpkg -i libcairo2_1.12.14-4_amd64.deb
While it lasts.
Sooner rather than later, an updated package elsewhere in sid/testing is going to need the updated cairo which underpins all of GTK (Gnome, XFCE, LXDE, Mint etc.). The better solution will be a wheezy chroot with a browser installed and using X forwarding.
what I'm using is just a wheezy chroot + schroot -p:
#!/bin/sh
schroot -p -c hangout -- /usr/bin/chromium
If we could see the source code for google-talkplugin, it could be fixed....
Not going to happen ...
+++ Antonio Terceiro [2013-10-14 11:19 -0300]:
On Fri, Oct 11, 2013 at 08:17:21AM +0100, Neil Williams wrote:
If we could see the source code for google-talkplugin, it could be fixed....
Not going to happen ...
Any word on whether upstream is going to fix it? This seems quite badly broken.
Can we try using jitsi or similar (which is alleged to work well these days over SIP or XMPP) then we wouldn't be knackered by unfixable proprietary breakage like this, and people could use either in-browser WebRTC tech or whatever local client they preferred? It just needs SIP/XMPP accounts for everyone, and we'd be smart to run our own turn server.
Wookey
On 14.10.13 19:03 +0100, Wookey wrote:
+++ Antonio Terceiro [2013-10-14 11:19 -0300]:
On Fri, Oct 11, 2013 at 08:17:21AM +0100, Neil Williams wrote:
If we could see the source code for google-talkplugin, it could be fixed....
Not going to happen ...
Any word on whether upstream is going to fix it? This seems quite badly broken.
JFYI, it seems to be working again for me on Debian testing.
-
Antonio Terceiro -
Neil Williams -
Nicolas Dechesne -
Serge Broslavsky -
Wookey