Well, I didn't, it's spotty and happened to align with my tests, but I do observer something else.
Sometimes the dbus_g_proxy_call just returns 0 and retval is also set to zero, and error is NULL. I've started digging into the dbus part of it, but the whole gnome-power-manager-dbus-hal interaction is more complex than I can readily understand. Oh, and to add to the issue, when the computer does fail to suspend (in my case, occasionally NetworkManager process goes nuts and prevents the actual internal kernel suspend from happening), it doesn't report an error. I don't know if the actual writing of mem to sys/power/state could be even theoretically caught, but I'm starting to think that the message is useless, as it most often for me indicates the exact opposite of reality. -- gpm says my computer failed to suspend even when it suspends/resumes fine https://bugs.launchpad.net/bugs/138824 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
