Bug 209007 - Cronometer crashes my KDE session.
Summary: Cronometer crashes my KDE session.
Status: RESOLVED UPSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-30 18:19 UTC by Me
Modified: 2010-05-27 20:16 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Me 2009-09-30 18:19:18 UTC
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    Fedora RPMs

Cronometer crashes my kde sessions.  It works fine in gnome. 

http://spaz.ca/cronometer/

Version-Release number of selected component (if applicable):

cronometer: 0.95

Cronometer worked fine in KDE 4.2.2.  It started crashing in KDE 4.2.3.  I initially reported it in early June, 2009 with the following.

$ rpm -q kmod-nvidia
kmod-nvidia-180.51-1.fc10.5.i686

$ rpm -q kdebase
kdebase-4.2.3-1.fc10.i386


How reproducible:

It was every time until yesterday.   Yesterday I ran cronometer with no
problems.   Today it crashed the session again.

I believe the problem appeared with kde 4.2.3.  It ran fine on kde 4.2 before
that. 

Steps to Reproduce:
1. Install cronometer
2. Run it.   
3. Move the application around a bit.


Actual results:

It looks like it corrupts the redrawing of the screen.  Mouse function is
affected too... or at least it seems to be.  Maybe its just a redraw thing.

The only way to save the machine from crashing outright is to immediately exit
the session.

I believe cronometer uses the Swing library.   Are other Swing applications
experiencing the same problem ?

Expected results:

It should run without crashing the session.

I initially reported the bug here.  https://bugzilla.redhat.com/show_bug.cgi?id=504173  They dismissed it as an nvidia problem because that was the bug flavor of the month, but we've had several KDE and nvidia releases since then and its still a problem.

The current release information for this problem is:

$ uname -a
Linux localhost.localdomain 2.6.30.8-64.fc11.i686.PAE #1 SMP Fri Sep 25 04:56:58 EDT 2009 i686 i686 i386 GNU/Linux

rpm -q kdebase
kdebase-4.3.1-2.fc11.i586

$ yum list akmod\*
Installed Packages
akmod-nvidia.i686               185.18.36-1.fc11                @rpmfusion-nonfree-updates
akmods.noarch                   0.3.6-3.fc11                    @rpmfusion-free-updates

Let me know if you need any other information.

Thanks for listening.
Comment 1 FiNeX 2009-10-01 15:44:26 UTC
Did you tried disabling desktop effects?
Comment 2 Me 2009-10-01 16:06:24 UTC
I don't believe I have them enabled.   Tell me exactly what you want to enable or disable and I will test it.

Thanks
Comment 3 FiNeX 2009-10-01 20:37:01 UTC
right click on a window title and select "configure window behaviour", you should see the option "Enable desktop effects". If it is checked, please uncheck it and try again to reproduce the crash.
Comment 4 Me 2009-10-01 22:17:44 UTC
Desktop effects are not enabled.  It crashes with it disabled.  

Please advise of any other tests you would like me to run.
Comment 5 Jonathan Thomas 2010-05-27 20:16:08 UTC
This is an Nvidia issue, and just because there have been nvidia updates since doesn't necessarily mean that the issue would be fixed. Likely nvidia isn't aware of the issue themselves. Reports of it working with the open source nouveau driver in the Fedora bug further support this, as well as the fact that all Xserver crashes are driver bugs.