On 1/7/25 06:01, Timothy M Butterworth wrote:
On Tue, Jan 7, 2025 at 3:51 AM gene heskett <ghesk...@shentel.net> wrote:
On 1/6/25 22:13, Max Nikulin wrote:
On 06/01/2025 14:09, gene heskett wrote:
On 1/5/25 21:21, Max Nikulin wrote:
On 05/01/2025 23:28, gene heskett wrote:
As for bug number, I'm not the OP, just a canary.
Then ask the author to add the bug number. Tell them that without a
link you were not be able to check current state of affairs and, as
a result, you have secured your reputation as a liar.
So be it Max, nothing I can do. This list doesn't want to accept that
I am truthful when reporting a problem. Shrug...
Gene, are you realizing that instead of reporting a problem, you are
actually just spreading some rumors and attacking Debian developers?
Be responsible, if you are expecting warm reaction.
The reaction I got for mentioning it, now years ago, convinced me that I
most obviously shouldn't have mentioned it. The reception I got at the
time could only be called hostile. I did use reportbug at the time and
I assume I was emailed a bug number, which I've obviously lost in all
the installs I was forced to do because once I had shut orca up, the
machine would not reboot, stuck very early in the boot process waiting
for orca to come alive. Forever, so reboots were reinstalls. I finally
figured out how to shut orca off and reboot. But opening a local file I
own is still subject to a 30+ second timeout during which time the
machine is totally frozen except the analog kclock. Many times I have
several screens full of errors logged, which might contain clues as to
what is blocking things, but the list strips attachments so no one but
me sees them.
I ask for help, describing what happening and no one has offered a
solution other than yet another new install. Only one other person has
reported a similar problem, by PM as hes seen the reception I've gotten
for suggesting the installer is broken, with an side comment that
installer in the live dvd image doesn't do that.
I also ran into the Orca and brltty Hell problem Gene described, after a
clean install from DVD. Disabling Orca through system settings did not work
and required logging off and then back in for the change to take effect.
Brltty broke my serial console and I still can not switch virtual
terminals. So far selecting yes to installing accessibility tools has been
a giant PITA! I will not make the accessibility hell mistake again! On my
new laptop I installed from KDE Live DVD and thankfully it did not even
have an option to install accessibility tools and everything works great.
Well almost great, it did not ask me to setup mirrors during the
installation so I had to manually setup debian repos.
I have only one laptop that I need to perform a clean install on to get
ride of the accessibilitiy hell. I am going to install Trixie weekly KDE
Live DVD on it. I was running Trixie on it until I updated to KDE 6.2.3 and
network manager applet disapeared. KDE 6.2.4 fixed that problem on my
virtual machine. So It is time to move Trixie back to physical hardware.
But I have enough work
stored on this machine now that I'd lose with a re-install that I'm
building me an 8T raid10 amanda backup system I hope to have working
when trixie is announced.
8 TB is not that big. I have a external 18 TB drive. It is 18 TB in name
only though! After fromating it with ext4 it only had 15TB of usuable
space. The drive itself was cheap. Which can be heard by the clicking and
grinding noises it makes.
That has to be spinning rust. And sounds like it is using a cane to
walk. In my systems there is only one spinning rust, the rest have all
been fitted with SSD from 120G to 4T. the only spinning rust is in the
machine running my 6040 gantry mill, and its a 250G seacrate built back
when they made good drives. Why just one? 2 years ago I bought a pair if
new seagate 2T's and put them in this machine. 1 to run /home on, and
one for amanda, backing up the rest of my stuff. Both of those drives
disappeared of the end of a sata-ii cable in consequtive nights less
that 2 weeks later. I lost everything including the only picture of my
first wife, who had a stroke and died in '68. She came with 2 of her
own and we made 3 more, all of which have since passed. I'd already had
my battles with seagate and that was the last straw. They would not sell
me a head drum for their tape changer, so it spent the holidays every
year in Oklahoma City getting a rebuild & new drum. At the time I was
the CE at a tv station with 13 Panasonic DVC-PRO machines, machines I
could put a new head in one in the morning and 1 in the afternoon. Its a
bit complex and needed a 4 trace scope with 100megs of bandwidth to do
it. I was fully qualified to do a drum in a tape drive. And was denied
the part. So over time I've had my fill of seagate. I didn't even bother
to warranty that junk.
Yes folks, electronically, I have been there and done that, with 2
exceptions caused by the FCC or whatever, I fixed it all, from $10,000
tv zoom lenses to $300,000 transmitters. But I can't fix what there is
no docs for. Or information I don't know where to pull the docs from.
With external storage prices getting lower and
read/write speeds increasing exponentially, particuarly with Thunderbolt 4
I no longer bother with RAID! I just have two external drives, one primary
for daily use and the other is a backup of the primary using rsync.
Considering that all but one of my PC's are laptops, the one that isn't a
laptop is a small form factor Micro PC with no drive expansion
capabilities, I could not run RAID even if I wanted to.
A du -h /home/gene is 343Gigs. I've been busy
with OpenSCAD and 3d printers.
Reread that topic related to klipper.
I probably originated it.
If there is no link to a Debian bug then either use a search engine to
find it yourself or ask the clipper community if somebody has
contacted Debian developers.
They have, and apparently got the same reception I've gotten. So they
wrote a patch and pinned it on discord. So we klipper users fixed it
years ago. Yet its an unauthorized line of code. Why, with that
attitude, should I bother, years later, with all this?
Finally request to update the topic with the outcome.
Searching (you need rights) for udev bugs should find it if some dev
hasn't erased it. I don't know how and have long since lost the pw. I
ask for a pw reset but don't get it. Several times. I'm apparently a
nobody to the devs.
Verify the bug has been fixed with "ls /dev/serial/by-id/" if you don't
get a valid response, that's the bug.
You should get something that looks faintly like this:
gene@coyote:~$ ls /dev/serial/by-id/
usb-1a86_USB_Serial-if00-port0
usb-FTDI_USB_HS_SERIAL_CONVERTER_FTDHG45D-if00-port0
word wrapped by tbird of course. Those are in fact brother printers or
cm11a's for x10 stuff. And they were NOT plugged in for the last 25
installs after someone said to unplug the usb stuff.
Thank you Max.
Cheers, Gene Heskett, CET.
--
"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
