Bug#968106: [Debian-on-mobile-maintainers] Bug#968106: phosh: Shell doesn't start

2020-08-17 Thread Guido Günther
Hi,
On Sun, Aug 16, 2020 at 07:47:04PM +0200, Michel Le Bihan via 
Debian-on-mobile-maintainers wrote:
> Hello,
> 
> I added `--aptopt='Apt::Install-Recommends "true"'` to mmdebstrap
> options, so my command was `sudo mmdebstrap --aptopt='Apt::Install-
> Recommends "true"' --include=linux-image-amd64,live-boot,xserver-xorg-
> video-all,phosh --arch amd64 bullseye debian-live-root 
> http://ftp.pl.debian.org/debian/`. I ended up with a 2.5G root that had
> gdm3 and gnome-shell that aren't quite useful or even wanted on mobile
> devices. When I selected Phosh as my shell and entered my password,
> Phosh didn't start and I ended up back on the login screen. I was able
> to start gnome-shell normally.
> 
> Also, why would a package required for Phosh to function only be
> recommended? Are there setups where Phosh can be started without those
> packages being installed?

It's needed for the session but not for phosh itself (hence Recommends:)
you can still run

   /usr/bin/phoc -E /usr/libexec/phosh

fine. I'm not entirely clear here though if a `Depends:` wouldn't be the
better thing to do. It does not happen with GNOME Shell since the
session file is in a separate package (gnome-session). Maybe we need a
phosh-session here? I'll open a bug for that.

That said I've also changed phosh's dependencies to not Recommend
`gnome-session` but `gnome-session-{bin,common` so it's easier to build
a stripped down system since e.g. GNOME Shell can be removed.

Cheers,
 -- Guido

> 
> Michel Le Bihan
> 
> ___
> Debian-on-mobile-maintainers mailing list
> debian-on-mobile-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers



Bug#968106: phosh: Shell doesn't start

2020-08-16 Thread Michel Le Bihan
Hello,

With `sudo mmdebstrap --include=linux-image-amd64,live-boot,xserver-
xorg-video-all,phosh,gnome-session-bin,libglib2.0-bin,gnome-settings-
daemon,policykit-1,phosh-osk-stub --arch amd64 bullseye debian-live-
root http://ftp.pl.debian.org/debian/` I got a working phosh setup with
a 966M root.

Michel Le Bihan



Bug#968106: phosh: Shell doesn't start

2020-08-16 Thread Michel Le Bihan
Hello,

I added `--aptopt='Apt::Install-Recommends "true"'` to mmdebstrap
options, so my command was `sudo mmdebstrap --aptopt='Apt::Install-
Recommends "true"' --include=linux-image-amd64,live-boot,xserver-xorg-
video-all,phosh --arch amd64 bullseye debian-live-root 
http://ftp.pl.debian.org/debian/`. I ended up with a 2.5G root that had
gdm3 and gnome-shell that aren't quite useful or even wanted on mobile
devices. When I selected Phosh as my shell and entered my password,
Phosh didn't start and I ended up back on the login screen. I was able
to start gnome-shell normally.

Also, why would a package required for Phosh to function only be
recommended? Are there setups where Phosh can be started without those
packages being installed?

Michel Le Bihan



Bug#968106: [Debian-on-mobile-maintainers] Bug#968106: phosh: Shell doesn't start

2020-08-16 Thread Guido Günther
Hi Bernhard,
On Sun, Aug 16, 2020 at 05:28:13PM +0200, Bernhard Übelacker wrote:
> Hello Michel Le Bihan,
> found this issue interesting and tried to get more information.
> 
> First the "trap int3" originates from here [1], and seems just
> a consequence of missing packages.
> 
> When installing following packages the user interface
> could successfully start, without changing the VM vga "hardware".
> 
>   systemctl stop phosh
>   apt update
>   apt install --no-install-recommends --no-install-suggests gnome-session-bin 
> libglib2.0-bin gnome-settings-daemon policykit-1 phosh-osk-stub
>   systemctl start phosh

Thanks for investigating. This brings up the issue if phosh should pull
in enough of gnome session to have the session file work and i think it
should. I'll add this to the next upload. We'll go with phosh-osk-stub
for now and do

squeekboard | phosh-osk-stub

once squeekboard is accepted.

I think we don't need the libglib2.0-bin and policykit-1 dependencies, right?

Cheers,
 -- Guido

> 
> Kind regards,
> Bernhard
> 
> 
> [1]
> (gdb) bt
> #0  _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
> #1  0x7f161ac595f5 in g_log_default_handler 
> (log_domain=log_domain@entry=0x55b43a8e7164 "phoc-server", 
> log_level=log_level@entry=6, message=message@entry=0x55b43b7dc1d0 "Could not 
> create backend", unused_data=unused_data@entry=0x0) at ../../..
> /glib/gmessages.c:3123
> #2  0x7f161ac5983c in g_logv (log_domain=0x55b43a8e7164 
> "phoc-server", log_level=G_LOG_LEVEL_ERROR, format=, 
> args=args@entry=0x7ffdc3657270) at ../../../glib/gmessages.c:1350
> #3  0x7f161ac59a1f in g_log 
> (log_domain=log_domain@entry=0x55b43a8e7164 "phoc-server", 
> log_level=log_level@entry=G_LOG_LEVEL_ERROR, 
> format=format@entry=0x55b43a8e7170 "Could not create backend") at 
> ../../../glib/gmessages.c:1415
> #4  0x55b43a8d1502 in phoc_server_constructed (object=0x55b43b7d8010) 
> at ../src/server.c:139
> #5  0x7f161ad41704 in g_object_new_internal 
> (class=class@entry=0x55b43b7d7b70, params=params@entry=0x0, 
> n_params=n_params@entry=0) at ../../../gobject/gobject.c:1977
> #6  0x7f161ad42f0d in g_object_new_with_properties 
> (object_type=94232580553008, n_properties=0, names=names@entry=0x0, 
> values=values@entry=0x0) at ../../../gobject/gobject.c:2105
> #7  0x7f161ad43961 in g_object_new (object_type=, 
> first_property_name=first_property_name@entry=0x0) at 
> ../../../gobject/gobject.c:1777
> #8  0x55b43a8d17ed in phoc_server_get_default () at 
> ../src/server.c:212
> #9  0x55b43a8d0f89 in main (argc=, argv= out>) at ../src/main.c:131

> 
> # Bullseye/testing amd64 qemu VM 2020-08-16
> 
> 
> apt update
> apt dist-upgrade
> 
> 
> apt install systemd-coredump mmdebstrap squashfs-tools sddm xserver-xorg 
> openbox xterm mc qemu-system-x86
> 
> 
> su -
> mkdir /home/benutzer/test
> cd/home/benutzer/test
> 
> mmdebstrap --include=linux-image-amd64,live-boot,xserver-xorg-video-all,phosh 
> --arch amd64 sid debian-live-root 
> http://192.168.178.25:/debian-11-bullseye-deb.debian.org/
> 
> 
> root@debian:/home/benutzer/test# mmdebstrap 
> --include=linux-image-amd64,live-boot,xserver-xorg-video-all,phosh --arch 
> amd64 sid debian-live-root 
> http://192.168.178.25:/debian-11-bullseye-deb.debian.org/
> I: automatically chosen mode: root
> I: chroot architecture amd64 is equal to the host's architecture
> I: running apt-get update...
> done
> I: downloading packages with apt...
> done
> I: extracting archives...
> done
> I: installing packages...
> done
> I: downloading apt...
> done
> I: installing apt...
> done
> I: installing remaining packages inside the chroot...
> done
> I: cleaning package lists and apt cache...
> done
> done
> 
> 
> chroot debian-live-root passwd
> chroot debian-live-root useradd -m -s /bin/bash -p $(openssl passwd -1 
> 123456) user
> chroot debian-live-root systemctl enable phosh
> cp debian-live-root/vmlinuz .
> cp debian-live-root/initrd.img .
> mksquashfs debian-live-root root.squashfs -comp lz4
> exit
> 
> cd /home/benutzer/test
> python3 -m http.server -b localhost 8080
> 
> cd /home/benutzer/test
> export DISPLAY=:0
> qemu-system-x86_64 \
> -machine accel=kvm \
> -m 2G \
> -device virtio-net-pci,netdev=net0 \
> -serial stdio -monitor vc \
> -netdev 
> user,id=net0,hostfwd=tcp::-:22,guestfwd=tcp:10.0.2.252:8080-tcp:localhost:8080,hostname=debian-live
>  \
> -kernel ./vmlinuz \
> -initrd ./initrd.img \
> -append "console=ttyS0 ip=frommedia boot=live nopersistence 
> fetch=http://10.0.2.252:8080/root.squashfs;
> 
> 
> 
> 
> [   28.531593] traps: phoc[354] trap int3 ip:7f45cbc70585 sp:7fff27e0a260 
> error:0 in libglib-2.0.so.0.6400.4[7f45cbc36000+81000]
> [   33.884796] traps: phoc[373] trap int3 ip:7f136d421585 sp:7ffce5012e30 
> error:0 in 

