Re: [XFree86] X-Server Crashes
Ar an 23ú lá de mí 1, scríobh a v : > i am attaching the logfile generated when the Xserver > crashed. Kindly reply at the earliest (**) FontPath set to "unix/:7100" [...] Fatal server error: could not open default font 'fixed' Looks like your font server isn't supplying you with a "fixed" alias. A workaround may be to add a line FontPath "/usr/X11R6/lib/X11/fonts/misc" before the 'FontPath "unix/:7100" line in your /etc/X11/XF86Config file, but in the long term you should probably work out why XFS isn't being started, or (more unlikely) why it isn't reading /usr/X11R6/lib/X11/fonts/misc . -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] X server crash and daemon/ServAuthDir pops up
Ar an 24ú lá de mí 1, scríobh a v : > Server Authorization directory (daemon/ServerAuthDir) is set to > /var/gdm but this does not exist. Please correct gdm configuration > /etc/X11/gdm/gdm.conf and restart gdm. This is a GDM, and therefore a Gnome problem. There doesn't seem to be a general gnome-user list, from looking at mail.gnome.org/mailman/ listinfo, so I'd suggest contacting your distribution-specific mailing lists for more detailed support on this. That said, you could, as root, create the directory /var/gdm, and give it appropriate permissions--700 should be fine if it behaves like its xdm counterpart. The following commands might do the tricl; mkdir /var/gdm chmod 700 /var/gdm -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] help in video card configuration
Ar an 24ú lá de mí 1, scríobh Vijay Kumar : > Can you please check it and help me to solve the problem. Have a look at http://marc.theaimsgroup.com/?l=xfree86&m=104339850812697 In general, searching mailing list archives before posting to that list will a) make your question more informed, b) make you look more clueful and c) be faster. -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] No config file?
Ar an 27ú lá de mí 1, scríobh Marek Denis : > (EE) Unable to locate/open config file [...] > WHAT's UP > > Thx for eventually help As root; cp /root/XF86Config /etc/X11 and try again. -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Segmentation Fault
Ar an 28ú lá de mí 1, scríobh Jordi Ferrer Plana : > I have a problem with my X server and Qt. When I try to start a Qt > application (like designer) I get a Segmentation Fault. Whe I try to > execute that application (on the same machine) to another X server > ($designer -display 192.168.1.2:0.0) it works fine. Anyone can help me? > How can I debug that (Xfree86.log doesn't report anything)? If you have the source to an application which displays this behaviour, compile it with debugging turned on, and identify the QT function with which you have this problem. (Running the application under gdb(1) would normally make this easier.) That should narrow down the problem, and will make guessing what the problem is easier. -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] probs related to running xserver
Ar an 29ú lá de mí 1, scríobh vikash gautam : > when i m starting xserver i m getting following message in log > file: [..] > (EE) Unable to locate/open config file > (EE) Error from xf86HandleConfigFile() You need a configuration file. Try running "xf86cfg" and copying the resulting XF86Config file to the directory /etc/X11 . -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Unable to go to the graphical mode -
Ar an 29ú lá de mí 1, scríobh chaitali : > I have loaded Linux on a machine the specufications are given below but am > unable to go to the graphical mode. Please help Your font server isn't running. Do a search for unix/:7100 in the archives of this mailing list at http://marc.theaimsgroup.com/?l=xfree86&r=1&w=2 , and your should be able to find a workable solution. -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] error X server
Hi,
Ar an 6ú lá de mí 2, scríobh Egbert Eich :
> Starting with XFree86 4.3 there are plans to build both fonts
> into the Xserver.
I'm not convinced that's particularly useful--these errors almost all
result from one particular distributor's limiting of the font path to
unix/:7100 . Perhaps the error message could be something like the
below; I realize ANSI string concatenation isn't something that can be
relied on, though.
Bye,
- Aidan
--
"I have heard the swelling cry of the English speaking peoples of the
world, and it tells me their cause is served best by flaming the few
complacent asses on usenet." -- T. Samant, 29 June 1997
--- xc/programs/Xserver/dix/main.c 2002-02-19 11:09:22.0 +
+++ /home/hcksplat/main.c 2003-02-06 14:49:17.676311000 +
@@ -397,10 +397,14 @@
defaultFontPath);
}
if (!SetDefaultFont(defaultTextFont))
- FatalError("could not open default font '%s'", defaultTextFont);
+ FatalError("could not open default font '%s'.\n"
+ "check any font servers are running, and that there is an\n"
+ "alias for '%s' somewhere in the font path.", defaultTextFont,
+defaultTextFont);
+
if (!(rootCursor = CreateRootCursor(defaultCursorFont, 0)))
- FatalError("could not open default cursor font '%s'",
- defaultCursorFont);
+ FatalError("could not open default cursor font '%s'"
+ "check any font servers are running, and that there is an"
+ "alias for '%s' somewhere in the font path.",
+defaultCursorFont, defaultCursorFont);
#ifdef DPMSExtension
/* check all screens, looking for DPMS Capabilities */
DPMSCapableFlag = DPMSSupported();
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] xdm question
Ar an 6ú lá de mí 2, scríobh Pacho Baratta : > "mozilla-bin" > "mozilla-bin" > "mozilla-bin" > "mozilla-bin" > "mozilla-bin" > . > . > > five instances of mozilla running means wasting about 50 Mb of ram, too much > for my machines... Mozilla is threaded pretty heavily, and, depending on your operating system, seperate threads may show up as seperate PIDs, even though they share the same address space and memory. So you may be counting the RAM those process use multiple times. -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Re: Security in new drivers
Ar an 12ú lá de mí 2, scríobh Mike A. Harris : > Anything short of a specific example of a real security problem > is nothing more than heresy. Don't get all dogmatic about it, Mike :-) . (Yes, you meant hearsay.) -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] possible to disable xinerama in xfree compilation?
Ar an 19ú lá de mí 2, scríobh revo : > now i don't know how to check if it really disabled and not > compiled. Once you've installed the build, start up the X server, then run the command "xdpyinfo -queryExtensions | grep -i xinerama" (without the newline) . If it returns a match, you have the xinerama extension built. If the library has been built, there'll be files in /usr/X11R6/lib/ matching the pattern libXinerama* . > can anyone please comment on this, if this is the right approach? > the goal of all this is to have a USE variable in gentoo's portage > called xinerama which allows to disable/enable having xinerama on > the whole system. Yeah, that should be the right approach. -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [Bug 72] #define HasParallelMake to YES in host.deffails on NetBSD 1.6P
Ar an 1ú lá de mí 4, scríobh Mark Vojkovich : >ParallelMake was never really supported and it would be alot of > work to make it function properly, so unless somebody wants to volunteer > to fix it, I don't think it's going to work any time soon. There should probably be a comment mentioning that in Imake.tmpl, in that case. To someone who doesn't know make that well, the error is confusing, and generic. > The problem is that a lot of dependencies are broken. Okay, so to fix that one would have to add in more dependency information in the various submakefiles? And build, and see what fails and why, and repeat. > You should be able to get a parallel build to complete with an old (less > parallel) version of make, like 3.75, but you'll need to do "make World; > make" to have it fix some of the stuff it missed on the first pass. To > my knowledge, everything builds properly with that, though I haven't > tried it in several months. Hmm. If you read the rest of that bugzilla entry, it seems that what parallel make support is there was written for the make(1) on various SVR4s (notably excluding Solaris), and that GNU make was never really supported with it. That would mean that your results above make sense. Right, I'll go mess with this some more and see can I do something constructive :-) [ Should this be going into the bugzilla entry, somehow? ] -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: final issues... xfree86 for the VIA Apollo CLE266
Ar an 1ú lá de mí 8, scríobh George Georgalis : > How do I disable tcp/6000 connections? No-one else seems to have mentioned this, so I'll address it; pass the server the options "-nolisten tcp" on the command line. -- "These are the prettiest looking witnesses we have had in a long time. I imagine you are all married. If not, you could be if you wanted to be." ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: final issues... xfree86 for the VIA Apollo CLE266
Ar an 4ú lá de mí 8, scríobh George Georgalis : > It works great, even if I kill X it comes back up, but it still listens > on 6000. I find this odd, maybe I need to invoke it with Xfree86, not X? Hmm, that shouldn't make a difference. I've got "-nolisten tcp" working on this machine with the 4.3.99.5 snapshot; it's getting called as /usr/bin/nice -15 /X11/bin/X -nolisten tcp -logverbose 2 -wm vt02 and both nmap(1) and lsof(1) confirm that it's not listening on TCP. Perhaps you could try moving the -nolisten tcp to the first two argument positions? -- "These are the prettiest looking witnesses we have had in a long time. I imagine you are all married. If not, you could be if you wanted to be." ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
