My issue is similar to this post by chad126 and is being posted because his post remains unsolved.

I'm running Ubuntu 18.04 (Bionic Beaver) on a Dell N7010 laptop using a WinTV-HVR-955Q USB tuner stick. All software was installed from the default Ubuntu apt repositories. Almost everything is working as expected. I can use MythTV to watch live TV, tune channels, record and watch recorded shows. But suspend is not working.

In my case, any attempt to suspend appears to work, but the system simply hangs and cannot be awakened except through a hard power-off reboot accomplished by holding the power button for 10 seconds.

When I explicitly request suspend, or when I allow the configured idle time to expire and the laptop attempts to sleep itself, it hangs. The display goes black and the HDD spins down. But the box hangs at that point. The power lights remain lit-steady (rather than pulsating as they do during a "normal" sleep). Nothing will awaken the box -- keyboard, mouse, and power button activities have no effect. Power-off reset is the only option, from which the laptop will reboot normally.

With or without the USB tuner plugged in, the laptop will shutdown normally and restart without issue. And it sleeps and awakens normally when the USB tuner is not plugged in. But when the tuner is plugged in, once it has attempted to sleep, it's hung and requires a forced power-off restart.

I have examined /var/log/system.log and see no differences in logged events when suspend is requested with and without the USB stick plugged in.

After having booted with the USB tuner unplugged, if I plug it in; its various embedded devices appear in /dev/dvb/adapter0 but MythTV reports All tuners busy and MythTV doesn't work. But after rebooting the box or restarting the mythtv-backend service from that tuners busy state, with the USB stick remaining plugged in, all works as desired -- except sleep.

So plugging the stick in after first-boot requires me to manually restart the services that are trying to use it. And once it's plugged in, the system will not suspend (or, at least, cannot awaken from suspend).

Hi Chucko,

I think you yourself have put your finger on the issue : the service for MythTV is preventing the system from successfully going through a suspend-resume cycle. This is a common occurrence for all sorts of reasons - often even caused by something as ubiquitous as WiFi adapters.

Since you've figured out yourself that the system suspends and resumes properly if you at first stop the MythTV service, then that is simply what I would do. Stop the service - suspend - resume - start the service. If you don't like doing this manually, you could create a script incorporating these steps and have it execute automatically when suspending.

Hope this helps - Cheers.

1 members found this post helpful.

Rickkkk: Thanks. Sorry for the late response. My email service shuttled the notification to me about your response into my spam folder and I'm only just now seeing it. Anyway, I'll work on some sort of a script to coordinate stopping and restarting the backend with suspending the box. I'm a bit surprised, though, that I'm the only one with this issue. I guess I'm just special!

... You may not be the only person with this issue ... Suspend-resume issues vary greatly depending on hardware, distro, kernel version, systemd or not, which services running, attached peripherals .. Bottom line - few situations are identical.

Hope you get it configured to your satisfaction !