Bug#968106: [Debian-on-mobile-maintainers] Bug#968106: Bug#968106: Bug#968106: phosh: Shell doesn't start

2020-08-16 Thread Guido Günther
Hi,
On Sun, Aug 16, 2020 at 05:50:15PM +0200, Jonas Smedegaard wrote:
> Quoting Bernhard Übelacker (2020-08-16 17:28:13)
> > Hello Michel Le Bihan,
> > found this issue interesting and tried to get more information.
> > 
> > First the "trap int3" originates from here [1], and seems just
> > a consequence of missing packages.
> > 
> > When installing following packages the user interface
> > could successfully start, without changing the VM vga "hardware".
> > 
> >   systemctl stop phosh
> >   apt update
> >   apt install --no-install-recommends --no-install-suggests 
> > gnome-session-bin libglib2.0-bin gnome-settings-daemon policykit-1 
> > phosh-osk-stub
> >   systemctl start phosh
> 
> I interpret that as there really is no bug here;
> 
> Suppressing recommendations is meant for exotic use-cases and therefore 
> suppressing multiple recommendations quite likely leads to a broken 
> unsupportable result.
> 
> Beware that mmdebstrap suppresses recommends by default.
> 
> mmdebstrap is not doing anything wrong: it is a powerful tool which can 
> do powerful good or powerful breakage depending on how it is used.

We don't have a 'keyboard' (either stub or real) nor
gnome-settings-daemon in 'recommends' - that at least should be fixed.
Cheers,
 -- Guido

> 
> 
>  - Jonas
> 
> -- 
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
> 
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private



> ___
> Debian-on-mobile-maintainers mailing list
> debian-on-mobile-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers



Bug#968106: [Debian-on-mobile-maintainers] Bug#968106: Bug#968106: phosh: Shell doesn't start

2020-08-16 Thread Jonas Smedegaard
Quoting Bernhard Übelacker (2020-08-16 17:28:13)
> Hello Michel Le Bihan,
> found this issue interesting and tried to get more information.
> 
> First the "trap int3" originates from here [1], and seems just
> a consequence of missing packages.
> 
> When installing following packages the user interface
> could successfully start, without changing the VM vga "hardware".
> 
>   systemctl stop phosh
>   apt update
>   apt install --no-install-recommends --no-install-suggests gnome-session-bin 
> libglib2.0-bin gnome-settings-daemon policykit-1 phosh-osk-stub
>   systemctl start phosh

I interpret that as there really is no bug here;

Suppressing recommendations is meant for exotic use-cases and therefore 
suppressing multiple recommendations quite likely leads to a broken 
unsupportable result.

Beware that mmdebstrap suppresses recommends by default.

mmdebstrap is not doing anything wrong: it is a powerful tool which can 
do powerful good or powerful breakage depending on how it is used.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature


Bug#968106: [Debian-on-mobile-maintainers] Bug#968106: phosh: Shell doesn't start

2020-08-16 Thread Bernhard Übelacker
Hello Michel Le Bihan,
found this issue interesting and tried to get more information.

First the "trap int3" originates from here [1], and seems just
a consequence of missing packages.

When installing following packages the user interface
could successfully start, without changing the VM vga "hardware".

  systemctl stop phosh
  apt update
  apt install --no-install-recommends --no-install-suggests gnome-session-bin 
libglib2.0-bin gnome-settings-daemon policykit-1 phosh-osk-stub
  systemctl start phosh

Kind regards,
Bernhard


