From: nospam@needed.invalid   
      
   On Fri, 11/1/2024 11:03 AM, Jim Diamond wrote:   
   > I use Slackware and tried a.o.l.s. first, but no luck there, so I am   
   > casting a wider net...   
   >   
   > I am using chromium-130.0.6723.58 (fwiw, this is the package   
   > chromium-130.0.6723.58-x86_64-1alien provided by Alien Bob) on   
   > Slackware64-15.0.   
   >   
   > It spits out huge number of errors like this:   
   >   
   > [11991:12010:1026/204311.343452:ERROR:bus.cc(407)] Failed to connect to the   
   >   bus: Could not parse server address: Unknown address type (examples of   
   valid   
   >   types are "tcp" and on UNIX "unix")   
   >   
   > I've googled around, but haven't been able to find any relevant articles.   
   >   
   > Does anyone here know what is causing this, and maybe even what I need to   
   > do to make chromium happy?   
   >   
   > I don't know if it is at all relevant, but I am using fvwm3, as opposed to   
   > a "desktop environment", and I don't know if I am missing some component   
   > that chromium needs to make it happy.   
   >   
   > (FWIW, chromium-126.0.6478.182-x86_64-1alien did the same thing.)   
   >   
   > Thanks for any cogent suggestions.   
   >   
   >                                 Jim   
      
    Around line 396 then, is where it spits out the error. The clause generating   
   the error is copied below.   
   It would help if the error message also printed out the   address_.c_str()    
   value.   
      
   https://chromium.googlesource.com/chromium/src/dbus/+/fd82f2808d   
   4c896a543b87cc5e973fb0eb8ceb2/bus.cc   
      
     if (bus_type_ == CUSTOM_ADDRESS) {   
       if (connection_type_ == PRIVATE) {   
         connection_ = dbus_connection_open_private(address_.c_str(),   
   error.get());   
       } else {   
         connection_ = dbus_connection_open(address_.c_str(), error.get());   
       }   
      
   No, I don't know what that means :-) Just following the breadcrumbs.   
      
   The root cause will be, some "filter" stage along the way, has messed   
   with the string a little too much, denuding it. Like, maybe the string   
   has a length of zero, as an example. It is unlikely to be a perfectly   
   good string it is tripping over -- unless DBUS is failing entirely,   
   like your arch doesn't even have a DBUS. I've seen that on occasion,   
   a piece of software attempts to talk to DBUS, when there isn't one.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)