I added debuginfo for glibc and reran ekosdebugger. Hopefully this provides useful additional information. Log files attached.
Read More...
Yes! I'd be happy to install whatever it takes. Sorry about the inconvenience; my goto distribution is Fedora and I wasn't aware that debugging would be more difficult there. But I have a dedicated laptop that can be used to iron this out so I don't mind adding a lot of debugging packages.
Read More...
Ok, it's hard to keep up with you guys! I'm attaching backtrace logs using both the command line suggestion from the moderator as well as from a newly updated ekosdebugger just to be sure I have the correct tools. I updated my ekosdebugger via dnf to version ekosdebugger-0.0.1.git-20201015134612.fc33.x86_64.
From command line. Just to verify: I issued the gdb command, then from elsewhere, I started kstars, loaded the joystick profile, and performed a connection upon which the joystick driver crashed. I then went back to the command line and cut and pasted the resulting backtrace:
Using the updated ekosdebugger, I obtained the following:
I hope this was helpful. Let me know.
Read More...
Following those instructions on my Fedora 33 system, these app and debug logs were generated:
Read More...
As a follow up, per the suggestion from xsnrg I added debuginfo for q5-qtbase with the command: sudo dnf --enablerepo=fedora-debuginfo install qt5-qtbase-debuginfo
which will hopefully provide additional information.
running the gdb backtrace analysis as described here,
fedoraproject.org/wiki/StackTraces
, I get the attached backtrace log file:
Read More...
Thanks for that dnf suggestion. Here's the backtrace log with those rpms installed.
Incidentally, I'm using the following to create the logs:
gdb
> run
# program crashes
> set logging file backtrace.log
> set logging on
> thread apply all bt full
> set logging off
> quit
This is from here: fedoraproject.org/wiki/StackTraces
Read More...
Ok. Keep in mind I only installed debuginfo rpms for kstars and indi. Not the QT libraries. So if the problem is in how kstars interacts with QT, I'm guessing my backtrace won't help you .
Read More...
Unfortunately still crashing in F33. See gdb log file. I did have to add the stellarsolve repo for a new dependency.
File Attachment:
File Name: backtrace_kstars-3.5.0.git-20201014175318.fc33.x86_64_2020-10-14.logFile Size: 4 KB
Read More...
Wow! That's cool. Thanks for the quick response. I'll install as soon as it's ready and report back. And yes, I'm using that repo.
Read More...
Hello-
I am experiencing an instant segmentation fault when I try to start kstars on a Fedora 33 system. Both stable and bleeding packages have this issue. I am attaching a backtrace log file. Please let me know if there is anything further I can do to help.
Thank you.
Read More...
Ok, This is for the bleeding edge git installation. (Stable installation is on another computer by the way, with the same result). And disconnecting the joystick eliminates the crash.
Let me know if I can provide any other assistance.
Thank you.
Read More...
Hello. I am experiencing driver crashes when I connect a Logitech F310 joystick/gamepad under Linux and Ekos. This is with both stable and bleeding edge kstars indi library versions. Device is established under /dev/input/js0.
The crash is instantaneous as soon as I hit connect.
logging outputs:
EKOS logfile:
[2020-10-13T20:11:43.063 EDT DEBG ][ org.kde.kstars.ekos] - Resetting Ekos Manager...
[2020-10-13T20:11:43.085 EDT INFO ][ org.kde.kstars.ekos] - "Starting INDI services..."
[2020-10-13T20:11:43.196 EDT INFO ][ org.kde.kstars.ekos] - "INDI services started on port 7624. Please connect devices."
[2020-10-13T20:11:43.206 EDT INFO ][ org.kde.kstars.ekos] - Ekos received a new device: "Telescope Simulator"
[2020-10-13T20:11:43.263 EDT INFO ][ org.kde.kstars.ekos] - Ekos received a new device: "CCD Simulator"
[2020-10-13T20:11:43.282 EDT INFO ][ org.kde.kstars.ekos] - Ekos received a new device: "Joystick"
[2020-10-13T20:11:46.490 EDT CRIT ][ org.kde.kstars.indi] - INDI driver "indi_joystick" crashed!
[2020-10-13T20:11:46.505 EDT INFO ][ org.kde.kstars.ekos] - "Joystick is offline."
[2020-10-13T20:11:46.508 EDT DEBG ][ org.kde.kstars.ekos] - Resetting Ekos Manager...
joystick logfile:
INFO 0.000927 sec : Session log file /home/matlis/.indi/logs/2020-10-14/indi_joystick/indi_joystick_00:22:26.log
DEBUG 34.442455 sec : Configuration successfully saved.
DEBUG 35.993195 sec : Toggle Debug Level -- Driver Debug
DEBUG 35.993239 sec : Toggle Logging Level -- Driver Debug
INFO 35.993271 sec : Session log file /home/matlis/.indi/logs/2020-10-14/indi_joystick/indi_joystick_00:22:26.log
DEBUG 35.993329 sec : Configuration successfully loaded.
INFO 43.278013 sec : Joystick is online.
I have the joystick set to the "xinput" mode (there is a button on the back to set either xinput or directinput) although the driver crashes at either setting.
jstest /dev/input/js0 confirms that the Linux driver is responding to command inputs from the joystick.
Please advise, thank you!
Read More...
Hello. I am experiencing driver crashes when I connect a Logitech F310 joystick/gamepad under Linux and Ekos. This is with both stable and bleeding edge kstars indi library versions. Device is established under /dev/input/js0.
The crash is instantaneous as soon as I hit connect.
logging outputs:
EKOS logfile:
[2020-10-13T20:11:43.063 EDT DEBG ][ org.kde.kstars.ekos] - Resetting Ekos Manager...
[2020-10-13T20:11:43.085 EDT INFO ][ org.kde.kstars.ekos] - "Starting INDI services..."
[2020-10-13T20:11:43.196 EDT INFO ][ org.kde.kstars.ekos] - "INDI services started on port 7624. Please connect devices."
[2020-10-13T20:11:43.206 EDT INFO ][ org.kde.kstars.ekos] - Ekos received a new device: "Telescope Simulator"
[2020-10-13T20:11:43.263 EDT INFO ][ org.kde.kstars.ekos] - Ekos received a new device: "CCD Simulator"
[2020-10-13T20:11:43.282 EDT INFO ][ org.kde.kstars.ekos] - Ekos received a new device: "Joystick"
[2020-10-13T20:11:46.490 EDT CRIT ][ org.kde.kstars.indi] - INDI driver "indi_joystick" crashed!
[2020-10-13T20:11:46.505 EDT INFO ][ org.kde.kstars.ekos] - "Joystick is offline."
[2020-10-13T20:11:46.508 EDT DEBG ][ org.kde.kstars.ekos] - Resetting Ekos Manager...
joystick logfile:
INFO 0.000927 sec : Session log file /home/matlis/.indi/logs/2020-10-14/indi_joystick/indi_joystick_00:22:26.log
DEBUG 34.442455 sec : Configuration successfully saved.
DEBUG 35.993195 sec : Toggle Debug Level -- Driver Debug
DEBUG 35.993239 sec : Toggle Logging Level -- Driver Debug
INFO 35.993271 sec : Session log file /home/matlis/.indi/logs/2020-10-14/indi_joystick/indi_joystick_00:22:26.log
DEBUG 35.993329 sec : Configuration successfully loaded.
INFO 43.278013 sec : Joystick is online.
I have the joystick set to the "xinput" mode (there is a button on the back to set either xinput or directinput) although the driver crashes at either setting.
jstest /dev/input/js0 confirms that the Linux driver is responding to command inputs from the joystick.
Please advise, thank you!
Read More...