Bug 497271 - Recent Files or Recent Locations doesn't load when using file picker.
Summary: Recent Files or Recent Locations doesn't load when using file picker.
Status: RESOLVED DUPLICATE of bug 495974
Alias: None
Product: xdg-desktop-portal-kde
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.2.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-10 12:08 UTC by caceko8579@lofiey
Modified: 2024-12-10 13:30 UTC (History)
2 users (show)

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


Attachments
Picture of the bug (59.83 KB, image/png)
2024-12-10 12:08 UTC, caceko8579@lofiey
Details
Video of the bug and how it disappears when a new app is opened (2.12 MB, video/mp4)
2024-12-10 12:10 UTC, caceko8579@lofiey
Details

Note You need to log in before you can comment on or make changes to this bug.
Description caceko8579@lofiey 2024-12-10 12:08:36 UTC
Created attachment 176488 [details]
Picture of the bug

SUMMARY
When file picker is invoked and I navigate to Recent FIles or Recent Locations, the cursor keeps spinning with nothing showing up. There is also a progress bar at the bottom with 0%.

STEPS TO REPRODUCE
1. Open Kwrite (or any other app).
2. Invoke file picker to open a file from the menu (CTRL + o) 
3. Go to Recent Files or Recent Locations

OBSERVED RESULT
Nothing loads, cursor keep spinning, file picker bottom has a progress bar with 0%

EXPECTED RESULT
Recent Files and Locations to show up.

SOFTWARE/OS VERSIONS
Linux: Fedora Linux 41
Kernel: 6.11.10-300.fc41.x86_64 (64-bit)
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0

ADDITIONAL INFORMATION
When noting is loading up, open any other app. Suddenly the Recent Files shows up as expected.
Comment 1 caceko8579@lofiey 2024-12-10 12:10:17 UTC
Created attachment 176489 [details]
Video of the bug and how it disappears when a new app is opened
Comment 2 David Edmundson 2024-12-10 13:30:26 UTC

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