| [CBLX] qu'es-ce qu'un Arduino board? Fwd:Bug #84139 in brltty (Ubuntu): "Arduino detected as braille device" |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/carrefourblinux Archives
]
Samj
concernant l'autodetection braille qui a été désactivée sous l'installeur
Ubuntu, j'ai été voir ici:
Bug #84139 in brltty (Ubuntu): "Arduino detected as braille device"
URL: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139
mais je ne vois pas de quoi il s'agit, 1re fois que je lis ce nom.
#[1]Bug 84139 Feed
[2]Log in / Register
Search launchpad: [3]____________________
[4]Launchpad > [5]Ubuntu > [6]"brltty" package
[7]Overview / Code / [8]Bugs / Blueprints / Translations / [9]Answers
Bug #84139 reported by [10] BHowell on 2007-02-09 ([11]Activity log)
[12](undecided) Bug #84139:
[13]This report is public
Arduino detected as braille device
[14][bug-dupe-icon] Mark as duplicate (This bug has 3 duplicates)
[15]Convert to a question
Affects Status Importance Assigned to Milestone
[16][edit] [17]brltty (Ubuntu) [18][edit] Fix Released [19][edit]
Undecided [20][edit] [21]Luke Yelavich
You are not the bug assignee nor the maintainer of brltty (Ubuntu),
and therefore cannot edit this bug's status.
Affecting: [22]brltty (Ubuntu)
Filed here by: [23] BHowell
When: 2007-02-09
Confirmed: 2007-03-05
Assigned: 2007-12-15
Started work: 2007-12-15
Completed: 2007-12-17
Package
[24]____________________ ([25]Choose...)
IFRAME: [26]popup_iframe_ubuntu_brltty.sourcepackagename
Status Importance
[27][(1)__Fix Released]
Undecided
Assigned to
[28](_) Nobody
[29](_) Me
[30](_) Luke Yelavich (themuso)
[31](_)
[32]____________________ ([33]Choose...)
IFRAME: [34]popup_iframe_ubuntu_brltty.assignee
Comment on this change (optional)
[35]______________________________________________________________
[36]______________________________________________________________
[37]______________________________________________________________
[38]______________________________________________________________
[39][_] E-mail me about changes to this bug report
[40]Also affects project [41]Also affects distribution [42]Nominate
for release
Binary package hint: brltty
I think this may be a bug in HAL but this is the symptom:
If I plug in my Arduino USB micro-controller board, brltty daemon
starts up and something keeps grabbing the device. My arduino
application cannot get access to the USB serial device.
If you are curious the arduino board is documented here: [43]http://
www.arduino.
cc
In any case, it's using an off the shelf FTDI usb serial controller.
The ftdi_sio module is loaded.
Here's the output of lsusb:
Bus 003 Device 006: ID 047b:0001 Silitek Corp.
Bus 003 Device 005: ID 09da:0006 A4 Tech Co., Ltd Optical Mouse WOP-35
/ Trust 450L Optical Mouse
Bus 003 Device 004: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
Bus 003 Device 002: ID 05e3:0606 Genesys Logic, Inc.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 005: ID 0403:6001 Future Technology Devices
International, Ltd 8-bit FIFO
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
[44]Update description / tags
[45]Link a related branch
[46]Link to CVE
[47] Samuel thibault wrote on 2007-02-09: [48]Re: [Bug 84139] Arduino
detected as braille device (permalink)
BHowell, le Fri 09 Feb 2007 04:20:35 -0000, a écrit :
> If I plug in my Arduino USB micro-controller board, brltty daemon
starts
> up and something keeps grabbing the device.
> Bus 003 Device 006: ID 047b:0001 Silitek Corp.
> Bus 003 Device 005: ID 09da:0006 A4 Tech Co., Ltd Optical Mouse
WOP-35 / Trust 450L Optical Mouse
> Bus 003 Device 004: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
> Bus 003 Device 002: ID 05e3:0606 Genesys Logic, Inc.
> Bus 003 Device 001: ID 0000:0000
> Bus 002 Device 005: ID 0403:6001 Future Technology Devices
International, Ltd 8-bit FIFO
> Bus 002 Device 001: ID 0000:0000
> Bus 001 Device 001: ID 0000:0000
That's odd: none of these device IDs should be matched by brltty, or
else there's a typo in Ubuntu's udev rules.
Samuel
[49] Colin Watson wrote on 2007-02-09: [50](permalink)
# HandyTech
SYSFS{idVendor}
=="0921", SYSFS{idProduct}=="1200", RUN+="/lib/brltty/brltty..sh -b ht
-d usb:"
SYSFS{idVendor}=="0403", SYSFS{idProduct}=="6001", RUN+="/lib/brltty/
brltty.sh -b ht -d usb:"
These come from Debian.
"8-bit FIFO". What's one of those? Sounds like maybe a generic bit of
electronics that sometimes happens to have a Braille terminal
attached?
[51] Henrik Nilsen Omma wrote on 2007-02-09: [52](permalink)
As noted in [53]bug 83939, when updating udev I got this error:
cp: cannot stat '/etc/udev/
rules.d/85-brltty.rules'
Which looks like a udev rules file getting lost.
[54] Samuel thibault wrote on 2007-02-09: [55]Re: [Bug 84139] Re:
Arduino detected as braille device (permalink)
Hi,
Colin Watson, le Fri 09 Feb 2007 09:18:12 -0000, a écrit :
> # HandyTech
> SYSFS{idVendor}=="0921"
, SYSFS{idProduct}=="1200", RUN+="/lib/brltty/brltty.sh -b ht -d usb:"
> SYSFS{idVendor}=="0403", SYSFS{idProduct}=="6001", RUN+="/
lib/brltty/brltty.sh -b ht -d usb:"
>
> These come from Debian.
Ah oops, indeed, I overlooked that. It's in the brltty repository too,
so I'm Ccing the mailing list: a Ubuntu user just wanted to plug a
special USB adapter (not related to braille at all), and brltty got
started, because the ID of his adapter is
Bus 002 Device 005: ID 0403:6001 Future Technology Devices
International, Ltd 8-bit FIFO
> "8-bit FIFO". What's one of those? Sounds like maybe a generic bit
of
> electronics that sometimes happens to have a Braille terminal
attached?
Possibly. Does anybody on the brltty list have more information on
this?
Please keep <email address hidden> in Cc, so that mails are recorded
in the bug tracker.
Samuel
[56] Mario Lang wrote on 2007-02-09: [57]Re: [BRLTTY] Re: [Bug 84139]
Re: Arduino detected as braille device (permalink)
Samuel Thibault <email address hidden> writes:
> Hi,
>
> Colin Watson, le Fri 09 Feb 2007 09:18:12 -0000, a écrit :
>> # HandyTech
>> SYSFS{idVendor}=="0921"
, SYSFS{idProduct}=="1200", RUN+="/lib/brltty/brltty.sh -b ht -d usb:"
>> SYSFS{idVendor}=="0403", SYSFS{idProduct}=="6001", RUN+="/
lib/brltty/brltty.sh -b ht -d usb:"
>>
>> These come from Debian.
>
> Ah oops, indeed, I overlooked that. It's in the brltty repository
too,
> so I'm Ccing the mailing list: a Ubuntu user just wanted to plug a
> special USB adapter (not related to braille at all), and brltty got
> started, because the ID of his adapter is
>
> Bus 002 Device 005: ID 0403:6001 Future Technology Devices
International, Ltd 8-bit FIFO
>
>> "8-bit FIFO". What's one of those? Sounds like maybe a generic bit
of
>> electronics that sometimes happens to have a Braille terminal
attached?
>
> Possibly. Does anybody on the brltty list have more information on
this?
The FTDI chip is used in Handy Tech Braille displays to implement
the USB connectivity. What they basically did is put this chip
on top of their already existing serial interface, therefore avoided
having to implement their own USB stack/protocol, they simply
reuse an existing USB->Serial adaptor chip, and drivers talk with the
display with the exact same byte-protocol either via serial, USB or
bluetooth.
FYI, here is how my Handy Tech Modular Evolution 88 identifies:
Bus 001 Device 041: ID 0403:6001 Future Technology Devices
International, Ltd 8-bit FIFO
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0403 Future Technology Devices International, Ltd
idProduct 0x6001 8-bit FIFO
bcdDevice 4.00
iManufacturer 1 FTDI
iProduct 2 USB <-> Serial
iSerial 0
bNumConfigura
tions 1
...
(the rest is standard USB->Serial adaptor config description...)
P.S.: I own (and use) devices of both types mentioned in this bug, the
PID 6001 and the PID 1200 (which is very rare indeed). Feel free
to contact me with more questions.
--
CYa,
Mario | Debian Developer <URL:[58]http://debian.
org/>
.''`. | Get my public key via finger <email address hidden>
: :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
`. `'
`- <URL:[59]http://delysid.org/> <URL:[60]http://www.staff.tugraz.
at/mlang/>
[61] Samuel thibault wrote on 2007-02-09: [62](permalink)
Mario Lang, le Fri 09 Feb 2007 14:34:18 -0000, a écrit :
> FYI, here is how my Handy Tech Modular Evolution 88 identifies:
>
> Bus 001 Device 041: ID 0403:6001 Future Technology Devices
International, Ltd 8-bit FIFO
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 1.10
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 8
> idVendor 0x0403 Future Technology Devices International, Ltd
> idProduct 0x6001 8-bit FIFO
> bcdDevice 4.00
> iManufacturer 1 FTDI
> iProduct 2 USB <-> Serial
> iSerial 0
> bNumConfigurations 1
Gasp, this is not specific to the braille device at all :(
I guess the only safe solution is to comment the line in the udev
script, and require users to either uncomment it by hand or load
brltty
explicitly.
Samuel
[63] Mario Lang wrote on 2007-02-09: [64](permalink)
Dave Mielke <email address hidden> writes:
>>Ah oops, indeed, I overlooked that. It's in the brltty repository
too,
>>so I'm Ccing the mailing list: a Ubuntu user just wanted to plug a
>>special USB adapter (not related to braille at all), and brltty got
>>started, because the ID of his adapter is
>
> The problem would be that brltty needs to do a bit more checking in
order to
> more accurately detect that type of braille display. Right now it's
just
> checking the vendour and product ids. It should probably also be
checking other
> things like the product and/or manufacturer names.
Unfortunately, the vendor/product strings were not specially
set for Handy Tech. They look like a standard serial
adaptor. My ME88 says "FTDI" as Vendor string and
"USB->Serial" as product string. That is not going to
help.
> We'll have to check one of those displays to see what it takes to
> uniquely identify it.
I am afraid we can't, without opening the device and looking at the
reset answer.
--
CYa,
Mario | Debian Developer <URL:[65]http://debian.org/
>
.''`. | Get my public key via finger <email address hidden>
: :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
`. `'
`- <URL:[66]http://delysid.org/> <URL:[67]http://www.staff.tugraz.
at/mlang/>
[68] Stu Hood wrote on 2007-03-05: [69](permalink)
Well, it seems the discussion confirms this bug anyway, but since I
just experienced it as well, I'll add my vote. brltty grabs the
connection and removes the raw serial device, and so obviously
removing brltty fixed it.
[70] Samuel thibault wrote on 2007-03-20: [71](permalink)
Do definitive correction (i.e. making both sighted and non-sighted
users completely happy) could be found. For now, I'd suggest dropping
brltty-ht 0x0003 0x0403 0x6001 from the hotplug/udev scripts for now
(since it seems to hit a number of users)
[72] Samuel thibault wrote on 2007-03-20: [73](permalink)
Err, I meant "No definitive correction"
[74] jonatan wrote on 2007-04-23: [75](permalink)
I think commenting away the line must be the best solution. This chip
is used in *lots* of products, and by default they use the same
product and vendor id:s. It leads to very strange, non-obvious
problems on such devices.
Please please please fix!
[76] Samuel thibault wrote on 2007-04-23: [77]Re: [Bug 84139] Re:
Arduino detected as braille device (permalink)
Hi,
Just to make sure there's no confusion: I'm not an ubuntu maintainer
so
I just can't fix it, somebody else has to do it.
Samuel
[78] Wiktor Wandachowicz wrote on 2007-09-18: [79](permalink)
I've been hit by this problem too. Even though answers found through
Google suggested a complete removal of brltty, I dig deeper. Finally I
narrowed down the problem to one of the udev rule, specifically
tailored for an otherwise generic 0403:6001 Vendor/Product
combination. After commenting it out, my USB->Serial adapter worked
flawlessly.
Additional info:
* [80]Bug #122834 - FTDI USB Serial Device converter disconnects
The conclusion is that udev rules should be changed. So, awaiting the
action from maintainers... A simple, one-liner removal. Please!
[81] Kyle James wrote on 2007-10-01: [82](permalink)
It is still a problem in gutsy beta.
[83] zdzichu wrote on 2007-11-04: [84](permalink)
This is still non fixed in Ubuntu 7.10. brltty still breaks USB Serial
devices made with FTDI chipset. This is serious issue, can we have
fixed udev package, please?
[85] Samuel thibault wrote on 2007-11-04: [86](permalink)
* [87]Comment a generic USB to serial adapter ID (589 bytes,
text/plain)
Can somebody apply the attached patch please?
[88] hugolp wrote on 2007-11-08: [89](permalink)
Im having the same problem in Gutsy. Not with the Arduino device, but
with another usb dongle that uses the same usb chip. Im going to
remove brtty as a temporal fix, but the udev rule should be changed.
[90] Joel Berger wrote on 2007-11-20: [91](permalink)
This also impacts the DATAQ DI-148U USB data acquisition board. These
only identify as 0403:6001 if you change the jumper settings (not
recommended for Windows use, but required for Linux use since the
module doesn't recognize the default 0683:1480). I guess a better
question is this: since FTDI serial chips are used for so many
devices, is there a better way to identify them than by USB
vendor/device ID?
[92] Samuel thibault wrote on 2007-11-20: [93](permalink)
Joel Berger, le Tue 20 Nov 2007 22:06:12 -0000, a écrit :
> This also impacts the DATAQ DI-148U USB data acquisition board.
These
> only identify as 0403:6001 if you change the jumper settings (not
> recommended for Windows use, but required for Linux use since the
module
> doesn't recognize the default 0683:1480). I guess a better question
is
> this: since FTDI serial chips are used for so many devices, is there
a
> better way to identify them than by USB vendor/device ID?
After research on the brltty list, there didn't seem to be any way.
Samuel
[94] Samuel thibault wrote on 2007-12-14: [95](permalink)
There is no intelligent way, because braille manufacturers didn't make
their device in an intelligent way. But the attached patch should be
just fine, I really wonder why it didn't get applied.
[96] Luke Yelavich wrote on 2007-12-15: [97](permalink)
I intend adding this patch to BrlTTY for hardy, and am also going to
investigate it as an update for gutsy and earlier. Thanks Samuel for
the patch.
[98] TomWhipple wrote on 2007-12-15: [99](permalink)
The easiest way to deal with this is to completely remove brltty with
Synaptic.
It might not be a good solution for the big picture, but my board is
working now. :-)
[100] Luke Yelavich wrote on 2007-12-17: [101](permalink)
brltty (3.9-5ubuntu1) hardy; urgency=low
* Merge from debian unstable, (LP: #176477) remaining changes:
- Conflicts: libbrlapi, libbrlapi-dev, libbrlapi1-dev.
- Add brltty-setup, installed in both the udeb and the normal
system.
- Add initramfs integration to run brltty-setup if necessary
before
usplash starts.
- Add ubiquity integration to propagate any brltty configuration
to the
target system.
- Add udev rules and /lib/brltty/
brltty.sh to the normal (non-udeb)
package as well.
- Enable brltty if /etc/default/brltty has RUN_BRLTTY=yes, which
is set
by the installer if brltty is configured; add a NEWS entry for
upgraders.
- Install udev rules with the same name (85-brltty.rules) in the
udeb as
in the deb.
- Change maintainer to Ubuntu Accessibility Developers
<email address hidden>
* Disable BrlTTY grabbing devices that use the FTDI USB to serial
chip.
(LP: #84139)
* Remove the dh-lisp build-dependency, remove the cl-brlapi package,
and
adjust the brltty package description accordingly. dh-lisp is not
in main.
brltty (3.9-5) unstable; urgency=low
* Hopefully fix disabling Java support on ARM for real this time.
* Disable Java on m68k as well.
* Revisit debhelper calls and simplify.
* Convert debian/copyright and debian/
libbrlapi0.5.copyright to UTF-8.
* Update Standards-Version to 3.7.3 (no changes).
* Fix debian/rules so that "dpkg-buildpackage -j2" does not fail.
* Make python-brlapi part of section python.
-- Luke Yelavich <email address hidden> Sat, 15 Dec 2007 11:44:23
+1100
To post a comment you must [102]log in.
What next?
* [103]Report another bug about brltty in ubuntu
* [104]List open bugs for brltty in ubuntu
Duplicates of this bug
[105]Bug #90172
[106]Bug #96147
[107]Bug #122834
[108]Subscribe/Unsubscribe
[109]Subscribe someone else
[spinner]
Bug attachments
* [110]Comment a generic USB to serial adapter ID ([111]edit)
* [112]Add
Search
Enter bug ID or keywords:
[113]______ [114]Search
[115]Show all open bugs
[116]What is Launchpad? | [117]Get help with Launchpad
© 2004-2009 [118]Canonical Ltd. | [119]Terms of use
IFRAME: [120]javascript:void(0);
References
Visible links
1. http://feeds.launchpad.net/bugs/84139/bug.atom
2. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+login
3. form field = text-submit field
4. https://bugs.launchpad.net/
5. https://bugs.launchpad.net/ubuntu
6. https://bugs.launchpad.net/ubuntu/+source
7. https://launchpad.net/ubuntu/+source/brltty
8. https://bugs.launchpad.net/ubuntu/+source/brltty
9. https://answers.launchpad.net/ubuntu/+source/brltty
10. https://bugs.launchpad.net/~mute-howell-ersatz
11. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+activity
12. https://bugs.launchpad.net/bugs/84139
13. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+secrecy
14. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+duplicate
15. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+create-question
16. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+viewstatus
17. https://bugs.launchpad.net/ubuntu/+source/brltty
18. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+viewstatus
19. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+viewstatus
20. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+viewstatus
21. https://bugs.launchpad.net/~themuso/+assignedbugs
22. https://bugs.launchpad.net/ubuntu/+source/brltty
23. https://bugs.launchpad.net/~mute-howell-ersatz
24. form field = text entry field
25. javascript:popup_window('@@popup-window?vocabulary=SourcePackageName&field=ubuntu_brltty.sourcepackagename&search='+escape(document.getElementById('ubuntu_brltty.sourcepackagename').value),'ubuntu_brltty.sourcepackagename','300','420')
26. javascript:void(0);
27. form field = popup menu
28. form field = radio button
29. form field = radio button
30. form field = radio button
31. form field = radio button
32. form field = text entry field
33. javascript:popup_window('@@popup-window?vocabulary=ValidAssignee&field=ubuntu_brltty.assignee&search='+escape(document.getElementById('ubuntu_brltty.assignee').value),'ubuntu_brltty.assignee','300','420'); document.getElementById('ubuntu_brltty.assignee').onkeypress()
34. javascript:void(0);
35. form field = text entry area
36. form field = text entry area
37. form field = text entry area
38. form field = text entry area
39. form field = checkbox
40. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+choose-affected-product
41. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+distrotask
42. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+nominate
43. http://www.arduino.cc/
44. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+edit
45. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+addbranch
46. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+linkcve
47. https://bugs.launchpad.net/~samuel-thibault
48. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/1
49. https://bugs.launchpad.net/~cjwatson
50. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/2
51. https://bugs.launchpad.net/~henrik
52. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/3
53. https://bugs.launchpad.net/bugs/83939
54. https://bugs.launchpad.net/~samuel-thibault
55. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/4
56. https://bugs.launchpad.net/~mlang-delysid
57. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/5
58. http://debian.org/
59. http://delysid.org/
60. http://www.staff.tugraz.at/mlang/
61. https://bugs.launchpad.net/~samuel-thibault
62. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/6
63. https://bugs.launchpad.net/~mlang-delysid
64. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/7
65. http://debian.org/
66. http://delysid.org/
67. http://www.staff.tugraz.at/mlang/
68. https://bugs.launchpad.net/~stuhood
69. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/8
70. https://bugs.launchpad.net/~samuel-thibault
71. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/9
72. https://bugs.launchpad.net/~samuel-thibault
73. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/10
74. https://bugs.launchpad.net/~jonatan
75. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/11
76. https://bugs.launchpad.net/~samuel-thibault
77. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/12
78. https://bugs.launchpad.net/~siryes
79. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/13
80. https://bugs.launchpad.net/bugs/122834
81. https://bugs.launchpad.net/~kvitale
82. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/14
83. https://bugs.launchpad.net/~zdzichu-gmail
84. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/15
85. https://bugs.launchpad.net/~samuel-thibault
86. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/16
87. http://launchpadlibrarian.net/10269767/patch
88. https://bugs.launchpad.net/~hugolp2
89. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/17
90. https://bugs.launchpad.net/~hikari-lp
91. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/18
92. https://bugs.launchpad.net/~samuel-thibault
93. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/19
94. https://bugs.launchpad.net/~samuel-thibault
95. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/20
96. https://bugs.launchpad.net/~themuso
97. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/21
98. https://bugs.launchpad.net/~mail-tomwhipple
99. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/22
100. https://bugs.launchpad.net/~themuso
101. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/comments/23
102. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+login?comments=all
103. https://bugs.launchpad.net/ubuntu/+source/brltty/+filebug
104. https://bugs.launchpad.net/ubuntu/+source/brltty/+bugs
105. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/90172
106. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/96147
107. https://bugs.launchpad.net/bugs/122834
108. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+subscribe
109. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+addsubscriber
110. http://launchpadlibrarian.net/10269767/patch
111. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+attachment/168484
112. https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139/+addcomment
113. form field = text entry field
114. form field = submit button
115. https://bugs.launchpad.net/ubuntu/+source/brltty/+bugs
116. https://bugs.launchpad.net/+tour
117. https://help.launchpad.net/
118. http://canonical.com/
119. https://bugs.launchpad.net/legal
120. javascript:void(0);
Hidden links:
121. https://bugs.launchpad.net/bugs/84139/+bug-portlet-subscribers-content
----- End forwarded message -----
--
https://bugs.launchpad.net/ubuntu/+bug/1 :
Micro$oft has a majority market share in the new desktop PC marketplace.
This is a bug, which Ubuntu is designed to fix !
http://www.ubuntu.com/
---
--
CarrefourBLinuX MailingListe
Pour obtenir de l'aide, envoyez le sujet help à:
carrefourblinux-request@xxxxxxxxxxxxxxxxxxx
Archives:
http://listengine.tuxfamily.org/lists.tuxfamily.org/carrefourblinux