I have installed the official kde-3.5.2 packages on my slackware 10.2 (i.e.
not slackware current).
but when I launch it, I encounter this problem:

~# startx

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/box:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.13 i686 [ELF]
Current Operating System: Linux box 2.4.31 #6 Sun Jun 5 19:04:47 PDT 2005
i686
Build Date: 11 September 2005
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun May 7 10:30:51 2006
(==) Using config file: "/etc/X11/xorg.conf"
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
kstartupconfig: error while loading shared libraries: libstdc++.so.6: cannot
open shared object file: No such file or directory
/opt/kde/bin/startkde: line 83: /root/.kde/share/config/startupconfig: No
such file or directory

waiting for X server to shut down

Filippo wrote:

> I have installed the official kde-3.5.2 packages on my slackware 10.2
> (i.e. not slackware current). but when I launch it, I encounter this
> problem:

You're probably going to need to upgrade some libraries as well.

> _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
> _XSERVTransOpen: transport open failed for inet6/box:0
> _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

There's probably a way to tell the Xserver not to (try to) use inet6
sockets.

> kstartupconfig: error while loading shared libraries: libstdc++.so.6:
> cannot open shared object file: No such file or directory

cxxlibs is out of date, compared to the version that KDE is looking for.

I don't think it's a good idea to try to run some packages from -current
on a "stable" system. You're likely to run into problems of exactly
this sort. If you really must have the KDE upgrade, you're probably
better off getting the sources, and the SlackBuild script from -current,
and building it fresh on your system.

I hope that helps.

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

Op Tue, 09 May 2006 12:12:14 +0200, schreef Filippo:

> I have installed the official kde-3.5.2 packages on my slackware 10.2 (i.e.
> not slackware current).
> but when I launch it, I encounter this problem:

> <snip>

> kstartupconfig: error while loading shared libraries: libstdc++.so.6: cannot
> open shared object file: No such file or directory
> /opt/kde/bin/startkde: line 83: /root/.kde/share/config/startupconfig: No
> such file or directory
>
> waiting for X server to shut down

i got around that by upgrading the gcc packages from the /d dir. in
-current.
but i guess you better just completely upgrade to -current to avoid more
prob.'s

cashmir

Sylvain Robitaille wrote:

> I don't think it's a good idea to try to run some packages from -current
> on a "stable" system. You're likely to run into problems of exactly
> this sort. If you really must have the KDE upgrade, you're probably
> better off getting the sources, and the SlackBuild script from -current,
> and building it fresh on your system.
>
> I hope that helps.

merci. I will try to upgrade the whole system

cashmir wrote:

> but i guess you better just completely upgrade to -current to avoid more
> prob.'s

I can upgrade everything. since it is the first time that I would do it,
which program that does it automatically is advisable?

Filippo wrote:
> cashmir wrote:
>
>> but i guess you better just completely upgrade to -current to avoid more
>> prob.'s
>
> I can upgrade everything. since it is the first time that I would do it,
> which program that does it automatically is advisable?

I like to use slackpkg for this (I think it is in Extra).

Be careful though - don't let it automatically update your kernel, and
there some packages that should be 'blacklisted' from upgrading:

$ cat /etc/slackpkg/blacklist
# This is a blacklist file. Any packages listed here won't be
# upgraded, removed or installed by slackpkg.
#
# The correct syntax is:
#
# to blacklist the package xfree86-devel-4.3.0-i386-1 the line will be:
# xfree86-devel
#
# Please, DON'T put any blank line(s) or any space(s) before or
# after the package name.
# If you do this, the blacklist will NOT work.
#
# Automated upgrade of kernel packages aren't a good idea (and you need to
# run "lilo" after upgrade). If you think the same, uncomment the lines
# below
#
kernel-ide
kernel-modules
kernel-source
kernel-headers
aaa_elflibs
alsa-driver
alsa-lib
alsa-utils
alsa-oss


Another thing; take a careful look at the -current Changelog. It's not
only upgrades, but some packages have been split (i.e. there are new
packages), and some have been added (amarok, libtunepimp, musicbrainz,
IIRC).

With all this in mind, all that remains is

# slackpkg update
# slackpkg update-gpg
# slackpkg upgrade-all

Good luck!

PJ

PJ Beers wrote:
> Another thing; take a careful look at the -current Changelog. It's not
> only upgrades, but some packages have been split (i.e. there are new
> packages), and some have been added (amarok, libtunepimp, musicbrainz,
> IIRC).
... and Slacpkg will not automatically install these packages, that's
the real problem. Some of these are needed for KDE to run.

PJ