Menu
▾
▴
#347 Pidgin stopped showing online contacts
Hi
Recently our company switched to MFA for everything. And now Pidgin doesn't show online contacts anymore complaining on not found Exchange server. Although I can send and receive messages.
I use sipe 1.23.3+sipe-0+201811221831~ubuntu18.04.1
A little update while I was writing this report..
I just tried to restart Pidgin and it doesn't connect anymore with next error.
"Web ticket request to https://lyncpctwebint.mycompanydomain.com:443/CertProv/CertProvisioningService.svc failed"
Skype For Business still works fine in my Windows VM and doesn't require any interactive authentication.
Unfortunately I couldn't find any debug log in Pidgin.
Discussion
What are we supposed to do with such a bug report? There is nothing in here which would allow developers to address the problem.
First your should exclude any configuration issues, as your company has obviously changed your setup. I would suggest reading the FAQ page, which also explains how to take appropriate logs.
Closing as NOTABUG
That's why you don't have open bugs. But likely there are hundreds of them. Some people just don't want to keep using software when they were rejected such a tough way :)
You were right about configuration. Somehow I entered invalid password.
So the only problem is offline contacts
So I should create kind of private bug to share logs. But this won't help users with the same problem. And FAQ has nothing helpful wrt this. that's pity.
Let me quote from the header text that appears when you click on
Create Ticketentry on the left hand side menu:after which an exhaustive list with information and link to the FAQ follows. Don't be surprised that your bugs get closed if you choose to ignore bug reporting instructions provided by the project.
As you still have not provided a full debug log, nobody will be able to help you with your "buddies are offline" issue. I can only take an educated guess that you either should try to re-add your buddies for the new setup or that the Exchange server autodiscovery does not work or you have specified the wrong Exchange server.
Nobody forces you to create a private bug report to share debug logs. If you are paranoid, run sed over the log to replace what you consider "sensitive information".
Complaining about documentation without providing suggestions how to improve it is also not helpful.
oh.. I'm a regular user. Just have a little more tolerance.
I created another bug. But honestly I'm at work right now and don't have much time to read everything and to understand what's sensitive in the log. I just want a little help.
That's what the Help forum is for. Creating bugs is just wasting everybodies time.
FYI: closing this discussion now. You can bitch about that in another bug report, if you want to.