This is currently still present in Bionic's Shotwell 0.28.1-0ubuntu1. ** Also affects: shotwell via https://bugzilla.gnome.org/show_bug.cgi?id=738486 Importance: Unknown Status: Unknown
** Summary changed: - issues when saving image (different from #1064332) + After saving image, Shotwell still thinks image is unsaved -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1664054 Title: After saving image, Shotwell still thinks image is unsaved Status in Shotwell: Unknown Status in shotwell package in Ubuntu: Confirmed 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. To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1664054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
