[SRU] Xfce resets TV mode to NULL when power cycled

For people on mythbuntu who encounter this with a mceusb remote, here's how i'm working around it:

1) Save this file to /home/user/fix_tv_state.sh and make it executable
==============================
#!/bin/sh
#Fix TV state when HDMI link is lost.
#By Mario Limonciello <email address hidden>

OUTPUT="HDMI-0"
BAD_MODE="1280x720"
GOOD_MODE="1920x1080"

for MODE in $BAD_MODE $GOOD_MODE; do
 DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
 sleep 2
done
==============================

2) Create ~/.lirc/irexec and put these contents:
==============================
begin
     remote = mceusb
     button = KEY_POWER
     prog = irexec
     repeat = 0
     config = /home/user/fix_tv_state.sh
end
==============================

3) Add to ~/.lircrc this line:
include ~/.lirc/irexec

4) Restart machine, lightdm or log out/in

Now power button on your mceusb remote will fix the HTPC video output state.

Status changed to 'Confirmed' because the bug affects multiple users.

After some more sleuth work with NVIDIA, we've discovered that this is happening because of a RANDR event. An X client is responding to the RANDR events and forcing it to this NULL resolution.

I checked what clients were running, and it's xfsettingsd causing this problem. If I kill xfsettingsd prior to turning on/off my TV it comes back at the right resolution.

Here is the xfsettingsd debug output when the RR events are received. When the TV comes up there is a handful of change events and the end result is that the output gets disabled but not re-enabled.

xfce4-settings(displays): RRScreenChangeNotify event received.
xfce4-settings(displays): Refreshing RandR cache.
xfce4-settings(displays): Detected CRTC 447.
xfce4-settings(displays): Detected CRTC 448.
xfce4-settings(displays): Noutput: before = 1, after = 0.
xfce4-settings(displays): Output disconnected: HDMI-0
xfce4-settings(displays): Disabling CRTC 447.
xfce4-settings(displays): No active output anymore! Attempting to re-enable the internal output.
xfce4-settings(displays): RRScreenChangeNotify event received.
xfce4-settings(displays): Refreshing RandR cache.
xfce4-settings(displays): Detected CRTC 447.
xfce4-settings(displays): Detected CRTC 448.
xfce4-settings(displays): Noutput: before = 0, after = 0.
xfce4-settings(displays): RRScreenChangeNotify event received.
xfce4-settings(displays): Refreshing RandR cache.
xfce4-settings(displays): Detected CRTC 447.
xfce4-settings(displays): Detected CRTC 448.
xfce4-settings(displays): Detected output 452 HDMI-0.
xfce4-settings(displays): Noutput: before = 0, after = 1.
xfce4-settings(displays): New output connected: HDMI-0

I'm seeing a similar issue after upgrading from mythbuntu 12.04 to 14.04. Only I'm using integrated graphics from intel sandybridge.

This issue also affects Gigabyte GA-EG45M-UD2H motherboard with Intel GMA X4500HD integrated graphics. Fresh install of mythbuntu 14.04. 13.10 was not affected.

I have the same issue with ASUS P5E-VM HDMI motherboard. Fresh install of 14.04. Previous version (13.??) was not affected.

Same problem with Intel NUC D54250WYK. I've only ever run 14.04 on it.

One workaround is to install gnome-settings-daemon and check the box in Xfce session settings to start gnome services on startup.

I added the following in /etc/mythtv/session-settings to work around this issue:
killall xfsettingsd

This will kill xfsettingsd when mythfrontend starts.

I think that I was experiencing this problem. I tried the workarounds mentioned above, but none of them really "worked". But I do not seem to be experiencing this issue when I switched to using DVI instead of HDMI. For what is worth, I am running Xubuntu 14.04 on a Dell Studio-XPS.

I am experiencing the same with Mythbuntu 14.04 and an AMD A10 APU. Deactivating the autorunning of xfsettingsd fixed the problem.

I have the same bug with Xubuntu 14.04 on AMD Radeon 6770 with a Toshiba HDTV

Turn off TV and signal is lost and can't get it back again until I restart the desktop.

Oops, I got linked to this bug from

http://ubuntuforums.org/showthread.php?t=2220583&page=4

I didn't realise it was registered as an Nvidia bug though.

Clearly its not as my card is an AMD.

AMD owns nVidia these days as one of their brands. You may perhaps be in
the right place.

^No AMD owns ATI, the other major graphics card provider.

I am also experiencing this problem on integrated Intel graphics on Xubuntu 14.04 when using HDMI. It's the first distro I have used on this system but I never had the problem on Xubuntu 12.04 on my previous sytem (which was VGA/D-sub).

I do not get 'NULL' in my /var/log/Xorg.0.log but the issue is basically the same problem. I do get null in dmesg however:

[code][ 0.152426] ACPI: SSDT (null) 0004C4 (v01 PmRef Cpu0Ist 00003000 INTL 20061109)
[ 0.153472] ACPI: SSDT (null) 000433 (v01 PmRef Cpu0Cst 00003001 INTL 20061109)
[ 0.160066] ACPI: SSDT (null) 00015F (v01 PmRef ApIst 00003000 INTL 20061109)
[ 0.163743] ACPI: SSDT (null) 00008D (v01 PmRef ApCst 00003000 INTL 20061109)[/code]

I downgraded xfce-settings to the 4.11.0 package from Saucy, and locked it at that version. It eliminated the issue, and everything appears to function normally.

Thanks Straximus, that worked for me too.

tl;dr - There is a bug in xfsettingsd that not only affects external monitors, but primary monitors as well.

I believe that I am encountering the same bug, but by a different scenario. This may also be the same bug as #1313539.

