User problem with automounting of camera in KDE

Matthew Carpenter matt
Tue Aug 22 05:41:25 PDT 2006


Hey Tim,

Whenever I run into something like this, it's often because the problematic 
user (yes, I realize you never call her that :) is not a member of the 
group "plugdev" (on Ubuntu systems).  

Also, when you add people to new groups, I've often heard complaints that the 
changes didn't have any effect... and then it magically starts working... 
because they made the changes while logged in as the user (su-d to root) and 
didn't log out and log in again.

$0x02
Matt

On Friday 18 August 2006 09:37, Tim Wunder wrote:
> Using FC5 and KDE 3.5.4 (from kde-redhat) in a multi-user environment (me,
> my wife, and my son).
>
> When I plug our camera into the USB port, I get a dialog asking me what to
> do with the newly found device, regardless of the number of other users
> logged in, or the order in which we log in. I can open it in a new window,
> and have access to the pictures through media:/camera.
>
> However, my wife's user code does not get this dialog. When she plugs the
> camera in, she always gets this error mesage: "Cannot find parent item
> media:/ in the tree. Internal error."
> If no one else is logged in, or if she was the first to log in, the camera
> will get mounted and Konqueror's file manager will open media:/camera and
> she'll have access to the pictures despite the error message. If she plugs
> the camera in and another user is logged into the system before her, she
> just gets the error message and cannot access the pictures in the camera.
> (media:/camera opens in konqueror to a blank page).
>
> This doesn't seem to be a console.perms problem as I have the following
> in /etc/security/console.perms.d/50-default.perms:
> <console>  0666 <camera>     0660 root.users
>
> When I plug in the camera and get the dialog, there's a checkbox to always
> do this with that kind of device (I forget the specific text as I'm not
> local to the box right now). I'm guessing that she's checked that, and
> there's something borken in the way it's handling things now.
>
> If that's the case, then something in ~/.kde is causing the problem. But
> what ? Ideas?
>
> Thanks,
> Tim

-- 
Matthew Carpenter 
matt at eisgr.com                          http://www.eisgr.com/

Enterprise Information Systems
* Network Server Appliances
* Security Consulting, Incident Handling & Forensics
* Network Consulting, Integration & Support
* Web Integration and E-Business
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://mail.linux-sxs.org/pipermail/linux-users/attachments/20060822/9175f079/attachment.pgp 



More information about the Linux-users mailing list