aanno

If I set the parameter to `within_size`, I can run Signal without problem! ``` $ cat /sys/kernel/mm/transparent_hugepage/shmem_enabled always [within_size] advise never deny force $ flatpak -v run org.signal.Signal # Working...

Hm, with `gocryptfs v2.3.2-12-gc674544 without_openssl`, I was not able to use a legacy (very old) FIDO2 hardware token (apparently because it does not support a PIN). With [solokey somu](https://github.com/solokeys/solo1), I...

Seems to be restricted to my f39 linux system. On Win11, everything works as expected.

The problem has been caused by corrupted files in `~/.local/share/keybase/` . I deleted the directory, run `run_keybase` and logged in again with `keybase login`. I guess that one of the...

Hm, I stepped upon the [profiles](https://docs.docker.com/compose/compose-file/compose-file-v3/#profiles) handling as well, when I'm trying to use the nextcloud all-in-one [manual install](https://github.com/nextcloud/all-in-one/blob/main/manual-install/readme.md). For me, it looked like all profiles were always started (even...

I can partly solve/circumvent issue 2 with: ``` $ podman exec -it sh /var/www/html # cp -r /opt/nextcloud/data/appdata_ocvkg7lyrl56/js . /var/www/html # cp -r /opt/nextcloud/data/appdata_ocvkg7lyrl56/css . /var/www/html # chown -R www-data:root...

I now also rechecked that the problems mentioned above are caused by `- NEXTCLOUD_DATA_DIR=/opt/nextcloud/data`, i.e. if I omit the line from my docker-compose file, everything works as expected. Conclusion: NEXTCLOUD_DATA_DIR...

Dear @0x47, sorry for replying late. I posted the question/problem some time ago. And I now think it's a bad idea to try to change NEXTCLOUD_DATA_DIR _from a working nextcloud...

The `myentrypoint.sh` thing is a kind of HACK that circumvents the 'Issue 2' of my bug report (i.e. the top post). The script just fixes that, copying the mentioned files...

@wing328: rebased to master (and sorry for being late)