I am running Xubuntu 14.04 on two of my four computers. I have all four computers connected to a single keyboard, monitor and mouse via a 4port KVM switch. Prior 14.04 upgrade, this setup worked like a dream. Post 14.04 upgrade, I have found that switching to either of the Xubuntu machines results in a blank monitor. On one machine, I am usually able to get to a virtual console and reset of the video by restarting lightdm. On the other machine, I am not able to even get a virtual console, and I have to ssh into the machine in order to restart lightdm.

The dying video happens so frequently that I starting the process of migrating away to XFCE. I installed Gnome Shell on one machine and Fluxbox on the other. Neither of these WM's exhibited the dying video phenomena.

Based upon this bug report, I decided to investigate the possibility that xfsettingsd might be the problem. Here's what I did.

1) Log in to a Xubuntu session.

2) Open a terminal window. Because I needed to do part of this from the Xubuntu session and part of this via ssh, I opened a new Byobu session (screen or tmux would work too). Then,

    $ killall xfsettingsd
    $ XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon 2>&1 | tee output.txt

3) After the initial output from xfsettingsd had finished,

    $ cp output.txt before.txt

4) Here's where the fun begins: I unplugged the monitor from the KVM switch. I waited a few seconds, and then I plugged the monitor back into the switch. No video. I switched the KVM to one of the other computers and verified that the monitor was corrected plugged in and working.

5) On one of the other computers with working video, I ssh'ed into the machine running the Xubuntu session and reconnected to the Byobu session. I found that xfsettingsd had crashed.

6) Executing "sleep 5; xfsettingsd" on the ssh session and switching to the Xubuntu machine restored the video.

7) I diff'ed the "before.txt" with the "output.txt". Here is the output that was generated when the monitor was unplugged and replugged.

xfce4-settings(displays): RRScreenChangeNotify event received.
xfce4-settings(displays): Refreshing RandR cache.
xfce4-settings(displays): Detected CRTC 63.
xfce4-settings(displays): Detected CRTC 64.
xfce4-settings(displays): Detected CRTC 65.
xfce4-settings(displays): Noutput: before = 1, after = 0.
xfce4-settings(displays): Output disconnected: VGA1
xfce4-settings(displays): Disabling CRTC 63.
xfce4-settings(displays): No active output anymore! Attempting to re-enable the internal output.
xfce4-settings(displays): RRScreenChangeNotify event received.
xfce4-settings(displays): Refreshing RandR cache.
xfce4-settings(displays): Detected CRTC 63.
xfce4-settings(displays): Detected CRTC 64.
xfce4-settings(displays): Detected CRTC 65.
xfce4-settings(displays): Noutput: before = 0, after = 0.
xfce4-settings(displays): RRScreenChangeNotify event received.
xfce4-settings(displays): Refreshing RandR cache.
xfce4-settings(di...

Following Straximus's lead (comment #18), I downgraded to the xfce4-settings package from Saucy. I left the machines allow all weekend long, and this morning the video on both machines worked as expected.

There is a regression bug between xfce4-settings 4.11.0-1ubuntu1 (saucy) and 4.11.2-1ubuntu2 (trusty).

This also affects me on Mythbuntu 14.04 x86 64bit with the open radeon driver and ATI RS880 [Radeon HD 4250] graphics controller.
The workaround for me was to disable xfsettingsd in the GUI Settings under "Session and Startup":
1) In the "Application Autostart" tab I unticked xfsettingsd.
2) In the "Session" tab I selected xfsettingsd and clicked "Quit Program".

Ahh, this issue has been driving me crazy since I did the 14.04 upgrade.

I'm using ubuntu 14.04 + xfce4 + plex connected to my yamaha receiver and panasonic hdtv (with pulse-eight cec usb dongle). (setup is years old).

The procedure above (#22) did the trick for me. Thanks!

Unfortunately, the workaround in #22 does not work form me. Since my computers are plugged in to a KVM switch, I need xfsettings running in order to reset my mouse and keyboard settings after switching computers.

Workaround #18 works for me.

Has anyone reported this bug upstream?

I am having the same problem. I upgraded frm Mythbuntu 12.04 to 14.04 with the Asus M3N78 motherboard (Nvidia 8200 graphics card & nvidia-304-updates driver).

Using xfce4-settings from Ubuntu 13.10 (as per post #18) fixed it for me. I have not tried using the suggestion from post #10.

There is another fix in this thread that I'll try later this week -> http://ubuntuforums.org/showthread.php?t=2221496

I added the options:
       Option "ConnectedMonitor" "DFP-0"
       Option "UseDisplayDevice" "DFP-0"
to the "devices" section of my /etc/X11/xorg.conf and it seems to have fixed it - even with the current xfce4-settings installed.

Tests I have done:
1/ boot with the television off, turn it on and get display
2/ boot with the television on, power cycle it (off time about 30 minutes) and have display
3/ boot with the television off, switch it on for 5 minutes, off for 30 minutes, back on and have display

As above, I have the Asus M3N78 motherboard (Nvidia 8200 onboard graphics) with nvidia-304-updates driver, using HDMI.

I have Ubuntustudio amd64 14.04LTS on a HTPC with a TV connected to HDMI-0 on a GA-880GMA-UD2H, Radeon mobo graphics.

Tried to follow #26, but it seems I don't have any xorg.conf in my /etc/X11.
Any advice?

My solution only works for Nvidia graphics cards using Nvidia drivers, sorry. Technically, it's a work-around, not a fix.

For those who do use Nvidia drivers but do not have an xorg.conf file, you can generate one with the "nvidia-xconfig" tool run as root or with sudo. See http://http.download.nvidia.com/XFree86/Linux-x86/1.0-8756/README/chapter-03.html

I did the fix in #26 and it fixed my issues as well.
The only difference was that in nvidia-settings my samsung tv was coming up as "DFP-1" so I had to change it to :
        Option "ConnectedMonitor" "DFP-1"
       Option "UseDisplayDevice" "DFP-1"

JeanLuke THANK YOU! This has been an huge source of frustration.

As of today this is still not assigned, so not really sure when they will get to fixing it.

I would like to try "this patch".
Please supply a link to where I can find it, and some detailed instructions on how to apply it. I am not a programmer.

Regards,

B. Nilsson

Alexander's patch also works nicely for me! So awesome to have a font I can read again and not to have to mess with Linux every time I turn off the receiver or switch it to a different input. Nice work!

Hey can you please send me some install information so that I can try it
out.

Cheers

Doug
On Nov 23, 2014 3:40 PM, "Chris" <email address hidden> wrote:

> Alexander's patch also works nicely for me! So awesome to have a font I
> can read again and not to have to mess with Linux every time I turn off
> the receiver or switch it to a different input. Nice work!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1308105
>
> Title:
> Xfce resets TV mode to NULL when power cycled
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
> Confirmed
> Status in xfce4-settings:
> Confirmed
> Status in “nvidia-graphics-drivers” package in Ubuntu:
> Invalid
> Status in “nvidia-graphics-drivers-331” package in Ubuntu:
> Invalid
> Status in “xfce4-settings” package in Ubuntu:
> Confirmed
>
> Bug description:
> I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new
> behavior that if the TV is power cycled it no longer detects a link
> with the HTPC.
>
> When this happens I can find in the xorg log that there is an
> accompanying log item:
>
> [ 39829.509] (II) NVIDIA(0): Setting mode "NULL"
>
> After debugging with NVIDIA at
> https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
> detected/ we've deteremined it's a X client that reacts to the RANDR
> events causing the mode to be set to NULL.
>
> Working through the list in an Xfce environment, the culprit is
> xfsettingsd. If xfsettingsd is running, it causes the TV to come up
> in a NULL mode. If it's killed, it remains in the mode it was
> previously running in.
>
>
> Until this is fixed, this behavior can be worked around with a simple
> shell script:
> ==============================
> #!/bin/sh
> #Fix TV state when HDMI link is lost.
> #By Mario Limonciello <email address hidden>
>
> OUTPUT="HDMI-0"
> BAD_MODE="1280x720"
> GOOD_MODE="1920x1080"
>
> for MODE in $BAD_MODE $GOOD_MODE; do
> DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
> sleep 2
> done
> ==============================
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions
>

I'm running mythbuntu and upgraded to 14.04. When I switched video inputs on my receiver the screen would die and I would have to manually run xrandr to force the display to start again. But after following the steps in post #22 the issue was resolved. Thanks Nick I would have never found that setting.

Hi,
I was wondering if someone could help me out on this.
I would like to apply the patch, but have very little ubuntu knowledge.
I am running ubuntu 14.04 and have found I get this problem.

The workaround in #22 works for me, but makes the fonts hard to read. This is why I would like to use Alexander's patch.

However, I am not sure how to do it.

I checked my system for xfsettingsd and displays.c but could not find either
sudo . -name displays.c -print
returns nothing (run from the root dir)

I assume that if I can find displays.c all I need to do is go to that directory and do:
patch < {patchname}

Any/All help appreciated.

Hey guys - a little help for a relative Ubuntu n00b?

I'm *not* running Mythbuntu - I'm running standard Ubuntu Desktop 14.04. I don't have xfce4-settings installed, but I am seeing very similar behaviour to that described in this bug report. I have a DisplayPort monitor attached. If I switch it off and switch it on again (or switch it to a different input and back again), Ubuntu doesn't detect the monitor and it says black. I have to reboot the box to get the display back. (There may be a way of getting it back using ssh but I haven't been able to do that yet).

If I change the monitor cable from DisplayPort to DVI this does not happen. I'm using a GTX660 with an HP LP2475w.

My behaviour looks like the same bug, but changing xfce4-settings won't help as I don't have it installed!

Can anyone verify this behaviour, and if verified, add the appropriate data in the "Affects" field? Thanks.

What works for me to get some output on my blank screen is to execute 'xrandr --auto' via ssh.

That only works when X was started in the first place, which may not be the case if you had booted without the screen on or something like that.

Could someone involved in this discussion PLEASE describe how to implement this patch.

With the current git-master (xfce4-settings 8adbd2e2463f5cc46c7ed94c0acf264155476268) and NO patches the issue does not occur for me. That is, neither when powering my HDMI-connected screen off and on again nor when physically disconnecting and reconnecting it.

However, I cannot even reproduce the original issue anymore. Weird!

My current configuration:
Xubuntu 14.04 x64
Kernel 3.13.0-45-generic
Intel Core i5-4590S
Intel driver 2.99.911-0intel1
Monitor attached with a HDMI-to-HDMI cable

Things that indeed changed:
- new, different mainboard (the old one died some weeks ago due to a power supply voltage peak)
- new but identical CPU (died due to the same reason)
- upgraded packages from the official Xubuntu 14.04 sources (got no related PPAs or such, so it's just regular updates)
- new kernel version (probably does not matter)

Btw, my machine is not a laptop, so I'm down to 0 outputs when physically disconnecting my screen (I kind of remember this being relevant in the source code).

Hi Everyone,

I'm glad to have found this thread (Many thanks to ToZ in forum.xfce.org): https://forum.xfce.org/viewtopic.php?id=9391

My problem is I read so many possible solutions that I really don't know what to do. I have an intel onboard graphics card and if I turn off TV i have blank screen when later I switch it on again (Xubuntu 14.04)

What is the procedure you reccomend me to do? From last posts here it seems to be a fixed releaded, how do I install?

I've make a recopilation of all the possible solutions I've read here:

****FIRST - Use this script when problem happends:
==============================
#!/bin/sh
#Fix TV state when HDMI link is lost.
#By Mario Limonciello <email address hidden>

OUTPUT="HDMI-0"
BAD_MODE="1280x720"
GOOD_MODE="1920x1080"

for MODE in $BAD_MODE $GOOD_MODE; do
 DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
 sleep 2
done
==============================

My question is: How can I run the script when HDMI link is lost if I've no video signal?

****SECOND - install gnome-settings-daemon and launch on system boot.
It seems too easy to be true, hehe, Do i try?

****THIRD - killall xfsettingsd
In my case I can leave computer on with desktop on screen, so I can't do this on any program boot. Whose are the consequences of killing this application on system boot?
I've read it can causes an undesired problem, fonts are unreadable (could cause some problem with image quality)

****FOUR - Using DVI cable instead of HDMI
I could use a DVI to HDMI cable, at last I can get sound from it, althought I'd prefer maintaining the DVI connection.

****FIVE - downgrade xfce-settings to the 4.11.0 package from Saucy, and locked it at that version (4.11.3 causes the problem).
How can I do this?

****SEVEN - Create xorg.conf and add those lines:
Option "ConnectedMonitor" "DFP1"
Option "UseDisplayDevice" "DFP1"

OR
       Option "ConnectedMonitor" "DFP-0"
       Option "UseDisplayDevice" "DFP-0"

to the "devices" section of /etc/X11/xorg.conf.

Only for nVidia cards

****EIGHT - Install a patched 4.11.3 (from my PPA here: https://launchpad.net/~landronimirc/+archive/ubuntu/collection , includes fix_for_bug11107.patch).
The person who told this seems to not have solved with this procedure. How can I do this? I mean, How can I Install this patched version.

****NINE - Sean's patch, "fix_for_bug11107.patch"
I don't know where to download it from or how to install, it seems to be explained in next option (TEN)

****TEN - Alexander's patch, also Sean's, explained here:
For Ubuntu 14.04, this is how your you can build xfsettings with the patches:

sudo apt-get install xfce4-dev-tools libexo-1-dev libgarcon-1-0-dev libxfce4ui-1-dev
git clone git://git.xfce.org/xfce/xfce4-settings
cd xfce4-settings
curl https://bugzilla.xfce.org/attachment.cgi?id=5681 > alexander-patch.diff
curl https://bugzilla.xfce.org/attachment.cgi?id=5723 > sean-patch.diff
Choose a patch to Apply: patch -p1 < <patch>
./autogen.sh && make && sudo make install
/usr/local/bin/xfsettings --replace

If you wanna to try other patch, first remove what's applied:
patch -R -p1 < <applied patch>

After playing, remember to remove the installed xfsettings:
sudo make uninsta...

 I've spent a good amount of hours researching and making tests, unfortunately I can't make it work and I'm really desperate, so I'd really thank any help.

I hope someone can lend me a hand (mainly on the procedures of patches of alexander and sean, I can't make them work).
----

The script of first solution works (in my case replacing HDMI-0 with HDMI1), I create it in ~/fixhdmi.sh and chmod 755 it.

The question here is automating the process, and in this I've not been able to, It only works running script manually from terminal (I've no try to make a shortcut, it's not valid for my needs) :(

I even added a wait time before the process (since the TV takes some time in beign ready I thought it could help) and a message after with zenity:

[code]#!/bin/sh
#Fix TV state when HDMI link is lost.
#By Mario Limonciello <email address hidden>
sleep 10
OUTPUT="HDMI1"
BAD_MODE="1280x720"
GOOD_MODE="1920x1080"

for MODE in $BAD_MODE $GOOD_MODE; do
 DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
 sleep 2
done
zenity --info --title="HDMI" --text="fixhdmi.sh has been executed"
[/code]

I've found a few entries explaining the procedure of udev, so I've create a the file /etc/udev/rules.d/hdmi.rules with this content

[code]KERNEL=="card0", SUBSYSTEM=="drm", ACTION=="change", RUN+="/home/fkervin/fixhdmi.sh[/code]

I also tryed:
[code]SUBSYSTEM=="drm", ACTION=="change", RUN+="/home/fkervin/fixhdmi.sh[/code]

I tried another ones I don't remember...

The result without the udev entry is "no signal message", with it I have cursor on screen over black for a seconds but then dissapear and "no signal" message again. It makes me think that

the udev could be working on TV disconnect but not on connect (only an idea). Later when I tried the alexander's mod I had the same effect, (cursor and blank screen), I don't how it there is any relation.

I've try udevadm in a power-off/power-on of the TV, having this result:

[code]
fkervin@fkervin:~$ sudo udevadm monitor
[sudo] password for fkervin:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[121.525065] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)
UDEV [135.590008] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)
KERNEL[142.156140] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)
UDEV [156.226634] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)
[/code]

I can't figure out how to make udev rule work :(

-----

I've try to install Xfce 4.12 packages:

[code]
sudo add-apt-repository ppa:xubuntu-dev/xfce-4.12
sudo apt-get update
sudo apt-get upgrade
[/code]

It unfortunately doesn't solve the problem.

------

killing xfsettingsd makes it work, but since it interfere on the icons, text and many elements, it's not appropiate.

------

In the option of installing an older xfce4-settings:

by adding the saucy mirrors to you sources.list, and running apt-get update && apt-get install xfce4-settings/saucy or apt-get -t saucy install xfce4-settings

I don't know what should I add to sources.list.

------

Alexander and sean's procedures:
I've try several times with no results, for example:

...

For those trying the above commands... the curl to get the patch files is likely not working.
I'm not motivated enough on curl to figure out the problem, but i was able to copy/paste with a browser.
If you are unsure, look at the patch files, git diff, the output of patch, etc...

For me the latest git did not fix the problem.
Sean's (updated) patch also did not fix the problem.
Alexander's patch *did* fix my problem.

My use case is with a single display attached to a A/V receiver. Turning the receiver off, and back on did not come pack.
Using alexander's one liner, it works great.

IMHO, this is a big issue, and i'm shocked that it's not been rectified yet.

Hi all,

Some days ago appeared xfce 4.12, I've made an sudo apt-get update and upgrade but problem is not solved.

Have I done something wrong or the problem is still not solved?

Regards

@fkervin The bug status is still not marked as fixed. There has not been a valid fix that doesn't cause a regression.

I have been having this issue on my 14.04 install for a while now (probably as long as Mario), i have been using my rPi and a button to run a command over ssh to fix it
DISPLAY=":0.0" xrandr --output HDMI-0 --auto

i upgraded me and my dad to xfce 4.12 and now he has the issue ga-a55m-ds2 motherboard and a AMD A6-3500 APU
he is running xubuntu 14.04 w/ linux 3.16.7 w/ xfce 4.12 (open source drivers, NOT fglrx/catalyst)
he is using DVI on a HP 2009M monitor
this command restores the display for him
DISPLAY=":0.0" xrandr --output DVI-0 --auto
he seems to have this issue wen the power manager turns the display off and the monitor goes into standby

I am currently experiencing this issue with a foxconn d180s j1800 motherboard and Xubuntu 15.04. After turning off the TV and receiver I do not receive any video when turning them back on. Running the script fixhdmi.sh posted above or 'xrandr -d :0 --auto' seems to fix the issue. I just need to figure out how to trigger when TV turns back on.

You could probably just use 'xrandr --auto', at least that worked for me.

I have actually now a different 'fix', by simply never having the system notice the hdmi-link goes down. I used this wiki-page to fix that for my Intel Haswell-cpu graphics.

https://wiki.archlinux.org/index.php/Kernel_mode_setting

My final cmdline is now this:
video=HDMI-A-1:1920x1080@60e dmr_kms_helper.edid_firmware=HDMI-A-1:edid/tv-edid-data.edid

The tv-edid-data file is located in /usr/lib/firmware/edid/ and was derived via 'get-edid'. It actually also seemed to work with the built-in '1920x1080.edid' (saves you retrieving it from your receiver, but I thought it a bit more save to have the actual edid).
Just supplying the video-parameter wasn't enough in my case, it failed to actually set the resolution to 1920x1080 (and used 1024x768 instead). Adding the edid-data fixed that (it may even be sufficient to only force-load the edid data).

The reason this works is not because it fixes the issue, but because it prevents the hdmi-link from ever going down - as far as the kernel is concerned.

My best solutions to the MythBuntu/XBMC/Kodi usecase:

1) Run a MythBuntu/XBMC/Kodi-session without any desktop at all! They're in /usr/share/xsessions/
for running completely standalone.

2) Running a really minimal WM that doesn't try to manage screens at all like Openbox. Works
well with Steam big picture mode.

