On Ubuntu Aspect currupts NTFS partition

Bug Reports
1

Observed behavior

When Aspects during start up of the program tries to load a photo library located on an NTFS partition that is NOT mounted, it corrupts the partition. It than can not be mounted again. It than can also not being repaired with gparted, but only with the disc repair of Windows itself.

Expected behavior

well, this should not happen. Actually, the whole thing does not make sense to me. :roll_eyes:

Steps required to reproduce

    • Dual boot Windows 11 & Ubuntu 24.04.3 LTS (Gnome Shell)

    • Separate Data partition with NTFS File system to have access from both OS.

    • my /etc/fstab on Ubuntu looks like this:

      # /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p6 during installation
UUID=0e28f8b0-fb43-4a41-bd73-0b1172f133bf /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p3 during installation
UUID=1C8C-7C72  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/nvme0n1p7 during installation
UUID=b110769a-ada4-46ad-bdc6-eb3a6e8d9a31 /home           ext4    defaults        0       2

    • photo library is located on Data partition to be used from Win & Ubuntu each with its own Aspect installation but accessing the same library.

    • When I boot up Ubuntu, the Data Partition is visible, but not mounted. - I forget to mount it but forget this but start Aspect via right click on the AppImage file → “run as program”

    • I get an error message “library access failure - Failed to load the library - library file does not exist.”

    • I mount the Data partition, while Aspect is still running. I get an error, mounting Partition corrupted.

    • I can not repair partition with gparted

    • I only can repair partition with the Window partition tool.

      I now had this problem two times, never had any other issue like this. But it is also the only program I have as an AppImage, everything else I installed as Snap or via apt-get.
      Now the third time when I tried to reproduce it to document it, I could not reproduce it - still get the ““library access failure - Failed to load the library - library file does not exist.” message but once I mount the partition, it works fine and nothing got corrupted. ?? Looks all strange to me.

      Where can I find a log to post here the next time this happens to me?

Operating system/Hardware used

Ubuntu 24.04.3 LTS with Gnome Shell
Lenovo ThinkPad X1 Carbon Gen 9
11th Gen Intel® Core™ i7-1165G7 × 8
Aspect Version 1.0.0-rc.43 free version.

2

I don’t really have an idea what would cause this behavior. There definitely is nothing that can access a volume on a level where it can directly corrupt anything, there are just ordinary file operations. I would say with very high certainty that this is caused by either a file system driver bug, or possibly by a hardware issue.

One thing that is possible is that Aspect somehow makes it more likely to hit this issue. The only thing that comes to mind there is a background process that checks for newly mounted drives every 2 seconds by invoking lsblk -OJ. Maybe there is a timing issue where calling it right when the drive is being mounted triggers some kind of race-condition?

If this was reproducible, I could look into how alternative ways to get information about mounted drives behave.

3

Yes, I expected this to be not to have any clear cause.

I am no programmer or developer, just an enthusiastic end user. So here we reached the point where I can not any more follow the conversation, since I miss the knowledge required.
I am happy to follow any step-by-step instructions, and post any logs etc. here, but please do not assume I do understand what we are talking here :wink: