After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773685 - power: don't change backlight on non active sessions
power: don't change backlight on non active sessions
Status: RESOLVED DUPLICATE of bug 772537
Product: gnome-settings-daemon
Classification: Core
Component: power
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2016-10-30 00:21 UTC by Lionel Landwerlin
Modified: 2017-01-13 16:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
power: don't change backlight on non active sessions (1.51 KB, patch)
2016-10-30 00:21 UTC, Lionel Landwerlin 		none Details | Review

Description Lionel Landwerlin 2016-10-30 00:21:27 UTC 
The session (gnome-shell/gnome-settings-daemon) instance running in the
background of the currently logged in user is spamming syslog with these
messages :

Oct 30 00:12:29 airy pkexec[15646]: Debian-gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 53
Oct 30 00:12:29 airy gnome-settings-daemon.desktop[1082]: Error executing command as another user: Not authorized
Oct 30 00:12:29 airy gnome-settings-daemon.desktop[1082]: This incident has been reported.
Comment 1 Lionel Landwerlin 2016-10-30 00:21:31 UTC 
Created attachment 338783 [details] [review]
power: don't change backlight on non active sessions
Comment 2 Bastien Nocera 2016-10-31 13:28:27 UTC 
This is supposed to be fixed by the patches in bug 756539 and bug 764896. We're not supposed to Claim the iio-sensor-proxy, and therefore we're not supposed to receive events about it, so there's probably a bug in that area.

The patch attached here is a work-around. I'd rather get at the root cause.
Comment 3 mike bayer 2016-10-31 13:46:37 UTC 
Bastien -

I'm assuming you don't have access to an environment which reproduces this.   I can share any details you'd like about my system here.   If this is a hint, the problem does not occur when the machine is freshly booted.  For me, I have to put the laptop into suspend (e.g. via lid close) and then resume for the errors to start up.   I tried poking around the other day in that area, thinking perhaps something like uninstalling xscreensaver (which I apparently had installed) would have some impact but the results didn't change.
Comment 4 Emmanuele Bassi (:ebassi) 2016-10-31 14:56:02 UTC 
This happens to me straight from first boot, with no suspend/resume cycle in between.
Comment 5 Mike Auty 2017-01-02 12:20:39 UTC 
I wondered if this could somehow be related to gdm, but I can confirm this happens (after a suspend/resume) when running X directly as the user without gdm running in the background.
Comment 6 Bastien Nocera 2017-01-13 16:53:54 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 772537 ***