Hi there,

in recent times I have problems to correctly suspend my system.

I now saw when suspending failed, I get this error message in /var/log/pm-suspend.log I guess NETWM is related to KDE, so maybe someone has a hint what this message means:

Code: Select all

NETWM: Warning readIcon() needs buffer adjustment!

I think I get this warning only at failed suspend.
Where does this message point to?
Is there a place where I could change this strange buffer?

Oh, and when I restart KWIN and try suspending again, it often works. So there is some relation to suspend issues and KWIN, but the warning from above is the only error message I have.

Thanks

KWindowSystem - a static function that reads the icon image from the window property.
The message means that the icon size exceeds available buffer and more memory needs to be allocated.

The function is usually invoked by kwin and taskbar, but also ksysguard and python bindings.
The debug is printed via fprintf() to stderr, so given the location probably caused by sth. that's invoked by pm-utils.

It's hard to say whether and why restarting KWin would "often" restore the ability to suspend, but I'm fairly sure the link is somewhere in your pm-utils scripts
If suspending fails, also try to write into /sys/power/state to check whther it's the kernel (nvidia?) or sth. in the userspace that blocks it.

luebking wrote:If suspending fails, also try to write into /sys/power/state to check whther it's the kernel (nvidia?) or sth. in the userspace that blocks it.

I don´t understand this sentence...

What do you mean with "try to write into /sys/power/state"?

Isn´t this what I do when invoking echo mem > /sys/power/state?

Ah, you mean when pm-suspend fails I should write to /sys/power/state? Well, this is what I actually did. When pm-suspend failed, I did echo mem > /sys/power/state.

Ah, you mean when pm-suspend fails I should write to /sys/power/state?

Yes - reading what i wrote, i see why referencing STR through userspace tools as "suspending" is confusing =)
Sorry for that.

Was writing into /sys/power/state successful (while pm-suspend failed) then?