#6399: procedure entry point GetGuiResources could not be located
------------------------------+---------------------------------------------
Reporter: tmetro | Owner: datallah
Type: defect | Status: assigned
Priority: minor | Milestone:
Component: winpidgin (gtk) | Version: 2.4.2
Resolution: | Keywords:
Pending: 0 |
------------------------------+---------------------------------------------
Changes (by datallah):
* status: new => assigned
Comment:
Replying to [comment:3 tmetro]:
> So you're saying a grep of the main source for !GetGuiResources doesn't
turn up anything?[[BR]]
Exactly. That also eliminates any of the plugins that are included in the
default installation.
> The last few lines logged up to the point where the dialog appears
are:[[BR]]
<snip>
> (19:22:32) plugins: probing C:\bin\net\misc\Pidgin\plugins\libxmpp.dll
<snip>
>
> I'm guessing that while the Jabber protocol plugin (libxmpp.dll) is a
good candidate, that debug log buffering and and/or multiple threads might
mean the cause isn't so obvious.
Hmm... it certainly isn't anything in the XMPP prpl plugin directly.
Pidgin is (with a couple specific exceptions) single-threaded, so
hopefully this isn't an issue.
> It appears the plugins are probed prior to the error, but not loaded
until after the dialog appears.
This tells us that it is something that happens during the initialization
of the xmpp prpl. In turn, this leads to CyrusSASL and eventually to the
GSSAPI plugin and then the MIT Kerberos library, where we find the
culprit.
You can avoid this issue by deleting the `saslGSSAPI.dll` from the
`...\Pidgin\sasl2` directory - it will have no negative effects since it
can't load anyway (it is used for authenticating with your Windows
Credentials for servers that support such a mechanism).
I'll update the installer to automatically remove the file on NT4.
--
Ticket URL: <http://developer.pidgin.im/ticket/6399#comment:4>
Pidgin <http://pidgin.im>
Pidgin