Just to humor you, I just turned the monitor off-on (I've been saying on-off but I'm hoping that's not where the confusion is stemming from)
but this time instead of fixing the incorrect resolution after CtrlAltF1\F7 I left it at the resolution that it defaults to. Then off-on again, and sure enough

the error still persists.

This leads me to believe my resolution preference isn't the problem. Thanks. So I'm not going to go screwing around with my grub settings any deeper than the first two options, the last thing I want is to be booted into a brick, thanks.

To regress and repeat the issue again,

the monitor staying blank after off-on started after creating xorg.conf

I created xorg.conf using the xorg -configure method as an attempt to correct the issue of

off-on bringing me into the wrong resolution.


Basically, when I turn the monitor off, then back on again, my system reads it as a new display, and of course defaults to the devices default instead of my set preference that I apply to both arandr and xfce display settings. I can change the resolution no problem.

But if I turn the monitor off, then on again, I have to change the resolution back to my setting because my preference does not persist.

After creating the xorg.conf file hoping that maybe my settings would persist there,
we have the new problem which I came here about.

Turning the monitor off, then on again brings me to a blank screen as if no TV input, however when I CtrlAltF1, the image is back but in console mode, and when I switch out of console mode CtrlAltF7, the image/signal is back, but at the incorrect resolution, the original issue.


Just making sure everyone is on the same page.

If I leave video or audio playing, the screen at least doesn't stay blank when I turn it back on.

Also, I could just use
as a workaround instead of turning the TV off, but that's a crappy alternative if you ask me. I'd rather be able to just turn it off and back on like I used to be able to do before creating the xorg.conf file.


Right now I'm under the assumption that something can be done with DPMS or HotplugEvent settings that will fix the blank screen issue.

Also, the resolution still isn't persistent, whatever.

If I run
BOTH PROBLEMS SOLVED!!!

........BUT WAIT! Doing so totally screws up my theme settings and keyboard shortcuts and a litany of other ugly issues.... k
running

brings back my theme settings and whatnot... ok
...but then the problems come back.


So the problem is somewhere concerning xfsettingsd ???

There's currently a kernel update in synaptic. It keeps it back in apt-get upgrade.

I just went in Synaptic and marked all upgrades and applied.

Crossing my fingers on this one.

No dice.

In the meantime I just can't turn off my TV while using my computer. Ever.



...come on guys how is anyone going to take Linux seriously as an operating system if we can't solve little problems like this? This is just embarrassing at this point.

If you google search XFCE HDMI Power cycling,
you will see lots of people have had the same issue as me.

There appears to be a functional "patch" but I don't know how to apply it and I'd really rather not blindly obey CL commands from threads over 2 years old.

If anyone can translate the patching process into stupid person language and update the syntax to corroborate with updated filenames and commands and whatnot, then I think we'll be able to fix this and help a lot of people.

I can't be the only one with this issue. At least with the inpersistent resolution part.

Just tried completely removing xfce4-settings,
I then reinstalled it and the packages it removed in the process.
In the reinstallation process it grabbed some extra packages that I didn't initially remove, but whatever.

Going to try rebooting now.

I'm trying this since killing xfsettingsd fixes BOTH issues.
Mind you it fixes the issues, but then my theme and keyboard shortcuts are messed up.

Ok that didn't work either.
At this point I give up on trying anything on my own.

Someone please make it well known that if you have XFCE,
CREATING xorg.conf WILL COMPLETELY RUIN THE ABILITY TO POWER CYCLE HDMI.

It's like my computer has cancer now. Easy to get, impossible to cure. Fantastic.

Troubleshoot this by
1-creating a virgin user, logging in as that user, setting the screen resolution as desired (if necessary), then cycling the display's power switch. If the results differ from normal user, then problem is rooted in user's personal settings; and/or
2-as regular user logging into IceWM instead of XFCE (IceWM has a very small footprint on disk and in RAM)(If XFCE and IceWM share settings this might not be useful.)

We can try to fix this legacy as well as the original problem with this custom xorg.conf (tested on a 720p Samsung):This can be tried with UseHotplugEvents set true first, then false; and DefaultModes on first, then off; and the two VertRefresh lines' # moved to the other if 60.01-60.03 creates a worse problem or no change.

Something else'es to try:
1-select 1280x720 instead of 1360x768.
2-boot with 3 appended to cmdline, login as normal user, run startx (this could pin blame on lightdm; getting startx to run might require reconfiguration: 'chmod 4711 /usr/bin/Xorg')
3-switch from lightdm to another login manager
4-If Plymouth is installed, purge it. If not, install it.

Does using the other HDMI port change anything? When turning the TV back on, does switching from the connected HDMI input port to TV or Composite or Component and then back to HDMI help?

Ok, I'll try that in a little while.

Looks like I screwed up by doing the Mark All Updates in Synaptic..
I knew better too that feature is ALWAYS asking for trouble.

Totally broke VLC, let me fix that then I'll get back to you on this one.
Sorry.

If I power cycle and then unplug the HDMI and plug it back in the image is back.

At this point I think I'm just going to have to reinstall the entire system.

VLC is completely broken and synaptic won't let me force version, as I mentioned there was a kernel update too so I'm guessing I have to undo that change too which means risking kernel panic.

This sucks.

When was your Sanyo FW32DO6F made?

Have you checked Sanyo's site for a firmware update?