https://bugs.kde.org/show_bug.cgi?id=398745
--- Comment #6 from TallFurryMan ---
Making the KSNotification::sorry auto-close would probably not fix the problem,
e.g. when multiple consecutive ESL files contain invalid sequence files.
Making the error blocking, and eventually auto-close to
https://bugs.kde.org/show_bug.cgi?id=398635
--- Comment #5 from TallFurryMan ---
Capture has changed so much that the description doesn't match anymore. I think
this should remain closed now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398745
TallFurryMan changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=398302
TallFurryMan changed:
What|Removed |Added
Resolution|WORKSFORME |FIXED
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=397969
--- Comment #7 from TallFurryMan ---
Yeah good idea, I'll open a new issue for this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398194
--- Comment #3 from TallFurryMan ---
No update yet. There are now tests for the Scheduler, but they aren't stable
enough and don't cover enough cases to safely work on this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=395232
TallFurryMan changed:
What|Removed |Added
Resolution|--- |NOT A BUG
CC
https://bugs.kde.org/show_bug.cgi?id=382434
TallFurryMan changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=108772
TallFurryMan changed:
What|Removed |Added
CC||eric.dejouha...@gmail.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=396182
TallFurryMan changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|REMIND
https://bugs.kde.org/show_bug.cgi?id=398301
--- Comment #2 from TallFurryMan ---
Will be verified with Capture tests.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=397970
--- Comment #5 from TallFurryMan ---
Will verify this issue with Capture tests soon.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396182
TallFurryMan changed:
What|Removed |Added
Resolution|--- |REMIND
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=422939
TallFurryMan changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=422941
TallFurryMan changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=423012
TallFurryMan changed:
What|Removed |Added
Version Fixed In||v3.4.3
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=422941
TallFurryMan changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/educ
https://bugs.kde.org/show_bug.cgi?id=422940
TallFurryMan changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/educ |https://invent.kde.org/educ
https://bugs.kde.org/show_bug.cgi?id=422940
TallFurryMan changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=398437
--- Comment #1 from TallFurryMan ---
The situation now is different. The Observatory does shut down, but a new job
is started between the pre-dawn margin and the actual dawn limit.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=423012
Bug ID: 423012
Summary: EKOS - PHD2 sometimes does not see the camera
Product: kstars
Version: git
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=422941
Bug ID: 422941
Summary: EKOS - PHD2 losing connection makes guider module
unrecoverable
Product: kstars
Version: git
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=422940
Bug ID: 422940
Summary: EKOS - PHD2 may fail calibration without notice
Product: kstars
Version: git
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=422939
Bug ID: 422939
Summary: EKOS - If PHD2 connects first, driver configuration is
not loaded
Product: kstars
Version: git
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=414216
TallFurryMan changed:
What|Removed |Added
Version|3.1.0 |3.4.1
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=414216
TallFurryMan changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
CC
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #14 from TallFurryMan ---
Jasem, could you confirm you adjusted the relevant test to verify your change?
Tests/kstars_ui/test_ekos.cpp, in TestEkos::testSimulatorProfile, line 134.
I don't see this in your changelog.
--
Yo
https://bugs.kde.org/show_bug.cgi?id=398192
TallFurryMan changed:
What|Removed |Added
Version|2.9.8 |3.4.0
--- Comment #12 from TallFurryMan
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #11 from TallFurryMan ---
Reproduced on my live (not current) system, confirming test is OK:
^C[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
0xb
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #10 from TallFurryMan ---
When the issue is reproduced, this is the stack from the event clicking the
"stop" button:
1 __GI___pthread_ti
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #9 from TallFurryMan ---
Refining the test, it appears the issue may source from the intrication of
signals between gadgets. The code is re-entring the event loop at various
places, and if the INDI server is still busy deleting properties
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #7 from TallFurryMan ---
In my test, INDI client is still creating properties after 20 seconds, so I'll
investigate further before calling the test proper:
1 sy
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #6 from TallFurryMan ---
I need to make very sure the test is spotting the right problem.
I'll then push a differential with said test for reference.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #5 from TallFurryMan ---
Reproduced using indi 1.7.9, and indi git tip. Call is stuck with the following
stack:
1 __GI___pthread_timedjoin_ex
https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #3 from TallFurryMan ---
Yes, confirmed again.
I just wrote a test to validate this and can reliably reproduce the issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398192
TallFurryMan changed:
What|Removed |Added
Assignee|mutla...@ikarustech.com |eric.dejouha...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=404868
TallFurryMan changed:
What|Removed |Added
Assignee|mutla...@ikarustech.com |eric.dejouha...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=404868
Bug ID: 404868
Summary: Scheduler delays subsequent jobs when hitting a
restriction violation
Product: kstars
Version: 3.0.1
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=402709
--- Comment #1 from TallFurryMan ---
Version? There was a regression with a hotfix for that specific issue:
https://github.com/KDE/kstars/commit/a3e3b2c7c42d64548bb2052700e8aa5998261b37
I assume the problem is still here somehow.
--
You are
https://bugs.kde.org/show_bug.cgi?id=381543
--- Comment #7 from TallFurryMan ---
Probably not. I'll test this during January if weather agrees.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400580
--- Comment #6 from TallFurryMan ---
*being at the meridian at that moment on the chart that is drawn on the screen.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400580
--- Comment #5 from TallFurryMan ---
Sure. I was only referring to the 4 minute offset. Actually I do not compare
softwares to prove which is right and which is wrong: this is bug is only about
the fact that the transit time presented in the dialog
https://bugs.kde.org/show_bug.cgi?id=400580
--- Comment #3 from TallFurryMan ---
No yet. Preliminary guess is that while calculating, the algorithm incorrectly
moves to a different day, which offsets the transit time by 4 minutes.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=400580
--- Comment #1 from TallFurryMan ---
I found this while rewriting the planning algorithm of the Scheduler.
#267265 is similar, but fixes an issue deeper in the calculations.
Calculating transit time with KNumbers gives proper results.
The issue seems
https://bugs.kde.org/show_bug.cgi?id=400580
Bug ID: 400580
Summary: Detail window has incorrect transit time
Product: kstars
Version: git
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=398405
TallFurryMan changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=398415
TallFurryMan changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=398757
--- Comment #5 from TallFurryMan ---
Found it! There is a syntax error in the dome XML, just after the declaration
of "isMoving"!
When qdbusxml2cpp generates the MOC, it doesn't report the error, but simply
stops reading the XML file..
https://bugs.kde.org/show_bug.cgi?id=398757
--- Comment #4 from TallFurryMan ---
Well, this is how the adaptor is created:
"
[ 13%] Generating domeadaptor.cpp, domeadaptor.h
cd /home/tallfurryman/dev/kstars_build/kstars &&
/usr/lib/x86_64-linux-gnu/qt5/bin/qdbusxml2cpp -m -a domead
https://bugs.kde.org/show_bug.cgi?id=398757
--- Comment #3 from TallFurryMan ---
I think we should resolve this one now that clearSequence is removed. The issue
was due to targetName being executed *before* clearSequence although the
property setter was requested *after* clearSequence. I will
https://bugs.kde.org/show_bug.cgi?id=381543
TallFurryMan changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=396182
TallFurryMan changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=396182
--- Comment #8 from TallFurryMan ---
Indeed it does depend on the free time of the handful of developers :)
We need to prioritize, and currently most of the work is fixing side-effects
following the D-Bus changes. We won't introduce new features
https://bugs.kde.org/show_bug.cgi?id=381545
TallFurryMan changed:
What|Removed |Added
Ever confirmed|0 |1
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=398744
--- Comment #3 from TallFurryMan ---
I propose to use the OSS services of Synopsys Coverity to get a static code
analysis of KStars.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398757
TallFurryMan changed:
What|Removed |Added
CC||mutla...@ikarustech.com
Assignee
https://bugs.kde.org/show_bug.cgi?id=398757
--- Comment #1 from TallFurryMan ---
Setting target name using member property targetName and method setProperty is
failing. Something is wrong with the way of calling this. Investigating.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=398757
Bug ID: 398757
Summary: Scheduler target name not taken into account by
Capture module
Product: kstars
Version: git
Platform: Other
OS: Linux
Status: U
https://bugs.kde.org/show_bug.cgi?id=398745
Bug ID: 398745
Summary: Crash when not closing warning pop-up on invalid
sequence file
Product: kstars
Version: 2.9.8
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=398744
--- Comment #1 from TallFurryMan ---
This particular situation on the shutdown script made Ekos unable to finish the
shutdown process, and state SHUTDOWN_SCRIPT never completed. Another timeout
safeguard to be implemented here.
--
You are receiving
during execution of
shutdown process, which could not execute.
Executing script /home/tallfurryman/Documents/EkosShutdown.sh
QProcessPrivate::createPipe: Cannot create pipe 0x4c676c0: Too many open files
It is obviously relatively difficult to track descriptor leaks for end-users,
so perhaps an
https://bugs.kde.org/show_bug.cgi?id=398504
--- Comment #4 from TallFurryMan ---
Thanks Jasem! Cedric, getting this to work under a short amount of time would
require you to extract the code tree in the pre-merge state and cherry-pick
Jasem's change. So it depends whether you are willing to
https://bugs.kde.org/show_bug.cgi?id=398503
--- Comment #8 from TallFurryMan ---
That's what I thought: Scheduler is not seeing the mount slew, and request the
slew operation again: "Warning: job 'Deneb' found not slewing, restarting.".
You don't get the same beha
https://bugs.kde.org/show_bug.cgi?id=398635
Bug ID: 398635
Summary: When capture suspends because of guiding deviation,
and capture is stopped, UI is in invalid state
Product: kstars
Version: git
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=398503
--- Comment #3 from TallFurryMan ---
Do you have logs for this?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398415
TallFurryMan changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=398503
TallFurryMan changed:
What|Removed |Added
CC||eric.dejouha...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=398504
TallFurryMan changed:
What|Removed |Added
CC||eric.dejouha...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #15 from TallFurryMan ---
One first step towards fixing this is in https://phabricator.kde.org/D15492
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=397562
TallFurryMan changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #14 from TallFurryMan ---
Preliminary work in the Capture module at
https://github.com/TallFurryMan/kstars, branch
improve__support_decimal_locales.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #12 from TallFurryMan ---
I'm planning to:
- replace atof calls used to read XML numbers, which use the system locale,
with QLocale::C string-to-type functions.
- make sure QString calls used to write XML numbers use the QLoca
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #11 from TallFurryMan ---
XML files are saved with the system locale, and loaded with no locale. This
issue is in Scheduler and Capture modules. Besides, all control texts need
rework to take locale into account properly.
--
You are
https://bugs.kde.org/show_bug.cgi?id=398405
TallFurryMan changed:
What|Removed |Added
CC||mutla...@ikarustech.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=398405
TallFurryMan changed:
What|Removed |Added
Assignee|mutla...@ikarustech.com |eric.dejouha...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #10 from TallFurryMan ---
I think the issue has been there for a long time actually. Besides, it might
evantually relate to the issue forum user alacant had.
Tested with target "NGC 281", created a scheduler job, saved, loade
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #9 from TallFurryMan ---
On my system, QString("%L1").arg(float_var) with float_var does produce "1,2",
while QString("%1").arg(float_var) does produces "1.2".
I'm checking where all this shoul
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #7 from TallFurryMan ---
Read some Qt docs, and found the problem: all of our arg() and number() calls
basically ignore locale. To properly support that, we can use "%L1" instead of
"%1" for a float number for insta
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #5 from TallFurryMan ---
Coordinates end up "HH MM SS.SS" after conversion instead of "HHh MM' SS,SS""
in the RA/DEC boxes, and the "." character is not recognized properly, leading
to offset&
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #4 from TallFurryMan ---
I reproduced the issue is more serious than I thought. The bug appears (also?)
in the .esl load procedure! Could this be a regression introduced by the
copy&paste of coordinates? This was working properly du
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #3 from TallFurryMan ---
Issue might be related to QString::toDouble in dms::setFromString.
Documentation in Qt11 doesn't mention any locale issue, so perhaps this is a
version compatibility problem?
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #2 from TallFurryMan ---
This seems proper indeed. Issue must be elsewhere, let me provide a scenario.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398437
TallFurryMan changed:
What|Removed |Added
Assignee|mutla...@ikarustech.com |eric.dejouha...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=398437
Bug ID: 398437
Summary: Job approaching dawn is always rescheduled, preventing
observatory shutdown
Product: kstars
Version: git
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=398415
Bug ID: 398415
Summary: Repeated Scheduler jobs are aborted before they
actually repeat
Product: kstars
Version: git
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=398405
Bug ID: 398405
Summary: Session planner copies RA/DEC to Scheduler without
fractional part
Product: kstars
Version: git
Platform: Other
OS: Linux
Statu
https://bugs.kde.org/show_bug.cgi?id=398388
--- Comment #4 from TallFurryMan ---
For this particular issue, there *is* a timeout in the Focus module, set to 45
seconds. But it is used to allow the user to pick a star, as the message
suggests. I'll add a branch considering inAutoFocus
https://bugs.kde.org/show_bug.cgi?id=398388
--- Comment #3 from TallFurryMan ---
Two things I need to fix before introducing additional timers in the Scheduler:
minimal workaround for the capture storage cache count (fits analysis later on)
and removal of the lock-up related to the manual
https://bugs.kde.org/show_bug.cgi?id=398388
--- Comment #1 from TallFurryMan ---
Jasem, this is one of the issues that impact the d-bus rework you are currently
doing. I'm worried that fixing those issues will create conflicts in your
branch, but I'm also worried that such issues would
https://bugs.kde.org/show_bug.cgi?id=398388
Bug ID: 398388
Summary: No failure in Scheduler when Focus module fails to
find a star
Product: kstars
Version: 2.9.8
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=398301
--- Comment #1 from TallFurryMan ---
Additional (really funny) note: the calibration options are part of the
sequence file, so any sequence file saved after "Wall" mode is configured will
make the Capture module slew to the wall source posi
https://bugs.kde.org/show_bug.cgi?id=398302
Bug ID: 398302
Summary: Mount cannot unpark after executing parking of
shutdown procedure manually
Product: kstars
Version: 2.9.8
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=398301
TallFurryMan changed:
What|Removed |Added
Summary|Once "Wall" mode is used, |Once "Wal
https://bugs.kde.org/show_bug.cgi?id=398301
Bug ID: 398301
Summary: Once "Wall" mode is used, all frames type use the
"Wall" coordinates
Product: kstars
Version: 2.9.8
Platform: Other
OS: Linux
S
https://bugs.kde.org/show_bug.cgi?id=396182
--- Comment #4 from TallFurryMan ---
No, no yet. That feature is properly specified, but we are busy fixing issues
in the Scheduler.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398198
--- Comment #2 from TallFurryMan ---
Agreed, this ticket only applies to the "Wall" mode.
Thinking about it, I even wonder if tracking would actually improve the flat
quality. But, well capturing something static is better done withou
https://bugs.kde.org/show_bug.cgi?id=398198
Bug ID: 398198
Summary: Mount tracking while taking flats in "Wall" mode
Product: kstars
Version: 2.9.8
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: n
https://bugs.kde.org/show_bug.cgi?id=398194
--- Comment #1 from TallFurryMan ---
Own plans include a feature that will update the priority of repeating
Scheduler jobs, so that even in LOOP_INFINITE or LOOP_UNTIL state, other jobs
may schedule in-between when their target can be observed. This
https://bugs.kde.org/show_bug.cgi?id=398194
Bug ID: 398194
Summary: Warning on Scheduler job looping indefinitely visible
with only one job in the list
Product: kstars
Version: 2.9.8
Platform: Other
OS: Linu
https://bugs.kde.org/show_bug.cgi?id=398193
Bug ID: 398193
Summary: Repeating Scheduler job marked aborted by past startup
before actually repeating
Product: kstars
Version: 2.9.8
Platform: Other
OS: Linux
1 - 100 of 157 matches
Mail list logo
