Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 15213 - After latest emerges of xfree and kde, there appears much borkedness
Summary: After latest emerges of xfree and kde, there appears much borkedness
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Seemant Kulleen (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-06 10:28 UTC by Guy
Modified: 2003-02-12 11:21 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guy 2003-02-06 10:28:11 UTC
I'm sorry for the bad summary description but I'm having problems dsecribing to
myself what is the actual problem.

I've gone through the very latest emerges of xfree, kde and baselayout.

All the emerges completed successfully.

I've run etc-update to update all the (many) config files changes. I tried to be
very careful in this step. On config files where I've made no changes, I've
overridden the old config file with the new config file (option 1). On config
files where I have made changes, I've interactively merged old and new (option 3).

The files I've merged include /etc/rc.conf and files of that sort.

Things I've noted so far are:

On machine 'dragon';

1) The computer automatically boots into the 'kdm' GUI. When I select my primary
user and 'kde-3.1' as the window manager, the kde boot progress box displays
that KDE 3.0 is loading.

2) I get a 'protocol unsupported' message. (I'll try to supply the message later
tonight.)

On machine 'work';

3) I get a 'protocol unsupported' message. (I don't yet know if it's the same
one. I'll try to supply this one later today.)

Notes: 

I think that this is all related to the config changes for X but I can't rule
out the multitude of config changes for kde.

I'm trying to see if there is other funny stuff happening, but some of it can be
hard to differentiate from things that were simply changed: example - on machine
 'work', the mouse pointer is completely different (large, semi-transparent and
with shadow) even though I have not updated fluxbox this week.

Reproducible: Didn't try
Steps to Reproduce:
1.
2.
3.

Actual Results:  
On machine 'work', the message is:

======================
Protocol not supported

file
======================

and I cannot 'browse' anything using konqueror. Besides the Internet, this
includes local directories etc.
Comment 1 Guy 2003-02-06 10:32:29 UTC
Here is the 'emerge info'

Portage 2.0.46-r9 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r3)
=================================================================
System uname: 2.4.20 i686 Pentium II (Deschutes)
GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png qtmt quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang readline arts tetex bonobo svga tcltk java guile X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl mozilla cdr -alsa"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-O2 -mcpu=i686 -pipe"
CXXFLAGS=""
ACCEPT_KEYWORDS="x86 ~x86"
MAKEOPTS="-j1"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"
Comment 2 Seemant Kulleen (RETIRED) gentoo-dev 2003-02-06 17:34:57 UTC
got any more details?
Comment 3 Guy 2003-02-06 17:56:38 UTC
What other details would you like? I have a list of the config files updated for xfree which I will look at on machine 'dragon' when I get home tonight. Other than that, I'm not sure where to start.

Fortunately, on machine 'work', fluxbox is my wm of choice and I have Moz, Opera and Lynx loaded as browsers so my ability to work is not impaired. And yes all three are working fine though konq is thoroughly borked.

On 'dragon', I have fluxbox loaded as my secondary wm so even there I'm not too put off. Of course, cut and paste across terminal windows don't work, but I have ways around that too.

I really would like some advice on what to start looking for and what to test. I can provide the .../work/config.log files from any of the packages you think appropriate as well.

:-)
Comment 4 Guy 2003-02-06 17:58:36 UTC
BTW - the emerge info provided so far is from machine 'work'
Comment 5 Guy 2003-02-06 20:51:04 UTC
Additional info from machine 'dragon':

When starting kde - in addition to the startup services dialog claiming that it is starting KDE 3.0 (instead of 3.1), it gives the following protocol message in a dialog box.

Could not start process Unable to create io-slave:
klauncher said: Unknown protocol: file

The kde menu is not available so I cannot launch any programs from within kde.

If I try to launch konqueror from within fluxbox, I get exactly the same results as from machine 'work'.

Actually, this turns out to be a much more serious problem for me than I originally thought. This is because I also can't launch KMail.

This is the 'emerge info' from machine 'dragon':

Portage 2.0.46-r11 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r3)
=================================================================
System uname: 2.4.20 i686 AMD Athlon(TM) XP1900+
GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg gnome libg++ mikmod mmx mpeg ncurses nls pdflib png qtmt quicktime spell truetype xml2 xmms xv zlib gtkhtml alsa gdbm berkdb slang readline arts bonobo svga tcltk java guile mysql X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gtk qt kde motif opengl mozilla cdr"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon-xp -O3 -pipe"
CXXFLAGS="-march=athlon-xp -O3 -pipe"
ACCEPT_KEYWORDS="x86 ~x86"
MAKEOPTS="-j1"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"
Comment 6 Seemant Kulleen (RETIRED) gentoo-dev 2003-02-09 06:03:38 UTC
can you remerge qt and kdelibs and test?
Comment 7 Guy 2003-02-09 22:52:15 UTC
I've been doing a number of things over the last three days.

I started by unmerging all the kde packages and xfree.

I explicitly remerged xfree-4.2.1-r2.
I started to explicitly remerge the kde-3.1 packages (not -r1 or -r2).
I ran into the same problem as bug 15245.
I unmerged libxml2-2.5.2.
I explicitly emerged libxml2-2.4.30.
I continued emerging the rest of the kde-3.1 packages.

SUCCESS! KDE now works as expected.

All the latest ebuilds of the kde packages are installed.

ALL of the borkedness on 'dragon' apears to be eliminated. It looks very much like the latest version of libxmsl2 is the culprit.

I'm going to unmerge libxml2 on my machine at work and check it's results tomorrow.

In the meantime, you may want to consider combining 15245 and 15213 (mark one as a dup of the other) even though they describe different but apparently related problems with a possible common cause. Depending on my results tomorrow with machine 'work', I'll be able to tell you for sure if these two bug reports are for the same bug.

Not that I did _not_ remerge QT.
Comment 8 Guy 2003-02-12 11:14:41 UTC
Machine 'work' had kde unmerged as above.
xfree (@2.4.99.4) was left alone.
libxml2-2.5.1 was explicitly emerged.
kde-3.1 was re-emerged.

Everything works as expected. All the borkedness with both 'dragon' and 'work' had to do with libxml2-2.5.2.

This bug can be closed.
Comment 9 Seemant Kulleen (RETIRED) gentoo-dev 2003-02-12 11:21:31 UTC
ok, closing because libxml2's update was the culprit.