After saving image, Shotwell still thinks image is unsaved

Bug #1664054 reported by madpentiste
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Shotwell
Unknown
Unknown
shotwell (Ubuntu)
Undecided
Unassigned

Bug Description

Shotwell 0.20.2, Ubuntu 14.04, Mate desktop environment 1.8.2

When trying to save a modified image, the following happens:

1) ctrl-S does not work (and is dimmed) -- only non-shortcut File > Save works

2) the new version of the image is actually saved on the hard drive (file manager shows new dates and time, and if the image is opened in another image viewer, the changes are there)

3) but shotwell itself sees the image as unsaved (with a star on the left side of the file name in the window banner) and will ask twice if you want to save it when you close the window.

Unlike bug #1064332, no freezing happens.

Revision history for this message
Jens Georg (yg-jensge) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in shotwell (Ubuntu):
status: New → Confirmed
Revision history for this message
Jani Uusitalo (uusijani) wrote :

This is currently still present in Bionic's Shotwell 0.28.1-0ubuntu1.

summary: - issues when saving image (different from #1064332)
+ After saving image, Shotwell still thinks image is unsaved
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.