Does NextCloud Memories allow modifying the coordinate data in HEIC files?

I’m trying to manually change the metadata of an HEIC file to specify a location. The UI accepts the change but it does not appear to persist it.

Nothing is appearing on occ log:watch that would specifically indicate a problem.

Nextcloud Hub 10 (31.0.5)
Operating system and version: Docker in Raspbian
Caddy proxy to nextcloud:apache (customized to add ffmpeg and imagemagick binaries)
Database: Postgres
Apps: 
- Recognize
- Memories

Steps:

  1. Choose an HEIC image in the Memories
  2. Open up the details
  3. Enter and save Geo data
  4. Info does not appear to be saved even refreshed.

Please fill in the Support Template and provide information about your environment, network, setup etc., etc. Please also describe IN DETAIL where you are editing what, using which GUI and what you exactly expect to see using the log command.

Custom Dockerfile

FROM mirror.gcr.io/library/nextcloud:apache
RUN --mount=type=cache,target=/var/lib/apt/lists \
    --mount=type=cache,target=/var/cache/apt \
 apt update && \
 apt install --no-install-recommends -y ffmpeg imagemagick

Caddyfile fragment

xxx.xxx.net {
	reverse_proxy nextcloud:80 {
      header_up X-Real-IP {http.request.remote.host}
      health_uri /ocs/v2.php/apps/serverinfo/api/v1/info
      health_headers {
        NC-Token secrettokenhere
      }
    }
}

Also I have a secondary container that runs /cron.sh

I also tried on the Edit Metadata GUI with no effect (not even the title would be saved)

I have checked that I have

tmpfs:
  - /tmp:exec

set as noted in Troubleshooting - Memories no luck

Also ran

occ maintenance:repair

The relevant log shows it’s okay

 - Repair steps for Memories
     - External table schema seem up to date
     - Recreated filecache trigger with: Doctrine\DBAL\Platforms\PostgreSQL120Platform
     - exiftool binary is configured: /var/www/html/custom_apps/memories/bin-ext/exiftool-aarch64-glibc
     - go-vod binary is configured: /var/www/html/custom_apps/memories/bin-ext/go-vod-aarch64
     - ffmpeg binary is configured: /usr/bin/ffmpeg

I also tried installing my own exiftool using apt no luck. The exiftool available on Debian is also older compared to the one bundled so I reverted back to the bundled one.

Found the related bug Unable to Save Metadata in Memories After Update to NextCloud 31.0.0 and Memories 7.5.0 · Issue #1406 · pulsejet/memories · GitHub

1 Like

I wonder… how do I enable debug logging only for memories?

You can use a log.condition.

1 Like

Thanks, but unfortunately all we can do at the moment is wait for the bug to be resolved by the development team.

  'loglevel' => '2',
  'log.condition' => [
    'matches' => [
      [
        'apps' => [ 'memories' ],
        'loglevel' => 0
      ]
    ]
  ],

Don’t really see any debug logs for memories.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.