[packman] Vivaldi 2.1.1337.51-1.2 does not start in TW any more
Stakanov
stakanov at disroot.org
Tue Sep 28 12:20:12 CEST 2021
In data lunedì 27 settembre 2021 19:33:12 CEST, Carsten Ziepke ha scritto:
> On Mon, 27 Sep 2021 12:07:51 +0200
>
> Stakanov <stakanov at disroot.org> wrote:
> > Vivaldi does not start in TW.
> > Error message from CLI:
> >
> > vivaldi
> > [3792:3806:0927/112725.469759:ERROR:service_manager_context.cc(277)]
> > Attempting to run unsupported native service: /usr/lib64/vivaldi/
> > chrome_renderer.service
> > [3792:3806:0927/112725.470526:ERROR:service_manager_context.cc(277)]
> > Attempting to run unsupported native service: /usr/lib64/vivaldi/
> > chrome_renderer.service
> > [3792:3806:0927/112725.476389:ERROR:service_manager_context.cc(277)]
> > Attempting to run unsupported native service: /usr/lib64/vivaldi/
> > chrome_renderer.service
> > [3792:3806:0927/112725.486099:ERROR:service_manager_context.cc(277)]
> > Attempting to run unsupported native service: /usr/lib64/vivaldi/
> > chrome_renderer.service
> > [3829:3829:0927/112725.549706:ERROR:sandbox_linux.cc(379)]
> > InitializeSandbox() called with multiple threads in process
> > gpu-process. Rilevato trace/breakpoint (core dump creato)
> >
> > latest version of TW.
> >
> > zypper search -s vivaldi
> > Caricamento dati del repository in corso...
> > Lettura dei pacchetti installati in corso...
> >
> > S | Name | Type | Version | Arch |
> > Repository
> > ---+---------+--------------------+-----------------+--------
> > +------------------- i+ | vivaldi | pacchetto |
> > 2.1.1337.51-1.2 | x86_64 | Packman Repository
> > v | vivaldi | pacchetto | 2.1.1337.51-1.2 | i586 |
> > Packman Repository
> >
> > | vivaldi | pacchetto sorgente | 2.1.1337.51-1.2 | noarch |
> >
> > Packman Repository
>
> Hi Stakanov,
>
> don't use this package. The vivaldi version is three years old
> Use instead the package (repo) directly from Vivaldi:
> https://help.vivaldi.com/desktop/install-update/manual-setup-vivaldi-linux-r
> epositories/#ZYpp_OpenSUSE
>
> Bye,
> Carsten
Which bears the question why such a package is still in the repo if
unmantained and outdated.......
Thank you for the solution. Already done.
More information about the Packman
mailing list