Re: Could not init font path element
On Fri, 21 Jan 2005, Matt Pregent wrote: > How do I fix this error? > Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing > from list! Install CID fonts. Uless you really need them, this is not an error at all but just a warning. No one uses CID fonts but the entry is still in the upstream xserver sources. Don't worry about it. > winPointerWarpCursor - Discarding first warp: 509 353 This one is just a notice that the xserver did not warp the pointer to the center of the screen. It is not required and is considered bad bahviour if the xserver forces the pointer to the center of the screen on startup. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: Could not init font path element
I've installed the CID fonts, well I think I did it right anyway, but it still gives me that grayish logon screen and I get no login screen at all. -Matt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander Gottwald Sent: Friday, January 21, 2005 9:39 AM To: cygwin-xfree@cygwin.com Subject: Re: Could not init font path element On Fri, 21 Jan 2005, Matt Pregent wrote: > How do I fix this error? > Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, > removing from list! Install CID fonts. Uless you really need them, this is not an error at all but just a warning. No one uses CID fonts but the entry is still in the upstream xserver sources. Don't worry about it. > winPointerWarpCursor - Discarding first warp: 509 353 This one is just a notice that the xserver did not warp the pointer to the center of the screen. It is not required and is considered bad bahviour if the xserver forces the pointer to the center of the screen on startup. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: Could not init font path element
On Fri, 21 Jan 2005, Matt Pregent wrote: > I've installed the CID fonts, well I think I did it right anyway, but it > still gives me that grayish logon screen and I get no login screen at all. Cygwin/X by itself does not provide a login screen. For remote use (login to a unix machine) you'll have to supply special parameters. please check the Cygwin/X userguide. It describes in detail how to use Cygwin/X http://x.cygwin.com/docs/ug/cygwin-x-ug.html bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: Could not init font path element
I've specified parameters already and it doesn't work. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander Gottwald Sent: Friday, January 21, 2005 10:56 AM To: cygwin-xfree@cygwin.com Subject: RE: Could not init font path element On Fri, 21 Jan 2005, Matt Pregent wrote: > I've installed the CID fonts, well I think I did it right anyway, but > it still gives me that grayish logon screen and I get no login screen at all. Cygwin/X by itself does not provide a login screen. For remote use (login to a unix machine) you'll have to supply special parameters. please check the Cygwin/X userguide. It describes in detail how to use Cygwin/X http://x.cygwin.com/docs/ug/cygwin-x-ug.html bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: Could not init font path element
Matt Pregent wrote: > I've specified parameters already and it doesn't work. Then check the FAQ. The is a large section in remote (XDMCP) usage. http://x.cygwin.com/docs/faq/cygwin-x-faq.html#xdmcp Maybe the remote access was disabled on the server or the network setting on windows is broken (use -from parameter and make sure reverse dns works properly) bye ago NP: Human Decay - Reduplication -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Could not init font path element
On Tue, 3 May 2005, a12 wrote: > Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing > from list! xorg-x11-fscl > Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, > removing from list! xorg-x11-fscl > Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing > from list! There are no such fonts in the distribution > Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, > removing from list! xorg-x11-f100 bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Could not init font path element
Hello, Thank you very much for your quick & adequate reply. Regards, Marek Alexander Gottwald wrotev: On Tue, 3 May 2005, a12 wrote: Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from list! xorg-x11-fscl Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! xorg-x11-fscl Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! There are no such fonts in the distribution Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! xorg-x11-f100 bye ago
Re: Could not init font path element problem
On Thu, Sep 15, 2005 at 09:58:51AM -0400, Francois Couillard wrote: > Okay when I'm trying to launch xwin from Cygwin prompt I get a "Could > not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from > list". > > In the Cygwin/X FAQ, they say to fix this problem by > a. Open a Cygwin shell and run *umount /usr/X11R6/lib/X11/fonts > * -- When I do that, it just say "No such file or directory" even though > it exist. Probably isn't mounted I guess. What's that mean? > > Then I have to reinstall the xorg font package. I tried to no avail. > > How can I get the correct font element? Any help would be greatly > appreciated. > Unless you want those fonts for a particular reason, I wouldn't worry about it, as those type errors are non-fatal. My Cygwin/X runs fine with the following errors: Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! Regards, Ken -- 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/
