Is it possible to disable the gsd-colorprocess please? this process keeps resetting my brightness with xrandr and i want to disable it on startup tried this. Did you try this option from the man page? these plugins can be individually disabled by changing the gsettings key org.gnome.settings-daemon.plugins. plugin-name.active, where plugin-name is the name of the plugin.
To see a list of all plugins, use the command gsettings list-children org.gnome.settings-daemon.plugins Thanks for this! I'll look into it and report back later this evening! It returns to a normal state after I kill the "gsd-color" process from the system monitor. For instance, gsd-color took 1Gb of memory while working, but after putting it to sleep overnight, it shows usage of 28Gb memory the next day. However, gnome-settings-daemon is necessary as it is needed for ensuring theme, keybindings, font hinting, and various other settings are handled properly.
This process is also used under Unity 7, but under Unity was forked as unity. I'm on a Linux Fedora 23 and I recently noticed that my gnome-shell process constantly uses 100% of one CPU (reported by htop, no visible applications running). There are some hints out there which cover some workarounds for bugs in the gnome-shell (deactivating background logo, re-aligning the monitors) but none of them help.
I tried to run. Hello, So i'm using xrandr to push the brightness above 1, the problem is after reboot or opening some app (it's random) it just reset. I found a solution on the net that consist to disable The GNOME Settings Daemon's color plugin from startup, this didn't work for me, i still see the "gsd-color" process i actually tried to pause the gsd-color and the reset didn't happen so i'm.
It's a file created by NoMachine during the installation but I don't know why this prevent gsd-color to create devices Last edited by Leeo97one (2017-08-17 12:41:42). Hi Straight to the point, as the title, i did some annoying findings about gsd-color (using gnome as actual desktop environment) Here's the issue. The Xorg with uid gdm has a child gsd.
gsd-color, gsd-keyboard, gsd-media-keys, and gsd-power not running after logging in after a gnome-shell crash Today, after hitting an unrelated gnome-shell crash (mutter#842 (closed)) and logging back into gnome-shell, Super+L doesn't lock my screen and my custom Super+T shortcut doesn't open a terminal.