[comp.unix.aix] 3003 info on other platforms?

paw@eleazar.dartmouth.edu (Pat Wilson) (04/19/91)

We're having trouble when we run info on platforms other than the
6000s - info will come up and be useable, but somehow (xmodmap call in
/usr/bin/info?) the keyboard mapping gets seriously wedged (remapped), 
making the X session useless thereafter.  

We don't see this problem with the GA info, and I don't remember it 
being a problem under 3002.  Of course, this /usr/bin/info is new
for 3003...  

Has anyone else seen this?  Do you have a work-around?  Is it fixed
(again) in 3005?

Thanks.

-- 
Pat Wilson
Systems Manager, Project NORTHSTAR
paw@northstar.dartmouth.edu

dave@visual1.jhuapl.edu (Dave Weintraub) (04/19/91)

In article <1991Apr19.143446.28123@dartvax.dartmouth.edu>, paw@eleazar.dartmouth.edu (Pat Wilson) writes:
|> We're having trouble when we run info on platforms other than the
|> 6000s - ... 
|> the keyboard mapping gets seriously wedged (remapped), 
|> making the X session useless thereafter.    
|> 
|> Has anyone else seen this?  
|> -- 
|> Pat Wilson
|> Systems Manager, Project NORTHSTAR
|> paw@northstar.dartmouth.edu

We had the same problem.  We were told that this is expected behavior;
the APAR is still open (5X762).

Dave Weintraub    dave@visual2.jhuapl.edu

jona@iscp.Bellcore.COM (Jon Alperin) (04/20/91)

Here's one for the FAQ:


In article <1991Apr19.143446.28123@dartvax.dartmouth.edu>, paw@eleazar.dartmouth.edu (Pat Wilson) writes:
|> We're having trouble when we run info on platforms other than the
|> 6000s - info will come up and be useable, but somehow (xmodmap call in
|> /usr/bin/info?) the keyboard mapping gets seriously wedged (remapped), 
|> making the X session useless thereafter.  
|> 
|> We don't see this problem with the GA info, and I don't remember it 
|> being a problem under 3002.  Of course, this /usr/bin/info is new
|> for 3003...  
|> 
|> Has anyone else seen this?  Do you have a work-around?  Is it fixed
|> (again) in 3005?
|> 
|> Thanks.
|> 
|> -- 
|> Pat Wilson
|> Systems Manager, Project NORTHSTAR
|> paw@northstar.dartmouth.edu

There was a bug in the info script. Change the xrdb to xmodmap.

-- 
Jon Alperin
Bell Communications Research

---> Internet: jona@iscp.bellcore.com
---> Voicenet: (908) 699-8674
---> UUNET: uunet!bcr!jona

* All opinions and stupid questions are my own *

dave@visual1.jhuapl.edu (Dave Weintraub) (04/20/91)

In article <1991Apr19.184111.15942@bellcore.bellcore.com>, jona@iscp.Bellcore.COM (Jon Alperin) writes:

|> In article <1991Apr19.143446.28123@dartvax.dartmouth.edu>, paw@eleazar.dartmouth.edu (Pat Wilson) writes:
|> |> We're having trouble when we run info on platforms other than the
|> |> 6000s - info will come up and be useable, but somehow (xmodmap call in
|> |> /usr/bin/info?) the keyboard mapping gets seriously wedged (remapped), 
|> |> making the X session useless thereafter.  
|> |> 

|> There was a bug in the info script. Change the xrdb to xmodmap 
|> Jon Alperin
|> 
We did.  We still have the problem described.
Thanks, but any other ideas?

Dave Weintraub

ejk@ux2.cso.uiuc.edu (Ed Kubaitis - CSO ) (04/21/91)

  ||> |> We're having trouble when we run info on platforms other than the
  ||> |> 6000s - info will come up and be useable, but somehow (xmodmap call in
  ||> |> /usr/bin/info?) the keyboard mapping gets seriously wedged (remapped), 
  ||> |> making the X session useless thereafter.  
  ||> |> 
  |
  ||> There was a bug in the info script. Change the xrdb to xmodmap 
  ||> Jon Alperin
  ||> 
  |We did.  We still have the problem described.
  |Thanks, but any other ideas?

When we had trouble due to the xrdb in the script, we commented it out
rather than changing it to xmodmap as recommended. We have had no keyboard 
mapping problems with either IBM or non-IBM servers. 

If you're running info on some non-IBM servers (such as NCD & HP) but using 
an IBM system as a font server, you may also have a problem caused by info
tampering with your server's font path.

IMO, clients should keep hands off of the server font path, key-mapping,
resource database, etc. Modifying these are the province of the user 
or a display manager running on the user's behalf. At least, Info should 
provide an option to bypass these favors.

----------------------------------
Ed Kubaitis (ejk@ux2.cso.uiuc.edu)
Computing Services Office - University of Illinois, Urbana