I'm sorry for this, it seems the libwayland update needed by Plasma breaks people who have Steam and other i386 packages installed.

A temporary fix is to download these packages I built

Code: Select all

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

I'll try and work out how to get these into the neon archive, we haven't supported i386 for a while.

kde-jriddell wrote:I'm sorry for this, it seems the libwayland update needed by Plasma breaks people who have Steam and other i386 packages installed.

A temporary fix is to download these packages I built

Code: Select all

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

I'll try and work out how to get these into the neon archive, we haven't supported i386 for a while.

Thanks man, much appreciated. I'll give it a try.

I'd have never expected Steam to be the source of those errors (<- not even sarcasm) and rather dabbled the rest of the evening with reinstalling amdgpu...

Update: @kde_jriddell - Unfortunately I still get dependency errors...

Code: Select all

(Reading database ... 237538 files and directories currently installed.)
Preparing to unpack .../libwayland-bin_1.20.0-1+20.04+focal+release+build1_i386.deb ...
Unpacking libwayland-bin:i386 (1.20.0-1+20.04+focal+release+build1) over (1.20.0-1+20.04+focal+release+build1) ...
Preparing to unpack .../libwayland-client0_1.20.0-1+20.04+focal+release+build1_i386.deb ...
Unpacking libwayland-client0:i386 (1.20.0-1+20.04+focal+release+build1) over (1.20.0-1+20.04+focal+release+build1) ...
Preparing to unpack .../libwayland-cursor0_1.20.0-1+20.04+focal+release+build1_i386.deb ...
Unpacking libwayland-cursor0:i386 (1.20.0-1+20.04+focal+release+build1) over (1.20.0-1+20.04+focal+release+build1) ...
Preparing to unpack .../libwayland-dev_1.20.0-1+20.04+focal+release+build1_i386.deb ...
Unpacking libwayland-dev:i386 (1.20.0-1+20.04+focal+release+build1) over (1.20.0-1+20.04+focal+release+build1) ...
Preparing to unpack .../libwayland-egl1_1.20.0-1+20.04+focal+release+build1_i386.deb ...
Unpacking libwayland-egl1:i386 (1.20.0-1+20.04+focal+release+build1) over (1.20.0-1+20.04+focal+release+build1) ...
Preparing to unpack .../libwayland-egl-backend-dev_1.20.0-1+20.04+focal+release+build1_i386.deb ...
Unpacking libwayland-egl-backend-dev:i386 (1.20.0-1+20.04+focal+release+build1) over (1.20.0-1+20.04+focal+release+build1) ...
Preparing to unpack .../libwayland-server0_1.20.0-1+20.04+focal+release+build1_i386.deb ...
Unpacking libwayland-server0:i386 (1.20.0-1+20.04+focal+release+build1) over (1.20.0-1+20.04+focal+release+build1) ...
Setting up libwayland-bin:i386 (1.20.0-1+20.04+focal+release+build1) ...
dpkg: error processing package libwayland-client0:i386 (--install):
 package libwayland-client0:i386 1.20.0-1+20.04+focal+release+build1 cannot be configured because libwayland-client0:amd64 is at a different version (1.18.0-1)
dpkg: error processing package libwayland-cursor0:i386 (--install):
 package libwayland-cursor0:i386 1.20.0-1+20.04+focal+release+build1 cannot be configured because libwayland-cursor0:amd64 is at a different version (1.18.0-1)
dpkg: dependency problems prevent configuration of libwayland-dev:i386:
 libwayland-dev:i386 depends on libffi-dev.
 libwayland-dev:i386 depends on libwayland-client0 (= 1.20.0-1+20.04+focal+release+build1); however:
  Package libwayland-client0:i386 is not configured yet.
 libwayland-dev:i386 depends on libwayland-cursor0 (= 1.20.0-1+20.04+focal+release+build1); however:
  Package libwayland-cursor0:i386 is not configured yet.

dpkg: error processing package libwayland-dev:i386 (--install):
 dependency problems - leaving unconfigured
dpkg: error processing package libwayland-egl1:i386 (--install):
 package libwayland-egl1:i386 1.20.0-1+20.04+focal+release+build1 cannot be configured because libwayland-egl1:amd64 is at a different version (1.18.0-1)
