Anomalous visual program editor of openDX in 64bit ubuntu/kubuntu

Bug #110404 reported by Gominolas
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lesstif2 (Ubuntu)
Confirmed
Undecided
Daniel T Chen

Bug Description

Binary package hint: dx

When running openDX 4.4.0 in Kubuntu Feisty Fawn 64bit, the software works properly (programs can be loaded, executed...). The problem comes when running a program, at the Visual Program Editor(VPE) window of the windows menu, where the area meant for editing programs just shows a thin tag and nothing can be edited in the window. Due to this issue no program cannot be edited.

- OpenDX version is 4.4.0.
- openDX 4.4.0 worked fine previously in the same computer with a SUSE 10.1 64bit distro
- The same problem has been observed in another computer with Kubuntu Edgy 64bit and previously in ubuntu forums (http://ubuntuforums.org/showthread.php?t=286379) with no answer.

Greetings,

Roland Blanch

Revision history for this message
Craig J Copi (cbug) wrote :

I can confirm I have seen the same problem on two different 64 bit Feisty boxes (one with nvidia card, one with ati).

To work around the problem I rebuilt the package without optimization (-O0). It runs as expected now.

Craig

Revision history for this message
tcriess (thorsten-riess) wrote :

I can confirm the bug here as well - on Feisty 64 bit and also on the latest Gutsy Alpha 64 bit. Self compiled version with -O0 works.
Thorsten.

Revision history for this message
tcriess (thorsten-riess) wrote :

Just curious: is there any chance that this obvious and annoying bug (which basically renders the application unusable) will be corrected at some point?

Revision history for this message
hippocanjump (hippocanjump) wrote :

Same error here

Gutsy, Dual Core AMD64 with Nvidia drivers. DX editor shows a thin tab with no space for editing programs. A bit of annoying, really.

Revision history for this message
hippocanjump (hippocanjump) wrote :

I tried compiling OpenDX-4.4.4 with the flags -O0 and got the same error in VPE.

Revision history for this message
Srinath Madhavan (msrinath80) wrote :

Seems to work fine on Debian testing after building from source. I've updated the thread on ubuntuforums --> http://ubuntuforums.org/showthread.php?p=5358922

Revision history for this message
Craig J Copi (cbug) wrote :

For Hardy I haven't been able to get the 4.4.0 package to work. Even when compiled with -O0 the VPE error persists. Interestingly if I compile from the original source it works fine.

Recently I pulled down the 4.4.4 source package from Intrepid (4.4.4-1) and compiled and installed it on my Hardy machines. It works as expected; no VPE error!

I do not have a 64 bit machine running Intrepid so I cannot verify that this is fixed in Intrepid.

Revision history for this message
Craig J Copi (cbug) wrote :

More information: The problem shows up when dx is built again lesstif2, it does NOT show up when built against libmotif3.

In Hardy I built 4.4.4-1 against libmotif3 and the editor works correctly.

In Intrepid if I build 4.4.4-1 against lesstif2 the editor does not work correctly. This is the way the dx package is built in the repositories.

In Intrepid if I build 4.4.4-1 against libmotif3 the editor does work correctly.

Daniel T Chen (crimsun)
Changed in dx:
assignee: nobody → crimsun
status: New → Confirmed
Revision history for this message
Paul Gevers (paul-climbing) wrote :

lesstif2 version 1:0.95.0-2.3 was fixed with respect to a major 64bit issue. Could you please check/confirm that the bug still exists with lesstif2 version 1:0.95.0-2.3?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.