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


Channel log from 25 November 2014   (all times are UTC)

01:24freedomrun has left IRC (freedomrun!~quassel@unaffiliated/freedomrun, Read error: Connection reset by peer)
04:11andygraybeal has left IRC (andygraybeal!~andy@h191.214.22.98.dynamic.ip.windstream.net, Quit: Ex-Chat)
05:20vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
05:56cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)
05:56cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
06:18mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, Ping timeout: 244 seconds)
06:46telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
06:48telex has joined IRC (telex!teletype@freeshell.de)
06:51map7_ has joined IRC (map7_!~map7@ppp59-167-194-79.static.internode.on.net)
06:59freedomrun has joined IRC (freedomrun!~quassel@unaffiliated/freedomrun)
07:30NeonLicht has left IRC (NeonLicht!~NeonLicht@darwin.ugr.es, Read error: Connection reset by peer)
07:34ricotz has joined IRC (ricotz!~rico@p5B2A80D8.dip0.t-ipconnect.de)
07:34ricotz has left IRC (ricotz!~rico@p5B2A80D8.dip0.t-ipconnect.de, Changing host)
07:34ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
07:40NeonLicht has joined IRC (NeonLicht!~NeonLicht@darwin.ugr.es)
07:44cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 244 seconds)
07:47mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.71.254)
07:53Fenuks has joined IRC (Fenuks!~Fenuks@mail.c-lan.ru)
07:54cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
08:21work_alkisg is now known as alkisg
08:59khildin has joined IRC (khildin!~khildin@ip-213-49-116-25.dsl.scarlet.be)
09:17khildin has left IRC (khildin!~khildin@ip-213-49-116-25.dsl.scarlet.be, Ping timeout: 258 seconds)
09:20IliasPap has joined IRC (IliasPap!c23fefeb@gateway/web/freenode/ip.194.63.239.235)
09:21
<IliasPap>
Καλημερα
09:22
<muppis>
!greek
09:22
<ltsp`>
greek: Στο παρόν κανάλι μιλάνε μόνο Αγγλικά, για υποστήριξη στα Ελληνικά από την υπηρεσία Τεχνικής Στήριξης ΣΕΠΕΗΥ διαβάστε το http://ts.sch.gr/wiki/IRC και στη συνέχεια πληκτρολογήστε /j #ts.sch.gr
09:24
<IliasPap>
Can somebody explain to me what does PXE-EC8: !PXE structure was not found in UNDI driver code segment mean. It sudenly appeared to all clients and they won't boot
09:28khildin has joined IRC (khildin!~khildin@ip-213-49-116-25.dsl.scarlet.be)
09:37freedomrun has left IRC (freedomrun!~quassel@unaffiliated/freedomrun, Read error: Connection reset by peer)
10:02alkisg is now known as work_alkisg
10:05IliasPap has left IRC (IliasPap!c23fefeb@gateway/web/freenode/ip.194.63.239.235, Ping timeout: 246 seconds)
10:14elpap9 has joined IRC (elpap9!c23fefeb@gateway/web/freenode/ip.194.63.239.235)
10:16
<elpap9>
Καλημερα απο Χίο. Ενώ για 2 βδομάδες όλα δούλευαν κανονικά, απο χθές οι μισοι clients βγάζουν !PXE structure was not found in UNDI driver code segment και άλλοι NO MORE net work devices Disk boot failure
10:37Fenuks has left IRC (Fenuks!~Fenuks@mail.c-lan.ru, Read error: Connection reset by peer)
10:37Fenuks|2 has joined IRC (Fenuks|2!~Fenuks@mail.c-lan.ru)
10:46elpap9 has left IRC (elpap9!c23fefeb@gateway/web/freenode/ip.194.63.239.235, Quit: Page closed)
11:36Fenuks|2 has left IRC (Fenuks|2!~Fenuks@mail.c-lan.ru, Read error: Connection reset by peer)
11:36Fenuks has joined IRC (Fenuks!~Fenuks@mail.c-lan.ru)
11:47freedomrun has joined IRC (freedomrun!~quassel@unaffiliated/freedomrun)
11:53khildin has left IRC (khildin!~khildin@ip-213-49-116-25.dsl.scarlet.be, Ping timeout: 265 seconds)
11:54adrianorg has joined IRC (adrianorg!~adrianorg@177.204.79.180.dynamic.adsl.gvt.net.br)
12:05minetreu has joined IRC (minetreu!57a2831c@gateway/web/freenode/ip.87.162.131.28)
12:05
<minetreu>
!futro
12:05
<ltsp`>
I do not know about 'futro', but I do know about these similar topics: 'future'
12:05
<minetreu>
cool
12:06
!future
12:06
<ltsp`>
future: Some of the highlights include working towards obsoleting LDM (using libpam-sshauth/libnss-sshsock), moving stuff out of ltsp-build-client into initramfs run-time modifications, and making it possible to maintain the chroot from a booted environment
12:06
<minetreu>
good to know
12:08
i cant bring up a good grafik on futro s450 machines, my ltsp-image is amd64 running on 14.04, any help in here?
12:09
after login, the display drivers fails (suspended monitor) completely
13:03JuJuBee has left IRC (JuJuBee!~mike_knic@24-148-115-153.ip.mhcable.com)
13:04JuJuBee has joined IRC (JuJuBee!~mike_knic@24-148-115-153.ip.mhcable.com)
13:20Fenuks has left IRC (Fenuks!~Fenuks@mail.c-lan.ru, Ping timeout: 240 seconds)
13:26
<minetreu>
ahhh kernel-panic
14:02andygraybeal has joined IRC (andygraybeal!~andy@h191.214.22.98.dynamic.ip.windstream.net)
14:25minetreu has left IRC (minetreu!57a2831c@gateway/web/freenode/ip.87.162.131.28, Ping timeout: 246 seconds)
14:39alkisg has joined IRC (alkisg!~Thunderbi@ubuntu/member/alkisg)
14:42work_alkisg has left IRC (work_alkisg!~alkisg@194.63.234.224, Ping timeout: 255 seconds)
14:50alkisg has left IRC (alkisg!~Thunderbi@ubuntu/member/alkisg, Quit: alkisg)
15:02Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
15:04Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Client Quit)
15:23minetreu has joined IRC (minetreu!57a2831c@gateway/web/freenode/ip.87.162.131.28)
15:23
<minetreu>
jup
15:30
still stuck on a futro s450 thin configuration, screenresolution is not matching and after login the driver fails complete
15:33telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
15:34telex has joined IRC (telex!teletype@freeshell.de)
15:39
<minetreu>
problem for me is, i can not login, so i cant see xrandr outputs or anything else
15:54khildin has joined IRC (khildin!~khildin@ip-213-49-116-25.dsl.scarlet.be)
16:14uuuolliw has joined IRC (uuuolliw!~william@fs-93-93-43-155.fullsave.info)
16:46work_alkisg has joined IRC (work_alkisg!~alkisg@194.63.234.224)
16:48
<minetreu>
no ideas about the s450 thin-client? i checked diff images, conf and xorgs... no success for me
16:51
<sbalneav>
What video chipset does it have.
16:54Faith has joined IRC (Faith!~paty@143.107.231.49)
16:54Faith has joined IRC (Faith!~paty@unaffiliated/faith)
16:56
<minetreu>
hi, radeon x1250
16:56
Unable to initialize GTK+ after login
17:04
my image is a amd64, server is ubuntu 14.04. various machines (mostly dell) running well
17:07
' Failed to find output xrandr-VGA1 ' which is ok, while the screen (1920x1080) is connected to dvi, so how to tell xrandr to look for dvi
17:11
xrandr -q -display 192.168.3.80:7
17:11freedomrun has left IRC (freedomrun!~quassel@unaffiliated/freedomrun, Read error: Connection reset by peer)
17:12
<minetreu>
Screen 0: minimum 320 x 200, current 2560 x 1080, maximum 8192 x 8192 DVI-0 connected 1920x1080+640+0
17:15
LVDS connected primary 640x480+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 640x480 60.0*+
17:16
which, if i am interpreting correct, uses both the dvi and lvds output and therefore shakes an error
17:50minetreu has left IRC (minetreu!57a2831c@gateway/web/freenode/ip.87.162.131.28, Ping timeout: 246 seconds)
18:12Markus_123 has joined IRC (Markus_123!~Markus123@193-81-136-11.adsl.highway.telekom.at)
18:14mealstrom has left IRC (mealstrom!~Thunderbi@46.63.71.254, Ping timeout: 255 seconds)
18:34minetreu has joined IRC (minetreu!2f450fff@gateway/web/freenode/ip.47.69.15.255)
18:36
<minetreu>
after several attempts with xrandr -output ... -display ...:7 i am halfway able to use a xsession with my thinclient futro s450
18:40
i found my solution here: https://github.com/gdi2k/mac2xrandr
19:01
but i guess there is a native way, too
19:08
how do you force evolution mail to shutdown after user logout, my clients stuck on the app without window manager...
19:50mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.63.163)
19:55khildin has left IRC (khildin!~khildin@ip-213-49-116-25.dsl.scarlet.be, Ping timeout: 250 seconds)
19:58mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, Ping timeout: 240 seconds)
20:19mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.63.163)
20:21Markus_123 has left IRC (Markus_123!~Markus123@193-81-136-11.adsl.highway.telekom.at, Quit: Leaving)
20:25Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
21:19map7_ has left IRC (map7_!~map7@ppp59-167-194-79.static.internode.on.net, Ping timeout: 244 seconds)
21:19minetreu has left IRC (minetreu!2f450fff@gateway/web/freenode/ip.47.69.15.255, Quit: gn8)
21:22vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
21:35khildin has joined IRC (khildin!~khildin@ip-213-49-116-25.dsl.scarlet.be)
21:36ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
21:42khildin has left IRC (khildin!~khildin@ip-213-49-116-25.dsl.scarlet.be, Quit: I'm gone, bye bye)
21:54takeawillpill has joined IRC (takeawillpill!4b443ff5@gateway/web/freenode/ip.75.68.63.245)
21:56
<takeawillpill>
Excuse me, but is there any fix or workaround for gallium? I've been having various opengl issues.
22:04championofcyrodi has left IRC (championofcyrodi!~cott@50-205-35-98-static.hfc.comcastbusiness.net, Remote host closed the connection)
22:08takeawillpill has left IRC (takeawillpill!4b443ff5@gateway/web/freenode/ip.75.68.63.245)
22:24telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
22:26telex has joined IRC (telex!teletype@freeshell.de)
22:35talntid has joined IRC (talntid!~talntid@173-160-189-58-Washington.hfc.comcastbusiness.net)
22:36
<talntid>
if LTSP still maintained/improved?
22:41
<vagrantc>
somewhat
22:42
talntid: it's mostly been in maintenance mode for the last couple years ... with some great ideas for improvements, but not much progress
22:43
it could sure use some additional energy, though...
22:43
<talntid>
yeah, I'm just trying to decide if I should keep it on my call center revamp
22:44
I'm running 60 clients off LTSP, but they're complaining their computers are pretty slow now
22:44
so I'm going to revamp it by end of year - just deciding if I stay with LTSP
22:44
<vagrantc>
thin or fat clients?
22:45
<talntid>
they are thin clients, no hard drives, but they use their web browser as a localapp
22:46
the issue could be network congestion, IOPS, cpu/ram usage on the server, or any of a few other things...
22:52sandro_ has joined IRC (sandro_!25758d2a@gateway/web/freenode/ip.37.117.141.42)
22:54
<vagrantc>
talntid: yeah, identifying exactly where the slowdown would be a good idea before going on to implement something new with the same problems... :)
22:55
<sandro_>
Hi, I just run ltsp-update-image and I saw lots of messages statinga file could not be read. The puzzling thing is that are all file inthe server'home, not in the the clinent's chroot.
22:57
<vagrantc>
sandro_: what was the exact commandline you used? is there an /etc/ltsp/ltsp-update-image.conf, and if so what's in it?
22:59
<sandro_>
the commadn line was: "/usr/sbin/ltsp-update-image -b /opt/ltsp/trusty", /opt/ltsp/trusty has a subdir i38 that hold a trusty client created with ltsp-build-client
22:59
the commadn line was: "/usr/sbin/ltsp-update-image -b /opt/ltsp/trusty", /opt/ltsp/trusty has a subdir i386 that hold a trusty client created with ltsp-build-client
23:00
currently it's running: "mksquashfs /opt/ltsp/trusty/i386 /opt/ltsp/trusty/images/i386.img.tmp -e cdrom"
23:03
I don't have any /etc/ltsp/ltsp-update-image.conf
23:04JuJuBee has left IRC (JuJuBee!~mike_knic@24-148-115-153.ip.mhcable.com, Ping timeout: 264 seconds)
23:05
<sandro_>
I'm runnung on ubuntu 12.04 ltsp-server 5.3.7-0ubuntu2.2
23:05
<vagrantc>
i wouldn't recommend using the --base feature...
23:06
then you'll need to specify it for every single tool
23:07
better to use /opt/ltsp/i386-trusty or trusty-i386 than /opt/ltsp/trusty/i386 ... the tools don't support the --base feature reliably.
23:11
<sandro_>
Well, in fact I did use -b opt when creating the image. Precisely I used
23:11
ltsp-build-client --config /etc/ltsp/ltsp-build-trusty.conf --dist trusty --fat-client-desktop ubuntu-desktop --chroot trusty-i386
23:12
no, not sure...
23:12
that's from the wrong terminal...
23:13
the right command in on the terminall that is busy.
23:14
I'm sure I used --dist trys and -b /opt/ltsp/trusty --fat-client-desktop ubuntu-desktop (not sure about the --config opt and the --chroot)
23:15
It as ltsp-build-client that added the i386 subdir
23:16
So, vagrantc, what is happening with the file that are in server's home? what do you suggest to do?
23:19
<vagrantc>
i don't know, i was just trying to rule out if you were effectively doing "ltsp-update-image --cleanup /" or something.
23:19
it kind of sounds like that's what it's doing.
23:20
<sandro_>
I never issued that command
23:23
By the way. I'm building a new image just out of despair. Up to yesterday I had a working system. 6 Fat clients with ltsp autentication.
23:23
After a power failure the server was up again but client only get to the ldm screen and don't authenticate any more.
23:24
The ldm debug writes:
23:24
nov 25 17:17:52: [ssh] INFO: calling rc.d pressh scripts nov 25 17:17:57: [ssh] CRITICAL: no response, restarting
23:26
But I can't understand what is not responding. Whe I try to authenticate the server logs (auth.log)
23:26
Connection closed by 192.168.1.40 [preauth]
23:26
<vagrantc>
did the ip address of the server change?
23:27
<sandro_>
no, not that I know, event thought I cant exclude that a second ip wasd also present on the server in the past (ldap was pointing there)
23:27
But the server workked with the present conf for months.
23:27
<talntid>
vagrantc, yeah I plan to determine where the slowdown is, just making sure that if it comes to that, it is still a good option
23:28
instead of doing research during build-time
23:29
<sandro_>
vagrant I also added LDM_SERVER=192.168.1.2 LDM_SSHOPTIONS="-o CheckHostIP=no" afetr reading some hint you wrote
23:32
If I issue ltsp-update-sshkeys, do I need to recreate the image via ltsp-update-image?
23:32
<vagrantc>
yes
23:33
i can't ever remember if ltsp-update-image runs ltsp-update-sshkeys before generating the image...
23:34
<sandro_>
ok, no problem... I can regenerate the image anyhow
23:35
the trusty image is building really slowly, i remember around 15 minute but now it seems much longer, do I remember correctly?
23:35
I gor 2 processor
23:35
I got 2 processor 2.4 GHz
23:44
<vagrantc>
depends on a lot of factors
23:50
<sandro_>
I'm rebuilding the old image and it gos at a reasonable speed, it's now 60% in less than 10 min.