kopete is supposed to have support for ICQ, MSN, etc, but eith 0.9.0 from portage (~x86), it only has jabber (when i try to add an account with the wizard) my KDE is 3.2 (plain old x86), but kopete is ~x86. Reproducible: Always Steps to Reproduce: 1. emerge kde 2. echo "net-im/kopete ~x86" >> /etc/portage/package.keywords 3. emerge kopete Actual Results: Expected Results: Portage 2.0.50-r11 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.6.7-gentoo-r11) ================================================================= System uname: 2.6.7-gentoo-r11 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs sandbox" GENTOO_MIRRORS="ftp://gentoo.mirrors.pair.com/ http://mirrors.tds.net/gentoo ftp://gentoo.netnitco.net/pub/mirrors/gentoo/source/ http://www.gigaload.org/gentoo.org/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow aalib alsa avi berkdb bzlib cdr cjk crypt curl dga dgs divx4linux doc gif gtk2 jpeg kde mad matroska mmx mng mpeg msn ncurses nls oggvorbis opengl pam pcre perl png posix postgres python quicktime readline samba sdl spell ssl tcpd tiff truetype unicode x86 xv xvid zlib"
Hmm this isn't the case for me. I see the full compliment of protocols.
It also will not launch when i try to run it from the command line in Konsole, it dies with this error: kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/hicolor/ group 48x48/stock/document not valid. kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/hicolor/ group 48x48/stock/generic not valid. kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/hicolor/ group 48x48/stock/io not valid. kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/hicolor/ group 48x48/stock/net not valid. QObject::connect: No such signal KopeteAccountManager::accountOnlineStatusChanged(KopeteAccount*,const KopeteOnlineStatus&,const KopeteOnlineStatus&) QObject::connect: (sender name: 'KopeteAccountManager') QObject::connect: (receiver name: 'KopeteSystemTray') kopete: error while loading shared libraries: kopete: undefined symbol: _ZN6Kopete2UI6Global13setSysTrayWIdEi kopete: ERROR: Communication problem with kopete, it probably crashed. and actually, if i launch most KDE apps from konsole, i get tons of those icon warnings.. maybe that's normal though.
Do you have the respective libraries present in /usr/kde/3.2/lib? /usr/kde/3.2 # ls -la *kopete* and /usr/kde/3.2/kde3 # ls -la *kopete* should show up some libraries for the IM protocols Kopete uses. Additionally this page could give you some help: http://kopete.sourceforge.net/index.php?page=installtips
I'm having the same problem. Here the only protocol which works is gadu-gadu. Using kopete from kdenetwork 3.3.0.
Do NOT post bugs here if you are using kopete from kdenetworks. This bug is for the standalone net-im/kopete package.
i checked /usr/kde/3.2 (and ./kde) and there was nothing about kopete.. my kopete stuff must be somewhere else... i am using net-im/kopete, but it looks like this could be a kopete problem, not necessarily an ebuild issue?
Dons posting pointed me to something else: Are you sure, you're excuting the correct binary (from net-im/kopete, not from kdenetwork). Check it with: # which kopete Maybe it could be a problem, that you're using kdenetwork _and_ the standalone version of kopete. It may be better to only use one of those versions.
/usr/bin/kopete i am not using kdenetworks, i have no idea what that is. all i did was emerge kde, and emerge kopete
If you emerged KDE with "emerge kde" you already have kdenetwork (the network programs of KDE) which contains kopete. AFAIK there's no need to install kopete (net-im/kopete) seperately. Or is there a specific reason?
Currently kdenetworks won't install if you have net-im/kopete installed. Perhaps I should set up the blocker the other way as well.
emerge -C kopete fixed this problem. after that i can use kopete from the menu, and it has all of the protocols listed. (i suppose that means i'm using kopete that was installed from kdenetwork) kopete should be masked as BLOCKED if you have kdenetworks installed then... An even better solution might be to have kdenetworks be a wrapper ebuild that just lists those components as RDEPENDS ?
Having kdenetwork as a wrapper is no good idea, because its the network package of KDE (which contains lots of other network programs) ;) It already includes kopete, so there is no need to install net-im/kopete if you have kdenetwork installed. net-im/kopete is ought to be installed, if you're not using KDE (or at least not using kdenetwork).
Set blocker in CVS. Should end that confusion.
