This is probably the dumbest user error made in the history of computing, and thus probably useful only if you want to have a laugh at my expense. Go ahead, I fully deserve it.
I had successfully switched my Windows storage drive to NTFS-3G and thought I would now have write-access to KeePassX‘s database. But despite having write-access to other files (such as images) on the drive, the Save button was still disabled in KeepAssX after opening the database file from it.
I tried copying the database to my home directory and opening it from there, but it remained unsavable. I checked, and all the access bytes were as they should be in order to allow for modifying the file. I tried creating a new database, and that seemed to work. I even contemplated exporting the old database to another format in Windows and then importing it in Ubuntu…
…until I realized I hadn’t actually made any changes in the database prior to trying to save it.
That’s right. After creating a test entry into the database I could save it just fine, even onto my NTFS drive. Doh!
I fully understand the reasoning behind disabling the saving function when no changes have been made in the data (KeepAssX is hardly alone in this choice of logic), but in this case my intuition seemed to work massively against that logic, so I guess that qualifies the issue as one of accessibility.
In my defence I can say that I did change the order in which the entries are shown in KeePassX (for some reason they seem to default to reverse alphabetical in Ubuntu) before trying to save, and that’s why my subconscious mind fully expected saving to be enabled. Apparently the listing order is not among the data saved in the database, but if it is, the Save button not reacting to it is an obvious bug in KeePassX.