Closed prahal closed 1 year ago
github-actions[bot]
commented
2 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
prahal
commented
2 years ago Should I open another issue for the fact the linuxserver.io build tests for docker-calibre test xrdp startup but not calibre startup inside of it ? It happened countless times that the docker image does not permit calibre startup due to a partial migration of its underlying libraries : qt5, libc, mesa. The build test is useless as is.
Maybe a grep for calibre in ps output after xrdp startup ?
github-actions[bot]
commented
2 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
github-actions[bot]
commented
1 year ago This issue is locked due to inactivity
qt5-base glibc mismatch with installed baseimage glibc
Expected Behavior
calibre autostart
Current Behavior
Steps to Reproduce
workaround: in the xrdp session, run xterm, then in xterm run
sudo pacman -Syu --noconfirmCould the cause be docker cache per https://pythonspeed.com/articles/docker-cache-insecure-images/ ?
Environment
OS: armbian CPU architecture: arm64 How docker service was installed: from the official docker repo via portainer in a stack
Docker logs
NB: in my mods I remove the openbox-session autostart output redirection to null (from /linuxserver/baseimage-rdesktop-web https://github.com/linuxserver/docker-baseimage-rdesktop-web/blob/arch/root/defaults/startwm.sh
/usr/bin/openbox-session > /dev/null 2>&1to/usr/bin/openbox-sessionso in the log you can see calibre error at startup ie: