Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 103395 - kopete-3.4.1-r1 on kde-3.4.1 crashes when sendin an icq-message
Summary: kopete-3.4.1-r1 on kde-3.4.1 crashes when sendin an icq-message
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-22 17:47 UTC by Jan Thoelken
Modified: 2005-08-23 06:29 UTC (History)
0 users

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 Jan Thoelken 2005-08-22 17:47:39 UTC
kopete connecting successfully to icq/mns/aol network. sending messages to
aol/msn  is working, but sending message to icq crashes kopete



Reproducible: Always
Steps to Reproduce:
1. start kopete
2. send message to an icq-contact


Actual Results:  
kopete crashed

Expected Results:  
sending message to my icq-contact :)

console output:

libkopete: WARNING: [Kopete::Plugin*
Kopete::PluginManager::loadPluginInternal(const QString&)] Unable to find a
plugin named ''!
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QObject::connect: No such signal TypingNotifyTask::gotInfo(const QString&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'oscarclient')
QGArray::find: Index 0 out of range
QGArray::find: Index 0 out of range
QGArray::find: Index 0 out of range
KCrash: Application 'kopete' crashing...


emerge info:

Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.3.5-20050130,
glibc-2.3.5-r1, 2.6.12-gentoo-r9 i686)
=================================================================
System uname: 2.6.12-gentoo-r9 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz
Gentoo Base System version 1.6.13
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
ccache version 2.3 [enabled]
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.5
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="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium4 -pipe"
CHOST="i686-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="-O2 -march=pentium4 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distcc distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://pandemonium.tiscali.de/pub/gentoo/
http://pandemonium.tiscali.de/pub/gentoo/
http://gd.tuwien.ac.at/opsys/linux/gentoo/
ftp://gd.tuwien.ac.at/opsys/linux/gentoo/"
LANG="de_DE@euro"
LC_ALL="de_DE@euro"
LINGUAS="de"
MAKEOPTS="-j15"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.de.gentoo.org/gentoo-portage"
USE="x86 X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups dvd eds emboss
encode fam foomaticdb fortran gdbm gif gpm gstreamer gtk2 imlib ipv6 java jpeg
kde libg++ libwww mad mikmod motif mp3 mpeg ncurses nls ogg oggvorbis opengl oss
pam pcmcia pdflib perl png python qt quicktime readline samba sdl spell ssl tcpd
tiff truetype truetype-fonts type1-fonts userlocales vorbis xml2 xv zlib
linguas_de userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LDFLAGS, PORTDIR_OVERLAY
Comment 1 Jan Thoelken 2005-08-23 05:42:52 UTC
it's not a general problem. kopete crashes while sending an icq-message, when 
the icq-contact-list is very big. 
Comment 2 Gregorio Guidi (RETIRED) gentoo-dev 2005-08-23 06:29:00 UTC
Without a backtrace it's difficult to tell, but I assume it's this bug: 
https://bugs.kde.org/show_bug.cgi?id=110518 
 
I hope a fix for this problem is released for kde-3.4.x, too.