From Newsgroup: alt.os.linux.mint

Bug reporting, never mind.
I recently got tempted to try and report a bug, after asking Google how
to do that, ending up with dead links and complains from other that it
is extremely complicated or better, impossible.
OK never mind, our cut and paste coders don't care anyway.

It reminds me of the old:
The second with a complaint will be shot, one complain we already had.
--
Once an organization gains any influence, it will be corrupted from both within and without.

Edmund

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Thu, 12/11/2025 11:08 AM, Edmund wrote:

Bug reporting, never mind.
I recently got tempted to try and report a bug, after asking Google how to do that,
ending up with dead links and complains from other that it
is extremely complicated or better, impossible.
OK never mind, our cut and paste coders don't care anyway.

It reminds me of the old:
The second with a complaint will be shot, one complain we already had.

Bug reporting is an art.

Practice makes perfect.

If you do not provide substantial related information in
one of these queries, nobody can turn your experience into
a positive one for you.

And there are some projects, I WOULD NOT recommend you file a bug.
Many other sites, the individuals involved are fully functional,
balanced human beings. But nothing prevents a bug reporting scheme,
from being filled with ass-hats. It happens.

On a typical site:

1) Authenticate yourself. You need to create an account, or
they may have some social media login as a solution.

2) Create the standard fileset defined for a bug report.
This establishes what distro this is, what kernel, what
graphics card and driver, what release of application this is,
and so on. On some sites, there is a bash shell they offer,
for generating the files.

3) Craft your description in the text, the way that other
"successful" threads craft them. You need sufficient color
commentary about what you were doing, to not leave the bug buster
wondering exactly what you were doing. Why, it's almost like crafting
good USENET questions, in fact :-) Nobody on the other side of
the screen, is a mind reader.

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On 12/11/25 18:07, Paul wrote:

On Thu, 12/11/2025 11:08 AM, Edmund wrote:

Bug reporting, never mind.
I recently got tempted to try and report a bug, after asking Google how to do that,
ending up with dead links and complains from other that it
is extremely complicated or better, impossible.
OK never mind, our cut and paste coders don't care anyway.

It reminds me of the old:
The second with a complaint will be shot, one complain we already had.

Bug reporting is an art.

Practice makes perfect.

If you do not provide substantial related information in
one of these queries, nobody can turn your experience into
a positive one for you.

And there are some projects, I WOULD NOT recommend you file a bug.
Many other sites, the individuals involved are fully functional,
balanced human beings. But nothing prevents a bug reporting scheme,
from being filled with ass-hats. It happens.

On a typical site:

1) Authenticate yourself. You need to create an account, or
they may have some social media login as a solution.

2) Create the standard fileset defined for a bug report.
This establishes what distro this is, what kernel, what
graphics card and driver, what release of application this is,
and so on. On some sites, there is a bash shell they offer,
for generating the files.

3) Craft your description in the text, the way that other
"successful" threads craft them. You need sufficient color
commentary about what you were doing, to not leave the bug buster
wondering exactly what you were doing. Why, it's almost like crafting
good USENET questions, in fact :-) Nobody on the other side of
the screen, is a mind reader.

Paul

Lot of words but admit it, you can't file a bug either.
--
Once an organization gains any influence, it will be corrupted from both within and without.

Edmund
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On 12/11/25 19:47, Mike Easter wrote:

Edmund wrote:

Bug reporting, never mind.

I agree; if you are 'only' an end user.-a For the most part, dev/s of an
app or a system or a website are *only* interested in the knowledgeable opinion of someone of their own 'caliber', not some end-user 'complaint' about something.

A bug report has to be of professional quality.

Did I tell you before you are a extremely ignorant prick who doesn't
even understand users run into bugs.
No, well here you have it.
--
Once an organization gains any influence, it will be corrupted from both within and without.

Edmund
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Edmund wrote:

Mike Easter wrote:

Edmund wrote:

Bug reporting, never mind.

I agree; if you are 'only' an end user.-a For the most part, dev/s of
an app or a system or a website are *only* interested in the
knowledgeable opinion of someone of their own 'caliber', not some end-
user 'complaint' about something.

A bug report has to be of professional quality.

Did I tell you before you are a extremely ignorant prick who doesn't
even understand users run into bugs.
No, well here you have it.

Silly boy; of course end users run into bugs; but it is my experience
that the *reporting* of bugs by those end-users isn't really what the
dev of the bug-issue wants to hear.

They want to hear a more professional-type report of what makes the bug.
--
Mike Easter
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Edmund wrote:

Bug reporting, never mind.

I agree; if you are 'only' an end user. For the most part, dev/s of an
app or a system or a website are *only* interested in the knowledgeable opinion of someone of their own 'caliber', not some end-user 'complaint'
about something.

A bug report has to be of professional quality.
--
Mike Easter
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Mike Easter wrote:

Edmund wrote:

Mike Easter wrote:

Edmund wrote:

Bug reporting, never mind.

I agree; if you are 'only' an end user.-a For the most part, dev/s of
an app or a system or a website are *only* interested in the
knowledgeable opinion of someone of their own 'caliber', not some end-
user 'complaint' about something.

A bug report has to be of professional quality.

Did I tell you before you are a extremely ignorant prick who doesn't
even understand users run into bugs.
No, well here you have it.

Silly boy; of course end users run into bugs; but it is my experience
that the *reporting* of bugs by those end-users isn't really what the
dev of the bug-issue wants to hear.

They want to hear a more professional-type report of what makes the bug.

If ever "the brass" or "the suits" complain about too few customers
visiting their sites, they did not regard the advice, to use their own
sites themselves to discover what crap gets downloaded onto the
customers.
Regards,
H.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Thu, 12/11/2025 12:35 PM, Edmund wrote:

Lot of words but admit it, you can't file a bug either.

The bugs I've filed, were fixed promptly. Meaning
"in about three months". One was reproducible on
demand, so all I had to indicate was a source of the
program, the undesired result, and the OS was fixed
so it didn't happen any more.

You have to:

1) Imagine there is only one opportunity to transfer
a description to the other end.

2) Imagine you're the dev receiving the input. For
reproducible bugs, those are the "best bugs" because
there is no ambiguity, no "could not reproduce"
coming back.

Remember that I used to work in the industry, receive
bug reports, take bug reports in my teeth that
other staff would not take, and run with them.
If I detected "shirking of duty", I would do it.
I would see to it that a thing was fixed. On occasion,
I would sit in the bug review meeting, as the "representative
from hardware", and I would watch how bug routing
was being done. That's how I learned what
ass-hats look like (turning "bugs" into "feature requests"
and other chicanery). It wasn't my job to do all of
that, but as a "team player", I would do my regular job
and that too.

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Thu, 12/11/2025 2:05 PM, Mike Easter wrote:

Edmund wrote:

Mike Easter wrote:

Edmund wrote:

Bug reporting, never mind.

I agree; if you are 'only' an end user.-a For the most part, dev/s of an app or a system or a website are *only* interested in the knowledgeable opinion of someone of their own 'caliber', not some end- user 'complaint' about something.

A bug report has to be of professional quality.

Did I tell you before you are a extremely ignorant prick who doesn't even understand users run into bugs.
No, well here you have it.

Silly boy; of course end users run into bugs; but it is my experience that the *reporting* of bugs by those end-users isn't really what the dev of the bug-issue wants to hear.

They want to hear a more professional-type report of what makes the bug.

To meet the quality requirement, just generate the files they
ask for as attachments. Usually there is a posting in a
forum with instructions for anyone to follow.

Other forums have had a kind of form to fill out, to ensure
the metadata is collected. But that can be less successful,
because the person filling the form may not know how to
answer the question. Running a script that collects the
info, leaves less to the imagination.

The forms that ask you to categorize what department the
bug should be sent to, that's just silly. Some of the bugs
straddle clear lines of delineation, and you "can't file
it under text editors" because it isn't about that. Bug routing
is work, but it is essential that a bug be forwarded by
someone at the other end, to the right queue for action.
We don't know how to do your job.

When we play "twenty questions" here, ask questions such
as "is it bigger than a bread box", that sort of thread
is an indication the initial description was lacking.
I sometimes include pictures, if there is an area I
want a person to focus on, to try and get a discussion
on some rails.

Some bugs never get fixed, the staff being uninterested
in the work involved. That's how Notepad on Windows
can go for fifteen years without the Find/Replace
behavior getting fixed. But it was eventually
fixed properly -- my jaw dropped the day I tested
that and it was fixed.

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Thu, 11 Dec 2025 19:11:29 -0500
Paul <nospam@needed.invalid> wrote:

[]

Some bugs never get fixed, the staff being uninterested
in the work involved. That's how Notepad on Windows
can go for fifteen years without the Find/Replace
behavior getting fixed. But it was eventually
fixed properly -- my jaw dropped the day I tested
that and it was fixed.

Cite?
I've found bug reports for notepad++, but didn't come across the MS bug
--
Bah, and indeed Humbug.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

On Fri, 12/12/2025 5:01 AM, Kerr-Mudd, John wrote:

On Thu, 11 Dec 2025 19:11:29 -0500
Paul <nospam@needed.invalid> wrote:

[]

Some bugs never get fixed, the staff being uninterested
in the work involved. That's how Notepad on Windows
can go for fifteen years without the Find/Replace
behavior getting fixed. But it was eventually
fixed properly -- my jaw dropped the day I tested
that and it was fixed.

Cite?
I've found bug reports for notepad++, but didn't come across the MS bug

Here are the test results. Tested Win7 and Win10 Wordpad for contrast.
Only one Notepad test thrown in.

Wordpad is slow.
And was still slow on Win10 before it was deprecated.

Notepad barely blipped a core doing the test.

[Picture] Click "Download Original" to stay away from the advertising

https://i.postimg.cc/nrpRHQ4J/Wordpad-is-slow-Notepad-OK.gif

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

; Scratch buffer -- list evaluation

On Thu, 11 Dec 2025 17:08:58 +0100, Edmund wrote:

Bug reporting, never mind. I recently got tempted to try and report
a bug, after asking Google how to do that, ending up with dead links
and complains from other that it is extremely complicated or better, impossible.

Or you could, you know, look at the projectrCOs home page. There you
will likely find source code, some docs, a bug tracker, possibly even
a wiki and discussion forums.
--- Synchronet 3.21a-Linux NewsLink 1.2