Summary: | Crash on startup - unknown reason | ||
---|---|---|---|
Product: | [Applications] marble | Reporter: | Mark Purcell <msp> |
Component: | general | Assignee: | marble-bugs |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Mark Purcell
2008-12-20 05:03:28 UTC
I have worked this through I think I know what is occurring. digikam blocks on marble, which blocks on gpsd which blocks awaiting my GPS device to provide current coordinates. Setup: I have a bluetooth GPS device which I have configured GPS to provide location services to any applications who request them, via gpsd. Marble on startup checks to see if location services are available via the gpsd socket, and if so presents your current location on the marble maps. digikam calls marble api on startup and does block if marble is blocking. Tests: gpsd running, bluetooth gps device off: 1. digikam crashes on startup. (after a delay) 2. marble starts slowly on command line, but is not responsive gpsd running, bluetooth gps device on: 1. digikam startup is good, and causes marble/ gpsd to make bluetooth connection - my location is displayed on embedded marble globe in digikam - excellent ;-) 2. marble startup is good - location showed on globe. disable gpsd: 1. digikam startup is good & quick. 2. marble startup is good & quick. - no location services (as expected) possible fixes: 1. ensure digikam doesn't block on marble issues 2. ensure marble doesn't block on gpsd issues. Marble are tracking this issue as: https://bugs.kde.org/show_bug.cgi?id=171548 Yes, it's a crash in Marble. Re-assigned. Gilles Caulier *** This bug has been marked as a duplicate of bug 171548 *** |