Hey look, it’s one of the folks I’m talking about:
I’m assuming you’re trying to turn your monitor off while there is still an active HDMI signal for some reason? Otherwise why wouldn’t you just let the monitor put itself to sleep when it detects no signal like everyone else I know?
Nah, I’m trying to let the monitors put themselves to sleep, genius. That’s what’s not working. There shouldn’t still be an active HDMI signal. Disabling DCC/CI doesn’t fix the problem, either, it just goes back to the monitors not actually ever shutting off, just turning off for a moment and then coming back on, with plasmashell crashing instead of the power monitor. I don’t care at all about controlling monitor brightness with DCC/CI but when the defaults cause crashes that’s an issue.
This is an out-of-the-box fresh install with no old dotfiles moved, complete refresh. These were the defaults I was given. Deciding to set your monitors to power down after 10 mins of inactivity shouldn’t be causing crashes. i shouldn’t have to manually turn my monitors off or do hacky shit with xscreensaver to get it working in fucking wayland just to not have monitor burn-in
I’ve not experienced any of this across many different linux systems… The default screensaver and lock screen work perfectly fine in KDE Plasma, and my monitors turn off when they should. I’ve even had no issues with HDR and variable refresh rates. (And the DCC/CI brightness controls for my TV work out of the box unlike windows).
I’m sorry you haven’t had the same experience. It almost seems like there could be something broken with your hardware if your monitor is continuing to detect a signal after things are asleep.
I’m sorry you made an ass out of yourself for making an assumption.
The thing is, Grandma won’t know what the fuck is going on or what DCC/CI even is. Grandma is poor and using pieced together old systems and shitty old monitors.
I’m not looking for a solution, I’m looking for people like you to stop making ass assumptions and get off your high fucking horse assuming the user must be at fault only realizing you’re wrong and being an ass after you already did it.
Look, I was trying to understand your issue, since I’m a developer and am curious about this kind of thing. I stated my assumptions to try and make my initial point of view clear and give you the opportunity to provide more information if my assumptions were wrong.
From what you’ve stated I don’t believe your problem is related to DCC/CI at all, and is likely something else with sleep states failing. Whatever is failing on your system is extremely unusual and is not something that I would expect a “Grandma” to ever encounter. If anything, older hardware should be better supported.
Look, you have zero attempt at self reflection here, this conversation is over. You made an assumption that the user was at fault and were wrong. Eat it. We aren’t in a fucking bug thread with my logs. Developers got no fucking social skills.
Hey look, it’s one of the folks I’m talking about:
Nah, I’m trying to let the monitors put themselves to sleep, genius. That’s what’s not working. There shouldn’t still be an active HDMI signal. Disabling DCC/CI doesn’t fix the problem, either, it just goes back to the monitors not actually ever shutting off, just turning off for a moment and then coming back on, with plasmashell crashing instead of the power monitor. I don’t care at all about controlling monitor brightness with DCC/CI but when the defaults cause crashes that’s an issue.
This is an out-of-the-box fresh install with no old dotfiles moved, complete refresh. These were the defaults I was given. Deciding to set your monitors to power down after 10 mins of inactivity shouldn’t be causing crashes. i shouldn’t have to manually turn my monitors off or do hacky shit with xscreensaver to get it working in fucking wayland just to not have monitor burn-in
I’ve not experienced any of this across many different linux systems… The default screensaver and lock screen work perfectly fine in KDE Plasma, and my monitors turn off when they should. I’ve even had no issues with HDR and variable refresh rates. (And the DCC/CI brightness controls for my TV work out of the box unlike windows).
I’m sorry you haven’t had the same experience. It almost seems like there could be something broken with your hardware if your monitor is continuing to detect a signal after things are asleep.
I’m sorry you made an ass out of yourself for making an assumption.
The thing is, Grandma won’t know what the fuck is going on or what DCC/CI even is. Grandma is poor and using pieced together old systems and shitty old monitors.
I’m not looking for a solution, I’m looking for people like you to stop making ass assumptions and get off your high fucking horse assuming the user must be at fault only realizing you’re wrong and being an ass after you already did it.
Look, I was trying to understand your issue, since I’m a developer and am curious about this kind of thing. I stated my assumptions to try and make my initial point of view clear and give you the opportunity to provide more information if my assumptions were wrong.
From what you’ve stated I don’t believe your problem is related to DCC/CI at all, and is likely something else with sleep states failing. Whatever is failing on your system is extremely unusual and is not something that I would expect a “Grandma” to ever encounter. If anything, older hardware should be better supported.
Look, you have zero attempt at self reflection here, this conversation is over. You made an assumption that the user was at fault and were wrong. Eat it. We aren’t in a fucking bug thread with my logs. Developers got no fucking social skills.
sorry, but “developers got no fucking social skills” coming from the only guy getting angry that someone’s trying to help him is hilarious
I made an assumption about what your goal was, and made no claims of fault or right/wrong. You can do whatever you want with your own computer. Bye