https://bugs.kde.org/show_bug.cgi?id=454866
Jasem Mutlaq changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #31 from steve ---
Hi everyone
This is fixed by turning off stellarsolver partitioning. The latter is now
default as of kstars 3.6.0
**does this count as RESOLVED?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #30 from steve ---
Works OK with phd2 which does NOT call sextract.
Tested over 2 sessions of 5 hours guiding with phd2.
logs etc:
https://drive.google.com/drive/folders/1B-OOitN-K5OCmUHoXOgwCXh1Lq3ZPNiG?usp=sharing
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #29 from steve ---
This is with the latest indi:
commit 3d63e3be5008605ce04621fb796f1a9b32c88a86 (HEAD -> master, origin/master,
origin/HEAD)
Author: Jasem Mutlaq
Date: Sat Jun 18 20:00:15 2022 +0300
Use IDSharedBlobAlloc and
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #28 from steve ---
The qsocketnotifier error and indi disconnect seem to be precipitated after a
Sextract:
[2022-06-20T00:20:42.763 CEST DEBG ][ org.kde.kstars.ekos.guide] - Received
guide frame.
[2022-06-20T00:20:42.763 CEST DEBG ][
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #27 from steve ---
This is the kstars git built with the latest INDI as requested testing from
here:
https://www.indilib.org/forum/development/11843-fast-blobs.html
It still crashes with the same indi disconnect error.
log:
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #26 from steve ---
Do you think this may help?
https://www.indilib.org/forum/development/11843-fast-blobs.html
Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #25 from steve ---
Hi
Any news on this bug?
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #24 from steve ---
That commit has already proven to be good.
here is the bisect log:
git bisect start
# bad: [ec5c439a01b81aa93fd67abe6fee370e3846a005] For lightbox, we must check
target state since for dark frame it must turned off and
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #23 from steve ---
OK. Found it in the git log. The previous commit is this one:
3d989ff71a2d1037fdcf0dd6fb2e0aafab144f6d
Will try.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
steve changed:
What|Removed |Added
Platform|Other |Kubuntu Packages
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #22 from steve ---
This is the bad commit according to git bisect, not myself.
Please could you help by telling me which is the previous commit you would like
testing?
Thanks.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #21 from Jasem Mutlaq ---
Are you 100% positive this is the bad commit? Can you try to checkout the
previous commit and see if it causes the crash? just to be sure.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #20 from steve ---
log corresponding to bad git bisect here:
https://drive.google.com/file/d/14nhEY_x8oLKdVzk54Mg67o2VUWsqyzCn/view?usp=sharing
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #19 from steve ---
git bisect bad
b028a6e607f64cb0f7eac284732e5b12c6df366d is the first bad commit
commit b028a6e607f64cb0f7eac284732e5b12c6df366d
Author: Hy Murveit
Date: Tue Apr 12 07:24:03 2022 +
Add Target Distance to the
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #18 from steve ---
For this bisect checkout, the indi server survived but still crashed upon:
[2022-06-11T04:16:40.210 CEST WARN ][ default] -
QSocketNotifier: Invalid socket 76 and type 'Read', disabling...
Anyway,
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #17 from steve ---
Yep. OK. I think I've understood.
Here's the next one:
git bisect good
Bisecting: 16 revisions left to test after this (roughly 4 steps)
[3d989ff71a2d1037fdcf0dd6fb2e0aafab144f6d] Fix broken checkbox label and
tooltip.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #16 from Jasem Mutlaq ---
Yes need to compile and test after each step.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #15 from steve ---
OK. That checkout gave the same error:
[2022-06-08T01:03:56.394 CEST DEBG ][ org.kde.kstars.indi] - ZWO CCD
ASI120MM Mini : "[DEBUG] Upload complete "
[2022-06-08T01:03:56.410 CEST DEBG ][
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #14 from steve ---
Just seen that it's the name of the commit which git bisect checked out. DUH!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #13 from steve ---
OK
Does this look OK?
steve@E5430:~/Projects/kstars$ git bisect start
steve@E5430:~/Projects/kstars$ git bisect bad
steve@E5430:~/Projects/kstars$ git bisect good
3369e6afa815a6d1e2089f417eade08d69e668a2
Bisecting: 85
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #12 from Jasem Mutlaq ---
There are many guides online on how to git bisect. Basically, you try to go
back until the last "good" commit you can find. So maybe when v3.5.8 was
released (3369e6afa815a6d1e2089f417eade08d69e668a2) and test with
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #11 from steve ---
Can you point me to a method for gir bisect?
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #10 from Jasem Mutlaq ---
You can use git bisect to find the offending commit. This would take a while
but you can figure out which commit caused this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #9 from steve ---
The issue doesn't occur with 3.5.8, so something which changed between then and
3.5.9?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #8 from Jasem Mutlaq ---
Unlikely.. unless you restarted your driver explicitly. Need to find WHY INDI
server gets disconnected exactly.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #7 from steve ---
Does:
Fix crash on driver restart; a541ab91429cc4f5b1df546fe2a2ce27d10dc900
https://github.com/KDE/kstars/commit/a541ab91429cc4f5b1df546fe2a2ce27d10dc900
Have any bearing upn this?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #6 from steve ---
Hi
Unfortunately, it happens randomly when capturing and/or guiding but always
within an hour of starting the session.
eos700d, eq6, zwo120mm mini
There are lots of these in the syslog. Don't know if it's related:
'
Jun 6
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #5 from Jasem Mutlaq ---
No there are separate USB issues. The error begins with INDI server
disconnecting
INDI server disconnected. Exit code: -1
No reason was given for this. After the BLOB managers were removed, there was
probably
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #4 from steve ---
There are lots of these in the syslog at the time of the indi disconnection:
usb 3-2: reset high speed USB device number 3 using xhci_hcd
Any pointers?
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #3 from steve ---
I'm using a Canon eos700d, eq6 mount and asi120mm guide camera.
The error occurs after taking around 15 to 20 frames (could be more, could be
less).
Socket error, so I thought it maybe the vnc server or client so switched
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #2 from Jasem Mutlaq ---
Any way to reproduce this? I cannot reproduce it here.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454866
--- Comment #1 from steve ---
This was also reported to the indilib forum:
https://www.indilib.org/forum/ekos/11784-kstars-qsocketnotifier-invalid-socket-error.html
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
33 matches
Mail list logo