[1]
(gdb) bt
#0  _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
#1  0x7f161ac595f5 in g_log_default_handler 
(log_domain=log_domain@entry=0x55b43a8e7164 "phoc-server", 
log_level=log_level@entry=6, message=message@entry=0x55b43b7dc1d0 "Could not 
create backend", unused_data=unused_data@entry=0x0) at ../../..
/glib/gmessages.c:3123
#2  0x7f161ac5983c in g_logv (log_domain=0x55b43a8e7164 "phoc-server", 
log_level=G_LOG_LEVEL_ERROR, format=, 
args=args@entry=0x7ffdc3657270) at ../../../glib/gmessages.c:1350
#3  0x7f161ac59a1f in g_log (log_domain=log_domain@entry=0x55b43a8e7164 
"phoc-server", log_level=log_level@entry=G_LOG_LEVEL_ERROR, 
format=format@entry=0x55b43a8e7170 "Could not create backend") at 
../../../glib/gmessages.c:1415
#4  0x55b43a8d1502 in phoc_server_constructed (object=0x55b43b7d8010) 
at ../src/server.c:139
#5  0x7f161ad41704 in g_object_new_internal 
(class=class@entry=0x55b43b7d7b70, params=params@entry=0x0, 
n_params=n_params@entry=0) at ../../../gobject/gobject.c:1977
#6  0x7f161ad42f0d in g_object_new_with_properties 
(object_type=94232580553008, n_properties=0, names=names@entry=0x0, 
values=values@entry=0x0) at ../../../gobject/gobject.c:2105
#7  0x7f161ad43961 in g_object_new (object_type=, 
first_property_name=first_property_name@entry=0x0) at 
../../../gobject/gobject.c:1777
#8  0x55b43a8d17ed in phoc_server_get_default () at ../src/server.c:212
#9  0x55b43a8d0f89 in main (argc=, argv=) 
at ../src/main.c:131

# Bullseye/testing amd64 qemu VM 2020-08-16


apt update
apt dist-upgrade


apt install systemd-coredump mmdebstrap squashfs-tools sddm xserver-xorg 
openbox xterm mc qemu-system-x86


su -
mkdir /home/benutzer/test
cd/home/benutzer/test

mmdebstrap --include=linux-image-amd64,live-boot,xserver-xorg-video-all,phosh 
--arch amd64 sid debian-live-root 
http://192.168.178.25:/debian-11-bullseye-deb.debian.org/


root@debian:/home/benutzer/test# mmdebstrap 
--include=linux-image-amd64,live-boot,xserver-xorg-video-all,phosh --arch amd64 
sid debian-live-root 
http://192.168.178.25:/debian-11-bullseye-deb.debian.org/
I: automatically chosen mode: root
I: chroot architecture amd64 is equal to the host's architecture
I: running apt-get update...
done
I: downloading packages with apt...
done
I: extracting archives...
done
I: installing packages...
done
I: downloading apt...
done
I: installing apt...
done
I: installing remaining packages inside the chroot...
done
I: cleaning package lists and apt cache...
done
done


chroot debian-live-root passwd
chroot debian-live-root useradd -m -s /bin/bash -p $(openssl passwd -1 123456) 
user
chroot debian-live-root systemctl enable phosh
cp debian-live-root/vmlinuz .
cp debian-live-root/initrd.img .
mksquashfs debian-live-root root.squashfs -comp lz4
exit

cd /home/benutzer/test
python3 -m http.server -b localhost 8080

cd /home/benutzer/test
export DISPLAY=:0
qemu-system-x86_64 \
-machine accel=kvm \
-m 2G \
-device virtio-net-pci,netdev=net0 \
-serial stdio -monitor vc \
-netdev 
user,id=net0,hostfwd=tcp::-:22,guestfwd=tcp:10.0.2.252:8080-tcp:localhost:8080,hostname=debian-live
 \
-kernel ./vmlinuz \
-initrd ./initrd.img \
-append "console=ttyS0 ip=frommedia boot=live nopersistence 
fetch=http://10.0.2.252:8080/root.squashfs;




