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.
Yeah, my ignore list is crazy big. So many auto \ RSS posters there filling up the feed. I run https://diasporapod.no - I try my best to keep spammers out. A couple of them slipped through the net, but I quickly remove them. I had to adjust the settings for the default captcha this week, keeping them out better now.
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.
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.
@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).
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.
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.
@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 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.
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.