Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: finotti on 2020/06/16, 19:44:30
-
This might be a false alarm (maybe it was not an update, or maybe it is just my box), but today after a recent update, I cannot load Gmail in chromium.
It was working this morning, so it must be one of the updates from today. You can see my updates here: https://paste.debian.net/1152376/ (https://paste.debian.net/1152376/) As you can see, chromium itself was not updated (current version is 81.0.4044.92-1), so I am not sure which package might have affected it.
EDIT: Here are the packages that were updated today:
# cat /var/log/dpkg.log | grep 2020-06-16 | grep upgrade
2020-06-16 06:59:51 upgrade pciutils:amd64 1:3.6.4-1 1:3.7.0-1
2020-06-16 06:59:52 upgrade libpci3:amd64 1:3.6.4-1 1:3.7.0-1
2020-06-16 06:59:52 upgrade libpci3:i386 1:3.6.4-1 1:3.7.0-1
2020-06-16 06:59:52 upgrade ucf:all 3.0042 3.0043
2020-06-16 06:59:53 upgrade libavutil56:i386 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:53 upgrade libavutil56:amd64 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:53 upgrade libswresample3:i386 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:54 upgrade libswresample3:amd64 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:54 upgrade libx264-160:i386 4:0.160.3007+git235ce61-dmo1 4:0.160.3009+git4c9b076-dmo1
2020-06-16 06:59:54 upgrade libx264-160:amd64 4:0.160.3007+git235ce61-dmo1 4:0.160.3009+git4c9b076-dmo1
2020-06-16 06:59:55 upgrade libavcodec58:amd64 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:55 upgrade libavcodec58:i386 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:56 upgrade libavformat58:amd64 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:57 upgrade libavresample4:amd64 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:57 upgrade libpostproc55:amd64 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:57 upgrade libswscale5:amd64 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:58 upgrade libavfilter7:amd64 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:58 upgrade libavdevice58:amd64 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:58 upgrade ffmpeg:amd64 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 06:59:59 upgrade ffmpeg-doc:all 10:4.2.3-dmo3 10:4.3-dmo1
2020-06-16 07:00:11 upgrade fonts-font-awesome:all 5.0.10+really4.7.0~dfsg-1 5.0.10+really4.7.0~dfsg-2
2020-06-16 07:00:12 upgrade inxi:all 3.1.01-1-1 3.1.03-1-1
2020-06-16 07:00:12 upgrade jdupes:amd64 1.15.0-1 1.16.0-1
2020-06-16 07:00:12 upgrade kde-config-cron:amd64 4:19.12.1-3 4:20.04.2-1
2020-06-16 07:00:13 upgrade libcmark0.29.0:amd64 0.29.0-3 0.29.0-4
2020-06-16 07:00:13 upgrade libevdocument3-4:amd64 3.36.5-1 3.36.5-2
2020-06-16 07:00:13 upgrade libevview3-3:amd64 3.36.5-1 3.36.5-2
2020-06-16 07:00:14 upgrade libsnappy-jni:amd64 1.1.7.3-1 1.1.7.5-1
2020-06-16 07:00:14 upgrade libsnappy-java:all 1.1.7.3-1 1.1.7.5-1
2020-06-16 07:00:14 upgrade libhtsjdk-java:all 2.18.2+dfsg-2 2.22.0+dfsg-1
2020-06-16 07:00:15 upgrade libmojolicious-perl:all 8.53+dfsg-1 8.54+dfsg-1
2020-06-16 11:54:54 upgrade kdf:amd64 4:19.12.2-1 4:20.04.2-1
2020-06-16 11:54:55 upgrade libjson-c4:amd64 0.13.1+dfsg-7 0.13.1+dfsg-8
2020-06-16 11:54:55 upgrade libpicard-java:amd64 2.18.25+dfsg-3 2.22.8+dfsg-1
2020-06-16 11:54:56 upgrade picard-tools:amd64 2.18.25+dfsg-3 2.22.8+dfsg-1
2020-06-16 11:54:56 upgrade python3-autopep8:all 1.5.2-1 1.5.3-2
I should say I'm running aptosid in this computer:
# inxi -v 3
System: Host: debian Kernel: 5.7.0-1.slh.1-aptosid-amd64 x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: KDE Plasma 5.17.5
Distro: aptosid 2013-01 - kde-full - (201305050307) base: Debian GNU/Linux bullseye/sid
Machine: Type: Desktop System: ASUS product: All Series v: N/A serial: N/A
Mobo: ASUSTeK model: Z87-PRO v: Rev 1.xx serial: 140120922701297 UEFI: American Megatrends v: 2103 date: 08/18/2014
Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:0036 charge: 55% (should be ignored)
status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard PID:0056 charge: 70% (should be ignored)
status: Discharging
Device-3: hidpp_battery_2 model: Logitech M310 charge: 55% (should be ignored) status: Discharging
CPU: Topology: Quad Core model: Intel Core i7-4771 bits: 64 type: MT MCP arch: Haswell rev: 3 L2 cache: 8192 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 55971
Speed: 3498 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 3498 2: 3498 3: 3498 4: 3498 5: 3499 6: 3499 7: 3499
8: 3499
Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel
bus ID: 00:02.0
Display: x11 server: X.Org 1.20.8 driver: intel resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.1.1 direct render: Yes
Network: Device-1: Intel Ethernet I217-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k port: f080 bus ID: 00:19.0
IF: eth0 state: up speed: 100 Mbps duplex: full mac: e0:3f:49:a3:4c:a6
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives: Local Storage: total: 12.06 TiB used: 5.96 TiB (49.4%)
Info: Processes: 346 Uptime: 1h 01m Memory: 31.25 GiB used: 6.86 GiB (22.0%) Init: systemd runlevel: 5 Compilers:
gcc: 9.3.0 Shell: bash v: 5.0.16 inxi: 3.1.03
I could not find any reports so far. If anyone has any ideas (besides using another browser), I'm all ears.
-
Hi finotti -- here I have SRWare Iron, Version 81.0.4200.0 (Developer Build) custom (64-bit). All other packages are fully updated.
There is no problem with gmail.
-
I don't use Chromium and gave up on all browsers with that base due to overhead, but I just fired up Google Chrome and logged into Gmail with no problem. Looks like they changed the appearance. Looks a lot like the droid app now. Been a while since I actually logged in to gmail itself via browser.
Also just dist-upgraded this afternoon.
This likely doesn't help your situation though. Just an FYI.
-
I don't use Chromium and gave up on all browsers with that base due to overhead, but I just fired up Google Chrome and logged into Gmail with no problem. Looks like they changed the appearance. Looks a lot like the droid app now. Been a while since I actually logged in to gmail itself via browser.
Also just dist-upgraded this afternoon.
This likely doesn't help your situation though. Just an FYI.
Thanks! That does help, as it probably means it is something on my setup, so I probably need to investigate instead of waiting for a fix upstream. I appreciate you taking the time to check!
-
A different profile and different user does not work either. Here is the messages I get in konsole:
$ /usr/bin/chromium --user-data-dir=/home/finotti/.config/chromium-test/
[58458:58458:0616/193456.165082:ERROR:browser_switcher_service.cc(238)] XXX Init()
[58500:58500:0616/193456.233263:ERROR:vaapi_wrapper.cc(482)] vaInitialize failed: unknown libva error
[58500:58500:0616/193456.244831:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
Received signal 11 SEGV_MAPERR 000000000090
#0 0x5629624185a9 (/usr/lib/chromium/chromium+0x52485a8)
#1 0x56296237dac3 (/usr/lib/chromium/chromium+0x51adac2)
#2 0x562962418131 (/usr/lib/chromium/chromium+0x5248130)
#3 0x7f7df3f9a110 (/lib/x86_64-linux-gnu/libpthread-2.30.so+0x1410f)
#4 0x56296028f2a7 (/usr/lib/chromium/chromium+0x30bf2a6)
#5 0x56296028a2f9 (/usr/lib/chromium/chromium+0x30ba2f8)
#6 0x5629601e60fb (/usr/lib/chromium/chromium+0x30160fa)
#7 0x5629601eb4c0 (/usr/lib/chromium/chromium+0x301b4bf)
#8 0x5629601eea29 (/usr/lib/chromium/chromium+0x301ea28)
#9 0x5629601ee839 (/usr/lib/chromium/chromium+0x301e838)
#10 0x5629601eeb64 (/usr/lib/chromium/chromium+0x301eb63)
#11 0x5629601e5e1e (/usr/lib/chromium/chromium+0x3015e1d)
#12 0x5629601ec9cf (/usr/lib/chromium/chromium+0x301c9ce)
#13 0x5629623c8442 (/usr/lib/chromium/chromium+0x51f8441)
#14 0x5629623d8139 (/usr/lib/chromium/chromium+0x5208138)
#15 0x5629623d7ed5 (/usr/lib/chromium/chromium+0x5207ed4)
#16 0x562962393daa (/usr/lib/chromium/chromium+0x51c3da9)
#17 0x5629623d89e9 (/usr/lib/chromium/chromium+0x52089e8)
#18 0x5629623b0c84 (/usr/lib/chromium/chromium+0x51e0c83)
#19 0x5629623ecaa9 (/usr/lib/chromium/chromium+0x521caa8)
#20 0x56296242846e (/usr/lib/chromium/chromium+0x525846d)
#21 0x7f7df3f8ef27 start_thread
#22 0x7f7def01431f clone
r8: 000056296028f310 r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000246
r12: 00007f7dd8041250 r13: 0000562968b43e00 r14: 00007f7da0028940 r15: 00007f7da000a6a0
di: 00007f7da0028940 si: 0000000000008000 bp: 00007f7d9f8629e0 bx: 000056296a4779b0
dx: 0000000000000000 ax: 0000000000000001 cx: 0000000000000000 sp: 00007f7d9f8629c0
ip: 000056296028f2a7 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000006
trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000090
[end of stack trace]
Calling _exit(1). Core file will not be generated.
It seems related to libva...
]# vainfo
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
-
Probably this.
critical bugs of ffmpeg (→ ) <Outstanding>
b1 - #963035 - ffmpeg: 4.3 breaks chromium
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963035 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963035)
-
Probably this.
critical bugs of ffmpeg (→ ) <Outstanding>
b1 - #963035 - ffmpeg: 4.3 breaks chromium
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963035 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963035)
Ah, you are correct! With the new ffmpeg that came today, the bug is gone. (I should say I'm using DMO, but I assume the fix has probably hit the official Debian repositories.)
-
Well, looks like ffmpeg and chromium both need patching to fully solve the issue from both ends. The Debian bug report was reassigned to chromium.
It crashed just now with Gmail open. Can't upgrade ffmpeg at the moment as it removes chromium.
chromium/unstable,now 83.0.4103.116-1 amd64 [installed]
ffmpeg/now 7:4.2.2-3 amd64 [installed,upgradable to: 7:4.3-2]
-
it crasches also with youtubestudio. We just have to wait a little :)
-
@finotti
It's why I use dmo, debian lags behind constantly, and I love expressing the idea, especially on irc, you can actually see peoples faces turn red because they are mad that you chose to use it, it's awesome.
Don't believe the debian bullshit about dmo, it's all politics
What most people don't know is that dmo is a debian developer
They will censor you on irc, it's fucking funny, debian is a embarrassment to linux period. codes of conduct, renaming packages, it's like what are we kindergardners
Offended this is how weak people are now a days and a very sad excuse for LIFE
my rant is over
Ian Ashley Murdock is rolling in his grave at what debian has become