Arch Linux

pajamaman18

Member

Registered: 2023-09-07

Posts: 7

Sway not starting after system update

After a recent update (system, not sway) sway just does not start anymore, I run sway and it just hangs.
I can still shut down by pressing my power button (it is bound to shutdown) and it seems to properly shut down though.

I reverted these updates and sway seems to work again, I don't have the time to figure out what exactly caused the issue though.

[2025-05-22T16:27:13+0200] [ALPM] downgraded glib2 (2.84.2-1 -> 2.84.1-1)
[2025-05-22T16:27:13+0200] [ALPM] downgraded libplacebo (7.351.0-1 -> 7.349.0-7)
[2025-05-22T16:27:13+0200] [ALPM] downgraded mesa (1:25.1.1-1 -> 1:25.0.5-1)
[2025-05-22T16:27:13+0200] [ALPM] downgraded hidapi (0.15.0-1 -> 0.14.0-3)
[2025-05-22T16:27:13+0200] [ALPM] downgraded ffmpeg (2:7.1.1-3 -> 2:7.1.1-2)
[2025-05-22T16:27:13+0200] [ALPM] downgraded mpv (1:0.40.0-3 -> 1:0.40.0-2)

I am guessing that ffmpeg and mpv are not the cause, will have to look into it in the evening

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,076

Re: Sway not starting after system update

much more likely mesa, unless you're running some video wallpaper or so, but both of those are just minor rebuilds against libplacebo and mesa is a  new major version.

Do you get a crash with a backtrace or so? https://wiki.archlinux.org/title/Core_d … _core_dump and maybe a full

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

... Also how long did you wait and are you starting a bunch of GUI applications? Might also be caches getting rebuilt which can take a while on new mesa bumps. Which GPU(s)?

eglinfo -B
glxinfo -B

?

pajamaman18

Member

Registered: 2023-09-07

Posts: 7

Re: Sway not starting after system update

As you suspected, it was indeed upgrading mesa from 25.0.5-1 -> 25.1.1-1.

I retried with just waiting for a while (~3 min), but still didn't get any output

Shortened output of eglinfo -B:

Wayland platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) UHD Graphics 620 (WHL GT2)
OpenGL core profile version: 4.6 (Core Profile) Mesa 25.0.5-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) UHD Graphics 620 (WHL GT2)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 25.0.5-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) UHD Graphics 620 (WHL GT2)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 25.0.5-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

glxinfo -B:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) UHD Graphics 620 (WHL GT2) (0x3ea0)
    Version: 25.0.5
    Accelerated: yes
    Video memory: 9874MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (WHL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.0.5-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.0.5-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.0.5-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

I didn't get any crash, nor does it look like I got any error messages in my journal.
Running sway with -d(ebug) gives (typed from photo):

...
starting sway version 1.10.1
could not connect to socket /run/seatd.sock: no such file or directory
backend 'seatd' failed to open seat, skipping

However this is exactly the same as with mesa downgraded, so I don't know what is going on

My journal output is http://0x0.st/8wkq.txt
I am trying to start some gui applications:

exec /usr/bin/thunderbird
exec /usr/bin/obsidian
exec gammastep
exec /usr/bin/safeeyes
exec /usr/bin/zotero

Commenting them out doesn't change anything though, still a complete lock up when starting sway

Lorec

Member

Registered: 2023-09-28

Posts: 12

Re: Sway not starting after system update

Thank you, the mesa update was apparently what was causing startx to hang for me as well.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 73,737

Re: Sway not starting after system update

https://bbs.archlinux.org/viewtopic.php?id=305727
Some posts there revolve around vmware, ignore those

You also have an nvidia chip, running on nouveau. So try to disable the simpledrm device.

---

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

pajamaman18

Member

Registered: 2023-09-07

Posts: 7

Re: Sway not starting after system update

Blacklisting nouveau made my external display stop functioning, so I don't think thats going to be an option for me.
I basically copied the settings described here https://wiki.archlinux.org/title/Hybrid … udev_rules
I also did mkinitcpio -p linux afterwards.

Adding "nvidia_drm.modeset=1" to my kernel parameters as mentioned in the thread you linked didn't fix it either.

Don't really have the time to fix this issue when a downgrade makes stuff work atm.
Thanks for the help in any case