|00:32||Statler|Home has left IRC (Statler|Home!~Georg@p54897308.dip0.t-ipconnect.de, Remote host closed the connection)|
|01:33||SmashK has left IRC (SmashK!5b40100b@gateway/web/freenode/ip.188.8.131.52, Ping timeout: 260 seconds)|
|05:09||GodFather has left IRC (GodFatheremail@example.com, Quit: Ex-Chat)|
|05:09||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|05:14||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 256 seconds)|
|05:16||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|05:22||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 256 seconds)|
|06:44||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
|08:15||ricotz has joined IRC (ricotz!~ricotz@p5B2A9FF3.dip0.t-ipconnect.de)|
|08:15||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|09:20||Statler|Home has joined IRC (Statler|Home!~Georg@p5B30E34D.dip0.t-ipconnect.de)|
|10:12||jp_ has joined IRC (jp_!7aac47af@gateway/web/freenode/ip.184.108.40.206)|
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.
In syslog, I get this error : GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
and then : Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Does anyone here know how to fix this issue ? Would be very helpful ...
|10:28||kjackal has joined IRC (firstname.lastname@example.org)|
!vnc-edide | echo jp_:
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
jp_: I didn't see anything
Where's the client? No epoptes client?
OK reboot the client now
jp_: try to login again
directly on the client
|11:16||kjackal has left IRC (email@example.com, Ping timeout: 276 seconds)|
jp_: hehe, notes are a problem when you're using IRC :D
Chat here or in a private IRC window
Yes, if the client is behind NAT, it can't do LDM_DIRECTX
So now with LDM_DIRECTX=False, the xterm session works
On the other hand, the gnome and kde sessions will be much harder because they don't work for thin clients
That's why mate is recommended
You could create a "fat chroot" and run the rpi in fat client mode, which means of course that things may become slow...
You can either work with changing the LAN setting and LDM_DIRECTX=True (faster), or using LDM_DIRECTX=False as it is now (slower)
ok, so, if I use the fat chroot, then it the "behind the NAT" issue won't be there ?
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
E.g. I've heard that KDE is causing hundreds of MB of cache on each ltsp login
ok then, let me change the setup to a LAN-LAN type and then try again
Remember you'll also need to upgrade the chroot to fat
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'
Or, did I miss something ?
Yes you missed it
KDE and Gnome don't run in thin mode
(without a lot of effort)
(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
(01:25:49 μμ) alkisg: That's why mate is recommended
KDE might work more easily because it also supports non opengl logins
But I haven't used KDE in ages, so I don't know the specifics
|11:33||SmashK has joined IRC (SmashK!5b40100b@gateway/web/freenode/ip.220.127.116.11)|
so, what you suggest is :
1. change to LAN to LAN
2. Run the steps as in : "Converting the thin chroot to a fat chroot" as in (https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi)
3. set : LDM_DIRECTX=True
4. Voila ! (?)
Yes, although LDM_DIRECTX doesn't matter for fat chroots
And, (5) use mate
add-apt-repository ppa:ts.sch.gr; apt update does not work anymore
In which distro/version? Paste the whole output to pastebin
|11:48||SmashK2 has joined IRC (SmashK2!5b40100b@gateway/web/freenode/ip.18.104.22.168)|
add-apt-repository: command not found...
Yes, this command is for ubuntu
Not for debian
And this repository too
got it done in the old amd64 LTSP-server with that, too
but I remember to do something to use this command before
apt-get install python-software-properties
is obsolete, must be: apt-get install software-properties-common
then I can install ltsp-manager
that repository contains ubuntu packagds
for debian, use debian experimental
it says so in the wiki
do you have a link?
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
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:
You're not using Ubuntu, don't add the ppa
Use debian experimental sources
https://packages.debian.org/search?keywords=ltsp-manager and https://wiki.debian.org/DebianExperimental
|12:05||jp_ has left IRC (jp_!7aac47af@gateway/web/freenode/ip.22.214.171.124)|
question beside of ltsp: node won't start with that i386-arch
8254 is not connected to IO-APIC
Do you mean that debian doesn't start on a client of yours? Why not ask in #debian?
You can also test with a live usb if you suspect hardware error
yep, that node (old server) does not start that Debian 9.3-i386
where to find that #Debian?
Type this: /join #debian
It's an IRC channel.
|12:39||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 276 seconds)|
|12:39||adrianorg has joined IRC (email@example.com)|
|13:44||kjackal has joined IRC (firstname.lastname@example.org)|
|13:57||Hyperbyte has joined IRC (Hyperbyteemail@example.com)|
|13:57||Hyperbyt1 has left IRC (Hyperbyt1firstname.lastname@example.org, Quit: leaving)|
|14:11||kjackal has left IRC (email@example.com, Ping timeout: 256 seconds)|
|17:08||lucascastro has joined IRC (firstname.lastname@example.org)|
|17:30||jp_ has joined IRC (jp_!7aac657d@gateway/web/freenode/ip.126.96.36.199)|
Hi Alkis. So, finally it works with the thin client (but very very slow) :-(
I didn't setup the fat client yet. So using the Kubuntu thin client itself.
I had to add a small entry in lts.conf (LDM_SESSION="plasma") to get the KDE running on the client.
Thanks for all the help Alkis. Will try out with the fat client later and see if it makes things better.
At the moment, it seems like working on a pre-historic machine ... :-)
|17:50||jp_ has left IRC (jp_!7aac657d@gateway/web/freenode/ip.188.8.131.52, Quit: Page closed)|
|19:03||SmashK2 has left IRC (SmashK2!5b40100b@gateway/web/freenode/ip.184.108.40.206, Ping timeout: 260 seconds)|
|19:12||mmarconm has joined IRC (mmarconm!~mmarconm@unaffiliated/mmarconm)|
|19:24||mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Quit: Leaving)|
|19:57||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
alkisg, I have followed your advice and installed x2go server and client. I'm about to test it. thanks again :-)
|22:02||SmashK has left IRC (SmashK!5b40100b@gateway/web/freenode/ip.220.127.116.11, Quit: Page closed)|
|22:10||lucascastro has left IRC (email@example.com, Ping timeout: 245 seconds)|
alkisg, works fine locally on a VM. Tomorrow for the big test on the institute network :-)
|23:03||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|23:25||Statler|Home has left IRC (Statler|Home!~Georg@p5B30E34D.dip0.t-ipconnect.de, Remote host closed the connection)|
|23:39||Nitrigaur has left IRC (Nitrigaur!~Nitrigaur@2001:982:2365:1:1e1b:dff:fe66:454a)|
|23:49||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|