[13:18] <TheProf> Hello everyone.  Question:  is it possible that an apt-get update && upgrade can cause the lts.conf file to be ignored?  I've got a new login screen on the thin clients, the default session option is lts.conf is being ignored, and the printers I've specified in lts.conf are not working.  Help? :)
[13:31] <alkisg> "a new login screen"? meaning?
[13:54] <TheProf> alkisg, means a new theme
[13:55] <TheProf> I just tried specifying a different theme in lts.conf, rebuilt the image and rebooted the thin client but it didn't pick up the change.
[14:11] <alkisg> TheProf: do you have tftpd-hpa as the tftp server?
[14:30] <TheProf> alkisg, sorry for the delays in responding -- just a busy day at the school here.  I am not sure which version of tftp server. I will try to determine it now
[14:31] <alkisg> TheProf: grep -i verbose /etc/default/tftpd-hpa
[14:33] <TheProf> that actually gives no output
[14:34] <TheProf> weird -- looking into the file gives me 4 lines
[14:34] <alkisg> Ah sorry
[14:34] <alkisg> My bad. What's the last line?
[14:34] <TheProf> tftp_username, directory, address, and optins.
[14:34] <alkisg> options?
[14:34] <TheProf> tftp_options='--secure'
[14:34] <alkisg> ok, change it to: --secure --verbose
[14:35] <alkisg> Then run: sudo service tftpd-hpa restart
[14:35] <alkisg> The reboot the client
[14:35] <alkisg> And finally do: grep lts.conf /var/log/syslog
[14:35] <alkisg> This will tell you where is the client trying to find lts.conf
[14:35] <TheProf> OK I'm doing that now.
[14:49] <TheProf> alkisg, OK I've rebooted the server.  The new login screen still came up.  grepping for lts.conf gives 2 lines:
[14:49] <TheProf> Oct 11 10:39:39 i7-eduLTSP in.tftpd[15825]: RRQ from 192.168.0.41 filename /ltsp/i386/lts.conf
[14:49] <TheProf> Oct 11 10:47:32 i7-eduLTSP in.tftpd[16710]: RRQ from 192.168.0.41 filename /ltsp/i386/lts.conf
[14:49] <TheProf> That's it.
[14:49] <alkisg> So it looks like it reads the correct lts.conf. Can you pastebin it?
[14:59] <TheProf> alkisg, sure - the whole syslog or only those two lines?
[15:00] <TheProf> Or are you talking about lts.conf?
[15:00] <alkisg> lts.conf
[15:00] <TheProf> !pastebin
[15:02] <TheProf> http://paste.ubuntu.com/706149/
[15:03] <alkisg> TheProf: erm, can you use pastebin instead? The paste.ubuntu.com site has an error and it doesn't allow me to download it as text
[15:03] <alkisg> pastebin.com
[15:03] <alkisg> I want to check it for syntax errors
[15:04] <TheProf> Not a problem at all -- doing so now.
[15:06] <TheProf> alkisg, http://pastebin.com/YFEGa2M2
[15:07] <alkisg> syntax error in /tmp/a, line=3
[15:07] <alkisg> Ah it contains windows newlines
[15:08] <alkisg> TheProf: so anyway try this: /opt/ltsp/i386/usr/bin/getltscfg -a -c /var/lib/tftpboot/ltsp/i386/lts.conf
[15:08] <alkisg> Do you get a syntax error?
[15:09] <TheProf> doing so now
[15:10] <TheProf> I edit the file with MC
[15:10] <TheProf> alkisg, no syntax error, it just outputs the uncommented lines.
[15:11] <alkisg> OK, so your client may be reading lts.conf after all
[15:11] <alkisg> See if SCREEN_02 works, like I said in #ltsp
[15:14] <TheProf> OK made the change in lts - going to reboot thin client
[15:23] <TheProf> alkisg, so once rebooted the thin client has a shell on ctrl-alt-F1
[15:24] <TheProf> granted I believe it always had one before.  No other difference I noticed.
[15:24] <alkisg> TheProf: how about alt+ctrl+f2 ?
[15:24] <TheProf> alkisg, no shell on F2
[15:24] <alkisg> You put those?
[15:24] <alkisg> SCREEN_02=shell
[15:24] <alkisg> SCREEN_07=ldm
[15:24] <alkisg> ?
[15:30] <TheProf> yes right under LDM_THEME line
[15:31] <alkisg> Then it doesn't look like your client is reading lts.conf, strange
[15:31] <alkisg> Now try this
[15:31] <TheProf> That's why I am feeling like it is ignoring it somehow.  Question: there is both /tftboot/ltsp/i386 and 64 bit?
[15:31] <alkisg> Login on the client, and run: ltsp-localapps xterm
[15:31] <TheProf> amd64 I meant directories.
[15:31] <alkisg> Usually people only need 1 chroot
[15:31] <alkisg> Not 2
[15:32] <alkisg> Let's continue troubleshooting from the local xterm
[15:32] <TheProf> OK.  Should I log in with the graphical prompt to run the xterm locally?
[15:33] <alkisg> Yes
[15:33] <TheProf> OK iu
[15:33] <TheProf> OK I'll go do that now.
[15:34] <TheProf> sorry I have to walk to another room to work on the thin clients.
[15:35] <TheProf> alkisg, I ran the command and it opened an xterm window
[15:35] <TheProf> where I was able to ls and see my files.
[15:35] <alkisg> Cool. Now there run: getltscfg -a
[15:35] <alkisg> And see if you get your lts.conf entries like before
[15:36] <TheProf> OK so from that prompt run getltscfg -a? Do I need to sudo?
[15:36] <alkisg> No
[15:36] <alkisg> (and yes to the first question)
[15:36] <alkisg> (no to sudo)
[15:37] <TheProf> OK :)
[15:49] <TheProf> alkisg, got an error that getltscfg is not installed and I need to install some sort of core utilities
[15:51] <alkisg> TheProf: is that still the local xterm?
[15:51] <alkisg> That you run with: ltsp-localapps xterm?
[15:51] <alkisg> That's very different than plain xterm or gnome-terminal, we don't want those
[15:52] <TheProf> yes that was in the ltsp-localapps xterm output window. I will go and try again to make sure.
[15:55] <alkisg> In the local xterm window, you should have getltscfg installed
[15:55] <alkisg> So you probably ran it in a "normal" , not "local" terminal
[16:00] <TheProf> alkisg, my apologies.  I had it in the wrong terminal as you surmized
[16:00] <TheProf> I got the same output as when I ran it locally on the server before.  Interestingly the first line is a commented out one "LDM_THEME="ltsp"
[16:02] <alkisg> Commented out? can you paste the whole line?
[16:03] <TheProf> http://pastebin.com/yShrkTmQ
[16:07] <alkisg> I don't see SCREEN_02 and SCREEN_07 there
[16:08] <alkisg> And yes, the comment does seem strange
[16:08] <alkisg> Are you sure you still have SCREEN_02 in your server lts.conf?
[16:11] <TheProf> alkisg, yes indeed it is there.
[16:12] <TheProf> do I need to rebuild the image after modifications to lts.conf? I thought that wasn't needed
[16:12] <alkisg> TheProf: ok, now again on the localxterm, do: cat /etc/lts.conf
[16:12] <alkisg> No, you don't need to update the image
[16:12] <TheProf> alkisg, ok i'll go try that now
[16:12] <alkisg> In that /etc/lts.conf, do you see SCREEN_02?
[16:12] <alkisg> TheProf: wait
[16:12] <TheProf> ok
[16:12] <alkisg> It's better to join irc from the client
[16:12] <alkisg> So that you don't go back and forth
[16:12] <alkisg> Here's a webpage for that:
[16:13] <alkisg> http://webchat.freenode.net
[16:13] <alkisg> You can join #edubuntu from there
[16:13] <TheProf> ok - wasn't sure in case i needed to reboot. website is a good solution
[16:13] <TheProf> going now
[16:16] <TheProf_client> Hello
[16:17] <alkisg> It should be easier to pastebin stuff now too :)
[16:17] <TheProf_client> Indeed! OK So I'm on the client.  Typing into the localapp xterm window "cat /etc/lts.conf" gives
[16:18] <TheProf_client> just pastebinning it
[16:19] <TheProf_client> OK stupid question: how do I copy text out of xterm?
[16:20] <alkisg> Select text in xterm
[16:20] <alkisg> Go to firefox and press middle click
[16:20] <TheProf_client> Fancy.
[16:21] <TheProf_client> http://pastebin.com/UnqLJJ0V
[16:22] <alkisg> Is this the same lts.conf that you have in your server?
[16:22] <TheProf_client> alkisg: yes it is.
[16:22] <alkisg> TheProf_client: so, you don't have SCREEN_02=shell
[16:22] <alkisg> Please put it
[16:23] <TheProf_client> wait! it's different
[16:23] <TheProf_client> That's the difference.
[16:23] <alkisg> TheProf_client: hmm ok, so now open a normal terminal, not a local one
[16:23] <alkisg> gnome-terminal
[16:23] <TheProf_client> I'm doing that right now to compare
[16:24] <alkisg> And from there, do:
[16:24] <alkisg> cat /var/lib/tftpboot/ltsp/i386/lts.conf
[16:24] <alkisg> and
[16:24] <alkisg> cat /opt/ltsp/i386/etc/lts.conf
[16:24] <alkisg> We're talking about 3 different lts.conf
[16:24] <alkisg> The 2 above, and the 1 you just pastedbin'ed from your client
[16:24] <alkisg> Which of those are the same?
[16:25] <TheProf_client> http://pastebin.com/j3UFFuwu
[16:25] <TheProf_client> that pastebin I just put in is the server's version of lts.conf
[16:26] <TheProf_client> this previous one http://pastebin.com/UnqLJJ0V is from the thin client ltsp-localapps xterm /etc/lts.conf
[16:26] <alkisg> OK, now check for the one in cat /opt/ltsp/i386/etc/lts.conf
[16:27] <TheProf_client> alkisg: OK checking now. The regular terminal on the server.
[16:28] <TheProf_client> http://pastebin.com/NUB1z51a
[16:28] <TheProf_client> that's the /opt/ltsp/i386/etc/lts.conf -- mostly empty
[16:28] <alkisg> TheProf_client: when you put SCREEN_02=shell in your lts.conf, did you reboot the client?
[16:30] <TheProf_client> alkisg: excellent question. I do not recall. I will reboot it now.
[16:31] <TheProf_client> alkisg: just rebooted a client.  No shell on F2, only F1
[16:31] <alkisg> TheProf_client: again open a local xterm, and again cat /etc/lts.conf
[16:31] <alkisg> And see if SCREEN_02=shell is there
[16:32] <alkisg> ltsp-localapps xterm
[16:33] <TheProf_client> OK trying this now
[16:34] <alkisg> (on the newly booted client of course, not the one you're chatting from now)
[16:34] <TheProf_client> yes :)
[16:35] <TheProf_client> so I did cat /etc/lts.conf after rebooting and local xterm and yes there is a "screen_02=shell" line
[16:36] <alkisg> Good, so we now that your clients do read lts.conf
[16:36] <alkisg> Now, on that newly booted client again, run: getltscfg -a
[16:36] <alkisg> And see if SCREEN_02 is there too
[16:37] <TheProf_client> screen_02=shell is there yes
[16:37] <TheProf_client> weird how that commented out line shows up also.
[16:38] <alkisg> TheProf_client: and you're sure that alt+ctrl+f2 doesn't work, right?
[16:39] <TheProf_client> Correct:  crtl+alt+F2 just a blank screen, same as F3 -> F6
[16:39] <TheProf_client> F1 gives shell, F7 gives graphical
[16:39] <alkisg> So it seems that getltscfg is having problems parsing your lts.conf
[16:39] <alkisg> Can you put it somewhere without using copy/paste?
[16:39] <alkisg> E.g. one way is this:
[16:39] <alkisg> On your server:
[16:39] <alkisg> sudo apt-get install pastebinit
[16:40] <TheProf_client> I think pastebin has a command line interface
[16:40] <alkisg> pastebinit /var/lib/tftpboot/ltsp/i386/lts.conf
[16:40] <TheProf_client> ah there we go :)
[16:40] <TheProf_client> OK
[16:41] <TheProf_client> sorry just a moment -- alternate user i'm using is not a sudoer
[16:42] <alkisg> su - otheruser
[16:44] <TheProf_client> http://paste.ubuntu.com/706222/
[16:45] <alkisg> Meh the same problem with paste.ubuntu again
[16:46] <alkisg> Try: pastebinit -b pastebin.com /var/lib/tftpboot/ltsp/i386/lts.conf
[16:46] <alkisg> Or: pastebinit -b http://pastebin.com /var/lib/tftpboot/ltsp/i386/lts.conf
[16:46] <alkisg> (not sure if it needs the http part)
[16:47] <TheProf_client> http://pastebin.com/2pR4mEhf
[16:49] <alkisg> TheProf_client: indeed it's a problem in getltscfg
[16:49] <alkisg> Let me pinpoint it...
[16:51] <TheProf_client> OK
[16:55] <alkisg> Hehe. It's silly. It has a problem because there's no newline at the end of the file.
[16:55] <alkisg> TheProf_client: please file a bug report in launchpad about it, and attach your lts.conf
[16:56] <alkisg> Then go to the last line and press enter so that it's fixed :D
[16:56] <TheProf_client> alkisg: sweet - I feel so special!
[16:56] <TheProf_client> So the enter at the end will allow the whole file to be parsed correctly?
[16:56] <alkisg> https://bugs.launchpad.net/ubuntu/+source/ltsp
[16:57] <alkisg> Yes, the problem is that now there's a " at the start and it causes a syntax error while evaluating it
[16:57] <alkisg> If you used vi you wouldn't have the problem :D
[16:57] <alkisg> (or gedit)
[16:58] <alkisg> Hmmmm but, I do see SCREEN_02 here
[16:58] <alkisg> While you didn't
[16:58] <TheProf_client> I use the built-in MC editor.
[16:58] <alkisg> Ah it was because you didn't reboot, ok
[16:58] <alkisg> The mc editor didn't append a newline at the end of the file
[16:58] <alkisg> And that confused getltscfg
[16:58] <TheProf_client> if I put 2 enters is that a problem? :) just to make sure :)
[16:58] <alkisg> Hehe sure
[16:59] <TheProf_client> :) rebooting client now
[17:01] <TheProf_client> Look at that! A different login screen!
[17:01] <alkisg> ...after 4 hours, a single enter did the trick ;)
[17:02] <TheProf_client> and when I log in it's no longer unity!
[17:02] <TheProf_client> that alone is worth the 4 hours :)
[17:02]  * alkisg is trying for 4 hours to get rid of unity in a standalone installation too
[17:03]  * TheProf_client loves that idea
[17:03] <alkisg> `gsettings set org.gnome.desktop.session session-name gnome-fallback ` unfortunately doesn't work
[17:04] <TheProf_client> I'm just rebooting the client attached to the printer to see if that will start working again also.
[17:06] <TheProf_client> ...and printing works.
[17:06] <TheProf_client> That enter really is picky!
[17:07] <alkisg> Meh. It looks like lightdm has the session hardcoded and ignores the user .dmrc and the gnome settings and everything
[17:08] <alkisg> s/hardcoded/in lightdm.conf/
[17:08] <TheProf_client> alkisg: Your help was invaluable.  I'm about to deploy 20 computers across several classrooms tomorrow and it would have been a major problem otherwise.
[17:09] <alkisg> You're welcome
[17:09] <TheProf_client> I have to get back to other school but my sincere thanks again.  Have a great day