Created attachment 147393 [details] Installation attempt SUMMARY *** After updates, which include libwayland-server0, i386 support libraries are broken, as there are no i386 versions. *** STEPS TO REPRODUCE 1. Update as usual 2. Open Steam 3. Get a message that these packages need to be installed/updated : libc6:amd64 libc6:i386 libegl1:amd64 libegl1:i386 libgbm1:amd64 libgbm1:i386 libgl1-mesa-dri:amd64 libgl1-mesa-dri:i386 libgl1:amd64 libgl1:i386 steam-libs-i386:i386 OBSERVED RESULT Dependency heck occurs. See attached output from apt. The following packages have unmet dependencies: libegl1:i386 : Depends: libegl-mesa0:i386 but it is not going to be installed libgbm1:i386 : Depends: libwayland-server0:i386 (>= 1.15.0) but it is not going to be installed So: $ apt policy libwayland-server0:i386 libwayland-server0:i386: Installed: (none) Candidate: 1.18.0-1 Version table: 1.18.0-1 500 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages And $ apt policy libwayland-server0 libwayland-server0: Installed: 1.20.0-1+20.04+focal+release+build1 Candidate: 1.20.0-1+20.04+focal+release+build1 Version table: *** 1.20.0-1+20.04+focal+release+build1 500 500 http://archive.neon.kde.org/user focal/main amd64 Packages 100 /var/lib/dpkg/status 1.18.0-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Attempting to install libwayland-server0:i386 creates more dependency problems.
Created attachment 147394 [details] Attempting to install libwayland-client0:1386
I've built i386 versions here, can you install them and check they help? http://embra.edinburghlinux.co.uk/~jr/tmp/wayland.tar.gz http://embra.edinburghlinux.co.uk/~jr/tmp/wayland/
Installing the ones I built: ``` wget http://embra.edinburghlinux.co.uk/~jr/tmp/wayland-debs.tar.gz tar xf wayland-debs.tar.gz dpkg --install wayland/*deb apt -f install ```
*** Bug 451324 has been marked as a duplicate of this bug. ***
*** Bug 451312 has been marked as a duplicate of this bug. ***
*** Bug 451328 has been marked as a duplicate of this bug. ***
This seems to break lockscreen and log in and out etc
The libwayland i386 debs should now be published in neon user edition apt
libwayland build7 packages now in neon user edition installing good for me
*** Bug 451332 has been marked as a duplicate of this bug. ***
I can confirm build7 of the various wayland packages fixes this! Can Clay confirm this resolves it? :D
Resolved for me after running : sudo apt update && sudo pkcon update (unfortunately using sudo pkcon update alone did not do anything!)
Updated latest wayland libs available by discover. Can confirm bug is gone.
*** Bug 451322 has been marked as a duplicate of this bug. ***
(In reply to Aranjedeath from comment #11) > I can confirm build7 of the various wayland packages fixes this! > > Can Clay confirm this resolves it? :D Apologies for the delay. Yes, I can confirm.
I've tried updating to the latest version, and still I have this issue: LANG=C apt list -i libwayland* Listing... Done libwayland-amdgpu-client0/focal,now 1.18.0.50000-1373477 amd64 [installed,automatic] libwayland-amdgpu-client0/focal,now 1.18.0.50000-1373477 i386 [installed,automatic] libwayland-amdgpu-egl1/focal,now 1.18.0.50000-1373477 amd64 [installed,automatic] libwayland-amdgpu-egl1/focal,now 1.18.0.50000-1373477 i386 [installed,automatic] libwayland-amdgpu-server0/focal,now 1.18.0.50000-1373477 amd64 [installed,automatic] libwayland-amdgpu-server0/focal,now 1.18.0.50000-1373477 i386 [installed,automatic] libwayland-client0/focal,now 1.20.0-1+20.04+focal+release+build7 amd64 [installed] libwayland-cursor0/focal,now 1.20.0-1+20.04+focal+release+build7 amd64 [installed] libwayland-egl1/focal,now 1.20.0-1+20.04+focal+release+build7 amd64 [installed] libwayland-server0/focal,now 1.20.0-1+20.04+focal+release+build7 amd64 [installed,automatic] Is it due to amdgpu driver installed? How could this be solved?
*** Bug 451334 has been marked as a duplicate of this bug. ***
(In reply to Igor Tarasov from comment #16) > I've tried updating to the latest version, and still I have this issue: > > LANG=C apt list -i libwayland* > Listing... Done > libwayland-amdgpu-client0/focal,now 1.18.0.50000-1373477 amd64 > [installed,automatic] > libwayland-amdgpu-client0/focal,now 1.18.0.50000-1373477 i386 > [installed,automatic] > libwayland-amdgpu-egl1/focal,now 1.18.0.50000-1373477 amd64 > [installed,automatic] > libwayland-amdgpu-egl1/focal,now 1.18.0.50000-1373477 i386 > [installed,automatic] > libwayland-amdgpu-server0/focal,now 1.18.0.50000-1373477 amd64 > [installed,automatic] > libwayland-amdgpu-server0/focal,now 1.18.0.50000-1373477 i386 > [installed,automatic] > libwayland-client0/focal,now 1.20.0-1+20.04+focal+release+build7 amd64 > [installed] > libwayland-cursor0/focal,now 1.20.0-1+20.04+focal+release+build7 amd64 > [installed] > libwayland-egl1/focal,now 1.20.0-1+20.04+focal+release+build7 amd64 > [installed] > libwayland-server0/focal,now 1.20.0-1+20.04+focal+release+build7 amd64 > [installed,automatic] > > Is it due to amdgpu driver installed? How could this be solved? I don't see these packages in the Ubuntu or Neon archives. Can you paste the output of: apt-cache policy libwayland-amdgpu-client0
Still happens when I start Steam. These 2 packages wont install: libegl1:i386 libgbm1:i386 pkcon update does not fix it. Kde Neon User edition CPU: 6-Core Intel Core i7-8750H (-MT MCP-) Kernel: 5.17.0-1.2-liquorix-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.24.4 Distro: KDE neon 20.04 5.24 Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: nvidia v: 510.60.02 Display: x11 server: X.Org 1.20.13 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz OpenGL: renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 510.60.02 root@vlad:/home/vlad# apt install libegl1:i386 libgbm1:i386 Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 2 Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) libgbm1:i386 < none -> 22.0.1~kisak1~f @un puN Ib > Broken libgbm1:i386 Depends on libwayland-server0:i386 < none | 1.18.0-1 @un uH > (>= 1.15.0) Considering libwayland-server0:i386 0 as a solution to libgbm1:i386 10000 Investigating (0) libegl-mesa0:i386 < none -> 22.0.1~kisak1~f @un uN Ib > Broken libegl-mesa0:i386 Depends on libwayland-client0:i386 < none | 1.18.0-1 @un uH > (>= 1.15.0) Considering libwayland-client0:i386 0 as a solution to libegl-mesa0:i386 0 Holding Back libegl-mesa0:i386 rather than change libwayland-client0:i386 Investigating (1) libgbm1:i386 < none -> 22.0.1~kisak1~f @un puN Ib > Broken libgbm1:i386 Depends on libwayland-server0:i386 < none | 1.18.0-1 @un uH > (>= 1.15.0) Considering libwayland-server0:i386 0 as a solution to libgbm1:i386 10000 Investigating (1) libegl1:i386 < none -> 1.3.2-1~ubuntu0.20.04.2 @un puN Ib > Broken libegl1:i386 Depends on libegl-mesa0:i386 < none | 22.0.1~kisak1~f @un uH > Considering libegl-mesa0:i386 0 as a solution to libegl1:i386 9998 Reinst Failed because of libwayland-client0:i386 Considering libegl-mesa0:i386 0 as a solution to libegl1:i386 9998 Considering libegl-mesa0:i386 0 as a solution to libegl1:i386 9998 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libegl1:i386 : Depends: libegl-mesa0:i386 but it is not going to be installed libgbm1:i386 : Depends: libwayland-server0:i386 (>= 1.15.0) but it is not going to be installed E: Unable to correct problems, you have held broken packages.
I ended up having to download the updated DEBs from the server, and manually install with dpkg. It worked fine from that point on.
Seems that libegl1:i386 libgbm1:i386 depend on libwayland-server0:i386 libwayland-server0:i386 cannot be insalled since libwayland-server0:amd64 is different libwayland-server0:i386 available version is 1.18.0-1 libwayland-server0:amd64 available version is 1.20.0-1+20.04+focal+release+build8 I can downgrade everything to version 1.18.0-1 and it installs properly, but then the lock screen not working bug returns, so it's a regression from the lock screen bug.
For anyone else being lead here by googling errors: install steam from the package manager and not by downloading steam from steampowered.com to avoid this problem. Worked for me on neon 22.04.
The supported method is actually to get it from FlatHub or the Snap Store using the Discover app, not the package manager. Neon does not officially support getting non-KDE apps from the package manager, and they can break randomly like this. It's quite unpleasant when it happens so I strongly recommend using one of the supported methods of getting apps. This bug report should maybe be closed, but I'll let the Neon maintainers make that decision.
Steam is not the only popular thing that can't be easily installed, also "wine". KDE neon is even mentioned on the official site: https://wiki.winehq.org/Ubuntu libpoppler-glib8 is not the only package but also libjpeg-turbo8 (updated yesterday)
(In reply to Konrad Materka from comment #24) > Steam is not the only popular thing that can't be easily installed, also > "wine". KDE neon is even mentioned on the official site: > https://wiki.winehq.org/Ubuntu > > libpoppler-glib8 is not the only package but also libjpeg-turbo8 (updated > yesterday) The libpoppler thing with wine is still an issue. This may be me not knowing all the supported ways on Neon to install wine, but in particular I need wine 8, and only method I've found (except building it myself) is via the winehq repos. By downgrading libpoppler (which is the recommended/only method out on the Internets), I was able to eventually install winehq-staging, but I lost it again after the next update of the system.
I used Wine from apt repository, but no longer. Probably better option is to use one of the Wine managers, like: Bottles, Lutris, PlayOnLinux, etc. You can have multiple versions of Wine at the same time, create separate prefixes, easily add workarounds, dependencies etc