-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calibre 6.0.0 app won't start #91
Comments
Was fixed few hours ago #90 |
My problem remains. I even cleaned the config directory. |
Pull the fresh image. |
Update, but unfortunately did not help.
|
Please could you provide more information about your Synology hardware? As in the specific model with CPU info. As our tests for this container boots fine https://github.com/linuxserver/docker-calibre |
I'm on a 716+ DS716+ | Intel Celeron N3150 | 4 cœurs | 4 | Oui | Braswell | DDR3 2 Go |
Please both try https://docs.linuxserver.io/faq#option-2-short-term-fix |
I'm having the same issue. The sort term fix is not working for me. |
The fix didn't work.
|
It does seem that units running the older v3 Synology kernel are the only ones affected by this. Unfortunately there isn't much we can do if your OS doesn't support the newer system calls by Calibre. |
Thank you, I will roll back the version to 5.44.0 |
I'm running a 32 b raspberry pi omv on Raspbian os and I cant get it to load either. Trying to roll back to the version that worked on #82 |
We didn't publish v6 on arm platforms |
Is that temporary? Will Calibre 6.x be eventually published for arm64/raspberry pi 4? |
Hello. Having the same issue, not only for this calibre docker, but for libreoffice one too. A curious thing is that "opening dialogs" show. Let's say I delete the calibre db: it shows the dialogs to set it. If I cancel or set it to a valid library location, it blacks out. The libreoffice container behaves the same. I can see the libreoffice toolbar, launch an application, see the libreoffice logo message, and it blacks out, OR remains only the "libreoffice logo message" area visible. Maybe this can give a clue. Tried op2 fix without success. Manjaro linux (Arch based) My hardware: Xeon 2678v3 + 16GB + NVIDIA GT630. |
Can we hope a developpement about this issue ? |
Probably not, 3.10.x has been EOL for 5 years. Even the longest-supported 3.x kernel, 3.16, has been EOL for 2 years. Technology marches on and at a certain point newer libraries are going to stop working with obsolete kernels. It might be possible to fudge something, but it's a short term fix at best and not something we can provide support for. |
But I'm using a modern kernel (5.15 here) and I'm having same issue.... Nor Calibre nor Libreoffice guacamole containers are working for me. See #91 (comment) for my specs. What can I do? |
I'm seeing this exact same behavior on my server. The guacamole login screen I'm seeing in my web browser is blank: [screenshot], and this is the error message I'm seeing at the end of
I'm running an up-to-date Debian Bullseye server:
... with a modern kernel:
... a recent (2017) AMD x86-64 processor:
... running Docker version 20.10.17 with Compose version 2.6.0, (both from Docker's official apt repository):
|
Is this with or without |
@thespad I've tried both with and without, it doesn't make a difference. |
So I think we've got two different, conflated issues here. The issue with Synology units on 3.x kernels is known and likely unfixable. If you've got issues with the container that don't meet those criteria, can you create a new issue and provide the necessary details (or copy/paste from here if you've already provided them) so we're only dealing with one problem at a time. |
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. |
Expected Behavior
Current Behavior
Black screen, Safari 15.5, macOS 12.4, M1
Steps to Reproduce
Environment
OS: Synology DSM 7.1
CPU architecture: x86_64
How docker service was installed: nas OS provided
Command used to create docker container (run/create/compose/screenshot)
docker-compose.yml
command to update:
Docker logs
The text was updated successfully, but these errors were encountered: