There were lots for pwlib, many in the configure script, so I tried to narrow it down by searching for /dev/raw1394 and got the following:
$ grep -R -i /dev/raw1394 pwlib-1.10.3/ ekiga-2.0.3/
pwlib-1.10.3/plugins/vidinput_dc/video4dc1394.cxx: * usual Video4Linux devices, specify "/dev/raw1394" or "/dev/video1394"
pwlib-1.10.3/plugins/vidinput_dc/video4dc1394.cxx: * --videoinput /dev/raw1394" should use your 1394 camera as video input.
pwlib-1.10.3/plugins/vidinput_dc/video4dc1394.cxx: if (devName == "/dev/raw1394")
pwlib-1.10.3/plugins/vidinput_dc/video4dc1394.cxx: PTRACE(0, "devName must be /dev/raw1394 or /dev/video1394");
pwlib-1.10.3/plugins/vidinput_dc/video4dc1394.cxx: if (PFile::Exists("/dev/raw1394"))
pwlib-1.10.3/plugins/vidinput_dc/video4dc1394.cxx: list.AppendString("/dev/raw1394");
From all this I'm *guessing* it's pwlib that's the culprit. A bit of extra info I didn't include before is that I have to select the 1394AVC driver in Ekiga, with the modified permissions on /dev/raw1394, for my camera to be detected.
Jérôme Guelfucci said 8 hours ago:
>
> So this is an Ekiga problem (as it works out of the box with kino) or a pwlib problem?
I just did the following:
$ apt-get source pwlib ekiga
$ grep -R -i 1394 pwlib-1.10.3/ ekiga-2.0.3/
The only lines in the output that showed up for Ekiga were:
ekiga-2. 0.3/po/ am.po:# : src/endpoint. cpp:1394 0.3/po/ bn.po:# : src/pref_ window. cpp:1394 src/pref_ window. cpp:1748 0.3/po/ el.po:# : ../src/ gui/main. cpp:1394 0.3/po/ is.po:# : src/ldap_ window. cpp:1279 src/ldap_ window. cpp:1394 0.3/debian/ changelog: Closes: #136701, #139450
ekiga-2.
ekiga-2.
ekiga-2.
ekiga-2.
There were lots for pwlib, many in the configure script, so I tried to narrow it down by searching for /dev/raw1394 and got the following:
$ grep -R -i /dev/raw1394 pwlib-1.10.3/ ekiga-2.0.3/ 10.3/plugins/ vidinput_ dc/video4dc1394 .cxx: * usual Video4Linux devices, specify "/dev/raw1394" or "/dev/video1394" 10.3/plugins/ vidinput_ dc/video4dc1394 .cxx: * --videoinput /dev/raw1394" should use your 1394 camera as video input. 10.3/plugins/ vidinput_ dc/video4dc1394 .cxx: if (devName == "/dev/raw1394") 10.3/plugins/ vidinput_ dc/video4dc1394 .cxx: PTRACE(0, "devName must be /dev/raw1394 or /dev/video1394"); 10.3/plugins/ vidinput_ dc/video4dc1394 .cxx: if (PFile: :Exists( "/dev/raw1394" )) 10.3/plugins/ vidinput_ dc/video4dc1394 .cxx: list.AppendStri ng("/dev/ raw1394" );
pwlib-1.
pwlib-1.
pwlib-1.
pwlib-1.
pwlib-1.
pwlib-1.
From all this I'm *guessing* it's pwlib that's the culprit. A bit of extra info I didn't include before is that I have to select the 1394AVC driver in Ekiga, with the modified permissions on /dev/raw1394, for my camera to be detected.