Discover can't update MESA and others -Dependencies Resolution Failed

Hi guys. My tumbleweed installation can’t update Mesa using discovery:

Dependency resolution failed:

the installed Mesa-32bit-24.2.6-1699.395.pm.1.x86_64 requires ‘Mesa = 24.2.6’, but this requirement cannot be provided the installed Mesa-24.2.6-1699.395.pm.1.x86_64 requires ‘Mesa-dri = 24.2.6’, but this requirement cannot be provided the installed Mesa-24.2.6-1699.395.pm.1.x86_64 requires ‘Mesa-gallium = 24.2.6’, but this requirement cannot be provided

Is this a problem of my particular system? Or some bad dependencies tat OpenSuse will fix with future updates?

I did zypper fresh, and zypper update using Konsole

The following 10 package updates will NOT be installed:
  libgbm1 librist4 Mesa Mesa-dri Mesa-gallium Mesa-libEGL1 Mesa-libGL1 MozillaThunderbird MozillaThunderbird-openpgp-librnp vlc-codec-fluidsynth
Nothing to do.

Thanks!

Hi @novaera
Have you tried sudo zypper ref && sudo zypper dup ?

Also show:
zypper se -s Mesa-dri

And please always show it with the complete commandline…

Packman is an external repo snd not maintained by openSUSE.

This is wrong. Tumbleweed needs to be upgraded via zypper dup

@localhost:~> sudo zypper se -s Mesa-dri
[sudo] password for root:
Retrieving repository ‘Packman’ metadata …[done]
Building repository ‘Packman’ cache …[done]
Loading repository data…
Reading installed packages…

S | Name | Type | Version | Arch | Repository
—±-------------------------±-----------±---------------------±-------±---------------------
i | Mesa-dri | package | 24.2.6-1699.395.pm.3 | x86_64 | (System Packages)
v | Mesa-dri | package | 24.2.7-1699.396.pm.1 | x86_64 | Packman
v | Mesa-dri | package | 24.2.6-1699.395.pm.5 | i586 | Packman
v | Mesa-dri | package | 24.2.6-392.1 | x86_64 | Main Repository (OSS)
i | Mesa-dri-32bit | package | 24.2.6-1699.395.pm.5 | x86_64 | Packman
v | Mesa-dri-32bit | package | 24.2.6-392.1 | x86_64 | Main Repository (OSS)
| Mesa-dri-32bit-debuginfo | package | 24.2.6-1699.395.pm.5 | x86_64 | Packman
| Mesa-dri-debuginfo | package | 24.2.7-1699.396.pm.1 | x86_64 | Packman
| Mesa-dri-debuginfo | package | 24.2.6-1699.395.pm.5 | i586 | Packman
| Mesa-dri-devel | package | 24.2.7-1699.396.pm.1 | x86_64 | Packman
| Mesa-dri-devel | package | 24.2.6-1699.395.pm.1 | i586 | Packman
| Mesa-dri-devel | package | 24.2.6-392.1 | x86_64 | Main Repository (OSS)
| Mesa-dri-nouveau | package | 24.2.7-1699.396.pm.1 | x86_64 | Packman
| Mesa-dri-nouveau | package | 24.2.6-1699.395.pm.5 | i586 | Packman
| Mesa-dri-nouveau | package | 24.2.6-392.1 | x86_64 | Main Repository (OSS)
| Mesa-dri-nouveau-32bit | package | 24.2.6-1699.395.pm.5 | x86_64 | Packman
| Mesa-dri-nouveau-32bit | package | 24.2.6-392.1 | x86_64 | Main Repository (OSS)
| Mesa-drivers | srcpackage | 24.2.7-1699.396.pm.1 | noarch | Packman
| Mesa-drivers | srcpackage | 24.2.6-1699.395.pm.5 | noarch | Packman
| Mesa-drivers-debugsource | package | 24.2.7-1699.396.pm.1 | x86_64 | Packman
| Mesa-drivers-debugsource | package | 24.2.6-1699.395.pm.5 | i586 | Packman

This is interesting, I didn’t even know this existed:

Here the output:

ocalhost:~> sudo zypper ref && sudo zypper dup
Repository ‘Main Repository (NON-OSS)’ is up to date.
Repository ‘Main Repository (OSS)’ is up to date.
Repository ‘Main Update Repository’ is up to date.
Repository ‘Packman’ is up to date.
Repository ‘Open H.264 Codec (openSUSE Tumbleweed)’ is up to date.
All repositories have been refreshed.
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…
3 Problems:
Problem: 1: the installed Mesa-32bit-24.2.6-1699.395.pm.1.x86_64 requires ‘Mesa = 24.2.6’, but this requirement cannot be provided
not installable providers: Mesa-24.2.6-392.1.x86_64[download.opensuse.org-oss]

Problem: 2: the installed Mesa-24.2.6-1699.395.pm.1.x86_64 requires ‘Mesa-dri = 24.2.6’, but this requirement cannot be provided
deleted providers: Mesa-dri-24.2.6-1699.395.pm.3.x86_64
not installable providers: Mesa-dri-24.2.6-392.1.x86_64[download.opensuse.org-oss]
Mesa-dri-24.2.6-1699.395.pm.5.i586[packman]

Problem: 3: the installed Mesa-24.2.6-1699.395.pm.1.x86_64 requires ‘Mesa-gallium = 24.2.6’, but this requirement cannot be provided
deleted providers: Mesa-gallium-24.2.6-1699.395.pm.3.x86_64
not installable providers: Mesa-gallium-24.2.6-392.1.x86_64[download.opensuse.org-oss]
Mesa-gallium-24.2.6-1699.395.pm.5.i586[packman]

Problem: 1: the installed Mesa-32bit-24.2.6-1699.395.pm.1.x86_64 requires ‘Mesa = 24.2.6’, but this requirement cannot be provided
not installable providers: Mesa-24.2.6-392.1.x86_64[download.opensuse.org-oss]

Solution 1: install Mesa-24.2.6-392.1.x86_64 from vendor openSUSE
replacing Mesa-24.2.6-1699.395.pm.1.x86_64 from vendor http://packman.links2linux.de
Solution 2: deinstallation of Mesa-32bit-24.2.6-1699.395.pm.1.x86_64
Solution 3: install Mesa-24.2.6-1699.395.pm.1.i586 despite the inferior architecture
Solution 4: keep obsolete Mesa-24.2.6-1699.395.pm.1.x86_64
Solution 5: break Mesa-32bit-24.2.6-1699.395.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):

I’m new here and I am totally lost. Trying my best to keep up and have my system working.

Hey, I was running into the same issue. I believe the problem is with which vendor your system is referencing. I was able to solve it like so:

Force a refresh of the package manager and repos:
sudo zypper refresh

Allow vendor changing:
sudo zypper dup --allow-vendor-change

(optional) If you must, remove any conflicting packages and reinstall them:

sudo zypper remove Mesa-32bit Mesa Mesa-dri Mesa-gallium
sudo zypper install Mesa Mesa-32bit

Some of your packages will be downgraded but this will change in the near future as these packages become maintained by OpenSuse. The reason for the downgrade is for a couple of reasons. 1. You are actively using these packages and so upgrading them via Zypper isn’t possible. 2. The vendor being referenced has an older version of the package in question.

You can check which packages that you are actively using, of which have changed by using:

zypper ps -s

For me, it was these packages:

PID  | PPID | UID  | User  | Command                | Service
-----+------+------+-------+------------------------+--------
2004 | 1887 | 1000 | jason | Xwayland               
2079 | 1831 | 1000 | jason | ksmserver              
2081 | 1831 | 1000 | jason | kded6                  
2173 | 1831 | 1000 | jason | plasmashell            
2205 | 1831 | 1000 | jason | kactivitymanagerd      
2207 | 1831 | 1000 | jason | gmenudbusmenuproxy     
2208 | 1831 | 1000 | jason | kaccess                
2210 | 1831 | 1000 | jason | org_kde_powerdevil     
2211 | 1831 | 1000 | jason | xdg-desktop-portal-kde 
2212 | 1831 | 1000 | jason | xembedsniproxy         
2425 | 1831 | 1000 | jason | xwaylandvideobridge    
2436 | 1831 | 1000 | jason | DiscoverNotifier       
2438 | 1831 | 1000 | jason | kalendarac             
2475 | 2474 | 1000 | jason | xdg-dbus-proxy         
2478 | 2426 | 1000 | jason | bwrap                  
2514 | 1831 | 1000 | jason | lact                   
2726 | 1831 | 1000 | jason | kwalletd6              
3589 | 1831 | 1000 | jason | plasma-discover        
4678 | 1831 | 1000 | jason | firefox                
5435 | 1831 | 1000 | jason | kitty                  
5449 | 5435 | 1000 | jason | bash           

Then finally:

sudo reboot

Good luck!

I get that Linux can be overwhelming, I used to use it as a software engineer but this is the first time I switched to it full time on my personal PC.

Since you’re new, a word of advice, some people on these forums won’t be super helpful, they would rather tell you what you are doing wrong rather than what to do right. Which can be helpful for learning the hard way but this can also isolate you from the community. Stack Overflow does the same thing.

Thankfully this is a relatively minor issue to run into but when you eventually break your system (like everyone does at least once), be aware that these forums can be brutally combative.

Just as a note, you don’t need to know what all of these commands do, but I highly recommend you take some time to learn the basics of package management, repositories and what they are/how to use them. I also recommend getting used to using the terminal. The Linux Terminal is very powerful and can make or break your system.

Try to build from source whenever possible, install packages manually, and customize to your hearts desire. Stick with it and before you know it, you will be pulling Linux knowledge out of your head like its nothing.

If you need any help, feel free to reach out to me.

:slight_smile: Hey!

Well, your instructions went well up 'till the

sudo zypper remove Mesa-32bit Mesa Mesa-dri Mesa-gallium

This actually broke the system real time. Started uninstalling everything (608 packages) and the system died on me real time and froze. :slight_smile:

I am back on windows and it’ll take a while for me to try again. Just too many broken things. I really tried my best and probably should have read more information, but thing is I have 4 kids and little time to fix things.

I really appreciate your help anyway!

That’s so nice to say, and unfortunatelly I felt it myself in this very community. Unfortunatelly I need a system that just works for my specific PC configuracion and looks like is mission impossible at the moment. Back to Windows 11 for now.

May give Linux a try in the near future!

What is great about OpenSuse and just Linux in general is you can rollback to a previous version. Linux knows when you are about to break something and does a great job of keeping up with your desktop state.

Just restart or hard power off your system and in the boot screen select “Load from a read-only snapshot”. If you do not see this, then try to access a terminal where you can.

After booting into a read-only snapshot, you can open a terminal from there and list your current snapshots using snapper:

    sudo snapper list

Then you use the snapshot number to rollback to before things broke. Please make sure you select the right snapshot number.:

    sudo snapper rollback <Whatever snapshot you chose here>

for example:

    sudo snapper rollback 114

Then of course:

    sudo reboot

It happens all the time, sorry you are having so many issues, man.

Also, this is my mistake, I should’ve mentioned this in my previous message but mesa-drivers are important. Uninstalling everything like that at once can cause some issues so you have to be sure that you have conflicting packages already installed before proceeding to remove existing ones. This is a rare occurrence but it can happen.

This was just an optional thing if the previous steps gave you any errors. That was my bad for not doing my due diligence and for that I apologize.

I still recommend sticking with Linux. It can be a headache and takes some time to get used to but if you do not have the time to give, I understand wanting to go back to Windows.

1 Like

@novaera explore WSL and openSUSE on your Windows setup to get a feel for it :wink:

