[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: A couple of more issues...

Laurent de Segur wrote:
> on 9/4/01 8:49 AM, Colin Walters at walters@verbum.org wrote:
> >
> >> - Finally X windows won't start up. Period. It has nothing to do
> >> with kernel 2.4.8. It has been like that even since I did the update
> >> to woody. If I enter the command startx, it tells me that it can't
> >> stat /etc/X11/X.
> >
> > Hm, strange.  Do you have the `xserver-xfree86' package installed?
> No, I didn't. Thanks for pointing that problem to me. How come was I able to
> install xfree86 with out being warn about not selecting xserver? Does that
> mean that I need to select the individual xfree86 packages manually? This
> would be really hard to remember all the names of various packages if it was
> the case. I probably misunderstood something.

You've discovered the flexibility of the X windowing system and the Debian
packaging. X's network transparency makes it possible to use clients without a
local server; Debian doesn't impose an artificial dependency on it.

If you want everything to use X locally, run tasksel and select the X window
core or full task.

> When I do apt-get install xserver-xfree86, I get a nasty string during
> installation that shows in the dialog next to ok, stating that 'Failed to
> open configuration file /etc/exim/exim.conf'. I think that I read this in
> another message. Not sure what is causing it.

Sounds like exim isn't configured yet, run eximconfig.

> I got my XF86Config-4 file from someone who's got the same iBook 2001. When
> I do a startx, the error message I get is: no screens found. The log stated
> that Screen(s) found but none have a usable configuration (!) I checked that
> my screen was set correctly for this machine and it seems like it. FYI, I
> run the xfree86 from Woody (4.0.3). Has anyone with a similar machine ran
> into that problem?

Yes, almost everyone for whom it doesn't work. ;)

That's a generic error which can be caused by a myriad of problems. Looking
carefully at /var/log/XFree86.0.log might reveal the cause. One common problem
is that you have to provide a bus ID.

Earthling Michel Dänzer (MrCooper)    \   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \        XFree86 and DRI project member

Reply to: