Bug 765777

Summary: gnome-settings-daemon using access() to log DEBUG messages
Product: [Fedora] Fedora Reporter: Yann Droneaud <yann>
Component: gnome-settings-daemonAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: bnocera, mkasik, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 12:08:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yann Droneaud 2011-12-09 11:57:51 UTC
While trying to trace gdm, gnome-shell and such in order to discover what's happening in bug 749521 and bug 760044

I have found /usr/libexec/gnome-settings-daemon using access(2) syscall in a quite strange way.

Here's an excerpt of strace output:

access("MARK: (null) main: start ", F_OK) = -1 ENOENT (No such file or directory)
access("MARK: (null) parse_args: start ", F_OK) = -1 ENOENT (No such file or directory)
access("MARK: gnome-settings-daemon parse_args: end ", F_OK) = -1 ENOENT (No such file or directory)
access("MARK: gnome-settings-daemon main: start opening gtk display", F_OK) = -1 ENOENT (No such file or directory)
access("MARK: gnome-settings-daemon main: end opening gtk display", F_OK) = -1 ENOENT (No such file or directory)
access("MARK: gnome-settings-daemon main: start gnome_settings_manager_new", F_OK) = -1 ENOENT (No such file or directory)
access("MARK: gnome-settings-daemon main: end gnome_settings_manager_new", F_OK) = -1 ENOENT (No such file or directory)
access("MARK: gnome-settings-daemon gnome_settings_manager_start: start ", F_OK) = -1 ENOENT (No such file or directory)
access("MARK: gnome-settings-daemon gnome_settings_manager_start: start initializing plugins", F_OK) = -1 ENOENT (No such file or directory)
access("MARK: gnome-settings-daemon main: end ", F_OK) = -1 ENOENT (No such file or directory)


It's clearly some DEBUG messages that should be recorded in either .xsession-errors or syslog().

Comment 1 Yann Droneaud 2011-12-09 13:26:39 UTC
According to a GNOME developer, it is related to

http://people.gnome.org/~federico/news-2006-03.html#login-time-2

I think it should be disable by default: desktop user doesn't need this.

Comment 2 Fedora End Of Life 2013-01-16 12:07:48 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 12:08:57 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.