[kstars] [Bug 500506] New: GPhoto on MacOS: Camera open error (-4): Error loading a library

Bastian bugzilla_noreply at kde.org
Fri Feb 21 05:53:30 GMT 2025


https://bugs.kde.org/show_bug.cgi?id=500506

            Bug ID: 500506
           Summary: GPhoto on MacOS: Camera open error (-4): Error loading
                    a library
    Classification: Applications
           Product: kstars
           Version: 3.7.5
          Platform: macOS (DMG)
                OS: macOS
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: mutlaqja at ikarustech.com
          Reporter: bastian at blankenburg.net
  Target Milestone: ---

Created attachment 178677
  --> https://bugs.kde.org/attachment.cgi?id=178677&action=edit
KStars/Ekos verbose log for INDI and CCD

SUMMARY


STEPS TO REPRODUCE
1. Ensure that ptpcamerad isn't running and mounting cameras.
2. Connect Olympus E-M5 II to computer running KStars. 
3. Configure local INDI server with GPhoto CCD driver.
4. Try to start INDI server and connect.

OBSERVED RESULT
Camera doesn't connect, INDI log shows
```
2025-02-21T05:31:10: [ERROR] Can not open camera: Power OK? If camera is
auto-mounted as external disk storage, please unmount it and disable
auto-mount. 
2025-02-21T05:31:10: [ERROR] Camera open error (-4): Error loading a library 
```

EXPECTED RESULT
Camera connects fine.

SOFTWARE/OS VERSIONS
macOS: Sonoma 14.7.1

ADDITIONAL INFORMATION
I've enabled verbose logging for Ekos -> INDI and Drivers -> CCD, and attached
the log file here.

In my old KStars version (3.6.8), I could connect my Olympus E-M5 II just fine
(using a script which periodically kills ptpcamerad every 0.1 seconds to
prevent it from mounting the camera, and which I also ran for the new versin). 

The old Kstars used libindi 2.0.5, while the new one uses 2.1.2. 

I also saw the same issue with the IndiStarter app: an old version that came
with libindi 2.0.2 worked fine, but the new one which bundles 2.1.2 does not,
showing the same error. So I think it's a libindi issue with was introduced
somewhere between 2.0.5 and 2.1.2.

-- 
You are receiving this mail because:
You are watching all bug changes.



More information about the kde-mac mailing list