Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 41568 - kopete can no longer load any protocols after upgrade to kde 3.2
Summary: kopete can no longer load any protocols after upgrade to kde 3.2
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High blocker (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-14 10:31 UTC by Dave Andruczyk
Modified: 2004-03-19 02:27 UTC (History)
1 user (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 Dave Andruczyk 2004-02-14 10:31:53 UTC
After emerging kde 3.2 and re-logging in to a kde3.2 session, kopete no longer works.
my accounts that had been there in kde 3.1.5 are now gone,  attempting to recreate them results in a dialog box " Impossible to load the protocol 'AIM' "(same theing for every protocol supported vi kopete..)  (kopete is version 0.7.5)

unmerging and remerging kopete has no effect. 

Reproducible: Always
Steps to Reproduce:
1. emerge kde-3.2
2. login to a kde 3.2 session
3. attempt to use kopete,  it can no longer load plugins, or function

Actual Results:  
kopete can no longer load an protocols to logging onto any IM service 

Expected Results:  
it should have worked like it did under kde 3.1.5 

Gentoo Base System version 1.4.3.13 
Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.24) 
================================================================= 
System uname: 2.4.24 i686 AMD Athlon(tm) MP 
distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disable 
d] 
Autoconf: sys-devel/autoconf-2.58 
Automake: sys-devel/automake-1.7.7 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-mcpu=athlon-mp -O2 -pipe" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1 
/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/confi 
g /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/ 
bind /var/qmail/control" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" 
CXXFLAGS="-mcpu=athlon-mp -O2 -pipe" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="autoaddcvs ccache sandbox" 
GENTOO_MIRRORS="http://gentoo.mirrors.pair.com/ ftp://gentoo.mirrors.pair.com/ f 
tp://gentoo.noved.org/" 
MAKEOPTS=" -j4 " 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="/usr/local/portage" 
SYNC="rsync://rsync.gentoo.org/gentoo-portage" 
USE="X aalib acl alsa apm arts avi berkdb bonobo cdr crypt cups curl dga directf 
b dvb dvd encode esd foomaticdb freetype gdbm ggi gif gnome gphoto2 gpm gtk gtk2 
 gtkhtml guile imlib jack java joystick jpeg kde libg++ libwww mad mikmod mmx mo 
tif mozilla mpeg mysql nas ncurses nls oggvorbis opengl oss pam pdflib perl png  
python qt quicktime readline ruby samba scanner sdl slang spell ssl svga tcltk t 
cpd tetex truetype usb videos wmf x86 xft xml2 xmms xv zlib"
Comment 1 Chris Bainbridge (RETIRED) gentoo-dev 2004-02-17 09:03:56 UTC
I had this problem. It appears the old kopete ebuild installed libraries into /usr/lib and /usr/lib/kde3 which aren't recorded, and kopete didn't block the install of the new kde (which is supposed to happen?). Solution:

emerge unmerge kopete
rm -f /usr/lib/libkopete* /usr/lib/kde3/kopete*

now try loading kopete from kde3.2 again, this time it should find the new libraries.
Comment 2 Dave Andruczyk 2004-02-17 11:04:30 UTC
Thanks that fixed it...
Comment 3 Martin Holzer (RETIRED) gentoo-dev 2004-03-19 02:27:53 UTC
closing