[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-user
Subject:    Re: [gentoo-user] Gcc 13.1 and chromium
From:       Paul Colquhoun <paulcol () andor ! dropbear ! id ! au>
Date:       2023-04-28 4:59:53
Message-ID: 1947329.usQuhbGJ8B () w540 ! andor ! dropbear ! id ! au
[Download RAW message or body]

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




[prev in list] [next in list] [prev in thread] [next in thread]