Problem starting on Linux

I downloaded & installed

I trying to use Komodo-IDE-9.1.0-87337-linux-x86 w CentOS release 6.6 (Final).

installed into /opt/Komodo-IDE-9

[136]gamma{grieve} /opt/Komodo-IDE-9/bin/komodo
komodo: error: error creating ‘/home/grieve/.komodoide’: File exists
komodo: error: could not determine the user data dir
[152]gamma{grieve} rm -Rf /home/grieve/.komodoide
[153]gamma{grieve} ls /home/grieve/.komodoide
ls: cannot access /home/grieve/.komodoide: No such file or directory
[154]gamma{grieve} /opt/Komodo-IDE-9/bin/komodo
komodo: error: error creating ‘/home/grieve/.komodoide’: File exists
komodo: error: could not determine the user data dir


Below is the output from the install script
NB in reference to below, I have selinux Disabled.

root-->tar -xvf Komodo-IDE-9.1.0-87337-linux-x86.tar
root-->cd Komodo-IDE-9.1.0-87337-linux-x86
root-->./install.sh 
Enter directory in which to install Komodo. Leave blank and
press 'Enter' to use the default [~/Komodo-IDE-9].
Install directory: /opt/Komodo-IDE-9

chcon: can't apply partial context to unlabeled file `/opt/xy/lib/mozilla/libfreebl3.so'
chcon: can't apply partial context to unlabeled file `/opt/xy/lib/mozilla/libfreebl3.so'
chcon: can't apply partial context to unlabeled file `/opt/xy/lib/mozilla/libfreebl3.so'
chcon: can't apply partial context to unlabeled file `/opt/xy/lib/mozilla/libfreebl3.so'
install: warning: could not set SELinux security context for '/opt/xy/lib/mozilla/libfreebl3.so': 'texrel_shlib_t', 'textrel_shlib_t', 'shlib_t', 's0' contexts failed (this can be safely ignored if you do not use SELinux on your system)

==============================================================================
Komodo IDE 9 has been successfully installed to:

*& so on ...*
---------

  =======================================================

Before delving any deeper - are you running a 32bit system? If not you ought to download the 64bit installer.

32 bit …

[160]gamma{grieve} uname -m
i686

So is the issue with the installer or actually starting Komodo? Whats the stdout from starting Komodo?

[164]gamma{grieve} Komodo-IDE-9/bin/komodo
komodo: error: error creating ‘/home/grieve/.komodoide’: File exists
komodo: error: could not determine the user data dir

If I delete the dir ~/komodoide; & retry I get the same error
[164]gamma{grieve} Komodo-IDE-9/bin/komodo --help
works as expected, but then it odes not read any setup files.

what’s i that dir ?
[165]gamma{grieve} ls -lR /home/grieve/.komodoide
/home/grieve/.komodoide:
total 0
drwxr-xr-x 2 grieve public 31 Jun 26 12:22 9.1/

/home/grieve/.komodoide/9.1:
total 0
-rwxr-xr-x 1 grieve public 0 Jun 26 12:22 mutex.lock*

I assume you made a typo in your message, not the actual rm you did, which should delete ~/.komodoide.

Could you try komodo --verbose ?

Komodo-IDE-9/bin/komodo --verbose
komodo: debug: Komodo information:
komodo: debug: Version: Komodo IDE 9.1.0 (Build 87337) linux-x86
komodo: debug: OS type: Linux release 2.6.32-431.20.3.el6.i686 on i686 (#1 SMP Thu Jun 19 19:51:30 UTC 2014)
komodo: debug: Komodo startup options:
komodo: debug: nFiles: 0
komodo: debug: mutex name: ‘/home/grieve/.komodoide/9.1/mutex.lock’
komodo: debug: acquired mutex: fd=3
komodo: error: error creating ‘/home/grieve/.komodoide’: File exists
komodo: error: could not determine the user data dir

while I have NOT yet solve this, I have determined that the problem seems to be
connected w NFS. In this work environment, /home is NFS mounted from a central
server.

I created a local account w $HOME=/lhome/dragon
The komodo binary started w/o problem.

This is unfortunate to say the least.
I normally work on a Mac w Yosemite, & SMB mounts; however w komodo 9.1 the editor started
adding random amounts of NULLs to the file. So I thought I edit on the host which owns the file (CentOS )
but cannot work with NFS ? is komodo some how tuned for stand alone systems?

hi @gve, sorry for taking SO LONG to respond. This topic had just come up on the bug tracker and I found this thread. It appears I missed your response last year, my apologies.

After a bit of googling I found this error, which seems quite relevant: https://bugzilla.redhat.com/show_bug.cgi?id=625544

Could you see if the steps to reproduce give you the same error as described there?

ie.

Steps to Reproduce:

  1. mount some nfs file system.
  2. touch test1 test2
  3. ls -lahZ test?
    -rw-rw-r–. mark mark system_u:object_r:nfs_t:s0 test1
    -rw-rw-r–. mark mark system_u:object_r:nfs_t:s0 test2
  4. $ cp --preserve=context test1 test2
    cp: failed to set the security context of test2' tosystem_u:object_r:nfs_t:s0’: Operation not supported

Actual results:

Preserving selinux security context fails.

Expected results:

Preserving selinux security context succeeds.