Adding my me too. I have a ECS Liva X with an intel graphics chip. When I turn off my Samsung TV the screen goes away. I added the suggestion above (killall xsettingsd) to the /etc/mythtv/session-settings and was able to confirm that it does workaround the problem.

I have a Viewsonic VX2475Smhl-4K attached with a DisplayPort cable to a Gigabyte GTX 970 (nvidia-358 driver, ASUS Z97-A, UEFI boot with CSM disabled), and it requires `xrandr --auto` after being power cycled. That's easy to set to a keyboard shortcut when logged in, but harder in xflock4. Even less amusing, Linux text VTs don't work until an `xrandr --auto` in an X session.

There were reports that non-VESA-compliant DisplayPort cables that wire pin 20 (DP_PWR) cause this problem, but I checked my Cable Matters cable with a multimeter and it does not wire pin 20.

Microsoft has a page about this problem: https://support.microsoft.com/en-us/kb/2625567

I also struggled with this bug when doing a fresh install of Mythbuntu 14.04 this week.

I downloaded xfce4-settings 4.11.0-1 from this link.

https://launchpad.net/ubuntu/saucy/amd64/xfce4-settings/4.11.0-1ubuntu1

Then "sudo dpkg -i xfce4-settings_4.11.0-1ubuntu1_amd64.deb" to install it and synaptic to lock this version.

I can now switch off my TV connected with HDMI cable and when I switch it back on it works.

Mythbuntu is running on a Gigabyte Brix GB-BXBT-2807 with 4gb ram, 120gb ssd, DVB-T usb tuner. The machine runs both front and backend.

Hi Greg,

    Trying to follow your instructions.

     What do you mean by... and synaptic to lock this version....

     What did you do, what did you execute

Thanks

Doug
On Jan 17, 2016 1:05 PM, "Greg Fordyce" <email address hidden> wrote:

> I also struggled with this bug when doing a fresh install of Mythbuntu
> 14.04 this week.
>
> I downloaded xfce4-settings 4.11.0-1 from this link.
>
> https://launchpad.net/ubuntu/saucy/amd64/xfce4-settings/4.11.0-1ubuntu1
>
> Then "sudo dpkg -i xfce4-settings_4.11.0-1ubuntu1_amd64.deb" to install
> it and synaptic to lock this version.
>
> I can now switch off my TV connected with HDMI cable and when I switch
> it back on it works.
>
> Mythbuntu is running on a Gigabyte Brix GB-BXBT-2807 with 4gb ram, 120gb
> ssd, DVB-T usb tuner. The machine runs both front and backend.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1308105
>
> Title:
> Xfce resets TV mode to NULL when power cycled
>
> Status in Mythbuntu:
> Confirmed
> Status in xfce4-settings:
> Confirmed
> Status in nvidia-graphics-drivers package in Ubuntu:
> Invalid
> Status in nvidia-graphics-drivers-331 package in Ubuntu:
> Invalid
> Status in xfce4-settings package in Ubuntu:
> Confirmed
>
> Bug description:
> I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new
> behavior that if the TV is power cycled it no longer detects a link
> with the HTPC.
>
> When this happens I can find in the xorg log that there is an
> accompanying log item:
>
> [ 39829.509] (II) NVIDIA(0): Setting mode "NULL"
>
> After debugging with NVIDIA at
> https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
> detected/ we've deteremined it's a X client that reacts to the RANDR
> events causing the mode to be set to NULL.
>
> Working through the list in an Xfce environment, the culprit is
> xfsettingsd. If xfsettingsd is running, it causes the TV to come up
> in a NULL mode. If it's killed, it remains in the mode it was
> previously running in.
>
>
> Until this is fixed, this behavior can be worked around with a simple
> shell script:
> ==============================
> #!/bin/sh
> #Fix TV state when HDMI link is lost.
> #By Mario Limonciello <email address hidden>
>
> OUTPUT="HDMI-0"
> BAD_MODE="1280x720"
> GOOD_MODE="1920x1080"
>
> for MODE in $BAD_MODE $GOOD_MODE; do
> DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
> sleep 2
> done
> ==============================
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions
>

I have exactly the same issue on 15.10 with an intel card.
philmmanjaro on github has published a patch to solve the issue. Just applies the patch on xfce 4.12 source code
The workaround to fix this is the following:

$> sudo apt-get install xfce4-dev-tools libexo-1-dev libgarcon-1-0-dev libxfce4ui-1-dev libxklavier-dev
$> git clone git://git.xfce.org/xfce/xfce4-settings
$> git clone https://github.com/manjaro/packages-extra.git
$> cd xfce4-settings
$> git checkout xfce4-settings-4.12.0
$> patch -p1 < ../packages-extra/xfce4-settings/hdmi-power-cycling.patch
$> ./configure --prefix=/usr --enable-pluggable-dialogs --enable-libxklavier
$> make
$> sudo make install
$> sudo reboot now

I did a small mistake on my compiling instruction above, replace ./configure by ./autogen.sh and it should work.

Any update on this issue?

Im getting it on the latest xubuntu nightly.

I can still access the console via Ctrl+Alt + F1. But cannot get back to the xfce desktop.

Reproducible on HP Pavilion SE a6655f, AMD x64, with Asus brand Geforce GT-220 (ENGT220) video card, only connected output is HDMI to surround receiver, then HDMI to Panasonic LED TV.
Unused workaround from comment #22 (disable xfsettingfsd) and has been solid since. I switched inputs on the TV away from the surround to a digital cable box, watched a little TV, then back without issue. I turned off TV and surround, turned back on, and I can still see the output from the HP.

Mythbuntu 14.0.4 LTS (fresh install of 14.04.4 actually).

A side-effect was that sometimes the mouse pointer would also disappear if I switched away and back again. I'll be watching that problem closely on this HP PC now that I've worked around the current problem.

Just a minor point: Glen pointed out in comment #86 that the curl command to get the patch files doesn't work.

I've done some playing around. For some reason 'curl https://bugzilla.xfce.org/attachment.cgi?id=5681' doesn't work - but 'curl -L http://bugzilla.xfce.org/attachment.cgi?id=5681', which follows the 302 redirect from 'http://bugzilla.xfce.org/...' to 'https://bugzilla.xfce.org/...', does work.

So it's possible to get the patches by issuing:

curl -L http://bugzilla.xfce.org/attachment.cgi?id=5681 > alexander-patch.diff
curl -L http://bugzilla.xfce.org/attachment.cgi?id=5723 > sean-patch.diff

The patch by jkampe68 (#109) did it for me. Here is my flow chart:

Downloaded the xfce4-settings_4.12.0.orig.tar.bz2 (https://launchpad.net/ubuntu/+archive/primary/+files/xfce4-settings_4.12.0.orig.tar.bz2) and unpacked it.

Saved the Patch by jkampe68 (http://bug-attachment.xfce.org/attachment.cgi?id=6590) as .patch file.

Navigated to xfce4-settings-4.12.0-orig/xfsettingsd/ and used the patch command to patch the displays.c file.

Now "./configure --prefix=/usr --sysconfdir=/etc" until all dependencies were fulfilled.
Garcon can be found here: https://mirror.netcologne.de/xfce/src/xfce/garcon/0.5/garcon-0.5.0.tar.bz2

"make"

"sudo make install"

Now the /usr/bin/xfsettingsd was replaced and everything worked well after reboot.

The attachment "Patch by jkampe68" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

Trying to implement the suggestion in #115, I've got the git repo from xfce.org and applied the patch, did the configure which ends with:

Build Configuration:

* Installation prefix: /usr
* Debug Support: full
* Xrandr support: yes
* UPower support: no
* Libnotify support: no
* Xcursor support: yes
* Xorg libinput support: no
* Embedded settings dialogs no
* Sounds settings support no
* Libxklavier support: yes
* Mime settings (gio-unix): yes

But attempting a build gives the error:

make[4]: Entering directory '/home/cmcmanis/src/xfce4-settings/dialogs/appearance-settings'
  CC xfce4_appearance_settings-main.o
main.c:44:34: fatal error: appearance-dialog_ui.h: No such file or directory
compilation terminated.
Makefile:667: recipe for target 'xfce4_appearance_settings-main.o' failed

So presumably there is a missing step here somewhere.

Scratch that, forgot to autogen.sh first, did it earlier but did not repeat after resolving the last dependency. So not it compiled, on to testing.

Ok I have confirmed that the patch in #115 (Saved the Patch by jkampe68 (http://bug-attachment.xfce.org/attachment.cgi?id=6590) as .patch file.) fixes the issue on NUC derived systems (Intel graphics, I've got a NUC5i7RYH and a Gigabyte BRIX) where the screen attached to the display port output does not come back on when power is re-applied to the monitor. The next step is validating that the screen can recover after a "sleep state" which has been initiated by light-lock.

I pulled the git repo applied the patch, ran autogen.sh then make, then make install. Rebooted and verified the new settingsd was running (

cmcmanis@charliehorse:~$ xfsettingsd --version
xfsettingsd 4.12.0git-56abfbd (Xfce 4.12)

Copyright (c) 2008-2011
 The Xfce development team. All rights reserved.

Please report bugs to <http://bugzilla.xfce.org/>.
cmcmanis@charliehorse:~$

Power cycled the monitor, and where previously this would always cause it to not come back, it now returns. System is Xubuntu 16.04 otherwise vanilla install.

And the title here really needs to be changed that this isn't an nVidia bug, that probably confuses people trying to find it.

OK. This has been driving me nuts for weeks. I would lose my entire X session every single day as soon as the screen blanked... quite troublesome when you're trying to make linux work as your daily drive, haha.

*Confirmed fix* w/ the patch suggested on xfce's bugzilla: https://bugzilla.xfce.org/show_bug.cgi?id=11107#c53

Download the xfce4-settings source, apply the patch, increment with a non-maintainer version number (for no future apt-get conflicts once this gets an official fix), and reinstall your patched xfce4-settings.

I had to learn how to patch a .deb file properly in the process, but that was worth it too.

-- Hardware/Software --
GPU: GTX 970 over DisplayPort 1.2
Monitor: Dell P2715 (4K@60Hz, hardware rev A03)
OS: Xubuntu Xenial (16.04 LTS)
Manually patched xfce4-settings version: 4.12.0-2ubuntu1

Useful links on patching .deb's:
https://help.ubuntu.com/community/UpdatingADeb
http://www.cyberciti.biz/faq/appy-patch-file-using-patch-command/

The patch in comment #53 works for me too, meaning that the desktop remains visible after power cycling my receiver. However, the MythTV frontend disappears (but the process is still running, according to ps). mythfrontend.log doesn't provide any clues as to what is happening at the time the receiver is turned off, either. I guess I could upgrade to Mythbuntu 16.04 but I'm expecting to encounter new problems then, such as no more 32-bit Chrome.

The patch by philmanjaro works for me too by following instructions by Alexandre ACEBEDO (aacebedo) from 2016-01-25, on a braswell system (N3150 - Zbox CI323)

One thing though, I still have an issue if the TV is turned off when the PC is booted initially, xrandr will give me the proper info and tell me the screen is connected once I power it on, but xfce will still show it as Disabled (by connecting with x11vnc), I'm not sure if it's related or not

xrandr -auto sometimes fixes it but not always I sometimes have to reboot the system with the TV powered on for it to start working again

As another workaround it is possible to disable the hotplug events in xorg conf.
here the steps:
switch to tty (crtl + alt + f1) and log in.
sudo service lightdm stop
sudo Xorg -configure # this creates an xorg.conf and displays where it is stored
sudo cp /path/to/xorg.conf.new /etc/X11/xorg.conf
sudo vim /etc/X11/xorg.conf

then add to the "Device" section:
 Option "UseHotplugEvents" "false"

save and quit and restart lightdm:
sudo service lightdm start

found it here:
https://ubuntuforums.org/showthread.php?t=2123353
http://www.gossamer-threads.com/lists/mythtv/users/570769
https://ubuntuforums.org/showthread.php?t=2220583&page=5

Hi.
This affects me too.
I'm looking for what some other users refer to as "Alexander's patch" but I can't find it.
Additionally, I see the post numbers jump fro #2 to #41... How can I see the other posts? Perhaps the patch was posted there?

Hi!
The XFCE4's maintainer claimed to have merged the patch for this bug here:
https://bugzilla.xfce.org/show_bug.cgi?id=11107#c67 on 2016-08-12.

A new version of xfce-settings (4.12.1) has been released on 2016-09-15 so we can assume that the fix is integrated in the release.

Note that the patch is not the same as the one I've linked in comment #107. I still have to test the new version.

Note also that the 4.12.1 version was not integrated in ubuntu 16.10 so we still have to recompile and install it manually :(

Thanks for that!
I think I'll keep waiting for the patched version to come out for my distro (32bit Xubuntu 16.04) as I'm really trying to avoid installing dev tool and compiling from source... I guess I'm just too old and grumpy now and prefer to spend time using my computers than fixing them. I already filled my quota of applying manual patches for things to just work in the 90's :D.

Anyway, I really appreciate the effort many of you guys put into making my life easier with great, open software.

I have an ASUS Z170M-Plus Mobo with an Intel Core i3-6100T, Intel HD 530 graphics and a Samsung TV connected through HDMI, running Mythbuntu 16.04.

I had the issue that when I turned the TV off and then back on again, the TV would say "No Signal" and I would have to run
$ sudo service lightdm restart
to get it to work again.

Based on Alexandre's comment #128, I installed xfce-settings 4.12.1 from here:
https://packages.debian.org/stretch/amd64/xfce4-settings/download
http://ftp.uk.debian.org/debian/pool/main/x/xfce4-settings/xfce4-settings_4.12.1-1_amd64.deb
and installed it on my Mythbuntu 16.04 installation. To my surprise, I didn't have any dependency issues, it all applied without problems and now the problem seems fixed! I can turn the TV off and on again and the picture comes back as expected.

Great work all in getting this sorted.

I also installed http://ftp.uk.debian.org/debian/pool/main/x/xfce4-settings/xfce4-settings_4.12.1-1_amd64.deb but my 2nd monitor doesn't come back on after it's entered power-save mode when I move the mouse which does turn my primary laptop display back on.

No combination of xrandr commands or switching to the console with CTRL-ALT-F1 brings it back on. The only thing that works is to power cycle the monitor which causes the display setup to switch back to single display mode. Then I have to go re-configure the dual display setup which is really annoying because I have to move all my windows back to their correct positions on the 2 displays.

I've tested my external monitor on windows and it always comes back on immediately even after entering the same power save mode so it's not an issue with the monitor.

Interestingly when I use the displayport over USB-C pass through it all works correctly. It's only with HDMI that the problem occurs.

I'm using a Dell Precision 5510 laptop with Intel Graphics enabled and the nvidia graphics disabled on Xubuntu 16.04.1 with all updates applied. I've also tested this with the same results on Ubuntu 16.10 with all updates applied.

xrandr shows it's still sending the signal to the external HDMI display even though the display is still in power saving mode:

tenpin: ~ xrandr
Screen 0: minimum 8 x 8, current 1920 x 2160, maximum 32767 x 32767
eDP1 connected 1920x1080+0+1080 (normal left inverted right x axis y axis) 346mm x 194mm
   1920x1080 59.93*+ 59.93
   1680x1050 59.95 59.88
   1600x1024 60.17
   1400x1050 59.98
   1600x900 60.00
   1280x1024 60.02
   1440x900 59.89
   1280x960 60.00
   1368x768 60.00
   1360x768 59.80 59.96
   1152x864 60.00
   1280x720 60.00
   1024x768 60.00
   1024x576 60.00
   960x540 60.00
   800x600 60.32 56.25
   864x486 60.00
   640x480 59.94
   720x405 60.00
   640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080 60.00*+ 50.00 59.94
   1920x1080i 60.00 50.00 59.94
   1600x1200 60.00
   1280x1024 75.02 60.02
   1152x864 75.00
   1280x720 60.00 50.00 59.94
   1024x768 75.03 60.00
   800x600 75.00 60.32
   720x576 50.00
   720x576i 50.00
   720x480 60.00 59.94
   720x480i 60.00 59.94
   640x480 75.00 60.00 59.94
   720x400 70.08
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Jonathan,

Given the latest version of xfce-settings (4.12.1) was easy to install and fixed all of my issues (see comment #130 above), it would be interesting to know whether this also fixed your problem.

Kind regards,

Aaron

I downloaded xfce4-settings 4.12.1-11 as stated in comment #130 but for my i386-based xubuntu 16.04 from https://packages.debian.org/stretch/i386/xfce4-settings/download

This solved it for me.

I tried xfce4-settings 4.12.1-11 as mentioned in #133 and indeed it "works", X does not crash.
However, the set screen resolution is lost. When I turn on the screen again, the desktop defaults to the highest possible screen resolution.
In my case, it means that my desktop menu bar and docky are placed outside the screen bounds, tricky to reset.
Better than it was before, but not quite there yet.

Note that there is a Ubuntu package of 4.12.1 available now http://packages.ubuntu.com/zesty/xfce4-settings which can be installed at least without dependency issues on Ubuntu 16.04.

The upstream commit that fixes the issue is here https://git.xfce.org/xfce/xfce4-settings/commit/?id=2233f20a7ec6d7cb7dcc5752d62d98e37d9c21ad.

As mentioned in the upstream bug report: "[...] one issue in the patch; when enabling the crtc it _unconditionally_ sets the output crtc (preferred) mode, rotation etc. properties". Anyway it was decided to merge the patch and address that issue in a new bug #. So maybe the best way is to do the same here, i.e. mark this as fixed in zesty and apply the patch in xenial and yakkety. And create a new bug for the lost screen resolution and other settings.

Running Xubuntu 16.04.1 with all updates applied as of 31/01/17 this bug affected me when using the HDMI port of a Braswell chipset Shuttle XS36V5. When resuming my Samsung TV from standby the HDMI wouldn't wake up and thus no picture. It was the only display device attached. Tried various combinations of power management settings in UEFI/XFCE/TV to no avail, as well as a different HDMI port on TV as well as different HDMI.

Upon a 'sudo reboot' from SSH or by pressing the power button on the shuttle (had power button set to 'shutdown' instead of 'ask') the TV would wake up within a second or two and show the shutting down logo.

Consulted your Freenode IRC channel, Flocculant suggested applying:

https://launchpadlibrarian.net/269857837/xfce4-settings_4.12.0-3ubuntu1_amd64.deb

Which i did with 'dpkg -i xfce4-settings_4.12.0-3ubuntu1_amd64.deb && apt-get install -f' and this fixed it. Petition to get this fix applied to a SRU for 16.04 thanks <3

This is affecting me on Mythbuntu 16.0.4.3 - with all updates applied as of 10.09.2017. Machine is an Intel NUC NUC6CAYS.

Display is a Panasonic TV connected via HDMI.

As with other users above running xrandr --output 'DP-1' --mode '1920x1080' brings the display back to life, as does restarting X11. The problem can be cured by killing xfsettingsd.

dmesg and Xorg.log (concatenated together) attached so that you can get a sense of the hardware involved.

Sorry not sure whether this issue is Ubuntu specific or whether the bug belongs upstream with the XFCE guys. Happy to help in any way I can.

Unfortunately, the version in 16.04 was not patched.

The bug is fixed in 18.04 which installs xfce4-settings 4.12.4.

Is there any hope of this being backported to 16.04? This is a big problem for our customers running our digital signage players running 16.04. This is a pretty critical bug to leave unaddressed in an LTS that still has two years of support left.

Attaching xenial debdiff

Uploaded package version 4.12.0-2ubuntu1.16.04.1

Hello Mario, or anyone else affected,

Accepted xfce4-settings into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xfce4-settings/4.12.0-2ubuntu1.16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

I have installed the package xfce4-settings (version 4.12.0-2ubuntu1.16.04.1) from xenial-proposed.
The fix worked for me. Thanks!

This bug was fixed in the package xfce4-settings - 4.12.0-2ubuntu1.16.04.1

---------------
xfce4-settings (4.12.0-2ubuntu1.16.04.1) xenial; urgency=medium

  * debian/patches/lp1308105.patch:
    - Fix Xfce resetting TV mode to NULL when power cycled (LP: #1308105)

 -- Sean Davis <email address hidden> Tue, 26 Mar 2019 21:52:13 -0400

The verification of the Stable Release Update for xfce4-settings has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.