I recommed using Vivaldi (available as AUR package, see https://aur.archlinux.org/packages/vivaldi/).
]]>/usr/bin/opera: line 13: /usr/lib/opera/opera: cannot execute binary file: Exec format error
/usr/bin/opera: line 13: /usr/lib/opera/opera: Success
/usr/bin/opera is a shell script starting /usr/lib/opera/opera with exec.
/usr/lib/opera/opera is 64-bit:
file /usr/lib/opera/opera
/usr/lib/opera/opera: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, stripped
PKGBUILD loads "http://get.geo.opera.com/pub/${pkgname} … _amd64.deb"
http://get.geo.opera.com/pub/opera/desk … .39/linux/ shows no 32-bit binary.
The last 32-bit binary was: http://get.geo.opera.com/pub/opera/desk … 898/linux/
So basically we have two options:
- blacklist it as upstream (the author of Opera) dropped it completely.
- ship an old versoin, but this would contradict the idea of a bleeding-edge distribution IMHO.
Maybe push it to the AUR as an opera32?
]]>(~)-(32 files, 1.3Mb)-> opera
/usr/bin/opera: line 13: /usr/lib/opera/opera: cannot execute binary file: Exec format error
/usr/bin/opera: line 13: /usr/lib/opera/opera: Success
(~)-(32 files, 1.3Mb)-> pacman -Q opera
opera 49.0.2725.34-1
Can someone reproduce the same bug on his/her own machine?
]]>