Re: Post-Upgrade to 2.10.10 pidgin.exe freezes interminably
On Tue, Nov 4, 2014 at 1:49 PM, Memisyazici, Aras ar...@vt.edu wrote: ISSUE: Pidgin.exe freezes upon launch, and cannot be terminated. Methods attempted to terminate process include psexec -s generated cmd window using taskkill, procexp and built-in taskmgr. Only way to clear the stuck process is to reboot the system. DEBUG Info: Stack trace: http://www.hastebin.com/obiqisifan.avrasm OS Info: Windows 7 SP1 64-bit (Version: 6.1.7601 Service Pack 1 Build 7601) STATUS: This behavior began post-upgrade to 2.10.10. STEPS TAKEN TO DEBUG: *) I've uninstalled pidgin, rebooted, upon logging back in, verified no left-overs (checked registry, removed .purple folder and verified nothing in program files), then rebooted one more time and re-installed. RESULT: Freezing *) per suggestion of datallah on freenode #pidgin removed A/V and EMET to see if that made a difference then repeated above step. RESULT: Freezing *) Removed entire profile on Windows system, created new profile, attempted to launch pidgin. RESULT: Freezing *) Using Process Explorer, killed each thread in stack individually. Then killed all open handles. RESULT: Still not able to kill process and is stuck At this point, I'm at a loss, which is why I'm seeking advice on what to try next. Are there any methods to debug pidgin, run it in some verbose fashion to see what it is stuck onand what we can do next? I don't think you're going to get any more useful output from the debug log, but you can use the instructions here ( https://developer.pidgin.im/wiki/TipsForBugReports#Windows) to get a debug log. Based on the stack trace, the fact that you can't kill the process, and the fact that you mentioned in IRC that it is now happening with 2.10.9 too, I believe that you need to look at what else changed on your machine in the same timeframe. There's unfortunately nothing too useful in the stacktrace that I can see - the most interesting thing is the presence of afd.sys. You may be able to see something interesting in the Windows Event Log related to AFD. I'm not familiar with AFD, the following: http://www.tech-faq.com/afd-sys.html is the best summary that I could find. -D ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: https://pidgin.im/cgi-bin/mailman/listinfo/support
Pidgin on Windows Server
Wanted to ask about this again because I never got a real answer. I am trying to get Pidgin to work on a Windows Server installation. The server is not multihomed. When I run it, it appears to work, but does not display any of the other users on the network. The server is on the same subnet as the rest of the machines that are currently using Pidgin. Other users can see me but I can't see any users. If a user messages me it does not show up in my messenger. Is there maybe a port conflict? I don't have a software firewall of any kind running on the server (the whole network runs through a hardware firewall before reaching outside). Any ideas? -Brian Henson ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: https://pidgin.im/cgi-bin/mailman/listinfo/support
Office Communicator issue regarding font displays on terminating hosts
Hi I've got an interesting issue I'm not sure how to resolve. I use Pidgin to get around Lync 2013's bloated UI. I'm experiencing an issue with fonts. No matter what font I select (either using the configuration under Tools - Preferences - Conversations - Font, or Tools - Plugins - Pidgin GTK+ Theme Control (or Conversation Colors) the display on the terminating machine (which is using Lync 2013) is a copy of the end user's font. Is this a known issue? To reiterate, Pidgin's font selection doesn't seem to negotiate with lync properly. Pidgin displays inbound messages from me to my recipients as the recipient's font configuration and there doesn't appear to be a way to fix this by modifying the font. For example: If my font is set to look like this And my recipient's font looks like this My font looks like this on the recipient's application (Lync 2013) But not like this. Scott Canaga L2 Support Engineer - Intermedia Inc Phone: 877-357-0750 Ext 8424 [intermedialogo] Intermedia 3310 146th Place SE Bellevue, Washington 98007 www.intermedia.nethttp://www.intermedia.net/ * Follow us on Twitterhttp://twitter.com/intermedia_net Read our report on the SMB rogue access threat: The Ex-Employee Menacehttp://www.intermedia.net/Reports/RogueAccess?utm_source=socialutm_medium=CorporateEmailSigutm_content=Reportutm_campaign=SSAppID About Intermedia Intermedia's Office in the Cloud(tm)http://www.intermedia.net/solutions/office-in-the-cloud delivers essential IT services for SMBs and the partners who serve them - including hosted Exchange, Hosted PBX, SecuriSync file sync and share, security, mobility, identity and access management, archiving, instant messaging, conferencing and more. Our services are all pre-integrated, managed from a single control panel, and backed by our famous worry-free experiencehttp://www.intermedia.net/support/worry-free. With 60,000 customers, over one million users and 5,000 active partners, Intermedia is the world's largest one-stop shop for cloud IT. Learn more at Intermedia.nethttp://intermedia.net. This message is intended only for the person(s) to which it is addressed and may contain Intermedia.net Inc privileged, confidential and/or proprietary information. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Any disclosure, copying, distribution, or the taking of any action concerning the contents of this message and any attachment(s) by anyone other than the named recipient(s) is strictly prohibited. ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: https://pidgin.im/cgi-bin/mailman/listinfo/support
