trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: November 2015

Re: [trinity-users] Re: TDE not reacting on camera [SOLVED]

From: "Dr. Nikolaus Klepp" <office@...>
Date: Mon, 2 Nov 2015 14:49:19 +0100
 Hi deloptes!

Am Mittwoch, 30. September 2015 schrieb deloptes:
> Dr. Nikolaus Klepp wrote:
> 
> > Hi all!
> > 
> > I have a funny problem with a camera: "Casio Exilim", is recognised as a
> > usb storage device, and under TDE <= 14.0.0 the camera was managed by TDEs
> > device manager, i.e. a popup appered "New media found. What do you want to
> > do?", just like any USB stick.
> > 
> > After the update to 14.0.1 things have changed: usb-sticks are still
> > managed as expected, just the camera is not. I can mount it manually (but
> > that's not quite what the user expected).
> > 
> > So, where should I go looking? It's debian jessie, btw.
> 
> sounds similar to my problem with the cell phone
> 
> https://bugs.trinitydesktop.org/show_bug.cgi?id=2444
> 
> solution based on bug
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650299
> 
> not sure if you are using the polkit though, but the answer should be
> somehwere around org.freedesktop.udisks or the packages I suppose.
> 
> hope this helps a bit
> 
> regards

Well, I just solved the problem - kind of. Looks like the "improvement" introduced by systemd folks in the form of a binary hardware dababase is the root of all evil. As it was to be expected, the database contains wrong information (haven't they learned a single bit from M$?). I had to "persuade" udev, that the camera is a "disk" and not something "generic", and udisk/usdisk2 that it's "removable". And it's important that these fixes are in the last ruleset, otherwise it does not work:

# /etc/udev/rules/99-casio.rules
ENV{ID_SERIAL}=="CASIO_COMPUTER_CASIO_QV_DIGITAL",ENV{ID_TYPE}="disk",ENV{UDISKS_AUTO}="1",ENV{UDISKS_SYSTEM}="0",ENV{UDISKS_SYSTEM_INTERNAL}="0"

Nik

-- 
Please do not email me anything that you are not comfortable also sharing with the NSA.