hyperion.ng: After upgrading to 2.0.0-alpha.11, service no longer exists

  • I confirm that this is an issue rather than a question.

Bug report

I upgraded to the new alpha.10.1 yesterday and it transpired that there was an issue with the build. After I upgraded hyperion, the service never came online.

I then install Hyperion alpha.11 following the release earlier but the service is not starting.

Steps to reproduce

  • Upgraded to alpha.11 via sudo apt-get update && sudo apt-get install hyperion

What is expected?

Running sudo systemctl hyperion and sudo systemtl hyperion.service should show the status of the Hyperion service

What is actually happening?

Running the above results in:

Unit hyperion.service could not be found.

Tried to reinstall hyperion by running sudo apt-get install --reinstall hyperion. Although it completes, no service exists still

System

Unable to obtain. Running Raspberry Pi 4. OS info below image

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 8
  • Comments: 30 (10 by maintainers)

Most upvoted comments

I have the same issue after upgrading from 2.0.0-alpha.11 to 2.0.12

I have the same problem. I had version Alpha 10 installed manually before.

I updated to version Alpha 11. Sadly the service also doesn’t exists. I also running raspbian headless. As suggested I uninstalled hyperion with this command sudo apt remove hyperion. Afterwards I checked, if the hyperion folder exists under /usr/share/ (It was removed)

I reinstalled Alpha 11 with this command sudo apt install hyperion

Sadly the service isn’t installed afterwards.

@mrdarrengriffin Does the reinstall fixed the problem for you?

It did, Try

sudo apt-get remove hyperion
sudo apt-get purge hyperion
sudo apt-get update
sudo apt-get install hyperion

I found the solution… The solution is pretty stupid.

I use the tool MobaXterm to connect to my raspberry. By default the feature X11-forwarding is turned on. So the gui based content is passed through the ssh connection.

After disabling this feature, the installation works fine!

image

Maybe this also helps somebody else.