Siduction Forum

Unpacking mesa-vulkan-drivers:i386 (25.2.1-2) ...
dpkg: error processing archive /var/cache/apt/archives/mesa-vulkan-drivers_25.2.1-2_i386.deb (--unpack):
trying to overwrite shared '/usr/share/vulkan/icd.d/intel_hasvk_icd.json', which is different from other instances of package mesa-vulkan-drivers:i386


(and similar errors for other files in that directory).

I'm not sure if this is a Debian bug or is specific to siduction since it was using its own version of mesa until 25.2.1 hit unstable.

I have the following error message
Unsatisfied dependencies:
mesa-vulkan-drivers : Breaks: mesa-vulkan-drivers:i386 (!= 25.2.1-2) but 25.1.5-0siduction1 is installed
mesa-vulkan-drivers:i386 : Breaks: mesa-vulkan-drivers (!= 25.1.5-0siduction1) but 25.2.1-2 is installed


Ah, looks like bug is known and fix is coming: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110523

Both architectures are now on version 25.2.1-2.

Quote from: ro_sid on 2025/08/30, 21:15:29
Both architectures are now on version 25.2.1-2.

That's not the problem.

Anyway, I hacked around it. I deleted all the files in /usr/share/vulkan/icd.d and then mesa-vulkan-drivers:i386 installed, but only 32-bit Vulkan was available. So I deleted all the files in /usr/share/vulkan/icd.d again and reinstalled mesa-vulkan-drivers. Now, everything worked except 32-bit stuff like Steam. So I made copies of the relevant json files for my system with 686 in the name:

cd /usr/share/vulkan/icd.d
sudo cp lvp_icd.json lvp_icd.686.json
sudo cp radeon_icd.json radeon_icd.686.json

and edited the 686 copies to change "library_arch": "64" to 32.

Now everything works.

OK, this problem caught me yesterday...

I forgot that that particular machine had i386 in (for running wine) and the dist-update stopped in the middle...  (A lot more packages besides mesa-vulkan-drivers were left unfinished.)  That computer is vital for our work, so I was going to try to follow seasons advice above to keep it working.

But, I first moved /usr/share/vulkan/icd.d to /usr/share/vulkan/icd.d-BACKUP and then "apt -f install" proceeded without errors, finishing the whole process.

Now, so far all is working, but I am afraid that this is going to come back to haunt me...

Here are the packages:


$ sudo apt policy mesa-vulkan-drivers
mesa-vulkan-drivers:
  Installed: 25.2.1-2
  Candidate: 25.2.1-2
  Version table:
*** 25.2.1-2 500
        500 http://debian-archive.trafficmanager.net/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     25.1.5-0siduction1 500
        500 https://mirror.math.princeton.edu/pub/siduction/fixes unstable/main amd64 Packages


$ sudo apt policy mesa-vulkan-drivers:i386
mesa-vulkan-drivers:i386:
  Installed: 25.2.1-2
  Candidate: 25.2.1-2
  Version table:
*** 25.2.1-2 500
        500 http://debian-archive.trafficmanager.net/debian unstable/main i386 Packages
        100 /var/lib/dpkg/status
     25.1.5-0siduction1 500
        500 https://mirror.math.princeton.edu/pub/siduction/fixes unstable/main i386 Packages


Any suggestions or ideas on how I should handle this?

@seasons: I thought of continuing with your process, but I got uncertain about the details.  Your 686 files should have "library_arch" as 64, and not 32, no?  And these were files coming from mesa-vulkan-drivers (64 bit) and not mesa-vulkan-drivers:i386, as it seems you've installed the latter last, right?

Quote from: finotti on 2025/09/02, 18:45:05
Your 686 files should have "library_arch" as 64, and not 32, no?

False. The 686 copies are for 32-bit Vulkan. The normal ones are 64-bit. This is what I ended up with (again, my system is only using radeon and llvmpipe so those are the only ones I bothered with):

radeon_icd.json
{
    "ICD": {
        "api_version": "1.4.318",
        "library_arch": "64",
        "library_path": "libvulkan_radeon.so"
    },
    "file_format_version": "1.0.1"
}

radeon_icd.686.json
{
    "ICD": {
        "api_version": "1.4.318",
        "library_arch": "32",
        "library_path": "libvulkan_radeon.so"
    },
    "file_format_version": "1.0.1"
}

lvp_icd.json
{
    "ICD": {
        "api_version": "1.4.318",
        "library_arch": "64",
        "library_path": "libvulkan_lvp.so"
    },
    "file_format_version": "1.0.1"
}

lvp_icd.686.json
{
    "ICD": {
        "api_version": "1.4.318",
        "library_arch": "32",
        "library_path": "libvulkan_lvp.so"
    },
    "file_format_version": "1.0.1"
}

Quote from: seasons on 2025/08/30, 23:17:18
[...] and edited the 686 copies to change "library_arch": "64" to 32.

Now everything works.

I performed right now an 'doas apt update && doas apt --solver 3.0 full-upgrade' and everything is ok. days before i had the same issue with mesa-vulcan.

Quote from: Isegrimm666 on 2025/09/06, 06:54:49
I performed right now an 'doas apt update && doas apt --solver 3.0 full-upgrade' and everything is ok.

There should be no need for that now. Mesa 25.2.2 is available and fixes the bug.