Re: [gentoo-user] Gcc 13.1 and chromium
On Friday, April 28, 2023 4:40:24 A.M. AEST Alan Grimes wrote: > I rebuilt my system on gcc 13.1. I think the compiler is good but it > exposed some bugs in a handful of packages, these are: > > tortoise /var/tmp/portage # tree -L 2 > . > ├── app-editors > │ └── scite-5.3.5 > ├── media-libs > │ ├── liblo-0.31 > │ └── nas-1.9.5 > └── media-sound > └── audacity-3.2.5 > > 8 directories, 0 files > tortoise /var/tmp/portage # > > I trust these will be patched and upstream will be notified, hardly > worth commenting actually. > > Chromium still shows the same error pattern but generated crashes at a > slower rate than previously, the result is that I was able to collect > error messages from the very beginning of the run: > > > atg@tortoise ~ $ chromium > [19039:19057:0427/143338.626886: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") > [19039:19057:0427/143338.626944: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") Have you tried starting it with: strace chromium to get debugging info on each system call. I might show you where the bad server address is coming from, as it will list all the files that are opened. -- Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/ Asking for technical help in newsgroups? Read this first: http://catb.org/~esr/faqs/smart-questions.html#intro
Re: [gentoo-user] Gcc 13.1 and chromium
David Rosenbaum wrote: This seems to be an environment variable issue. Do you have a value set for DBUS_SESSION_BUS_ADDRESS? No. I don't have the slightest clue as to anything whotsoever about dbus or how to begin to fix it, or why I suddenly need to know how to fix it. I know that the Unix signals system is absolute garbage but that's it... -- Beware of Zombies. =O #EggCrisis #BlackWinter White is the new Kulak. Powers are not rights.
Re: [gentoo-user] Gcc 13.1 and chromium
jul...@jroy.ca wrote: On Thu, 2023-04-27 at 14:40 -0400, Alan Grimes wrote: atg@tortoise ~ $ chromium [19039:19057:0427/143338.626886: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") This seems to be an environment variable issue. Do you have a value set for DBUS_SESSION_BUS_ADDRESS? Try `dbus-launch chromium` Interesting, I know not about dbus... No idea why my policy of benign neglect suddenly stopped working. Still doesn't work but the barf changed slightly. atg@tortoise ~ $ dbus-launch chromium [50590:50590:0427/225551.905078:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled. [50590:50590:0427/225551.958159:ERROR:network_service_instance_impl.cc(541)] Network service crashed, restarting service. [50590:50590:0427/225551.984259:ERROR:network_service_instance_impl.cc(541)] Network service crashed, restarting service. [LATER] [50590:50590:0427/225552.885388:ERROR:network_service_instance_impl.cc(541)] Network service crashed, restarting service. [50590:50612:0427/225552.904674:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.StartServiceByName: object_path= /org/freedesktop/DBus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [50590:50590:0427/225552.910883:ERROR:network_service_instance_impl.cc(541)] Network service crashed, restarting service. [50590:50590:0427/225552.936156:ERROR:network_service_instance_impl.cc(541)] Network service crashed, restarting service. -- Beware of Zombies. =O #EggCrisis #BlackWinter White is the new Kulak. Powers are not rights.
Re: [gentoo-user] Gcc 13.1 and chromium
Dave On Thu, Apr 27, 2023, 14:52 jul...@jroy.ca wrote: > On Thu, 2023-04-27 at 14:40 -0400, Alan Grimes wrote: > > atg@tortoise ~ $ chromium > > [19039:19057:0427/143338.626886: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") > > This seems to be an environment variable issue. > Do you have a value set for DBUS_SESSION_BUS_ADDRESS? > > Try `dbus-launch chromium` > > -- > Julien >
Re: [gentoo-user] Gcc 13.1 and chromium
On Thu, 2023-04-27 at 14:40 -0400, Alan Grimes wrote: > atg@tortoise ~ $ chromium > [19039:19057:0427/143338.626886: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") This seems to be an environment variable issue. Do you have a value set for DBUS_SESSION_BUS_ADDRESS? Try `dbus-launch chromium` -- Julien signature.asc Description: This is a digitally signed message part
[gentoo-user] Gcc 13.1 and chromium
I rebuilt my system on gcc 13.1. I think the compiler is good but it exposed some bugs in a handful of packages, these are: tortoise /var/tmp/portage # tree -L 2 . ├── app-editors │ └── scite-5.3.5 ├── media-libs │ ├── liblo-0.31 │ └── nas-1.9.5 └── media-sound └── audacity-3.2.5 8 directories, 0 files tortoise /var/tmp/portage # I trust these will be patched and upstream will be notified, hardly worth commenting actually. Chromium still shows the same error pattern but generated crashes at a slower rate than previously, the result is that I was able to collect error messages from the very beginning of the run: atg@tortoise ~ $ chromium [19039:19057:0427/143338.626886: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") [19039:19057:0427/143338.626944: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") [19039:19039:0427/143338.670482:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled. [19039:19057:0427/143338.731872: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") [19039:19057:0427/143338.731887: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") [19039:19057:0427/143339.201394: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") [19039:19057:0427/143339.201408: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") [19039:19039:0427/143339.237821:ERROR:network_service_instance_impl.cc(541)] Network service crashed, restarting service. [19039:19039:0427/143339.263712:ERROR:network_service_instance_impl.cc(541)] Network service crashed, restarting service. [19039:19039:0427/143339.289434:ERROR:network_service_instance_impl.cc(541)] Network service crashed, restarting service. [repeats indefinitely] -- Beware of Zombies. =O #EggCrisis #BlackWinter White is the new Kulak. Powers are not rights.
