On Thu, Nov 20, 2008 at 11:47:49PM +0100, Moritz Muehlenhoff wrote:
> On Sat, Nov 15, 2008 at 11:55:55PM -0800, Steve Langasek wrote:
> > On Wed, Oct 22, 2008 at 08:49:27AM +0200, Thomas Viehmann wrote:
> > Well, that sounds better than the current state, but a) the code for it
> > isn't written a
On Sat, Nov 15, 2008 at 11:55:55PM -0800, Steve Langasek wrote:
> On Wed, Oct 22, 2008 at 08:49:27AM +0200, Thomas Viehmann wrote:
>
> > probably I'm just dense, but why would (the admittedly gross hack) of
> > looking at /proc/$XSCREENSAVER-PID/environ (for DISPLAY and XAUTHORITY),
> > getting ui
Hi Steve,
thanks for your input on this.
Steve Langasek wrote:
> Well, that sounds better than the current state, but a) the code for it
> isn't written and I'm not familiar enough with xscreensaver to be confident
> of getting it right on the first try myself, b) we have to cover more than
> jus
On Wed, Oct 22, 2008 at 08:49:27AM +0200, Thomas Viehmann wrote:
> probably I'm just dense, but why would (the admittedly gross hack) of
> looking at /proc/$XSCREENSAVER-PID/environ (for DISPLAY and XAUTHORITY),
> getting uid for that process, trying xscreensaver-command -exit, if the
> screensave
Hi,
probably I'm just dense, but why would (the admittedly gross hack) of
looking at /proc/$XSCREENSAVER-PID/environ (for DISPLAY and XAUTHORITY),
getting uid for that process, trying xscreensaver-command -exit, if the
screensaver exited, start xscreensaver again with that uid and environ,
otherwi
5 matches
Mail list logo
