[13:48] <dgroos> ping: alkisg
[13:48] <alkisg> Hey dgroos, what's up?
[13:49] <dgroos> alkisg: I'm trying to use sch-scripts and I get this error: http://pastebin.com/mFT4yfkz
[13:50] <dgroos> I'm guessing the prob. is that I'm not upgrading the client component (you fixed it last year to not update).  Any ideas?
[13:50] <alkisg> dgroos: what's the output of this? sudo pwck
[13:50] <alkisg> No it shouldn't be related to the client component (and also you didn't upgrade the server component too, right?)
[13:52] <dgroos> OK--only if sudo apt-get update/upgrading will do this.  Here's the output: http://pastebin.com/vJAVt8dp
[13:53] <alkisg> dgroos: fix the users that have invalid groups
[13:54] <dgroos> (I'm in the teacher's room right now and might have to leave at moments notice.)
[13:54] <dgroos> OK, will do.  I notice that it isn't listing all users?
[13:54] <alkisg> That command checks your /etc/passwd for errors
[13:54] <dgroos> ah...
[13:55] <dgroos> brb...
[13:55] <alkisg> And the last 5 lines say that you have users with invalid group numbers
[13:55] <alkisg> sch-scripts shouldn't crash from that; it should just display a warning
[13:56] <alkisg> ...or maybe one of the devs broke that line while splitting it to under 80 chars... let me see...
[14:00] <alkisg> Yeah. :( Unfortunately one junior dev decided to reformat the source code so that it fits in 80 columns, and he broke it in many places :(
[14:00] <alkisg> Please do this: sudo gedit /usr/lib/python2.6/dist-packages/schscripts/lib_users.py
[14:00] <alkisg> Remove those 2 lines:
[14:00] <alkisg>                 print " * I couldn't find user %s in shadow file. Are you " + \
[14:00] <alkisg>                     "root?" % (p.pw_name)
[14:00] <alkisg> And replace them with this line:
[14:01] <alkisg>                 print " * I couldn't find user %s in shadow file. Are you root?" % (p.pw_name)
[14:01] <alkisg> This way sch-scripts won't crash. You'll still get a warning though, as your /etc/passwd is broken.
[14:10] <dgroos> alkisg: thanks!
[14:10] <dgroos> All computers/login worked (first time full class using all computers)!
[14:11] <alkisg> How many?
[14:14] <dgroos> alkisg: working :D
[14:15] <dgroos> just 16--we've got 8 tables, 2 computers/table.
[14:15] <alkisg> Cool :)
[14:17] <dgroos> got a lot of lines in terminal after submitting the sudo sch-scripts command:
[14:17] <dgroos>  * I couldn't find user GCOS-ROOSEVELT\Administrator in shadow file. Are you root?
[14:17] <dgroos>  * I couldn't find user GCOS-ROOSEVELT\Guest in shadow file. Are you root?
[14:17] <dgroos> this pair of lines was repeated about 20 times.
[14:18] <dgroos> brb
[14:19] <alkisg> Ignore them, they're just warnings
[14:20] <alkisg> You're probably using something different than /etc/passwd for authentication. AD or LDAP maybe?
[14:20] <dgroos> mgariepy: FYI, adding the ";" did the trick! working great :D.
[14:20] <dgroos> alkisg: yes, LDAP authentication to the district AD server--took me a few days to get it to work, but it was worth it.
[14:21] <alkisg> Cool - just ignore the warnings then
[14:21] <dgroos> I'm wondering what ramifications it will have on everything, however.  Good to know I can ignore those comments.
[14:22] <alkisg> It's possible that it means that you haven't configured AD/LDAP 100% correctly, but as far as sch-scripts is concerned, sure, just ignore them
[14:28] <mgariepy> dgroos, nice :)
[15:51] <dgroos> Anyone using menueditor with lucid fatclients?  How's it working?
[15:52] <dgroos> ahhh... mgariepy = Marc Gar...
[15:52] <dgroos> didn't know that :)
[15:53] <dgroos> mgariepy: any thoughts on lucid + fatclients + menueditor?
[16:42] <mgariepy> dgroos, never tried that  but in theory it should work,
[17:10] <dgroos> mgariepy: How about a combination of any 2 of the 3? :)
[17:15] <mgariepy> dgross : https://launchpad.net/~menueditor-devel/+archive/backports
[17:15] <mgariepy> for the fat client you should ask alkisg
[17:20] <dgroos> I will, thanks, I think I'll post (repost?) to the user's list as well.
[17:20] <dgroos> gotta go
[17:21] <alkisg> mgariepy: how does the menu editor apply settings? where does it hook?
[17:21] <mgariepy> ok cya
[17:21] <mgariepy> extract the generated menu file from edubuntu-menueditor in a directory under /etc and add a file in /etc/desktop-profiles/
[17:28] <mgariepy> after that, there is a file desktop-profiles in /etc/X11/Xsession.d/20desktop-profiles_activateDesktopProfiles
[17:31] <alkisg> Ah, got it. So he could just transfer the configuration files in the chroot
[17:31] <alkisg> (another reason why being able to boot fat chroots read/write would be a handy idea)
[17:32] <mgariepy> would be great for image modification indeed
[17:33] <mgariepy> i use a configuration manager (bcfg2) to manage thin client chroot and it works great but it's not for everybody :)
[17:33] <mgariepy> it's not user friendly enough i guess
[20:03] <highvoltage> in my experience it works fine if you have an mgariepy around