Re: xnest on 10.5
Re: xnest on 10.5
- Subject: Re: xnest on 10.5
- From: William Scott <email@hidden>
- Date: Mon, 21 Jan 2008 19:38:15 -0800 (PST)
Dear Jeremy et al:
Here are three screenshots that explain the problem I am having:
http://tinyurl.com/39p6au
The first shows keyboard input working via Xnest (albeit imperfectly).
The second shows keyboard input getting garbled with Xephyr as a
replacement. Also no icons show up in the file browser, but they did
when I used Xnest. The third shows Xephyr behaving normally in a
locally nested twm session.
Bill
On Mon, 21 Jan 2008, Jeremy Huddleston wrote:
>> are you sure everything is working right with your SM/WM?
>
> Sorry, acronym lookup failure there.
Session Manager, Window Manager.
>> Anything revealing in the log?
<snip />
That output you gave was just related to your local X server (of which
Xephyr is a client). I was more referring to the output when you run
Xephyr (stderr, stdout in Terminal.app)
> All I get to the terminal I run it from (whether stdout or stderr I
> don't know, I'd guess the latter) is our old and probably irrelevant
> friend:
>
> Extended Input Devices not yet supported. Impelement it at line 625
> in kinput.c
>
> No output in any logs on the remote system that I can see.
Ok.
>> What if you do: -screen 1024/1024x768/768?
>
> No difference. In fact I have to quit X11 before I get any further
> system.log output, so that's only happening as a result of the
> Xquartz startup, I think.
<snip />
> I think the problem's upstream anyway.
From what you've shown that'd be my guess as well since there's
nothing special we're doing with Xephyr. Have you searched
bugs.freedesktop.org for this issue? If not, could you please search
for it and file a new bug if neccessary? Also, please let me know
what the bug number is, so I can track it here as well.
> I just tested the exact same Xephyr commandline from another ubuntu
> box on the network and I got the same thing, except the -screen
> parameter seemed not to have any effect on the size of the local
> window opened either; so what I got was a 1600x1200 desktop in a
> 1600x1200 window on a local desktop that was too small for it. So in
> that respect, it seems, the current Apple X11 Xephyr is working
> better because at least it opens the local window the right size!
Weird.
<snip>
> So, Xephyr -screen appears to be broken in upstream, and when fixed
> there will presumably be fixed here too. (Either that or there's
> some highly non-obvious parameters I should be giving to tell it to
> match the desktop size to the local window size...) *Please* don't
> remove Xnest from the distribution yet! :-)
Ok, like I've said before. Xnest and Xvfb will remain until I'm sure
Xephyr and Xfake are regression free over them. I'll give notice, and
you'll get a chance to test / voice feedback in this mailing list
before that happens.
Thanks,
Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3040 bytes
Desc: not available
Url : http://lists.apple.com/mailman/private/x11-users/attachments/20080121/0695c86a/smime.bin
------------------------------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden