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. 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. 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
