Package Conflict When using Steam in Ubuntu

[ca1ic0]

Recently , i install Ubuntu24.04 on my pc with A750 GPU,the detail of the PC is:
1.MB: Asrock B450
2.CPU:ryzen5500
3.GPU: A750
4. Memory:16GB DDR4 3400MHZ
After the install of OS, I install the computing package because i want to use oneAPI and ipex according to the official page
https://dgpu-docs.intel.com/driver/client/overview.html
And i notice that this is a big change in the page , like package name and package need to be installed.
After the install of intel package , i install Steam,and launch Steam, Steam install some i386 package and it cause conflict in APT,as follows:

Then i try on Ubuntu24.04 and Ubuntu22.04, the conflict appear in both .

The command i execute

# Install the Intel graphics GPG public key wget -qO - https://repositories.intel.com/gpu/intel-graphics.key | \ sudo gpg --yes --dearmor --output /usr/share/keyrings/intel-graphics.gpg # Configure the repositories.intel.com package repository echo "deb [arch=amd64,i386 signed-by=/usr/share/keyrings/intel-graphics.gpg] https://repositories.intel.com/gpu/ubuntu noble client" | \ sudo tee /etc/apt/sources.list.d/intel-gpu-noble.list # Update the package repository meta-data sudo apt update # Install the compute-related packages apt-get install -y libze1 intel-level-zero-gpu intel-opencl-icd clinfo

And i also found that , if i install steam first and install intel gpu package later , the conflict disappear , but the steam and game wont work well .

After the contact with intel official consumer support , he reply ：

您好，这边进一步排查了您反馈的问题判断可能是一个运行库冲突的问题。对应的计算运行库的支持属于开发方面 ，建议您可以前往githu官方页面：https://github.com/intel/compute-runtime
进行问题的提交：https://github.com/intel/compute-runtime/issues
以获取进一步的帮助。

it is about that i should invoke a issue to report the problem!
Hope it could be solved soon , thank you !

[JablonskiMateusz]

Hi @ca1ic0
Could you please share exact command lines to reproduce the issue?

[ca1ic0]

Hi @ca1ic0 Could you please share exact command lines to reproduce the issue?

OK,

1. Clean Install Of Ubuntu24.04LTS
2. based oe the doc , execute the following cmd:

# Install the Intel graphics GPG public key
wget -qO - https://repositories.intel.com/gpu/intel-graphics.key | \
  sudo gpg --yes --dearmor --output /usr/share/keyrings/intel-graphics.gpg

# Configure the repositories.intel.com package repository
echo "deb [arch=amd64,i386 signed-by=/usr/share/keyrings/intel-graphics.gpg] https://repositories.intel.com/gpu/ubuntu noble client" | \
  sudo tee /etc/apt/sources.list.d/intel-gpu-noble.list

# Update the package repository meta-data
sudo apt update

# Install the compute-related packages
apt-get install -y libze1 intel-level-zero-gpu intel-opencl-icd clinfo

3. Get the Steam Deb Package from https://store.steampowered.com/about/

dpkg -i steam_latest.deb

4. Start the Steam Client In Gnome launcher
   After that ,steam itself will execute a process of checking and installing required package which is not controlled by me.

Then you will see the error in the terminal which is invoked by Steam. And the APT package manager will report crack

[JablonskiMateusz]

if you start from clean Ubuntu 24.04 and install only libze1 intel-level-zero-gpu intel-opencl-icd clinfo
how do you conflict with libigdgmm12 ? It is not installed automatically

[ca1ic0]

if you start from clean Ubuntu 24.04 and install only libze1 intel-level-zero-gpu intel-opencl-icd clinfo how do you conflict with libigdgmm12 ? It is not installed automatically
sry ,i put the wrong picture because the problem happened month ago.

later i'll re-install the OS ，and export a more detailed log and clear screenshot.

[ca1ic0]

There is the terminal log
terminal.log

After install of intel package，install steam and launch it. I record the screen, there is the video

Uploading 无标题视频_20241217_10171558.mp4…

Uploading 无标题视频_20241217_10171558.mp4…

[ca1ic0]

video
https://github.com/user-attachments/assets/f7bda4d7-019c-461b-bd09-d5e2cccb605b

[JablonskiMateusz]

It looks like some issue with mesa package, I don't see anything related to intel-compute-runtime in that log

[ca1ic0]

It looks like some issue with mesa package, I don't see anything related to intel-compute-runtime in that log

but if i dont install libze1 intel-level-zero-gpu intel-opencl-icd clinfo , there wont be err in apt.
later i will re-install Ubuntu, and try install steam directly and record the log

