It looks like chromium has no freakin idea how to use dbus...

A decenently good OS would provide an IPC mechanism and little else. =|
So basically this is just a hack-layer to get around the inherent fact
that linux is garbage.

Dbus is in my runlevels and shows no errors when I poke it with the
script in /etc/init.d


I've been limping along on Konqueror and it is generating completely
routine dbus traffic no issues:

atg@tortoise ~ $ dbus-monitor --session
[....]
signal time=1682692275.716176 sender=:1.5 -> destination=(null
destination) serial=339394 path=/KonqHistoryManager; interface=org.kde.Konqueror.HistoryManager; member=notifyHistoryEntry
   array of bytes [
      00 00 00 68 00 68 00 74 00 74 00 70 00 73 00 3a 00 2f 00 2f 00 77 00 77
      00 77 00 2e 00 66 00 72 00 65 00 65 00 64 00 65 00 73 00 6b 00 74 00 6f
      00 70 00 2e 00 6f 00 72 00 67 00 2f 00 77 00 69 00 6b 00 69 00 2f 00 49
      00 6e 00 74 00 72 00 6f 00 64 00 75 00 63 00 74 00 69 00 6f 00 6e 00 54
      00 6f 00 44 00 42 00 75 00 73 00 2f ff ff ff ff ff ff ff ff 00 00 00 01
      00 00 00 00 00 25 89 9f 02 41 f0 04 00 00 00 00 00 00 25 89 9f 02 41 f0
      04 00 00 00 00 08 00 3a 00 31 00 2e 00 35
   ]
signal time=1682692276.678553 sender=:1.5 -> destination=(null
destination) serial=339395 path=/KonqHistoryManager; interface=org.kde.Konqueror.HistoryManager; member=notifyHistoryEntry
   array of bytes [
      00 00 00 68 00 68 00 74 00 74 00 70 00 73 00 3a 00 2f 00 2f 00 77 00 77
      00 77 00 2e 00 66 00 72 00 65 00 65 00 64 00 65 00 73 00 6b 00 74 00 6f
      00 70 00 2e 00 6f 00 72 00 67 00 2f 00 77 00 69 00 6b 00 69 00 2f 00 49
      00 6e 00 74 00 72 00 6f 00 64 00 75 00 63 00 74 00 69 00 6f 00 6e 00 54
      00 6f 00 44 00 42 00 75 00 73 00 2f ff ff ff ff 00 00 00 24 00 49 00 6e
      00 74 00 72 00 6f 00 64 00 75 00 63 00 74 00 69 00 6f 00 6e 00 54 00 6f
      00 44 00 42 00 75 00 73 00 00 00 00 00 00 00 00 00 25 89 9f 02 41 f3 c6
      00 00 00 00 00 00 25 89 9f 02 41 f3 c6 00 00 00 00 08 00 3a 00 31 00 2e
      00 35
   ]
method call time=1682692306.604101 sender=:1.82 -> destination=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello


Today's update did nothing to chromium.

Apparently by doing nothing whatsoever, I managed to make the only
system in the world that can't run chromium in this way but seems fine
on all other apps. =\

--
Beware of Zombies. =O
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 2023-04-28 at 11:15 -0400, Alan Grimes wrote:

So basically this is just a hack-layer to get around the inherent
fact
that linux is garbage.

I don't think shitting on Linux will attract a lot of help on this
mailing list. Nevertheless...

Dbus is in my runlevels and shows no errors when I poke it with the
script in /etc/init.d

What login manager and DE/WM are you using? If you're using a WM, it's
your own reponsibility to setup dbus when starting your session. A DE
will do this for you.

Typically, you can start your WM using `dbus-run-session <wm>`, at
least for Wayland. I'm not familiar with X11 but maybe you can use the
same command.

That said, I'm not sure dbus is the problem with chromium, since you're
still having the same network error when starting it with `dbus-launch chromium`...

Have you seen https://github.com/systemd/systemd/issues/22223 ?

The last comment sounds pertinent:

after update package dev-libs/icu to version 72.1 and rebuild
chromium, chromium work well.

Maybe an incompatible icu version caused this problem.

--
Julien

-----BEGIN PGP SIGNATURE-----

iQGTBAABCgB9FiEEUri1ZrRDZASH+Q0NvvIpdEiEiEIFAmRL76xfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDUy QjhCNTY2QjQ0MzY0MDQ4N0Y5MEQwREJFRjIyOTc0NDg4NDg4NDIACgkQvvIpdEiE iELtdwgAvu2hBGCCBOp11fAz1VzU3fUk+On7t/dpgWzSSTYl4ytadGv+RjdycnWD 7uG65PRdVHGHXaKO0DXvN2sWuFqw7RRNLM3Lpi5wKpfueagtxmdDDBKzRhaiaFRt J5t+l6v5v9ZM4ZgKn0mDVIMgDaGSIxuA98O0wDIUty6grkz2bHtJSpv85woxPVIL YwggVdcVRV6xDrU6iFD9VcR8MbZV0+qt3lYoJN/VRbkrZ/ooS06zE0qbdXp/7Dwv aeDKKT4b+If46PnbJxt/ltVcZJk/8pLwFGwnggoqryl62zF5+/eHNQC798dqva/M bAUiS5hJHljGDIpxQwZqfGfG279jeg==
=VSja
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2023-04-28, Alan Grimes <alonzotg@verizon.net> wrote:

A decenently good OS would provide an IPC mechanism and little else. =|
So basically this is just a hack-layer to get around the inherent fact
that linux is garbage.

Then one might wonder why you don't stop using it.

--
Grant

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2023-04-28, julien@jroy.ca <julien@jroy.ca> wrote:

What login manager and DE/WM are you using? If you're using a WM,
it's your own reponsibility to setup dbus when starting your
session. A DE will do this for you.

Typically, you can start your WM using `dbus-run-session <wm>`, at
least for Wayland. I'm not familiar with X11 but maybe you can use
the same command.

That said, I'm not sure dbus is the problem with chromium, since
you're still having the same network error when starting it with
`dbus-launch chromium`...

I have always seen lots of dbus errors from chromium and chrome (and
various other apps). I don't run a "desktop environment", don't use a
display manager, and don't start my WM (openbox) with a dbus session.

There are probably some features of chromium/chrome that don't work
because of that (but I don't know what they might be). Neither has
ever any stability issues for me.

Dbus does seem to auto-start and work enough that Thunderbird can
tell me of incoming e-mails with desktop notifications...


$ chromium
[3339:3365:0428/111152.793404:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3339:3365:0428/111152.794422:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3339:3365:0428/111152.847772:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3339:3365:0428/111152.847804:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3339:3365:0428/111152.882407:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3339:3365:0428/111152.882447:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3339:3498:0428/111153.007404:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any
.service files
[3339:3498:0428/111153.007565:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by
any .service files
[3339:3498:0428/111153.007720:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by
any .service files
[3339:3363:0428/111154.521351:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3339:3339:0428/111154.521447:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
[3339:3363:0428/111154.521569:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3339:3339:0428/111154.521635:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
[3339:3363:0428/111154.521753:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3339:3339:0428/111154.521816:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
[3339:3363:0428/111154.521933:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3339:3339:0428/111154.521992:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
[3339:3363:0428/111154.522125:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[3339:3339:0428/111154.522186:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.

Have you seen https://github.com/systemd/systemd/issues/22223 ?

The last comment sounds pertinent:

after update package dev-libs/icu to version 72.1 and rebuild
chromium, chromium work well.

Maybe an incompatible icu version caused this problem.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)