Mailinglist Archive: opensuse (2348 mails)

< Previous Next >
Re: [opensuse] Novell Bugzilla - At it Again - Bugs Apparently Dismissed Without Sufficient Investigation
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Fri, 4 Apr 2008 12:37:39 +0200 (CEST)
  • Message-id: <alpine.LSU.1.00.0804041214410.2816@xxxxxxxxxxxxxxxx>
Hash: SHA1

The Friday 2008-04-04 at 01:20 -0500, David C. Rankin wrote:


How many of you have ever gotten the feeling that some of the developers with Novell bugzilla work harder trying to punt bugs than they do actually trying to understand whether a valid problem exists or not? I have been frustrated a number of times when gone the extra mile to provided a detailed documented bug submission, only to have someone at Novell try to punt the bug when it is apparent that not one iota of investigation has been done sufficient to either rule in or rule out a problem.


it for some cockemamy reason. The latest classic example:

A software bug is being reported, but since the software log says the error is hardware, they try and close the bug. Notwithstanding the entire bug focuses on the systems response to having the nvidia kernel module loaded, and how it runs fine without the software, the entire bug was closed as invalid because the mcelog says some of the errors are hardware error. And, if mcelog say so, then it's got to be true! Sad, really.

The report has some points not clear.

For one thing, if the problem occurs _only_ when the nvidia driver loaded, the one made by nvidia, then you will have a very hard time convincing anyone to even look at it. It is closed source! The kernel puts a message saying "Tainted!", and developers will not touch it as if it were leprous.

They have their reasons and I wont argue them, nor who is to blame, but it is a sad situation for users, who certainly are not to be blamed. This is like a city transport strike: they go against the management, but it is the users who suffer it.

Then at some point in the report you say that you got locks or crashes, days after removing that driver, and the log says "hardware". When the assignee says "its' hardware, then invalid", you say that it was triggered by having the nvidia module loaded.

You see, if it happens when or after loading the nvidia module, they will not look at it. If it happens when loading or after the open source nv then you have a point, even if it says "hardware", but by reporting it on the same bugzilla as the one mentioning "nvidia", it will be dismissed point blank.

I have had bugs dismissed just because I had a vmware or nvidia driver loaded, even if the bug was totally unrelated to those modules, and closed as invalid, no questions asked. I had to demonstrate that the bug reproduced without those closed source things and reopen. They could have asked whether I could reproduce the bug without those modules, but no, they closed it fast.

They should find a compromise, a method, of handling these situations. Users need these closed source components. Linux is not complete without it. Have a look, consider what the problem might be, forward the report to nvidia or what ever, collaborate a bit in resolving it....

- -- Cheers,
Carlos E. R.

Version: GnuPG v2.0.4-svn0 (GNU/Linux)

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups