• 24 Posts
  • 178 Comments
Joined 2 years ago
cake
Cake day: June 17th, 2023

help-circle



  • Thanks! This is what I’m getting here. If I understand this correctly, this is a list of POSSIBLE inhibitors…not which one was triggered last time blocking the actual suspension right?

    WHO            UID  USER    PID   COMM            WHAT                                                                       WHY                                                       >
    Libvirt        0    root    77709 libvirtd        shutdown                                                                   Virtual machines need to be saved                         >
    ModemManager   0    root    1183  ModemManager    sleep                                                                      ModemManager needs to reset devices                       >
    NetworkManager 0    root    1087  NetworkManager  sleep                                                                      NetworkManager needs to turn off networks                 >
    UPower         0    root    1896  upowerd         sleep                                                                      Pause device polling                                      >
    PowerDevil     1000 timonoj 2165  org_kde_powerde handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch KDE handles power events                                  >
    Screen Locker  1000 timonoj 1878  kwin_wayland    sleep                                                                      Ensuring that the screen gets locked before going to sleep>
    
    6 inhibitors listed.
    lines 1-9/9 (END)
    

    Having a second thought about this, it looks like Screen Locker might be the culprit. But I’m not completely sure. I really could see the desktop wasn’t even locked after a whole night. So maybe it failed to trigger? How can I look at…what’s inhibiting the screen from locking, now? Just like suspension, it works when manually triggered with Meta key + L.





  • Just for clarification. In ProtonPlus, with Lutris selected on the top left, I went and clicked to install “Proton-GE-Latest, GE-Proton10-26, EM-10.0.32, EM-10.0.31, Proton-10.0.3, DXVK v2.7.1, VK3D-Proton v3.0b, VK3D-Lutris v2.14”. All of these. However, in Lutris - any game’s configuration - Runner tab, I get only: System (9.0 Ubuntu), wine-ge-8.26, and Proton-GE-Latest. There’s quite a lot of them missing. And I don’t know what triggers the ones it finds and why the others are missing.














  • Nope… I’d still say it’s on you. They really go for zero knowledge encrypted email. You are the only owner of any and all ways of recovering your account. And under no circumstances they should have any way to access your files or emails. This obviously increases privacy… But also the risk of losing everything.

    Tuta also blocks reusing addresses. It also screwed me because i used one for a quick test, and i didn’t properly keep the credentials. Now i can’t use that address ever again. I guess it makes sense to avoid impersonation.

    I’d say if this is not your threat model, you might want to check less restrictive options, maybe mailbox.org.

    And don’t get me wrong, I have a long list of pet peeves with Proton. But i think that part works as designed.