You are not logged in.

Pages: 1

#1 2025-06-29 16:44:52

Everything2067
Member
Registered: 2025-06-29
Posts: 7

[SOLVED] GNOME Wayland not logging in.

I have GNOME shell installed. Today, I tried out xfce just for fun. I installed it using pacman and started it. I made sure to stop the gdm service.

sudo systemctl stop gdm
sudo pacman -S xfce4 xfce4-goodies xfwm
startxfce4

I did not add it to xinitrc (as given by the wiki) because I just wanted to test it. After that, I uninstalled the above packages and rebooted. Now, when I log in with my main user by selecting "GNOME", it firsts shows the console for a short time then goes back to the login screen. However, I can log into my account by selecting the GNOME on Xorg option before logging in. Strangely, I can log into other users in Wayland just fine without any problem.

By running

journalctl -b

I copied over the logs (not all, just the ones that I thought may be useful). I've redacted my username and hostname for my own privacy.
https://pastebin.com/Kczi8LeX

What I've tried:

  • Resetting GDM configuration with

    sudo gdm-config reset

    It just gives me an error

    (gdm-config:81583): Gdm-CRITICAL **: 21:57:09.552: Failed to run “reset” command: /usr/lib/gdm-auth-config-arch is not an executable

  • Reinstalling GNOME and GDM. No change.

  • Disabling extensions. Still no change.

  • Exploring the forum and other sites and trying out other solutions.

I'll appreciate your response, whether it works or not. I am mostly busy throughout the day, so it'll take me some time to respond. Thanks.

Last edited by Everything2067 (2025-06-30 11:48:58)

Offline

#2 2025-06-29 21:49:44

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,712

Re: [SOLVED] GNOME Wayland not logging in.

Jun 29 21:28:39 desktop-[redacted] gnome-shell[1171]: Using public X11 display :0, (using :1 for managed services)
Jun 29 21:28:39 desktop-[redacted] gnome-shell[1171]: Using Wayland display name 'wayland-0'
Jun 29 21:28:40 desktop-[redacted] gnome-shell[1171]: cogl_texture_2d_new_with_format: assertion 'width >= 1' failed
Jun 29 21:28:40 desktop-[redacted] kernel: gnome-shell[1171]: segfault at ffffffffffffffc0 ip 00007feb8ad6517a sp 00007fff3d84dc70 error 5 in libmutter-cogl-16.so.0.0.0[8417a,7feb8acef000+a4000] likely on CPU 5 (core 1, socket 0)
Jun 29 21:28:40 desktop-[redacted] kernel: Code: f3 0f 1e fa 55 48 89 e5 41 55 41 54 49 89 fc 53 48 83 ec 18 48 63 05 fd 32 05 00 64 48 8b 1c 25 28 00 00 00 48 89 5d d8 89 f3 <4c> 8b 2c 07 48 8b 05 23 34 05 00 48 85 c0 0f 84 e2 00 00 00 4d 85
Jun 29 21:28:40 desktop-[redacted] systemd-coredump[1228]: Process 1171 (gnome-shell) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Jun 29 21:28:40 desktop-[redacted] systemd[1]: Created slice Slice /system/systemd-coredump.
Jun 29 21:28:40 desktop-[redacted] systemd[1]: Started Process Core Dump (PID 1228/UID 0).
Jun 29 21:28:40 desktop-[redacted] systemd-coredump[1229]: Process 1171 (gnome-shell) of user 1000 dumped core.
                                                        
                                                        Stack trace of thread 1171:
                                                        #0  0x00007feb8ad6517a n/a (libmutter-cogl-16.so.0 + 0x8417a)
                                                        #1  0x00007feb8b3d8a20 n/a (libmutter-16.so.0 + 0x1d8a20)
                                                        #2  0x00007feb8b3d9810 n/a (libmutter-16.so.0 + 0x1d9810)
                                                        #3  0x00007feb8b27eebf n/a (libmutter-16.so.0 + 0x7eebf)
                                                        #4  0x00007feb8b28bfe7 n/a (libmutter-16.so.0 + 0x8bfe7)
                                                        #5  0x00007feb8b26eaaf n/a (libmutter-16.so.0 + 0x6eaaf)
                                                        #6  0x00007feb8bf6e83a g_closure_invoke (libgobject-2.0.so.0 + 0x1183a)
                                                        #7  0x00007feb8bf8d42b n/a (libgobject-2.0.so.0 + 0x3042b)
                                                        #8  0x00007feb8bf8f48f n/a (libgobject-2.0.so.0 + 0x3248f)
                                                        #9  0x00007feb8bf8f709 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32709)
                                                        #10 0x00007feb8bf8f7c4 g_signal_emit (libgobject-2.0.so.0 + 0x327c4)
                                                        #11 0x00007feb8b2e0052 meta_context_start (libmutter-16.so.0 + 0xe0052)
                                                        #12 0x0000559185e5f535 n/a (/usr/bin/gnome-shell + 0x2535)
                                                        #13 0x00007feb8b0376b5 n/a (libc.so.6 + 0x276b5)
                                                        #14 0x00007feb8b037769 __libc_start_main (libc.so.6 + 0x27769)
                                                        #15 0x0000559185e5f9d5 n/a (/usr/bin/gnome-shell + 0x29d5)

smells like a bogus monitor configuration (because of the 0x0-texture)
https://wiki.archlinux.org/title/GDM#Se … r_settings - GDM still starts? So it's probably only the bogus ~/.config/monitor.xml?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#3 2025-06-30 05:31:04

Everything2067
Member
Registered: 2025-06-29
Posts: 7

Re: [SOLVED] GNOME Wayland not logging in.

seth wrote:
Jun 29 21:28:39 desktop-[redacted] gnome-shell[1171]: Using public X11 display :0, (using :1 for managed services)
Jun 29 21:28:39 desktop-[redacted] gnome-shell[1171]: Using Wayland display name 'wayland-0'
Jun 29 21:28:40 desktop-[redacted] gnome-shell[1171]: cogl_texture_2d_new_with_format: assertion 'width >= 1' failed
Jun 29 21:28:40 desktop-[redacted] kernel: gnome-shell[1171]: segfault at ffffffffffffffc0 ip 00007feb8ad6517a sp 00007fff3d84dc70 error 5 in libmutter-cogl-16.so.0.0.0[8417a,7feb8acef000+a4000] likely on CPU 5 (core 1, socket 0)
Jun 29 21:28:40 desktop-[redacted] kernel: Code: f3 0f 1e fa 55 48 89 e5 41 55 41 54 49 89 fc 53 48 83 ec 18 48 63 05 fd 32 05 00 64 48 8b 1c 25 28 00 00 00 48 89 5d d8 89 f3 <4c> 8b 2c 07 48 8b 05 23 34 05 00 48 85 c0 0f 84 e2 00 00 00 4d 85
Jun 29 21:28:40 desktop-[redacted] systemd-coredump[1228]: Process 1171 (gnome-shell) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Jun 29 21:28:40 desktop-[redacted] systemd[1]: Created slice Slice /system/systemd-coredump.
Jun 29 21:28:40 desktop-[redacted] systemd[1]: Started Process Core Dump (PID 1228/UID 0).
Jun 29 21:28:40 desktop-[redacted] systemd-coredump[1229]: Process 1171 (gnome-shell) of user 1000 dumped core.
                                                        
                                                        Stack trace of thread 1171:
                                                        #0  0x00007feb8ad6517a n/a (libmutter-cogl-16.so.0 + 0x8417a)
                                                        #1  0x00007feb8b3d8a20 n/a (libmutter-16.so.0 + 0x1d8a20)
                                                        #2  0x00007feb8b3d9810 n/a (libmutter-16.so.0 + 0x1d9810)
                                                        #3  0x00007feb8b27eebf n/a (libmutter-16.so.0 + 0x7eebf)
                                                        #4  0x00007feb8b28bfe7 n/a (libmutter-16.so.0 + 0x8bfe7)
                                                        #5  0x00007feb8b26eaaf n/a (libmutter-16.so.0 + 0x6eaaf)
                                                        #6  0x00007feb8bf6e83a g_closure_invoke (libgobject-2.0.so.0 + 0x1183a)
                                                        #7  0x00007feb8bf8d42b n/a (libgobject-2.0.so.0 + 0x3042b)
                                                        #8  0x00007feb8bf8f48f n/a (libgobject-2.0.so.0 + 0x3248f)
                                                        #9  0x00007feb8bf8f709 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32709)
                                                        #10 0x00007feb8bf8f7c4 g_signal_emit (libgobject-2.0.so.0 + 0x327c4)
                                                        #11 0x00007feb8b2e0052 meta_context_start (libmutter-16.so.0 + 0xe0052)
                                                        #12 0x0000559185e5f535 n/a (/usr/bin/gnome-shell + 0x2535)
                                                        #13 0x00007feb8b0376b5 n/a (libc.so.6 + 0x276b5)
                                                        #14 0x00007feb8b037769 __libc_start_main (libc.so.6 + 0x27769)
                                                        #15 0x0000559185e5f9d5 n/a (/usr/bin/gnome-shell + 0x29d5)

smells like a bogus monitor configuration (because of the 0x0-texture)
https://wiki.archlinux.org/title/GDM#Se … r_settings - GDM still starts? So it's probably only the bogus ~/.config/monitor.xml?

Hi, thanks for the reply. My monitors.xml file looks like this:

<monitors version="2">
  <configuration>
    <layoutmode>physical</layoutmode>
    <logicalmonitor>
      <x>0</x>
      <y>0</y>
      <scale>1</scale>
      <primary>yes</primary>
      <monitor>
        <monitorspec>
          <connector>eDP-1</connector>
          <vendor>HPN</vendor>
          <product>HP ALL-in-One</product>
          <serial>[redacted]</serial>
        </monitorspec>
        <mode>
          <width>1920</width>
          <height>1080</height>
          <rate>60.000</rate>
        </mode>
      </monitor>
    </logicalmonitor>
  </configuration>
</monitors>

Strangely, there was no monitors.xml file in /var/lib/gdm/.config, so I copied the same monitors.xml there. Rebooted and the issue still persists.
Next, I edited the logical monitor x and y values. I edited it to 1920 and 1080 (I just realized that those were not width and height) and no, the issue still persists.
I then logged in the other user (which was also in the wheel group) to see if it has a monitors.xml file. It did not.
Last thing I tried was renaming the monitors.xml file in the home directory and in /var/lib/gdm/.config to monitors.xml.old, hoping that a working file would regenerate. It did not work.
All the methods I tried outputted the same errors in journalctl. I'm still accepting answers. Thank you again for the reply smile

Last edited by Everything2067 (2025-06-30 05:31:41)

Offline

#4 2025-06-30 06:23:47

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,712

Re: [SOLVED] GNOME Wayland not logging in.

Last thing I tried was renaming the monitors.xml file in the home directory and in /var/lib/gdm/.config to monitors.xml.old, hoping that a working file would regenerate.

