github-actions[bot]
commented
4 months ago Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Closed dave2492 closed 1 month ago
github-actions[bot]
commented
4 months ago Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
LinuxServer-CI
commented
3 months ago This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
drizuid
commented
2 months ago so, much like the prior ticket you mentioned, you did not fill out the template. there is no docker run provided. We have 2, (you and the other guy) who failed to provide the template info and have the problem, out of thousands. That "error" is expected as there is no desktop environment. Without the template info, we cannot assist you. I'll leave this up a couple days for you to provide the docker run, if you don't, I will close it.
github-actions[bot]
commented
2 months ago A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.
danepowell
commented
2 months ago I agree this error is a red herring, but it might still be worth addressing just for all of the confusion and support burden it causes.
Part of the problem is that the server takes a long time (a minute or two) to fully start, longer than one would expect, and there's no log output during that time. It's natural to see an exception as the last line in the logs and assume the process crashed (even though it's actually just taking a while to come up).
drizuid
commented
2 months ago I agree this error is a red herring, but it might still be worth addressing just for all of the confusion and support burden it causes.
Part of the problem is that the server takes a long time (a minute or two) to fully start, longer than one would expect, and there's no log output during that time. It's natural to see an exception as the last line in the logs and assume the process crashed (even though it's actually just taking a while to come up).
unfortunately, we cannot fix the error, it is an error generated by installing calibre into the container using the mod. calibre expects, generally, a desktop environment.
as to the startup time, a long startup time is abnormal, depending on your hardware, but a new container for me starts up in about 20 seconds, including mod install.
I do not see anything in this ghi that we can address, but if you see something, please let me know or submit a PR for us to check out.
venuses
commented
1 month ago I run this command to fix it.
apt install -y xdg-utils
drizuid
commented
1 month ago xdg-utils
ok i stand corrected, we can superfluously add a package, increasing image size, to remove some benign lines of text from the log. However, as stated, the text is benign, it does NOT cause the container to fail or introduce any issues at all.
for those wishing to do this, simply add the below to your environment variables for persistent install of xdg-utils.
- DOCKER_MODS=linuxserver/mods:universal-package-install
- INSTALL_PACKAGES=xdg-utilsnote that I have not tested this, it is purely something suggested by the user above and it should NOT fix the desktop integration text, because it cannot work in this container.
danepowell
commented
1 month ago xdg-utils is only 60 KB. And I'd argue the warning is not benign if it causes so much confusion and wastes your time with conversations like this.
drizuid
commented
1 month ago xdg-utils is only 60 KB. And I'd argue the warning is not benign if it causes so much confusion and wastes your time with conversations like this.
so as per your link it's not 60KB, and it's presumptuous to assume what is a waste of space for other users. ALSO, i do not believe it fixes the text because the desktop integration SHOULD still fail. Until someone can demonstrably show that it resolves it, my solution provided above is what they can do.
JFPCreations
commented
1 month ago - DOCKER_MODS=linuxserver/mods:universal-package-install - INSTALL_PACKAGES=xdg-utils
Thank you. This solves my problem.
Without it, my Calibre-web does not work and give me :
Is there an existing issue for this?
Current Behavior
Identical to the closed bug #269. Closed on technicality. Is a real problem, however.
I installed the calibre-web docker latest on Unraid and it failed to fully start because it could not find the file xdg-icon-resource.
The problem is because the file xdg-icon-resource is missing. It is provided by the package xdg-utils.
Once I installed that package and restarted the docker, then it finished initialization as expected.
Expected Behavior
For the docker to complete initialization.
Steps To Reproduce
Same as the bug #269
Environment
CPU architecture
x86-64
Docker creation
Container logs