From: Alan Grimes <alonzotg@verizon.net>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] chromium and dbus...
Date: Fri, 28 Apr 2023 11:15:01 -0400 [thread overview]
Message-ID: <c3bed095-77d9-b11d-a3bd-d7b7781af593@verizon.net> (raw)
In-Reply-To: c3bed095-77d9-b11d-a3bd-d7b7781af593.ref@verizon.net
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.
next parent reply other threads:[~2023-04-28 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c3bed095-77d9-b11d-a3bd-d7b7781af593.ref@verizon.net>
2023-04-28 15:15 ` Alan Grimes [this message]
2023-04-28 15:37 ` [gentoo-user] Re: chromium and dbus Grant Edwards
2023-04-28 16:09 ` [gentoo-user] " julien
2023-04-28 16:16 ` [gentoo-user] " Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c3bed095-77d9-b11d-a3bd-d7b7781af593@verizon.net \
--to=alonzotg@verizon.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox