These are the channel logs matching your query lightdm
| 2023-01-19 | [03:19:41] <SUPERB[m]> I searched the website but couldn't figure out how should I configure the /etc/config.scm after installing XFCE and lightdm manually through the shell! |
| 2023-01-19 | [03:31:22] <gnucode> also delete lightdm-service-type |
| 2023-01-18 | [17:55:35] <podiki[m]1> well, my elogind change did something...it broke lightdm |
| 2023-01-18 | [17:55:55] <podiki[m]1> apteryx: glad to have lightdm back, but my change to elogind to ignore power key seems to have broke it (just get blinking cursor) |
| 2023-01-18 | [17:57:04] <apteryx> podiki[m]1: does the lightdm system test reproduces the problem? |
| 2023-01-18 | [17:58:10] <podiki[m]1> I have not tried to run the tests, I'm justusing lightdm (no configuration change) which worked, modifying elogind to change power button behavior gives me just the blinking cursor |
| 2023-01-18 | [18:00:39] <podiki[m]1> apteryx: haven't run yet, but looking at the lightdm tests, it just looks for empty greeters or multiple configurations; I haven't modified either |
| 2023-01-18 | [18:03:07] <apteryx> make check-system TESTS=lightdm |
| 2023-01-18 | [18:05:30] <podiki[m]1> or is it unrelated to lightdm and is the elogind change? (I'll try with another dm) |
| 2023-01-18 | [18:05:46] <apteryx> I'm not sure, but it could be a lightdm bug |
| 2023-01-18 | [18:06:38] <apteryx> any errors under /var/log/lightdm/ ? |
| 2023-01-18 | [18:07:04] <podiki[m]1> a belated thanks for lightdm service though, i used to use it on arch and have preferred it over sddm/gdm |
| 2023-01-18 | [18:08:59] <podiki[m]1> ah, error in seat0-greeter.log: Error reading existing Xauthority: Failed to open file ?/var/lib/lightdm/.Xauthority?: Permission denied |
| 2023-01-18 | [18:14:19] <podiki[m]1> apteryx: no changes to my system config besides sddm to lightdm and elogind power button |
| 2023-01-18 | [18:15:33] <podiki[m]1> apteryx: some state leftover from previous dm? but I did use lightdm successfully just before fixing my elogind change |
| 2023-01-18 | [18:17:46] <podiki[m]1> apteryx: hmm. i haven't used the vm tests before, I ran the lightdm tests (passed) so it was built, how can I use it now? |
| 2023-01-18 | [18:18:58] <apteryx> podiki[m]1: something like 'guix system vm -e '(@@ (gnu tests lightdm) %lightdm-os)' |
| 2023-01-18 | [18:49:08] <podiki[m]1> apteryx: any idea why lightdm is trying to load xauthority from /var/lib/lightdm and getting a permission denied? |
| 2023-01-18 | [19:32:50] <podiki[m]1> apteryx: lightdm doesn't work anymore even without the elogind config; something funky going on, why is /var/lib/lightdm owned by 972:974?? |
| 2023-01-18 | [19:44:54] <podiki[m]1> apteryx: fixed! i removed /var/lib/lightdm (and lightdm-data) and reconfigured. somehow the directories were owned by that weird numerical user not lightdm |
| 2023-01-18 | [20:20:24] <apteryx> perhaps you switched your graphical login manager to something else, leading to the lightdm user being removed, then recreated when you added it back with a different id? |
| 2023-01-18 | [20:22:29] <podiki[m]1> not sure. I think the original operation was changing sddm to lightdm but with wrong elogind config (shouldn't have done anything) which worked, then fixing elogind and lightdm was broken |
| 2023-01-15 | [21:59:25] <SUPERB[m]> <lechner> "and then you rebooted?" <- There is an error for lightdm-service-type |
| 2023-01-14 | [09:22:34] <SUPERB[m]> So after rebooting I installed XFCE and then lightdm |
| 2023-01-14 | [09:33:27] <vivien> SUPERB[m], you would edit /etc/config.scm to add lightdm-service-type and xfce-desktop-service-type according to the example in the manual for lightdm-service-type and as (service xfce-desktop-service-type) for xfce, and run sudo guix system reconfigure /etc/config.scm |
| 2023-01-14 | [18:22:16] <SUPERB[m]> vivien: For installing xfce and lightdm through the shell on Debian I used to reboot after the installation was complete and then install xfce and lightdm and then:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/31e04df3172c9a389d1b993100f7f1305887efe4>) |
| 2023-01-14 | [19:54:44] <Fare> SUPERB[m], have you tried lightdm ? |
| 2023-01-14 | [19:56:10] <SUPERB[m]> Fare: I've installed xfce and lightdm but don't know how to enable it |
| 2023-01-14 | [20:01:58] <SUPERB[m]> "systemctl enable lightdm" would enable it on Debian |
| 2023-01-14 | [20:19:03] <SUPERB[m]> <vivien> "SUPERB, you would edit /etc/..." <- I thought I should add them under service section cuz it was xfce-desktop-service-type and lightdm-seevice-type |
| 2023-01-14 | [20:20:36] <oriansj> you would replace the (service slim-service-type) with (service lightdm-service-type) in the services section of your configuration |
| 2023-01-14 | [20:21:14] <oriansj> look into lightdm-configuration if you want to configure it away from stock |
| 2023-01-14 | [20:23:12] <oriansj> and select it at loginwith lightdm |
| 2023-01-14 | [20:27:28] <oriansj> SUPERB[m]: lightdm like most login managers allow you to select the desktop environment you run at login time. |
| 2023-01-14 | [22:30:34] <SUPERB[m]> But which one is the right place gor lightdm command? |
| 2023-01-14 | [22:39:28] <nckx> Also make sure you're importing the (gnu services lightdm) module at the top of this file. |
| 2023-01-14 | [22:50:22] <SUPERB[m]> nckx: I installed Guix without checking any DE and after installation was complete and reboot installed XFCE and lightdm through the shell |
| 2023-01-13 | [20:58:42] <mirai> *cough* lightdm |
| 2023-01-13 | [20:59:53] <apteryx> is lightdm doc out of sync? |
| 2023-01-13 | [21:00:33] <apteryx> by the way, if you use lightdm, I was never able to fix this bug: https://github.com/Xubuntu/lightdm-gtk-greeter/issues/105 |
| 2023-01-13 | [21:00:53] <guix-helper-bot> [PATCH] Properly format list of packages & sync lightdm documentation. <https://issues.guix.gnu.org/60582> |
| 2023-01-13 | [21:12:02] <mirai> apteryx: that lightdm issue, could it be related to gdm missing icons? |
| 2023-01-11 | [23:18:08] <Euler-Maskerony> Now I am trying to set up display manager (lightdm). I have some problems. Can someone help me, please? First: why there is no information anywhere that I must add (gnu services lightdm) to use-modules? |
| 2023-01-11 | [23:18:52] <Euler-Maskerony> Only with this line compiler accepts lightdm-service-type |
| 2023-01-11 | [23:26:47] <Euler-Maskerony> Here you may see that I defined lightdm service and there xorg-configuration is commented, because for some reason I can't specify keyboard-layout. It says that it is wrong type. |
| 2023-01-07 | [20:19:09] <daviid> ok, then you ne3ed to disable an option or switch to lightdm, which i did, because i was horrified the gnome team made this change without 'any warnings' and i was managing remotely, few servers ... that day, a few y ago now was a total disaster for me and a all bunch of researchers ... |
| 2023-01-07 | [20:20:08] <daviid> but i highly recommend you switch to lightdm, and stilluse gnome as a desktop if you wish ... |
| 2023-01-07 | [20:20:50] <old> Quick recipe for changing to lightdm? |
| 2023-01-07 | [20:21:10] <daviid> i switched to lightdm :) - but let me see if i cn find the setting, i think others here also know ... |
| 2023-01-07 | [20:21:36] <daviid> just install lightdm, remove gdm and restart |
| 2023-01-07 | [20:26:52] <old> So just adding a (service lightdm-service-type ...) should suffices? |
| 2023-01-07 | [21:02:27] <old> with lightdm |
| 2023-01-07 | [21:03:01] <old> And lightdm shows "Failed to start session" |
| 2023-01-07 | [21:52:41] <daviid> old: ok, as i don't use guix, i would edit the /etc/gdm3/greeter.dconf-defaults - as suggested by the link, it has the options commented, and explains tose ... i never had that problem with lightdm ... |
| 2022-12-31 | [01:36:38] <omlet[m]> Its possible replace gdm to ly lightdm ? |
| 2022-12-31 | [01:38:12] <mirai> add lightdm like any service |
| 2022-11-28 | [18:45:19] <unmatched-paren> civodul: how about greetd and the lightdm-service-type? |
| 2022-11-18 | [16:09:34] <apteryx> bah, qt applications don't work atop lightdm... |
| 2022-11-17 | [16:45:24] <apteryx> yeah that's what I'll have to do (or lightdm or slim) if I can't figure it out quickly |
| 2022-11-17 | [20:54:29] <apteryx> ACTION couldn't make gdm work again on their desktop -- now on lightdm |
| 2022-10-17 | [18:14:01] <GNUtoo> Maybe it was done by the display manager like gdm / lightdm, etc |
| 2022-09-20 | [05:41:50] <apteryx> is 'make check-system TESTS=lightdm' failing for anybody else? |
| 2022-09-09 | [20:16:08] <apteryx> lightdm-seat-configuration has the xserver-command for example |
| 2022-08-31 | [07:39:13] <roptat> oh wow, lightdm :D |
| 2022-08-29 | [17:09:35] <podiki[m]> apteryx: great getting the lightdm service finally done! a nice addition |
| 2022-08-29 | [17:10:51] <podiki[m]> I used lightdm a while back (on Arch), might try it out again on next reconfigure |
| 2022-08-13 | [09:15:51] <unmatched-paren> oh, cool, maxim sent a patchset for a lightdm service |
| 2022-08-10 | [15:46:00] * apteryx has a weird issue with Wrong type to apply: #<syntax-transformer lightdm-configuration-greeters> unless I byte compile the module |
| 2022-08-10 | [16:12:34] <apteryx> jpoiret: I'm working out kinks on (gnu services lightdm) (not yet added): https://paste.centos.org/view/1c4c115b. I define a configuration using define-configuration. It does some introspection to fake polymorphism on the greeter configurations, via variable name manipulation. Apparently if the module is not byte compiled, the bindings made by define-configuration are not finalized or something, |
| 2022-08-10 | [16:12:36] <apteryx> appear as syntax-transformer instead of procedure. The error trying to run the module after a change without byte compilation: Wrong type to apply: #<syntax-transformer lightdm-configuration-greeters> |
| 2022-08-10 | [16:21:29] <apteryx> (module-ref (current-module) 'lightdm-configuration?) -> syntax-transformer |
| 2022-08-10 | [16:21:52] <apteryx> but: (class-of lightdm-configuration?) -> procedure-class |
| 2022-08-10 | [16:24:22] <jpoiret> what does `lightdm-configuration?` tell you? |
| 2022-08-10 | [16:26:01] <apteryx> $5 = #<procedure %lightdm-configuration?-procedure (obj)> |
| 2022-08-10 | [16:27:31] <jpoiret> it works in (class-of lightdm-configuration?) because Guile starts by reading the code, and when stumbling upon lightdm-configuration? it applies the corresponding syntax-transformer, which ends up with (class-of %lightdm-configuration?), which when eval'd gives you the result you got |
| 2022-08-10 | [16:28:28] <jpoiret> but when you (module-ref (....) 'lightdm-configuration?), the syntax-transformer is never applied because it is never read, rather, you get the raw syntax-transformer object that it refers to |
| 2022-08-10 | [22:38:06] <apteryx> jpoiret: I found the culprit in lightdm.scm; it was the order of usage of the syntax in the file |
| 2022-08-09 | [07:24:56] <apteryx> phew, tested that XDMCP works in lightdm (it didn't in GDM) |
| 2022-08-08 | [05:51:56] <apteryx> (working on lightdm) |
| 2022-08-08 | [15:31:04] <apteryx> would there be an elegant way to provide an environment variable to the lightdm login greeter? It doesn't carry its parent (lightdm) environment variables, rather it seems its env is initialized anew from /etc/environment (PAM) and perhaps /etc/profile |
| 2022-08-08 | [15:34:59] <apteryx> the alternative is to hack the lightdm-gtk-greeter package to look its default config file at /etc/lightdm/gtk-greeter.conf |
| 2022-08-08 | [16:09:24] <apteryx> civodul: what do you mean by 'necessarily unset'? I'd expect the login components spawned by lightdm to inherit its environment (which is furher refined by sourcing /etc/profile, IIUC). |
| 2022-08-08 | [16:10:45] <apteryx> civodul: my use case here is allowing lightdm-gtk-greeter to find its configuration via XDG_CONFIG_DIRS, which I set on lightdm, but is overridden by /etc/profile |
| 2022-08-08 | [17:11:36] <civodul> apteryx: does lightdm-gtk-greeter have a wrapper to set XDG_*? |
| 2022-08-08 | [17:24:34] <civodul> apteryx: from what i see, lightdm-gtk-greeter would put everything it needs as a prefix of XDG_DATA_DIRS, but i guess i'm overlooking something |
| 2022-08-08 | [17:37:14] <apteryx> its config is generated from the lightdm service |
| 2022-08-08 | [17:39:49] <apteryx> (with a patch to lightdm-gtk-greeter that has its default config (CONFIG_FILE) set to /etc/lightdm/lightdm-gtk-greeter.conf |
| 2022-08-08 | [19:23:39] <apteryx> hmm... "Failed to launch bus: Failed to connect to session bus" from lightdm gtk greeter logs |
| 2022-08-08 | [19:37:55] <apteryx> ah, lightdm clears the env itself for the child processes (seats) it launches: process_set_clear_environment (script, TRUE); |
| 2022-08-07 | [00:36:50] <rekado> (service lightdm-service-type) perhaps? |
| 2022-08-07 | [02:55:54] <apteryx> rekado_: exactly: (services (cons lightdm-service-type %my-desktop-services)) thanks :-) |
| 2022-08-07 | [03:58:40] * apteryx tries booting a VM with lightdm as display manager |
| 2022-08-07 | [06:48:59] * apteryx got lightdm to run, with icons missing |
| 2022-08-07 | [16:02:10] <apteryx> any clue to fix: [lightdm] ** (process:409): WARNING **: 07:21:15.347: Error updating user /org/freedesktop/Accounts/User1000: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface ?org.freedesktop.DisplayManager.AccountsService? |
| 2022-08-07 | [16:09:39] <apteryx> the lightdm service requires dbus, but not polkit... perhaps that's the problem |
| 2022-08-07 | [16:39:10] <apteryx> so, the lightdm-service-type needs to extend the system profile to add the lightdm package for dbus, and the lightdm service needs to have XDG_DATA_DIRS set to the lightdm package for the accountsservice extensions to be found |
| 2022-08-07 | [17:00:23] <podiki[m]> would be great to have lightdm and more robust dbus service finding while we're at it :) |
| 2022-08-07 | [17:02:45] <podiki[m]> apteryx: you are reviving that older patch series with the lightdm service? |
| 2022-08-07 | [20:21:52] <apteryx> (about lightdm) |
| 2022-08-07 | [20:22:29] <podiki[m]> nice! I used to use lightdm and liked it for my non-DE life |