Conversation
Notices
-
@hikerus
Is there a chance you could run it from command line first and send me the output? I would be interested to see if I can see why it crashes in the first place.
On windows it's a bit messy, you have to go into regedit, then search for 'yaics' all the settings are there, just delete the yaics 'folder' in registry and it'll go back to defaults.
-
@hikerus Ok, thanks for checking. You have this issue after resetting the settings?
Do you have 'show attached' images enabled?
-
Do you have 'attachment images' enabled when you test both accounts?
-
Thank you,
Could you do one more test please? Disable the 'public' tab in the settings, and see if that helps.
Things like that is very hard to debug.. Often it's a server side issue. But yaics should not crash even if it *was* a server side issue, So it would be nice to try and figure out what's going wrong.
-
@hikerus I start to suspect a setting is stored wrong somehow, could you take a printscreen of the settings in the registry? I would like to see what defaults it stores on your end.
-
@hikerus ok. Ill register a account on quitter.se and check in a little bit.
-
@hikerus I do. Stigatle@cryptolab.net . I need about 30 minutes until I can sit down, need to get my kids to sleep first. Add me and Ill be there shortly.
-
@hikerus I'm able to reproduce a error on quitter.se , now I have to do some more debugging and figure out exactly what's going on.
-
@hikerus So, it's the 'parseid' that causes this issue.
Now If I understand things correctly, each user has their own 'ID', if I enter this:
https://quitter.no/api/account/verify_credentials.xml
I see my user ID as : <id>743</id>
if I do the same on quitter se - the id tag is empty.
https://quitter.se/api/account/verify_credentials.xml
So to me this seems to be the cause for the issue. I have no idea why quitter.se does not show the ID for the users, but it's a problem for yaics.
When the ID for the 'user' is wrong it throws a fatal error (causing it to crash):
qFatal("parseUser(): id bad");
So - now I at least know the cause for quitter.se .
You can also check for this on the other server, by changing the url above.
Also - I will create a error message displaying the error, instead of it crashing, I'll upload a 'nightly' build for you so that you can test that on the other server as well.
I will write a bug ticket so that we do not forget this one.
-
I have built a 'unstable\nightly' release now (from latest source), I will update the download links tomorrow, I ran out of time today.
So (when you have time) please try this release,
Download from here:
https://stigatle.no/owncloud/index.php/s/Kgboc8JZZBxzxAh
the fix is what I mentioned - it gives a error message at least now, still crashes after that - but it should at least say what is wrong.
Also the time in the statuses should be printed a bit nicer now :)
I'll work on things again over the weekend.
-
@hikerus :( argh..
I'll debug some more tomorrow. I would like to see some of the XML output that I mentioned earlier, so that I have something to compare with.
I'll register a account on your server as well for debugging tomorrow.
I suspect it's the same kind of issues that others have reported too earlier (that I did not solve at the time).
-
@hikerus If you trust me with that - then feel free. I have all my contact info \ key here:
https://stigatle.no/index.php/contact/
-
@hikerus thanks! Ill check on it when I get home from work today.
-
Thanks for the email. I will look into it tonight. :)
-
Hi, I tested on windows \ linux now, both clients worked on your server. Do you still have the issue you mentioned? I could build a debug version of the client, maybe that will give me some clues as to what's going on.
-
I'll make and upload a debug build, I'll send the link shortly.
-
I uploaded a debug version now, it's at the same place as previous release. It will most likely crash also, but it's worth a shot, maybe it'll give some more information.
If we still cannot solve this, Is there a chance I could guide you through on how to compile it from source and run the debug version in QT creator?
That would tell me exactly where it goes wrong, but I understand if you do not want to spend time doing that, just let me know either way.
The download link is the same as before:
https://stigatle.no/owncloud/index.php/s/Kgboc8JZZBxzxAh
-
Yeah, that message on quitter.se is expected.
I have no idea why qutter.se does not have the 'id' set for the users in the xml like other servers does.
I have to ask the admin there I guess, and I have forgotten who that is. so if anyone of you know - then let me know :)
I did not have any trouble with the server you sent on email.
Maybe you can create a fresh user and log in with that?
Or just log in with "my" account that you sent by email, just to be sure that works for you too.
-
Thank you!
-
Yeah, that could be a issue.
Honestly - I have never ever used the 'dm' feature, and I have no idea if it even works in #yaics . I was thinking about disabling it, or at least make it optional.
But I now think you are on to something, that could be the issue indeed.
-
I tried to send a DM now on this account to you, but quitter.no does not allow to send it -
[POST] "https://quitter.no/api/direct_messages/new.xml"
[ERROR] "Network error: Error transferring https://quitter.no/api/direct_messages/new.xml - server replied: Internal Server Error"
So - I wonder if DM's work at all with quitter?
And if noone uses it - then maybe it should be deprecated from #ycaics ,
Or at least be made optional - but disabled as default.
stig atle
All Bobinas P4G content and data are available under the