[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2023-04-16 Thread Nelson Fonseca
https://bugs.kde.org/show_bug.cgi?id=354130

Nelson Fonseca  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |---
 CC||nelsin...@gmail.com

--- Comment #37 from Nelson Fonseca  ---
Hi There,

The error persists even with the last version recently updated. The following
details of my Arch Linux version and the telepathy packages that I have
installed:

Operating System: Arch Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.11-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
Memory: 31.3 GiB of RAM
Graphics Processor: AMD BARTS
Manufacturer: Apple Inc.
Product Name: iMac12,2
System Version: 1.0

❯ yay -Qs telepathy
local/telepathy-accounts-signon 2.1-3
local/telepathy-farstream 0.6.2-7
local/telepathy-gabble 0.18.4-4 (telepathy)
local/telepathy-glib 0.24.2-2
local/telepathy-haze 0.8.1-1 (telepathy)
local/telepathy-idle 0.2.2-1 (telepathy)
local/telepathy-kde-accounts-kcm 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-approver 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-auth-handler 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-call-ui 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-common-internals 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-contact-list 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-contact-runner 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-desktop-applets 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-filetransfer-handler 22.12.3-1 (kde-applications
kde-network telepathy-kde)
local/telepathy-kde-integration-module 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-send-file 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-text-ui 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-logger 0.8.2-5
local/telepathy-logger-qt 17.09.0-1
local/telepathy-mission-control 5.16.6-2
local/telepathy-morse 0.1.0-3
local/telepathy-qt 0.9.8-2
local/telepathy-salut 0.8.1-7 (telepathy)

ERRORS:
- There was a problem while trying to connect nelsin...@kdetalk.net - An
unknown error was encountered (org.freedesktop.DBus.Error.Failed), please
report this
- There was a problem while trying to connect google8 - An unknown error was
encountered (org.freedesktop.DBus.Error.Failed), please report this

KSystemlog:
4/16/23 12:39 PMplasmashell ktp-common-internals: Current presence
changed: "offline" ""
4/16/23 12:39 PMplasmashell ktp-common-internals: Requested
presence changed: "available" ""
4/16/23 12:39 PMplasmashell ktp-common-internals: Presence
changing: true
4/16/23 12:39 PMplasmashell ktp-common-internals: Account
"gabble/jabber/google_2dim_8" enabled: true
4/16/23 12:39 PMplasmashell ktp-common-internals: Account
"gabble/jabber/ktp_2dkde_2dtalk_2dim_7" enabled: true
4/16/23 12:39 PMplasmashell ktp-models: Creating a new Account from
account: Tp::Account(0x5557b508a8c0)
4/16/23 12:39 PMplasmashell ktp-models: Account not already in
model. Create new Account from account: Tp::Account(0x5557b508a8c0)
4/16/23 12:39 PMplasmashell ktp-models: Creating a new Account from
account: Tp::Account(0x5557b834d690)
4/16/23 12:39 PMplasmashell ktp-models: Account not already in
model. Create new Account from account: Tp::Account(0x5557b834d690)


Thanks a lot for the support!

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2022-12-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=354130

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #36 from Bug Janitor Service  ---
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://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2022-12-02 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #35 from Bug Janitor Service  ---
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://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

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!

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2022-11-17 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=354130

Justin Zobel  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #34 from Justin Zobel  ---
Thank you for reporting this issue in KDE software. As it has been a while
since this issue was reported, can we please ask you to see if you can
reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when
replying. Thank you!

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2018-04-09 Thread Simon Andric
https://bugs.kde.org/show_bug.cgi?id=354130

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2017-11-29 Thread Rettich
https://bugs.kde.org/show_bug.cgi?id=354130

Rettich  changed:

   What|Removed |Added

 CC||sebastian.rad...@gmx.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2017-11-20 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=354130

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2017-09-04 Thread Alexander Opitz
https://bugs.kde.org/show_bug.cgi?id=354130

Alexander Opitz  changed:

   What|Removed |Added

 CC||o...@gmx.at

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2017-04-15 Thread Martin Klapetek
https://bugs.kde.org/show_bug.cgi?id=354130

Martin Klapetek  changed:

   What|Removed |Added

 CC||mklape...@kde.org

--- Comment #32 from Martin Klapetek  ---
If someone can provide me with a tested patch, I'm happy
to review and merge it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2017-04-14 Thread Murz
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #31 from Murz  ---
Confirm this problem on Kubuntu 16.10 and also on fresh Kubuntu 17.04 with KDE
5.9 and kde-telepathy 15.08.3, telepathy-gabble 0.18.3-3

disable "X-OAUTH2" by 'disable_sasl_mechanisms: ["X-OAUTH2"]' solves the
problem on my own ejabberd server, but I use public jabber server and can't
connect to it.

Seems that if "X-OAUTH2" auth fail - Telepathy don't try next auth mechanism,
but stop trying and return error with wrong password. Maybe we can quickly fix
this logic problem?

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2017-04-14 Thread Murz
https://bugs.kde.org/show_bug.cgi?id=354130

Murz  changed:

   What|Removed |Added

 CC||mur...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2017-02-17 Thread Dmitry
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #30 from Dmitry  ---
(In reply to k3a from comment #27)
> If you are managing your own ejabberd server, you can disable "X-OAUTH2" by
> disable_sasl_mechanisms: ["X-OAUTH2"]
> 
> or read OAuth docs
> https://docs.ejabberd.im/developer/ejabberd-api/oauth/

This one helped me! Thank you k3a!

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2017-02-16 Thread Dmitry
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #29 from Dmitry  ---
This is what I see now in the server log when I'm trying to connect to
ejabberd:

2017-02-16 10:55:13.743 [info] <0.961.0>@ejabberd_listener:accept:333
(#Port<0.85220>) Accepted connection :45668 -> :5222
2017-02-16 10:55:13.828 [info]
<0.13203.19>@ejabberd_c2s:wait_for_feature_request:723
({socket_state,fast_tls,{tlssock,#Port<0.85220>,#Port<0.85221>},<0.13202.19>})
Failed authentication for @ from : Invalid token

I've tried to remove and configure the jabber connection again, tried with and
without "require ssl" option.
Both ends are running ArchLinux, efabberd 17.01, kde telepathy 16.12.2.

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2017-01-26 Thread Kolya Ay
https://bugs.kde.org/show_bug.cgi?id=354130

Kolya Ay  changed:

   What|Removed |Added

 CC||kolya...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2017-01-02 Thread Felix
https://bugs.kde.org/show_bug.cgi?id=354130

Felix  changed:

   What|Removed |Added

 CC||fe...@enqueue.eu

--- Comment #28 from Felix  ---
I am facing the same issue: Telepathy cannot connect to the ejabberd service.
It looks to me like the fallback to the PLAIN authentication method never takes
place. However, I am not competent enough to judge whether this error is in
ktp-auth-handler or gabble. Let me know if you need any debug output.

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-10-25 Thread tinti via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

tinti  changed:

   What|Removed |Added

 CC||viniciusti...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-10-23 Thread k3a via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

k3a  changed:

   What|Removed |Added

 CC||roo...@k3a.me

--- Comment #27 from k3a  ---
If you are managing your own ejabberd server, you can disable "X-OAUTH2" by
disable_sasl_mechanisms: ["X-OAUTH2"]

or read OAuth docs
https://docs.ejabberd.im/developer/ejabberd-api/oauth/

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-10-17 Thread lzet via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

lzet  changed:

   What|Removed |Added

 CC||p...@bk.ru

--- Comment #26 from lzet  ---
Created attachment 101602
  --> https://bugs.kde.org/attachment.cgi?id=101602=edit
google+xmpp

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-10-04 Thread tony den haan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #25 from tony den haan  ---
could it be because our server requires logging in as u...@domain.com?

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-10-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

ip...@kinetiksoft.com changed:

   What|Removed |Added

 CC||ip...@kinetiksoft.com

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-09-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

stil...@gmail.com changed:

   What|Removed |Added

 CC||stil...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-09-02 Thread somnium via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #23 from somnium  ---
This is still not working. It is the same on openSUSE Tumbleweed. I use a
ejabberd server an the password is not sent to the server like explained in
this bug report. Please reopen this report or I need to create a new one.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-09-02 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

tro...@free.fr changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #24 from tro...@free.fr ---
Apparently not totally solved.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-09-01 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #22 from tro...@free.fr ---
Weird. To make it work I had to go to "Configure" -> "Advanced" and enter a
second time the server address. Did you try that ? Entering it only at first
setup did not work.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-08-31 Thread somnium via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #21 from somnium  ---
I cannot confirm, that this bug is fixed. It is still occuring on Archlinux
with KDE Applications 16.08.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-08-31 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

tro...@free.fr changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-08-31 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #20 from tro...@free.fr ---
The big is fixed in Telepathy 16.08 on Archlinux.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-08-17 Thread Jan Šimek via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

Jan Šimek  changed:

   What|Removed |Added

 CC||jsimek...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-07-29 Thread Vadim Dyadkin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

Vadim Dyadkin  changed:

   What|Removed |Added

 CC||dyad...@lns.pnpi.spb.ru

--- Comment #19 from Vadim Dyadkin  ---
I have the same problem in Gentoo. Ktp works with jabberd2 but not with
ejabberd. Psi works with both. Patch from comment 13 solves the problem with
ejabberd.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-06-02 Thread tony den haan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #18 from tony den haan  ---
kopete and empathy also claim authentication failed. Could they be failing to
use starttls properly?

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-06-02 Thread tony den haan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

tony den haan  changed:

   What|Removed |Added

 CC||kdeb...@tuxick.net

--- Comment #17 from tony den haan  ---
Same here, if i'm lucky i get prompted for password again. Pidgin works, so i
know it's not the server.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-04-29 Thread somnium via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #16 from somnium  ---
The strange thing on openSuse Tumbleweed is, that ktp uses gnome-keyring. When
I set up an xmpp account, a password prompt for the gnome-keyring is shown. I
don't know, if this has anything to do with this issue. There is definitly an
issue in ktp-auth-handler. I cloned the repo and will take a look. Maybe I will
come up with an solution.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-04-28 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

eseif...@error-reports.org changed:

   What|Removed |Added

 CC||eseif...@error-reports.org

--- Comment #15 from eseif...@error-reports.org ---
I'm seeing the same issue on Gentoo Linux. Login to XMPP only fails if I try to
save the password. Log in works without saving the password to kwallet.

telepathy-qt: 0.9.6.1
telepathy-gabble: 0.18.3
ktp-auth-handler: 15.12.3
ktp-accounts-kcm: 15.12.3

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-04-24 Thread somnium via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #14 from somnium  ---
This problem is still not fixed with KDE Applications 16.04 on Arch Linux.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-04-05 Thread Fabian Henze via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #13 from Fabian Henze  ---
Created attachment 98255
  --> https://bugs.kde.org/attachment.cgi?id=98255=edit
Ugly hack to disable oauth2 authentication (breaks google accounts, fixes xmpp)

The attached patch fixes the problem for me. Unfortunately it's just a really
ugly workaround, which breaks google accounts.

But if this fixes it for other users as well, someone with more kde telepathy
knowledge might be able to figure out what's wrong.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-04-04 Thread Fabian Henze via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

Fabian Henze  changed:

   What|Removed |Added

 CC||flyse...@gmx.de

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-02-26 Thread Christian González via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

Christian González  changed:

   What|Removed |Added

 CC||chgonzal...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-02-17 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #12 from tro...@free.fr ---
Still not fixed in telepathy 15.12.2.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-02-13 Thread Szegi Krisztián via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

Szegi Krisztián  changed:

   What|Removed |Added

 CC||crosssz...@gmail.com

--- Comment #11 from Szegi Krisztián  ---
Same problem. And additionally, in a plasma5 environment, it (also) uses
gnome-keyring (it had me set up a new default keyring) but I also see a new
entry with the corresponding password under "accounts" in kde's wallet manager
after creating the Jabber account. After several attempts, there were entries
with for example the server name (talk.google.com) which I definitely not typed
in as password. I removed the Jabber account, removed all relevant entries from
wallet manager, created the account from scratch, and still no luck. But now, I
have only one password maps entry under accounts in wallet manager, with id
"7".
Something around password managing smells fishy.
Please look into it

My setup:
OpenSUSE Tumbleweed 20160209-0
(Maybe) relevant packages
telepathy-kde : 0.9.0-16.1
telepathy-gabble : 0.18.3-1.6
ktp-auth-handler : 15.12.1-19.1
ktp-accounts-kcm : 15.12.1-19.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-02-10 Thread Darin Miller via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

Darin Miller  changed:

   What|Removed |Added

 CC||darinsmil...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2016-01-09 Thread Tom Kijas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

Tom Kijas  changed:

   What|Removed |Added

 CC||t.ki...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2015-12-25 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

andreas.sturmlech...@gmail.com changed:

   What|Removed |Added

 CC||andreas.sturmlechner@gmail.
   ||com

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2015-12-23 Thread sourcemaker via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #10 from sourcemaker  ---
I've given up trying to use KTP. 
Welcome back Kopete!

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2015-12-20 Thread somnium via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #7 from somnium  ---
The problem still persists in KDE Applications 15.12 on Arch Linux. I am not
able to connect via XMPP/Jabber.

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2015-12-20 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

k...@ca.sh13.net changed:

   What|Removed |Added

 CC||k...@ca.sh13.net

--- Comment #8 from k...@ca.sh13.net ---
Also exists on Kubuntu 15.10 (and it's a regression from 15.04), with KDE
Frameworks 5.15.0 and Telepathy 15.08.2. Anyone here who can build KDE
Telepathy and bisect the change which broke this?

-- 
You are receiving this mail because:
You are watching all bug changes.


[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

2015-12-20 Thread Dmitry via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354130

--- Comment #9 from Dmitry  ---
I'm shocked! Critical bug about broken a part of main main functionality still
unconfirmed for two months!

-- 
You are receiving this mail because:
You are watching all bug changes.