Re: non-starting browsers - the whole sad history

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sunday, February 27, 2022 1:01:06 PM EST E. Liddell wrote:
> On Sun, 27 Feb 2022 10:59:33 -0500
> 
> gene heskett <gheskett@xxxxxxxxxxx> wrote:
> > someplace in my USB tree, there's at least one, and probably more,
> > FDTI usb to serial adaptors that the installer THINKS is a Braille
> > driver, so it, without asking, installs brltty and orca, the speech
> > enabled screen reader no one can understand. And it, if you remove
> > the stuff after the install is done, will NOT reboot past the 10
> > second mark in the boot log cuz its stuck looking for that crap and
> > can't find it.
> > 
> > Very damned distracting when its trying to pronounce every key you
> > type and no one knows how to remove it without filling the boot
> > drive with> 
> >  /var/log/syslog until the system is unusable because of the lags
> >  imposed> 
> > by opening the log when its 50+ megabytes 18 hours after the install,
> > search for the end of it, writing 9 or 10 more lines of error
> > messages
> > and closing the log, for every keystroke typed.
> > 
> > The only fix I've found that lets my machine stay up for a few days,
> > (uptime is 7+ days atm) is to find the .conf files in /etc, and
> > direct
> > all that error output to /dev/null. That leaves one line of errors
> > still going to syslog about every 20 seconds as something in
> > systemd.d keeps looking for the speech dispatcher over blue tooth,
> > and there isn't any of that except the keyboad and mouse.
> 
> Sounds like you need to kill the service(s) involved using whatever
> systemd's equivalent of rc-update is (or overwrite the service files
> with no-ops and then make them unwritable so they can't be changed),
> blacklist any kernel modules involved, and possibly write some udev
> rules to force the problem device to be properly identified.  Rather a
> tedious process that would have to start with identifying the problem
> device and its USB ID.

idVendor           0x0403 Future Technology Devices International, Ltd
idProduct          0x6001 FT232 Serial (UART) IC

idVendor           0x0403 Future Technology Devices International, Ltd
idProduct          0x6001 FT232 Serial (UART) IC

That device seems to be the device triggering all this hate and 
discontent, but the differences in priority of whats to be done boggles 
my mind.

I have done around 20 installs, which include finding, unpacking a 
copying back to where they belong each time I thought I had whupped it 
this time. Thats around a 40 hour day per install.

Two of those are plugged in but in all the hubs laying on the floor, I 
have no idea which cable is actually those 2. And I can see 3 hubs from 
this chair. Now if we had an lsusb utility that told us which port of 
which hub it was plugged into...

I don't want to lose that data yet again, but while the installer can 
find the partitions and the raifd10 just fine, it will not proceed with 
the install unless it can format a goodly number of gigabytes of data 
away yet again... I've been doing these from scratch installs since early 
October last year. This stuff can be removed with the package manager, 
but it will not remove the startup stuff that stops a reboot from 
proceeding past the 10 second mark because the startup stuff has not been 
removed too, so the only way I could reboot was to install it all new, 
which of course put it back in.

I asked how to get rid of it gracefully several times and was either 
ignored, or was given advice that was totally unrelated to the problem 
but all of which involved doing yet another install.

Surely whats been installed should be removable without destroying the 
rest of the system? But that approach isn't on the menu.  

Yet I'm to blame for my frustration? 

Debian made this situation, and debian s/b willing to help without me 
embarking on yet another multiday install and data recovery that takes 
days to get it all back.  I have another SSD the netinstall could be 
copied to and booted from if I could figure out how to bypass the iso 
9660 stuff, and that could be edited to bypass this stuff, but no one at 
debian in a position to actually fix it wants to help me do that. In 
fairness to debian I have not specifically asked about that possibility.

Thank you, take care and stay well, E. Liddell

> E. Liddell

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
One of the things I have not yet restored.


____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx



[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux