upgrade xscreensaver.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Even if X server is to blame for the hack looping xscreensaver is to
blame for not unlocking the screen. If I can kill the hack
xscreensaver can too. And the reason the hacks are separate is
exactly that xscreensaver need not rely on their correct operation
for xscreensaver itself to
This is a bug in your X server / video driver, not xscreensaver.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Seriously dude, just configure your X server properly. This is not an
xscreensaver problem.
If you think you have both square pixels, and different DPI
horizontally and vertically, then I think you don't know what DPI
stands for.
--
To UNSUBSCRIBE, email to
There is zero chance that xscreensaver will ever be modified to handle
non-square pixels.
Configure your X server to handle your video card sanely, or go buy a
video card that doesn't suck.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
You're funny.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Read the FAQ. You can't control xscreensaver with xset. This is by
design.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
This almost certainly means that your video card only supports gamma
modification on one of the two screens. This is stupid, but not
uncommon. Hardware problem.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
It says your second screen is turned off:
xscreensaver: 04:12:27: screens in use: 1
xscreensaver: 04:12:27:0/0: 1920x1200+0+0 (VGA-0)
xscreensaver: 04:12:27: rejected screens: 2
xscreensaver: 04:12:27:1/0: 1920x1200+0+0 (DVI-0) -- output disabled
xscreensaver: 04:12:27:2/0:
Launch xscreensaver with xscreensaver -verbose -log log.txt and send
the log.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
a bug in the nvidia driver's implementation
of RANDR extension that xscreensaver 5.07 works around but 5.05 didn't.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com
Try it with 5.07. I'm boycotting all Debian bugs until they upgrade
the damned thing already.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fixed in 5.07.
Come on already, Debian people -- will you please push out the new
version so that we stop getting these reports?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
If you are using PAM, then it should not be necessary for xscreensaver
to be setuid. Some component of the PAM stack should be setuid
instead (or else PAM can't ever work for non-setuid programs).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
On Aug 28, 2008, at 7:57 AM, Gary Kramlich wrote:
I'm still seeing this in sid. 5.05-3.
This is unsurprising, since (as I said) it's fixed in 5.07.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Aug 20, 2008, at 2:07 AM, Paul Slootman wrote:
But why not revert to the old behaviour of showing the failed login
attempts in the password entry window, instead of a separate popup?
Because that would be harder and I'm lazy?
--
Jamie Zawinski [EMAIL PROTECTED
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] http
against it too.
This is all that I know about how to make mplayer behave:
http://www.jwz.org/xscreensaver/faq.html#dvd
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com
faq. What's your point?
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
http://jwz.livejournal.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
is seen! */
+ /* case KeyRelease:*/
+ /* case ButtonRelease:*/
case MotionNotify:
if (p-debug_p)
@@ -1083,8 +1086,6 @@
if (until_idle_p si-cycle_id)/* no cycle timer when inactive */
abort ();
-
- return;
}
--
Jamie Zawinski [EMAIL PROTECTED
You've got some other program running that is grabbing the kbd and
preventing xscreensaver from being able to activate.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com
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:
Ok, let me make sure I understand this:
- your monitor is currently rotated 90 degrees
- in that configuration, it is 1200 pixels horizontally and 1600
pixels vertically
- you have RANDR 1.2
So, in that state, test-randr shows:
test-randr: 10:03:45: Current Rotation:90
there is. I think the only options I have
available are PAM_SUCCESS and PAM_CONV_ERR. (I think that PAM_ABORT
means internal error, not cancel.)
So, yeah. PAM sucks.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http
where someone really did type the wrong password,
there's no way to tell the difference between that and didn't try.
Also, those incorrect attempts are logged in syslog too.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED
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
Well, I had someone else report that to get the right sizes, I had to
do that swap width and height is RR_Rotate_* is set nonsense. But
if you're still seeing it mis-rotated, then that means that on your
system, it will probably work if you comment those lines out. Which
means -- I have
to believe RANDR and not Xinerama,
or they get one big screen instead of two screens.
Can you send the output of the test-xinerama and test-randr
programs from xscreensaver/driver/?
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL
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 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
Please try 5.07.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Aug 4, 2008, at 4:55 AM, sebastien wrote:
The writer of xscreensaver reply that this bug was fixed with later
version.
What I said was, this is not an xscreensaver bug, it was fixed in a
later version *of Perl*.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482280
--
To
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]
I don't know how to fix this, but it's probably not easy. Since I
don't particularly care, I'm not going to try. Sorry.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Jul 16, 2008, at 9:38 AM, Andrzej Novak wrote:
I just had to replace the one installed by the pristine source package
with the one included in the Debian package. I don't know exactly why
the one from source package didn't work (I don't know much about PAM,
and I see all three files in my
crashes (obviously!)
- There is ever a situation where a screen is not
completely covered by the xscreensaver windows.
(Unless two screens are configured to overlap).
Thanks!
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL
Works for me:
% xscreensaver-command -deactivate
xscreensaver-command: not active: idle timer reset.
xscreensaver: 13:42:23: ClientMessage DEACTIVATE received while
inactive: resetting idle timer.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
a new computer just for this.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
http://jwz.livejournal.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
Uh, that's what xscreensaver/driver/screensaver-properties.desktop is...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
your root window. See which one
blows up.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
http://jwz.livejournal.com/
--
To UNSUBSCRIBE, email
Did you test what happens if nscreens remains 0 for some length of
time, e.g., through another idle cycle? I'm guessing the answer is
nothing good...
It's hard to tell just by looking at it, but I suspect that, for
example, with that change it's going to be running hacks on screens
that
I don't get it. How is it even possible for xfwm to interfere with
xscreensaver's windows? They are override-redirect.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Apr 3, 2008, at 8:52 AM, Lionel Elie Mamane wrote:
Here is a patch that fixes
the issue; the enclosed check was adding X coordinates to heights
and comparing the result; that's silly and a typo. I changed it to add
Y coordinates to heights.
Oops! That looks like the right fix, thanks.
I think this is fixed by the patch in bug 473681?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I think what this bug really says is: when xscreensaver-demo forks
xscreensaver, and then xscreensaver-demo's controlling terminal and
stdin/stdout go away, something bad happens to xscreensaver.
However, I can't reproduce that.
If any of you can reproduce it, perhaps it would fix it to
Thanks for your report. Yes, we should use x-terminal-emulator
instead,
which will pick an available terminal program.
Don't you have some GUI thing for displaying man pages?
Back in Gnome 1.4, gnome-help-browser man:qix worked, but they broke
that in Gnome 2.2. As of Gnome 2.6.3, yelp
On Mar 12, 2008, at 1:55 PM, Tormod Volden wrote:
We should not build our packages with any Gnome dependencies, since
they are often used on non-Gnome systems.
Is there actually a meaningful distinction between Gtk and Gnome
these days? I thought they had blurred that line long ago?
If
On Mar 3, 2008, at 2:19 AM, Tormod Volden wrote:
Believe me, the reason for the package split is exactly to make things
easier for third-party screensaver infrastructures (like
gnome-screensaver and kscreensaver), so that they can use xscreensaver
hacks without the user having xscreensaver
I, for one, actually like the leading zero. For me it makes the
display
feel complete when using 24 hour mode.
Jamie, what do you think?
I think it looks better with the leading zero.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
http://www.jwz.org/xscreensaver/faq.html#dpms-load
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Thanks! I think this is a bit simpler, though: does this patch work
for you?
diff -u -r1.32 fade.c
--- fade.c 9 Jul 2005 03:11:42 - 1.32
+++ fade.c 26 Jan 2008 23:10:18 -
@@ -157,6 +157,28 @@
}
+static void
+sleep_from (struct timeval *now, struct timeval *then,
to work at all.
However, if the system uses PAM, and PAM is configured properly, it
shouldn't be necessary.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com
I'd like to keep my xscreensaver settings in Git, which I currently do
for many other dotfiles. I want that configuration to contain a very
minimal set of settings, to just blank and lock:
Your wishes do not correspond with reality. Sorry. Not a bug.
--
To UNSUBSCRIBE, email to [EMAIL
See comments on this latest Xinerama/Randr braindamage at
https://bugzilla.redhat.com/show_bug.cgi?id=389501
Given that xscreensaver *worked fine* before the latest Randr started
causing Xinerama to claim that screens exist where there are no
screens, I consider this a Randr bug.
There may
Obviously, fireworkx should not be showing a transparent background.
Equally obviously, this is not a bug in xscreensaver. It's a bug in
the X server, or in some lower layer like the video driver. You
should reassign this.
Is fireworkx the only OpenGL saver that provokes this bug?
--
== RootWindow.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
http://jwz.livejournal.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On Nov 13, 2007, at 4:00 PM, Simon Huggins wrote:
This workrave program is in Debian so you can find out whatever it is
at: http://packages.debian.org/sid/workrave
Ok, but I'm not going to because I don't care.
I have no idea if it's changed the name of windows but I get the
message
a
Which whole log? It doesn't seem to be logging to .xsession-errors
sadly just spamming which ever xterm it was run from...
RTFAQ - http://www.jwz.org/xscreensaver/bugs.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Nov 5, 2007, at 4:11 PM, Steffen Joeris wrote:
With this patch, xscreensaver fails to build:
Sorry, typo: pw-prompt_screen should have been pw-prompt_screen-
screen. Revised patch:
diff -u -r1.85 lock.c
--- lock.c 10 Jul 2007 20:27:24 - 1.85
+++ lock.c 1 Nov 2007
What do you mean by screen is off?
Please describe exactly the symptom you are seeing.
I don't understand what you're trying to do with your patch.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Not the advanced *button*, the advanced *tab*, up at the top of the
window.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
root 918 Z13:07:10 [do_screen_saver] defunct
root 3898 Z16:05:37 [do_screen_saver] defunct
Hmm... The string do_screen_saver does not appear anywhere in the
xscreensaver source. Are you sure these zombies are being left by
xscreensaver and not some other package?
--
1) If a GL saver is consuming 100% CPU, then that means that OpenGL
is running on the CPU and not on the GPU, in other words, it's not
using your graphics hardware at all. So you should try and figure out
why that would be.
2) There's no way for xscreensaver to realize that it's not on the
also sprach Jamie Zawinski [EMAIL PROTECTED] [2007.09.19.1927 +0100]:
That's talking about RANDR, not Xinerama.
Please reread the bug report. It may not be obvious, but Raphaël is
using xrandr, which in turn uses Xinerama. The difference between
the two is that Xinerama was not expected
On Sep 19, 2007, at 2:55 AM, martin f krafft wrote:
See
http://lists.freedesktop.org/archives/xorg/2007-September/028432.html.
Restarting the xscreensaver daemon fixes it for me. The solution is
to make xscreensaver listen for XINERAMA change events.
What is a XINERAMA change event?
That's talking about RANDR, not Xinerama.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
That means that the xscreensaver executable is from a different
release than the installed app-defaults/XScreenSaver file: somehow
you have an older app-defaults file installed.
Just deleting it will fix the problem (it's ok to have no app-
defaults file at all, but it's not ok to have one
Didn't you guys solve this last time by using .6x for xscreensaver?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
That patch is already included in 5.03. But you people are still
shipping 4.24, which is nearly eighteen months old. I really wish
you'd upgrade already.
Also, it is damned near impossible to exploit that. For it to be a
problem, the attacker needs to have already compromised either the
4.24 is almost two years old. Does this happen with 5.02?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
All SDL does is use standard X calls to disable blanking and DPMS
while
it's running then reenable them when it exits.
Yeah, well, the standard X calls are insufficient for xscreensaver
to work properly.
You can support it explicitly, or you can continue to have things not
work right.
Intentional behavior, not a bug. When xscreensaver is in use,
xscreensaver-demo is the UI for setting blanking behavior, not
xset. There is no way to make both UIs co-exist sensibly, so
xscreensaver wins.
http://www.jwz.org/xscreensaver/faq.html#dvd
--
To UNSUBSCRIBE, email to [EMAIL
You are running a release that is 15 months old. Upgrade.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The way mplayer disables xscreensaver is idiotic, so it would not be
at all surprising that mplayer would also screw up your dpms settings.
The only sensible way for a video player to interact with xscreensaver:
http://www.jwz.org/xscreensaver/faq.html#dvd
The mplayer developers are aware of
to be gzipped. Or making sure that unused
localizations don't get installed.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
http://jwz.livejournal.com
You don't believe that, do you?
I believe it is the third-best solution, if the first two I mentioned
are unavailable.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I think you should take my word for it that this bug is *unfixable*
on the xscreensaver side. Your patch will not fix it, it will just
move the bug around. People have been complaining about this for
literally ten years, and in all that time, nobody (including me) has
come up with a
xsublim isn't really a screen saver. It doesn't work like the
others, and doesn't need an xml file (in fact, that wouldn't work).
See the man page.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xscreensaver-getimage uses gdk_pixbuf_new_from_file() to load images
(which is a format-agnostic routine that knows nothing about JPEG per
se). The only sane way to solve this is for either: GTK to auto-
rotate the images; or for GTK to tell the caller that the image
should be rotated.
your root window. See which one
blows up.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
http://jwz.livejournal.com/
--
To UNSUBSCRIBE, email
X sucks. FAQ: http://www.jwz.org/xscreensaver/faq.html#mouse-idle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Apr 16, 2006, at 10:27 AM, Manuel Lorenzo Frieiro wrote:
I have configured my system to use blowfish encrypted passwords,
since I
have changed this xscreensaver cannot unlock the screen
(authentication
failure).
I have broken my PAM configuration, and so I am reporting a bug
against
Thanks for your answer but I don't think that this error is on my
configuration or PAM modules.
Other programs (login, wdm, passwd, sudo, su, etc.) work correctly,
xscreensaver no.
Did xscreensaver work before you started messing with your PAM
config? Then your PAM config is what broke
This is intentional. Not a bug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
My problem is that when I come back and want to unlock, the screen
gets
unblanked _after_ I enter my password, which basically means I have
to enter
my password blindly.
If you're trying to say that the screen is still completely black
while xscreensaver has an (invisible but functioning)
So... you're running some external program to duplicate the work of
the XDPMS extension? E.g., xset dpms off. XScreenSaver does that
already, it's in preferences.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I tried to play with xset dpms options but it did not change
anything. My screen still does not shutdown completely with
xscreensaver. Am I missing something ?
If xset dpms off doesn't completely power off your monitor, then
your video driver is broken.
Get a working video driver, and
xset dpms force off does shutdown my screen. So it looks like my
video driver works, does it ?
If that powers off your screen, then xscreensaver should also be
powering off your screen, as per the DPMS settings in xscreensaver-demo.
If it's not, that's a bug. Perhaps your copy of
By log it I meant, of course, the log part where it actually blacks
your screen and (should have) powered off the monitor.
Leave it logging for several hours without interaction. Don't try to
influence the test with xscreensaver-command.
Unknown device ID 5460, please report. Assuming
to understand this crap.
Is the executable setuid?
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
http://jwz.livejournal.com/
--
To UNSUBSCRIBE, email
Uhm, http://www.jwz.org/xscreensaver/download.html still lists
The latest xscreensaver source, as a gzipped tar file:
xscreensaver-4.23.tar.gz
Oh, heh. I forgot I hadn't released that yet! Sorry.
Well, you've got something to look forward to!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
I understand this rationale, but it is still irritating to have it
running hacks that are known not to be installed.
Could there be an extra option, such that it *does* show the
uninstalled
hacks in the list, but it doesn't try to execute them?
That part was fixed in 4.24.
--
To
the
- monitor from powering down. */
- XForceScreenSaver (si-dpy, ScreenSaverReset);
-
- /* And if the monitor is already powered off, turn it on.
- You'd think the above would do that, but apparently not? */
- monitor_power_on (si);
}
--
Jamie Zawinski [EMAIL PROTECTED
is powering off one monitor and not the other? I
don't know why that would be...
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
http://jwz.livejournal.com
has to call setgid before setgroups? If so, reversing
the order of the calls around line 137 in setuid.c might fix it?
Ralf, can you verify that this program does work on your system, and
maybe direct me to the real problem?
Also see the test-uid.c program in xscreensaver/driver/.
--
Jamie
xscreensaver: 0: unrecognised ClientMessage WM_SOMETHING
This was fixed in 4.23.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
http
processes. E.g., xscreensaver
cannot use the VT_LOCKSWITCH ioctl (which would be a nice option to
prevent VT switching when the screen was locked) because that ioctl
can only be called by root (and xscreensaver has long discarded its
privs by the time it would want to use it).
--
Jamie
that the X server is running
on is not the selected one. You want the screen saver to un-throttle
when the user switches back.
However, I don't know how to tell A) which VT X is on; B) whether it
is the front; or C) when it changes.
--
Jamie Zawinski [EMAIL PROTECTED
reported a bug about this some time ago -- http://
bugzilla.gnome.org/show_bug.cgi?id=168231
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
http
target audience happens to be.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
http://jwz.livejournal.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
201 - 300 of 344 matches
Mail list logo
