Mein #Gnome unter #OpenSuse ist kaputt, weil ich so lange keine Updates mehr eingespielt hatte.
Hab dann einen neuen Desktop installiert, weil ich sonst keinen grafischen Desktop mehr hatte.
Wie kann ich Gnome reparieren?
Reicht es, wenn ich über #YAST Gnome (Basic) und Gnome (Wayland) lösche und neu installiere oder mache ich damit ggf. mehr kaputt?
Welches von den beiden Gnome benötige ich?
Mein #Gnome unter #OpenSuse ist kaputt, weil ich so lange keine Updates mehr eingespielt hatte.
Hab dann einen neuen Desktop installiert, weil ich sonst keinen grafischen Desktop mehr hatte.
Wie kann ich Gnome reparieren?
Reicht es, wenn ich über #YAST Gnome (Basic) und Gnome (Wayland) lösche und neu installiere oder mache ich damit ggf. mehr kaputt?
Welches von den beiden Gnome benötige ich?
Apparently my OS install is eight and a half years old 😁 I know this because someone in the forum thread noticed that I still had ffmpeg 4 installed rather than ffmpeg 8 and asked how old my system was.
`sudo btrfs subvolume show /.snapshots|grep Creation` gives you a creation date for btrfs subvolumes (which Snapper uses for snapshots). And mine reports October 2017.
This is the power of rolling distros and filesystem-level snapshots!
(My system may actually be a bit less than that, because I might have had to reinstall once and just reused the volumes - but that's the only date that I can find)
Liegt es an #Leap, oder an mir?
Wer mich kennt, der weiß das ich viel und gerne #openSUSE #Tumbleweed benutze. Nun habe ich als Hauptsystem ein Rechner mit vorinstallierten Leap ergattert und stoße immer wieder auf Probleme, die müsselig per Terminal aus dem Weg geschaffen werden müssen. Soviel gebastel war ich unter #Tumbleweed nicht gewohnt. Kleinste Änderungen an der Firewall, dem CUP-Server, der Repository-Liste usw.
Ugh, I guess the snapper version I tried to restore didn't actually revert the bad changes I made. Despite following instructions, so that was neat.
I will have to accept the fact that I did an oopsie which cannot be recovered; thankfully, I simply reinstalled openSUSE Tumbleweed.
However, apparently, I lost all my pictures despite saving them on a different drive. That's weird and makes me upset. All my documents, music, and videos are alive and kicking at least. Big sad, but I'll live.
Found someone suggesting that it could be libav. But I've got gstreamer-plugins-libav, which is pulling in libavcodec62.
And if I re-enable Packman and install their bad/ugly-codecs then it STILL doesn't work. I'm missing something and I can't see what.
Balls and bugger it. Time for a rollback. Thank goodness for Snapper! #openSUSE #Tumbleweed #Btrfs
Well, this is fun.
I've got the `repo-openh264` repo configured (codecs.opensuse.org) and it has a `gstreamer-plugin-openh264` package available. But it's only v1.22 and GStreamer is at 1.28 in #openSUSE #Tumbleweed now. And if I install it then one of the conflicts indicates that it's now bundled in `gstreamer-plugins-bad` (and I can see a SO file in the list)
That repo has the `mozilla-openh264` package as well.
There's a different version of of libopenh264 with a version string that includes `noopenh264`, but it's from repo-oss.
If I run `ffmpeg -codecs | grep 264` then I get a line ` ..V.LS h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10`, so it knows SOMETHING about the codec.
But even after switching packages, ffplay still gives "No decoder could be found for codec h264" and Videos gives "requires a H.264 (Baseline Profile) decoder plugin, which is not installed" 😐
And I can't just uninstall and reinstall the whole of GStreamer because that rips out loads of other packages with it (and ignoring the dependencies defeats the idea of "try to clean it up")
Robyn
RSS Tecnolocuras
IBBoard
Andreas B. ن
Crest of Light
mickey
openSUSE en Español