Re: Window Manager trouble/Thanks
Problem finally resolved. I think what went wrong was that I did an apt-get remove on wmaker soon after upgrade, and emptied some of the directories *by hand* when I saw that they weren't going away (because not empty). In retrospect this was a boneheaded thing to do, but it seemed like a good idea at the time :ox I finally did a dpkg --purge on wmaker, then reinstalled, which did the trick. Thanks for the help and patience. Once again I have learned a bundle. G _ | // G l e n n B e c k e r| | // I don't wanna kill my china pig. | // -- Captain Beefheart | | // [EMAIL PROTECTED] | _| At 5:32pm on Sat, 3 Feb 2001, Erik Steffl wrote: Glenn Becker wrote: OK, Here is what I get when I try to start WindowMaker into a vanilla X display: install: cannot stat `/etc/GNUstep/Defaults/WindowMaker': No such file or directory And indeed, there is no such file there. Which says to me that something is wrong with the wmaker installation; however, I have done apt-get remove on wmaker a few times, and nothing has changed. Weird. that's strange, on my system: jojda:~dpkg -S /etc/GNUstep/Defaults/WindowMaker wmaker: /etc/GNUstep/Defaults/WindowMaker and the file is indeed there. do you get any errors when trying to install wmaker? did you try to purge it and then reinstall? what do you get when you run the above dpkg command? there are quite a few active bugs against wmaker pacage, lot of them over one year old, maybe it's not even maintained anymore? fvwm is no longer a problem because there was just an upgrade in testing and the new package works ok. sawmill I may just have to live without. G ... erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Window Manager trouble/Thanks
Hi, Excuse my continuing X density. :-) When I run plain X from root, I get a grey screen and X cursor -- which moves fine -- but nothing else. Either a) I just don't know how to pop up a console window from this bare display, or b) I should be getting more than this, and this is a clue to whatever's wrong. I have included an X.err file below ... it records me starting plain X up from root, then CTRL-ALT-BKSPing to down it. Second, of the WMs I have installed, here is a breakdown of what works and what doesn't -- thought there might be some common gnd between the members of each set that would provide a clue: Works: Enlightenment, icewm, blackbox, twm, AfterStep Classic Doesn't Work: wmaker, fvwm, sawmill I'm most interested in this phenom as a sign of something larger wrong with my system. How can a bloated beast like Enlightenment run flawlessly when those others don't? WMaker is my favorite WM but I suppose I can learn to live w/o it ... but what is happening here? And why *should* I live w/o WMaker ... if I don't want to? :-) G Here is the X.err file: XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.18 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Sat Feb 3 06:56:34 2001 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor NEC (**) | |--Device Voodoo3 (generic) (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) XKB: rules: xfree86 (**) XKB: model: pc101 (**) XKB: layout: us (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.0.2, module version = 0.1.0 (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.0.2, module version = 0.1.0 (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (--) PCI:*(0:14:0) 3Dfx Interactive Voodoo3 rev 1, Mem @ 0xf400/25, 0xfc00/25, I/O @ 0x1000/8 (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.a (II) Module freetype: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.1.8 (II) Loading /usr/X11R6/lib/modules/drivers/tdfx_drv.o (II) Module tdfx: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 (II) TDFX: Driver for 3dfx Banshee/Voodoo3 chipsets: 3dfx Banshee, 3dfx Voodoo3, 3dfx Voodoo5 (--) Assigning device section with no busID to primary device (--) Chipset 3dfx Voodoo3 found (II) Loading /usr/X11R6/lib/modules/libvgahw.a (II) Module vgahw: vendor=The XFree86 Project compiled for 4.0.2, module version = 0.1.0 (II) Loading /usr/X11R6/lib/modules/linux/libint10.a (II) Module int10: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 (II) TDFX(0): Softbooting the board (through the int10 interface). (II) TDFX(0): Primary V_BIOS segment is: 0xc000 (II) TDFX(0): Softbooting the board succeeded. (**) TDFX(0): Depth 16, (--) framebuffer bpp 16 (==) TDFX(0): RGB weight 565 (==) TDFX(0): Default visual is TrueColor (--) TDFX(0): Chipset: 3dfx Voodoo3 (--) TDFX(0): Linear framebuffer at 0xFC00 (--) TDFX(0): MMIO registers at addr 0xF400 (--) TDFX(0): PIO registers at addr 0x1000 (--) TDFX(0): VideoRAM: 16384 kByte Mapping 32768 kByte (==) TDFX(0): Using gamma correction (1.0, 1.0, 1.0) (II) TDFX(0): NEC: Using hsync
Re: Window Manager trouble/Thanks
Glenn Becker wrote: Hi, Excuse my continuing X density. :-) When I run plain X from root, I get a grey screen and X cursor -- which moves fine -- but nothing else. Either a) I just don't know how to pop up a console window from this bare display, or b) I should be getting more than this, and this is a clue to whatever's wrong. I have included an X.err file below ... it records me starting plain X up from root, then CTRL-ALT-BKSPing to down it. Second, of the WMs I have installed, here is a breakdown of what works and what doesn't -- thought there might be some common gnd between the members of each set that would provide a clue: Works: Enlightenment, icewm, blackbox, twm, AfterStep Classic Doesn't Work: wmaker, fvwm, sawmill I'm most interested in this phenom as a sign of something larger wrong with my system. How can a bloated beast like Enlightenment run flawlessly when those others don't? WMaker is my favorite WM but I suppose I can learn to live w/o it ... but what is happening here? And why *should* I live w/o WMaker ... if I don't want to? :-) What do you get when you run : $ update-alternatives --config x-window-manager -- ~~~
Re: Window Manager trouble/Thanks
What do you get when you run : $ update-alternatives --config x-window-manager -- ~~~ Here is what I get: There are 8 programs which provide `x-window-manager'. SelectionCommand --- +1/usr/bin/enlightenment 2/usr/bin/X11/asclassic 3/usr/bin/X11/fvwm2 4/usr/X11R6/bin/icewm 5/usr/bin/sawmill 6/usr/X11R6/bin/twm * 7/usr/bin/blackbox 8/usr/X11R6/bin/wmaker Enter to keep the default[*], or type selection number: ..this is *after* I selected blackbox (one of the WMs that work). Changing this selection does not change the non-functioning of WMaker. Thanks, Glenn
Re: Window Manager trouble/Thanks
Glenn Becker wrote: Hi, Excuse my continuing X density. :-) When I run plain X from root, I get a grey screen and X cursor -- which moves fine -- but nothing else. Either a) I just don't know how to pop up a console window from this bare display, or b) I should be getting more than this, and this is a clue to whatever's wrong. I have included an X.err file below ... it records me starting plain X up from root, then CTRL-ALT-BKSPing to down it. you're on a good way. you can use ctrl-alt-Fn (n is 1 - 6, usually) to go back to one of the virtual consoles, from there run fvwm -display :0, you can run any X client like this so if fvwm does not run, try xterm, it should work. now you can try to run various window managers from command line to see what error messages you get. if you do not know how to run the window manager, check it's menu file like this (you need to know the name of the package): dpkg -L fvwm|grep menu /usr/share/doc/fvwm/examples/post-hook.menu-form-exit /usr/lib/menu /usr/lib/menu/fvwm /etc/menu-methods /etc/menu-methods/fvwm the interesting one is /usr/lib/menu/fvwm: ... ?package(fvwm):\ needs=wm\ section=WindowManagers\ title=Fvwm\ longtitle=FVWM Windows manager (version 2.xx)\ command=/usr/bin/X11/fvwm2 ... so you would use following commandline to run it: /usr/bin/X11/fvwm2 -display :0 see if you get any error message, if not, switch to X server vt (ctrl-F7 for :0, ctrl-F8 for :1, usually) you can try all window managers like this, one after another (you cannot run more than one at a time) Second, of the WMs I have installed, here is a breakdown of what works and what doesn't -- thought there might be some common gnd between the members of each set that would provide a clue: Works: Enlightenment, icewm, blackbox, twm, AfterStep Classic Doesn't Work: wmaker, fvwm, sawmill I'm most interested in this phenom as a sign of something larger wrong with my system. How can a bloated beast like Enlightenment run flawlessly when those others don't? WMaker is my favorite WM but I suppose I can learn to live w/o it ... but what is happening here? And why *should* I live w/o WMaker ... if I don't want to? :-) try the method above, you should see the error messages. Here is the X.err file: XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.18 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Sat Feb 3 06:56:34 2001 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor NEC (**) | |--Device Voodoo3 (generic) (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) XKB: rules: xfree86 (**) XKB: model: pc101 (**) XKB: layout: us (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.0.2, module version = 0.1.0 (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.0.2, module version = 0.1.0 (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (--) PCI:*(0:14:0) 3Dfx Interactive Voodoo3 rev 1, Mem @ 0xf400/25, 0xfc00/25, I/O @ 0x1000/8 (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.a (II) Module freetype: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.1.8 (II) Loading /usr/X11R6/lib/modules/drivers/tdfx_drv.o (II) Module tdfx: vendor=The XFree86 Project
Re: Window Manager trouble/Thanks
OK, Here is what I get when I try to start WindowMaker into a vanilla X display: install: cannot stat `/etc/GNUstep/Defaults/WindowMaker': No such file or directory And indeed, there is no such file there. Which says to me that something is wrong with the wmaker installation; however, I have done apt-get remove on wmaker a few times, and nothing has changed. Weird. fvwm is no longer a problem because there was just an upgrade in testing and the new package works ok. sawmill I may just have to live without. G _ | // G l e n n B e c k e r| | // I don't wanna kill my china pig. | // -- Captain Beefheart | | // [EMAIL PROTECTED] | _| At 2:02pm on Sat, 3 Feb 2001, Erik Steffl wrote: Glenn Becker wrote: Hi, Excuse my continuing X density. :-) When I run plain X from root, I get a grey screen and X cursor -- which moves fine -- but nothing else. Either a) I just don't know how to pop up a console window from this bare display, or b) I should be getting more than this, and this is a clue to whatever's wrong. I have included an X.err file below ... it records me starting plain X up from root, then CTRL-ALT-BKSPing to down it. you're on a good way. you can use ctrl-alt-Fn (n is 1 - 6, usually) to go back to one of the virtual consoles, from there run fvwm -display :0, you can run any X client like this so if fvwm does not run, try xterm, it should work. now you can try to run various window managers from command line to see what error messages you get. if you do not know how to run the window manager, check it's menu file like this (you need to know the name of the package): dpkg -L fvwm|grep menu /usr/share/doc/fvwm/examples/post-hook.menu-form-exit /usr/lib/menu /usr/lib/menu/fvwm /etc/menu-methods /etc/menu-methods/fvwm the interesting one is /usr/lib/menu/fvwm: ... ?package(fvwm):\ needs=wm\ section=WindowManagers\ title=Fvwm\ longtitle=FVWM Windows manager (version 2.xx)\ command=/usr/bin/X11/fvwm2 ... so you would use following commandline to run it: /usr/bin/X11/fvwm2 -display :0 see if you get any error message, if not, switch to X server vt (ctrl-F7 for :0, ctrl-F8 for :1, usually) you can try all window managers like this, one after another (you cannot run more than one at a time) Second, of the WMs I have installed, here is a breakdown of what works and what doesn't -- thought there might be some common gnd between the members of each set that would provide a clue: Works: Enlightenment, icewm, blackbox, twm, AfterStep Classic Doesn't Work: wmaker, fvwm, sawmill I'm most interested in this phenom as a sign of something larger wrong with my system. How can a bloated beast like Enlightenment run flawlessly when those others don't? WMaker is my favorite WM but I suppose I can learn to live w/o it ... but what is happening here? And why *should* I live w/o WMaker ... if I don't want to? :-) try the method above, you should see the error messages. Here is the X.err file: XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.18 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Sat Feb 3 06:56:34 2001 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor NEC (**) | |--Device Voodoo3 (generic) (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) XKB: rules: xfree86 (**) XKB: model: pc101 (**) XKB: layout: us (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (II)
Re: Window Manager trouble/Thanks
Glenn Becker wrote: OK, Here is what I get when I try to start WindowMaker into a vanilla X display: install: cannot stat `/etc/GNUstep/Defaults/WindowMaker': No such file or directory And indeed, there is no such file there. Which says to me that something is wrong with the wmaker installation; however, I have done apt-get remove on wmaker a few times, and nothing has changed. Weird. that's strange, on my system: jojda:~dpkg -S /etc/GNUstep/Defaults/WindowMaker wmaker: /etc/GNUstep/Defaults/WindowMaker and the file is indeed there. do you get any errors when trying to install wmaker? did you try to purge it and then reinstall? what do you get when you run the above dpkg command? there are quite a few active bugs against wmaker pacage, lot of them over one year old, maybe it's not even maintained anymore? fvwm is no longer a problem because there was just an upgrade in testing and the new package works ok. sawmill I may just have to live without. G ... erik
Window Manager trouble/Thanks
Thanks to the help of the list, I have managed to whittle away many of the X problems that plagued me subsequent to an upgrade to testing. Wish I could express -- w/o being foofy -- how much this community has come to mean to me since moving to Debian some months ago. The support is tremendous, and it's all reflected by and on and in the distro itself, which as far as I'm concerned has no peer. The two things are so intertwined. I can only hope that I reach a level of proficiency that will allow me to help others as they have helped me. ANYhoo, the sole remaining problem is that half my window managers don't work any more. This wouldn't be such a big deal -- I don't *really* use 'em all -- if it weren't for the fact that one of the ones that no longer works is Window Maker, which is my favorite. Basically, when I try to switch to any of the 'problematic' WMs, X just fails. Goes away. And I'm back at a console prompt. The only line in the X error output that looks weird (to me) is the last one, which reads: Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! But that doesn't sound awful enough to make a WM fail. I have checked for that directory and it does exist ... what is supposed to happen here and what can I do to fix it? G _ | // G l e n n B e c k e r| | // I don't wanna kill my china pig. | // -- Captain Beefheart | | // [EMAIL PROTECTED] | _|
Re: Window Manager trouble/Thanks
Glenn Becker wrote: ... Basically, when I try to switch to any of the 'problematic' WMs, X just fails. Goes away. And I'm back at a console prompt. The only line in it looks like the WM dies (does not run or something similar). X often hangs on window manger (it's the last program, not run in bg and if it exits the X exits as well). try to run X only (might need to do it as root) and then run (from command line) the window manager of choice (the one that cause X to exit) and see what it says. use -display :0 option to startthe WM on X server 0, for examle: fvwm -display :0 erik
