Yup, either method should work. For the next image, we're going with the null symlink to avoid cluttering the cmdline.hippy wrote: I added net.ifnames=0 to cmdline.txt to revert back to using eth0 which has fixed the issues I had with apps expecting that rather than the new convention. That seemed to work.
I am seeing this on a NOOBS install I have, but not on the image... interesting. Is this a NOOBS install in your case?hippy wrote:The dhcp.conf has a rather odd group attribute of "82" -
Yes, via NOOBS install. Only Raspbian installed - Sorry, should have mentioned that!ShiftPlusOne wrote: ↑Mon Aug 21, 2017 12:55 pmI am seeing this on a NOOBS install I have, but not on the image... interesting. Is this a NOOBS install in your case?hippy wrote:Thedhcp.confdhcpcd.conf has a rather odd group attribute of "82" -
Code: Select all
pi@Pi3B:~$ cat /etc/group| grep "pi"
adm:x:4:pi
dialout:x:20:pi
cdrom:x:24:pi
sudo:x:27:pi
audio:x:29:pi
video:x:44:pi
plugdev:x:46:pi
games:x:60:pi
users:x:100:pi
input:x:101:pi
netdev:x:108:pi
pi:x:1000:
spi:x:999:pi
i2c:x:998:pi
gpio:x:997:pi
pi@Pi3B:~$
Code: Select all
pi@Pi3B:~$ id
uid=1000(pi) gid=1000(pi) groups=1000(pi),4(adm),20(dialout),24(cdrom),27(sudo),
29(audio),44(video),46(plugdev),60(games),100(users),101(input),108(netdev),997(
gpio),998(i2c),999(spi)
pi@Pi3B:~$
Could you be a little more specific about where to put the files?spl23 wrote: ↑Mon Aug 21, 2017 10:34 amWe've found a potential cause of the Chromium crashes; there seems to be something wrong in the ffmpeg library which is shipping in this Chromium package, so it looks as if something may have gone wrong when building it.
If anyone would like to try a fix, there are some replacement ffmpeg library files available from https://www.dropbox.com/s/cdpgxfnbp2isy ... e.tgz?dl=0
If someone with the problem could try downloading the file, unpacking it, and copying the files to the relevant locations under /usr/lib, then try the sites which crashed and report back here if it helps or not, that would be very useful!
Found the issue. '82' is the group id of netdev when NOOBS runs, so when bsdtar sees 'netdev', it remaps it. However, within raspbian, the group id is 108.hippy wrote: Yes, via NOOBS install. Only Raspbian installed - Sorry, should have mentioned that!
No problem, and thanks for the explanation.
Code: Select all
pi@Pi3B:~$ ls -l /etc/dhcpcd.conf
-rw-rw-r-- 1 root 82 1630 Jul 17 14:13 /etc/dhcpcd.conf
pi@Pi3B:~$ sudo chown :netdev /etc/dhcpcd.conf
pi@Pi3B:~$ ls -l /etc/dhcpcd.conf
-rw-rw-r-- 1 root netdev 1630 Jul 17 14:13 /etc/dhcpcd.conf
pi@Pi3B:~$
Good to hear about this
Ah, thanks for clearing that up.spl23 wrote: ↑Mon Aug 21, 2017 2:35 pmThe zip contains two files, libffmpeg_chrome.so.60 and neon/vfp/libffmpeg_chrome.so.60. These should both be copied to /usr/lib/arm-linux-gnueabihf, so they should overwrite /usr/lib/arm-linux-gnueabihf/libffmpeg_chrome.so.60 and /usr/lib/arm-linux-gnueabihf/neon/vfp/libffmpeg_chrome.so.60, respectively. Neither needs to be renamed - they just overwrite these two files.
Hmm - it definitely fixes the animations for me. For reference, many of the animations on Reddit in the "GIFs" section are not GIFs at all; they are h.264 video files, and these pass through our hardware acceleration (which animated GIFs don't). These were the files which were causing the problem - actual animated GIFs seem to be fine.Kratos wrote: ↑Mon Aug 21, 2017 4:05 pmAh, thanks for clearing that up.spl23 wrote: ↑Mon Aug 21, 2017 2:35 pmThe zip contains two files, libffmpeg_chrome.so.60 and neon/vfp/libffmpeg_chrome.so.60. These should both be copied to /usr/lib/arm-linux-gnueabihf, so they should overwrite /usr/lib/arm-linux-gnueabihf/libffmpeg_chrome.so.60 and /usr/lib/arm-linux-gnueabihf/neon/vfp/libffmpeg_chrome.so.60, respectively. Neither needs to be renamed - they just overwrite these two files.
Unfortunately, I think I did everything correctly, but it still throws the "Aw, Snap!" page when loading animations.
for me too.Hmm - it definitely fixes the animations for me
Now it does for me as well! I rebooted and haven't had the issue yet.
OK, thanks for confirming - we'll get an official update to the Chromium package out in the near future.
No problem, thanks for the swift solution!
Edited: Still is. Deleted previous content because proven not relevant.
Code: Select all
sudo apt-get update
sudo apt-get upgrade
You need to spot the difference between leading edge upgrades, middle ground upgrades and late upgrades. Being leading edge means you get to find the new bugs, but you get the new function early. Being in the middle is the simple, conservative approach. Being on the late upgrade path costs money - a lot of my day job is working on historic mainframe systems trying to get them upgraded for the latest IBM hardware (when their old kit goes end-of-support). The folks on Wheezy are the ones we need to worry about, I've not looked whether it's possible to go from Wheezy to Stretch in a single hop.