Bug 648718

First I would like to know, why it crashes. Please attach /var/log/Xorg.0.log.old right after the crash. Thanks.

Created attachment 396639 [details]
requested log files

I don't see any Xserver crash in the logfile. Please attach ~/.xsession-errors as well.

Created attachment 396646 [details]
xsession.errors file

noone said it was the xserver crashing... its plasma-desktop that crashes every time since that new nvidia driver came out. google results suggest that other people have the same problems with that driver on other linux flavours... I suggest getting the older driver back, which version was that again, nvidia-gfxG02-kmp-default-256.53_k2.6.34.0_12-15.1.i586

Are you using KDE 4.4 or have you updated to a newer release from the Build Service?

A guy reported the following in #suse on IRC earlier today. 

[17:53] <shodan45> plasma-workspace is crashing on me soon after login, I think I'm having this bug: https://bugs.kde.org/show_bug.cgi?id=251719
[17:53] <cb400f> downgrade nvidia blob
[17:53] <cb400f> I think.. at least a lot of people with kde 4.5 are whining about that
[17:55] <shodan45> err I'm using the regular kde provided by the standard 11.3 repos
[17:55] <shodan45> aka 4.4.4
[17:57] * shodan45 thinks somebody didn't test enough before pushing that nvidia driver public.... :(
[17:57] <cb400f> so you did install the driver?
[17:57] <shodan45> yep, last thing I did yesterday before shutting down

Maybe the info in the linked KDE bug report helps. Personally I'm too scared to upgrade nvidia and test it.

*** Bug 648071 has been marked as a duplicate of this bug. ***

In KDE 4.4 plasma works well with the driver 260.19.12

I confirm plasma-desktop crashes under KDE 4.5.X with 260.19.12 nvidia driver, while works in KDE 4.4.X. 

Moreover, also VirtualBox 3.2.8 crash with "Floating point exception".

I successfully reinstalled 256.53 driver with .run installer downloaded from nvidia web site:
http://www.nvidia.com/object/linux-display-ia32-256.53-driver.html

After, I discovered repository with the old driver:

http://anorien.warwick.ac.uk/mirrors/opensuse/nvidia/download.nvidia.com/opensuse/11.3/i586/

No problems with 4.4 here either. 64-bit, 11.3/kde 4.4, -desktop kernel. Seems the guy I talked to on IRC was wrong.

just fyi, w/

rpm -qa | egrep -i "virtualbox|kdebase4-runtime-4|nvidia-gfx|kernel-desktop-2"
 VirtualBox-3.2-3.2.10_66523_openSUSE113-1.x86_64
 kernel-desktop-2.6.34.7-0.4.1.x86_64
 nvidia-gfxG02-kmp-desktop-260.19.12_k2.6.34.0_12-22.1.x86_64
 kdebase4-runtime-4.5.2-7.3.x86_64

no problems of any kind, with either VB or KDE/Plasma

Just to comment, how I get ride of nvidia trouble during : 
a) nvidia update
b) kde upgrade ( version change 4.4.4 to 4.5x for example ) 

This morning after update, each time you try to open folder with picture you get crash etc ... 

Everything works if ONLY if you clear all previous temp data (usually found in /tmp or /var/tmp/) remove any kde-* related folder.

In this case : 
opensuse 11.2 2.6.31-14 / kde 4.4.4-3.7.2 / 32bits

No problems ( nvidia installed by installer ) seen under 
opensuse-factory 2.6.36-rc4 & kde-factory 4.5.2

(In reply to comment #10)
> No problems with 4.4 here either. 64-bit, 11.3/kde 4.4, -desktop kernel. Seems
> the guy I talked to on IRC was wrong.

Guy on IRC (shodan45) here - after removing & re-adding all the plasmoids I was using, I narrowed it down to "comic" causing the crash.

To reproduce, add a comic plasmoid to the desktop, then configure it to show a comic (I tried dilbert & xkcd). Crashes every time for me, even on a fresh user account.

Also, I'm on 32-bit. Otherwise, same setup as above.

this bug doesn't affect everyone, not even with the same software setup & similar hardware. i've had no problems with the latest nvidia driver using KDE 4.5.2 (factory repos). it seems to depend on the hardware used, but i couldn't figure out yet which hardware component triggers the problems. here's my system:

intel core2 duo @ 2.59 GHz, 4 GB RAM
openSUSE 11.3, KDE 4.5.2 (factory repo)
uname -a: Linux phani 2.6.36-rc8-34-desktop #1 SMP PREEMPT 2010-10-21 10:11:03 +0200 x86_64 x86_64 x86_64 GNU/Linux
card: nvidia 9400 GT (fairly recent, but cheap card; 1 GB memory, PCI-express)
driver: 260.19.12 (.run file from nvidia website)

i've seen one or two users on the forums who don't have problems; but then, those w/o problems rarely speak up.

Besides Mathias Homann, Antonio Guadagnin I'm the third one who confirms this bug.

I would be glad to provide any needed info about my system and this crash (if you would tell what exactly is needed).
Thanks.

I can confirm this issue with KDE 4.5 and nvidia driver 260.19.12 from the nvidia-repo.
It is working with 260.19.12 installed via .run-file.
So this seems related to the nvidia package from the repo.

https://bugs.kde.org/show_bug.cgi?id=251719#c1
bug not reproduced, if deleted any clock widgets.

Application: plasma-desktop (0.3)
KDE Platform Version: 4.5.2 (KDE 4.5.2)
Qt Version: 4.7.0
Operating System: Linux 2.6.34.7-0.4-pae i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
Updating the NVIDIA driver in openSUSE 11.3 KDE 4.5.2

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma-Arbeitsfläche (kdeinit4), signal: Floating point exception
[KCrash Handler]
#7  0xb771010a in enter.8103 () from /lib/ld-linux.so.2
#8  0xb7710771 in do_lookup_x () from /lib/ld-linux.so.2
#9  0xb7710b49 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2
#10 0xb771245b in _dl_relocate_object () from /lib/ld-linux.so.2
#11 0xb771982e in dl_open_worker () from /lib/ld-linux.so.2
#12 0xb771550f in _dl_catch_error () from /lib/ld-linux.so.2
#13 0xb77192e6 in _dl_open () from /lib/ld-linux.so.2
#14 0xb5d1bbdd in dlopen_doit () from /lib/libdl.so.2
#15 0xb771550f in _dl_catch_error () from /lib/ld-linux.so.2
#16 0xb5d1c342 in _dlerror_run () from /lib/libdl.so.2
#17 0xb5d1bca7 in dlopen@@GLIBC_2.1 () from /lib/libdl.so.2
#18 0xb6da43e5 in QLibraryPrivate::load_sys (this=0x87e5450) at plugin/qlibrary_unix.cpp:205
#19 0xb6d9e864 in QLibraryPrivate::load (this=0x87e5450) at plugin/qlibrary.cpp:484
#20 0xb6d9e948 in QLibraryPrivate::loadPlugin (this=0x87e5450) at plugin/qlibrary.cpp:516
#21 0xb6d98883 in QPluginLoader::load (this=0xbfd34f9c) at plugin/qpluginloader.cpp:227
#22 0xb706992f in KPluginLoader::load() () from /usr/lib/libkdecore.so.5
#23 0xb7069df5 in KPluginLoader::KPluginLoader(KService const&, KComponentData const&, QObject*) () from /usr/lib/libkdecore.so.5
#24 0xb4d66a5a in Plasma::DataEngineManager::loadEngine (this=0x8578958, name=...) at /usr/src/debug/kdelibs-4.5.2/plasma/dataenginemanager.cpp:137
#25 0xb4d9dc55 in Plasma::DataEngineConsumer::dataEngine (this=0x8516fd8, name=...) at /usr/src/debug/kdelibs-4.5.2/plasma/private/dataengineconsumer.cpp:100
#26 0xb4d22d97 in Plasma::Applet::dataEngine (this=0x8512e38, name=...) at /usr/src/debug/kdelibs-4.5.2/plasma/applet.cpp:663
#27 0xa9944f62 in ClockApplet::init() () from /usr/lib/libplasmaclock.so.4
#28 0xa9a27a3e in ?? () from /usr/lib/kde4/plasma_applet_dig_clock.so
#29 0xb4d4a92f in Plasma::ContainmentPrivate::initApplets (this=0x82d6ae8) at /usr/src/debug/kdelibs-4.5.2/plasma/containment.cpp:474
#30 0xb4d5ce46 in Plasma::CoronaPrivate::importLayout (this=0x81b1050, conf=..., mergeConfig=false) at /usr/src/debug/kdelibs-4.5.2/plasma/corona.cpp:525
#31 0xb4d5db95 in Plasma::Corona::loadLayout (this=0x8136020, configName=...) at /usr/src/debug/kdelibs-4.5.2/plasma/corona.cpp:460
#32 0xb4d5dc74 in Plasma::Corona::initializeLayout (this=0x8136020, configName=...) at /usr/src/debug/kdelibs-4.5.2/plasma/corona.cpp:363
#33 0xb166419a in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#34 0xb166785e in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#35 0xb1670409 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#36 0xb6dba96d in QMetaObject::metacall (object=0x80daf00, cl=QMetaObject::InvokeMetaMethod, idx=42, argv=0x81951a0) at kernel/qmetaobject.cpp:237
#37 0xb6dc5465 in QMetaCallEvent::placeMetaCall (this=0x81972f8, object=0x80daf00) at kernel/qobject.cpp:534
#38 0xb6dc969f in QObject::event (this=0x80daf00, e=0x81972f8) at kernel/qobject.cpp:1211
#39 0xb6db471a in QCoreApplication::event (this=0x80daf00, e=0x81972f8) at kernel/qcoreapplication.cpp:1561
#40 0xb62b68dd in QApplication::event (this=0x80daf00, e=0x81972f8) at kernel/qapplication.cpp:2439
#41 0xb62b41a4 in QApplicationPrivate::notify_helper (this=0x80e43a8, receiver=0x80daf00, e=0x81972f8) at kernel/qapplication.cpp:4396
#42 0xb62bcdd7 in QApplication::notify (this=0x80daf00, receiver=0x80daf00, e=0x81972f8) at kernel/qapplication.cpp:3798
#43 0xb73fa9c1 in KApplication::notify (this=0x80daf00, receiver=0x80daf00, event=0x81972f8) at /usr/src/debug/kdelibs-4.5.2/kdeui/kernel/kapplication.cpp:310
#44 0xb6db412e in QCoreApplication::notifyInternal (this=0x80daf00, receiver=0x80daf00, event=0x81972f8) at kernel/qcoreapplication.cpp:732
#45 0xb6db7e6c in sendEvent (receiver=0x0, event_type=0, data=0x80572a0) at kernel/qcoreapplication.h:215
#46 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x80572a0) at kernel/qcoreapplication.cpp:1373
#47 0xb6db7fbc in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#48 0xb6de26d4 in sendPostedEvents (s=0x80e6710) at kernel/qcoreapplication.h:220
#49 postEventSourceDispatch (s=0x80e6710) at kernel/qeventdispatcher_glib.cpp:277
#50 0xb5af0b49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#51 0xb5af1350 in ?? () from /usr/lib/libglib-2.0.so.0
#52 0xb5af160e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#53 0xb6de285b in QEventDispatcherGlib::processEvents (this=0x80e09c0, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#54 0xb636919a in QGuiEventDispatcherGlib::processEvents (this=0x80e09c0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#55 0xb6db340d in QEventLoop::processEvents (this=0xbfd35f14, flags=...) at kernel/qeventloop.cpp:149
#56 0xb6db3639 in QEventLoop::exec (this=0xbfd35f14, flags=...) at kernel/qeventloop.cpp:201
#57 0xb6db8090 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#58 0xb62b1ed4 in QApplication::exec () at kernel/qapplication.cpp:3672
#59 0xb165d06d in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#60 0x0804e441 in _start ()

Possible duplicates by query: bug 255221, bug 255203, bug 255090, bug 255062, bug 251719.

Reported using DrKonqi

(In reply to comment #16)
> I can confirm this issue with KDE 4.5 and nvidia driver 260.19.12 from the
> nvidia-repo.
> It is working with 260.19.12 installed via .run-file.
> So this seems related to the nvidia package from the repo.

I tried this way unsuccessfully, therefore I think this bug isn't related to the package.

is there still any info needed, then please elaborate on WHAT is needed.

I updated the kernel, glibc and some other stuff some time ago. Since there I have issues with plasma. I updated the nvidia driver from the repo afterwards. So I think it has nothing to do with the nvidia repo.

I'm also using KDE 4.5

Sorry, I forgot: I'm using openSUSE 11.2

@Mathias Rabe: Maybe you have a different bug?

I'm quite sure that it's related to the nvidia driver in my case, as this was the only package I upgraded before it stopped working.

Kernel: PAE 2.6.34.7-0.5 (and -0.4) 32bit
KDE: 4.5.2 from the build service
nVidia-Driver: 260.90.12 from the official repo
graphics hardware (according to lspci): 01:00.0 VGA compatible controller: nVidia Corporation G94 [GeForce 9600 GT] (rev a1)

Has the situation changed when using new version of NVIDIA driver: nvidia-gfxG02-kmp-desktop-260.19.12_k2.6.34.0_12-24.1.x86_64?

Upgrading to 260.19.12_k2.6.34.0_12-24.1 did not work for me.

Thank you for saving me 30 minutes of my time. :)
Pity, it hasn't been fixed. :(

Nothing has changed in nvidia-gfxG02 260.19.12 RPMs. The only real change in the 11.3 repo was the introduction of nvidia-gfx 96.43.19 RPMs, since this legacy driver now support xorg-server 1.8.

update to 260.19.21 hasn't helped

update to 260.19.29 and X.org Server 1.9.3 hans't helped

As mentionned in https://bugs.kde.org/show_bug.cgi?id=251719
Most of the people having trouble are using openSUSE with 32bits configuration.

Is there's something special in our rpm that make them bad.
I've asked in the kde bug thread to people with opensuse to try the nvidia installer, just to be sure.

But I saw here people having trouble with x86_64 too. 
I couldn't reproduce that crash with my quadro FX-360M under factory 11.4 x86-64 ( used of the nvidia installer )

Nor with a Geforce 8600GT pci-e under 11.2 32bits and kde 4.4.4

Whatever the trouble is in KDE or nvidia things, we got a trouble, as no other distributions seems to be sensible to that crash.

i can confirm, that bug hit me as well...

i reported upstream because of kde bug report tool, here it is:

https://bugs.kde.org/show_bug.cgi?id=261987

(includes a proper strace as well)

nVidia drivers 260.19.29 work fine in openSUSE 11.4 M5

I just updated to 260.19.29 in 11.3; it still doesn't work.

Has anyone solved the problem after a fresh install?

Mine was gone after reinstall glibc. Now everything is working great and fast. (64bits, 4.6rc2, nvidia installer, kernel head)

Ramon, it has very few report under 64bits.
98% of the reports also counted in the kde upstream one are about 32bits.

(In reply to comment #33)
> I just updated to 260.19.29 in 11.3; it still doesn't work.

Same here, doesn't work with 260.19.29, 11.3 (32 bits). Using KDE 4.6 RC2. (Although it first stopped working with KDE 4.5.x after the nvidia update to 260.xx.xx) 

In KDE 4.5 crash clocks (and therefore you can't even log in with them). Also at least Ktorrent and Amarok, crash. 

In KDE 4.6 clocks and Amarok still crash. Ktorrent is now fine. But Krunner crashes (and keeps re-spawning and crashing), and so does the Search and Launch Activity when given input to search.

As a side note, in KDE 4.6 (at least Beta2 - RC2) KWin freezes quite hard a few seconds after login (and then effects are automatically deactivated).

Opensuse11.3, 32bit
GF6600 (260.19.29)
kernel 2.6.37
Plasma-desktop in kde 4.6 and 4.5 crash.

Why not just provide 256.xx.xx alongside with  260.xx.xx in the Nvidia OpenSUSE repository? Given the huge amount of people being affected by this bug it seems like the sane thing to do...

256.xx.xx not supported by new kernel (2.6.37) for upcoming release 11.4...

(In reply to comment #40)
> 256.xx.xx not supported by new kernel (2.6.37) for upcoming release 11.4...

Well this is about 11.3...

Yes, I have this problem too.

32bit opensuse
Nvidia graphics
KDE 4.5.
I5

Unusable with the latest 260 Nvidia driver KDE starts but screen is blank except for krunner messages that keep displaying for ever. Reverting to Nvidia 256... and then all's well.

Hi,
I had the same problem, but I was able to sort it out with this workaround:

1. in the KDE system setting (systemsettings) go to the Desktop Effects
2. go to Advanced setting. there is OpenGL setting.
3. switch the texture filtering to the "Trilinear".
4. save it and restart the KDE.

- now it should works ;-)

KDE 4.5.5
Nvidia - from Nvidia repository 260.19.12

Martin

(In reply to comment #43)
> Hi,
> I had the same problem, but I was able to sort it out with this workaround:
> 
> 1. in the KDE system setting (systemsettings) go to the Desktop Effects
> 2. go to Advanced setting. there is OpenGL setting.
> 3. switch the texture filtering to the "Trilinear".
> 4. save it and restart the KDE.
> 
> - now it should works ;-)
> 
> KDE 4.5.5
> Nvidia - from Nvidia repository 260.19.12
> 
> Martin

Hello Martin. 

I cannot find "texture filtering" in the Advanced Settings. 
There is:
- Compositing Type
- Keep Window Thumbnails
- Scale Method
- OpenGL Mode
And none of these have the option "Trilinear". Could you post a screenshot somewhere?

I am using KDE(In reply to comment #44)
> (In reply to comment #43)
> > Hi,
> > I had the same problem, but I was able to sort it out with this workaround:
> > 
> > 1. in the KDE system setting (systemsettings) go to the Desktop Effects
> > 2. go to Advanced setting. there is OpenGL setting.
> > 3. switch the texture filtering to the "Trilinear".
> > 4. save it and restart the KDE.
> > 
> > - now it should works ;-)
> > 
> > KDE 4.5.5
> > Nvidia - from Nvidia repository 260.19.12
> > 
> > Martin
> 
> Hello Martin. 
> 
> I cannot find "texture filtering" in the Advanced Settings. 
> There is:
> - Compositing Type
> - Keep Window Thumbnails
> - Scale Method
> - OpenGL Mode
> And none of these have the option "Trilinear". Could you post a screenshot
> somewhere?

I am using KDE 4.6 RC2 by the way (and not KDE 4.5.x)

Created attachment 408623 [details]
advence desktop setting for Nvidia in KDE 4.5

(In reply to comment #45)
> I am using KDE(In reply to comment #44)
> > (In reply to comment #43)
> > > Hi,
> > > I had the same problem, but I was able to sort it out with this workaround:
> > > 
> > > 1. in the KDE system setting (systemsettings) go to the Desktop Effects
> > > 2. go to Advanced setting. there is OpenGL setting.
> > > 3. switch the texture filtering to the "Trilinear".
> > > 4. save it and restart the KDE.
> > > 
> > > - now it should works ;-)
> > > 
> > > KDE 4.5.5
> > > Nvidia - from Nvidia repository 260.19.12
> > > 
> > > Martin
> > 
> > Hello Martin. 
> > 
> > I cannot find "texture filtering" in the Advanced Settings. 
> > There is:
> > - Compositing Type
> > - Keep Window Thumbnails
> > - Scale Method
> > - OpenGL Mode
> > And none of these have the option "Trilinear". Could you post a screenshot
> > somewhere?
It is in the OpenGL options  field : Texture filter: - Trilinear (best quality)

When I setup this options plasma-desktop started work...  

Martin

> 
> I am using KDE 4.6 RC2 by the way (and not KDE 4.5.x)

(In reply to comment #47)
> (In reply to comment #45)
> > I am using KDE(In reply to comment #44)
> > > (In reply to comment #43)
> > > > Hi,
> > > > I had the same problem, but I was able to sort it out with this workaround:
> > > > 
> > > > 1. in the KDE system setting (systemsettings) go to the Desktop Effects
> > > > 2. go to Advanced setting. there is OpenGL setting.
> > > > 3. switch the texture filtering to the "Trilinear".
> > > > 4. save it and restart the KDE.
> > > > 
> > > > - now it should works ;-)
> > > > 
> > > > KDE 4.5.5
> > > > Nvidia - from Nvidia repository 260.19.12
> > > > 
> > > > Martin
> > > 
> > > Hello Martin. 
> > > 
> > > I cannot find "texture filtering" in the Advanced Settings. 
> > > There is:
> > > - Compositing Type
> > > - Keep Window Thumbnails
> > > - Scale Method
> > > - OpenGL Mode
> > > And none of these have the option "Trilinear". Could you post a screenshot
> > > somewhere?
> It is in the OpenGL options  field : Texture filter: - Trilinear (best quality)
> 
> When I setup this options plasma-desktop started work...  
> 
> Martin
> 
> > 
> > I am using KDE 4.6 RC2 by the way (and not KDE 4.5.x)


Apparently name got changed in 4.6
I think it's "scale method" now. 

I tried all 3 options, crisp, smooth and accurate. None solved it.

(In reply to comment #43)
> Hi,
> I had the same problem, but I was able to sort it out with this workaround:
> 
> 1. in the KDE system setting (systemsettings) go to the Desktop Effects
> 2. go to Advanced setting. there is OpenGL setting.
> 3. switch the texture filtering to the "Trilinear".
> 4. save it and restart the KDE.
> 
> - now it should works ;-)
> 
> KDE 4.5.5
> Nvidia - from Nvidia repository 260.19.12
> 
> Martin

I tested this workaround and NOT WORK: "Floating point exception"

Hi,
could someone who is affected and the following applies(!)

has a FPE in  /lib/ld-linux.so.2
uses openSUSE (guess that's a given)
uses KDE4.5 or higher
uses Nvidia binary driver 260.19.12+
uses a i586 kernel/userland
tried the nvidia binary installer

please try with a vanilla kernel + nvidia binary installer? opensuse provides kernel-vanilla for this.
This is just to rule out any kernel patches, it might still crash further on.

I have installed 11.3 on four machines, a dual core x64 MSI Wind and an Acer Aspire One, an Athlon 3200 XP, nvidia 6200 (also tried with 7600) AGP, self build and a Compaq Intel based 32 bit, nvidia 6200 PCI. (this is a friend's machine, so only tried once)

The MSI and AAO have always been perfectly behaved. Both are running factory upgraded 11.3, KDE 4.6

The Compaq "floating point"ed early in this saga, so I reverted to stock 11.3

The Athlon, fully upgraded, openSUSE, nvidia, KDE, (all RPM or installer) was perfectly happy all the way up to 4.5.95

So, getting the floating exception on 4.6.0 came as a bit of a surprise

I've just seen a report that this bug is present on 11.4 M6

While we all know that between releases we are on our own, I found it close to impossible to downgrade the nvidia driver as legacy drivers only work (or not) the hard way. Further, the 11.4 news, doesnn't look great.

The lack of any real support for Plan B (e.g., easy nvidia downgrade) could reduce the number of interested users willing to participate in testing and bug reporting. This would be bad news, practically and reputationally.

I've been with the distro since 1999 and thought we'd moved beyond the pain of _buying_ an upgrade only to discover printing didn't work anymore (9.1 since you ask)

I find the lack of co-ordinated information dispiriting, bordering on disdainful. Over the years I've diligently tried to contribute by bug reporting and offering countering views to some of the rabid FUD spewed out about both KDE and openSUSE. I've bought nvidia exclusively.

Funnily enough, my resolve going forward is in need of some attention.

It would be massively helpful if someone representing openSUSE, KDE and nvidia could provide a confidence building report to us all. I don't appear to be on my own in feeling that we re being treated like mushrooms.

Gerry we are sorry about this, it is just so hard to tackle, it's been bouncing from bugs.kde.org to nvforums and here, most seem determined it's a suse issue and I am looking into this but as a volounteer and not owning a nvidia system this is tough to do. It seems to have stayed under the radar for way too long =/

Also the somewhat exact problem case doesn't make this much easier, that's why I am trying to nail down where the problem is (that is why I was asking for testing with vanilla kernel)

We don't provide the nvidia repo, nvidia does btw so we have no direct access, I don't even know if we have someone to talk to Nvidia directly, except maybe Stefan Dirsch.


It seems to be crashing loading a shared library, I tried asking around for a good way to catch the library that causes this but noone had any nonintrusive ideas =(

I can confirm this bug on my system:

openSUSE 11.3
Kernel 2.6.38-rc2.2.1.i586
KDE 4.6.0
NVIDIA x86-260.16.36

To stop the crashes, it isn't enough to switch the driver back to Nouveau, but I have to manually remove the NVIDIA driver with "./NVIDIA... --uninstall", otherwise plasma continues to crash, even when using Nouveau.

> It seems to have stayed under the radar for way too long
> =/

I don't understand this. 

The bug report on bugs.kde.org is from mid September, when 260.xx.xx was provided in nvidia's repositories. At that time there were tons of people affected and numerous reports. The guys at #opensuse-kde on freenode were certainly well aware of it. Bug was closed as Resolved - Upstream and one would expect some sort of down/upstream communication. Not to mention it was reported here too, and linked to bugs.kde.org. How can something as massive as this stay under the radar?


Right now it is the 43th bug with most duplicate reports at bugs.kde.org!
https://bugs.kde.org/duplicates.cgi

This is pretty impressive for a bug that is distro specific.
It gets worst. Most bugs on this list, 
  - haven't had any duplicate reports in a long time
  - are already fixed
Out of this list, this is the bug with more duplicates submitted in the past week and in the past month!

I have noticed this bug cropping up from time to time on #opensuse-kde, but lacking an nvidia card and knowing there was often troubles with the binary nvidia driver and plasma when there was a new kde version / nvidia driver version I assumed it would shake out itself, as it often did.

The opensuse-kde team is spread very thin on paid developers, if they aren't affected by the bug and are swamped with work this might just not be noticed yeah.

And yes it is quite embarassing.


So did someone try the vanilla kernel?

Karsten 

Thank you for replying.

Would a 6200 PCI-E (bought by mistake...) be of any use?

If so, email me so I can work out how to get it to you

Would it be possible to provide a guide to downgrading the driver and persuade nvidia to include this option on their opensuse the easy way section?

I lack the knowledge of tracking this down thoroughly, so thanks for the offer but I can't make good use of it.

Until then you can only follow the 'Hard way from the openSUSE wiki:
http://en.opensuse.org/SDB:NVIDIA_the_hard_way
And use this download instead of the most recent one:
http://www.nvidia.com/object/linux-display-ia32-256.53-driver.html
This is the most uptodate 256 version I could find, it also is the 32bit version, as 64bit seems unaffected (or it is another issue)

I'll look into adding some warning regarding KDE4 and Nvidia repo into the wiki, but I doubt this will be read =/

Stefan is there a way we can ask Nvidia to keep 256 for now in the Nvidia repos?

(In reply to comment #57)
> Stefan is there a way we can ask Nvidia to keep 256 for now in the Nvidia
> repos?

No, this won't work.

to Stefan

I'm really concerned by the bug hitting everyone with the following configuration
A nvidia Geforce with 260xx drivers series (openSUSE rpm drivers, or nvidia .run installer)
A openSUSE 11.3 32bits (that's important, it's doesn't crash under 64bits)
-> perharps it's the same with 11.4 32bits
And kde 4.5x and more 4.6


The hp touchscreen we have at the fosdem booth has the symptom, so it's really easy to reproduce even in Nürnberg, or Prada, I don't know where it is stored actually.
You just have to install the 260.19.36 drivers in the /home/geeko/Download folders and you will get a lot of floating point exception.

I know how bad or hard it can be to fix those type of crap. But we must address that in the quickest time frame. Otherwise it's will just be unaffordable support both for kde, and us ... Thanks to have updated the Priority to P1

Perhaps the next 270.18 beta driver already contain a fix (but api change too etc see the changelog for that) I didn't have the time during the fosdem to test it.

After tomorrow I will have a nvidia ion pc where I will be able to trace all of what we can. I will start to install it under 11.4/factory and kde 4.6 and the nvidia drivers (.run installer) and report back what's happen

While crawling through nvnews forums (which is what nvidia considers their bugtracker ...) it seems 270.18 doesn't help either, I can't find it anymore as their search is laughable, but it's on the bko bugreport as well: https://bugs.kde.org/show_bug.cgi?id=251719#c140

https://bugs.kde.org/show_bug.cgi?id=251719#c12 has a backtrace which seems to point to the problem rather well - there is a division by zero because the enter() function gets a zero size passed. I don't know where from or why though.

And the enter() function is in the dynamic loader, so this is glibc/ld.so problem presumably, although the nvidia .so may be broken too.

I'll set up a demo machine and take it to our toolchain people next week.

Hello,
I just want to confirm, that this bug seems to affect 32-bit systems only. I had the plasma crash after login since the 260 nvidia driver release. Therefore I downgraded to 256 version. At the last weekend I did an architecture upgrade (no fresh install) from 32 to 64 bit and ... now it works with the 260 driver!

My system:
- Laptop HP Pavilion dv7
- openSUSE 11.3 (desktop kernel) with KDE 4.5
- Nvidia 9600M

Unfortunately I have a 2nd affected laptop (same software configuration) with a Nvidia 6800 but with an older 32-bit CPU. So this bug is still attending me...

regards
endym

I think this bug _may_ affect more than KDE. 

For some time now mplayer crashes on me with many wmv's. 
"MPlayer interrupted by signal 11 in module: init_video_codec"

However it works if you use:
"strace mplayer video"

This is the exact same workaround that many of us have been using to run amarok.

I'm just pushing some informations given by users


> > Ditmar Unger <ditmar@...> writes:

> > 
> > 
>> >> ich habe gerade vlc auf die Version 1.1.7 gehoben und egal, ob es das Paket 
>> >> von Videolan oder das von packman ist (inkl. Löschen aller config-Dateien), 
>> >> vlc startet unter OpenSuSE 11.3, 32 bit wg. einer fpe nicht mehr.

	Dear Bruno,
	I'm not on the list; is sending a mail to you O.K.?

Seem to be related to

https://bugzilla.novell.com/show_bug.cgi?id=648718
&
https://bugs.kde.org/show_bug.cgi?id=251719

Opensuse 11.3 32bits seems to be your case, 
	yes

Did you use nvidia drivers if yes
	yes, version 260.19.29

Try to start vlc with gdb or strace : if that works it's definitively related.
	yes: strace vlc >/tmp/2011-02-20_strace_vlc.txt 2>&1
	works nicely; fpe occurds when stopping vlc
	log is in the attachment

So two solution : please add your case on the bugzilla.novell.com if you can 
	could you do that for me - thanks a lot! Can you then send me the link to follow the discussion?

describing your hardware 
	Athlon 4850e, two nvidia PCIe graphic cards (dual-seat configuration):
	02:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 7100 GS] (rev a1) (prog-if 00 [VGA controller])
        Kernel driver in use: nvidia
	04:00.0 VGA compatible controller: nVidia Corporation Device 0de1 (rev a1 
(prog-if 00 [VGA controller])
        Kernel driver in use: nvidia

and
zypper lr -d output. (Thx for doing that)
	O.K., see 2nd attachment

Your alternative solution : downgrade the drivers to the latest 253. one
	thanks; I did not do that yet; vlc-1.1.5 did work until the update without any other change of configuration
	but I did not find vlc-1.1.5 after a short google search.


	Thanks for your help and regards,
	Ditmar.




2011-02-20_strace_vlc.txt

execve("/usr/bin/vlc", ["vlc"], [/* 87 vars */]) = 0
brk(0)                                  = 0x804d000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb776d000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=103341, ...}) = 0
mmap2(NULL, 103341, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7753000
close(3)                                = 0
open("/usr/lib/libvlc.so.5", O_RDONLY)  = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\\\0\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=108568, ...}) = 0
mmap2(NULL, 111304, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7737000
fadvise64(3, 0, 111304, POSIX_FADV_WILLNEED) = 0
mmap2(0xb7751000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19) = 0xb7751000
close(3)                                = 0
....


Can we be sure that one is not a blocker 11.4 in 32bits.

I can confirm this issue on a very lot of computer and its a blocker for 11.4 in my opinion.

A lot of users wants to use the closed source nvidia driver, and in case its working on other distributions they will switch if it wont work.

Nobody can work with a black screen...

has _anyone_ confirmed the problem on 11.4? I won't make an 11.3 bug that's _possibly_ also happening on 11.4 a ship stopper.

The only report I've seen for 11.4 was:
https://bugs.kde.org/show_bug.cgi?id=251719#c154
https://bugs.kde.org/show_bug.cgi?id=251719#c157

Donn says he emailed openSuSE-Factory. Maybe contact him?

the amarok crash is independent - and reproducible without NV afaik.

(In reply to comment #68)
in 11.4 260.19 + KDE 4.6 work fine
see comment #32
https://bugzilla.novell.com/show_bug.cgi?id=648718#c32

Is this a 64bit or a 32bit system?

32bit

I upgrade to 11.4rc1 32bit and 270.18 beta drivers. Plasma-desktop still not working.

(In reply to comment #70)
> the amarok crash is independent - and reproducible without NV afaik.

Hi Stephan, 

I'm not sure what you mean by this. The NV update definitely causes amarok to crash. This as been confirmed and is well documented. You can find numerous amarok crash reports marked as duplicate of the NV bug report. As an example, here's just a few: 
https://bugs.kde.org/show_bug.cgi?id=253055
https://bugs.kde.org/show_bug.cgi?id=255249
https://bugs.kde.org/show_bug.cgi?id=255479
https://bugs.kde.org/show_bug.cgi?id=255490
As usual with crashes caused by the NV problem, the backtraces exhibit the usual "Floating point exception", and running the app with strace is an effective workaround. 

Regarding the specific case of Donn's bug, he doesn't have a lot of info that thread, not sure if he posted one of the duplicate reports. But he does mention at least that the "strace" workaround does the trick, and he seems to be convinced it is the same bug. 

So of course it could be something else... just not sure why you think it is.

I second Andrey Karepin's comment. Plasma and Amarok work properly in openSUSE 11.4 RC1 (x86) with NVIDIA drivers ver. 260.19.36.

OS installation method: local install from KDE Live CD

Driver installation method: 
1) get sources from X11:Drivers:Video OBS project using 'osc' program (OBS account is required)
2) build RPMs both for x11-video-nvidiaG02 and nvidia-gfxG02 locally using 'rpmbuild -bb <PACKAGENAME>.spec'
3) install newly created RPMs: x11-video-nvidiaG02-<VERSION>.i586.rpm and nvidia-gfxG02-kmp-<KERNEL_FLAVOR>-<VERSION>.i586.rpm

Some extra info (FWIW):

$ rpm -qa | grep nvidia
nvidia-gfxG02-kmp-default-260.19.36_k2.6.37.0_20-1.i586
x11-video-nvidiaG02-260.19.36-1.i586

$ cat /etc/SuSE-release
openSUSE 11.4 RC 1 (i586)
VERSION = 11.4
CODENAME = Celadon

$ uname -a
Linux linux-2d0f.site 2.6.37-20-default #1 SMP 2011-01-22 00:41:44 +0100 i686 i686 i386 GNU/Linux

$ lsmod | grep nvidia
nvidia               9387956  41 
i2c_core               27479  3 nvidia,i2c_i801,videodev

$ lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8400M GS] (rev a1)

I can confirm this bug

after dist-upgrade from 11.2 to 11.3, I had to downgrade KDE45 to the distro version 4.4

since vlc didn't work either, I investegated some time in this issue and found this ticket.

With downgrade of the nvidia driver to 256.53, both work again KDE46 and vlc

why don't you downgrade the official NVIDIA driver rpm to this version until you find the bug?

Yes, amarok crashes by run, but amarok not work and use driver nouveau, Plasa-desktop work.

Okay, I have a machine available that reproduces this one with amarok.
The FPE in ld-linux.so is because the register ($esi) is zero:

000090f0 <enter.8102>:
    90f0:       55                      push   %ebp
    90f1:       31 d2                   xor    %edx,%edx
    90f3:       57                      push   %edi
    90f4:       56                      push   %esi
    90f5:       83 ec 08                sub    $0x8,%esp
    90f8:       8b 74 24 18             mov    0x18(%esp),%esi
    90fc:       89 04 24                mov    %eax,(%esp)
    90ff:       8b 44 24 1c             mov    0x1c(%esp),%eax
    9103:       89 4c 24 04             mov    %ecx,0x4(%esp)
    9107:       8d 6e fe                lea    -0x2(%esi),%ebp
    910a:       f7 f6                   div    %esi  <<<<<< FPE

Looking at the source, this can't happen.  It's the size parameter which
starts from 31, and then only increases to next prime numbers.  Indeed,
if running under gdb or valgrind, the FPE doesn't happen, and the first call
to enter.8102 (coinciding with the point where the crash would normally happen)
has this parameter be set to 61, which indeed is the next prime number
_dl_higher_prime_number would return for 31.

So, something between calculating that next prime number and this routine
is going fishy.  As I have traced the source of the invalid zero somewhat
in a core file (the zero is already in the argument stack slot, and on the caller side in a register where debuginfo isn't sufficient to trace it back
further), I would speculate that something clobbers the stack.  I can't yet
rule out that something clobbers registers, though.

I install new beta driver from ftp://download.nvidia.com/XFree86/Linux-x86/270.29/ and now plasma work!

I can confirm this driver works on Opensuse 11.3 - 32bit.

I also can confirm nvidia 270.29 beta driver work on openSUSE 11.3 32 bit with KDE 4.6.0

That would be very good, because despite a reproducing machine I can't get
near the root cause of this problem.  Any sort of timing differences makes
the error go away, so I can't observe it under controlled circumstances :-/

This sounds highly promising! So when can I turn my NVIDIA repo back on?

Many thanks to the testers with more time and courage than I!

Update to 270.29 didn't work here, KDE 4.6.0 not working.

back to 256.53 here :'-(

(In reply to comment #85)
> Update to 270.29 didn't work here, KDE 4.6.0 not working.
> 
> back to 256.53 here :'-(

+ 1

same behavior on my system (oSS11.3 KDE4.6 + +32 Bit)
Nvidia Driver: 270.29 Beta does not work =
Nvidia Driver: 256.53 = works!

Too bad :-/  If anybody can give me a system where this happens even under
strace (or better yet, gdb) I can take a look again.

It isn't a problem of the rpm package, it also crashes with the nvidia insitaller, the only issue from suse is that you use that broken version from nvidia to create the rpms.

Why not stay with 256.53 or maybe both versions. It also seems to be an issue with different graphic cards. (mine: GeForce Go 7300)

i agree to workaround having 256.53 together with the latest, but i can't understand yet why only suse is affected by this bug, other distros are just fine

Lubos on comment #61 and #62 said that it could be glibc problem. And also on KDE bugzilla bug no 251719, the first comment said about the same think. I wonder if by using the latest glibc will solve the problem.

Lubos on comment #61 and #62 said that it could be glibc problem. And also on KDE bugzilla bug no 251719, the first comment said about the same think. I wonder if by using the latest glibc will solve the problem.

See my comment #79.  The div-by-zero is in ld.so, no doubt.  But the code
therein is okay, so something else must be clobbering stack or registers
asynchronously.  That's probably also why I couldn't reproduce it with any
self-built glibc with some debugging code, or under gdb or strace.  I.e.
when using a different glibc the fault may indeed go away, but it will merely
be hidden, not solved.  This heisenbug property would also explain why only
openSUSE seems to have the problem, its glibc happens to be unfortunate
enough to have just the right code layout to trigger the bug :-/

I googled this workarounds for this bug:
compile glibc without --enable-omitfp (USE="-glibc-omitfp")
or start "broken soft" with other libGL:
LD_PRELOAD=/usr/lib/opengl/xorg-x11/lib/libGL.so.1 ccsm
or launch with strace:
strace gimp &>/dev/null

On the -factory mailinglist it is claimed the problem is solved with Nvidia beta blob 270.29. But apparently 270.30 is 
out too.

http://lists.opensuse.org/opensuse-factory/2011-03/msg00028.html

I wonder if anyone here is able/willing to test and verify - preferably with 11.4 systems of course :-)

(In reply to comment #94)
i update driver to 270.30 in 11.3, after update glibc, plasma-desktop and amarok work fine

(In reply to comment #94)
> I wonder if anyone here is able/willing to test and verify - preferably with
> 11.4 systems of course :-)

After updating the driver in 11.3 to version 270.30 the bug disappeared.

I couldn't get any useful results on 11.4, because the bug is not reproducible on my hardware with 11.4-RC1 (probably upgraded to RC2 via YaST, I cannot say for sure) + KDE 4.6 + NVIDIA driver ver. 260.19.36.

(In reply to comment #94)
I test 270.30 to openSUSE 11.4: plasma-desktop and amarok work fine.

I just tested:

11.4, 32-bit
KDE 4.6.0
Nvidia blob 260.19.36 (KMP from the Nvidia repo)

And for me Plasma and Amarok (both in completely default configuration) were working fine.

Can anyone else confirm? 

It'd be nice to be able to get rid of all the warnings in the wiki etc., if the problem is actually solved now - even with 260 series.

Plasma and amaroks works for me:
11.4 64-Bit
KDE 4.6.0
Nvidia installed via repo: 260.19.36

> Plasma and amaroks works for me:
> 11.4 64-Bit
> KDE 4.6.0
> Nvidia installed via repo: 260.19.36

That's not very helpful, it was always known the problem existed only on 32-bit systems :-)(In reply to comment #99)

(In reply to comment #98)
> I just tested:
> 
> 11.4, 32-bit
> KDE 4.6.0
> Nvidia blob 260.19.36 (KMP from the Nvidia repo)
> 
> And for me Plasma and Amarok (both in completely default configuration) were
> working fine.
> 
> Can anyone else confirm? 
> 
> It'd be nice to be able to get rid of all the warnings in the wiki etc., if the
> problem is actually solved now - even with 260 series.

Just upgraded to 11.4 on a 32-bit system and KDE starts just fine, but Amarok crashes with a floating point exception.

(In reply to comment #101)
> Just upgraded to 11.4 on a 32-bit system and KDE starts just fine, but Amarok
> crashes with a floating point exception.

Could you list the widgets you use in Amarok? Does it happen with a new user too?

(In reply to comment #102)
> (In reply to comment #101)
> > Just upgraded to 11.4 on a 32-bit system and KDE starts just fine, but Amarok
> > crashes with a floating point exception.
> 
> Could you list the widgets you use in Amarok? Does it happen with a new user
> too?

I created a new user, and the steps were:

- amarok does not have MP3 support, do you want to install ? (no)
- dialog pops up for collection selection, I pick $HOME/Documents
- amarok windows briefly appears
- crash

As for the widgets, I have no idea, but should be nothing out of the ordinary.

I'm experiencing similar problem. Not with failing KDE, but vlc.
When started from konsole, vlc will crash on floating point exception. When run with strace there is no problem. What is interesting, when I connect through ssh, set display envvar to :0.0 and start vlc, it starts up on target machine without problem.

just zypper duped openSUSE from 11.3 to 11.4 (kernel 2.6.37.1-1.2-desktop)
vlc 1.1.7-1.pm.12.1.i586
nvidia driver 270.26

(In reply to comment #104)
See comment #97. The bug seems to be fixed in the latest nvidia beta driver, so try updating to 270.30.

Right, indeed 270.30 is working for me. I didn't find that version through nVidia beta driver download web site, my apologies.

dup to 11.4 not working here, KDE not loading at all with driver from rpm. Installing beta driver 270.30 login screen is working but then I got black screen with KDE 4.6.0 or never closing loading screen with 4.6.1

last working driver 256.30 not building anymore with suse 11.4

--> at least zypper dup from 11.4 to 11.3 works fine and I am able to build 256.30 again

(In reply to comment #107)
If you can see the mouse cursor on KDE 4.6.0 black screen, then what's your video card model?

It might probably be a known problem with older NVIDIA cards. See this link: http://userbase.kde.org/GPU-Performance, under 'nvidia - black window problem' section. Try disabling effects (Alt+Shift+F12 by default) or switching the rendering engine from OpenGL to XRender.

I've got black desktop (black plasma-desktop window actually) with 11.4+KDE 4.6+NVIDIA 270.30 on built-in GeForce 7050, but the same software set works fine on GF 8400M GS. I didn't try the stable driver from the repository though.

I tried again and can now confirm too openSUSE 11.4 with standard KDE 4.6.0 working. :-)

I am sorry about my misstatement. :-(

*** Bug 681521 has been marked as a duplicate of this bug. ***

FYI: 11.4 Good
Issue experienced on Default 11.3 32-bit installation,
Upgraded to 11.4 32-bit from DVD medium, installed NVidia via 1-click YMP, no issues.


OS Information
OS:  Linux 2.6.37.1-1.2-desktop i686
  System:  openSUSE 11.4 (i586)
  KDE:  4.6.00 (4.6.0) "release 6"

Display Info
Vendor:  nVidia Corporation
  Model:  GeForce Go 7400
  2D driver:  nvidia
  3D driver:  NVIDIA 260.19.44

(In reply to comment #111)
I can confirm that Plasma doesn't crash anymore in KDE 4.6.1 (from the build service) even with the nvidia driver version 260.19.44 (instead of 270).

On the other hand, Amarok still does (except if started with gdb), and sometimes Konsole crashes too on closing a tab, although I'm not sure the latter is related to this bug.

Hardware: GeForce 6200 TurboCache

I had the FPE before with NVIDIA 260.19.44 (from the NVIDIA website) and KDE 4.6.0.
Just upgraded the driver to NVIDIA 270.41.03 and now amarok and nvidia-settings can run properly.

Hardware: GeForce 9300M GS
OS: openSUSE 11.4

OpenSUSE 11.4 x86_32 (installed yesterday; changed (before knowing about this issue) from nouveau to nvidia)
2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10 +0100 i686 athlon i386 GNU/Linux

00:12.0 VGA compatible controller: nVidia Corporation C67 [GeForce 7150M / nForce 630M] (rev a2)

Gnome desktop (though the KDE desktop is also installed because I like some of the tools)

#The following four return from `rpm -qa | grep -i nvidia`
nvidia-gfxG02-kmp-desktop-260.19.44_k2.6.37.1_1.2-23.1.i586
x11-video-nvidiaG01-173.14.28-28.1.i586
nvidia-gfxG01-kmp-desktop-173.14.28_k2.6.37.1_1.2-27.1.i586
x11-video-nvidiaG02-260.19.44-24.1.i586

Verified that running `vlc /dev/sr0` sees the FP exception, but prepending that with `strace -s 0` or `gdb` prevents the problem.

Since I haven't seen references to other instances on the web while reading through the bug:
http://trac.videolan.org/vlc/ticket/4588 #closed thinking it was an OpenSUSE issue
http://forum.videolan.org/viewtopic.php?f=13&t=88396 #VideoLAN forum thread where user found the solution of back-revving the NVidia driver.
http://forum.videolan.org/viewtopic.php?f=13&t=87226 #VideoLAN forum thread where timing issue was found due to gdb/strace troubleshooting failures
http://forums.opensuse.org/english/get-technical-help-here/multimedia/453777-vlc-tries-start-but-crashes.html #OpenSUSE forum thread

Also in the KDE forums: http://forum.kde.org/viewtopic.php?f=66&t=92382

Installed the new driver (270.41.06). 

It solved most problems (KDE, Amarok, Ktorrent, Mplayer)
Xine still crashes. Running "strace xine" works as before. 

 
Using: 
openSUSE 11.3
nvidia-gfxG02-kmp-desktop-270.41.06_k2.6.34.0_12-4.1.i586

I guess this is fixed with never nvidai drivers.