[digikam] [Bug 382649] New: Save As button freezes on second call

[Mário Pereira]

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

            Bug ID: 382649
           Summary: Save As button freezes on second call
           Product: digikam
           Version: 5.6.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: ImageEditor
          Assignee: digikam-devel at kde.org
          Reporter: bin.to.hex+kde at gmail.com
  Target Milestone: ---

When editing CR2 files, the Save As button works ok on the first image that I
edit after opening digikam. When I go to edit the second CR2 file, when
clicking Save As, the button stays pressed and digikam stops responding,
requiring a force close.

The following is displayed in the console when saving the first image:
---

digikam.general: startSavingAs called

(digikam:18368): Gtk-CRITICAL **: gtk_file_chooser_default_set_current_name:
assertion 'impl->action == GTK_FILE_CHOOSER_ACTION_SAVE || impl->action ==
GTK_FILE_CHOOSER_ACTION_CREATE_FOLDER' failed

(digikam:18368): GLib-GObject-WARNING **: cannot register existing type
'GdkWindow'

(digikam:18368): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0'
failed

(digikam:18368): GLib-GObject-CRITICAL **: g_type_register_static: assertion
'parent_type > 0' failed

(digikam:18368): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0'
failed

---
After this, the Save As dialog appears and the file can be saved.
On the second call, only this is displayed in the console and digikam stops
responding:
---

digikam.general: startSavingAs called

(digikam:18368): Gtk-CRITICAL **: gtk_file_chooser_default_set_current_name:
assertion 'impl->action == GTK_FILE_CHOOSER_ACTION_SAVE || impl->action ==
GTK_FILE_CHOOSER_ACTION_CREATE_FOLDER' failed

---
This is pretty anoying, as it forces to close and re-open digikam after each
file, not the ideal thing to do when you have 200 photos to process.

-- 
You are receiving this mail because:
You are the assignee for the bug.