The latest camsource seems to have begun acting strangely - Can't pinpoint when it started, but here's what's happening; When starting camsource, it seems to randomly and quietly crash. Reproducible: Always Steps to Reproduce: 1. Start camsource, it starts up, everything is ok, it says closing stdout and going into background 2. pidof camsource may or may not report anything, in fact most times it doesn't 3. repeat the above until alas a pid is reported Actual Results: Camsource is not started until you have repeated the above X amount of times Expected Results: camsource actually stays alive In the mean time until this is fixed, I've made a little script to start camsource, wait a second, and then check for a pid - and if there isn't one loop until there is. Portage 2.0.51-r2 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20041006-r0, 2.6.9-rc4-love1 i686) ================================================================= System uname: 2.6.9-rc4-love1 i686 Intel(R) Pentium(R) 4 CPU 3.20GHz Gentoo Base System version 1.5.3 distcc 2.18 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -ftracer -fprefetch-loop-arrays -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -ftracer -fprefetch-loop-arrays -pipe -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks sandbox" GENTOO_MIRRORS="http://lug.mtu.edu/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d acpi aim alsa apache2 arts audiofile avi berkdb bitmap-fonts cdparanoia cdr crypt cups dba dvd dvdr encode f77 faad flac flash foomaticdb freetype ftp gb gd gdbm gif gimp gimp-print glx gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml hal icq imagemagick imlib jabber jack java joystick jpeg kde ladcca ldap libg++ libwww lzw-tiff mad mbox mhash mikmod mmx motif mozilla mpeg msn mysql ncurses nls nptl nptlonly nvidia offensive oggvorbis opengl pam pcmcia pdflib perl php png python qt quicktime readline samba scanner sdl slang snmp socks5 spell sse ssl svga tcltk tcpd tga tiff truetype truetype-fonts trusted type1-fonts usb userlocales v4l v4l2 wavelan wmf wxwindows x86 xft xine xml xml2 xmms xprint xrandr xscreensaver xv yahoo zlib"
does this also happen with more stable kernel sources?
Seems to be a OHCI problem - my old 350mhz with a UHCI usb controller works fine, strangely enough. So this may be more related to qc-usb (the camera driver) than camsource.
It is also happening to me. After some times I try, there is only one camsource process (it used to be 4) and it is a defunct one. I've just update my kernel an headers and I tried to recompile camsource without success. Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.12-gentoo-r4 i686) ================================================================= System uname: 2.6.12-gentoo-r4 i686 AMD Athlon(tm) XP 2600+ Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Jun 11 2005, 15:11:46)] distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig candy ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://www.las.ic.unicamp.br/pub/gentoo/ ftp://ftp.las.ic.unicamp.br/pub/gentoo/" LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.samerica.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext 7zip X apache2 avi berkdb bitmap-fonts bluetooth bonobo bzip2 bzlib cddb cdr crypt cups curl divx4linux dvd dvdr emboss esd fam firefox flac foomaticdb fortran gd gdbm gif gphoto2 gpm gtk gtk2 gtkhtml guile imagemagick imlib innodb jack java javascript jpeg jpeg2k junit kdeenablefinal ldap libg++ libwww lirc logrotate mad mmx mmx2 mmxext mng motif mp3 mpeg msn mysql ncurses nls nptl nptlonly nvidia offensive ogg oggvorbis opengl oscar pam pdflib perl php png python quicktime readline rtc ruby samba sasl sdl slang sqlite sse ssl tcltk tcpd threads tiff truetype truetype-fonts type1-fonts unicode v4l v4l2 vhosts vorbis xine xinerama xml xml2 xmms xosd xv xvid yv12 zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
I haven't tested this yet again on my OHCI usb controller, but I can only assume it's still broken. It might also be the qc-usb driver - seems that it (the driver) dies every time something closes the device, and it won't start working until the second time something tries to access it. Probably the fault of the qc-usb driver in that case. It all seems very sketchy to me but it works for what I need it to at the moment.
I tried a testcase with camsource where a video source would randomly fail - it does show that camsource goes away in these cases - but I wouldn't blame that on camsource - there's lots of stuff that fails when a device goes away that is currently in use. Granted, camsource could benefit from a patch to treat badly behaved device differently, but that's for upstream.
