from:"Bill Turner, wb4alm"

[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04

2022-12-16 Thread Bill Turner, wb4alm

Installation of UBUNTU 22.04.1 on August 15, 2022 STILL HAS THIS BUG.

The installation was an upgrade from UBUNTU 20.04 which failed due to
other issues with PYTHON.

Subsequent clean installs of UBUNTU 22.04.1 constantly caused re-
occurances of this bug.

It was necessary to UNINSTALL brltty to restore access to my USB->Serial
converts.

Installation of LINUX MINT 21 in December 2022 did --NOT-- have this
problem.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1958224

Title:
  brltty claiming cp210x devices on 22.04

Status in brltty package in Ubuntu:
  Fix Released
Status in brltty source package in Jammy:
  Fix Released
Status in brltty package in Debian:
  Confirmed

Bug description:
  * Impact

  The brltty udev rules are claiming generic devices IDs which makes
  some other devices like Arduino cards not able to interact with the
  serial port anymore

  * Test Case

  Try to use an Arduino over a cp210x or FTDI serial port, it should be
  able to talk to the computer

  - upgrades from focal/impish to the SRU version should have no
  question and no /etc/udev/rules.d/86-brltty-usbgeneric.rules generated

  - upgrades from brltty 6.4-4ubuntu2
  1. if a device matching the IDs 0403:6001 / 10C4:EA60 / 10C4:EA80 is 
connectect at the time of the upgrade it should prompt with the debconf question
  1.a if the answer is yes, /etc/udev/rules.d/86-brltty-usbgeneric.rules should 
be generated
  1.b if the answer is no, /etc/udev/rules.d/86-brltty-usbgeneric.rules not 
installed

  2. if no matching device is connected
  there should be no debconf question nor 
/etc/udev/rules.d/86-brltty-usbgeneric.rules generated

  - installing brltty when it was not installed
  no question and no config generated

  * Regression potential

  If the debconf logic is wrong users could be prompted with the
  question when not needed or not prompted when they should. If the udev
  rules was incorrect or wrongly installed it could lead to have brltty
  not starting when it should

  ---

  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy
  brltty:  Installed: 6.4-2ubuntu1

   brltty appears once again to be claiming cp210x devices with the
  vendor/product ID of:

  idVendor=10c4, idProduct=ea60

  Example dmesg output:
    999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
  [  999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
  [  999.215977] usb 3-6.3: Manufacturer: Silicon Labs
  [  999.215978] usb 3-6.3: SerialNumber: 0005
  [  999.234070] usbcore: registered new interface driver usbserial_generic
  [  999.234081] usbserial: USB Serial support registered for generic
  [  999.235262] usbcore: registered new interface driver cp210x
  [  999.235272] usbserial: USB Serial support registered for cp210x
  [  999.235298] cp210x 3-6.3:1.0: cp210x converter detected
  [  999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
  [  999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
  [  999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input42
  [  999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' 
sets config #1
  [  999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
  [  999.995066] cp210x 3-6.3:1.0: device disconnected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1990357] Re: ch340 USB/serial - brltty interference

2022-12-16 Thread Bill Turner, wb4alm

Under UBUNTU 22.04.1 brltty PREVENTED me from using a USB->serial
converter to access a remote piece of equipment. Once uninstalled, I had
full access to the remote device.

Under LINUX MINT 21, you cannot uninstall brltty, and it did --NOT--
create a problem with the remote device, other than a name change to the
port.

Under UBUNTU 22.04.1, the port is named  /dev/ttyUSB0
Under Linux Mint 21,  the port is named  /dev/ttyS0

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1990357

Title:
  ch340 USB/serial - brltty interference

Status in brltty package in Ubuntu:
  Confirmed

Bug description:
  the CH340 does show up in lsusb:
  'Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics CH340 serial converter'

  but does not show up in /dev if brltty is installed on the system.

  Device does show up as /dev/ttyUSB0 after removing brltty and
  rebooting.

  tested systems:
  Ubuntu 22.04.1 (live USB) - problem present
  Linux Mint 21 (fresh install, updated) - problem present

  ubuntu-bug does not recognise brltty as an ubuntu package and thus
  refuses to collect data.

  The CH340 is a very common USB/serial converter chip used in cheap 3D 
printers and microcontroller development boards.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5json: {
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 21
  InstallationDate: Installed on 2022-09-20 (0 days ago)
  InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: brltty 6.4-4ubuntu3 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Tags: third-party-packages vanessa
  Uname: Linux 5.15.0-48-generic x86_64
  UnreportableReason: This does not seem to be an official Linux package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990357/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1839544] Re: power setting "display off" maximum is 15 minutes, used to have several hour increment values

2019-08-28 Thread Bill Turner, wb4alm

This should be a very simple thing to fix. And if I knew "C" I would fix it
myself.
but I don't, my knowledge base is in many other computer programming languages
that date all the way back to the 1960's. While I still program computers,
now-a-days they are primarily a tool to be used in solving other problems...

In my opinion, the best long term fix would be to provide a "[ ] other" box
with a way to allow entering the actual idle time desired -- then a user can
set it to what ever their circumstances dictates.

unfortunately, The concept of "keyboard idle" is not necessarily the
best indication of an "unattended terminal". and the futuristic concept
of tracking eyeball movements to see if anybody is actually looking at
the screen, would probably not be acceptable to most humans.

"15 min" of no keyboard/mouse movement is too short a time period, especially
when the screen is being used to display reference material.

"never" is too long, especially when you need to keep user specific
background processes running - or I would simply logoff and log back on
later.

(One would hope that the user selectable "idle time" values are being
translated internally to some form of seconds or minutes, and that they
are not simply used to set a series of "bit switches", thus my
suggestion to provide a text entry box.)

I would also like to suggest that most folks use a computer to solve
real world problems, and that computers exist primarily as a tool to be
used, and not just as just programming exercises

Thank you.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1839544

Title:
power setting "display off" maximum is 15 minutes, used to have
several hour increment values

Status in gnome-control-center package in Ubuntu:
New

Bug description:
Just upgraded to Ubuntu 18.04.2 LTS from Ubuntu 16.04 LTS.

In the POWER settings for blanking the display, there used to be
several options that allowed selecting a time interval of 1 hour, 2
hours, 4 hours, etc.

Under Ubuntu 18.04.2 there are only 9 selectable time values:
i.e. 1 min, 2 min, 3 min, 4 min, 5 min, 8 min, 10 min, 12 min, 15 minutes,
and never.

This might be fine for a portable laptop running on batteries, but is
not acceptable for a desktop system.

The never option is not good, because then the monitor NEVER goes
dark.

My preferred time is to set this to 1-hour because of the length of
conference calls.
It is a real nuisance to have the screen blank on you while you are reading
information displayed on the screen to a multi-person conference call...
...Especially if you lock your screen, requiring you to log back on.

I suggest adding some of the time values back to the pull down list,
or possibly adding a "other" fill-in value box where the user can
specify in minutes when he wants the screen to blank when idle.

I consider this to be a bug, and not a feature enhancement, because I
used to be able to say "1 hour".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839544/+subscriptions

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1839544] [NEW] power setting "display off" maximum is 15 minutes, used to have several hour increment values

2019-08-08 Thread Bill Turner, wb4alm

Public bug reported:

Just upgraded to Ubuntu 18.04.2 LTS from Ubuntu 16.04 LTS.

In the POWER settings for blanking the display, there used to be several
options that allowed selecting a time interval of 1 hour, 2 hours, 4
hours, etc.

Under Ubuntu 18.04.2 there are only 9 selectable time values:
i.e. 1 min, 2 min, 3 min, 4 min, 5 min, 8 min, 10 min, 12 min, 15 minutes, and
never.

This might be fine for a portable laptop running on batteries, but is
not acceptable for a desktop system.

The never option is not good, because then the monitor NEVER goes dark.

My preferred time is to set this to 1-hour because of the length of conference
calls.
It is a real nuisance to have the screen blank on you while you are reading
information displayed on the screen to a multi-person conference call...
...Especially if you lock your screen, requiring you to log back on.

I suggest adding some of the time values back to the pull down list, or
possibly adding a "other" fill-in value box where the user can specify
in minutes when he wants the screen to blank when idle.

I consider this to be a bug, and not a feature enhancement, because I
used to be able to say "1 hour".

** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New