Red Hat Bugzilla – Bug 504173
Cronometer crashes KDE session; please add cronometer to Fedora
Last modified: 2010-01-09 18:05:11 EST
Description of problem:
a) Please ad the cronometer application to the Fedora repositories.
Cronometer is a program for tracking fitness information and goals. It can be used to monitor diet, keep a training log and track and plot various target biomarkers. (It ships with only a few biomarkers, but one can easily edit the xml file to add however many one wants...)
I've been using Cronometer for about a year now. Other than the recently found bug below, its been totally stable.
b) cronometer crashes my kde sessions.
Version-Release number of selected component (if applicable):
$ rpm -q kmod-nvidia
$ rpm -q kdebase
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 3.2.3. It ran fine on kde 3.2 before that.
Steps to Reproduce:
1. Install cronometer
2. Run it.
3. Move the application around a bit.
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 ?
It should run without crashing the session.
It was stated that this is probably a problem with kmod-nvidia. I'm actually doubting that because the whole system becomes unstable, ie mouse and keyboard response is impaired too.
I know I haven't tagged this to the right Fedora component. I didn't know where to place a request for a new component.
I know I should have separate bug entries for the request to add cronometer and fixing the crash, but a) then we would have 2 mis-tagged entries and b) the bug will need to be fixed before cronometer is added to the repository.
Thanks for listening.
This is still an issue in F11. Even worse, in fact. Cronometer now locks up my session to the point that I have to do a hard reboot by powering down.
I tested Cronometer in a Gnome session on my laptop and it seems to work just fine. It didn't crash in the 10 minutes that I entered data and looked at charts.
$ rpm -q kdebase
$ rpm -q kmod-nvidia
Let me know if you need more information.
(In reply to comment #0)
> a) Please ad the cronometer application to the Fedora repositories.
> Cronometer is a program for tracking fitness information and goals. It can be
> used to monitor diet, keep a training log and track and plot various target
> biomarkers. (It ships with only a few biomarkers, but one can easily edit the
> xml file to add however many one wants...)
One of the best ways to get a package into Fedora is to become a packager. See here for more information:
If you do not wish to maintain the package yourself, try someone else who would be interested. You can add the package to the wishlist on the wiki here:
> b) cronometer crashes my kde sessions.
> $ rpm -q kmod-nvidia
> 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.
> It was stated that this is probably a problem with kmod-nvidia.
This is indeed likely. Whether it's Nvidia's fault or not, the issue is impossible to debug for a Fedora developer due to the proprietary nature of the driver. Only Nvidia have the sources, and they're the only one who can help.
> I'm actually doubting that because the whole system becomes unstable, ie
> mouse and keyboard response is impaired too.
A huge part of the proprietary driver runs in kernel space, where it can do absolutely anything. Severe system instability included.
Try to reproduce the problem without using the proprietary driver. Use nouveau, nv, or vesa instead. If you can reproduce it then, please file a new bug against the respective xorg-x11-drv-* component.
I was not able to run nouveau on my computer. See https://bugzilla.redhat.com/show_bug.cgi?id=528188
Good news though... the issue has disappeared. I was able to run Cronometer version 0.95 without any issue. I then updated and was able to run 0.97 as well. Both work fine.