I've just gotten a ThinkPad T470s set up with Fedora 25. After a few days of use, I now have gnome-settings-daemon
taking up a whole CPU core (100% in top
, 25% in the System Monitor GUI). There are two instances of gnome-settings-daemon
running, one under my user account and one under gdm
, and it is the gdm
-owned instance that is having this problem.
I've tried attaching a debugger to the process and it appears to be stuck in poll
whenever I interrupt it:
#0 0x00007f911f59a01d in poll () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007f911facc166 in g_main_context_poll (priority=<optimized out>, n_fds=7, fds=0x55576d83b560, timeout=<optimized out>, context=0x55576d379380) at gmain.c:4228
#2 g_main_context_iterate (context=0x55576d379380, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3924
#3 0x00007f911facc4f2 in g_main_loop_run (loop=0x55576d4e54b0) at gmain.c:4125
#4 0x00007f9121670175 in gtk_main () at gtkmain.c:1312
#5 0x000055576c8bd66b in main (argc=<optimized out>, argv=<optimized out>) at main.c:434
I found some earlier threads from the ~F17 days talking about a similar problem, but it involved checking the Xsession logs, and I'm running Wayland. I'm a bit stumped at this point.