SUMMARY Ekos crashes while plate solving irrespective of methods (internal, local astrometry, online astrometry, etc). Linux x86_64 5.4.0.104 Let me know if there are ways to go back to one previous version which worked flawlessly. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Ubuntu Mate 20.04.4 LTS ADDITIONAL INFORMATION
Hi there, can you verify if this issue still exists now that I made StellarSolver 2.2 and that we released KStars 3.5.8? I worked hard to address crashing issues like this one, so hopefully these changes will fix it. I am sorry that the upgrade in StellarSolver affected the Stable version of KStars 3.5.7. The new version of StellarSolver should have just been used by 3.5.8 and not 3.5.7 since the APIs were incompatible, but then when it got updated to the PPA, many people's systems used the new StellarSolver with the old KStars, which wasn't good.. We did update the PPA with a patch to try to fix 3.5.7 to work with StellarSolver 2, but it wasn't really designed for it. The new KStars 3.5.8 and the new StellarSolver 2.2 should be pretty good together.
Thank y On Sat, Mar 19, 2022 at 11:42 PM Rob <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=451331 > > Rob <rlancaste@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |rlancaste@gmail.com > > --- Comment #1 from Rob <rlancaste@gmail.com> --- > Hi there, can you verify if this issue still exists now that I made > StellarSolver 2.2 and that we released KStars 3.5.8? I worked hard to address > crashing issues like this one, so hopefully these changes will fix it. I am > sorry that the upgrade in StellarSolver affected the Stable version of KStars > 3.5.7. The new version of StellarSolver should have just been used by 3.5.8 > and not 3.5.7 since the APIs were incompatible, but then when it got updated to > the PPA, many people's systems used the new StellarSolver with the old KStars, > which wasn't good.. We did update the PPA with a patch to try to fix 3.5.7 to > work with StellarSolver 2, but it wasn't really designed for it. The new > KStars 3.5.8 and the new StellarSolver 2.2 should be pretty good together. > > -- > You are receiving this mail because: > You reported the bug.
Thank you for contacting me. Using simulators did not crash kstars, but I have not had a chance to try with real equipment since the weather is not cooperating. Also the moon is big. Sincerely, Takashi Wakui On Sun, Mar 20, 2022 at 4:36 PM Takashi WAKUI <takashiesperanza@gmail.com> wrote: > > Thank y > > On Sat, Mar 19, 2022 at 11:42 PM Rob <bugzilla_noreply@kde.org> wrote: > > > > https://bugs.kde.org/show_bug.cgi?id=451331 > > > > Rob <rlancaste@gmail.com> changed: > > > > What |Removed |Added > > ---------------------------------------------------------------------------- > > CC| |rlancaste@gmail.com > > > > --- Comment #1 from Rob <rlancaste@gmail.com> --- > > Hi there, can you verify if this issue still exists now that I made > > StellarSolver 2.2 and that we released KStars 3.5.8? I worked hard to address > > crashing issues like this one, so hopefully these changes will fix it. I am > > sorry that the upgrade in StellarSolver affected the Stable version of KStars > > 3.5.7. The new version of StellarSolver should have just been used by 3.5.8 > > and not 3.5.7 since the APIs were incompatible, but then when it got updated to > > the PPA, many people's systems used the new StellarSolver with the old KStars, > > which wasn't good.. We did update the PPA with a patch to try to fix 3.5.7 to > > work with StellarSolver 2, but it wasn't really designed for it. The new > > KStars 3.5.8 and the new StellarSolver 2.2 should be pretty good together. > > > > -- > > You are receiving this mail because: > > You reported the bug.
Please check against KStars 3.6.1 and report back.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Created attachment 153200 [details] attachment-6205-0.html Hi Is this regarding the bug report a long time ago? Ekos does not crash any more. Thank you. Takashi On Tue, Oct 25, 2022, 14:01 Bug Janitor Service <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=451331 > > --- Comment #5 from Bug Janitor Service <bug-janitor@kde.org> --- > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! > > -- > You are receiving this mail because: > You reported the bug.
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!