Cinnamon refuses to start an xorg session with xorg-server 21.1.25

Did my weekly yay -Syu today, rebooted, and found that Cinnamon refused to start.

(Of course I’m probably one of maybe a dozen EOS users using Cinnamon.)

Oddly, the Cinnamon Wayland session did start, but Cinnamon Wayland is still pretty janky.

After digging through my pacman logs, I saw that xorg had updated… likely in response to recent security issues. I downgraded xorg-server and xorg-server-common to 21.1.24, which is a few months old at this point, and that fixed my issue.

I’m posting in the hopes that this a) may help other Cinnamon users and b) may help to shine light on an unfixed bug.

Your downgrade lines up with what others are running into. Since the 21.1.25 update there are startup-crash reports from several directions: an Arch forum thread with multiple users whose Xorg dumps core at startup, and Cinnamon crash reports surfacing on the Manjaro and CachyOS forums as well - so this is not Cinnamon-specific, and not just you.

The Arch packaging tracker has an entry for it: 21.1.25-1 segfaults on start when VariableRefresh and TearFree are enabled (amdgpu driver options). Two documented workarounds from that discussion: downgrade xorg-server and xorg-server-common to 21.1.24 - exactly what you did - or switch off VariableRefresh and TearFree in the Xorg config if you have those options set. The tracker entry is currently marked closed, but the Arch package is still 21.1.25 from October 7, so I cannot tell from the outside whether a fixed build is already on its way.

One thought on your case: if you do not use VariableRefresh or TearFree at all, your crash would be a second variant beyond the one in the tracker entry - then the downgrade is the known workaround until a fixed package lands. I have no Cinnamon install here, so this is from the bug reports rather than first-hand.

Maybe some AMD problem. I’m running EOS w/ Cinnamon without any issues. Lenovo T14 Gen 1, X.Org 21.1.25, Intel CometLake-U GT2 [UHD Graphics] (i915).

Do you use VariableRefresh or / and TearFree with you Intel-GPU?

I don’t even think that’s possible, guess it’s possibly an AMD option?

No, AdaptiveSync or VRR could be used by AMD, Intel and nVidia.
Maybe you didn’t activate VariableRefresh or / and TearFree (?).

.

https://community.intel.com/t/adaptive-vsync/121840/

Thank you for posting in our Intel communities.

VESA Adaptive Sync is one of several different standards to achieve Variable Refresh Rate (VRR). Intel Arc A-Series GPUs are compatible with VESA Adaptive Sync.

In a nutshell VRR adjust its refresh rate based on the frame rate of the video source, including game content, to eliminate the stuttering or tearing of the image and enable smooth display of the source.

In Intel Arc Control you can also set different options for frame-delivery technologies. Check this link for more information.

As for your question on disabling ‘AdaptiveVsyncEnable’ in Regedit - as policy we do not support modifying the Windows Registry as this can lead to system instability or catastrophic results.

You can enable or disable VRR using Intel Arc Control and also via Windows → Settings → System → Display → Graphics.

Best Regards,

Von M.

Intel Customer Support Technician

Type into console/terminal:
xrandr --props and have a look at vrr_capable: 1

Sorry, my laptop doesn’t even show vrr_capable with xrandr. Just a plain old IPS FHD.

Guess this is geared toward the gaming community. I’m not gaming.

VRR capability of GPU has nothing to do with display VRR capability.
If your GPU or Monitor/TV does’n support it, you should noch run into the same problems.

The Problem could/should be by X.Org X Server 1.21.1.25.

That may be so. I’m satisfied that my system runs and I can do my work. That’s all, folks.

You have an older graphics card type. So just relax. :blush:

I use a.t.m. the modeset-driver.

I’m actually totally relaxed. EOS being the only Arch-based distro that allowed me to do my work each and every day without much tinkering or breakages. It just rocks on, every bloody day—real neat!

But since I use Cinnamon and X.11, I keep an eye on threads saying something is broken.

Just in case it helps, here is my inxi -Ga:

Graphics:
  Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: Lenovo driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:9b41 class-ID: 0300
  Device-2: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:101 chip-ID: 04f2:b6d0
    class-ID: fe01 serial: 0001
  Display: x11 server: X.Org v: 21.1.25 with: Xwayland v: 24.1.14 driver: X:
    loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: BOE Display 0x07db built: 2018 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 158 gamma: 1.2
    size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9
    modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
    inactive: wayland
  API: OpenGL v: 4.6 vendor: intel mesa v: 26.2.4-arch1.1 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
    device-ID: 8086:9b41 memory: 14.92 GiB unified: yes
  API: Vulkan v: 1.4.363 layers: 2 device: 0 type: integrated-gpu name: Intel
    UHD Graphics (CML GT2) driver: mesa intel v: 26.2.4-arch1.1
    device-ID: 8086:9b41 surfaces: N/A
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo
    x11: xdpyinfo, xprop, xrandr

You use the older Intel driver i915, so your system is not in danger to this problem.

If you want trouble, use the newer Intel driver iris (Iris Xe Graphics) and enable the
Option "TearFree" "true"

… or just try modesetting for a different view. Backup could be usefull.