Bug 146086 - gnome-bluetooth-manager: illegal configuration key
Summary: gnome-bluetooth-manager: illegal configuration key
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-bluetooth   
(Show other bugs)
Version: 3
Hardware: athlon
OS: Linux
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL: n/a
Depends On:
TreeView+ depends on / blocked
Reported: 2005-01-25 10:23 UTC by MIchael Kolmodin
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-05-31 10:41:31 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description MIchael Kolmodin 2005-01-25 10:23:11 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001

Description of problem:
gnome-bluetooth-manager: illegal configuration key, nothing happens
when clicking on "Properties".

Hunting down other problems I've noted that gnome-bluetooth-manager
tries to create a configuration directory named "Gnome Bluetooth
Manager". gconfd rejects this request since the key contains blanks.
The message at console when starting the application is:

(Bluetooth Device Manager:20523): GConf-CRITICAL **: file
gconf-client.c: line 553 (gconf_client_add_dir): assertion
`gconf_valid_key (dirname, NULL)' failed

I suspect that this is related to the fact that nothing happens when I
click on the "Properties" menu entry.

I also think that there should be a bug filed on gconfd for this: it
rejects the configuration key without any type of info like logging
etc. I've verified this in the source. Will not file such a bug
though; I've the necessary diffs to enable logging by now :-)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Start gnome-bluetooth-manager in terminal window.
2. See error message (above)
3. Click on the "Edit | Properties" menu entry


Actual Results:  Nothing

Expected Results:  No error printout, a Properties window displayed.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.