<opalvaults[m]>can anyone tell me how to get sway to show up in GDM loging menu? unfortunately .guix-profile/share/xsession is read-only. Any other spot that GDM checks? I've also guix system reconfigured with sway in the package list
<opalvaults[m]>so in theory it should have popped up if it was packaged with a .desktop file
<GNUtoo>I had to test that but I've some updates issues at the moment
<opalvaults[m]>The desktop environments in Guix use the Xorg display server by default. If you’d like to use the newer display server protocol called Wayland, you need to use the sddm-service instead of GDM as the graphical login manager. You should then select the “GNOME (Wayland)” session in SDDM. Alternatively you can also try starting GNOME on Wayland manually from a TTY with the command “XDG_SESSION_TYPE=wayland exec dbus-run-session
<opalvaults[m]>gnome-session“. Currently only GNOME has support for Wayland.
<opalvaults[m]>but I'm not exactly sure where I'm supposed to put that declaration
<opalvaults[m]>my file doesn't have anything in particular regarding GDM, only gnome-desktop-service-type
<opalvaults[m]>Yeah I think having GDM be compositor/server agnostic would be nice
<opalvaults[m]>okay, so I'm trying to get Sway installed and showing up in GDM. I have sway installed, and I removed xorg from the service modules. What is the correct syntax to add gdm to services without xorg?
<opalvaults[m]>because i'm just running into repl error after repl error. i think im going crazy looking at the word 'unwind' and 'with-exception-handler'.
<awb99>I have the same problems as opalvault when trying to install sway on my machine.
<awb99>it would be great if anyone could post a config that works.
<awb99>I had a look at all configurations that I could find, and I dont think anyone of the publicly available configs for sway work.
<awb99>I am trying to rebuild my system, and I am getting a lot of node dependencies that I have no idea which package brings them. I tried to graph the packages but it seems that I can only graph the packages of one package.
<lilyp>it might be stuck and not react to keyboard input tho
<Kabouik>The install was made from the Guix System installer iso. I couldn't install using the GUI (got backtrace issues) and I struggled with the manual install, so what I did is go in the shell for manual install, and from there use `guix system image --image-type=efi-raw /path/to/some-config.scm`, and then I dded the image file to a drive.
<Kabouik>It does boot, but leaves me there (picture posted above)
<Kabouik>Yeah I have to try tty. Problem is I was travelling so I took an old 40% keyboard I never used, I have to find how to emulate F2 :p
<pkal>Kabouik: If you don't have anything else installed, I think it is better to just do a clean reinstallation.
<Kabouik>Yes, but I don't know how that would chance since this is already a new install from last night with 0 change
<Kabouik>What's weird when booting is I am prompted for login and password before the issue occurs, and if I'm fast enough, I can even login. But regardless, the booting continues and will eventually get stuck (see login at the top): https://0x0.st/orAK.jpg
<pkal>Well you could install the system without GDM, or chroot to reconfigure the system to replace GDM with something like slim
<Kabouik>I'm trying to chroot but fail due to /bin/bash not found. I tried `sudo chroot /path/to/guix-fs /gnu/store/hash-bash/bin/bash and it did went through, but then it can't find any command, I guess it doesn't know where to look for executables
<Kabouik>Also weirdly the hostname was that of my host distro, not the guix hostname, so I'm not sure chroot really worked
<Kabouik>How did you manage to chroot into your guix filesystem pkal?
<fiesh>jackhill: so actually, I take back that modify-sysfs-in-some-way is a feature that's missing. it can all be done with udev, more or less at least, only hindered by its awful syntax and debugging options
<rekado>apteryx: stuck :-/ We’re out of space on the SAN. We’ve copied 4.2TB and the SAN has hit its reserve, so we can’t even get the allocated 5TB filled.
<rekado>so, currently, there are no more experiments from my side.
<jackhill>fiesh: yeah, all we might need is something in the cookbook or manual
<rekado>also: the discussion at https://issues.guix.gnu.org/51787 has provided enough evidence that there isn’t all that much we can do to improve performance for /gnu when we insist on keeping it flat and huge.
<rekado>use of btrfs does not alleviate concerns over fragmentation, and its baseline performance is considerably worse in our initial tests.
<rekado>xfs might be better for /gnu, but it’s unclear if it matters at our scale
<rekado>xfs cannot easily be grown, so it would be messier to maintain in the long run
<rekado>ext4 has good performance on the SAN and it’s easy to grow as we get more hardware.
<jackhill>rekado: are you sure? I though xfs could be grown, but not shrunk (while ext4 can be offline, and btrfs can be online)
<rekado>the biggest impact perhaps is the use of tiered storage; SSDs for caching boosts performance noticeably.
<lilyp>Kabouik, pkal: As perverted as it sounds, but you might have an easier chance switching VTs earlier than later
<Kabouik>I rebooted but I think there was still something wrong in the filesystem, after I booted, the terminal didn't know any command except `guix` (not even ls or cp or mkdir), even after I sourced /etc/profile
<Kabouik>Well that is weird. Guix was installed on a USB thumb drive, and now that I have powered Guix off and rebooted in another distro, the thumb drive doesn't show up anymore. I'm afraid it might be lost.
<Kabouik>lsusb lists it, but nor parted nor lsblk see anything (they used to).
<podiki[m]>that could explain it, if the drive was failing :/
<Kabouik>Hum that's weird though, I always got to the grub menu at least and then Guix started to boot. After I tried something like you did (changing /var/*/gdb UID to 983), I got the same issue once again, and then on the next boot it did work and started X. I couldn't do anything in there because no internet connection and no commands found, so I powered off, and now the drive shows in lsusb but not lsblk. I can't see how it would have worked "this much" if
<podiki[m]>could have been its last legs? or filesystem corruption (would that mean it wouldn't show in lsblk?); not sure
<Kabouik>Yeah I really don't understand why it no longer shows in lsblk, but I'm very doubtful about it failing just right when I try to install Guix while I have been using it for so long before with no issue, don't think it's a coincidence
<Kabouik>Even the BIOS stopped listing it as a boot device