On Mon, Apr 26 2010 at 02:30, Andrea Bolognani wrote:
So, as I mentioned above, I have two X servers from stable with two
different drivers and one scrotwm from testing, which connects to X
server via tcp socket.
So the version of Xlib (or related libraries) used by the X server is
differen
On Mon, Apr 26 2010 at 21:53, Dmitry Derjavin wrote:
And -- please don't forget about it -- scrotwm works well with all of
my mixed library versions when started from another terminal.
We have a workaround! Adding 'sleep 1' before scrotwm invocation in
.xsession script helps. It looks like a
Do both of you still get the bug?
Yes, still the same situation I described last time.
Hannes, did you try to start scrotwm from an X terminal?
It works then.
I think it's fair to assume that this is some sort of startup issue as
it seems to be properly initialised when run from an xterm
And -- please don't forget about it -- scrotwm works well with all
of my mixed library versions when started from another terminal.
We have a workaround! Adding 'sleep 1' before scrotwm invocation in
.xsession script helps. It looks like a race condition.
Unfortunately, this does not
On Mon, Apr 19 2010 at 14:57, Andrea Bolognani wrote:
It seems like Xorg is undergoing a lot of updates and changes, lately,
so I wonder — like Hannes did — if the bug wasn’t triggered by some
bug in the underlying infrastructure, with video drivers being the
most likely cause due to KMS and
On Sat, Apr 24 2010 at 15:23, Andrea Bolognani wrote:
I think it's not video drivers, because I tried to run scrotwm with two
X servers -- one on Nvidia and another on ATI with the same result.
In both cases it was 1:7.3+20 from stable.
Scrotwm itself was installed on both stable and
Sorry for my long silence. Since first reporting the problem, I've done
regular updates from the testing branch, of course. When I tried things
out again after reading Dimitry's suggestions today, this lead to some
interesting new developments:
When I put scrotwm in my .xsession file and run
On Thu, Mar 18, 2010 at 01:06:45PM +0100, Hannes wrote:
Sorry for my long silence. Since first reporting the problem, I've done
regular updates from the testing branch, of course. When I tried things
out again after reading Dimitry's suggestions today, this lead to some
interesting new
On Tue, Mar 16 2010 at 23:07, Andrea Bolognani wrote:
I can reproduce the bug when starting scrotwm from .xsession with xdm.
But if I run it manually from any terminal with properly set $DISPLAY
-- screen, xterm, VT -- it works just perfectly.
Steps to reproduce:
- create ~/.xsession
I can reproduce the bug when starting scrotwm from .xsession with xdm.
But if I run it manually from any terminal with properly set $DISPLAY
-- screen, xterm, VT -- it works just perfectly.
Steps to reproduce:
- create ~/.xsession with the only line containing 'xterm';
- log in to xdm
So, if the problem occurs even when libswmhack is not present, we can
rule out a libswmhack problem, can't we?
Yes, I think so. libswmhack only causes 'more of the same' problems
if .xsession-errors is to be believed. I went for that conclusion at
first, because Marco Peereboom had told me the
11 matches
Mail list logo
