Thomas Adam writes: > On Sat, Jul 23, 2011 at 07:38:49PM +0100, Thomas Adam wrote: > > On Sat, Jul 23, 2011 at 11:56:19AM -0600, Glenn Golden wrote: > > > Recently I was capturing stderr from fvwm for debug purposes, and I notic >ed > > > that it contains some early error messages that look like they were gener >ated > > > by fvwm-menu-desktop. (The messages are identical to those seen when simp >ly > > > invoking fvwm-menu-desktop from a bash commandline with no args.) > > > > > > These messages appear in the stderr stream prior to various "Echo" messag >es > > > that are issued by my StartFunction. And there's nothing in my config fil >e > > > that explicitly invokes fvwm-menu-desktop (in fact my configuration does >not > > > use xdg menu generation at all). This is why I am wondering if fvwm-menu- >desktop > > > is being invoked as a routine part of the init sequence. > > > > > > If so, is there a simple (i.e. config-able) way to prevent fvwm-menu-desk >top > > > from being invoked? > > > > It gets called from SetRCDefaults() in fvwm.c -- but it's been designed to > > only be enacted if you're using the builtin menu and you move your mouse > > over the entry marked "Desktop Menu". That's the only point at which > > fvwm-desktop-menu is invoked there. > >
[Assuming you meant fvwm-menu-desktop.] > > > > There might be something else starting it though, it depends how you're > > running FVWM. When you say there's nothing in your config file, that's > > *NOT* the same as you invoking: > > > > fvwm -f /dev/null > > > > which you should do to be absolutely sure FVWM isn't invoking > > fvwm-menu-desktop directly through some system-wide config file, or > > something. > My .xinit invokes fvwm like this: $ fvwm -f $HOME/.fvwm/config So when ~/.fvwm/config is stripped down to contain only a comment, I suspect fvwm's init behavior should not differ from $ fvwm -f /dev/null unless fvwm somehow differentiates between an empty file (/dev/null) and one containing only a comment. In any case, to put this particular sub-question to rest: I just started fvwm with "-f /dev/null" and got the same results as earlier described. So again this seems to point away from anything having to do with my config setup. > > Oh, and if you could actually *paste* these errors as well -- you'll get the > same ones as you running: > > fvwm-menu-desktop > > directly from a terminal. I'm not a mind-reader. > No? I thought that was available as an fvwm module... :) Here is the entire stdout, as obtained via $ fvwm -f /dev/null 2> fvwm_errs and then, as soon as fvwm comes up, kill(1)ing it from another VT. No mouse operations (or anything else) was done within fvwm prior to killing it. I used kill(1) rather than "Exit" from the builtin menu to even further eliminate any possibility of an accidental mouse-over on the "Desktop Menu" item. ============================================================================= WARNING: '/etc/xdg/menus/applications-kmenuedit.menu' does not exist Unknown 'Layout': 'HASH(0x856bd5c) Merge ARRAY(0x856bdec) Separator ARRAY(0x856bdbc) Merge ARRAY(0x856be70)' [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from mini.folder.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from mini.cat.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from mini.folder.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from mini.cat.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from mini.folder.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from mini.cat.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from mini.folder.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from mini.ofolder.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from mini.ofolder.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from mini.ofolder.xpm ============================================================================= The first two lines are identical to the stderr from $ fvwm-menu-desktop except for the specific address values of the hashes of course. Just to emphasize: The issue for me is not the underlying cause of these particular errors being generated by fvwm-menu-desktop (or whoever is generating them); it wouldn't surprise me to learn (e.g.) that my /etc/xdg is horribly misconfigured or in some half-baked state. My system is a heavily customzed mash-up of Redhat and CentOS distros, and I don't use any of the dynamic menu generation stuff at all, nor do I use gnome or kde desktop (or any "desktop environment" for that matter.) My only question is the relatively academic one of simply understanding why in the wide world fvwm-menu-desktop is being invoked at all [if in fact it is], since I haven't [knowingly] requested it, and whether there is any way to avoid it (and whether it might possibly even be a bug that it is being invoked.) Thanks, Glenn