Help to contribute fixing a possible bug

[Javier Almansa]

Hi Jasem,

Thanks for the quick reply.

Actually, first thing that I tried after building kstars from master branch
(pulled last night BST) was to reproduce the issue, however I ran into
something else which I don't know if it is another bug or a
misconfiguration issue on my side (but definitely didn't see it on the
previous stable version shipped with stellarmate):

* I setup a profile with the simulators, create a capture sequence and then
a job with a couple of targets to try to reproduce the original issue. For
the job I choose targets that are close to polaris so to ensure they are
always over the horizon, then I disable all constrains (twilight, altitude,
etc).  Set the job to be scheduled ASAP, greedy scheduler, etc...)
* when I start the job, the scheduler schedules the jobs exactly one hour
after I hit start.
* I checked the geographical settings, time zones, time configuration, etc
and I couldn't find anything.

As an example, I got the following logs:

2026-03-31T22:41:49 Sleeping until observation job CEPHEUS is ready at Tue
Mar 31 23:41:48 2026
2026-03-31T22:41:48 Scheduler plan for the next 48 hours starting Tue Mar
31 22:41:48 2026 (0.009)s:
2026-03-31T22:41:48 CEPHEUS 03/31 22:41 --> 22:44 job completion
2026-03-31T22:41:48 M 45 03/31 22:45 --> 22:48 job completion
2026-03-31T22:41:47 Scheduler started.
2026-03-31T22:41:47 Scheduler is awake.

There you can see that CEPHEUS is scheduled to start at 22:41 but then the
scheduler is sleeping until 23:41 (exactly one hour after).

I wanted to do a bit more of research once I was more rested (yesterday was
a long day :)) to see if this was a misconfiguration on my side or a real
bug before reporting, and then, try to reproduce my original issue again.

But as per your email, I'll try to reproduce the original issue right now
and let you know ASAP.

Cheers,
Javier

On Wed, 1 Apr 2026 at 12:22, Jasem Mutlaq <mutlaqja at ikarustech.com> wrote:

> Hello Javier,
>
> KStars 3.8.2 (due for release today or tomorrow) includes many fixes for
> the task queue. If the issue is reproducible, please try the latest code to
> see if you can reproduce it. I'll hold off the KStars release until
> tomorrow, pending your response regarding this.
>
> --
> Best Regards,
> Jasem Mutlaq
>
>
>
> On Wed, Apr 1, 2026 at 2:18 PM Javier Almansa <javieralso at gmail.com>
> wrote:
>
>> Hi all,
>>
>> Couple of days ago I raised what I think it is a bug on the scheduler (
>> https://bugs.kde.org/show_bug.cgi?id=518015). This allegedly bug leaves
>> my observatory on an unsafe state so I would like it to be fixed as soon as
>> possible.
>>
>> Since I understand that developers/contributors might be busy and this
>> might take time to get fixed, I have decided to give it a try and fix it
>> myself. I have downloaded the sources and already built kstars from master
>> branch to start with :)
>>
>> However, before I dive into the code, could someone kindly confirm
>> whether the bug I reported is an actual bug and not just a configuration
>> issue or similar? Once the bug is confirmed, I will start taking a look at
>> it.
>>
>> Thanks,
>> Javier
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20260401/ee3b906a/attachment.htm>