Webkit upgrade 1.8.1-3.4 > 2.4.1-1 breaks things

[Muximize]

Today I ran sudo apt-get update && apt-get dist-upgrade which upgraded libwebkitgtk-3.0-0 from 1.8.1-3.4+rpi1 to 2.4.1-1rpi22rpi1 together with a bunch of dependencies.

After that, my application (using gkreidl's fantastic Minimal Kiosk Browser) stopped working properly. HTML was rendered correctly, but CSS animations where ignored. Reverting libwebkitgtk (and libjavascriptcoregtk) to the previous version fixed this.

Is anyone else having issues with the updated Webkit?
What is the right place to submit bugs like this?
Where can I find information on when and why these packages where added to the repository?

[plugwash]

What is the output of

apt-cache policy libwebkitgtk-3.0-0

I suspect this is collabora's doing.

[Muximize]

Code: Select all

$ apt-cache policy libwebkitgtk-3.0-0
libwebkitgtk-3.0-0:
  Installed: 1.8.1-3.4+rpi1
  Candidate: 2.4.1-1rpi22rpi1
  Version table:
     2.4.1-1rpi22rpi1 0
        500 http://archive.raspberrypi.org/debian/ wheezy/main armhf Packages
 *** 1.8.1-3.4+rpi1 0
        500 http://mirrordirector.raspbian.org/raspbian/ wheezy/main armhf Packages
        100 /var/lib/dpkg/status

[plugwash]

Ok, looks like it's the raspberry pi foundation's doing. Complain to them.

[Muximize]

I'd love to, but I can't find how to best reach the foundation on technical issues. Aren't they on this forum?

[gkreidl]

Today I ran sudo apt-get update && apt-get dist-upgrade which upgraded libwebkitgtk-3.0-0 from 1.8.1-3.4+rpi1 to 2.4.1-1rpi22rpi1 together with a bunch of dependencies.

After that, my application (using gkreidl's fantastic Minimal Kiosk Browser) stopped working properly. HTML was rendered correctly, but CSS animations where ignored. Reverting libwebkitgtk (and libjavascriptcoregtk) to the previous version fixed this.

Is anyone else having issues with the updated Webkit?
What is the right place to submit bugs like this?
Where can I find information on when and why these packages where added to the repository?

It seems that you have installed the experimental web = Epiphany browser. To get this to work, a lot of system libraries have to be upgraded to newer versions which may (or will) break a lot of stable Wheezy applications. I've warned about that from the beginning.

If I would install that on my current system I would not to be able to create a stable, well tested version of Minimal Kiosk Browser any more. So I have no chance to test how Kweb works with the modified webkitgtk libraries (I'm running from HD and don't want to corrupt that)..

The only secure way to do this would be to switch to Jessie first which has all the new libraries installed. I'll create a Jessie OS on a separate RPi in a while and then I'll create a version of kweb compiled for Jessie. That might work with the modified libraries from Collabora (and I'll have at least a chance to test it). One of the reasons I haven't done that yet is the unsolved issue of adding gstreamer-1.0 with OMX support for the RPi to Jessie. Then kweb may also be able to play web video (at least SD resolutions) inside the browser window without having to use omxplayer. That's the reason for the "use omxplayer" toggle button in the toolbar.

[fruitoftheloom]

Hi gkreidl Web (Epiphany 3.8.2) Web Browse Beta I have installed and it does in fact not render CSS3 and to be quite truthfu apart from a few updates it does not seem any better now than it did 8 months ago, which is a shame

Personally I do not feel that it is ready for prime time so we either use Minimal Kiosk or wait for an update to Midori

https://developer.cdn.mozilla.net/media ... index.html

Code: Select all

apt-cache policy libwebkitgtk-3.0-0
libwebkitgtk-3.0-0:
  Installed: 2.4.1-1rpi22rpi1
  Candidate: 2.4.1-1rpi22rpi1
  Version table:
 *** 2.4.1-1rpi22rpi1 0
        500 http://raspberrypi.collabora.com/ wheezy/web armhf Packages
        500 http://archive.raspberrypi.org/debian/ wheezy/main armhf Packages
        100 /var/lib/dpkg/status
     1.8.1-3.4+rpi1 0
        500 http://mirrordirector.raspbian.org/raspbian/ wheezy/main armhf Packages

[Muximize]

Thanks for the explanation gkreidl.

I did not install Collabora's Web myself, it seems like someone put it in the live repo yesterday. Apt-get upgrade said "packages kept back" including webkit. That's why I ran dist-upgrade.

[gkreidl]

Thanks for the explanation gkreidl.

I did not install Collabora's Web myself, it seems like someone put it in the live repo yesterday. Apt-get upgrade said "packages kept back" including webkit. That's why I ran dist-upgrade.

That's bad news! What do you get when you run:

Code: Select all

cat /etc/apt/sources.list

?

[Muximize]

Code: Select all

$ cat /etc/apt/sources.list
deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi

[gkreidl]

Code: Select all

$ cat /etc/apt/sources.list
deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi

I just also got libwebkitgtk-3.0-common_2.4.1-1rpi22rpi1_all.deb via normal upgrade (no dist-upgrade). This must be a heavily fixed version, as a normal webkitgt-3.0 2.4.1 would require lots of other upgrades. but only very few packages have been upgraded.

I'll check the webkitgtk documentation for changes. So far I have not met any problems. Can you give me a link to some page that doesn't work any more (you mentioned CSS animation)?

Update: I've just seen the large amount of upgrades you get via dist-upgrade.

[fruitoftheloom]

Hi gkreidl I use this for CSS3 testing https://developer.mozilla.org/en-US/demos/tag/tech:css3

[plugwash]

It seems that you have installed the experimental web = Epiphany browser. To get this to work, a lot of system libraries have to be upgraded to newer versions which may (or will) break a lot of stable Wheezy applications. I've warned about that from the beginning.

If you read his apt-cache policy output that version of webkit came from the main foundation repository, not from the collabora "web" repository.

My guess would be the foundation have copied the "web" stuff to their main repository.

[gkreidl]

If you read his apt-cache policy output that version of webkit came from the main foundation repository, not from the collabora "web" repository.

My guess would be the foundation have copied the "web" stuff to their main repository.

Yes. and after running dist-upgrade the whole system is a terrible mess. Lots of applications are throwing critical errors (Lxterminal, Openbox window manager ..), true color (32 bit display) video output has complementary colors (blue is yellowish and vice versa) in the browser and Javascript has turned into pure pain (freezing the RPi for minutes) ... I'll give a more detailed report when I've had more time for testing.

This is no stable Wheezy any more, neither is it Jessie testing, it's just a mess in between.

[asb]

If you read his apt-cache policy output that version of webkit came from the main foundation repository, not from the collabora "web" repository.

My guess would be the foundation have copied the "web" stuff to their main repository.

Yes. and after running dist-upgrade the whole system is a terrible mess. Lots of applications are throwing critical errors (Lxterminal, Openbox window manager ..), true color (32 bit display) video output has complementary colors (blue is yellowish and vice versa) in the browser and Javascript has turned into pure pain (freezing the RPi for minutes) ... I'll give a more detailed report when I've had more time for testing.

This is no stable Wheezy any more, neither is it Jessie testing, it's just a mess in between.

Updating dependencies is not ideal for sure, though needless to say we haven't encountered any of those issues in testing. I look forward to your more detailed report.

[Fidelius]

Yes. and after running dist-upgrade the whole system is a terrible mess. Lots of applications are throwing critical errors (Lxterminal, Openbox window manager ..), true color (32 bit display) video output has complementary colors (blue is yellowish and vice versa) in the browser and Javascript has turned into pure pain (freezing the RPi for minutes) ... I'll give a more detailed report when I've had more time for testing.

This is no stable Wheezy any more, neither is it Jessie testing, it's just a mess in between.

The weekend update (apt-get update, then apt-get dist-upgrade) also broke GNOME's "mahjongg". When you start it, it crashes with some protected memory error (would have to copy message from the Pi). And this is just one of the few programs I tested.

P.S: Also the Raspberry Logo in the lightdm welcome screen is broken.

Hm....

[gkreidl]

Apologies for asking but what relevance is this to libwebkit3 and CSS3

Would it not be prudent to start a new post explaing your issues, so that the developers can ascertain how this situation has arisen ?

To get the new version of webkitgtk working lots of packages had to be updated to newer versions ... and breaking other, not updated programs that way. But I'll open a new thread tomorrow about problems with the new dist-upgrade. I'll have to run some more tests first.

That was my message (translated back from German):
81 updated, 46 new installed, 7 removed
That's quite a lot.

[fruitoftheloom]

Apologies for asking but what relevance is this to libwebkit3 and CSS3

Would it not be prudent to start a new post explaing your issues, so that the developers can ascertain how this situation has arisen ?

To get the new version of webkitgtk working lots of packages had to be updated to newer versions ... and breaking other, not updated programs that way. But I'll open a new thread tomorrow about problems with the new dist-upgrade. I'll have to run some more tests first.

That was my message (translated back from German):
81 updated, 46 new installed, 7 removed
That's quite a lot.

Had uninstalled Web Web Browser, libwebkit3 and all dependencies, then autoremove/autoclean, and put back sources to wheezy default.

Update, upgrade, dist-upgrade, rpi-update

Manually reinstall libwebkit3 via synaptic and ensured all packges which required additinal configuration where full installed andno issues what so ever !!!

Code: Select all

apt-cache policy libwebkitgtk-3.0-0
libwebkitgtk-3.0-0:
  Installed: 2.4.1-1rpi22rpi1
  Candidate: 2.4.1-1rpi22rpi1
  Version table:
 *** 2.4.1-1rpi22rpi1 0
        500 http://archive.raspberrypi.org/debian/ wheezy/main armhf Packages
        100 /var/lib/dpkg/status
     1.8.1-3.4+rpi1 0
        500 http://mirrordirector.raspbian.org/raspbian/ wheezy/main armhf Packages

The response about thread hijacking was aimed at Fidielus as he did not state he had a libwebkit error, I myself posted as after the OP posted I checked CSS3 and found same issue that I had the collabora update, but now have the RPF update.

FYI IceWeasel though slow is a fallback

[gkreidl]

I don't have the collabora repository enabled. Everything I got with dist-upgrade came from the foundation.

[fruitoftheloom]

UPDATE: have installed KWEB 1.5.1 in Jessie and CSS3 is working using this demo

https://developer.cdn.mozilla.net/media ... index.html

Code: Select all

apt-cache policy libwebkitgtk-3.0-0
libwebkitgtk-3.0-0:
  Installed: 2.4.4-2
  Candidate: 2.4.4-2
  Version table:
 *** 2.4.4-2 0
        500 http://mirrordirector.raspbian.org/raspbian/ jessie/main armhf Packages
        100 /var/lib/dpkg/status
     2.4.1-1rpi22rpi1 0
        500 http://raspberrypi.collabora.com/ wheezy/web armhf Packages
        500 http://archive.raspberrypi.org/debian/ wheezy/main armhf Packages

[diederik]

Updating dependencies is not ideal for sure, though needless to say we haven't encountered any of those issues in testing. I look forward to your more detailed report.

Is it an idea to add a testing/jessie repo to raspberrypi.org wheezy repo?
When there's a new package add it to the testing repo first and when there are no (important) bugs reported then migrate it to wheezy. My guess is that quite a few users would run testing/jessie and that means that it would get tested by a lot of users before it gets migrated to stable/wheezy.

[gkreidl]

Before I'm giving any detailed report I'm busy with an emergency update of Minimal Kiosk Browser. I'm reverting back to gtk+2 and libwebkit1 and add an experimental version (kweb3) that will use the new libraries (and happily freeze and crash when visiting certain websites). I've got it running alreday; it's lots faster, supports true color (32 bit) again and doesn't crash. (all crashes I've seen so far came from openbox and Javascript, mostly critical warnings, errors, segfaults and so on from the new glib libraries).

[Muximize]

So, here's the reason this was put in the Repo:

http://www.raspberrypi.org/web-browser-released/

[fruitoftheloom]

So, here's the reason this was put in the Repo:

http://www.raspberrypi.org/web-browser-released/

Yes quite so, though I have been using Web Epiphany Browser Beta with the latest version of libwebkit3 without issue and originally Collabora pushed out this update.


It seems the maintainers of Raspbian Wheezy thought it was stable enough, though it is not yet in Debian Wheezy Stable

https://packages.debian.org/wheezy/libwebkitgtk-3.0-0 Package: libwebkitgtk-3.0-0 (1.8.1-3.4)


As I stated above the issue is not in Raspbian Jessie Testing

https://packages.debian.org/jessie/libwebkitgtk-3.0-0 Package: libwebkitgtk-3.0-0 (2.4.4-2 and others)

[asb]

So, here's the reason this was put in the Repo:

http://www.raspberrypi.org/web-browser-released/

Yes quite so, though I have been using Web Epiphany Browser Beta with the latest version of libwebkit3 without issue and originally Collabora pushed out this update.


It seems the maintainers of Raspbian Wheezy thought it was stable enough, though it is not yet in Debian Wheezy Stable

https://packages.debian.org/wheezy/libwebkitgtk-3.0-0 Package: libwebkitgtk-3.0-0 (1.8.1-3.4)


As I stated above the issue is not in Raspbian Jessie Testing

https://packages.debian.org/jessie/libwebkitgtk-3.0-0 Package: libwebkitgtk-3.0-0 (2.4.4-2 and others)

To be totally clear, there is a difference between pure Raspbian wheezy (as maintained by plugwash), and what is distributed to users in official Foundation SD Card images. It's hoped there are very few issues left due to upgrading these packages, but please do report them here or on the blog post (and NOT on the Raspbian bug tracker).