[   28.531593] traps: phoc[354] trap int3 ip:7f45cbc70585 sp:7fff27e0a260 
error:0 in libglib-2.0.so.0.6400.4[7f45cbc36000+81000]
[   33.884796] traps: phoc[373] trap int3 ip:7f136d421585 sp:7ffce5012e30 
error:0 in libglib-2.0.so.0.6400.4[7f136d3e7000+81000]
[   39.221241] traps: phoc[381] trap int3 ip:7f99bb354585 sp:7ffd8b465610 
error:0 in libglib-2.0.so.0.6400.4[7f99bb31a000+81000]
[   44.560172] traps: phoc[389] trap int3 ip:7f0c127e8585 sp:7fff4ec1e510 
error:0 in libglib-2.0.so.0.6400.4[7f0c127ae000+81000]
[   49.897137] traps: phoc[397] trap int3 ip:7fea829a4585 sp:7ffd2f846bc0 
error:0 in libglib-2.0.so.0.6400.4[7fea8296a000+81000]
...
[  257.428198] traps: phoc[1618] trap int3 ip:7f61de676585 sp:7fff9ffe6490 
error:0 in libglib-2.0.so.0.6400.4[7f61de63c000+81000]

echo "deb http://192.168.178.25:/debian-11-bullseye-debug.deb.debian.org/ 
sid-debug main contrib non-free" >> /etc/apt/sources.list

apt update
apt install systemd-coredump openssh-server 

Bug#968106: [Debian-on-mobile-maintainers] Bug#968106: phosh: Shell doesn't start

2020-08-09 Thread Guido Günther
Hi,
On Sat, Aug 08, 2020 at 08:09:24PM +0200, Michel Le Bihan via 
Debian-on-mobile-maintainers wrote:
> Package: phosh
> Version: 0.4.3-1
> Severity: grave
> Justification: renders package unusable
> 
> Hello,
> 
> On a freshly created Debian sid live system:
> ```
> sudo mmdebstrap --include=linux-image-amd64,live-boot,xserver-xorg-video-
> all,phosh --arch amd64 sid debian-live-root http://ftp.pl.debian.org/debian/
> sudo chroot debian-live-root passwd
> sudo chroot debian-live-root useradd -m -s /bin/bash -p $(openssl passwd -1
> 123456) user
> sudo chroot debian-live-root systemctl enable phosh
> cp debian-live-root/vmlinuz .; cp debian-live-root/initrd.img .
> sudo mksquashfs debian-live-root root.squashfs -comp lz4
> python3 -m http.server -b localhost 8080
> qemu-system-x86_64 -machine accel=kvm -m 4G -device virtio-net-pci,netdev=net0
> -serial stdio -monitor vc -netdev
> user,id=net0,hostfwd=tcp::-:22,guestfwd=tcp:10.0.2.252:8080-tcp:localhost:8080,hostname=debian-
> live -kernel ./vmlinuz -initrd ./initrd.img -append "console=ttyS0
> ip=frommedia boot=live nopersistence
> fetch=http://10.0.2.252:8080/root.squashfs;
> ```
> (last command is to start the test VM)
> 
> Phosh doesn't start. On the console I see:
> ```
> traps: phoc[362] trap int3 ip:7f684a6d9585 sp:7ffccc2cfe90 error:0 in
> libglib-2.0.so.0.6400.4[7f684a69f000+81000]
> ```

Your VM likely DRM capable GPU (see e.g. drm_info).
 -- Guido



Bug#968106: phosh: Shell doesn't start

2020-08-08 Thread Michel Le Bihan
Package: phosh
Version: 0.4.3-1
Severity: grave
Justification: renders package unusable

Hello,

On a freshly created Debian sid live system:
```
sudo mmdebstrap --include=linux-image-amd64,live-boot,xserver-xorg-video-
all,phosh --arch amd64 sid debian-live-root http://ftp.pl.debian.org/debian/
sudo chroot debian-live-root passwd
sudo chroot debian-live-root useradd -m -s /bin/bash -p $(openssl passwd -1
123456) user
sudo chroot debian-live-root systemctl enable phosh
cp debian-live-root/vmlinuz .; cp debian-live-root/initrd.img .
sudo mksquashfs debian-live-root root.squashfs -comp lz4
python3 -m http.server -b localhost 8080
qemu-system-x86_64 -machine accel=kvm -m 4G -device virtio-net-pci,netdev=net0
-serial stdio -monitor vc -netdev
user,id=net0,hostfwd=tcp::-:22,guestfwd=tcp:10.0.2.252:8080-tcp:localhost:8080,hostname=debian-
live -kernel ./vmlinuz -initrd ./initrd.img -append "console=ttyS0
ip=frommedia boot=live nopersistence
fetch=http://10.0.2.252:8080/root.squashfs;
```
(last command is to start the test VM)

