Kopete-0.7.4 emerges fine, will start up, but see this error if start in console: ******************************** bash-2.05b$ kopete QFile::open: No file name specified bash-2.05b$ kio (KMimeType): WARNING: KServiceType::offers : servicetype Kopete/Plugin not found kio (KMimeType): WARNING: KServiceType::offers : servicetype Kopete/Plugin not found kio (KMimeType): WARNING: KServiceType::offers : servicetype Kopete/Plugin not found kio (KMimeType): WARNING: KServiceType::offers : servicetype Kopete/Plugin not found ******************************** If right click on the kicker panel icon (which is blank paper with ?) and select 'Configure Kopete' window pops up, but it doesn't know where the Plugins are, so nothing works. Because there are no plugins to choose from, there are no services avail to pick, add account wizard doesn't work correctly,... only Appearance & Behavior seem to have anything that works. Have tried this several times, cleaning old emerge out before retrying. The plugins are in /usr/lib/kde3, but not seen by app. Reproducible: Always Steps to Reproduce: 1. Emerge kopete 2. Start kopete from console or make menu entry. 3. Get icon in panel, right click to configure, no plugins seen. Also see message in console. Actual Results: Cannot use kopete, is very modular program and without plugins it will not show any services available or add/use accounts. Expected Results: To be able to configure kopete to add an account, select service want to use and use it's IM features. #emerge info Portage 2.0.49-r20 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.4.20-gentoo-r6) ================================================================= System uname: 2.4.20-gentoo-r6 i686 AMD Athlon(tm) XP 2400+ Gentoo Base System version 1.4.3.10p1 distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer" 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/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="3dnow X aalib apm arts avi berkdb bonobo cdr crypt cups dvd encode esd flash foomaticdb gdbm gif gnome gphoto2 gpm gtk gtk2 gtkhtml guile imlib java jpeg kde libg++ libwww mad mikmod mmx motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png postgres python qt quicktime readline scanner sdl slang spell sse ssl svga tcpd tetex tiff truetype x86 xml2 xmms xv zlib" Have tried several things like: 1) remerge 'kdenetwork' 2) add to ~/.kderc : [Directories] prefixes=/usr/lib/kde3 3) Add /usr/lib/kde3 to env.d Compared my kopete build to another system where working on problem for 'enter' key shut app down and they are the same as can tell (except for the user files). That ended up being another bug, cause no shortcut said to quit if hit enter, removed a few of the shortcuts with multiple keys used with enter and fixed problem. Gaim works fine on this system.
Got it working now and not sure how. Added to /usr/portage/net-im/kopete-0.7.4.ebuild this: ********************** src_compile() { ./configure \ --enable-debug=yes } ********************* To see if produced a more verbose output to troubleshoot. Rebuilt the digest, used the same tarball that portage fetched earlier. Rebooted cause removing a harddrive (just adding this info because did it). Started kopete in terminal and this was output: ******************** bash-2.05b$ kopete kopete: using X11 MIT Screensaver extension bash-2.05b$ kopete: [KopetePlugin* LibraryLoader::loadPlugin(const QString&)] Successfully loaded plugin 'spellcheck' kopete: [KopetePlugin* LibraryLoader::loadPlugin(const QString&)] Successfully loaded plugin 'aim' kopete: [KopetePlugin* LibraryLoader::loadPlugin(const QString&)] Successfully loaded plugin 'history' kopete: [KopetePlugin* LibraryLoader::loadPlugin(const QString&)] Successfully loaded plugin 'texteffect' ***************************** Get the proper icon now in kicker panel, started configure kopete and all the plugins are seen. Able to make it sort of work now. Don't see how it works now after what did. Unable to connect to anyone that is currently online though. Have seen others with this plugins not seen issue, so don't know if want to close this or not.
Contacts working now. Had to delete them all and start over and remove the ~/.kde apps/kopete contacts file and start over cause didn't want to save them when changed names and alias to get it working. Don't know if want to close this or not cause still think it might be an issue, and not sure why after not emerging anything else,.... and adding the line to ebuild started working. ????
Tested to make sure, unmerged kopete and put ebuild back to normal and emerged again. Kopete nogo again: Could not find plugins. Put the debug enable back, this time FULL. Seems to work even better now. Plugins are seen again. Contacts work, but only when you add them manually. I was contacted by someone as soon as got it up and only had one contact (not the same person), he was sending messages, but couldn't talk back. Had to add him manually to talk to him, even though the window popped up to talk to him. Seg faults also sometimes when close it out on the kicker panel. So disregard previous end of post that not sure want to close this out or not. It is definately a bug. Only sees plug-ins when enable debug in the ebuild for some off the wall reason and works better when enable full debug. (had trouble more trouble with contacts when just enabled debug with yes). I know this sounds strange, but it is what is happening. Have not tested if this behaviour changes when don't open in console yet. Wouldn't surprise me. This has got to be the buggyist software put on this computer yet that can remember. Going to look in /var/log/portage and see if can find a difference during the build process that is noticable between the two.
Okay, now know why it works, not sure why debug enabled changes the plugin locations though. Hope this prints out correctly (if not can cleanup) First is the checks, then at the end of the build process you can see that it put the plugins in different location for the debug enabled setup. **************************************************** No Debug DEBUG FULL configure: WARNING: If you wanted to set the --build type, do < If a cross compiler is detected then cross compile mode w < ................ checking for i686-pc-linux-gnu-strip... no < checking for strip... strip ................ checking for i686-pc-linux-gnu-gcc... gcc | checking for gcc... gcc ................ checking dependency style of gcc... none | checking dependency style of gcc... gcc3 ................ > checking whether g++ supports -fno-builtin... yes > checking whether g++ supports -Woverloaded-virtual... yes ................ checking for BSD-compatible nm... nm | checking for BSD-compatible nm... /usr/bin/nm -B ................ checking command to parse nm output from gcc object... ok | checking command to parse /usr/bin/nm -B output from gcc obje ................ checking for i686-pc-linux-gnu-ranlib... no < ................ checking for i686-pc-linux-gnu-strip... strip | checking for strip... strip ................ checking for Xinerama... yes | checking for Xinerama... no Good - your configure finished. Start make now Good - your configure finished. Start make now Think found the reason it works now. **************************************************** make[2]: Leaving directory `/var/tmp/portage/kopete-0.7.4/wor make[2]: Leaving directory `/var/tmp/portage/kopete-0.7.4/wor make[1]: Leaving directory `/var/tmp/portage/kopete-0.7.4/wor make[1]: Leaving directory `/var/tmp/portage/kopete-0.7.4/wor man: man: prepallstrip: prepallstrip: strip: strip: strip: strip: usr/bin/kopete | usr/kde/3.1/bin/kopete usr/bin/kconf_update_bin/kopete-account-kconf_update | usr/kde/3.1/bin/kconf_update_bin/kopete-account-kconf_upda usr/lib/kde3/kopete_highlight.so | usr/kde/3.1/lib/kde3/kopete_highlight.so usr/lib/kde3/libkrichtexteditpart.so | usr/kde/3.1/lib/kde3/libkrichtexteditpart.so usr/lib/kde3/kopete_aim.so | usr/kde/3.1/lib/kde3/kopete_aim.so usr/lib/kde3/kopete_yahoo.so | usr/kde/3.1/lib/kde3/kopete_yahoo.so usr/lib/kde3/kopete_wp.so | usr/kde/3.1/lib/kde3/kopete_wp.so usr/lib/kde3/kopete_nowlistening.so | usr/kde/3.1/lib/kde3/kopete_nowlistening.so usr/lib/kde3/kopete_autoreplace.so | usr/kde/3.1/lib/kde3/kopete_autoreplace.so usr/lib/kde3/kopete_icq.so | usr/kde/3.1/lib/kde3/kopete_icq.so usr/lib/kde3/kopete_irc.so | usr/kde/3.1/lib/kde3/kopete_irc.so usr/lib/kde3/kopete_msn.so | usr/kde/3.1/lib/kde3/kopete_msn.so usr/lib/kde3/kopete_jabber.so | usr/kde/3.1/lib/kde3/kopete_jabber.so usr/lib/kde3/kopete_cryptography.so | usr/kde/3.1/lib/kde3/kopete_cryptography.so usr/lib/kde3/kopete_contactnotes.so | usr/kde/3.1/lib/kde3/kopete_contactnotes.so usr/lib/kde3/kopete_sms.so | usr/kde/3.1/lib/kde3/kopete_sms.so usr/lib/kde3/kopete_translator.so | usr/kde/3.1/lib/kde3/kopete_translator.so usr/lib/kde3/kopete_webpresence.so | usr/kde/3.1/lib/kde3/kopete_webpresence.so usr/lib/kde3/kopete_connectionstatus.so | usr/kde/3.1/lib/kde3/kopete_connectionstatus.so usr/lib/kde3/kopete_spellcheck.so | usr/kde/3.1/lib/kde3/kopete_spellcheck.so usr/lib/kde3/kopete_texteffect.so | usr/kde/3.1/lib/kde3/kopete_texteffect.so usr/lib/kde3/kopete_history.so | usr/kde/3.1/lib/kde3/kopete_history.so usr/lib/libkopete.so.1.0.0 | usr/kde/3.1/lib/libkopete.so.1.0.0 usr/lib/libkopete_oscar.so.1.0.0 | usr/kde/3.1/lib/libkopete_oscar.so.1.0.0 making executable: /usr/lib/libkopete.so.1.0.0 < making executable: /usr/lib/libkopete_oscar.so.1.0.0 < >>> Completed installing into /var/tmp/portage/kopete-0.7.4/i >>> Completed installing into /var/tmp/portage/kopete-0.7.4/i preinst preinst base base kde-functions kde-functions kde kde postinst postinst base base kde-functions kde-functions kde kde
it installs in /usr/lib/kde3/ here as well, but it works
Well, installs and knows location on KDE 3.2 for plugins, but still doesn't work correctly. Gaim works perfect. Have two aliases. Can log in on Gaim alias, send a message to kopete alias and it will ask if want to view or ignore. Choose view, message from Gaim comes up fine. Try to talk back and says that the contact isn't online. Not online but just viewed the message from them, right. Same thing with all my other contacts, they can IM me, get the message, type something back and says they aren't online. Tried starting with --nofork option, but not seeing anything in console to give a clue? Tried removing/recreating the contacts, removing ~/*/.kde kopete files, reinstalling kdenetwork (talking about kde3.2), posting on kde forums (pretty much just get that kopete is pretty new,....) Don't have previous kde versions installed only kde 3.2 now, so can't be a conflict. Mention this cause 3.2 doesn't play nice with previous kde versions like 3.1.5 at least.
Not sure, but you probably just want to close this one, since other versions have came out and put the plugins in the right place. Still see some with plugins in the wrong place in the forum, but that could still be from a previous build like this one. The Kopete that comes with KDE3.2 (version 0.8.0) works. My other issue was that it shows all contacts offline for Aim Protocol. Seems that it isn't sending the contactlist correctly to the server, but it does retrieve it correctly. I 'fixed' it by setting up Gaim with the same login.oscar.aol.com and port 5190, kopete uses. Gaim correctly sends the contactlist to the server. Did that for each account. Then start Kopete and it will then correctly download the contactlist and show contacts online correctly. I have already filed a bug report with Kopete people and they are working on it. They have added it as a wishlist though???? Weird.
see above comment - this should all be happy now using kopete in kdenetwork.