Setting up libwayland-egl-backend-dev:i386 (1.20.0-1+20.04+focal+release+build1) ...
Setting up libwayland-server0:i386 (1.20.0-1+20.04+focal+release+build1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.7) ...
Errors were encountered while processing:
 libwayland-client0:i386
 libwayland-cursor0:i386
 libwayland-dev:i386
 libwayland-egl1:i386



Update 2: @kde_jriddell - Scratch the above. After "apt update && pkcon update" all dependencies are solved.
Unfortunately nothing's changed, the screen locker is still broken, I still can't use the Logout/Restart/Shutdown buttons and flameshot still works extremely slow.

Thx for the answer and the explanation. I really installed steam for some gaming but i didnt thought that this would be a problem. Anyway i wait until the problem is finally fixed and there is an update in discover.

The libwayland i386 debs should now be published in neon user edition apt

plasmabug wrote:You have to manually install it:
sudo apt install libwayland-client0 libwayland-cursor0 libwayland-egl1
power options returns but still blank screen and no panel in my case

I update everything using

Code: Select all

sudo apt update

but these 3 packages don't upgrade, so I reinstall it with

Code: Select all

sudo reinstall libwayland-client0 libwayland-cursor0 libwayland-egl1

then Reboot.

Everything is working fine, with a few minor visual glitches, like messy dots on password fields.

I did it like you csandrade87,
and now everything works fine. But in Discover i get updates again for the three files

Code: Select all

libwayland-client0-1.20.0-1+20.04+focal+release+build6.amd64   wayland compositor infrastructure - client library
 libwayland-cursor0-1.20.0-1+20.04+focal+release+build6.amd64   wayland compositor infrastructure - cursor library
 libwayland-egl1-1.20.0-1+20.04+focal+release+build6.amd64      wayland compositor infrastructure - EGL library
 libwayland-server0-1.20.0-1+20.04+focal+release+build6.amd64   wayland compositor infrastructure - server library


But i will ignore them before i have the same issue again. But one question i have: How can i ignore special updates? So that they not be installed again with other updates?

Many THx

I've published another update of the libwayland packages versioned build7 which should install fine now

kde-jriddell wrote:I've published another update of the libwayland packages versioned build7 which should install fine now

Thank you! I install the new packages and everything is working fine.

[quote="jBut one question i have: How can i ignore special updates? So that they not be installed again with other updates?[/quote]

I hope Discover has an option or checkboxes that we can select with packages update or not.

csandrade87: "I hope Discover has an option or checkboxes that we can select with packages update or not."
Yes but when i uncheck them and restart discover they will be checked again.

kde-jriddell
Thx for your work, now everything works fine like all the time i use kdeneon great project!

Greetings

Hondo

Fixed with the last update. Thank you very much Neon's team!!!

Fixed with the last update. Thank you very much Neon's team!

csandrade87 wrote:

plasmabug wrote:You have to manually install it:
sudo apt install libwayland-client0 libwayland-cursor0 libwayland-egl1
power options returns but still blank screen and no panel in my case

I update everything using

Code: Select all

sudo apt update

but these 3 packages don't upgrade, so I reinstall it with

Code: Select all

sudo reinstall libwayland-client0 libwayland-cursor0 libwayland-egl1

then Reboot.

Everything is working fine, with a few minor visual glitches, like messy dots on password fields.

Second command seems to be missing "apt" from it. Anyway, reinstalled those, restarted, still no screens like log-out/restart/shutdown in KDE Neon. Also can't mine for about a month now, thinking of moving to Kubuntu I guess, since Neon become very problematic lately... but lost days and it will be quite a bit of work to move around if I can't fix all this stuff *sigh*

This fix breaks i386 support and steam complains about missing dependencies

can someone please build new versions of libwayland-server0:i386 and libwayland-client0:i386

https://bugs.kde.org/show_bug.cgi?id=451315

Sorry for the noise, I found the problem. I have an old KDE neon user edition installation from 2016 that I've upgraded continuously.
The contents of

Code: Select all

/etc/apt/sources.list.d/neon.list

Code: Select all

deb [arch=amd64] http://archive.neon.kde.org/user focal main
deb-src [arch=amd64] http://archive.neon.kde.org/user focal main


Once I removed [arch=amd64] all problems went away.
I also did a fresh neon installation in a VM to inspect the apt source and [arch=amd64] was not present, so most likely a carry on from an older version