LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-11-2018, 12:29 PM   #1
statguy
Member
 
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 14.2, current
Posts: 416

Rep: Reputation: 36
Screensaver sometimes does not unlock


Hello.

I am running -current and noticed recently that sometimes I cannot unlock my computer after the screensaver starts. I am running KDE. I have only noticed it when the screensaver starts automatically after a period of inactivity. It's really just a minor inconvenience (as long as I save things before I leave the computer) since I can use Ctl-Alt-Backspace to kill and restart X.

Has anyone else come across this behaviour? In the event there is a bug somewhere, any suggestions to help locate it?
 
Old 01-11-2018, 09:20 PM   #2
wagscat123
Member
 
Registered: Jan 2009
Location: Maryland-Pennsylvania border, USA
Distribution: openSUSE 42.3/15.0, Tumbleweed, OS X 10.10, Ubuntu 17.10/18.04, and Linux Mint 17.3/18.1
Posts: 699
Blog Entries: 10

Rep: Reputation: 96
These commands might give you more control over your situation:

Code:
loginctl lock-session
loginctl unlock-session
 
Old 01-11-2018, 09:36 PM   #3
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,294

Rep: Reputation: 895Reputation: 895Reputation: 895Reputation: 895Reputation: 895Reputation: 895Reputation: 895
Quote:
Originally Posted by wagscat123 View Post
These commands might give you more control over your situation:

Code:
loginctl lock-session
loginctl unlock-session
Those commands may work fine under OpenSUSE, Ubuntu or Mint.

BUT, they have zero value for Slackware, because it does not use SystemD.

Last edited by Darth Vader; 01-11-2018 at 09:39 PM.
 
1 members found this post helpful.
Old 01-11-2018, 09:43 PM   #4
FlinchX
Member
 
Registered: Nov 2017
Distribution: Slackware Linux
Posts: 201

Rep: Reputation: Disabled
At the risk of being offtopic, I must say that all screensavers I have tried are bad. All except one.

Eventually, each screensaver I tried, would get me scared. I would enable it and take a 10 minute AFK just to return and see that it segfaulted and my computer isn't locked anymore. The only screensaver that did never do this to me yet is slock from suckless tools. There's a buildscript for it on SBo. I became a big fan of it and I'm preaching it to everyone
 
1 members found this post helpful.
Old 01-12-2018, 06:53 AM   #5
statguy
Member
 
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 14.2, current
Posts: 416

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by Darth Vader View Post
Those commands may work fine under OpenSUSE, Ubuntu or Mint.

BUT, they have zero value for Slackware, because it does not use SystemD.
Thanks for that.

Let me ask you something then. Is this simply one of the things one should expect when running a pre-release such as -current (I have no problem with that) that will work itself out on the way to release? Is there any value to the community to try and locate possible causes? If so, what would you suggest (I still have lots to learn about these things, but I run -current to have the chance to learn)?
 
Old 01-12-2018, 07:19 AM   #6
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 5,066

Rep: Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864
What screensaver do you use? Have you checked your logs (using ssh or Ctrl+Alt+F1 to go to a different terminal) to see if there's any errors popping up?
 
Old 01-12-2018, 07:29 AM   #7
statguy
Member
 
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 14.2, current
Posts: 416

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by bassmadrigal View Post
What screensaver do you use? Have you checked your logs (using ssh or Ctrl+Alt+F1 to go to a different terminal) to see if there's any errors popping up?
If I read the ps output right I think these two lines answer the which screensaver question.

Code:
4602  0.3  1.8 2883372 142572 ?      Sl   08:21   0:00 /usr/lib64/kde4/libexec/kscreenlocker_greet --immediateLock
4605  0.3  0.6 365892 50816 ?        S    08:21   0:00 keuphoria.kss -window-id 79691828
Next time it fails to unlock I'll look for messages. Would they be in /var/log/messages or one of the other log files in /var/log?
 
Old 01-12-2018, 08:13 AM   #8
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,294

Rep: Reputation: 895Reputation: 895Reputation: 895Reputation: 895Reputation: 895Reputation: 895Reputation: 895
Quote:
Originally Posted by statguy View Post
Thanks for that.

Let me ask you something then. Is this simply one of the things one should expect when running a pre-release such as -current (I have no problem with that) that will work itself out on the way to release? Is there any value to the community to try and locate possible causes? If so, what would you suggest (I still have lots to learn about these things, but I run -current to have the chance to learn)?
Long story short, the loginctl command is not available under Slackware, at least unless someone run Dlackware, because it is part of SystemD.

https://www.freedesktop.org/software.../loginctl.html

I know, that can look strange for an average "Linux user", but Slackware has already diverged enough from a typical "Linux distribution" that I prefer to consider Slackware, well... just Slackware.

