I am using octoprint and TouchUI on a small touch display since a few month.
Now I found Octoscreen and decided to switch for Experimental purposes.
I followed this instruction:
... from 9:15 min
The sudo dpkg extract and install command gave me an error back:
sudo dpkg -i octoscreen_2.5-1_armhf.deb (Reading database ... 86728 files and directories currently installed.)
Preparing to unpack octoscreen_2.5-1_armhf.deb ...
Unpacking octoscreen (2.5-1) over (2.5-1) ...
Setting up octoscreen (2.5-1) ...
Installing service /lib/systemd/system/lightdm.service
Failed to preset unit: File /etc/systemd/system/display-manager.service already exists and is a symlink to /lib/systemd/system/lightdm.service.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on octoscreen.service: No such file or directory
I am connected via PuTTY and not able to check the display locally at the moment.
Any Idea what path I have to follow to solve this error?
Did you install OctoPrint by flashing the OctoPi IMG to your microSD? If so, then the octoprint service is controlled by a service handler within the /etc/init.d folder area rather than using the /etc/systemd/system section of Raspbian.
So if you see systemctl, that's using the other system.
Also, anything within that /etc/systemd/system folder has those scripts appended with a .service extension like the error message was suggesting. In contrast, the files under /etc/init.d don't have file extensions.
So whoever built the octoscreen_2.5-1_armhf.deb package might have made a mistake, I'm guessing.
u r absolutely right ... I installed Octoprint by flashing the sd card.
I checked if the files in /etc/systemd/system are appended with .service and there a a plenty of them.
The files at /etc/init.d have no extension like this ... but base their names are different.
Anyhow ... what does it mean?
What is my aproach to install or configure Octoscreen?
I did not get the part of your message containing the systemctl
I guess what I was trying to say is that the author of OctoScreen has built his Debian package based upon the assumption that OctoPrint itself is started up using the systemd daemon rather than with the initd daemon. I think anyone who imaged from the OctoPi IMG would have the init.d version.
There appears to be an open issue on his repository with this same installation error. I commented there, linking back to this thread.
In case you're curious, here is my current setup (flashed with the OctoPi image):
As guessed, you have the OctoPi-imaged installation and your octoprint service is started from init.d rather than from systemd. If you're curious feel free to cat /etc/init.d/octoprint if you'd like to see how that service handler does its job when you, for example, say sudo service octoprint start.
All that said, now take this to the octoscreen issue, chime in with the other person/people and ask that author what to do. By helping him fix his code, it will help everyone.
I deleted the repeat of this post on another thread. No, I didn't mean for you to spread out here.
I'm suggesting that you reach out to the author of OctoScreen. Start with their repository, visit the Issues link, research to see if someone else is already talking about this. If not, start a new issue.
Did you ever find a fix for this issue? I believe I am having the same issue. My screen is partly off to the side. When I reboot I see the message that systemctl was not turned on or something to that affect. can you assist me? Thank you.