Author Topic: Install problem (of trial) and config question  (Read 1301 times)

nifisher

  • Junior Community Member
  • Posts: 2
  • Hero Points: 0
Install problem (of trial) and config question
« on: October 04, 2013, 03:18:10 pm »
I've been playing with the trail some this week and had a problem and a few quick questions.

For the questions, where can I configure what the OS Shell and the File Browser to launch are?  I don't have xTerm installed nor am I running a desktop environment so those two options fail to do anything useful currently.

And for the problem, when running the 'vsinst' script, it seems to run successfully up until it tries to verify licensing at which point it simply hangs.  The output to the screen reads as:
Code: [Select]
(5:1195)$ sudo ./vsinst


*************************************************************
*************************************************************
*           SlickEdit INSTALLATION PROGRAM           
*                       Version 18.0.1.2                   
*************************************************************
*************************************************************

Estimated disk space needed:  350 MB (including 50 MB for tag files)

<ENTER> to continue...

 END USER LICENSE AGREEMENT FOR SLICKEDIT(R) 2013
[... removed ...]
Do you agree to the above license terms? [yes or no]
yes

Install directory [/opt/slickedit/]:

You are installing version 18.0.1.2 on top of a previous installation.
You will no longer be able to run the previous version.  You may
lose some of your configuration changes. Configuration changes for
any SlickEdit menus and tool bars will be lost.
Continue [Y]?

Checking disk space. Please wait...

Some old global configuration files have been found.
Do you want a backup of these files [Y]?
Directory for old configuration files [/opt/slickedit/old]:

Unpacking files:
...
done
Checking distribution files. Please wait...
Updating user and group file ownership. Please wait...                 
Updating misc files. Please wait...
Compiling macros. Please wait...                                       
Fixing file privileges. Please wait...                                 
Running license manager to verify licensing...

A simple 'pkill vsinst' terminates it.   It exhibited the same behavior on both the original install and on overwriting the existing install (the above example).   Configuring the license manually and running the application worked fine though.  I can't seem to find a log file which might have more information (though, I may not have searched hard enough).

System information:
Code: [Select]
OS: Arch Linux
Kernel: x86_64 Linux 3.10.9-1-ARCH
Shell: bash 4.2.45
Resolution: 1680x1050
WM: OpenBox
WM Theme: Syscrash
GTK3 Theme: Orion
Disk: 100G / 151G (70%)
CPU: AMD Phenom II X6 1090T Processor @ 3.612GHz
 RAM: 5912MB / 15968MB

Rodney

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 734
  • Hero Points: 47
Re: Install problem (of trial) and config question
« Reply #1 on: October 04, 2013, 04:06:32 pm »
There are some window managers we have issues with. Fluxbox comes to mind, in addition to yours (Openbox). You may be the first Openbox user to report on this. If the problem is the same as on Fluxbox, then the License Manager dialog somehow gets unmapped after being shown. Obviously this is why you never see it. We are not sure why yet. Your workaround is the best solution.

Looks like we do not know what to run for Openbox for shell and filemanager commands. If you are inclined, you can hack the Slick-C source.

The Slick-C command run by Tools>OS Shell is 'launch_os_shell'.
The Slick-C command run by Tools>OS File Browser is 'explore'.

You can do a 'fp explore' from the SlickEdit command line to go to the source. It should be obvious from inspection what needs to be done.

Let us know, and thanks for the feedback!

++rodney

nifisher

  • Junior Community Member
  • Posts: 2
  • Hero Points: 0
Re: Install problem (of trial) and config question
« Reply #2 on: October 04, 2013, 06:57:05 pm »
Not shocked that Openbox would have similar problems to Fluxbox.  Let me know if there is a log or anything that I can send over that would be of use on that.

Figured there would be somewhere to set what executables to launch.  Both launch now, though I'll have to dig some more on how the terminal launches to clean up some errors at the top of the window.  I just set an exe name, and didn't clean up the rest for the time being.

Thank you for the guidance, sir.