Hello, sorry for the delay,
Just like Michael, the latest patch against 5.07 allows xscreensaver to
work properly:
...
xscreensaver: 17:52:52: WARNING: RANDR says all screens are 0x0! Ignoring it.
xscreensaver: 17:52:52: screens in use: 1
xscreensaver: 17:52:52:0/0: 1280x1024+0+0
...
So
On Aug 20, 2008, at 9:04 AM, Pierre Ynard wrote:
I assume that there is still a problem with RANDR, which was already
there before the upgrade of xscreensaver broke?
Yes, it's crazy that RANDR is reporting a screen of size 0x0.
--
Jamie Zawinski [EMAIL PROTECTED]
So I ran xrandr --verbose and got the following:
= OUTPUT OF xrandr --verbose
Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
default connected (normal)
Identifier: 0x46
Timestamp: 983056
Subpixel: unknown
Clones:
CRTCs:
Can you try this patch against 5.07, and see what it does when your X
server is configured in the way that was resulting in a 0x0 screen
before? Thanks...
cvs diff: Diffing .
Index: screens.c
===
RCS file:
On Thu, 14 Aug 2008 01:57:44 PDT, Jamie Zawinski wrote:
Can you try this patch against 5.07, and see what it does when your X
server is configured in the way that was resulting in a 0x0 screen
before? Thanks...
This patch does work on my system. I included xscreensaver.log below
from a
On Aug 14, 2008, at 9:52 AM, Michael H Buselli wrote:
On Thu, 14 Aug 2008 01:57:44 PDT, Jamie Zawinski wrote:
Can you try this patch against 5.07, and see what it does when your X
server is configured in the way that was resulting in a 0x0 screen
before? Thanks...
This patch does work on
On Thu, 14 Aug 2008 10:00:53 PDT, Jamie Zawinski wrote:
Does anything sensible happen if xscreensaver is running and you
resize the screen with the xrandr program? (I'm guessing no, it
does something wrong, but that there's nothing I can do about that.)
No, xrandr is unable to resize my
Jamie Zawinski [EMAIL PROTECTED] said:
There have been so many patches flying by that I don't really know
what code you're actually running any more. Please let me know what
happens when you are finally able to try this with xscreensaver 5.07,
rather than a multiply-patched 5.06.
Please show me the output of the test-xinerama and test-randr
programs from the xscreensaver/driver/ directory. Thanks!
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
On Wed, 13 Aug 2008 20:42:54 PDT, Jamie Zawinski wrote:
Please show me the output of the test-xinerama and test-randr
programs from the xscreensaver/driver/ directory. Thanks!
= test-xinerama
test-xinerama: 22:58:26: XineramaQueryExtension(dpy, ...) == 0, 0
test-xinerama: 22:58:26:
On Aug 13, 2008, at 9:02 PM, Michael H Buselli wrote:
test-randr: 22:58:49: sizes: none
Ok, well, see that there? Where RANDR says you have one screen with
no available orientations or sizes?
What the hell am I supposed to do with that?
G...
--
Jamie Zawinski [EMAIL
On Wed, 13 Aug 2008 21:24:00 PDT, Jamie Zawinski wrote:
test-randr: 22:58:49: sizes: none
Ok, well, see that there? Where RANDR says you have one screen with
no available orientations or sizes?
What the hell am I supposed to do with that?
I'll toy with my system and see if I can
Package: xscreensaver
Version: 5.05-3
Severity: important
Hello,
After upgrading from version 5.05-1 and restarting my X session,
xscreensaver doesn't work anymore. Nothing happens after the specified
inactivity delay. An xscreensaver -noslash process is running as
usual. When started
The existing xscreensaver process must be hung somehow. Attach a gdb
to it and send a stack trace. Make sure you are running a version
that was compiled with -g.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
14 matches
Mail list logo
