gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading

Bug #1768207 reported by Tom
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

First time starting gnome-control-center after login, it takes ~70seconds to load and 100%CPU. Only first time starting I get "nvc0_screen_create:906 - Error allocating PGRAPH context for M2MF: -16".

In terminal "top" shows "gst-plugin-scan" is the offender. I installed two extensions initially but now all are switched off with same effect.

Second and other times starting, all is normal

Dell XPS 15, BIOS v1.9, Ubuntu 18.04LTS, *clean* install all default, just had to start nvidia to be able to login at all first time.

Revision history for this message
Tom (tom-lorinthe) wrote :

Might this have to do with nvidia driver 390 on optimus laptops? If I "sudo prime-select nvidia" the problem does not occur. But with "prime-select intel" it has...

Revision history for this message
Wouter van Os (wouter0100) wrote :

Also having this issue on my Acer aspire v3-772g with clean install on 18.04, although - no nvidia driver(s) installed. Really a clean install.

I tried installing the nvidia driver, but then I came across a different issue, which seems to be related to bug #1752053.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Wouter van Os (wouter0100) wrote :

An additional note is that this also seems to occur when I unlock my notebook and the settings is not yet open (but I used it before locking it).

Revision history for this message
Tom (tom-lorinthe) wrote :

@Wouter Last one is excellent find: I also noticed that sometimes my suspend leads to complete laptop freeze and force power off is necessary. Now you made realize it has to to with gnome-settings: I can only use suspend if I did not start gnome-settings before, even though it is not running when I try to suspend.

Note to myself: never use suspend after you used gnome-settings

Revision history for this message
Wouter van Os (wouter0100) wrote :

@Tom didn't realize that - I'm having the exact same issues that sometimes a reboot is required after suspend (which I use heavily).. Didn't connect that with gnome-settings yet.

Revision history for this message
Tom (tom-lorinthe) wrote :

For some reason, the issue does not longer exist with me. It might has to do with my /etc/default/grub where I have now GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=1 nouveau.modeset=0 nouveau.runpm=0"

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.