|00:05||mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Ping timeout: 240 seconds)|
|00:09||ben_roose has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|00:18||mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)|
|00:38||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
|02:52||mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Ping timeout: 246 seconds)|
|02:52||quinox has left IRC (email@example.com, Ping timeout: 246 seconds)|
|02:52||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 264 seconds)|
|02:53||quinox has joined IRC (firstname.lastname@example.org)|
|02:53||mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)|
|02:54||Fenuks has joined IRC (Fenuks!~Fenuks@gate.ifmieo.nspu.ru)|
|04:40||gbaman has left IRC (email@example.com, Remote host closed the connection)|
|04:48||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|05:25||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 250 seconds)|
|05:27||adrianorg has joined IRC (email@example.com)|
|05:30||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
|05:45||eemeli has joined IRC (eemeli!3e94cd0c@gateway/web/freenode/ip.18.104.22.168)|
|05:52||stgraber has left IRC (stgraber!~stgraber@ubuntu/member/stgraber, Ping timeout: 260 seconds)|
|05:59||stgraber has joined IRC (firstname.lastname@example.org)|
|06:11||gbaman has joined IRC (email@example.com)|
|06:16||gbaman has left IRC (firstname.lastname@example.org, Ping timeout: 276 seconds)|
|06:30||pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 265 seconds)|
|06:35||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|06:45||pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)|
|07:21||vmlintu has joined IRC (email@example.com)|
|07:35||uXus has left IRC (uXus!~uXus@22.214.171.124, Quit: ail bi bek)|
|07:39||uXus has joined IRC (uXus!~uXus@126.96.36.199)|
|07:44||mikkel has joined IRC (firstname.lastname@example.org)|
|08:05||fnurl has left IRC (fnurl!3cf8605f@gateway/web/cgi-irc/kiwiirc.com/ip.188.8.131.52, Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)|
|08:13||gbaman has joined IRC (email@example.com)|
|08:17||gbaman has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|08:25||fnurl has joined IRC (fnurl!3cf8605f@gateway/web/cgi-irc/kiwiirc.com/ip.184.108.40.206)|
|08:26||Softeisbieger has joined IRC (Softeisbieger!~Softeisbi@dsl-217-162-128.pool.bitel.net)|
|08:58||NeonLicht has joined IRC (NeonLicht!~NeonLicht@darwin.ugr.es)|
|09:14||gbaman has joined IRC (email@example.com)|
|09:19||gbaman has left IRC (firstname.lastname@example.org, Ping timeout: 255 seconds)|
|10:15||gbaman has joined IRC (email@example.com)|
|10:20||gbaman has left IRC (firstname.lastname@example.org, Ping timeout: 272 seconds)|
|10:47||vanitas has joined IRC (vanitas!c23fd4bd@gateway/web/freenode/ip.220.127.116.11)|
|10:55||vanitas has left IRC (vanitas!c23fd4bd@gateway/web/freenode/ip.18.104.22.168, Quit: Page closed)|
|11:19||gbaman has joined IRC (email@example.com)|
|11:29||dtcrshr has joined IRC (dtcrshr!~datacrush@2801:88:f7a:100:240:a7ff:fe2d:d7c0)|
|11:29||dtcrshr has joined IRC (dtcrshr!~datacrush@unaffiliated/datacrusher)|
|11:31||F-GT has joined IRC (F-GTfirstname.lastname@example.org)|
|11:38||stgraber has left IRC (email@example.com, Changing host)|
|11:38||stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber)|
Who maintains ltsp-remoteapps and ltsp-localapps scripts? I'd like to talk about those before I make a bug report.
muppis: I think the only devs working on ltsp currently are me and vagrantc
Shame. I wish I had time to help. :(
I don't think all the parts of ltsp have a maintainer per se...
Yup, we don't have much time for ltsp either
There's something odd in handling desktop files. If I define Mimetypes in dekstop file and put Exec=ltsp-remoteapps xdg-open %U, xdg-open were dropped and only %U is passed to ltsp-remoteapps, which didn't work. Made workaround to ltsp-remoteapps to check is arg passed as command actual user's file and add xdg-open as command.
I wonder what is the most used usecase for ltsp these days. Is it beefy fatclients or something like rasppi..
muppis, it doesn't sound good to include xdg-open in the command line
It should be integrated to ltsp-remoteappsd, but not in the desktop file
|12:20||alkisg is now known as work_alkisg|
|12:45||robb_nl has joined IRC (firstname.lastname@example.org)|
|12:48||Fenuks has left IRC (Fenuks!~Fenuks@gate.ifmieo.nspu.ru, Ping timeout: 260 seconds)|
work_alkisg, I know. That's why I called it a workaround.
muppis: what I'm saying is that it's easier to accept proper fixes upstream, than workarounds
I know that too. :D
So I just hinted that you direct your effords that way...
|13:26||gvy has joined IRC (gvy!~mike@altlinux/developer/mike)|
|13:46||gvy has left IRC (gvy!~mike@altlinux/developer/mike, Ping timeout: 240 seconds)|
|13:59||gvy has joined IRC (gvy!~mike@altlinux/developer/mike)|
|14:08||markit has joined IRC (email@example.com)|
|14:22||robb_nl has left IRC (firstname.lastname@example.org, Quit: I'm gone, bye bye)|
|14:37||Fenuks has joined IRC (Fenuks!~Fenuks@22.214.171.124)|
|14:55||ben_roose has joined IRC (email@example.com)|
|15:21||Fenuks has left IRC (Fenuks!~Fenuks@126.96.36.199, Quit: KVIrc 4.3.1 Aria http://www.kvirc.net/)|
|15:56||mikkel has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|16:05||robb_nl has joined IRC (email@example.com)|
when does vagrant usually show up?
During his daytime. :P
which may be???
soon ish. iirc he's somewhere near UTC -6
|16:11||robb_nl has left IRC (firstname.lastname@example.org, Ping timeout: 264 seconds)|
|16:15||TatankaT has left IRC (TatankaTemail@example.com, Ping timeout: 250 seconds)|
|16:16||TatankaT has joined IRC (TatankaTfirstname.lastname@example.org)|
|16:18||markit has left IRC (email@example.com, Quit: Konversation terminated!)|
|16:24||bennabiy has left IRC (bennabiy!~bennabiy@unaffiliated/bennabiy, Remote host closed the connection)|
|16:25||robb_nl has joined IRC (firstname.lastname@example.org)|
|16:26||bennabiy has joined IRC (bennabiy!~bennabiy@unaffiliated/bennabiy)|
|16:51||robb_nl has left IRC (email@example.com, Read error: Connection reset by peer)|
|17:12||robb_nl has joined IRC (firstname.lastname@example.org)|
|17:38||gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)|
|17:48||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
hey vagrant :)
|17:50||* vagrantc waves|
the install was with edubuntu but i needed to muck with it since i was using a raid and multiple nics...
|17:57||lbssousa has joined IRC (email@example.com)|
|18:01||lbssousa has left IRC (firstname.lastname@example.org, Ping timeout: 256 seconds)|
|18:03||lbssousa has joined IRC (email@example.com)|
work_alkisg: thanks for your comments regarding the networkmanager interface thing...
|18:17||lbssousa has left IRC (firstname.lastname@example.org, Ping timeout: 264 seconds)|
|18:21||robb_nl has left IRC (email@example.com, Ping timeout: 250 seconds)|
donjon: that url you gave just shows me an empty page
it should give you a dropdown box and select button
it is a bit cumbersome to have to select something from a drop-down
|18:35||work_alkisg is now known as alkisg|
vagrantc: you're welcome :) It's basically a follow-up from https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1492546, problems with ltsp + systemd (solved)
i set it up that way in case you need different files
donjon: please just use a regular pastebin
!pastebin | echo donjon
donjon pastebin: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
or if you prefer, paste.debian.net
ok... i'll do that sorry
Or apache autoindex, e.g. http://people.ubuntu.com/~alkisg/ltsp/
Plain file listing...
donjon: i selected lts.conf from the drop-down, hit submit, and it gives me gibberish html
yeah, that's nice too
It looks like you have the greek schools ppa in the server but not in the chroot, you should put it in the chroot as well...
|18:41||* vagrantc forgets what the issue even was :)|
yeah i guess i haven't updated the sources in side for a while
problems were some apps were seeing network printers while others weren't
also some apps were seeing usb drives and some weren't
oh yeah, probably some combination of fat clients with remoteapps or thin clients with localapps ...
depending on what you have installed in the chroot and how much ram your clients have, they may be defaulting to fat clients
even if not specifically configured as such
|18:44||Softeisbieger has left IRC (Softeisbieger!~Softeisbi@dsl-217-162-128.pool.bitel.net, Quit: Leaving)|
donjon: what are the rough specs of our clients?
the mem on the thin clients is 2G
those should make decent fat clients
dual core cpu
but, like alkisg said, get your LTSP updated
doing that right now :)
donjon: updating the sources is a completely different things from updating the packages
lots of bugfixes since the versions you're running
i understand that
You need to run `add-apt-repository ppa:ts.sch.gr` inside the chroot, and *then* run apt-get update etc
So that you get LTSP 5.5.5 in the chroot, you now have 5.5.1
should that be done outside as well?
I think you already have done that outside the chroot
You can check by running `apt-cache policy ltsp-server`
LTSP 5.5.5 fixes a lot of printing problems over 5.5.1, so it might fix your issues
vagrantc: when I reply to a debian bug report, do I get automatically subscribed to it?
|18:49||* vagrantc nods|
vagrantc: can you help me subscribe to all ltsp bugs in debian? :)
alkisg: yes! :)
alkisg: if i recall correctly.... email firstname.lastname@example.org with "subscribe SOURCEPACKAGE EMAIL" for each of ltsp, ldm and ltspfs
alkisg: you can also get a web interface https://packages.qa.debian.org/cgi-bin/pts.cgi
alkisg: you could also possibly subscribe via tracker.debian.org/SOURCEPACKAGE ... but that interface is relatively new and i haven't used it much
https://packages.qa.debian.org/cgi-bin/pts.cgi probably needs some email=parameter, it doesn't work for me
alkisg: with email, i think you can do all three in one email
Or maybe I need to login to qa first... let me check
alkisg: should be a subscription drop-down in the lower-left
vagrantc: is that only for source changes (uploads etc), or bug reports too?
alkisg: if you select "opts" from the drop-down, it should give you checkboxes to pick
Cool, thanks, subscribing to everything there...
it'll send you a confirmation email that you should just need to reply to
All done :)
alright, i really need to sit down and do some LTSP testing on Debian!
Did you have any time to work on the new releases?
I have an ldm patch pending, about the multi-monitor setup...
Now that debian defaults to nbd, I think we can have a common wiki (at ltsp.org), and only note the differences between debian/ubuntu whenever those apply
|19:06||lbssousa has joined IRC (email@example.com)|
|19:08||gp has left IRC (firstname.lastname@example.org, Quit: Leaving)|
alkisg: i can spend some time this week and the coming week updating LTSP in Debian
i don't know that i have any multi-monitor clients to test with, though
I can probably do some testing myself as well
I do have a stretch vm, I'll debuild or I can add some repository of yours if you have one
|19:18||* vagrantc got derailed on other projects recently|
I think 16.04 feature freeze is in feb 18, we have enough time for it to be migrated there...
i ususally just use debian.org :)
this will be the first release where ubuntu just pulls from debian? :)
I mean, before you upload to unstable... maybe to experimental?
unstable should be fine for LTSP ... if there really are problems, i'll block it from hitting testing
from the sounds of it, there may be significant bugs at the moment anyways
i guess it's not true, i usually have a local repository for packages :)
i can push them somewhere instead of just locally
vagrant: I did the updates and ltsp-update-kernel and ltsp-update-image... new paste: http://pastebin.com/mynWrz1N
still no difference on client
|19:44||lbssousa has left IRC (email@example.com, Ping timeout: 246 seconds)|
|20:55||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
What's the best way to get rid off the "this kernel requires the following features not present on the cpu pae"
Hello by the way o/
Maijin: use a kernel that doesn't require pae
most distros have one
Yep, but what preference and stuff should I change in the config ?
I'm using edubuntu btw
"change this file: ‘/usr/share/ltsp/plugins/ltsp-build-client/Ubuntu/020-kernel-selection’. I removed 2 times ‘-pae’ in the kernel selection. Seems to install by default the pae kernel. Removing this ended with an install of non-pae kernel for the thin clients."
but maybe I have to do something after that?
cause it doesn't work :(
||cw: oh I see that you need to use same arch as your client
is that correct?
not sure, that guide is really old though
I can tell you though, clients that did not have CPU pae support did not perform well for me. I did get one to work once, but it was unacceptable
||cw: héhé, is refurbish clients for association
we are creating a small edubuntu stuff for school in the Philippines
that's all we got yet
there was one I even had to compile my own kernel for, ubuntu has made some really questionable cpu support choices
But if it's the problem with the server
then I'll need to reinstall it with forcepae
and it should then work
right now is x64
one SoC in fact they finally included the LAN driver for (the support ticket to add it mentioned this SoC) and in the same built they also started requiring a CPU feature the SoC didn't have.
I've done x64 server, it works, you just have to make sure you set arch right all the time, and of course any custom compiles for the client image becomes a pain
If it's confirm that I can use a x64 server and a non pae client
I'll need then to know what to do
|21:21||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
does this apply?
you might be able to just change up the pxe config to add the flag
|22:42||dtcrshr has left IRC (dtcrshr!~datacrush@unaffiliated/datacrusher, Quit: Saindo)|
|23:47||ben_roose has left IRC (firstname.lastname@example.org, Remote host closed the connection)|