chrome on f18 (fix)
Neal Becker
ndbecker2 at gmail.com
Wed Jan 16 18:38:04 UTC 2013
Reindl Harald wrote:
>
>
> Am 16.01.2013 18:03, schrieb Neal Becker:
>> Mike Wohlgemuth wrote:
>>
>>> On Wed, 2013-01-16 at 10:11 -0500, Neal Becker wrote:
>>>> Well, workaround really.
>>>>
>>>> /usr/lib64/libudev.so.0 -> /usr/lib64/libudev.so.1
>>>>
>>>
>>> A better solution is probably:
>>>
>>> yum remove google-chrome-stable
>>> yum install google-chrome-stable
>>>
>>> Woogie
>>>
>>
>> Really? I just tried it, but looks like google-chrome-stable is still linked
>> to libudev.so.0:
>>
>> ldd /opt/google/chrome/chrome | grep udev
>> libudev.so.0 => /lib64/libudev.so.0 (0x00007ff603cb0000)
>>
>
> for me it works, there must be some magic in the rpm-scripts
>
> [root at srv-rhsoft:~]$ ldd /opt/google/chrome/chrome | grep udev
> libudev.so.0 => not found
> libudev.so.1 => /lib64/libudev.so.1 (0x00007fbd92d17000)
Yes, if I remove /lib64/libudev.so.0 link, and then reinstall:
ldd /opt/google/chrome/chrome | grep udev
libudev.so.0 => not found
libudev.so.1 => /lib64/libudev.so.1 (0x00007f3c62696000)
which is weird, but somehow seems to work
More information about the users
mailing list