• Browser
  • Mail
  • News
  • Community
  • About
Register Login
HomeBlogsForumThemesContributeSocial

Vivaldi

  • Browser
  • Mail
  • News
  • Community
  • About

Navigation

    • Home
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    We will be doing maintenance work on Vivaldi Translate on the 11th of May starting at 03:00 (UTC) (see the time in your time zone).
    Some downtime and service disruptions may be experienced.
    Thanks in advance for your patience.

    1. Home
    2. Desktop
    3. Vivaldi for Linux
    4. Vivaldi Won't Start After Update

    Vivaldi Won't Start After Update

    Vivaldi for Linux
    3
    17
    545
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Felemur
      F
      Felemur
      last edited by

      A friends Dell computer running the latest Mint Cinnamon with all updates won't start Vivaldi browser after the Vivaldi Update yesterday. Click on the Vivaldi V icon, and you see a small wheel spin for a few seconds, then nothing.

      I have almost the same computer, with the same Mint Cinnamon at the same state of updates and I have no problem.

      Was going to re-install, but my friend does not want to lose speed dials and other settings.

      Any thoughts?

      DoctorG
      D
      1 Reply Last reply
      Reply Quote 0
      • DoctorG
        D
        DoctorG Soprano @Felemur
        last edited by DoctorG

        @Felemur Some more information would be useful.
        In Shell start:
        inxi

        Perhaps a graphics driver issue?
        Tell output of
        inxi -Gxxx

        What happens if started in shell:
        vivaldi
        and if t hat fails to start:
        vivaldi --disable-gpu

        If that does not help, just for a check try to start with a temporary test profile.
        vivaldi --user-data-dir="/tmp/TESTVIV"

        _bug hunter · Volunteer helper · Sopranos tester · Language DE,EN · ♀👵
        Known old dragon lady: Gwen aka Dr. Gwen Agon aka GwenDragon aka DoctorGTesting


        Linux Debian 12 KDE X11 / Windows 11 Pro
        Intel i5-7400 / NVidia GT 710

        1 Reply Last reply Reply Quote 0
        • Felemur
          F
          Felemur
          last edited by

          OK, will do that. Will get back ASAP.

          @DoctorG said in Vivaldi Won't Start After Update:

          In Shell start:
          inxi
          Perhaps a graphics driver issue?
          Tell output of
          inxi -Gxxx
          What happens if started in shell:
          vivaldi
          and if t hat fails to start:
          vivaldi --disable-gpu
          If that does not help, just for a check try to start with a temporary test profile.
          vivaldi --user-data-dir="/tmp/TESTVIV"

          1 Reply Last reply Reply Quote 1
          • Felemur
            F
            Felemur
            last edited by

            Here are the results:

            pamela@pamela-Latitude-E7440:~$ inxi
            CPU: Dual Core Intel Core i5-4310U (-MT MCP-)
            speed/min/max: 798/800/3000 MHz Kernel: 5.4.0-124-generic x86_64 Up: 1h 16m
            Mem: 1979.9/7863.3 MiB (25.2%) Storage: 223.57 GiB (37.3% used) Procs: 231
            Shell: bash 5.0.17 inxi: 3.0.38


            pamela@pamela-Latitude-E7440:~$ inxi -Gxxx
            Graphics:
            Device-1: Intel Haswell-ULT Integrated Graphics vendor: Dell driver: i915
            v: kernel bus ID: 00:02.0 chip ID: 8086:0a16
            Display: x11 server: X.Org 1.20.13 driver: modesetting
            unloaded: fbdev,vesa resolution: 1366x768~60Hz
            OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2)
            v: 4.5 Mesa 21.2.6 compat-v: 3.0 direct render: Yes


            pamela@pamela-Latitude-E7440:~$ vivaldi
            Bus error (core dumped)


            pamela@pamela-Latitude-E7440:~$ vivaldi --disable-gpu
            Bus error (core dumped)


            pamela@pamela-Latitude-E7440:~$ vivaldi --user-data-dir="/tmp/TESTVIV"
            Bus error (core dumped)

            DoctorG
            D
            1 Reply Last reply
            Reply Quote 0
            • DoctorG
              D
              DoctorG Soprano @Felemur
              last edited by DoctorG

              @Felemur I have same kernel, but no Intel GPU, no bus error and crash.

              On your PC any entry in /var/log/syslog at time of crash?

              _bug hunter · Volunteer helper · Sopranos tester · Language DE,EN · ♀👵
              Known old dragon lady: Gwen aka Dr. Gwen Agon aka GwenDragon aka DoctorGTesting


              Linux Debian 12 KDE X11 / Windows 11 Pro
              Intel i5-7400 / NVidia GT 710

              1 Reply Last reply Reply Quote 0
              • Felemur
                F
                Felemur
                last edited by

                @DoctorG said in Vivaldi Won't Start After Update:

                I have same kernel, but no Intel GPU, no bus error and crash.
                On your PC any entry in /var/log/syslog at time of crash?

                This is a bit beyond my skill level, but I looked through the file and spoke with her when she tried to start Vivaldi, and this seems to be the first of a long set of entries about Vivaldi in the syslog for today's date. I copied the first few lines and pasted below.

                
                Aug 11 05:52:52 pamela-Latitude-E7440 systemd[1]: [email protected]: Succeeded.
                Aug 11 05:52:52 pamela-Latitude-E7440 systemd-coredump[1896]: Process 1887 (vivaldi-bin) of user 1000 dumped core.#012#012Stack trace of thread 1887:#012#0  0x00007fc477c1a5d3 memset (ld-linux-x86-64.so.2 + 0x235d3)#012#1  0x00007fc477bfe429 _dl_map_segments (ld-linux-x86-64.so.2 + 0x7429)#012#2  0x00007fc477c0161b _dl_map_object (ld-linux-x86-64.so.2 + 0xa61b)#012#3  0x00007fc477bf82e9 map_doit (ld-linux-x86-64.so.2 + 0x12e9)#012#4  0x00007fc477c14cba _dl_catch_exception (ld-linux-x86-64.so.2 + 0x1dcba)#012#5  0x00007fc477c14d63 _dl_catch_error (ld-linux-x86-64.so.2 + 0x1dd63)#012#6  0x00007fc477bf94e0 do_preload (ld-linux-x86-64.so.2 + 0x24e0)#012#7  0x00007fc477bfd1cf dl_main (ld-linux-x86-64.so.2 + 0x61cf)#012#8  0x00007fc477c13c4b _dl_sysdep_start (ld-linux-x86-64.so.2 + 0x1cc4b)#012#9  0x00007fc477bf904c _dl_start_final (ld-linux-x86-64.so.2 + 0x204c)#012#10 0x00007fc477bf8108 _start (ld-linux-x86-64.so.2 + 0x1108)
                Aug 11 05:52:52 pamela-Latitude-E7440 systemd[1]: [email protected]: Succeeded.
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: Started Process Core Dump (PID 1971/UID 0).
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: Started Process Core Dump (PID 1972/UID 0).
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: Started Process Core Dump (PID 1973/UID 0).
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd-coredump[1974]: Process 1969 (cat) of user 1000 dumped core.#012#012Stack trace of thread 1969:#012#0  0x00007f34127d05d3 memset (ld-linux-x86-64.so.2 + 0x235d3)#012#1  0x00007f34127b4429 _dl_map_segments (ld-linux-x86-64.so.2 + 0x7429)#012#2  0x00007f34127b761b _dl_map_object (ld-linux-x86-64.so.2 + 0xa61b)#012#3  0x00007f34127ae2e9 map_doit (ld-linux-x86-64.so.2 + 0x12e9)#012#4  0x00007f34127cacba _dl_catch_exception (ld-linux-x86-64.so.2 + 0x1dcba)#012#5  0x00007f34127cad63 _dl_catch_error (ld-linux-x86-64.so.2 + 0x1dd63)#012#6  0x00007f34127af4e0 do_preload (ld-linux-x86-64.so.2 + 0x24e0)#012#7  0x00007f34127b31cf dl_main (ld-linux-x86-64.so.2 + 0x61cf)#012#8  0x00007f34127c9c4b _dl_sysdep_start (ld-linux-x86-64.so.2 + 0x1cc4b)#012#9  0x00007f34127af04c _dl_start_final (ld-linux-x86-64.so.2 + 0x204c)#012#10 0x00007f34127ae108 _start (ld-linux-x86-64.so.2 + 0x1108)
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: [email protected]: Succeeded.
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd-coredump[1996]: Process 1970 (cat) of user 1000 dumped core.#012#012Stack trace of thread 1970:#012#0  0x00007f47dc7445d3 memset (ld-linux-x86-64.so.2 + 0x235d3)#012#1  0x00007f47dc728429 _dl_map_segments (ld-linux-x86-64.so.2 + 0x7429)#012#2  0x00007f47dc72b61b _dl_map_object (ld-linux-x86-64.so.2 + 0xa61b)#012#3  0x00007f47dc7222e9 map_doit (ld-linux-x86-64.so.2 + 0x12e9)#012#4  0x00007f47dc73ecba _dl_catch_exception (ld-linux-x86-64.so.2 + 0x1dcba)#012#5  0x00007f47dc73ed63 _dl_catch_error (ld-linux-x86-64.so.2 + 0x1dd63)#012#6  0x00007f47dc7234e0 do_preload (ld-linux-x86-64.so.2 + 0x24e0)#012#7  0x00007f47dc7271cf dl_main (ld-linux-x86-64.so.2 + 0x61cf)#012#8  0x00007f47dc73dc4b _dl_sysdep_start (ld-linux-x86-64.so.2 + 0x1cc4b)#012#9  0x00007f47dc72304c _dl_start_final (ld-linux-x86-64.so.2 + 0x204c)#012#10 0x00007f47dc722108 _start (ld-linux-x86-64.so.2 + 0x1108)
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: [email protected]: Succeeded.
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd-coredump[1975]: Process 1965 (vivaldi-bin) of user 1000 dumped core.#012#012Stack trace of thread 1965:#012#0  0x00007fb768f765d3 memset (ld-linux-x86-64.so.2 + 0x235d3)#012#1  0x00007fb768f5a429 _dl_map_segments (ld-linux-x86-64.so.2 + 0x7429)#012#2  0x00007fb768f5d61b _dl_map_object (ld-linux-x86-64.so.2 + 0xa61b)#012#3  0x00007fb768f542e9 map_doit (ld-linux-x86-64.so.2 + 0x12e9)#012#4  0x00007fb768f70cba _dl_catch_exception (ld-linux-x86-64.so.2 + 0x1dcba)#012#5  0x00007fb768f70d63 _dl_catch_error (ld-linux-x86-64.so.2 + 0x1dd63)#012#6  0x00007fb768f554e0 do_preload (ld-linux-x86-64.so.2 + 0x24e0)#012#7  0x00007fb768f591cf dl_main (ld-linux-x86-64.so.2 + 0x61cf)#012#8  0x00007fb768f6fc4b _dl_sysdep_start (ld-linux-x86-64.so.2 + 0x1cc4b)#012#9  0x00007fb768f5504c _dl_start_final (ld-linux-x86-64.so.2 + 0x204c)#012#10 0x00007fb768f54108 _start (ld-linux-x86-64.so.2 + 0x1108)
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: [email protected]: Succeeded.
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: Started Process Core Dump (PID 2022/UID 0).
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: Started Process Core Dump (PID 2023/UID 0).
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: Started Process Core Dump (PID 2021/UID 0).
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd-coredump[2025]: Process 2020 (cat) of user 1000 dumped core.#012#012Stack trace of thread 2020:#012#0  0x00007ff2b30c05d3 memset (ld-linux-x86-64.so.2 + 0x235d3)#012#1  0x00007ff2b30a4429 _dl_map_segments (ld-linux-x86-64.so.2 + 0x7429)#012#2  0x00007ff2b30a761b _dl_map_object (ld-linux-x86-64.so.2 + 0xa61b)#012#3  0x00007ff2b309e2e9 map_doit (ld-linux-x86-64.so.2 + 0x12e9)#012#4  0x00007ff2b30bacba _dl_catch_exception (ld-linux-x86-64.so.2 + 0x1dcba)#012#5  0x00007ff2b30bad63 _dl_catch_error (ld-linux-x86-64.so.2 + 0x1dd63)#012#6  0x00007ff2b309f4e0 do_preload (ld-linux-x86-64.so.2 + 0x24e0)#012#7  0x00007ff2b30a31cf dl_main (ld-linux-x86-64.so.2 + 0x61cf)#012#8  0x00007ff2b30b9c4b _dl_sysdep_start (ld-linux-x86-64.so.2 + 0x1cc4b)#012#9  0x00007ff2b309f04c _dl_start_final (ld-linux-x86-64.so.2 + 0x204c)#012#10 0x00007ff2b309e108 _start (ld-linux-x86-64.so.2 + 0x1108)
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: [email protected]: Succeeded.
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd-coredump[2027]: Process 2019 (cat) of user 1000 dumped core.#012#012Stack trace of thread 2019:#012#0  0x00007f6f534e85d3 memset (ld-linux-x86-64.so.2 + 0x235d3)#012#1  0x00007f6f534cc429 _dl_map_segments (ld-linux-x86-64.so.2 + 0x7429)#012#2  0x00007f6f534cf61b _dl_map_object (ld-linux-x86-64.so.2 + 0xa61b)#012#3  0x00007f6f534c62e9 map_doit (ld-linux-x86-64.so.2 + 0x12e9)#012#4  0x00007f6f534e2cba _dl_catch_exception (ld-linux-x86-64.so.2 + 0x1dcba)#012#5  0x00007f6f534e2d63 _dl_catch_error (ld-linux-x86-64.so.2 + 0x1dd63)#012#6  0x00007f6f534c74e0 do_preload (ld-linux-x86-64.so.2 + 0x24e0)#012#7  0x00007f6f534cb1cf dl_main (ld-linux-x86-64.so.2 + 0x61cf)#012#8  0x00007f6f534e1c4b _dl_sysdep_start (ld-linux-x86-64.so.2 + 0x1cc4b)#012#9  0x00007f6f534c704c _dl_start_final (ld-linux-x86-64.so.2 + 0x204c)#012#10 0x00007f6f534c6108 _start (ld-linux-x86-64.so.2 + 0x1108)
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: [email protected]: Succeeded.
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd-coredump[2024]: Process 2016 (vivaldi-bin) of user 1000 dumped core.#012#012Stack trace of thread 2016:#012#0  0x00007f8330c8b5d3 memset (ld-linux-x86-64.so.2 + 0x235d3)#012#1  0x00007f8330c6f429 _dl_map_segments (ld-linux-x86-64.so.2 + 0x7429)#012#2  0x00007f8330c7261b _dl_map_object (ld-linux-x86-64.so.2 + 0xa61b)#012#3  0x00007f8330c692e9 map_doit (ld-linux-x86-64.so.2 + 0x12e9)#012#4  0x00007f8330c85cba _dl_catch_exception (ld-linux-x86-64.so.2 + 0x1dcba)#012#5  0x00007f8330c85d63 _dl_catch_error (ld-linux-x86-64.so.2 + 0x1dd63)#012#6  0x00007f8330c6a4e0 do_preload (ld-linux-x86-64.so.2 + 0x24e0)#012#7  0x00007f8330c6e1cf dl_main (ld-linux-x86-64.so.2 + 0x61cf)#012#8  0x00007f8330c84c4b _dl_sysdep_start (ld-linux-x86-64.so.2 + 0x1cc4b)#012#9  0x00007f8330c6a04c _dl_start_final (ld-linux-x86-64.so.2 + 0x204c)#012#10 0x00007f8330c69108 _start (ld-linux-x86-64.so.2 + 0x1108)
                Aug 11 05:53:18 pamela-Latitude-E7440 systemd[1]: [email protected]: Succeeded.
                Aug 11 05:53:50 pamela-Latitude-E7440 systemd[1]: Started Process Core Dump (PID 2052/UID 0).
                Aug 11 05:53:50 pamela-Latitude-E7440 systemd[1]: Started Process Core Dump (PID 2051/UID 0).
                Aug 11 05:53:50 pamela-Latitude-E7440 systemd[1]: Started Process Core Dump (PID 2053/UID 0).
                Aug 11 05:53:50 pamela-Latitude-E7440 systemd-coredump[2058]: Process 2049 (cat) of user 1000 dumped core.#012#012Stack trace of thread 2049:#012#0  0x00007f5f616265d3 memset (ld-linux-x86-64.so.2 + 0x235d3)#012#1  0x00007f5f6160a429 _dl_map_segments (ld-linux-x86-64.so.2 + 0x7429)#012#2  0x00007f5f6160d61b _dl_map_object (ld-linux-x86-64.so.2 + 0xa61b)#012#3  0x00007f5f616042e9 map_doit (ld-linux-x86-64.so.2 + 0x12e9)#012#4  0x00007f5f61620cba _dl_catch_exception (ld-linux-x86-64.so.2 + 0x1dcba)#012#5  0x00007f5f61620d63 _dl_catch_error (ld-linux-x86-64.so.2 + 0x1dd63)#012#6  0x00007f5f616054e0 do_preload (ld-linux-x86-64.so.2 + 0x24e0)#012#7  0x00007f5f616091cf dl_main (ld-linux-x86-64.so.2 + 0x61cf)#012#8  0x00007f5f6161fc4b _dl_sysdep_start (ld-linux-x86-64.so.2 + 0x1cc4b)#012#9  0x00007f5f6160504c _dl_start_final (ld-linux-x86-64.so.2 + 0x204c)#012#10 0x00007f5f61604108 _start (ld-linux-x86-64.so.2 + 0x1108)
                Aug 11 05:53:50 pamela-Latitude-E7440 systemd[1]: [email protected]: Succeeded.
                Aug 11 05:53:50 pamela-Latitude-E7440 systemd-coredump[2070]: Process 2050 (cat) of user 1000 dumped core.#012#012Stack trace of thread 2050:#012#0  0x00007fc46acd55d3 memset (ld-linux-x86-64.so.2 + 0x235d3)#012#1  0x00007fc46acb9429 _dl_map_segments (ld-linux-x86-64.so.2 + 0x7429)#012#2  0x00007fc46acbc61b _dl_map_object (ld-linux-x86-64.so.2 + 0xa61b)#012#3  0x00007fc46acb32e9 map_doit (ld-linux-x86-64.so.2 + 0x12e9)#012#4  0x00007fc46accfcba _dl_catch_exception (ld-linux-x86-64.so.2 + 0x1dcba)#012#5  0x00007fc46accfd63 _dl_catch_error (ld-linux-x86-64.so.2 + 0x1dd63)#012#6  0x00007fc46acb44e0 do_preload (ld-linux-x86-64.so.2 + 0x24e0)#012#7  0x00007fc46acb81cf dl_main (ld-linux-x86-64.so.2 + 0x61cf)#012#8  0x00007fc46accec4b _dl_sysdep_start (ld-linux-x86-64.so.2 + 0x1cc4b)#012#9  0x00007fc46acb404c _dl_start_final (ld-linux-x86-64.so.2 + 0x204c)#012#10 0x00007fc46acb3108 _start (ld-linux-x86-64.so.2 + 0x1108)
                Aug 11 05:53:50 pamela-Latitude-E7440 systemd[1]: [email protected]: Succeeded.
                
                DoctorG
                D
                1 Reply Last reply
                Reply Quote 0
                • DoctorG
                  D
                  DoctorG Soprano @Felemur
                  last edited by DoctorG

                  @Felemur Debugging this is out of knowldege for me, too!

                  Can save that log in a text file, report crash to Vivaldi tracker and send the the file? And do not forget to copy information from https://forum.vivaldi.net/post/603833 and send them?

                  I hope our Linux dev will find the issue.

                  _bug hunter · Volunteer helper · Sopranos tester · Language DE,EN · ♀👵
                  Known old dragon lady: Gwen aka Dr. Gwen Agon aka GwenDragon aka DoctorGTesting


                  Linux Debian 12 KDE X11 / Windows 11 Pro
                  Intel i5-7400 / NVidia GT 710

                  1 Reply Last reply Reply Quote 0
                  • Felemur
                    F
                    Felemur
                    last edited by

                    OK, I will do that. Thanks.

                    Is there a way I can save her settings (speed dials, history, etc) and re-install Vivaldi so she can get back to work using it? She is able to use Firefox, but she is used to Vivaldi and works from home.

                    DoctorG
                    D
                    1 Reply Last reply
                    Reply Quote 1
                    • DoctorG
                      D
                      DoctorG Soprano @Felemur
                      last edited by

                      @Felemur uninstalling Vivaldi is not a problem, and she will not lose settings and browser data.

                      _bug hunter · Volunteer helper · Sopranos tester · Language DE,EN · ♀👵
                      Known old dragon lady: Gwen aka Dr. Gwen Agon aka GwenDragon aka DoctorGTesting


                      Linux Debian 12 KDE X11 / Windows 11 Pro
                      Intel i5-7400 / NVidia GT 710

                      1 Reply Last reply Reply Quote 0
                      • Felemur
                        F
                        Felemur
                        last edited by

                        OK, thank you for your help today. Bug report has been submitted.

                        DoctorG
                        D
                        1 Reply Last reply
                        Reply Quote 1
                        • DoctorG
                          D
                          DoctorG Soprano @Felemur
                          last edited by

                          @Felemur I try to ping a Linux dev. Please wait until tomorrow or some more days.

                          _bug hunter · Volunteer helper · Sopranos tester · Language DE,EN · ♀👵
                          Known old dragon lady: Gwen aka Dr. Gwen Agon aka GwenDragon aka DoctorGTesting


                          Linux Debian 12 KDE X11 / Windows 11 Pro
                          Intel i5-7400 / NVidia GT 710

                          1 Reply Last reply Reply Quote 0
                          • Felemur
                            F
                            Felemur
                            last edited by

                            BTW, I uninstalled, then reinstalled Vivaldi through the synaptic package manager, and it works great again + all the speed dials, history, etc. is there and working well.

                            Really appreciate your help.

                            Unrelated, but I was checking to see how long I've been here, and this November it will be 7 years. Wow, that went fast. Everyone I've managed to switch to Vivaldi ends up thanking me after a while.

                            1 Reply Last reply Reply Quote 0
                            • B
                              bVgBmfGe2bsRsA
                              last edited by

                              I'm seeing this too on Fedora 36. I just updated to Vivaldi 5.4.2753.28 today from the official repo / rpm package, now it core dumps on start. Launching with --disable-gpu or --user-data-dir parameters doesn't help. It looks like there's some kind of problem with what the shell script launcher at /opt/vivaldi/vivaldi is doing. If instead you launch /opt/vivaldi/vivaldi-bin it will start up.

                              [foo@Z840 vivaldi-testing]$ inxi
                              CPU: 2x 14-core Intel Xeon E5-2690 v4 (-MT MCP SMP-)
                              speed/min/max: 1273/1200/3500 MHz Kernel: 5.18.16-200.fc36.x86_64 x86_64
                              Up: 2h 19m Mem: 7516.8/257839.5 MiB (2.9%) Storage: 1.82 TiB (9.2% used)
                              Procs: 753 Shell: Bash inxi: 3.3.19
                              
                              [foo@Z840 vivaldi-testing]$ inxi -Gxxx
                              Graphics:
                                Device-1: NVIDIA GP106GL [Quadro P2000] driver: nvidia v: 515.65.01
                                  arch: Pascal pcie: speed: 8 GT/s lanes: 16 ports: active: none
                                  off: DP-1,DP-3,DP-4 empty: DP-2 bus-ID: 04:00.0 chip-ID: 10de:1c30
                                  class-ID: 0300
                                Device-2: Logitech Logitech Webcam C925e type: USB
                                  driver: snd-usb-audio,uvcvideo bus-ID: 3-3.2:6 chip-ID: 046d:085b
                                  class-ID: 0102 serial: A6AF0AEF
                                Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3
                                  compositor: kwin_x11 driver: X: loaded: nvidia
                                  unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
                                  gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
                                Screen-1: 0 s-res: 7680x1440 s-dpi: 108 s-size: 1806x342mm (71.10x13.46")
                                  s-diag: 1838mm (72.37")
                                Monitor-1: DP-1 mapped: DP-0 note: disabled pos: primary,left
                                  model: HP X27q serial: 6CM1340WMF res: 2560x1440 dpi: 65024
                                  size: 1x1mm (0.04x0.04") diag: 685mm (27") modes: max: 2560x1440
                                  min: 640x480
                                Monitor-2: not-matched mapped: DP-4 pos: primary,center res: 2560x1440
                                  dpi: 65024 size: 1x1mm (0.04x0.04") diag: 1mm (0.06") modes: N/A
                                Monitor-3: not-matched mapped: DP-6 pos: right res: 2560x1440 dpi: 65024
                                  size: 1x1mm (0.04x0.04") diag: 1mm (0.06") modes: N/A
                                OpenGL: renderer: Quadro P2000/PCIe/SSE2 v: 4.6.0 NVIDIA 515.65.01
                                  direct render: Yes
                              

                              Here were all the packages upgraded at the same time.

                              Packages Altered:
                                  Upgrade  coreutils-9.0-8.fc36.x86_64                         @updates
                                  Upgrade  coreutils-common-9.0-8.fc36.x86_64                  @updates
                                  Upgrade  egl-wayland-1.1.10-6.20220726gitaaf8608.fc36.x86_64 @updates
                                  Upgrade  grub2-common-1:2.06-47.fc36.noarch                  @updates
                                  Upgrade  grub2-efi-x64-1:2.06-47.fc36.x86_64                 @updates
                                  Upgrade  grub2-tools-1:2.06-47.fc36.x86_64                   @updates
                                  Upgrade  grub2-tools-efi-1:2.06-47.fc36.x86_64               @updates
                                  Upgrade  grub2-tools-extra-1:2.06-47.fc36.x86_64             @updates
                                  Upgrade  grub2-tools-minimal-1:2.06-47.fc36.x86_64           @updates
                                  Upgrade  grubby-8.40-64.fc36.x86_64                          @updates
                                  Upgrade  libwebp-1.2.4-1.fc36.x86_64                         @updates
                                  Upgrade  webkit2gtk3-2.36.6-1.fc36.x86_64                    @updates
                                  Upgrade  webkit2gtk3-jsc-2.36.6-1.fc36.x86_64                @updates
                                  Upgrade  vivaldi-stable-5.4.2753.28-1.x86_64                 @vivaldi
                              
                              DoctorG
                              D
                              1 Reply Last reply
                              Reply Quote 0
                              • DoctorG
                                D
                                DoctorG Soprano @bVgBmfGe2bsRsA
                                last edited by DoctorG

                                @bVgBmfGe2bsRsA Please read https://help.vivaldi.com/desktop/troubleshoot/reporting-crashes-on-linux/
                                Can you save crashdump log in a text file, report crash to Vivaldi tracker and send them the file? And do not forget to copy information you posted here and send them?

                                _bug hunter · Volunteer helper · Sopranos tester · Language DE,EN · ♀👵
                                Known old dragon lady: Gwen aka Dr. Gwen Agon aka GwenDragon aka DoctorGTesting


                                Linux Debian 12 KDE X11 / Windows 11 Pro
                                Intel i5-7400 / NVidia GT 710

                                B
                                1 Reply Last reply
                                Reply Quote 0
                                • B
                                  bVgBmfGe2bsRsA @DoctorG
                                  last edited by

                                  @DoctorG

                                  I can't get a good crash dump from Vivaldi, because it looks like the problem is that libffmpeg.so is busted, so it's the LD_PRELOAD from the vivaldi launcher shell script that is failing.

                                  [file@Z840 ~]$ file /var/opt/vivaldi/media-codecs-91bd4343f863b7747e2b9a1b9f0012e41e51c3dbb380058fc6bdeb7e5a913adf/libffmpeg.so
                                  /var/opt/vivaldi/media-codecs-91bd4343f863b7747e2b9a1b9f0012e41e51c3dbb380058fc6bdeb7e5a913adf/libffmpeg.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, missing section headers at 3375096
                                  

                                  You'll notice the bit about missing section headers.

                                  [foo@Z840 ~]$ export LD_PRELOAD="/var/opt/vivaldi/media-codecs-91bd4343f863b7747e2b9a1b9f0012e41e51c3dbb380058fc6bdeb7e5a913adf/libffmpeg.so"
                                  Bus error (core dumped)
                                  

                                  Just trying to export that variable like the launcher shell script does results in the error. I'll submit a bug for it now.

                                  B
                                  1 Reply Last reply
                                  Reply Quote 1
                                  • B
                                    bVgBmfGe2bsRsA @bVgBmfGe2bsRsA
                                    last edited by

                                    @bVgBmfGe2bsRsA

                                    I submitted VB-90987 for this.

                                    B
                                    1 Reply Last reply
                                    Reply Quote 1
                                    • B
                                      bVgBmfGe2bsRsA @bVgBmfGe2bsRsA
                                      last edited by

                                      @bVgBmfGe2bsRsA

                                      It looks like they just pushed a new version (5.4.2753.33) that fixes the corrupt libffmpeg.so that caused the issue.

                                      1 Reply Last reply Reply Quote 0
                                      Loading More Posts
                                      • Oldest to Newest
                                      • Newest to Oldest
                                      • Most Votes
                                      Reply
                                      • Reply as topic
                                      Log in to reply
                                      • 1 / 1
                                      • First post
                                        Last post

                                      Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.

                                      Copyright © Vivaldi Technologies™ — All rights reserved. Privacy Policy | Code of conduct | Terms of use | Vivaldi Status