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


Channel log from 27 March 2012   (all times are UTC)

00:05irule has joined IRC (irule!~irule@189.199.30.249)
00:20rthomson has left IRC (rthomson!~rthomson@mars.pet.ubc.ca, Quit: Reached EOD)
00:27irule has left IRC (irule!~irule@189.199.30.249, Ping timeout: 264 seconds)
00:38irule has joined IRC (irule!~irule@189.199.30.249)
00:50irule has left IRC (irule!~irule@189.199.30.249, Quit: Leaving)
00:50irule has joined IRC (irule!~irule@189.199.30.249)
02:32irule has left IRC (irule!~irule@189.199.30.249, Ping timeout: 260 seconds)
02:34irule has joined IRC (irule!~irule@189.199.30.249)
03:30andygraybeal_ has left IRC (andygraybeal_!~andy@h54.89.31.71.dynamic.ip.windstream.net, Ping timeout: 246 seconds)
03:31adrianorg__ has left IRC (adrianorg__!~adrianorg@177.18.170.194, Ping timeout: 264 seconds)
04:01irule has left IRC (irule!~irule@189.199.30.249, Ping timeout: 252 seconds)
04:12alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
04:34
<alkisg>
cyberorg, knipwim, or anyone else, if you ever want to package http://www.epoptes.org for your distros, we're more than glad to help (a request for RHEL has just been made on launchpad). :)
04:44staffencasa has left IRC (staffencasa!~staffenca@128-193-148-207.oregonstate.edu, Ping timeout: 240 seconds)
05:08staffencasa has joined IRC (staffencasa!~staffenca@128-193-148-207.oregonstate.edu)
05:35bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
06:25
<knipwim>
alkisg: good to know
06:47Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com)
07:22alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
07:27khildin has joined IRC (khildin!~khildin@ip-80-236-227-194.dsl.scarlet.be)
07:31cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 246 seconds)
07:58bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
08:02mcfloppy has joined IRC (mcfloppy!~kvirc@95-88-45-130-dynip.superkabel.de)
08:23dobber has joined IRC (dobber!~dobber@213.169.45.222)
08:32Trixboxer has joined IRC (Trixboxer!~Trixboxer@115.124.115.71)
08:40cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
08:56Gremble has joined IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com)
08:57ogra_ has left IRC (ogra_!~ogra@p5098ed03.dip0.t-ipconnect.de, Excess Flood)
08:58alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
08:59ogra_ has joined IRC (ogra_!~ogra@p5098ed03.dip0.t-ipconnect.de)
09:04khildin has left IRC (khildin!~khildin@ip-80-236-227-194.dsl.scarlet.be, Read error: Connection reset by peer)
09:04Gremble has left IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com, Quit: I Leave)
09:05khildin has joined IRC (khildin!~khildin@ip-80-236-227-194.dsl.scarlet.be)
09:41frederickjh has joined IRC (frederickjh!~frederick@rivendell/member/frederickjh)
09:42frederickjh has left IRC (frederickjh!~frederick@rivendell/member/frederickjh)
09:44jtsop has joined IRC (jtsop!~quassel@2001:648:2300:2e0a:21e:33ff:fe24:96d4)
09:46jtsop has left IRC (jtsop!~quassel@2001:648:2300:2e0a:21e:33ff:fe24:96d4, Remote host closed the connection)
09:55cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 246 seconds)
10:28khildin has left IRC (khildin!~khildin@ip-80-236-227-194.dsl.scarlet.be, Remote host closed the connection)
10:28khildin has joined IRC (khildin!~khildin@ip-80-236-227-194.dsl.scarlet.be)
10:29wim__ has joined IRC (wim__!~chatzilla@WEGC203035.UNI-GRAZ.AT)
10:31andygraybeal has left IRC (andygraybeal!~andy.gray@obsidian.casanueva.com, Read error: Connection reset by peer)
10:32andygraybeal has joined IRC (andygraybeal!~andy.gray@obsidian.casanueva.com)
10:33alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
10:37staffencasa has left IRC (staffencasa!~staffenca@128-193-148-207.oregonstate.edu, Ping timeout: 250 seconds)
10:49
<wim__>
hi, we have two identical servers with ltsp-server-standalone with the users home dir mount over nfs. The clients are booting with FAT_CLIENT=true (in lts.conf). The problem is: when a Client is booting from server1, gnome3 is working fine, but when he is booting from server2, gnome3 is always in fallback mode. Servers have the same hardware and also the same software is installed. It's not...
10:50
...clear to me why it's not working on server2. Any help, ideas ..? Txs
10:50
We are using Debian/wheezy
10:53
<andygraybeal>
wow you got your system up on gnome3, sooon for me!
10:53
<Hyperbyte>
wim__, are the clients identical?
11:05
<alkisg>
wim__: nvidia drivers on any of the servers? also, is the user using the same home dir on both cases?
11:12
<wim__>
Hyperbyte: yes its the same client
11:13
alkisg: the user is using the same homedir (mount über nfs).
11:14
andygraybeal: yes, and its working great, only on one server users always get gnome3 fallback mode
11:15
<andygraybeal>
wim__, yes, i'm looking forward to upgrading.. and i've been planning on using fallback mode intentionally; but this will change if the group here recommends different.
11:18
<alkisg>
wim__: any atheros NICs on any of the 2 servers?
11:19
(also you didn't answer the question about nvidia drivers)
11:19Deaconf19 has joined IRC (Deaconf19!~chatzilla@p2150-ipbfp205yosemiya.okinawa.ocn.ne.jp)
11:19
<Deaconf19>
anyone up?
11:20
<alkisg>
!ask
11:20
<ltsp>
alkisg: ask: Don't ask to ask a question, simply ask it, and if someone knows the answer, they'll respond. Please hang around for at least 15 minutes after asking a question, as not everybody constantly monitors the channel.
11:20
<Hyperbyte>
Deaconf19, if you realize that "anyone" could include... well... anyone... including you.... you could answer the question "anyone up" yourself. That is, if you're up.
11:20
Are you up?
11:21* alkisg is indeed feeling a bit down today... P
11:21
<Deaconf19>
Thanks for that brief description :)
11:22
I ma trying to launch vmware view from the imaged pushed to a think client. I mounted /proc then did a apt-get for the package however when I push the image I do not have the software installed
11:24
I guess in short. The thin image uses it's own software or the one on the server?
11:24
<alkisg>
Depends on if your run the app locally, which is called "localapps", or remotely, within the user session which is running on the server
11:25
<Deaconf19>
does one have an advantage over the other?
11:26
<alkisg>
The first uses the client CPU and RAM, the second one your server's, and also the network for screen transfers
11:26
So yeah they're completely different
11:26
<Deaconf19>
I want the server to do the work
11:27
<alkisg>
Then why did you mount /proc? And, where?
11:27
<Deaconf19>
Because 1. I am really new to this area of the game. 2 I thought I needed to install on the local image
11:28
<alkisg>
Where did you mount /proc? In the chroot?
11:29
Whatever software you install on your server, it's immediately available to the clients, without logoff, provided they have logged in to a linux session on the server.
11:29
Does that answer your question?
11:29
<Deaconf19>
Yes sorry
11:29jvin has left IRC (jvin!~jvin@108-82-19-151.lightspeed.livnmi.sbcglobal.net, Quit: Left... chased by weasles!)
11:29
<Deaconf19>
chroot /opt/ltsp/i386
11:29
mount -t proc proc /poc
11:30
*/proc
11:30Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com, Remote host closed the connection)
11:30
<Deaconf19>
then I did an apt-get
11:30
<alkisg>
And your clients log in normally on LDM, and get a gnome desktop etc, and you want vmware view available in that session?
11:31
<Deaconf19>
Yes
11:31
<alkisg>
OK, just install it on your server then
11:31
Not in the chroot
11:31
<Deaconf19>
oh ok
11:31Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com)
11:31
<Deaconf19>
so what does LDM stand for?
11:32
<wim__>
alkisg: no atheros NICs, only intel and realtek
11:32
also no nvidia drivers on the 2 Servers, both have the exact same hardware
11:32
<alkisg>
Deaconf19: LTSP Display Manager
11:33
<Deaconf19>
So installing apps on the server automatically makes them available to the LDM?
11:33
<alkisg>
LDM is the login screen
11:33
It has no applications
11:33
<Deaconf19>
oh
11:33
<alkisg>
After you login, you work on the server
11:33
<Deaconf19>
Oh wow
11:33
I see now I understand
11:33
<alkisg>
So yes, any apps on the server are available
11:34
!docs
11:34
<ltsp>
alkisg: docs: For the most current documentation, see https://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream
11:34
<alkisg>
I think you need to read up on LTSP a bit... ^
11:34
<Deaconf19>
I have been reading the PDF
11:35
obviously not enough though
11:37bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Quit: Goin' down hard)
11:38
<Deaconf19>
Does LTSP use local logins only?
11:39
<wim__>
Deaconf19: no, we use authentication over LDAP
11:39
<Deaconf19>
ok
11:39
<alkisg>
They're called "remote logins", as you authenticate to the server, instead of locally on the client itself, which has no users.
11:39
Any authentication mechanism that the server supports is available for ltsp too
11:39
<Deaconf19>
nice
11:39
ok thanks for the information.
11:40
Hopefully this will be the last step and then I am done
11:40
I really appreciate the help
11:41
<alkisg>
You're welcome
11:41Deaconf19 has left IRC (Deaconf19!~chatzilla@p2150-ipbfp205yosemiya.okinawa.ocn.ne.jp, Quit: ChatZilla 0.9.88.1 [Firefox 11.0/20120312181643])
11:44Parker955_Away is now known as Parker955
11:47cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
11:52adrianorg__ has joined IRC (adrianorg__!~adrianorg@177.18.170.194)
11:53Parker955 is now known as Parker955_Away
11:57
<Hyperbyte>
alkisg, if you're feeling down then you should do your research about PNG's before sending mails onto the list. :P
11:57
Only kidding. ;-)
11:57
<alkisg>
Hyperbyte: my diploma was about graphics, I even developed a game engine :)
11:58
(in assembly/pascal/dos)
11:58
The problem with the login screen bands is the lack of dithering, not the available colors...
11:59
That's why I'm insisting that you people should do any comparisons *after* login
11:59
<Hyperbyte>
"you people"? lol!
11:59
<alkisg>
You and Ben :D
12:00
<Hyperbyte>
Hey I'm not complaning
12:00
*complaining
12:00
<alkisg>
Nah, but you're being misleading :P
12:00
<Hyperbyte>
I think LTSP is mainly suitable in office and working environments
12:00
<alkisg>
It's true that there are colors in an 8bpp palette that can't be expressed in 16bpp
12:00
But it's not true about the image we use in the login screen
12:00
<Hyperbyte>
If 16bit vs 32bit was important for productivity, then I wouldn't use thin clients...
12:01
<alkisg>
If you open the same image after login with a decent image viewer, you'll see no bands
12:01
<Hyperbyte>
I don't even use the default image! =D
12:01
I'm not the one talking about bands here.
12:01
<alkisg>
Ben is talking about the debian one, the blue low quality one...
12:02
<Hyperbyte>
Plus with 20% vision you don't really care about these details. :P
12:02
<alkisg>
Haha
12:02
True
12:02
I was thinking of posting a detailed mail with a full comparison, but I don't think it's worth it; another person sent a mail about having xvideo problems with 16bpp, which would be far more serious
12:03
But he couldn't post to the list; maybe he's using html, dunno
12:03
So he sent it to me privately, I asked him for more information, lets see...
12:03
<Hyperbyte>
Or maybe his e-mail got sucked into a parallel universe
12:03
<alkisg>
I think his email couldn't be expressed in 16bpp and got lost :P
12:04
Anyway even if we switch back to 32bpp by default, X_SMART_COLOR_DEPTH will still be there, and I'll be using it :D
12:05
<Hyperbyte>
It's still a very trivial issue. Like LDM_DIRECTX
12:05
It's needed for maybe 1% of the users, and for 90% of the users it is causing problems.
12:06
<alkisg>
Unfortunately LDM_DIRECTX is security-sensitive... :(
12:07
I do hope those ssh guys come up with a very very fast encryption, so that we can leave it to false in the future
12:10cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 264 seconds)
12:10
<Hyperbyte>
What would be even cooler, is encryption built right into the network cards.
12:10
<alkisg>
ipsec might help there, dunno
12:11
<Hyperbyte>
Oh, I don't want it
12:11
I'm just saying it'd be cooler, so you don't have to worry about it anymore on a software level.
12:11
<alkisg>
If point to point encryption was the default, implemented in hardware, things would be much more simple and we'd have better performance
12:11
I think ipsec has better chances to be implemented in hardware than ssh...
12:11
<Hyperbyte>
I prefer physical security. For example, everyone who attaches a foreign device to our network here, gets physically harmed. :P
12:11
<alkisg>
Hahaha
12:12
<Hyperbyte>
Just kidding again of course. ;-)
12:12
But I do have a mac filter on our local network.
12:13
<alkisg>
ltsp-localapps xterm; ip link show; get mac; fake mac; bypassed
12:14
<Hyperbyte>
Sure.
12:14
But - that's not something the average user can do.
12:14
Plus, I don't rely on the mac filter.
12:15
All local resources are password protected.
12:17artista-frustrad has joined IRC (artista-frustrad!~fernando@200.247.43.2)
12:21Gremble has joined IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com)
12:23alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
12:29toscalix has joined IRC (toscalix!~toscalix@62.87.105.183)
12:34bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Quit: Leaving.)
12:35bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
12:37bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Client Quit)
12:37bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
12:41Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com, Remote host closed the connection)
12:42Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com)
12:44mika__ has joined IRC (mika__!~mika@li87-38.members.linode.com)
13:01artista-frustrad has left IRC (artista-frustrad!~fernando@200.247.43.2, Remote host closed the connection)
13:06bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
13:15Gremble has left IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com, Quit: I Leave)
13:17andygraybeal_ has joined IRC (andygraybeal_!~andy@obsidian.casanueva.com)
13:18andygraybeal_ has left IRC (andygraybeal_!~andy@obsidian.casanueva.com, Client Quit)
13:24bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Quit: Leaving.)
13:35dead_inside has joined IRC (dead_inside!~dead_insi@76.75.3.174)
13:42bengoa has joined IRC (bengoa!~bengoa@2001:1291:229:2:216:cbff:feab:6cc9)
13:52ogra_ has left IRC (ogra_!~ogra@p5098ed03.dip0.t-ipconnect.de, Excess Flood)
13:53ogra_ has joined IRC (ogra_!~ogra@p5098ed03.dip0.t-ipconnect.de)
13:55Gremble has joined IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com)
13:57
<Hyperbyte>
Gremble! :>
13:57
<Gremble>
Hyperbyte!
13:58
can I help you?
13:59
<Hyperbyte>
That depends. What do you have to offer me? :-)
14:00
<Gremble>
Phhhht
14:00
dunno
14:01
well it's sunny here some I'm going to go outside
14:01
laters
14:01Gremble has left IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com, Quit: I Leave)
14:01
<dead_inside>
i have a cookie
14:04
<Hyperbyte>
...
14:05
Why would Gremble go out when there's a perfectly good cookie in here?
14:05etyack has joined IRC (etyack!~etyack@fw.acurrus.com)
14:05
<Hyperbyte>
Hey etyack :-)
14:05
<dead_inside>
he might be on a diet
14:05
<etyack>
howdy Hyperbyte
14:06
<Hyperbyte>
dead_inside, so he's fleeing from the cookie. I get it.
14:06
:)
14:07
<etyack>
i have a question concerning sshfs and honoring umask in 10.04 -- it doesn't seem to work, any suggestions?
14:09
<Hyperbyte>
How are you setting the umask? And where?
14:10
<etyack>
setting in /etc/profile on server and ltsp chroot.
14:10
works fine on local file systems - server and fat client
14:10
but not /home/ - sshfs export
14:10
<Hyperbyte>
Well, I have no experience with this and no idea how sshfs actually works
14:10
<etyack>
no problem
14:11||cw has left IRC (||cw!~chris@phpgroupware/cw, Remote host closed the connection)
14:11
<etyack>
found some gentoo forum posts that this is a known issue
14:11
<Hyperbyte>
But I'd imagine sshfs depends on the umask on the server, and wouldn't load /etc/profile because it'd be using a minimal shell and not bash
14:11
But that's just a guess.
14:12
<etyack>
sure
14:12
<Hyperbyte>
Although sh would load /etc/profile too
14:12
<etyack>
right.
14:16
<Hyperbyte>
http://andre.frimberger.de/index.php/linux/sshfs-fix-for-wrong-file-permissions-on-server/
14:16cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
14:17
<Hyperbyte>
Interesting stuff...
14:17
<etyack>
Hyperbyte - same post i found
14:17
<Hyperbyte>
:)
14:19
As another workaround you could always use nfs over sshfs
14:20
<etyack>
going to try that also. looking into fuse umask option
14:22alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
14:26bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 245 seconds)
14:28khildin has left IRC (khildin!~khildin@ip-80-236-227-194.dsl.scarlet.be, Ping timeout: 246 seconds)
14:30toscalix has left IRC (toscalix!~toscalix@62.87.105.183, Read error: Connection reset by peer)
14:40
<stgraber>
alkisg: did you test LTSP in up to date precise since the last uploads?
14:40
<alkisg>
stgraber: no, not yet
14:40
<stgraber>
alkisg: hmm, ok, because apparently we can't login :)
14:40
<alkisg>
I'll do an overall test in a few days when I have an alpha version for ltsp-server-pnp
14:40
Ouch
14:40
<stgraber>
alkisg: I'm still installing here for testing
14:42
<alkisg>
stgraber: ...you mean the 3 commits after ltsp 5.3.6, right? I don't see what could cause a login problem...
14:43
<stgraber>
alkisg: no, I mean ltsp 5.3.6 + ldm 2.3.7 (current Precise)
14:43staffencasa has joined IRC (staffencasa!~staffenca@128-193-148-207.oregonstate.edu)
14:43
<alkisg>
Let me update a chroot and test...
14:44
<stgraber>
alkisg: the description I got was pretty confusing so I'm currently testing Edubuntu with ltsp-live + Ubuntu alternate with ltsp to see if I can get the same issue and see what's going on
14:45
<alkisg>
stgraber: are you talking about https://bugs.launchpad.net/bugs/966267
14:45
?
14:45Gremble has joined IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com)
14:45
<stgraber>
alkisg: yeah
14:45
<alkisg>
OK, let's see if my updated VM experiences the same problem..
14:46
<stgraber>
crashing right after entering the username sounds like an ldm bug, except that we didn't really touch ldm in a while ... the only bit that change was wwm and an wwm crash shouldn't kill ldm
14:47
Edubuntu ltsp live seems to work here (ldm with guestlogin)
14:47
<alkisg>
Maybe it's a hardware-specific bug (e.g. with unity) that we haven't seen in our own clients
14:48
<stgraber>
alkisg: well, he says it crashes before entering the password
14:48
alkisg: so there shouldn't be any unity involved at this point
14:48
<alkisg>
"After entering the user name the screen switches to a black console with a cursor on the top left corner of the screen." ==> I assume he means the password to?
14:48
too?
14:48Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@ip-80-238-8-128.bskyb.com, Ping timeout: 245 seconds)
14:48
<alkisg>
If not, it sounds like our bug, yeah
14:49
<stgraber>
14:29 < jibel> stgraber, it switches to a black screen right after entering the username and it doesn't let me enter the passwor
14:50
<alkisg>
Hmm...
14:50
I'd suspect wwm, but why black?!
14:53
<Hyperbyte>
I'm gonna say something incredibly stupid here maybe
14:54
But could the SSH server be rejecting the user already as soon as the username is entered?
14:54
<stgraber>
no
14:54
<Hyperbyte>
Ok. :P
14:54
<stgraber>
ssh is established only after we get the password
14:54
<Hyperbyte>
Ah.
14:54
<stgraber>
(or was last I checked, maybe we/I changed that and I don't remember)
14:54
<alkisg>
Even so, it wouldn't explain the crash or the black screen
14:56
<stgraber>
oh, it's with an amd64 client, that might explain why we didn't see it
14:56* alkisg doesn't have amd64 chroots
14:56* stgraber runs another install in 64bit
14:57
<alkisg>
Nope, everything still works fine in my updated VM
14:57
Although the login box tab functionality might have broken, let me check again...
14:58
No it's ok
15:02kco has left IRC (kco!b12cf0fd@gateway/web/freenode/ip.177.44.240.253, Quit: Page closed)
15:03
<stgraber>
alkisg: reproduced on 32bit here
15:03
<alkisg>
Hm. Why would new installed be affected but not precise upgrades?
15:05
<stgraber>
no idea ... that's with the same thin client I used to test Edubuntu
15:05
so definitely not a client issue either
15:05
<Hyperbyte>
Who you gonna call... bug busters!
15:05
<highvoltage>
I ain't scared of no bugs
15:07
<stgraber>
argh, it's not always reproducable...
15:07
or it disappeared when adding SCREEN_02 + SCREEN_07 to lts.conf
15:07
but that'd be really annoying
15:08
<alkisg>
Aaah now I remember a similar issue
15:08
<stgraber>
hmm, that client is completely dead ... can't even switch to my shell on vt2
15:08
<alkisg>
It was caused by plumouth, it had a keyboard hook or something
15:08* stgraber installs ssh in the chroot
15:08
<alkisg>
And when the user pressed enter, his xorg would crash
15:09
And the users would see a small cursor flashing on the top of the screen
15:09
<stgraber>
oh, that'd explain it. Not sure why nobody saw it happen before though
15:10
<alkisg>
stgraber: can you tell him to try with tab instead?
15:10
If he can always reproduce it in his system, that is...
15:10
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/532047
15:11
<stgraber>
alkisg: I can try here, I think I can reproduce it fairly easily now
15:11
<alkisg>
(see the list of duplicates there :D)
15:11jvx has joined IRC (jvx!~jvx@2602:304:ceec:dbc0:210:b5ff:fe8a:3a95)
15:12
<stgraber>
alkisg: pressing tab worked, re-trying with enter to confirm it explodes
15:12||cw has joined IRC (||cw!~chris@gateway.wilsonmfg.com)
15:12||cw has joined IRC (||cw!~chris@phpgroupware/cw)
15:12
<alkisg>
stgraber: don't
15:12
<stgraber>
alkisg: could it be that we don't kill plymouth as well as we used to?
15:12
<alkisg>
Press enter inside the session
15:12
stgraber: btw... when I changed the openvt code, at first I tried without the -f parameter, but some times that didn't work, and I had to put -f back
15:12
<jvx>
Should local devices (usb flash drives) work on standard ltsp clients or is there a setting I need to change?
15:13
<alkisg>
stgraber: so something was using vt7 before the ldm script was launched
15:13
stgraber: (presumably plymouth)
15:13
<stgraber>
right, I think we need to kill it harder
15:13Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com)
15:14
<Hyperbyte>
jvx, should work, assuming it's a standard drive that doesn't require special drivers, and is formatted in a filesystem Linux and LTSP can understand.
15:14
<alkisg>
stgraber: do we also have a FRAMEBUFFER=y setting in the initramfs? Is that needed?
15:14
<stgraber>
alkisg: confirmed, if I use <tab> it works
15:14
<alkisg>
stgraber: also try enter inside the session
15:14
Anywhere
15:14
<stgraber>
yeah it crashed it
15:14Trixboxer has left IRC (Trixboxer!~Trixboxer@115.124.115.71, Quit: "Achievement is not the end, its the beginning of new journey !!!")
15:14* stgraber looks at adding some code to kill plymouth for good before touching SCREEN_07
15:16
<jvx>
Hyperbyte, I thought they were supposed to work, but first attempt didn't. guess I have to try a few more clients and flash drives. is there a command like lsusb that would show 'something' connected on the client?
15:17
<alkisg>
stgraber: do remove the -f openvt parameter with the same commit, so that we're sure that tty collisions don't happen again without us visibly knowning about it
15:17
<stgraber>
alkisg: yep, will do. Now building a chroot with sshd so I can check exactly what's left running and see how to make it quit without messing with the screen too much
15:18
<alkisg>
stgraber: try SCREEN_07=shell
15:18
Or SCREEN_02 to avoid colisions :D
15:18
<stgraber>
I want to avoid switching vt as I know plymouth may do some things when you do that
15:18
<alkisg>
SCREEN_DEFAULT=02
15:19
...it's not even needed
15:19
plymouth would be on vt7, and you'd be on 02 by default
15:19
(don't put an ldm screen at all)
15:21risca has joined IRC (risca!~risca@wi-secure-1371.cc.umanitoba.ca)
15:21
<stgraber>
alkisg: hmm, we don't actually have plymouth running when ldm is started ...
15:22
though we might have it running just before which may be equally bad
15:22
<alkisg>
RCFILE_01=ps aux > /tmp/ps.$$ ?
15:23
stgraber: btw, I was wondering if we should be using openvt for X screens at all
15:24
Maybe if we don't, X/plymouth will cooperate better
15:24
Although that's only for vt7...
15:25
...hmm no, we can specify the vt in the X command line
15:26
<stgraber>
I remember us having some problem with that in the past because of the way X activates the vt
15:26
but might be worth checking if it works now
15:27
I added "plymouth quit" to ltsp-init-function and dropped the -f flags, will check if it magically works now
15:27komunista has joined IRC (komunista!~slavko@adsl-195-168-247-102.dynamic.nextra.sk)
15:30
<stgraber>
alkisg: I don't have plymouth running but openvt still tells me it's in use...
15:31
<alkisg>
stgraber: maybe plymouth doesn't free the vt? I don't know how vts are handled...
15:32
Even thought that bug was marked as resolved, I still saw similar bug reports from time to time
15:32
So I think that there's still some plymouth related bug standing
15:34
<stgraber>
alkisg: hmm, the upstart job (and probably the regular sysvinit script) were wrong ... they were killing plymouth after starting screen_session
15:35
alkisg: I'm trying to revert all my changes and just change the init script, see if that's enough
15:40
alkisg: that did the trick apparently
15:40
<alkisg>
Cool!
15:44dobber has left IRC (dobber!~dobber@213.169.45.222, Remote host closed the connection)
15:48Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com, Remote host closed the connection)
15:48Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com)
15:49
<alkisg>
stgraber: remember to remove the -f from the openvt call
15:49
I only put it (again) there because of that plymouth problem
15:50
<stgraber>
alkisg: I kept it because it's still needed ...
15:51
alkisg: plymouth doesn't seem to always close the vt properly
15:51
<alkisg>
:(
15:51
OK
15:51
Maybe it forks something in the background and waits for a couple of seconds for something to finish... anyways
15:53asmok has joined IRC (asmok!~asmok@adsl-85-157-204-13.regionline.fi)
15:57rthomson has joined IRC (rthomson!~rthomson@mars.pet.ubc.ca)
16:14jvx has left IRC (jvx!~jvx@2602:304:ceec:dbc0:210:b5ff:fe8a:3a95, Quit: Leaving)
16:15etyack has left IRC (etyack!~etyack@fw.acurrus.com)
16:18dead_inside has left IRC (dead_inside!~dead_insi@76.75.3.174, Ping timeout: 244 seconds)
16:24alexqwesa_ has joined IRC (alexqwesa_!~alex@109.172.12.47)
16:25alexqwesa has left IRC (alexqwesa!~alex@109.172.12.47, Ping timeout: 265 seconds)
16:25risca has left IRC (risca!~risca@wi-secure-1371.cc.umanitoba.ca, Ping timeout: 245 seconds)
16:29andygraybeal has left IRC (andygraybeal!~andy.gray@obsidian.casanueva.com, Read error: Connection reset by peer)
16:33dead_inside has joined IRC (dead_inside!~dead_insi@76.75.3.174)
16:38
<alkisg>
knipwim, cyberorg: as mentioned in ltsp-discuss, I'm going to remove the init-ltsp.d/Distro/symlinks from trunk, so that we move to the "cascading-style-sheets"-like packaging, is that OK with you?
16:38
*in ltsp-developer
16:39
I.e. opensuse should package init-ltsp.d/common directly to init-ltsp.d/, and override those files with init-ltsp.d/opensuse ones
16:46andygraybeal has joined IRC (andygraybeal!~andy.gray@obsidian.casanueva.com)
16:55
<knipwim>
alkisg: agreed
16:55
<alkisg>
knipwim: nice, pushing :)
16:56
<knipwim>
not much agreement yet on the mailinglist btw
16:56
<alkisg>
knipwim, cyberorg, stgraber: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2152
16:56khildin has joined IRC (khildin!~khildin@ip-80-236-227-194.dsl.scarlet.be)
16:56
<alkisg>
knipwim: about the names? Yeah... Let's try to get vagrantc to accept the new names, and do the changes, and we can tell anyone that disagrees later "you're late" :P
16:58
stgraber: here's the new ltsp-client-core.install, just 3 lines changed, if you can request a daily build with that I can test it...
16:58
http://paste.ubuntu.com/902477/
17:09wim__ has left IRC (wim__!~chatzilla@WEGC203035.UNI-GRAZ.AT, Quit: ChatZilla 0.9.88.1 [Iceweasel 10.0.2/20120217174734])
17:21
<alkisg>
knipwim, cyberorg, stgraber: I'm also doing the ltsp-common-functions => (ltsp-server-functions, ltsp-client-functions) that we agreed, OK?
17:21
A packaging change will be needed for that too, and it will allow ltsp-client to be installed alongside ltsp-server
17:21
<knipwim>
check
17:23* knipwim is thinking about packaging instructions on the wiki ;)
17:23
<alkisg>
Why not in the source?
17:24
<knipwim>
sure, as long as it's in a consistent place
17:24
under a # Packaging header or something
17:27khildin has left IRC (khildin!~khildin@ip-80-236-227-194.dsl.scarlet.be, Quit: I'm gone, bye bye)
17:39staffencasa has left IRC (staffencasa!~staffenca@128-193-148-207.oregonstate.edu, Read error: Connection reset by peer)
17:39shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-232.se.biz.rr.com, Ping timeout: 248 seconds)
17:41
<Llama_be>
Hey knipwim
17:42
I have used this file for network card modules: http://pastebin.com/rUq8nQqG
17:45
<alkisg>
stgraber: a two-line packaging change is needed for r2153 too, I renamed ltsp-common-functions to ltsp-[server|client]-functions
17:48
<knipwim>
Llama_be: yeah i saw earlier
17:49
<Llama_be>
ah, wasn't sure you saw, and I haven't had much online time until now
17:49
<knipwim>
i was wondering if we would need the empty variables
17:50
<Llama_be>
I don't know about that. But I imagined it would be safer to declare them
17:50
<knipwim>
and i was thinking we could only implement it in kicktoo
17:50
<Llama_be>
it would also be easier for people editing the file
17:51
I haven't yet took a dive in kicktoo or quickstart, so I don't know about that ;)
17:52
<knipwim>
kicktoo has a separate initramfs-builder download and initramfs build
17:52
<Llama_be>
but my setup is "in production" now, so I'm not playing with it too much anymore
17:52
<knipwim>
so we can put the file after the install of the initramfs builder
17:52
<Llama_be>
I might copy the setup in my home lab though ;)
17:52
<knipwim>
:)
17:53
<Llama_be>
Now that I know of kicktoo, I kinda want to dig into it, and create some profiles for various machines I have running
17:54
My dream situation would be that should anything happen to our infrastructure, it should all be documented so well, they could bring it up without needing me :)
17:54
<knipwim>
cool
17:54
<Llama_be>
I hate documenting though ;)
17:55
<knipwim>
you could have one command to recreate it all
17:55
you do? it helps me with some structure
17:55
and helps me remember stuff ;)
17:55
<Llama_be>
yeah, the remembering stuff is sometimes a problem :-p
17:56
<knipwim>
if you have any questions about kicktoo, just ask them on the github page
17:56
the maintainer is very active
17:57
or if you have change proposals
17:57
<Llama_be>
On the other hand: almost everything runs on an VMWare ESXi server, so I could just as well make sure they could restore backups of the virtual machines and document that ;)
17:58
(my parents have a small company with 5 computers or so, and I probably over-engineered the whole network, but I think it works nicely :) )
18:00
<knipwim>
nothing with over engineering it
18:00
if you're good at it, you can earn some money probably
18:01
<Llama_be>
my actual job is working with Cisco VoIP products
18:01
<knipwim>
hmm? like being on the phone all day?
18:02
<Llama_be>
nah, making sure other people can be on the phone :)
18:04
Basically we install the network devices (but thats mainly my coworkers) and then on top of that, we have phones and a server that controls the phones
18:04
and gateways to make it interact with the public phone lines and such
18:06
<knipwim>
is that all plug and play, or you have to configure stuff also
18:07
<Llama_be>
there's quite a lot of configuring in that
18:07
every company is different in how it wants its calls to be handled
18:11
and it's not only phones, it's the complete collaboration package
18:12
but the collaboration part is only starting more or less
18:12
today I've been in a meeting to discuss demo material for video conferencing
18:13
in a couple of months you should be able to call me over SIP to my phone here on my desk, with video included :)
18:13
<knipwim>
cool
18:21
<Llama_be>
and you might have seen Cisco Telepresence?
18:24komunista has left IRC (komunista!~slavko@adsl-195-168-247-102.dynamic.nextra.sk, Ping timeout: 252 seconds)
18:29alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)
18:37kco has joined IRC (kco!b12cf0fd@gateway/web/freenode/ip.177.44.240.253)
18:39komunista has joined IRC (komunista!~slavko@adsl-195-168-230-167.dynamic.nextra.sk)
18:42
<kco>
Hi , is there anyway to get the hostname of the thin client via script?
18:44
<dead_inside>
kco are you talking about a remote script you can run from the server to go out and figure out a clients hostname, or a script you can run locally on the thin client
18:45
<kco>
on the thin client
18:46
<dead_inside>
i believe you can run from the terminal: ltsp-localapps xterm
18:46
that will open a local terminal window that will show the hostname
18:47
or you can press crate + alt + f2
18:47
<Hyperbyte>
kco:
18:47
#!/bin/sh
18:47
hostname=`hostname`
18:47
echo $hostname
18:51
<kco>
dead_inside: but how can I use that in a script?
18:51
<Hyperbyte>
kco: ^^
18:52
That script above does exactly what you want.
18:52
<dead_inside>
Hyperbyte's example is for a script, my example is just to figure it out quickly
18:52
its not something someone would normally script
18:52
however
18:52
<Hyperbyte>
kco, maybe you should start by telling us what you're trying to achieve, rather than asking specific questions that don't mean anything to us.
18:53
<dead_inside>
Hyperbyte on a thin client wont your script return the hostname of the app server it is connected to? not the hostname of the thin client?
18:54
<bara>
is 3d turned off by default on fatclients?
18:54
<Hyperbyte>
dead_inside, no, it won't.
18:54
<kco>
ok...Hyperbyte's script returns the name of the server
18:55
<Hyperbyte>
bara, if by 3d you mean compiz, I believe it isn't. But it might be a good idea to do so.
18:55
kco, no.
18:55
The script I gave you returns whatever the "hostname" command returns
18:55
<dead_inside>
lol
18:55
<Hyperbyte>
And that's the hostname of the computer the script is being executed on
18:55
If you're running the script on my computer, it'd say "razor.middelkoop.cc"
18:56
<bara>
oh think have to install firmware-linux-nonfree ;)
18:56
<Hyperbyte>
If you run it on your server, it gives the hostname of the server, if you run it on the client, it gives the hostname of the client.
18:56
<dead_inside>
mines "Overlord.local"
18:56
<Hyperbyte>
kco, remember that with thin clients, all software (including your terminal) runs on the server.
18:56
If you want a terminal on a thin client locally (so on the client itself rather than the server), use this:
18:56
!localxterm
18:56
<ltsp>
Hyperbyte: localxterm: Any applications that you launch on a thin client actually run on the server. However, if in a client you run 'ltsp-localapps xterm', a local xterm will open, and any commands that you enter there will be executed locally on the client.
18:58
<kco>
so...there's no way to discover the name of the thin client running a command on the server?
18:58
or running a remote application
18:59shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-232.se.biz.rr.com)
19:02
<Hyperbyte>
kco, sure there is.
19:02
But you told dead_inside earlier you were running a script on the client that needed the hostname
19:02
SmallR2002:45 <kco> on the thin client
19:03
<dead_inside>
and Hyperbyte's script will work perfectly when ran from the thin client
19:03
<Hyperbyte>
kco, what are you trying to do, less specifically?
19:05
<kco>
I have an application server named "ltspappimg"
19:06
when I run hostname on a remote gnome-terminal it returns "ltspappimg", that's ok
19:08
but on the same gnome-terminal, I need to run a script that gives me the name of the thin client configured on the dhcp server
19:09
<Hyperbyte>
kco, why do you need a script that gives you the name of the client?
19:10
<kco>
because on the same script I need informations concernig the user logged in
19:10
<Hyperbyte>
What information?
19:11
<kco>
the name of the user
19:11
but it does not exists inside the chroot
19:12
<Hyperbyte>
It shouldn't. Users should only exist on the server.
19:12
If you want the name of the user, just use the $USER variable
19:13
But you're still not telling me -what exactly- this script of yours is supposed to do
19:14
<kco>
it sends information about all the machines to a central server
19:15
hostname, IP, users
19:15
MAC
19:16
<dead_inside>
you should look into the ltsp-cluster control center kco, the terminal logs have most all that info
19:16alexqwesa_ has left IRC (alexqwesa_!~alex@109.172.12.47, Read error: Operation timed out)
19:17
<kco>
and the script runs as root...so the $USER variable doesn't work
19:18alexqwesa has joined IRC (alexqwesa!~alex@109.172.12.47)
19:22
<kco>
ltsp-cluster-control is intalled on a diffrent server...can I have acces to this logs in a remote gnome-terminal?
19:25
<Hyperbyte>
kco, type 'w' in a terminal on your server.
19:27
<kco>
nti pts/2 192.168.1.26:7.0 15:08 5:37 0.20s 0.20s bash
19:29
<Hyperbyte>
That shows all logged in users.
19:29
But if you're running LTSP-cluster then there's better ways probably, as dead_inside suggested, I have no idea about that.
19:30risca has joined IRC (risca!~risca@wi-secure-2252.cc.umanitoba.ca)
19:30
<kco>
I was already using 'w'...but iy doesn't show the hostname
19:33
<Hyperbyte>
You know the hostname in LTSP is just 'ltsp' plus the host part of the IP address huh?
19:34
192.168.0.5/255.255.255.0 would be called "ltsp5"
19:36
<kco>
in Ctrl + Alt + F1 it is ltcpd007249
19:36
in my case
19:41Parker955_Away is now known as Parker955
19:43
<Hyperbyte>
Oh, then cluster does that differently
19:43
See, I told you I know nothing about LTSP-cluster. :P
19:45
<kco>
I think it's not related to the LTSP-cluster
19:45
the name is set on the DHCP
19:48Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com, Quit: Leaving)
19:55
<dead_inside>
kco are you on an ipv4 or ipv6, normally the clients will auto set their host name as ltsp plus the last part of the ip address
20:00alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
20:03
<kco>
ipv4...but the IPs are statically set on the server
20:03
<alkisg>
kco: echo $LTSP_HOSTNAME gives you the client hostname
20:04
*LTSP_CLIENT_HOSTNAME
20:15
<kco>
alkisg: it works with ordinary users, but not as root
20:15
I'll try to find a way around that
20:16
thanks everybody
20:16Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com)
20:16
<alkisg>
kco: what do you mean as root?
20:16
Are you running the script as root from a thin client and you want to find out its hostname?
20:16
Or from the server?
20:18bengoa has left IRC (bengoa!~bengoa@2001:1291:229:2:216:cbff:feab:6cc9, Quit: Leaving.)
20:24
<kco>
from a thin-client
20:24
<alkisg>
kco: are you using sudo to run it, or su -?
20:24
<kco>
su -
20:25
<alkisg>
Try su without -, that should keep the environment
20:26
Or su -p
20:26bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
20:27
<kco>
the script will run automatically when in user login
20:27
<alkisg>
How?
20:28
From /etc/xdg/autorun ? from pam_exec? how?
20:28
<kco>
probably /etc/profile
20:28
<alkisg>
Then it won't run as root
20:31Gremble has left IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com, Quit: I Leave)
20:31
<kco>
then I'll have to run it some other way
20:31
<alkisg>
OK, when you find that way, tell us so that we can help you discover the client hostname from there
20:32
<kco>
what if I use pam_exec?
20:34
<alkisg>
I think you should better explain your script requirements in more detail, so that you get better (and faster) help
20:34
Why does it need to run on login? Why does it need to run as root? Does it send information for all users or just for that one? etc
20:35Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com, Ping timeout: 272 seconds)
20:37Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com)
20:40
<kco>
when a user log in the script sends information about the machine using netcat
20:40
<alkisg>
That doesn't require root privileges
20:40andygraybeal has left IRC (andygraybeal!~andy.gray@obsidian.casanueva.com, Read error: Connection reset by peer)
20:41Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com, Client Quit)
20:42
<kco>
some of the information require the user to be root
20:42
<alkisg>
Client information?! Which one?
20:42ry has left IRC (ry!~ry@static-71-183-64-28.nycmny.fios.verizon.net, Quit: Leaving)
20:43
<kco>
I think it runs # lshw
20:43
<alkisg>
Why do you need clients to get the *server* hardware each time they login?
20:43
Remember, your client sessions run on the server
20:45
<kco>
yes..you have a point
20:45
<alkisg>
I think what you really want is to have a script that runs on the thin clients themselves, not in the server
20:45
Not when the users log in, but when the clients boot
20:46
<kco>
I will try to find
20:46
<alkisg>
So there you are root, have the $(hostname), and lshw and everything
20:46
<kco>
a way to run it as a common user*
20:46
and get rid of the information I don't need
20:47
<alkisg>
Do you want the client hardware information, or you don't care about that?
20:48
<kco>
It will be great if I can get that info...
20:49
<alkisg>
Right, so as I said, you want to run that on the clients themselves
20:49
See the lts.conf manpage about RCFILE_01
20:49
!lts.conf
20:49
<ltsp>
alkisg: lts.conf: http://manpages.ubuntu.com/lts.conf
20:50
<kco>
thanks...I'll try using RCFILE_01
20:54staffencasa has joined IRC (staffencasa!~staffenca@128-193-148-207.oregonstate.edu)
21:07staffencasa has left IRC (staffencasa!~staffenca@128-193-148-207.oregonstate.edu, Quit: Leaving)
21:12mcfloppy has left IRC (mcfloppy!~kvirc@95-88-45-130-dynip.superkabel.de, Ping timeout: 252 seconds)
21:21staffencasa has joined IRC (staffencasa!~staffenca@128-193-148-207.oregonstate.edu)
21:25bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 265 seconds)
21:32andygraybeal has joined IRC (andygraybeal!~andy.gray@obsidian.casanueva.com)
21:50alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
21:57asmok has left IRC (asmok!~asmok@adsl-85-157-204-13.regionline.fi, Quit: Lähdössä)
22:00komunista has left IRC (komunista!~slavko@adsl-195-168-230-167.dynamic.nextra.sk, Quit: Leaving.)
22:21dead_inside has left IRC (dead_inside!~dead_insi@76.75.3.174, Quit: Leaving...)
23:21adrianorg__ has left IRC (adrianorg__!~adrianorg@177.18.170.194, Remote host closed the connection)