Bug 2255516 - Digikam buggy on Fedora w/ Gnome (default workstation)
Summary: Digikam buggy on Fedora w/ Gnome (default workstation)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: digikam
Version: 39
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-21 13:22 UTC by gil@cukie.me
Modified: 2024-11-27 22:27 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 22:27:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 468980 0 NOR UNCONFIRMED Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppIm... 2023-12-22 14:05:00 UTC

Description gil@cukie.me 2023-12-21 13:22:30 UTC
Attempting to close certain Settings windows in digikam causes the screen to flicker and the application to freeze, making it unusable.

From journalctl, I saw that there were some wayland compatibility error messages. E.g.

Dec 21 07:52:56 fedora digikam[50990]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

I'm not sure if that's a red herring, but after some digging [1] I found that starting digikam with `-platform xcb` fixed the issues. The linked thread makes it sound like QT won't fix issues with QT5. Would it make sense to default to `-platform xcb` on Fedora Gnome (maybe other desktop environments too, I'm a bit out of my depth)?

[1](https://discussion.fedoraproject.org/t/bug-with-qt-software-digikam-texstudio/74839/2)

Reproducible: Always

Steps to Reproduce:
1. Launch digikam
2. Navigate to Settings -> Configure Digikam
3. Close the Settings window, using the X icon in the top right
Actual Results:  
Flickering Settings page. App freezes.

Expected Results:  
Settings page is closed. App does not freeze.

Comment 1 nucleo 2023-12-21 16:04:29 UTC
What version of digikam is installed?

Can you, please, report bug on
https://bugs.kde.org/enter_bug.cgi?format=guided&product=digikam

Comment 2 gil@cukie.me 2023-12-22 03:02:38 UTC
Version 8.2.0

Created a bug at https://bugs.kde.org/show_bug.cgi?id=478861

Comment 3 nucleo 2024-03-15 20:18:04 UTC
Can you, please check digikam 8.3.0 from updates-testing?

Comment 4 gil@cukie.me 2024-05-07 00:11:08 UTC
Hi, sorry for the late response. I can still reproduce on F39 with version 8.3.0

Comment 5 Aoife Moloney 2024-11-13 10:18:50 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Aoife Moloney 2024-11-27 22:27:34 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.