[Debian-on-mobile-maintainers] Bug#1065519: Bug#1065519: phosh-full: Phosh not booting on login or from cmd on OrangePi

[Guido Günther]

control: reassign -1 phoc

Hi Evan,

The problem is that the compositor can't start:

On Tue, Mar 05, 2024 at 08:46:24PM +0000, Evan Robinson wrote:
[..snip..]

> Mar 05 20:33:38 orangepicm4 phoc[3244]: [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
> Mar 05 20:33:38 orangepicm4 phoc[3244]: [libseat] [seatd/seat.c:61] Could not open tty0 to update VT: Permission denied
> Mar 05 20:33:38 orangepicm4 phoc[3244]: [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
> Mar 05 20:33:38 orangepicm4 kernel: [drm:vop2_plane_atomic_check] *ERROR* Unsupported linear format at Cluster0-win0
> Mar 05 20:33:38 orangepicm4 kernel: [drm:vop2_plane_atomic_check] *ERROR* Unsupported linear format at Cluster0-win0

This is odd: I can't seem to find this error message in the
rockchip_drm_vop2 mainline driver. Are you using a vendor kernel?
If so which one exactly?

> Mar 05 20:33:38 orangepicm4 phoc[3244]: [libseat] [seatd/seat.c:72] Could not open terminal for VT 0: Permission denied
> Mar 05 20:33:38 orangepicm4 phoc[3244]: [libseat] [seatd/seat.c:461] Could not open VT for client
> Mar 05 20:33:38 orangepicm4 phoc[3244]: [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
> Mar 05 20:33:38 orangepicm4 phoc[3244]: [libseat] [seatd/seat.c:86] Could not open terminal to clean up VT 0: Permission denied
> Mar 05 20:33:40 orangepicm4 lightdm[3258]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=110) by (uid=0)
[..snip..]

You seem to have lightdm still running but use phosh.service. Please
stop lightdm to make sure they don't race for the same tty.

> Mar 05 20:33:48 orangepicm4 phoc[3188]: [backend/backend.c:107] Timeout waiting session to become active
> Mar 05 20:33:48 orangepicm4 phoc[3188]: [backend/backend.c:272] failed to start a session
> Mar 05 20:33:48 orangepicm4 phoc[3188]: [backend/backend.c:322] failed to add backend 'drm'
> Mar 05 20:33:48 orangepicm4 phoc[3244]: [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
> Mar 05 20:33:48 orangepicm4 phoc[3244]: [libseat] [seatd/seat.c:86] Could not open terminal to clean up VT 0: Permission denied
> Mar 05 20:33:48 orangepicm4 phoc[3188]: Failed to create server: Could not create backend
> Mar 05 20:33:48 orangepicm4 systemd[1]: phosh.service: Main process exited, code=exited, status=1/FAILURE
> Mar 05 20:33:48 orangepicm4 systemd[1]: phosh.service: Failed with result 'exit-code'.
> Mar 05 20:33:48 orangepicm4 systemd[1]: phosh.service: Triggering OnFailure= dependencies.

To debug further could you create a .phoshdebug file in your users $HOME
with:

  G_MESSAGES_DEBUG=phoc-wlroots
  export G_MESSAGES_DEBUG

(if you didn't change phosh.service the relevant user is the one with
uid 1000). Then

  systemctl stop phosh
  systemctl start phosh

and get the logs from that one. To shorten the log you can use

  journalctl _COMM=phoc

as the other processes don't matter atm.

Cheers,
 -- Guido