Hi, On Sun, 30 Dec 2018 22:46:16 +0100 "H. Nikolaus Schaller" <[email protected]> wrote:
> > Am 30.12.2018 um 20:58 schrieb Andreas Kemnade <[email protected]>: > > > > On Sun, 30 Dec 2018 20:06:34 +0100 > > "H. Nikolaus Schaller" <[email protected]> wrote: > > > >> Hi, > >> > >>> Am 30.12.2018 um 20:02 schrieb Andreas Kemnade <[email protected]>: > >>> > >>> Hi, > >>> > >>> On Sun, 30 Dec 2018 19:20:33 +0100 > >>> Mark Müller <[email protected]> wrote: > >>> > >>>> On 2018/12/30 0:07, Andreas Kemnade wrote: > >>>>> adduser purism > >>>>> is important. > >>>> > >>>> Thanks, that's right - I knew I forgot something... ;-) > >>>> > >>>>> I started a fresh debian buster using a patched > >>>>> cdebootstrap/libinstaller > >>>>> (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904699) > >>>>> > >>>>> Now I am with a non-working touchscreen but screen output. > >>>> > >>>> Well, touchscreen is working, but there seems to be a bug in > >>>> wlroots/rootston concerning how key presses are handled. I had a lengthy > >>>> test yesterday and a phosh developer helped me a lot. So here's what we > >>>> found so far: > >>>> > >>>> * "libinput debug-events" shows the touch events for the touch screen > >>>> correctly > >>>> > >>>> * try starting /usr/lib/wlroots/touch - it's a stand alone touch demo > >>>> for wlroots and needs a tty (f.ex. start it over ssh via "openvt -c 8 -- > >>>> /usr/lib/wlroots/touch" while rootston/phosh is not running) > >>>> > >>>> * you can start a GTK+3 app under X11 directly and you'll see touch > >>>> input working; same app won't work correctly, if you start it directly > >>>> with rootston > >>>> > >>>> * here's the issue i've found: the position of a touch event is read > >>>> correctly, but only the first touch seems to be correctly recognized as > >>>> a "pressed" event. Every following touch event seems to be categorized > >>>> as a "mouse over". > >> > >> Well, this categorization is done on GUI level. The /dev/input events > >> only know about mouse press/move/release. > >> > >> So it should not even be possible to generate mouse-over events, because > >> there are no position reports between release and press. > >> > >>>> > >>>> * you can try it with a real mouse on the GTA04 and start the "Calls" > >>>> app in Phosh. When your mouse is over a digit button, the button changes > >>>> it's appearance a bit (="mouse over") and when you click it (="pressed" > >>>> event), it changes as well. Remember how a button in "mouse > >>>> over"/"pressed" state looks like and then try to touch these buttons. > >>>> You'll see a really strange behaviour :D > >>>> > >>> I attached a keyboard+trackpad. I only come to a pin unlock dialog > >>> (even with the modem having its pin unlocked!). And there seems to > >>> be reception level displayed on the lockscreen. > >>> Anything more I forgot? > >>> needs the purism user be in special groups/have special properties? > >> > >> And does it have a well known default for the password (e.g. for ssh over > >> USB)? > >> > > I personally would block that user for ssh and use another one for it. > > Well, yes. But we need something for creating a bootable (plus useable) image > for demonstration purposes. Hardening the system is something for future study > and maybe Phosh will do it differently from how it is done currently. Or will > enforce to choose a new one on first boot. > Well, DenyUsers purism in /etc/sshd_config is simple. And then having a sane root password (for ssh access) at least would give some basic security. > > I manually created that user, so I gave him a sane password. I never > > thought that PIN=password here. > > So I'll try to adduser for the "default" pin Mark has mentioned in the other > mail. > changed the password here and then I could log in. I attached my patched usb hub (with keyboard+trackpad) to the gta04 and then I could play around a bit. Regards, Andreas
pgpR6jzbRnhnK.pgp
Description: OpenPGP digital signature
_______________________________________________ Community mailing list [email protected] http://lists.goldelico.com/mailman/listinfo.cgi/community http://www.tinkerphones.org
