[Bug 914665] New: proprietary nvidia drivers break flash-player plugins
http://bugzilla.novell.com/show_bug.cgi?id=914665 Bug ID: 914665 Summary: proprietary nvidia drivers break flash-player plugins Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: bnc-team-screening@forge.provo.novell.com Reporter: thejze@gmx.at QA Contact: sndirsch@suse.com Found By: --- Blocker: --- Created attachment 620793 --> http://bugzilla.novell.com/attachment.cgi?id=620793&action=edit output of: ~> firefox 2> tmp/nvidia_install_error.log Overview: On my desktop pc I use a Nvidia graphics card. When I added the nvidia community repository, the video driver was automatically changed to the driver system from that repo. After this change fash-player plugins did not work any more, with different symptoms. After switching back to the nouveau driver and rebooting fash-player plugins worked again. Hardware: ~> sudo hwinfo --gfxcard|grep Model Model: "nVidia GK107 [GeForce GTX 650]" Installed nvidia-packages: nvidia-uvm-gfxG03-kmp-desktop-340.65_k3.16.6_2-32.1.x86_64 x11-video-nvidiaG03-340.65-32.1.x86_64 nvidia-glG03-340.65-32.1.x86_64 conky-feature-nvidia-1.9.0-29.2.x86_64 nvidia-texture-tools-2.0.6-25.1.8.x86_64 nvidia-computeG03-340.65-32.1.x86_64 nvidia-gfxG03-kmp-desktop-340.65_k3.16.6_2-32.1.x86_64 from Nvidia Community Repository (Yast says "Hersteller obs://build.suse.de/home/sndirsch:drivers") Other Software: MozillaFirefox-35.0-9.1.x86_64 from OpenSuse Update Repository flash-player-11.2.202.438-2.25.1.x86_64 from OpenSuse Update-Non-Oss Repository pullin-flash-player-12.3-6.4.1.x86_64 from OpenSuse Update Repository flash-player-kde4-11.2.202.438-2.25.1.x86_64 from OpenSuse Update-Non-Oss Repository How to reproduce: 1) Start Firefox 2) Go to a site with flash-plugins e.g. youtube 3) The process hangs, but can be killed 4) start firefox -safe-mode from the command line to clean up the session The effect is reproducible until switching back to the nouveau driver and again to the nvidia driver. After that (rebooting of course) firefox behaves different: plugins are shown either as grey boxes or with an error message in it. The attachment shows the error log when firefox is started from the command line. Workaround: Replace the nvidia drivers by the nouveau driver and reboot. Flash-plugins run properly. The nvidia repository has to be deactivated to prevent automatic reinstallation upon the next call of the Yast software installation module. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=914665
--- Comment #1 from Thomas Hejze
http://bugzilla.novell.com/show_bug.cgi?id=914665
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=914665
Thomas Hejze
Is this still reproducable with release 346.35?
Yast proposes the packages with the label G03 in the names. For those I only find the release 340.76 in the repository. Packages with release 346.35 are only available for G04 series. I did not dare to overule Yast's package selection, because I thought that Yast does some sort of hardware detection and I do not know the difference between G03 and G04 series. Should I try the G04 packages or would I brick my Nvidia graphics card if I did so? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=914665
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=914665
--- Comment #5 from Stefan Dirsch
Should I try the G04 packages or would I brick my Nvidia graphics card if I did so?
Don't worry. Driver just bails out, if an unsupported GPU has been detected. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=914665
Thomas Hejze
(In reply to Thomas Hejze from comment #3)
Should I try the G04 packages or would I brick my Nvidia graphics card if I did so?
Don't worry. Driver just bails out, if an unsupported GPU has been detected.
I'm afraid, G04 packages with release 346.35 did not solve the problem. Same behaviour as with 340.65 (graphically, I did not check logfiles). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=914665
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=914665
--- Comment #8 from Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=914665
Thomas Hejze
Also please make sure that package libvdpau-va-gl is *not* installed
I did not find a package libvdpau-va-gl but libvdpau-va-gl1 from the distribution/oss repository. Do you mean that? Yast always wants to reinstall it, when I call "Software installieren oder löschen".
VDPAU_DRIVER environment variable is *not* set.
Could you tell me which file in /etc I have to edit, if I have to do it manually? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=914665
--- Comment #12 from Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=914665
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=914665
Thomas Hejze
Also please make sure that package libvdpau-va-gl is *not* installed and VDPAU_DRIVER environment variable is *not* set. Otherwise vdpau will be routed back to libva. Possible loop?
Installing libva-vdpau-driver together with the G04 package set did the job. libvdpau-va-gl1 was marked as taboo in Yast. Unsetting the VDPAU_DRIVER environment variable by hand was not necessary. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=914665
Thomas Hejze
participants (1)
-
bugzilla_noreply@novell.com