Phosh doesn't start. On the console I see:
```
traps: phoc[362] trap int3 ip:7f684a6d9585 sp:7ffccc2cfe90 error:0 in
libglib-2.0.so.0.6400.4[7f684a69f000+81000]
```

When attempting to start it manually:
```
user@debian:~$ phoc

(phoc:468): phoc-wlroots-CRITICAL **: 18:03:33.384:
[backend/session/logind.c:760] Failed to get seat id: No data available

(phoc:468): phoc-wlroots-CRITICAL **: 18:03:33.393: [backend/session/direct-
ipc.c:30] Do not have root privileges; cannot become DRM master

(phoc:468): phoc-wlroots-CRITICAL **: 18:03:33.396:
[backend/session/session.c:96] Failed to load session backend

(phoc:468): phoc-wlroots-CRITICAL **: 18:03:33.405: [backend/backend.c:286]
Failed to start a DRM session

(phoc:468): phoc-server-ERROR **: 18:03:33.407: Could not create backend
[   76.891092] traps: phoc[468] trap int3 ip:7feeea992585 sp:7ffe555d1130
error:0 in libglib-2.0.so.0.6400.4[7feeea958000+81000]
Trace/breakpoint trap
```

```
user@debian:~$ phoc -E '/usr/bin/phosh -U' -C /usr/share/phosh/phoc.ini

(phoc:517): phoc-wlroots-CRITICAL **: 18:04:01.976:
[backend/session/logind.c:760] Failed to get seat id: No data available

(phoc:517): phoc-wlroots-CRITICAL **: 18:04:01.978: [backend/session/direct-
ipc.c:30] Do not have root privileges; cannot become DRM master

(phoc:517): phoc-wlroots-CRITICAL **: 18:04:01.981:
[backend/session/session.c:96] Failed to load session backend

(phoc:517): phoc-wlroots-CRITICAL **: 18:04:01.983: [backend/backend.c:286]
Failed to start a DRM session

(phoc:517): phoc-server-ERROR **: 18:04:01.986: Could not create backend
```

Starting phosh as root doesn't help:
```
root@debian:~# phosh
/usr/bin/phosh: 12: gnome-session: not found

(phoc:558): phoc-wlroots-CRITICAL **: 18:06:37.488:
[backend/session/logind.c:760] Failed to get seat id: No data available

(phoc:558): phoc-wlroots-CRITICAL **: 18:06:37.490:
[backend/session/direct.c:176] Could not get current tty number: Inappropriate
ioctl for device

(phoc:558): phoc-wlroots-CRITICAL **: 18:06:37.494:
[backend/session/session.c:96] Failed to load session backend

(phoc:558): phoc-wlroots-CRITICAL **: 18:06:37.496: [backend/backend.c:195]
failed to start a session

(phoc:558): phoc-wlroots-CRITICAL **: 18:06:37.498: [backend/backend.c:235]
failed to start backend 'drm'

(phoc:558): phoc-server-ERROR **: 18:06:37.500: Could not create backend
```

root@debian:~# phoc -E '/usr/bin/phosh -U' -C /usr/share/phosh/phoc.ini

(phoc:611): phoc-wlroots-CRITICAL **: 18:07:10.418:
[backend/session/logind.c:760] Failed to get seat id: No data available

(phoc:611): phoc-wlroots-CRITICAL **: 18:07:10.421:
[backend/session/direct.c:176] Could not get current tty number: Inappropriate
ioctl for device

(phoc:611): phoc-wlroots-CRITICAL **: 18:07:10.425:
[backend/session/session.c:96] Failed to load session backend

(phoc:611): phoc-wlroots-CRITICAL **: 18:07:10.428: [backend/backend.c:286]
Failed to start a DRM session

(phoc:611): phoc-server-ERROR **: 18:07:10.431: Could not create backend
```

It's also possible that I missed an important step, but I couldn't find
anything related in the doc.

Michel Le Bihan



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'unstable'), (600, 'experimental'), (500, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages phosh depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  fonts-lato   2.0-2
ii  gsettings-desktop-schemas3.36.1-1
ii  libc62.31-2
ii  libcairo21.16.0-4
pn  libfeedback-0.0-0