Re: Digital camera problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2006-04-07 at 07:48 -0500, Gerry Tool wrote:
> Aad Rijnberg wrote:
> > Hello,
> > 
> > since a week I have installed FC5; everything works OK, but today I was trying 
> > to upload some pictures on my digital camera via USB to the PC and the 
> > connection could not be established. I suspect SELinux.
> > 
> > I use Digikam for photo management, and did auto detection of the camera  
> > which succeeded to make the proper selection (Canon PowerShot 510 (normal 
> > mode) ). This means that it can connect to the camera somehow. When I then 
> > selected the camera (via Camera->Canon PowerShot 510 (normal mode)) to get a 
> > window with thumbnails it came up with a message :
> > "Failed to connect to camera. Please make sure its connected properly and 
> > turned on. Would you like to try again?"
> > 
> > I looked in /var/log/messages, and came across the following line:
> > Apr  7 13:25:47 localhost kernel: audit(1144409147.815:368): avc:  denied  
> > { search } for  pid=2897 comm="cat" name="console" dev=dm-4 ino=393220 
> > scontext=system_u:system_r:hald_t:s0 
> > tcontext=system_u:object_r:pam_var_console_t:s0 tclass=dir
> > 
> > Any suggestions?
> > 
> > Aad
> > 
> Have you tried to use System > Administration > Security Level and 
> Firewall to set SELinux permissive?
> 

It does not look to me like the selinux error listed above has anything
to do with your camera.  More like something was trying to run cat on
the console.  But that could be a wrong.

I recently tried to connect a digital camera to an FC4 system.  Both
gthumb and digikam had problems seeing the camera.  The funny part is
that I was able to access the pictures since the system mounted the
camera as a USB drive.  I was able to copy the files directly from the
camera to a directory on the system.  

Had the following in my /var/log/messages:

Apr  7 09:21:57 lathe kernel: usb 1-2.7: new full speed USB device using
ehci_hcd and address 25
Apr  7 09:21:57 lathe kernel: scsi7 : SCSI emulation for USB Mass
Storage devices
Apr  7 09:22:02 lathe kernel:   Vendor: NIKON     Model: NIKON DSC E2100
Rev: 1.00
Apr  7 09:22:02 lathe kernel:   Type:   Direct-Access
ANSI SCSI revision: 02
Apr  7 09:22:02 lathe kernel: SCSI device sda: 250368 512-byte hdwr
sectors (128 MB)
Apr  7 09:22:02 lathe kernel: sda: Write Protect is off
Apr  7 09:22:02 lathe kernel: sda: assuming drive cache: write through
Apr  7 09:22:02 lathe kernel: SCSI device sda: 250368 512-byte hdwr
sectors (128 MB)
Apr  7 09:22:02 lathe kernel: sda: Write Protect is off
Apr  7 09:22:02 lathe kernel: sda: assuming drive cache: write through
Apr  7 09:22:02 lathe kernel:  sda: sda1
Apr  7 09:22:02 lathe kernel: sd 7:0:0:0: Attached scsi removable disk
sda
Apr  7 09:22:02 lathe scsi.agent[8620]: disk
at /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2.7/1-2.7:1.0/host7/target7:0:0/7:0:0:0
Apr  7 09:22:03 lathe fstab-sync[8663]: added mount point /media/usbdisk
for /dev/sda1
Apr  7 09:22:03 lathe kernel: SELinux: initialized (dev sda1, type
vfat), uses genfs_contexts
Apr  7 09:24:15 lathe kernel: usb 1-2.7: USB disconnect, address 25
Apr  7 09:24:15 lathe fstab-sync[8859]: removed mount
point /media/usbdisk for /dev/sda1


The last couple of lines are when I unmounted and disconnected the
camera.  I suspect that gthumb and digikam are looking for the camera to
be mounted in a specific location.  In this case it gets mounted
in /media/usbdisk.  I have also noted that if you don't unmount the
camera the next time it will create a second mount point /media/usbdisk1
and so on.  





[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux