Created attachment 173176 [details] indi log *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Have two nikon cameras connected via usb to the computer running Kstars 3.7.1 With the update to 3.7.1 from 3.7.0 only one camera can connect at ones. By deactivating the successfully connected camera in indi settings the other one can be activated and used. Suspect a introduced bug, perhaps in indi_nikon_ccd ? but really don't not at all. This bug makes Kstars quite useless for guided astrophoto for me. STEPS TO REPRODUCE 1. see summary 2. 3. OBSERVED RESULT See summary EXPECTED RESULT SOFTWARE/OS VERSIONS Linux astrodatorn 6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 2 20:41:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux 3.7.1 stable ADDITIONAL INFORMATION deleted /usr/libexec/gvfs-mtp-volume-monitor /usr/libexec/gvfs-gphoto2 /usr/libexec/gvfs-gphoto2-volume-monitor and rebooted. There is no mounting of cameras going on. bb@astrodatorn:~$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 04b0:0412 Nikon Corp. D80 (MTP/PTP mode) Bus 002 Device 003: ID 04b0:0439 Nikon Corp. NIKON DSC D7200 Bus 002 Device 004: ID 067b:23a3 Prolific Technology, Inc. ATEN Serial Bridge Bus 002 Device 005: ID 8087:07dc Intel Corp. Bluetooth wireless interface Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub bb@astrodatorn:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 21,7M 1 loop /snap/4ktube/84 loop1 7:1 0 21,9M 1 loop /snap/4ktube/90 loop2 7:2 0 4K 1 loop /snap/bare/5 loop3 7:3 0 10,1M 1 loop /snap/canonical-livepatch/278 loop4 7:4 0 10,1M 1 loop /snap/canonical-livepatch/282 loop5 7:5 0 104,2M 1 loop /snap/core/17200 loop6 7:6 0 55,7M 1 loop /snap/core18/2823 loop7 7:7 0 55,7M 1 loop /snap/core18/2829 loop8 7:8 0 63,9M 1 loop /snap/core20/2264 loop9 7:9 0 63,9M 1 loop /snap/core20/2318 loop10 7:10 0 74,3M 1 loop /snap/core22/1564 loop11 7:11 0 74,3M 1 loop /snap/core22/1586 loop12 7:12 0 66,2M 1 loop /snap/core24/423 loop13 7:13 0 66,2M 1 loop /snap/core24/490 loop14 7:14 0 6,4M 1 loop /snap/curl/1754 loop15 7:15 0 80,1M 1 loop /snap/ffmpeg/1286 loop16 7:16 0 269,3M 1 loop /snap/firefox/4757 loop17 7:17 0 10,7M 1 loop /snap/firmware-updater/127 loop18 7:18 0 349,7M 1 loop /snap/gnome-3-38-2004/143 loop19 7:19 0 269,8M 1 loop /snap/firefox/4793 loop20 7:20 0 504,2M 1 loop /snap/gnome-42-2204/172 loop21 7:21 0 16M 1 loop /snap/gphoto2/8 loop22 7:22 0 505,1M 1 loop /snap/gnome-42-2204/176 loop23 7:23 0 140K 1 loop /snap/gtk2-common-themes/13 loop24 7:24 0 91,7M 1 loop /snap/gtk-common-themes/1535 loop25 7:25 0 450,2M 1 loop /snap/kf5-5-108-qt-5-15-10-core22/5 loop26 7:26 0 101,5M 1 loop /snap/p7zip-desktop/220 loop27 7:27 0 162,1M 1 loop /snap/pyqt5-runtime-core20/9 loop28 7:28 0 12,9M 1 loop /snap/snap-store/1113 loop30 7:30 0 38,7M 1 loop /snap/snapd/21465 loop31 7:31 0 38,8M 1 loop /snap/snapd/21759 loop32 7:32 0 476K 1 loop /snap/snapd-desktop-integration/157 loop33 7:33 0 183,7M 1 loop /snap/spotify/77 loop34 7:34 0 500K 1 loop /snap/snapd-desktop-integration/178 loop35 7:35 0 181,8M 1 loop /snap/spotify/78 loop36 7:36 0 693,4M 1 loop /snap/stellarium-daily/1799 loop37 7:37 0 672,2M 1 loop /snap/stellarium-daily/1724 loop38 7:38 0 64M 1 loop /snap/sublime-text/156 loop39 7:39 0 63,9M 1 loop /snap/sublime-text/177 loop40 7:40 0 149,6M 1 loop /snap/thunderbird/507 loop41 7:41 0 321,1M 1 loop /snap/vlc/3721 loop42 7:42 0 321,1M 1 loop /snap/vlc/3777 loop43 7:43 0 10,5M 1 loop /snap/snap-store/1173 sda 8:0 0 111,8G 0 disk ├─sda1 8:1 0 512M 0 part /boot/efi └─sda2 8:2 0 111,3G 0 part /var/snap/firefox/common/host-hunspell /
I experienced this as well but with one Nikon and Canon camera connected. It used to work fine. I suspect it's more libgphoto2 issue that caused this.
It was indeed an INDI Driver issue (not KStars). Please update from GIT and it should be resolved.
(In reply to Jasem Mutlaq from comment #2) > It was indeed an INDI Driver issue (not KStars). Please update from GIT and > it should be resolved. Great to have that resolved. I will se if I can learn how to do that. Otherwise I have to wait for the 2.10 release if it will make it or the next. Thanks for looking in to this! Björn
Hi, I did build and installed indilib from git. It did not work with kstars. the Nikon driver crashed all the time. Bad thing I could not go back to the stable version so I hade to reinstall the entire linux installation, but that just me not knowing better. Any thoughts on when the stable version driver will work with the kstars dito? Best regards Björn
Did you make sure to install INDI then INDI-3rdparty afterwards? The stable driver would be released on Oct 1st.
(In reply to Jasem Mutlaq from comment #5) > Did you make sure to install INDI then INDI-3rdparty afterwards? The stable > driver would be released on Oct 1st. I did do "sudo apt-reg reinstall kstars-bleeding" afterwards. Didn't work. Nikon driver still crashed (and eqmod as well). Gave up and then tried to go back to last working by sudo apt-get remove indi-full kstars-bleeding gsc followed by sudo apt-get install indi-full kstars-bleeding gsc But the drivers still crashed. I could not figure out how to revert from the git installation. Then I reinstalled a fresh install of Ubuntu 24.04 LTS. Did need to move from ubuntu to xubuntu anyway. gnome was to taxing of the hardware. Cheers/Björn
(In reply to Björn Bergman from comment #6) > (In reply to Jasem Mutlaq from comment #5) > > Did you make sure to install INDI then INDI-3rdparty afterwards? The stable > > driver would be released on Oct 1st. > > I did do "sudo apt-reg reinstall kstars-bleeding" afterwards. Didn't work. > Nikon driver still crashed (and eqmod as well). > Gave up and then tried to go back to last working by > sudo apt-get remove indi-full kstars-bleeding gsc > followed by > sudo apt-get install indi-full kstars-bleeding gsc > But the drivers still crashed. > I could not figure out how to revert from the git installation. > > Then I reinstalled a fresh install of Ubuntu 24.04 LTS. > Did need to move from ubuntu to xubuntu anyway. gnome was to taxing of the > hardware. > > Cheers/Björn Aha, Is see. No I didn't understand I should have installed INDI-3rdparty from git afterwards... my bad!