Hello,
I have ekiga from the current Debian unstable (it's version 2.0.3). One
day I had to restart my computer and since then ekiga does not start
anymore. That means that starting ekiga in a console does not output
anything, does not show a GUI but is also not terminating, so actually
it is runn
On Sun, 11 Feb 2007 12:56:19 +0100
Tobias Eberle <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have ekiga from the current Debian unstable (it's version 2.0.3).
> One day I had to restart my computer and since then ekiga does not
> start anymore. That means that starting ekiga in a console does not
>
On dim, 2007-02-11 at 12:56 +0100, Tobias Eberle wrote:
> Hello,
Hi Tobias,
>
> I have ekiga from the current Debian unstable (it's version 2.0.3). One
> day I had to restart my computer and since then ekiga does not start
> anymore. That means that starting ekiga in a console does not output
> a
Hello Fabrice,
> Did you try to run gconf-editor and see if the key
> "/apps/ekiga/general/user_interface/start_hidden is active" ? (there
> should be a way to display that pair key/value from CLI, but I don't
> remember it)
> If yes either deactivate it, either try to check if your notfication
>
Hello Jan,
> Can you run it under gdb?
> $ gdb $(which ekiga)
> once it was killed:
> (gdb) threads apply all bt
Ekiga does not crash so "once it was killed" is not possible only "after
I have killed it".
starting ekiga leads to lots of "no debugging symbols found" and
...
[Thread debugging usin
Hello,
> > "/apps/ekiga/general/user_interface/start_hidden is active" ? (there
> > should be a way to display that pair key/value from CLI, but I don't
> > remember it)
Is there a way to delete /apps/ekiga/? Maybe it helps...
Tobias
___
ekiga-list ma
Le dimanche 11 février 2007 à 13:59 +0100, Tobias Eberle a écrit :
> Hello Fabrice,
>
> > Did you try to run gconf-editor and see if the key
> > "/apps/ekiga/general/user_interface/start_hidden is active" ? (there
> > should be a way to display that pair key/value from CLI, but I don't
> > remembe
On Sun, 11 Feb 2007 15:10:27 +0100
Damien Sandras <[EMAIL PROTECTED]> wrote:
> > It was disabled and it does not change anything if it is enabled or
> > disabled.
> >
>
> Is accessibility enabled ?
Yes, also my next question. There are many mutexes waiting.
J.
--
"One of the main causes of
As for me, I have a bit different settings:
> auth enable;
> encrypt enable;
> #
> security auto;
>
>
>
>rfcomm0 {
> # Automatically bind the device at startup
> bind yes;
>
>
I have had to go thru pairing process. And after, when switching on the
HS, i
Thanks for the help. I was finally able to get it working by deleting
ALL the bluez and bluetooth stuff and reinstalling. I was able to get
the devices to pair. However, the results were very poor. Apparently
ALSA doesn't play well together with bt-sco anymore.
Every time I tried to use "Headset"
> Is accessibility enabled ?
shouldn't.
In the Gnome preferences I found:
"Keyboard accessibility features"
"Assistive Technologies"
both are disabled.
Clicking through the items in gconf-editor I notices the following:
After I entered /apps/ekiga/general/user_interface/calls_history_window
ab
11 matches
Mail list logo
