kopete-kde4 crashes when connecting to some Jabber servers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE Network |
Invalid
|
High
|
|||
kdenetwork (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
kopete-kde4 crashes when connecting to some Jabber servers (mostly feature-rich ejabberd) but works fine with others (ascetic jabberd2)
Harald Sitter (apachelogger) wrote : | #1 |
Changed in kdenetwork-kde4: | |
status: | New → Incomplete |
Sergei A. Beilin (sbeilin) wrote : | #2 |
1) jabber.ru is an example. I can use Psi or older Kopete to connect to, but not the latest Kopete. jabber.org now works fine, but friends complain that Google's XMPP server also gets Kopete down (did not test)
2) The last lines to stderr of crashing Kopete are:
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x633c58
QImage::scaled: Image is a null image
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x63caf1
QImage::scaled: Image is a null image
kopete(7646) Kopete:
KCrash: crashing... crashRecursionC
KCrash: Application Name = kopete path = <unknown> pid = 7646
Unable to start Dr. Konqi
That'all. (Yes, I have kdenetwork-dbg-kde4 installed)
In KDE Bug Tracking System #157316, Arnaud DELCASSE (delcasse) wrote : | #23 |
Version: (using Devel)
Installed from: Compiled sources
Compiler: gcc
OS: Linux
When I want to connect to a Jabber account through system tray's icon, Kopete crashes. It happens only with 1 of my Jabber accounts (the one which I deleted a MSN transport in Kopete accounts list).
I'm using Archlinux's "KDEmod" 4.0.1 version of KDE, with Kopete version 0.50.1
Here is the backtrace :
(no debugging symbols found)
Using host libthread_db library "/lib/libthread
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5ae16d0 (LWP 12561)]
[New Thread 0xb2adcb90 (LWP 12573)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging sym...
In KDE Bug Tracking System #157316, Arnaud DELCASSE (delcasse) wrote : | #24 |
In fact, it crashes every time I try to connect to this account, not only when I'm using system tray
Gary (pento) wrote : | #3 |
It dies for me when connecting to the Google Talk servers. I get the following error to stderr, but only if the contact list is open:
KCrash: crashing... crashRecursionC
KCrash: Application Name = kopete path = <unknown> pid = 14485
Unable to start Dr. Konqi
If the contact list is closed, I just get:
Unable to start Dr. Konqi
I am using kdenetwork-
In KDE Bug Tracking System #157316, protoman (protomank) wrote : | #25 |
Me too. I have a MSN and ICQ transport in my gtalk accound and kopete in kde4 simply crashes every time.
Terence Simpson (tsimpson) wrote : | #4 |
Are you still experiencing this problem with current KDE4 packages?
Gary (pento) wrote : | #5 |
Unfortunately I can't test. I downgraded back to Gutsy/KDE3, Hardy/KDE4 was missing a bunch of stuff that I needed.
Stephan Rügamer (sruegamer) wrote : | #6 |
Hi,
I confirm this bug. You can try to use my jabber server (jabberme.
If you need assistance, please catch me on irc :)
Regards,
\sh
Changed in kdenetwork-kde4: | |
importance: | Undecided → Critical |
status: | Incomplete → Confirmed |
Dennis Nienhüser (earthwings) wrote : | #7 |
I just tried with jabberme.net and it connected fine, Kopete 0.50.1, KDE 4.0.3. Are you still experiencing the problem?
Stephan Rügamer (sruegamer) wrote : | #8 |
Now it's getting even worse...
X + computer freezes completly after logging in.
Ok, I tried it with an empty account, this works as expected.
But having a really full account with many jabber buddies+icq transport buddies it's somehow not working.
Harald Sitter (apachelogger) wrote : | #9 |
Someone please search/create a report on http://
Thank you.
In KDE Bug Tracking System #157316, brot (schnitzelkuchen) wrote : | #26 |
I can confirm this bug with kopete svn trunk r835161, allthough it only crashes once when adding the jabber account with the transports, after that crash everything works like it should (except if you dare to remove that account again ;) )
kopete(
ASSERT: "identityItemHa
kopete(17568) ChatWindowStyle
kopete(17568) ChatWindowStyle
kopete(
"[
0: /usr/kde/
1: /usr/kde/
2: /usr/kde/
3: /usr/kde/
4: /lib64/
5: /usr/lib64/
6: /usr/lib64/
7: /usr/kde/
8: /usr/kde/
9: /usr/lib64/
10: /usr/kde/
11: /usr/kde/
12: /usr/kde/
13: /usr/kde/
14: /usr/lib64/
15: /usr/kde/
16: /usr/kde/
17: /usr/kde/
18: /usr/kde/
19: /usr/kde/
20: /usr/kde/
21: /usr/lib64/
22: /usr/kde/
23: /usr/lib64/
24: /usr/lib64/
25: /usr/lib64/
26: /usr/lib64/
In KDE Bug Tracking System #157316, Mlroper (mlroper) wrote : | #27 |
I am experiencing this issue, though without any MSN account complications.
Kopete crashes shortly after connecting to a Jabber server (in this case, the Jabber server is powered by Openfire 3.5.1).
After connecting to the Jabber account, the contacts pane is momentarily populated with Jabber contacts before the application immediately crashes.
Here is the backtrace (redundant lines replaced with "..."):
(no debugging symbols found)
...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5a9f720 (LWP 7535)]
[New Thread 0xb2f27b90 (LWP 7539)]
(no debugging symbols found)
...
(no debugging symbols found)
[KCrash handler]
#6 0xb652c9bc in memcpy () from /lib/tls/
#7 0xb7ca21da in ?? () from /usr/lib/
#8 0xb7c8e269 in KNetwork:
from /usr/lib/
#9 0xb7c8e04b in KNetwork:
from /usr/lib/
#10 0xb7e884f9 in QMetaObject:
#11 0xb7e88bc2 in QMetaObject:
#12 0xb7ec5ca3 in QSocketNotifier
#13 0xb7e8eb8f in QSocketNotifier
#14 0xb6e26c0c in QApplicationPri
from /usr/lib/
#15 0xb6e2b7a9 in QApplication:
#16 0xb79acc93 in KApplication:
#17 0xb7e736a9 in QCoreApplicatio
from /usr/lib/
#18 0xb7e9ee23 in ?? () from /usr/lib/
#19 0xb641bbf8 in g_main_
#20 0xb641ee5e in ?? () from /usr/lib/
#21 0xb641f3ac in g_main_
#22 0xb7e9ef98 in QEventDispatche
from /usr/lib/
#23 0xb6eba1b5 in ?? () from /usr/lib/
#24 0xb7e7292d in QEventLoop:
#25 0xb7e72abd in QEventLoop::exec () from /usr/lib/
#26 0xb7e74d3d in QCoreApplicatio
#27 0xb6e26567 in QApplication::exec () from /usr/lib/
#28 0x0808732b in ?? ()
#29 0xb64cf450 in __libc_start_main () from /lib/tls/
#30 0x080637a1 in _start ()
#0 0xb7f7e410 in __kernel_vsyscall ()
mehturt (mehturt) wrote : | #10 |
I have similar problem with our company jabber server..
The console error is:
KCrash: crashing... crashRecursionC
KCrash: Application Name = kopete path = <unknown> pid = 25278
kdeinit4: Got EXEC_NEW '/usr/lib/
kdeinit4: preparing to launch /usr/lib/
kwin: X Error (error: <unknown>
The backtrace is attached.
mehturt (mehturt) wrote : | #11 |
I added my backtrace to this bug, http://
In KDE Bug Tracking System #157316, mehturt (mehturt) wrote : | #28 |
I'm seeing similar problem when connecting to OpenFire 3.5.2 jabber server.
I'm using kopete 4:4.1.0-
I'll attach the backtrace.
I can provide more info if necessary.
In KDE Bug Tracking System #157316, mehturt (mehturt) wrote : | #29 |
Created attachment 26489
backtrace
In KDE Bug Tracking System #157316, James Lamb (admin-oranged) wrote : | #30 |
Created attachment 26493
kopete kcrash debug output
Attached is my backtrace as I have been having the same issues when connecting
to jabber on KDE 4.0 and 4.1
scor (omgbebebe) wrote : | #12 |
Hi!
I confirm this bug to. I use kubuntu hardy and kde 4.1. When i reinstall qca-tls package, crashes gone and now kopete work well. I don`t know may it help or not, btw i happy now:))
Changed in kdenetwork: | |
status: | New → Unknown |
Changed in kdenetwork: | |
status: | Unknown → New |
Kevin Christmas (kachristmas) wrote : | #13 |
Crashes when connecting to an Openfire (open source) jabber server over SSL.
Application: Kopete (kopete), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fe07138b780 (LWP 7092)]
[New Thread 0x43379950 (LWP 7097)]
[New Thread 0x4102e950 (LWP 7093)]
[KCrash handler]
#5 0x00007fe06d050f82 in memcpy () from /lib/libc.so.6
#6 0x00007fe06fb0eb51 in KNetwork:
this=0x1103750, dev=0x117be60, len=-1)
at /build/
#7 0x00007fe06fafe408 in KNetwork:
this=0x1136d00)
at /build/
#8 0x00007fe06fafe292 in KNetwork:
this=0x1136d00, _c=QMetaObject:
_a=<value optimized out>)
at /build/
#9 0x00007fe06f46a8b6 in QMetaObject:
from_
at kernel/
#10 0x00007fe06f4a3fae in QSocketNotifier
at .moc/release-
#11 0x00007fe06f470b5f in QSocketNotifier
e=0x7fff793
#12 0x00007fe06dd34acf in QApplicationPri
receiver=
#13 0x00007fe06dd36c85 in QApplication:
receiver=
#14 0x00007fe06ffecea1 in KApplication:
receiver=
at /build/
#15 0x00007fe06f4566b9 in QCoreApplicatio
this=
at kernel/
#16 0x00007fe06f47f85a in socketNotifierS
at ../../include/
#17 0x00007fe06a0cb02a in IA__g_main_
at /home/kchristma
#18 0x00007fe06a0cdfe5 in g_main_
dispatch=1, self=<value optimized out>)
at /home/kchristma
#19 0x00007fe06a0ce507 in IA__g_main_
may_block=1) at /home/kchristma
#20 0x00007fe06f47f9df in QEventDispatche
flags=<value optimized out>) at kernel/
#21 0x00007fe06ddbe20f in QGuiEventDispat
this=0x1296dba, flags=<value optimized out>)
at kernel/
#22 0x00007fe06f455b35 in QEventLoop:
In KDE Bug Tracking System #157316, Kevin Christmas (kachristmas) wrote : | #31 |
I can confirm that this is effecting me when I try to connect to an openfire jabber server
Application: Kopete (kopete), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fe07138b780 (LWP 7092)]
[New Thread 0x43379950 (LWP 7097)]
[New Thread 0x4102e950 (LWP 7093)]
[KCrash handler]
#5 0x00007fe06d050f82 in memcpy () from /lib/libc.so.6
#6 0x00007fe06fb0eb51 in KNetwork:
this=0x1103750, dev=0x117be60, len=-1)
at /build/
#7 0x00007fe06fafe408 in KNetwork:
this=0x1136d00)
at /build/
#8 0x00007fe06fafe292 in KNetwork:
this=0x1136d00, _c=QMetaObject:
_a=<value optimized out>)
at /build/
#9 0x00007fe06f46a8b6 in QMetaObject:
from_
at kernel/
#10 0x00007fe06f4a3fae in QSocketNotifier
at .moc/release-
#11 0x00007fe06f470b5f in QSocketNotifier
e=0x7fff793
#12 0x00007fe06dd34acf in QApplicationPri
receiver=
#13 0x00007fe06dd36c85 in QApplication:
receiver=
#14 0x00007fe06ffecea1 in KApplication:
receiver=
at /build/
#15 0x00007fe06f4566b9 in QCoreApplicatio
this=
at kernel/
#16 0x00007fe06f47f85a in socketNotifierS
at ../../include/
#17 0x00007fe06a0cb02a in IA__g_main_
at /home/kchristma
#18 0x00007fe06a0cdfe5 in g_main_
dispatch=1, self=<value optimized out>)
at /home/kchristma
#19 0x00007fe06a0ce507 in IA__g_main_
may_block=1) at /home/kchristma
#20 0x00007fe06f47f9df in QEventDispatche
flags=<value optimized out>) at kernel/
#21 0x00007fe06ddbe20f in QGuiEventDispat
this=0x1296dba, flags=<value optimized out>)
at kernel/
#22 0x00007fe06f455b35 in QEvent...
In KDE Bug Tracking System #157316, Marcel Schaal (marcelschaal) wrote : | #32 |
*** This bug has been confirmed by popular vote. ***
Changed in kdenetwork: | |
status: | New → Confirmed |
In KDE Bug Tracking System #157316, Me-ngeefk4xayt3t4u9watah405veq (me-ngeefk4xayt3t4u9watah405veq) wrote : | #33 |
*** Bug 170374 has been marked as a duplicate of this bug. ***
Changed in kdenetwork: | |
importance: | Critical → High |
In KDE Bug Tracking System #157316, Jonathan Thomas (echidnaman-f) wrote : | #34 |
Bug 170684 is a dupe of this too.
In KDE Bug Tracking System #157316, Alan Jones (skyphyr) wrote : | #35 |
Thanks for reporting. If somebody could repro on a recent build with debug symbols and provide a new backtrace that would be very helpful.
Cheers,
Alan.
Jonathan Thomas (echidnaman) wrote : | #14 |
Is this still an issue for anybody using KDE 4.2 beta2? Upstream would like to see if this is still an issue in a more recent version of KDE.
If it is, could somebody install kdenetwork-dbg and get a new backtrace? Thanks.
Changed in kdenetwork: | |
status: | Confirmed → Incomplete |
Kevin Christmas (kachristmas) wrote : | #15 |
I'm connecting to the finicky jabber server perfectly with the version of kopete in KDE 4.2b2.
However, kopete will crash if I manually disconnect from the finicky jabber server. I thought I had the debug packages installed, but I don't. I will install them now.
mehturt (mehturt) wrote : | #16 |
I can confirm the same, connect to jabber works now, sending receiving messages is ok. Manual disconnect causes application to crash, though I don't have core file created.
The console output is:
KCrash: Application 'kopete' crashing...
sock_file=
kdeinit4: preparing to launch /usr/lib/
QWidget: Must construct a QApplication before a QPaintDevice
Kevin Christmas (kachristmas) wrote : | #17 |
mehturt, I couldn't get a backtrace on the disconnect for some reason. Could you add one to the bug I filed upstream?
https:/
Thanks.
mehturt (mehturt) wrote : | #18 |
Ok, I attached to kopete via gdb and changed the status to Offline, this is what I got:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fddea1346f0 (LWP 16546)]
0x0000000000000001 in ?? ()
(gdb) bt
#0 0x0000000000000001 in ?? ()
#1 0x00007fdde50262c5 in QMetaObject:
#2 0x00007fdde62bd424 in QAbstractSocket
#3 0x00007fdde62c0a98 in ?? () from /usr/lib/
#4 0x00007fdde62b1991 in ?? () from /usr/lib/
#5 0x00007fdde42ecc3d in QApplicationPri
#6 0x00007fdde42f49ba in QApplication:
#7 0x00007fdde5bf4f0b in KApplication:
#8 0x00007fdde501dd61 in QCoreApplicatio
#9 0x00007fdde50463d9 in ?? () from /usr/lib/
#10 0x00007fdddf98fd3b in g_main_
#11 0x00007fdddf99350d in ?? () from /usr/lib/
#12 0x00007fdddf9936cb in g_main_
#13 0x00007fdde504615f in QEventDispatche
#14 0x00007fdde437ea6f in ?? () from /usr/lib/
#15 0x00007fdde501c682 in QEventLoop:
#16 0x00007fdde501c80d in QEventLoop::exec () from /usr/lib/
#17 0x00007fdde501ecbd in QCoreApplicatio
#18 0x0000000000449f8c in main (argc=1, argv=0x7ffff217
Is that sufficient?
Kevin Christmas (kachristmas) wrote : | #19 |
Yes, that should be fine. Thank you. I'll copy that to the bug I filed upstream.
In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote : | #36 |
I am seeing this bug in Kubuntu 8.10, using Kopete 0.60.3, using KDE 4.1.3. I'm seeing approximately the same traceback as has previously been reported, and only when connecting to my companys Openfire server, with 100+ contacts on it. My connection to jabber.org seems to work without issue.
I will try to download and compile a kopete to give a more complete backtrace. Thank you.
In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote : | #37 |
Created attachment 30059
Crash log from kopete crash (9-Jan-2009)
Okay. I rebuilt from trunk today, and get the following crash when I try to connect to the corporate OpenFire 3.5.1 server. As earlier mentioned, there are 120 or more contacts on my contact list (preconfigured for all in the company) and while they seem to be loading into the buddy list window, the app then crashes. Attached is the save from the KDE crash handler.
In KDE Bug Tracking System #157316, Kevin Christmas (kachristmas) wrote : | #38 |
My office uses Openfire 3.4.5. Using the Kopete Version 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)), I have NOT experienced any problems connecting to the Openfire Jabber server.
Chris Ross's experience suggests a regression or a difference in XMPP server implementations that a fix missed?
In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote : | #39 |
Perhaps. How many contacts do you have in your contact list on that jabber server, however? Other folks in this bug chain have also, like me, mentioned that they have many dozen, or even hundreds, of contacts, so I suspect that may be related.
If you're being notified of many dozens or hundreds of contacts being available as well, then your conclusion is likely the correct one.
In KDE Bug Tracking System #157316, Kevin Christmas (kachristmas) wrote : | #40 |
There are 74 out of 122 people online and connected to my company's Jabber server. So yeah, I have more than a few dozen on my contact list.
Changed in kdenetwork: | |
status: | Incomplete → Triaged |
In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote : | #41 |
Has there been any headway on this? I'd hate to have to install all of the additional GNOME crud to get Pidgin working, but may need to do so to be able to chatter with my coworkers.
Alan, have you had a chance to look into this, and is the crash log I provided sufficient?
Thanks.
In KDE Bug Tracking System #157316, mehturt (mehturt) wrote : | #42 |
<offtopic>you don't need GNOME to get Pidgin running, just GTK</offtopic>
In KDE Bug Tracking System #157316, Kevin Christmas (kachristmas) wrote : | #43 |
I upgraded to the new RC1 yesterday. Using the Kopete KDE 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)), I'm still not experiencing any problems establishing a connection to my company's OpenFire jabber server.
In KDE Bug Tracking System #157316, mehturt (mehturt) wrote : | #44 |
I can confirm that. Using Kopete 0.60.82 and KDE 4.1.96 it works for me too.
In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote : | #45 |
Interesting. I just tried to run a trunk build from today (Kopete Version 0.70.50, using the installed KDE 4.1.3) and the first time I connected, I saw most of the contact information load, then it crashed. Or at least, it exited (was running --nofork). I tried again, and it seemed to cope. It connected, then disconnected for some reason but remained running. I was able to reconnect, and now it shows all 91/199 contacts for that server.
:-/ I'm not sure about this. I hate inconsistent bugs.
In KDE Bug Tracking System #157316, hydralien (hydralien) wrote : | #46 |
Issuing the same on Ubuntu 8.10 in Kopete version 4:4.1.3 (from what ubuntu says). I'm using SSL on jabber connection (not sure if that matters) and my contact list also contains >100 records.
Are there any updates/status for this bug?
Here's crash report:
Application: Kopete (kopete), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb59016c0 (LWP 29189)]
[New Thread 0xb30afb90 (LWP 29190)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols...
Changed in kdenetwork: | |
importance: | High → Medium |
capi /. (barraponto) wrote : | #20 |
i'm using jaunty kopete 0.70.2 on kde 4.2.2 and it both connects and disconnects from gtalk servers...
maybe this bug was fixed.
tags: | added: kopete |
aurelieng (aurelien-grosdidier) wrote : | #21 |
I'm using Jaunty, Kopete 0.70.2 and KDE 4.2.3, and it keeps connecting/
In KDE Bug Tracking System #157316, Dario Andres (andresbajotierra) wrote : | #47 |
Is this still valid with an updated KDE version ? Thanks
In KDE Bug Tracking System #157316, Cross+kde (cross+kde) wrote : | #48 |
I no longer see this bug in Kubuntu 9.10, which [I believe] is using KDE 4.2.2. Whatever the "norm" in Kubuntu 9.10. "Works for me".
In KDE Bug Tracking System #157316, Dario Andres (andresbajotierra) wrote : | #49 |
Thanks, let's wait for the reporter reply.
Changed in kdenetwork: | |
status: | Confirmed → Unknown |
Jonathan Thomas (echidnaman) wrote : | #22 |
This should work in KDE 4.2.2, and since there haven't been any reports of crashes for a long time I'm closing this bug.
Changed in kdenetwork (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in kdenetwork: | |
importance: | Unknown → High |
status: | Unknown → Incomplete |
In KDE Bug Tracking System #157316, Andrew-crouthamel (andrew-crouthamel) wrote : | #50 |
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.
For more information about our bug triaging procedures please read the wiki located here: https:/
If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.
Thank you for helping us make KDE software even better for everyone!
In KDE Bug Tracking System #157316, Andrew-crouthamel (andrew-crouthamel) wrote : | #51 |
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.
For more information about our bug triaging procedures please read the
wiki located here:
https:/
Thank you for helping us make KDE software even better for everyone!
Changed in kdenetwork: | |
status: | Incomplete → Invalid |
Got any example servers to try?
Also try installing kdenetwork-dbg-kde4 and check for useful output when starting kopete from konsole.