Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Can't unlock screen in plasma5
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
est921
n00b
n00b


Joined: 20 Dec 2015
Posts: 28

PostPosted: Wed Oct 19, 2016 5:36 pm    Post subject: Can't unlock screen in plasma5 Reply with quote

Hi, have merged plasma 5.8.0, and while most things works as expected I cannot unlock the desktop again after locking it. It simply returns the message "Unlock failed", even when I enter the correct password. I do not use systemd. Any advice?
Back to top
View user's profile Send private message
Roman_Gruber
Advocate
Advocate


Joined: 03 Oct 2006
Posts: 3806
Location: Austro Bavaria

PostPosted: Wed Oct 19, 2016 5:38 pm    Post subject: Reply with quote

a known bug with the screensaver in kde when you are not using systemd
won t fix, i have read about it yesterday here in another post.
Back to top
View user's profile Send private message
est921
n00b
n00b


Joined: 20 Dec 2015
Posts: 28

PostPosted: Wed Oct 19, 2016 5:41 pm    Post subject: Reply with quote

Roman_Gruber wrote:
a known bug with the screensaver in kde when you are not using systemd
won t fix, i have read about it yesterday here in another post.


That's reassuring... Thank you for such a quick response though
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Wed Oct 19, 2016 6:52 pm    Post subject: Reply with quote

...a response which is wrong. It's not a bug specific to non-systemd use, there is just no graceful way to solve it when it happens (and it happens on systemd as well).

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

One thing that can trigger this is updating Qt, Frameworks or Plasma from within a running session. If this does not unlock ever for you, there's a different setup issue though - normally it would work, regardless of your init system.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 5592

PostPosted: Wed Oct 19, 2016 7:15 pm    Post subject: Reply with quote

asturm wrote:
there is just no graceful way to solve it when it happens

But there is one:
Code:
emerge -C plasma
emerge xscreensaver


KDE, working software. Pick one.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Wed Oct 19, 2016 7:32 pm    Post subject: Reply with quote

@est921: Don't let yourself get distracted by those guys, there's no reason the lockscreen should not work for you. There likely is an issue in the underlying stack, check the bug here: https://bugs.gentoo.org/show_bug.cgi?id=564618#c11

Btw, you mention emerging Plasma 5.8.0, yet we have 5.8.2 already as of yesterday. ;)
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
est921
n00b
n00b


Joined: 20 Dec 2015
Posts: 28

PostPosted: Thu Oct 20, 2016 10:11 am    Post subject: Reply with quote

Thanks for the link asturm, setting suid on
Code:
/usr/libexec/kcheckpass
as someone suggested in the bugtracker did help. Don't know if that's a safe thing to do though
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Thu Oct 20, 2016 10:33 am    Post subject: Reply with quote

It's certainly not the way it should be, but the fallback solution for kscreenlocker on systems without PAM.

Some people have issues with >=sys-libs/pam-1.2.1-r1 (filecaps does not work in some cases).
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Roman_Gruber
Advocate
Advocate


Joined: 03 Oct 2006
Posts: 3806
Location: Austro Bavaria

PostPosted: Fri Oct 21, 2016 7:58 am    Post subject: Reply with quote

asturm wrote:
...a response which is wrong. It's not a bug specific to non-systemd use, there is just no graceful way to solve it when it happens (and it happens on systemd as well).

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

One thing that can trigger this is updating Qt, Frameworks or Plasma from within a running session. If this does not unlock ever for you, there's a different setup issue though - normally it would work, regardless of your init system.


Whatever I love your comment ... Especially always the same offense that guys do not read posts or give improper answers

Quote:
We expect the non-logind users to add code for this


When you had read the bug than you would not have said the stuff above

I gave a response to the inital topic, there was no discussion or topic if it happens on systemd crap anyway

Does not change the fact that the screensaver is broken or with flaws.

I use xscreensaver myself for at least three years without flaws. xscreensaver works for myself

--

Regarding your screensaver issue and back to your topic.

The xscreensaver is a basic packag which works usually. It has many features or more features compared to gnome / kde years ago. I have not used installed recent screensaver packages from these desctop environments. PErsonally I see those additional screensaver packages as lint / useless packages as the xscreensaver package is already provided and integrated.

You may just as suggested unmerge the kde screensaver and use the xscreensaver instead


Last edited by Roman_Gruber on Fri Oct 21, 2016 8:30 am; edited 1 time in total
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Fri Oct 21, 2016 8:28 am    Post subject: Reply with quote

I know the bug very well, the cause is not in kscreenlocker, but in the underlying stack. You keep talking about a screensaver where there is no screensaver. It's fine if you use xscreensaver, just be aware of its security issues.

If you had read the above messages, you would have seen that the issue is actually solved.

Roman_Gruber wrote:
there was no discussion or topic if it happens on systemd crap anyway

Roman_Gruber wrote:
a known bug with the screensaver in kde when you are not using systemd

...you do read your own messages?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum