As a workaround, I did the following (in a root terminal):
cd /usr/bin
mv gnome-screensaver gnome-screensver.karmic
cp -a /media/Jaunty-64/usr/bin/gnome-screensaver gnome-screensaver.jaunty
cp gnome-screensaver.jaunty gnome-screensaver
(I then performed the reboot required for today's kernel update.)
This was sufficient to restore the desired behavior. I've noticed no problems after my brief testing.
Notes:
1) "Jaunty-64" is my old 9.04 root partition. Not everyone would have this available. In that case, downloading the appropriate jaunty package and exploding it (dpkg-deb --extract) would provide the appropriate file.
2) I chose to do copies instead of symlinks so that a future package update won't clobber my jaunty copy.
It may be possible to manually install the jaunty package, forcing the version. However I have no idea how that may affect the rest of the system. Besides, that would hide any new updates that might correct the problem.
If I read http:// svn.gnome. org/viewvc/ gnome-screensav er/trunk/ src/gs- monitor. c?view= log correctly, the FIXME was introduced in rev 1578 on 18-Jan. There has been no activity since 20-Jan on gs-monitor.c.
As a workaround, I did the following (in a root terminal):
cd /usr/bin r.karmic Jaunty- 64/usr/ bin/gnome- screensaver gnome-screensav er.jaunty er.jaunty gnome-screensaver
mv gnome-screensaver gnome-screensve
cp -a /media/
cp gnome-screensav
(I then performed the reboot required for today's kernel update.)
This was sufficient to restore the desired behavior. I've noticed no problems after my brief testing.
Notes:
1) "Jaunty-64" is my old 9.04 root partition. Not everyone would have this available. In that case, downloading the appropriate jaunty package and exploding it (dpkg-deb --extract) would provide the appropriate file.
2) I chose to do copies instead of symlinks so that a future package update won't clobber my jaunty copy.
It may be possible to manually install the jaunty package, forcing the version. However I have no idea how that may affect the rest of the system. Besides, that would hide any new updates that might correct the problem.