Summary: | yahoo connection says: password incorrect | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | bazzoon <bazzoon00> |
Component: | Yahoo Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | dialouge box |
Description
bazzoon
2004-04-20 07:00:51 UTC
Created attachment 5712 [details]
dialouge box
Here is the box that tells me my password is wrong and asks me for it again.
are you using kwallet? No. kwallet was not used. However, even when I activated kwallet, the problem presisted and the problem was irrelevant to it. Did you build kopete in 64-bit mode? IIRC, you can build either a 32-bit app or a 64-bit app with an AMD64 processor. I grapped the i386 fedora core 1 kde SRPMS and I rebuilt them with the command: rpmbuild --rebuild --target x86_64 soandso.src.rpm I don't have a fix yet, but as a work around you can pass -m32 to gcc to make it build a 32 bit app when you compile kopete. CVS commit by adridg: What's the point of determining the uint32 type if you don't use it? Use it, and then all of a sudden amd64 and x86 give the same results. CCMAIL: 79981-done@bugs.kde.org M +3 -3 sha.h 1.1.4.1 --- kdenetwork/kopete/protocols/yahoo/libyahoo2/sha.h #1.1:1.1.4.1 @@ -10,8 +10,8 @@ int strprintsha(char *dest, int *hashval typedef struct { - unsigned long H[5]; - unsigned long W[80]; + uint32 H[5]; + uint32 W[80]; int lenW; - unsigned long sizeHi,sizeLo; + uint32 sizeHi,sizeLo; } SHA_CTX; Hallo zusammen, vielleicht hier auch jemand der deutsch versteht?! Ich habe glaube ich gleiches Problem! Das Passwort wird nicht angenommen er sagt immer es sei falsch! Aber auf der Webseite funktioniert es! Und mit dem für Win der Messager funktioniert es auch! bitte hilft mir weiter! Vielen Dank! MfG! JMK! I would just like to add that I have had the same problem with my Gentoo workstation on a non-64 AMD processor as well. |