Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem
Dear Stuart, I tried the two things you suggested - the same libreoffice problems & same message occurred with a freshly-created default user. The pkg_info list you indicated as helpful is attached. I have cc'ed this to ports as you suggested. regards with gratitude, cal. PS the original email describing the problem is appended below for interested ports@ readers. ___ From: owner-m...@openbsd.org on behalf of Stuart Henderson Sent: Monday, 26 September 2022 11:27 PM To: misc@openbsd.org Subject: Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem On 2022-09-25, Luke A. Call wrote: > Details in case it helps: > https://marc.info/?l=openbsd-misc&m=161280915705719&w=2 > https://marc.info/?l=openbsd-bugs&m=164814366002554&w=2 I think I tried to read that bugs@ report before but got totally bogged down in all the detail about how you use a special script for pkg_add etc The packages you talked about as being necessary were I think devhelp and gsettings-desktop-schemas libreoffice's chain of dependencies already includes gsettings-desktop-schemas and libreoffice is running fine here without devhelp, so there must be something other than just those involved It would be helpful to have a list of all packages installed on a machine where it is failing. (full output of "pkg_info -q"). Also try to replicate with a newly created user i.e. so it is isolated from the contents of config files in your home directory. Please send reports about ports to po...@openbsd.org and/or the port maintainer. They are more likely to get seen there than on bugs@, and *much* more likely to get seen there than on misc. ___ Original message: ___ Dear OBSDer's - I am running 7.1 with out of the box FVWM. Since this Sunday morning libreoffice has crashed whenever I try to either open an existing file or create a new file in libreoffice writer. When opening it allows file selection but then crashes. (Below I have put the crash message ex launching terminal, the messages from a pkg_add -u, and a dmesg). I have tried the following remedies with the same result: opening different files, updating all packages with doas pkg_add -u (looked promising as there was a libreoffice update), rebooting a few times, syspatching again (first attempt at using libreoffice since applying patch 10_expat yesterday? or Friday?), and also opening the safe mode of libreoffice. The same result seems to occur. I tried to run an doas EXPORT PYTHONHOME [:] but have no idea what should be set as and and how the grammar should quite be. In accord with requested convention, there is a dmesg at the end of the file. Any help gratefully received. (Sorry if this is a stupid problem or if the information here is unhelpfully insufficient.) regards, Cal message in terminal screen from which libreoffice was invoked: cfl$ libreoffice Warning: failed to launch javaldx - java may not function correctly Could not find platform independent libraries Consider setting $PYTHONHOME to [:] Python path configuration: PYTHONHOME = (not set) PYTHONPATH = '/usr/local/lib/libreoffice/program/../program' program name = 'python3' isolated = 0 environment = 1 user site = 1 import site = 1 sys._base_executable = '/usr/local/bin/python3' sys.base_prefix = '/usr/local' sys.base_exec_prefix = '/usr/local' sys.platlibdir = 'lib' sys.executable = '/usr/local/bin/python3' sys.prefix = '/usr/local' sys.exec_prefix = '/usr/local' sys.path = [ '/usr/local/lib/libreoffice/program/../program', '/usr/local/lib/python39.zip', '/usr/local/lib/python3.9', '/usr/local/lib/python3.9/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized LookupError: no codec search functions registered: can't find encoding Current thread 0x00b1d90594e8 (most recent call first): pthread_mutex_destroy on mutex with waiters! ___@@ The results of the pkg_add process - libreoffice was indeed updated: cfl$ doas pkg_add -u doas (cfl@cfl.modem) password: quirks-5.5 signed on 2022-09-24T12:39:42Z Collision in partial-webkitgtk4-2.36.8->webkitgtk4-2.36.8: the following files already exist /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSBase.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSContextRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSObjectRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSStringRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSTypedArray.h from webkitgtk4-2.36.8
Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem
On 2022-09-25, Luke A. Call wrote: > Details in case it helps: > https://marc.info/?l=openbsd-misc&m=161280915705719&w=2 > https://marc.info/?l=openbsd-bugs&m=164814366002554&w=2 I think I tried to read that bugs@ report before but got totally bogged down in all the detail about how you use a special script for pkg_add etc The packages you talked about as being necessary were I think devhelp and gsettings-desktop-schemas libreoffice's chain of dependencies already includes gsettings-desktop-schemas and libreoffice is running fine here without devhelp, so there must be something other than just those involved It would be helpful to have a list of all packages installed on a machine where it is failing. (full output of "pkg_info -q"). Also try to replicate with a newly created user i.e. so it is isolated from the contents of config files in your home directory. Please send reports about ports to po...@openbsd.org and/or the port maintainer. They are more likely to get seen there than on bugs@, and *much* more likely to get seen there than on misc.
Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem
Thank you - this is a helpful start and some tips to go on with, and the from-terminal opening might be a workaround for now. -cal. From: Luke A. Call Sent: Monday, 26 September 2022 12:39 AM To: Cal Ledsham ; misc@openbsd.org Subject: Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem Details in case it helps: https://marc.info/?l=openbsd-misc&m=161280915705719&w=2 https://marc.info/?l=openbsd-bugs&m=164814366002554&w=2 On 2022-09-25 08:24:44-0600, Luke A. Call wrote: > I had a similar problem where I could open files with LO if I typed them > on the command line when launching LO, but File / Open would crash when > choosing the file and hitting OK. But I don't think mine was > python-related. It seemed that my cleaning up by removing evidently unused > packages > removed something that was required for LO but not explicitly listed in > its dependencies. Fortunately I had been logging the output whenever I > ran pkd_delete, and could use that for reference. After a long process of > elimination, reinstalling things to see what would happen, I think it was one > of these that made it work again (though probably a different one for > you): > > (from most to least likely): devhelp gsettings-desktop-schemas > glib2-networking > (and probably not, but maybe caused some other package to be installed > that did it: gnome-desktop totem) > > The relevant email thread at the time is probably in the archives; I > never got a reply, IIRC. > > Good luck :) > > > On 2022-09-25 02:23:00+, Cal Ledsham wrote: > > Dear OBSDer's - > > I am running 7.1 with out of the box FVWM. Since this Sunday morning > > libreoffice has crashed whenever I try to either open an existing file or > > create a new file in libreoffice writer. When opening it allows file > > selection but then crashes. > > > > (Below I have put the crash message ex launching terminal, the messages > > from a pkg_add -u, and a dmesg). > > > > I have tried the following remedies with the same result: opening different > > files, updating all packages with doas pkg_add -u (looked promising as > > there was a libreoffice update), rebooting a few times, syspatching again > > (first attempt at using libreoffice since applying patch 10_expat > > yesterday? or Friday?), and also opening the safe mode of libreoffice. The > > same result seems to occur. I tried to run an doas EXPORT PYTHONHOME > > [:] > > but have no idea what should be set as and and how > > the grammar should quite be. > > > > In accord with requested convention, there is a dmesg at the end of the > > file. > > > > Any help gratefully received. > > > > (Sorry if this is a stupid problem or if the information here is > > unhelpfully insufficient.) > > > > regards, > > Cal > > > > message in terminal screen from which libreoffice was invoked: > > > > cfl$ libreoffice > > Warning: failed to launch javaldx - java may not function correctly > > Could not find platform independent libraries > > Consider setting $PYTHONHOME to [:] > > Python path configuration: > > PYTHONHOME = (not set) > > PYTHONPATH = '/usr/local/lib/libreoffice/program/../program' > > program name = 'python3' > > isolated = 0 > > environment = 1 > > user site = 1 > > import site = 1 > > sys._base_executable = '/usr/local/bin/python3' > > sys.base_prefix = '/usr/local' > > sys.base_exec_prefix = '/usr/local' > > sys.platlibdir = 'lib' > > sys.executable = '/usr/local/bin/python3' > > sys.prefix = '/usr/local' > > sys.exec_prefix = '/usr/local' > > sys.path = [ > >'/usr/local/lib/libreoffice/program/../program', > >'/usr/local/lib/python39.zip', > >'/usr/local/lib/python3.9', > >'/usr/local/lib/python3.9/lib-dynload', > > ] > > Fatal Python error: init_fs_encoding: failed to get the Python codec of the > > filesystem encoding > > Python runtime state: core initialized > > LookupError: no codec search functions registered: can't find encoding > > > > Current thread 0x00b1d90594e8 (most recent call first): > > > > pthread_mutex_destroy on mutex with waiters! > > >
Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem
Details in case it helps: https://marc.info/?l=openbsd-misc&m=161280915705719&w=2 https://marc.info/?l=openbsd-bugs&m=164814366002554&w=2 On 2022-09-25 08:24:44-0600, Luke A. Call wrote: > I had a similar problem where I could open files with LO if I typed them > on the command line when launching LO, but File / Open would crash when > choosing the file and hitting OK. But I don't think mine was > python-related. It seemed that my cleaning up by removing evidently unused > packages > removed something that was required for LO but not explicitly listed in > its dependencies. Fortunately I had been logging the output whenever I > ran pkd_delete, and could use that for reference. After a long process of > elimination, reinstalling things to see what would happen, I think it was one > of these that made it work again (though probably a different one for > you): > > (from most to least likely): devhelp gsettings-desktop-schemas > glib2-networking > (and probably not, but maybe caused some other package to be installed > that did it: gnome-desktop totem) > > The relevant email thread at the time is probably in the archives; I > never got a reply, IIRC. > > Good luck :) > > > On 2022-09-25 02:23:00+, Cal Ledsham wrote: > > Dear OBSDer's - > > I am running 7.1 with out of the box FVWM. Since this Sunday morning > > libreoffice has crashed whenever I try to either open an existing file or > > create a new file in libreoffice writer. When opening it allows file > > selection but then crashes. > > > > (Below I have put the crash message ex launching terminal, the messages > > from a pkg_add -u, and a dmesg). > > > > I have tried the following remedies with the same result: opening different > > files, updating all packages with doas pkg_add -u (looked promising as > > there was a libreoffice update), rebooting a few times, syspatching again > > (first attempt at using libreoffice since applying patch 10_expat > > yesterday? or Friday?), and also opening the safe mode of libreoffice. The > > same result seems to occur. I tried to run an doas EXPORT PYTHONHOME > > [:] > > but have no idea what should be set as and and how > > the grammar should quite be. > > > > In accord with requested convention, there is a dmesg at the end of the > > file. > > > > Any help gratefully received. > > > > (Sorry if this is a stupid problem or if the information here is > > unhelpfully insufficient.) > > > > regards, > > Cal > > > > message in terminal screen from which libreoffice was invoked: > > > > cfl$ libreoffice > > Warning: failed to launch javaldx - java may not function correctly > > Could not find platform independent libraries > > Consider setting $PYTHONHOME to [:] > > Python path configuration: > > PYTHONHOME = (not set) > > PYTHONPATH = '/usr/local/lib/libreoffice/program/../program' > > program name = 'python3' > > isolated = 0 > > environment = 1 > > user site = 1 > > import site = 1 > > sys._base_executable = '/usr/local/bin/python3' > > sys.base_prefix = '/usr/local' > > sys.base_exec_prefix = '/usr/local' > > sys.platlibdir = 'lib' > > sys.executable = '/usr/local/bin/python3' > > sys.prefix = '/usr/local' > > sys.exec_prefix = '/usr/local' > > sys.path = [ > >'/usr/local/lib/libreoffice/program/../program', > >'/usr/local/lib/python39.zip', > >'/usr/local/lib/python3.9', > >'/usr/local/lib/python3.9/lib-dynload', > > ] > > Fatal Python error: init_fs_encoding: failed to get the Python codec of the > > filesystem encoding > > Python runtime state: core initialized > > LookupError: no codec search functions registered: can't find encoding > > > > Current thread 0x00b1d90594e8 (most recent call first): > > > > pthread_mutex_destroy on mutex with waiters! > > >
Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem
I had a similar problem where I could open files with LO if I typed them on the command line when launching LO, but File / Open would crash when choosing the file and hitting OK. But I don't think mine was python-related. It seemed that my cleaning up by removing evidently unused packages removed something that was required for LO but not explicitly listed in its dependencies. Fortunately I had been logging the output whenever I ran pkd_delete, and could use that for reference. After a long process of elimination, reinstalling things to see what would happen, I think it was one of these that made it work again (though probably a different one for you): (from most to least likely): devhelp gsettings-desktop-schemas glib2-networking (and probably not, but maybe caused some other package to be installed that did it: gnome-desktop totem) The relevant email thread at the time is probably in the archives; I never got a reply, IIRC. Good luck :) On 2022-09-25 02:23:00+, Cal Ledsham wrote: > Dear OBSDer's - > I am running 7.1 with out of the box FVWM. Since this Sunday morning > libreoffice has crashed whenever I try to either open an existing file or > create a new file in libreoffice writer. When opening it allows file > selection but then crashes. > > (Below I have put the crash message ex launching terminal, the messages from > a pkg_add -u, and a dmesg). > > I have tried the following remedies with the same result: opening different > files, updating all packages with doas pkg_add -u (looked promising as there > was a libreoffice update), rebooting a few times, syspatching again (first > attempt at using libreoffice since applying patch 10_expat yesterday? or > Friday?), and also opening the safe mode of libreoffice. The same result > seems to occur. I tried to run an doas EXPORT PYTHONHOME > [:] > but have no idea what should be set as and and how the > grammar should quite be. > > In accord with requested convention, there is a dmesg at the end of the file. > > Any help gratefully received. > > (Sorry if this is a stupid problem or if the information here is unhelpfully > insufficient.) > > regards, > Cal > > message in terminal screen from which libreoffice was invoked: > > cfl$ libreoffice > Warning: failed to launch javaldx - java may not function correctly > Could not find platform independent libraries > Consider setting $PYTHONHOME to [:] > Python path configuration: > PYTHONHOME = (not set) > PYTHONPATH = '/usr/local/lib/libreoffice/program/../program' > program name = 'python3' > isolated = 0 > environment = 1 > user site = 1 > import site = 1 > sys._base_executable = '/usr/local/bin/python3' > sys.base_prefix = '/usr/local' > sys.base_exec_prefix = '/usr/local' > sys.platlibdir = 'lib' > sys.executable = '/usr/local/bin/python3' > sys.prefix = '/usr/local' > sys.exec_prefix = '/usr/local' > sys.path = [ >'/usr/local/lib/libreoffice/program/../program', >'/usr/local/lib/python39.zip', >'/usr/local/lib/python3.9', >'/usr/local/lib/python3.9/lib-dynload', > ] > Fatal Python error: init_fs_encoding: failed to get the Python codec of the > filesystem encoding > Python runtime state: core initialized > LookupError: no codec search functions registered: can't find encoding > > Current thread 0x00b1d90594e8 (most recent call first): > > pthread_mutex_destroy on mutex with waiters! >
Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem
Dear OBSDer's - I am running 7.1 with out of the box FVWM. Since this Sunday morning libreoffice has crashed whenever I try to either open an existing file or create a new file in libreoffice writer. When opening it allows file selection but then crashes. (Below I have put the crash message ex launching terminal, the messages from a pkg_add -u, and a dmesg). I have tried the following remedies with the same result: opening different files, updating all packages with doas pkg_add -u (looked promising as there was a libreoffice update), rebooting a few times, syspatching again (first attempt at using libreoffice since applying patch 10_expat yesterday? or Friday?), and also opening the safe mode of libreoffice. The same result seems to occur. I tried to run an doas EXPORT PYTHONHOME [:] but have no idea what should be set as and and how the grammar should quite be. In accord with requested convention, there is a dmesg at the end of the file. Any help gratefully received. (Sorry if this is a stupid problem or if the information here is unhelpfully insufficient.) regards, Cal message in terminal screen from which libreoffice was invoked: cfl$ libreoffice Warning: failed to launch javaldx - java may not function correctly Could not find platform independent libraries Consider setting $PYTHONHOME to [:] Python path configuration: PYTHONHOME = (not set) PYTHONPATH = '/usr/local/lib/libreoffice/program/../program' program name = 'python3' isolated = 0 environment = 1 user site = 1 import site = 1 sys._base_executable = '/usr/local/bin/python3' sys.base_prefix = '/usr/local' sys.base_exec_prefix = '/usr/local' sys.platlibdir = 'lib' sys.executable = '/usr/local/bin/python3' sys.prefix = '/usr/local' sys.exec_prefix = '/usr/local' sys.path = [ '/usr/local/lib/libreoffice/program/../program', '/usr/local/lib/python39.zip', '/usr/local/lib/python3.9', '/usr/local/lib/python3.9/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized LookupError: no codec search functions registered: can't find encoding Current thread 0x00b1d90594e8 (most recent call first): pthread_mutex_destroy on mutex with waiters! ___@@ The results of the pkg_add process - libreoffice was indeed updated: cfl$ doas pkg_add -u doas (cfl@cfl.modem) password: quirks-5.5 signed on 2022-09-24T12:39:42Z Collision in partial-webkitgtk4-2.36.8->webkitgtk4-2.36.8: the following files already exist /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSBase.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSContextRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSObjectRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSStringRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSTypedArray.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSValueRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JavaScript.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/WebKitAvailability.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCAutocleanups.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCClass.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCContext.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCDefines.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCException.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCOptions.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCValue.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCVirtualMachine.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCWeakValue.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/jsc.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/webkit2/WebKitApplicationInfo.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/webkit2/WebKitAuthenticationRequest.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/webkit2/WebKitAutocleanups.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/webkit2/WebKitAutomationSession.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/we
Re: FVWM terminal emulator transparency issue in -current
Thanks! I just made it run at opacity .55 and I LOVE IT! Thanks! On Mon, Feb 15, 2021 at 11:25 PM Thomas Frohwein wrote: > On Mon, Feb 15, 2021 at 05:03:55PM -0600, Luke Small wrote: > > I'm running fvwm window manager and I just switched to -current. Roxterm > is > > totally messed up, won't do transparent background and I tried > > xfce4-terminal and it says it won't do transparent backgrounds because > > compositing is disabled Sure first-world problems, but I REALLY want > > fvwm to do transparent terminal emulators! > > You can just run a compositor. xcompmgr(1) is in the X install. I > personally > use compton from the package of the same name. picom (also in packages) is > supposed to be a successor to compton. They allow more compositor tricks > than xompmgr. > > I've never got application's transparency settings to work well, so my > .kshrc (set in ENV in .profile) contains lines calling transset-df from > the package of the same name: > > [ -n "$XTERM_VERSION" ] && transset-df --id "$WINDOWID" 0.85 > /dev/null > [ -n "$KITTY_WINDOW_ID" ] && transset-df --id "$WINDOWID" 0.85 > /dev/null >
Re: FVWM terminal emulator transparency issue in -current
On Mon, Feb 15, 2021 at 05:03:55PM -0600, Luke Small wrote: > I'm running fvwm window manager and I just switched to -current. Roxterm is > totally messed up, won't do transparent background and I tried > xfce4-terminal and it says it won't do transparent backgrounds because > compositing is disabled Sure first-world problems, but I REALLY want > fvwm to do transparent terminal emulators! You can just run a compositor. xcompmgr(1) is in the X install. I personally use compton from the package of the same name. picom (also in packages) is supposed to be a successor to compton. They allow more compositor tricks than xompmgr. I've never got application's transparency settings to work well, so my .kshrc (set in ENV in .profile) contains lines calling transset-df from the package of the same name: [ -n "$XTERM_VERSION" ] && transset-df --id "$WINDOWID" 0.85 > /dev/null [ -n "$KITTY_WINDOW_ID" ] && transset-df --id "$WINDOWID" 0.85 > /dev/null
FVWM terminal emulator transparency issue in -current
I'm running fvwm window manager and I just switched to -current. Roxterm is totally messed up, won't do transparent background and I tried xfce4-terminal and it says it won't do transparent backgrounds because compositing is disabled Sure first-world problems, but I REALLY want fvwm to do transparent terminal emulators! -Luke
fullscreen iridium stops me scrolling to another fvwm virt. desktop!
fullscreen iridium browser often stops letting me scroll to another fvwm virtual desktop, but I never have that problem with firefox! Whats the deal? On iridium, I either have to click on the browser window border or I have to unmaximize the browser window to leave space between the browser window and the virtual desktop border. -Luke
Re: FVWM basic config file
This configuration rocks, both of them. I love FVWM. I think FVWM should dropped as the default WM, its old and clunky. I think it should be twm. On Sun, Nov 25, 2018 at 11:55 PM Ingo Schwarze wrote: > Hi Manuel, > > Manuel Solis wrote on Sun, Nov 25, 2018 at 08:50:23PM -0600: > > > I have read some post about getting along with the default WM, i mean > > complaining about configuring it, saying that the man page its dificult > > and stuff, and then saddly going to another WM. > > > > I my OpenBSD era (from 60 to date) i was using cwm but wondering why they > > say that Theo uses fvwm, so i wondered that maybe it is worth it to try. > > The default fvwm(1) is certainly not the best part of OpenBSD - the > code is old and crappy. > > I can't speak for Theo, but the reason i'm using it is nothing more > and nothing less than that i don't want to bother configuring a > window manager. If i have one complaint about the base fvwm(1) - > apart from the crappy code - it is that it is way too bloated and > has way too many features. For that reason, even though i'm rarely > using .dot-files for any programs (except git, mutt, and ssh, which > don't work at all without a config file), this is one of the few > programs where i do have my own config file. The point is to get > rid of all the horrible bloat in the default .fvwrc: > >$ grep -cv -e '^$' -e '^#' /usr/X11R6/lib/X11/fvwm/.fvwmrc > 378 >$ grep -cv -e '^$' -e '^#' /home/schwarze/.fvwmrc > 81 > > Yours, > Ingo > > >$ ls ~/.profile ~/.*shrc* ~/.ex* ~/.vi* > ls: /home/schwarze/.*shrc*: No such file or directory > ls: /home/schwarze/.ex*: No such file or directory > ls: /home/schwarze/.profile: No such file or directory > ls: /home/schwarze/.vi*: No such file or directory > >$ cat /home/schwarze/.fvwmrc > # .fvwmrc - fv window manager configuration script > # Ingo Schwarze, 10.6.2001 > # Version: Ingo Schwarze, 22.11.2010 > > > # standard settings > > # paths > ModulePath /usr/X11R6/lib/X11/fvwm > PixmapPath /usr/X11R6/include/X11/pixmaps > IconPath /usr/X11R6/include/X11/bitmaps > > # screens > DeskTopSize 1x1 > EdgeResistance 1 1 > EdgeScroll 0 0 > > # windows > WindowFont -adobe-times-bold-r-*-*-14-*-*-*-*-*-*-* > IconFont -adobe-helvetica-bold-r-*-*-10-*-*-*-*-*-*-* > AddToDecor Default HilightColor DarkRed Wheat > Style "*" UseDecor Default, Color Black/LightSteelBlue > Style "*" BorderWidth 7, HandleWidth 7 > Style "*" Icon unknown1.xpm, IconBox 0 -10 -280 -1 > Style "*" MWMFunctions, MWMDecor, HintOverride > Style "*" DecorateTransient, NoPPosition > Style "*" SmartPlacement, StubbornPlacement, SloppyFocus > > > # menus > > MenuStyle Black LightGrey DarkGrey > + -adobe-times-bold-r-*-*-12-*-*-*-*-*-*-* fvwm > > AddToMenu terminal > + "xterm" Exec xterm -ls -geometry 80x80 > + "usta" Exec xterm -T usta.de -geometry 80x80 -e /usr/bin/ssh usta > > AddToMenu window "window" Title > + "move%jmove.xpm%" Move > + "resize%jresize.xpm%" Resize > + "maximize%mini.maximize-horiz.xpm%" Maximize > + "raise%jraise.xpm%" Raise > + "lower%jlower.xpm%" Lower > + "iconify%mini.iconify.xpm%" Iconify > + "stick%mini.stick.xpm%" Stick > + "" Nop > + "list%jwindow.xpm%" WindowList > + "" Nop > + "refresh%mini.refresh.xpm%" RefreshWindow > + "close%mini.winXX-close.xpm%" Close > + "delete%mini.cut.xpm%" Delete > + "destroy%mini.destroy.xpm%" Destroy > > AddToMenu system "system" Title > + "xlock%mini.xlock.xpm%" Exec exec xlock -mode blank > + "recapture%mini.refresh.xpm%" Recapture > + "xrdb -load%jx.xpm%" Exec xrdb -load $HOME/.Xdefaults > + "restart%mini.excl.xpm" Restart fvwm > + "scrotwm" Restart scrotwm > + "quit%mini.exit.xpm%" Quit > > > # mouse > > ClickTime 750 > > # on the wallpaper > Mouse 1 R A Menu terminal Nop > Mouse 2 R A Menu window Nop > Mouse 3 R A Menu system Nop > > # i
Re: FVWM basic config file
Hi Manuel, Manuel Solis wrote on Sun, Nov 25, 2018 at 08:50:23PM -0600: > I have read some post about getting along with the default WM, i mean > complaining about configuring it, saying that the man page its dificult > and stuff, and then saddly going to another WM. > > I my OpenBSD era (from 60 to date) i was using cwm but wondering why they > say that Theo uses fvwm, so i wondered that maybe it is worth it to try. The default fvwm(1) is certainly not the best part of OpenBSD - the code is old and crappy. I can't speak for Theo, but the reason i'm using it is nothing more and nothing less than that i don't want to bother configuring a window manager. If i have one complaint about the base fvwm(1) - apart from the crappy code - it is that it is way too bloated and has way too many features. For that reason, even though i'm rarely using .dot-files for any programs (except git, mutt, and ssh, which don't work at all without a config file), this is one of the few programs where i do have my own config file. The point is to get rid of all the horrible bloat in the default .fvwrc: $ grep -cv -e '^$' -e '^#' /usr/X11R6/lib/X11/fvwm/.fvwmrc 378 $ grep -cv -e '^$' -e '^#' /home/schwarze/.fvwmrc 81 Yours, Ingo $ ls ~/.profile ~/.*shrc* ~/.ex* ~/.vi* ls: /home/schwarze/.*shrc*: No such file or directory ls: /home/schwarze/.ex*: No such file or directory ls: /home/schwarze/.profile: No such file or directory ls: /home/schwarze/.vi*: No such file or directory $ cat /home/schwarze/.fvwmrc # .fvwmrc - fv window manager configuration script # Ingo Schwarze, 10.6.2001 # Version: Ingo Schwarze, 22.11.2010 # standard settings # paths ModulePath /usr/X11R6/lib/X11/fvwm PixmapPath /usr/X11R6/include/X11/pixmaps IconPath /usr/X11R6/include/X11/bitmaps # screens DeskTopSize 1x1 EdgeResistance 1 1 EdgeScroll 0 0 # windows WindowFont -adobe-times-bold-r-*-*-14-*-*-*-*-*-*-* IconFont -adobe-helvetica-bold-r-*-*-10-*-*-*-*-*-*-* AddToDecor Default HilightColor DarkRed Wheat Style "*" UseDecor Default, Color Black/LightSteelBlue Style "*" BorderWidth 7, HandleWidth 7 Style "*" Icon unknown1.xpm, IconBox 0 -10 -280 -1 Style "*" MWMFunctions, MWMDecor, HintOverride Style "*" DecorateTransient, NoPPosition Style "*" SmartPlacement, StubbornPlacement, SloppyFocus # menus MenuStyle Black LightGrey DarkGrey + -adobe-times-bold-r-*-*-12-*-*-*-*-*-*-* fvwm AddToMenu terminal + "xterm" Exec xterm -ls -geometry 80x80 + "usta" Exec xterm -T usta.de -geometry 80x80 -e /usr/bin/ssh usta AddToMenu window "window" Title + "move%jmove.xpm%" Move + "resize%jresize.xpm%" Resize + "maximize%mini.maximize-horiz.xpm%" Maximize + "raise%jraise.xpm%" Raise + "lower%jlower.xpm%" Lower + "iconify%mini.iconify.xpm%" Iconify + "stick%mini.stick.xpm%" Stick + "" Nop + "list%jwindow.xpm%" WindowList + "" Nop + "refresh%mini.refresh.xpm%" RefreshWindow + "close%mini.winXX-close.xpm%" Close + "delete%mini.cut.xpm%" Delete + "destroy%mini.destroy.xpm%" Destroy AddToMenu system "system" Title + "xlock%mini.xlock.xpm%" Exec exec xlock -mode blank + "recapture%mini.refresh.xpm%" Recapture + "xrdb -load%jx.xpm%" Exec xrdb -load $HOME/.Xdefaults + "restart%mini.excl.xpm" Restart fvwm + "scrotwm" Restart scrotwm + "quit%mini.exit.xpm%" Quit # mouse ClickTime 750 # on the wallpaper Mouse 1 R A Menu terminal Nop Mouse 2 R A Menu window Nop Mouse 3 R A Menu system Nop # in the title bar of a window Mouse 0 1 A Menu window Close Mouse 1 T A Raise Mouse 2 T A Move Mouse 3 T A Lower Mouse 0 2 A Maximize-Func Mouse 0 4 A Iconify # at the edge of a window Mouse 0 SF A Resize # in an icon Mouse 1 I A Iconify Mouse 2 I A Move Mouse 3 I A Iconify # pager AddToFunc InitFunction"I" Module FvwmPager 0 9 AddToFunc RestartFunction "I" Module FvwmPager 0 9 Style "FvwmPager" StaysOnTop, Color DimGrey/LightGrey *FvwmPagerGeometry 60x560+0+0 *FvwmPagerRows 10 *FvwmPagerColu
FVWM basic config file
Hello Misc, I have read some post about getting along with the default WM, i mean complaining about configuring it, saying that the man page its dificult and stuff, and then saddly going to another WM. I my OpenBSD era (from 60 to date) i was using cwm but wondering why they say that Theo uses fvwm, so i wondered that maybe it is worth it to try. So i attach my .fvwmrc and i hope that will help someone to start tweaking it and get along with it and be happy with it. I think that the config file is basic enough to start (for me it helped to migrate from cwm) and has a good bindings that one might find useful as: - Control + arrow navigation between pages - Control + Meta + number to move window to page (i couldnt make it dinamically so it could work if its more than 9 pages, sorry about that) - Shift + Left/right to circulate focus between open windows (Like alt tab) - Control + Meta + arrows to snap window to left, right, maximize and iconify (that is my favorite) - Meta + d dmenu (pkg_add dmenu) - Meta + i screenshot ( pkg_add ImageMagick) - Meta + x close window - Control + Meta + p power off - Meta + t make it transparent (pkg_add transset-df) - Meta + m move window - It uses feh to set the wallpaper - It uses conky for basic info - It uses dmenu to fast start applications. I am eager to share it here since it works for the fvwm in base 64, i noticed that there are plenty config files online but they are meant for a newer fvwm that is not in OpenBSD and i couldnt make it work, even i was tempted to post a mail asking for Theo´s config file but i had the impression that the answer would be as fun and educational as always. Again, i hope that it helps. Manuel Solis # This is a customized file based on the bare bones sample .fvwm2rc/system.fvwm2rc # file for fvwm-2. It is the combination of hints for the other .fvwm2rc files # samples, as well as pointers from the various links on the official fvwm web # page (see the FAQ). For questions ask man page. Key Bindings # some simple default mouse bindings: # for the root window: Mouse1RANop Mouse 3R A Menu RootMenu Nop # for the title bar buttons: Mouse 01A Menu Window-Ops2 Close Mouse 02A Maximize-Func Mouse 04A Iconify # for other parts of the window/borders/icons: Mouse 1FAResize-or-Raise Mouse 1TSAMove-or-Raise Mouse 1IAMove-or-Iconify Mouse 2IAIconify Mouse 2FSTAMenu Window-Ops2 Nop Mouse 3TSIFARaiseLower # some simple default key bindings: # Arrow Keys # press arrow + control anywhere, and scroll by 1 page Key LeftACScroll -100 0 Key RightACScroll +100 +0 Key UpACScroll +0 -100 Key DownACScroll +0 +100 # press arrow + Meta anywhere, and Snap Right/Left, Maximize or iconify Key LeftACMLeftSnap Key RightACMRightSnap KeyUpACMMaximize 100 97 KeyDownACMIconify # Shift + arrow to circulate focos between programs # Similar to Alt + Tab Key Left ASPrev [*] FocusAndWarp Key RightASNext [*] FocusAndWarp KeySuper_RAAWindowList # Alt - Tab function to circulate focus between programs #Key Tab A M Next [*] FocusAndWarp # Key bindings # Press Meta + Keys bindings Key Return AMExec /usr/X11R6/bin/xterm Key dAMExec /usr/local/bin/dmenu_run Key iAMExec /usr/local/bin/import -window root $HOME/screenshot.jpg KeykAMExec setxkbmap -layout us KeylAMExec setxkbmap -layout es KeymAMMove #Exec /usr/X11R6/bin/xterm -e man fvwm Key tAMExec /usr/local/bin/transset-df -p -t 0.6 #transparent window KeyxWMDelete KeyxIMDestroy KeyrACMRestart /usr/X11R6/bin/fvwm # Press Meta + Ctrl + Keys bindings KeypACMExec /usr/bin/doas halt -p # Keyboard accelerators Key F1AMMenu RootMenu Key F2AMMenu Window-Ops Key F3AMWindowList FvwmWinList Key F4AMIconify Key F5AMMove Key F6AMResize #Key F7AMCirculateUp #Key F8AMCirculateDown Key1WCMMuevePagina 0 0 Key2WCMMuevePagina 1 0 Key3WCMMuevePagina 2 0 Key4WCMMuevePagina 0 1 Key5WCMMuevePagina 1 1 Key6WCMMuevePagina 2 1 Key7WCMMuevePagina 0 2 Key8WCMMuevePagina 1 2 Key9WCMMuevePagina 2 2 Global Settings # be sure to customize these paths for your installation: ModulePath
Re: disable fvwm screensaver?
Hi Jordan, On Thu, 12 Jul 2018 23:56:31 -0700 Jordan Geoghegan wrote: > 'xset s off && xset -dpms' seemed to do the trick. I popped it into > my ~/.profile and am now off to the races! Try removing xidle's timeout from your ~/.xinitrc file or /etc/X11/xdm/Xsession Or in your ~/.Xresources file, configure it with these parameters: XIdle.timeout XIdle.nice XLock.mode XLock.usefirst XLock.lockdelay XLock.nice See xidle(1) and xlock(1) Tweaks can also be done in your ~/.fvwmrc file (Sample: /usr/X11R6/lib/X11/fvwm/.fvwmrc) Cheers, -- Craig Skinner | http://linkd.in/yGqkv7
Re: disable fvwm screensaver?
On 07/12/18 18:34, Edgar Pettijohn III wrote: man xset I haven't used it to disable the screen saver, so I'm not sure the exact command. But you need something like: xset s off Hey Edgar, Thanks for help! 'xset s off && xset -dpms' seemed to do the trick. I popped it into my ~/.profile and am now off to the races! Cheers, Jordan
Re: disable fvwm screensaver?
On 07/12/18 20:19, Jordan Geoghegan wrote: Hello, Sorry for the noob question. I am having trouble disabling the screen saver / screen timeout for fvwm. I am using an OpenBSD machine as a video terminal for my CCTV system and need the screen to be on 24/7 so employees can see the camera playback. Unfortunately the screen blanks after a short time. I have done the RTFM dance, but I am feeling a little special right now-- I can't find any reference to screen timeout in the fvwm man page. How would one go about disabling the screen timeout on fvwm? Cheers, Jordan man xset I haven't used it to disable the screen saver, so I'm not sure the exact command. But you need something like: xset s off
disable fvwm screensaver?
Hello, Sorry for the noob question. I am having trouble disabling the screen saver / screen timeout for fvwm. I am using an OpenBSD machine as a video terminal for my CCTV system and need the screen to be on 24/7 so employees can see the camera playback. Unfortunately the screen blanks after a short time. I have done the RTFM dance, but I am feeling a little special right now-- I can't find any reference to screen timeout in the fvwm man page. How would one go about disabling the screen timeout on fvwm? Cheers, Jordan
Snapshot - fvwm virtual desktop still shows 6.2
Hello, I upgraded to the latest snapshot. I can see the major release is now 6.3, but fvwm's virtual desktop still shows OpenBSD 6.2. b1$ uname -a OpenBSD b1.example.org 6.3 GENERIC.MP#104 amd64 David
Re: font face in fvwm vs cwm
On Tue, May 30, 2017 at 06:22:27PM +0300, Mihai Popescu wrote: > Hello, > > I installed a snapshot of amd64 recently and I was using fvwm from > Openbsd base to install some packages. I even started Firefox to look > for some documentation. > > Later, I was going back to cwm since I use it daily. I have a feeling > that Firefox pages fonts in fvwm were more appealing that what I see > now in cwm. Is it just my imagination? > > Let's say i will go back to fvwm, but I see there is one fvwm in base, > shipped by default, but there is also a package called fvwm2. Could > you give me some recommandation for one of the other, please? > > Thanks. > I can't say that I've ever really noticed the fonts looking /nicer/ in fvwm vs any other of the traditional window managers. I did notice that using lavish desktop environments such as gnome or xfce usually resulted in a pleasant font experience. Check out the xsettingsd package, I have been using it with WindowMaker and now at least gtk apps look very nice outside a large environment. -ryan
Re: font face in fvwm vs cwm
On 30 May 2017 at 11:22, Mihai Popescu wrote: > Hello, > > I installed a snapshot of amd64 recently and I was using fvwm from > Openbsd base to install some packages. I even started Firefox to look > for some documentation. > > Later, I was going back to cwm since I use it daily. I have a feeling > that Firefox pages fonts in fvwm were more appealing that what I see > now in cwm. Is it just my imagination? > > Let's say i will go back to fvwm, but I see there is one fvwm in base, > shipped by default, but there is also a package called fvwm2. Could > you give me some recommandation for one of the other, please? I believe the fvwm that is installed with the system is quite old. The fvwm2 package is much more current and that's the one I would use if I had to choose between the two. But be aware -- this is a heavy-weight window manager. Configuring it a software development project.
font face in fvwm vs cwm
Hello, I installed a snapshot of amd64 recently and I was using fvwm from Openbsd base to install some packages. I even started Firefox to look for some documentation. Later, I was going back to cwm since I use it daily. I have a feeling that Firefox pages fonts in fvwm were more appealing that what I see now in cwm. Is it just my imagination? Let's say i will go back to fvwm, but I see there is one fvwm in base, shipped by default, but there is also a package called fvwm2. Could you give me some recommandation for one of the other, please? Thanks.
Re: Cannot Cleanly Exit FVWM / X Windows System
On 02/05/2016 03:41 AM, Dahlberg, David wrote: Am Donnerstag, den 04.02.2016, 16:40 -0500 schrieb Samir Parikh: If you investigate more closely, you will probably find out, that the system still works, just the graphics is fscked up: Try logging in via ssh, or shutting down the system by blindly typing into ttyC0. I know this is a stupid question but should I try logging into ttyC0 via CRTL-ALT-F1 while FVWM/X.org is still running or when I am in the original shell at login? When xenocara hangs, you may press e.g. Ctrl-Alt-F2 and enter blindly: | | | shutdown -p now In the other posting you were saying that pressing the power button shortly wouldn't work. At least on my 2015 Lenovo you need to press the power button for aprox. 2 seconds to send an ACPI powerdown. Any ideas or suggestions? 1) Use modesetting(4) in xorg.conf and wait for 5.9 Does not work on 5.8 yet -> See Jonathan Grey's comment. He is one of the devs, who ported the Broadwell support. So basically you have two options: If you want to stay on -stable: You have to work around the but. E.g. by starting the X server with startx and killing it from the console instead of regularly logging out. If you use XDM put the following into /etc/X11/xdm/xdm-config: | DisplayManager.*.resetSignal: 9 This still destroys the graphics on your consoles, but at least you get a shiny new X server login after exiting. In that situation, most graphical Desktop environments won't work, but the more simplistic ones do. The following setup worked okay'ish for me: xfce4, with xfce4-power-manager, no xscreensaver installed (xfce4-power-manager + xscreensaver triggers the bug) 3) Update to a recent snapshot. Ok. Thank you for the ideas. Perhaps I'll look into a recent snapshot if not other methods work The `problem' with a snapshot is that from then on you will be following current and keep on updating. It was bad luck for you to buy the wrong machine at the wrong time. I did the same though, knowing quite well that a lot of the OpenBSD developers use the same Laptop as me and thus will feel the same pain ;-) Regarding Broadwell Graphics support: Matthew Dillon and wrote it first for DragonflyBSD. The OpenBSD people could not directly import it, as the graphics stacks seem to differ significantly between Open and Dragonfly. After Matt Dillon also ported his Broadwell support to Linux, jsg@ and kettenis@ started to implement it in OpenBSD. This was shortly after the 5.8 release. Be assured that the Ubuntus and RedHats have not been faster either and AFAIK FreeBSD/PC-BSD is still working on Haswell support ;-) maybe OpenBSD is not the right OS for my skills and laptop. I hope that is not the case though!) Don't be afraid. Your problem is that you have bought the latest and greatest of models and open source support takes usually a few month. If you install 5.9 (to be released 1st of May), it will probably work fine for you. And about the simplicity: If it works, it is IMHO easier to master than most of the Linux distros that I know of. And definitively better documented :-) Cheers, David David, Jonathan -- Thanks for your help and tips. As you say, perhaps I've got the right laptop and the wrong time. Unfortunately, I don't have the technical skills to keep up with all of the updates with a snapshot or -RELEASE at this point. I was able to successfully run Fedora 23 and Ubuntu MATE 15.10 with no problems, including wireless and the screen brightness keys so I think I'll stay with that for now and look at putting on OpenBSD or FreeBSD on this older T61. I promise I'll be back with more questions as I really would like to make BSD work for me! Samir
Re: Cannot Cleanly Exit FVWM / X Windows System
On Thu, Feb 04, 2016 at 08:39:43AM +, David Dahlberg wrote: > Am Mittwoch, den 03.02.2016, 15:29 -0500 schrieb Samir Parikh: > > I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s > > with a fairly default installation. > > The T405s is a Broadwell. > > > I have a few issues to sort out but my first concern is that I cannot > > exit out of FVWM. I launch it via the command startx while logged in > > as > > root. When I go to exit (left mouse click on the desktop > Exit), > > the > > system just hangs which requires me to forcefully power down the > > laptop. > > If you investigate more closely, you will probably find out, that the > system still works, just the graphics is fscked up: Try logging in via > ssh, or shutting down the system by blindly typing into ttyC0. > > Broadwell graphics support was added a while ago. IIRC 5.8 should have > some basic support, but still a few bugs. By now (-current) it is petty > stable though. > > > Any ideas or suggestions? > > 1) Use modesetting(4) in xorg.conf and wait for 5.9 The update that added Broadwell related parts to inteldrm went in after 5.8. The modesetting driver requires kms support. So yes, use snapshots. > 2) Avoid the vulnerable code paths (e.g. "shutdown" in wm) > and wait for 5.9 > 3) Update to a recent snapshot.
Re: Cannot Cleanly Exit FVWM / X Windows System
Hi David -- Thanks for your reply! On 02/04/16 03:39, David Dahlberg wrote: Am Mittwoch, den 03.02.2016, 15:29 -0500 schrieb Samir Parikh: I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s with a fairly default installation. The T405s is a Broadwell. I have a few issues to sort out but my first concern is that I cannot exit out of FVWM. I launch it via the command startx while logged in as root. When I go to exit (left mouse click on the desktop > Exit), the system just hangs which requires me to forcefully power down the laptop. If you investigate more closely, you will probably find out, that the system still works, just the graphics is fscked up: Try logging in via ssh, or shutting down the system by blindly typing into ttyC0. I know this is a stupid question but should I try logging into ttyC0 via CRTL-ALT-F1 while FVWM/X.org is still running or when I am in the original shell at login? Broadwell graphics support was added a while ago. IIRC 5.8 should have some basic support, but still a few bugs. By now (-current) it is petty stable though. Any ideas or suggestions? 1) Use modesetting(4) in xorg.conf and wait for 5.9 2) Avoid the vulnerable code paths (e.g. "shutdown" in wm) and wait for 5.9 3) Update to a recent snapshot. Ok. Thank you for the ideas. Perhaps I'll look into a recent snapshot if not other methods work (I also have to get my wireless working so maybe OpenBSD is not the right OS for my skills and laptop. I hope that is not the case though!)
Re: Cannot Cleanly Exit FVWM / X Windows System
Hi Marcus -- Thank you for the quick reply. I'll try to provide some additional details and answers to your questions below: On 02/04/16 03:12, Marcus MERIGHI wrote: Hello Samir, spytho...@gmail.com (Samir Parikh), 2016.02.03 (Wed) 21:29 (CET): Hi Everyone! This is my first post to the mailing list as I am new to OpenBSD. I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s with a fairly default installation. I have a few issues to sort out but my first concern is that I cannot exit out of FVWM. I launch it via the command startx while logged in as root. https://en.wikipedia.org/wiki/Principle_of_least_privilege TL;DR: don't run as root. Use doas(1). Point noted. Right now, my main goal is to get OpenBSD working on this laptop as quickly as possible. Once I do, I will create additional users for day-to-day use but do understand your advice. When I go to exit (left mouse click on the desktop > Exit), the system just hangs which requires me to forcefully power down the laptop. Did you try 'ctrl+alt+backspace'? This should end X. Yes, that was another method I had used which I should have pointed out. Unfortunately, I got the same result in that FVWM just froze. Did you try a short power button press followed by some waiting for a clean shutdown? Yes. I waited for about 10 seconds, quickly pressed the laptop power button, and then waited for another 10 seconds but the system was still hung. Did you try to switch the tty back to ttyC0 (ctrl+alt+F1) when X/fvwm are making you wait? Yes. I tried pressing CTRL-ALT-F1 as well but with the same results, unfortunately. I am not using a login or display manager such as xdm(1) so I do not have an ~/.xinitrc or /etc/rc.conf.local file. During installation, I answered Yes to "Do you expect to run the X Window System?" and No to "Do you want the X Window System to be started by xdm(1)?" When you have restarted, the /var/log/Xorg.0.log file should still be there. Maybe that gives some clues. Please see my Xorg.0.log file below at the end of the email. And, from http://www.openbsd.org/mail.html: Include important information Don't waste everyone's time with a hopelessly incomplete question. No one other than you has the information needed to resolve your problem, it is better to provide more information than needed than not enough detail. Maybe someone already knew what you problem is if he/she only saw your dmesg? Bye, Marcus I will include that in the future. Thanks for keeping me honest! Here is the output of my Xorg.log. (The output of dmesg follows immediately after.) If the standard practice on this list is to use something like pastebin instead of email, please let me know as well. [40.874] (--) checkDevMem: using aperture driver /dev/xf86 [40.880] (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32) [40.894] X.Org X Server 1.16.4 Release Date: 2014-12-20 [40.894] X Protocol Version 11, Revision 0 [40.894] Build Operating System: OpenBSD 5.8 amd64 [40.894] Current Operating System: OpenBSD t450s.home 5.8 GENERIC.MP#1236 amd64 [40.894] Build Date: 16 August 2015 03:14:12AM [40.894] [40.894] Current version of pixman: 0.32.6 [40.894]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [40.894] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [40.894] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 4 16:09:46 2016 [40.896] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [40.896] (==) No Layout section. Using the first Screen section. [40.897] (==) No screen section available. Using defaults. [40.897] (**) |-->Screen "Default Screen Section" (0) [40.897] (**) | |-->Monitor "" [40.897] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [40.897] (==) Disabling SIGIO handlers for input devices [40.897] (==) Automatically adding devices [40.897] (==) Automatically enabling devices [40.897] (==) Not automatically adding GPU devices [40.902] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [40.902] (==) ModulePath set to "/usr/X11R6/lib/modules" [40.902] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [40.902] (II) Loader magic: 0x1964859356a
Re: Cannot Cleanly Exit FVWM / X Windows System
Am Mittwoch, den 03.02.2016, 15:29 -0500 schrieb Samir Parikh: > I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s > with a fairly default installation. The T405s is a Broadwell. > I have a few issues to sort out but my first concern is that I cannot > exit out of FVWM. I launch it via the command startx while logged in > as > root. When I go to exit (left mouse click on the desktop > Exit), > the > system just hangs which requires me to forcefully power down the > laptop. If you investigate more closely, you will probably find out, that the system still works, just the graphics is fscked up: Try logging in via ssh, or shutting down the system by blindly typing into ttyC0. Broadwell graphics support was added a while ago. IIRC 5.8 should have some basic support, but still a few bugs. By now (-current) it is petty stable though. > Any ideas or suggestions? 1) Use modesetting(4) in xorg.conf and wait for 5.9 2) Avoid the vulnerable code paths (e.g. "shutdown" in wm) and wait for 5.9 3) Update to a recent snapshot.
Re: Cannot Cleanly Exit FVWM / X Windows System
Hello Samir, spytho...@gmail.com (Samir Parikh), 2016.02.03 (Wed) 21:29 (CET): > Hi Everyone! This is my first post to the mailing list as I am new to > OpenBSD. > I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s with a > fairly default installation. > I have a few issues to sort out but my first concern is that I cannot exit > out of FVWM. I launch it via the command startx while logged in as root. https://en.wikipedia.org/wiki/Principle_of_least_privilege TL;DR: don't run as root. Use doas(1). > When I go to exit (left mouse click on the desktop > Exit), the system just > hangs which requires me to forcefully power down the laptop. Did you try 'ctrl+alt+backspace'? This should end X. Did you try a short power button press followed by some waiting for a clean shutdown? Did you try to switch the tty back to ttyC0 (ctrl+alt+F1) when X/fvwm are making you wait? > I am not using > a login or display manager such as xdm(1) so I do not have an ~/.xinitrc or > /etc/rc.conf.local file. During installation, I answered Yes to "Do you > expect to run the X Window System?" and No to "Do you want the X Window > System to be started by xdm(1)?" When you have restarted, the /var/log/Xorg.0.log file should still be there. Maybe that gives some clues. And, from http://www.openbsd.org/mail.html: Include important information Don't waste everyone's time with a hopelessly incomplete question. No one other than you has the information needed to resolve your problem, it is better to provide more information than needed than not enough detail. Maybe someone already knew what you problem is if he/she only saw your dmesg? Bye, Marcus > !DSPAM:56b26471126511186110957!
Cannot Cleanly Exit FVWM / X Windows System
Hi Everyone! This is my first post to the mailing list as I am new to OpenBSD. I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s with a fairly default installation. I have a few issues to sort out but my first concern is that I cannot exit out of FVWM. I launch it via the command startx while logged in as root. When I go to exit (left mouse click on the desktop > Exit), the system just hangs which requires me to forcefully power down the laptop. I am not using a login or display manager such as xdm(1) so I do not have an ~/.xinitrc or /etc/rc.conf.local file. During installation, I answered Yes to "Do you expect to run the X Window System?" and No to "Do you want the X Window System to be started by xdm(1)?" Any ideas or suggestions? Thanks in advance. Samir Parikh
Re: Fvwm
Edgar Pettijohn wrote: I have learned a lot about fvwm configuration Learn more from the fvwm support community: http://www.fvwm.org/contact/ -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
Fvwm
I'm trying to change the border color of Windows from the stock reddish color to another color. So far I have been unsuccessful. I have learned a lot about fvwm configuration and made a lot of other changes along the way. Any help is appreciated. Thanks, Edgar Sent from my iPad
Re: How to disable keyboard+mouse input in FVWM?
Hello, I also tried "Style * NeverFocus" in "/usr/X11R6/lib/X11/fvwm/.fvwmrc" but didn't worked :O Thanks! On 2014. 09. 13. at 1:03 PM, "Thomas Adam" wrote:On 12 September 2014 19:22, wrote: > Still didn't found a way to disable the mouse and keyboard. > > Any hints please? I asked you before what you meant by this, and suggested: Style * NeverFocus Is that not what you're after? It's a pretty odd request. Are you trying to build some kind of kiosk? I've written about such things in the past. -- Thomas Adam
Re: How to disable the mouse cursor in FVWM?
Hello, I tried several CursorMove and CursorStyle configs, none of them work. I don't have xorg.conf.d. Many thanks! On 2014. 09. 15. at 3:52 PM, "Piotr Isajew" wrote:Dnia 12.09.2014 somelooser3...@hushmail.com napisaÅ/a: > > we are using OpenBSD 5.5 with FVWM. > > How can we disable the mouse cursor? To disable input events from pointing device you could add something like that in /etc/X11/xorg.conf.d: Section "InputClass" Identifier "mouse-all" MatchIsPointer "on" Option "ignore" "yes" EndSection This however will not hide the pointer. For that I would try to use CursorMove command in FVWM to get cursor off-screen and/or CursorStyle to set cursors to something that will not disturb.
Re: How to disable keyboard+mouse input in FVWM?
On 12 September 2014 19:22, wrote: > Still didn't found a way to disable the mouse and keyboard. > > Any hints please? I asked you before what you meant by this, and suggested: Style * NeverFocus Is that not what you're after? It's a pretty odd request. Are you trying to build some kind of kiosk? I've written about such things in the past. -- Thomas Adam
Re: How to disable the mouse cursor in FVWM?
On 12 September 2014 19:18, wrote: > Hello, > > we are using OpenBSD 5.5 with FVWM. > > How can we disable the mouse cursor? > > So we shouldn't see the mouse cursor if we push the mouse a little. > > Is the solution somewhere here? : Not via FVWM directly. You might be able to use unclutter to always hide the pointer though. -- Thomas Adam
Re: How to disable keyboard+mouse input in FVWM?
On Fri, 12 Sep 2014 20:22:10 +0200 somelooser3...@hushmail.com wrote: > Still didn't found a way to disable the mouse and keyboard. > > Any hints please? > > Have a nice day! > On 2014. 09. 01. at 12:53 PM, somelooser3...@hushmail.com > wrote:Besides gluing the USB holes on a PC, how can I disable any > keyboard and any mouse input for a logged in user on an OpenBSD 5.5 > with FVWM? A rather odd request considering what can be done with physical access but anyway. man config e.g. disable wsmouse etc. in boot.conf
Re: How to disable keyboard+mouse input in FVWM?
Still didn't found a way to disable the mouse and keyboard. Any hints please? Have a nice day! On 2014. 09. 01. at 12:53 PM, somelooser3...@hushmail.com wrote:Besides gluing the USB holes on a PC, how can I disable any keyboard and any mouse input for a logged in user on an OpenBSD 5.5 with FVWM? Many thanks,
How to disable the mouse cursor in FVWM?
Hello, we are using OpenBSD 5.5 with FVWM. How can we disable the mouse cursor? So we shouldn't see the mouse cursor if we push the mouse a little. Is the solution somewhere here? : # grep -i mouse /usr/X11R6/lib/X11/fvwm/.fvwmrc ColormapFocus FollowsMouse Style "*" FocusFollowsMouse # some simple default mouse bindings: Mouse 1 R A Menu RootMenu Nop Mouse 2 R A Menu Window-Ops Nop Mouse 3 R A WindowList Mouse 0 1 A Menu Window-Ops2 Close Mouse 0 2 A Maximize-Func Mouse 0 4 A Iconify Mouse 1 F A Resize-or-Raise Mouse 1 TS A Move-or-Raise Mouse 1 I A Move-or-Iconify Mouse 2 I A Iconify Mouse 2 FST A Menu Window-Ops2 Nop Mouse 3 TSIFA RaiseLower + "Focus Follows Mouse" ChangeDefaultFocus FocusFollowsMouse + "Colormap Follows Mouse" ColormapFocus FollowsMouse *FvwmIconBoxMouse 1 Click RaiseLower *FvwmIconBoxMouse 1 DoubleClick Iconify *FvwmIconBoxMouse 2 Click Iconify -1, Focus *FvwmIconBoxMouse 3 Click Module FvwmIdent # ## Many thanks!
Re: How to disable keyboard+mouse input in FVWM?
On 1 September 2014 11:53, wrote: > Besides gluing the USB holes on a PC, how could I disable the keyboard > and mouse input for a logged in user on a OpenBSD 5.5 install with > FVWM? Style * NeverFocus -- Thomas Adam
How to disable keyboard+mouse input in FVWM?
Besides gluing the USB holes on a PC, how could I disable the keyboard and mouse input for a logged in user on a OpenBSD 5.5 install with FVWM? Many thanks,
Re: fvwm in base [was: "X -configure" segmentation fault]
> namely an implementation of the stuff that makes it possible to go fullscreen > and back. I remade .fvwmrc and set this to do what you wanted: Key F9 A M Maximize 100 100 There is a lot options to change and make fvwm just perfect. This takes the shell as an input and fullscreens it and, with repeated press (alt-F9), scales back. Best regards Zoran
Re: fvwm in base [was: "X -configure" segmentation fault]
Marc, On 15 September 2013 21:34, Marc Espie wrote: > On Sun, Sep 15, 2013 at 08:12:53PM +0100, Thomas Adam wrote: >> Hi, >> >> On 15 September 2013 11:48, Jérémie Courrèges-Anglas wrote: >> > James Griffin writes: >> > >> >> * Thomas Adam [2013-09-12 10:17:56 +0100]: >> >> >> >>> On 12 September 2013 06:10, Carson Chittom wrote: >> >>> > Zoran Kolic writes: >> >>> > >> >>> >> In fact, fvwm is in base part. >> >>> > >> >>> > A while ago, there was a message to misc from the fvwm developer about >> >>> > relicensing fvwm to allow a more recent version into base. I wonder if >> >>> > there is any status update? >> >>> >> >>> That is I. Unfortunately, FVWM cannot be relicensed. >> >>> >> >>> -- Thomas Adam >> >> >> >> If it can't be relicensed so an up-to-date version can be included in >> >> the base distribution then is there much point in it being there at all? >> >> People can simply use the package/port to install a supported version >> >> and the base distribution can simply have cwm as its main wm. >> > >> > Lots of people use the base fvwm. Which works fine for them, even if >> > older. Also fvwm is easier to work than cwm when you don't know either. >> >> I agree. The fact that there's a newer version of FVWM in ports is >> fine; FVWM in base, despite being older might be a minor nuisance, but >> not insurmountable. > > One thing we can do is re-do some of the useful code. Unfortunately, whilst this might work for very simple things, you're on to something of a lost cause in the grander scheme of things (read: you might as well just write your own window manager.) I'd dearly love to be able to relicence FVWM, but that requires something I cannot do for a twenty year project. It's a real shame, but there's code added there from all sorts of proprietary companies over the years, and contacting them in nigh impossible. > I've been playing a bit with the newer one. One thing I really would like > is for chromium (video) and fvwm to play nice with each other, namely an > implementation of the stuff that makes it possible to go fullscreen and back. > > Point me in the right direction, and I will look at rewriting this under > a reasonable licence... This is where it'll go south. You need EWMH support for this, and you can't just pick-and-choose the best bits and shoe-horn it in to that FVWM version at all easily. The undertaking would be quite big. -- Thomas Adam
Re: fvwm in base [was: "X -configure" segmentation fault]
On Sun, Sep 15, 2013 at 4:34 PM, Marc Espie wrote: > On Sun, Sep 15, 2013 at 08:12:53PM +0100, Thomas Adam wrote: >> Hi, >> >> On 15 September 2013 11:48, Jérémie Courrèges-Anglas wrote: >> > James Griffin writes: >> > >> >> * Thomas Adam [2013-09-12 10:17:56 +0100]: >> >> >> >>> On 12 September 2013 06:10, Carson Chittom wrote: >> >>> > Zoran Kolic writes: >> >>> > >> >>> >> In fact, fvwm is in base part. >> >>> > >> >>> > A while ago, there was a message to misc from the fvwm developer about >> >>> > relicensing fvwm to allow a more recent version into base. I wonder if >> >>> > there is any status update? >> >>> >> >>> That is I. Unfortunately, FVWM cannot be relicensed. >> >>> >> >>> -- Thomas Adam >> >> >> >> If it can't be relicensed so an up-to-date version can be included in >> >> the base distribution then is there much point in it being there at all? >> >> People can simply use the package/port to install a supported version >> >> and the base distribution can simply have cwm as its main wm. >> > >> > Lots of people use the base fvwm. Which works fine for them, even if >> > older. Also fvwm is easier to work than cwm when you don't know either. >> >> I agree. The fact that there's a newer version of FVWM in ports is >> fine; FVWM in base, despite being older might be a minor nuisance, but >> not insurmountable. > > One thing we can do is re-do some of the useful code. > > I've been playing a bit with the newer one. One thing I really would like > is for chromium (video) and fvwm to play nice with each other, namely an > implementation of the stuff that makes it possible to go fullscreen and back. > > Point me in the right direction, and I will look at rewriting this under > a reasonable licence... Enhanced Window Manager Hints.
Re: fvwm in base [was: "X -configure" segmentation fault]
On Sun, Sep 15, 2013 at 08:12:53PM +0100, Thomas Adam wrote: > Hi, > > On 15 September 2013 11:48, Jérémie Courrèges-Anglas wrote: > > James Griffin writes: > > > >> * Thomas Adam [2013-09-12 10:17:56 +0100]: > >> > >>> On 12 September 2013 06:10, Carson Chittom wrote: > >>> > Zoran Kolic writes: > >>> > > >>> >> In fact, fvwm is in base part. > >>> > > >>> > A while ago, there was a message to misc from the fvwm developer about > >>> > relicensing fvwm to allow a more recent version into base. I wonder if > >>> > there is any status update? > >>> > >>> That is I. Unfortunately, FVWM cannot be relicensed. > >>> > >>> -- Thomas Adam > >> > >> If it can't be relicensed so an up-to-date version can be included in > >> the base distribution then is there much point in it being there at all? > >> People can simply use the package/port to install a supported version > >> and the base distribution can simply have cwm as its main wm. > > > > Lots of people use the base fvwm. Which works fine for them, even if > > older. Also fvwm is easier to work than cwm when you don't know either. > > I agree. The fact that there's a newer version of FVWM in ports is > fine; FVWM in base, despite being older might be a minor nuisance, but > not insurmountable. One thing we can do is re-do some of the useful code. I've been playing a bit with the newer one. One thing I really would like is for chromium (video) and fvwm to play nice with each other, namely an implementation of the stuff that makes it possible to go fullscreen and back. Point me in the right direction, and I will look at rewriting this under a reasonable licence...
Re: fvwm in base [was: "X -configure" segmentation fault]
Hi, On 15 September 2013 11:48, Jérémie Courrèges-Anglas wrote: > James Griffin writes: > >> * Thomas Adam [2013-09-12 10:17:56 +0100]: >> >>> On 12 September 2013 06:10, Carson Chittom wrote: >>> > Zoran Kolic writes: >>> > >>> >> In fact, fvwm is in base part. >>> > >>> > A while ago, there was a message to misc from the fvwm developer about >>> > relicensing fvwm to allow a more recent version into base. I wonder if >>> > there is any status update? >>> >>> That is I. Unfortunately, FVWM cannot be relicensed. >>> >>> -- Thomas Adam >> >> If it can't be relicensed so an up-to-date version can be included in >> the base distribution then is there much point in it being there at all? >> People can simply use the package/port to install a supported version >> and the base distribution can simply have cwm as its main wm. > > Lots of people use the base fvwm. Which works fine for them, even if > older. Also fvwm is easier to work than cwm when you don't know either. I agree. The fact that there's a newer version of FVWM in ports is fine; FVWM in base, despite being older might be a minor nuisance, but not insurmountable. -- Thomas Adam
Re: fvwm in base [was: "X -configure" segmentation fault]
James Griffin writes: > * Thomas Adam [2013-09-12 10:17:56 +0100]: > >> On 12 September 2013 06:10, Carson Chittom wrote: >> > Zoran Kolic writes: >> > >> >> In fact, fvwm is in base part. >> > >> > A while ago, there was a message to misc from the fvwm developer about >> > relicensing fvwm to allow a more recent version into base. I wonder if >> > there is any status update? >> >> That is I. Unfortunately, FVWM cannot be relicensed. >> >> -- Thomas Adam > > If it can't be relicensed so an up-to-date version can be included in > the base distribution then is there much point in it being there at all? > People can simply use the package/port to install a supported version > and the base distribution can simply have cwm as its main wm. Lots of people use the base fvwm. Which works fine for them, even if older. Also fvwm is easier to work than cwm when you don't know either. -- jca | PGP: 0x06A11494 / 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
Re: fvwm in base [was: "X -configure" segmentation fault]
* Thomas Adam [2013-09-12 10:17:56 +0100]: > On 12 September 2013 06:10, Carson Chittom wrote: > > Zoran Kolic writes: > > > >> In fact, fvwm is in base part. > > > > A while ago, there was a message to misc from the fvwm developer about > > relicensing fvwm to allow a more recent version into base. I wonder if > > there is any status update? > > That is I. Unfortunately, FVWM cannot be relicensed. > > -- Thomas Adam If it can't be relicensed so an up-to-date version can be included in the base distribution then is there much point in it being there at all? People can simply use the package/port to install a supported version and the base distribution can simply have cwm as its main wm.
Re: fvwm in base [was: "X -configure" segmentation fault]
On 12 September 2013 06:10, Carson Chittom wrote: > Zoran Kolic writes: > >> In fact, fvwm is in base part. > > A while ago, there was a message to misc from the fvwm developer about > relicensing fvwm to allow a more recent version into base. I wonder if > there is any status update? That is I. Unfortunately, FVWM cannot be relicensed. -- Thomas Adam
Re: fvwm in base [was: "X -configure" segmentation fault]
On Thu, Sep 12, 2013 at 12:10:36AM -0500, Carson Chittom wrote: > Zoran Kolic writes: > > > In fact, fvwm is in base part. > > A while ago, there was a message to misc from the fvwm developer about > relicensing fvwm to allow a more recent version into base. I wonder if > there is any status update? > I do know he is stepping down from the development, forums and wiki of fvwm2 - announced earlier this week.
Re: fvwm in base [was: "X -configure" segmentation fault]
Zoran Kolic writes: > In fact, fvwm is in base part. A while ago, there was a message to misc from the fvwm developer about relicensing fvwm to allow a more recent version into base. I wonder if there is any status update?
Re: fvwm will not start since 12 June snapshot
On Sat, Jun 16, 2012 at 11:20:33PM -0500, eagir...@cox.net wrote:
> Since the 12 June snapshot I have been unable to run fvwm, either
> from xdm or using startx. Dmesg and Xorg.log below.
It should be fixed in the next snapshot.
> --
> Ed Ahlsen-Girard
> Ft. Walton Beach FL
>
> OpenBSD 5.1-current (GENERIC) #231: Tue Jun 12 18:31:26 MDT 2012
> t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel(R) Pentium(R) 4 CPU 2.66GHz ("GenuineIntel" 686-class) 2.66 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID,xTPR
> real mem = 1072713728 (1023MB)
> avail mem = 1044353024 (995MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 09/23/03, BIOS32 rev. 0 @ 0xffe90,
> SMBIOS rev. 2.3 @ 0xf0450 (56 entries)
> bios0: vendor Dell Computer Corporation version "A08" date 09/23/2003
> bios0: Dell Computer Corporation Dimension 4550
> acpi0 at bios0: rev 0
> acpi0: sleep states S0 S1 S3 S4 S5
> acpi0: tables DSDT FACP SSDT APIC BOOT ASF!
> acpi0: wakeup devices VBTN(S4) PCI0(S3) USB0(S3) USB1(S3) USB2(S3) PCI1(S5)
> KBD_(S3)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: apic clock running at 132MHz
> ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
> ioapic0: misconfigured as apic 0, remapped to apid 8
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 2 (PCI1)
> acpicpu0 at acpi0
> acpibtn0 at acpi0: VBTN
> bios0: ROM list: 0xc/0xf800 0xcf800/0x800 0xe/0x1800 0xe1800/0x2800
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82845G Host" rev 0x01
> intelagp0 at pchb0
> agp0 at intelagp0: aperture at 0xe800, size 0x800
> ppb0 at pci0 dev 1 function 0 "Intel 82845G AGP" rev 0x01
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 "NVIDIA GeForce4 MX 420" rev 0xa3
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x01: apic 8 int 16
> uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x01: apic 8 int 19
> uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x01: apic 8 int 18
> ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x01: apic 8 int 23
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> ppb1 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x81
> pci2 at ppb1 bus 2
> cmpci0 at pci2 dev 0 function 0 "C-Media Electronics CMI8738/C3DX Audio" rev
> 0x10: apic 8 int 21
> audio0 at cmpci0
> opl at cmpci0 not configured
> mpu at cmpci0 not configured
> vendor "Broadcom", unknown product 0x4212 (class communications subclass
> modem, rev 0x02) at pci2 dev 1 function 0 not configured
> fxp0 at pci2 dev 8 function 0 "Intel PRO/100 VE" rev 0x81, i82562: apic 8 int
> 20, address 00:07:e9:c3:c0:ba
> inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0
> ichpcib0 at pci0 dev 31 function 0 "Intel 82801DB LPC" rev 0x01
> pciide0 at pci0 dev 31 function 1 "Intel 82801DB IDE" rev 0x01: DMA, channel
> 0 configured to compatibility, channel 1 configured to compatibility
> wd0 at pciide0 channel 0 drive 0:
> wd0: 16-sector PIO, LBA, 57220MB, 117187500 sectors
> wd1 at pciide0 channel 0 drive 1:
> wd1: 16-sector PIO, LBA, 76319MB, 156301488 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
> wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: <_NEC, DVD+RW ND-1100A, 10GE> ATAPI 5/cdrom
> removable
> wd2 at pciide0 channel 1 drive 1:
> wd2: 16-sector PIO, LBA, 76319MB, 156301488 sectors
> cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> wd2(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 5
> ichiic0 at pci0 dev 31 function 3 "Intel 82801DB SMBus" rev 0x01: apic 8 int
> 17
> iic0 at ichiic0
> spdmem0 at iic0 addr 0x50: 512MB DDR SDRAM non-parity PC2700CL2.5
> spdmem1 at iic0 addr 0x51: 512MB DDR SDRAM non-parity PC2700CL2.5
> usb1 at uhci0: USB revision 1.0
> uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> usb2 at uhci1: USB revision 1.0
> uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> usb3 at uhci2: USB revision 1.0
> uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> isa0 at ichpcib0
> isadma0 at isa0
&g
fvwm will not start since 12 June snapshot
Since the 12 June snapshot I have been unable to run fvwm, either from xdm or
using startx. Dmesg and Xorg.log below.
--
Ed Ahlsen-Girard
Ft. Walton Beach FL
OpenBSD 5.1-current (GENERIC) #231: Tue Jun 12 18:31:26 MDT 2012
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) 4 CPU 2.66GHz ("GenuineIntel" 686-class) 2.66 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID,xTPR
real mem = 1072713728 (1023MB)
avail mem = 1044353024 (995MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 09/23/03, BIOS32 rev. 0 @ 0xffe90, SMBIOS
rev. 2.3 @ 0xf0450 (56 entries)
bios0: vendor Dell Computer Corporation version "A08" date 09/23/2003
bios0: Dell Computer Corporation Dimension 4550
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC BOOT ASF!
acpi0: wakeup devices VBTN(S4) PCI0(S3) USB0(S3) USB1(S3) USB2(S3) PCI1(S5)
KBD_(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 132MHz
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 8
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (PCI1)
acpicpu0 at acpi0
acpibtn0 at acpi0: VBTN
bios0: ROM list: 0xc/0xf800 0xcf800/0x800 0xe/0x1800 0xe1800/0x2800
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82845G Host" rev 0x01
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xe800, size 0x800
ppb0 at pci0 dev 1 function 0 "Intel 82845G AGP" rev 0x01
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "NVIDIA GeForce4 MX 420" rev 0xa3
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x01: apic 8 int 16
uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x01: apic 8 int 19
uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x01: apic 8 int 18
ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x01: apic 8 int 23
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb1 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x81
pci2 at ppb1 bus 2
cmpci0 at pci2 dev 0 function 0 "C-Media Electronics CMI8738/C3DX Audio" rev
0x10: apic 8 int 21
audio0 at cmpci0
opl at cmpci0 not configured
mpu at cmpci0 not configured
vendor "Broadcom", unknown product 0x4212 (class communications subclass modem,
rev 0x02) at pci2 dev 1 function 0 not configured
fxp0 at pci2 dev 8 function 0 "Intel PRO/100 VE" rev 0x81, i82562: apic 8 int
20, address 00:07:e9:c3:c0:ba
inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0
ichpcib0 at pci0 dev 31 function 0 "Intel 82801DB LPC" rev 0x01
pciide0 at pci0 dev 31 function 1 "Intel 82801DB IDE" rev 0x01: DMA, channel 0
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 57220MB, 117187500 sectors
wd1 at pciide0 channel 0 drive 1:
wd1: 16-sector PIO, LBA, 76319MB, 156301488 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <_NEC, DVD+RW ND-1100A, 10GE> ATAPI 5/cdrom
removable
wd2 at pciide0 channel 1 drive 1:
wd2: 16-sector PIO, LBA, 76319MB, 156301488 sectors
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
wd2(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 5
ichiic0 at pci0 dev 31 function 3 "Intel 82801DB SMBus" rev 0x01: apic 8 int 17
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 512MB DDR SDRAM non-parity PC2700CL2.5
spdmem1 at iic0 addr 0x51: 512MB DDR SDRAM non-parity PC2700CL2.5
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at ichpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
mtrr: Pentium Pro MTRR support
ulpt0 at uhub2 port 2 confi
Re: Failed to setup fvwm for antialiased Xft fonts
From: Richard Toohey > Welcome to OpenBSD. Thanks! > The installation? Boot off the CD and follow the instructions and OpenBSD > will be installed 5 minutes later. Yes, that's already done. I really meant 'configuring' the installation, not 'setting up'. Basically I am trying to make fvwm and others look nicer than the somewhat ugly defaults of the base. > Install an application - pkg_add Yes, I am familiar with this sort of package management - I used it in Arch Linux, were 'pacman' I believe was inspired by the *BSD system, like a lot of its structure. > Then go and do the reading. Right! I did read a lot before installing, but I was mainly concerned with hardware compatibility and also porting some applications I have written for Linux. Only hardware issue, so far, is lack of support for my ASUS Xonar sound card. Software wise, one of my apps fails when I enable multi-threading, so this may be an issue if I don't find the cause, likely something wrong in my amateurish self-taught programming. > Expect to still be reading and learning many years later - I am. Between the > man pages, the FAQs, the source, and your favourite search engine - it's > (usually!) all there. Yes, usable documentation is one of the more important attractions of OBSD for me. I have been frustrated with Linux documentation quite often, especially ALSA, which I need in some of my Ham Radio software. > Just remember - it's not Linux, it hasn't got the deep pockets (filled with > $$$s) of Ubuntu. Yeah, perhaps the micro$oft of Linux! > It's not dumbed down - it expects the end-user to do a bit of thinking - how > can it guess/assume what is required on your machine or how it should be > configured? No problem, the documentation as we agree is excellent, I usually find that the hardest thing is arriving at the right place! Here I find that chosing the right keywords for Google search is something of an art. > It's better at some things, worse at others, ahead in some ways, behind in others. It won't cure cancer, but no kittens or babies are harmed. > Only you can decide if it works for work in the way you need it to. Different jobs > need different tools. YMMV. I just need stability and a good software development environment, were OBSD should excel. I am getting tired of the relentless march of changes in a distro like Arch, although others are, as you say, more stable but 'dumbed down' > Good luck. Thanks! but I think its more a matter of hard work... ;-) Regards Neoklis - Ham Radio Call 5B4AZ QTH Locator KM64KR Website: http://www.qsl.net/5b4az/
Re: Failed to setup fvwm for antialiased Xft fonts
On 10/12/2011, at 5:18 AM, Neoklis Kyriazis wrote: > - Original Message - > From: Richard Toohey > > To: Tekk > Cc: Neoklis > Kyriazis ; OpenBSD > Sent: Friday, December > 9, 2011 9:03 AM > Subject: Re: Failed to setup fvwm for antialiased Xft fonts > On 9/12/2011, at 7:27 PM, Tekk wrote: > >> iirc the binary packages are audited, > ports are not >> > >> Guys, they put so much effort into the docs & FAQ - read > them. The >> recommendation is to use the binary packages unless you know you > are doing. > > > OK, sorry about that, but I am a complete beginner in OpenBSD and > there is so much to read that I have not been able to cover all the > > ground. Welcome to OpenBSD. > And it was the first attempte at ports also. > > I guess I should spend less time > in trying to set up the installation > > and more on reading > The installation? Boot off the CD and follow the instructions and OpenBSD will be installed 5 minutes later. Install an application - pkg_add Then go and do the reading. Expect to still be reading and learning many years later - I am. Between the man pages, the FAQs, the source, and your favourite search engine - it's (usually!) all there. Just remember - it's not Linux, it hasn't got the deep pockets (filled with $$$s) of Ubuntu. It's not dumbed down - it expects the end-user to do a bit of thinking - how can it guess/assume what is required on your machine or how it should be configured? It's better at some things, worse at others, ahead in some ways, behind in others. It won't cure cancer, but no kittens or babies are harmed. Only you can decide if it works for work in the way you need it to. Different jobs need different tools. YMMV. Good luck. > > Regards > Neoklis - Ham Radio Call 5B4AZ > QTH Locator KM64KR > Website: > http://www.qsl.net/5b4az/
Re: Failed to setup fvwm for antialiased Xft fonts
- Original Message - From: Richard Toohey To: Tekk Cc: Neoklis Kyriazis ; OpenBSD Sent: Friday, December 9, 2011 9:03 AM Subject: Re: Failed to setup fvwm for antialiased Xft fonts On 9/12/2011, at 7:27 PM, Tekk wrote: > iirc the binary packages are audited, ports are not > > Guys, they put so much effort into the docs & FAQ - read them. The > recommendation is to use the binary packages unless you know you are doing. OK, sorry about that, but I am a complete beginner in OpenBSD and there is so much to read that I have not been able to cover all the ground. And it was the first attempte at ports also. I guess I should spend less time in trying to set up the installation and more on reading Regards Neoklis - Ham Radio Call 5B4AZ QTH Locator KM64KR Website: http://www.qsl.net/5b4az/
Re: Failed to setup fvwm for antialiased Xft fonts
On 9/12/2011, at 7:27 PM, Tekk wrote: > iirc the binary packages are audited, ports are not > Guys, they put so much effort into the docs & FAQ - read them. The recommendation is to use the binary packages unless you know you are doing. http://www.openbsd.org/faq/faq15.html#Intro The packages and ports collection does NOT go through the same thorough security audit that is performed on the OpenBSD base system. Although we strive to keep the quality of the packages collection high, we just do not have enough human resources to ensure the same level of robustness and security. > On Thu, 8 Dec 2011, Neoklis Kyriazis wrote: > >> - Original Message - >> From: Thomas Adam >> To: Neoklis >> Kyriazis >> Cc: OpenBSD >> Sent: Thursday, >> December 8, 2011 6:41 PM >> Subject: Re: Failed to setup fvwm for antialiased Xft >> fonts >> >>> No -- OpenBSD's version of FVWM as included in base is ancient. Get >>> the one from ports which will have XFT support. >> >> >> Hi, >> >> Thanks for the tip. I >> have tried to install fvwm2 from the ports tree, >> but I saw a lot of gcc >> warnings during compilation, some of them >> possibly serious. >> >> >> This leads me to >> a more general question about using third party >> software. Is the source code >> of the binary application packages in >> the mirrors scrutinized, to fix the >> source of such warnings?And I >> suppose applications installed from the ports >> system are "as is", >> since the source is downloaded from upstream? >> >> My thanks >> in advance. >> >> >> >> Regards >> >> Neoklis - Ham Radio Call 5B4AZ >> QTH Locator KM64KR >> Website: http://www.qsl.net/5b4az/
Re: Failed to setup fvwm for antialiased Xft fonts
iirc the binary packages are audited, ports are not On Thu, 8 Dec 2011, Neoklis Kyriazis wrote: - Original Message - From: Thomas Adam To: Neoklis Kyriazis Cc: OpenBSD Sent: Thursday, December 8, 2011 6:41 PM Subject: Re: Failed to setup fvwm for antialiased Xft fonts No -- OpenBSD's version of FVWM as included in base is ancient. Get the one from ports which will have XFT support. Hi, Thanks for the tip. I have tried to install fvwm2 from the ports tree, but I saw a lot of gcc warnings during compilation, some of them possibly serious. This leads me to a more general question about using third party software. Is the source code of the binary application packages in the mirrors scrutinized, to fix the source of such warnings?And I suppose applications installed from the ports system are "as is", since the source is downloaded from upstream? My thanks in advance. Regards Neoklis - Ham Radio Call 5B4AZ QTH Locator KM64KR Website: http://www.qsl.net/5b4az/
Re: Failed to setup fvwm for antialiased Xft fonts
- Original Message - From: Thomas Adam To: Neoklis Kyriazis Cc: OpenBSD Sent: Thursday, December 8, 2011 6:41 PM Subject: Re: Failed to setup fvwm for antialiased Xft fonts > No -- OpenBSD's version of FVWM as included in base is ancient. Get > the one from ports which will have XFT support. Hi, Thanks for the tip. I have tried to install fvwm2 from the ports tree, but I saw a lot of gcc warnings during compilation, some of them possibly serious. This leads me to a more general question about using third party software. Is the source code of the binary application packages in the mirrors scrutinized, to fix the source of such warnings?And I suppose applications installed from the ports system are "as is", since the source is downloaded from upstream? My thanks in advance. Regards Neoklis - Ham Radio Call 5B4AZ QTH Locator KM64KR Website: http://www.qsl.net/5b4az/
Re: Failed to setup fvwm for antialiased Xft fonts
Hi, On 8 December 2011 16:32, Neoklis Kyriazis wrote: > Hi all > > I have been trying in vain to setup fvwm for anti-aliased fonts > in > obsd 5.0. I tried the instructions in man of fvwm and some > tips on google, but > with no result. fvwm reports that it can't > get the specified fonts. I made > sure I used fonts as listed by > fc-list and tried them in xterm's config, which > worked, also on > my Arch Linux installation. > > Is it possible to have > anti-aliased fonts in OpenBSD's fvwm? > If so, any hints please? No -- OpenBSD's version of FVWM as included in base is ancient. Get the one from ports which will have XFT support. -- Thomas Adam
Failed to setup fvwm for antialiased Xft fonts
Hi all I have been trying in vain to setup fvwm for anti-aliased fonts in obsd 5.0. I tried the instructions in man of fvwm and some tips on google, but with no result. fvwm reports that it can't get the specified fonts. I made sure I used fonts as listed by fc-list and tried them in xterm's config, which worked, also on my Arch Linux installation. Is it possible to have anti-aliased fonts in OpenBSD's fvwm? If so, any hints please? My thanks in advance. Regards Neoklis - Ham Radio Call 5B4AZ QTH Locator KM64KR Website: http://www.qsl.net/5b4az/
Re: [Fvwm][Bug?] Keyboard layout changes when fvwm restart
Oops, I replied to individuals... Sorry... --- Bruce Khereid to Olivier 4:55 PM (18 hours ago) Hi Olivier, Thank you for your quick reply. I did the configuration for the X Server, by adding an option "XkbLayout" in Section "InputDevice" for the keyboard, in xorg.conf. I think that's what you meant by "global X configuration"? Sorry that I entered a wrong option name in the previous mail. What I don't understand is that does FVWM receive original hardware keycode or something translated to letters according to the layout specified in xorg.conf? Sorry but I'm not familiar with X protocol. Thank you! --- Olivier Mehani to me 5:01 PM (18 hours ago) Hi again, Bruce, On Mon, Jul 19, 2010 at 04:55:25PM +0800, Bruce Khereid wrote: > I did the configuration for the X Server, by adding an option "XkbLayout" in > Section "InputDevice" for the keyboard, in xorg.conf. I think that's what > you meant by "global X configuration"? Sorry that I entered a wrong option > name in the previous mail. Yep, that's what I weant by global, which also rules my explanation out. > What I don't understand is that does FVWM receive original hardware keycode > or something translated to letters according to the layout specified in > xorg.conf? Sorry but I'm not familiar with X protocol. I don't either. I'm pretty sure it gets the mapped symbols rather than direct keycodes, but can't explain the behaviour of FVWM... Did you have a llok at the logs (though I'm not sur it will mention anything about sucessful shortcut assignment...)? --- Bruce Khereid to Christoph 11:19 AM (5 minutes ago) Cool! It works now. Thanks to all of you!
Re: [Fvwm][Bug?] Keyboard layout changes when fvwm restart
On Mon, 2010-07-19 at 18:27 +1000, Olivier Mehani wrote: > Hi, > > On Mon, Jul 19, 2010 at 04:07:06PM +0800, Bruce Khereid wrote: > > After startx, the GoToPage actions were bound to Ctrl-F and Ctrl-D in > > QWERTY layout (which are Ctrl-E and Ctrl-U in Dvorak, or the 3rd and > > 4th keys in the middle line), so I began to think all those bindings > > are parsed as in QWERTY layout. But after I restarted the fvwm (by > > typing restart in FvwmTalk), things changed, it began to interpret the > > configurations in Dvorak layout, that is, Ctrl-F and Ctrl-D in Dvorak > > layout, which are Ctrl-Y and Ctrl-H in QWERTY, started to turn the > > page. > > How (When) is your keyboard mapped to Dvorak? Is it in the global X > configuration, or only for the session (e.g. with a setxkbmap somewhere > in a xstartup script)? > > I suspect it's set up by the session, which means that FVWM starts while > your keyboard still has a QWERTY mapping, and based its shortucts on > that. Restarting FVWM would then let it rebind the shortcuts to the new > keys with the given symbols. > > I may also be completely wrong. No you are not: At the first start of a more recent X the keyboard layout is in the early milli-seconds set to US, after that it changes to the value in the configs. FVWM does not yet support keyboard layout changes for keybindings (if ever). I wrote a ugly patch to support that, but the easy way is to set the xkbmap before: Just add a "setxkbmap de" in .xsession for example. I'll look forward to add this hint into the manpage of FVWM although it should be documented in X somewhere. happy FVWMing, chf
Re: [Fvwm][Bug?] Keyboard layout changes when fvwm restart
On 19 July 2010 18:07, Bruce Khereid wrote: > QWERTY layout. But after I restarted the fvwm (by typing restart in > FvwmTalk), things changed, it began to interpret the configurations in > Dvorak layout, that is, Ctrl-F and Ctrl-D in Dvorak layout, which are Ctrl-Y > and Ctrl-H in QWERTY, started to turn the page. > > Is that a bug of Fvwm? Is anybody encountered this problem before? Oh that's just Theo... HE'S IN UR ROUTR REMAPPIN UR KEEZ
Re: [Fvwm][Bug?] Keyboard layout changes when fvwm restart
Hi, On Mon, Jul 19, 2010 at 04:07:06PM +0800, Bruce Khereid wrote: > After startx, the GoToPage actions were bound to Ctrl-F and Ctrl-D in > QWERTY layout (which are Ctrl-E and Ctrl-U in Dvorak, or the 3rd and > 4th keys in the middle line), so I began to think all those bindings > are parsed as in QWERTY layout. But after I restarted the fvwm (by > typing restart in FvwmTalk), things changed, it began to interpret the > configurations in Dvorak layout, that is, Ctrl-F and Ctrl-D in Dvorak > layout, which are Ctrl-Y and Ctrl-H in QWERTY, started to turn the > page. How (When) is your keyboard mapped to Dvorak? Is it in the global X configuration, or only for the session (e.g. with a setxkbmap somewhere in a xstartup script)? I suspect it's set up by the session, which means that FVWM starts while your keyboard still has a QWERTY mapping, and based its shortucts on that. Restarting FVWM would then let it rebind the shortcuts to the new keys with the given symbols. I may also be completely wrong. -- Olivier Mehani PGP fingerprint: 4435 CF6A 7C8D DD9B E2DE F5F9 F012 A6E2 98C6 6655 [demime 1.01d removed an attachment of type application/pgp-signature]
[Fvwm][Bug?] Keyboard layout changes when fvwm restart
Hi, I use Dvorak keyboard layout, and have already added kbd Option in xorg.conf, and everything work fine with programs run in the X environment. When I compose my own .fvwmrc for Fvwm, I defined some key bindings for it, say: Key FACGoToPage 1 1 Key DACGoToPage 0 0 After startx, the GoToPage actions were bound to Ctrl-F and Ctrl-D in QWERTY layout (which are Ctrl-E and Ctrl-U in Dvorak, or the 3rd and 4th keys in the middle line), so I began to think all those bindings are parsed as in QWERTY layout. But after I restarted the fvwm (by typing restart in FvwmTalk), things changed, it began to interpret the configurations in Dvorak layout, that is, Ctrl-F and Ctrl-D in Dvorak layout, which are Ctrl-Y and Ctrl-H in QWERTY, started to turn the page. Is that a bug of Fvwm? Is anybody encountered this problem before? Thanks! Bruce
Re: fvwm - move a window freeze others
On Thu, Dec 11, 2008 at 07:10:02PM +0100, Jesus Sanchez wrote: > Indeed I tried a Opaquemovesize 100 and worked ! > I already didn't know why but if the window is opaque the > activity dont stops. Ah, that was it. I had it backwards. Window resizing should also freeze things then.
Re: fvwm - move a window freeze others
Dan Harnett escribis: On Thu, Dec 11, 2008 at 02:10:04PM +0100, Hannah Schroeter wrote: Hi! On Wed, Dec 10, 2008 at 04:05:45PM -0500, Ted Unangst wrote: On Wed, Dec 10, 2008 at 3:29 PM, Jesus Sanchez wrote: I'm using FVWM as window manager and works really fine but when I have various windows (xterms for example) and drag one window to move it around, after a few seconds, all of them stops doing its work, also gkrellm freezes until I drop the moving window in any place, this is normal? I don't consider it particularly desirable, but that's normal for fvwm. Yes, I can confirm that, too, also for fvwm2 from ports, alas. "Nice" if that interrupts xmms from playing sound (because it blocks on updating its display), for example. Of course, for fvwm2, it's an upstream issue rather than an OpenBSD (or port maintainer) issue. Just a "me too". The best workaround that I'm aware of (and still use fvwm) is to disable opaque window movements by setting OpaqueMoveSize to 0. At least that used to help things the last time I used fvwm. Indeed I tried a Opaquemovesize 100 and worked ! I already didn't know why but if the window is opaque the activity dont stops. -J
Re: fvwm - move a window freeze others
On Thu, Dec 11, 2008 at 02:10:04PM +0100, Hannah Schroeter wrote: > Hi! > > On Wed, Dec 10, 2008 at 04:05:45PM -0500, Ted Unangst wrote: > >On Wed, Dec 10, 2008 at 3:29 PM, Jesus Sanchez <[EMAIL PROTECTED]> wrote: > >> I'm using FVWM as window manager and works really fine but when I have > >> various windows (xterms for example) and drag one window to move it > >> around, after a few seconds, all of them stops doing its work, also > >> gkrellm freezes until I drop the moving window in any place, this is > >> normal? > > >I don't consider it particularly desirable, but that's normal for fvwm. > > Yes, I can confirm that, too, also for fvwm2 from ports, alas. > > "Nice" if that interrupts xmms from playing sound (because it blocks on > updating its display), for example. > > Of course, for fvwm2, it's an upstream issue rather than an OpenBSD (or > port maintainer) issue. Just a "me too". The best workaround that I'm aware of (and still use fvwm) is to disable opaque window movements by setting OpaqueMoveSize to 0. At least that used to help things the last time I used fvwm.
Re: fvwm - move a window freeze others
Hi! On Wed, Dec 10, 2008 at 04:05:45PM -0500, Ted Unangst wrote: >On Wed, Dec 10, 2008 at 3:29 PM, Jesus Sanchez <[EMAIL PROTECTED]> wrote: >> I'm using FVWM as window manager and works really fine but when I have >> various windows (xterms for example) and drag one window to move it >> around, after a few seconds, all of them stops doing its work, also >> gkrellm freezes until I drop the moving window in any place, this is >> normal? >I don't consider it particularly desirable, but that's normal for fvwm. Yes, I can confirm that, too, also for fvwm2 from ports, alas. "Nice" if that interrupts xmms from playing sound (because it blocks on updating its display), for example. Of course, for fvwm2, it's an upstream issue rather than an OpenBSD (or port maintainer) issue. Kind regards, Hannah.
Re: fvwm - move a window freeze others
On Wed, Dec 10, 2008 at 3:29 PM, Jesus Sanchez <[EMAIL PROTECTED]> wrote: > I'm using FVWM as window manager and works really fine but when I have > various windows (xterms for example) and drag one window to move it > around, after a few seconds, all of them stops doing its work, also > gkrellm freezes until I drop the moving window in any place, this is > normal? I don't consider it particularly desirable, but that's normal for fvwm.
fvwm - move a window freeze others
Hi list, using 4.3 stable. I'm using FVWM as window manager and works really fine but when I have various windows (xterms for example) and drag one window to move it around, after a few seconds, all of them stops doing its work, also gkrellm freezes until I drop the moving window in any place, this is normal? -Jesus.
Re: upgrading FVWM to 2.4
Ted / Johan, thx. i downloaded 2.4.20 tar from fvwm site and ran ./configure --prefix /usr/X11r6 (otherwise default /usr/local) and then make and then make install after that i was able to use the new fvwm version. -BG. ~~aapka kalyan ho~~ - Original Message From: Ted Unangst <[EMAIL PROTECTED]> To: badeguruji <[EMAIL PROTECTED]> Cc: misc@openbsd.org Sent: Monday, January 7, 2008 5:04:01 PM Subject: Re: upgrading FVWM to 2.4 On 1/7/08, badeguruji <[EMAIL PROTECTED]> wrote: > I figure that i will need to give some runtime arguments to following commands for upgrading my fvwm installation. as per README from fvwm package... pkg_add fvwm2 is a lot easier...
Re: upgrading FVWM to 2.4
On Jan 7, 2008, at 9:55 AM, badeguruji wrote: Hello, I figure that i will need to give some runtime arguments to following commands for upgrading my fvwm installation. as per README from fvwm package... can someone tell me what is the right value for PREFIX and EPREFIX? Since they are not part of the base install with X, I'd keep them in / usr/local/bin. Or, better, build a package/port for it and submit it.
Re: upgrading FVWM to 2.4
On 1/7/08, badeguruji <[EMAIL PROTECTED]> wrote: > I figure that i will need to give some runtime arguments to following > commands for upgrading my fvwm installation. as per README from fvwm > package... pkg_add fvwm2 is a lot easier...
upgrading FVWM to 2.4
Hello, I figure that i will need to give some runtime arguments to following commands for upgrading my fvwm installation. as per README from fvwm package... can someone tell me what is the right value for PREFIX and EPREFIX? Installation directories: --prefix=PREFIX install architecture-independent files in PREFIX [/usr/local] --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX [PREFIX] By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc. You can specify an installation prefix other than `/usr/local' using `--prefix', for instance `--prefix=$HOME'. For better control, use the options below. Fine tuning of the installation directories: --bindir=DIR user executables [EPREFIX/bin] --sbindir=DIR system admin executables [EPREFIX/sbin] --libexecdir=DIR program executables [EPREFIX/libexec] --sysconfdir=DIR read-only single-machine data [PREFIX/etc] --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] --localstatedir=DIRmodifiable single-machine data [PREFIX/var] --libdir=DIR object code libraries [EPREFIX/lib] --includedir=DIR C header files [PREFIX/include] --oldincludedir=DIRC header files for non-gcc [/usr/include] --datarootdir=DIR read-only arch.-independent data root [PREFIX/share] --datadir=DIR read-only architecture-independent data [DATAROOTDIR] --infodir=DIR info documentation [DATAROOTDIR/info] --localedir=DIRlocale-dependent data [DATAROOTDIR/locale] --mandir=DIR man documentation [DATAROOTDIR/man] --docdir=DIR documentation root [DATAROOTDIR/doc/PACKAGE] --htmldir=DIR html documentation [DOCDIR] --dvidir=DIR dvi documentation [DOCDIR] --pdfdir=DIR pdf documentation [DOCDIR] --psdir=DIRps documentation [DOCDIR] Since I did not do that (I do not knwo where is OpenBSD installing fvwm related stuff) I guess after running the following sequence, i have two versions installed on my system... [host]/tmp # ./configure # make # make install so that, from an xterm window $ which fvwm /usr/X11R6/bin/fvwm $ $ fvwm -version [FVWM][main]: Fvwm Version 2.2.5 compiled on Aug 8 2007 at 23:03:41 [FVWM][main]: <> can't open display $ $ /usr/local/bin/fvwm -version FVWM version 2.4.20 compiled on Jan 7 2008 at 11:33:48 with support for: ReadLine, XPM, GNOME WM hints, Shape, SM, Xinerama $ can someone tell the right values for PREFIX and EPREFIX? thx, -BG ~~aapka kalyan ho~~
Re: fvwm in base and repository with security issues?
Marco Peereboom writes: > > -Nix Fan. (Fvwm, IMHO is ugly..) > > Fluxbox is fugly, fvwm is awesome. > > this discussion is very useful! cwm (with the changes I've made :-) is looking nicer and nicer! I hope to see these changes in the tree, soon. // marc
Re: fvwm in base and repository with security issues?
Can we please stop this discussion? Nothing is going to change in base X. All the other things you guys are so called "proposing" are in packages/ports. Use them; that's why they are there for. Base is fine, leave it alone. On Wed, Jan 02, 2008 at 09:19:06AM -0500, Douglas A. Tutty wrote: > On Tue, Jan 01, 2008 at 10:46:43PM -0800, Unix Fan wrote: > > Douglas A. Tutty wrote: > > > > > To satisfy my own curiosity, looking at > > > > > www.en.wikipedia.org/wiki/Category:Free_X_window_managers which > > > provides links to 45 window managers for which there are wiki pages, > > > I looked at the licence for each and found that only xmonad, wmii, > > > fluxbox, and blackbox are licenced under BSD or MIT license. > > > > > Since I didn't look at the software itself, I don't know if any > > > require GPL libraries. > > > > > Just thought I'd FYI. I'm not making an argument either/any way. > > > Fluxbox is MIT licenced, it's dependencies are Imlib2, which is BSD > > licenced.. everything else is included in Xorg and is (AFAIK..) under > > a similar licence. > > I also forgot that Enlightenment seems to be under a suitable licence, > although probably too big to put in base. > > Doug.
Re: fvwm in base and repository with security issues?
* Douglas A. Tutty wrote: [...] > I also forgot that Enlightenment seems to be under a suitable licence, > although probably too big to put in base. enlightnment is development code that does not run stable. It is not usable for "production" or "every day use" machines. > > Doug. > - Marc Balmer
Re: fvwm in base and repository with security issues?
On Tue, Jan 01, 2008 at 10:46:43PM -0800, Unix Fan wrote: > Douglas A. Tutty wrote: > > > To satisfy my own curiosity, looking at > > > www.en.wikipedia.org/wiki/Category:Free_X_window_managers which > > provides links to 45 window managers for which there are wiki pages, > > I looked at the licence for each and found that only xmonad, wmii, > > fluxbox, and blackbox are licenced under BSD or MIT license. > > > Since I didn't look at the software itself, I don't know if any > > require GPL libraries. > > > Just thought I'd FYI. I'm not making an argument either/any way. > Fluxbox is MIT licenced, it's dependencies are Imlib2, which is BSD > licenced.. everything else is included in Xorg and is (AFAIK..) under > a similar licence. I also forgot that Enlightenment seems to be under a suitable licence, although probably too big to put in base. Doug.
Re: fvwm in base and repository with security issues?
On Tue, Jan 01, 2008 at 10:46:43PM -0800, Unix Fan wrote: > Douglas A. Tutty wrote: > > To satisfy my own curiosity, looking at > > www.en.wikipedia.org/wiki/Category:Free_X_window_managers which provides > > links to 45 window managers for which there are wiki pages, I looked at > > the licence for each and found that only xmonad, wmii, fluxbox, and > > blackbox are licenced under BSD or MIT license. > > > > Since I didn't look at the software itself, I don't know if any require > > GPL libraries. > > > > Just thought I'd FYI. I'm not making an argument either/any way. > > > > Doug. > > Fluxbox is MIT licenced, it's dependencies are Imlib2, which is BSD > licenced.. everything else is included in Xorg and is (AFAIK..) under a > similar licence. > > -Nix Fan. (Fvwm, IMHO is ugly..) Fluxbox is fugly, fvwm is awesome. this discussion is very useful!
Re: fvwm in base and repository with security issues?
Douglas A. Tutty wrote: > To satisfy my own curiosity, looking at > www.en.wikipedia.org/wiki/Category:Free_X_window_managers which provides > links to 45 window managers for which there are wiki pages, I looked at > the licence for each and found that only xmonad, wmii, fluxbox, and > blackbox are licenced under BSD or MIT license. > > Since I didn't look at the software itself, I don't know if any require > GPL libraries. > > Just thought I'd FYI. I'm not making an argument either/any way. > > Doug. Fluxbox is MIT licenced, it's dependencies are Imlib2, which is BSD licenced.. everything else is included in Xorg and is (AFAIK..) under a similar licence. -Nix Fan. (Fvwm, IMHO is ugly..)
Re: fvwm in base and repository with security issues?
On Tue, Jan 01, 2008 at 08:27:43PM +, Owain Ainsworth wrote: > On Sun, Dec 30, 2007 at 09:53:29PM -0500, Okan Demirmen wrote: > > > Is there anything up with newer versions then? Why should it not be > > > brought up to date? > > > > i believe license is the issue. > > Correct. Newer version of fvwm are GPLed.. To satisfy my own curiosity, looking at www.en.wikipedia.org/wiki/Category:Free_X_window_managers which provides links to 45 window managers for which there are wiki pages, I looked at the licence for each and found that only xmonad, wmii, fluxbox, and blackbox are licenced under BSD or MIT license. Since I didn't look at the software itself, I don't know if any require GPL libraries. Just thought I'd FYI. I'm not making an argument either/any way. Doug.
Re: fvwm in base and repository with security issues?
On Sun, Dec 30, 2007 at 09:53:29PM -0500, Okan Demirmen wrote: > > Is there anything up with newer versions then? Why should it not be > > brought up to date? > > i believe license is the issue. Correct. Newer version of fvwm are GPLed.. -- Alas, I am dying beyond my means. -- Oscar Wilde, as he sipped champagne on his deathbed
Re: fvwm in base and repository with security issues?
On Mon 2007.12.31 at 01:05 +, Edd Barrett wrote: > Cwm is very good, but there are some bugs in that too. I notice that > if you hide a window so the pointer falls onto the root window and > then try to search for a window (alt+/ if i remember correctly), then > the search menu is not displayed.To make it start working again one > must move the mouse pointer over a window. fixed, thanks - but file a bug (or tell someone) next time ;) > Is there anything up with newer versions then? Why should it not be > brought up to date? i believe license is the issue.
Re: fvwm in base and repository with security issues?
Hi there, On 30/12/2007, Jan <[EMAIL PROTECTED]> wrote: > I would suggest to remove all window managers from base except twm. Twm is in > all default X installations and could be left in as last resort. Cwm is very good, but there are some bugs in that too. I notice that if you hide a window so the pointer falls onto the root window and then try to search for a window (alt+/ if i remember correctly), then the search menu is not displayed.To make it start working again one must move the mouse pointer over a window. > I hope someone will lead this issue to the people taking decisions about what > should be > in and what not, resulting in or updating or removing fvwm. Many people know and love fvwm. I think they may have something to say about removing it. > Pau Wrote > please, don't touch fvwm 2.2.5... it's just perfect... not in vain > it's the default wm in obsd... Don't touch t! Is there anything up with newer versions then? Why should it not be brought up to date? > Douglas Wrote > Personally, I use icewm since its quite > light-weight yet configurable to some extent (e.g. menu and taskbar). But no-where as minimal as anything in base. Icewm links imlib, which would mean importing GPL software into base (big no no). Also it would make base larger. I must admit I use a GPL licensed window manager (JWM), but it was my decision to install it from packages, so it is not a problem. -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: fvwm in base and repository with security issues?
On 12/30/07, Jan <[EMAIL PROTECTED]> wrote: > Security fixes in fvwm-menu-directory. (CVE-2006-5969) i don't get it. i can make a magic directory name and... run commands as myself? > Security fixes in FvwmCommand > Security fix for fvwm-menu-directory. See BugTraq id 9161. > Security patch in fvwm-bug. See > http://securitytracker.com/alerts/2004/Jan/1008781.html i don't have this program. > Security fixes in fvwm-menu-directory (BugTraq id 9161) is this different than Bugtraq id 9161 above? for that matter, how is it different than CVE-2006-5969? > Security fixes in fvwm_make_directory_menu.sh > Security fixes in fvwm_make_browse_menu.sh > Fixed tempfile vulnerabilities in FvwmCommand. > Fixed detection of safe system version of mkstemp. > Security fix in fvwm-menu-directory. (CVE-2006-5969) is this different than CVE-2006-5969 above?
Re: fvwm in base and repository with security issues?
please, don't touch fvwm 2.2.5... it's just perfect... not in vain it's the default wm in obsd... Don't touch t! 2007/12/30, Douglas A. Tutty <[EMAIL PROTECTED]>: > On Sun, Dec 30, 2007 at 07:36:47PM +0100, Jan wrote: > > > I would suggest to remove all window managers from base except twm. > > Twm is in all default X installations and could be left in as last > > resort. When someone needs a window manager, he can install it from > > repo or ports, but it should not be as now, that a 'left over' which > > is much to old, full of bugs and unmaintained, can be used on the > > 'most secure operating system ever'. > > If this is a true issue that applies to OBSD rather than a non-issue > because of custom fixes applied by OBSD, the I would suggest that there > be a more configurable wm other than twm in base. The reason is > simple. Anything in base has a good security audit done. Things in > ports/packages don't. Personally, I use icewm since its quite > light-weight yet configurable to some extent (e.g. menu and taskbar). > > Doug.
Re: fvwm in base and repository with security issues?
On Sun, Dec 30, 2007 at 07:36:47PM +0100, Jan wrote: > I would suggest to remove all window managers from base except twm. > Twm is in all default X installations and could be left in as last > resort. When someone needs a window manager, he can install it from > repo or ports, but it should not be as now, that a 'left over' which > is much to old, full of bugs and unmaintained, can be used on the > 'most secure operating system ever'. If this is a true issue that applies to OBSD rather than a non-issue because of custom fixes applied by OBSD, the I would suggest that there be a more configurable wm other than twm in base. The reason is simple. Anything in base has a good security audit done. Things in ports/packages don't. Personally, I use icewm since its quite light-weight yet configurable to some extent (e.g. menu and taskbar). Doug.
fvwm in base and repository with security issues?
After a discussion on the openbsd irc I am sending this mail, hoping fvwm will be removed from base and repo, or updated. The fvwm version in base is 2.2.5, which is released somewhere in the late nighties. Every installation using X, does have this program installed on the system. Then in the repo, there is a version 2.4.19, which is also some years old. The developer of fvwm is telling me that both versions are way to old, full of security issues and 2.2.5 is not even supported anymore in which way ever... Looking at the news page of fvwm I see a list of security issues and other issues solved in newer versions then 2.4.19: Security fixes in fvwm-menu-directory. (CVE-2006-5969) Security fixes in FvwmCommand Security fix for fvwm-menu-directory. See BugTraq id 9161. Security patch in fvwm-bug. See http://securitytracker.com/alerts/2004/Jan/1008781.html Security fixes in fvwm-menu-directory (BugTraq id 9161) Security fixes in fvwm_make_directory_menu.sh Security fixes in fvwm_make_browse_menu.sh Fixed tempfile vulnerabilities in FvwmCommand. Fixed detection of safe system version of mkstemp. Security fix in fvwm-menu-directory. (CVE-2006-5969) The list of other issues (crashing window managers, race conditions, infinite loops etc...) is much longer. I would suggest to remove all window managers from base except twm. Twm is in all default X installations and could be left in as last resort. When someone needs a window manager, he can install it from repo or ports, but it should not be as now, that a 'left over' which is much to old, full of bugs and unmaintained, can be used on the 'most secure operating system ever'. I hope someone will lead this issue to the people taking decisions about what should be in and what not, resulting in or updating or removing fvwm. Thanks, Jan
Re: Running cwm and fvwm at the same time?
> > quite a while since I last had a look at cwm) :-) > > You can use a tool called XBindKeys. > > http://hocwp.free.fr/xbindkeys/xbindkeys.html It's in ports... x11/xbindkeys. However, the cwm keybinding support works fine. Since I documented it and added some extra features it should be better (check the commit that occurred in the last few days). If there's any problems with it. Let me know. -0- -- When someone says "I want a programming language in which I need only say what I wish done," give him a lollipop.
Re: Running cwm and fvwm at the same time?
On Tue, Nov 20, 2007 at 11:36:26AM +0100, Alexander Hall wrote: > Well, these seems to run quite well on a single one. :-) Can anyone > confirm this? Yes, I can reproduce this (launching cwm in a session already having fvwm running, i.e. on the same display). I need a beer now. Ciao, Kili
Re: Running cwm and fvwm at the same time?
On 10:26:22 Nov 20, Alexander Hall wrote: > Hi! > > I'm just curious how come it its possible to start (and run) cwm at the > same time as running fvwm (from base). AFAIK a window manager normally > cannot (or refuses to) run if another window manager is already in use. Correct. > Is this only a courtsey from the second window manager? I thought there > were limitations in X that forced this behaviour. It works at the X level. Only one program can take control of the root window and decide window placements, receive events etc. That X client has special status and is called as window manager. > > Anyway, I'd expect cwm to behave that way, too, but please feel free to > explain to me why I'm wrong. I dunno about cwm (never used it ) but if you use the Xnest program you can run any number of X servers and consequently run a different window manager in each. $ export DISPLAY=host:display:screen In the case of Xnest, it is yet another X client but it also acts as a X server. So it runs as a normal X client inside which you can run any window manager of your choice. The other method is running Xserver on different virtual terminals as mentioned in the reply to this post. # X :n or even $ startx -- :n > > I also meant to ask about key bindings, but after finding a new part in > the man pages, I realize I have to test a few things first. (Yes, it was > quite a while since I last had a look at cwm) :-) You can use a tool called XBindKeys. http://hocwp.free.fr/xbindkeys/xbindkeys.html I faintly remember that it compiled and worked fine for OpenBSD. Best, Girish
Re: Running cwm and fvwm at the same time?
Jan Stary wrote: On Nov 20 10:26:22, Alexander Hall wrote: I'm just curious how come it its possible to start (and run) cwm at the same time as running fvwm (from base). How exactly does that happen on your box? Well, using fvwm as window manager, I simply run cwm from a shell. I did not expect it to run, but it does. Strange things happen though, as one might expect. After killing cwm (ctrl+c), I need to restart fvwm to restore the window placement etc. AFAIK a window manager normally cannot (or refuses to) run if another window manager is already in use. Is this only a courtsey from the second window manager? I thought there were limitations in X that forced this behaviour. A window manager needs its own $DISPLAY, but that's IMHO the only limitation. tty00$ startx tty01$ startx -- :1 Well, these seems to run quite well on a single one. :-) Can anyone confirm this? /Alexander
Re: Running cwm and fvwm at the same time?
On Nov 20 10:26:22, Alexander Hall wrote: > I'm just curious how come it its possible to start (and run) cwm at the > same time as running fvwm (from base). How exactly does that happen on your box? > AFAIK a window manager normally > cannot (or refuses to) run if another window manager is already in use. > Is this only a courtsey from the second window manager? I thought there > were limitations in X that forced this behaviour. A window manager needs its own $DISPLAY, but that's IMHO the only limitation. tty00$ startx tty01$ startx -- :1 Jan
Running cwm and fvwm at the same time?
Hi! I'm just curious how come it its possible to start (and run) cwm at the same time as running fvwm (from base). AFAIK a window manager normally cannot (or refuses to) run if another window manager is already in use. Is this only a courtsey from the second window manager? I thought there were limitations in X that forced this behaviour. Anyway, I'd expect cwm to behave that way, too, but please feel free to explain to me why I'm wrong. I also meant to ask about key bindings, but after finding a new part in the man pages, I realize I have to test a few things first. (Yes, it was quite a while since I last had a look at cwm) :-) /Alexander
gmplayer locks up Fvwm
OpenBSD 4.1 GENERIC#0 i386 Hi: Don't know if any one else experienced this. When gmplayer is activated from Fvwm's menu then it locks up fvwm. To reproduce: 1) Put: +"GMplayer" Exec exec gmplayer in the RootMenu section, of the .fvwmrc 2) Restart Fvwm 3) Click on GMplayer in the Fvwm menu. 4) Fvwm locks up and requires ALT-CTL-Backspace The fix is show here: http://www.mail-archive.com/[EMAIL PROTECTED]/msg08129.html Namely make the menu entry as so: + "GMplayer"Exec exec xterm -iconic -e gmplayer -- Kind regards, Jonathan
Re: How to uninstall fvwm with obsd4.0?
No need to uninstall the older version, just install the new one via ports. At the end, it will spit out a message to add 'exec /usr/local/bin/fvwm2' to your .xinitrc or .xsession file. That will Do The Right Thing. On 2007 Mar 02 (Fri) at 19:24:58 +0800 (+0800), ronald jiang wrote: :I want to install a newer one. : -- Uncle Ed's Rule of Thumb: Never use your thumb for a rule. You'll either hit it with a hammer or get a splinter in it.
Re: How to uninstall fvwm with obsd4.0?
On 2007/03/02 10:02, Nick ! wrote: > On 3/2/07, Stuart Henderson <[EMAIL PROTECTED]> wrote: > >On 2007/03/02 09:34, Nick ! wrote: > >> However, I *think* you should just be able to install the new > >> fvwm--which presumably means compiling and that means manually copying > >> the new fvwm over the old > > > >ugh. install the new one under /usr/local/... > > > > Oh, sorry. Yes that is better. I was worrying about assuaging the OP's > intuitive fear of having the old one interfere; I should have been > careful to understand his thinking but not take it myself. :) to the OP; just specify the full path in .xsession or wherever else you start fvwm; if you remove/overwrite the original in /usr/X11R6/bin you may fix things in the short time but store problems for upgrade time.
Re: How to uninstall fvwm with obsd4.0?
On 3/2/07, Stuart Henderson <[EMAIL PROTECTED]> wrote: On 2007/03/02 09:34, Nick ! wrote: > However, I *think* you should just be able to install the new > fvwm--which presumably means compiling and that means manually copying > the new fvwm over the old ugh. install the new one under /usr/local/... Oh, sorry. Yes that is better. I was worrying about assuaging the OP's intuitive fear of having the old one interfere; I should have been careful to understand his thinking but not take it myself. -Nick
Re: How to uninstall fvwm with obsd4.0?
On 2007/03/02 09:34, Nick ! wrote: > However, I *think* you should just be able to install the new > fvwm--which presumably means compiling and that means manually copying > the new fvwm over the old ugh. install the new one under /usr/local/...
Re: How to uninstall fvwm with obsd4.0?
On 3/2/07, z0mbix <[EMAIL PROTECTED]> wrote: On 02/03/07, ronald jiang <[EMAIL PROTECTED]> wrote: > I want to install a newer one. http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_delete&sektion=1&manpath=OpenBSD+4.0 fvwm isn't a package. However, I *think* you should just be able to install the new fvwm--which presumably means compiling and that means manually copying the new fvwm over the old, and moving any man pages and stuff to their proper places--and it won't conflict (this isn't Windows). -Nick
