Freeze related to export to remote storage

[Gilles Caulier]

It miss in AppImage because it use KIO which use a lots of run time
dependencies not solvable with AppImage. Also, KIO do not work under OSX
and Windows. So, for me there is no future of KIO in digiKam. digiKam will
become more and more a pure Qt application.

Typically, we drop all KIO dependencies in digiKam & co excepted this one.
We don't have planed to port this tool as pure Qt5 implementation.

Do no ask me which run time dependency is missing. KIO is a waste of time
to work properly. I lost more weeks to try to bundle this tool in all
digiKam bundles.

Gilles Caulier

2016-12-18 12:27 GMT+01:00 Simon Frei <freisim93 at gmail.com>:

> Hi
>
> When I use debian packages or compile digikam myself, it freezes when on
> clicking "Select target location..." in the "Export o Remote Storage"
> dialog. The message on the console is GLib/Gdk related, so I assumed it is
> a debian dependency issue. I tried to verify this by using the appimage
> (5.4.0-01), but there is no "Export to remote storage..." entry in the
> "Export" menu there. So what is the status of that tool, i.e. why is it
> missing in the appimage?
>
> For reference this is the command line output on freeze:
>
> (digikam:2410): GLib-GObject-WARNING **: cannot register existing type
> 'GdkWindow'
>
> (digikam:2410): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0'
> failed
>
> (digikam:2410): Gdk-CRITICAL **: gdk_window_ensure_native: assertion
> 'GDK_IS_WINDOW (window)' failed
>
> and the backtrace: http://pastebin.com/xLSevGhy
>
> Cheers,
> Simon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20161218/1ea35ca6/attachment.html>