Aiptek tablet only registers as a mouse in /dev/input

Bug #361693 reported by Shaved Wookie
78
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Wizardpen
Invalid
Undecided
Unassigned
koffice
Invalid
Undecided
Unassigned
xserver-xorg-input-aiptek (Ubuntu)
Expired
Wishlist
Unassigned

Bug Description

Binary package hint: xserver-xorg-input-aiptek

Hi there,

I installed xorg-input-aiptek and followed the guide at XXXXXXXXXXXXXXXX. The pen on my Aiptek tablet works but without clicks or pressure sensitivity. It also moves the cursor only when the pen is actually touching the tablet. On further investigation, there's no aiptektablet created in /udev/input. It seems to be registering as input6. Here's a bunch of other possibly relevant data:

===========================
ls /dev/input shows:

by-id by-path event0 event1 event2 event3 event4 event5 event6 mice mouse0 mouse1 mouse2

===========================
udevadm info -a -p /devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.0/input/input6 gives:

looking at device '/devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.0/input/input6':
    KERNEL=="input6"
    SUBSYSTEM=="input"
    DRIVER==""
    ATTR{name}=="Aiptek"
    ATTR{phys}=="usb-0000:00:12.0-2/input0"
    ATTR{uniq}==""
    ATTR{modalias}=="input:b0003v08CAp0010e0105-e0,1,2,3,4,k80,81,82,83,84,85,86,87,B7,B8,B9,BA,BB,BC,BD,BE,BF,C0,C1,C2,110,111,112,140,141,142,143,144,146,147,14A,14B,14C,r0,1,8,a0,1,8,18,1A,1B,28,m0,lsfw"

  looking at parent device '/devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.0':
    KERNELS=="3-2:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="aiptek"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{bNumEndpoints}=="01"
    ATTRS{bInterfaceClass}=="03"
    ATTRS{bInterfaceSubClass}=="00"
    ATTRS{bInterfaceProtocol}=="00"
    ATTRS{modalias}=="usb:v08CAp0010d0105dc00dsc00dp00ic03isc00ip00"
    ATTRS{supports_autosuspend}=="0"
    ATTRS{size}=="6000x4500"
    ATTRS{pointer_mode}=="either"
    ATTRS{coordinate_mode}=="absolute"
    ATTRS{tool_mode}=="pen"
    ATTRS{xtilt}=="disable"
    ATTRS{ytilt}=="disable"
    ATTRS{jitter}=="50"
    ATTRS{delay}=="400"
    ATTRS{event_count}=="1"
    ATTRS{diagnostic}=="no errors"
    ATTRS{odm_code}=="0x0200"
    ATTRS{model_code}=="0x00c9"
    ATTRS{firmware_code}=="0105"
    ATTRS{stylus_lower}=="lower"
    ATTRS{stylus_upper}=="upper"
    ATTRS{mouse_left}=="left"
    ATTRS{mouse_middle}=="middle"
    ATTRS{mouse_right}=="right"
    ATTRS{wheel}=="0"
    ATTRS{execute}=="Write anything to this file to program your tablet."

  looking at parent device '/devices/pci0000:00/0000:00:12.0/usb3/3-2':
    KERNELS=="3-2"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{configuration}==""
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bmAttributes}=="80"
    ATTRS{bMaxPower}==" 26mA"
    ATTRS{urbnum}=="27"
    ATTRS{idVendor}=="08ca"
    ATTRS{idProduct}=="0010"
    ATTRS{bcdDevice}=="0105"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPacketSize0}=="8"
    ATTRS{speed}=="1.5"
    ATTRS{busnum}=="3"
    ATTRS{devnum}=="2"
    ATTRS{version}==" 1.10"
    ATTRS{maxchild}=="0"
    ATTRS{quirks}=="0x0"
    ATTRS{authorized}=="1"
    ATTRS{manufacturer}=="AIPTEK International Inc."
    ATTRS{product}=="USB Tablet Series Version 1.05"

  looking at parent device '/devices/pci0000:00/0000:00:12.0/usb3':
    KERNELS=="usb3"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{configuration}==""
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bmAttributes}=="e0"
    ATTRS{bMaxPower}==" 0mA"
    ATTRS{urbnum}=="39"
    ATTRS{idVendor}=="1d6b"
    ATTRS{idProduct}=="0001"
    ATTRS{bcdDevice}=="0206"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{speed}=="12"
    ATTRS{busnum}=="3"
    ATTRS{devnum}=="1"
    ATTRS{version}==" 1.10"
    ATTRS{maxchild}=="3"
    ATTRS{quirks}=="0x0"
    ATTRS{authorized}=="1"
    ATTRS{manufacturer}=="Linux 2.6.28-11-generic ohci_hcd"
    ATTRS{product}=="OHCI Host Controller"
    ATTRS{serial}=="0000:00:12.0"
    ATTRS{authorized_default}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:12.0':
    KERNELS=="0000:00:12.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="ohci_hcd"
    ATTRS{vendor}=="0x1002"
    ATTRS{device}=="0x4397"
    ATTRS{subsystem_vendor}=="0x1043"
    ATTRS{subsystem_device}=="0x834e"
    ATTRS{class}=="0x0c0310"
    ATTRS{irq}=="16"
    ATTRS{local_cpus}=="ffffffff,ffffffff"
    ATTRS{local_cpulist}=="0-63"
    ATTRS{modalias}=="pci:v00001002d00004397sv00001043sd0000834Ebc0Csc03i10"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

=================================

and my /etc/udev/rules.d/61-aiptek.rules is:

DRIVERS=="aiptek",ATTRS{size}=="6000x4500",ATTRS{model_code}=="0x00c9", SYMLINK+="input/aiptektablet"

although it *still* doesn't create the symlink with just:

DRIVERS=="aiptek", SYMLINK+="input/aiptektablet"

=================================

I'm on Kubuntu Jaunty AMD64 updated daily.

Tags: kubuntu
Bryce Harrington (bryce)
tags: added: kubuntu
Revision history for this message
Waldeck Schützer (waldeck-dm) wrote :

The input symlink is no longer required after intrepid. According the information above, one can see that the correct driver was attached to your tablet, so it should work as expected. Now, have you followed the part of the guide which instructs you to write a hal .fdi file? It might help if you attach a copy of that file to this bug report.

Revision history for this message
variona (variona) wrote :

I followedthe guide to create the file 10-linuxaiptek.fdi, in the directory /usr/share/hal/fdi/policy.
Hovering above the tablet works until the first click (either tip or button) from then on it works mouse like (relative), clicks don't do anything noticeable from then on (no selecting or drawing possible). As the document states:"Some tablets (6000U, 12000U, 14000U) seems to use Wacom drivers, if you experience problems with button presses (Your mouse pointer freezes), but you can move the cursor try the updated packets for Wacom." I removed the xserver-xorg-input-aiptek package but this didn'change anything. Still the aiptek kernel module is being loaded and the results remainthe same.
I have an Aiptek 12000U tablet.

Revision history for this message
Shaved Wookie (shavedwookie) wrote :

I heard that this is a QT 4.5 issue meets (K)Ubuntu using non-standard names. I tried installing the experimental QT4.6 packages, but no change.

My tablet (also a 12000U) seems to register as input 8/mouse 2 and in dmesg I get:
input: Aiptek as /devices/pci0000:00/0000:00:12.2/usb1/1-6/1-6.3/1-6.3:1.0/input/input8

3 years I've been trying to get this to work. *sigh*

Oh, and the "updated" packages mentioned at https://help.ubuntu.com/community/Wacom are outdated as Karmic's default ones are more recent.

Revision history for this message
Shaved Wookie (shavedwookie) wrote :

By the way, wacdump seems to return x/y position, pressure and touch=down perfectly. When I click the right button or middle button wacdump registers nothing and the cursor doesn't move, but I'm not too fussed by that right now. I just want pressure and the ability to register a tap!

Is it possible to symlink where KDE / x.org are looking for it to where it's showing up?

Revision history for this message
Shaved Wookie (shavedwookie) wrote :

Oh, and to update my specs from when I first filed this bug, I'm now on:
Kubuntu Karmic AMD 64 with KDE 4.3.3

Revision history for this message
Shaved Wookie (shavedwookie) wrote :

Seems to be something to do with the Aiptek / Wacom driver packages, not Koffice.

Changed in koffice:
status: New → Invalid
Revision history for this message
Shaved Wookie (shavedwookie) wrote :

Added Wizardpen driver project as that's listed in LP as being responsible for non Wacom tablets.

Revision history for this message
gypsy_roadhog (neil-turner) wrote :

I have experienced similar problems. I have tested my Aiptek tablet against the alpha2 release of lucid lynx 10.4 and this seems to solve the problem.

Revision history for this message
Gerard Krol (gerard-) wrote :

You are using the Aiptek drivers (as you should with your tablet), marking as invalid for wizardpen.

Changed in wizardpen:
status: New → Invalid
Revision history for this message
Marin (marin-m) wrote :

I use an Aiptek-like tablet (Trust TB-2100) and this bug affects me also.

Revision history for this message
hva (francesco-hermanitosverdes) wrote :

I have had a look at how wacom tablets are supported in Lucid:
seems fdi files have to be translated to udev rules, see this:
https://wiki.kubuntu.org/X/InputConfiguration
and then we are back to a sort of xorg.conf configuration system, through local snippets added in /usr/lib/X11/xorg.conf.d

I will try to see if I can work things out.
I was thinking about adding udev rules like this:

ACTION!="add|change", GOTO="xorg_aiptek_end"
KERNEL!="event[0-9]*", GOTO="xorg_aiptek_end"

ATTRS{idVendor}=="08ca", ENV{x11_driver}="aiptek", SYMLINK+="input/aiptektablet"

LABEL="xorg_aiptek_end

and a '10-aiptek.conf' xorg.conf.d snippets more or less like this:

Section "InputClass"
 Identifier "pen"
 MatchProduct "Aiptek|AIPTEK|aiptek"
 MatchDevicePath "/dev/input/event*"
 Driver "aiptek"
 Option "SendCoreEvents" "true"
 Option "USB" "on"
 Option "Type" "stylus"
 Option "Mode" "absolute"
 Option "zMin" "0"
 Option "zMax" "511"
EndSection

Has anyone already tried this kind of approach?

Revision history for this message
hva (francesco-hermanitosverdes) wrote :

In Lucid configuring as reported on previous comment seems to work.
Only thing not resolved is with buttons:
at startup I have only pen-tip working, after reconfiguring with
xinput set-button-map Aiptek 1 3 2 4 5
I have pen-tip as button 1 and lower stylus button as right-click, but the upper stylus button doesn't work at all

Revision history for this message
Flatlander (tomi-neste) wrote :

I still have these problems with Lucid and Trust TB-3100 (which is some kind of an Aiptek I believe).

Movement works ok as long as I don't touch the tablet, after that the cursor only moves when the tip is pressed. The other two buttons on the stylus don't seem to work either.

Revision history for this message
Julian W (naboo-ws) wrote :

FlatLander, I have exactly the same problem.

I have followed hva's tutorial on the ubuntu wiki, but it doesn't seem to change anything. The tablet was partly support without it, but the same irritating bug still continues. I think it is also responsible for crashing Gimp all the time when pressure sensitivity is activated.

Since you people are talking about a driver needing to be installed, is this to be done separately from hva's fix?
Thanks!

Revision history for this message
Teteph (stephane-ravier) wrote :

