Cron-o-meter (Java application) crashes F10 KDE 4.2.2 sessions.

[linux guy]

I am running cronometer 0.9.5 as downloaded from
http://spaz.ca/cronometer/ .

It ran fine with KDE 4.2 and 4.2.1.  It now crashes the session with KDE
4.2.2.  It looks like something is wrong with repaint.  It seems fine if
the application is just open, but as soon as you move the application
window the whole desktop area starts going weird.

$ java -version
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode)

BTW: Cronometer seems to be well written and its useful for people who
want to track diet and fitness goals. I recommend that it be included in
the Fedora repositories.

Thanks for listening.

[Rahul Sundaram]

On 05/06/2009 03:19 AM, Linuxguy123 wrote:
> BTW: Cronometer seems to be well written and its useful for people who
> want to track diet and fitness goals. I recommend that it be included in
> the Fedora repositories.
>
> Thanks for listening.

Would you be willing to participate and be a maintainer?

https://fedoraproject.org/wiki/PackageMaintainers/Join

Even if you don't understand packaging, you can read up, ask questions
and get help.

Rahul

[Craig White]

On Wed, 2009-05-06 at 03:35 +0530, Rahul Sundaram wrote:
> On 05/06/2009 03:19 AM, Linuxguy123 wrote:
> > BTW: Cronometer seems to be well written and its useful for people who
> > want to track diet and fitness goals. I recommend that it be included in
> > the Fedora repositories.
> >
> > Thanks for listening.
>
> Would you be willing to participate and be a maintainer?
>
> https://fedoraproject.org/wiki/PackageMaintainers/Join
>
> Even if you don't understand packaging, you can read up, ask questions
> and get help.

----
how is he supposed to pull that off if he's using Sun's JRE and not
OpenJDK?

Craig

[Rahul Sundaram]

On 05/06/2009 03:53 AM, Craig White wrote:
> how is he supposed to pull that off if he's using Sun's JRE and not
> OpenJDK?

What he uses on his own system is his preference.

There is no reason it shouldn't work with OpenJDK since OpenJDK in
Fedora has passed TCK 100%. Of course, if there are any bugs that is
preventing the application from running with OpenJDK, you can file them.

Rahul

[Craig White]

On Wed, 2009-05-06 at 04:05 +0530, Rahul Sundaram wrote:
> On 05/06/2009 03:53 AM, Craig White wrote:
> > how is he supposed to pull that off if he's using Sun's JRE and not
> > OpenJDK?
>
> What he uses on his own system is his preference.
>
> There is no reason it shouldn't work with OpenJDK since OpenJDK in
> Fedora has passed TCK 100%. Of course, if there are any bugs that is
> preventing the application from running with OpenJDK, you can file them.

----
and if someone reports a bug against the package, he tells them that it
works with Sun Java?

Craig

[linux guy]

On Tue, 2009-05-05 at 16:02 -0700, Craig White wrote:
> and if someone reports a bug against the package, he tells them that
> it
> works with Sun Java?

I knew that I was going to get criticized for using JRE and not
OpenJDK.

I don't have time to be the maintainer for anything right now.  Maybe in
the fall, I'll see how my projects go this summer.

What JVM is used is irrelevant.  They should both work with KDE4.2.2 or
maybe more correctly, KDE4.2.2 should work with both of them.  I'm
guessing that the Java widget library doesn't work with KDE4.2.2.  Does
Cronometer use Swing ?  I haven't looked yet.

Cronometer & JRE worked fine with KDE 4.2.1 and now it/they crash with
KDE 4.2.2 on my machine.  Has anyone been able to duplicate this
behavior ?

Thanks

[Rahul Sundaram]

On 05/06/2009 04:32 AM, Craig White wrote:
> On Wed, 2009-05-06 at 04:05 +0530, Rahul Sundaram wrote:
> > On 05/06/2009 03:53 AM, Craig White wrote:
> > > how is he supposed to pull that off if he's using Sun's JRE and not
> > > OpenJDK?
> >
> > What he uses on his own system is his preference.
> >
> > There is no reason it shouldn't work with OpenJDK since OpenJDK in
> > Fedora has passed TCK 100%. Of course, if there are any bugs that is
> > preventing the application from running with OpenJDK, you can file them.
>
> and if someone reports a bug against the package, he tells them that it
> works with Sun Java?

Not sure I understand the context of the question well. For the
application to be packaged in Fedora, it needs to work with OpenJDK
first. So part of the packaging process is to ensure integration. If on
a later date a bug report is filed, the answer would depend on what the
bug report is about in the first place.

