post-upgrade problems

[Jon TURNEY]

Tom Roche wrote:
> summary: After upgrading from X 6.8.99.901-1 to 7.4-1, I had font
> problems, but could launch an xterm from the new cygwin. After
> attempting to fix that by installing fonts, I cannot launch an xterm
> from the new cygwin.
> 
> details:
> 
> I'm attempting to debug a problem with the cygwin upgrade I attempted
> today (25 May 09). I haven't upgraded for about a year, so I went from
> xorg-x11-* version=6.8.99.901-1 to version=7.4-1. (For details of the
> old config, see
> 
> http://www.unc.edu/~tr/cygcheck_20090525old_1404.txt
> 
> Note that, 
> 
> * while `cygcheck` shows my winXP=SP2, I believe it's actually SP3,
>   and up-to-date, except for WGA.
> 
> * I'm able to switch between my old and new cygwins by changing
>   windows paths and cygwin mounts. The old cygwin still works
>   correctly: I'm using it to compose and send this post.
> 
> ) I initially upgraded to the configuration represented by
> 
> http://www.unc.edu/~tr/cygcheck_20090525new_1420.txt

> It had font-related problems:
> 
> 0 When I started my initial xterm (via a copy of startXwin.bat), I
>   noticed that it showed a toolbar, whereas my previous cygwin's xterms
>   did not. Is that working as designed?

http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-how-do-i-get-rid-of-xterm-menu

> 1 When I started my initial xterm, I noticed that all the chars in the
>   toolbar were in the same huge font, though the body text of the
>   xterm is normal.
> 
> When I run emacs from the initial xterm
> 
> $ emacs --debug-init &
> 
> I get the following problems
> 
> 3 In the launching xterm: I see the error text
> 
>> Warning: Cannot convert string "-*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
>> Warning: Cannot convert string "-*-helvetica-medium-r-*--*-120-*-*-*-*-iso8859-1" to type FontStruct
> 
> 4 In the launched emacs: all char in its menubar were in same huge font
>   as the launching xterm's menubar.
> 
> 5 In the launched emacs: all char in the body of its frame (i.e. where
>   the text of a file would display) displayed as boxes, i.e. as
>   unrepresentable.

http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-where-are-my-fonts

> After perusing the cygwin-xfree archives, I decided I needed to
> install fonts. Instead of being cautious, I just installed all the
> font-* packages, resulting in the configuration
> 
> http://www.unc.edu/~tr/cygcheck_20090525new_1530.txt
> 
> but something went horribly wrong, since now I can't even launch an
> xterm :-( When I run my startXwin.bat, 
> 
> 0 the window for that batch file pops up briefly
> 
> 1 the window for Xwin.exe opens briefly, then closes
> 
> and I never get my xterm. When I try to open an xterm (or emacs) by
> right-clicking on the X in my tray and then choosing Applications>
> xterm, nothing happens. (The only thing that I'm able to open with
> tray>rclick>Applications is notepad.)
> 
> What should I do to fix this?

Try starting xterm from a shell.  It may be reporting some error as it tries 
to start up, but you can't see it with either of those methods of starting it.

You'll probably want to read about the upgrade at
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-x-is-broke
as 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/