Today's 4.1.2369.11-1 Crashes on Arch Linux
-
Vivaldi has been running just great for the last month or so on my Arch system. Today the 4.1.2369.11-1 upgrade came out, and after installing it and rebooting, it will not start correctly. All I get is a blank white screen. Usually when it starts up, I get the white screen with the large V in the center, and then it continues to the browser display that is normal.
Obviously I have not changed a thing, except to update both the ffmpeg codec 92.0.4515.115-1 and the main Vivaldi 4.1.2369.11-1 stable file.
Any ideas as to why this is happening, anyone? For the time being, I did a sudo downgrade and went back to version 4.0.2312.41-1, which still runs just fine again.
-
I have the exact same issue, also running Arch Linux.
-
I can confirm this behaviour on Arch Linux. After the upgrade, Vivaldi "keeps white".
Maybe this is related to some Chromium update? I experienced some freezes/crashes of Google Chrome after a recent update.
-
I don't think the 4.1 version is ready for 'prime time' yet, at least not on Arch.
I'm going to re-install the update, then run it from the terminal, and see what errors it throws. I'll post the results in a few...
-
Alright, with the new update ran from the terminal with the command of :
vivaldi-stable I get the following errors reported:vivaldi-stable [0728/140208.760566:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2) [0728/140208.760667:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2) [21498:21498:0728/140209.453943:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [0728/140213.812287:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2) [0728/140213.812324:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2) [21498:21498:0728/140214.331692:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [0728/140215.757904:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2) [0728/140215.757929:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2) [0728/140216.205566:ERROR:scoped_ptrace_attach.cc(37)] process not stopped [0728/140216.205657:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) [21498:21498:0728/140216.214143:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.To my untrained eye, looks like it's a problem with cpu scaling and network services crashing.... Is there an expert in the crowd??
There is no 'cpufreq' directory on my system in the /sys/devices/system/cpu/cpu0 directory. There is a cpufreq directory, but it is out in the /sys/devices/system/cpu/ directory, but it's completely empty. Don't know why Vivaldi is looking for that anyways, to be honest....
-
My output is a bit different, I get the network service crash but nothing about the CPU.
This is mostly repetitive, but changes a bit at the bottom:
~ vivaldi-stable [409113:409113:0728/140106.022895:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [0728/140111.145787:ERROR:scoped_ptrace_attach.cc(37)] process not stopped [0728/140111.145871:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) [0728/140111.145910:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) [409113:409113:0728/140111.149616:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [0728/140112.940594:ERROR:scoped_ptrace_attach.cc(37)] process not stopped [409113:409113:0728/140112.944201:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [409113:409113:0728/140113.225206:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [0728/140114.202027:ERROR:scoped_ptrace_attach.cc(37)] process not stopped [0728/140114.202095:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) [409113:409113:0728/140114.205189:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [0728/140115.458762:ERROR:scoped_ptrace_attach.cc(37)] process not stopped [0728/140115.458833:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) [409113:409113:0728/140115.461050:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [409113:409113:0728/140117.243494:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [0728/140118.495378:ERROR:scoped_ptrace_attach.cc(37)] process not stopped [0728/140118.495439:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) [409113:409113:0728/140118.498633:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [409113:409113:0728/140119.563653:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [0728/140120.838731:ERROR:scoped_ptrace_attach.cc(37)] process not stopped [409113:409113:0728/140120.840358:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [0728/140122.085754:ERROR:scoped_ptrace_attach.cc(37)] process not stopped [0728/140122.085822:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) [409113:409113:0728/140122.089388:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [409113:409113:0728/140124.838535:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [0728/140126.105424:ERROR:scoped_ptrace_attach.cc(37)] process not stopped [0728/140126.105490:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) [409113:409113:0728/140126.108240:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service. [0728/140127.167280:ERROR:ptracer.cc(422)] ptrace: No such process (3) [0728/140127.167292:ERROR:ptracer.cc(446)] Unexpected registers size 0 != 216 [0728/140127.167295:WARNING:process_reader_linux.cc(378)] Couldn't initialize main thread. [0728/140127.358074:ERROR:scoped_ptrace_attach.cc(37)] process not stopped [0728/140127.372135:ERROR:scoped_ptrace_attach.cc(37)] process not stopped [0728/140127.372154:ERROR:scoped_ptrace_attach.cc(27)] ptrace: No such process (3) [0728/140127.372162:ERROR:scoped_ptrace_attach.cc(27)] ptrace: No such process (3) [0728/140127.372167:ERROR:scoped_ptrace_attach.cc(27)] ptrace: No such process (3) [0728/140127.372172:ERROR:scoped_ptrace_attach.cc(27)] ptrace: No such process (3) [0728/140127.372176:ERROR:scoped_ptrace_attach.cc(27)] ptrace: No such process (3) [0728/140127.372181:ERROR:scoped_ptrace_attach.cc(27)] ptrace: No such process (3) [0728/140127.372198:ERROR:file_io_posix.cc(144)] open /proc/409573/auxv: Permission denied (13) [0728/140127.372209:ERROR:process_memory.cc(41)] short read [0728/140127.372213:ERROR:process_snapshot_linux.cc(75)] Couldn't read exception info [0728/140127.372253:ERROR:scoped_ptrace_attach.cc(45)] ptrace: No such process (3) [0728/140127.372306:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) -
Yeah, I wondered about why it's looking for cpu scaling on my system. That is something that is usually associated with an Intel cpu, but I run an AMD cpu. There is nothing in vivaldi:flags at all having to do with scaling that I can find, so I'm at a loss there.
I'm not about to run Vivaldi in sudo mode so that ptrace can work.. not going to take that risk.
Looks like the big thing is that something is causing our network service to crash, which makes Vivaldi hang. Hopefully the 'powers that be' will read this thread, and check into the issue... Hopefully.......
-
Well after digging around for a while on the net, seems like the issue is mostly with Chromium per this link: Network Issue
Thing is, if they knew about this on the 21st, why did they still release the update today? Oh well, I'm confident it will be taken care of in due time...
My OS: Arch Linux with the i3 Window Manager. And now, the GREATEST browser of them all!!
-
@doppleganger said in Today's 4.1.2369.11-1 upgrade will not start correctly:
Well after digging around for a while on the net, seems like the issue is mostly with Chromium per this link: Network Issue
Thing is, if they knew about this on the 21st, why did they still release the update today? Oh well, I'm confident it will be taken care of in due time...
Great find, hopefully this is fixed sooner rather than later. I already miss my bookmarks.
-
@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!
My OS: Arch Linux with the i3 Window Manager. And now, the GREATEST browser of them all!!
-
@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.
My OS: Arch Linux with the i3 Window Manager. And now, the GREATEST browser of them all!!
-
@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. Будем подождать...
