Vivaldi won't start after system crash
-
Okay, I deleted Calendar and Calendar-journal and that got rid of the error lines about calendar... But it still won't start. Output is now:
$ vivaldi-stable [0119/142604.724707:ERROR:elf_dynamic_array_reader.h(64)] tag not found fish: Job 1, 'vivaldi-stable' terminated by signal SIGSEGV (Address boundary error) -
@cryptoquick I mentioned it might not be the problem. Have you tried on a new profile? That’s the most important step. If that doesn’t work, it’s something else entirely.
-
Okay, I tried this:
╭─hunter@hunter in ~/.config/vivaldi took 0s ╰─λ mv Default/ DefaultBackup ╭─hunter@hunter in ~/.config/vivaldi took 0s ╰─λ vivaldi-stable [0120/130240.344983:ERROR:elf_dynamic_array_reader.h(64)] tag not found fish: Job 1, 'vivaldi-stable' terminated by signal SIGSEGV (Address boundary error)Still not working
-
@cryptoquick If the profile is not the problem, it’s the application itself. Try a reinstall, but I don’t know what is going wrong for you or where the problem lies.
-
Hello @cryptoquick
Similar issue was fixed on this other thread by following the steps on the "Extras" https://forum.vivaldi.net/topic/104543/switching-v-profiles-error/2I hope that helps.
Regards,
Fred. -
Hi, thanks for pointing that out. The Extras tasks don't make sense, since Vivaldi won't start even after moving the default user folder, I can't change settings for websites or the browser, or remove extensions.
The error I'm getting is a bit different now after some Arch system updates:
vivaldi-stable [65407:65407:0206/142920.382714:ERROR:search_engines_managers_factory.cc(77)] File can't be read: /home/hunter/.config/vivaldi/search_engines_prompt.json [0206/142920.546169:ERROR:elf_dynamic_array_reader.h(64)] tag not found fish: Job 1, 'vivaldi-stable' terminated by signal SIGSEGV (Address boundary error)Same result though.
I checked systemd logs. Here's the output from journalctl:
Feb 06 14:34:48 hunter-21fvcto1ww systemd-coredump[66931]: [🡕] Process 66844 (vivaldi-bin) of user 1000 dumped core. Stack trace of thread 66844: #0 0x00005fa67f80c69c n/a (n/a + 0x0) #1 0x00005fa684d3c155 n/a (n/a + 0x0) #2 0x00005fa6806f06e5 n/a (n/a + 0x0) #3 0x00005fa6806f07e3 n/a (n/a + 0x0) #4 0x00005fa68576fc36 n/a (n/a + 0x0) #5 0x00005fa6806f06e5 n/a (n/a + 0x0) #6 0x00005fa6806f07e3 n/a (n/a + 0x0) #7 0x00005fa6806f06e5 n/a (n/a + 0x0) #8 0x00005fa6806f07e3 n/a (n/a + 0x0) #9 0x00005fa6814d8481 n/a (n/a + 0x0) #10 0x00005fa6814d7588 n/a (n/a + 0x0) #11 0x00005fa6814d6741 n/a (n/a + 0x0) #12 0x00005fa6814d64b3 n/a (n/a + 0x0) #13 0x00005fa67e5b43f5 n/a (n/a + 0x0) #14 0x00005fa6811dd823 n/a (n/a + 0x0) #15 0x00005fa6811dd542 n/a (n/a + 0x0) #16 0x00005fa685539490 n/a (n/a + 0x0) #17 0x00005fa68189012f n/a (n/a + 0x0) #18 0x00005fa68188f450 n/a (n/a + 0x0) #19 0x00005fa6816e5db6 n/a (n/a + 0x0) #20 0x00005fa6816cc784 n/a (n/a + 0x0) #21 0x00005fa6816cdc14 n/a (n/a + 0x0) #22 0x00005fa681654ad8 n/a (n/a + 0x0) #23 0x00005fa68151b0c7 n/a (n/a + 0x0) #24 0x00005fa68151af6d n/a (n/a + 0x0) #25 0x00005fa68151b3ad n/a (n/a + 0x0) #26 0x00005fa680e15698 n/a (n/a + 0x0) #27 0x00005fa680e14ec3 n/a (n/a + 0x0) #28 0x00005fa680e75401 n/a (n/a + 0x0) #29 0x00005fa680e744ca n/a (n/a + 0x0) #30 0x00007fd9d3ae3488 n/a (libc.so.6 + 0x27488) #31 0x00007fd9d3ae354c __libc_start_main (libc.so.6 + 0x2754c) #32 0x00005fa681cd035a n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 ░░ Subject: Process 66844 (vivaldi-bin) dumped core ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ Documentation: man:core(5) ░░ ░░ Process 66844 (vivaldi-bin) crashed and dumped core. ░░ ░░ This usually indicates a programming error in the crashing program and ░░ should be reported to its vendor as a bug. -
Hello @cryptoquick
The error says that the File can't be read: /home/hunter/.config/vivaldi/search_engines_prompt.json
- Does the file exist?
- Does the file have proper read permissions?
Regards,
Fred. -
It does not exist. I have no idea what should go into this file. I'm also not convinced it's the reason Vivaldi is crashing with a segfault.
-
@cryptoquick
Hi, the file include the default search engines for different countries."wikipedia_fr": { "name": "Wikipedia", "keyword": "w", "search_url": "https://fr.wikipedia.org/wiki/Special:Search?search={searchTerms}", "suggest_url": "https://fr.wikipedia.org/w/api.php?action=opensearch&search={searchTerms}", "favicon_url": "https://fr.wikipedia.org/static/favicon/wikipedia.ico", "type": "VIVALDI_SEARCH_ENGINE_WIKIPEDIA", "id": 6For example.
You can move your profile folder "Default" to a save place and delete all other content in .config/vivaldi.
At next start Vivaldi re create all in .config/vivaldi.
I tested this a few minutes ago.EDIT: Important!
If you use more than one profile you have to keep the other folders too, they are called Profile 1, Profile 2 and so forth. -
@mib2berlin said in Vivaldi won't start after system crash:
.config/vivaldi
Okay, that led to good progress, thank you. By moving the entire ~/.config/vivaldi folder, Vivaldi was able to start again.
I moved my old profiles back, but only the default profile is showing up in the list.
-
@cryptoquick
Hm, maybe I forgot something?
If you still have the Backup delete the other profiles, or move them out of .config/vivaldi, create new profiles as you need.
As example: Delete the content of Profile 1 and copy over the content from the first profile in your backup, and so forth.
I had the same with 2 extra profiles, nothing in the list but it work now.
The naming is correct now too.
EDIT: You can try to copy over the file Local State, it include the profile information.
Then you can save some work with deleting and copys. -
Hmm... My Local State file is 34KB in size. When I copied it over, it didn't recover the rest of my profiles, though.
-
@cryptoquick
This was only a test if restore Local State save you some work.
I had deleted all except the profile folders and copy over the content of a profile in a new created profile work.@mib2berlin said in Vivaldi won't start after system crash:
If you still have the Backup delete the other profiles, or move them out of .config/vivaldi, create new profiles as you need.
As example: Delete the content of Profile 1 and copy over the content from the first profile in your backup, and so forth.