So, my comment was literally directed to that OpenSUSE user and his reply.


-------------------------------------------------------------
In other hand, generally speaking, I do not think that the slackware-current is for rookies and learning.

Contrary, I believe that it is for the advanced users, who willingly assume the role of beta-testers, and they are able to debug themselves the operating system, and also able to report back issues in a meaningful way.


-------------------------------------------------------------
At the end of day, I believe that what you describe can be a possible inconsistency between screensavers and ConsoleKit and/or PolicyKit, our custom thingies used to avoid the PAM and SystemD.

Unless you are able to debug further the issue, I am afraid that I cannot make a more meaningful statement, that's WHY also I do not responded (yet) to you, directly.

Last edited by Darth Vader; 01-16-2018 at 07:16 AM.
 
Old 01-12-2018, 08:17 AM   #9
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 5,066

Rep: Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864
Quote:
Originally Posted by statguy View Post
Next time it fails to unlock I'll look for messages. Would they be in /var/log/messages or one of the other log files in /var/log?
It depends on what might be locking up. If it is X, /var/log/Xorg.0.log might be helpful, if it's KDE related, it could be in /var/log/messages or ~/.xsession-errors. There could also be other logs that might provide insight, so it's best to just check whatever you can find to see if it contains something that might help figure out the issue.
 
Old 01-15-2018, 02:19 PM   #10
wagscat123
Member
 
Registered: Jan 2009
Location: Maryland-Pennsylvania border, USA
Distribution: openSUSE 42.3/15.0, Tumbleweed, OS X 10.10, Ubuntu 17.10/18.04, and Linux Mint 17.3/18.1
Posts: 699
Blog Entries: 10

Rep: Reputation: 96
Oops - I forgot that Slackware doesn't use systemd and thus loginctl. Besides my attachment to the vestigial runlevel change command "init 0", I take systemd for granted now

I googled this issue and cut-off results after 10/1/2011 (to get results for Slackware :P), and some of the commands below may do the trick for you. These are pre-systemd but mostly KDE 4-era

http://www.commandlinefu.com/command...e-lock-utility

Last edited by wagscat123; 01-15-2018 at 02:22 PM. Reason: pedantic
 
Old 01-15-2018, 05:17 PM   #11
OldHolborn
Member
 
Registered: Jul 2012
Distribution: Slackware
Posts: 171

Rep: Reputation: 147Reputation: 147
Quote:
Originally Posted by Darth Vader View Post

... but a typical "Linux distribution" has already diverged enough from Slackware that I prefer to consider Slackware, well... just Slackware.
Fixed that for you
 
3 members found this post helpful.
Old 01-16-2018, 08:02 AM   #12
statguy
Member
 
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 14.2, current
Posts: 416

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by bassmadrigal View Post
It depends on what might be locking up. If it is X, /var/log/Xorg.0.log might be helpful, if it's KDE related, it could be in /var/log/messages or ~/.xsession-errors. There could also be other logs that might provide insight, so it's best to just check whatever you can find to see if it contains something that might help figure out the issue.
I had another lock-up this morning so I logged in via a console to check the log files. I looked at ~/.xsession-errors, /var/log/messages, /var/log/Xorg.0.log, /var/log/syslog, /var/log/kdm.log and /var/log/ConsoleKit/history, /var/log/debug and the output from dmesg. I saw nothing in any of these that looked like errors from the screen lock. The only errors I did see were in kdm.log related to DBUS. Here they are.

Code:
klauncher(1495) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(1487)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"
A couple other notes:

This lock-up has (so far) only happened when the screensaver starts automatically. The other thing is after I used console to log in (Ctrl-Alt-F1), when I switched back to my KDE session, it was unlocked and I did not manually kill any processes. If I have a not hung screen lock, switching back and forth between the terminal and X session leaves the session locked.
 
Old 01-16-2018, 08:15 AM   #13
montagdude
Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 946

Rep: Reputation: 670Reputation: 670Reputation: 670Reputation: 670Reputation: 670Reputation: 670
This is the KDE screensaver, I take it? If it is problematic for you, it might be worth just disabling it altogether and trying something else, like xscreensaver, i3lock, slock, etc.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
to unlock grbiggero Linux - Newbie 1 07-05-2015 01:05 PM
[SOLVED] screensaver unlock issues pljulien Linux - Security 1 05-16-2013 02:05 PM
Unlock Dissenter LinuxQuestions.org Member Intro 0 04-03-2011 08:32 PM
gnome-screensaver does not unlock with correct password also deepclutch Debian 1 02-20-2008 01:21 PM
kde screensaver wont unlock trscookie Linux - Software 6 04-24-2006 05:52 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:19 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration