coriander fails with Firewire-iSight-Webcam using libdc1394. Error: Failed to initialize libdc1394 Segmentation fault

Bug #379088 reported by produnis
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libdc1394-22 (Ubuntu)
Fix Released
DC1394 Package Mainteners' team

Bug Description

Binary package hint: libdc1394-22

I want to use my 5-year old external Firewire-iSight-Webcam. I installed Ubuntu 9.04 on the 2nd HD of my MacPro-Intel.
I read, that firewire-iSights would run, if libdc1394 and coriander is installed. If I apt-get install coriander, it fetches the packages libdc1394-22 and libraw1394-8

If I try to sudo coriander, it gives me the error:

libdc1394 error: Failed to initialize libdc1394
Segmentation fault

If I dmesg |grep 1394 it gives me

produnis@UbuntuPro:/etc/modprobe.d$ dmesg |grep 1394
[ 3.099019] ohci1394 0000:10:0b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 3.149757] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[16] MMIO=[f2e04000-f2e047ff] Max Packet=[4096] IR/IT contexts=[4/8]
[ 4.567364] ieee1394: config ROM CRC error
[ 4.567411] ieee1394: Node added: ID:BUS[0-01:1023] GUID[000a27000406c399]
[ 4.567510] ieee1394: Host added: ID:BUS[0-02:1023] GUID[0019e3fffe8ebf56]
[ 8.872307] video1394: Installed video1394 module
[ 8.939386] ieee1394: raw1394: /dev/raw1394 device initialized
[ 9.483024] NOTE: The dv1394 driver is unsupported and may be removed in a future Linux release. Use raw1394 instead.
[ 1862.165728] coriander[5177]: segfault at 0 ip b794c3b7 sp bfef7ec0 error 4 in[b793f000+2c000]

So it seems as if there is something wrong with libdc1394, -22 and the coriander-handshake on Mac-Machines...

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: coriander 2.0.0-1
SourcePackage: coriander
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
produnis (schlarmann-uni-wh) wrote :
Peter Antoniac (pan1nx)
Changed in libdc1394-22 (Ubuntu):
assignee: nobody → DC1394 Package Mainteners' team (libdc1394-dev)
Revision history for this message
Viktors Petrovs (viks77) wrote :

Check for device file: /dev/raw1394
Do You have one? Do You have permissions to read/write to this device?

$ ls -la /dev/raw1394

On my Ubuntu 9.04 system this looks like:

crw-rw---- 1 root disk 171, 0 2009-10-30 11:34 /dev/raw1394

This means You must be either root or in the disk users group.

If there is no device file, You must load raw1394 module. From Your dmesg logs seems like module is loaded.

Revision history for this message
Scott Kitterman (kitterman) wrote :

This bug was fixed in the package libdc1394-22 - 2.2.0-2
Sponsored for Rohan Garg (rohangarg)

libdc1394-22 (2.2.0-2) unstable; urgency=low

  * Really move libdc1394-utils to section utils.
  * Add Multi-Arch support.
  * Don't store debug symbols of the utils.

 -- Guus Sliepen <email address hidden> Sat, 10 Mar 2012 17:06:32 +0100

libdc1394-22 (2.2.0-1) unstable; urgency=low

  * New upstream release.
    - Renames poorly named externally-visible symbol usb_init. Closes: #655332
  * Move libdc1394-utils to section utils. Closes: #663073
  * Bump Standards-Version.

 -- Guus Sliepen <email address hidden> Sat, 10 Mar 2012 16:11:05 +0100

Changed in libdc1394-22 (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.