Comments (22)
oh, that's what you mean by messed?, let me see what happen if i change the sddm theme
from nix-installer.
hmmm, i can't print it, but i reverted my sddm going to /etc/sddm.conf.d/kde_settings.conf and writing this
[Users] MaximumUid=1000 MinimumUid=1000
because my user is uid=1000, so it only show my user, look at /etc/passwd to be sure what's your uidDo you mean after using the installer?
yep, apparently sddm become that way because the nix-installer create various nix-users, and sddm becomes confused, but i'm not sure, for me it worked
from nix-installer.
hmmm, i can't print it, but i reverted my sddm going to /etc/sddm.conf.d/kde_settings.conf and writing this
[Users] MaximumUid=1000 MinimumUid=1000
because my user is uid=1000, so it only show my user, look at /etc/passwd to be sure what's your uidDo you mean after using the installer?
yep, apparently sddm become that way because the nix-installer create various nix-users, and sddm becomes confused, but i'm not sure, for me it worked
/etc/sddm.conf.d/kde_settings.conf
[Users]
MinimumUid=1000
MaximumUid=1001
Note: both the test users I created are now correctly handled by SDDM
Purrrfect, I confirm this is the solution. I believe it's an SDDM issue. I will reach out to the SDDM team and let them know about this.
Thanks for taking the time to help me troubleshoot this issue, @Viliansh 🚀
If everyone agrees, we can close this issue.
from nix-installer.
urg, ok the installer worked on a VM, look like the problem is with me, what i can do to debug this?
from nix-installer.
Looks like upstream has a similar issue reported: NixOS/nix#10247. Although it is about /var
not /home
, this may be related.
from nix-installer.
Looks like upstream has a similar issue reported: NixOS/nix#10247. Although it is about
/var
not/home
, this may be related.
the problem is that, i installed nix in a vm(running fedora atomic) and it worked fine, but i tried in bare metal(also using fedora atomic) and it give me this error
from nix-installer.
how do i update to the master branch?
from nix-installer.
This was closed in error -- the fix hasn't yet made it to a released version of Nix yet.
from nix-installer.
This was closed in error -- the fix hasn't yet made it to a released version of Nix yet.
oh, ok thank you!
from nix-installer.
Hi all 👋
@cole-h Once the new version with the symlink fix is released, what will be the proper way to update a Single-user
installation, given nix-env
bails out with the symlink error message?
from nix-installer.
btw installed nix-2.21.2 and everything seen to be working fine, thank you all!, want me to close it now, or wait until the installer get updated?
from nix-installer.
On my side after updating to nix-2.21.2
via sh <(curl -L https://releases.nixos.org/nix/nix-2.21.2/install) --no-daemon
:
$ nix-env -iA nix
error: attribute 'nix' in selection path 'nix' not found
This is a Single-user
installation.
from nix-installer.
i ran this curl --proto '=https' --tlsv1.2 -sSf -L https://install.determinate.systems/nix | sh -s -- install --nix-package-url https://releases.nixos.org/nix/nix-2.21.2/nix-2.21.2-x86_64-linux.tar.xz
and worked
from nix-installer.
i ran this
curl --proto '=https' --tlsv1.2 -sSf -L https://install.determinate.systems/nix | sh -s -- install --nix-package-url https://releases.nixos.org/nix/nix-2.21.2/nix-2.21.2-x86_64-linux.tar.xz
and worked
Oh yes, the Determinate installer! Sadly, the SELinux policy they ship breaks /var
on all the Fedora Atomic Desktop (the "immutable" flavors), so I had to uninstall it a few months ago :(
In my case, I'm using an alternate method to install Nix as Single-user
, which works great. The only issue is the symlink issue you mentioned in your OP up to 2.21.1
.
Edit: typo
from nix-installer.
i ran this
curl --proto '=https' --tlsv1.2 -sSf -L https://install.determinate.systems/nix | sh -s -- install --nix-package-url https://releases.nixos.org/nix/nix-2.21.2/nix-2.21.2-x86_64-linux.tar.xz
and workedOh yes, the Determinate installer! Sadly, the SELinux policy they ship breaks
/var
on all the Fedora Atomic Desktop (the "immutable" flavors), so I had to uninstall it a few months ago :(In my case, I'm using an alternate method to install Nix as
Single-user
, which works great. The only issue is the symlink issue you mentioned in your OP up to2.21.1
.
i'm literally using fedora kinoite right now, and it update selinux policies from what i read in the installer, what issue you had? (and my nix profile is located in .local/state so i think it's also single-user)
from nix-installer.
Moar Kinoite goodness! 💙
TL;DR: I'm not using Kinoite itself, but a close-to-vanilla image that include some batteries.
I'm running https://universal-blue.org + https://blue-build.org/. uBlue is a special sauce you pour on top of ostree
-based spins, that allows you to customize your images the way you want them (I.e. https://github.com/cig0/bluebuild/blob/main/config/recipes/). uBlue adds a few QoL enhancements to vanilla Atomic images (like Kinoite), and then I take those images as my base images for my hosts. A great uBlue derivated is https://preview.getaurora.dev/, which was born out of the desire of enjoying all the goodness of https://projectbluefin.io/ (Universal Blue official image), but with the greatness of KDE as DE.
Anyway, I believe that's enough context. So, the first thing I noticed when running Determinate's installer was that the policy somehow breaks SDDM - i.e. avatars won't show up on the login screen. It also produces some other side effects like:
I'm also being spammed with the AVC error messages:
Can you confirm you're not experiencing any weird stuff on your official Atomic Desktop Kinoite image, like the one I describe above?
from nix-installer.
Can you confirm you're not experiencing any weird stuff on your official Atomic Desktop Kinoite image, like the one I describe above?
nop, never saw these errors and my sddm is working fine, also you can always rollback if something bad happens no?
from nix-installer.
Can you confirm you're not experiencing any weird stuff on your official Atomic Desktop Kinoite image, like the one I describe above?
nop, never saw these errors and my sddm is working fine, also you can always rollback if something bad happens no?
This is super interesting.
I downloaded the Fedora Atomic Kinoite 39 (https://download.fedoraproject.org/pub/fedora/linux/releases/39/Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-39-1.5.iso) image, and the F40 Beta Kinoite image (https://download.fedoraproject.org/pub/fedora/linux/releases/test/40_Beta/Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-40_Beta-1.10.iso), and definitely can reproduce the error.
Methodology:
- I created a VM for each distro
- Refreshed the repositories metadata
- Upgraded the OS via
rpm-ostree
- Upgraded everything else with Discover
The only additional change I made to the Fedora Atomic Desktop 40 Beta Kinoite installation was to switch the Fedora SDDM theme to KDE's theme -- everything else was left untouched:
Fedora Atomic Desktop Kinoite 39
Before applying DS' Nix installer:
After applying DS' Nix installer:
Fedora Atomic Desktop Kinoite 40 Beta
Before applying DS' Nix installer:
After applying DS' Nix installer:
Edit: I forgot to mention I installed Nix using the same command from #912 (comment)
curl --proto '=https' --tlsv1.2 -sSf -L https://install.determinate.systems/nix | sh -s -- install --nix-package-url https://releases.nixos.org/nix/nix-2.21.2/nix-2.21.2-x86_64-linux.tar.xz
from nix-installer.
actually @cig0 you already have a VM, make a test for me, reinstall the vm like you did, but DON'T install nix, just create another user like you would you in KDE (going to settings and clicking Add users) and log out to see if the sddm changes
from nix-installer.
actually @cig0 you already have a VM, make a test for me, reinstall the vm like you did, but DON'T install nix, just create another user like you would you in KDE (going to settings and clicking Add users) and log out to see if the sddm changes
@Viliansh I reverted all the changes made by the installer by deleting the VM snapshot and booting from the one I took right after updating both systems for the first time. The SDDM background image for F40 Beta Kinoite is the stock one (as I took the VM snapshot before even changing the SDDM theme).
HTH!
from nix-installer.
hmmm, i can't print it, but i reverted my sddm going to /etc/sddm.conf.d/kde_settings.conf and writing this [Users] MaximumUid=1000 MinimumUid=1000
because my user is uid=1000, so it only show my user, look at /etc/passwd to be sure what's your uid
from nix-installer.
hmmm, i can't print it, but i reverted my sddm going to /etc/sddm.conf.d/kde_settings.conf and writing this
[Users] MaximumUid=1000 MinimumUid=1000
because my user is uid=1000, so it only show my user, look at /etc/passwd to be sure what's your uid
Do you mean after using the installer?
from nix-installer.
Related Issues (20)
- Uninstaller: error deleting APFS volume <auto generated issue. almost> HOT 1
- Uninstaller: rolling back nix `launchd` services currently is not best-effort
- Installer [minor]: `macOS` keychain item is named after APFS container device node and not after `Nix Store` APFS volume
- error: unable to start build process HOT 4
- The keychain lacks a password for the already existing "Nix Store" volume HOT 1
- macOS, zsh, ssh and path_helper HOT 1
- The keychain lacks a password for the already existing "Nix Store" volume HOT 2
- Group `nixbld` existed but had a different gid (996) than planned (30000) HOT 2
- System has not been booted with systemd as init system (PID 1). Can't operate. HOT 1
- macOS 15 has group id 301 occupied. might need changing HOT 6
- MacOS 15.0 Beta broke users - attempting to re-install HOT 2
- nix-installer not placing nix on path in arch linux
- Crashes with `trying to unpack outside of destination path: /nix/temp-install-dir` if `/nix/temp-install-dir` exists
- Can't install or repair due to corrupted Nix store HOT 1
- nix-installer is inconsistent about what it does with nix-daemon.service
- --force has no effect if `nix-daemon.service` already exists
- Feature request: `/nix/nix-installer uninstall --keep-store`
- "uninstall" deletes files beyond those it says it will delete
- <autogenerated-issue>
- linux-multi - No such file or directory (os error 2)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nix-installer.