Re: report a Debian bug
On 11/1/23 19:57, Felix Miata wrote:
gene heskett composed on 2023-11-01 19:20 (UTC-0400):
Felix Miata wrote:
gene heskett composed on 2023-10-31 10:26 (UTC-0400):
Mail sent to admin@bugzilla.com bounces.
Bugzilla.com has nothing to do with tracking any kind of software issues. It's
about Volkswagen Bug automobiles.
That is informative, thanks Felix, but what is wrong with publishing
the correct address? Not being able to use it, I haven't reserved space
for it in the wet ram... ;o)>
For one thing, I never use it directly, and another, it doesn't include the string
bugzilla, so I don't remember what it is, and thus need to look it up, same as
you, if and when I want it. I use the Debian software named reportbug. If you
don't wish to use reportbug, start here:
https://www.debian.org/Bugs/
If you do:
https://www.debian.org/Bugs/Reporting
or
man reportbug
I started with that, was amazed at the complexity so I figured I'd just
wing it, used the novice profile but when it asked me for package I gave
it 12 for other, then got stuck in a forever loop and when it was
obvious it wasn't going let me go by I gave it a ctl-c. I have no clue
what to file it against as it doesn't give me a program list to choose
from but a list of mostly web pages. I can however, describe the
miss-behaviour I get and have 2 or 4 times on this list and been ignored.
So what i'm going to do next is transfer my /home, the whole MaryAnn
from a 4 drive raid10 to a single 2T SSD,, and then switch /home from
the raid to a single drive, thereby removing the raid10 from the culprit
list.
If that doesn't fix it, then its something to do with the graficks.
I have one real clue, some one the openscad list said the preview mode
opened a bunch of gfx buffers it used the preview mode that it didn't do
in final build mode, so I ran some tests on a fairly complex project,
noting that the openscad logging window said a preview was done in a bit
over a second but the final monocolored version took over 9 seconds to
render, giving me an image I could move in 3d space in the preview
window in real time. But that 1.2 second preview render took 30 to 45
seconds to show in\on screen and every update of that image took at
least 45 seconds to register on screen, and during that 45 seconds or
more, openscad was frozen from all other input. That is as close to a
clue as I have, also manifested when any kind of a file requester needs
to be drawn on screen it is subjectto to that same time killing lockup
except it might be as long as 5 minutes before the requestor is drawn on
screen. That raid was built by buster, worded fine for bullseye, but
seems to be a disaster for bookworm, yet an fsck finds nothing wrong.
Those are the clues I have. Nothing obvious and common to all this
contaminates the logs.
I own the whole nearly 1.8T raid10, every byte of it. Why can't I use
it? Instead its holding me for an undefined ransom in time that I at 89
don't have a lot of left.
Thanks Felix, take care & stay well.
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
Reply to: