DietPi-Software | Chromium: Newest version fails on Tinkerboard

[stogoh]

Creating a bug report/issue:

Required Information:

• Distro version | 9.6
• Kernel version | Linux DietPi 4.4.103+ Fix warning when running scp over openssh-server #1 SMP Fri Jun 22 16:14:49 CST 2018 armv7l GNU/Linux
• SBC device | Asus Tinker Board (armv7l)
• Power supply used | 5V 3A
• SDcard used | SanDisk ultra 16GB

Additional Information (if applicable):

• Software title | Chromium
• The software is a fresh install
• The issure occurs also after reinstall
• ReportID: d5560227-5006-460e-b79c-632b96af2e01

Steps to reproduce:

Running sudo chromium --no-sandbox or chromium browser

Expected behaviour:

The chromium brower should start

Actual behaviour:

The browser shows up for a short time, but then closed immediately.

Extra details:

Console output

[4557:4557:1127/200750.582342:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-proce$
[4521:4734:1127/200750.597713:ERROR:bus.cc(394)] Failed to connect to the bus: Could not parse server address: Unknown address t$
Received signal 11 SEGV_MAPERR 000000000000
#0 0x000080f1ebf0 <unknown>
#1 0x000080eab300 <unknown>
#2 0x000080f1eee2 <unknown>
#3 0x000080f1f124 <unknown>
#4 0x0000b2cb4fe0 <unknown>
#5 0x00007fc53fe0 <unknown>
#6 0x00008119cc94 <unknown>
#7 0x000081559916 <unknown>
#8 0x000081e4f6dc <unknown>
#9 0x000081e4f7a8 <unknown>
#10 0x000081e4f87c <unknown>
#11 0x000081e4f904 <unknown>
#12 0x000081e4f936 <unknown>
#13 0x000080df3c88 <unknown>
#14 0x000080df3cc2 <unknown>
#15 0x000080ca7cc0 <unknown>
#16 0x000080cabd14 <unknown>
#17 0x000080cabf82 <unknown>
#18 0x0000800e4ad6 <unknown>
#19 0x000080328836 <unknown>
#20 0x0000800eb182 <unknown>
#21 0x0000800eb66a <unknown>
#22 0x0000800e6776 <unknown>
#23 0x000080c8ae74 <unknown>
#24 0x000080c8b69a <unknown>
#25 0x000080c8fffe <unknown>
#26 0x000080c8ac78 <unknown>
#27 0x00007fad8190 ChromeMain
#28 0x0000b2ca64aa __libc_start_main
[end of stack trace]
Calling _exit(1). Core file will not be generated.

[MichaIng]

@stogoh
Thanks for your report. We will investigate.

[stogoh]

@MichaIng
Sidenote
I had the same problem with TinkerOS after sudo apt-get upgrade. But when I just use the image which is online and not update it, then chromium is working. Maybe some package is getting updated and then does not work anymore.

[MichaIng]

Thanks for the info. So we need to check which version still works, what changed and what we need to adjust e.g. in xorg.conf to get it running again.

[Fourdee]

@stogoh

Looks like an issue with GPU accell, as a workaround for now, try disabling the glamor driver:

mv /etc/X11/xorg.conf.d/20-modesetting.conf /etc/X11/xorg.conf.d/20-modesetting.conf.disable

[stogoh]

I have now disabled the driver, but now it fails to initialize xserver. So I‘m suck in the console right now.

[Fourdee]

@stogoh

Updating our TinkerOS image, i'll take a look in the next hour or two.

[Fourdee]

Confirmed issue: https://tinkerboarding.co.uk/forum/archive/index.php/thread-1735.html

@stogoh
To return X back to working state:

mv /etc/X11/xorg.conf.d/20-modesetting.conf* /etc/X11/xorg.conf.d/20-modesetting.conf

[Fourdee]

Still occurs with v67...

wget https://snapshot.debian.org/archive/debian-security/20180701T015633Z/pool/updates/main/c/chromium-browser/chromium_67.0.3396.87-1~deb9u1_armhf.deb
dpkg -i *.deb
rm *.deb

Same with egl flag removed.

[Fourdee]

Note to self:

• Image updated to mainline (in testing folder)
• midgard driver with EGL support
• Confirmed Kodi support
• Confirmed Chromium under autostart support
• Do not release until v6.19 is live, due to dev prep'ed and desktop changes

ref: Fourdee@fc823eb

[stogoh]

Well. I just updated to the newest version of DietPi and the problem returns again.

[MichaIng]

@Fourdee
The new images are in place, if I see right? If still an issue with current Chromium, is there something we can do about running systems? Any chance to update them to mainline kernel on dietpi-update? I guess too risky and might break custom setups that depend on current kernel. So at least should be only optional...

[MichaIng]

I guess the issue has been resolved with the new images. I mark this as closed for now, but feel free to reopen if required.

If this is really kernel related, I see no chance that we can automate a fix via update. This has to be done manually to assure no unexpected issues occur, or, at best flash the new image.

[MichaIng]

@stogoh
Could you please try out the following:

cd /tmp
wget https://dietpi.com/downloads/binaries/asus/testing/ASUSTB_GPU.7z
7zr x ASUSTB_GPU.7z
rm ASUSTB_GPU.7z
apt-mark unhold xserver-common xserver-xorg-core
dpkg -i *.deb
G_AGF
apt-mark hold xserver-common xserver-xorg-core

[stogoh]

@stogoh
Could you please try out the following:

cd /tmp
wget https://dietpi.com/downloads/binaries/asus/testing/ASUSTB_GPU.7z
7zr x ASUSTB_GPU.7z
rm ASUSTB_GPU.7z
apt-mark unhold xserver-common xserver-xorg-core
dpkg -i *.deb
G_AGF
apt-mark hold xserver-common xserver-xorg-core

@MichaIng
I've done it. Chromium is still working.

BTW: I had to enter G_SUDO before executing G_AGF

[MichaIng]

@stogoh

I've done it. Chromium is still working.

Good so far, would be great if you could test it with the new(est) Chromium version.

BTW: I had to enter G_SUDO before executing G_AGF

Jep expected of course 🙂.

[stogoh]

Well. I updated chromium from version 67.0.3396.87 to 72.0.3626.122 and it's not working again. Chromium just flashes white for a bit. I've also executed G_AGF command again. Still not working.

[MichaIng]

@stogoh
To verify image and kernel version:

cat /etc/armbian_version
uname -a

I've also executed G_AGF command again. Still not working.

This is btw just to let APT automatically install dependency packages after using dpkg -i to install packages manually.

[stogoh]

"Uname -a" outputs:

Linux Barfritz 4.4.103+ #1 SMP Fri Jun 22 16:14:49 CST 2018 armv7l GNU/Linux

[MichaIng]

@stogoh
Ah it looks like you use an old TinkerOS based image. The new one is based on ARMbian which ships a new mainline based kernel, which might have the required support, not sure. Sadly AFAIK it is not possible or at least difficult to migrate to ARMbian kernel + bootloader basis, so either you need to reflash or of course stay with the older Chromium version, which should not be that bad.

But I will keep the issue open to see if other ATB users with the new image run into the same issue.

Thanks for testing the new graphics+xorg packages btw. which do not solve the issue sadly but do not hurt as well and ship a slightly enhanced media feature support + newer library versions.

[MichaIng]

I mark this issue as closed. New Buster image is up. Tester required for GPU acceleration support: #3094