I had more or less the same problem in my laptop and in my main PC. But you can get around it just by login again and doing the update through zypper. I believe it restarts the session 3 times, and one of those after login, you just have a black screen. Use Ctrl+Alt+T to bring up the terminal and zypper dup again. After zypper is done just restart and everything will be fine.
Did this with both PCs and both are working with no problems.
Yeah, if I’d known what was going on I could have just switched to VT1 straight away and finished the update. Did the other machine fine by updating from VT1 from the start.
Further to this, my sound stopped working. “No input/output devices detected.”
Turned out if I went to the settings and turned on “show inactive devices”, then changed the Profile from ‘none’ to ‘Analog Stereo Duplex’, it went back to normal and worked. sigh
That’s what I get for a rolling release, I guess. I just hope the friends I set up on Linux Mint don’t get similar issues, since I’m not around to help when things break.
It’s currently being staged. I guess how much time for it to make to TW is mostly a matter of how well it’ll pass QA. Hopefully, it’s a matter a (very) few days.
Interesting, I can’t post here if I select “English” as the post language.
I get an error 400 HTTP status with a JSON error: “language_not_allowed”.
It works fine if I leave the language as “Undetermined”. Are these just the OpenSuse community settings?
And without YaST, you can set GRUB_TIMEOUT=0 in /etc/default/grub, then run update-bootloader or grub2-mkconfig -o /boot/grub2/grub.cfg as root.
It’s just one of the things I noticed.
I haven’t used openSUSE in a year or two, but I did really like it. You can easily adjust the Grub timeout with YaST. It was under System > Bootloader.
I ultimately stopped using openSUSE because I kept getting conflicts with zypper and Packman, but that was probably my fault. If you’re on Discord, the openSUSE server is one of the more friendly ones I’ve seen and very helpful.
Thanks, I had a look and I wanted to ask even though it is kinda obvious but I want to confirm about the “community packages”. Who is building them? The word community implies that it may be a community behind them but the naming system suggests that they are personal repos (and most probably not checked). What is the case?
They’re repos maintained by a single person, and official documentation tells you to avoid them, cause their purpose is to be a place where maintainers can break unimportant stuff.
If something is only available through community repos, the official way forward would be to submit a bug report to OpenSUSE, asking to include the package in the official repo, or to contact the maintainer and ask them to do it.
I’d keep use of community repos to a minimum and prefer first flatpak, then the experimental repo over them. No one but the maintainer themselves checks or tests the community repos for stability and compatibility.
But I’ve activated one community repo for a package that wasn’t available anywhere else (sane-airscan).
I see. Yes, it is as I had suspected and yes, as there is not any guarantee that the package is legit unless you know the maintainer, then I also think it is better to avoid. Thanks for explaining
I think the problem is that you're adding a subnet mask (/24) to your IPs. They should either be bare or have a /32 mask. The /24 mask is allowing the whole 192.168.0.1-254 address range.
Thank you so much, removing the subnet part actually fixed it!! I thought I’d have to be more specific than just the IP, but listing them bare is apparently how you do it.
openSUSE
Top