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


Channel log from 8 March 2017   (all times are UTC)

00:17new__ubuntu1 has joined IRC (new__ubuntu1!Abdo@195.43.8.241)
00:20new__ubuntu has left IRC (new__ubuntu!~Abdo@156.209.169.232, Ping timeout: 260 seconds)
00:40Guest88863 has joined IRC (Guest88863!~weare@jp1.sshide.com)
00:46Guest88863 has left IRC (Guest88863!~weare@jp1.sshide.com, Remote host closed the connection)
01:16jgee has left IRC (jgee!~jgee@200.118.140.142, Remote host closed the connection)
01:31Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack)
01:54Royale_AJS has joined IRC (Royale_AJS!~Royale_AJ@108.222.210.42)
02:05Royale_AJS has left IRC (Royale_AJS!~Royale_AJ@108.222.210.42, Quit: Royale is leaving)
04:45quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: :wq)
04:46quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
05:18Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Ping timeout: 260 seconds)
05:29Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack)
05:49Statler has joined IRC (Statler!~Georg@p579FF26B.dip0.t-ipconnect.de)
06:29JayRhithu has joined IRC (JayRhithu!75f52a2c@gateway/web/freenode/ip.117.245.42.44)
06:29
<JayRhithu>
facing Issue in PiNet login... pls help
06:30
<alkisg>
!pinet
06:30
<ltsp>
I do not know about 'pinet', but I do know about these similar topics: 'paste'
06:30
<alkisg>
!raspberrypi
06:30
<ltsp>
raspberrypi: (#1) Ubuntu/LTSP on Pi 2: https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi, or (#2) Debian/LTSP (with raspbian chroot) on Pi: http://cascadia.debian.net/trenza/Documentation/raspberrypi-ltsp-howto/, or (#3) unofficial Ubuntu/LTSP (with raspbian chroot) on Pi: http://pinet.org.uk/
06:30
<JayRhithu>
ya
06:30
<alkisg>
(1) and (2) are supported here
06:30
(3) is not
06:31
Pinet is not the recommented method to netboot PIs with LTSP
06:34
<JayRhithu>
ok... i gt info from pinet.org.uk tht support will be available here... no probs... is it possible to run an application installed in Ubuntu server on a Raspberry client through LTSP? (eg: firefox)
06:34
<alkisg>
Of course it's possible
06:35
Tell pinet.org.uk that we don't support pinet here, they'll have to come again here and support it themselves if they want to :)
06:35
<JayRhithu>
ok... ok...
06:36
<alkisg>
(we helped them build it, but they didn't want to properly send it to debian/ubuntu repositories, so that's the extend of our help there :))
06:38
The other 2 methods are properly integrated into debian and ubuntu
06:38
<JayRhithu>
ok
06:40
I have server (AMD CPU, 4GB Ram, 500GB HDD, Edubuntu 14.04 (LTS-Trusty Thar), i need to create a LTSP lab with Raspberry Pi Model 2 clients.
06:42
https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi --- shall i choose this?
06:45JayRhithu has left IRC (JayRhithu!75f52a2c@gateway/web/freenode/ip.117.245.42.44, Quit: Page closed)
06:54ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:14mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
07:37ScissorHill has joined IRC (ScissorHill!~quassel@122.171.106.18)
07:37ScissorHill_ has joined IRC (ScissorHill_!~quassel@122.171.106.18)
07:41markus_e92 has left IRC (markus_e92!~markus_e9@80-121-122-53.adsl.highway.telekom.at, Ping timeout: 264 seconds)
07:43markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-22-51.adsl.highway.telekom.at)
08:37ZAJDAN has left IRC (ZAJDAN!4d30954b@gateway/web/freenode/ip.77.48.149.75, Quit: Page closed)
08:46forum has joined IRC (forum!~Icedove@212-183-98-216.adsl.highway.telekom.at)
08:56forum has left IRC (forum!~Icedove@212-183-98-216.adsl.highway.telekom.at, Quit: forum)
08:56forum has joined IRC (forum!~Icedove@212-183-98-216.adsl.highway.telekom.at)
09:17forum has left IRC (forum!~Icedove@212-183-98-216.adsl.highway.telekom.at, Ping timeout: 260 seconds)
09:46
<alkisg>
!client-list
09:46
<ltsp>
client-list: to get a list of all nbd-clients (which sometimes is the same as ltsp clients), run: netstat -tn | sed -n 's/.*:10809 *\([0-9.]*\):.*/\1/p' | sort -Vu
09:59markus_e92 has left IRC (markus_e92!~markus_e9@91-115-22-51.adsl.highway.telekom.at, Ping timeout: 256 seconds)
10:01markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-159-10.adsl.highway.telekom.at)
10:02forum has joined IRC (forum!~Icedove@212-183-98-216.adsl.highway.telekom.at)
10:37new__ubuntu has joined IRC (new__ubuntu!~Abdo@156.208.182.168)
10:37new__ubuntu1 has left IRC (new__ubuntu1!Abdo@195.43.8.241, Read error: Connection reset by peer)
10:41new__ubuntu has left IRC (new__ubuntu!~Abdo@156.208.182.168, Read error: Connection reset by peer)
10:41new__ubuntu has joined IRC (new__ubuntu!Abdo@195.43.8.241)
11:24Statler has left IRC (Statler!~Georg@p579FF26B.dip0.t-ipconnect.de, Remote host closed the connection)
11:26
<new__ubuntu>
is it a must to use ubuntu mate for ltsp?
11:26
what is the features in ubuntu mate to makes it preferable? for ltsp
11:50Statler has joined IRC (Statler!~Georg@mail.lohn24.de)
11:51Statler has left IRC (Statler!~Georg@mail.lohn24.de, Remote host closed the connection)
11:53Statler has joined IRC (Statler!~Georg@mail.lohn24.de)
12:26JayRhithu has joined IRC (JayRhithu!75f52a2c@gateway/web/freenode/ip.117.245.42.44)
12:27
<new__ubuntu>
h all
12:27
comparing italc and epoptes
12:27
had any one tried it before?
12:28
<JayRhithu>
hi alkisg, Raspi-LTSP server installed and sd card image file created but RPi stucks with "/bin/sh: can't access tty; job control turned off" (initramfs)
12:28
pls help..
12:34forum has left IRC (forum!~Icedove@212-183-98-216.adsl.highway.telekom.at, Ping timeout: 240 seconds)
12:35JayRhithu has left IRC (JayRhithu!75f52a2c@gateway/web/freenode/ip.117.245.42.44)
12:45ZAJDAN has joined IRC (ZAJDAN!4d30954b@gateway/web/freenode/ip.77.48.149.75)
12:56
<vlt>
new__ubuntu: In general MATE seems to be more leightweight than some other environments which makes it suitable for terminals.
12:57new__ubuntu has left IRC (new__ubuntu!Abdo@195.43.8.241, Quit: Leaving)
13:12adrianorg has left IRC (adrianorg!~adrianorg@177.18.98.87, Ping timeout: 260 seconds)
13:13adrianorg has joined IRC (adrianorg!~adrianorg@177.18.98.87)
13:24
<ZAJDAN>
vlt: since I use linux I always used Gnome2...same opinion..is fast, minimalistic and nevertheless strong
13:25
I never seen better applet than in Gnome2 -symbol Map......everywhere else it is terrible
13:26
and Thanks to MATE we can use legendary Gnome2 :_)
13:30
<vlt>
For some reason I can't Alt+Tab to more than one other program anymore on Ubuntu 16.04 MATE. It drives me crazy.
13:32ScissorHill_ has left IRC (ScissorHill_!~quassel@122.171.106.18, Remote host closed the connection)
13:32ScissorHill has left IRC (ScissorHill!~quassel@122.171.106.18, Read error: Connection reset by peer)
13:37
<ZAJDAN>
On ubuntu I do not know, but on debian it is ok
13:59ScissorHill has joined IRC (ScissorHill!~quassel@122.171.106.18)
13:59ScissorHill_ has joined IRC (ScissorHill_!~quassel@122.171.106.18)
14:07
<alkisg>
vlt, does it happen for all users, new users, guests etc, or just you?
14:07
Or are you talking for inside vnc/rdp?
14:11
<vlt>
All users (including new ones). We are connected via xrdp, yes.
14:12
Many other key combination work (ctrl-shift-left, ...-right, AltGr+e for €, ...+q for @).
14:13
But some don#t.
14:13
<alkisg>
OK then it's not certain that it's a mate issue, it might be a combination of software interacting with each other
14:14
E.g. when multiple sources try to handle the keyboard repeat, they fight with each other
14:14
In x11vnc there are heuristics to bypass that because there's no proper API to do it
14:14
<vlt>
I'll try to verify that in remote X mode.
14:14
<alkisg>
First verify that it doesn't happen locally :
14:14
<vlt>
Another problem: Any idea how to make the screensaver work when running MATE desktop in an xrdp/xvnc session?
14:15
alkisg: Locally? How?
14:15
<alkisg>
Log in to the server, or to a worstation, or to an ltsp fat client
14:15
Anywhere where mate doesn't run remotely
14:17
<vlt>
On Ubuntu 12.04 I had MATE running in Xvnc sessions without any key stroke problems. Now on 16.04 it's hard to even get mate-session running in a pure Xvnc session (without xrdp's sesman).
14:17
I'll do some tests and report back.
14:17
alkisg: Any idea about the screensaver/lock?
14:17forum has joined IRC (forum!~Icedove@212-183-98-216.adsl.highway.telekom.at)
14:18
<alkisg>
I think that's because remote sessions don't properly notify accountsservice about the login session, and the screensaver asks that accountsservice API
14:18
So the fix would be in xvnc/xrdp, not in mate
14:19
(in their "new session" handlers
14:19
Well, or in accountsservice
14:19
The problem with ltsp fat clients getting a screensaver when they don't have a password set though, that's a mate issue :D
14:24forum has left IRC (forum!~Icedove@212-183-98-216.adsl.highway.telekom.at, Ping timeout: 240 seconds)
14:50
<ZAJDAN>
did anybody try LTSP on Slackware?
14:55ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
15:01
<alkisg>
ZAJDAN: you can't just try ltsp on different distributions, you have to implement it, maintain it there
15:02
New code should be added, bugs should be fixed etc, it's not a job for users but for developers
15:02
Hopefully now with ltsp-pnp that task will be a lot easier, but he still have a lot of ltsp5 legacy to keep up with
15:03
At some point there was an ltsp maintainer for gentoo. I don't think any developer has worked on supporting ltsp on slackware...
15:05
<ZAJDAN>
Centos is maintained about LTSP?
15:06
<alkisg>
There was a guy many years ago that supported ltsp on fedora and hence centos, and made k12linux etc
15:07
I don't think it's maintained in at least the last 5 years
15:08
<ZAJDAN>
anyway the best is Debian :)
15:08
<alkisg>
Debian and Ubuntu have good support for LTSP, yes. Choosing between them is a matter of other priorities, not LTSP.
15:13
<ZAJDAN>
is somehow possible create in LTSP boot menu which will offer boot 'instant system'(default LTSB) and installation image of some Linux distros
15:13
should I read about syslinux?
15:13
<alkisg>
Yes, but it's not related to LTSP, it's a standard multiboot menu
15:13
Yes
15:13
LTSP has support for a menu, but you need more than that
15:14
<ZAJDAN>
for diskless station the menu will come from LTSP server
15:15
when I do not want to use floppy or CD
15:15
<alkisg>
Yes, but it won't be the ltsp menu, it will be a pxelinux menu that comes from "a server"
15:15
<ZAJDAN>
so from this reason I am interested how to make in LTSP
15:15
<alkisg>
The fact that you're also using ltsp is not too related
15:16
Read about pxelinux menus
15:16
<ZAJDAN>
ok...thnx for the info
15:16
<alkisg>
np
15:42lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Ping timeout: 256 seconds)
16:05mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
16:19adrianor1 has joined IRC (adrianor1!~adrianorg@186.213.152.139)
16:21adrianorg has left IRC (adrianorg!~adrianorg@177.18.98.87, Ping timeout: 240 seconds)
16:28markus_e92 has left IRC (markus_e92!~markus_e9@91-115-159-10.adsl.highway.telekom.at, Ping timeout: 240 seconds)
16:29ScissorHill_ has left IRC (ScissorHill_!~quassel@122.171.106.18, Remote host closed the connection)
16:29ScissorHill has left IRC (ScissorHill!~quassel@122.171.106.18, Remote host closed the connection)
16:30markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-159-175.adsl.highway.telekom.at)
16:48forum has joined IRC (forum!~Icedove@212-183-98-216.adsl.highway.telekom.at)
17:22ZAJDAN has left IRC (ZAJDAN!4d30954b@gateway/web/freenode/ip.77.48.149.75, Ping timeout: 260 seconds)
18:08markus_e92 has left IRC (markus_e92!~markus_e9@91-115-159-175.adsl.highway.telekom.at, Ping timeout: 268 seconds)
18:18sbalneav has left IRC (sbalneav!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.mtsallstream.net, Quit: WeeChat 1.0.1)
18:19sbalneav has joined IRC (sbalneav!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.mtsallstream.net)
18:23sbalneav has left IRC (sbalneav!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.mtsallstream.net, Client Quit)
18:24sbalneav has joined IRC (sbalneav!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.mtsallstream.net)
18:27sbalneav has left IRC (sbalneav!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.mtsallstream.net, Client Quit)
18:29sbalneav has joined IRC (sbalneav!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.mtsallstream.net)
18:37sbalneav has left IRC (sbalneav!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.mtsallstream.net, Quit: WeeChat 1.0.1)
18:38sbalneav has joined IRC (sbalneav!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.mtsallstream.net)
19:04lucascastro has joined IRC (lucascastro!~lucas@186.227.186.18)
19:17hima has joined IRC (hima!~hima@41.35.173.200)
19:18
<hima>
hi all
19:18
when i run ipconfig
19:18
on my server terminal
19:18
it did not show any network interfaces except local ine
19:18
lo
19:34Statler has left IRC (Statler!~Georg@mail.lohn24.de, Remote host closed the connection)
19:51tarzeau has left IRC (tarzeau!~alex@mail.aiei.ch, Ping timeout: 240 seconds)
19:54
<||cw>
hima: on the server itself? you do need to make your server OS install work on the lan before even starting to configure ltsp
19:55
<hima>
i solved
19:55
by stoping Network manager
19:55
and start it again
20:03Statler has joined IRC (Statler!~Georg@p579FF26B.dip0.t-ipconnect.de)
20:03vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
20:16forum has left IRC (forum!~Icedove@212-183-98-216.adsl.highway.telekom.at, Quit: forum)
20:28hima has left IRC (hima!~hima@41.35.173.200, Quit: Leaving)
20:48Statler has left IRC (Statler!~Georg@p579FF26B.dip0.t-ipconnect.de, Remote host closed the connection)
20:49ZAJDAN has joined IRC (ZAJDAN!4d30954b@gateway/web/freenode/ip.77.48.149.75)
21:06sbalneav has left IRC (sbalneav!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.mtsallstream.net, Quit: WeeChat 1.0.1)
21:07sbalneav has joined IRC (sbalneav!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.mtsallstream.net)
21:08* vagrantc waves to sbalneav
21:09
<sbalneav>
Hey vagrantc
21:23
<ZAJDAN>
hi vagrant.....yesterday we spoke about the Debian bugreport...today I had plan simulate the problem
21:23
but I am not sure which package I should to report
21:24
probably I will try to check out what is in dmesg, /var/log/syslog * errorlog
21:25
where you recommend take the info for the report?
21:26
<vagrantc>
ZAJDAN: the failure to boot issue?
21:26
er, failure to reboot
21:27
or failure to poweroff?
21:27
ZAJDAN: probably ltsp-client for starters, we can always reassign later
21:27
ZAJDAN: are you using without a chroot (e.g. ltsp-pnp style?)
21:28
<ZAJDAN>
from epoptes reboot Thin Client and shutdown also
21:29
yes pnp, but on Debian 8 it works nice(without problem) just with debian 9 is the problem
21:29
<vagrantc>
right
21:29
my guess is it's a problem even when not using epoptes
21:29
<alkisg>
ZAJDAN: it's best to involve as few applications as possible; so instead of using epoptes to shutdown, just try to shutdown from LDM. If it happens from there as well, it's not an epoptes issue and the persons that will look at that bug report won't have to bother about that
21:30
Usual suspects are: nbd-client/nbd-disconnect, systemd, and ifupdown
21:30
<vagrantc>
ZAJDAN: but i'd rather have the bug report to begin the conversation than attempting to get it perfect
21:30
<ZAJDAN>
ok..sounds logic..will try
21:30
<vagrantc>
it's easy to reassign bugs, clone them, etc. as appropriate
21:31
<ZAJDAN>
shutdown from LDM?
21:31
<vagrantc>
the login screen
21:32
<ZAJDAN>
but in this case I hace to set off autologin in lts.conf...yes?
21:33
to get login screen on client station
21:34
<alkisg>
Yes
21:35
<ZAJDAN>
ahh I could do switch user and maybe will appears login window
21:35
<vagrantc>
no
21:35
could also try shutdown from within session
21:36
<alkisg>
If it's a fat client...
21:36
<vagrantc>
could also open a root shell and run poweroff with some arguments
21:36
<ZAJDAN>
thin client do the problem
21:36
<vagrantc>
or if you're using lxde :)
21:36
<alkisg>
ZAJDAN: fat clients poweroff properly?!
21:36
<vagrantc>
fat clients are fine?
21:38
i think ubuntu saw this problem first, and then in some recent update, debian started seeing it
21:38
<ZAJDAN>
I remember that yes, but I will boot one station now to we could see
21:38* vagrantc suspects when NBD switched to using systemd natively or something
21:40
<alkisg>
I think the last time I checked that issue, the best solution was to write systemd units for ltsp
21:40
Now that ubuntu 12.04 won't be supported anymore, it'll be a good time to move to systemd... :D
21:41
<vagrantc>
oh boy, break new world/flamefest
21:41
brave new...
21:43
<ZAJDAN>
Debian9-newly booted Thin client - from login screen -> reboot --->frozen with LDM background(without inputs, icons,etc)
21:44
<alkisg>
Thin clients are no different to fat clients at LDM
21:44
The difference is after login
21:44
But do try with a fat client too...
21:45
<ZAJDAN>
same problem FAT clients just difference(LDM background, input, icons..still displayed ) but all frozen
21:45
<alkisg>
You can also specify SCREEN_07=shell in lts.conf, and run `poweroff` at that shell, so that you see systemd messages on screen
21:45
Also, make sure that you don't have anything in rc.local
21:45
<ZAJDAN>
rc.local is default
21:46
<alkisg>
(like RCFILE_xx in lts.conf)
21:47
<ZAJDAN>
ok should I try SCREEN_07=shell ...?
21:47
erka
21:47
<alkisg>
I think it's better, eys
21:47
yes
21:47
<ZAJDAN>
to see the otput from systemd
21:47
ok...will try
21:49
thin boy is booting now
21:49
is up...now I will try reboot from LDM
21:50
<alkisg>
If you have SCREEN_07=shell, there shouldn't be any LDM at all
21:51
Just a command line to run `poweroff` from
21:51
<ZAJDAN>
tru
21:51* alkisg waves, good night all...
21:51
<ZAJDAN>
just terminal...so I rebooted from the terminal and reboot was successfully done
21:52
so can we say that the problem is LDM?
21:59
<vagrantc>
huh
21:59
if that's the case, then probably some desktop environment is holding some file descriptor open
22:00
but if from LDM it still fails... hmmm... that's strange.
22:00
LDM shouldn't really be any different than SCREEN_07=shell
22:01
ZAJDAN: you might want to do a few repeated attempts, just in case it's a race condition that only works/fails some of the time
22:04GodFather has joined IRC (GodFather!~rcc@2600:100d:b125:4884:fd7d:2384:4197:6f21)
22:07
<ZAJDAN>
vargrantc: from LDM?
22:09
<vagrantc>
ZAJDAN: from shell too
22:09
e.g. you had one success... but 1 attempt isn't much
22:10
<ZAJDAN>
ok
22:11
<vagrantc>
ZAJDAN: in the end, file a bug on one of ldm or ltsp-client with the information you have available... and we'll go from there :)
22:12
<ZAJDAN>
FAT client - when LDM - I login ..then from menu..LogOut...from login screen reboot - successfully
22:15
again FAT client -> login from LDM....from menu LogOut -> login screen -> reboot - successfully
22:16
again in same way - successfully
22:17
<vagrantc>
now i'd be curious to see the same from a thin client
22:18
<ZAJDAN>
3x login from LDM(login screen) - user completely loged - > menu ->LogOut -> login screen -> reboot ---> successfully
22:20
when I boot up the FAT client ..stay in LDM login screen -> reboot - client frozen
22:20
now I will try with Thin
22:22
result about the FAT: I have to be completely loged into MATE enviroment...then is possible reboot
22:24
Think client? problem in both cases
22:25
Thin
22:26
ha!
22:27
I let the Thin client fozen and after cca 3 minutes....rebooted itself
22:28ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:41
<vagrantc>
ok... that sounds more likely an issue with ltsp-client/nbd interaction
23:25GodFather has left IRC (GodFather!~rcc@2600:100d:b125:4884:fd7d:2384:4197:6f21, Read error: Connection reset by peer)
23:30url_work has joined IRC (url_work!~url_work@220.128.110.82)
23:33lurky_work has left IRC (lurky_work!~url_work@220-128-110-82.HINET-IP.hinet.net, Ping timeout: 260 seconds)