On Thu, 14 Apr 2016 10:06:38 +0200 Tormod Volden wrote:
> On Thu, Apr 14, 2016 at 1:38 AM, Jamie Zawinski wrote:
> > I'm not going to change anything here. Xscreensaver is working as designed.
> > The problem being experienced is because the system it is running on is
> > misconfigured.
> >
> >
Le jeudi 7 avril 2016, 22:45:20 Tormod Volden a écrit :
> On Sat, Mar 5, 2016 at 5:22 PM, Alexandre Detiste
> >
> > I'd like to help on this bug, and the 106 other ones.
> >
>
> Alexandre,
>
> That would be fantastic!
I said so right before I got this mission with a 6 hours daily commute :-)
On Thu, Apr 14, 2016 at 1:38 AM, Jamie Zawinski wrote:
> I'm not going to change anything here. Xscreensaver is working as designed.
> The problem being experienced is because the system it is running on is
> misconfigured.
>
> Specifically, xscreensaver is only halfway installed;
I'm not going to change anything here. Xscreensaver is working as designed. The
problem being experienced is because the system it is running on is
misconfigured.
Specifically, xscreensaver is only halfway installed; and it is configured to
run modes that the half-install does not include.
On Sat, Apr 9, 2016 at 5:41 AM, Jamie Zawinski wrote:
> I still think the root of the problem here is that the "zoom" xscreensaver
> hack is marked as enabled in the .ad file, but it is not actually installed.
> So the .ad file is wrong. Correcting it would fix this. I suppose it
I still think the root of the problem here is that the "zoom" xscreensaver hack
is marked as enabled in the .ad file, but it is not actually installed. So the
.ad file is wrong. Correcting it would fix this. I suppose it would be possible
to do that in a post-install script on the xscreensaver
On Fri, Apr 8, 2016 at 7:01 PM, Jamie Zawinski wrote:
> On Fri Apr 08 2016 02:12:12, Tormod Volden wrote:
>
>> But let me be clear, I am only talking about the part "let's start the
>> hack with name X". For running helpers etc it would be nice to have a
>> reasonable PATH so
On Fri Apr 08 2016 02:12:12, Tormod Volden wrote:
> But let me be clear, I am only talking about the part "let's start the
> hack with name X". For running helpers etc it would be nice to have a
> reasonable PATH so xscreensaver-get-images & friends can be found
> without that we force full paths
On Fri, Apr 8, 2016 at 12:35 AM, Jamie Zawinski wrote:
> If you modify xscreensaver to not obey $PATH, you are making it do this
> weird, confusing, undiscoverable thing.
>
> If you merely launch it with a different $PATH, then it's easy to know what's
> going on. Especially since
On Fri, Apr 8, 2016 at 12:39 AM, Jamie Zawinski wrote:
>
> Hey guess what, this is a problem that only exhibits itself because you took
> the code that I had tested and distributed, ripped half of it out, and
> expected the other half to continue working properly.
>
> I am shocked
> This bug does _NOT_ happen when "xscreensaver-data-extra"
> which provides /usr/lib/xscreensaver/zoom is also installed.
Hey guess what, this is a problem that only exhibits itself because you took
the code that I had tested and distributed, ripped half of it out, and expected
the other half
If you modify xscreensaver to not obey $PATH, you are making it do this weird,
confusing, undiscoverable thing.
If you merely launch it with a different $PATH, then it's easy to know what's
going on. Especially since the $PATH appears in error messages about not being
able to find things.
>
On Thu, Apr 7, 2016 at 10:54 PM, Jamie Zawinski wrote:
> Having xscreensaver override and ignore the $PATH that the user passed in is
> a terrible idea.
Since we are in control of where we install the hacks
(/usr/lib/xscreensaver), it is not that bad. But it would prevent the
user
Having xscreensaver override and ignore the $PATH that the user passed in is a
terrible idea.
But if init scripts are involved, perhaps those scripts should launch
xscreensaver without /usr/games/ on $PATH.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
On Sat, Mar 5, 2016 at 5:22 PM, Alexandre Detiste
wrote:
> Le samedi 5 mars 2016, 16:29:41 Stephen Kitt a écrit :
>>
>> Or perhaps xscreensaver-demo should only look in /usr/lib/xscreensaver...
>> (For the xscreensaver maintainers: the context here is that the
Le samedi 5 mars 2016, 16:29:41 Stephen Kitt a écrit :
>
> Or perhaps xscreensaver-demo should only look in /usr/lib/xscreensaver...
> (For the xscreensaver maintainers: the context here is that the zoom-player
> package provides /usr/games/zoom, which xscreensaver attempts to use for its
> Zoom
Control: reassign -1 xscreensaver
On Fri, 04 Mar 2016 12:50:02 +0100, Alexandre Detiste
wrote:
> xscreensaver tried to run 'zoom'; which resulted in this text in a
> ugly yellow font on black backgroud:
>
> "zoom: invalid option -- 'r'
> Try `zoom --help' or `zoom
Package: zoom-player
Version: 1.1.5~dfsg-2
Severity: normal
Hi,
xscreensaver tried to run 'zoom'; which resulted in this text in a
ugly yellow font on black backgroud:
"zoom: invalid option -- 'r'
Try `zoom --help' or `zoom --usage' for more information."
This can be reproduced with
18 matches
Mail list logo