IT has a reason why a nvidia card costs some money and an intel one is crap.

Most noob friendy is an nvidia card. than start nvidia-settings. detect monitor. configure, apply. done. if you want ot keep it, you can generate that xorg.config

intel gpu is problematic since 10 years at least. it is more for text based shells, not for graphical user interfaces. it has lower HDMI standards and other flaws.

--

I aslo recommend rule out a hardware issue.

use a decent linux iso or a proper linux distribution. debian is definitely not a proper distro.

use another proper working cable. use some other connection port.

use a working computer

--

and no it is not xorg related. it is more systemd + newbie debian distro related. debian based distros have many flaws. since years. also debian ships unsecure outdated packages, see. e.g xscreensaver what the guy wrote on his homepage.

--

Usually since many years before systemd disease, you did not even need an xorg.conf
I had my gentoo running for several years without a xorg.conf on different hardware platforms.
again use a proper distro, or configure your hardware properly
and also buy a proper gpu. (for those guys who disagree => go to kernel.org and see all those intel related acpi / gpu / brightness / intel uefi issues and other issues. unanswered, unsolved, unfixed since many years!)

Is it such hard to use rm command to delete a config file as superuser?
This has not changed since slackware 96

That's completely irrelevant to the issue.

_roman_ either delete your post or read the thread again and edit what you said.

There's just so many things wrong there that I don't have the time for it.

What proof do you have of that? When made often speaks to known longevity issues, but only when exact model number is known, and possibly serial number as well.

Experience is my proof.
This issue is software related.
Software started it, software will end it.

I can plug my system into a different TV right now and have the same exact problems. I'm willing to bet money on it. Ok?

Your xorg.conf didn't work either, I'm going to try a few other things and report back.

Besides dude think about it, by your logic, I have to create a xorg entry for
every
single
monitor
in
existence

in order for this error to disappear.
That's not happening. Even if it wasn't impossible, I'm not doing that.

Why? Because I travel a lot and I can't predict what kind of make and model number and year produced for
every
single
monitor
I encounter, that's just ridiculous.


Again, I regress and repeat, I've used this computer with many other TVs and monitors in the past when traveling, the Sanyo is just the one in my office.
Ok?


I hereby require the next poster to breakdown and repeat what's happening in two sentences before saying anything.
Because right now I'm under the impression none of you understand what my issue is.

killing xfsettingsd fixes BOTH the blanking problem AND the inpersistent resolution problem.

Now with that being the case that means that I don't need to throw in additional specs for the TV it means somewhere along the lines in a setting or configuration file somewhere something is wrong concerning DPMS or HotPlugEvents or something of that nature.

And no I can't just kill xfsettingsd and go about my day because my themes and keyboard shortcuts require it to function.

Coincidence is always a possibility with weird trouble like you've experienced. That xorg.conf file -configure generated likely, at most, did nothing more than irrevocably expose a hardware weakness, because nothing in it, with the possible exception of UseHotplugEvents, specified doing anything that wasn't already being done via Xorg automagic.

Fine, if you have in fact already done so. I can't remember reading that you wrote that you already have done so in this very long thread.

Still waiting for your response to what changes if anything when you try a virgin user or an Xorg session other than XFCE.

Here we go:

If you use XFCE,
NEVER EVER EVER EVER CREATE A xorg.conf !!!!
IT WILL RUIN YOUR DISPLAY SETTINGS PERMANENTLY NO MATTER WHAT DISPLAY YOU USE AND DELETING THE FILE WILL NOT REVERT THE CHANGES!!

Also, every time you turn off your monitor you HAVE TO CHANGE THE RESOLUTION. EVERY TIME. YOU HAVE TO.


There we go problem solved.

I'm just going to reinstall my entire system I don't have time to argue about this anymore.

What do you think?
If killing xfsettingsd fixes it, then obviously the issue lies somewhere within xfce settings or a configuration file somewhere.

Do you really think I'm about to install an entirely new WM just to test what I already know? No.

For those of you wondering, post #56 is the solution.

It says how you think you broke it. It does not say anything about how you fixed it. It does not say that you reinstalled, only that you intended to.

The screen blanking stopped. I didn't do anything it just fixed itself on its own somehow.

Still comes back to 1920x1080, but it at least comes back.