Gnome 3.28 Settings Manager bug

---

Hi guys,

Just installed Antergos, which brought in the new 3.28 meta packages.

The Gnome settings manager appears to have a bug issue, as it will time out in a lockup while open, or just time out while not opening.

Other times, it will open and function properly.

Thanks,
GM

i got this too (gnome-control-center) lagging on open up, or on open tabs for some settings, like user-management.

Open from terminal do not give any hint, but journal gives logs on changing tabs:

Mär 28 10:24:11 empowered64 dbus-daemon[339]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.497' (uid=1000 pid=22508 comm="gnome-control-center ")
Mär 28 10:24:11 empowered64 systemd[1]: Starting Time & Date Service...
Mär 28 10:24:11 empowered64 dbus-daemon[339]: [system] Successfully activated service 'org.freedesktop.timedate1'
Mär 28 10:24:11 empowered64 systemd[1]: Started Time & Date Service.
Mär 28 10:24:11 empowered64 pipewire[19760]: [E][module-protocol-native.c:278 connection_data()] protocol-native 0x5623d1fa5d70: got connection error
Mär 28 10:24:29 empowered64 pipewire[19760]: [E][module-protocol-native.c:278 connection_data()] protocol-native 0x5623d1fa5d70: got connection error
Mär 28 10:24:37 empowered64 dbus-daemon[339]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.497' (uid=1000 pid=22508 comm="gnome-control-center ")
Mär 28 10:24:37 empowered64 systemd[1]: Starting Hostname Service...
Mär 28 10:24:37 empowered64 dbus-daemon[339]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mär 28 10:24:37 empowered64 systemd[1]: Started Hostname Service.
Mär 28 10:24:40 empowered64 kernel: INFO: task python:518 blocked for more than 120 seconds.
Mär 28 10:24:40 empowered64 kernel:       Tainted: P           O     4.15.13-1-ARCH #1
Mär 28 10:24:40 empowered64 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mär 28 10:24:40 empowered64 kernel: python          D    0   518      1 0x00000004
Mär 28 10:24:40 empowered64 kernel: Call Trace:
Mär 28 10:24:40 empowered64 kernel:  ? __schedule+0x24b/0x8c0
Mär 28 10:24:40 empowered64 kernel:  schedule+0x32/0x90
Mär 28 10:24:40 empowered64 kernel:  schedule_preempt_disabled+0x14/0x20
Mär 28 10:24:40 empowered64 kernel:  __mutex_lock.isra.0+0x274/0x520
Mär 28 10:24:40 empowered64 kernel:  ? pp_ioctl+0x35/0x910 [ppdev]
Mär 28 10:24:40 empowered64 kernel:  pp_ioctl+0x35/0x910 [ppdev]
Mär 28 10:24:40 empowered64 kernel:  do_vfs_ioctl+0xa4/0x630
Mär 28 10:24:40 empowered64 kernel:  SyS_ioctl+0x74/0x80
Mär 28 10:24:40 empowered64 kernel:  do_syscall_64+0x74/0x190
Mär 28 10:24:40 empowered64 kernel:  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Mär 28 10:24:40 empowered64 kernel: RIP: 0033:0x7fc3dc12ed87
Mär 28 10:24:40 empowered64 kernel: RSP: 002b:00007fffe0214ea8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Mär 28 10:24:40 empowered64 kernel: RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fc3dc12ed87
Mär 28 10:24:40 empowered64 kernel: RDX: 00007fffe0214eb4 RSI: 0000000040047091 RDI: 0000000000000003
Mär 28 10:24:40 empowered64 kernel: RBP: 00007fffe0215040 R08: 0000000000000004 R09: 0000000000000000
Mär 28 10:24:40 empowered64 kernel: R10: 0000000000004000 R11: 0000000000000246 R12: 00007fffe0214f0c
Mär 28 10:24:40 empowered64 kernel: R13: 00007fffe0215140 R14: 00007fffe0214f40 R15: 0000000000000003

I got this task python:518 blocked prior GNOME 3.28 update but it comes up directly on opening some tabs in settings …

Happened to me a minute ago on another machine, running Arch + GNOME: “Settings window does not respond”.

i just install 3 optional dependencies for gnome-control-center + reinstall itself, and it starts without lagging

sudo pacman -S vino rygel gnome-user-share gnome-control-center

seems to work only on reinstalling gnome-control-center it works till reboot… so optional deps are not a solution…

A search for a solution in Internet unveils that the problem with not opening Gnome Control Center is a long-lasting story. A few examples.

• for the first time the problem was encountered back in 2012

• later people searched for a solution again in 2013

• and again in 2015

• in 2016

• as well as in 2017

• and now in 2018 the problem still persists

In other words, the problem practically exists since the first Gnome 3.0 release in 2011. Six years weren’t enough to find a reliable solution. A bit too long.

extra/gnome-session 3.28.0-1 1 -> 2

killall gnome-control-center

is helping, after this it starts

Why is this not a problem with other Linux versions? Like Manjao and Fedora.

@john-vore As I wrote above: the same happens occasionally on my other machine, running vanilla Arch.

No one knows what this is causing… so there can not be an answear for this, instead of that ArchLinux (and o Antergos itself also) using latest GNOME and Software, what most other Distros do not do…

Thank You, You guys are check.

@joekamprad said in Gnome 3.28 Settings Manager bug:

killall gnome-control-center

still not solved, but kill all helps:

killall gnome-control-center

inside terminal…

seems to work here as normal now!
Can you confirm?

@joekamprad Hanged once for me last night.

https://bbs.archlinux.org/viewtopic.php?id=235651

@joekamprad Not really a big pain, as it happens occasionally.

i find a hint on archforum:

sudo systemctl --global disable pipewire.socket

and reboot seem to solve this issue under gnome-xorg