Following update to XWin or xorg-server: changed syntax to get a xterm terminal window
For ages I used XWin -nolock -nolisten local -multiwindow xterm -display localhost:0.0 to get a xterm terminal. Following recent updates I get a fatal error: Cannot establish any listening sockets. In the past, updates to XWin have sometimes led to similar difficulties, but I have always managed to iterate to a new successful joint syntax XWin arguments xterm arguments but this time I am totally stymied. Can anybody offer me a working syntax please? Thank you. Fergus -- 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/
Starting XWin from a portable CD
I'm running Cygwin-X from a portable device. From a write-able stick the start command bin\run bin\XWin -nolock -nolisten local -logfile /dev/null -multiwindow works perfectly well. Notice the switch -logfile /dev/null which means the file XWin.0.log is not written. (Slightly odd I know. The switch -logfile should specify a filename not a directoryname, but it seems to work?) However using an identical architecture as on the stick, but on a CD, the same start command results in Failed to activate core devices. So is there something else that needs to be written and cannot be diverted to /dev/null (or somewhere write-able). Or, if I know what it is, can I divert it or otherwise turn it off? (Oh woe woe woe. I've lost count of the things that worked so easily on 1.5 and somehow don't on 1.7, this start command on a portable CD being one of the list.) Thank you! Fergus -- 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: Updated: xorg-server-1.9.2-1
Fatal server error: Can't read lock file /tmp/.X0-lock Does /tmp/.X0-lock exists? Is it readable by you? Yes. Are you sure /tmp is getting mounted successfully where you expect it to be? Yes. Have you tried '-nolock', as suggested by [1] I hadn't then. But I have now and as a consequence everything is working perfectly. Thank you. (Over time I have occasionally had to moderate the syntax of both XWin and xterm command lines to go from working to failing and back again to working. This is just another example. On an earlier occasion, the recommended use of -nolock failed. I am just happy when the current usage works. Thanks again.) Fergus -- 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: Updated: xorg-server-1.9.2-1
Dear Jon, Since the update I have been unable to start XWin under [1.7]. Following my usual sequence at a bash prompt: mount n:/tmp /tmp # drive n: is NTFS as required run XWin -multiwindow Normally these two would be followed by a command line for xterm, but I am not getting that far! The second line repeatedly generates a Cygwin/X error message box, where the reason given is very familiar: Can't read lock file /tmp/.X0-lock I used to get this when /tmp was FAT32 but as you see from line 1 I am making an explicit mount to a NTFS drive, and in the recent past this step has been all that is necessary to make progress. When I open /var/log/xwin/XWin.0.log for more information I read ~ cat /var/log/xwin/XWin.0.log 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 -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1280 h 1024 winInitializeDefaultScreens - native DPI x 96 y 96 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/mandible:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 Fatal server error: Can't read lock file /tmp/.X0-lock [1]+ Donerun XWin -multiwindow Can anything be determined from the 3 lines in this file beginning _XSERV (Unable .. failed .. failed)? Do I need to change my command sequence? BTW it's interesting (is it?) that the error message refers to 1.9.2.0 not 1.9.2-1. I'm surprised that there are no other anguished reports to you following the update, but I guess that's because the fault/ problem/ difficulty is mine rather than general. ?? Any insights much appreciated. Thank you, Fergus PS It kills me not to copy this to cygwin at cygwin dot com which I feel will have a much wider readership and skill set amongst that readership, but anybody sinning in this regard is always referred straight to Cygwin-X. A strange separation of reporting. Not that I am doubting your specific capability, just the potential for Me Too amongst readers. (Or even Not Me, but I Know What's Going Wrong.) -- 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: [PATCH] Repair '-nolock'
(Sorry to send twice: originally sent yesterday Sunday 0728 GMT but never arrived at cygwin-xfree at cygwin dot com; 2nd attempt today Monday 0752 GMT and hope for better progress.) Message was: Thank you. 1 Will this amendment eventually be incorporated into an updated .bz2 file under /release? 2 If not then (I am sorry) I do not know how to introduce a patch into an existing executable. Something like: unwrap src, change os/utils.c, rebuild? If this is something everybody in the world except me knows, can you direct me to a howto? Thanks again. Fergus -- 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/
Unrecognized option: -nolock
With the latest release 1.7.0-67 Cygwin [1.7] now works glitch-free on FAT32 filesystems; but to run X on FAT32 we still have to revert to 1.7.0-60. The recommended fix (there may be more than one but this seems potentially the easiest and most effective) is to run X -nolock. But this option is unrecognised in the current XWin. Please could -nolock be reintroduced so that FAT32 users can take full advantage of the current .dll? Thank you. Fergus -- 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't read lock file
// Which is bad since FAT32 has no security at all. Any process of any user on the machine can overwrite any file, even in the Windows folder. NTFS is much more secure and has a couple of features you never get with FAT32, and hardlinks are only one minor advantage. You should really update the filesystem to NTFS using the on-board convert.exe tool. Well. I took the advice and converted both FAT32 systems (one for 1.5 and one for 1.7) to NTFS. I quite like some of the file management consequences - e.g. chkdsk output, more efficient use of space - but working within Cygwin I'm not a happy bunny. I am sure that in many parallel universes the step you have advised results in huge benefits, but so far I can only report detriment to [1] use and [2] understanding. (I know [1] that requests/ complaints/ comments should not be too user-specific and as for [2] I'm really just hanging myself out to dry. But here goes ...) I operate both Cygwins 1.5 and 1.7 on a partitioned portable drive hooked up to different machines at different times. After changing to NTFS I find statements of folder permissions completely incomprehensible e.g. the + in drwxrwxrwx+; also that they do not alter after chmod instructions in the way I was expecting; that there are MANY additional user names and group names including ?? ; that files I worked on on Machine 1 now produce Permission denied when I try to work on them on Machine 2 All right, all of the above merely make manifest a complete lack of understanding of permissions, privileges, rights, etc. But it is after all my mobile drive, and every file on it was put there by me, is owned by me in some sense, and I ought to be able to do stuff. Finally (and I have tried to search for a solution) I alias ls as ls --color and had some lovely rxvt* xterm* and gnuplot* color schemes set up in ~/.Xdefaults. Now the rxvt* and xterm* color schemes have been lost (to be replaced by, I assume, some standard set, with a particularly horrid colour combination for directories (fg blue bg green). Confusingly, realised gnuplot* colors are still as set in .Xdefaults. Is there a way I can recover what I want for rxvt and xterm (maybe by putting the instructions into a different file). I think I will revert to FAT32 partitions and maybe put up with a working if not current XWin in 1.7. Like my experience with mobile phones, there is a threshold of sophistication beyond which I am just plain incapable of making progress, and the conversion of FAT32 to NTFS seems to have crossed that threshold for me with its unintended (or unexpected anyway) consequences. It is a marvellous advance in security I am sure (and I am very appreciative that Corinna and Jon took this up and responded to me) but I guess it just isn't for me. Thank you. If meanwhile you can point me somewhere for a solution to the lost colour schemes, I would be very grateful. Fergus -- 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/
Can't read lock file
I have made no alterations/ patches/ amendments and have a completely current [1.7] system. For all of cygwin1.7.61.dll - cygwin1.7.64.dll the command run XWin fails with a reference to /vat/log/XWin.0.log which reads Can't read lock file /tmp/.X0.lock But when reverting to cygwin1.7.60.dll everything goes ahead smoothly and correctly and I can start a X terminal etc. Q1. Is it still the case that this problem is not well understood as in this reference? http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cant-read-lock-file (My experiments with possible cause/ cure are confounded because on Machine 1 I have NTFS filesystems but lack administrator rights and on Machine 2 where I am Administrator, all filesystems are FAT32.) Q2. Is there anything obvious in the progression from cygwin1.7.60.dll to cygwin1.7.61.dll that might explain why the start command run XWin works with 1.7.60 and fails with 1.7.61? Finally Q3. Confession: I am completely confused by all recent posts about LANG, locale and all the rest. Are fiddling with LANG or applying patches such as described at http://cygwin.com/ml/cygwin-xfree/2009-11/msg00071.html fixes intended to address problems starting XWin? Thank you. Fergus PS Not quite finally. Can I please ask a 4th question: Q4 Why are questions about X specifically directed to a different mailing list? Apart from occasional high-frequency dialogue as at present, posts about X are (or seem to me to be) no more frequent than posts about grep or ls or chmod or ... . The main Cygwin list has a much higher readership and posts directed there might generate many useful hints, tips, experiences, fixes or even solutions? -- 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/
Strange architecture under /etc/X11/
There seem to be 00s or even 000s of strangely configured links under /etc/X11/, all taking the form a - a. Often (always?) the link a - a is located in a directory called a. eg /etc/X11/rstart/commands/x11r6/x11r6 and any number under /etc/X11/xserver/ such as /etc/X11/xserver/en_US/en_US This seems to me to cause havoc with file handling resulting in multiple error msgs No such file or directory or Too many levels of symbolic links. Fergus -- 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: How to add a title to xterm
How to add a title to xterm? I start cygwinx by startx. The following commands does not work: xterm -T columbia xterm -title columbia xterm -title columbia I do not use startx: for me, it sets up unnecessary or inconvenient defaults. 1. Start bash then 2. run XWin -nolisten local -multiwindow Enter 3. xterm -display localhost:0.0 -title Columbia Enter works fine for me ... Fergus -- 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/
xpdf: error messages
I assume this is the place to comment on the recent provision of xpdf (not cygwin@). Thanks for this. One minor irritation. It doesn't matter what .pdf I choose to view (I've tried many) it turns out that on quitting the successful viewing and before the resumption of the Cygwin prompt, six identical error messages are presented as follows: Warning: XtRemoveGrab asked to remove a widget not on the list Warning: XtRemoveGrab asked to remove a widget not on the list Warning: XtRemoveGrab asked to remove a widget not on the list Warning: XtRemoveGrab asked to remove a widget not on the list Warning: XtRemoveGrab asked to remove a widget not on the list Warning: XtRemoveGrab asked to remove a widget not on the list The version of xpdf provided is v.3.00 Copyright 1996-2004 Glyph Cog LLC. As it happens I have v.2.02p11 from the same source. This is huge (8MB, Goodness knows why) and takes a long time to load but does not present the error msgs after viewing. My fix is to use the command structure xpdf filename.pdf 2/dev/null which effectively mutes the error messages but this is not quite optimal. Thanks. Fergus
Re: installing a window manager - help please
I can't get so much as a basic window manager started with the ability to open a new xterm. Assuming you have a full install, or at least sufficient to run XWin, is this any good at least to get you going? Sorry if this is the one thing you can do ... in which case sorry for wasting your time. 1. Start with bash --login -i 2. At the bash prompt check your PATH. It should look something like this: ~ echo $PATH /home/yourname/bin:/usr/local/bin:/usr/X11R6/bin:/usr/bin:/bin 3. If so you can usefully reduce the length of the following two lines, but full pathnames are included if you need them (or want to see them): /usr/X11R6/bin/run /usr/X11R6/bin/XWin -nolisten local -multiwindow /bin/xterm -display localhost:0.0 The -nolisten local switch is something I have found to work if your machine is not permanently connected online. (For some reason I don't understand and which may even be good, Xwin constantly listens to network connections and throws a fit if it can't hear anything.) 4. Once you've got Xwin up and running you can jump in and out of xterm and back to bash as you please. You don't have to start Xwin a 2nd time (in fact it objects if you do). If you prefer to, you can set DISPLAY in your environment and not have to type -display ... each time. 5. If after this you make more progress with fvwm please let me know as I can't get anywhere either. Fergus
Re: How to clean the local package directory?
The file /etc/setup/installed.db lists all the packages, and only the packages that you have currently installed, together with their version numbers. If you ara happy with that installation (and it sounds as though you are: your post does not mention any requirement for re-installation, it explicitly states how tedious that would be) then it looks to me as though the best approach would be to edit that file into a .bat file to be run from outside Cygwin, or a script to be run from within Cygwin, that will (1) move the files you want to keep to a new location, (2) delete what's left, (3) rename new location to old. (Or have the effect of (1) - (3), however you manage the detail.) Any good, do you think? Fergus If you wanted to run a fresh installation with just these packages, and without the effort of picking them, then this too can be contrived, but that's another story. Do you?
Re: XWin on Windows 98 unreliable
This works for me on W98 on a non-networked machine: bash run XWin -nolisten local -multiwindow should do it. Then if you want to run xterm (say) just use xterm -display localhost:0.0 HTH. Fergus
Re: Problem with xman
Rodrigo,
Thank you. Your mod to /bin/nroff provided as an attachment at
http://www.cygwin.com/ml/cygwin-xfree/2004-03/msg00299.html worked
perfectly. That is, an xman page now appears with the expected enhanced
view rather than the escape codes.
As a separate issue, I have noticed that any attempt to view a second xman
page is defeated (at least in XP Pro) with an error message as follows:
Xman Warning:
Something went wrong trying to run the command:
cd /usr/man ; tbl /usr/man/man1/{requested page} | neqn | nroff -man
..{rest of msg off screen}
and
cannot create /tmp/xman002688: permission denied
whose solution may reside in something to do with permissions rather than
Xman ...
Fergus
Problem with xman
I'm running XWin -51 and the 20040306 snapshot. If I try xman then everything looks as though it's going to work beautifully (and it does, as far as file access etc goes) but a typical man page, when it appears, shows control instructions like this: 1mNAME0m diff - compare files line by line 1mSYNOPSIS0m 1mdiff 22m[4mOPTION24m] ... 4mFILES0m etc. Anybody else get this? Do I need to do something simple to correct this behaviour? Fergus
XWin: problems on un-networked machine
For a while I've been able to use XWin running from a reduced Cygwin-on-CD on a non-networked machine by using the command line mount -buf $TMPDIR /tmp/ XWin -nolisten local -multiwindow (ther first line is intended to allow the writing on XWin.log and, in the past, has achieved exactly this). However, lately, and including the most recent update of XWin _and_ the latest (I think) snapshot of cygwin1.dll, this has now failed, with no logfile XWin.log written. The application XWin dies immediately, as shown by ps. 1. I attach cygcheck.out 2. Sorry, I know this is an essentially pointless question, but _why_ does XWin require internet access??!! and, are there other / better switches I should or could be using than -nolisten local to render the application useable on a non-networked machine? Thanks, Fergus cygcheck.out Description: Binary data
cygwin-X: bits of .Xdefaults selectively ignored
When starting rxvt after XWin -multiwindow, most of ~/.Xdefaults is picked up (such as rxvt*background, rxvt*foreground, rxvt*color10, rxvt*geometry and many more) but, whatever I try, I can't get it to implement rxvt*font: Lucida Console-14 though this, and all the other instructions, are successfully read identified and enacted in rxvt in non-X mode. Any help / ideas? PS. Despite several efforts to identify the rules going on here, I can find no easy way of defining/ guessing/ forecasting which fonts from the Windows provision rxvt will understand, and which not. Thank you. Fergus
How to kill XWin from a script
This might be well-known, in which case sorry for wasting your time.
It can be inconvenient to have one or several copies of XWin remaining after
exiting Cygwin.
You can do kill PID but for this you need to know what the PID is and then
type the command explicitly.
A command (or script) which will kill them all stone dead without previous
reference to ps is
kill `ps | grep XWin | awk '{print $1}'`
Put it in .bash_logout? Or wherever suits.
Fergus
Re: internet required?
Actually, I think there's something to this. A few versions of XWin ago (I can look it up if it will help) I could use X in a Cygwin process from a portable CD by initiating the process as bash mount -buf c:/tmp /tmp/ XWin -nolisten local -multiwindow rxvt -display localhost:0.0 and this allowed me an X environment with no internet access (and from any Windows machine, even if not networked). (Plus appropriate tweaks to .bashrc etc. The point of this email is not the portability of the system but the useability of XWin in a portable context.) Today I made a new CD, with a completely up-to-date Cygwin. Something HAS altered because now the 4th line gives me a rxvt cannot open display error msg, and it is clear that Norton Firewall is taking an interest whereas previously this had not occurred (presumably the -nolisten local switch played a role here?) More details, if I can, if you need them ... Thanks. Fergus
Re: Portable Cygwin works, but XWin fails
Solution: Mount /tmp to the windows tempdir mount -bu $(cygpath -m $TEMP) /tmp mount -bu $WINDIR/Temp /tmp Thank you. This worked just fine. I now possess a superb portable CD with stats, emacs, vim, Perl, LaTeX, ..., which I can use in any Windows machine with a CD drive. CD still only 640/700 full. ... Fergus
Portable Cygwin works, but XWin fails
I have been able to run portable versions of Cygwin, reduced in one way or another, both from writable USB memory sticks and from unwritable CDs. Lately I tried running XWin from a writable stick. By observing which files were written where, and as a consequence setting up links using ln -s /dev/null /tmp/Xwin.log ln -s /dev/null /var/run/utmp it really seemed that I had addressed all problems: in repeated uses, nothing new was written to the stick at all. I then burned a CD, but disappointingly XWin dies as soon as it is started. That is, I start the process with bash, and then try XWin -multiwindow which I would normally follow with rxvt -display localhost:0.0 -e bash but XWin does not persist. (Sorry: I don't know how to express what happens other than to say it dies immediately.) This is VERY disappointing. Any clues to what else I might try? By the way, in mounting the portable version, I have already established that the directory /cygdrive/c/tmp/ must exist, so I suppose I could try ln -s /cygdrive/c/tmp/XWin.log /tmp/XWin.log before burning to CD. (I've already made 5 coasters. At this rate I'll be able to floor the bathroom.) Thanks. Fergus
Re: Portable Cygwin works, but XWin fails
Thank you: No, I now think (on looking at a file /cygdrive/c/tmp/XWin.log, brought into being by defining the link described in my previous email) that the problem seems not to be with the creation of this file, but with the creation of the directory /tmp/.X11-unix. (The file XWin.log says: _XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno = 17 _XSERVTransMakeAllCOTSServerListeners: failed to create listener for local Fatal server error: Failed to establish all listening sockets winDeinitClipboard - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress and the noting shutdown in progress must be what I have described as XWin dies.) So: is there a way I can try to get this directory (and, specifically, I suppose, its contents) written to /cygdrive/c/tmp/ rather than to /tmp/? Fergus PS: Entirely unrelated question. When I start XWin from a conventional HD full installation of Cygwin, on a broadband 24-hour internet-connected machine, it evidently accesses the web. (I know this, because when Norton is up and running, I can tell that XWin specifically asks permission to do so.) Why does it do this? As far as I can tell, if I pull the broadband plug, Cygwin and XWin still work ...)
Re: Portable Cygwin works, but XWin fails
What is your display variable set to? localhost:0.0 Do you have a /tmp/.X11-unix/X0 file on your memory stick? Yes: so I wonder whether in trying to make a CD version, as well as re-routing the file /tmp/XWin.log, I ought also to try to re-route the file /tmp/.X11-unix/X0. But: the trouble seems to occur earlier, at the point that XWin atempts to make the directory /tmp/.X11-unix. Can I trick XWin into creating this elsewehere (i.e. somewhere writeable?) Fergus
Re: Portable Cygwin works, but XWin fails
No, you don't need to. Just Xwin.exe -nolisten local. Thank you. This worked just fine. I take the point about Google-ing - that's how I learned that diverting tmp/XWin.log might help. I didn't see the -nolisten local advice ... Just one final question: when I get into rxvt after XWin -nolisten local -multiwindow , the keyboard suddenly becomes USA, whereas it is set (correctly) to UK otherwise, within bash, within rxvt and for that matter within Windows. In this case, when I exit rxvt back to bash, the UK keyboard is recovered. Does the -nolisten local switch impose some kind USA default, as it would indeed appear to do? Fergus
Failure to make grap 1.30 under cygwin 1.5.5
A configure / make /make install that has been working successfully oob for a long time recently failed. the relevant .tgz is unaltered, only Cygwin has changed. Does the following output from make, throw any light on this? The configure worked fine. I attach cygcheck.out. Fergus ~/tmp/grap-1.30 make grep ^# grap.y grap.cc ; grep ^# grap_lex.l grap_lex.cc; touch y.tab.h g++ -MM -Wall -DHAVE_CONFIG_H grap.cc grap_lex.cc *.cc .depend; rm -f grap.cc grap_lex.cc y.tab.h bison -y -d grap.y mv y.tab.c grap.cc g++ -Wall -DHAVE_CONFIG_H -c -o grap.o grap.cc flex -ograp_lex.cc grap_lex.l g++ -Wall -DHAVE_CONFIG_H -Wno-unused -c grap_lex.cc grap_lex.l: In function `void expand_macro(macro*)': grap_lex.l:979: error: `yytext_ptr' undeclared (first use this function) grap_lex.l:979: error: (Each undeclared identifier is reported only once for each function it appears in.) grap_lex.l: In function `bool is_macro(const std::string)': grap_lex.l:990: error: parse error before `--' token grap_lex.l: At global scope: grap_lex.l:996: error: parse error before `]' token make: *** [grap_lex.o] Error 1 ~/tmp/grap-1.30 cygcheck.out Description: Binary data
Re: Failure to make grap 1.30 under cygwin 1.5.5
flex 2.5.31-1 sucks ... ... upgrade to 2.5.4-2. Well this worked just fine. Thank you very much for this pragmatic help. Fergus
Re: Still getting Signal 11 error msg
Attaching cygcheck output is something that Fergus has seemed reluctant to do. The cygwin problems page also has a lot of tips for reporting problems, one of which is to not send email with vague subjects. Sorry -- I was at fault on both counts. Thank you Chris, Harold and Jan for picking this up. You have helped greatly, as follows: Start - Run - start XWin -multiwindow Start - Run - run rxvt -display localhost:0.0 -e bash --login -i xdvi a4.dvi Signal 11 xdvi.bin a4.dvi ** successful presentation to screen of a4.dvi ** My reluctance to attach cygcheck output stems from not knowing what's best to send. So here (two attachments) is the output from cygcheck -c (I understand some or all Incompletes not to matter) and from cygcheck -srv. Thanks again for all your help. I appreciate it. Fergus cygcheck.srv Description: Binary data cygcheck.c Description: Binary data
xdvi Signal 11 failure
Up to date with everything, W98/SE, massive upgrade to tet*/tex*2-12* this morning: I now find a re-occurrence of an earlier problem, which is that xdvi a4.dvi returns the message Signal 11 rather than previewing a well-tested and unaltered a4 page of maths. This, following start XWin -multiwindow run rxvt -display localhost:0.0 -e bash Something I've forgotten to do? By the way, because it was convenient, I also installed the *2-12*src* files under /usr/src/. There were very many occurrences of the warning messages warning: moving directory out of the way warning: deleting so I can make a directory there (Not that this interferes with the utility of any programs.) Fergus
xpdf as an alternative to Acrobat Reader
There's always Acrobat Reader for viewing .pdf files, but I just tried looking at xpdf from ftp://ftp.foolabs.com/pub/xpdf/xpdf-2.02pl1.tar.gz. As far as it goes, it installs in Cygwin very nicely but at the end of the configure stage it says configure: WARNING: Couldn't find X / Motif you will be able to compile pdftops, pdftotext, pdfinfo, pdffonts, and pdfimages but not xpdf and indeed at the end of make install there they all are, but not xpdf. Has anybody succeeded in a successful install and is it easy to explain how? Thank you. Fergus
Re: xpdf as an alternative to Acrobat Reader
You need to install lesstif and the XFree86-lib-compat packages, if they are not already installed. Thank you for swift response. These are, and were, both already installed. Do I need to do a bit of background re-naming or something to fool the xpdf installer into believing that it is Motif not lesstif that is installed? Fergus
Two simple QQ about XWin
Q1. Can anybody tell me what startup sequence (another/ different command line switch?) is equivalent to Start - Run - start XWin -multiwindow then point to the System Tray and choose Show Root Window please? Thank you! Q2. I've compared $ set vars.list both when XWin is running and when not, expecting a small difference in env vars (or something). But all that has changed are PIDs. I want to be able to query the O/S to ask whether X is running or not. Is there a way of doing this, please? Apart from say ps -a | grep XWin. Thank you! Fergus P.S. There are so many ways of starting Cygwin up ... there are often questions on the list How Do You Start Yours? For a non-X system I use rxvt -e bash with presentation options picked up from ~/.Xdefaults. For X it seems to have to be a two-liner start XWin -multiwindow # see Q1 above for what I really want run rxvt -display :0.0 -e bash for a nice sparse system. I am not wild about the default startx. Any advance on this for a nice neat rxvt session in an X environment? Any possibility of a one-liner that I'm missing? Fergus
Re: Incorporating .epsi files into TeX docs : failure
Thank you very much indeed. I put /usr/X11R6/bin/ before /usr/bin/ in the PATH so that the gs.exe I wanted was picked up before the other gs.exe I didn't want. Now it all works perfectly. I'll leave PATH defined like this (i.e. with the transposition). There may be other consequences, not all good, since I don't always start XWin ... we'll see. Thanks again. Fergus
Re: Recent upgrade of xfree-xserv: missing DLLs
There is a new package, XFree86-lib-compat-4.3.0-1, that contains the old DLLs for 4.2.0 X Clients. Thank you for swift response. Also (2) now in rxvt under XWin I find that pressing # gives \, pressing ~ gives |, pressing \ gives and pressing | gives . No similar keyboard problems with bash. Also (3) when XWin is not started, I cannot even run rxvt (as in rxvt -e bash). Hmmm. No point in worrying about probs 2 and 3 when I know a solution to prob 1 is in the pipeline. Thank you. I will let you know how things go. Fergus
Re: Recent upgrade of xfree-xserv: missing DLLs
There is a new package, XFree86-lib-compat-4.3.0-1, that contains the old DLLs for 4.2.0 X Clients. OK. XFree86-lib-compat-4.3.0-1 eventually reached a mirror near me, and I installed it. Things now work that for a brief period did not. However, after set DISPLAY followed by start XWin -multiwindow followed by run rxvt -e bash, I still find that pressing # gives \, pressing ~ gives |, pressing \ gives and pressing | gives whilst these keys work just fine in bash. I do not mean to download every agony on readers, and will continue to try to sort this. But is anybody experiencing similar recent anomalies, and are they indicative of something obvious? Fergus
Recent upgrade of xfree-xserv: missing DLLs
I just upgraded this morning from XFree86-xserv-4.3.0-1 to 4.3.0-2, jumped immediately into xdvi, and got a missing DLL message, specifically libice.dll. Unfortunately reverting to 4.3.0-1 did not recover things: I get the same message. I am not totally certain the two events (upgrade, message) are related: yesterday there was a massive upgrade of other parts of the XFree86 provision. Any connection? Fergus
Newbie : XWin, rxvt, gv
After using rxvt without XFree I thought I'd try XFree. I'm amazed. Almost
everything just works, and the bits that don't must be my bad driving. It's
so nice to use gnuplot (which compiled oob) and not wgnuplot, for instance.
Apart from a minor error msg, xdvi simply works. So does latex. I'm
absolutely staggered.
I'm running W98/SE.
I would like to ask a couple of questions:
Q1 of 2.
I start things up with a three-line batch file
set DISPLAY=127.0.0.1:0.0
start XWin -multiwindow
run rxvt {switches} -e /bin/bash
I'm sorry: I'm completely new to this. are the args to DISPLAY to do with
size and resolution or something else? What is the role of the word start?
I ask because on exiting rxvt I always end up with a copy of XWin hanging
around that has to be kill'd through Task Manager. Can I omit the word
start, or if not, should there be a 4th line that carries the sense of stop
XWin? Similarly, the word run. Can I omit this word and just use
rxvt {switches} -e /bin/bash?
Q2 of 2.
In Feb there were two postings about gv. Currently I use gsview32 from
GSTools, but I really dislike having to nip outdoors to use something. Has
anybody successfuly compiled gv-3.5.8 into Cygwin (or later? 3.5.8 is the
most modern I could find).
Thank you very much. Sorry for the very simple-minded nature of these
questions.
Fergus
Corrupted file x2x-1.27-1-src.tar.bz2
In the directory release/XFree86/x2x/, the file x2x-1.27-1-src.tar.bz2 has the correct md5sum (being 87075ba00b0cd15f35975c956f14591a); but running bzip2 -tv gives a file ends unexpectedly error message, and attempting to run bzip2 -dv fails. Fergus
