New Updates For A New Decade | The Roundup #14

paracetamol

Also had problem with time both on my physical machine and in a virtualbox installation immediately after the update. In both cases the solution in https://discuss.getsol.us/d/3446-unstable-repo-users-testing-desired-for-systemd-244/12 worked. I am mentioning this because the issue showed up consistently for me.

WetGeek

I'm late to the party, because I live near the west coast of N. America. This morning I've upgraded four VMs and a multimedia server so far. The only oddity I encountered was on the multimedia machine. That would be the need to run the two files in /usr/share/vivaldi-stable/ that allow it to stream commercial content:

update-ffmpeg
update-widevine

I suspect the VMs probably require the same updates, but I don't use those for streaming entertainment, so I probably won't bother with those. Just three more machines to upgrade, so things are looking good here so far.

cet

Updated using the terminal.Everything went fine.Thank you.

[deleted]

Done it via terminal. Everything went as described in the blogpost. All fine as far as i can tell after the (hard) reboot.

sudo usysconf run -f finishes successful as well after the reboot.

elfprince

Hmmm, I'm scared to update now. Seems too risky, and do not wish to lose my only workstation for work and play. Also, why use power button to shutdown and not the 'shutdown' from the panel? Isn't that the same thing?

WetGeek

elfprince I'm scared to update now

After all the unmitigated successes folks (including me) have been reporting? What bothers you?

JoshStrobl

elfprince Also, why use power button to shutdown and not the 'shutdown' from the panel? Isn't that the same thing?

No, one is forcing it to shutdown, the other uses systemd. That's why we specified.

Now I need to log out every time prior to shutdown ?

What? No. At no point to we ever indicate that. We only say to log out first this specific instance because of the systemd upgrade.

I don't welcome big drastic changes until they have been well tested prior. I have doubts.

Seriously? We've tested this for like a week now and you can see all the reports of it being fine.

elfprince

WetGeek Well, it got more complicated. Now I need to log out every time prior to shutdown ? Use the power button instead of the normal shutdown procedure via the panel? You have tons of machines, I have this one only. I am afraid to come up with an unusable system. It ran smoothly so far. I don't welcome big drastic changes until they have been well tested prior. I have doubts.

[deleted]

elfprince well, i can understand you. But you have a few options to feel better.
For example just wait a day or so and follow this forum to see what people report.
You can do a backup of your system prior to the update (one should always do backups, right 😂 ).
Have a live system of solus handy (as suggested in the blogpost) to boot and troubleshoot if necessary afterwards. With that live system booted beforehand, you could also create an image via gnome-disks (on the live iso) of your installed system/hard disk before updating (-> backup as mentioned above). I would say you are in a pretty good shape then

WetGeek

elfprince You have tons of machines, I have this one only.

If I were in your position (and I have been in the past) I would do exactly what you said. Wait until all the bugs have been discovered and dealt with.

If it's a work computer, even this big update probably wouldn't have to be configured today. Or even this week. Maybe just continue your work for now with what you know is a working computer, and go for a full upgrade next Friday if no real problems have been encountered by then?

paracetamol

WetGeek With all due respect, someone stressing this much over upgrades due to relying on just one machine should rethink using a rolling distro and choose a LTS super stable workhorse such as Debian.

elfprince Reading your post I get a suspicion there's some confusion. You won't need to log out (an optional step) and hard reset your machine every time after the update. Just once, to allow the new systemd to kick in.

elfprince

[deleted] Thanks for your support and advice. I am not an expert in Linux. All those things you have mentioned just went over my head. 😅 I do not wish to disturb a well running system. I've seen in some above posts that people had some problems following this update. If it ain't broken - don't fix it? Why go to the trouble of potentially reinstalling the system? Imagine that this is a Windows user, who knows nothing about Linux. I think he or she would think twice about this as well.
Yes, I was considering to wait for a while until the 'dust settles' ;-) And see others' experiences first.

JoshStrobl

elfprince If it ain't broken - don't fix it?

Because that's not how this works. You need to update your system.

picnerd

The update went through without errors. However, Eopkg complained about VirtualBox and network manager.
Then I ran sudo usysconf run -F and sudo sync. But then I had to switch off hard. But the system rebooted without any problems.
After that I executed sudo eopkg check.
I filtered the result with grep:
picnerd@picnerd ~ $ sudo eopkg check | grep -e 'Datei korrupt' Datei korrupt: usr/lib/tmpfiles.d/udisks2.conf picnerd@picnerd ~ $

greetings

JoshStrobl

picnerd This has been reported previously. Neither are actual issues 🙂

elfprince

JoshStrobl I will wait a little before doing this update. Thank you for clearing up my other questions. 😃

WetGeek

JoshStrobl We've tested this for like a week now and you can see all the reports of it being fine.

He uses his one and only computer for work. What if some proprietary piece of software that's required for his work has a serious problem with the upgrade? I.e., software that hasn't been tested for a week?

In that case, I'd be nervous, too. Elfprince, just be sure you have a good backup available when you do upgrade.

picnerd

JoshStrobl
Just wanted to let you know that everything is fine. 👍 😂

JacekJagosz

I have 3 problems after those new updates:
1) When shutting down I get:
watchdog: watchdog0: watchdog did not stop! systemd-shutdown[1]: Failed to finalize DM devices, ignoring
and the shutdown takes longer.
2) Upowerd fully boggles down one thread (25% CPU usage) every second boot
3) Quite rarely qmi-proxy also completely tanks the CPU and the 4G modem stops being visible.
This is a 2-week old plasma install, I will probably reinstall when new ISOs come out, and hopefully then the situation is much better.

elfprince

WetGeek Thank you for understanding!

JoshStrobl

WetGeek What if some proprietary piece of software that's required for his work has a serious problem with the upgrade? I.e., software that hasn't been tested for a week?

If it's a proprietary piece of software it's not likely going to be in the repo in the first place, in which how would it ever be tested? I'm sorry but it's just not a good argument.

WetGeek

JoshStrobl I'm sorry but it's just not a good argument

It is if his computer runs what he uses at work just fine now, but perhaps won't run it after this update. That's why I suggested creating a backup before the upgrade, if he doesn't have one already. What got my attention was where he stated that he has only that one work machine available. I'd be careful, too.

« Previous Page Next Page »