Re: FVWM: Controlling initial size of a "gThumb" window
In message , Dan Espen wrote: >So, I'm afraid I can't duplicate your issue but I can see gthumb >is really buggy. I'm not sure that's a proper assumption. Gthumb works well enough for me on both Ubuntu (18.04) and FreBSD (12.0). No crashes at all so far. And anyway, even if the thing crashes, it might not be the thing itself. I reported a bug to the FreeBSD folks recently where Opera was crashing every time I tried to opne the print menu: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238413 It turned out that the actual bug was in a thing called libproxy that it was using. (The version number for that library is currently 0.4.15 :-)
[SOLVED] Re: FVWM: Strange problem with localhost
Ok, so, I deleted the line setenv DISPLAY localhost:0.0 from my ~/.login file and then exited X, logged out (console) and then logged back in (console again) and checked. At that point, the environment variable DISPLAY wasn't set at all. I then started up X (via xinit) as I am accustomed to doing, which in turn started up fvwm, and I then got an xterm window and checked again. Now I have the following: DISPLAY=:0 Now all of the following are working happily: firefox opera chrome xpdf evince gimp vlc So everybody is happy, it seems, and I am back in the saddle again. My thanks to Stephen Dennison for taking me right to the heart of the matter. (It serves me right. This is the kind of thing that happens when/if one neglects to upgrade things for years and years. What can I say? I was busy. :-) Regards, rfg
Re: FVWM: Strange problem with localhost
In message <20190617205926.mwzkffi363jut...@bennettconstruction.us>, chris wrote: >> 127.0.0.1 localhost localhost.tristatelogic.com > > >Having localhost.tristatelogic.com after localhost seems to be wrong to >me. Forgive me if I am mistaken. This reminds me of that old saying... "In the land of the blind, the one-eyed man is king." In this context, I am just one of the blind men, groping my way around... and I am neither too proud nor too ashamed to admit it. In short, I have no idea if you are right or wrong, or if the content of my /etc/hosts file even makes much bloody difference to anything, in practice. (I have a question pending abuot that very issue on the freebsd-net mailing list. It appears to me that manual edits of my /etc/hosts file aren't even having any effect at all. I'm trying to find out why.) >Anything I can learn is a plus to me! Ditto. Regards, rfg
Re: FVWM: Strange problem with localhost
In message , Stephen Dennison wrote: >There's probably nothing wrong with localhost per se... OK. I guess that's the good news. >> Basically, once I start up X and fvwm, I see that all of my xterm >> windows are automagically inheriting the following environment variable >> and the value shown: >How did you start up "X"? Which "X" are you running? What OS and are >you using a login manager, display manager, etc? I am using: FreeBSD 11.0-RELEASE xorg-7.7_3 (installed from packages) I start X by just logging in (console) and then running xinit. I have a (slightly) personally tailored .xinitrc file. I am *not* using any X login manager. >Perhaps you inadvertently set the value of DISPLAY in one of your dot >files and that's the actual problem? O! Good lord! Good catch! I just now checked, and yes, the ancient .login file (used by my prefered shell, tsch) does indeed contain: setenv DISPLAY localhost:0.0 I probably put that in there 10+ years ago to solve some problem and then never looked at it ever again since. So I just simply need to remove that?? Marvelous. I'll try it. >> I futzed around trying to fix this problem for awhile and I managed to >> discover that if I manually set DISPLAY instead to just :0.0 then suddenly >> all my X applications start to work again. >Right, because it stops trying to use the TCP transport and uses local instead. I see. I am probably stating the obvious, but for a person like me who is not at all steeped in the current machinations and/or machanisms of the X server, this was/is rather entirely non-obvious. >> Here is the output from the command "getent hosts localhost" on the system >> in question: >> >> ::1 localhost >> 127.0.0.1 localhost localhost.tristatelogic.com >> >> >> What am I doing wrong? Why doesn't the default value of localhost:0.0 >> for DISPLAY work just as well as :0.0 ? >In summary, localhost:0.0 says to use the TCP transport for the >connection instead of local and your system is probably not listening >on tcp. So, just out of curiosity, when did that change? (I must sheepishly admit that I haven't updated this system in years, so it might even have changed 6 ofr more years ago. Obviously, I didn't get the memo. :-)
Re: FVWM: Two small oddities
In message ,
Dan Espen wrote:
>"Ronald F. Guilmette" writes:
>> What about the second issue I mentioned? That one is far more serious.
>> Why doesn't chrome{ium} behave itself in a normal fashion, just like
>> everything else, and pop to the foreground when you click on some visible
>> part of it (e.g. along the very top edge on the window)?
>>...
>You might like:
>
>Style * MouseFocusClickRaises
Sorry that I didn't respond to this sooner.
All I want to say is "Thanks, that did indeed fix the problem."
Re: FVWM: One more question...
I had asked about how to get a digital xclock in the empty space just under the analog xclock and the xbiff thingy in the default theme for fvwm... In message , Jaimos Skriletz wrote: >Add this command to your StartFunction > >AddToFunc StartFunction I Test (Init) Exec exec xlock -digtal -strftime '%a %b >%d %T' > >The test is just to ensure it is only run during the init (first >start) And not after ever restart. OK, so I tried that, fixing the one small typo (digtal->digital), which was my fault, since it was present in my original question. The bad news is that just adding that one line top my ~/.fvwm2rc file -did- create an effect, but not at all what was intended. What happened was that the original analog xclock in the default theme got pushed out to a place on my destop that is sort-of near to the center top of my screen (and it was rendered MUCH bigger than before) and the digital xclock got kind-of stuffed into the little box where the analog xclock formerly was (in the default theme)... except of course that the text of my new digital xclose could not fix in that small space, so it just got cut off after the first few (leftmost) characters. So, bottom line, I'm still hoping that someone will tell me how to get a digital xclock into the empty space in the default theme that sits below the xbiff icon thingy and the analog xclock. I can't imagine that this should be too awfully difficult, but I quite certainly have no idea how to do it properly.
Re: FVWM: two questions about icons
Sorry. My bad, I forgot to attach the xprop output file to my prior
emssage. It is attached to this one.
GDK_TIMESTAMP_PROP(GDK_TIMESTAMP_PROP) = 0x61
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x40018a
_NET_FRAME_EXTENTS(CARDINAL) = 7, 7, 31, 7
_KDE_NET_WM_FRAME_STRUT(CARDINAL) = 7, 7, 31, 7
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_CHANGE_DESKTOP,
_NET_WM_ACTION_CLOSE, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_MAXIMIZE_HORZ,
_NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_MOVE,
_NET_WM_ACTION_RESIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_STICK
_NET_WM_DESKTOP(CARDINAL) = 0
_NET_WM_ICON_VISIBLE_NAME(UTF8_STRING) = "FreeBSD Handbook - Mozilla Firefox"
_NET_WM_VISIBLE_NAME(UTF8_STRING) = "FreeBSD Handbook - Mozilla Firefox"
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
bitmap id # to use for icon: 0x147
bitmap id # of mask for icon: 0x14e
window id # of group leader: 0x141
_GTK_THEME_VARIANT(UTF8_STRING) =
WM_WINDOW_ROLE(STRING) = "browser"
XdndAware(ATOM) = BITMAP
_NET_WM_ICON(CARDINAL) =Icon (64 x 64):
.^
_-
-;-:
`_";-`
_~"";-'
.~i/)1}})|?>~^_;""";-. .
` ^|xYYUJCCLLtffjz\_";-. '!
}>>xOOZXYUJCLLtffjzz<-"";-'<(`
>U? >LQ00OZXYJJCLLtffjzu_-~I|!
,CUv:nooQ0OOZYUJCCLttfjzz{_-";?/:
{UJJl !QaooQ0OZXfnvnLLtffjzz\_~"";!l.
'CUUJL:]hhaooQ0Xx[1){tLLtffjzx?_-i-
YUJCCLtfzxnucr]}{1[cr]}{)|/tLtffjjt>+++~;;;~-_
zYUJCCLtfzxnvcr[}{1[cr]}{)||LLttffjfx-~.
-ZYUJCLLtjzxnvcr[}{1{cr]}{)(tCLLttfffLu-~~---
[XYUJCLLtjzxuvcr[}{))cr][{cUJCCLLLttffLn_~~---__+
.JXYUJCLLtjzxuvcr[}{))[rrzOZYUJCCtttLji<<<+--_.
><_--__+;
+CXYUJCLLtjzxuvcr[}{))(X0OOZXYUUJJCCLLY1/+_+++<
;OZYUJCLLtjzxnvcr[}{1)(Y00OZZXYYUJJJLLUt/|i>>i+__+>,
IOZYUJCCLtfzxnvcuxnun})0Q00OOZXYYUUCCCJZI)|<<<>I
1OZYUJCCLtfzxnntLfjQkhJaQQ00OOZZXYYUUUJO}l)/iii!<<>/
nOZYUJCCLtfjxxLLtjfbhaaaoQQ00OOZZXX0x_|(I<<<>>i/
LOZXUJJCLLfjzfCtfjfbhhaaooQQ000OOZZZXXX0L_I\\l!!li!?
z0ZXYUJCLLfjzLLfjznakhhaaooQQOOOZZZQY_>/\?>>ii!I
)0ZXYUJCLLtjzLtfzxuxhkhhaaoooQQoY_+?//IllI!iiiI!
<0OXYUJCCLtfjtfjxnucvakhhaaaooQQQ00aJ++!!!?i
`QOZYUJCCLtfffjzxuvr}}YkhhhQCnrvL00kj++I???III?!!lI+
.ZOZXYJJCLLfjfjznucr}{1]xx]\//?II|YQQQok}<>??//^
v0OZYUJCCLtfjjxnvcr]}{1))(|\\/??IIfaaaooobC>>>?///?I?I
\QOZXUUJCLLtjjxnnvcr]}{1)((|\\|xULoahd|iii/??<
"Q0ZXYUJCCLtfjzuvc][}{1))fbdbbhhbj!!!l///\/\\\///^
.L0OZYUJJCLLtjzxnuvztzxnvcutkpbkkhkb0Ill!?/\l
)Q0ZXYUJCCLtfjzxuvvaqbahpwqdbbkkkba\IIll/\\||\\"
^00OXYUJJCLLtfzxnuvvopdbd0|?III?\|?
.cQOZXYUJCCLtfjzxnuvcYdpf//(||_
;00OXYUJJCLLtfjzxnuvcnXbppddkC1\\\||]-
.rQOZXYUJCCLLtfzxnuuvrr]nLYZZYtc((|||||{u:
:O0OZYUJJCCLtfjzxnuvvcr][}{{11))(((((()))1t1
.\Q0ZXYUJJCLLtfjzxnuvvcr][[}{111)))(()))1z{?
'x0OZXYUJCCLLtfjzxnuuvcr]][}}{{11)))111r{{'
^Y0OZYUUJCCLLtfjzxnnuvcrr][[}}{{1)1{{{}}_
-O0ZXYUJJCCLLtfjzxxnuvvcrr][[}}{{}}}[[!
.>OOZXYUJJCCLLtfjzzxnuuvccrr]][[}{{}[[[]]i
.>OOZXYUJJCCLLtfjjzxxnuuvccrrr]][[]rrr]-
.-YOZXYUJJCCLLttfjzzxnnuuvvcc]]]|'
:tOZXYUJJCCLLLtfjjzzxnnuuuvvvvvvr".
')OZXYUJJCCCLLttfjjzzxxnnvuuuj?.
.-CZXYUUJJCCLLLtffjjzzxxxnnnxjYX|
'\UXYUUJJCCCLLLttffjjzzztJXJj|
.`/LYYUJJJCCttfffjjjzzv;
.'-[CYUJJtttfz{;.
Re: FVWM: two questions about icons
In message firefox.xprop wrote: >This is probably because my memory is failing me (I wasn't able to >double check what resource/class firefox uses these days). > >Use FvwmIdent or xprop and figure out the correct resource/class of >firefox on your system and use that instead of 'firefox' in the Style >line. Please see attached fle which is the output from xprop. I seriously have no idead= what I am looking for in this file, but I do see several places where the name "Firefox" (capitalized) appears. My assumption was that perhaps this is the magic string I needed to be using, so I substituted that in, in place of "firefox" in the Style lines within both ~/.fvwm2rc and also ~/.fvwm/config and then I again exited X and restarted it, and I'm still getting the BIG icons. Maybe you can look at this xprop output and intuit what name, precisely, I should be using in the Style line, but I'm totally ignorant of all of this stuff so it's a complete enigma to me. >One really needs to read the docs and understand what commands are >doing in fvwm to make the most out of it. For a Style you need to >ensure you match the name/class/resource of the window. OK, two things... First, at this point my goals are -very- modest. I don't really need to "make the most" out of fvwm. I'm mostly happy with the default fuctionality -and- with the default theme. Second, to be frank, I've already been throughly intimidated by the gigantic size of the fvwm man page. I mean seriously... holy moses! It's wonderful that fvwm provides such massive flexibility and such massive configurability, but unless and until I need to write a Master's thesis on this one tool, I don't believe that I'll have time to delve seriously into even the first couple of layers of the complexity here. Don't get me wrong. I admire this tool and also every person who has worked to create it. But my needs are simple and my time, limited. If I can just get these three simple things fixed then I'll be a happy camper: (1) proper (48x48) icon size for Firefox, (2) a proper sort of an icon being used for minimized xterm windows and (3) a nice digital xclock displaying in the space below where the default theme is putting the xbiff thingy and analog xclock. I've already received a suggestion on how to do that last one... which I have yet to try, but which I am hoping will work... so now I just need some simple fixes for the other two. As I say, I greatly admire fvwm and all of this ornate configurability. It apparently gives the user that ability to configure just about everything. That's wonderful, of course. I just wish that it had an option also to select a preferred icon size. That would have simplified everything a lot, I think. Regards, rfg P.S. Many UNIX programs/utilities that support their own config files document the format of allowable entries in those files in a separate man page from the one that documents the program itself (e.g. ntp.conf and many others). This makes it a bit easier to find what one is looking for, either by looking at the man page for the program or at the man page for the configuration file. I only mention this because it seems to me that the man page for fvwm might benefit from such a separation of concerns (into two separate man pages). Just a thought. Probably worth what you paid for it. :-)
Re: FVWM: two questions about icons
In message Jaimos Skriletz wrote: >If you don't like the icon provided by the application you can >configure fvwm to use custom icons via the Icon Style (or >WindowStyle). For example if you find a firefox icon and put it in >your ImagePath, you can tell fvwm to use it for firefox as follows: > >Style firefox Icon firefox.png > >(you could also just use a full path for your icon specification). I've now tried to do this in multiple different ways and it just ain't working for me. I was able to find and download an appropriate 48x48 firefiox .png icon file and I've now tried to get fvwm to make us eof that in mutiple different ways and so far it is just refusing. So if some kind soul can tell me what I'm doing wrong, I'd appreciate it. I started out by just putting the .png file into my own home directory (permissions 0644) and then I added the following single line at some random point in the ~/.fvwm2rc file which I had copied from the systemwide default file /usr/local/rfg/system.fvwm2rc Style firefox Icon /home/rfg/.Firefox-icon-48x48.png And yes, I double-checked that the file really did exist at that exact path. After doing this, I shutdown X and restarted it. No change. Firefox still minimized to an oversized icon. I wasn't sure whether or not the use of full pathnames was supported, so I copied the .png file into a directory, /usr/local/rfg/icons/ (removing the leading period in the filename as I did so) and then changed the above to the following and tried again: ImagePath /usr/local/rfg/icons Style firefox Icon Firefox-icon-48x48.png Still no joy. I noted that someone here had saidf that the cannonical location of the per-user fvwm config file is now ~/.fvwm/config so I copied my tailored config file to that location and again exited X and restarted, and still the Firefox icons are the big fat ones. I guess I'm doing something wrong, but it isn't obvious what that might be. Does fvwm create a detailed log file anywhere that I should be studying for hints about what files it is reading and what went wrong?
Re: FVWM: two questions about icons
In message <20190531001538.084a9320...@apps1.cs.toronto.edu>,
Chris Siebenmann wrote:
> The bad news is that modern EWMH X programs generally don't supply
>their icons as files in the filesystem; instead, they provide multiple
>sizes of icons as X properties, which you can usually see by using
>'xprop' on a suitable window (it's all of the _NET_WM_ICON stuff, and
>I think the WM_HINTS stuff, although I don't know how the bitmap ids
>are used).
Thanks much. I really -am- just to dumb end-luser, and thus didn't even
know about xprop until just now.
But I ran it on (non-minimized) Firefox and Opera browser windows on my
system of interest and it appears that Opera only offers up a single 48x48
icon, whereas Firefox now offers all of: 16x16, 32x32, 48x48, 64x64, and
128x128 versions.
Strangely, the output of xprop executed on a Chrome{ium} browser window
-seems- to say to me that Chrom{ium} is only offering up a 128x128 icon
for itself, but when minimized, the icon displayed in actually way smaller
than that... somwhere between the 48x48 icon size used by Opera and what
I am just guessing is probably the somewhat larger 64x64 size used , at
present, for Firefox.
I just mention this because it appears to me that in that (Chrom{ium}) case,
someboyd may be doing some sort of scaling or something.
So, anyuway, what I want is for Fvwm to be using the 48x48 icon for its
representation of a minimized Firefox window.
Surely there -must- be -some- way to force that, no?
>If you want to see what size of icon fvwm is using for some
>window, you can use 'xwininfo' on the icon; this will tell you the
>icon's Width and Height.
Thanks. Yet another thing I learned today.
>The actual source PNGs for these Firefox icons are present in the
>source code but are magically bundled into the compiled and installed
>Firefox.
I guess that me offering this observation is rather pointless, but I'll
offer it anyway: This choice, to embed the icons into the compailed
binaries, is, in my humble opinion, of debatable merit.
I know. I know. If I want to grouse about -that- questionable design
decision, then I'm in the entirely Wrong Place for doing so. (If I get
motivated, I'll register my opinion on this topic elsewhere.)
>Never the less you can simply pull the PNGs out of the source
>code, once you know the magical location. Probably the simplest way is
>through the Github Firefox mirror, where I believe you can find all of
>the sizes in the default*.pngs here:
>
>https://github.com/mozilla/gecko-dev/tree/master/browser/branding/official
OK, I -think- I understand what you are suggesting. I'd basically be
telling/forcing Fvwm to override the icon size choice it is currently
making in the case of Firefox. And I'd be doing it by forcing Fvwm to
use a .png of my choosing... which is exactly the kind of localized hack
that I myself had suggested earlier. But please answer me this: Why
should I even have to go through all this if the Firefox binary that
I'm using already has an built-in/compiled-in 48x48 icon? Why can't
I just tell Fvwm that my first preference for icon sizes in 48x48 in
all cases?
>So, basically, you probably want to use xwininfo on an Opera icon to
>find out how big it is, then download the appropriate sized defaultNN.png
>file and set it as Firefox's icon. This will override anything Firefox
>is hinting to fvwm and fvwm is picking up on.
See above. I'm still perplexed as to why I even need to resort to such a
hack.
And BTW, who or what is doing the apparent scaling on the Chromium icon?
Maybe I just need to get that thing working on my side, eh?
FVWM: One more question...
Other than the questions I've alreasdy posted, I just have one more and then I think I'm done. If i can find a solution for this and the others I've posted, then I think I'll be a happy camper. On the new system I'm configuring, I'm running without any .fvwmrc file in the home directory of the account that I start X from. So I guess this means that Fvwm is picking up some default .fvwmrc file from someplace. That's fine, and whereever it is, and whatever it contains, it seems to -mostly- fit my needs rather well, so I don't really need to diddle it... much. I've got a nice traditional clock face, and a nice xbiff thingy to tell me know when I have new mail. Perfect. But just below those things there is an empty space. I would very much like to place another xclock in that empty space as follows: xclock -digtal -strftime '%a %b %d %T' Can someone tell me how to do that?
Re: FVWM: two questions about icons
In message , you wrote: >On Wed, May 29, 2019 at 9:43 PM Ronald F. Guilmette > wrote: >> >> >> >> Greetings, >> >> First, the icon used to repreesent minimuzed Firefox windows is >> substantially larger than t was for the prior version(s) of fvwm >> that I had been accustomed to using. Since I tend to have a LOT >> of different brwosers windoes open and minimized on my screen, >> this is likely to cause me some consternation, over the long run. >> >> So, is there an alternative minimized icon available for Firefox? >> > >Fvwm doesn't come with a set of icons. Fvwm will honor the apps icon >that it provides via EWMH standards. This is also the case for xterm >or any other program. > >If you don't like the icon provided by the application you can >configure fvwm to use custom icons via the Icon Style (or >WindowStyle). For example if you find a firefox icon and put it in >your ImagePath, you can tell fvwm to use it for firefox as follows: > >Style firefox Icon firefox.png > >(you could also just use a full path for your icon specification). > >If you like the minimized window look, there are some custom functions >that do this using imagemagick to create an icon image and use it. > >https://fvwmforums.org/wiki/Tips/ThumbnailsAsIcons/ Thanks for all this info. I'm going to try to fish the old Firefox icon out of my old FreeBSD system. If I can find it, then I'll try to see if I can get fvwm to use it as you've instructed. If all else fails, I suppose that I can always RTFM, although I didn't (and don't) really know anything at all about this EWMH you mentioned. (But Google is my friend.) Hummm... did a find on my old system's /usr directory, searching for .png files, and I found several candidates that may be what I'm looking for, but I don't know which one is the Right One. I guess that it might help if I knew the size of the icon that fvwm on the new system was using to represent Opera. That's the size I want. So, how can I figure out the location, in the file system, of the icon that fvwm is using (on the new system I am configuring) for the Opera browser? I looked at a couple of man pages and didn't files any FILES sections at the end. :-( Regards, rfg P.S. I've just -quickly- glanced at the man page for fvwm. I think that it is marvelous that someone went to all of the trouble to well and properly document this tool. However, that having been said, please forgive me for just noting that in all of my multiple decades of using UNIX systems, this has got to be, by far, the single biggest/longest man page that I personally have ever seen. That's -not- a bad thing. More documentation is almost always better documentation. It's just a bit bewildering for a casual user, such as myself, who doesn't really have a year or two to become familiar with all of this stuff. But I guess that's why this mailing list exists, eh?
FVWM: two questions about icons
Greetings, I'm upgrading/replacing a rather old FreeBSD system that I've been neglecting for some time, and I installed the latest and greatest fwvm package on this new FreeBSD 12.0-RELEASE system. All appears to be working well so far, but there are two small annoyances. First, the icon used to repreesent minimuzed Firefox windows is substantially larger than t was for the prior version(s) of fvwm that I had been accustomed to using. Since I tend to have a LOT of different brwosers windoes open and minimized on my screen, this is likely to cause me some consternation, over the long run. So, is there an alternative minimized icon available for Firefox? I should perhaps mention also that I have already installed all three of teh followuing browsers onto this new FreeBSD system that I am just now setting up: Firefox, Opera, and Chromium (aka "chrome"). Somewhat unexpectedly, the minimized icons for each of these is a different size that the others (!) That's right, all three of the icons for these browsers are different sizes. That certainly seems a bit odd. Of all three, the icon used for Opera is the smallest and seems to be the closest to what I had historically seen, in terms of icon size, for Firefox. If this is just as issue with the FreeBSD port/package of fvwm, then by all means, please do tell me and I'll contact the revevant FreeBSD port maintainer instead pf whoever is manning this mailing list. Just one other thing: It has long been the case, even with the very old and very crusty version of fvwm that I'd been using in the past, that when I minimize a xterm window, I don't get any sort of an icon in that case. Rather, those minimized xterm windows end up plopping themselves over along the right hand edge of my screen, rather than along the bottom edge (as for the browser icons) and they look like small "squished" versions of the corresponding original un-minimized xterm windows. I'm perfectly OK with the placement of these, along the right hand edge of my screen, and in fact I prefer that, but I do wonder if it might not be possible to get those minimized xterm windows represented as small, standard sized icons also, instead of as smaller version of themselves. Any and all advice or help will be appreciated. Regards, rfg
FVWM: acroread9 -- Where's the minimize button?
Is it just me, or has anyone else experienced an oddity where the window containing acroread, unlike all other applications windows, fails to have a standard sort of minimization button in the upper right hand corner of the window frame? Is this is a known problem? Is there a workaround?
FVWM: Problems with fvwm-1.24 on FreeBSD 7.2-RELEASE/amd64
Greetings again, I should start by saying thank you to all of you who tried to help me the last time I dropped in here... quite a long time ago. I really did appreciate how much you all were willing to try to help me to transition from fvwm 1.24 to fvwm 2.xx, but ya know, some people just can't be helped. :-) But seriously, in the end it just came down to a matter of time. I just ran out of time to work on transitioning to fvwm 2.xx, and I managed, in the end, to hack my old .fvwmrc file around enough so that it would continue to do what I needed it to do (with fvwm-1.24), and as other tasks were pressing n me, I had to leave it at that. So anyway, I never did make that jump to fvwm 2.xx. Im still using fvwm-1.24. That situation perfectly acceptable to me, right up until recently, when I started trying to migrate myself from FreeBSD 7.0-RELEASE/i386 to 7.2-RELEASE/amd64. *Now* Ive got major trouble, and I'm in need of some friendly advice again. In a nutshell, I _have_ been able to build and install fvwm-1.24 onto FreeBSD 7.2-RELEASE/amd64 (from the FreeBSD ports tree), _however_ the resulting executable is behaving very badly indeed. It's using up 100% of the CPU time. Definitely bad, big time. So I want to try to run this thing under gdb, and see what (if anything) I can manage to puzzle out about why it may be pegging the CPU usage. This is where I get lost. I know real well how to use gdb on ``ordinary'' sorts of (text-output) programs, but I really have now idea how to run gdb on any sort of X11 application, must less on a window manager that's normally started out of my .xinitrc file. So could somebody here please pass me a clue? How does one use gdb to debug an X11 window manager? Where and how do you start gdb and the window manager? (I've really never even attempted anything even remotely like this before, so I'm just lost.) When answering, please assume that I've already managed to get fvwm compiled with -g (to include debugging info). I have. Thanks in advance for any help. Regards, rfg
Re: FVWM: Highly Ignorant - But Seeking Help
In message [EMAIL PROTECTED], you w rote: 2008/8/10 Thomas Adam [EMAIL PROTECTED]: http://edulinux.homeunix.org/~n6tadam/fvwm2rc-ronald Did you send me mail with this link before now?? I must have mised it entirely for some reason. So I am curious to know if this is OK -- or not. Some feedback from you, Ronald, if not from common courtesy would be the least you could do. Um... I apologize. I got seriously side-tracked. I've had more hardware problems, in addition to the ones that caused me to go and buy a new machine and try to install a fresh(er) version of FreeBSD on it at the same time (and then update all of my other stuff, including fvwm). But really, I have no excuse other than the fact that I just didn't feel that I had the time right now to learn what I needed to learn to make a go of things with fvwm2. (The good news is that it's terrifically sophisticated. The bad news is that it's terrifically sophisticated. :-) So anyway, I felt the need to get on to doing other things... like the suddenly critical task of upgrading, at long last, to BIND9 so as to avoid the widely predicted instant and horrible death... and so I put this (fvwm upgrade) on the back burner and just installed fvwm 1.24 on FreeBSD 7.0. I even had to tweek a few things in order to get even that to work, but all is essentially back to normal for me now. I did learn a few things in the process, and my old .fvwmrc file has in fact been tweeked by me a fair amount now. (I never really knew much about what was going on in there, but now I do have a better understanding, especially on the topic of why the startup of sub-thingies should really be done in the .fvwmrc file and _not_in my .xinitrc file.) Anyway, thank you, everybody, for all of the e-mails you sent about my attempt at upgrading. I really did save them all in my inbox with the hopes of getting back to that project someday. But you know the old saying... life is what happens while you are making other plans. (I really need an assistant here who could do the care and feeding of all of my machines and the routine software upgrades. Sigh. But I have no money for that, and it's just me, so I'm stuck trying to juggle every- thing.)
Re: FVWM: Highly Ignorant - But Seeking Help
In message [EMAIL PROTECTED], you wr ote: 2008/8/5 Ronald F. Guilmette [EMAIL PROTECTED]: I want a console xterm window (iconified) in the upper right of my screen, with a small font. Even though I start up X as an ordinary non-root user, I want that console xterm to be associated with the system console, i.e. so that I can de-iconify it anytime I want and look at recent console messages, e.g. if I think I'm being attacked and want to see recent IPFW firewall messages. (Yes, I _do_ know that I may have to see the permissions on the /dev/console very loosely in order to do this as an ordinary user. That's OK. I don't mind. I'm the only person that uses this system, ever.) So you mean xconsole, then? No, A real Xterm window. I'd like all Xterms to be associated with a proper sort of Xterm icon, like they were in the Old Days. (I just installed fvwm 2.4.0 from the ports collection on FreeBSD and the Xterm icon seems to no longer be associated with iconified Xterm windows. What did I do wrong?) You assumed. That's what's wrong. :P You probably need to copy over your existing .xpm files from your installation. OK, but aren't icons for usual things (e.g. Xterm) part of either fvwm or else the X window system itself? When I iconify ordinary windows (e.g. Firefox) I'd like them to iconify into positions along the RIGHT edge of the screen, starting at the top, just below the iconified console Xterm, and then going down along the right edge of my screen as I iconify more windows. That's the way that fvwm 1.x did things, but now, fvwm2 seems to want to iconify by default things like firefox into the LOWER LEFT corner of my screen. (What did I do wrong?) You didn't do anything wrong here -- by default unless you change it, the icon placements default to the whole screen. You want to specify the following in your config file: Style * IconBox a b c d, IconFill t r, IconGrid 30 30 Ummm... OK. Obviously. :-) I will talk more about this later. That will help. I'd kind-of like the colors of the borders of focused and unfocused windows to go back to the colors I selected for this with fvwm1, i.e. a sort of a light gold and a dark gold, respectively. With fvwm2, this seems to have cheanged into pink and dark grey. (Again, what did I do wrong?) Nothing. You're not aware of colorsets (in your case via FvwmTheme for FVWM 2.4.20). The way you're specifying the colours now for focused and unfocused windows are obsolete by far. OK, and to fix it, I do what? The only other stuff I really want is a numeric clock and an ordinary circular clock, someplace towards the bottom right of my screen, a little Xbiff mail thingy someplace down in that corner (at some convenient smallish size) and also down in that corner, a couple of buttons that I can press whenever I want to spawn a new Xterm that will run over on one or another of the other machines on my network, but that will display on the screen I'm looking at... the one under control of fvwm. And the default ConfigFvwmButtons file defines something approximating this. So what say you folks? Will anybody take pity on me and help me? Included below is (1) my current/old .xinitrc file and (2)my current/old .fvwmrc file that works OK with fvwm 1.x. (I don't even know where I got most of this stuff anymore. I probably just hacked around, haphazardly, on example config files provided with fvwm1 until I kind-of got what I wanted. But even that was only done years and years ago, and so I've even forgotten how fvwm1 works!) I will convert your .fvwmrc file to something which works on FVWM 2.5.26 -- and that's final. I am not going to bugger about on 2.4.20 setting up FvwmTheme, etc. You really do want FVWM 2.5.26 -- since you're on one of the *BSDs that's a shame, but I will let you figure out how to install that. :) OK, no problem. I can do that. FreeBSD is setup to allow install of either 2.4.0 or else the latesr 2.5.x. I have no problem using 2.5.x. The only reason I didn't start there was because it was said to me non-stable, and comments on the wab site to the effect that If something breaks with this, we won't help you. I will send you an email later after work with a modified file. Thank you a LOT!
FVWM: Highly Ignorant - But Seeking Help
Greetings, I've been using fvwm for a long long long long time, but I was never really very good at it. In fact, I've been using 1.24 for literally ages and ages. Now I want to _finally_ transition myself to fvwm2, but ... and this is a weird sort of criticism, I know... the thing is just TOO sophisticated. The man page is HUGE, and I was just barely able to figure out enough of fvwm1 to get done what I wanted to get done... which is very minimal... when I started with fvwm1, perhaps 8 or 9 years ago. Anyway, all I really want is to be able to take my current .fvwmrc file and move it over so that I mostly get the same effect(s) that I have been getting, up until now, with fvwm1. But when I just try to use my existing .fvwmrc file with fvwm2, all sort of things seems to break. I've started to try to work my way through the new man page for the new fvwm2, but it is very slow going for me, because I dopn't even understand most of the terminology. So anyway, I've come to this list in the hopes that somebody will take pity on me and just help me to get my old .fvwmrc file updated so that it will work properly with fvwm 2.40. Actually, my existing .fvwmrc file _does_ sort-of work a little bit, but as I say, many things seem broken. I'm hoping somebody here will help me with those things. NOTE: I'm including my current .fvwmrc file at the end of this message. My needs as regards to fvwm are really quite modest. I'll try to list them. (I work under FreeBSD, by the way.) I want a console xterm window (iconified) in the upper right of my screen, with a small font. Even though I start up X as an ordinary non-root user, I want that console xterm to be associated with the system console, i.e. so that I can de-iconify it anytime I want and look at recent console messages, e.g. if I think I'm being attacked and want to see recent IPFW firewall messages. (Yes, I _do_ know that I may have to see the permissions on the /dev/console very loosely in order to do this as an ordinary user. That's OK. I don't mind. I'm the only person that uses this system, ever.) I'd like all Xterms to be associated with a proper sort of Xterm icon, like they were in the Old Days. (I just installed fvwm 2.4.0 from the ports collection on FreeBSD and the Xterm icon seems to no longer be associated with iconified Xterm windows. What did I do wrong?) When I iconify ordinary windows (e.g. Firefox) I'd like them to iconify into positions along the RIGHT edge of the screen, starting at the top, just below the iconified console Xterm, and then going down along the right edge of my screen as I iconify more windows. That's the way that fvwm 1.x did things, but now, fvwm2 seems to want to iconify by default things like firefox into the LOWER LEFT corner of my screen. (What did I do wrong?) I'd kind-of like the colors of the borders of focused and unfocused windows to go back to the colors I selected for this with fvwm1, i.e. a sort of a light gold and a dark gold, respectively. With fvwm2, this seems to have cheanged into pink and dark grey. (Again, what did I do wrong?) The only other stuff I really want is a numeric clock and an ordinary circular clock, someplace towards the bottom right of my screen, a little Xbiff mail thingy someplace down in that corner (at some convenient smallish size) and also down in that corner, a couple of buttons that I can press whenever I want to spawn a new Xterm that will run over on one or another of the other machines on my network, but that will display on the screen I'm looking at... the one under control of fvwm. That's all I really need. Like I said, I'm not very sophisticated, and my needs are modest. (I'm mostly a command-line sort of guy... a leftover from the early days of computing when that was all we had. So that's why pretty much all I need is buttons for launching Xterms on various systems on my network. Although a little button to launch firefox locally would be nice too. But I don't have that right now.) So what say you folks? Will anybody take pity on me and help me? Included below is (1) my current/old .xinitrc file and (2)my current/old .fvwmrc file that works OK with fvwm 1.x. (I don't even know where I got most of this stuff anymore. I probably just hacked around, haphazardly, on example config files provided with fvwm1 until I kind-of got what I wanted. But even that was only done years and years ago, and so I've even forgotten how fvwm1 works!) Current .xinitrc file: == #!/bin/sh xhost +goofy.lan.tristatelogic.com xhost +lapdog.lan.tristatelogic.com #xset s on xset dpms 900 1800 0 # Startup script and setting up the Xserver #xrdb -display $DISPLAY $HOME/.Xdefaults $HOME/.xrdb.log 21 #xsetroot -bitmap $HOME/.wood_grain.xbm -fg black -bg '#a05000' xsetroot -solid black xset s
