Latest Yum Update Messed Up Chrome
I yum updated yesterday and it updated chrome from 44.x to 45.x.
It runs but it has errors going to web pages and won’t load its own settings/extension pages either. I ran chrome from the command-line and see these errors:
$ google-chrome libGL error: dlopen /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
libGL error: failed to load driver: swrast
[13006:13043:0901/222041:ERROR:logging.h(779)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd was not provided by any .service files
[13006:13043:0901/222041:ERROR:native_backend_kwallet_x.cc(412)] Error contacting kwalletd (isEnabled)
[13006:13043:0901/222041:ERROR:logging.h(779)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
[13006:13043:0901/222041:ERROR:native_backend_kwallet_x.cc(412)] Error contacting kwalletd (isEnabled)
[13006:13046:0901/222041:ERROR:zygote_host_impl_linux.cc(374)] Did not receive ping from zygote child
[6:6:0901/222041:ERROR:zygote_linux.cc(573)] Zygote could not fork: process_type renderer numfds 5 child_pid -1
[13006:13046:0901/222041:ERROR:zygote_host_impl_linux.cc(374)] Did not receive ping from zygote child
I wish I could go back to a previous version of 44, but I can’t find a previous version. It seems google likes to hide those. This is the CentOS I have:
lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch Distributor ID: CentOS
Description: CentOS Linux release 7.1.1503 (Core)
Release: 7.1.1503
Codename: Core
I then decided to update the graphics drivers from ati web site to see if that would help. Now I can’t boot to a login. It stops at Reached target Graphical Interface.
I reboot then pressed e at a boot line. Do I remove load_video to get just a console so I can remove the ati driver?
I just removed that line and it says press Ctrl-x to start or ctrl-c fro command prompt, but all it get are x for ctrl-x on the screen and c for ctrl-c.
Any ideas from here?
Thanks,
-wes
10 thoughts on - Latest Yum Update Messed Up Chrome
Op 2-sep.-2015 20:59 schreef Wes James:
I had trouble with Chrome today, it turned out tot be a Selinux issue. There is a RedHat bugreport for it.
Greetz Johan
Ah, yes. I saw that when running. But I think I got a message like that each time I ran chrome??
Thanks,
wes
——– Original message ——–
Ah, yes. I saw that when running. But I think I got a message like that each time I ran chrome??
Thanks,
wes
Usually, selinux tells what you need to do in order to stop receiving its error messages about a particular problem. Did you peruse the full message, and not just the ‘headline’?
Sent from my Samsung Galaxy S5
Am 02.09.2015 um 21:10 schrieb Johan Vermeulen:
Maybe (i’m not running CentOS on my desktop) it will help to install mesa-dri-drivers. This package contains the missing library.
regards Ulf
—– Oorspronkelijk bericht —
On 6.7, it won’t even run till I set SELinux to permissive.
I see, as mentioned, a RedHat bug about it, (though that seems to be for RH-7.x
https://rhn.redhat.com/errata/RHBA-2015-1701.html
To be more accurate, it will open, but I will get the Oh snap page saying it’s crashed, all extensions will crash (same happens if I disable all extensions).
As most google-chrome users probably already know, the latest SELinux updates have fixed the issue, and google-chrome once again runs with SELinux at enforcing.
Thanks for the info. Now I need to go google some pages to find out how I can log in to my box after installing ati drivers which now won’t boot to the gui. I need to get in and remove that .rpm and I’ll probably be able to boot after that.
-wes
woo-hoo – got it. I tried different kernel boot selections and decided to select the rescue one. It came up with a CentOS background then would go away from that to a screen saying there was a problem then a logout button in the middle that would do nothing. I pressed ctl-alt-f2 and got a text based login screen and logged in and removed the fglrx*.rpm whatever I got from ati/amd. Rebooted and got a gui and logged in and then ran the yum update and chrome now works :)
Now I can update my student labs – manual login for updates is a pita grande!
-wes