Numlock Capslock change status on focus in xterm
Hi all. I updated Cygwin yesterday, I had no problem before. In xterm, both Numlock and Capslock modifiers are changing status by gaining focus. If Capslock is off, there is no problem : xterm stay in lowercase. If it is on, gaining focus make change the status (first Alt-tab=off, second Alt-tab=on, etc.). Same thing with Numlock. Some infos about my installed versions : $ xterm -version Cygwin 6.8.99.903(237) ]$ X -version Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.5.3.0 (10503000) Contact: cygwin-xfree@cygwin.com $ cygcheck -s [...] Cygwin DLL version info: DLL version: 1.5.25 DLL epoch: 19 DLL bad signal mask: 19005 DLL old termios: 5 DLL malloc env: 28 API major: 0 API minor: 156 Shared data: 4 DLL identifier: cygwin1 Mount registry: 2 Cygnus registry name: Cygnus Solutions Cygwin registry name: Cygwin Program options name: Program Options Cygwin mount registry name: mounts v2 Cygdrive flags: cygdrive flags Cygdrive prefix: cygdrive prefix Cygdrive default prefix: Build date: Thu Jun 12 19:34:46 CEST 2008 CVS tag: cr-0x5f1 Shared id: cygwin1S4 [...] Cygwin Package Information Package Version _update-info-dir00780-1 alternatives1.3.30c-2 ash 20040127-4 base-files 3.7-1 base-passwd 2.2-1 bash3.2.39-20 binutils20080624-2 bzip2 1.0.5-2 coreutils 6.10-2 crypt 1.1-1 csih0.1.8-1 cvs 1.11.22-1 cygrunsrv 1.34-1 cygutils1.3.2-1 cygwin 1.5.25-15 cygwin-doc 1.4-4 diffutils 2.8.7-1 e2fsprogs 1.35-3 editrights 1.01-2 expat 2.0.1-1 file4.21-1 findutils 4.4.0-3 font-alias 1.0.1-1 font-bitstream-dpi751.0.0-1 font-bitstream-vera-ttf 1.10-1 font-cursor-misc1.0.0-1 font-encodings 1.0.2-1 font-misc-misc 1.0.0-1 fontconfig 2.6.0-1 freetype2 2.3.7-1 gawk3.1.6-1 gcc 3.4.4-3 gcc-core3.4.4-3 gcc-g++ 3.4.4-3 gcc-mingw-core 20050522-1 gcc-mingw-g++ 20050522-1 gdb 6.8-2 gettext 0.17-1 grep2.5.3-1 groff 1.19.2-2 gzip1.3.12-2 less382-1 libbz2_11.0.5-2 libdb4.54.5.20.2-2 libexpat0 1.95.8-2 libexpat1 2.0.1-1 libexpat1-devel 2.0.1-1 libfontconfig1 2.6.0-1 libfontenc1 1.0.4-2 libfreetype2-devel 2.3.7-1 libfreetype26 2.3.7-1 libgdbm41.8.3-8 libGL1 7.2-2 libICE6 1.0.4-2 libiconv2 1.12-1 libintl10.10.40-1 libintl20.12.1-3 libintl30.14.5-1 libintl80.17-1 libncurses7 5.3-4 libncurses8 5.5-3 libpcre07.8-1 libpixman1_00.12.0-1 libpopt01.6.4-4 libreadline65.2.12-10 libSM6 1.1.0-1 libwrap07.6-4 libX11_61.1.5-1 libXau6 1.0.4-1 libXaw7 1.0.4-2 libxcb-xlib01.1-2 libxcb1 1.1-2 libXdmcp6 1.0.2-3 libXext61.0.4-1 libXft1 1.0.0-1 libXft2 2.1.13-1 libxkbfile1 1.0.5-2 libXmu6 1.0.4-1 libXmuu11.0.4-1 libXpm4 3.5.7-2 libXrender1 0.9.4-2 libXt6 1.0.5-2 lndir 1.0.1-2 login 1.9-8 luit1.0.3-1 make3.81-2 man 1.6e-1 mingw-runtime 3.15.1-1 minires 1.01-1 mkfontdir 1.0.4-1 mkfontscale 1.0.5-1 openssh 5.1p1-9 openssl 0.9.8i-1 pcre7.8-1 perl5.10.0-5 rebase 2.4.4-1 rgb 1.0.3-1 run 1.1.10-1 rxvt20050409-9 sed 4.1.5-2 tar 1.20-1 tcltk 20080420-1 termcap 20050421-1 terminfo5.5_20061104-1 texinfo 4.8a-1 tzcode 2008a-1 util-linux 2.13.1-2 vim 7.2-3 w32api 3.12-1 wget1.11.3-1 which 2.19-1 wtf 0.0.4-6 X-startup-scripts 1.1.0-2 xauth 1.0.3-1 xcursor-themes
RE: Upgrade failed now remote X11 fails :-(
Duane Ellis wrote: Duane Ellis wrote: === [upgrade cygwin/X fails] [various attachments...] To be clear: It worked before - just fine until I upgraded Jon Turney Can you try again without -clipboard in your Jon Turney script just to rule something out? Hmm without -clipboard I cannot cut/paste between the two machines (ie:cygwin/x and windows) But it *DOES* make a difference, I can now SSH into the system. Jon turney Just to be clear, when you remove -clipboard, you are able to run up startx successfully? Yes, that is exactly the problem. duane You asked what version of KDE I'm using... duane The program: kded --version reports duane Qt: 3.3.3 KDE:3.3.1-3.14 Red Hat Jon Thanks. Maybe I can find a RH image of that vintage to do some testing with... FYI - The machine runs RHEL4 I believe -- 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/ -- 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/
AW: openbox scrambled after xorg 7.4 update
Yaakov wrote: Voelker, Bernhard wrote: my openbox window manager is not usable anymore: the menues, window titles etc. are not rendered correctly and can't be read anymore. Is openbox supported with the new xorg version? Any other ideas? http://cygwin.com/ml/cygwin-xfree/2008-11/msg00079.html Yaakov oops, thanx. In the meantime, I guess I'll use blackbox - this still works fine ;-) http://blackboxwm.sourceforge.net/ and a cygwin binary: http://www.stokebloke.com/cygwin/index.php Have a nice day, Berny -- 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/
X11R7 and rebasing
I have seen that after the release of X11R7, many problems are partially resolved by rebasing. Some time ago, I remember that on cigwin-apps list there was the suggestion that the package maintainer should build their packages adding '-Wl,--enable-auto-image-base' for DLLs. Has this be done for the recent release? If 'yes', just for curiosity, where, than, this need of rebasing comes from? Thanks, Angelo. -- 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/
startx doesn't if $HOME contains white spaces
Hello, my $HOME is : $ echo $HOME /c/Documents and Settings/patrick.PRO2204 when I start 'startx' $ startx /usr/bin/startx: line 38: [: too many arguments /usr/bin/startx: line 107: [: too many arguments Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.5.3.0 (10503000) Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/bin/X :0 -auth /c/Documents and Settings/patrick.PRO2204/.serverauth.3056 Unrecognized option: and use: X [:display] [option] I think that white spaces in my $HOME directory name causes the problem. I patch startx on lines 38 and 107 if [ -f $userclientrc ]; then if [ -f $userserverrc ]; then but this is not enough ... does anybody encounters the same problem ? -- 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: X11R7 and rebasing
On Nov 19 14:30, Angelo Graziosi wrote: I have seen that after the release of X11R7, many problems are partially resolved by rebasing. Some time ago, I remember that on cigwin-apps list there was the suggestion that the package maintainer should build their packages adding '-Wl,--enable-auto-image-base' for DLLs. Has this be done for the recent release? If 'yes', just for curiosity, where, than, this need of rebasing comes from? --enable-auto-image-base is not a 100% solution because there is none. It just can ease the pain somewhat. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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: startx doesn't if $HOME contains white spaces
Marco Atzeri a écrit : --- ludo ha scritto: ... it is not a good idea: http://cygwin.com/faq/faq-nochunks.html#faq.using.filename-spaces thanks for the link now ... startx works well -- 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: X11R7 and rebasing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Angelo Graziosi wrote: I have seen that after the release of X11R7, many problems are partially resolved by rebasing. Some time ago, I remember that on cigwin-apps list there was the suggestion that the package maintainer should build their packages adding '-Wl,--enable-auto-image-base' for DLLs. Has this be done for the recent release? If 'yes', just for curiosity, where, than, this need of rebasing comes from? libtool. Yaakov Cygwin/X -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkkMjkACgkQpiWmPGlmQSMvNACgrqb/4f3a4kTSqPMOCrH3ZZjV QZYAoNMNgO+6XVlMgx4vQ8n96aWHs5g0 =kD75 -END PGP SIGNATURE- -- 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: startx doesn't if $HOME contains white spaces
Marco Atzeri wrote on Wednesday, November 19, 2008 1:49 PM:: --- ludo ha scritto: my $HOME is : $ echo $HOME /c/Documents and Settings/patrick.PRO2204 it is not a good idea: http://cygwin.com/faq/faq-nochunks.html#faq.using.filename-spaces I think that white spaces in my $HOME directory name causes the problem. [...] does anybody encounters the same problem ? of course, for this reason we don't do it :-) my $HOME in cygwin is /home/marco If you wish cygwin to use /c/Documents and Settings/patrick.PRO2204 rather than setting up a separate $HOME directory, you could just use mount: mount $USERPROFILE /home/patrick Then edit your /etc/passwd file to set your home directory to /home/patrick. You $HOME would now be /home/patrick for cygwin programs, and Windows can continue using its Hey! Now that we *can* have spaces in filenames, let's use them EVERYWHERE! Phil -- This email has been scanned by Ascribe PLC using Microsoft Antigen for Exchange. -- 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: startx doesn't if $HOME contains white spaces
FYI - While I agree with you it is not a good idea reality makes life hard. There are times - due to corporate policy etc - a user has no control over this. It would be helpful - if for cygwin, one would write scripts pre-emptively knowing that this problem can occur, it's not hard - it just means pre-emptively wrapping a few things in quotes. Often, end users have little control over the way corporate systems configure PCs. Alternatively, one could get the Cygwin Setup.exe people to recognize this problem and either (1) issue a *BIG*FAT*WARNING* when the system is installed, updated, etc, or (2) forcably some how - make $HOME something safe. I for one, had to figure out that SSH refuses to work if certain files are on windows server and not local to the machine. -Duane. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Betts Sent: Wednesday, November 19, 2008 10:32 AM To: cygwin-xfree@cygwin.com Subject: RE: startx doesn't if $HOME contains white spaces Marco Atzeri wrote on Wednesday, November 19, 2008 1:49 PM:: --- ludo ha scritto: my $HOME is : $ echo $HOME /c/Documents and Settings/patrick.PRO2204 it is not a good idea: http://cygwin.com/faq/faq-nochunks.html#faq.using.filename-spaces I think that white spaces in my $HOME directory name causes the problem. [...] does anybody encounters the same problem ? of course, for this reason we don't do it :-) my $HOME in cygwin is /home/marco If you wish cygwin to use /c/Documents and Settings/patrick.PRO2204 rather than setting up a separate $HOME directory, you could just use mount: mount $USERPROFILE /home/patrick Then edit your /etc/passwd file to set your home directory to /home/patrick. You $HOME would now be /home/patrick for cygwin programs, and Windows can continue using its Hey! Now that we *can* have spaces in filenames, let's use them EVERYWHERE! Phil -- This email has been scanned by Ascribe PLC using Microsoft Antigen for Exchange. -- 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/ -- 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/
Upgrade woes.
I updated my cygwin the other day, as I periodically do, and I am very sorry I did so. Here are some of the problems I have encountered. 1) Couldn't start cygwin X at all. The link on my desktop pointed to a script (which I had customized) in /usr/X11R6/bin, which was deleted by the upgrade. It took me a while to find the replacement -- mysteriously moved to /usr/bin, minus my customizations. 2) Fonts I had added no longer work. Everything looks fine in /usr/X11R6/lib/X11/fonts. Messed around there for a while, to no avail. After much Googling, found that the fonts have been moved to /usr/share/fonts. 3) While trying to figure out why my fonts weren't working, I naturally tried to use xfontsel. bash: xfontsel: command not found. WHAT?! It turns out that it's now in its own cygwin package, as are about a billion other useful utilities that have been deleted without warning. 4) xterms all now have a useless, annoying menu at the top. I want to make it go away. Had to wade through the xterm manual to learn that this is apparently called a toolbar and is now on by default. I am extremely annoyed. I have lost many hours of productivity just trying to get back to where I was on Monday, and I'm still not there. The worst part of it is that I (and probably most cygwin users out there) was completely blindsided, and there was no post-upgrade help to be found. What's on the news page at cygwin.com? A kernel upgrade in June. Before that, a kernel upgrade in May, and one in March. Nothing new in the FAQ. No announcement of a change that's going to screw up your whole system. At x.cygwin.com, things are even worse. Last updated: 2004-01-10 0200 EST (Harold L Hunt II). Not helpful. There is a short note at the bottom of the main page directing people to the mailing list announcement. It contains useful information such as before you upgrade, do this and that and the other thing. Wish I had known about some of those before I upgraded! It also notes without explanation that most programs are in their own packages now. This is terribly inconvenient to us ordinary users. My xterms are screwed up. Numlock is very wonky: Let's say I start off with numlock on; I am in a Windows (non-X) window; I switch to an xterm; I use the numeric keypad to type; I get nothing (tildes, escape codes, non-numlock crap). I switch to another xterm, I type on the keypad, I get digits. I switch back to the first xterm, it's still acting as though numlock is off. I switch to a Windows window, then back to the first xterm. Now it behaves as though numlock is on. I switch to the second xterm window, *it* is behaving as though numlock is off. All this time, the numlock LED is lit. I can consistently repeat this. xfontsel is broken. The main part of the window does not redraw itself when dropdown menus disappear, so you wind up with large portions of old menus cluttering the client area. Several of the fonts are rendered with a broken, crappy look. As far as I can tell, this is not a problem with the font iself -- but who knows! I am sure that the cygwin X developers put a great deal of time and effort into this upgrade. And I honestly appreciate the work that they do. Being a contributor to open-source software myself, I can appreciate what they go through. But this upgrade was surely poorly thought-out. I am not a cygwin developer; I am not really even a cygwin power user, although I will not -- cannot -- use Windows without cygwin. So I am not subscribed to the cygwin mailing lists. I just run setup.exe periodically to get patches. It should not have re-architected my whole damn system without warning. Eric -- 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: Upgrade woes.
On Wed, Nov 19, 2008 at 11:03:11AM -0500, Eric Roode wrote: I updated my cygwin the other day, as I periodically do, and I am very sorry I did so. Here are some of the problems I have encountered. So you just blindly updated without noticing that X was changing? Wow. It's amazing that you aren't being constantly burned by software updates with that kind of optimistic attitude. cgf -- 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/
Upgrade woes.
On Wed, 19 Nov 2008 11:26:11 -0500, Christopher Faylor wrote: On Wed, Nov 19, 2008 at 11:03:11AM -0500, Eric Roode wrote: I updated my cygwin the other day, as I periodically do, and I am very sorry I did so. Here are some of the problems I have encountered. So you just blindly updated without noticing that X was changing? Wow. It's amazing that you aren't being constantly burned by software updates with that kind of optimistic attitude. Yeah, trust the developers. How *could* I have been so stupid? For the record, yes I upgrade all the time. I happen to think it's good practice to get regular patches. In general, developers don't push through upgrades that break everything. I'm surprised (and annoyed, and angry) that this wasn't the case this time. Thanks for blaming the victim! Eric -- 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: Upgrade woes.
I have the same Numlock/Capslock issue (see my previous post). Stop fighting about this, it doesn't help ! Please, does anybody have a solution ?? -- 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/
tetex-x11, texlive, xdvi, and X11R7.4
I mentioned in a different thread [1] that I've been trying to build texlive for X11R7.4. Angelo Graziosi had previously built it successfully [2] using the previous version of X11. [His build still works in X11R7.4 if one installs the obsolete libXaw8 package.] I'm now able to get my build to complete, but the resulting xdvi program segfaults. More precisely, it first spews out many warnings that say No type converter registered for '' to ' and then it segfaults. I can run xdvi --version and xdvi --help without a problem, but calling xdvi with no argument or with a specified dvi file both produce the segfault. BTW, xdvi can be compiled to use either xaw or motif, and I get the same behavior either way. There is a cygwin version of xdvi in the tetex-x11 package, which Yaakov [3] listed as one of the packages that needs to be rebuilt for the new X11. I'm wondering whether the tetex maintainer is planning to do this. Note that tetex is actually way out of date, having been replaced in the tex community by texlive (or by the windows miktex program), but I'm hoping that someone more expert than I am will track down the xdvi problem in the course of rebuilding tetex-x11. A better long-term solution would be for someone to make an official texlive package for cygwin, but that's a much bigger project. Finally, I would appreciate any suggestions that anyone can offer as to how I can figure out why xdvi segfaults. I'm not a programmer, and I have no idea where to begin. I did try strace, but I don't know what I should be looking for in the output. Here are all the lines containing the word exception, if that helps: --- Process 2444, exception C005 at 610DEFA1 423 1298097 [main] xdvi-motif 2444 _cygtls::handle_exceptions: In cygwin_except_handler exc 0xC005 at 0x610DEFA1 sp 0x22CC44 60 1298157 [main] xdvi-motif 2444 _cygtls::handle_exceptions: In cygwin_except_handler sig 11 at 0x610DEFA1 37 1298194 [main] xdvi-motif 2444 _cygtls::handle_exceptions: In cygwin_except_handler calling 0x0 38 1298232 [main] xdvi-motif 2444 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION --- Process 2444, exception C005 at 61016583 1927954 3226967 [main] xdvi-motif 2444 _cygtls::handle_exceptions: In cygwin_except_handler exc 0xC005 at 0x61016583 sp 0x22C738 160 3227127 [main] xdvi-motif 2444 _cygtls::handle_exceptions: In cygwin_except_handler sig 11 at 0x61016583 82 3227209 [main] xdvi-motif 2444 _cygtls::handle_exceptions: In cygwin_except_handler calling 0x0 69 3227278 [main] xdvi-motif 2444 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 39975 3267253 [main] xdvi-motif 2444 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Ken [1] http://cygwin.com/ml/cygwin-xfree/2008-11/msg00116.html [2] http://www.webalice.it/angelo.graziosi/cygwin/texlive/texlive.html [3] http://cygwin.com/ml/cygwin-apps/2008-11/msg00078.html -- 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/
[ANNOUNCEMENT] New package: nas/libaudio2/libaudio-devel-1.9.1-2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been added to the Cygwin net release: +++ nas-1.9.1-2 +++ libaudio2-1.9.1-2 +++ libaudio-devel-1.9.1-2 The Network Audio System is a network-transparent, client/server audio system based on X11. Yaakov Cygwin/X DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the cygwin-xfree mailing list is the appropriate place. CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO: === To unsubscribe to the cygwin-xfree-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkkX1sACgkQpiWmPGlmQSO/ewCeNbgaRTVsTqKjltcJC9DIXIr2 0uUAn3UK8t9AhiZakp7K3YRICSrcF0vA =drg0 -END PGP SIGNATURE- -- 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: Small update for X server 1.5.3 patch set
Yaakov (Cygwin Ports) wrote: Jon TURNEY wrote: Please find at the URL below a small update to the xorg server patch set. Committed; could you please svn up and test? I also changed the log location patch to use a separate log for each display (e.g. XWin.0.log), as is done on Linux; the old XWin.log name is still used when no display was actually launched. What do you think about it? Works for me. Note that you don't actually need to the formatting of the log file name yourself, LogInit() already has code to replace %s in the log file name with the display name. If your going to do a release soon-ish, you might considered disabling the call to winRestoreModeKeyStates() in winmultiwindowwndproc.c. The code which tries to synchronize locking key states (e.g. caps lock, etc.) between X and Windows has broken, so is now toggling the modifiers in X every time an X window gains focus. Having the lock state in X just unsynchronized instead might be marginally less irritating until I get a chance to work on a proper fix. -- 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: Upgrade woes.
Dont Care wrote: I have the same Numlock/Capslock issue (see my previous post). Stop fighting about this, it doesn't help ! Please, does anybody have a solution ?? Yes. The location of the startup bat files changed from /usr/X11R6/bin to /usr/bin. You need to change your start menu shortcuts to run the new .bat file. I think there's a package that's supposed to do it automatically for you too. I think the frustration on some people's behalf is that this question has been asked (and answered) maybe 50 times already on the list. -- 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: Upgrade woes.
On Wed, 19 Nov 2008 17:06:37 -0500, Chuck wrote: Dont Care wrote: I have the same Numlock/Capslock issue (see my previous post). Stop fighting about this, it doesn't help ! Please, does anybody have a solution ?? Yes. The location of the startup bat files changed from /usr/X11R6/bin to /usr/bin. You need to change your start menu shortcuts to run the new .bat file. I think there's a package that's supposed to do it automatically for you too. How does the location of the startup batch file affect the behavior of numlock and capslock in xterm? I think the frustration on some people's behalf is that this question has been asked (and answered) maybe 50 times already on the list. I for one did peruse the mailing list archives, and did a bunch of google searching, before posting here. I saw how things had been moved from /usr/X11R6/foo to /usr/foo. (That change makes zero sense to me, but what the hell, I'm just a luser). I do not see how that affects the behavior of xterm, especially capslock/numlock/toolbar behavior. Maybe I'm just dense. Try to see the frustration of the people who are asking these questions -- suddenly things are broken, and it is not apparent why, and the cygwin websites say nothing, and the hundreds of mailing-list messages do not appear to address the questions we have. Eric -- 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: Upgrade woes.
Eric Roode wrote: How does the location of the startup batch file affect the behavior of numlock and capslock in xterm? Yes. The batch file is different. The binary is different. The environment variables are different. For example this is in the old batch file but not in the new one. SET XAPPLRESDIR=/usr/X11R6/lib/X11/app-defaults SET XCMSDB=/usr/X11R6/lib/X11/Xcms.txt SET XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB SET XNLSPATH=/usr/X11R6/lib/X11/locale I suspect that XKEYSYMDB one has something to do with the problem you're having. The new file doesn't assign these variables at all, and runs a different binary. -- 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: Upgrade woes.
Chuck wrote: I think the frustration on some people's behalf is that this question has been asked (and answered) maybe 50 times already on the list. Perhaps because people can't find the info. they need in any other way than posting to this list? I know that I only happened on this list during the past two days because I was a regular updater and all of a sudden things just didn't work any more after upgrading. I looked through the FAQ announcements didn't see anything that would help me through problems/hiccups with the upgrade... so I joined the list. And I still can't /quite/ get everything that I need working... app-image-san-004:image undefined control XView warning: Cannot load font set '-bh-lucida-medium-r-*-*-*-120-*-*-*-*-*-*' (Font package) XView warning: Unable to open default font set XView error: Cannot open connection to window server: app-image-san-004:10.0 (Server package) app-image-san-004: I'm certain that this is an xset snafu (scripts to invoke mission critical applications at my company expect to see fonts in certain directories on the X server). Symlinks need updating I suppose, and I have to do the mkfontdir shuffle as well on all of my non-cygwin supplied font directories (that got moved)... Sigh... Can someone here provide a link to documentation that we can turn to in a FAQ form to help us proactively identify and fix commonly encountered problems with the update? I'm looking for something like a HOWTO migrate. If such doesn't exist, I suppose that I can help cook something up from my own experiences... Thanks, Michael PS -- Yaakov Jon, thanks for all the help thanks for stepping up and working on Cygwin/X. I know that once the initial pain is over that this will be great for everyone. It's going to be nice to be on a more current X. -- 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: Upgrade woes.
On Wed, Nov 19, 2008 at 03:16:05PM -0800, Back, Michael wrote: Chuck wrote: I think the frustration on some people's behalf is that this question has been asked (and answered) maybe 50 times already on the list. Perhaps because people can't find the info. they need in any other way than posting to this list? You seem to be missing the point that if it was discussed in the list you can use the list archive as a resource. You don't have to just blindly send email assuming that no one else would ever have asked the same question. cgf -- 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: Upgrade woes.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Back, Michael wrote: I solved this one by guessing and loading the right font pack... Which font pack contains this one?: app-image-san-004:station: Warning: Can't chmod /dev/console XView warning: Cannot load font set '-*-screen-bold-r-*-*-*-160-*-*-*-*-*-*' (Font package) station: line 26 of /image/bin.rls/custom/production_station_buttons, FONT: Cannot open button font 'screen.b.16' No such font is provided by X.Org, and some googling makes me suspect that this may be a Solaris-specific font. Yaakov Cygwin/X -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkkxUoACgkQpiWmPGlmQSNlMgCeKoWpCSbxPLMqh8rWdtlxqtr1 ts8AoIGGmglMABN9zpo6p2z2jCnUf2AD =Q1x7 -END PGP SIGNATURE- -- 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: Upgrade woes.
Eric Roode wrote: I updated my cygwin the other day, as I periodically do, and I am very sorry I did so. Here are some of the problems I have encountered. It has always been the advice of this list that you should read the announcements on cygwin-announce@ and cygwin-xfree-announce before upgrading blindly. Now, often you can get away with /not/ doing that, d nothing bad will happen. But if I ran setup, and saw 157 new packages about to be upgraded...I might want to investigate a little before clicking continue. http://cygwin.com/ml/cygwin-xfree-announce/2008-11/msg0.html But, as always, it's up to you. We'll happily refund all the money you paid. -- Chuck -- 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/
Documentation
Hi All, I've tried installing the Cygwin X11 server to try to be able to run an X app, but the cygwin installation packages were completely different to the ones mentioned on the website and in the documentation. I had to search the mailing list to get the required package names. So, can I suggest that the website and/or documentation are updated to reflect the package name changes? I'm sure it would save a lot of pain for people in the future. Regards, Jonathan Johansen -- 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: Upgrade woes.
Back, Michael wrote: Christopher Faylor did utter a clarion call of great frustration unto the heavens: On Wed, Nov 19, 2008 at 03:16:05PM -0800, Back, Michael wrote: Chuck wrote: I think the frustration on some people's behalf is that this question has been asked (and answered) maybe 50 times already on the list. Perhaps because people can't find the info. they need in any other way than posting to this list? You seem to be missing the point that if it was discussed in the list you can use the list archive as a resource. You don't have to just blindly send email assuming that no one else would ever have asked the same question. My point is that relying on a user to have the forethought, time, and patience to scour through a mailing list archive is probably not the most effective or convenient form of communicating common upgrade problems and solutions. Probably not surprisingly, this idea is not new. It's been discussed before and only remains as a topic for discussion because of a lack of resources to help make the situation better. If anyone would like to research, monitor, and dig in to help make the documentation or install tools better and more helpful, I expect that would be welcome. Keep in mind that where Cygwin/X is concerned, there has been no maintainer for _years_ so I think we can all anticipate the amount of work to get all the packages upgraded, documented, and spiffy is significant. And there will be some bumps along the way... -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - FAX Holliston, MA 01746 -- 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: X11R7 and rebasing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 [EMAIL PROTECTED] wrote: How's that? What, exactly, does libtool have to do with cygwin's fork emulation code? The closest libtool comes to this issue is the fact that it automatically turns on enable-auto-image-base -- which should help somewhat alleviate the problem (although, as Corinna pointed out earlier, it's not a panacea). Sorry, I misread and thought, based on the flow of the message, that the last question was how the enable-auto-image-base was done. Indeed libtool is part of the solution and not the cause. Yaakov Cygwin/X -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkk6WoACgkQpiWmPGlmQSOmLACgvvwMaUAouTt/dbkaX+xNmE5P wsQAoKt7ln0Opmogs1rYsIgEQ7l+75ee =YlvX -END PGP SIGNATURE- -- 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: Documentation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jonathan Johansen wrote: I've tried installing the Cygwin X11 server to try to be able to run an X app, but the cygwin installation packages were completely different to the ones mentioned on the website and in the documentation. I had to search the mailing list to get the required package names. So, can I suggest that the website and/or documentation are updated to reflect the package name changes? I'm sure it would save a lot of pain for people in the future. http://cygwin.com/acronyms/#SHTDI Yaakov Cygwin/X -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkk6mMACgkQpiWmPGlmQSNnoQCg9dovtbYAd+xAV73rTcYkBUsl /cAAoKDvc2rshXsqn3N9Qt6tz5N+PgEU =M4zL -END PGP SIGNATURE- -- 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/
