You are not logged in.
Pages: 1
This problem is fixed - see below.
Last edited by peebee (2019-05-18 11:13:56)
Offline
Possibly related: https://bugs.archlinux32.org/index.php? … task_id=70
Although I guess if your CPU actually has SSE2, then it's a different crash. Does lscpu list sse2 in it's flags at the end?
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
works on 64-bit.
stable or testing/i686: chromium 74.0.3729.131-3.1
stable or testing/pentium4: chromium 74.0.3729.131-3.0
The pentium4 version works fine (on a machine with SSE2), you can also just install
this one packages if your /proc/cpuinfo says you have SSE2.
As mentioned above on i686 it should not segfault but show "Oh Snap" and show
!has.sse2() on the shell (if you start it in a shell, this is)/
Maybe there is something else going on there with a keyring/wallet software, but
without a coredump or stacktrace its hard to tell.
Offline
To be fair it does sound like a different crash. The reporter reports it crashed when loading a specific webpage, not during initialisation which I guess the normal sse2 errors happen in.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
yeah, you're right. I would actually test https and non-https pages, this would be an indicator to openssl/tls.
If it's only login pages, it sounds like a form completion for login credentials or a wallet software. I lately
get annoying popups of wallet software trying to store my passwords, popups I didn't experience before.. :-)
Offline
This problem is fixed - see below.
Last edited by peebee (2019-05-18 11:14:25)
Offline
chromium wouldn't start up, if the linker dependencies would not be satisified. :-)
The Xeon E5450s BTW is a 64-bit machine, see https://ark.intel.com/content/www/us/en … z-fsb.html . :-)
Offline
So it has the sse2 flag but prints aw, snap when running 32-bit chromium. I guess it's possible Intel didn't implement all the 32-bit versions of the sse2 opcodes but did implement the 64-bit ones, but this is the first time I've come across that if that's what it's doing.
To my mind, crashes when logging in could either be cookie troubles or weird javascript hacks that try to eliminate robots/spammers.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Apologies - although dependencies were 'satisfied' they were not fully 'up to date' for some reason - having now updated some of the dependencies chromium-74.0.3729.131-3.2-i686.pkg.tar.xz is now behaving correctly on the 2 problem webpages.
Thanks for help given.
Offline
No apologies needed, glad it works now. :-)
Offline
deleted due to incompetence :-(
Last edited by peebee (2019-05-21 16:18:05)
Offline
What do you mean by "in About"? It looks ok on my end:
$ pacman -Qp /mnt/archlinux32/i686/testing/chromium-74.0.3729.157-1.0-i686.pkg.tar.xz
chromium 74.0.3729.157-1.0
Offline
deleted
Last edited by peebee (2019-05-21 16:17:31)
Offline
Oh dear - how embarassing - my fault again - all is now OK.
Offline
hi, i have updated the system and chromium (pentium4) crashes:
$ chromium
(chromium:703): Gtk-WARNING **: 00:57:35.183: Theme parsing error: gtk.css:9:0: expected '}' after declarations
[735:735:0520/005737.924321:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is egl
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
[902:902:0520/005754.297766:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is egl
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
0372
[946:946:0520/005821.434104:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is egl
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
[974:974:0520/005827.701811:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is disabled
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
[1003:1003:0520/005833.250785:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is disabled
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372Last edited by anabasis (2021-06-28 16:59:30)
Offline
Probably it's best to start a new thread for this request, since this one is marked as [Fixed].
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Pages: 1