>From duplicate bug #1719300, the chromedriver binary also needs the
rpath.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1718885
Title:
chromium doesn't start in guest
patchelf is not available in trusty, so that won't work to set the rpath
on the binary after the build. Will need to patch chromium to set the
rpath at build time.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification
And the following fixes the issue:
sudo patchelf --set-rpath "\$ORIGIN/." /usr/lib/chromium-browser
/chromium-browser
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Chromium 60 was built with is_component_build=true. Chromium 61 is built
with is_component_build=false, and in that configuration the rpath does
not contain the directory where shared libs (such as libffmpeg.so) are
built. There's a good explanation of why there:
Confirmed, in chromium 60.0.3112.113 ldd was able to locate
libffmpeg.so:
$ ldd /usr/lib/chromium-browser/chromium-browser | grep ffmpeg
libffmpeg.so => /usr/lib/chromium-browser/./libffmpeg.so
(0x7fec793cc000)
In chromium 61.0.3163.79, it can't locate it:
$ ldd
> That's why the shell script /usr/bin/chromium-browser sets
LD_LIBRARY_PATH=/usr/lib/chromium-browser before executing the binary.
Yeah, with this info there is no need in ldd output, as it is not super
related to the problem.
--
You received this bug notification because you are a member of
> One other oddity is why all our LTS machines (both 14.04 and 16.04) now have
> libffmpeg.so
> in /usr/lib/chromium-browser, not /usr/lib/chromium-browser/libs. But when I
> checked
> with dpkg-query, the former (/usr/lib/chromium-browser/libffmpeg.so) is
> definitely
> what was listed, and
I'm not at the kiosks now and can't run apt-cache, but I did run ldd
earlier, and can report that for the Chromium binary (/usr/lib/chromium-
browser/chromium-browser) ldd reports libffmpeg.so as not found. That's
why the shell script /usr/bin/chromium-browser sets
All nine of our kiosks, running a mix of Ubuntu 14.04.5 LTS and 16.04.3
LTS, are now exhibiting this bug. So we can definitely reproduce it on
a mix of hardware and software. Uninstalling and reinstalling Chromium
did not help.
Here's someone else's forum post on the same topic too:
People with working chromium-browser 61 could you please post those
commands outputs here?
---
apt-cache policy chromium-browser
ldd /usr/lib/chromium-browser/chromium-browser
---
Maybe it'll help investigate this thing.
--
You received this bug notification because you are a
This also affects us. It started on Sep 22 on part of our test servers
as soon as chromium-browser upgraded to 61 from 60. What I have found so
far:
Chromium 60 uses libraries from its folder:
-
ubuntu@test4:~$ sudo apt-cache policy chromium-browser
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Description changed:
Hi,
on one of my kiosk systems running xubuntu 16.04.2 (Kernelversion
4.4.0-28-generic) chromium stop working today. It just won't start
- anymore. When try to run the launcher from shell it just reports:
+ anymore. When I try to run the launcher from shell it
I have done that to no avail.
libffmpeg is installed in /usr/lib/chromoium-browser/libffmpeg.so and
/usr/lib/x86_64-linux-gnu/oxide-qt/libffmpeg.so
On 22/09/2017 12:20, Olivier Tilloy wrote:
I can't reproduce the problem in a clean xenial VM.
When you say you can locate libffmpeg.so, where is
I can't reproduce the problem in a clean xenial VM.
When you say you can locate libffmpeg.so, where is it installed?
Does the following command improve things?
sudo apt install --reinstall chromium-codecs-ffmpeg-extra
--
You received this bug notification because you are a member of
16 matches
Mail list logo