[ca1ic0]

Here is the video , no err this time

1. clean install the OS
2. install the Steam
3. launch Steam
   https://github.com/user-attachments/assets/848c65f3-334f-45d8-a6e9-27d9bf6043ae

[JablonskiMateusz]

Here is the video , no err this time

1. clean install the OS
2. install the Steam
3. launch Steam
   https://github.com/user-attachments/assets/848c65f3-334f-45d8-a6e9-27d9bf6043ae

once you have this setup, please install libze1 intel-level-zero-gpu intel-opencl-icd clinfo and show results

[ca1ic0]

once you have this setup, please install libze1 intel-level-zero-gpu intel-opencl-icd clinfo and show results

1. clean install the OS
2. install libze1 intel-level-zero-gpu intel-opencl-icd clinfo
3. install the Steam
4. launch Steam
   behave is video
   https://github.com/user-attachments/assets/f7bda4d7-019c-461b-bd09-d5e2cccb605b

[ca1ic0]

And i remember the doc page before has a guide in installing i386 package for Steam Gaming , But the newer doc page delete the Guide and dont have guide in i386 package installing. I think it might be caused by the change of package name? After the change of doc page , the project xpumanager also crack in my pc (before it can work 😂although it is designed for datacenter gpu) beacause of the package name change .
i search on the web , and it might be incorrect but i remeber the later doc has something just like this

sudo dpkg --add-architecture i386 
sudo apt update
sudo apt install  -y \
  udev mesa-va-drivers:i386 mesa-common-dev:i386 mesa-vulkan-drivers:i386 \
  libd3dadapter9-mesa-dev:i386 libegl1-mesa:i386 libegl1-mesa-dev:i386 \
  libgbm-dev:i386 libgl1-mesa-glx:i386 libgl1-mesa-dev:i386 \
  libgles2-mesa:i386 libgles2-mesa-dev:i386 libosmesa6:i386 \
  libosmesa6-dev:i386 libwayland-egl1-mesa:i386 libxatracker2:i386 \
  libxatracker-dev:i386 mesa-vdpau-drivers:i386 libva-x11-2:i386

[eero-t]

3.GPU: A750
...

1. Clean Install Of Ubuntu24.04LTS
   ...
   After the install of OS, I install the computing package because i want to use oneAPI and ipex according to the official page
   https://dgpu-docs.intel.com/driver/client/overview.html

@ca1ic0 Ubuntu 24.04 has new enough GPU drivers to support A750.

So you do not need to (and should avoid) installing alternative driver versions from Intel repositories.

While user-space drivers in Intel repository offer the same functionality as ones in Ubuntu repositories, they are NOT interchangeable [1].

If some software requires driver package & lib names available only from Intel repo packages, I think it's better to file a bug that they should provide also versions built against distro package & lib names.

