Re: Clipboard periodically breaks
On Thu Sep 26 20:35:21 2013, m...@codespunk.com (Matt D.) wrote: Jon, Thanks for looking into this. I can confirm that your changes correct the issue where highlighting next would cause arbitrary pastes to occur. Good work! I also concede that there does not seem to be a good solution to transparently fix the two-to-one clipboard issue; as XWin may indeed be able to interpret calls to X's two clipboards, there wouldn't be any reasonable way for it to identify which clipboard is actually being used. I'm reading this wich much interest: for me, too, copy-pasting between Windows applications and Cygwin xterms to break after some time, and this has been happening for a year or so. I'm not aware of doing anything special to cause it to break, but the only way I know how to fix it is to restart X. This is with recent Cygwin packages on Windows 7. I haven't tested with a newer build of the X server. However, an environment variable that tells it which clipboard to use would provide an immediate solution and be used used on a per-application basis. For example, I can use aliases when launching programs: $ xclip=clipboard1 gedit $@ (monitor only clipboard 1) $ xclip=clipboard2 gedit $@ (monitor only clipboard 2) No option would indicate that both clipboard 1 and clipboard 2 would be handled as they are now. I'm not familiar with X programming but I'm assuming here that it would be possible for xclip to read from a particular process's own environment (rather than xclip's own) while processing a clipboard event to do this. What do you think? As an interested bystander, I have no doubt that that type of specific solution to specific clipboard interaction problems can possibly work, but using them will require detailed knowledge of how the X and Windows clipboards interact. My question is different: is it possible to implement the interaction in such a way that a user such as me, who is not aware of any subtleties, can get consistency, in the sense that all copy-paste actions between X an Windows that work when X is started continue to work in the same way for the duration of the session? Matt D. -- Reinier Post TU Eindhoven -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: failed to activate core devices errors
Katrin and others, Op do 10 februari 2011 om 17:12:55 (+) schreef jon.tur...@dronecode.org.uk (Jon TURNEY): On 05/02/2011 23:42, katrin schmid wrote: thanks for the reply. Swrast_dri.so didnt seems to be the problem in my case, will try the XMing now. I followed this: http://robust.cs.utep.edu/arch1-wiki/index.php/Setup_Xming_and_Cygwin#Installing_and_Configuring_the_Xming_X_Server If you followed those instructions and got stuck, I suggest you contact the author. I suggested the XMing server as a workaround for XWin failing to start. I think such a workaround is on-topic here. (Meanwhile I have managed to fix that problem in two different ways, thanks to the advice on this list - see my earlier message - but these fixes don't appear to work for Katrin.) When I was using XMing, I just launched it from its own start menu item, then started Cygwin bash and launched an xterm from it. Once that worked, I automated it into a shortcut - its target is: C:\cygwin\bin\nohup.exe /usr/bin/env PATH=/usr/bin DISPLAY=localhost:0 xterm -e tcsh which leaves an ugly cmd shell on the screen, but I didn't bother to fix that. -- Reinier -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: xorg-server-1.9.2-1 Fullscreen Issue
On Mon, Jan 24, 2011 at 05:48:44PM +, Jon TURNEY wrote: On 21/01/2011 04:38, Frederick D. Hansen wrote: On Fri, 2010-11-19 at 13:37 +, Jon TURNEY wrote: On 18/11/2010 12:33, Frederick Hansen wrote: Just FYI, after upgrading to xorg-server 1.9.2, any attempt to run in fullscreen results in an error. Downgrading to version 1.8.2 seems to correct the issue. Running either version in multiwindow also works. The contents of Xwin.log are shown below: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.9.2.0 (10902000) Build Date: 2010-11-03 XWin was started with the following command line: /usr/bin/XWin -fullscreen -depth 8 -clipboard -silent-dup-error By the way, on my machine, this is just: X :0 -multiwindow [snip] [ 30091.406] (EE) XKB: Could not invoke xkbcomp [ 30091.406] (EE) XKB: Couldn't compile keymap [ 30091.406] XKB: Failed to compile keymap [ 30091.406] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [ 30091.406] Fatal server error: [ 30091.406] Failed to activate core devices. This was the same for me. Are you sure that removing -fullscreen allows the X server to start properly? I didn't have it in the first place. I use XP SP3. I can't reproduce this problem. The problem going away when you remove (and hence prevent from loading) the dynamically loaded swrast_dri.so *really* makes this look like a remap problem. I'm on Windows 7. Renaming /usr/lib/dri/swrast_dri.so fixed the problem for me. I then renamed it back and ran rebase on it with the defaults used in rebaseall. X is still starting up. I then created rebase.lst using the commands used in rebaseall. /usr/lib/dri/swrast_dri.so is in there. But I have run rebaseall immediately prior to starting X and it was still failing to start. So it does appear to be a rebase problem, and I have no clue why rebaseall couldn't fix it. (It was completing successfully.) There is some work upstream to remove this rather pointless fork/exec of xkbcomp and replace it with libxkbcommon, but that now seems unlikely to appear in X server 1.10. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Reinier Post -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: can not startx
Yaakov (Cygwin/X yselkowitz at users.sourceforge.net writes: On 05/01/2010 16:56, eric lin wrote: this is my /var/log/XWin.0.log where I think problm cause, fail startx, please help, eric Sigh. Lets try this again: Problem reports: http://cygwin.com/problems.html Yaakov Cygwin/X I can't follow the rules, there because I'm posting this from http://post.gmane.org/post.php?group=gmane.os.cygwin.xfreefollowup=20508 which doesn't support attachments. My XWin.0.log exhibits the same problem eric lin reported: XKB: Could not invoke xkbcomp [etc.] To check this I replaced xkbcomp with a shell script and indeed, it does not get called. Running as X -logverbose 100 does not shed any light on the problem. Running X or XWin with strace doesn't work (strace refuses to run X and on XWin crashes out with access violation, I'm on Windows 7). The problem appeared after running a rebaseall and rebooting for a regular Windows 7 update. I haven't made any hardware changes and Cygwin/X was running fine yesterday. After the problem appeared, running another erebaseall or updating my Cygwin 1.7 installation didn't help. I'm not replying here to report the problem in full detail (because I can't add attachments) but to report a workaround: install XMing from http://sourceforge.net/projects/xming/ and run that. Then after setting $DISPLAY to 127.0.0.1:0.0 I can run X clients such as xterm from the Cygwin bash prompt. -- Reinier Post TU Eindhoven -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
