GNOME debugging thread

J

j0rgeOP•8/22/25, 1:38 AM

yo

J

Jordan 🌱•8/22/25, 1:38 AM

Aug 22 05:07:20 bluefin org.gnome.Shell.desktop[1686]: (EE) could not connect to wayland server

Aug 22 05:07:20 bluefin org.gnome.Shell.desktop[1686]: (EE) could not connect to wayland server

Aug 22 05:07:20 bluefin org.gnome.Shell.desktop[1686]: (EE) could not connect to wayland server

Aug 22 05:07:20 bluefin org.gnome.Shell.desktop[1686]: (EE) could not connect to wayland server

J

Jordan 🌱•8/22/25, 1:39 AM

I think this is the culprit

T

tulip•8/22/25, 1:39 AM

rootful xwayland definitely works btw

J

Jordan 🌱•8/22/25, 1:39 AM

and the issue matches this one https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8506

T

tulip•8/22/25, 1:39 AM

seems that the shell is failing to start rootless xwalyand on-login

JJordan 🌱`Aug 22 05:07:20 bluefin org.gnome.Shell.desktop[1686]: (EE) could not connect t...

J

Jordan 🌱•8/22/25, 1:39 AM

wait no, this is from 50m before the other one

JJordan 🌱and the issue matches this one https://gitlab.gnome.org/GNOME/gnome-shell/-/iss...

J

James•8/22/25, 1:40 AM

love the not gnome tag

J

Jordan 🌱•8/22/25, 1:41 AM

Aug 22 05:57:18 localhost /usr/libexec/gdm-wayland-session[1638]: dbus-daemon[1638]: [session uid=42 pid=1638] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=42 pid=1639 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Aug 22 05:57:18 localhost /usr/libexec/gdm-wayland-session[1638]: dbus-daemon[1638]: [session uid=42 pid=1638] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 22 05:57:18 localhost gnome-session[1639]: gnome-session-binary[1639]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Aug 22 05:57:18 localhost gnome-session-binary[1639]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1

Aug 22 05:57:18 localhost /usr/libexec/gdm-wayland-session[1638]: dbus-daemon[1638]: [session uid=42 pid=1638] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=42 pid=1639 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Aug 22 05:57:18 localhost /usr/libexec/gdm-wayland-session[1638]: dbus-daemon[1638]: [session uid=42 pid=1638] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 22 05:57:18 localhost gnome-session[1639]: gnome-session-binary[1639]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Aug 22 05:57:18 localhost gnome-session-binary[1639]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1

Aug 22 05:57:18 localhost /usr/libexec/gdm-wayland-session[1638]: dbus-daemon[1638]: [session uid=42 pid=1638] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=42 pid=1639 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Aug 22 05:57:18 localhost /usr/libexec/gdm-wayland-session[1638]: dbus-daemon[1638]: [session uid=42 pid=1638] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 22 05:57:18 localhost gnome-session[1639]: gnome-session-binary[1639]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Aug 22 05:57:18 localhost gnome-session-binary[1639]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1

Aug 22 05:57:18 localhost /usr/libexec/gdm-wayland-session[1638]: dbus-daemon[1638]: [session uid=42 pid=1638] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=42 pid=1639 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Aug 22 05:57:18 localhost /usr/libexec/gdm-wayland-session[1638]: dbus-daemon[1638]: [session uid=42 pid=1638] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 22 05:57:18 localhost gnome-session[1639]: gnome-session-binary[1639]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Aug 22 05:57:18 localhost gnome-session-binary[1639]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1

J

Jordan 🌱•8/22/25, 1:41 AM

these also match

J

Jordan 🌱•8/22/25, 1:41 AM

do you have a delta of things that changed when this first started

J

James•8/22/25, 1:42 AM

I think systemd bumped

J

Jordan 🌱•8/22/25, 1:43 AM

oh

J

James•8/22/25, 1:44 AM

let me do an ostree diff one sec

J

James•8/22/25, 1:46 AM

I actually need to downgrade again to a working image

J

Jordan 🌱•8/22/25, 1:46 AM

no worries

J

Jordan 🌱•8/22/25, 1:47 AM

get the details of what changed and when/how it started happening and we can bisect the compoments from there

J

James•8/22/25, 1:55 AM

  systemd 257-12.el10 -> 257-11.el10
  systemd-container 257-12.el10 -> 257-11.el10
  systemd-libs 257-12.el10 -> 257-11.el10
  systemd-oomd 257-12.el10 -> 257-11.el10
  systemd-pam 257-12.el10 -> 257-11.el10
  systemd-resolved 257-12.el10 -> 257-11.el10
  systemd-udev 257-12.el10 -> 257-11.el10
  gnome-session 48.0-9.el10 -> 48.0-2.el10
  gnome-session-wayland-session 48.0-9.el10 -> 48.0-2.el10
  gnome-shell 48.3-6.el10 -> 48.3-2.el10
  gnome-shell-common 48.3-6.el10 -> 48.3-2.el10

  systemd 257-12.el10 -> 257-11.el10
  systemd-container 257-12.el10 -> 257-11.el10
  systemd-libs 257-12.el10 -> 257-11.el10
  systemd-oomd 257-12.el10 -> 257-11.el10
  systemd-pam 257-12.el10 -> 257-11.el10
  systemd-resolved 257-12.el10 -> 257-11.el10
  systemd-udev 257-12.el10 -> 257-11.el10
  gnome-session 48.0-9.el10 -> 48.0-2.el10
  gnome-session-wayland-session 48.0-9.el10 -> 48.0-2.el10
  gnome-shell 48.3-6.el10 -> 48.3-2.el10
  gnome-shell-common 48.3-6.el10 -> 48.3-2.el10

  systemd 257-12.el10 -> 257-11.el10
  systemd-container 257-12.el10 -> 257-11.el10
  systemd-libs 257-12.el10 -> 257-11.el10
  systemd-oomd 257-12.el10 -> 257-11.el10
  systemd-pam 257-12.el10 -> 257-11.el10
  systemd-resolved 257-12.el10 -> 257-11.el10
  systemd-udev 257-12.el10 -> 257-11.el10
  gnome-session 48.0-9.el10 -> 48.0-2.el10
  gnome-session-wayland-session 48.0-9.el10 -> 48.0-2.el10
  gnome-shell 48.3-6.el10 -> 48.3-2.el10
  gnome-shell-common 48.3-6.el10 -> 48.3-2.el10

  systemd 257-12.el10 -> 257-11.el10
  systemd-container 257-12.el10 -> 257-11.el10
  systemd-libs 257-12.el10 -> 257-11.el10
  systemd-oomd 257-12.el10 -> 257-11.el10
  systemd-pam 257-12.el10 -> 257-11.el10
  systemd-resolved 257-12.el10 -> 257-11.el10
  systemd-udev 257-12.el10 -> 257-11.el10
  gnome-session 48.0-9.el10 -> 48.0-2.el10
  gnome-session-wayland-session 48.0-9.el10 -> 48.0-2.el10
  gnome-shell 48.3-6.el10 -> 48.3-2.el10
  gnome-shell-common 48.3-6.el10 -> 48.3-2.el10

J

Jordan 🌱•8/22/25, 1:56 AM

gnome-session got downgraded? no wait I am reading it the other way around

J

Jordan 🌱•8/22/25, 1:56 AM

I guess they patch gnome-session a bunch

J

James•8/22/25, 1:56 AM

this is all a downgrade to the working image

J

Jordan 🌱•8/22/25, 1:56 AM

is this centos?

J

James•8/22/25, 1:56 AM

all the gnome revs are mine

J

Jordan 🌱•8/22/25, 1:56 AM

ah

J

James•8/22/25, 1:56 AM

I got a COPR

J

James•8/22/25, 1:57 AM

I was trying to patch this https://github.com/ublue-os/bluefin-lts/issues/625

GitHub

GNOME first run crashing on first run · Issue #625 · ublue-os/blu...

After a fresh install of the bib ISOs, gets stuck here: Hey did we bring the first run thing back with G48?

J

James•8/22/25, 1:57 AM

Adrian helped me with 2 patches for 49

J

Jordan 🌱•8/22/25, 1:59 AM

could you link me the sources of the copr

J

Jordan 🌱•8/22/25, 2:00 AM

also, you could probably build 49.beta of session and gdm, though need to check if we need shell too

J

James•8/22/25, 2:00 AM

yeah
https://src.fedoraproject.org/fork/jreilly1821/rpms/gnome-shell/tree/rawhide-el10+-no-x11

J

Jordan 🌱•8/22/25, 2:00 AM

I think we need at least 49.alpha.0 of shell

J

James•8/22/25, 2:01 AM

yeah problem is centos bundles moxzjs and gjs and fedora doesn't

J

James•8/22/25, 2:01 AM

i've been building everything out of the feora distgit but I cant build gjs due to the bundling

J

James•8/22/25, 2:02 AM

so I can't bump gjs right now

J

j0rgeOP•8/22/25, 2:02 AM

oh also jordan, we'll be doing backports on the LTS from now on, so it doesn't need to be perfect, it just needs to be reliable enough to last until 49 gets backported.

J

j0rgeOP•8/22/25, 2:02 AM

the gnome backports will be rolling it's not a "normal" LTS

J

James•8/22/25, 2:02 AM

yeah 49 will be better we just have to fake it until then

J

Jordan 🌱•8/22/25, 2:02 AM

yea I am more curious on what part of the stack makes it fail more or less

JJames i've been building everything out of the feora distgit but I cant build gjs due...

T

tulip•8/22/25, 2:03 AM

it doesnt!!!! you can just bump mozjs to 128 just fine :clueless:

J

James•8/22/25, 2:03 AM

because RH kinda force x11 off even though it wasn'

J

Jordan 🌱•8/22/25, 2:03 AM

cause I know 49.alpha nad 49.beta worked, but we never tested 48 of shell plus some patch from 49 session

Ttulip it doesnt!!!! you can just bump mozjs to 128 just fine :clueless:

J

James•8/22/25, 2:03 AM

then why was 48.4 still failing?

J

Jordan 🌱•8/22/25, 2:03 AM

actually RH didn't disable x11

J

Jordan 🌱•8/22/25, 2:03 AM

they only removed the xorg-server binary

J

Jordan 🌱•8/22/25, 2:04 AM

everything still builds against x11 libs

J

Jordan 🌱•8/22/25, 2:04 AM

(which is how we are still finding bugs)

JJames then why was 48.4 still failing?

T

tulip•8/22/25, 2:04 AM

they dont have mozjs128 on their repos yet

J

James•8/22/25, 2:04 AM

soo I should remove all my disable x11's

J

Jordan 🌱•8/22/25, 2:04 AM

yeap

J

Jordan 🌱•8/22/25, 2:04 AM

it will make things just work

Similar Threads

Similar Threads

Similar Threads