• KDE Screensaver does not start & lock the screen

    On a new installation (see also https://forum.antergos.com/topic/9985/) I can not get the screen lock to work.
    PowerDevil does dimm the screen, but the Screen Locking (System settings, workspace, desktop behavior, screen locking) does not kick in after the desired time.

    It does work when I hit Ctrl+Alt+L,
    It does work when I close the lid and re-open the lid (which is under hardware energy settings).

    I tried changing the wallpaper type (https://bbs.archlinux.org/viewtopic.php?id=236664), both to image and plain color.
    Set the activation to 1min (ask for password: immediately)

    Switched my DM from LightDM to SDDM.
    I don’t know where to look next.

    Is there anyone that can help me figure this thing out?

    There does not seem to be any mention in the journal.
    It’s just like the timer for activity does not start (But it does for the PowerDevil backlight.

    There are some errors in the journal:

    • plasmashell[748]: QXcbConnection: XCB error: 2 (BadValue), sequence: 11113, resource id: 79691781, major code: 142 (Unknown), minor code: 3
    • org_kde_powerdevil[793]: powerdevil: Can’t contact ck
    • org_kde_powerdevil[793]: powerdevil: We are now into activity “adcfdab2-360b-4c18-9848-88dd6e2c8107”
    • kdeinit5[706]: kf5.kservice.services: The desktop entry file “/usr/share/applications/org.kde.systemmonitor.desktop” has Type= “Application” but no Exec line
    • kdeinit5[706]: kf5.kservice.sycoca: Invalid Service : “/usr/share/applications/org.kde.systemmonitor.desktop”
    • kwin_x11[742]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 65463, resource id: 79691931, major code: 18 (ChangeProperty), minor code: 0
  • @herman-hofman said in KDE Screensaver does not start & lock the screen:

    org_kde_powerdevil[793]: powerdevil: We are now into activity “adcfdab2-360b-4c18-9848-88dd6e2c8107”

    Hot Keys >ALT+SPACE (Plasma Search)>screen Locking> Activation

  • @modisc
    That’s the same thing as

    • System Settings
      • Workspace
        • Desktop behavior
          • Screen locking

    It is set to:

    • Automatically (after 1 minute)
    • Require a password: immediately
    • Single image
      I picked one allready in the list, I think it’s this one: /usr/share/wallpapers/FlyingKonqui/contents/images/

    The screen does dim (after 5 minutes as per energy saving setting)

    Could this be related to Bumblebee?

    Here’s another thing I noticed.

    On a clean boot, the screensaver does not work.
    When I wake the laptop from suspend, screensaver works!
    Key difference I noticed is: ksmserver.
    When the screensaved does start, the journal has a log line :

    ksmserver[6755]: lock called
    (... powerdevil...)
    ksmserver[6755]: Lock window Id:  18874397
    dbus-daemon[457]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.47' (uid=1000 pid=6820 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
    ksmserver[6755]: CreateNotify: 18874397
    dbus-daemon[457]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
    org_kde_powerdevil[6820]: powerdevil: Udev device changed "/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight" "/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight"
    ksmserver[6755]: CreateNotify: 60817411

    Those are not present when the screen goes black because of power savings.
    And this does not always happen.
    2n time around the ksmserver is called to log me back in, but does not get the “lock called” event again.

  • Hi.
    Terribly sorry for my tardy response. I’m not always online on this forum.

    sorry for the confusion/mix-up earlier regarding plasma search.

    I understand that at least you don’t have to worry about you screen saver not working from suspend. At least at that point in time it’s functioning correctly. It just doesn’t kick in when you want it to and that is your focus here.
    Ok, so firstly:

    1. I do not know if it’s related to bumblebee.
      I would be guessing and my guess may be incorrect so I’m not going to venture into that realm as my knowledge-base will/can carry me only so far.

    2. What does come to mind is ownership conflicts. It’s not necessarily a correct answer but it is one to look / think about. I’m just throwing it out there as a possibility. Not necessarily as a concrete solution.

    3. Also, I don’t know if you have xscreensaver installed or not. It’s only a question. Don’t necessarily install if you don’t.

    4. Switching to/from LightDM/ SDDM doesn’t really offer solutions. For the most part, only graphical logins.

    5. Another thing that comes to mind are ACPI modules. ACPI

  • what shows ls ~/.config/autostart/ ? may there are some levtover from light-locker

  • xscreensaver is installed.

    Here’s the autostart:

    anydesk.desktop*  dropbox.desktop  franz.desktop

    Also, the output for systemctl: https://paste2.org/gtjB7UEE
    and ACPI: https://paste2.org/MgmUCWgM

    Strange thing is, whole weekend it was not working, now it is working as expected.
    Since I’m not using those, I switched off Franz and AnyDesk.
    I will test if those might responsible.

  • Found it, but I don’t understand it.
    When I’m running Franz, on my Desktop the screensaver behaves normally, but on my laptop, the screen does not get locked.
    When I stop Franz, locking works normal.

    I guess I will need the Franz developers for this problem.
    Thanks @Modisc for your assistance.

    I will keep you informed…

  • Left a questing in the Slack channel of Franz.
    I the meantime I switched to Rambox.
    Though I’d like to know why and how this works, I guess this is not an Antergos issue, but more with the Franz App (or one of its configured web-apps).

    Thanks @Modisc for helping!

  • Looks like Rambox has the same problem.
    Can still be the programming framework (electron) or one of the web clients.

  • When I turn off slack web interface within Rambox, the screensaver does start.
    Apparently something within the slack web interface prohibits starting the screensaver.

  • @herman-hofman said in KDE Screensaver does not start & lock the screen:

    Apparently something within the slack web interface prohibits starting the screensaver.

    I have to say that this is quite strange. I honestly wouldn’t know what to make of that.
    A script of some kind perhaps?

  • looks like what video players can do sort of, as they nned some task to prevent screensaver/locker to start if you play a video.

kde206 lock33 screensaver12 Posts 12Views 1815
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.