2 Likes

Hey! I must say this is hands down the absolute easiest way to roll back a system. I am really impressed. I have been able to just pick up a snap from yesterday night, and boom. All back to “normal”.

I really appreciate your tenacity on helping me (I really mean it) and thanks to it I am back to OpenSuse :slight_smile:

No need to apologize for anything! It is 100% my fault for not reading more documentation and understanding what was I doing. Luckily for me OpenSuse had my back covered with automatic snapshots. Again, I’m still amazed but how easy was to recover the system.

I will now concentrate again on your previous instructions and see if I can fix those mesa update issues.

Thanks to LeaveItToBeaver I am back to OpenSuse. I am going to be careful not to brake things again! :slight_smile:

I should note that you are using Packman, which seems to have jumped the gun and uploaded Mesa 24.2.7 early. This usually makes updates fail until the Tumbleweed repos catch up, which they will when 20241120 releases. Just sit tight until then.

Thanks for pointing that out! But, allow me to ask you some questions please :slight_smile:
What is packman? How did I end up having packman?

Is there a way to have the system clean and as vanilla as possible in order to avoid this issues?

Thanks!

I’m facing the same issue, but it can be resolved if I uninstall Steam apparently.

Resolving dependencies...
Computing distribution upgrade...

The following 50 packages are going to be upgraded:
  audit-rules avahi branding-openSUSE emacs-auctex grub2-branding-openSUSE libavahi-client3 libavahi-client3-32bit
  libavahi-common3 libavahi-common3-32bit libavahi-core7 libncurses6 libncurses6-32bit libOSMesa8
  libreoffice-branding-openSUSE libsignal libsolv-tools-base libvlc5 libvlccore9 libvulkan_intel libvulkan_intel-32bit
  libvulkan_radeon libvulkan_radeon-32bit Mesa-vulkan-device-select Mesa-vulkan-device-select-32bit ncurses-devel
  ncurses-utils openSUSE-release openSUSE-release-appliance-custom plymouth-branding-openSUSE python311-yt-dlp
  ruby-solv signal-desktop signal-libringrtc tack terminfo terminfo-base terminfo-iterm terminfo-screen veracrypt
  veracrypt-lang vlc vlc-codec-fluidsynth vlc-codec-gstreamer vlc-codecs vlc-noX vlc-qt vlc-vdpau
  wallpaper-branding-openSUSE yast2-qt-branding-openSUSE yt-dlp

The following product is going to be upgraded:
  openSUSE Tumbleweed  20241118-0 -> 20241119-0

The following 5 packages are going to be downgraded:
  Mesa Mesa-dri Mesa-gallium Mesa-libEGL1 Mesa-libGL1

The following 5 packages are going to change vendor:
  Mesa          http://packman.links2linux.de -> openSUSE
  Mesa-dri      http://packman.links2linux.de -> openSUSE
  Mesa-gallium  http://packman.links2linux.de -> openSUSE
  Mesa-libEGL1  http://packman.links2linux.de -> openSUSE
  Mesa-libGL1   http://packman.links2linux.de -> openSUSE

The following package is going to be REMOVED:
  steam

50 packages to upgrade, 5 to downgrade, 1 to remove, 5  to change vendor.

Package download size:   116,4 MiB

Package install size change:
              |     475,2 MiB  required by packages that will be installed
    -2,8 MiB  |  -  477,9 MiB  released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): n

I’m probably just going to wait until it magically resolves itself in the future though.

I do have Steam and actually use it every day… Could then be an issue? I want to keep using it.

OpenSUSE is pure open source. Note the name. There are codec (multimedia) that have patents or other encumbrances. Because openSUSE only allows open source in it’s distribution Packman was created to allow anyone that may want or need encumbered things to install them .

Note also the tumbleweed is cutting edge and thus more prone to these little disruptions . If you want more stable use leap. Or, we have now slowroll which updates maybe once per month rather then almost daily.