Bug 577045

Summary: Sysinfo Display Info Driver field shows "Unknown" after installing Nvidia proprietary driver
Product: [openSUSE] openSUSE 11.3 Reporter: Roman Bysh <rb03884>
Component: KDE4 ApplicationsAssignee: E-mail List <kde-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium CC: ctrippe, rb03884
Version: Milestone 1   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Display Info PNG file

Description Roman Bysh 2010-02-04 15:58:49 UTC
Created attachment 340759 [details]
Display Info PNG file

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.1 Firefox/3.6

After installing the Nvidia proprietary driver followed by running the command:

sax2 -r -m 0=nvidia

init 5; exit

I started sysinfo --> Display Info --> Driver --> Unknown

It should show the Nvidia driver version number. The identical information can be found by running the following:

glxinfo | grep -i OpenGL

OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 8600 GTS/PCI/SSE2
OpenGL version string: 3.2.0 NVIDIA 190.53 

Reproducible: Always

Steps to Reproduce:
1. Install Nvidia proprietary drivers
2. Run:   sax2 -r -m 0=nvidia
3. Run:   sysinfo /
Actual Results:  
Display Info
  Vendor:  nVidia Corporation
  Model:  GeForce 8600 GTS
  Driver:  Unknown

Expected Results:  
Display Info
  Vendor:  nVidia Corporation
  Model:  GeForce 8600 GTS/PCI/SSE2
  Driver:  190.53
Comment 1 Christian Trippe 2010-02-04 18:54:38 UTC
Is there a reason, why you report the same bug twice?

*** This bug has been marked as a duplicate of bug 570200 ***
Comment 2 Roman Bysh 2010-02-04 19:24:35 UTC
My understanding was that if you are reviewing a new version of openSUSE, it was okay to submit a separate bug entry.

The first one applied to openSUSE 11.2. Since it had not been addressed in openSUSE 11.2. I noticed it again in openSUSE 11.3 Milestone 1 and the problem still persists.

So, what you are saying is that a tester can only create a single bug entry for more that one version of openSUSE? 

Please clarify as I'm still new to Bugzilla.


Roman
Comment 3 Christian Trippe 2010-02-04 19:30:30 UTC
(In reply to comment #2)
> My understanding was that if you are reviewing a new version of openSUSE, it
> was okay to submit a separate bug entry.
> 
> The first one applied to openSUSE 11.2. Since it had not been addressed in
> openSUSE 11.2. I noticed it again in openSUSE 11.3 Milestone 1 and the problem
> still persists.
> 
> So, what you are saying is that a tester can only create a single bug entry for
> more that one version of openSUSE? 

Yes, it would be better to change the product of the bug to the newer version with a comment like "Still reproducible with openSUSE XYZ."
Comment 4 Roman Bysh 2010-02-04 19:43:02 UTC
Okay. Thank you for pointing this out. Can we see this issue resolved when openSUSE 11.3 Milestone 2 is released?
Comment 5 Christian Trippe 2010-02-04 20:51:59 UTC
(In reply to comment #4)
> Okay. Thank you for pointing this out. Can we see this issue resolved when
> openSUSE 11.3 Milestone 2 is released?

I do only bug screening for KDE bugs on openSUSE so I cannot tell you for sure, but I doubt it, as there are much more critical bugs to be taken care of.
Comment 6 Roman Bysh 2010-02-05 18:48:40 UTC
I understand. And, I agree, we have more critical bugs to be addressed. However, this bug was not fixed for the entire version of openSUSE 11.2 including all milestones. 

Now, I'm seeing this happen again with a very new version. I thought we could "nip it in the bud" early.

The thing is that information missing from "sysinfo" is important for all users - new and old users. We also have people reviewing the distro for possible purchase not to mention magazine reviews.