Description of problem: Since upgrading to Fedora 12 I can no longer connect to an Openfire Jabber server (v3.6.4) with my account. I can successfully connect with pidgin and empathy to the same account. I also have a Fedora 11 laptop with all recent updates and that still works fine. Incidentally this is also running Kopete 0.80.2 on KDE 4.3.4 I get these errors in my .xsession-errors when connecting kdeinit4: preparing to launch /usr/bin/kopete Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. JingleSessionManager::JingleSessionManager created. Creating the PushJingleSession task.... Object::connect: No such signal XMPP::JingleSessionManager::incomingSession() After a while Kopete gives an error saying it could not establish a TLS session Version-Release number of selected component (if applicable): How reproducible: Always fails to connect Steps to Reproduce: 1.Add a Jabber account to kopete to an openfire jabber server requiring SSL 2.Change your status to online 3. After a while an error appears saying could not establish a TLS session Actual results: An error appears saying could not establish a TLS session Expected results: Expected to be online Additional info: I have noticed that PSI (which is another QT based client) also has a smilair issue. It too cannot connect to the same jabber server. Pidgin works fine, as do other non QT based clients I have installed: qca2-devel-2.0.2-2.fc12.i686 qca-ossl-2.0.0-0.8.beta3.fc12.i686 qca-1.0-13.fc12.i686 qca-tls-1.0-18.fc12.i686 qca2-2.0.2-2.fc12.i686 qca-gnupg-2.0.0-0.4.beta3.fc12.i686
Probably best to report this one upstream to bugs.kde.org please.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I can confirm this bug remains in Fedora 14. Under the same Jabber account described above, the problem remains.
I can confirm i've the same problem in Fedora 14
I can confirm that it doesn't work for me neither. Fedora 15 64bit. I will bug it upstream
Is is already done: https://bugs.kde.org/show_bug.cgi?id=221533
Fun, https://bugs.kde.org/show_bug.cgi?id=221533#c16 seems to imply this to be some sort of openssl/qca-ossl issue
openssl-1.0.1-0.1.beta2.fc17.x86_64 just broke kopete on rawhide, reverting to openssl.x86_64 0:1.0.0g-1.fc17 makes kopete work again.
There seem to be multiple issues that have just started recently. In my case, I see a connection come and go as I run kopete by monitoring the status on openfire. The problem is kopete crashes with a file lock issue. I've tried downgrading to the previous nfs-utils which was in a time frame that worked on the client side. I'll try the server side when I get a chance. I get the following crash report. BUG: unable to handle kernel paging request at ffffffffffffffb8 IP: [<ffffffffa08520e9>] nfs_have_delegation+0x9/0x40 [nfs] PGD 1c07067 PUD 1c08067 PMD 0 Oops: 0000 [#1] SMP CPU 1 Modules linked in: fuse ip6table_filter ip6_tables ipt_MASQUERADE bridge stp llc nfs lockd fscache auth_rpcgss nfs_acl ebt_snat ebtable_nat ebtables ebt_dnat nf_nat_pptp nf_nat_amanda nf_nat_tftp nf_nat_h323 nf_nat_proto_udplite nf_nat_sip nf_nat_ftp nf_nat_snmp_basic nf_nat_proto_gre nf_nat_irc nf_nat_proto_sctp libcrc32c nf_nat_proto_dccp act_nat nf_conntrack_proto_dccp nf_conntrack_netbios_ns nf_conntrack_tftp nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre xt_conntrack ts_kmp nf_conntrack_amanda nf_conntrack_ftp nf_conntrack_snmp nf_conntrack_broadcast nf_conntrack_sip nf_conntrack_netlink nf_conntrack_h323 nf_conntrack_irc nf_conntrack_sane nf_conntrack_proto_udplite ip_set nfnetlink ipt_LOG xt_state xt_multiport iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 xt_CHECKSUM iptable_mangle tpm_bios joydev vhost_net macvtap macvlan tun virtio_net kvm_amd kvm snd_hda_codec_hdmi snd_hda_codec_realtek ppdev microcode serio_raw fglrx(PO edac_core edac_mce_amd k10temp fam15h_power parport_pc parport snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device r8169 mii snd_pcm snd_timer snd soundcore forcedeth snd_page_alloc i2c_nforce2 uinput binfmt_misc sunrpc ata_generic pata_acpi sata_nv radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan] ... [<ffffffffa083ffa1>] nfs4_handle_exception+0x241/0x3a0 [nfs] [<ffffffffa0842b9c>] nfs4_proc_lock+0xec/0x440 [nfs] [<ffffffffa082318d>] do_setlk+0xed/0x110 [nfs] [<ffffffffa0823239>] nfs_flock+0x89/0xe0 [nfs] [<ffffffff811cbf83>] sys_flock+0x113/0x1c0 [<ffffffff815fc5a9>] system_call_fastpath+0x16/0x1b Code: fd ff e9 40 fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 66 66 66 66 90 f0 80 4f 48 04 5d c3 55 48 89 e5 66 66 66 66 90 <48> 8b 57 b8 31 c0 48 85 d2 74 0c 8b 4a 30 83 e6 03 21 f1 39 f1 RIP [<ffffffffa08520e9>] nfs_have_delegation+0x9/0x40 [nfs] Although tainted, it also happens on an nvidia tainted kernel. Not sure that the video driver could mess with NFS, but I suppose anything is possible.
kernel-3.3.4-3.fc16.x86_64 with upstream NFS patches fixes this issue for kopete. Thanks!
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping