Christoph Roeper

No response to December issues and pull requests? 😲 My summary to decent OSS Web Application Launcher projects. - [Hamsket](https://github.com/TheGoddessInari/hamsket) (this project): See this thread for current development progress. However...

I can confirm and reproduce the crash on [Fedora 30](https://getfedora.org/) with [GNOME](https://www.gnome.org/) 3.32.2 giving the following error message: ``` AppImageLauncherSettings: /lib64/libcurl.so.4: no version information available (required by /usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so) (AppImageLauncherSettings:15850): Gtk-WARNING...

At the time of writing the above comment I had installed `version 1.5.0` using the rpm package `appimagelauncher-1.5.0-travis780.git20190816.cc1a7ad.x86_64.rpm` with dnf. Today I upgraded to version 2.0.0 (git commit 4075ba1) again...

Same issue on a bare metal Debian 10 machine, but only if the playbook runs as non-root (with become password). Looking into `roles/ssh_hardening/tasks/crypto_hostkeys.yml` the task _Replace default 2048 bits RSA...

In addition to the feature request, running the latest asbru-cm (v6.3.3) under Wayland (Fedora 36) with `xfreerdp`, some mouse functions are not available, like drag/move/resize windows. However mouse drag/move/resize windows...

No, as of today I did not find a solution; workaround: I pinned my Vagrant to version 2.3.4 in my Dockerfile. Does the setup with vagrant 2.3.7 and plugin 0.12.2...

I had an error in my modified `Dockerfile` because of the new Vagrant download version name, i.e. 2.3.7-1 or 2.4.0-1 with regards to the dash -1. After fixing the `Dockerfile`...

Sure, it is basically the original `Dockerfile`, updated to version 2.4.0 with some _script friendly_ modifications. Dockerfile building plugin from git repository (not working) ```dockerfile # syntax = docker/dockerfile:1.0-experimental ARG...

Reopening this issues, because I have some new learning from my research. Also both Dockerfiles in the above post are **not working**. Feel free to close this issue because of...

I have to correct myself, the `autocomplete="off"` attribute does not work reliable. According to a long stackOverflow thread [Disabling Chrome Autofill](https://stackoverflow.com/questions/15738259/disabling-chrome-autofill) there is no reliable way of disabling autofill in...