Update blocked because conflict with Packman

Just installed Packman to see correctly some video and only few days after first compatibility problem:

~> sudo zypper dup
[sudo] password for root: 
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...
14 Problems:
Problem: 1: problem with the installed Mesa-25.0.3-1699.415.pm.1.x86_64
Problem: 2: problem with the installed Mesa-dri-25.0.3-1699.415.pm.1.x86_64
Problem: 3: problem with the installed Mesa-gallium-25.0.3-1699.415.pm.1.x86_64
Problem: 4: problem with the installed Mesa-libEGL1-25.0.3-1699.415.pm.1.x86_64
Problem: 5: problem with the installed Mesa-libGL1-25.0.3-1699.415.pm.1.x86_64
Problem: 6: problem with the installed Mesa-libva-25.0.3-1699.415.pm.1.x86_64
Problem: 7: problem with the installed Mesa-vulkan-device-select-25.0.3-1699.415.pm.1.x86_64
Problem: 8: problem with the installed libOSMesa8-25.0.3-1699.415.pm.1.x86_64
Problem: 9: problem with the installed libgbm1-25.0.3-1699.415.pm.1.x86_64
Problem: 10: problem with the installed libvdpau_r600-25.0.3-1699.415.pm.1.x86_64
Problem: 11: problem with the installed libvdpau_radeonsi-25.0.3-1699.415.pm.1.x86_64
Problem: 12: problem with the installed libvulkan_lvp-25.0.3-1699.415.pm.1.x86_64
Problem: 13: problem with the installed libvulkan_radeon-25.0.3-1699.415.pm.1.x86_64
Problem: 14: the installed calibre-8.2.1-1.1.x86_64 requires 'libQt6Gui.so.6(Qt_6.8.2_PRIVATE_API)(64bit)', but this requirement cannot be provided
deleted providers: libQt6Gui6-6.8.2-3.2.x86_64


Problem: 1: problem with the installed Mesa-25.0.3-1699.415.pm.1.x86_64
 Solution 1: install Mesa-25.0.3-412.1.x86_64 from vendor openSUSE
  replacing Mesa-25.0.3-1699.415.pm.1.x86_64 from vendor http://packman.links2linux.de
 Solution 2: keep obsolete Mesa-25.0.3-1699.415.pm.1.x86_64

Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): 

A basic search throws this thread:

You can read these wiki for good practices about using additionnal repositories.

https://en.opensuse.org/Additional_package_repositories

I recommend that you reduce Packman’s priority so that the solver calculates dependency resolution in favor of officials repositories.

sudo zypper modifyrepo -p 120 Packman

As a reminder, the higher the priority value, the lower the priority of the repository.

This issue can occur occasionally if the packman build is not done in time, and the oficial repos have a newer version. Then just wait a day or so and you can update! However this time some things have happened:

You might have hit the problem that recently mesa was moved from packman-essentials to packman-extra.

Reddit thread
Mailing list

Problem is fixed with adding the packman-extra repository:

sudo zypper ar -cfp 90 'https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/Extra/' packman-extra

However you might want to put a higher number than 90, for example 120 which lowers the repositories priority such that its packages are not chosen except for the already installed mesa. It creates the complexity that if you ever run --allow-vendor-change in the zypper dup command your mesa might get replaced by the official repos which is why I put 90 as the priority instead (same as essentials) which instead has the problem of installing other things that you might not want to have from the packman-extra instead of official repos…

I preferred it being in essentials, but not ut to me and well see if it changes again…

Does anyone ever bother to try their install without packman to see what actually works or doesn’t?

@nMax AFAIK the only reason to use Mesa from packman is if you have an AMD GPU and need enc/dec?

3 Likes

Nothing to do with amd, its for patented media codecs such as h264/h256 which are not in the official repos for reasons I’m not entirely clear about. Without the packman you cant play such codecs hardware accelerated - meaning firefox, vlc and w/e will do raw cpu software decoding which might be stuttery or not be able to keep up with higher resolutions and either way consumes a lot of battery.

One way around that is to use flatpack versions of software, as software packaged there includes those codecs for themselves. That has the disadvantage of flatpacks, but you might find it worth it if it avoids these packman repo annoyances.

@nMax not here… Newer Intel GPU’s provide guc/huc then there is H.264 provided. I use flatpak VLC… I don’t use Firefox but have no troubles in google-chrome (rpm).

But again, it’s more about the “just add”, rather than let me test what works and what doesn’t. Time and time again, users add then get frustrated when facing conflicts, when in many cases it can all be avoided these days…

Correct me if I’m wrong but how does guc avoid the issue with patents? Every computer with any form of gpu will have h264 hw enc/dec support, its about the software that makes use of the hw capabilities. If mesa cant have them, I don’t see how intel-media-driver can…

Using flatpaks will solve the issue as mentioned, but you might for good or bad reasons want to use the native package. Many things do not work at all as flatpacks, or lack features (steam broken, passkeys and such in browsers etc.).

Does chrome somehow include graphics drivers? Otherwise you are software decoding there…

More and more things are using only good codecs, so the problem is disappearing but especially for videos from cameras/mobile phones and such are still stuck on h264/h265. Playing bluray and such needs AC-1 but all of those patents have expired in most of the world so that should at least be reactivated in official mesa…

@nMax by default newer Intel GPU’s are enabled OTB, older needs to be turned on (and taints the kernel).

Again, it’s all about the end user testing to see what works for them. At present users just add without any forethought which is what I’m advocating against :wink:

Then and only then can the user be advised the best course of action for their needs etc…

1 Like

An example of what Malcolm is writing about.
Intel Haswell (some 10 yrs old):

vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Simple            :	VAEntrypointEncSlice
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileH264MultiviewHigh      :	VAEntrypointVLD
      VAProfileH264MultiviewHigh      :	VAEntrypointEncSlice
      VAProfileH264StereoHigh         :	VAEntrypointVLD
      VAProfileH264StereoHigh         :	VAEntrypointEncSlice
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileVP9Profile0            :	VAEntrypointVLD

Nvidia GeForce GTX960M

vdpauinfo
...
Decoder capabilities:

name                        level macbs width height
----------------------------------------------------
MPEG1                           0 65536  4080  4080
MPEG2_SIMPLE                    3 65536  4080  4080
MPEG2_MAIN                      3 65536  4080  4080
H264_BASELINE                  51 65536  4096  4096
H264_MAIN                      51 65536  4096  4096
H264_HIGH                      51 65536  4096  4096
VC1_SIMPLE                      1  8190  2048  2048
VC1_MAIN                        2  8190  2048  2048
VC1_ADVANCED                    4  8190  2048  2048
MPEG4_PART2_SP                  3  8192  2048  2048
MPEG4_PART2_ASP                 5  8192  2048  2048
DIVX4_QMOBILE                   0  8192  2048  2048
DIVX4_MOBILE                    0  8192  2048  2048
DIVX4_HOME_THEATER              0  8192  2048  2048
DIVX4_HD_1080P                  0  8192  2048  2048
DIVX5_QMOBILE                   0  8192  2048  2048
DIVX5_MOBILE                    0  8192  2048  2048
DIVX5_HOME_THEATER              0  8192  2048  2048
DIVX5_HD_1080P                  0  8192  2048  2048
H264_CONSTRAINED_BASELINE      51 65536  4096  4096
H264_EXTENDED                  51 65536  4096  4096
H264_PROGRESSIVE_HIGH          51 65536  4096  4096
H264_CONSTRAINED_HIGH          51 65536  4096  4096
H264_HIGH_444_PREDICTIVE       51 65536  4096  4096
...

and the Packman Mesa adds nothing.
Of course YMMV but with Intel/Nvidia sold in the last 10 yrs it is unlikely that you need the Packman Mesa. You may still need ffmpeg or VLC from Packman, but that is another story.

I’m not sure I understand how these patent bound codecs can be included in intel-media-driver or w/e nvidia driver but not mesa or ffmpeg etc.

If you still need packman for ffmpeg, vlc and other such packages to do hw acceleration then you wont have system-wide hw acceleration unless you add packman - no?

I completely agree with don’t add without test but it does sound like you will hit software decoding in some way or place unless you run packman.

Just for the sake of it, I only replied how to fix OP:s problem, I don’t recommend people to blindly add packman-extras if one wasn’t running packman-essentials before for the codecs.

After more than one month problem is still there.
Here’s a list of what I tried with no results.

  1. change Packman priority

command line seems not correct

~> sudo zypper modifyrepo -p 120 Packman
Repository Packman not found.

I changed manually Packman priority in “YaST reposistories” but this doesn’t solve the problem.
Anyway this is not the best way to act, changing priority could lead to use “original Suse” VLC thant doesn’t play several video. This is why I installed Packman.

  1. using Packman extra
    I use additional repos only if I have to because additional package often means additional problems.

  2. wait a bit, Packman will be updated.
    After a month still not true.

Nobody suggested a simple solution: allow partial update. In Discover you can’t select what you want to update. This could easily allow to exclude package that avoid update.
This should be a basic feature but it’s still unavailable.
There is and old bug still unsolved after years!

You need to do:

zypper dup --allow-vendor-change

That’ll get you back on TW packages.

Also, it’ll ask you what to do about calibre.
Select remove it. It is using an older 6.8 Qt package and you need to get the Qt 6.9 updates. I really can’t see all of it.

I can’t see the rest of it.

Add the packman extra repo and then do:

zypper dup --from packman --allow-vendor-change

That’ll get your codecs back from packman.

Also, there is now a way to use a GUI for updates. It’ll be the new update method is TW. Myrlyn works great. Under Options Menu you’ll see Allow Vendor Change and it’ll edit repos etc. It’ll make two entries on your application menu under System. One is read only so you can look around and not break anything, and the other is root mode.

It looks like Yast but it’ll do dup! On the Updates Tab there is a Package Update and Dist-Upgrade button. Make sure you use the Dist-Upgrade button.

You can see and get Myrlyn here.

You’re right, I forgot. But I would avoid going back and forth between TW and Packman repos because it will happen regularly.

Instead using Myrlyn seems much more useful. I installed it and finally I can select which packages update. With many partial updates I reduced packages to update from more than 2000 (two thousands) to “only” 200.

1 Like

Then I go back to the initial update problem:

~> sudo zypper dup
[sudo] password for root: 
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...
9 Problems:
Problem: 1: problem with the installed Mesa-25.0.3-1699.415.pm.1.x86_64
Problem: 2: problem with the installed Mesa-dri-25.0.3-1699.415.pm.1.x86_64
Problem: 3: problem with the installed Mesa-gallium-25.0.3-1699.415.pm.1.x86_64
Problem: 4: problem with the installed Mesa-libEGL1-25.0.3-1699.415.pm.1.x86_64
Problem: 5: problem with the installed Mesa-libGL1-25.0.3-1699.415.pm.1.x86_64
Problem: 6: problem with the installed Mesa-libva-25.0.3-1699.415.pm.1.x86_64
Problem: 7: problem with the installed Mesa-vulkan-device-select-25.0.3-1699.415.pm.1.x86_64
Problem: 8: problem with the installed libvulkan_lvp-25.0.3-1699.415.pm.1.x86_64
Problem: 9: problem with the installed libvulkan_radeon-25.0.3-1699.415.pm.1.x86_64

Problem: 1: problem with the installed Mesa-25.0.3-1699.415.pm.1.x86_64
 Solution 1: install Mesa-25.0.5-414.1.x86_64 from vendor openSUSE
  replacing Mesa-25.0.3-1699.415.pm.1.x86_64 from vendor http://packman.links2linux.de
 Solution 2: keep obsolete Mesa-25.0.3-1699.415.pm.1.x86_64

1 Like

This should work.

zypper dup --allow-vendor-change
  1. Set Packman priority back to 90
  2. sudo zypper dup --allow-vendor-change
  3. conflict in one (or two?) files → allow substitution
  4. update completed
    Thanks for suggestion.

Now I hope I’m still able to play all videos because it isn’t clear if I’m using Packman codecs or not. We will see.
Anyway Packman seems not so fast in updating their packages but sometime their packages are necessary. Not the best situation …

1 Like

Sorry it took so long to get you on the right path.
I’m glad you got it though.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.