[gnome-bluetooth] gnome-phone-manager + FC3 + me: no startup
Michael Kolmodin
Michael at kolmodin.net
Tue Jan 25 14:43:21 PST 2005
I'm trying to get gnome-phone-manager running on Fedora core 3; so far
without success. Configuration + compilation seems to be OK after the
std:: namespace patch. After starting the program I get:
$ gnome-phone-manager
** Message: New connection device is (null)
** Message: No device!
** Message: Exiting connect thread
[ a few seconds delay ]
conn_complete: status 0x04
^C
$
but no UI at all, it just sits there. (gnome-bluetooth-mamanger seems to
work OK out of the box, but it has errors concerning the gconfd API.)
I've been fiddling around for a while, and I have become suspicious
about the gconfd stuff. After enabling gconf-client debug printout I get
[snip]
gconf trace: Adding directory '/apps/gnome-phone-manager/prefs'
gconf trace: Adding notify to engine at '/apps/gnome-phone-manager/prefs'
gconf trace: Onelevel preload of '/apps/gnome-phone-manager/prefs'
gconf trace: Caching values in '/apps/gnome-phone-manager/prefs'
gconf trace: Doing remote query for
/apps/gnome-phone-manager/prefs/popup_mess
However, using gconf-editor I cannot see that the configuration
directory /apps/gnome-phone-manager'. It just doesn't exist, even if I
let gconfd shut down after logout. Some time, I cant remember how/when,
I think I noted that the app looked up a key which had a name like
"no_UI" (???) and from this decided not to show the UI.
To believe is, however, to not know. The only thing I'm absolutely sure
of is that I want to see the UI. Any clue out there?
--michael
More information about the gnome-bluetooth
mailing list