SUMMARY Gwenview does NOT start but just freezes, whether its run from krunner, the K menu, or from any command line. On command line, no output is printed, it just freezes until CTRL-C is pressed STEPS TO REPRODUCE 1. Type gwenview in command line or krunner or select it in the start menu 2. 3. OBSERVED RESULT Nothing happens EXPECTED RESULT I would expect to see the gwenview window, or anything for that matter SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Kubuntu 25.04 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.3 Kernel Version: 6.14.0-29-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION
If something 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!
(In reply to A Linux User from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's going on. It gets a little weirder: Turns out it wasn't crashing, it was starting up, but really REALLY slowly, as in taking ~24 hours to get the window to show. I have a 10K+ wallpaper directory from which random wallpapers are shown. Sometimes there is a wallpaper in there that I want to delete or copy, and "open wallpaper" and then gwenview opens it and I do my thing. I tried opening wallpapers multiple times on a Wednesday morning, nothing happened. I also started a few by hand from consoles, and for at least a minute there was no text output at all on the command line (normally there are always a bunch of warnings, gwenview can be quite chatty when run from the command line) until I CTRL-C'd the process. I multiple times SIGKILLED all gwenview processes, and tried again to open wallpapers from the desktop, but nothing happened. I continued working, forgetting all about the started gwenview processes. Then, Thursday afternoon whilst working, all of the sudden, gwenview pops up some 10x out of no-where with the different wallpapers I requested to open at the end of the day before The processes were there the entire time, presumably blocked. Right when those wallpapers showed, gwenview proceeded to work as normal again. The only thing I can imagine it was blocking on was perhaps an NFS drive that I have that works over a VPN that sometimes is off, so NFS access might hang. Could that be related into why it wasn't starting up? If that is the case, is there a way to have gwenview either time out on such a thing, or at least print something on the command line / logs like "Waiting for drive data to arrive" or something? Mind you: The wallpaper files themselves are NOT on the NFS drive, maybe I used gwenview for an image on the NFS drive before in the past, and gwenview was trying to load the history list of images?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
I don't have a backtrace at hand but the issue basically can be replicated with adding an NFS drive, then blocking the IP for that NFS, breaking NFS, and then starting gwenview with an image on that drive, or start gwenview with an image in the history, etc... Basically gwenview will wait forever until (24 hours later) the NFS becomes available. I think a -possible- fix would be a timeout on the file loading?