Change:
patchShebangs src/data-to-c.pl ''; <ins> preFixup = '' # https://github.com/NixOS/nixpkgs/issues/101881 gappsWrapperArgs+=( --prefix XDG_DATA_DIRS : "${gnome.caribou}/share" ) # https://github.com/NixOS/nixpkgs/issues/129946 buildPythonPath "${python3.pkgs.xapp}" patchPythonScript $out/share/cinnamon/cinnamon-desktop-editor/cinnamon-desktop-editor.py ''; </ins> passthru = { providedSessions = [ "cinnamon" "cinnamon2d" ]; };

Discussion:
Describe the bug The cinnamon-menu-editor doesn't open the cinnamon-desktop-editor, if I want to change the 'Properties' of a menu Entry. To Reproduce https://user- Expected behavior https://user- Additional context Here is the cinnamon-desktop-editor source: Notify maintainers thanks for making cinnamon available in NixOS! :) Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(linux): nixpkgs: Maintainer information:
Open the menu editor through the terminal and edit the properties then send the output
I open cinnamon-menu-editor in Terminal, select an entry, click "Properties": This is in the launcher- :
I marked this as stale due to inactivity. &rarr;
This patch fixes the issue, if nobody wish to investigate on this issue I will go ahead and commit this change on next cinnamon update. Edit: Ah I probably don't need to set dontWrapPythonPrograms Edit 2: Non English user can still encounter some l10n issues like translated strings are not modified, we will track the issue in

Describe the bug When cinnamon is started either via gdm or in a . Sometimes the desktop icons do load Always a window spawns telling me that I'm in fallback mode no taskbar, no window decorations (hence I think no compositor & window manager) To Reproduce Here I'm kind of unsure: I deleted all nemo and cinnamon folder in $HOME, .config and .local/share. Still this occurs on all of my machines. IIRC this first happen when accidentally starting a "virtual keyboard" app cinnamon "Virtual keyboard" cinnamon components crash instantly, the and the behavior is reproducible on further attempts of starting cinnamon Expected behavior Cinnamon starts and is usable Additional context Booting into an old generation did not fix this, however, I'm quite unsure what could be the cause of it. This is some log which I could create by running cinnamon from a . I'm not sure whether this is related to the issue or not. relevant : Output captured (the log is over 2000 lines long, this is from the very end and might be the issue): Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs: Maintainer information:
I will say that it does start in lightdm. IIRC upstream uses slick greeter and lightdm, so maybe it's just broken for that dm.
it is broken when started on as well, and it used to work in gdm just a day a go as well. Thinking more of the problem, what else can break the startup of cinnamon if all of these are empty/removed: + + + ? There must be something in my $HOME which alters the startup procedure of cinnamon to break (otherwise it wouldn't work for you?!) but what can it be? Edit: I now gathered a more meaningful error: Edit 2: Found the remaining part thing: dconf. After renaming , cinnamon starts just fine. Holy moly. Running "Virtual keyboard" from the cinnamon menu breaks it immediately, though.
Which package provides gio for ? We'd need to add that to buildInputs then the error should be fixed
That is . Be sure to on the source code to always run a to see what namespaces are imported.

From there you track where those typelibs come from to determine the dependencies that belong in
Any updates on this?
It would need to be tested if the issue still persists.
The bug is still persistent. system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs:
The bug is still present in 21.05: system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs:
The main problem I have is that I have no idea where to even start debugging the segfault, as it seems to be part of native code
Any chances upstream has some idea? Not sure how to get in touch with them without making it seem like "We have a problem and you shall fix it".
I ran and I found that it is missing , just install it and the bug will disappear. I think this package is a must or we have a security-issue here
I can confirm installing caribou fixes the issue. I haven't really looked into it yet, the related line is likely at And I managed to SIGSEGV gjs-console (cjs-console) in a shell with: I search for the output , and found this So I do and the SIGSEGV is gone. So I guess caribou is needed for this case.