If it is a bug in the application, he needs to file it upstream, if it
is the packaging, he needs to fix it. If it is about interaction with
OpenJDK vs Sun JDK, he can file it against OpenJDK and if it does work
with Sun JDK, he is free to suggest that as a workaround.

Rahul

[linux guy]

I did a alternatives --config java and selected JDM instead of JRE.

I ran cronometer and it behaved the same.   The problem exists
regardless of which JVM is used.

# java -version
java version "1.6.0_0"
IcedTea6 1.4 (fedora-15.b14.fc10-i386) Runtime Environment (build
1.6.0_0-b14)
OpenJDK Server VM (build 14.0-b08, mixed mode)

Can someone confirm they are experiencing the same behavior ?

Thanks

[Lillian Angel]

Linuxguy123 wrote:
> I did a alternatives --config java and selected JDM instead of JRE.
>
> I ran cronometer and it behaved the same.   The problem exists
> regardless of which JVM is used.
>
> # java -version
> java version "1.6.0_0"
> IcedTea6 1.4 (fedora-15.b14.fc10-i386) Runtime Environment (build
> 1.6.0_0-b14)
> OpenJDK Server VM (build 14.0-b08, mixed mode)
>
> Can someone confirm they are experiencing the same behavior ?

I tested it with OpenJDK + Gnome and it works fine.

Lillian

[Colin J Thomson]

On Wednesday 06 May 2009 15:16:03 Lillian Angel wrote:
> Linuxguy123 wrote:
> > I did a alternatives --config java and selected JDM instead of JRE.
> >
> > I ran cronometer and it behaved the same.   The problem exists
> > regardless of which JVM is used.
> >
> > # java -version
> > java version "1.6.0_0"
> > IcedTea6 1.4 (fedora-15.b14.fc10-i386) Runtime Environment (build
> > 1.6.0_0-b14)
> > OpenJDK Server VM (build 14.0-b08, mixed mode)
> >
> > Can someone confirm they are experiencing the same behavior ?
>
> I tested it with OpenJDK + Gnome and it works fine.

Tested here also - KDE-4.2.2, Nvidia system/GFX card, rpmfusion's 180.51 
packages,

java version "1.6.0_0"
IcedTea6 1.4 (fedora-15.b14.fc10-i386) Runtime Environment (build 1.6.0_0-b14)
OpenJDK Client VM (build 14.0-b08, mixed mode)

Works fine here.

Colin

[linux guy]

On Wed, 2009-05-06 at 18:18 +0100, Colin J Thomson - G6AVK wrote:
> On Wednesday 06 May 2009 15:16:03 Lillian Angel wrote:
> > Linuxguy123 wrote:
> > > I did a alternatives --config java and selected JDM instead of JRE.
> > >
> > > I ran cronometer and it behaved the same.   The problem exists
> > > regardless of which JVM is used.
> > >
> > > # java -version
> > > java version "1.6.0_0"
> > > IcedTea6 1.4 (fedora-15.b14.fc10-i386) Runtime Environment (build
> > > 1.6.0_0-b14)
> > > OpenJDK Server VM (build 14.0-b08, mixed mode)
> > >
> > > Can someone confirm they are experiencing the same behavior ?
> >
> > I tested it with OpenJDK + Gnome and it works fine.
>
> Tested here also - KDE-4.2.2, Nvidia system/GFX card, rpmfusion's 180.51 
> packages,
>
> java version "1.6.0_0"
> IcedTea6 1.4 (fedora-15.b14.fc10-i386) Runtime Environment (build 1.6.0_0-b14)
> OpenJDK Client VM (build 14.0-b08, mixed mode)
>
> Works fine here.

hmmmmm....  why would it crash on my installation and not others ?

[Colin J Thomson]

On Wednesday 06 May 2009 23:11:50 Linuxguy123 wrote:
> On Wed, 2009-05-06 at 18:18 +0100, Colin J Thomson - G6AVK wrote:
> > On Wednesday 06 May 2009 15:16:03 Lillian Angel wrote:
> > > Linuxguy123 wrote:
> > > > I did a alternatives --config java and selected JDM instead of JRE.
> > > >
> > > > I ran cronometer and it behaved the same.   The problem exists
> > > > regardless of which JVM is used.
> > > >
> > > > # java -version
> > > > java version "1.6.0_0"
> > > > IcedTea6 1.4 (fedora-15.b14.fc10-i386) Runtime Environment (build
> > > > 1.6.0_0-b14)
> > > > OpenJDK Server VM (build 14.0-b08, mixed mode)
> > > >
> > > > Can someone confirm they are experiencing the same behavior ?
> > >
> > > I tested it with OpenJDK + Gnome and it works fine.
> >
> > Tested here also - KDE-4.2.2, Nvidia system/GFX card, rpmfusion's 180.51
> > packages,
> >
> > java version "1.6.0_0"
> > IcedTea6 1.4 (fedora-15.b14.fc10-i386) Runtime Environment (build
> > 1.6.0_0-b14) OpenJDK Client VM (build 14.0-b08, mixed mode)
> >
> > Works fine here.
>
> hmmmmm....  why would it crash on my installation and not others ?

