[opensuse] Ekiga config file?
Does anyone have any idea where Ekiga hides its configuration? I've got Ekiga installed (in openSUSE 12.1/KDE4.7.2), and want to import my config from my backup. I followed the steps here: http://wiki.ekiga.org/index.php/Troubleshooting#I_reinstalled_Linux_and_I_wa... ... so I copied over the .gconf/ekiga directory and contents and started up Ekiga... but it doesn't find any of the old settings at all. I've searched all over my /home, looking for other palces Ekiga could be hiding its config, but turned up nothing so far. I've killed gconfd-2, deleted .gconf/ekiga and restarted Ekiga... and it starts up using the basic settings I set in the first start wizard... and it recreates a very basic .gconf/ekiga. This is apparently not where it stores the SIP configuration information. So.. does anyone have any clue where Ekiga is hiding its main configuration? C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Mar 4, 2012 at 13:38, C
Does anyone have any idea where Ekiga hides its configuration?
I've got Ekiga installed (in openSUSE 12.1/KDE4.7.2), and want to import my config from my backup. I followed the steps here: http://wiki.ekiga.org/index.php/Troubleshooting#I_reinstalled_Linux_and_I_wa... ... so I copied over the .gconf/ekiga directory and contents and started up Ekiga... but it doesn't find any of the old settings at all.
I've searched all over my /home, looking for other palces Ekiga could be hiding its config, but turned up nothing so far. I've killed gconfd-2, deleted .gconf/ekiga and restarted Ekiga... and it starts up using the basic settings I set in the first start wizard... and it recreates a very basic .gconf/ekiga. This is apparently not where it stores the SIP configuration information.
So.. does anyone have any clue where Ekiga is hiding its main configuration?
Hmmm that is so... weird. I don't understand gconf at all :-P I rebooted and.. whiz bang, Ekiga picked up the config that was sitting in the .gconf/ekiga directory for hours beforehand. Weird that application level config changes are not picked up until after at least a logout/login. Anyway... it works.. and you can ignore me again :-) C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello C, Am Sonntag, 4. März 2012, 23:04:27 schrieb C:
On Sun, Mar 4, 2012 at 13:38, C
wrote: Does anyone have any idea where Ekiga hides its configuration? So.. does anyone have any clue where Ekiga is hiding its main configuration? Hmmm that is so... weird. I don't understand gconf at all :-P I rebooted and.. whiz bang, Ekiga picked up the config that was sitting in the .gconf/ekiga directory for hours beforehand. Weird that application level config changes are not picked up until after at least a logout/login. Thanks for that mail. That i have asked myself yesterday too. Maybe do you also know where Ekiga stores the Logindata for a Network? -- Sincerly yours Sascha Manns - open-slx GmbH Community Agent / Documentation Specialist Web (business): http://www.open-slx.com Web (private): http://saigkill.homelinux.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Mar 5, 2012 at 10:47, Sascha Manns
Am Sonntag, 4. März 2012, 23:04:27 schrieb C:
On Sun, Mar 4, 2012 at 13:38, C
wrote: Does anyone have any idea where Ekiga hides its configuration? So.. does anyone have any clue where Ekiga is hiding its main configuration? Hmmm that is so... weird. I don't understand gconf at all :-P I rebooted and.. whiz bang, Ekiga picked up the config that was sitting in the .gconf/ekiga directory for hours beforehand. Weird that application level config changes are not picked up until after at least a logout/login. Thanks for that mail. That i have asked myself yesterday too. Maybe do you also know where Ekiga stores the Logindata for a Network?
It all seems to be in the same place... in $home/.gconf/ekiga Somehow Ekiga hangs on to whatever is in there and doesn't release or update itself if you manually change the contents. The documentation says to simply exit Ekiga, killall gconfd-2 and restart Ekiga to get it to re-read the manually changed configuration, but I've yet to be able to get it to do that... I have to logout/login to see the chanegs. The network login data is buried in the XML files in that directory. If you're manually changing or want to completely wipe the setup, then exit Ekiga, kill gconfd-2, delete/change the .gconf/ekiga directory and... logout/in I guess... unless you can discover what other process is running that makes Ekiga retain the settings it has read and kill that too. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2012-03-05 at 10:57 +0100, C wrote:
On Mon, Mar 5, 2012 at 10:47, Sascha Manns
wrote: Am Sonntag, 4. März 2012, 23:04:27 schrieb C:
On Sun, Mar 4, 2012 at 13:38, C
wrote: Does anyone have any idea where Ekiga hides its configuration? So.. does anyone have any clue where Ekiga is hiding its main configuration? Hmmm that is so... weird. I don't understand gconf at all :-P I rebooted and.. whiz bang, Ekiga picked up the config that was sitting in the .gconf/ekiga directory for hours beforehand. Weird that application level config changes are not picked up until after at least a logout/login. Thanks for that mail. That i have asked myself yesterday too. Maybe do you also know where Ekiga stores the Logindata for a Network? It all seems to be in the same place... in $home/.gconf/ekiga Somehow Ekiga hangs on to whatever is in there and doesn't release or update itself if you manually change the contents.
No, Ekiga doesn't hang on to anything. Ekiga uses the gconf *service* for configuration - it gets and sets config via the gconfd session daemon. gconfd loads its databases when you start it an operates from RAM flushing changes to its persistent database. So you can't change settings beneath it. Use the gconf-tool and gconf-editor.
The network login data is buried in the XML files in that directory. If you're manually changing or want to completely wipe the setup, then exit Ekiga, kill gconfd-2, delete/change the .gconf/ekiga directory and... logout/in I guess... unless you can discover what other process is running that makes Ekiga retain the settings it has read and kill that too.
It probably stores passwords/credentials in the keyring.
On Mon, Mar 5, 2012 at 11:47, Adam Tauno Williams
Ekiga hangs on to whatever is in there and doesn't release or update itself if you manually change the contents.
No, Ekiga doesn't hang on to anything. Ekiga uses the gconf *service* for configuration - it gets and sets config via the gconfd session daemon. gconfd loads its databases when you start it an operates from RAM flushing changes to its persistent database. So you can't change settings beneath it. Use the gconf-tool and gconf-editor.
Uggh.. gconf-tool-2 is installed on my system... and it's unpleasant to use to say the least. I haven't installed gconf-editor. How do these line up with the fact that I simply wanted to "reuse" my old settings from a previous install (I re-installed my openSUSE system this past weekend, with a clean /home, copying over the settings (from my backup) I wanted to reuse/retain). The documentation here: http://wiki.ekiga.org/index.php/Troubleshooting#I_reinstalled_Linux_and_I_wa... didn't seem to work as indicated which is what prompted me to question things. How can you use gconftool-2 to import old settings? I suppose I could have copied over the old settings *before* I launched Ekiga for the first time post-install, but... I didn't. It's not a big deal.. just trying to understand how it works.. since it's pretty much completely different than anything I usually use (generally KDE apps, but I do use GTK apps as well). C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Adam Tauno Williams
-
C
-
Sascha Manns