https://bugs.kde.org/show_bug.cgi?id=450039
Hy changed:
What|Removed |Added
CC||hymu...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=450039
--- Comment #3 from Hy ---
I have a MBP as well. Try the "two finger down or up" swipe on the trackpad.
When focused on the timeline it seems to zoom in X. When focused on the graph
window it seems to zoom in Y. As I said, if you have a
https://bugs.kde.org/show_bug.cgi?id=455573
Bug ID: 455573
Summary: Valgrind crashes when running KStars test
Product: valgrind
Version: 3.17.0
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity
https://bugs.kde.org/show_bug.cgi?id=455573
Hy changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=444789
Hy changed:
What|Removed |Added
CC||hymu...@gmail.com
--- Comment #1 from Hy ---
Jean-Claude
https://bugs.kde.org/show_bug.cgi?id=444789
Hy changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=458079
Hy changed:
What|Removed |Added
CC||hymu...@gmail.com
--- Comment #1 from Hy ---
What OS
https://bugs.kde.org/show_bug.cgi?id=458079
--- Comment #3 from Hy ---
(In reply to sequel.county_0d from comment #2)
> This is on astroberry version 2.0.4 so 32bit linux 5.10.103-v7l+.
>
> Kstars says 3.6.0
What type of computer? Raspberry Pi 4?
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=458079
--- Comment #5 from Hy ---
Created attachment 151457
--> https://bugs.kde.org/attachment.cgi?id=151457&action=edit
screenshot of it working fine on my system.
Works fine on my 64-bit Ubuntu on Intel mini-pc
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=458079
--- Comment #6 from Hy ---
@jasem I cannot reproduce. Of course, I'm not using the same software. I run a
64-bit Ubuntu 20.04 on an intel mini-pc (NUC). I'm not running Stellarmate OS.
Perhaps you folks can try it out on an RPi4 with 32-bit O
https://bugs.kde.org/show_bug.cgi?id=430365
--- Comment #11 from Hy ---
I was not able to reproduce this, however I did look through the code and
tightened up a couple things and am submitting merge request
https://invent.kde.org/education/kstars/-/merge_requests/430 that will
hopefully improve
https://bugs.kde.org/show_bug.cgi?id=450046
Hy changed:
What|Removed |Added
CC||hymu...@gmail.com
Assignee|mutla
https://bugs.kde.org/show_bug.cgi?id=450046
Hy changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=450046
--- Comment #3 from Hy ---
Jean-Claude, Of course, no problem making the suggestions. Appreciate any/all
of them. Please continue to do so.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432546
--- Comment #16 from Hy ---
I'd say, bottom line, you need to find the StellarSolver parameters that work
with your guide scope and guide camera. Sometimes getting stellarsolver to work
well can be tricky. (For guide, you only need the star-dete
https://bugs.kde.org/show_bug.cgi?id=432546
--- Comment #17 from Hy ---
BTW, send a fits file and I can see if I could find some parameters that work
for you.
Please keep in mind, that the presets profiles are starting points, but you can
edit and improve them for your hardware.
--
You are
https://bugs.kde.org/show_bug.cgi?id=432546
--- Comment #20 from Hy ---
You said:
but I never found any detailed instructions on how to do so
You're right, it isn't well documented. It would be great if you wrote those
instructions. I can point you in the general direction of where
https://bugs.kde.org/show_bug.cgi?id=432546
--- Comment #22 from Hy ---
I'm happy to help, and, as I suggested, you're right that it's not well
documented. If/when you do get up to speed, it would be very helpful to have
you share your experience by documenting and helping other
https://bugs.kde.org/show_bug.cgi?id=432546
Hy changed:
What|Removed |Added
CC||hymu...@gmail.com
--- Comment #3 from Hy ---
Thanks for
https://bugs.kde.org/show_bug.cgi?id=432546
--- Comment #5 from Hy ---
If you have that parameter at 4.5, then that's not the problem. No need to mess
with that. I guess I have to look further in your log...3.5.0 was when
StellarSolver got introduced, and it is used in guiding, but I th
https://bugs.kde.org/show_bug.cgi?id=432546
--- Comment #8 from Hy ---
I'm not sure what's causing your problems, but my guess is this:
with 3.5.0 came the introduction of StellarSolver. SepMultiStar relies on
stellar solver to do it star detection.
Each module, focus, guide, and a
https://bugs.kde.org/show_bug.cgi?id=432546
--- Comment #11 from Hy ---
It is my belief that the StellarSolver profiles given are not yet "mature" and
could certainly use tweaking for some systems. It may be that you need to
adjust parameters for your system, and I recognize that the
https://bugs.kde.org/show_bug.cgi?id=475185
Hy changed:
What|Removed |Added
CC||hymu...@gmail.com
--- Comment #1 from Hy ---
Jean-Claude
https://bugs.kde.org/show_bug.cgi?id=475185
Hy changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=460375
Hy changed:
What|Removed |Added
CC||hymu...@gmail.com
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=430365
Hy changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=430365
--- Comment #5 from Hy ---
(In reply to MountainAirCA from comment #3)
> Regarding the second issue I mentioned about not being able to retain the
> simulator guide star... I noticed that I also could not plate-solve. No
> location on the
https://bugs.kde.org/show_bug.cgi?id=430597
Bug ID: 430597
Summary: Valgrind crashes when trying to debug kstars
Product: valgrind
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=430597
--- Comment #2 from Hy ---
Tom,
I'm happy and motivated to supply you with as much information as you need to
debug this problem. Please bear with me and feel free to ask what you need.
Here is the output when I run valgrind.
Please let me know
https://bugs.kde.org/show_bug.cgi?id=430597
Hy changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=430597
Hy changed:
What|Removed |Added
Resolution|DUPLICATE |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=430597
--- Comment #11 from Hy ---
Thanks Tom. As I said, the program doesn't crash like that normally (without
valgrind), it is just starting up the gui, not doing much.
On a whim, I thought, perhaps this happens with all Qt programs, not just
KStar
https://bugs.kde.org/show_bug.cgi?id=430597
--- Comment #13 from Hy ---
(In reply to Paul Floyd from comment #12)
> On Fedora 33 amd64 I can run qtcreator 4.14 / Qt 5.15.2, though it does
> generate vast numbers of errors which slows execution significantly.
>
> Could you post th
https://bugs.kde.org/show_bug.cgi?id=430597
--- Comment #15 from Hy ---
Thanks Mark!
Excellent find. I tried "export LIBGL_ALWAYS_SOFTWARE=1" before running
valgrind, and yes it does now run. Excellent workaround.
I don't know if this is a VMWare issue, though can't ru
https://bugs.kde.org/show_bug.cgi?id=149930
Hy changed:
What|Removed |Added
Version Fixed In||3.7.1
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=400128
Bug ID: 400128
Summary: Ekos plate solving angle difference doesn't normalize
for 360 degrees
Product: kstars
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=400128
Hy changed:
What|Removed |Added
CC||hymu...@gmail.com
--
You are receiving this mail because
e.com/support.html?view=kb&kbartid=5
in Switching to the Beta Channel, it says "The system should not be upgraded"
I assume you mean NOW, not NOT.
Hy
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416650
Hy changed:
What|Removed |Added
CC||hymu...@gmail.com
--- Comment #4 from Hy ---
Can I ask
https://bugs.kde.org/show_bug.cgi?id=416650
--- Comment #5 from Hy ---
I just noticed that Jasem and I fixed an issue recently that would be
consistent with your stack trace. If you can retry with the latest code, it may
solve your issue.
That said, there may not yet be a "latest code&quo
https://bugs.kde.org/show_bug.cgi?id=497187
--- Comment #1 from Hy ---
Philip,
I'm not sure how to reproduce/debug this...I don't have your environment, and
it doesn't crash in other environments. Are you able to compile from source and
test? If so, I have a "shot-in-the-dar
https://bugs.kde.org/show_bug.cgi?id=497995
Hy changed:
What|Removed |Added
CC||hymu...@gmail.com
--- Comment #1 from Hy ---
Mark,
Are
https://bugs.kde.org/show_bug.cgi?id=497187
--- Comment #4 from Hy ---
It's merged now into the head of the code tree. Would be on the next nightly
build as well.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=497187
--- Comment #3 from Hy ---
Philip,
I no longer think that that change is a good idea. Sorry if you spent time
testing it. I just put i an MR with some changes and am trying to merge it
into the 3.7.5 beta tree. When it's merged, or if you ca
https://bugs.kde.org/show_bug.cgi?id=497995
Hy changed:
What|Removed |Added
Latest Commit||25d7ea35e06ed885455c48864b5
https://bugs.kde.org/show_bug.cgi?id=497995
Hy changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=500744
Hy changed:
What|Removed |Added
CC||hymu...@gmail.com
--- Comment #1 from Hy ---
Konstantin
47 matches
Mail list logo
