From: zsd@jdvb.ca   
      
   On 2024-11-29 at 17:52 AST, #Paul    
   wrote:   
   > Jim Diamond  wrote:   
   >> The problem was that I was starting my window manager (fvwm3) in such a way   
   >> that DBUS_SESSION_BUS_ADDRESS was not defined.  Apparently not having this   
   >> environment variable defined upsets chromium to no end.   
   >   
   > There is quite a lot of this sort of thing. In my setup I use a range   
   > of different usernames for different things: personal stuff, work,   
   > work emails, browsing the net, games, banking. So I log in as one user   
   > (with fvwm) and then -- in various virtual windows and workspaces --   
   > fire the various things up from terminals running as the selected   
   > user, i.e. where I have logged in or su'd to whichever user it happens   
   > to be.   
   >   
   > But some "modern" software, including browswers, seem to expect a   
   > bunch of env stuff to be defined, set, or created by some sort of full   
   > login process; and therefore tend to bitterly complain if (eg)   
   > XDG_RUNTIME_DIR is not set, or is pointing to the "wrong" place, or   
   > has not been created as expected.  Usually I just write some   
   > little wrapper scripts to sort it all out manually.   
   >   
   > I would like to say that it is all sorted now, but if I do, no doubt   
   > something else will turn up... after all, I don't seem to have noticed   
   > any DBUS_SESSION_BUS_ADDRESS warnings yet. :-/   
      
   Maybe we (or better yet, someone else :-) needs to create a page on the   
   fvwm wiki listing all the "desktop environment" environment variables that   
   fvwm doesn't set up but which various programs get upset about.   
      
                                   Jim   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)