chromium (Alien Bob version) whinage

[Jim Diamond]

I am using Alien Bob's chromium chromium-130.0.6723.58-x86_64-1alien
package on S64-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?

(FWIW, chromium-126.0.6478.182-x86_64-1alien did the same thing.)

Thanks.
Jim

[root]

Post by Jim Diamond
I am using Alien Bob's chromium chromium-130.0.6723.58-x86_64-1alien
package on S64-15.0.
[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?
(FWIW, chromium-126.0.6478.182-x86_64-1alien did the same thing.)
Thanks.
Jim

I'm sorry I can't help with your problem Jim, but I have a question.
Have you recently switched over to Slackware 15? Also, why would
one prefer Alien Bob's Chromium over Google's google-chrome-stable?

[Jim Diamond]

Post by root

Post by Jim Diamond
I am using Alien Bob's chromium chromium-130.0.6723.58-x86_64-1alien
package on S64-15.0.
[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?
(FWIW, chromium-126.0.6478.182-x86_64-1alien did the same thing.)
Thanks.
Jim

I'm sorry I can't help with your problem Jim, but I have a question.
Have you recently switched over to Slackware 15? Also, why would
one prefer Alien Bob's Chromium over Google's google-chrome-stable?

Hi root,

no, I've been using S15 since February 8, 2022. (Not recent unless you are
a geologist. ;-)

My reasons for using chromium (as opposed to chrome) are now mostly lost in
the depths of time, but I have a vague recollection about chromium not
tracking you to the same degree as chrome does. While I don't have any
major secrets I'm hiding from google, they don't need to know everything
about me, either.

(And yes, I realize that Alien Bob has a package which is more de-googled,
and perhaps I should be using that.)

Cheers.

Jim

[Alexander Grotewohl]

Post by Jim Diamond

Post by root

Post by Jim Diamond
I am using Alien Bob's chromium chromium-130.0.6723.58-x86_64-1alien
package on S64-15.0.

I'm sorry I can't help with your problem Jim, but I have a question.
Have you recently switched over to Slackware 15? Also, why would one
prefer Alien Bob's Chromium over Google's google-chrome-stable?

My reasons for using chromium (as opposed to chrome) are now mostly lost
in the depths of time, but I have a vague recollection about chromium
not tracking you to the same degree as chrome does. While I don't have
any major secrets I'm hiding from google, they don't need to know
everything about me, either.
(And yes, I realize that Alien Bob has a package which is more
de-googled, and perhaps I should be using that.)

i use the chromium-ungoogled build from him to access a plugin for the
LINE messenger, so i don't use it extensively, but i did poke around some
websites today to fake it and i didn't get those errors.

unsolicited but i think it's neat:

https://github.com/NeverDecaf/chromium-web-store

will net you normal plugin support again.. though i'd imagine you're
undoing a minor bit of of degoogling at that point (it watches for
updates)

[Jim Diamond]

Post by Alexander Grotewohl

Post by Jim Diamond

Post by root

Post by Jim Diamond
I am using Alien Bob's chromium chromium-130.0.6723.58-x86_64-1alien
package on S64-15.0.

I'm sorry I can't help with your problem Jim, but I have a question.
Have you recently switched over to Slackware 15? Also, why would one
prefer Alien Bob's Chromium over Google's google-chrome-stable?

My reasons for using chromium (as opposed to chrome) are now mostly lost
in the depths of time, but I have a vague recollection about chromium
not tracking you to the same degree as chrome does. While I don't have
any major secrets I'm hiding from google, they don't need to know
everything about me, either.
(And yes, I realize that Alien Bob has a package which is more
de-googled, and perhaps I should be using that.)

i use the chromium-ungoogled build from him to access a plugin for the
LINE messenger, so i don't use it extensively, but i did poke around some
websites today to fake it and i didn't get those errors.
https://github.com/NeverDecaf/chromium-web-store
will net you normal plugin support again.. though i'd imagine you're
undoing a minor bit of of degoogling at that point (it watches for
updates)

Thanks for your comments. I wonder if I am missing some "desktop
environment" thing (I use fvwm3), or whether there is some other weird
thing happening on my system. Oh well...

Jim

[King Beowulf]

Post by Jim Diamond
I am using Alien Bob's chromium chromium-130.0.6723.58-x86_64-1alien
package on S64-15.0.
[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?
(FWIW, chromium-126.0.6478.182-x86_64-1alien did the same thing.)
Thanks.
Jim

Using Slackware64 15.0 with Xfce and Alienbob's

Version 130.0.6723.91 (Official Build, ungoogled-chromium) (64-bit)

works great, esp. for my accessing corporate overlord's microsoft azure
nonsense

-kb

[Jim Diamond]

Post by Jim Diamond
I am using Alien Bob's chromium chromium-130.0.6723.58-x86_64-1alien
package on S64-15.0.
[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?
(FWIW, chromium-126.0.6478.182-x86_64-1alien did the same thing.)

Just in case anyone comes across this in the future...

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.

Jim

[#Paul]

Post by Jim Diamond
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. :-/

#Paul

[Jim Diamond]

Post by #Paul

Post by Jim Diamond
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