Bug 412290 - Gwenview hangs when loading if cifs share not connected
Summary: Gwenview hangs when loading if cifs share not connected
Status: RESOLVED DUPLICATE of bug 397158
Alias: None
Product: gwenview
Classification: Applications
Component: general (show other bugs)
Version: 19.04.3
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-24 19:09 UTC by Eric Adams
Modified: 2019-10-07 03:22 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Adams 2019-09-24 19:09:15 UTC
SUMMARY
Gwenview will not open an image (local disk) when cifs network mounts are disconnected. I assume it is doing a directory scan of some kind for whatever reason and hangs while trying to access the share.

STEPS TO REPRODUCE
1. Either manually mount or add a mount option to fstab to a network share using cifs.
2. Disconnect the network or use a different network where the share is not accessible
3. Open any image on your local disk or other accessible location.

OBSERVED RESULT
The main Gwenview window appears but nothing is shown and eventually Plasma asks if you'd like to close or wait.

EXPECTED RESULT
Gwenview doesn't care if a network location is inaccessible and is able to open images regardless.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 19.04 with backports ppa enabled. 
Operating System: Kubuntu 19.04
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.2
Kernel Version: 5.0.0-29-lowlatency
OS Type: 64-bit

ADDITIONAL INFORMATION
Comment 1 Eric Adams 2019-09-24 19:12:01 UTC
I forgot to add that the workaround for this is to simply unmount the network share if you are on a different network. Gwenview is fine after that. Obviously not a high severity issue but thought it was worth reporting all the same.
Comment 2 Nate Graham 2019-10-07 03:22:26 UTC
*** This bug has been marked as a duplicate of bug 397158 ***