cosmic-comp: crash durring startup

[me-it-is]

Nixpkgs version

• Unstable (25.11)

Describe the bug

when login into a cosmic session it hangs with a blinking cursor

Steps to reproduce

Install cosmic and try to login

Expected behaviour

cosmic starts up normaly

Screenshots

No response

Relevant log output

Nov 23 13:28:30 <hostname> .cosmic-comp-wrapped[2515]: Unable to become drm master, assuming unprivileged mode
Nov 23 13:28:30 <hostname> .cosmic-comp-wrapped[2515]: thread 'main' panicked at 'Failed to load LibEGL: DlOpen { desc: "libEGL.so.1: cannot open >
                                                          0: log_panics::Config::install_panic_hook::{{closure}}
                                                          1: std::panicking::panic_with_hook
                                                          2: std::panicking::panic_handler::{{closure}}
                                                          3: std::sys::backtrace::__rust_end_short_backtrace
                                                          4: __rustc::rust_begin_unwind
                                                          5: core::panicking::panic_fmt
                                                          6: core::result::unwrap_failed
                                                          7: core::ops::function::FnOnce::call_once
                                                          8: std::sync::poison::once::Once::call_once_force::{{closure}}
                                                          9: std::sys::sync::once::futex::Once::call
                                                         10: smithay::backend::egl::ffi::make_sure_egl_is_loaded::{{closure}}::{{closure}}
                                                         11: smithay::backend::egl::ffi::egl::metaloadfn
                                                         12: smithay::backend::egl::ffi::egl::load_with::inner
                                                         13: std::sync::poison::once::Once::call_once::{{closure}}
                                                         14: std::sys::sync::once::futex::Once::call
                                                         15: smithay::backend::egl::ffi::make_sure_egl_is_loaded
                                                         16: smithay::backend::egl::display::EGLDisplay::new
                                                         17: cosmic_comp::backend::kms::device::init_egl
                                                         18: cosmic_comp::backend::kms::device::<impl cosmic_comp::state::State>::device_added
                                                         19: cosmic_comp::backend::kms::init_backend
                                                         20: cosmic_comp::backend::init_backend_auto
                                                         21: cosmic_comp::run
                                                         22: cosmic_comp::main
                                                         23: std::sys::backtrace::__rust_begin_short_backtrace
                                                         24: main
                                                         25: __libc_start_call_main
                                                         26: __libc_start_main_alias_1
                                                         27: _start
Nov 23 13:28:30 <hostname> .cosmic-comp-wrapped[2515]: Failed to restore previous state. Error: Invalid argument (os error 22)
Nov 23 13:28:30 <hostname> cosmic-session[2466]: process ' COSMIC_SESSION_SOCK=12 cosmic-comp ' failed with code 101
Nov 23 13:28:30 <hostname> cosmic-session[2466]: cosmic-comp exited with error code 101
Nov 23 13:28:30 <hostname> cosmic-session[2466]: draining stdin receiver before restarting process
Nov 23 13:28:30 <hostname> cosmic-session[2467]: sleeping for 3ms before restarting process cosmic-comp (restart 0)
Nov 23 13:28:30 <hostname> cosmic-session[2466]: restarted process ' COSMIC_SESSION_SOCK=12 cosmic-comp ', now at 1 restarts
Nov 23 13:28:30 <hostname> cosmic-session[2466]: process 'ProcessKey(1v1)' cancelled
Nov 23 13:28:30 <hostname> cosmic-session[2466]: cosmic-comp exited with error code 137

Additional context

No response

System metadata

fetching path input 'path:/nix/store/rqigshwjn8kaj3g472gv0jk99xw85m40-source'
these 6 paths will be fetched (0.77 MiB download, 10.25 MiB unpacked):
/nix/store/vm303svk9lm31riwv42q75zbrbwrcypk-file-5.45
/nix/store/a7nvqa7rkfqpa6vspbncal3d6flbnyj8-gnu-config-2024-01-01
/nix/store/n7qxwqwbhxhrhdym3bhprf0lvymli2iv-gnumake-4.4.1
/nix/store/ayfx0nn300ggdkvdvjnhb17fqwdzq4fi-patchelf-0.15.2
/nix/store/k5z8rkvj1fn1nrf05l5a86aflc5s1p6m-stdenv-linux
/nix/store/f8w8n1sdi14gkgwnmshgnannjfs5p976-update-autotools-gnu-config-scripts-hook
copying path '/nix/store/a7nvqa7rkfqpa6vspbncal3d6flbnyj8-gnu-config-2024-01-01' from 'https://cache.nixos.org'...
copying path '/nix/store/n7qxwqwbhxhrhdym3bhprf0lvymli2iv-gnumake-4.4.1' from 'https://cache.nixos.org'...
copying path '/nix/store/vm303svk9lm31riwv42q75zbrbwrcypk-file-5.45' from 'https://cache.nixos.org'...
copying path '/nix/store/ayfx0nn300ggdkvdvjnhb17fqwdzq4fi-patchelf-0.15.2' from 'https://cache.nixos.org'...
copying path '/nix/store/f8w8n1sdi14gkgwnmshgnannjfs5p976-update-autotools-gnu-config-scripts-hook' from 'https://cache.nixos.org'...
copying path '/nix/store/k5z8rkvj1fn1nrf05l5a86aflc5s1p6m-stdenv-linux' from 'https://cache.nixos.org'...