I have exactly the same trouble as FlatLander but with a Trust 400-V2. I should mentioned that it was working almost perfectly (I just couldn't start X server with tablet plugged in) in Ubuntu 9.04. This is annoying to lose such functionalities after upgrade.

Revision history for this message
David Richfield (davidrichfield) wrote :

I'm having exactly the same issue with a Genius G-Pen 560 since I upgraded to Lucid. The pointer moves until I touch the tablet, but afterwards, it only moves when the tip is in contact with the tablet. I see the driver is getting events, because the number in /sys/bus/usb/drivers/aiptek/3-2\:1.0/event_count increases when I hover over the tablet, even though the pointer doesn't move.

Revision history for this message
David Richfield (davidrichfield) wrote :

This is actually a bug in the kernel driver if I understand correctly: Even without xserver-xorg-input-aiptek installed, I get exactly the same behavour!

Revision history for this message
matangdilis (matangdilis) wrote :

I have tried hva's solution documented in the community documentation here: https://help.ubuntu.com/community/AiptekTablet?highlight=%28%28AiptekTablet%29%29 for the Genius G-Pen 560. It appears that there is No need to issue xinput commands unless you want to remap the buttons. All the buttons seem to work with only the conf and rules files scripted.

I simply copied them except for setting zMax to 1024 for the gpen 560. See here to download the configuration files needed: http://matangdilis.blogspot.com/2010/09/genius-g-pen-560-for-ubuntu-lucid.html .

Please confirm if this bug is already solved, perhaps the community documentation can be updated regarding button mappings. Thanks to hva for the solution.

Revision history for this message
matangdilis (matangdilis) wrote :

Oh. I'm running lucid amd64 with kernel 2.6.32-24.42.

Revision history for this message
David Richfield (davidrichfield) wrote : Re: [Bug 361693] Re: Aiptek tablet only registers as a mouse in /dev/input
Download full text (5.8 KiB)

Brilliant! I'll test that as soon as I get home and let you know.

On Mon, Sep 13, 2010 at 7:15 AM, matangdilis <email address hidden> wrote:
> Oh. I'm running lucid amd64 with kernel 2.6.32-24.42.
>
> --
> Aiptek tablet only registers as a mouse in /dev/input
> https://bugs.launchpad.net/bugs/361693
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in koffice free integrated office suite for KDE: Invalid
> Status in Wizardpen graphics pad/tablet driver for Linux: Invalid
> Status in "xserver-xorg-input-aiptek" package in Ubuntu: New
>
> Bug description:
> Binary package hint: xserver-xorg-input-aiptek
>
> Hi there,
>
> I installed xorg-input-aiptek and followed the guide at XXXXXXXXXXXXXXXX. The pen on my Aiptek tablet works but without clicks or pressure sensitivity. It also moves the cursor only when the pen is actually touching the tablet. On further investigation, there's no aiptektablet created in /udev/input. It seems to be registering as input6. Here's a bunch of other possibly relevant data:
>
> ===========================
> ls /dev/input shows:
>
> by-id by-path event0 event1 event2 event3 event4 event5 event6 mice mouse0 mouse1 mouse2
>
> ===========================
> udevadm info -a -p /devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.0/input/input6 gives:
>
> looking at device '/devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.0/input/input6':
> KERNEL=="input6"
> SUBSYSTEM=="input"
> DRIVER==""
> ATTR{name}=="Aiptek"
> ATTR{phys}=="usb-0000:00:12.0-2/input0"
> ATTR{uniq}==""
> ATTR{modalias}=="input:b0003v08CAp0010e0105-e0,1,2,3,4,k80,81,82,83,84,85,86,87,B7,B8,B9,BA,BB,BC,BD,BE,BF,C0,C1,C2,110,111,112,140,141,142,143,144,146,147,14A,14B,14C,r0,1,8,a0,1,8,18,1A,1B,28,m0,lsfw"
>
> looking at parent device '/devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.0':
> KERNELS=="3-2:1.0"
> SUBSYSTEMS=="usb"
> DRIVERS=="aiptek"
> ATTRS{bInterfaceNumber}=="00"
> ATTRS{bAlternateSetting}==" 0"
> ATTRS{bNumEndpoints}=="01"
> ATTRS{bInterfaceClass}=="03"
> ATTRS{bInterfaceSubClass}=="00"
> ATTRS{bInterfaceProtocol}=="00"
> ATTRS{modalias}=="usb:v08CAp0010d0105dc00dsc00dp00ic03isc00ip00"
> ATTRS{supports_autosuspend}=="0"
> ATTRS{size}=="6000x4500"
> ATTRS{pointer_mode}=="either"
> ATTRS{coordinate_mode}=="absolute"
> ATTRS{tool_mode}=="pen"
> ATTRS{xtilt}=="disable"
> ATTRS{ytilt}=="disable"
> ATTRS{jitter}=="50"
> ATTRS{delay}=="400"
> ATTRS{event_count}=="1"
> ATTRS{diagnostic}=="no errors"
> ATTRS{odm_code}=="0x0200"
> ATTRS{model_code}=="0x00c9"
> ATTRS{firmware_code}=="0105"
> ATTRS{stylus_lower}=="lower"
> ATTRS{stylus_upper}=="upper"
> ATTRS{mouse_left}=="left"
> ATTRS{mouse_middle}=="middle"
> ATTRS{mouse_right}=="right"
> ATTRS{wheel}=="0"
> ATTRS{execute}=="Write anything to this file to program your tablet."
>
> looking at parent device '/devices/pci0000:00/0000:00:12.0/usb3/3-2':
> KERNELS=="3-2"
> SUBSYSTEMS=="usb"
> DRIVERS=="usb"
> ATTRS{configuration}==""
> ATTRS{bNumInterfaces}==" 1"
> ATTRS{bConfigurationValue}=="1"
> ATTRS{bmAttri...

Read more...

Revision history for this message
David Richfield (davidrichfield) wrote :

Yes, adding the udev rule works!

Revision history for this message
Luca Béla Palkovics (luca-bela-palkovics) wrote :

On Ubuntu 10.10 the folder /usr/lib/X11/xorg.conf.d/ is at /usr/share/X11/xorg.conf.d
see at https://wiki.ubuntu.com/X/Config

Revision history for this message
Luca Béla Palkovics (luca-bela-palkovics) wrote :

But wont solve the problem ..If i plug the tablet .. i can move the cursor.. (+ coordinates are absolute) the moment I do a click(-> tip touches the tablet).. I can't move the cursor anymore.. well it does move when I do a click ..

Revision history for this message
David Richfield (davidrichfield) wrote :

On Wed, Sep 29, 2010 at 3:28 PM, LucaBelaPalkovics
<email address hidden> wrote:
> But wont solve the problem ..If i plug the tablet .. i can move the
> cursor.. (+ coordinates are absolute) the moment I do a click(-> tip
> touches the tablet).. I can't move the cursor anymore.. well it does
> move when I do a click ..
>

This is exactly the problem that I had, and setting the udev rule (as
hva recommended) solved it for me. Did you try that?

--
David Richfield
e^(πi)+1=0

Revision history for this message
Luca Béla Palkovics (luca-bela-palkovics) wrote :

Yeah I added the udev rule with "gksudo gedit /lib/udev/rules.d/69-xserver-xorg-input-aiptek.rules"
I copy&past it form https://help.ubuntu.com/community/AiptekTablet and compared it with hva's version it's nearly the same.

LABEL="xorg_aiptek_end
was changed to
LABEL="xorg_aiptek_end"
which I think is correct

Revision history for this message
Luca Béla Palkovics (luca-bela-palkovics) wrote :

Is there the possibility that the X-Server needs the "next line" character after "EndSection" ?
I just added now a new line after EndSection .. and magically everything worked >.>

Revision history for this message
osz.winkelmann@brturbo.com.br (osz-winkelmann-6) wrote :

I was using my Trust Tablet 4200 in Ubuntu 10.04 and everything was fine (I didn't have the left/right button capability but it was fine with pressure and sensitivity) but when I installed the 10.10 version I lost the "hovering thing" as you described early. I still have pressure but when I take my pen from the Tablet I loose track and when I touch the Table again there's a jump from one point to another and it is marked with an annoying line...

Revision history for this message
osz.winkelmann@brturbo.com.br (osz-winkelmann-6) wrote :

Apparently, I solved part of my problem! I entered the usr/share/x11/xorg.conf.d/10-evdev.conf and changed the

Section "InputClass"
        Identifier "evdev tablet catchall"
        MatchIsTablet "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Whith the Aiptek Input:

Section "InputClass"
        Identifier "pen"
        MatchProduct "Aiptek|AIPTEK|aiptek"
        MatchDevicePath "/dev/input/event*"
        Driver "aiptek"
        Option "SendCoreEvents" "true"
        Option "USB" "on"
        Option "Type" "stylus"
        Option "Mode" "absolute"
        Option "zMin" "0"
        Option "zMax" "1024"
EndSection

Now I have the "hovering thing", the velocity sensitivity but I'm not sure about the pressure sensitivity, maybe I can work without it for a while.

Revision history for this message
hva (francesco-hermanitosverdes) wrote :

https://help.ubuntu.com/community/AiptekTablet has been updated with instructions for Maverick.
Testing is needed.

Revision history for this message
Simo Djuric (findingsimo) wrote :

I can confirm the following: Genius G-Pen 560 works if you rename "10-aiptek.conf" file to "50-aiptek.conf" (which is suggested on the community page, though it took me two hours of fiddling with it to actually notice that suggestion).

Everything works, including pressure sensitivity (tested in Gimp) and right click button. The "smaller" button which should act as left click serves as "paste", though at this moment I would be happy even if neither worked as long as the bug in question is resolved.

Revision history for this message
shalafi (rportales) wrote :

Thank you all for the info, specially the small details referring to:

- the xorg.config.d not being in the indicated location but on /usr/share/X11
- renaming the config file to 50-aiptek.conf

After that, the tablet does not have the "hovering effect" anymore and everything works fine, including pressure.

For the record, I have a Debian testing with a 2.6.32 kernel and my tablet is a Trust TB-3100

Revision history for this message
rachad (rachad63) wrote :

Hi thank you for all your comments, I test succesfully Hyperpen T-6000u Aiptek tablet, a very cheap tablet ! . Using udev configuration and putting osni's file xorg configuration, It works very fine although Xorg crashes when I plug off the tablet. Is this behaviour avoidable with a workaround ? Thanks you again guys.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

The udev rule should not be necessary. And, it's likely that the wacom driver could work. Try adding "Aiptek|AIPTEK|aiptek" to the Wacom Class in /usr/share/X11/xorg.conf.d/50-wacom.conf, and see if the device works?

Changed in xserver-xorg-input-aiptek (Ubuntu):
importance: Undecided → Wishlist
status: New → Incomplete
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

sorry, realized it would need changes to the wacom driver, so ignore the previous comment.

Revision history for this message
David Tombs (dgtombs) wrote :

Timo, you still want this bug incomplete then?

Revision history for this message
Gerard Krol (gerard-) wrote : Out of office: [Bug 361693] Re: Aiptek tablet only registers as a mouse in /dev/input

I'll try to read this mail August 2nd.

Ik ga proberen dit mailtje 2 augustus te lezen.

Regards/Groeten,

Gerard Krol
Zermelo Roostermakers

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-input-aiptek (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-input-aiptek (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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