With today's update (or yesterday's, many traffic these days) I seem not to need the thinkpad_acpi update any more, as long as I use the VESA driver.
I just did one suspend 2 ram, one hibernate, resume was ok both times.
I use amd64 only, so if Robbob tests with i386 this issue could eventually be assigned to the nvidia-glx-new package.
Let's just hope NVidia solves the problem soon.
Fortunately, their driver is easy to install for expierienced users, so personally I could live with manual driver upgrades after gutsy release.
One more observation:
With nvidia drivers (and nvidia's NV-GLX), glx apps die immediately with a memory fault when started as normal user, but work when started as root.
Looks like a wrong file mode, but I don't care for now.
With today's update (or yesterday's, many traffic these days) I seem not to need the thinkpad_acpi update any more, as long as I use the VESA driver.
I just did one suspend 2 ram, one hibernate, resume was ok both times.
I use amd64 only, so if Robbob tests with i386 this issue could eventually be assigned to the nvidia-glx-new package.
Let's just hope NVidia solves the problem soon.
Fortunately, their driver is easy to install for expierienced users, so personally I could live with manual driver upgrades after gutsy release.
One more observation:
With nvidia drivers (and nvidia's NV-GLX), glx apps die immediately with a memory fault when started as normal user, but work when started as root.
Looks like a wrong file mode, but I don't care for now.