ray field
September 22nd, 2020, 05:31 PM
Installed 20.04 last week, and been experiencing strangeness with the display -- most notably now, that my screenlock times out seconds after I stop typing/mousing, whatever I set the timeout to. Using the box at home, I don't password protect the lock.
It's a new GeForce1030 card with the Nvidia drivers, but I really don't think it's a driver issue, had similar issues with the Nouveau drivers.
Other information:
1) I keep root on a separate partition from /home, but for reasons not worth going into, instead of installing 20.04 over 16.04, I reformatted and repartitioned and copied a /home backup -- only reason I bring it up is because I wonder if something left there is messing with my configuration?
2) syslog shows countless instances on the order of every 3-4 seconds of "ep 22 08:05:14 Xxxxx gnome-shell[14113]: Object .Gjs_ui_pointerA11yTimeout_PieTimer (0x5566dc58fc20), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs."
It's a new GeForce1030 card with the Nvidia drivers, but I really don't think it's a driver issue, had similar issues with the Nouveau drivers.
Other information:
1) I keep root on a separate partition from /home, but for reasons not worth going into, instead of installing 20.04 over 16.04, I reformatted and repartitioned and copied a /home backup -- only reason I bring it up is because I wonder if something left there is messing with my configuration?
2) syslog shows countless instances on the order of every 3-4 seconds of "ep 22 08:05:14 Xxxxx gnome-shell[14113]: Object .Gjs_ui_pointerA11yTimeout_PieTimer (0x5566dc58fc20), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs."