SUMMARY *** Hi, As is shown in the video (https://imgur.com/F1Kia6o), neither KRunner nor the App Launcher seems to be able to open recent documents. In the panel below it shows a blank icon with a loading bar but then they close and the document doesn't open. The plugin is active, the documents open fine from the file manager. I'm not sure if this is a general bug or something specific to my setup. I would appreciate any help solving this issue, or at least just a method to try and troubleshoot it. Thanks in advance. *** STEPS TO REPRODUCE 1. Open a document from the file manager 2. Close the document. Open it from the *recent* from either KRunner or the app launcher 3. Document loads for a second, then it doesn't open OBSERVED RESULT You see a blank thumbnail on the panel with a loading circle, but it then closes and the document doesn't open. EXPECTED RESULT Any recent document would open normally just as if opened from the file manager. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-33-generic (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION
Created attachment 149320 [details] A video showcasing the bug
Unable to reproduce. Does this happen only for Okular supported files? Or also for others like images, audio, videos?
(In reply to Bacteria from comment #2) > Unable to reproduce. > > Does this happen only for Okular supported files? Or also for others like > images, audio, videos? Pretty much with everything. Nothing opens, even files don't open unless I click on the icon to the left. Apps launch fine, however. Is there a way for me to try and debug this? I'm still a beginner, as you can probably tell by how messy this bug report is. Normally I open whatever app I need to troubleshoot from the terminal to see what issues crop up. It doesn't work in this case.
> unless I click on the icon to the left. Not sure what you mean here. Are you able to open the file if you click on the icon of search result? > Is there a way for me to try and debug this? Not sure. But you can get logs of the whole plasmashell using: killall plasmashell & kstart5 plasmashell
(In reply to Bacteria from comment #4) > > unless I click on the icon to the left. > > Not sure what you mean here. Are you able to open the file if you click on > the icon of search result? > > > Is there a way for me to try and debug this? > > Not sure. But you can get logs of the whole plasmashell using: killall > plasmashell & kstart5 plasmashell Here's a video of what I mean. https://imgur.com/JXxIzVi The launcher opens apps--including the file manager--but can't seem to open places or documents. I tried making a new user to see if the issue is due to something I did, but no dice. The issue persisted. Maybe I should try reinstalling the DE or a specific component? There are no broken packages as far as I know.
(In reply to Bacteria from comment #4) > > unless I click on the icon to the left. > > Not sure what you mean here. Are you able to open the file if you click on > the icon of search result? > > > Is there a way for me to try and debug this? > > Not sure. But you can get logs of the whole plasmashell using: killall > plasmashell & kstart5 plasmashell Hi, So I ended up finding the culprit behind this bug! Before formatting my disk, I copied and pasted the content of my home folder into another drive. Then, after I set up my new installation, I copied and pasted that content wholesale back into the home folder, which is what screwed up the launcher's ability to access my files. Thanks you for taking the time to look into this.
Oh so I guess the cached recent files must still be pointing to older locations of the system. Glad you figured it out.
(In reply to Bacteria from comment #7) > Oh so I guess the cached recent files must still be pointing to older > locations of the system. > > Glad you figured it out. Know what? Scrap that. I tried messing around with another new installation. It turns out, the GIMP English help documentation, for some reason, lists the dependency "wslu", and wslu is what screws up the launcher. Just... How? Anyway, thanks for the help! I can't believe I stuck with this only to end up on this bizarre conclusion.