[Digikam-devel] [Bug 192437] New: Insulate digiKam from geolocation crashes in Marble

[DGardner]

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

           Summary: Insulate digiKam from geolocation crashes in Marble
           Product: digikam
           Version: 0.10.0
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel at kde.org
        ReportedBy: dkde at gardnersworld.org


Version:           0.10.0 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

I'm classifying this as a wish, because I see other bug reports about
digiKam crashes in the geolocation code that have been rejected as a
problem for the Marble widget.

I installed 0.10.0 on the weekend for the first time and was taken
aback at how shockingly unstable it was. I even had a run of five
crashes and restarts in less than two minutes. If I don't show the
right-hand Marble geolocation panel, things are more stable. Other
bug reports have reported crashes and these have been attributed
to bugs in the Marble project and therefore not applicable to
digiKam.

As geolocation is one of the nice new features, I want to be able
to use it, but the crashing problem is too severe. I cannot think
of any application I have used in the last twenty years that has
crashed so often. Until I found out it was probably a Marble issue,
I was ready to ditch digiKam 0.10.0 as an alpha-quality release
that I should never have installed.

Is there any way that digiKam can insulate itself better from these
kinds of crashes in its dependent libraries or widgets? Even if the
best it could do was report that, "Marble has crashed and cannot be
used until digiKam has been restarted." That would be better than
the current situation where digiKam crashes every few minutes.

Even without viewing Marble, 0.10.0 crashes too often (a few times
per hour), so some defensive approach to these crashes would be great
if it is at all possible. Things are so bad that I'll have to build a
debug version of digiKam from source and always run it under gdb to
be able to capture all of the back-traces and report the crashes
more accurately. I'll probably do that next weekend in the hope that
you can fix them in 0.10.1.

When is 0.10.1 coming out? The release plan is gone from the digiKam
site. Even when it wasn't very accurate, it at least gave users some
impression that improvements were in the works. I really appreciated
the developers communicating that information and I miss it now.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.