[Bug 1856516] Re: Excessive memory usage by gnome-shell in 19.10

2020-02-10 Thread Simon Lord
I just spent the day researching this only to discover it's an ongoing
bug which is several years old.

I outline my results here: https://forum.level1techs.com/t/ubuntu-19-10
-gnome-shell-memory-leak/153376

To summarize that post, simply moving windows and toggling workspaces
causes gnome-shell to jump from 200mb to 1.2G of ram use in a matter of
minutes (several hours if I'm not intentionally trying to open apps and
move windows around).

This bug is affecting me on Ubuntu 19.10 running on an Aorus Master X570
with a 3950X and 64G of memory.  The machine is only a few weeks old.
It's a clean install.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1856516

Title:
  Excessive memory usage by gnome-shell in 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2019-11-04 Thread Simon Lord
Created an account just to confirm I too am hit with this bug.

Started as 19.04 running on Ryzen 2700X, 32G, RTX2060 with nVidia 430
drivers.

After successfully upgrading from 19.04 to 19.10, or so I thought, I was
met with the login screen upon system reboot.  This was very strange as
I had auto-login set to true with 19.04 so I should *not* be seeing this
login screen.

My linux-fu is weak as I'm currently transitioning from OS X to Linux
and was completely lost on how to continue.  The solution was to go
scorched earth and do a clean install of 19.10.  My /home directory is
on a separate drive so I was confident things would work out ok.

The clean install went well but at this point I was still unaware that
the issue was related to the auto-login (and perhaps nvidia 435 combo).
So after modding my fstab and rebooting I was confronted again with the
login screen and not being able to login (ie, no matter how many times I
typed my password the login screen would ignore me).

After some Googling I discovered this page you are reading now.

I did another clean install but this time I mv'd .config and .local in
my /home directory to borked.config and borked.local (as mentioned, my
linux-fu is weak but I assumed that my previous auto-login setting is
stored in a pref file *somewhere* in either of those directories).

After updating fstab I then toggled the auto-login a few times to ensure
the prefs would show it clearly in the OFF position.  Then I rebooted.

SUCCESS.  The login screen appeared but this time I *was* able to login
— I spent another hour moving files from my *borks* back to .config and
.local and I'm mostly back to normal.

As mentioned by anidotnet above, this is my second update (18.04 > 18.10
&& 19.04 > 19.10) and both were extremely unpleasant with this latest
update taking the cake.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs