[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#440679: kscreensaver: Phosphor scripting option removed?

Op Tuesday 04 September 2007, schreef Bert Verbeek:
> > the phosphor screensaver is just a wrapper around the phosphor
> > xscreensaver. What version of xscreensavers have you installed? if you
>
>   xscreensavers_5.03-2
>
> > downgrade to a earlier version of xscreensavers, do you get your options
> > back?
>
> A downgrade to
>
>   xscreensaver_4.24-5
>
> from stable gives the 'Text  Program' option back,
> and my script output is visible again.
>
> So, should I report this bug to xscreensavers?
> Or can you redirect it?
>
> Bert

I had contact with the maintainer from xscreensaver,
unfortunately without result.

I'm stuck now with two developers pointing at each other,
not an easy situation.

For your info the e-mail discussion with xscreensaver is attached.

I think the best would be, that you contact each other directly, 
for the case you want to resolve this bug. 
If not, please tag it as Won't fix.

Kind regards,
Bert Verbeek
--- Begin Message --- 
Hello Jose,

Thanks for your quick reply, even on Christmas Day!

First of all, Merry Christmas and a Happy New Year, to you.


Now I'm stuck with two developers pointing at each other,
not an easy situation.

I don't have the knowledge to decide were the problem is,
but maybe you can help me. I have two strong answers:

1. You have a strong point in pointing out that 5.03 works (5.04 in my 
situation) works. I tested also:
 
	/usr/lib/xscreensaver/phosphor -program <myscript> 

in a konsole. It works.

2. But what about the strong point of the kscreensaver team?

Downgrading xscreensaver only, to 

  xscreensaver_4.24-5

from stable gives the 'Text  Program' option back,
So the wrapper seems ok?


The only logic I can think of is that the interface for xscreensaver changed 
between 4.24 and 5.03 and kscreensaver is not aware of it?

I hope you will find the time to think about it,

Kind regards, 
bert Verbeek

Op Wednesday 26 December 2007, schreef u:
> Bert Verbeek wrote:
> > Hello,
> >
> > could you give your opinion about the bug I reported to the kscreensavers
> > package?
> >
> >   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440679
> >
> > As it looks now it might be an xscreensaver problem.
> >
> > Bert
>
> Well, I do not believe is a bug in xscreensaver since someone already
> reported use phosphor as terminal emulator with xscreensaver_5.03-2,
> there must be something in kscreensaver wrong. ;-)
>
> This is the proof that someone used it:
> http://bugs.debian.org/443443
>
> Regards.

--- End Message ---
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bert Verbeek wrote:
> Hello Jose,
> 
> Thanks for your quick reply, even on Christmas Day!
> 
> First of all, Merry Christmas and a Happy New Year, to you.
> 
> 
> Now I'm stuck with two developers pointing at each other,
> not an easy situation.
> 
> I don't have the knowledge to decide were the problem is,
> but maybe you can help me. I have two strong answers:
> 
> 1. You have a strong point in pointing out that 5.03 works (5.04 in my 
> situation) works. I tested also:
>  
> 	/usr/lib/xscreensaver/phosphor -program <myscript> 
> 
> in a konsole. It works.
> 
> 2. But what about the strong point of the kscreensaver team?
> 
> Downgrading xscreensaver only, to 
> 
>   xscreensaver_4.24-5
> 
> from stable gives the 'Text  Program' option back,
> So the wrapper seems ok?
> 
> 
> The only logic I can think of is that the interface for xscreensaver changed 
> between 4.24 and 5.03 and kscreensaver is not aware of it?
> 
> I hope you will find the time to think about it,

Well, I got your point, but there's nothing on xscreensaver that
modifies the wrapper in any way.

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
http://ghostbar.ath.cx/{about,acerca} - http://debian.org.ve
`ghostbar' @ irc.debian.org/#debian-ve,#debian-devel-es
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHdDWQOKCtW8rKsRgRArVNAJ98JMQFT1t6ytAvyF0QMOwo74k7rQCfaqg/
445hlHIWaRB2B6JT0K2m2LU=
=oZZ3
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: