Vivaldi always crashing for no reason.
-
@npro
Stop thinking "Qubes-OS"..Think Debian, Fedora, PCLinuxOS, Slackware, CentOS, RedHat, Devuan, etc...
And yes, most browsers these days are just a chromium base with altered code... MS Edge, Google Chrome, FireFox, Opera, Brave, DuckDuckGo, and others....
-
@DRWhite25 said in Vivaldi always crashing for no reason.:
Think Debian, Fedora, PCLinuxOS, Slackware, CentOS, RedHat, Devuan, etc...
And yes, most browsers these days are just a chromium base with altered code... MS Edge, Google Chrome, FireFox, Opera, Brave, DuckDuckGo, and others....@DRWhite25 said in Vivaldi always crashing for no reason.:
It's only been happenning since upgrading to version 7 something. Never happenned in 6. And early 7 was fine as well.
@DRWhite25 said in Vivaldi always crashing for no reason.:
ivaldi shouldn't be doing anything with the cpufreq, I mean Vivaldi 6.* didn't do anything that caused this issue, so it is something that was changed in version 7.
@DRWhite25 said in Vivaldi always crashing for no reason.:
So it's Vivaldi 7.* that has the issue. That's the only thing that has been updated on the system after all.
So just do test with Chromium 134 in any of those 30 distros of yours, because that is what has changed between 6 and 7.1.
And post your system specs already. Generic "blah blah my system" don't say anything. What kind of troubleshooting do you expect if you don't offer the basic info.
-
model name : AMD Ryzen 5 2600X
cpu MHz : 3600.000
cpu cores : 2
MemTotal: 4025936 kBWhat else do you need?
You want the fact I run 12 monitors?
Or maybe my PS/2 KBD/Mouse?
My SATA SSDs?
My HDDs?
My RAID storage device?Love how you keep editing and editing your post while I'm writing a reply...
-
@DRWhite25 said in Vivaldi always crashing for no reason.:
Love how you keep editing and editing your post while I'm writing a reply...
just adding all your quotes about how it was ok with Vivaldi 6.
-
@DRWhite25 I will try Qubes OS 4.2.4 with Debian 12 in my VM (VirtalBox VM / Windows 11 host) now.
Stay tuned. -
@DRWhite25 said in Vivaldi always crashing for no reason.:
What else do you need?
how about your GPU?
-
-
--disable-gpu
As I say, GPU isn't the problem....
Whether I have that option set or not, it doesn't have any effect.
It isn't the GPU..
-
@DoctorG why do so, the same happens with any distro OP said. And it's not that trivial to inform you, programs there must be run each in its own defined virtual machine.
-
@npro Whut? I feel like in Kubernetes hell. Than i will not try that exotic Qubes OS.
-
@DRWhite25 If you don't post your GPU model then good luck, I'm out.
-
@npro I'm still trying to find out what it's identified as. I'll let you know when I know.
-
@DoctorG maybe it got better, please do test after all, I 'd like to hear your opinion
-
@npro When was the last time you were using it? I've been using Qubes since version pre-1
-
@DoctorG https://www.qubes-os.org/doc/how-to-install-software/
"When you wish to install software in Qubes OS, you should generally install it in a template. For installing templates themselves, see how to install a template. Advanced users may also be interested in learning how to install software in standalones and dom0."
*"Installing
Certain templates come preinstalled with Qubes OS. However, there may be times when you wish to install a fresh template from the Qubes repositoriesYou can use a command line tool - qvm-template - or a GUI - qvm-template-gui.
At the command line in dom0, qvm-template list --available will show available templates. To install a template, use:
$ qvm-template install <template_name>
You can also use qvm-template to upgrade or reinstall templates."* -
@DRWhite25 It doesn't matter as I don't have to think Qubes OS about your issue.
-
I install in standalone systems, OR every time the guest starts.
I don't think Qubes-OS either... I think UNIX and BSD and whatever else I want to have installed and running securely at the same time.
I have been doing things in Qubes since day 1 that most people just don't know how or why, yet it works seamlessly.
Then after quite a while someone asks if something can be done, and I say yes it can, and tell them how.But I don't think QUBES-OS about this issue wither, because it's all in the operating system I'm running Vivaldi in, not in Domain-0.
You need to change your perspective to use Qubes if you just think Qubes when you are using it...
-
@npro I'd just say " generic "/" custom 'Qubes' "
I mean the GPU doesn't matter as that isn't the problem...
-
@DRWhite25 But it would be great if you could send the dev team crash dumps from time of crash so that they can understand what is triggering the crashes.
Here's more info about how to send crash dump files:
-
@DoctorG said in Vivaldi always crashing for no reason.:
that they can understand what is triggering the crashes.
Indeed, since this affects a lot of casual (mainstream) distros as we found out, otherwise it would be strictly Qubes OS related.