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


Channel log from 4 March 2018   (all times are UTC)

00:32Statler|Home has left IRC (Statler|Home!~Georg@p54897308.dip0.t-ipconnect.de, Remote host closed the connection)
01:33SmashK has left IRC (SmashK!5b40100b@gateway/web/freenode/ip.91.64.16.11, Ping timeout: 260 seconds)
05:09GodFather has left IRC (GodFather!~rcc@wsip-24-249-172-218.ph.ph.cox.net, Quit: Ex-Chat)
05:09GodFather has joined IRC (GodFather!~rcc@wsip-24-249-172-218.ph.ph.cox.net)
05:14GodFather has left IRC (GodFather!~rcc@wsip-24-249-172-218.ph.ph.cox.net, Ping timeout: 256 seconds)
05:16GodFather has joined IRC (GodFather!~rcc@wsip-24-249-172-218.ph.ph.cox.net)
05:22GodFather has left IRC (GodFather!~rcc@wsip-24-249-172-218.ph.ph.cox.net, Ping timeout: 256 seconds)
06:44alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
08:15ricotz has joined IRC (ricotz!~ricotz@p5B2A9FF3.dip0.t-ipconnect.de)
08:15ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
09:20Statler|Home has joined IRC (Statler|Home!~Georg@p5B30E34D.dip0.t-ipconnect.de)
10:12jp_ has joined IRC (jp_!7aac47af@gateway/web/freenode/ip.122.172.71.175)
10:13
<jp_>
Hi Alkis
10:14
I am finally able to get the logon screen show up on the client (raspberyy pi) terminal, but now, after I try to login, the screen comes back again to the login screen.
10:17
In syslog, I get this error : GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
10:18
and then : Failed to connect to Mir: Failed to connect to server socket: No such file or directory
10:19
Does anyone here know how to fix this issue ? Would be very helpful ...
10:28kjackal has joined IRC (kjackal!~quassel@109-74-56-122.static.acetelecom.hu)
10:32
<alkisg>
!vnc-edide | echo jp_:
10:32
<ltsp>
jp_: vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
10:46
<jp_>
ok
10:51
shared ...
10:58
<alkisg>
jp_: I didn't see anything
10:58
Where's the client? No epoptes client?
11:03
OK reboot the client now
11:14
jp_: try to login again
11:14
directly on the client
11:14
<jp_>
ok
11:16kjackal has left IRC (kjackal!~quassel@109-74-56-122.static.acetelecom.hu, Ping timeout: 276 seconds)
11:23
<alkisg>
jp_: hehe, notes are a problem when you're using IRC :D
11:23
Chat here or in a private IRC window
11:23
Yes, if the client is behind NAT, it can't do LDM_DIRECTX
11:25
So now with LDM_DIRECTX=False, the xterm session works
11:25
On the other hand, the gnome and kde sessions will be much harder because they don't work for thin clients
11:25
That's why mate is recommended
11:26
You could create a "fat chroot" and run the rpi in fat client mode, which means of course that things may become slow...
11:27
You can either work with changing the LAN setting and LDM_DIRECTX=True (faster), or using LDM_DIRECTX=False as it is now (slower)
11:27
<jp_>
ok, so, if I use the fat chroot, then it the "behind the NAT" issue won't be there ?
11:27
<alkisg>
With a fat chroot you'll be able to use kde and gnome. But no ltsp developer is using those, so they're not very tested
11:28
E.g. I've heard that KDE is causing hundreds of MB of cache on each ltsp login
11:29
<jp_>
ok then, let me change the setup to a LAN-LAN type and then try again
11:29
<alkisg>
Remember you'll also need to upgrade the chroot to fat
11:31
<jp_>
chroot to fat ? But I thought if I want to run using thin-client, then all I need to do is make my kubunto be able to ping the raspberry (LAN to LAN, instead of LAN to WAN), and then change LDM_DIRECTX to 'True'
11:31
Or, did I miss something ?
11:31
<alkisg>
Yes you missed it
11:32
KDE and Gnome don't run in thin mode
11:32
(without a lot of effort)
11:32
<jp_>
:-))
11:32
<alkisg>
(01:25:43 μμ) alkisg: On the other hand, the gnome and kde sessions will be much harder because they don't work for thin clients
11:32
(01:25:49 μμ) alkisg: That's why mate is recommended
11:33
KDE might work more easily because it also supports non opengl logins
11:33
But I haven't used KDE in ages, so I don't know the specifics
11:33SmashK has joined IRC (SmashK!5b40100b@gateway/web/freenode/ip.91.64.16.11)
11:33
<jp_>
so, what you suggest is :
11:34
1. change to LAN to LAN
11:35
2. Run the steps as in : "Converting the thin chroot to a fat chroot" as in (https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi)
11:36
3. set : LDM_DIRECTX=True
11:36
4. Voila ! (?)
11:39
<alkisg>
Yes, although LDM_DIRECTX doesn't matter for fat chroots
11:39
And, (5) use mate
11:41
<SmashK>
hi
11:41
add-apt-repository ppa:ts.sch.gr; apt update does not work anymore
11:44
<alkisg>
In which distro/version? Paste the whole output to pastebin
11:46
<SmashK>
debian 9.3-i386
11:48SmashK2 has joined IRC (SmashK2!5b40100b@gateway/web/freenode/ip.91.64.16.11)
11:48
<SmashK2>
add-apt-repository: command not found...
11:49
<alkisg>
Yes, this command is for ubuntu
11:49
Not for debian
11:49
And this repository too
11:50
<SmashK2>
got it done in the old amd64 LTSP-server with that, too
11:50
but I remember to do something to use this command before
11:51
apt-get install python-software-properties
11:53
is obsolete, must be: apt-get install software-properties-common
11:55
then I can install ltsp-manager
11:55
<alkisg>
that repository contains ubuntu packagds
11:55
*packages
11:55
for debian, use debian experimental
11:55
it says so in the wiki
11:55
<SmashK>
where?
11:56
do you have a link?
11:58
<alkisg>
!ltsp-manager
11:58
<ltsp>
ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
11:58
<alkisg>
http://wiki.ltsp.org/wiki/Ltsp-manager/Installation => Currently, LTSP Manager is only available in Debian Experimental and in Ubuntu 16.04 via the Greek schools PPA. If you're using Ubuntu, to add the PPA to your sources, run:
11:59
You're not using Ubuntu, don't add the ppa
11:59
Use debian experimental sources
12:00
https://packages.debian.org/search?keywords=ltsp-manager and https://wiki.debian.org/DebianExperimental
12:05jp_ has left IRC (jp_!7aac47af@gateway/web/freenode/ip.122.172.71.175)
12:21
<SmashK2>
question beside of ltsp: node won't start with that i386-arch
12:21
8254 is not connected to IO-APIC
12:21
<alkisg>
Do you mean that debian doesn't start on a client of yours? Why not ask in #debian?
12:22
You can also test with a live usb if you suspect hardware error
12:24
<SmashK2>
yep, that node (old server) does not start that Debian 9.3-i386
12:24
where to find that #Debian?
12:25
<alkisg>
Type this: /join #debian
12:25
It's an IRC channel.
12:39adrianorg has left IRC (adrianorg!~adrianorg@179.187.31.214.dynamic.adsl.gvt.net.br, Ping timeout: 276 seconds)
12:39adrianorg has joined IRC (adrianorg!~adrianorg@179.187.31.214.dynamic.adsl.gvt.net.br)
13:44kjackal has joined IRC (kjackal!~quassel@109-74-56-122.static.acetelecom.hu)
13:57Hyperbyte has joined IRC (Hyperbyte!~jan@middelkoop.cc)
13:57Hyperbyt1 has left IRC (Hyperbyt1!~jan@middelkoop.cc, Quit: leaving)
14:11kjackal has left IRC (kjackal!~quassel@109-74-56-122.static.acetelecom.hu, Ping timeout: 256 seconds)
17:08lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
17:30jp_ has joined IRC (jp_!7aac657d@gateway/web/freenode/ip.122.172.101.125)
17:31
<jp_>
Hi Alkis. So, finally it works with the thin client (but very very slow) :-(
17:32
I didn't setup the fat client yet. So using the Kubuntu thin client itself.
17:34
I had to add a small entry in lts.conf (LDM_SESSION="plasma") to get the KDE running on the client.
17:36
Thanks for all the help Alkis. Will try out with the fat client later and see if it makes things better.
17:47
At the moment, it seems like working on a pre-historic machine ... :-)
17:50jp_ has left IRC (jp_!7aac657d@gateway/web/freenode/ip.122.172.101.125, Quit: Page closed)
19:03SmashK2 has left IRC (SmashK2!5b40100b@gateway/web/freenode/ip.91.64.16.11, Ping timeout: 260 seconds)
19:12mmarconm has joined IRC (mmarconm!~mmarconm@unaffiliated/mmarconm)
19:24mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Quit: Leaving)
19:57vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
21:52
<Nitrigaur>
alkisg, I have followed your advice and installed x2go server and client. I'm about to test it. thanks again :-)
22:02SmashK has left IRC (SmashK!5b40100b@gateway/web/freenode/ip.91.64.16.11, Quit: Page closed)
22:10lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Ping timeout: 245 seconds)
22:44
<Nitrigaur>
alkisg, works fine locally on a VM. Tomorrow for the big test on the institute network :-)
23:03ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
23:25Statler|Home has left IRC (Statler|Home!~Georg@p5B30E34D.dip0.t-ipconnect.de, Remote host closed the connection)
23:39
<Nitrigaur>
\q
23:39Nitrigaur has left IRC (Nitrigaur!~Nitrigaur@2001:982:2365:1:1e1b:dff:fe66:454a)
23:49GodFather has joined IRC (GodFather!~rcc@104.193.100.52)