Freeze related to export to remote storage

[Simon Frei]

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

[Gilles Caulier-4]

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 <[hidden email]>:

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

[Simon Frei]

Ok, so if I understand you correctly this tool is just kept for legacy reasons but might even be completely removed in the future?
Is there a way to copy files from digikam to some path that is not part of any collection? For me this is an important feature (e.g. to copy a specific selection of pictures using tags/filters to a usb stick for presentation on a different computer).

On 18/12/16 13:02, Gilles Caulier wrote:

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 <[hidden email]>:

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

[Gilles Caulier-4]

use Dolphin file manager and D&D file from DK to target in Dolphin.

The tool must be re-written in fact.

Gilles Caulier

2016-12-18 13:37 GMT+01:00 Simon Frei <[hidden email]>:

Ok, so if I understand you correctly this tool is just kept for legacy reasons but might even be completely removed in the future?
Is there a way to copy files from digikam to some path that is not part of any collection? For me this is an important feature (e.g. to copy a specific selection of pictures using tags/filters to a usb stick for presentation on a different computer).

On 18/12/16 13:02, Gilles Caulier wrote:

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 <[hidden email]>:

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

[Simon Frei]

Embarassing that I did not think of that - I almost never use a file manager, but still. Thanks for your guidance.
Is it ok if I open a bug report (wishlist) asking for such a rewrite, even though this is understandably not a priority? Just to have something to refer to on the debian bugtracker.

On 18/12/16 13:38, Gilles Caulier wrote:

use Dolphin file manager and D&D file from DK to target in Dolphin.

The tool must be re-written in fact.

Gilles Caulier

2016-12-18 13:37 GMT+01:00 Simon Frei <[hidden email]>:

Ok, so if I understand you correctly this tool is just kept for legacy reasons but might even be completely removed in the future?
Is there a way to copy files from digikam to some path that is not part of any collection? For me this is an important feature (e.g. to copy a specific selection of pictures using tags/filters to a usb stick for presentation on a different computer).

On 18/12/16 13:02, Gilles Caulier wrote:

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 <[hidden email]>:

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

[Gilles Caulier-4]

Yes, its fine.

Gilles

2016-12-18 14:15 GMT+01:00 Simon Frei <[hidden email]>:

Embarassing that I did not think of that - I almost never use a file manager, but still. Thanks for your guidance.
Is it ok if I open a bug report (wishlist) asking for such a rewrite, even though this is understandably not a priority? Just to have something to refer to on the debian bugtracker.

On 18/12/16 13:38, Gilles Caulier wrote:

use Dolphin file manager and D&D file from DK to target in Dolphin.

The tool must be re-written in fact.

Gilles Caulier

2016-12-18 13:37 GMT+01:00 Simon Frei <[hidden email]>:

Ok, so if I understand you correctly this tool is just kept for legacy reasons but might even be completely removed in the future?
Is there a way to copy files from digikam to some path that is not part of any collection? For me this is an important feature (e.g. to copy a specific selection of pictures using tags/filters to a usb stick for presentation on a different computer).

On 18/12/16 13:02, Gilles Caulier wrote:

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 <[hidden email]>:

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