Welcome to iraf.net Friday, May 17 2024 @ 02:56 AM GMT


 Forum Index > Archives > Sitemail Archives
 Error Message running xgterm from home directory
   
Anonymous: Guest
 06/21/2005 10:17PM (Read 2947 times)  



[hayden@educ401 hayden]$ pwd
/home/hayden
[hayden@educ401 hayden]$ ls
login.cl login.cl.OLD uparm
[hayden@educ401 hayden]$ xgterm
xgterm: error while loading shared libraries: libncurses.so.4: cannot open
shared object file: No such file or directory
[hayden@educ401 hayden]$ uname -a
Linux educ401 2.4.20-6 #1 Thu Feb 27 10:06:59 EST 2003 i686 i686 i386
GNU/Linux
[hayden@educ401 hayden]$

 
Anonymous: Guest
 06/21/2005 10:17PM  



Hello Unnamed IRAF User,
Try getting the binary distribution from ftp://iraf.noao.edu/pub/fitz/x11iraf-v1.3.2-bin.redhat.tar.gzThis should fix the 'h_errno' message but ximtool is still limited to
8-bit displays for the moment. The libncurses is a known problem explained
in the README file as:> -------------------------------------------
> March 31, 2003 -- NOTES for RedHat 8 Users.
> -------------------------------------------
>
> Users have reported two common problems using XGterm on RedHat 8
> systems:
>
> 1) An error message of the form
>
> xgterm:error while loading shared libraries: libncurses.so.4:
> cannot open shared file: No such object or directory
>
> Solution:
> This is a known problem with how the binary was built and RH7
> systems. The simplest solution is to just create a symlink to
> satisfy the dependency, i.e. as 'root' do
>
> # cd /usr/lib
> # ln -s libncurses.so.5 libncurses.so.4
>
> Alternatively you could recompile the system from the sources
>
> 2) The behavior that the xgterm window will appear briefly and then shut
> down with no error message.
>
> Solution:
> The workaround is to either start XGterm as "xgterm -ut" to disable
> this utmp entry, or else change the permissions on the binary as
> root using
>
> # chown root:utmp xgterm
> # chmod g+s xgterm
>
> This will make the binary setgid root and should give it the proper
> permissions to write a utmp entry. The reason 'xterm' doesn't require
> this is that it's linked against a special library which calls a
> different setgid root task to create the same entry.
Also, for recent Fedora systems you'll probably want a patched
version of the XGterm binary available from the http://iraf.noao.edu
iraf homepage.
Hope this helps, let us know if you still have problems.Cheers,
Mike Fitzpatrick

 
Anonymous: Guest
 06/21/2005 10:17PM  



[hayden@educ401 hayden]$ pwd
/home/hayden
[hayden@educ401 hayden]$ ls
login.cl login.cl.OLD uparm
[hayden@educ401 hayden]$ xgterm
xgterm: error while loading shared libraries: libncurses.so.4: cannot open
shared object file: No such file or directory
[hayden@educ401 hayden]$ uname -a
Linux educ401 2.4.20-6 #1 Thu Feb 27 10:06:59 EST 2003 i686 i686 i386
GNU/Linux
[hayden@educ401 hayden]$

 
Anonymous: Guest
 06/21/2005 10:17PM  



Hello Unnamed IRAF User,
Try getting the binary distribution from ftp://iraf.noao.edu/pub/fitz/x11iraf-v1.3.2-bin.redhat.tar.gzThis should fix the 'h_errno' message but ximtool is still limited to
8-bit displays for the moment. The libncurses is a known problem explained
in the README file as:> -------------------------------------------
> March 31, 2003 -- NOTES for RedHat 8 Users.
> -------------------------------------------
>
> Users have reported two common problems using XGterm on RedHat 8
> systems:
>
> 1) An error message of the form
>
> xgterm:error while loading shared libraries: libncurses.so.4:
> cannot open shared file: No such object or directory
>
> Solution:
> This is a known problem with how the binary was built and RH7
> systems. The simplest solution is to just create a symlink to
> satisfy the dependency, i.e. as 'root' do
>
> # cd /usr/lib
> # ln -s libncurses.so.5 libncurses.so.4
>
> Alternatively you could recompile the system from the sources
>
> 2) The behavior that the xgterm window will appear briefly and then shut
> down with no error message.
>
> Solution:
> The workaround is to either start XGterm as "xgterm -ut" to disable
> this utmp entry, or else change the permissions on the binary as
> root using
>
> # chown root:utmp xgterm
> # chmod g+s xgterm
>
> This will make the binary setgid root and should give it the proper
> permissions to write a utmp entry. The reason 'xterm' doesn't require
> this is that it's linked against a special library which calls a
> different setgid root task to create the same entry.
Also, for recent Fedora systems you'll probably want a patched
version of the XGterm binary available from the http://iraf.noao.edu
iraf homepage.
Hope this helps, let us know if you still have problems.Cheers,
Mike Fitzpatrick

 
   

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login