Re: [SOLVED] Re: Automatic screen locking
Il 02/09/20 16:47, local10 ha scritto: Aug 20, 2020, 01:56 by loca...@tutanota.com: Aug 18, 2020, 19:22 by ago...@gmail.com: an example: https://lists.debian.org/debian-kde/2019/11/msg7.html You were right, it was juk that was preventing automatic screen locking from working correctly. A bit strange though as juk controls are on the lock page and one can control juk even if the system is locked. Thanks to everyone who responded. ;) https://bugs.kde.org/show_bug.cgi?id=421011 -- Saluti, Luca Pedrielli
[SOLVED] Re: Automatic screen locking
Aug 20, 2020, 01:56 by loca...@tutanota.com: > Aug 18, 2020, 19:22 by ago...@gmail.com: > >> an example: >> >> https://lists.debian.org/debian-kde/2019/11/msg7.html >> >> You were right, it was juk that was preventing automatic screen locking from working correctly. A bit strange though as juk controls are on the lock page and one can control juk even if the system is locked. Thanks to everyone who responded.
Re: Automatic screen locking
Il 20/08/20 03:56, local10 ha scritto: Aug 18, 2020, 19:22 by ago...@gmail.com: an example: https://lists.debian.org/debian-kde/2019/11/msg7.html I'm running sddm but do not have ktorrent installed. More info: $ cat ~/.config/kscreenlockerrc [$Version] update_info=kscreenlocker.upd:0.1-autolock [Daemon] LockGrace=30 Timeout=1 $ cat ./.xsession-errors | grep -i lock 2020-08-19T21:16:39 Checking update-file '/usr/share/kconf_update/kscreenlocker.upd' for new updates 2020-08-19T21:16:39 Checking update-file '/usr/share/kconf_update/webengineurlinterceptoradblock.upd' for new updates Configuring Lock Action org.kde.plasmaquick: New Applet "Digital Clock" with a weight of 54 org.kde.plasmaquick: Delayed preload of "Digital Clock" after 3.347 seconds org.kde.plasmaquick: Applet "Digital Clock" loaded after 163 msec $ cat ./.xsession-errors | grep -i screen 2020-08-19T21:16:39 Checking update-file '/usr/share/kconf_update/kscreenlocker.upd' for new updates kscreen.kded: UPower not available, lid detection won't work kscreen.kded: PowerDevil SuspendSession action not available! kscreen: Requesting missing EDID for outputs (81) powerdevil: Handle button events action could not check for screen configuration $ cat ./.xsession-errors | grep -i err Qt: Session management error: networkIdsList argument is NULL qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 814, resource id: 46137352, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 815, resource id: 46137352, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2533, resource id: 65011717, major code: 18 (ChangeProperty), minor code: 0 org.kde.pim.akonadicore: Job error: "" for collection: QVector() libepub (II): Found containerr libepub (II): Found containerr qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3136, resource id: 10485765, major code: 18 (ChangeProperty), minor code: 0 Qt: Session management error: networkIdsList argument is NULL qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8191, resource id: 2097194, major code: 18 (ChangeProperty), minor code: 0 : QML QQuickLayoutAttached: Binding loop detected for property "preferredHeight" qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2731, resource id: 10485763, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2759, resource id: 54525958, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2765, resource id: 56623110, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2776, resource id: 48234502, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2808, resource id: 58720263, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2935, resource id: 71303174, major code: 142 (Unknown), minor code: 3 powerdevil: Added interrupt session ... See https://pastebin.com/x66hiscg for complete .xsession-errors file. Thanks At this point I don't know how to help you anymore :( However you may have to confront the running programs, configuration files and log files with the new working user. -- Saluti, Luca Pedrielli
Re: Automatic screen locking
Aug 18, 2020, 19:22 by ago...@gmail.com: > an example: > > https://lists.debian.org/debian-kde/2019/11/msg7.html > > I'm running sddm but do not have ktorrent installed. More info: $ cat ~/.config/kscreenlockerrc [$Version] update_info=kscreenlocker.upd:0.1-autolock [Daemon] LockGrace=30 Timeout=1 $ cat ./.xsession-errors | grep -i lock 2020-08-19T21:16:39 Checking update-file '/usr/share/kconf_update/kscreenlocker.upd' for new updates 2020-08-19T21:16:39 Checking update-file '/usr/share/kconf_update/webengineurlinterceptoradblock.upd' for new updates Configuring Lock Action org.kde.plasmaquick: New Applet "Digital Clock" with a weight of 54 org.kde.plasmaquick: Delayed preload of "Digital Clock" after 3.347 seconds org.kde.plasmaquick: Applet "Digital Clock" loaded after 163 msec $ cat ./.xsession-errors | grep -i screen 2020-08-19T21:16:39 Checking update-file '/usr/share/kconf_update/kscreenlocker.upd' for new updates kscreen.kded: UPower not available, lid detection won't work kscreen.kded: PowerDevil SuspendSession action not available! kscreen: Requesting missing EDID for outputs (81) powerdevil: Handle button events action could not check for screen configuration $ cat ./.xsession-errors | grep -i err Qt: Session management error: networkIdsList argument is NULL qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 814, resource id: 46137352, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 815, resource id: 46137352, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2533, resource id: 65011717, major code: 18 (ChangeProperty), minor code: 0 org.kde.pim.akonadicore: Job error: "" for collection: QVector() libepub (II): Found containerr libepub (II): Found containerr qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3136, resource id: 10485765, major code: 18 (ChangeProperty), minor code: 0 Qt: Session management error: networkIdsList argument is NULL qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8191, resource id: 2097194, major code: 18 (ChangeProperty), minor code: 0 : QML QQuickLayoutAttached: Binding loop detected for property "preferredHeight" qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2731, resource id: 10485763, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2759, resource id: 54525958, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2765, resource id: 56623110, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2776, resource id: 48234502, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2808, resource id: 58720263, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2935, resource id: 71303174, major code: 142 (Unknown), minor code: 3 powerdevil: Added interrupt session ... See https://pastebin.com/x66hiscg for complete .xsession-errors file. Thanks
Re: Automatic screen locking
Il 18/08/20 19:54, local10 ha scritto: Aug 18, 2020, 17:33 by ago...@gmail.com: maybe is running a program that prevent automatic screen locking? I don't recall specifically installing anything like that. Unless something was installed as a part of recommended packages and then somehow got activated. Thanks, an example: https://lists.debian.org/debian-kde/2019/11/msg7.html -- Saluti, Luca Pedrielli
Re: Automatic screen locking
Aug 18, 2020, 17:33 by ago...@gmail.com: > maybe is running a program that prevent automatic screen locking? > I don't recall specifically installing anything like that. Unless something was installed as a part of recommended packages and then somehow got activated. Thanks,
Re: Automatic screen locking
Il 18/08/20 18:57, local10 ha scritto: Aug 18, 2020, 12:51 by perezme...@gmail.com: I haven't noticed that myself. Try creating a new user to see if it's a configuration issue or a system issue. For a new user automatic screen locking work properly, that is, the system locks the screen after a specified amount of time. Not sure why it doesn't do this for my regular account though. Thanks, maybe is running a program that prevent automatic screen locking? -- Saluti, Luca Pedrielli
Re: Automatic screen locking
Aug 18, 2020, 12:51 by perezme...@gmail.com: > I haven't noticed that myself. Try creating a new user to see if it's > a configuration issue or a system issue. > For a new user automatic screen locking work properly, that is, the system locks the screen after a specified amount of time. Not sure why it doesn't do this for my regular account though. Thanks,
Re: Automatic screen locking
Hi! On Mon, 17 Aug 2020 at 16:13, local10 wrote: > > Aug 13, 2020, 20:19 by loca...@tutanota.com: > > > > > > >> Hi, > >> > >> For some reason automatic screen locking stopped working for me. It used > >> to work some time back but then just stopped. I currently have the "Lock > >> screen automatically after" set to one minute (for test purposes) but it > >> just doesn't lock the screen even after 5 minutes. I can still lock the > >> screen manually though. > >> > >> Any ideas? Thanks > >> > > More info: > > > > # echo "It's a Debian Buster PC"; uname -a > > It's a Debian Buster PC > > Linux tst 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64 > > GNU/Linux > > > > # aptitude show kde-standard > > Package: kde-standard > > Version: 5:102 > > State: installed I haven't noticed that myself. Try creating a new user to see if it's a configuration issue or a system issue. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Re: Automatic screen locking
Aug 13, 2020, 20:19 by loca...@tutanota.com: > > >> Hi, >> >> For some reason automatic screen locking stopped working for me. It used to >> work some time back but then just stopped. I currently have the "Lock screen >> automatically after" set to one minute (for test purposes) but it just >> doesn't lock the screen even after 5 minutes. I can still lock the screen >> manually though. >> >> Any ideas? Thanks >> > More info: > > # echo "It's a Debian Buster PC"; uname -a > It's a Debian Buster PC > Linux tst 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64 > GNU/Linux > > # aptitude show kde-standard > Package: kde-standard > Version: 5:102 > State: installed > Anybody? Thanks
FWD: Automatic screen locking
> Hi, > > For some reason automatic screen locking stopped working for me. It used to > work some time back but then just stopped. I currently have the "Lock screen > automatically after" set to one minute (for test purposes) but it just > doesn't lock the screen even after 5 minutes. I can still lock the screen > manually though. > > Any ideas? Thanks > More info: # echo "It's a Debian Buster PC"; uname -a It's a Debian Buster PC Linux tst 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64 GNU/Linux # aptitude show kde-standard Package: kde-standard Version: 5:102 State: installed
Automatic screen locking
Hi, For some reason automatic screen locking stopped working for me. It used to work some time back but then just stopped. I currently have the "Lock screen automatically after" set to one minute (for test purposes) but it just doesn't lock the screen even after 5 minutes. I can still lock the screen manually though. Any ideas? Thanks
