Hello,
I have compiled Ekiga (latest version) on Zenwalk Snapshot. Compilation went
on properly without any error message. But when I start the program, nothing
happens. What should I do?
Thanks for your help,
Anand
___
ekiga-list mailing list
Ananda Murthy R S wrote:
Hello,
I have compiled Ekiga (latest version) on Zenwalk Snapshot. Compilation went
on properly without any error message. But when I start the program, nothing
happens. What should I do?
Is the process running or does it finish immediately?
Start ekiga with -d 4 and
Hello Eugen,
Thanks for your immediate reply. This is the output I got after giving the
command ekiga -d 4:
ekiga_start.log
dyna.cxx(111)H264DYNASuccessfully loaded
'libavcodec.so.52'
dyna.cxx(337)H264DYNASuccessfully loaded libavcodec
library and verified
This is really interesting.
First, move /usr/lib/opal-3.6.2/codecs/video/h264_video_pwplugin_helper
to another directory, so that it would b=not be found, and restart ekiga
-d 4.
Second, remove the file where it was and start ekiga through gdb, as
shown at
After moving h264_video_pwplugin_helper I got this:
ekiga -d 4 | tee ekiga_start.log
dyna.cxx(111)H264DYNASuccessfully loaded
'libavcodec.so.52'
dyna.cxx(337)H264DYNASuccessfully loaded libavcodec
library and verified functions
h264pipe_unix.cxx(297)
Le lundi 12 février 2007 à 00:17 +0100, Tobias Eberle a écrit :
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:
Le lundi 12 février 2007 à 14:14 +0100, Tobias Eberle a écrit :
Hello,
Try gdb ekiga
type 'run'
then when it freezes, hit Ctrl-C and type thread apply all bt
I have already done that. See my answer to the post from Jan yesterday.
Did you kill it with Ctrl-C or with killall -9 ekiga
Hello,
Did you kill it with Ctrl-C or with killall -9 ekiga ?
Because the backtrace does not contain anything useful.
Ctrl-C
You could also use strace and examine ekiga -d 4.
I have solved it! In the strace output I found that it tried to access
an sftp resource through gnome-vfs using
Hi !
Le lundi 12 février 2007 à 20:20 +0100, Tobias Eberle a écrit :
Hello,
Did you kill it with Ctrl-C or with killall -9 ekiga ?
Because the backtrace does not contain anything useful.
Ctrl-C
You could also use strace and examine ekiga -d 4.
I have solved it! In the strace
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
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
output
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
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 using
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 mailing
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
remember it)
If
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 the fall
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
17 matches
Mail list logo