Sorry, I may not be able to offer specific help, but I have some
general advice:
Generally you don't want to mess with your system's file structure.
What I mean is that copying/moving files around is usually a Bad Idea.
Of course, the exception is stuff in /usr/local, which is intended for
stuff you maintain on your own, outside the scope of dpkg. The reason
is that dpkg won't know to clean out the stuff from wherever you copy
it to when you try to remove or upgrade the package.
A better solution in times like these is to find out where the files
are being sought: if you have a config file that searches in
/usr/X11R6/bin/lmorph, change the *config* file to
/usr/X11R6/lib/xscreensaver. I'd say to start by opening up
~/.xscreensaver and seeing if it uses absolute (and obsolete) paths.
I think the paths aren't usually explicitly specified, so take this
piece of advice from xscreensaver(1):
Make sure your $PATH environment variable is set
up correctly before xscreensaver is launched, or
it won't be able to find the programs listed in
the programs resource.
Meaning, specifically, add /usr/X11R6/lib/xscreensaver to your $PATH.
Vineet
* Krisno Pryosusilo (krisno@aeroden.com.au) [010630 10:13]:
> Hi all,
> I'm not sure where to start looking for a solution, or if I should just
> wait to see if this fixes itself ... and I'm hoping for some pointers :).
> I'm using Progeny Debian (on a laptop) and have recently done an upgrade
> using the gnome-apt tool which comes with the distro. Since my latest
> update, my screensaver doesn't work anymore.
> I have noticed that the screensaver files (I use lmorph) have moved
> from /usr/X11R6/bin to /usr/X11R6/lib/xscreensaver ... however merely
> copying the files back to the original path doesn't seem to work ...
>
> Thanks in advance,
>
> Krisno
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Attachment:
pgpfdKK24SeF7.pgp
Description: PGP signature