I have a 2009 FLI filter wheel, CFW-2-7. It is connecting via USB and is visible on the system, and in fact it gets a good ways through the connection process before crashing. Here are the last few lines output by kstyars before crashing:

org.kde.kstars.ekos: "FLI CCD is online."
org.kde.kstars.indi: FLI CFW : "[INFO] Connecting to FLI CFW..."
org.kde.kstars.indi: FLI CFW : "[INFO] Filter wheel is online. Retrieving basic data. "
org.kde.kstars.ekos: "FLI CFW filter is online."
QObject::disconnect: Unexpected null parameter
Segmentation fault


Earlier it logged this:

org,kde.kstars.ekos: Ekos received a new device: "FLI CFW"
Dispatch command error(-1):
<setTextVector device="FLI CFW" name="Model" state="Idle" timeout="60" timestamp="2020-09-15T05:12:01">
<oneText name="Model">
CFW-2-7
</oneText>
<oneText name="HW Rev">
0
</oneText>
<oneText name="FW Rev">
32768
</oneText>
</setTextVector>


Have you seen this before??

Wayne

So KStars crashing is something different, can you please installed ekos-debugger and run KStars from there? Then you'll get logs with backtraces that can be useful to investigate this.

Here are the brief logs I captured:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0xaf773090 (LWP 1953)]
[New Thread 0xa9ebd090 (LWP 1954)]
[New Thread 0xa8f45090 (LWP 1955)]
[New Thread 0xa6f44090 (LWP 1956)]
[New Thread 0xa4dff090 (LWP 1957)]
[New Thread 0xa1ff4090 (LWP 1958)]
[New Thread 0xa0ccc090 (LWP 1959)]
[New Thread 0xa04cb090 (LWP 1960)]
[New Thread 0x9fcca090 (LWP 1961)]
[New Thread 0x9f4c9090 (LWP 1962)]
[New Thread 0x9ecc8090 (LWP 1963)]
[New Thread 0x9dfac090 (LWP 1964)]
[New Thread 0x9bfab090 (LWP 1965)]
[Thread 0x9bfab090 (LWP 1965) exited]
[Thread 0xa0ccc090 (LWP 1959) exited]
[New Thread 0xa0ccc090 (LWP 1970)]
Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0x006e9f68 in Ekos::FilterManager::initFilterProperties (this=this@entry=0x2beeca0) at ./kstars/oal/filter.h:44
#0 0x006e9f68 in Ekos::FilterManager::initFilterProperties (this=this@entry=0x2beeca0) at ./kstars/oal/filter.h:44
#1 0x006ea154 in Ekos::FilterManager::initFilterProperties (this=0x2beeca0) at ./kstars/ekos/auxiliary/filtermanager.cpp:237
#2 Ekos::FilterManager::setCurrentFilterWheel (this=0x2beeca0, filter=0x36ed910) at ./kstars/ekos/auxiliary/filtermanager.cpp:232
#3 0x0070173c in Ekos::Capture::checkFilter (this=this@entry=0x3ae6d28, filterNum=, filterNum@entry=1) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qsharedpointer_impl.h:312
#4 0x007086e4 in Ekos::Capture::addFilter (this=0x3ae6d28, newFilter=newFilter@entry=0x36ed910) at ./kstars/ekos/capture/capture.cpp:475
#5 0x006be654 in Ekos::Manager::setFilter (this=0x35e20f8, filterDevice=<optimized out>) at /usr/include/c++/8/bits/unique_ptr.h:342
#6 0xb4b68380 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#7 0x0060989e in INDIListener::newFilter (this=this@entry=0x38215d0, _t1=) at ./obj-arm-linux-gnueabihf/kstars/KStarsLib_autogen/FRI4DANIHA/moc_indilistener.cpp:415
#8 0x00670702 in INDIListener::registerProperty (this=0x38215d0, prop=0xa9542630) at ./kstars/indi/indilistener.cpp:282
#9 0xb4b64c68 in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#10 0xb4b68bec in QObject::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#11 0xb545ddb4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#12 0xb54662a8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#13 0x038215d0 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0xaf773090 (LWP 1981)]
[New Thread 0xa9ebd090 (LWP 1982)]
[New Thread 0xa8fad090 (LWP 1983)]
[New Thread 0xa6fac090 (LWP 1984)]
[New Thread 0xa4dff090 (LWP 1985)]

This might be a clue...

I have only specified FLI CFW as the filter device. I have never set any properties, like number of filter slots or names of filters. I could not find any place in the UI to do that. Maybe this is a simple problem.

Wayne

I believe I found one possible way this can crash and submitted a fix. Please try again in the next nightly or compile KStars from GIT.

Hi Jasem,

I am stuck updating to the nightly build. This method doesn't seem to be working:

sudo apt-add-repository ppa:mutlaqja/indinightly
sudo apt-get update
sudo apt-get install indi-full kstars-bleeding

First, apt-add-repository was not present on the Stellarmate device, so I added it with:

sudo apt-get install software-properties-common

Now that apt-add-repository is there, I get an error adding the repo: "could not find a distribution template for Raspbian/buster"

Are there different instructions for getting the nightly build on this device? Or can I download binaries and drag them into the right spots?

Wayne

For StellarMate, the PPA will not work. Wait for tonight update in a few hours it will be out.

Where should I look for download/install instructions? If not the PPA then is there a place to fetch the build output?

I’ve hunted for Stellarmate update instructions but haven’t found any useful hints.

Thanks for the help.

Wayne

I found instructions for Raspberry Pi but they resulted in a pre-release build from 08-29 being installed.

www.indilib.org/download/

This is the only place where I have found any information about updating a Raspberry Pi. Where do I go to fetch the latest bleeding-edge build? Or should I just try to build from source on the Pi?

Wayne

Also, I am generally operating Stellarmate from kstars on a Mac. Maybe it would be easier to fetch the nightly build for Mac OS?

Wayne

Great timing. I submitted this a couple days ago - same problem:

invent.kde.org/education/kstars/-/issues/39

Looks like the fix Jasem put in may have got it working. Will continue testing.

I am now watching the entire universe rebuild from source on my Mac. Hopefully I will be able to test tonight as well. I am brand new to the community and the underlying frameworks. Plenty of learning curve ahead.

Wayne