← Back to team overview

ubuntu-phone team mailing list archive

Re: Sharing dynamic informations between the user session and the greeter

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Terry wrote on 07/03/14 14:39:
> 
> On Fri, Mar 7, 2014 at 5:39 AM, Matthew Paul Thomas 
> <mpt@xxxxxxxxxxxxx <mailto:mpt@xxxxxxxxxxxxx>> wrote:
>> 
>> But they behave very differently: music should keep playing at 
>> the lock screen but not the greeter, the camera and mic should 
>> keep recording at the lock screen but not the greeter, Touch
>> apps may allow limited access at the lock screen but not the
>> greeter, your preferred keyboard layout should persist at the
>> lock screen but not the greeter, screen magnification should
>> persist at the lock screen but not the greeter, and so on.
> 
> Well, keyboard layouts should work correctly per-user on the 
> greeter too.

Sorry, I was using "greeter" too loosely as a synonym for "login
screen", i.e. the screen that lets you choose between multiple accounts.

Ubuntu on a phone currently does not use a login screen, because there
are never multiple user accounts to choose from. Instead, when starting
the phone, you go directly to the lock screen (a.k.a. "welcome
screen") for the only account.

On multi-user devices, the login screen and lock screen might end up
being implemented by the same code, but whether they should be is part
of the question in the first place.

> And why not allow Touch apps on the greeter?  Imagine the first 
> boot (with an encrypted home, so we can't auto-login).  Why should 
> that behave much differently in terms of whether the user can take 
> photos or not?
> 
> ...

Whose photo library would the photos end up in? You can't assume they
should migrate to the account of whoever logs in next; that next login
might be your grandmother several days later.

- -- 
mpt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMdpzkACgkQ6PUxNfU6ecrrnQCePYV/ig9SJKKOI/2lck17+71a
qmgAniroardt9ZPyPhUZzHWn9JT1P0fF
=Sr03
-----END PGP SIGNATURE-----


Follow ups

References