Dmesg - QDBusConnection # segfault

system: "x86_64-linux"
host os: Linux 6.1.31, NixOS, 23.05 (Stoat), 23.05.419.3a70dd92993
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.13.3
channels(root): "nixgl, nixos-23.05, nixos-hardware"
channels(usera): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

[ 24.436673] QDBusConnection[2697]: segfault at 7f91b1c8da68 ip 00007f91be8fa76d sp 00007f91b8ca9a00 error 4 in[7f91be697000+316000] likely on CPU 11 (core 20, socket 0)

What does it mean and how to solve it?

How does this differ from your other topic 22.11 issues # QDBusConnection segfault?

Also if you ask for help, you are expected to do some of the work yourself, and mention what you did. Otherwise, you run the risk of being considered a help vampire, and invite moderate application of garlic.

For segfaults, the minimum information necessary are:

  • When does the crash happen? In response to which user action?
  • Stack trace including debug symbols. After obtaining the symbols, run coredumpctl to find the process id of the crashed process and then coredumpctl gdb <pid> in which you enter bt command.

it is other soft and hardware

  • on this system and before the upgrade, it looked fine (and with the upgrade I got issues e.g. window flickering … )

I have not idea what this could mean and cannot find information about it in researching the issue … (if that is a vampire?)

Thanks for the information, wouldn’t associate “Debug Symbols” with segfaults (like the word itself is not existing in the page content)

Well, from all the context you provided, it looks the same to me. So unless you have some reason to think it is a different issue that you have not shared, I would assume it is the same issue.

General procedure for debugging crashes is getting a stack trace to find out what part of a program is responsible. That is not really specific to NixOS (see e.g. Arch Linux or Fedora) and we can help guide you through the process if you need more details.