(I filed one for XPUManager: intel/xpumanager#89)

While Intel package & lib names came first, and distros chose to use different ones later, I think packages in Intel package repository should be updated to align with distro conventions, and provide transition packages for people upgrading from the old Intel package & lib names, to avoid these kind of conflicts.

---

[1] Issues:

• They are compiled for the uAPI of the (out-of-tree) i915 DKMS GPU kernel driver in that same repository, so they may not work with i915 distro kernel
• They can have different package names, and different library file names. While OpenCL and Level-Zero API frontends should abstract this, some SW packages add direct dependencies to backend libraries files and package names, and break when those change
• They may have different package name, but same i.e. conflicting library names, meaning that package installs fail

[ca1ic0]

3.GPU: A750
...

1. Clean Install Of Ubuntu24.04LTS
   ...
   After the install of OS, I install the computing package because i want to use oneAPI and ipex according to the official page
   https://dgpu-docs.intel.com/driver/client/overview.html

@ca1ic0 Ubuntu 24.04 has new enough GPU drivers to support A750.

So you do not need to (and should avoid) installing alternative driver versions from Intel repositories.

While user-space drivers in Intel repository offer the same functionality as ones in Ubuntu repositories, they are NOT interchangeable [1].

If some software requires driver package & lib names available only from Intel repo packages, I think it's better to file a bug that they should provide also versions built against distro package & lib names.

(I filed one for XPUManager: intel/xpumanager#89)

While Intel package & lib names came first, and distros chose to use different ones later, I think packages in Intel package repository should be updated to align with distro conventions, and provide transition packages for people upgrading from the old Intel package & lib names, to avoid these kind of conflicts.

[1] Issues:

• They are compiled for the uAPI of the (out-of-tree) i915 DKMS GPU kernel driver in that same repository, so they may not work with i915 distro kernel
• They can have different package names, and different library file names. While OpenCL and Level-Zero API frontends should abstract this, some SW packages add direct dependencies to backend libraries files and package names, and break when those change
• They may have different package name, but same i.e. conflicting library names, meaning that package installs fail

Ok, i Got it . This time i didn't add intel repo in apt and install media package from the ubuntu official repo, steam install works fine. Maybe the document could be improved like added some notice or more information?

[ca1ic0]

later i will try steam gaming

[JablonskiMateusz]

once you have this setup, please install libze1 intel-level-zero-gpu intel-opencl-icd clinfo and show results

1. clean install the OS
2. install libze1 intel-level-zero-gpu intel-opencl-icd clinfo
3. install the Steam
4. launch Steam
   behave is video
   https://github.com/user-attachments/assets/f7bda4d7-019c-461b-bd09-d5e2cccb605b

I understand the scenario here, but you have some issues with packages needed for steam, and if it is not visible without compute runtime, it should also manifest in reverse way, i.e. if you have successfully installed stream and then you install compute-runtime packages, there should be some conflict on packages, I wonder which packages are conflicting

[eero-t]

This time i didn't add intel repo in apt and install media package from the ubuntu official repo, steam install works fine. Maybe the document could be improved like added some notice or more information?

The instructions at start of that doc did state that you should use distro packages (as your HW is supported):
https://dgpu-docs.intel.com/driver/client/overview.html#selecting-the-right-operating-system-version

I understand the scenario here, but you have some issues with packages needed for steam, and if it is not visible without compute runtime, it should also manifest in reverse way, i.e. if you have successfully installed stream and then you install compute-runtime packages, there should be some conflict on packages, I wonder which packages are conflicting

@JablonskiMateusz here's somewhat similar discussion in XPUM ticket: intel/xpumanager#74 (comment)

Because there's no better Intel GPU monitoring solution, people install xpu-smi, but as it's not as actively maintained as compute-runtime project, it has deps to conflicting packages.

=> IMHO zello_sysman binary could be provided by default compute-runtime L0 install, so that people have at least some working GPU metrics tool along with the driver package.

PS. XPUM is a bit awkward for distros. It install Python modules with pip, and last I checked, depends on versions that would need to be come from multiple Ubuntu versions, partly because Ubuntu includes completely broken ones: https://bugs.launchpad.net/ubuntu/+source/grpc/+bug/1971114

[JablonskiMateusz]

The XPUM issue sounds like a separate problem.

Let me summarize what was concluded here. Please correct me if I missed anything.

1. @ca1ic0 states that there is conflict on packages when compute-runtime is installed and then steam is installed/used
2. @eero-t states there is package conflict in XPUM
3. @eero-t states that zello_sysman binary could be somehow delivered to provide very basic GPU metrics tool

Regarding 1.

1. issue is not seen if compute-runtime is not installed
2. @ca1ic0 please provide dpkg installation error log to show which packages are conflicting
3. @ca1ic0 please try to install compute-runtime packages after stream is working fine - if there is still an issue, please share installation log

Regarding 2.

1. The conflict is on igsc package which is not a part of compute-runtime releases
2. @eero-t please create corresponding issue in https://github.com/intel/igsc

Regarding 3.

1. The idea sounds reasonable
2. @eero-t please create a separate issue(feature request) in our GitHub so we can discuss it internally

[eero-t]

@eero-t please create a separate issue(feature request) in our GitHub so we can discuss it internally

Done: #787

[ca1ic0]

The XPUM issue sounds like a separate problem.

让我总结一下这里的结论。如果我遗漏了什么，请纠正我。

1. @ca1ic0 states that there is conflict on packages when compute-runtime is installed and then steam is installed/used
2. @eero-t states there is package conflict in XPUM
3. @eero-t states that zello_sysman binary could be somehow delivered to provide very basic GPU metrics tool

Regarding 1.

1. issue is not seen if compute-runtime is not installed
2. @ca1ic0 please provide dpkg installation error log to show which packages are conflicting
3. @ca1ic0 please try to install compute-runtime packages after stream is working fine - if there is still an issue, please share installation log

Regarding 2.

1. The conflict is on igsc package which is not a part of compute-runtime releases
2. @eero-t please create corresponding issue in https://github.com/intel/igsc

Regarding 3.

1. The idea sounds reasonable
2. @eero-t please create a separate issue(feature request) in our GitHub so we can discuss it internally

OK， i will provide a more detailed log in 2025.1.1 vacation.
And thanks for your support!