Attempting to use kopete to chat with a user who is using the offical Google Talk client will cause them to be disconnected from Google talk. It appears to be a problem with the typing notification as the user is often disconnected as you are typing. Afterwards the effect is somewhat sporadic with messages randomly getting through once the user has logged in as they are continously disconnected from your attempts to converse with them. When they have been disconnected their Jabber resource is also changed which forces a new chat window to have to be opened before further chat can be commenced. The problem has only been observed when using kopete to chat with an offical client user. Users using other clients with Google talk such as Gaim or psi appear to have no problems conversing with me when I use kopete. I am using the current stable branch KDE on amd64, kopete-3.4.1-r1 Reproducible: Always Steps to Reproduce: 1. Connect to Google Talk using Kopete 2. Open a chat with a user who is using the offical Google Talk client. 3. Start typing a message to the user. Actual Results: The user will have been disconnected from Google talk and kopete will say they have gone offline. When they come back online their Jabber Resource has changed and a new chat window must be created in order to talk to them. Expected Results: The chat should proceed as normal with both users hopefully having a long and fulfilling conversation :) Portage 2.0.51.22-r2 (default-linux/amd64/2005.0/no-multilib, gcc-3.4.4, glibc-2.3.5-r1, 2.6.12-gentoo-r9 x86_64) ================================================================= System uname: 2.6.12-gentoo-r9 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" LC_ALL="en_AU.UTF-8" LINGUAS="en_GB" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" USE="amd64 X aac alsa avi bash-completion berkdb bitmap-fonts cdr cjk crypt curl dvd dvdr eds fam flac foomaticdb fortran gif gstreamer hal ieee1394 imlib java jpeg kde kdeenablefinal lm_sensors lzw lzw-tiff mad motif mp3 ncurses nls nptl ogg oggvorbis opengl pam pdflib perl pic png python quicktime readline samba spell ssl tcpd tiff truetype truetype-fonts type1-fonts unicode usb userlocales vorbis xine xml2 xpm xv zlib linguas_en_GB userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LDFLAGS, PORTDIR_OVERLAY
This is a bug which will have to be resolved upstream, there is already an open bug report on this issue and I have provided a link below. http://bugs.kde.org/show_bug.cgi?id=111537
I am already aware of that kde bug report and posted comment #3 there. I already included the link in the bugzilla report in the url section. (In reply to comment #1) > This is a bug which will have to be resolved upstream, there is already an open > bug report on this issue and I have provided a link below. > > http://bugs.kde.org/show_bug.cgi?id=111537
Sorry I didn't spot the URL - its late here :) Until a patch is produced there is nothing we can do on this end.
