SUMMARY When I save or open files with the KDE file picker and there's a pdf in any of the folders I explore, whenever I hover the pdf file, the file selector exits without selecting or saving anything. STEPS TO REPRODUCE 1. Open a file using the file picker 2. move to a folder containing a pdf 3. hover the pdf with the mouse OBSERVED RESULT The file selector terminates and no file has been selected EXPECTED RESULT The file selector doesn't terminate until I close it, or I select a file. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.13.7-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION I tried with falkon, chromium and firefox (with the portal). They all do as described earlier in the report. I just tried with Gwenview, and the file selector disappears temporarily, and then i can use it normally.
If something exited abnormally, it may have crashed. We need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks!
Created attachment 179622 [details] attachment-711566-0.html There's no entry for the file selector in coredumpctl --reverse When I do the procedure with chromium launched from a terminal I get this message [79061:79061:0321/071937.952883:ERROR:request.cc(165)] Request cancelled by user. so I guess the file selector understands "hovering a pdf" as "cancel". The only difference I noticed with pushing cancel is that, when i hover a pdf there's a bouncy cursor notification after the selector closes. Le 21/03/2025 à 01:50, TraceyC a écrit : > https://bugs.kde.org/show_bug.cgi?id=501787 > TraceyC > [<kdedev@tlcnet.info>](mailto:kdedev@tlcnet.info) > changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > CC| | > kdedev@tlcnet.info > --- Comment #1 from TraceyC > [<kdedev@tlcnet.info>](mailto:kdedev@tlcnet.info) > --- > If something exited abnormally, it may have crashed. We need a backtrace of it > so we can figure out what's going on. Can you please attach a backtrace of the > crash using the coredumpctl command-line program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > ? > > Thanks! > > -- > You are receiving this mail because: > You reported the bug.
Well, that's weird. Thanks for the detail, that helps. I'll let the frameworks maintainers take a deeper look from here.