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.
Today's 4.1.2369.11-1 Crashes on Arch Linux
-
@gyozaguy said in Today's 4.1.2369.11-1 upgrade will not start correctly:
Great find, hopefully this is fixed sooner rather than later. I already miss my bookmarks.
Also, don't forget that you can always downgrade to the last version of Vivaldi, and continue running that until this current issue is resolved. That is what I'm running now as I type this... Just install the 'downgrade' program, and use that.
-
@doppleganger said in Today's 4.1.2369.11-1 upgrade will not start correctly:
@gyozaguy said in Today's 4.1.2369.11-1 upgrade will not start correctly:
Great find, hopefully this is fixed sooner rather than later. I already miss my bookmarks.
Have you ever considered using a great program called buku ? IMHBCO, it's the best of the best bookmark manager out there. It's mainly a terminal prog, but not limited to that, in fact I rarely use the terminal with it. I mostly use it with rofi , and there is also an extension you can install for it with Vivaldi. If you get the time, perhaps check it out... You'll never have to 'miss your bookmarks' again!
I used to use a service like that but it decided to start charging, so I quit using other services because this same situation has happened to me too many times. Maybe I should check it out though, or at the very least back things up more often.
-
@gyozaguy said in Today's 4.1.2369.11-1 upgrade will not start correctly:
I used to use a service like that but it decided to start charging, so I quit using other services because this same situation has happened to me too many times. Maybe I should check it out though, or at the very least back things up more often.
I don't think I explained it correctly. buku is not a service, it has everything stored locally on your system. It's just a program that you install from the github page, and is a VERY powerful bookmark manager. All totally free and open source. It will import all your current bookmarks in about 1.5secs, and you won't lose any of them.
You can get it at buku and there's a great Youtube video about it also.
Youtube vid link is https://www.youtube.com/watch?v=9HzEHrUBQXE&t=20s
-
After even more digging into this issue, I have found the final definitive answer to the problem, as it applies to those of us who run Arch Linux. Link above for reference. Basically, the issue is this:
It all comes down to the network crashing problem. It affects all chromium based browsers, and because vivaldi supplies a pre-compiled binaries blob to Arch, it cannot be patched.
We Arch users will just have to wait until the next release, and hope that the Vivaldi devs take notice of our (Arch Linux) plight.
-
@doppleganger said in Today's 4.1.2369.11-1 upgrade will not start correctly:
After even more digging into this issue, I have found the final definitive answer to the problem, as it applies to those of us who run Arch Linux. Link above for reference. Basically, the issue is this:
It all comes down to the network crashing problem. It affects all chromium based browsers, and because vivaldi supplies a pre-compiled binaries blob to Arch, it cannot be patched.
We Arch users will just have to wait until the next release, and hope that the Vivaldi devs take notice of our (Arch Linux) plight.
That's too bad, but at least we can downgrade in the meantime (thanks for suggesting "downgrade" by the way, very useful).
-
@gyozaguy said in Today's 4.1.2369.11-1 Crashes on Arch Linux - Devs Plz Take Notice:
thanks for suggesting "downgrade" by the way, very useful
No problem. You are most welcome!!
-
@guigirl Awesome, disabling
systemd-resolvedworked for me. Thanks! After looking at the Chromium bug, it looks like there's a chance the fix will be published next week.
-
@guigirl said in Today's 4.1.2369.11-1 Crashes on Arch Linux - Devs Plz Take Notice:
This is NOT a Vivaldi problem [it affects all chromium-based browsers], so anyone inclined to whinge at V Devs about this is ill-informed.
If perhaps you aimed that statement at me, I would like to point out that I have never, once, 'whinged' at any V dev, nor am I 'ill-informed'. If you would re-read my post, I said exactly the same thing that you did, namely "it affects all chromium-based browsers"
My exact wording was "It affects all chromium based browsers, and because vivaldi supplies a pre-compiled binaries blob to Arch, it cannot be patched."
There was never a disparaging word said against any dev. I'm not sure if English is your native language, so I'll translate what I wrote to simpler terms for you. "vivaldi supplies a pre-compiled binaries blob to Arch, it cannot be patched", in simpler terms, means that it is indeed an Arch 'thing', due to the fact that it cannot be dealt with in the PKGBUILD phase of compiling.
To the well informed, they would know that this issue has already been dealt with by the Chromium devs, so that a work-around of disabling systemd-resolved is not necessary as of the 26th of this month. My statement of "I hope that the Vivaldi devs take notice of our (Arch Linux) plight." , and again note that I said "Arch Linux", was a way of asking that the updated and patched version of Chromium be used as the base for the pre-compiled binary which Vivaldi uses, and then is provided to Arch.
Hopefully this will clear up any confusion and mis-conceptions you may have had regarding my post that referenced this subject in order to prevent you from being ill-informed.
Personally, I feel that your post was most excellent and informative, right up until your PS: comment. I feel that was not needed, nor called for, in any way. Just saying......
-
@guigirl said in Today's 4.1.2369.11-1 Crashes on Arch Linux - Devs Plz Take Notice:
@doppleganger A thousand apologies. It must have been someone else who posted
@doppleganger said in Today's 4.1.2369.11-1 Crashes on Arch Linux - Devs Plz Take Notice:
I don't think the 4.1 version is ready for 'prime time' yet, at least not on Arch.
Or, maybe it was
nobody, again...I'll try one last time with you. Vivaldi is built on a Chromium foundation, and it is a closed-source product. No one can help with the small bugs/issues other that the group who develops Vivaldi. Not the Arch community, not any community of linux users. Vivaldi only.
Now if in the course of developing that closed-source product it is built on a faulty foundation, results such as some not being able to run it on Arch occurs. It happens. There are small issues and bugs with almost every piece of software out there, thus the reasons for updates existing.
If your reality is that it's not a problem with the way Vivaldi was built, and that the devs should in no way be alerted to that fact, then so be it, it's your reality.
My reality is that if a faulty foundation was used, it's not completely ready for ALL 'prime time' ARCH users, and the devs might care to be notified as to that fact.
I urge you to read my sig, and you'll know my viewpoint regarding Vivaldi.
'Nuff said by me to you.
-
//MODEDIT: Added the English translation (machine-translated) - original post below
Trouble...
If you remember that the developers removed the button (PiP) from youtube player (which they themselves added there) for a month and a half. You can expect a fix not earlier than a year from now. (((I rolled back to the version 4.0.2312 for now. We will wait...
Беда...
Если вспомнить, что разработчики полтора месяца убирали кнопку (PiP) с youtube плеера (которую они сами же туда и добавили). То исправление этого бага можно ждать не раньше чем через год. (((Откатился пока до версии 4.0.2312. Будем подождать...
-
@xakep Please in english language or post in your local rus forum.
-
The downgrade option for me was an easier route than disabling resolved, since I actually use that. Fixes are on the way upstream (apparently around the end of August?) and Vivaldi devs are aware of it, as noted here: https://forum.vivaldi.net/post/502937
So it doesn't seem like it will be all that long before the fix finds its way to Vivaldi.
-
Thanks for suggesting to downgrade the package, I wouldn't have thought to do that since I've never had to do it before. But if anyone needs help downgrading go to this link -> https://wiki.archlinux.org/title/downgrading_packages
-
Perhaps I wasn't clear, I'm downgrading Vivaldi, not systemd-resolved . I know it isn't really Vivaldi's fault, but the combination of the latest Vivaldi and the latest resolved is apparently what can produce the issue, and downgrading Vivaldi for me is the easier short-term workaround.
-
@guigirl Why would you even think I was talking about downgrading anything other than Vivaldi? I didn't read anyone mention downgrading systemd and I didn't mention it myself. Maybe I should've laid out the steps to be more clear? If so then I can do that:
cd /var/cache/pacman/pkgls- Look for the vivaldi package in your cache directory, version previous to 4.1 and copy it. I will post the version which was in my cache in the next command...
sudo pacman -U vivaldi-4.0.2312.41-1-x86_64.pkg.tar.zst
Correct me if I'm wrong but downgrading Vivaldi shouldn't break anything since it's not something the system relies upon. I really don't know where you got the idea that I was somehow suggesting to downgrade anything besides Vivaldi. I posted the link to the wiki on downgrading packages so people could read it themselves and it would be more clear on what they were actually doing. I wasn't the first one to suggest downgrading Vivaldi so I'm not sure why you targeted me but I only posted to say thanks to the person who suggested it because now I'm using Vivaldi again...
-
Best practice if you don't want to downgrade is to temporarily stop service in case it's enabled by any other "Chrome" based browsers you have like so as which worked for me :
sudo systemctl disable systemd-resolved.service sudo systemctl stop --now systemd-resolved.serviceUntil they fix it. Once fixed just reverse it
sudo systemctl enable systemd-resolved.service sudo systemctl start --now systemd-resolved.serviceHope this helps...
-
@gostly said in Today's 4.1.2369.11-1 Crashes on Arch Linux:
..... Maybe I should've laid out the steps to be more clear? If so then I can do that:cd /var/cache/pacman/pkgls- Look for the vivaldi package in your cache directory, version previous to 4.1 and copy it. I will post the version which was in my cache in the next command...
sudo pacman -U vivaldi-4.0.2312.41-1-x86_64.pkg.tar.zst
...... I only posted to say thanks to the person who suggested it because now I'm using Vivaldi again.
Hello gostly! I'm the OP of this thread, and it was my original comment of downgrading V so that I could continue to use it because of the issue the new version has with systemd-resolved.
I have something to suggest to you, and any other members reading this thread. While the above method you describe to downgrade a package will work, there is a much, much easier, faster, and official way of doing the same thing for almost any package that is installed on your system.
What I suggest is to install the 'downgrade' package from the AUR. Current version is 10.1.0-1 . Once that package is installed, it's a breeze to downgrade whatever you choose, for whatever reason you have. It's your system, you make the choices as to whether you like a new version of a program or not.
Once 'downgrade' is installed, usage is the same for any package you choose. From your terminal, enter the below command, and you're good to go.
sudo downgrade <package_name>For example sudo downgrade vivaldi
The result of that command will give you a list of the available versions you can downgrade to, in a numbered list. Enter the number of your choice, and if that particular version is not stored locally on your system, 'downgrade' will go out and download it from a repo. It will then install the version you choose, and that's that. If you change your mind, you can simply Ctrl+C out of it to quit the 'downgrade' program.
I have used the 'downgrade' package for any number of reasons over the last 6 or 7 years of running Arch, and it's a valuable and powerful tool to have in your toolbox.
So as I said, your listed method will work, however after installing 'downgrade' there is only one command to enter, and the rest is gravy!
An FYI for better Arch living ...
-
@doctorg said in Chrome based browers not working with systemd 249:
New Stable 4.1.2369.15 fixed the systemd issue!
Big Party for Archies now. -
@doctorg said in Today's 4.1.2369.11-1 Crashes on Arch Linux:
@doctorg said in Chrome based browers not working with systemd 249:
New Stable 4.1.2369.15 fixed the systemd issue!
Big Party for Archies now.That was a fast response by the Devs. Good news, indeed!
-
For all Arch Linux users, the updated version just became available in the repos about 5 minutes ago, and I can confirm that the new version does indeed work with systemd-resolved enabled.
Nice work, V team, and thanks for all the effort!
