irda-utils conflict with Wacom drivers

Bug #1119763 reported by pakopako
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
irda-utils (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Apologies if I'm not following customary guidelines, but I was in the process of looking for the Upstream Tracker for Irda-Utils trying to cite a bug in the package. Unable to find said Tracker, I am uploading this bug to LaunchPad.

To use the IrCP-Tray for OBEX beaming and receiving files with a cell-phone, I must edit "/etc/default/irda-utils" and set AUTOMATIC="true" (and reboot). I cannot use "sudo irattach." Upon doing so and rebooting, my PC will have a functioning IrCP-Tray (on /dev/ttyS1), but the Wacom device will no longer function.

Using "setserial -g /dev/ttyS[0123456789], ttyS4 (the usual port for the Wacom) will be listed as "invalid." Upon restoring /etc/default/irda-utils, Wacom service is also restored. I can edit other values in that file with impunity (such as modifying "DEVICE=" or "MAX_BAUD_RATE=") as long as AUTOMATIC="false" (or is commented out) and it will not affect the Wacom functionality (but the Infrared functionality will remain inactive.)

The hardware is a notebook tabletPC, model Toshiba M200 with nVidia NV34M [GeForce FX Go5200 32M/64M] chipset (via lshw -c display). The OS is Ubuntu 11.04. The Wacom takes up ttyS4, UART: 16550A, Port: 0x0338, IRQ: 4.

My irda-utils file is listed as such:
ENABLE="true"
AUTOMATIC="false"
DISCOVERY="true"
DEVICE="/dev/ttyS1"
DONGLE="none"
SETSERIAL=""
USE_SMCINIT="no"
MAX_BAUD_RATE="115200"

There is a detailed experience at: http://ubuntuforums.org/showthread.php?t=2113246

Revision history for this message
pakopako (pakopako) wrote :

Unsure if this should be tagged as affecting other Packages other than Irda-Utils.

description: updated
affects: nvidia-kernel-common (Ubuntu) → irda-utils (Ubuntu)
Changed in irda-utils (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.