(Bluetooth Device Manager:30252): GConf-CRITICAL **: file
gconf-client.c: line 547 (gconf_client_add_dir): assertion
`gconf_valid_key (dirname, NULL)' failed
Jan 24 00:39:27 nasu gconfd (twillber-29351): Failed to write
Failed to open
No such file or directory
Jan 24 00:39:27 nasu gconfd (twillber-29351): Failed to sync one or
more sources: Failed to write some configuration data to disk
This happens always after scanning for bluetooth devices, and exiting
scan for devices (found one device)
This error causes that next time starting the gnome-bluetooth-manager,
the device list is empty.
I don't have "/home/twillber/.gconf/system/bluetooth" in my system.
Either nothing created it, or I removed it at some point.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thank you in advance.
(this message is mass message)