02:22 | spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Ping timeout: 245 seconds) | |
03:18 | jgee has left IRC (jgee!~jgee@190.159.118.121, Ping timeout: 244 seconds) | |
03:20 | jgee has joined IRC (jgee!~jgee@190.159.118.121) | |
05:14 | pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 244 seconds) | |
05:23 | pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme) | |
05:54 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
06:30 | kjackal has joined IRC (kjackal!~quassel@ppp-94-66-223-164.home.otenet.gr) | |
07:35 | statler has joined IRC (statler!~Georg@gwrz3.lohn24.de) | |
08:02 | ZAJDAN has left IRC (ZAJDAN!~zdenek@77.48.149.75, Read error: Connection reset by peer) | |
08:07 | Basinator has joined IRC (Basinator!511476ce@gateway/web/freenode/ip.81.20.118.206) | |
08:08 | <Basinator> Not *strictly* a bug, but at least on ubuntu (and maybe some other distros) after installing LTSP and connecting with a client
| |
08:08 | the message "Authentification is required to create a color managing device", asking for root pw when logging in as non-root user
| |
08:08 | creating sudo nano /etc/polkit-1/localauthority/50-local.d/color.pkla
| |
08:08 | [Allow colord for all users] Identity=unix-user:* Action=org.freedesktop.color-manager.create-device;org.freedesktop.color-manager.create-profile;org.freedesktop.color-manager.delete-device;org.freedesktop.color-manager.delete-profile;org.freedesktop.color-manager.modify-device;org.freedesktop.color-manager.modify-profile ResultAny=yes ResultInactive=yes ResultActive=yes
| |
08:08 | will fix this
| |
08:09 | maybe you want/can add that to LTSP on post-installation triggers?
| |
08:09 | Just a thought, and wanted to let you know about this.
| |
08:36 | <alkisg> Basinator: that's for thin clients , right?
| |
08:37 | The next ltsp won't support thin clients at all
| |
08:37 | !fatclients
| |
08:37 | <ltsp`> fatclients: Nowadays LTSP supports thin and fat clients. They are both diskless and netbooted from the same LTSP chroot, but while thin clients run the session on the server and transfer the screen, fat clients run the session locally with their own CPU/RAM, thus performing amazingly better. See also !ltsp-pnp and https://help.ubuntu.com/community/UbuntuLTSP/FatClients
| |
08:38 | <Basinator> aye
| |
08:39 | That's bad news for me though.
| |
08:52 | <alkisg> How so? You could use x2go or xfreerdp for "thin clients"
| |
08:52 | I.e. boot over LTSP, then connect with x2go/xfreerdp
| |
08:52 | <Basinator> For us, we use LTSP to provide computer resources for low spec clients which only need something like a browser or office
| |
08:52 | I just worked myself into LTSP, lol.
| |
08:52 | <alkisg> How "low spec"? CPU/RAM?
| |
08:52 | <Basinator> Would it be an issue to leave the functionality for thin clients in future updates?
| |
08:53 | aye
| |
08:53 | <alkisg> I mean, mention the specific cpu and ram for a client
| |
08:53 | <highvoltage> thin clients won't be inherintly impossible on ltsp6 itself, you would still be able to make some kind of rdp (or whatever session)
| |
08:53 | the problem is more with how all the other upstream software has changed
| |
08:56 | <alkisg> Thin clients were based on XDMCP or `ssh -X`, with wayland that isn't an option anymore. So using one of the other remote desktop apps, even if you netboot clients with LTSP, is a sensible choice
| |
10:13 | kjackal has left IRC (kjackal!~quassel@ppp-94-66-223-164.home.otenet.gr, Ping timeout: 250 seconds) | |
10:48 | kjackal has joined IRC (kjackal!~quassel@2a02:587:9a0a:1100:d97d:a226:af4d:1270) | |
11:29 | <Basinator> Sounds like that in the end I will have no choice but to have to work into the other software solutions then?
| |
11:32 | <highvoltage> yeah XDMCP and ssh -x will become increasingly unusable
| |
11:33 | <Basinator> Wait. I was aware of Wayland getting developed, but I didnt expect Xorg to basically die out? ._.
| |
11:39 | <highvoltage> it's not just that, also the way that applications use xorg that changed. like, in the old days you could run gnome+compiz and all your vectors would be sent over the network and rendered locally on the thin client. which was efficient and fast. that's not possible in gnome 3 anymore.
| |
11:51 | Faith has joined IRC (Faith!~Paty_@unaffiliated/faith) | |
12:51 | <alkisg> Basinator: you didn't answer though, which CPU and how much RAM do your clients have?
| |
12:51 | Because if they're 32bit, you'll also have issues finding any distro that will support them
| |
12:52 | And if they're 64bit... well, maybe you should be running them as fat clients instead
| |
13:54 | spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut) | |
14:08 | <Basinator> It is for a customer so not sure about that. I think the clients are 32-bit, but would have to ask for confirmation a work mate.
| |
14:08 | Also, afk freetime now, it is beer o' clock.
| |
14:08 | <alkisg> Basinator: well, thin clients die at the same time when distros give up on 32bit, so it's symmetrical :)
| |
14:09 | Have a nice...beer :)
| |
14:10 | Basinator has left IRC (Basinator!511476ce@gateway/web/freenode/ip.81.20.118.206, Quit: Page closed) | |
15:25 | josefig1 has left IRC (josefig1!~josefig@unaffiliated/josefig, Quit: Ping timeout (120 seconds)) | |
15:25 | josefig1 has joined IRC (josefig1!~josefig@unaffiliated/josefig) | |
15:29 | ricotz_ has joined IRC (ricotz_!~ricotz@ubuntu/member/ricotz) | |
15:29 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Ping timeout: 255 seconds) | |
15:33 | kjackal has left IRC (kjackal!~quassel@2a02:587:9a0a:1100:d97d:a226:af4d:1270, Ping timeout: 276 seconds) | |
15:34 | ricotz__ has joined IRC (ricotz__!~ricotz@p5B2A8B34.dip0.t-ipconnect.de) | |
15:38 | ricotz_ has left IRC (ricotz_!~ricotz@ubuntu/member/ricotz, Ping timeout: 255 seconds) | |
15:59 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
17:01 | woernie has joined IRC (woernie!~werner@p50867386.dip0.t-ipconnect.de) | |
17:12 | josefig1 has left IRC (josefig1!~josefig@unaffiliated/josefig, Ping timeout: 250 seconds) | |
17:12 | josefig1 has joined IRC (josefig1!~josefig@unaffiliated/josefig) | |
17:27 | kjackal has joined IRC (kjackal!~quassel@62.74.62.225) | |
17:33 | kjackal has left IRC (kjackal!~quassel@62.74.62.225, Quit: No Ping reply in 180 seconds.) | |
17:36 | kjackal has joined IRC (kjackal!~quassel@62.74.62.225) | |
17:39 | statler has left IRC (statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection) | |
17:39 | ricotz_ has joined IRC (ricotz_!~ricotz@ubuntu/member/ricotz) | |
17:42 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Ping timeout: 250 seconds) | |
18:00 | josefig1 is now known as josefig | |
18:26 | kjackal has left IRC (kjackal!~quassel@62.74.62.225, Ping timeout: 245 seconds) | |
18:29 | kjackal has joined IRC (kjackal!~quassel@62.74.56.120) | |
18:37 | kjackal has left IRC (kjackal!~quassel@62.74.56.120, Ping timeout: 245 seconds) | |
19:15 | <quinox> fat booting and then running vnc / x2go / rdp should be fine even on low-spec hardware right?
| |
19:15 | woernie has left IRC (woernie!~werner@p50867386.dip0.t-ipconnect.de, Remote host closed the connection) | |
19:21 | <quinox> unless you run stuff on a toaster
| |
19:24 | <alkisg> Yup, it should be fine. All these are slower than remote xorg in LAN, but noone cares about remote xorg anymore
| |
19:37 | kjackal has joined IRC (kjackal!~quassel@2a02:587:793e:5d00:d97d:a226:af4d:1270) | |
20:46 | Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving) | |
20:59 | ricotz_ has left IRC (ricotz_!~ricotz@ubuntu/member/ricotz, Remote host closed the connection) | |
21:37 | kjackal has left IRC (kjackal!~quassel@2a02:587:793e:5d00:d97d:a226:af4d:1270, Ping timeout: 252 seconds) | |