IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 2 January 2019   (all times are UTC)

08:48ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
13:51spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)
14:00ta2fb has left IRC (ta2fb!~tadam@50-205-35-98-static.hfc.comcastbusiness.net, Quit: Leaving.)
15:00adrianorg has joined IRC (adrianorg!~adrianorg@187.113.250.144)
15:03adrianor1 has left IRC (adrianor1!~adrianorg@191.32.100.105, Ping timeout: 250 seconds)
19:29GodFather has joined IRC (GodFather!~rcc@38.135.45.194)
19:46ta2fb has joined IRC (ta2fb!~tadam@50-205-35-98-static.hfc.comcastbusiness.net)
19:46
<ta2fb>
alkisg: you were so helpful yesterday, I have another question - is there a simple way to enable screen lock? it doesn't seem to start because gdm isn't running
19:47
<alkisg>
ta2fb: remind me, which de are you using?
19:49
By default, the user password isn't transferred to fat clients
19:49
So if you locked, it wouldn't be possible to unlock
19:49
Some DEs are clever enough to see that and prohibit locking
19:49
!lock
19:49
<ltsp>
(lock [<channel>] <key>) -- Locks the factoid(s) associated with <key> so that they cannot be removed or added to. <channel> is only necessary if the message isn't sent in the channel itself.
19:49
<alkisg>
!hash
19:49
<ltsp>
I do not know about 'hash', but I do know about these similar topics: 'LDM_PASSWORD_HASH', 'ROOT_PASSWORD_HASH'
19:49
<alkisg>
!LDM_PASSWORD_HASH
19:49
<ltsp>
LDM_PASSWORD_HASH: LDM_PASSWORD_HASH=True in lts.conf saves the password hash to /etc/shadow on login, so that the users can unlock the screensaver etc. If they happen to change their password though, that only takes effect until logout.
19:49
<alkisg>
Try this one ^
19:50
<ta2fb>
I do have LDM_PASSWORD_HASH=true
19:50
<alkisg>
And which DE?
19:50
(desktop environment)
19:50
Ubuntu, MATE, Lubuntu etc?
19:50
<ta2fb>
the default, ubuntu
19:50
<alkisg>
So, gnome
19:50
<mwalters>
fur keeps you warm
19:50
oops, wrong channeel ;)
19:51
<alkisg>
For sure
19:51
:)
19:51
<mwalters>
fur sure
19:51
<alkisg>
:D
19:51
ta2fb: and what happens if you try to lock screen on the client?
19:51
No response at all? Any error message?
19:52
<ta2fb>
nothing happens, get this message in /var/log/syslog
19:52
Couldn't lock screen: Cannot invoke method; proxy is for a well-known name without an owner
19:52
and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
19:52
which I googled which has something to do with gdm being stopped
19:52
I started it but that broke things as you could imagine
19:53
<alkisg>
Oh yeah don't start gdm, this won't be ltsp anymore
19:53
So, the user can properly authenticate, right? For example, on the client, if you open a terminal and run `su - $USER`, you can re-login as the user. Correct?
19:54
<ta2fb>
yes, and I also enabled ssh and that works as well
19:54
<alkisg>
It would be a shame if gnome doesn't work without gdm. For example, ubuntu had lightdm for ages.
19:54
<ta2fb>
yea
19:55
<alkisg>
Open a bug report in ltsp; maybe sometime someone will have a look at it
19:55
Here I maintain 1000+ schools, but we're using MATE
19:55
I plan to switch them to gnome later on for Ubuntu 20.04
19:55
!ltsp-bug
19:55
<ltsp>
ltsp-bug: To file a bug report for upstream LTSP, go to https://bugs.launchpad.net/ltsp
19:55
<ta2fb>
ok, sounds good
19:56
I will file a report and will play around with some things
19:56
we had to do some funky stuff on 16.04 before so I will see how that solution works and will let you know
19:56
<alkisg>
So for the moment, ltsp-related mate bugs get solved more quickly; while for other DEs, not so much, unless someone tests and comes up with a solution
19:57* alkisg tried gnome recently and it needed 1 GB just for the DE; we have clients with 1 GB that we expect to run firefox too :)
19:57
<alkisg>
It became horribly bloated with the "moving the DE to javascript" thing
19:58
<mwalters>
(not LTSP specific) while we're on the subject of DEs and screensaves... how can I make a system wide idle-time out for mate/ltsp?
19:58
I put a file, `screen-timeout` in /etc/dconf/db/local.d
19:58
<alkisg>
In general, you run dconf watch / in a terminal, and change whatever setting you want
19:58
that way you see the related gsetting
19:59
<mwalters>
and put in [org/mate/desktop/session]\nidle-delay=15
19:59
but no luck
19:59
<alkisg>
Then, you can either put defaults in /usr/share/glib/schemas, or mandatory settings in /etc as you said
19:59
<mwalters>
yeah, I figured that part out
19:59
np just hoping you knew off the top of your head, I'll keep digging
20:00
<ta2fb>
you mean screen lock?
20:00
ltsp-chroot
20:00
20:00
mkdir -p /etc/dconf/db/local.d/locks
20:00
20:00
echo """/org/gnome/desktop/session/idle-delay
20:00ta2fb has left IRC (ta2fb!~tadam@50-205-35-98-static.hfc.comcastbusiness.net, Excess Flood)
20:00
<mwalters>
lol
20:00ta2fb has joined IRC (ta2fb!~tadam@50-205-35-98-static.hfc.comcastbusiness.net)
20:00
<mwalters>
wb ;)
20:00
<ta2fb>
oops
20:00
<alkisg>
Hehe, that will teach you to flood in freenode :P
20:00
!pastebin
20:00
<ltsp>
pastebin: try !paste
20:00
<ta2fb>
did you get all that?
20:00
<alkisg>
!paste
20:00
<ltsp>
paste: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
20:00
<mwalters>
no, I'd appreciate it if you co uld paste bin it, though. Thanks!
20:01
<ta2fb>
that link doesn't resolve for me
20:01
<mwalters>
I figured i had an older way to do it or something and I just couldn't figure out the magic words to google it
20:01spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Ping timeout: 246 seconds)
20:01
<mwalters>
doesn't seem like it's common to have multiuser GUI based boxes
20:01
<alkisg>
https://wiki.gnome.org/Projects/dconf/SystemAdministrators
20:01
This is the guide ^
20:02
<mwalters>
Thanks!
20:02
<alkisg>
"Lockdown is supported by creating a 'locks' subdirectory in the keyfile directory (ie: /etc/dconf/db/local.d/locks)." etc etc
20:02
<mwalters>
oh, I missing the locks
20:03
Great stuff, thanks!
20:03
<alkisg>
np
20:09
<ta2fb>
it looks like http://ltsp.pastebin.com doesn't resolve for me, any reason why that may be the case?
20:13
<mwalters>
doesn't for me either
20:14spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)
20:20
<alkisg>
!forget paste
20:20
<ltsp>
The operation succeeded.
20:20
<alkisg>
!forget pastebin
20:20
<ltsp>
The operation succeeded.
20:23
<alkisg>
!learn paste as To avoid channel flooding, please upload text longer than 3 lines to http://paste.debian.net. Don't forget to paste the resulting URL here.
20:23
<ltsp>
The operation succeeded.
20:23
<alkisg>
!learn pastebin as see !paste
20:23
<ltsp>
The operation succeeded.
20:25
<ta2fb>
alkisg: you can close this bug: https://bugs.launchpad.net/ltsp/+bug/1810330
20:27
mwalters: this will lock the screen after a time you specify - won't do a logout
20:27
http://paste.debian.net/1058373/
20:27
ignore the fact that the comment time doesn't match the actual value sent
20:32
<alkisg>
ta2fb: you can close it, there's no "bug maintainer"
20:33
<mwalters>
oh, derp
20:33
I also put it on the ltsp server... not the chroot
20:33
My ltsp boxes are all VMs now... with chroots...
20:33
I can't keep up with this web of abstractions I've sewn myself in to
20:34
<ta2fb>
alkisg: would I mark the bug as fix committed?
20:35
<||cw>
mwalters: I know that feel
20:36
in testing stuff I had a usb-serial device passed to a vm guest that netbooted to ltsp and pass the port to xfreerdp to a terminal server
20:37
also all my servers are vms in a cluster. it's the only way to live these days
20:41
<ta2fb>
non-important question - is there a way to change the initial login screen to add a banner/text?
20:55
<mwalters>
ta2fb: I'm pretty sure there's something on ltsp.org about that
20:57
http://wiki.ltsp.org/wiki/Tips_and_Tricks/User_Experience#LDM_Greeter_and_Theme
20:58
this is cryptic, but should probably point you in the right direction
20:58
specifically, the very last line in that section
21:03
<ta2fb>
cool, thanks, mwalters
21:09
<alkisg>
ta2fb: "fix committed" means that code was added in ltsp to fix it
21:09
So no, it should be "invalid", which means "not a bug in the ltsp code"
21:09
I set it to invalid.
21:09
assignee is the one that will write the ltsp code that will fix the bug
21:10
So it should be left blank, since it wasn't a bug
21:19
<ta2fb>
oh, ok, thank you for clarifying
22:32vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
22:37ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
22:53
<josefig>
hello, is there a way to install epoptes-client and "manage" the remote pcs on ltsp arch ?
22:53
by remote I mean local LAN IP
23:18GodFather has left IRC (GodFather!~rcc@38.135.45.194, Ping timeout: 244 seconds)