This week’s openSUSE Tumbleweed snapshots were steady and there were no large updates. While updating openSUSE rolling release once a week could result in a ...
@thelinuxcast I also had problems with #vivaldi after an update on #opensuse#tumbleweed.
I had to delete all files in .config/vivaldi/Default/GPUCache
I also deleted all "GPUCache" - folder within .config
Since that time vivaldi works well again.
@nixCraft
Oh,a flame war 🔥 come on! If you crash Arch is because you tried hard, and for the same thing it's more stable than Debian.
Debian has the fame but historically ever was a crashing distro.
For example, #openSUSE#Leap is more stable than Debian by far. I would say even #Tumbleweed.
Tumbleweed snapshots didn’t lack excitement this week as multiple packages received updates and a couple major versions arrived for openSUSE rolling release users this week.
“The 5.38.0 version introduces a host of new features, including the class feature and support for #Unicode 15.0. The language also improves defined-or and logical-or assignment default expressions in signatures, and more. There was a significant deprecation in the release with the use of ' as a package name separator.”
I think I will start a thread here as a sort of diary.
Starting at #FrOSCon, I have started to try #openSUSE on my laptop. As a #Debian Developer, I felt reluctant to try something else, and Debian is a great project.
However, as I am teaching openSUSE at Linuxhotel, I thought I should maybe get more familiar with it 🤣. Also, I had already fallen in love with #zypper.
If you are keen in following the pros and cons I discover, take a seat!
@Natureshadow I have not experienced this in the last eight years with #tumbleweed. And I refresh my repos a lot (as I maintain some packages and frequently test them).
This could be a broken mirror somewhere.
This week’s openSUSE Tumbleweed updates had changes for harfbuzz, xterm, Redis, Audacity and more Snapshots have been rolling out consistently this week.
My only negative takeaways from a few experiences with it:
pacman spoiled me. zypper feels slow
No packagekit by default, and it's a pain to figure out how to implement. Every forum post I could find on the subject basically said, "Duh, why don't you just use the root password, lol!" #stupid
Great distro, otherwise.
(And yes, I'm using the old fashioned SuSE capitalization, just 'cause ;)
#Linux people: I am switching away from #Fedora (slow start-up time in addition to open source brouhaha).
After installing #openSUSE with #KDE, I discovered the #LEAP version doesn’t recognize my #WiFi chip set. Online documentation says that #Tumbleweed does.
Should I go for #Tumbleweed or some other KDE-based distro?
@vwbusguy I would suggest to do something with the #MicroOS server variant. That is more "exciting" than plain #Tumbleweed, as the latter just works. MicroOS just works, too. But is immutable and transactional and thus more interesting...
Woo, new adventure today. I got a wild hair, and decided to try and package a workable LXQt-Wayland for openSUSE, using labwc as the compositor. So far I can get the compositor to start? So that's progress, I suppose. Using the work done at https://github.com/stefonarch/LXQt-Wayland-files to see if I can't get something working....
Is it just me? We can find millions of dollars to shape majestic conference centres with exquisite curved designs. Yet looking for funding for museums?#tumbleweed
I have used manjaro in the past and for the reasons outlined in all the previous remarks and which I could not recover and fix 3x. I switched to openSUSE and didn't look back. I wondered why I didn't use openSUSE much sooner. it's solid, it's fast, it's reliable, it uses #btrfs filesystem, and has rollback feature as my insurance.
I didn't get that with manjaro. everytime I did update with manjaro after the 1st screwup, and reimaged the second time, I was nervous like walking on egg shells. as a user, I shouldn't have to feel that way. I gave manjaro 3 chances, after the 3rd screw up. I had enough. Manjaro was too complicated for me to troubleshoot, I'm just a novice user. So I went for a robust distro that was simple to use. I switched to openSUSE #Tumbleweed rolling release.
When using openSUSE, I don't feel that way. i feel super relaxed about the routine #openSUSE updates. after 4 yrs running openSUSE Tumbleweed, not 1 single incident issue. that's what I call reliable and stressful #Linux distro. For me its simple because it has #yast, the command and control #GUI#management console. I don't need to know #CLI to admin my OS. I have yast. easy peasy.
PostgreSQL, Xen, glibc Update in Tumbleweed (news.opensuse.org)
This week’s openSUSE Tumbleweed snapshots were steady and there were no large updates. While updating openSUSE rolling release once a week could result in a ...
Perl, Pipewire, LibreOffice Update in Tumbleweed (news.opensuse.org)
Tumbleweed snapshots didn’t lack excitement this week as multiple packages received updates and a couple major versions arrived for openSUSE rolling release users this week.
Tumbleweed Update Highlights Redis, HarfBuzz Changes (news.opensuse.org)
This week’s openSUSE Tumbleweed updates had changes for harfbuzz, xterm, Redis, Audacity and more Snapshots have been rolling out consistently this week.
Does the RHEL Fork announcement affect openSUSE? (en.opensuse.org)
tl:dr...
Tumbleweed Boosts GNOME, MariaDB with Updates (news.opensuse.org)
A week of five openSUSE Tumbleweed snapshots brought crucial updates for key packages like GNOME, MariaDB, transactional-update and others.
Initial poking at putting together an LXQt-Wayland desktop for openSUSE (mastodon.naturalorder.me)
Woo, new adventure today. I got a wild hair, and decided to try and package a workable LXQt-Wayland for openSUSE, using labwc as the compositor. So far I can get the compositor to start? So that's progress, I suppose. Using the work done at https://github.com/stefonarch/LXQt-Wayland-files to see if I can't get something working....