Bug 364565 - Gwenview displaying a PNG crashes when directory is renamed.
Summary: Gwenview displaying a PNG crashes when directory is renamed.
Status: RESOLVED FIXED
Alias: None
Product: gwenview
Classification: Applications
Component: general (show other bugs)
Version: Other (add details in bug description)
Platform: Mint (Ubuntu based) Linux
: NOR crash
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords:
: 334308 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-06-20 19:40 UTC by JCG
Modified: 2017-09-27 16:31 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JCG 2016-06-20 19:40:35 UTC
1. I opened a folder in Dolphin. The folder contained .png files and .txt files. 
 2. I opened a .png file using Gwenview to look at a picture. 
 3. With Gwenview still displaying the PNG image, I want back to Dolphin. 
 4. I changed directory to the next level up. 
 5. I renamed the folder containing the .png and .txt files. 
 6. Gwenview crashed. (It does not happen when editing the TXT files.)

Reproducible: Always

Steps to Reproduce:
1. Open a folder containing a PNG file
2. Open the PNG file with Gwenview
3. Rename the folder ==> Gwenview crashes

Actual Results:  
Gwenview's image viewing window closed and a "Gwenview - The KDE Crash Handler" system window opened. 

Expected Results:  
Perhaps Gwenview could remain on screen, displaying the PNG file.  

It may have occurred in one of these modules: 
x86_64-linux-gnu/libglib-2.0.so.0
 - or - 
x86_64-linux-gnu/libQtCore.so.4

Renaming the directory while the file is open is an unusual activity. I can live with this bug.
Comment 1 Nate Graham 2017-09-08 19:07:24 UTC
Couldn't reproduce in GwenView 17.11.70 in KDE Neon. Looks fixed! When I renamed the directory, the GwenView window flashed for a moment; clearly it was updating itself to account for the changes folder name.
Comment 2 Nate Graham 2017-09-08 19:56:23 UTC
*** Bug 334308 has been marked as a duplicate of this bug. ***