Please mark stable media-libs/libgphoto2-2.2.1-r1 on your arch. It solves several problems: Most important: It now generates udev-rules that work with udev-103 to let the permissions be correct out of the box.
Super gelaufen, sparc stable.
Matthias: I don't understand why you CCd me to this bug, can you explain?
blubb: You seem interested in changing libgphoto-ebuilds, at least according to your comment on Bug #139884.
That's correct, but only as far as the USE_EXPAND thing goes, which won't affect the stablization of 2.2.1-r1, so I'm removing myself again. Thanks anyway for thinking of me :)
on x86: media-libs/libgphoto2-2.2.1-r1 USE="exif hal nls usb -doc" seems to be basically ok with media-gfx/gtkam-0.1.12-r2 USE="exif gnome nls -debug" for me with an "Kodak CX6230". however, can anyone explain to me what kind of sorcery needs to be done to access the camera as non root user (i'm in the plugdev group) ?
the problem is that libgphoto is trying to access the camera from it's /dev link instead of /proc entry, AFAIR the devices created in /dev/usb are owned by root so I had to manually modify a rule in udev for these to be owned by plugdev group and tada, it works :)
(In reply to comment #6) > the problem is that libgphoto is trying to access the camera from it's /dev > link instead of /proc entry, AFAIR the devices created in /dev/usb are owned by > root so I had to manually modify a rule in udev for these to be owned by > plugdev group and tada, it works :) > The required udev-rules have been added around half a month ago, if you used that ebuild before, you need to reemerge it.
in reply to comment #0, comment #5 and comment #7: hmm, this doesn't seem to apply to me then: " Most important: It now generates udev-rules that work with udev-103 to let the permissions be correct out of the box. " i've merged libgphoto2-2.2.1-r1 about 10h ago, i'm using udev-103 and i ran etc-update. to be absolutely sure, i've restarted my box. the user i want to have access to the camera is in the plugdev group. however, without any further modifications (i haven't done anything in this direction yet) i can only access the camera as root. maybe this is something specific to my configuration, or the camera (see comment #5) i'm using.
media-libs/libgphoto2-2.2.1-r1 USE="doc exif hal nls usb" 1. emerges on x86 2. passes collision test 3. kde-base/kamera-3.5.5 emerges with it don't have hardware to test atm Portage 2.1.1-r2 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.4-r4, 2.6.18.4 i686) ================================================================= System uname: 2.6.18.4 i686 Genuine Intel(R) CPU T2300 @ 1.66GHz Gentoo Base System version 1.12.6 Last Sync: Wed, 20 Dec 2006 18:30:01 +0000 ccache version 2.3 [disabled] app-admin/eselect-compiler: [Not Present] dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.3.5-r3, 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.3 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=prescott -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2 -march=prescott -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--nospinner" FEATURES="autoconfig collision-protect distlocks metadata-transfer parallel-fetch sandbox sfperms strict test userfetch userpriv usersandbox" GENTOO_MIRRORS="http://mirror.switch.ch/mirror/gentoo/ http://gentoo.inode.at/" LINGUAS="en de en_GB de_CH" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X a52 aac acpi alsa apache2 asf berkdb bitmap-fonts cairo cdr cdrom cli cracklib crypt cups dbus divx dlloader dri dts dvd dvdr dvdread eds elibc_glibc emboss encode fam ffmpeg firefox flac fortran gdbm gif gnome gpm gstreamer gtk hal iconv input_devices_keyboard input_devices_mouse ipv6 isdnlog java jpeg kde kdeenablefinal kernel_linux ldap libg++ linguas_de linguas_de_CH linguas_en linguas_en_GB mad mikmod mmx mono mp3 mpeg ncurses nls nptl nptlonly ogg opengl oss pam pcre perl png ppds pppd python qt3 qt4 quicktime readline reflection rtsp ruby samba sdl session smp spell spl sse sse2 sse3 ssl svg tcpd test tetex theora threads truetype truetype-fonts type1-fonts udev unicode userland_GNU vcd video_cards_fbdev video_cards_i810 video_cards_vesa vorbis win32codecs wxwindows x264 xine xml xorg xprint xv xvid zlib" Unset: CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
in reply to comment #5 and comment #8: thanks to zzam, it turned out that the issues i had with accessing my camera with media-gfx/gtkam-0.12-r1 as non root user are an issue of it's own, as i'm able to do so using media-gfx/gphoto2-2.2.0 (see bug 158684). as this gtkam related issue is not solved by downgrading libgphoto2 making libgphoto2-2.2.1-r1 stable on x86 seems to be ok for me; just don't forget to stable media-gfx/gphoto2-2.2.0 at the same time; otherwise users will face build errors.
ppc64 stable
Hooray, bugzilla works now. x86 done yesterday.
ppc stable
Stable on Alpha.
amd64 done.
(In reply to comment #15) > amd64 done. > What version of udev are you using?
ia64 stable