You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any Place with less than 16 characters gets overwritten/replaced with 0x1E.
This happens both with the Comment window and on browsing and existing photo.
Steps to reproduce
Case 1: Open a browser view of photos with comment:Place less than 16 characters eg Manchester created in pix 3.2.2.
Case 2: Open the Comment window, set Place to Manchester, press save....
Expected behavior
Place should remain as previously written (case 1) or written as entered (Case 2)
Additional information
Comment window does actually save correctly, the corruption seems to occur when the browser view refreshes. This can be seen by selecting a photo in browser view with Properties visible on the screen. Change the Place to "Less than 16" and click save whilst observing Place in the properties pane which will briefly change to "Less than 16" before becoming 0x1E.
The text was updated successfully, but these errors were encountered:
Distribution
Mint 22.0
Package version
3.4.3
Frequency
Always
Bug description
Any Place with less than 16 characters gets overwritten/replaced with 0x1E.
This happens both with the Comment window and on browsing and existing photo.
Steps to reproduce
Case 1: Open a browser view of photos with comment:Place less than 16 characters eg Manchester created in pix 3.2.2.
Case 2: Open the Comment window, set Place to Manchester, press save....
Expected behavior
Place should remain as previously written (case 1) or written as entered (Case 2)
Additional information
Comment window does actually save correctly, the corruption seems to occur when the browser view refreshes. This can be seen by selecting a photo in browser view with Properties visible on the screen. Change the Place to "Less than 16" and click save whilst observing Place in the properties pane which will briefly change to "Less than 16" before becoming 0x1E.
The text was updated successfully, but these errors were encountered: