Summary: | after starting the INDI-Service the INDI control panel remains empty and the menu, which appears after right-mouse-click in the sky view does not show any telescope, Update problem? | ||
---|---|---|---|
Product: | [Applications] kstars | Reporter: | Stefan Kießling <info> |
Component: | general | Assignee: | kstars |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Stefan Kießling
2004-07-16 12:38:24 UTC
I have similar configuration here (SUSE 9.1, gcc 3.3.3) but don't have any problems. You said you go to device manager, click on telescope, select etx90, then click "start service". That's all you need to do. The "client" tab is connect to remote clients only or when you start an INDI server from the console. Use Ksysguard or a similar application to check KStars children after you click on "start service", does it have an indiserver child with an lx200autostar grandchild? At any rate, KDE 3.3 adds a server log that will alert you if the INDI server fails to start for any reason. Am Samstag, 17. Juli 2004 00:01 schrieb Jasem Mutlaq: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=85322 > > > > > ------- Additional Comments From mutlaqja ikarustech com 2004-07-17 00:01 > ------- I have similar configuration here (SUSE 9.1, gcc 3.3.3) but don't > have any problems. > > You said you go to device manager, click on telescope, select etx90, then > click "start service". That's all you need to do. > > The "client" tab is connect to remote clients only or when you start an > INDI server from the console. > > Use Ksysguard or a similar application to check KStars children after you > click on "start service", does it have an indiserver child with an > lx200autostar grandchild? Yes, it has both. It's almost been a year since this bug was reported. Do you experience this bug in KDE 3.4 or HEAD? No more reports or additional information for this bug. Please close the bug as WORKSFORME. closed |