[Updated 9 January to include a status update on the Chromium issue. -Peng]
[Updated 10 January to report that the daily build of Chromium is working again. -Peng]
A day or two ago I noticed that I’ve been having problems getting Evolution opened due to a glitch in the RSS plugin that also affects Liferea and my affect other RSS readers. You know you are affected by this bug when you launch your RSS reader in the terminal and see an error that says something like
symbol lookup error: /usr/lib/libwebkit-1.0.so.2: undefined symbol: soup_content_decoder_get_type
I found a thread on the Ubuntu Forums that has a great fix for this bugger. It turns out something happened withe the WebKit Team PPA and they have to do a major upgrade. The short form answer is that you should open Symantic and do a search for libsoup. Look for libsoup2.4-1 and libsoup-gnome2.4-1, then select each package one at a time and use Package > Force Version to select these versions:
- libsoup2.4-1_2.28.2-1~kkwkt1
- libsoup-gnome2.4-1_2.28.2-1~kkwkt1
Apply the changes and you should be able to open your app. Please do not accept upgrades for these packages until you see an updated package that’s newer than today (the best place to see that info is to check the PPA link I posted above and check for a published date that’s later than today).
The Evo bug is one I’ve been dealing with for a few days, but after getting the daily updates I was found that Chromium flat won’t run anymore. Not even Epiphany would run anymore so I had to fire up Firefox to find a bug report. I found Issue 31809: chromium does not start: Inconsistency detected by ld.so. Comment 17 has a fix for us.
Please stop confirming. We have enough info to show that it’s reproducible on a bunch of different ubuntu distros so it’s not something else. the bug is definitely in chromium (or in the way it is built in ubuntu). The error message seems to indicate
something about memory corruption.
In the meantime, you can downgrade to yesterday’s version, or shift to one of the other channels/PPAs:
https://launchpad.net/~chromium-daily/+archive/dev
https://launchpad.net/~chromium-daily/+archive/beta
fta’s comment about not needing to confirm it anymore is because most of the previous comments were “me too” comments. I added the first PPA (the “dev” one) and was able to roll back Chromium to a version that works (version 4.0.266.0 (Developer Build 33992)).
I need to run to the grocery store before the place gets too crazy but I wanted to make sure I had the fixes for these two issues posted before I run out the door.
Updated 9 January 8:15am: I just saw a comment on the Chromium bug that I wanted to pass along.
malloc overrides have been reenabled in r35823, using a different method.
Ubuntu folks: tomorrow’s PPA will not have any malloc overrides and the next day’s will have the new set. Hopefully that will be enough to disambiguate any issues.
At some point, bugdroid will wake up and spam this bug will all the change records
In other words if you’re running Ubuntu don’t take the update today (Saturday), wait until Sunday’s update is available. And before you accept the update pop over to the bug report and see if there’s a confirmation that the bug is fixed for us. I’ll update this post again when I have confirmation that the daily build runs on Ubuntu again. Big thanks to agl for fixing the bug and for making sure Ubuntu users have the status information we need for running this great browser.
Updated 10 January 9:35am: I am very happy to say that the Chromium Daily PPA once again has packages that can be used by users of Ubuntu 9.10. Open your Software Sources (Applications > System > Administration > Software Sources), go to the Other Software tab, and make sure the only Chromium PPA enabled is the PPA for Ubuntu Chromium – Daily Builds (http://ppa.launchpad.net/chromium-daily/ppa/ubuntu) or a similar source for your system. The PPA should not be the dev or beta source I listed in my original post. Then update your package information with sudo apt-get update and you should see that there are updates available for chromium-browser. As the screenshot on the right shows the version you want to take to is 4.0.295.0~svn20100110r35882-0ubuntu1~ucd1~karmic, specifically looking for “r35882″. Install the updates, close Chromium, and when you relaunch Chromium you should be able to go to about:version and see something like this:
Chromium 4.0.295.0 (Developer Build 35882) Ubuntu
If you can’t launch Chromium after installing version 4.0.295.0~svn20100110r35882-0ubuntu1~ucd1~karmic than I think it’s safe to say that either you didn’t get the proper version or you have a glitch in your old install. Go ahead and remove, but not purge, Chromium with sudo apt-get remove chromium-browser and then reinstall it (sudo apt-get install chromium-browser). That should get your system able to launch Chromium again.
Yooouge thanks to Fabien Tassin (aka fta) and the rest of the Chromium devs for helping us identify, workaround and resolve this issue for us. Each of us owe you at least a round of drinks.
Like this:
Be the first to like this post.