Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.os.linux > #80737
| From | Jim Diamond <zsd@jdvb.ca> |
|---|---|
| Newsgroups | alt.os.linux |
| Subject | chromium error messages |
| Date | 2024-11-01 12:03 -0300 |
| Organization | A noiseless patient Spider |
| Message-ID | <slrnvi9re2.3fe.zsd@x360.localdomain> (permalink) |
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
Back to alt.os.linux | Previous | Next — Next in thread | Find similar | Unroll thread
chromium error messages Jim Diamond <zsd@jdvb.ca> - 2024-11-01 12:03 -0300
Re: chromium error messages Paul <nospam@needed.invalid> - 2024-11-01 15:15 -0400
Re: chromium error messages Jim Diamond <zsd@jdvb.ca> - 2024-11-03 17:26 -0400
Re: chromium error messages ("SOLVED") Jim Diamond <zsd@jdvb.ca> - 2024-11-26 12:19 -0400
csiph-web