Vivaldi not fully installing on Fedora 25 64-bit



  • I attempted to install Vivaldi on Fedora 25 (64-bit) and dnf displayed a message that the key import failed. Is there a way to fix this? I used dnf to erase/remove Vivaldi, then attempted a second install with the same result. The output of the install is below:

    Running transaction
    Installing : vivaldi-stable-1.7.735.46-1.x86_64 1/1
    error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
    error: /tmp/vivaldi.sig.3efRve: key 1 import failed.
    Redirecting to /bin/systemctl start atd.service
    Verifying : vivaldi-stable-1.7.735.46-1.x86_64 1/1

    Installed:
    vivaldi-stable.x86_64 1.7.735.46-1

    Complete!



  • I then attempted another install, a while after running dnf again and this time, the error of the key import failing, did not display.

    However, this time, vivaldi.repo was not re-created in /etc/yum.repos.d. I removed the repo entry from that directory when the first two installs apparently didn't fully succeed.

    Could someone please explain what is happening? I have removed/erased it again. Thank you.

    Running transaction
    Installing : vivaldi-stable-1.7.735.46-1.x86_64 1/1
    Redirecting to /bin/systemctl start atd.service
    Verifying : vivaldi-stable-1.7.735.46-1.x86_64 1/1

    Installed:
    vivaldi-stable.x86_64 1.7.735.46-1

    Complete!



  • This is a common occurrence when you install a Chromium-based browser. I haven't looked into what's happening specifically, but the error can be safely ignored. It's basically saying that it can't acquire a lock file and therefor has to delay importing the key until some later moment. I haven't had any problems because the key has always been imported and the repo added automatically anyway. The warning is sort of misleading, it would be cool if someone could figure out how to remove it.



  • I also removed the vivaldi.repo file in /etc/yum.repos.d, but when I tried to install it the second time, the vivaldi.repo file was not re-created, so I have no idea what information needs to be in that file to recreate it manually, in order to Vivaldi to update itself when necessary.

    If that information were available somewhere, I would gladly reinstall Vivaldi and manually re-create the vivaldi.repo file.



  • @edwardp
    I have a test install of fedora25.
    This is the content of my /etc/yum.repos.d/vivaldi.repo file.

    [vivaldi]
    name=vivaldi
    baseurl=http://repo.vivaldi.com/archive/rpm/x86_64
    enabled=1
    gpgcheck=1
    gpgkey=http://repo.vivaldi.com/archive/linux_signing_key.pub
    

    The vivaldi rpm installs a script to '/etc/cron.daily/vivaldi', that in turn installs the repo and signing key.



  • @CantankRus I just re-installed the RPM file, no errors appeared, a vivaldi entry was present in /etc/cron.daily/ and after creating the vivaldi.repo file as above, Vivaldi launched and runs fine. I also did another update of the system afterwards (I run 'sudo dnf upgrade' in a terminal.) and it retrieved the necessary information from the Vivaldi repository, so it should be all set now.

    Thank you for the assistance. :)


Log in to reply
 

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