marig345 / prpltwtr

Automatically exported from code.google.com/p/prpltwtr
GNU General Public License v2.0
0 stars 0 forks source link

Unable to load prpltwtr 0.9.0 (Win XP 32) if debug symbols aren't installed #59

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Client (Pidgin, finch, empathy, etc): Pidgin (German)
Client Version: 2.9.0
LibPurple Version: 2.9.0
PrplTwtr Version: 0.9.0
Operating System: Windows XP 32 bit (German)

Problem/Feature request (Be as specific as possible. Steps to reproduce are
especially helpful):

After installing the DLLs won't load. 0.8.0 worked fine. Debug log says that 
the module could not be found:

(15:04:08) plugins: probing D:\Pidgin\plugins\libgtkprpltwtr.dll
(15:04:08) plugins: D:\Pidgin\plugins\libgtkprpltwtr.dll is not loadable: 
`D:\Pidgin\plugins\libgtkprpltwtr.dll': Das angegebene Modul wurde nicht 
gefunden.
(15:04:08) plugins: probing D:\Pidgin\plugins\libprpltwtr_statusnet.dll
(15:04:08) plugins: D:\Pidgin\plugins\libprpltwtr_statusnet.dll is not 
loadable: `D:\Pidgin\plugins\libprpltwtr_statusnet.dll': Das angegebene Modul 
wurde nicht gefunden.
(15:04:08) plugins: probing D:\Pidgin\plugins\libprpltwtr_twitter.dll
(15:04:08) plugins: D:\Pidgin\plugins\libprpltwtr_twitter.dll is not loadable: 
`D:\Pidgin\plugins\libprpltwtr_twitter.dll': Das angegebene Modul wurde nicht 
gefunden.

The DLLs are present, neither the protocol not the plugin are shown in Pidgin.

Original issue reported on code.google.com by Drah...@googlemail.com on 17 Jul 2011 at 1:08

GoogleCodeExporter commented 8 years ago
Is libprpltwttr.dll being loaded? All three depend on it. [I'm not 100% sure I 
know how to translate the German into the exact English message that I'd 
recognize].

There was a change in the names from 0.8.0 to 0.9.0. Perhaps try deleting 
*prpltwtr*.dll, and reinstalling 0.9.0.

Note that you'll need to re-enable gtkprpltwtr after this.

Original comment by mikeage on 18 Jul 2011 at 2:58

GoogleCodeExporter commented 8 years ago
According to Process Explorer the DLL is not loaded. I do not have any 
leftovers from the old install (as far as I can see). To be sure I'll add a 
list of the existing DLLs in my Pidgin main dir as well as in the plugins dir.

====================
Main dir:
====================
exchndl.dll
freebl3.dll
libcurl-4.dll
libgtkspell.dll
libjabber.dll
libmeanwhile-1.dll
libnspr4.dll
liboscar.dll
libplc4.dll
libplds4.dll
libprpltwtr.dll
libpurple.dll
libsasl.dll
libsilc-1-1-2.dll
libsilcclient-1-1-2.dll
libxml2-2.dll
libymsg.dll
nss3.dll
nssckbi.dll
nssutil3.dll
pidgin.dll
smime3.dll
softokn3.dll
sqlite3.dll
ssl3.dll
wmpuice.dll

====================
plugins dir:
====================
autoaccept.dll
buddynote.dll
convcolors.dll
extplacement.dll
gtkbuddynote.dll
history.dll
iconaway.dll
idle.dll
joinpart.dll
libaim.dll
libbonjour.dll
libgg.dll
libgtkprpltwtr.dll
libicq.dll
libirc.dll
libmsn-pecan.dll
libmsn.dll
libmxit.dll
libmyspace.dll
libnovell.dll
libprpltwtr_statusnet.dll
libprpltwtr_twitter.dll
libsametime.dll
libsilc.dll
libsimple.dll
libxmpp.dll
libyahoo.dll
libyahoojp.dll
log_reader.dll
markerline.dll
musicinfo.dll
musictracker.dll
newline.dll
notify.dll
offlinemsg.dll
perl.dll
pidgin-otr.dll
pidgin-pp.dll
pidginrc.dll
pidginSnarl.dll
psychic.dll
relnot.dll
screenshot.dll
sendbutton.dll
spellchk.dll
ssl-nss.dll
ssl.dll
statenotify.dll
tcl.dll
themeedit.dll
ticker.dll
timestamp.dll
timestamp_format.dll
win2ktrans.dll
winprefs.dll
xmppconsole.dll
xmppdisco.dll

I also added the lists as files so you can remove the lists in this comment if 
it gets too messy to read.

I also tried renaming libprpltwtr.dll to libprpltwttr.dll but it did not make a 
difference.

Original comment by Drah...@googlemail.com on 18 Jul 2011 at 5:26

Attachments:

GoogleCodeExporter commented 8 years ago
The rename was unnecessary; I had a typo in my comment ;)

I'm not sure what to tell you, other than WorksForMe. I wonder if it could be 
related to the language somehow, although I'm not sure how.

Can you send me a debug log showing how libprpltwtr.dll is being loaded, as 
well?

Also, are you willing to try with a fresh pidgin installation? You can install 
PortablePidgin in another directory, and install the plugin there; it won't 
affect your main pidgin install (but you can't run them simultaneously).

Can you confirm that if you go back to 0.8.0, it works (note that you'll have 
to uninstall 0.9.0 first)

Thanks for your help; sorry I don't have any ideas at the moment.

Original comment by mikeage on 19 Jul 2011 at 2:41

GoogleCodeExporter commented 8 years ago
I tried a fresh portable version of 2.9.0. Here's the complete debug log. I 
changed the language to English so the messages are easier to understand.

Original comment by Drah...@googlemail.com on 21 Jul 2011 at 3:26

Attachments:

GoogleCodeExporter commented 8 years ago
It's working now. The debug symbols are a non-optional dependency (I did not 
copy the debug symbols as I did not intend to debug).

Thank you for your help.

Original comment by Drah...@googlemail.com on 21 Jul 2011 at 3:36

GoogleCodeExporter commented 8 years ago
Interesting. That's not good. [I always use the debug symbols, and they're the 
default, so I guess no one noticed].

Thanks for investigating this. I will try to figure out what happened

Original comment by mikeage on 21 Jul 2011 at 5:43

GoogleCodeExporter commented 8 years ago
I already thought that making the debug symbols a dependency was no intension. 
At least it's working now and it can be fixed in 0.10.0

Original comment by Drah...@googlemail.com on 21 Jul 2011 at 5:47

GoogleCodeExporter commented 8 years ago
I think I have a fix for this in the makefiles.

Can you try the attached version and confirm that it works for you? Note that 
this version also includes some extra stuff, namely lists you've subscribed to 
but didn't create, and a fix for using the per-account (instead of the global) 
proxy definitions)

The actual code will be delivered tomorrow; I don't have time tonight :)

Original comment by mikeage on 21 Jul 2011 at 7:03

Attachments:

GoogleCodeExporter commented 8 years ago
ACK. It's working. Thank you.

Original comment by Drah...@googlemail.com on 21 Jul 2011 at 8:26

GoogleCodeExporter commented 8 years ago

Original comment by mikeage on 23 Jul 2011 at 6:24