X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 01 Apr 2013 01:52 AM by  anon
IDL 8.1 Fedora 18 Gnome
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
01 Apr 2013 01:52 AM
    Hi, I recently upgraded to Fedora 18 and the console showed following error on opening idlde ash@ncl-cepd-lp-004 : ~ > idlde # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x3c4c4e5c, pid=2268, tid=3064060736 # # JRE version: 6.0_17-b04 # Java VM: Java HotSpot(TM) Server VM (14.3-b01 mixed mode linux-x86 ) # Problematic frame: # C 0x3c4c4e5c # # An error report file with more information is saved as: # /home/ash/hs_err_pid2268.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # ash@ncl-cepd-lp-004 : ~ > No errors is obtained when IDL is used without graphics. As per one other thread, this problem should disappear when upgraded to 8.2.2. Is a solution available without upgrading to 8.2.2 ? Regards, Ashish Orpe Scientist, National Chemical Laboratory, Pune 411008 India

    Deleted User



    New Member


    Posts:
    New Member


    --
    02 Apr 2013 03:25 PM
    Hi Ashish, Try renaming (or deleting) the following hidden directory, by typing the following in your Linux prompt from your home directory: mv .idl _idl Then, try starting IDLDE again. Did that help? Cheers, Fernando

    Deleted User



    New Member


    Posts:
    New Member


    --
    02 Apr 2013 10:39 PM
    Hi Fernando, Deleting .idl directory does not help as it recreates it again alongwith the error mentioned previously. Renaming .idl as _idl also does not help as opening idlde creates .idl again irrespective of the presence of "_idl". The error remains the same. Do you think this problem may go away with a new version of java ? There were absolutely no issues with Fedora Core 17 -- Ashish

    Deleted User



    New Member


    Posts:
    New Member


    --
    03 Apr 2013 09:25 AM
    Hi Ashish, What about renaming the following from your home directory: mv IDLWorkspace82 IDLWorkspace82_back I just wanted to say that you need to be careful with the above directory, it might contain your own IDL code programs inside projects. So, just be careful and don't delete it, just rename it. IDL will create a new one. If this is the solution, then you can import your project back again into the newly created workspace directory. Another possibility is that the Linux Desktop Manager is the problem. Are you using Gnome or KDE?. Try a different one, we have seen problems with newer versions of Gnome, the fancy versions. Cheers, Fernando
    You are not authorized to post a reply.