touch not working on lockscreen
What problem did you encounter
Rebooted device, sat idle for 10seconds, touch not working
What is the current behaviour?
Touch not working
What is the expected behaviour?
Touch works
How to reproduce
I rebooted, sat idle for ~ 10 seconds, the arrow-up animation stops (clock still advances), but touch no longer works.
Quick 3 second video showing it not reacting to touch: 00067.MTS
Which version did you encounter the bug in?
-
I Compiled it myself. If you compiled phosh from source please provide the git revision via e.g. by running git log -1 --pretty=oneline
and pasting the output below. -
I used the precompiled Debian package (e.g. by running a prebuilt image). Please paste the output oof dpkg -s phosh
below.
Package: phosh
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 488
Maintainer: Guido Günther <agx@sigxcpu.org>
Architecture: arm64
Version: 0.0.3~567.gbp38a86e
Depends: dconf-gsettings-backend | gsettings-backend, libc6 (>= 2.17), libcairo2
(>= 1.2.4), libgcr-base-3-1 (>= 3.8.0), libgcr-ui-3-1 (>= 3.8.0), libgdk-pixbuf
2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.55.1), libgnome-desktop-3-17 (>= 3.17.92),
libgtk-3-0 (>= 3.13.7), libhandy-0.0-0 (>= 0.0~git20180429), libnm0 (>= 1.0.0),
libpam0g (>= 0.99.7.1), libpango-1.0-0 (>= 1.22.0), libpangocairo-1.0-0 (>= 1.1
4.0), libpulse-mainloop-glib0 (>= 0.99.1), libpulse0 (>= 0.99.1), libupower-glib
3 (>= 0.99.4-3~), libwayland-client0 (>= 1.9.91), fonts-lato
Recommends: gnome-session
Description: Pure Wayland shell for mobile devices
Phosh is a simple shell for Wayland compositors speaking the layer-surface
protocol. It currently supports
.
* a lockscreen
* brightness control and nighlight
* the gcr system-prompter interface
* enough of org.gnome.Mutter.DisplayConfig to make gnome-settings-daemon happy
* a homebutton that toggles a simple favorites menu
* status icons for battary and wwan
.
If you're not working on a Wayland compositor then this package is likely not
very useful for you.
Homepage: https://source.puri.sm/Librem5/phosh
What hardware are you running phosh on?
-
amd64 qemu image -
Librem5 devkit -
nested compositor. If so please give the full command you start phosh with. -
other (please elaborte)
Releveant logfiles
Please provide relevant logs. You can e.g. the logs since last boot read
with journalctl -b 0
.
-- Logs begin at Thu 2019-02-14 10:12:02 UTC, end at Thu 2019-05-30 23:22:17 UTC
May 30 23:20:40 pureos systemd[1537]: Listening on Sound System.
May 30 23:20:40 pureos systemd[1537]: Listening on GnuPG cryptographic agent and
May 30 23:20:40 pureos systemd[1537]: Listening on GnuPG cryptographic agent and
May 30 23:20:40 pureos systemd[1537]: Reached target Paths.
May 30 23:20:40 pureos systemd[1537]: Starting D-Bus User Message Bus Socket.
May 30 23:20:40 pureos systemd[1537]: Listening on GnuPG cryptographic agent and
May 30 23:20:40 pureos systemd[1537]: Listening on GnuPG network certificate man
May 30 23:20:40 pureos systemd[1537]: Listening on GnuPG cryptographic agent (ss
May 30 23:20:40 pureos systemd[1537]: Reached target Timers.
May 30 23:20:41 pureos systemd[1537]: Listening on D-Bus User Message Bus Socket
May 30 23:20:41 pureos systemd[1537]: Reached target Sockets.
May 30 23:20:41 pureos systemd[1537]: Reached target Basic System.
May 30 23:20:41 pureos systemd[1537]: Starting Sound Service...
May 30 23:20:41 pureos systemd[1537]: Started Hægtesse, a daemon for voice call
May 30 23:20:41 pureos systemd[1537]: Reached target Audio for voice calls.
May 30 23:20:41 pureos systemd[1537]: Reached target Default.
May 30 23:20:41 pureos phosh[1531]: 2019-05-30 23:20:41 - [rootston/config.c:370
May 30 23:20:41 pureos phosh[1531]: 2019-05-30 23:20:41 - [rootston/config.c:370
May 30 23:20:41 pureos phosh[1531]: 2019-05-30 23:20:41 - [backend/session/login
May 30 23:20:41 pureos phosh[1531]: 2019-05-30 23:20:41 - [backend/backend.c:128
May 30 23:20:41 pureos phosh[1531]: 2019-05-30 23:20:41 - [backend/drm/backend.c
May 30 23:20:41 pureos phosh[1531]: 2019-05-30 23:20:41 - [backend/drm/drm.c:60]