cross-posted from: https://discuss.online/post/34255100

Thought I’d create a distinct thread from the previous one asking about daily use, because I really do want to hear more on people’s pain points. Great to know people are generally sounding pretty positive in those posts who recently switched, but want to know your difficulties as well! This way old and new users can share their thoughts, hopefully to inspire a respectful discussion.

  • Snot Flickerman@lemmy.blahaj.zoneEnglish
    4·
    1 day ago

    Screen blanking, or rather screen blanking not functioning properly.

    I have literally spent 9 months researching every possible angle and even going as far as buying some of those Edid Emulator passthroughs for each monitor to see if those helped. Tried disabling the Kscreen manager in KDE. Tried manually controlling it via CLI and DPMS. Tried different mice and keyboards to see if it was my inputs waking it up. Tried making sure all the monitors had their auto-select input option disabled. Nope, my monitors blank for a second or two and then unblank immediately. The issue is present in both X11 and Wayland.

    I have had to jump through hoops to enable a screen saver in wayland. I have to turn my monitors off manually every night. It’s really frustrating. It seems like a really simple thing, but it’s like, literally all I want is consistent screen blanking and I have spent the better part of 9 months on and off trying to find a fucking solution to no avail. I still have no explanation for why they wake instantly, they don’t seem to be triggered by anything on the system, based on the logs.

    I even made a post asking for help regarding it here on Lemmy about six months ago. No luck.

    It drives me up the wall because I’m actually really good at researching and finding solutions for problems I’ve run into online. This one mystifies and eludes me and while seeming minor I feel like is a genuine pain in my ass.

    Related: Have an old laptop running a server OS with no GUI and have no ability to disable the monitor since technically there isn’t any monitor rendering set up, so all commands to screen blank the monitor fail because there’s technically no monitor to turn off according to the system.

    • Holytimes@sh.itjust.works
      3·
      18 hours ago

      Had a problem like this a year ago, figured out it was because I was using display port. Some weird quirk of its protocol basically fubars it.

      Switching to hdmi cables fixes the problem.

      But HDMI cables have bigger issues so I just learned to deal with the problem.

      • Markaos@discuss.tchncs.de
        1·
        9 hours ago

        Funny thing is that the same issue was resolved for me by switching the other way around - from HDMI to DisplayPort. So there’s something weirder going on than a bug in DP implementation

      • Snot Flickerman@lemmy.blahaj.zoneEnglish
        1·
        18 hours ago

        I don’t really have an option. I have four monitors and four video outputs, and only one output is HDMI. In fact, three of the cables are DP to HDMI because I don’t have any DP capable monitors. So yeah.

        Some weird quirk of its protocol basically fubars it.

        Seems like this would be something to be producing logs on for community developers in hopes of finding a solution though. Could you maybe point me to the info you found on this? I’d be interested to see if there’s any timeline that anyone is working toward in fixing it.

    • Redkey@programming.dev
      2·
      1 day ago

      I’m sorry if you’ve already checked this, but I had a similar problem with a Windows laptop recently that just would NOT stay in standby. It wasn’t a question of if, but how long.

      Eventually I found that some "Wake on IP’ settings were set to “Wake on any/all IP traffic”. I switched those off and now the thing stays in standby/screen blanked.