• system: "x86_64-linux"
• host os: Linux 6.17.8, NixOS, 25.11 (Xantusia), 25.11.20251121.2ac8b8e
• multi-user?: yes
• sandbox: yes
• version: nix-env (Lix, like Nix) 2.93.3 System type: x86_64-linux Additional system types: i686-linux, x86_64-v1-linux, x86_64-v2-linux, x86_64-v3-linux, x86_64-v4-linux Features: gc, signed-caches System configuration file: /etc/nix/nix.conf User configuration files: ~/.config/nix/nix.conf:/nix/store/f2v7r2g04j7chwyl15xz1iasfs2kx80k-stylix-kde-config/nix/nix.conf:/etc/xdg/nix/nix.conf:~/.nix-profile/etc/xdg/nix/nix.conf:/nix/profile/etc/xdg/nix/nix.conf:~/.local/state/nix/profile/etc/xdg/nix/nix.conf:/etc/profiles/per-user/<username>/etc/xdg/nix/nix.conf:/nix/var/nix/profiles/default/etc/xdg/nix/nix.conf:/run/current-system/sw/etc/xdg/nix/nix.conf Store directory: /nix/store State directory: /nix/var/nix Data directory: /nix/store/i6lm069c9din9v4ry6szspx5zrn0qzhv-lix-2.93.3/share
• channels(root): "home-manager, nixos"
• nixpkgs: /nix/store/rqigshwjn8kaj3g472gv0jk99xw85m40-source

Notify maintainers

@alyssais @nyabinary @HeitorAugustoLN @Pandapip1 @a-kenji @ahoneybun @drakon64 @michaelBelsanti @thefossguy

---

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this is a bug and not a support request.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.

[thefossguy]

Could you provide more information about your hardware? Specifically your GPU, since the crash is related to libegl.
Please also specify any NixOS configuration options that you may have "overridden" to be different than the values specified in the cosmic module.

[thefossguy]

Looked into it from my end, and it looks like an issue with libgl than cosmic-comp.

[tomwrw]

Same issue here after rebuilding this morning. cosmic-greeter hangs on boot. Works fine on by build from the 17th which was beta6. If it helps I am running a 9070xt GPU. If I drop in to a terminal and try to run cosmic-greeter from command line, I get the following:

The application panicked (crashed).
Message: Create event loop: NotSupported(NotSupportedError { reason: "neither WAYLAND_DISPLAY nor WAYLAND_SOCKET nor DISPLAY is set." })
Location: /build/cosmic-greeter-1.0.0-beta.6-vendor/iced_winit-0.14.0-dev/src/program.rs:185

[rafaelcga]

I am experiencing the same issue. Rebuilt this morning and I am login into a blinking terminal cursor instead of the GUI. Checking journalctl -b -1 | grep cosmic I got the following trace:

Nov 24 12:34:19 fractal systemd[1]: Starting cosmic-greeter-daemon.service...
Nov 24 12:34:20 fractal systemd[1]: Started cosmic-greeter-daemon.service.
Nov 24 12:34:25 fractal greetd[1465]: pam_unix(greetd:session): session opened for user cosmic-greeter(uid=991) by (uid=0)
Nov 24 12:34:25 fractal systemd-logind[932]: New session '1' of user 'cosmic-greeter' with class 'greeter' and type 'tty'.
Nov 24 12:34:25 fractal (systemd)[1469]: pam_unix(systemd-user:session): session opened for user cosmi-greeter(uid=991) by (uid=0)
Nov 24 12:34:25 fractal systemd-logind[932]: New session '2' of user 'cosmic-greeter' with class 'manager-early' and type 'unspecified'.
Nov 24 12:34:25 fractal systemd[1]: Started Session 1 of User cosmic-greeter.
Nov 24 12:34:25 fractal .cosmic-comp-wrapped[1497]: shortcuts custom config error: GetKey("custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
Nov 24 12:34:25 fractal .cosmic-comp-wrapped[1497]: Unable to become drm master, assuming unprivileged mode
Nov 24 12:34:25 fractal .cosmic-comp-wrapped[1497]: thread 'main' panicked at 'Failed to load LibEGL: DlOpen { desc: "libEGL.so.1: cannot open shared object file: No such file or directory" }': /build/cosmic-comp-1.0.0-beta.6-vendor/smithay-0.7.0/src/backend/egl/ffi.rs:148
                                                      17: cosmic_comp::backend::kms::device::init_egl
                                                      18: cosmic_comp::backend::kms::device::<impl cosmic_comp::state::State>::device_added
                                                      19: cosmic_comp::backend::kms::init_backend
                                                      20: cosmic_comp::backend::init_backend_auto
                                                      21: cosmic_comp::run
                                                      22: cosmic_comp::main
Nov 24 12:34:25 fractal .cosmic-comp-wrapped[1497]: Failed to restore previous state. Error: Invalid argument (os error 22)

EDIT: Forgot to mention, I am using an NVIDIA RTX 5070 Ti and not using mesa, if that helps.

[tomwrw]

I am experiencing the same issue. Rebuilt this morning and I am login into a blinking terminal cursor instead of the GUI. Checking journalctl -b -1 | grep cosmic I got the following trace:

Nov 24 12:34:19 fractal systemd[1]: Starting cosmic-greeter-daemon.service...
Nov 24 12:34:20 fractal systemd[1]: Started cosmic-greeter-daemon.service.
Nov 24 12:34:25 fractal greetd[1465]: pam_unix(greetd:session): session opened for user cosmic-greeter(uid=991) by (uid=0)
Nov 24 12:34:25 fractal systemd-logind[932]: New session '1' of user 'cosmic-greeter' with class 'greeter' and type 'tty'.
Nov 24 12:34:25 fractal (systemd)[1469]: pam_unix(systemd-user:session): session opened for user cosmi-greeter(uid=991) by (uid=0)
Nov 24 12:34:25 fractal systemd-logind[932]: New session '2' of user 'cosmic-greeter' with class 'manager-early' and type 'unspecified'.
Nov 24 12:34:25 fractal systemd[1]: Started Session 1 of User cosmic-greeter.
Nov 24 12:34:25 fractal .cosmic-comp-wrapped[1497]: shortcuts custom config error: GetKey("custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
Nov 24 12:34:25 fractal .cosmic-comp-wrapped[1497]: Unable to become drm master, assuming unprivileged mode
Nov 24 12:34:25 fractal .cosmic-comp-wrapped[1497]: thread 'main' panicked at 'Failed to load LibEGL: DlOpen { desc: "libEGL.so.1: cannot open shared object file: No such file or directory" }': /build/cosmic-comp-1.0.0-beta.6-vendor/smithay-0.7.0/src/backend/egl/ffi.rs:148
                                                      17: cosmic_comp::backend::kms::device::init_egl
                                                      18: cosmic_comp::backend::kms::device::<impl cosmic_comp::state::State>::device_added
                                                      19: cosmic_comp::backend::kms::init_backend
                                                      20: cosmic_comp::backend::init_backend_auto
                                                      21: cosmic_comp::run
                                                      22: cosmic_comp::main
Nov 24 12:34:25 fractal .cosmic-comp-wrapped[1497]: Failed to restore previous state. Error: Invalid argument (os error 22)

Blinking cursor is exactly what I see. Also get the same journalctl output when I run journalctl -b -1 | grep cosmic.

[Pandapip1]

Going to update my nixpkgs and see if I can replicate. Since it looks like it might be libgl-related, if you're encountering this if you could post your GPU specs that could be helpful.

Update: I can reproduce, Intel UHD Graphics 620 @ 1.10 GHz. greetd.service complains that no client is connecting, but cosmic-greeter-daemon.service claims to be running. Will continue to investigate later.

[busyboredom]

I'm having this issue on an AMD Radeon 860M (the integrated GPU in my Ryzen AI 7 350)

[V0idLord]

I have the same issue on my laptop after updating today, using AMD integrated graphics, Radeon 780M.

[PaulGrandperrin]

Same issue with integrated Intel HD Graphics 630 + Nvidia GeForce 1050 (proprietary driver)

[Pandapip1]

It sure looks like this coincided with a staging-next -> master merge. There are a lot of apparmor updates, I wonder if one of them broke something: https://github.com/NixOS/nixpkgs/pull/461523/files. I'll build f04cb2c and see if it's present there.

[me-it-is]

I'm using a 3080 with proprietary drivers and open source kernel modules. services.upower.enable is forced to false, and enviroment.cosmic.excludedPackages is set to an empty array.

[ahoneybun]

Does anyone have a Intel CPU and integrated Intel Graphics?

[BerriJ]

Does anyone have a Intel CPU and integrated Intel Graphics?

I can confirm that this also affects Intel Integrated graphics :(

CPU: 12th Gen Intel i5-12600K (16) @ 4.900GHz
GPU: Intel AlderLake-S GT1

[thefossguy]

So far, I can confirm that this affects almost everyone. And as @Pandapip1 mentioned, this is likely with the staging branch that got merged which has the offending change. But, since it is "staging" bisecting it is more time consuming due to having to compile everything. Sorry about the delay everyone.