From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830 Description of problem: When configuring a palm pilot through the serial port, if the gpilotd-control-applet is run from an icon, or launched from evolution, there is nothing to let a user know that the program cannot read-write to the device /dev/ttyS0 or /dev/ttyS1 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. After an install the permissions on /dev/ttyS0 are crw-rw---- 2. launch gpilotd-control-applet from an icon 3. No notice from the GUI lets a user know that the program cannot access device /dev/ttyS0 4. A user is unable to configure the device until they change permissions Actual Results: No notice from the GUI lets a user know that the program cannot access device /dev/ttyS0 Expected Results: A pop-up or error box letting the user know that /dev/ttyS0 exists, but the permisssions prevent configuring the device. Additional info: chmod o+rw /dev/ttyS0
The error on the command line for incorect permissions is this: gpilotd-WARNING **: Could not open device Cradle (/dev/ttyS0): reason: "Permission denied".
You problem is that you need to add entries for /dev/ttyS[01] to /etc/security/console.perms, that will give you Access to the serial port that you need. But as an addition to this bug, my install did not create a /dev/pilot, which is in console.perms. No big deal, I created it to point to ttyS0 but the problem I had is that I didn't have permission on /dev/pilot untill I logged out and logged in again, It's confusing and I'm sure it will confuse a lot of others.
This will need to be fixed upstream rather than as a Red Hat specific change. Please file a bug requesting this in bugzilla.gnome.org
katzj, This isn't something that needs to be added to the dev rpm?
Opened on gnome bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=96281