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


Channel log from 15 April 2015   (all times are UTC)

00:26andygraybeal has left IRC (andygraybeal!~andy@h35.189.190.173.dynamic.ip.windstream.net, Ping timeout: 256 seconds)
01:23andygraybeal has joined IRC (andygraybeal!~andy@h35.189.190.173.dynamic.ip.windstream.net)
01:43telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
01:44telex has joined IRC (telex!teletype@freeshell.de)
02:45Yeison has joined IRC (Yeison!c8086f49@gateway/web/cgi-irc/kiwiirc.com/ip.200.8.111.73)
02:45
<Yeison>
good evening
02:52* vagrantc waves
03:00Yeison has left IRC (Yeison!c8086f49@gateway/web/cgi-irc/kiwiirc.com/ip.200.8.111.73, Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
03:05gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Remote host closed the connection)
03:31MarconM has joined IRC (MarconM!~Marcelo@191.222.4.69)
03:31MarconM has joined IRC (MarconM!~Marcelo@unaffiliated/marconm)
04:06MarconM has left IRC (MarconM!~Marcelo@unaffiliated/marconm, Ping timeout: 264 seconds)
04:33vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi)
04:58gdi2k has left IRC (gdi2k!~gdi2k@49.151.77.1, Ping timeout: 255 seconds)
04:58gdi2k_ has left IRC (gdi2k_!~gdi2k@49.151.77.1, Ping timeout: 264 seconds)
05:00vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi, Ping timeout: 272 seconds)
05:10gdi2k_ has joined IRC (gdi2k_!~gdi2k@180.191.105.4)
05:12roue has left IRC (roue!~roue@66-188-172-213.dhcp.stcd.mn.charter.com, Ping timeout: 256 seconds)
05:14gdi2k has joined IRC (gdi2k!~gdi2k@180.191.105.4)
05:14vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi)
05:29vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
06:00roue has joined IRC (roue!~roue@66-188-172-213.dhcp.stcd.mn.charter.com)
06:13alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
06:22alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)
06:28vlt_ is now known as vlt
07:15gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
07:19gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Ping timeout: 240 seconds)
07:28mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
07:45Fenuks has joined IRC (Fenuks!~Fenuks@mail.c-lan.ru)
08:50Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
09:05gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
09:09gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Ping timeout: 252 seconds)
10:26khildin has joined IRC (khildin!~khildin@ip-213-49-84-128.dsl.scarlet.be)
10:54gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
11:00gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Ping timeout: 256 seconds)
11:11ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
11:13gdi2k has left IRC (gdi2k!~gdi2k@180.191.105.4, Quit: Leaving)
11:17gdi2k_ has left IRC (gdi2k_!~gdi2k@180.191.105.4, Ping timeout: 245 seconds)
11:18gdi2k_ has joined IRC (gdi2k_!~gdi2k@180.191.105.4)
11:22Faith has joined IRC (Faith!~paty@unaffiliated/faith)
11:34Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Quit: I Leave)
12:08khildin has left IRC (khildin!~khildin@ip-213-49-84-128.dsl.scarlet.be, Ping timeout: 256 seconds)
12:20telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
12:22telex has joined IRC (telex!~telex@freeshell.de)
12:29gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
12:54gdi2k_ has left IRC (gdi2k_!~gdi2k@180.191.105.4, Ping timeout: 252 seconds)
12:55gdi2k_ has joined IRC (gdi2k_!~gdi2k@180.191.105.4)
13:07MarconM has joined IRC (MarconM!~Marcon@unaffiliated/marconm)
13:43root has joined IRC (root!bad7c897@gateway/web/freenode/ip.186.215.200.151)
13:47work_alkisg has joined IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr)
13:55
<bennabiy>
Hi alkisg :)
14:13
<work_alkisg>
Hi bennabiy, everything ok?
14:13work_alkisg is now known as alkisg
14:14
<bennabiy>
I tried with stock Ubuntu and lost video on it as well
14:14
<alkisg>
Then it's an ubuntu issue, you should check on #ubuntu-x about that
14:14
(ubuntu, xorg, kernel, whatever)
14:14
non-ltsp though
14:14
<bennabiy>
but I moved an image over from a different lab that was just running the original mint 17 and it at least got me a visible window, although it was 640x480
14:15
yes
14:15
I do not want to trouble you with what does not apply to LTSP ( as I know you are already busy enough )... I was just saying hi
14:16
It is frustrating that it is not working.. but that is my issue to deal with
14:16
<alkisg>
As I wrote a few days back, I would suggest that you tried with stock ubuntu or debian or fedora, some of the main distributions, so that you know where to report it, be it upstream or distro-specific
14:16
Because if e.g. it's due to some older mint kernel, noone would care if mint doesn't update it
14:28
<bennabiy>
alkisg : it is the same with upstream ubuntu 14.04
14:28
I tried on 14.04
14:28
<alkisg>
Start chatting with people in #ubuntu-x, and try other/newer versions too
14:28
E.g. Ubuntu 15.04, fedora...
14:28
Debian...
14:29Markus123 has joined IRC (Markus123!~markus@178.165.131.36.wireless.dyn.drei.com)
14:31Markus123 has left IRC (Markus123!~markus@178.165.131.36.wireless.dyn.drei.com, Remote host closed the connection)
14:31Markus123 has joined IRC (Markus123!~markus@178.165.131.36.wireless.dyn.drei.com)
15:04mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
15:13khildin has joined IRC (khildin!~khildin@ip-213-49-84-128.dsl.scarlet.be)
15:15vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
15:17Fenuks has left IRC (Fenuks!~Fenuks@mail.c-lan.ru, Ping timeout: 240 seconds)
15:39alkisg is now known as work_alkisg
15:52khildin has left IRC (khildin!~khildin@ip-213-49-84-128.dsl.scarlet.be, Ping timeout: 248 seconds)
16:23
<championofcyrodi>
yesterday i added a new NUC to our ltsp clients. while running in my session things would be going 'fine', but then suddenly i would get a gnome ui popup asing for root@server's password with the window title 'ssh'
16:23
it looked as though my sshfs connection was being reset or something...
16:23
of course clicking cancel about 15 times makes it go away
16:37
<vagrantc>
it shouldn't be logging in as the root user
16:49AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-gzjqjkkmmghioari)
17:21Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
17:40Faith has joined IRC (Faith!~paty@unaffiliated/faith)
18:06telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
18:08telex has joined IRC (telex!teletype@freeshell.de)
18:46alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
18:49alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)
19:36awei has joined IRC (awei!4b44c5f9@gateway/web/freenode/ip.75.68.197.249)
19:38
<awei>
I have ltsp-server 5.5.4 and ldm 2:2.215 on client. but still having trouble unlocking screen on fat client. i type password in and i just get the animated loading icon. any ideas?
19:39khildin has joined IRC (khildin!~khildin@ip-213-49-84-128.dsl.scarlet.be)
19:55gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Remote host closed the connection)
19:56vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi, Ping timeout: 255 seconds)
20:00
<vagrantc>
awei: locking on fat clients require some hackish workarounds
20:01
awei: set LDM_HASHPASS=true in lts.conf, which will generate a local password hash that lasts as long as the user is logged in.
20:01
<awei>
vagrantc: i've made progress (like i can log in from tty1)
20:01
yup, got that part.
20:01
<vagrantc>
awei: what have you configured?
20:01
<awei>
so, i have ltsp-server 5.5.4 and ldm 2.2.15 on client, updated lts.conf
20:02
i can now log in via tty1 on fat client
20:02
<vagrantc>
how are you able to log in via tty?
20:02
<awei>
i dunno, it worked using non-root account
20:02
<vagrantc>
that's not normally possible
20:02
<awei>
i have /home mounted NFS, would that do anything?
20:02
<vagrantc>
did you manually configure a user in the chroot?
20:03
<awei>
nope.
20:03
i think it worked actually
20:03
<vagrantc>
awei: you have LDM_HASHPASS=true in lts.conf?
20:03
<awei>
let me try again... there's just a tremendous lag returning from locked screen.
20:03
vagrantc: yes, i have that in lts.conf LDM_HASHPASS=true
20:03
<vagrantc>
logging in via tty should only work while the user is logged in via LDM, then.
20:04
<awei>
yes, ok, it's working. nevermind... it's just laggy
20:04
<vagrantc>
before login, after login, the tty login shouldn't work
20:04* vagrantc sighs
20:04
<vagrantc>
:P
20:04
<awei>
:)
20:04
is the lag due to network latency?
20:04
or just crappy processor
20:05
initial unlock of screen took ~3 mins. successive attempts are much faster.
20:09
<vagrantc>
possibly crappy processor ...
20:09MarconM has left IRC (MarconM!~Marcon@unaffiliated/marconm, Quit: Leaving)
20:09
<vagrantc>
screensaver usually runs "nice" which can make it extra laggy under heavy load
20:10
but that sounds really bad.
20:10
not sure what would cause that
20:10
LDM_HASHPASS hasn't been around very long
20:10
<awei>
vagrantc: ok, thanks for info... also, fyi, i had to use LDM_PASSWORD_HASH=true and not LDM_HAS_PASS
20:10
<vagrantc>
though i think there are some fairly large installs using it
20:11
ah, fair enough
20:11
sorry for leading you astray
20:11
<awei>
vagrantc: no problem. thanks again.
20:12
vagrantc: is there a way to prevent from writing /usr/share/glib-2.0/schemas/10_ltsp_schema.override on every boot?
20:12
i see that it's disabling lock screen
20:14ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
20:15
<vagrantc>
awful.
20:15
no idea what does that
20:16
<awei>
vagrantc: ok. thx.
20:18
<vagrantc>
it actually writes to /usr/share/ ??
20:19
awei: what OS ?
20:19
<awei>
i *believe* that it is echoing to the /usr/share/...10_ltsp_schema.override with the gnome disable lockout screen stuff
20:19
i'm on ubuntu 14.04.2
20:19
<vagrantc>
nothing shoudln't be writing to /usr/ except dpkg unpacking packages...
20:20
<awei>
i've mounted my fat fat chroot as rw and i can see that the more i log in the more lines are being written to this file
20:20
<vagrantc>
nothing *should* be writing to /usr
20:20
<awei>
want me to write up a bug?
20:20
<vagrantc>
sure
20:20
<awei>
(to give back for all the help i received)
20:21
<vagrantc>
i mean, disabling screen locking on environments where (historically) screen locking just locked the user out makes some sense
20:21
but writing to a file in /usr seems like there's got to be some other way of accomplishing that ...
20:22
<awei>
i dont' *know* if that's what is exactly happening, it's just a hunch
20:22
just because i can see the file growing
20:22
<vagrantc>
does any package own the file?
20:23
dpkg -S ltsp_schema
20:23
<awei>
on fat client?
20:23Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
20:23
<vagrantc>
anywhere
20:23
<awei>
lemme try...
20:24
<vagrantc>
either from a booted fat client, or in the fat client chroot (or on the server if it's an ltsp-pnp style image)
20:24
<awei>
"dpkg-query: no path found matching pattern *10_ltsp.gschema.override*"
20:27
<vagrantc>
you might be overly specify
20:27
try "dpkg -S ltsp_schema
20:27
"
20:27
a file that generates that might be named something else entirely
20:27
<awei>
lemme try again...
20:28
<vagrantc>
unnless the filename isn't what you've said
20:28
could also try "locate ltsp.gschema" on the server
20:29
but the file that generates it could be named anything
20:29
might want to look around in /etc/X11/Xsession.d/ too
20:29
<awei>
ok, i'll try to track it down.
20:47alkisg_android has joined IRC (alkisg_android!~yaaic@176.92.155.141)
20:48
<alkisg_android>
awei, check /usr/share/ltsp/init-ltsp.d
20:48
<awei>
looking...
20:48
<alkisg_android>
it does that dynamically on boot
20:49
<vagrantc>
ah, it doesn't write it directly, it must call some script
20:49
<alkisg_android>
you can delete the script with INIT_COMMAND_01="rm /usr/..."
20:50
<vagrantc>
how did i miss that one
20:50
<awei>
i found it
20:50
it's in 50-gsettings-overrides
20:50
<vagrantc>
ah, i was given the wrong filename to search :P
20:51
<alkisg_android>
sorry small keyboard can't type much :)
20:51
<vagrantc>
that should really be optional.
20:51
<awei>
sorry, i was referring to the generated file
20:51
<vagrantc>
and certainly when LDM_PASSWORD_HASH is true
20:51
<alkisg_android>
previously there was no way to unlock
20:52
now sure it can be disabled when hash pass is true
20:52* vagrantc nods
20:52
<awei>
still want me to file a bug?
20:52
i'll just log it...
20:52
<vagrantc>
file a bug, sure
20:52khildin has left IRC (khildin!~khildin@ip-213-49-84-128.dsl.scarlet.be, Remote host closed the connection)
20:53
<vagrantc>
we also don't have a way to disable init-ltsp.d scripts :(
20:53
which would be more complicated code, but would allow admins to override things like this easily
20:54
<alkisg_android>
a space separated list would be easy to implement globally on sbin/init-ltsp
20:55
<vagrantc>
+ ! boolean_is_true "$LDM_PASSWORD_HASH" &&
20:55
rather than layered override files?
20:56* vagrantc always gets confused with negation checks against booleans
20:56
<alkisg_android>
i think i have such a don't-include list in cleanup.d
20:56
<awei>
ok, logged #1444693 fyi...
20:57gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
20:57
<vagrantc>
pretty similar to https://bugs.launchpad.net/ltsp/+bug/1316320
21:00
if they've got LDAP or some other authentication enabled, checking LDM_PASSWORD_HASH isn't enough
21:00
but it should definitely be disabled when LDM_PASSWORD_HASH=true
21:01
though the unrelated switch_user functionality should possibly stay
21:03
<alkisg_android>
user switching ends with lock screen
21:04
and it's implemented with accountsservice, which ltsp breaks
21:04
so it's broken in 2 places...
21:06
<vagrantc>
isn't there a user-switcher also accessible from drop-down menus as well?
21:06
or that's different entirely?
21:08
<alkisg_android>
normally menus are only shown if policy allows it
21:08
hidden otherwise
21:09
the menu that you say though doesn't work at all without lightdm in ubuntu
21:10
<vagrantc>
or gdm3 in debian...
21:10
at least, it used to
21:11
been some years since i've tried
21:16* alkisg_android waves
21:16alkisg_android has left IRC (alkisg_android!~yaaic@176.92.155.141, Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org)
22:31vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
22:47AlexPortable has left IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-gzjqjkkmmghioari, Quit: Connection closed for inactivity)
23:22awei has left IRC (awei!4b44c5f9@gateway/web/freenode/ip.75.68.197.249, Ping timeout: 246 seconds)
23:35adrianor1 has joined IRC (adrianor1!~adrianorg@187.115.105.77)
23:38work_alkisg has left IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr, Ping timeout: 250 seconds)
23:38izzle121 has left IRC (izzle121!~izzle121@d-206-53-82-160.cpe.metrocast.net, Ping timeout: 250 seconds)
23:38adrianorg has left IRC (adrianorg!~adrianorg@187.115.105.77, Ping timeout: 250 seconds)
23:38izzle has left IRC (izzle!~izzle121@70-90-102-229-ma-ne.hfc.comcastbusiness.net, Ping timeout: 250 seconds)
23:38telex has left IRC (telex!teletype@freeshell.de, Write error: Connection reset by peer)
23:38izzle has joined IRC (izzle!~izzle121@2601:6:1600:4c00:52e5:49ff:fec0:534b)
23:38izzle121 has joined IRC (izzle121!~izzle121@d-206-53-82-160.cpe.metrocast.net)
23:38marjus has joined IRC (marjus!marius@flage.org)
23:39zamba has left IRC (zamba!marius@flage.org, Ping timeout: 248 seconds)
23:40work_alkisg has joined IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr)
23:40telex has joined IRC (telex!teletype@freeshell.de)