On 14 March 2017 at 21:32, Zbigniew Jędrzejewski-Szmek
wrote:
> gdm does not listen on the network, so whether or not gdm is still
> running after you log doesn't make that much difference. A local user
> can always cause gdm to be launched, by using the switch-user
> functionality.
> It would be
On Tue, Mar 14, 2017 at 08:05:20PM +, Tomasz Kłoczko wrote:
> On 14 March 2017 at 19:39, Zbigniew Jędrzejewski-Szmek
> wrote:
>
> > This doesn't show much, after being wrapped ;)
> >
>
> OK. Please tell a bit more about what kind of wrapping you been using here
> :)
In mutt your message appe
On 14 March 2017 at 19:39, Zbigniew Jędrzejewski-Szmek
wrote:
> This doesn't show much, after being wrapped ;)
>
OK. Please tell a bit more about what kind of wrapping you been using here
:)
> shows that gdm user is running whole set of processes running in full
> > separated X/Wayland session.
On Tue, 2017-03-14 at 19:39 +, Zbigniew Jędrzejewski-Szmek wrote:
> > Is it really needs to be so complicated?
>
> Yeah, mostly.
The login screen is a full gnome-shell instance run by the gdm user, as
you see from your process tree, so yes indeed.
The real problem here is the login screen sh
On Tue, Mar 14, 2017 at 06:37:05PM +, Tomasz Kłoczko wrote:
> Hi,
>
> Just started looking why in lat few weeks my gnome desktop los a lot of its
> previous speed. I found that already it is consequence of some issues in
> last chrome. Seems chrome developers managed to kill few most annoying
Hi,
Just started looking why in lat few weeks my gnome desktop los a lot of its
previous speed. I found that already it is consequence of some issues in
last chrome. Seems chrome developers managed to kill few most annoying
memory leaks causing that time to time crome processes associated with som
