Bug 483123 - [Regression] Gwenview Removed Compatibility with XDG Specification
Summary: [Regression] Gwenview Removed Compatibility with XDG Specification
Status: RESOLVED DUPLICATE of bug 482141
Alias: None
Product: gwenview
Classification: Applications
Component: general (show other bugs)
Version: 24.02.0
Platform: Arch Linux Other
: NOR normal
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-10 15:34 UTC by John
Modified: 2024-03-11 08:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description John 2024-03-10 15:34:32 UTC 
PROBLEM:
[Regression] Gwenview Removed Compatibility with xdg Specification

REPLICATE:
1. Open Gwenview
2. Press ctrl+shift+f
3. Set slideshow to "loop"
4. Press "play" to play slideshow

WHAT HAPPENS:
1. WAS (KDE 5)= Slideshow could go on for hours.
2. IS (Current KDE 6) = Slideshow doesn't work. Screens goes blank and computer locks (SDDM login screen).

EXPECTED RESULTS:
Fix the regression by "invoking xdg rules", i.e. by stopping the screen to go blank and stopping the lock screen to activate while the sildeshow plays. Just like it happens on every video player. It used to work on KDE 5. Now it doesn't on KDE 6.


INFO:
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Graphics Platform: X11
Graphics Processor: Intel Only
Comment 1 Tim Carr 2024-03-11 00:06:04 UTC 
Confirmed, probably related to bug 481481, seems Gwenview is inhibiting the screenlocker when the slideshow is inactive, and not inhibiting it when slideshow is active.
Comment 2 Tim Carr 2024-03-11 07:00:09 UTC 
Forgot to include my system info.

Operating System: Arch Linux 
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Gwenview Version: 24.02.0
Comment 3 Nicolas Fella 2024-03-11 08:54:50 UTC 

*** This bug has been marked as a duplicate of bug 482141 ***