Comment 2 for bug 1680750

Revision history for this message
Joshua Powers (powersj) wrote :

@teo8976, thanks for reporting this.

Currently there is insufficient information to even begin work on this report. If we are to track down a root cause or help your diagnose this any further then we would need to know more.

I am no expert on pm-utils, but I think the following would get something going:

1. It sounds like this used to work? Was it working on 16.04 and only recently broke?
2. What model is your hardware?
3. Did you recently update the system BIOS? Are you running the latest? You can collect this by running sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

I cannot promise this will get you a resolution, but more information is indeed required. I am marking this as 'incomplete' and feel free to move it back to 'new' when you respond.