Skip to main content ↑ ↓
Topic: [Newbie Question] How to update Plasma to fix Lock Screen Bug (Read 359 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[Newbie Question] How to update Plasma to fix Lock Screen Bug

Hello,

New Barebones Install
I'm new to Artix and came here after reading and watching many positive reviews about it  :)
I just installed the bare-bones version with Calamares.

The Bug
As the automatic lock screen activated, I encountered the bug that prevents unlocking:
"Unlock" button on lockscreen after entering correct password

Apparently it's caused by a bug in Plasma that's been fixed now:
Fix non-functional lockscreen due to bad cherry-pick

Looking for a Best Practice Fix
So I wanted to update plasma, but wasn't sure how.
I'm assuming it's done with pacman selecting the respective Plasma package.
But this requires knowing the package name (and might not be best practice).

So I checked if there might be an answer in the help center (Meta -> Help).

I didn't find any results, though:
Quote
Search Results for 'update':
Application Manuals
  • kate - SQL Plugin
  • kinfocenter - Network Information Module
  • dolphin - Panels
  • kate - Symbol Viewer Plugin
  • kate - Document Preview Plugin
  • kwallet5 - Chapter 2. KWallet Manager
  • ksysguard - Work Space
  • ark - Working with Files
  • kcontrol5/khtml-adblock - AdBlocK Filters
  • kate - CTags Plugin

So I thought I'd ask my (presumably rather basic question) here:

  • What's the best way to fix this bug on my system?

What confused me about the bug report linked above is this attribute:
Quote
Version Fixed In:   5.23.3.1
Which is an older version than the one affected:
Quote
Version:   5.25.3

Here is my system info:

Code: [Select]
Operating System: Artix Linux x86_64
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
Kernel Version: 5.18.10-artix1-1 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 15,6 GiB of RAM
Graphics Processor: AMD Radeon RX 5500 XT


Community Edition as Workaround
Another workaround I considered:

Is it perhaps a good idea to just switch to the "it just works" Community Edition instead of this barebones edition if I don't have any prior experience?
If so, is there a command I could execute to install all the additional packages, rather than just installing the Community ISO over my current Artix partition?
Or, if I were to keep my barebones Artix, how would I best go about getting into the weed of things?


TL;DR:
I encountered a lock screen bug that came with the latest barebones Plasma Edition.
Should I fix it? Or consider switching to the Community Edition right away, if that already makes me struggle?


Thanks for reading!

Re: [Newbie Question] How to update Plasma to fix Lock Screen Bug

Reply #1 –
The bug report mentions
Quote
introduced two assignments to properties which don't exist in 5.25 yet
Maybe in recent versions those properties do exist ? In which case the fix in the commit you linked isn't necessary anymore ?

Anyway the file mentioned in the commit is here /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml

You could make a backup and then either comment or delete the two lines the commit removes.
But I suspect your problem may actually be elsewhere?

If it does work you'd need to repeat each time plasma-workspace is updated. Until it's really fixed (if it isn't  :) )

Edit: I should read more thoroughly. Just update your whole system with
Code: [Select]
 sudo pacman -Syu
and I think that will fix it..

Re: [Newbie Question] How to update Plasma to fix Lock Screen Bug

Reply #2 –
in addition to what gripped has written, as this is a rolling release, after installation and a reboot as prompted, it is essential to update fully before adding anything else and then do another reboot (your kernel is on 5.18, this machine is already on 6.0.12) - then see how it is!   Enjoy.
 

Re: [Newbie Question] How to update Plasma to fix Lock Screen Bug

Reply #3 –
Thanks to the both of you for the quick replies!

You were right, @gripped: a whole system update using `sudo pacman -Syu` did the trick.
Seems I over-complicated things by thinking I'd have to update individual packages here.

And good point, @gavincc, I should have updated right away. Rookie mistake, eh? :-[