I have no idea really, maybe your gfx card is one of the newer ones but I 
thought most of the problems where fixed in the current Nvidia drivers. This 
is assuming it is an Nvidia problem. Have you tried the NV driver as a test?

FYI I use a Geforce 7800GS.

Goodluck

Colin

[Kevin Kofler]

Linuxguy123 wrote:
> It ran fine with KDE 4.2 and 4.2.1.  It now crashes the session with KDE
> 4.2.2.  It looks like something is wrong with repaint.  It seems fine if
> the application is just open, but as soon as you move the application
> window the whole desktop area starts going weird.

If it crashes the whole session, this is most likely a bug in your graphics
driver, not KDE.

Was your graphics driver also updated?

Kevin Kofler

[linux guy]

On Wed, 2009-05-06 at 05:14 +0200, Kevin Kofler wrote:
> Linuxguy123 wrote:
> > It ran fine with KDE 4.2 and 4.2.1.  It now crashes the session with KDE
> > 4.2.2.  It looks like something is wrong with repaint.  It seems fine if
> > the application is just open, but as soon as you move the application
> > window the whole desktop area starts going weird.
>
> If it crashes the whole session, this is most likely a bug in your graphics
> driver, not KDE.
>
> Was your graphics driver also updated?

$ yum list *nvidia*
Loaded plugins: downloadonly, kmdl, priorities, refresh-packagekit
2 packages excluded due to repository priority protections        
Installed Packages                                                
kmod-nvidia.i686 180.51-1.fc10.1  installed
kmod-nvidia-2.6.27.15-170.2.24.fc10.i686.i686  180.29-1.fc10 installed 
kmod-nvidia-2.6.27.19-170.2.35.fc10.i686.i686  180.29-1.fc10.1installed 
kmod-nvidia-2.6.27.21-170.2.56.fc10.i686.i686  180.51-1.fc10.1 installed
xorg-x11-drv-nvidia.i386     180.51-1.fc10  installed
xorg-x11-drv-nvidia-libs.i386   180.51-1.fc10  installed

# cat yum.log | grep nvidia
Jan 27 08:29:46 Updated: kmod-nvidia-180.22-1.fc10.1.i686
Jan 27 08:29:47 Installed: kmod-nvidia-2.6.27.12-170.2.5.fc10.i686-180.22-1.fc10.1.i686
Jan 27 08:29:51 Updated: xorg-x11-drv-nvidia-180.22-1.fc10.i386
Jan 27 08:29:52 Updated: xorg-x11-drv-nvidia-libs-180.22-1.fc10.i386
Jan 27 08:30:08 Updated: kmod-nvidia-2.6.27.9-159.fc10.i686-180.22-1.fc10.i686
Jan 27 08:30:18 Erased: kmod-nvidia-2.6.27.5-117.fc10.i686
Jan 29 09:21:53 Updated: kmod-nvidia-180.25-1.fc10.i686
Jan 29 09:22:02 Updated: kmod-nvidia-2.6.27.12-170.2.5.fc10.i686-180.25-1.fc10.i686
Jan 29 09:22:04 Updated: xorg-x11-drv-nvidia-180.25-1.fc10.i386
Jan 29 09:22:11 Updated: xorg-x11-drv-nvidia-libs-180.25-1.fc10.i386
Feb 19 07:50:34 Updated: xorg-x11-drv-nvidia-libs-180.29-1.fc10.i386
Feb 19 07:50:52 Updated: xorg-x11-drv-nvidia-180.29-1.fc10.i386
Feb 19 07:50:53 Installed: kmod-nvidia-2.6.27.15-170.2.24.fc10.i686-180.29-1.fc10.i686
Feb 19 07:50:53 Updated: kmod-nvidia-180.29-1.fc10.i686
Feb 19 07:51:05 Updated: kmod-nvidia-2.6.27.12-170.2.5.fc10.i686-180.27-1.fc10.i686
Feb 19 07:51:11 Erased: kmod-nvidia-2.6.27.7-134.fc10.i686
Mar 03 09:35:35 Erased: kmod-nvidia-2.6.27.9-159.fc10.i686
Mar 05 07:46:34 Installed: kmod-nvidia-2.6.27.19-170.2.35.fc10.i686-180.29-1.fc10.1.i686
Mar 05 07:46:34 Updated: kmod-nvidia-180.29-1.fc10.1.i686
Apr 03 13:09:14 Installed: kmod-nvidia-2.6.27.21-170.2.56.fc10.i686-180.29-1.fc10.2.i686
Apr 03 13:09:14 Updated: kmod-nvidia-180.29-1.fc10.2.i686
Apr 03 13:10:21 Erased: kmod-nvidia-2.6.27.12-170.2.5.fc10.i686
Apr 25 09:13:39 Updated: xorg-x11-drv-nvidia-libs-180.51-1.fc10.i386
Apr 25 09:14:21 Updated: kmod-nvidia-2.6.27.21-170.2.56.fc10.i686-180.51-1.fc10.1.i686
Apr 25 09:14:24 Updated: xorg-x11-drv-nvidia-180.51-1.fc10.i386
Apr 25 09:14:24 Updated: kmod-nvidia-180.51-1.fc10.1.i686

