With 10.2, I was not able to compile wine. So, when the changelog came with
a new x11-6.8.2 to address just this fault I was happy!
However, after installing the new x11-6.8.2 my X server would not start..
Ok, I reinstalled the old x11-6.8.2 from my install CD. Still the X server
will not start!

My questions are:
1) just installing a new version (using pkgtool) - may that break the
system?
2) is there any easier way to repair the damage (than reinstalling
Slackware)?

occam wrote:
> With 10.2, I was not able to compile wine. So, when the changelog came with
> a new x11-6.8.2 to address just this fault I was happy!
> However, after installing the new x11-6.8.2 my X server would not start..
> Ok, I reinstalled the old x11-6.8.2 from my install CD. Still the X server
> will not start!
>
> My questions are:
> 1) just installing a new version (using pkgtool) - may that break the
> system?
> 2) is there any easier way to repair the damage (than reinstalling
> Slackware)?

The server (probably) won't start because installing x11-6.8.2 overwrote
your working xorg.conf (etc/X11/xorg.conf). Always keep a backup of any
xorg.conf's that work!

Le Wed, 28 Sep 2005 23:49:39 -0500, Chris Sorenson a écrit*:

> occam wrote:
>> With 10.2, I was not able to compile wine. So, when the changelog came with
>> a new x11-6.8.2 to address just this fault I was happy!
>> However, after installing the new x11-6.8.2 my X server would not start..
>> Ok, I reinstalled the old x11-6.8.2 from my install CD. Still the X server
>> will not start!
>>
>> My questions are:
>> 1) just installing a new version (using pkgtool) - may that break the
>> system?
>> 2) is there any easier way to repair the damage (than reinstalling
>> Slackware)?
>
> The server (probably) won't start because installing x11-6.8.2 overwrote
> your working xorg.conf (etc/X11/xorg.conf).

And where did you find this funny idea ?-D)

> Always keep a backup of any
> xorg.conf's that work!

This idea is a good one, though ;-)

One thing could be b0rken by an upgrade of x11- that's the call to
xinitrc in the startx script. And it won't do any harm if you already
have an ~/.xinitrc file.


What can you see in /var/log/Xorg.0.log ? Any error you could
print here or repair ?
Just saying "X server doesn't start" is not enough for my keyboard
to be able to help your chair ;-)

> > Always keep a backup of any
> > xorg.conf's that work!
>
> This idea is a good one, though ;-)

Yes, I DO have a backup (actually, two)

> One thing could be b0rken by an upgrade of x11- that's the call to
> xinitrc in the startx script. And it won't do any harm if you already
> have an ~/.xinitrc file.

That was ok..
>
> What can you see in /var/log/Xorg.0.log ? Any error you could
> print here or repair ?
> Just saying "X server doesn't start" is not enough for my keyboard
> to be able to help your chair ;-)

The messages were "screens found but no usable configuration" and
"failed to load GLX" (different times).
However, I reloaded the new version of x11, checked that the config
file was ok, and this time it worked.
But wine still does not compile, and the /var/log/packages has TWO
x11-6.8.2 entries, and I still cannot use my favorite usenet program
(Agent).

On Thu, 29 Sep 2005 08:44:16 +1000, occam <occam@internode.razoron.net> wrote:

>With 10.2, I was not able to compile wine. So, when the changelog came with
>a new x11-6.8.2 to address just this fault I was happy!
>However, after installing the new x11-6.8.2 my X server would not start..
>Ok, I reinstalled the old x11-6.8.2 from my install CD. Still the X server
>will not start!
>
>My questions are:
>1) just installing a new version (using pkgtool) - may that break the
>system?
>2) is there any easier way to repair the damage (than reinstalling
>Slackware)?

Well, I'll check what I did wrong later - now that I have my X system back.
I even got wine running - the package from LinuxPackages works well. Thank you,
Adam Schreiber!
================================================== ==
<remove my attribute to get my proper email address>