[BUG] Linux: Automatic shutdown fails after job completion – obsolete UPower D-Bus call

[tamo_bln]

Description

Hybrid's automatic shutdown function does not reliably work under Linux (Mint 22.3 and Ubuntu 26.04 LTS were tested) .

After an encoding job finishes, Hybrid's shutdown countdown remains stuck at 

00:01 h

, and the system does not power off.

The issue has occurred on two different Linux systems.

Steps to reproduce

1. Start an encoding job in Hybrid.
   
2. Enable the automatic shutdown action after job completion.
   
3. Wait until the encoding job finishes.
   
4. Observe the shutdown countdown.
   

Actual behavior: The countdown remains at

00:01 h

, and the computer stays powered on.

Expected behavior: Hybrid should initiate a system shutdown when the countdown expires.

Technical findings

On October 29, 2026, at 11:27:39, the system journal recorded the following D-Bus rejection originating from Hybrid:

dbus-daemon: Rejected send message comm="/tmp/.mount_HybridnKeHFj/usr/bin/Hybrid" interface="org.freedesktop.UPower.Shutdown" member="Shutdown" destination="org.freedesktop.UPower"

The Hybrid executable links against

libQt6DBus.so.6

and contains references to:

org.freedesktop.Hal.Device.SystemPowerManagement org.freedesktop.UPower.Shutdown org.freedesktop.DeviceKit.Power org.freedesktop.UPower.Hibernate

On the affected system, UPower 1.90.3 does not expose a

Shutdown

method.

However, systemd-logind provides the following methods:

org.freedesktop.login1.Manager.CanPowerOff org.freedesktop.login1.Manager.PowerOff org.freedesktop.login1.Manager.PowerOffWithFlags

A string search of the Hybrid executable did not reveal references to 

org.freedesktop.login1

,

systemctl

, or 

loginctl

. This is not conclusive proof that no fallback exists.

Suspected cause

Hybrid may be attempting to use a legacy Linux power-management interface that is no longer supported by current UPower versions.
The rejected D-Bus call is confirmed by the system journal. Whether this rejection directly causes the countdown to freeze at 

00:01 h

still needs investigation.

Suggested investigation

Please check Hybrid's Linux shutdown implementation, particularly the handling of failed UPower D-Bus calls and whether 

systemd-logind

can be used for shutdown on current Linux systems.

No changes to system permissions or Polkit configuration have been made.

Regards

tamo_bln

[Selur]

Ah, totally forgot about that function.
Yes, it's probably an issue related to the the old shutdown calls Hybrid used.
I'll look into it and plan to:
a. check that if the shutdown fails Hybrid gets re-enabled
b. the shutdown hopefully works

Cu Selur

[tamo_bln]

Hi Selur,

this sounds like a plan. 

It's just a minor issue. Take all the time you need to have a look into it. 

Thank you!

tamo_bln

[Selur]

Probably, easy to fix, packaging and testing takes most of the time.

Cu Selur

[tamo_bln]

Yes, I can well believe that’s where most of the time goes. It’s often the case with many things that the actual task itself takes very little time, but all the bits and pieces around it end up being all the more time-consuming.

Thank you for planning to sort this out.

tamo_bln

[Selur]

Uploaded a new dev (Hybrid-2026.11.02.2-x86_64_oldGlibc) which hopefully fixes the problem. (seems to work here)

Cu Selur