Jonesy composed on 2016-08-03 19:27 (UTC-0600):

Sl?vek Banko wrote:

...

Gtk-qt-engine sometimes causes problems. You can try to uninstall it and install another gtk-engine, for example qtcurve.

I wonder if he could be thinking about this? http://bugs.pearsoncomputing.net/show_bug.cgi?id=2477

Thankls for the quick reply! But, confusion!!!

|$ sudo apt-get remove gtk-qt-engine |Reading package lists... Done |Building dependency tree |Reading state information... Done |Package 'gtk-qt-engine' is not installed, so not removed |0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Do you mean this below?

ii gtk-qt-engine-trinity 4:14.0.4~pre1-0ubuntu16.04.0+0~a amd64 theme engine using Qt for GTK+ 2.x and Trinity

Probably.

And your suggestion of "qtcurve"... That's it? Just "qtcurve"? sudo apt-get install qtcurve ??????????

# aptitude search qtcurve | grep gtk: gtk2-engines-qtcurve.

I use gtk2-engines-oxygen for 16.04/14.x. gtk-qt-engine-trinity is installed, but I can't use any Java apps, because their fonts are always illegibly tiny and won't obey DE font settings (TDE or any variant of KDE).

On Thu, 4 Aug 2016, Thierry de Coulon wrote:

On Thursday 04 August 2016 01.57:20 Sl?vek Banko wrote:

...

On Thursday 04 of August 2016 01:48:32 Jonesy wrote:

...

I'm trying to get moneydance to run on on 64-bit Ubuntu 16.04

(...)

...

...

I've installed the new "amd64" moneydance as instructed by their website, and I get this when I try to run it: |$ Moneydance |[kcrash] TDECrash: Application 'output.logl-gtk-tqt-application' | crashing...

(...)

...

Gtk-qt-engine sometimes causes problems. You can try to uninstall it and install another gtk-engine, for example qtcurve.

I've just tried to install Moneydance on openSUSE 13.1 + TDE 14.0.0, using the RPM package from their site. Except that I have nothing in the TDE "startmenu", starting moneydance from /opt/moneydance over the moneydance.desktop file works like a charm.

"TDE 14.0.0" ? I'm on TDE 14.0.4 with Slavek's Preliminary stable builds.

I have qtcurve installed

So maybe your issue is more specifically Ubuntu related? Or Java? Could the error message be the result of something else missing?

Anyway, Moneydance _can_ run on TDE

Have a good day (or night... depending where you live),

Thank you, Thierry, for the encouraging report/feedback. And, Good Morning to you (or night... depending where you live.) :-) It's Mountain Daylight Time here...

Other "activities' will keep me away from this until later today. But, I will do as Slavek suggested and as Felix explained, and I will report back.

I need to report back, too, on bringing up Trinity TDE 14.04 on Ubuntu 16.04. It was not pretty, and it's not yet perfect, but in the end it's something I feel comfortable about going forward with.

Thanks everybody! Jonesy

On Thursday 04 August 2016 11:44:06 Thierry de Coulon wrote:

On Thursday 04 August 2016 15.25:02 Jonesy wrote:

...

"TDE 14.0.0" ? I'm on TDE 14.0.4 with Slavek's Preliminary stable builds.

Yep :)

openSUSE is at "Leap 42.1" and TDE at 14.0.4, but I see no reason to update as everything works fine here and I did not identify any feature that justifies an update.

Long time ago (Gene may confirm) Linux users were proud to state that their kernel was still bellow 1.0, meaning it was good and stable and did not need to upgrade.

Well, I'm still on wheezy (debian 7.11) running a Debian 3.16.7-ckt25-2+deb8u3~bpo70+1 kernel. Because my hardware requires a real time kernel, the other 3 machines are currently running a 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4 kernel, specially patched and built by the linuxcnc folks. The pae on those machines does not work but they don't have that much memory anyway as it runs everything I need in 2 gigs.

But I do update all 4 machines daily as linuxcnc is in constant development, and I, not running a commercial machine shop where downtime=loss of money, so I am running the development branch because I can afford to bleed a bit it they break something. I enjoy playing the part of a development tester.

Now, everyone has been trained to think that any piece of software that has not received an update in the week is probably no more supported, insecure and maybe dangerous...

Those non linuxcnc updates I get from the wheezy repos are supposedly security only updates, but there are several such updates a week. Or a huge drop of fixes for tde-trinity from slavek's repo.

Other than some pretty big problems introduced in linuxcnc as they changed the kinematics to divorce an "axis" from a "joint", which were then arbitrarily linked in the axis display .ini and .hal files, several of which I found and reported, one of which cost me about $30 in broken tooling, found and fixed the next day, and a loss of speed in the one machine that still uses software step generation that caused some strange errors, its been an enjoyment to me that I have helped to stabilize the next official release.

The above change was made to simplify the configuration of a robotic arm with many joints and degrees of movement freedom. In some robotic arms, a move of the end of the arn and its final 2 joints carrying the gripper, aka effector, in a straight line from point a to point b may see 5 motors all moving at the same time, but at different rates needed to keep the effector moving in a dead straight line within a micron or so. Or to carry a plasma torch (or a water jet cutter) to cut complex shapes out of what ever material is being used. Or a MIG welder, writing a message on steel or just doing a precise weld, joining as many parts as the jig will hold at once. Limited only by the code writers imagination. We have some tools to help us write gcode, tools I may play with occasionally but have not used to cut metal unless I need a hole cut of a certain size and depth. Generally, because I may have expensive wood under the tool, I write my own gcode.

I'd still happily be running SuSE 8.2 if it supported my hardware :)

True, but hardware does wear out and get replaced with more capable stuff thats needs drivers to make it do the best it can. So we upgrade. And sometimes the upgrade is a pita. I wore out the cheap small mouse on this machine, so I go get another lookalike, only to discover that to save batteries, it puts itself completely to sleep and must be woke up again with a press on the buttons on the side. And that has led to some mouse miss-fires as I wave it around to locate its curser. Thats a PIMA, and I'd much rather put a battery in it twice as often.

To say that I am happy with tde is an understatement. Except for the no audio after a restart problem, I have nearly zero complaints.

Thierry

Cheers, Gene Heskett