That was the idea (mostly about your  It did not work.
Unfortunately

It did not work.

You still get 

cogl_texture_2d_new_with_format: assertion 'width >= 1' failed

?

So

not all, just the ones that I thought may be useful

let's look at the irrelevant parts.
Please post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

(This will directly upload the journal of the boot to 0x0.st, you can sed-replace user and hostname, but it's not really sensitive data. Just maybe embarrassing tongue)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#5 2025-06-30 07:12:12

Everything2067
Member
Registered: 2025-06-29
Posts: 7

Re: [SOLVED] GNOME Wayland not logging in.

seth wrote:

Please post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

(This will directly upload the journal of the boot to 0x0.st, you can sed-replace user and hostname, but it's not really sensitive data. Just maybe embarrassing tongue)

Here is the link: https://0x0.st/8UtM.txt
You are right about the sensitive data though lol. I was just frustrated last night.

Offline

#6 2025-06-30 07:44:09

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,712

Re: [SOLVED] GNOME Wayland not logging in.

Jun 30 10:31:16 desktop-84886qa /usr/lib/gdm-x-session[2409]: (EE) AIGLX error: dlopen of /usr/lib/dri/i965_dri.so failed (/usr/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory)
Jun 30 10:31:16 desktop-84886qa /usr/lib/gdm-x-session[2409]: (EE) AIGLX error: unable to load driver i965
Jun 30 10:31:17 desktop-84886qa /usr/lib/gdm-x-session[2409]: (II) IGLX: Loaded and initialized swrast

Remove every xf86-video-* package.
X11 aside,

Jun 30 10:43:10 desktop-84886qa systemd[1]: Started Session 11 of User test-user.
Jun 30 10:43:11 desktop-84886qa systemd[13446]: Reached target GNOME Wayland Session.
Jun 30 10:43:11 desktop-84886qa systemd[13446]: Reached target Session services which should run early before the graphical session is brought up.
Jun 30 10:43:11 desktop-84886qa systemd[13446]: Reached target GNOME Shell.

test-user and GDM run on wayland, only your main users session fails on 

Jun 30 10:26:02 desktop-84886qa gnome-shell[1187]: cogl_texture_2d_new_with_format: assertion 'width >= 1' failed
Jun 30 10:26:02 desktop-84886qa kernel: gnome-shell[1187]: segfault at ffffffffffffffc0 ip 00007fc15198317a sp 00007fffd8c89c10 error 5 in libmutter-cogl-16.so.0.0.0[8417a,7fc15190d000+a4000] likely on CPU 1 (core 1, socket 0)
Jun 30 10:26:02 desktop-84886qa kernel: Code: f3 0f 1e fa 55 48 89 e5 41 55 41 54 49 89 fc 53 48 83 ec 18 48 63 05 fd 32 05 00 64 48 8b 1c 25 28 00 00 00 48 89 5d d8 89 f3 <4c> 8b 2c 07 48 8b 05 23 34 05 00 48 85 c0 0f 84 e2 00 00 00 4d 85
Jun 30 10:26:02 desktop-84886qa systemd-coredump[1246]: Process 1187 (gnome-shell) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Jun 30 10:26:02 desktop-84886qa systemd[1]: Created slice Slice /system/systemd-coredump.
Jun 30 10:26:02 desktop-84886qa systemd[1]: Started Process Core Dump (PID 1246/UID 0).
Jun 30 10:26:03 desktop-84886qa systemd-coredump[1247]: Process 1187 (gnome-shell) of user 1000 dumped core.
                                                        
                                                        Stack trace of thread 1187:
                                                        #0  0x00007fc15198317a n/a (libmutter-cogl-16.so.0 + 0x8417a)
                                                        #1  0x00007fc151fd8aa0 n/a (libmutter-16.so.0 + 0x1d8aa0)
                                                        #2  0x00007fc151fd9890 n/a (libmutter-16.so.0 + 0x1d9890)
                                                        #3  0x00007fc151e7eedf n/a (libmutter-16.so.0 + 0x7eedf)
                                                        #4  0x00007fc151e8c007 n/a (libmutter-16.so.0 + 0x8c007)
                                                        #5  0x00007fc151e6eacf n/a (libmutter-16.so.0 + 0x6eacf)
                                                        #6  0x00007fc152ba683a g_closure_invoke (libgobject-2.0.so.0 + 0x1183a)
                                                        #7  0x00007fc152bc542b n/a (libgobject-2.0.so.0 + 0x3042b)
                                                        #8  0x00007fc152bc748f n/a (libgobject-2.0.so.0 + 0x3248f)
                                                        #9  0x00007fc152bc7709 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32709)
                                                        #10 0x00007fc152bc77c4 g_signal_emit (libgobject-2.0.so.0 + 0x327c4)
                                                        #11 0x00007fc151ee00d2 meta_context_start (libmutter-16.so.0 + 0xe00d2)
                                                        #12 0x0000557327dfc535 n/a (/usr/bin/gnome-shell + 0x2535)
                                                        #13 0x00007fc151c376b5 n/a (libc.so.6 + 0x276b5)
                                                        #14 0x00007fc151c37769 __libc_start_main (libc.so.6 + 0x27769)
                                                        #15 0x0000557327dfc9d5 n/a (/usr/bin/gnome-shell + 0x29d5)

See https://wiki.archlinux.org/title/Debuginfod for a better backtrace that will hopefully reveal what kind of texture ends up being 0x0, triggering this segfault.
You can use one of the older coredumps, https://wiki.archlinux.org/title/Core_d … _core_dump

There's however a good chance that it's the cursor theme/size
https://www.mail-archive.com/debian-bug … 38806.html

I tracked it down to /org/gnome/desktop/interface/cursor-size dconf
value somehow being set to zero (possibly by XFCE), and this triggering
an assertion in libmutter:

https://wiki.archlinux.org/title/Cursor_themes#GNOME - what would be an epic self-own of this clownish "we only care about core gnome applications" DE…

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#7 2025-06-30 11:37:03

Everything2067
Member
Registered: 2025-06-29
Posts: 7

Re: [SOLVED] GNOME Wayland not logging in.

seth wrote:

There's however a good chance that it's the cursor theme/size
https://www.mail-archive.com/debian-bug … 38806.html

I tracked it down to /org/gnome/desktop/interface/cursor-size dconf
value somehow being set to zero (possibly by XFCE), and this triggering
an assertion in libmutter:

https://wiki.archlinux.org/title/Cursor_themes#GNOME - what would be an epic self-own of this clownish "we only care about core gnome applications" DE…

I set the cursor size dconf to default (in dconf editor) and wayland is working again. Thank you so much smile smile.

Last edited by Everything2067 (2025-06-30 11:48:35)

Offline

Pages: 1

Board footer

Powered by FluxBB