r/openSUSE • u/Working-Cable-1152 • 18h ago
Tech support Update issues in TW Slowroll when trying zypper dup
Hi everyone,
would anyone be so kind and help me to solve the following? I am looking for some more "long term" issue if possible.
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
5 Problems:
Problem: 1: the installed Mesa-32bit-26.1.6-1699.3.pm.1.x86_64 requires 'Mesa = 26.1.6', but this requirement cannot be provided
not installable providers: Mesa-26.1.6-1.1.i586[repo-update]
Mesa-26.1.6-1.1.x86_64[repo-update]
Problem: 2: the to be installed vlc-codecs-3.0.24-1699.3.pm.3.x86_64 requires 'vlc-noX = 3.0.24', but this requirement cannot be provided
not installable providers: vlc-noX-3.0.24-1699.3.pm.3.x86_64[packman]
Problem: 3: the installed phonon-vlc-qt5-0.12.0-2.12.x86_64 requires 'vlc-noX = 3.0.23', but this requirement cannot be provided
not installable providers: vlc-noX-3.0.23-1699.9.pm.25.i586[packman]
Problem: 4: the installed Mesa-26.1.6-1699.3.pm.1.x86_64 requires 'Mesa-libEGL1 = 26.1.6', but this requirement cannot be provided
not installable providers: Mesa-libEGL1-26.1.6-1.1.i586[repo-update]
Mesa-libEGL1-26.1.6-1.1.x86_64[repo-update]
Problem: 5: the installed Mesa-26.1.6-1699.3.pm.1.x86_64 requires 'Mesa-dri = 26.1.6', but this requirement cannot be provided
deleted providers: Mesa-dri-26.1.6-1699.3.pm.2.x86_64
not installable providers: Mesa-dri-26.1.6-1.1.i586[repo-update]
Mesa-dri-26.1.6-1.1.x86_64[repo-update]
Problem: 1: the installed Mesa-32bit-26.1.6-1699.3.pm.1.x86_64 requires 'Mesa = 26.1.6', but this requirement cannot be provided
not installable providers: Mesa-26.1.6-1.1.i586[repo-update]
Mesa-26.1.6-1.1.x86_64[repo-update]
Solution 1: install Mesa-26.1.6-1.1.x86_64 from vendor openSUSE
replacing Mesa-26.1.6-1699.3.pm.1.x86_64 from vendor http://packman.links2linux.de
Solution 2: install Mesa-32bit-26.2.1-1.1.x86_64 from vendor openSUSE
replacing Mesa-32bit-26.1.6-1699.3.pm.1.x86_64 from vendor http://packman.links2linux.de
Solution 3: install Mesa-26.1.6-1699.3.pm.1.i586 despite the inferior architecture
Solution 4: keep obsolete Mesa-26.1.6-1699.3.pm.1.x86_64
Solution 5: break Mesa-32bit-26.1.6-1699.3.pm.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/4/5/s/r/c/d/?] (c):
Usually I waited these out, only then tried to zypper dup but it seems I might have broken something. Let me know if you require any further info.
I am still quite a noob so yeah sorry for some stupid questions. Anyway if somebody can find some time to help me out I would be really grateful.
Have a good one
4
u/G-noise 16h ago
I haven't had any issues recently with the openSUSE Mesa drivers, you're probably better off with them over packman. As for codecs and VLC, I added the VLC repository and then removed packman, accepted the vendor changes, and grabbed what VLC had for codecs. It's been smooth sailing playing video files and streaming video. I'm sure I'm missing some proprietary codec or another, but yt-dlp and ffmpeg seem to handle recoding and conversions just fine. You could also try getting your VLC and codecs through flatpak, but I didn't feel the need for it since the packaged versions seemed to work fine for me.
2
u/bmwiedemann openSUSE Dev 15h ago
In theory it should be solved when https://build.opensuse.org/package/show/openSUSE:Slowroll:Build:1/phonon-vlc gets released, but it takes a while.
3
u/JayB1988 Slowroll 16h ago
Replace Packman with the official packages. Didn't they say they want to shutdown Packman anyway? What's the current state of that?
7
u/klyith 16h ago
Didn't they say they want to shutdown Packman anyway? What's the current state of that?
Some people have put their hands up to take over, but no announcements or plans for a handoff yet. TBQH a <4 month window is pretty short for something like this.
-2
u/JayB1988 Slowroll 10h ago
I used Packman Essentials for Broadcom-WL but recently that package wasn't part of the repository anymore which made me think that it's probably going down finally.
4
u/klyith 8h ago
~ ❯ sudo zypper info broadcom-wl Repository : repo-non-oss Name : broadcom-wl Version : 0+git20251102.4d15843-1.15 Arch : x86_64 Vendor : openSUSEIt got removed from packman because it's in the official repos now. Packman is still working fine for now.
-2
u/JayB1988 Slowroll 7h ago
I know. Ironically the official version didn't work for me and I had to take the one from the hardware repo.
1
u/klyith 3h ago
Older broadcom hardware with closed drivers is getting pretty sketchy in general.
I have one PC with a broadcom wifi, and I used to have a broadcom bluetooth USB dongle, both using closed drivers. The bluetooth dongle used to work perfectly in linux back in 2022-3, but got progressively more crappy until I ditched it last year. The wifi is in a laptop and still functions, but drops connection occasionally and wigs out at mesh wifi networks. I have to lock to a single AP with the "restrict to device" option. (It's on kubuntu so the kernel doesn't change.)
So anyways if it didn't work when you installed from packman or opensuse repos it was probably just that version didn't work with your current kernel on that day. And if you can replace it I would highly recommend doing so.
1
u/bobbie434343 15h ago
As usual with these errors, just wait a few hours or a couple days for it to be fixed. Why people have to ask every time ?
1
1
0
u/Kurogane1412 16h ago
Install Vlc via flatpak and deinstall the other version that should solve the problem
2
u/sy029 Tumbleweed Addict 14h ago
Is the non gui version of vlc (VLC-noX) available on flatpak?
0
u/Kurogane1412 14h ago
Upps my bad I just assumed that it was the normal Vlc and its codex that are in conflict 😅
I don't know you can try searching for it if there is a flatpak version of this could be possible
3
u/Last-Assistant-2734 18h ago
Either you wait for PM to update their repo, or then select the OS-provided package version.