> I find it strange, if I read it correctly, that it first succeeds
> to replace the -*-helvetica-bold-r-*-*-*-140-*-*-*-*-iso8859-1 font
> (with -*-*-medium-r-*-*-*-140-*-*-p-*-iso10646-1) twice but fails the
> third time…
I think the output is still truncated on that third attempt. It should
Hello,
On Wed, Aug 19, 2020 at 11:42:55PM +0200, Nicolas Boullis wrote:
>
> On Sun, Aug 16, 2020 at 09:58:04AM -0700, Jamie Zawinski wrote:
> >
> > If you're feeling adventurous, rebuilding with DEBUG defined in
> > utils/font-retry.c and sending me the output of a run with that version
> >
Hi,
On Sun, Aug 16, 2020 at 11:04:55AM -0700, Jamie Zawinski wrote:
>
> I assure you, I did not write all that code for shits and giggles, but
> to fix an actual problem people were experiencing on font-bereft
> systems like yours.
I did not pretend you wrote any code for no good reason. To
> Well, that “set of garbage fonts” is fine for XScreenSaver 5.36…
I assure you, I did not write all that code for shits and giggles, but to fix
an actual problem people were experiencing on font-bereft systems like yours.
>> so it would be helpful if you send me the output of xlsfonts on
Hello,
On Sun, Aug 16, 2020 at 09:58:04AM -0700, Jamie Zawinski wrote:
> XScreenSaver (as of 5.42) tries really hard to do something sensible
> with whatever set of garbage fonts you happen to have installed,
Well, that “set of garbage fonts” is fine for XScreenSaver 5.36…
> so it would be
XScreenSaver (as of 5.42) tries really hard to do something sensible with
whatever set of garbage fonts you happen to have installed, so it would be
helpful if you send me the output of xlsfonts on your system where it's doing
something terrible.
Is there anything about fonts in the log output
Package: xscreensaver
Version: 5.42+dfsg1-1
Followup-For: Bug #932837
Dear Maintainer,
For what it’s worth, I just upgraded my laptop from stretch to buster
and started experiencing exactly the same problem as Jacob Adams.
Here is a screenshot that show the unlock dialog.
I tried to downgrade
On 7/29/19 6:55 PM, Tormod Volden wrote:
>> Kernel taint flags: TAINT_USER
>
> BTW, do you know why your kernel is tainted?
I have no idea. It seems like TAINT_USER is really generic, so I'm not sure how
I would track it down.
>
>>> If you really think its a kernel problem then I can certainly
> Kernel taint flags: TAINT_USER
BTW, do you know why your kernel is tainted?
> > If you really think its a kernel problem then I can certainly build a newer
> > version to test, but I don't currently have the time and there's nothing
> > newer
> > available from Debian AFAIK, not even in
On 7/29/19 1:56 PM, Jacob Adams wrote:
> If you really think its a kernel problem then I can certainly build a newer
> version to test, but I don't currently have the time and there's nothing newer
> available from Debian AFAIK, not even in unstable.
Forgot about experimental. Pulled 5.0.2-1~exp1
On 7/29/19 9:18 AM, Tormod Volden wrote:
> On Tue, Jul 23, 2019 at 9:33 PM Jacob Adams wrote:
>>
>> No text at all appears in the unlock dialog.
>> The version number and the text in the buttons simply is not visible.
>
> Hi Jacob,
>
> Thanks for your bug report. Can you please try to check if
On Tue, Jul 23, 2019 at 9:33 PM Jacob Adams wrote:
>
> No text at all appears in the unlock dialog.
> The version number and the text in the buttons simply is not visible.
Hi Jacob,
Thanks for your bug report. Can you please try to check if it is
related to the graphics driver? Can you try a
Package: xscreensaver
Version: 5.42+dfsg1-1
Severity: normal
No text at all appears in the unlock dialog.
The version number and the text in the buttons simply is not visible.
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64
13 matches
Mail list logo
