screensaver

[Bill Fink]

Unfortunately installing kdeaddons3 didn't help any.  Messing around some
more with strace, I have now determined that when it tries to access the
file /usr/bin/??????????? instead of /usr/bin/kmatrix.kss, that those
really are 11 '?' characters in the filename.

I have a new theory.  The '?' character is 0x3F.  Since all the characters
come out the same, and since the kmatrix.css name comes from the Exec=
line in the /usr/share/applnk/System/ScreenSavers/KMatrix.desktop file,
where Encoding=UTF-8 is specified, I'm thinking that multi-byte characters
are being used for internationalization support, and due to endianness
issues (PPC versus PC) the wrong byte is getting used out of a multi-byte
character, but this is all pure conjecture on my part.

I even tried making a symbolic link from /usr/bin/??????????? to
/usr/bin/kmatrix.kss, and when I tried to do a test of the Matrix
screensaver from the KDE control center it did appear to do _something_,
but it still didn't work.  The strace also showed that the access of
/usr/bin/??????????? succeeded which had always failed before.

So it does appear to be a KDE bug (or possibly a bug in some system
library that KDE uses).

						-Regards

						-Bill



On Fri, 12 Jul 2002, Michael wrote:

> Well in my case this was due to the fact that I did not install kdeaddons3.
> 
> Once you do that you should be fine.
> 
> Michael :o)
> 
> PS.... sorry I didn't post this message when I solved the problem.
> 
> 
> 
> On Sunday 07 July 2002 01:19 am, Bill Fink wrote:
> > I have the same problem.  After upgrading from KDE 2.2.1 to 3.0.1,
> > none of the KDE screen savers work.  I cannot even do a setup or
> > test of any of the screensavers.  However, I can manually run
> > kmatrix.kss just fine from the command line.
> >
> > I tracked this down somewhat and it definitely appears to be a bug
> > somewhere in KDE.  I started up the KDE control center, and then did
> > an strace on this process.  When I did a test of the Matrix screensaver
> > I got:
> >
> > access("/usr/bin/???????????", F_OK)    = -1 ENOENT (No such file or
> > directory)
> >
> > This should have been an access of /usr/bin/kmatrix.kss.  Note that the
> > number of '?' characters is equal to the number of characters in
> > kmatrix.kss. I suspect a signed versus unsigned character problem causing
> > the high order bit in the character to be set (I am running on a PPC
> > system).  I tried to verify my suspicion by using the "-x" or "-xx" option
> > to strace but it still printed "/usr/bin/???????????" rather than the hex
> > values I wanted to see.
> >
> > So this definitely seems to be a KDE bug, but I couldn't come up with
> > any workaround to get it to work properly.
> >
> > 						-Regards
> >
> > 						-Bill
> >
> > P.S.  I am not subscribed to this list.
> >
> > On 2002-05-21, Michael Lawver wrote:
> > > They do not function at all.
> > >
> > > I'm not referring to xscreensaver at all here.  After I upgraded to dke3,
> > > all of the default screensavers in kde simply do not function any more. 
> > > In fact, you can't even see the previews for any of them working.
> > >
> > > I've seen this on two machines now, any Ideas on what could be causing it
> > > and how it may be corrected? (As per my original posting)
> > >
> > > Michael
> > >
> > > On Monday 20 May 2002 10:48 am, James Richard Tyrer wrote:
> > > > Michael wrote:
> > > > > Hello,
> > > > >
> > > > > I just recently updated my FreeBSD to run kde3.
> > > > >
> > > > > The problem I have is that my screensaver worked just fine under
> > > > > kde2.2.2 but now no longer works under kde3.
> > > > >
> > > > > I've seen this occur twice now since I've updated from kde2 to kde3
> > > > > on another machine.
> > > > >
> > > > > Any suggestions on what could be causing this and how I can correct
> > > > > it?
> > > >
> > > > What does "no longer works" mean?
> > > >
> > > > When I installed KDE3 on my Linux system, it didn't find the
> > > > xscreensaver files.  I opened a Konsole, added:
> > > > "/usr/X11R6/lib/xscreensaver" to the PATH, and ran "kappfinder".  Now
> > > > Control Center lists all of them OK.
> > > >
> > > > Does anyone know why Penrose won't work?
> >
> > ___________________________________________________
> > This message is from the kde mailing list.
> > Account management:  http://mail.kde.org/mailman/listinfo/kde.
> > Archives: http://lists.kde.org/.
> > More info: http://www.kde.org/faq.html.
___________________________________________________
This message is from the kde mailing list.
Account management:  http://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.