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.
Debian | V Fails to Start
-
@speakertomeat Both KDE (Plasma) and GNOME use different secure keyrings (used to store passwords), which are supposed to unlock automatically upon login to the session. I'm wondering if this could be related.
Vivaldi on Linux:
openSUSE Tumbleweed and Slowroll (Xfce 4.20)
Fedora 42 and Rawhide (Xfce 4.20)Android (10)
Vivaldi user since 2016. Thank you to all Vivaldi users.
-
@mib2berlin
rename Default folder still can't startup
current my workround is downgrade to 6.7
but my cookie will lost, I need re-login all site -
@owan0zyxel
Hm, even 6.7 start the profile is not in a clean state if you downgrade.
Did you downgrade before at some point?Opensuse Tumbleweed x86_64 KDE 6.2 X11, Windows 11 Pro, Vivaldi latest
HP Probook Intel(R) i5-8350U 16 GB, GPU UHD 620, SSD 256 GB
Miniforum-B550 AMD Ryzen 7 4700G 16 GB, Radeon Graphics
Redmi Note 14, HyperOS Android 14 -
@mib2berlin Thank you for the suggestion. tested it and still segfault. I also tried moving away Session Storage just in case.
-
@edwardp Yes, but i wonder what is it that vivaldi unlocks via the wallet that is causing the problem. I'll check the wallet on kde anyhow see what entries are there for vivaldi.
-
@speakertomeat
Hi, did I understand correctly you can start Vivaldi using Gnome?
Iirc you can copy the Kwallet key to Gnome keyring, I try to find the thread about.
Copy this over to Gnome:
-
@mib2berlin
I never downgraded before 6.8.
I frequently encountered Segmentation faults since 6.8.
Downgrading to 6.7 always solved the issue. -
@owan0zyxel Downgrade breaks settings data in profile and causes unexpected and unknown issues, and if you have bad luck such can not be fixed by helpers.
️
Downgrade officially not advised by Vivaldi team. -
Sadly, I did a test and downgrading to 6.7 does resolve my issue, and vivaldi starts.
What I wonder is if there's a mechanism for me to send the MDMP from 6.8 to devs so that they can see maybe what is causing the segfault on 6.8 and help resolve it on a new version
-
@speakertomeat
Hi, if Vivaldi create a crash log file you can report it and add the latest file.
The logs should be in /.config/vivaldi/Crash Reports/https://help.vivaldi.com/desktop/troubleshoot/reporting-crashes-on-linux/
-
@mib2berlin
I have send crash report
many thanks for help -
Meanwhile. In my case, I downgraded to Vivaldi 6.7.3329.41 and vivaldi started working again.... the with Vivaldi still open I upgraded back to 6.8.3381.48, and it starts perfectly and works.....
Edit: That is, with Vivaldi 6.7 running (in case it's important but I doubt it) I upgrade on my package manager to ñatest 6.8. The shutdown the running 6.7, and restart Vivaldi, and the newer 6.8 starts perfectly.
-
@speakertomeat
Hi, strange but fine for now.
Did you try to reinstall Vivaldi at some point before? -
@mib2berlin said in Segfault:
@speakertomeat
Hi, strange but fine for now.
Did you try to reinstall Vivaldi at some point before?No, I admit I didn't.... but again, as long as it couldn't read my config directory, be it for lack of the key in the wallet, or me cleaning it, the old Vivaldi worked, so the binary wasn't outright corrupted.... though it could've been a corrupted library or app segment that didn't get triggered when there wasn't a specific config to enable it....
-
@speakertomeat
I am sorry no idea but sometimes a install get's corrupted after an update. In this case it is nothing wrong in your profile and a simple remove Vivaldi and add it again fix issues.Cheers, mib
-
Well, once again, reboot my pc, vivaldi 6.8 segfaults, even the just released newer 6.8.3381.50.
And now, there's no more 6.7 in vivaldi's repository. Thankfully I hadn't cleaned my apt cache and found my old .deb in /var/cache/apt/archives (you should have a vivaldi-stable-6.7...... there). Make a backup of that file somewhere, so each time vivaldi segfaults after a reboot or who knows what, install 6.7, start it, once it starts close it and install 6.8
Beware that some of your sessions (not all of them, for some odd reason) will be lost and you'll have to login. And vivaldi 6.7 dislikes the email data format from 6.8 so won't read it and as I am not currently using vivaldi mail I haven't checked if data is not lost, so beware.
And I hope someday Vivaldi finds and squashes this bug.
P.s. I don't want to check the mire of legalese about redistribution of Vivaldi so even if you ask via DM I'm sorry to say I won't send you my backed up copy of 6.7, I'm sorry.
-
@owan0zyxel said in Segfault:
@mib2berlin
I have send crash report
many thanks for helpCould you please post the bug report number (VB-xxxxxx)? Thank you.
Vivaldi on Linux:
openSUSE Tumbleweed and Slowroll (Xfce 4.20)
Fedora 42 and Rawhide (Xfce 4.20)Android (10)
Vivaldi user since 2016. Thank you to all Vivaldi users.
-
Hi, old builds are in the Archive.
The Vivaldi team don't recommend the downgrade of Vivaldi, this can cause unexpected errors in the future.Cheers, mib
-
@owan0zyxel said in Segfault:
@mib2berlin
I have send crash report
many thanks for helpCould you please post the bug report number (VB-xxxxxx)? Thank you.
On my own side, I'm unable to report since the MDMP (Crash Log) files I try to upload are rejected by the report system for being too large (8.3 MB)
-
@speakertomeat
Hi, the .dmp files are good to compress, a 500KB file compress to 40KB for example.
Then upload as .zip file.Cheers, mib
