Date: Fri, 23 Apr 1999 09:23:52 -0500 (CDT) From: Jonathan Fosburgh <wotan@fosburgh.dyndns.org> To: justin@csad.coventry.ac.uk Cc: questions@FreeBSD.ORG Subject: Re: Xi's Motif2.0 keybindings disappear after a week Message-ID: <Pine.BSF.4.05.9904230921400.50067-100000@fosburgh.dyndns.org> In-Reply-To: <199904231410.PAA14157@mascarpone.coventry.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 23 Apr 1999, Justin Murdock wrote: > I've been running Xi graphics' mwm for a 6 months now, but > after about a week the root menus and keybindings fail. > > Things that might be of influence: > I run 2.2.7-RELEASE, Xemacs 20.4, xmysql, xterms, > xautolock with xlockmore, and display SGI netscape sessions. > > This is a fairly typical session: > last pid: 27862; load averages: 0.11, 0.16, 0.24 14:49:21 > 53 processes: 1 running, 48 sleeping, 4 stopped > CPU states: 6.9% user, 0.0% nice, 17.7% system, 1.0% interrupt, 74.4% idle > Mem: 48M Active, 16M Inact, 17M Wired, 14M Cache, 7932K Buf, 29M Free > Swap: 448M Total, 51M Used, 397M Free, 11% Inuse > > 1) How do I rebind them? > 2) anybody else have this problem? > 3) should I replace the symbolic link that redirects libc.so.2.2 to > /usr/lib/libc.so.3.1? > 4) it was just a hack to get it working. > 5) where would I get libc.so.2.2 from? > > > dmesg: > CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX> > real memory = 134217728 (131072K bytes) > avail memory = 128770048 (125752K bytes) > DEVFS: ready for devices > Probing for devices on PCI bus 0: > chip0 <generic PCI bridge (vendor=1106 device=0597 subclass=0)> rev 4 on pci0:0:0 > chip1 <generic PCI bridge (vendor=1106 device=8598 subclass=4)> rev 0 on pci0:1:0 > chip2 <generic PCI bridge (vendor=1106 device=0586 subclass=1)> rev 65 on pci0:7:0 > pci0:7:1: VIA Technologies, device=0x0571, class=storage (ide) [no driver assigned] > chip3 <generic PCI bridge (vendor=1106 device=3040 subclass=128)> rev 16 on pci0:7:3 > > > xdpyinfo: > name of display: bottom:0.0 > version number: 11.0 > vendor string: The XFree86 Project, Inc > vendor release number: 3320 > maximum request size: 4194300 bytes > motion buffer size: 256 > bitmap unit, bit order, padding: 32, LSBFirst, 32 > image byte order: LSBFirst > number of supported pixmap formats: 2 > supported pixmap formats: > depth 1, bits_per_pixel 1, scanline_pad 32 > depth 24, bits_per_pixel 32, scanline_pad 32 > keycode range: minimum 8, maximum 134 > focus: window 0x400000e, revert to PointerRoot > number of extensions: 19 > BIG-REQUESTS > DOUBLE-BUFFER > DPMS > LBX > MIT-SCREEN-SAVER > MIT-SHM > MIT-SUNDRY-NONSTANDARD > RECORD > SECURITY > SHAPE > SYNC > XC-APPGROUP > XC-MISC > XFree86-DGA > XFree86-Misc > XFree86-VidModeExtension > XInputExtension > XKEYBOARD > XTEST > default screen number: 0 > number of screens: 1 > > screen #0: > dimensions: 1280x1024 pixels (433x347 millimeters) > resolution: 75x75 dots per inch > depths (1): 24 > root window id: 0x25 > depth of root window: 24 planes > number of colormaps: minimum 1, maximum 1 > default colormap: 0x21 > default number of colormap cells: 256 > preallocated pixels: black 0, white 16777215 > options: backing-store YES, save-unders YES > largest cursor: 64x64 > current input event mask: 0x70003c > ButtonPressMask ButtonReleaseMask EnterWindowMask > LeaveWindowMask SubstructureRedirectMask FocusChangeMask > PropertyChangeMask > number of visuals: 1 > default visual id: 0x20 > visual: > visual id: 0x20 > class: TrueColor > depth: 24 planes > available colormap entries: 256 per subfield > red, green, blue masks: 0xff0000, 0xff00, 0xff > significant bits in color specification: 8 bits > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > Is there a possibility that the numlock key is getting turned on? I don't use Xi but I have used the lesstif version of mwm and turning on numlock does cause problems with things like that. If that is the problem it should be an easy fix of just turning off numlock. -- Jonathan Fosburgh Geotechnician Snyder Oil Corporation Houston, TX Home Page: http://www.geocities.com/vienna/1498 Manager, FreeBSD Webring: http://www.geocities.com/vienna/1498/computer/freebsdring.html ICQ: 32742908 AIM: Namthorien To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9904230921400.50067-100000>