No, there is a sort of “vendor stickyness”, if you now have Mesa from vendor “openSUSE” it will not be replaced by Mesa from vendor “packman.links2linux.de”.
That is, until you do a “zypper dup --from packman --allow-vendor-change” of course.
Please show
zypper lr -d
you are likely using a different definition (cdn?)
sean@suse:~> zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+--------------------------------------+--------------------+---------+-----------+---------+----------+--------+---------------------------------------------------------------------------------+---------
1 | NVIDIA:repo-non-free | repo-non-free | No | ---- | ---- | 99 | rpm-md | https://download.nvidia.com/opensuse/tumbleweed | NVIDIA
2 | https-download.opensuse.org-6625927a | openSUSE:Factory | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/tumbleweed/repo/oss/ |
3 | nordvpn | nordvpn | Yes | (r ) Yes | Yes | 99 | rpm-md | https://repo.nordvpn.com//yum/nordvpn/centos/x86_64 |
4 | openSUSE:repo-non-oss | repo-non-oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/non-oss | openSUSE
5 | openSUSE:repo-openh264 | repo-openh264 | Yes | (r ) Yes | Yes | 99 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed | openSUSE
6 | openSUSE:repo-oss | repo-oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/oss | openSUSE
7 | openSUSE:repo-oss-debug | repo-oss-debug | No | ---- | ---- | 99 | N/A | http://cdn.opensuse.org/debug/tumbleweed/repo/oss | openSUSE
8 | openSUSE:repo-oss-source | repo-oss-source | No | ---- | ---- | 99 | N/A | http://cdn.opensuse.org/source/tumbleweed/repo/oss | openSUSE
9 | openSUSE:update-tumbleweed | update-tumbleweed | Yes | (r ) Yes | Yes | 99 | rpm-md | http://cdn.opensuse.org/update/tumbleweed | openSUSE
10 | packman | packman | Yes | (r ) Yes | Yes | 90 | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/ |
11 | packman-essentials | packman-essentials | Yes | (r ) Yes | Yes | 90 | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/Essentials/ |
Change that to
sudo zypper dup --from http://download.opensuse.org/update/tumbleweed/
--allow-vendor-change`
1 Like
No, using cdn there, the correct syntax is:
sudo zypper dup --from openSUSE:update-tumbleweed --allow-vendor-change
2 Likes
Yes. Should I copy the content of the file?
Ok that worked thank you. Can i now do a system update and dup?
sory i replied to the wrong answer this one worked
Do you have working snapshots?
If so - go for it.
Thanks all for you help, system fully updated with mesa vendor change to opensuse using:
sudo zypper dup --from openSUSE:update-tumbleweed --allow-vendor-change
Then restart and normal zypper update & dup.
I disabled the packman & packman essentials repos in yast but obvs there are packages other than mesa in there so i guess its safe to enable?
It did not worked for me. SDDM has graphical glitches - I did not test further. I restore from snapshot.
Safe to enable, but remember that if you do a “zypper dup --from packman --allow-vendor-change” everything in the packman repo, including Mesa, will change vendor again (unless it is temporarily locked, of course). “zypper dup” without “–allo-vendor-change” is safe thanks to “vendor stickiness” though.
(BTW, I see no use of having both Packman and Packman Essentials enabled at the same time, since the latter is a subset of the former)
Had the same issue with my AMD Radeon RX Vega 64 with this mornings update.
The just released (in the main Tumbleweed update channel) Mesa version 24.1.1-385.1 seems to have fixed it now.
2 systems (laptop and desktop) both fixed by todays update.
The laptop was packman free, the desktop was using packman so I disabled packman repo and simply dup’ed with allow-vendor-change and all reverted to default OS repo.
Today update fixed the issue (without packman)
So I had an AMD iGPU, and I was affected by the borked Mesa… but all it manifested as was a corrupted user icon in the Application Launcher. None of the other issues.
That being said, using this fix removes the ability for me to use hardware acceleration for H.264 videos, which is a tad inconvenient. Is there a way to do that while keeping this fix?
Only install the codecs from Packman. And don’t switch all system packages to Packman. SDB:Installing codecs from Packman repositories - openSUSE Wiki
2 Likes
Linking this wiki article does not help in this case. Because all described methods there will definitely switch all system packages to packman…
This was already explained two days ago in this thread…
2 Likes
You don’t have to. There is a command in that wiki to only install the codecs.
You should be able to digest that information and understand how to only install the codecs.
Sorry that I tried to be helpful, I will say no more. 
Why not directly posting the relevant command instead of deliberatly breaking the systems of unexperienced users again by linking the complete wiki article?
Most users in this thread where not even able to do basic troubleshooting or recherche (no blame!). It is not expected that these users can “digest the information” as you suggest…
2 Likes