Following up on the above, on current with the most recent version of all packages, the initial attempt to start iridium core dumps with the following:
``` [rdahlgren@builder :: ~] $ iridium [59856:-1030190016:1120/113635.371153:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory libGL error: MESA-LOADER: failed to retrieve device information libGL error: MESA-LOADER: failed to open i915: Cannot load specified object (search paths /usr/X11R6/lib/modules/dri, suffix _dri) libGL error: failed to load driver: i915 libGL error: failed to open /dev/dri/card0: No such file or directory libGL error: failed to load driver: i965 libGL error: MESA-LOADER: failed to open swrast: Cannot load specified object (search paths /usr/X11R6/lib/modules/dri, suffix _dri) libGL error: failed to load driver: swrast zsh: trace trap (core dumped) iridium ``` Note that chromium works without issue, firefox works, and glxgears works. I've emailed the iridium maintainer as well but have not received a response. Ron On Fri, Nov 3, 2023 at 6:35 PM Ronald Dahlgren <ronald.dahlg...@gmail.com> wrote: > Hello, > > I'm running 7.4 GENERIC.MP#1440 amd64 and the latest iridium package, > iridium-2023.10.118. Lately, iridium has been failing to start, immediately > dying with a core dump: > ``` > [rdahlgren@ranger2 :: ~] $ iridium > [89014:-471097792:1103/183201.949947:ERROR:bus.cc(407)] Failed to connect > to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No > such file or directory > zsh: trace trap (core dumped) iridium > ``` > > Note that if the messagebus service is started, the dbus error goes away > but the core dump still occurs. This has been happening for at least a > week, across the intervening snapshots and package updates. > > How can I collect more information to identify the problem? Nothing > relevant appears in /var/log/messages > > Respectfully, > Ron > > -- > RD > > -- RD
