Kstars-bleeding in ubuntu 17.04. 2017-08-19T17:38:19Z 2.8.1 In the profile editor I tried to set phd2 host and address. Host can be set and saved. However the port remains 0 no matter what I do. Editing kstarsrc [Guide] section PHD2Port has no effect. The profile editor shows zero. Cliking Connect on the guider panel throws "The connection was refuded by the peer. Make sure that PHD2 is running, and check that host name and port are correct". PHD2 is actually listening on tcp 4300 and 4400. I tried to set both in the kstarsrc with no success.
I also modified the sqlite db directly and saved ports both 4300 and 4400 to two different profiles. After launching kstars I still saw port numbers zero in both profiles.
This is odd, I cannot reproduce this bug. Are you using English locale?
phd@astro2:~$ echo $LC_ALL en_US.UTF-8 phd@astro2:~$ echo $LANG en_US.UTF-8 phd@astro2:~$
phd@astro2:~$ uname -a Linux astro2 3.4.39 #1 SMP PREEMPT Mon Oct 12 12:02:29 CEST 2015 armv7l armv7l armv7l GNU/Linux phd@astro2:~$
I presume you're using the PPA, can you please update to the latest version and try again?
Updated. It still does not work. Port is saved wrong. Strange, apart from this everything else seems to be working. I'm using LXDE should this matter. Further detail is that I created two profiles, so now I have three. Simulators, Doma1 and Doma2. I updated the sqlite file for Doma1 and Doma2 to have 4400 and 4300 as ports. Then I opened kstars and looked at both Doma1 and Doma2 profiles. Both showed 0 in the port field. The I modified Doma1 and saved the profile. I opened it once again and still saw zero at the port number. Then I looked at the sqlite db. For the profile I modified the port got updated to NULL, whereas with the unmodified profile I saw the original value of 4300 in the DB although it showed up as zero in the control and when kstars was trying to read it for connecting phd2.
I noticed one more thing... The field in the db is called `guidepost`. Everywhere else it is typed correctly. 'indiwebmanagerport' and 'port'. Maybe this has something to do with it...
guiderpost :)
well one thing you could do is to delete userdb but you will lose all settings and DSOs and then start KStars and it will recreate the whole db again.
Created attachment 107420 [details] Typo in the sqlite db field name
Git commit ac0ca2bd4da72db56f8eabdeefa58f7fa632054d by Jasem Mutlaq. Committed on 21/08/2017 at 10:24. Pushed by mutlaqja into branch 'master'. Fix stupid typo M +1 -1 kstars/auxiliary/ksuserdb.cpp https://commits.kde.org/kstars/ac0ca2bd4da72db56f8eabdeefa58f7fa632054d
Deleted user db. Retried. Same result. Maybe it could be made NOT NULL and fill it with 0 and see what happens. You always get a zero value in the control anyway.
It was a typo as you found it and it is now fixed. You either compile KStars now from Git or wait until the next release.
Thank you. An alter table on the db might do until then as a workaround, right?
I can confirm that altering the schema works. Of course first you need to rename then re-create the table. Then create the new table with correct column names and then migrate the data if you want a correct fix as sqlite does not support ALTER TABLE. :)