[Kevin Kofler]

Linuxguy123 wrote:
> Apr 25 09:13:39 Updated: xorg-x11-drv-nvidia-libs-180.51-1.fc10.i386
> Apr 25 09:14:21 Updated: kmod-nvidia-2.6.27.21-170.2.56.fc10.i686-180.51-1.fc10.1.i686
> Apr 25 09:14:24 Updated: xorg-x11-drv-nvidia-180.51-1.fc10.i386
> Apr 25 09:14:24 Updated: kmod-nvidia-180.51-1.fc10.1.i686

I guess that's the offending update.

Kevin Kofler

Cron-o-meter (Java application) still crashes. Now F10 KDE 4.2.3 sessions.

[linux guy]

I was hoping that cronometer would stop crashing in KDE4.2.3.  But it
hasn't.  Below is the original post to this group.

I wonder if Qt4.5.1 will solve it.

Where should I report this problem ?

Thanks

LG

On Tue, 2009-05-05 at 15:49 -0600, Linuxguy123 wrote:
> I am running cronometer 0.9.5 as downloaded from
> http://spaz.ca/cronometer/ .
>
> It ran fine with KDE 4.2 and 4.2.1.  It now crashes the session with KDE
> 4.2.2.  It looks like something is wrong with repaint.  It seems fine if
> the application is just open, but as soon as you move the application
> window the whole desktop area starts going weird.
>
> $ java -version
> java version "1.6.0_10"
> Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
> Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode)
>
> BTW: Cronometer seems to be well written and its useful for people who
> want to track diet and fitness goals. I recommend that it be included in
> the Fedora repositories.
>
> Thanks for listening.

Cron-o-meter (Java application) still crashes. Now F10 KDE 4.2.3 sessions.

[Rex Dieter]

Linuxguy123 wrote:
> I was hoping that cronometer would stop crashing in KDE4.2.3.  But it
> hasn't.  Below is the original post to this group.

cronometer folks know about their app crashing?  If not, they ought to.

-- Rex

Cron-o-meter (Java application) still crashes. Now F10 KDE 4.2.3 sessions.

[linux guy]

On Thu, 2009-05-21 at 09:28 -0500, Rex Dieter wrote:
> Linuxguy123 wrote:
> > I was hoping that cronometer would stop crashing in KDE4.2.3.  But it
> > hasn't.  Below is the original post to this group.
>
> cronometer folks know about their app crashing?  If not, they ought to.

I reported it.  There was no reply.

FWIW Cronometer doesn't crash the session anymore.  A new kmod-nvidia
got installed on May 26th.

Cron-o-meter (Java application) still crashes. Now F10 KDE 4.2.3 sessions.

[linux guy]

On Tue, 2009-06-02 at 12:48 -0600, Linuxguy123 wrote:
> On Thu, 2009-05-21 at 09:28 -0500, Rex Dieter wrote:
> > Linuxguy123 wrote:
> > > I was hoping that cronometer would stop crashing in KDE4.2.3.  But it
> > > hasn't.  Below is the original post to this group.
> >
> > cronometer folks know about their app crashing?  If not, they ought to.
>
> I reported it.  There was no reply.
>
> FWIW Cronometer doesn't crash the session anymore.  A new kmod-nvidia
> got installed on May 26th.

I spoke too soon.  It crashed my session this morning.