[07:41] <KIAaze> hi, I just reconnected a machine to Ubuntu one, but the Ubuntu one folder already had contents (as the machine used to be connected last year or so), and now all of them are gone!
[07:41] <KIAaze> Does ubuntu one place contents somewhere else while it resyncs everything?
[07:41] <KIAaze> it's also a symbolic link to another folder
[07:42] <KIAaze> Can replacing ~/Ubuntu\ One with a symbolic link be problematic?
[07:43] <jgdx> Hi KIAaze, you should let us know through https://one.ubuntu.com/help/contact/ as well as hanging out here for a bit. :)
[07:43] <KIAaze> oh, ok, found the data again.
[07:44] <KIAaze> it's in my old home directory
[07:44] <KIAaze> I guess there's still a problem with dbus and stuff
[07:44] <KIAaze> the new home is correctly defined in /etc/passwd and the rest seems to work
[07:44] <KIAaze> at least the data is still there. Was a bit worried for a moment
[07:44] <jgdx> Ok. Regarding symlinks, see https://one.ubuntu.com/help/faq/does-ubuntu-one-support-symlinks-or-hard-links/
[07:49] <KIAaze> so what would ubuntu one do if I replaced ~/Ubuntu One with a symlink before starting U1?
[07:50] <KIAaze> also, where can I find info on debugging dbus/gnome. I think my home directory system might be a bit messed up at the moment.
[08:04] <jgdx> KIAaze: If you do not get a lot of responses here, the contact form is your best bet, I think.
[08:05] <KIAaze> that's ok
[08:05] <KIAaze> I completely removed all U1 packages and will try to fix dbus/gnome first
[08:06] <KIAaze> I had similar problems with other programs (virtualbox for example, which still refuses to use the new home for some reason)
[08:06] <KIAaze> at least now I know I can't use symlinks for U1
[08:08] <mandel> morning all!
[08:08] <KIAaze> I basically moved my home from an NFS network drive to the local PC, but still authenticate over the network. For some reason that seems to cause some problems with dbus.
[08:09] <KIAaze> morning :)
[08:17] <facundobatista> mandel et al, hola! I have a couple of client branches, if you're interested in a review (an easy and a not so easy one)
[08:17] <facundobatista> https://code.launchpad.net/~facundo/ubuntuone-client/plt-fixpath/+merge/124518
[08:17] <facundobatista> https://code.launchpad.net/~facundo/ubuntuone-client/fix-progress-events/+merge/124537
[08:17] <facundobatista> (thanks!)
[08:17] <mandel> facundobatista, sure, is my review day should I'll look at them right now :)
[08:17] <mandel> facundobatista, should you me in BA already?
[08:17] <facundobatista> mandel, *awesome*
[08:18] <facundobatista> mandel, yes, I'm back at home
[08:18] <mandel> facundobatista, then yo to bed, is way to late/early for you :)
[08:19] <facundobatista> mandel, early, just arrived, but if I go to bed now then I will not wake up
[08:19] <facundobatista> hey, I slept like 4 hours in the bus
[08:19]  * facundobatista is ready to rock (?)
[08:20] <mandel> facundobatista, yes, but in the bus, is not the same thing.. but try if you want :)
[08:32] <mandel> facundobatista, this one has a +1 https://code.launchpad.net/~facundo/ubuntuone-client/fix-progress-events/+merge/124537 the other I'll take longer to really understand all the changes
[08:34] <JamesTait> Hello, world! :)
[08:42]  * mandel reboot due to software upgrade
[08:57] <mandel> facundobatista, ping
[08:59] <facundobatista> mandel, pong
[08:59] <mandel> facundobatista, do you have a bug that describes what you are fixing the the plt?
[08:59] <facundobatista> mandel, kind of
[09:00] <facundobatista> the bug is not particular, and to actually fix the bug I need a second branch after this (splitted them because they were too many lines)
[09:00] <facundobatista> mandel, but I can explain you the situation
[09:00] <mandel> facundobatista, can you do that in the mp so that the next person can read it?
[09:00] <facundobatista> (and probably then paste these linees in the MP)
[09:00] <mandel> lol, ok I'll paste them :)
[09:01] <facundobatista> mandel, let me explain it here, and if it's clear enough I'll fix the MP
[09:01] <facundobatista> if it's not clear, just ask
[09:01] <mandel> ok, go ahead
[09:01] <facundobatista> so... the situation is the following, the PathLockTree locks operations on other operations regarding the path
[09:02] <facundobatista> if you touch a file 'foo', a MakeFile and Upload are queued, the Makefile will be executed, taking the lock on 'foo', the Upload will be locked because of the same path
[09:02] <facundobatista> when Makefile finishes, it releases the lock, the Upload jumps in, all happy
[09:03] <facundobatista> so, if you then do something like "ls > foo; mv foo bar"
[09:03] <facundobatista> syncdaemon will get the FILE_CREATE and CLOSE_WRITE and will queue the Makefile and actually send HQ to hash the file
[09:04] <facundobatista> the Makefile will be executed, taking the lock on 'foo'
[09:04] <facundobatista> of course, there's a move really fast after the CREATE and CLOSE
[09:04] <facundobatista> internal stuff is adjusted because of that move
[09:05] <facundobatista> milliseconds later, the HQ jumps in, and tries to hash 'foo', it gets an error because the file moved! so after that error the correct path is taken (MOVE adjusted internal stuff!), and finally HQ hashes 'bar'
[09:05] <facundobatista> when HQ finishes hashing bar, it queues an Upload
[09:05] <facundobatista> the Upload tries to get the pathlock on 'bar' and it succeeds!!!
[09:05] <facundobatista> because the Makefile was holding a lock on 'foo'
[09:06] <facundobatista> so the Upload jumps in, but out of order
[09:06] <facundobatista> so
[09:06] <facundobatista> the fix does the following
[09:06] <facundobatista> when the MOVE is processed by syncdaemon
[09:06] <facundobatista> it adjusts the path of PathLockTree, changing 'foo' to 'bar', there
[09:07] <facundobatista> so, the Upload will be locked
[09:07] <facundobatista> and that's all
[09:07] <facundobatista> it made me to change a little the internals of PathLockTree, but that's another more complex story
[09:07] <mandel> facundobatista, ok, makes sense
[09:13] <mandel> facundobatista, added this as a comment for the next guy
[09:14] <facundobatista> mandel, thank you very much!
[09:14] <mandel> facundobatista, no problem, I'll let you know if I have other questions, will let you know if there is a +1 :)
[09:14] <mandel> facundobatista, but first coffee hehe
[09:14] <facundobatista> :)
[10:18] <mandel> facundobatista, +1 with one small silly comment that does not block the branch, implement it if you think is a good idea :)
[10:18] <mandel> facundobatista, the rest does make sense
[10:19] <facundobatista> mandel, yes, probably those tests could have a little refactoring
[10:19] <facundobatista> they were just a few at the beginning, and then I keep adding and adding corner cases
[10:19] <mandel> facundobatista, :)
[10:20] <mandel> facundobatista, I know the feeling, I did the same with the filesystem_notifications
[10:36] <alecu> morning all!
[10:36] <alecu> hello mandel!
[10:37] <mandel> alecu, morning!
[10:37] <mandel> alecu, how is everything going?
[10:40] <alecu> mandel: sleepy!
[10:40] <alecu> mandel: got back from cordoba like an hour ago :-)
[10:42] <mandel> alecu, you and facundobatista are crazy, how was it?
[10:42] <mandel> alecu, shall we praise gatox organization skills?
[10:43] <alecu> mandel: sure! I love that gatox has really great taste to pick graphic designers
[10:44] <mandel> alecu, he does have some taste, yes :)
[10:44] <alecu> mandel: and the conference shirts were the best quality I had in any around here.
[10:44] <alecu> mandel: a metrosexual taste one could say
[10:44] <mandel> alecu, are there picts of the actual tees?
[10:46] <alecu> mandel: can't find any pics yet, we should ask gatox
[10:46] <alecu> mandel: but they had this logo big in the front: http://www.pydaycba.com.ar/
[10:46] <mandel> alecu, saw that one, it is really well done
[10:47] <mandel> alecu, and the page is 1000000 times better than the pycon ar one to be honest
[10:47] <alecu> mandel: I think you forgot a few zeros
[10:47] <mandel> alecu, probably, I should have use exponents
[10:48] <mandel> alecu, I have started proposing little bug fixes to unity so that we don't land in a big mp the ui for the payments stuff
[10:48] <alecu> mandel: that only means that gatox has good taste, and the current pyconar organizers do not. It applies to every bit of the conference, and it is so very obvious in that page.
[10:49] <mandel> alecu, it is very very obvious in that pages indeed
[10:49] <alecu> mandel: awesome! I'm reinstalling virtualbox, because the vm where I was developing with Q won't start again :-(
[10:49] <mandel> alecu, sorry to hear that :(
[10:50] <mandel> alecu, I have had tons of problems with the free drivers during the sprint and had to re-install the machine lots of times
[10:50] <mandel> I'm settled with the nvidia ones
[10:51] <mandel> alecu, have you heard anything about the team sprint? if it is during pycon ar I need to know so I can get some money back from my ticket to ar..
[10:56] <alecu> mandel: no, I have not heard anything else
[10:56] <alecu> mandel: we should ping ralsina and chipaca about that.
[10:57] <mandel> alecu, yes, I'm not a big fan of wasting money
[10:57] <ralsina> alecu, mandel: I have not heard either, but AFAIK it's that week. Should get final absolute confirmation today, tomorrow at the latest.
[10:57] <Chipaca> mandel: it is highly likely to be that week. Only way it wouldn't be is if there ins't a place for it. In london. During a recession.
[10:59] <mandel> Chipaca, ralsina, ok, let me know if I should cancel the tickets, I did take them with the possibility of canceling them
[10:59] <mandel> so not a huge deal if done with enough time
[10:59] <Chipaca> mandel: as soon as I know the place is confirmed, i'll let you know.
[11:00] <mandel> Chipaca, thx!
[11:01]  * alecu should find an insurance company that can provide a clone alecu to give his talks.
[11:02] <mandel> ralsina, 1-1 in a few mins over g+ hangout to show the progress of the payment preview?
[11:03] <mandel> ralsina, I just need to setup the g+ plugin
[11:10] <ralsina> mandel: I am leaving to take kid to school, so in 30'
[11:10] <ralsina> alecu: we should start asking to reschedule all our talks on saturday
[11:11] <mandel> ralsina, sure, no problem :)
[11:13] <alecu> ralsina: we have already warned the organizers about this possible problem. Their reaction (as usual) was to make the schedule public, so I don't care anymore :P
[11:16] <mandel> alecu, is up to them, did you mention all canonical people, or should I do it too?
[11:17] <alecu> mandel: we told the organizers that a lot of us would probably miss the conference.
[11:17] <mandel> alecu, can you merge lp:~mandel/avani/unity-lens-music.ubuntuone-purchase with yours? I have update some strings as per design requests
[11:18] <alecu> mandel: but they have a schedule and total lack of reasoning skills, so they went ahead and published the grid of talks.
[11:18] <gatox> good morning
[11:19] <alecu> mandel: so, they can do as they please. I promised earlier on the year that I just won't worry about this years pycon anymore.
[11:19] <mandel> alecu, fair enough, I'm not terribly worried
[11:19] <alecu> morning gatox!
[11:20] <gatox> alecu, hi.... what happend??
[11:20] <mandel> gatox, buenas!
[11:20]  * gatox is interested in the discussion
[11:20] <gatox> jeje
[11:20] <gatox> mandel, hellooo
[11:20] <mandel> gatox, we decided to kill you and feed you to the wolfs, that is all
[11:20] <gatox> mandel, i'm discovering that lately a lot of people have those plans
[11:20] <alecu> gatox: was telling mandel about how much I love this years' pyconar organizers.
[11:20] <gatox> :S
[11:21] <gatox> alecu, LOL :P
[11:21] <mandel> gatox, and praising your tests with designer ;-)
[11:21] <mandel> designers*
[12:15] <ralsina> I am going to give my talk on saturday at pycon but it's going to be like this, only backwards: http://www.youtube.com/watch?v=wyKBSy6rgdY
[12:16] <ralsina> alecu: it's ok, since gatox is organizing the next one, we can expect improvements! ;-)
[12:16] <gatox> ralsina, jeje you are mistaken sir :P
[12:17] <mandel> gatox, for president!
[12:17] <gatox> ralsina, if i organize a pycon.... i just day.... my ocd can't resist
[12:17] <gatox> just die
[12:17] <gatox> :P
[12:18] <ralsina> gatox: consider it shock therapy
[12:18] <gatox> jejeje
[12:19] <ralsina> gatox: like when monk got a job picking up garbage
[12:20] <mandel> uhhh monk, good guy :)
[12:25] <dobey> hmmm
[12:28] <mandel> ralsina, do you have time to do the 1-1 now?
[12:28] <ralsina> mandel: sure
[12:28] <ralsina> mandel: let me get my headser
[12:28] <ralsina> t
[12:28] <mandel> ralsina, g+ so that I can share the screen to show the progress
[12:28] <ralsina> sure
[12:30] <ralsina> mandel: invited you
[12:30] <mandel> ralsina, joining
[12:31] <mandel> ralsina, can you hear me?
[12:31] <ralsina> no
[12:31] <mandel> one sec
[12:32] <mandel> ralsina, lets try skype
[12:33] <mandel> ralsina, did you see anything?
[12:34] <mandel> ralsina, if you saw it we can move to mumble which seems to work better
[12:35] <ralsina> mandel: I saw it, let's mumble now
[12:35] <mandel> ralsina, yes, that does not seem to work well on my linux machine
[12:36] <ralsina> mine got incredibly slow
[12:36] <ralsina> still recovering load at 12
[12:37] <ralsina> ok mandel, waiting or you on mumble
[12:37] <mandel> ralsina, there in 1 min
[12:37] <mandel> or less
[12:54] <mandel> lunch time in spain
[13:44]  * mandel back
[13:44] <ralsina> mandel: please do that video and mail me + cparrino
[13:45] <ralsina> mandel: include all the explanations you gavemeabout the transition etc
[13:45] <mandel> ralsina, I was going to give them :)
[13:52] <dobey> so beta freeze is this week
[13:53] <ralsina> dobey: yep
[13:54] <chaselivingston> ralsina: how's darwin looking for a beta release?
[13:54] <chaselivingston> mmcc: ^^
[13:56] <ralsina> chaselivingston: I think we will delay it a week or two.
[13:56] <dobey> needs more evolution?
[13:56] <mmcc> chaselivingston: there are two bugs I'd like to squash before a beta - the one you and I saw with not syncing a dragged-in file, and the  quit problem (maybe)
[13:57] <ralsina> mmcc: I still want to try the "bigger hammer" approach to quiting ;-)
[13:57] <chaselivingston> mmcc: ok cool, fyi changing the name of that folder didn't force upload either
[13:58] <mmcc> chaselivingston: yes, I saw that email… :( if I could get your syncdaemon logs, that'd be handy
[13:58] <chaselivingston> mmcc: ok, i'll try to get those to you today
[13:58] <mmcc> chaselivingston: sure, whenever you can, thanks!
[13:58] <chaselivingston> mmcc: thanks!
[13:58] <mmcc> ralsina: remind me of the bigger hammer?
[13:58] <ralsina> mmcc: os.kill(os.getpid())
[13:59] <mmcc> ralsina: oh right :)
[13:59] <mmcc> ralsina: well, there's also the issue of how to catch cmd-Q, which still goes around our wrapper code, and is caught somewhere in our app even though we don't have a menu bar anymore
[14:00] <ralsina> mmcc: oh, ok :-(
[14:00] <ralsina> mmcc: I suspect OSX is just killing our process
[14:02] <mmcc> ralsina: it's got to be in Qt somewhere. the key event from cmd-Q isn't sent to the system, so if your app doesn't grab it, it'll get ignored. In our case we're just not grabbing it above Qt, I think
[14:03] <mmcc> In other news, Apple dev relations guy was less helpful than usual on my problem with the daemon installation / upgrade process.
[14:03] <mmcc> This is a problem because either upgrading just works or we need to add some notifications to the user that the job was removed but can't be installed until they quit and start over…
[14:04] <ralsina> mmcc: this may affect only you and mandel in the whole universe
[14:04] <ralsina> mmcc: unless this is about the busy file error?
[14:05] <mandel> why it would affect just us?
[14:05] <mmcc> ralsina: no, it's just if you have an old root daemon installed. It does only affect like four people right now, but as soon as we find a bug after a beta release, it affects everyone.
[14:06] <mmcc> mandel: because we were the only people with dev versions of the root daemon (us and a few other brave souls)
[14:06] <ralsina> mmcc: ok
[14:06] <mandel> oh, ok
[14:06] <ralsina> mmcc: so, this seems like a reasonably cmmon thing we are trying to do
[14:06] <ralsina> mmcc: just overwriting a running daemon. There must be some way to do it.
[14:07] <mmcc> ralsina: yes, doesn't it? the apple guy first said that the "install" routine should do an upgrade if you give it a daemon with a bumped version number, but it doesn't
[14:07] <chaselivingston> mmcc: just sent that log your way
[14:07] <mmcc> chaselivingston: great, thanks. can you tell me the name of the folder that didn't sync, too?
[14:07] <chaselivingston> sure, SOA Vocal
[14:08] <chaselivingston> mmcc: ^^
[14:08] <mmcc> chaselivingston: great, thanks!
[14:08] <chaselivingston> mmcc: np
[14:09] <ralsina> mmcc: could our daemon be ignoring SIGTERM?
[14:10] <ralsina> mmcc: the launchd docs suggest that we should "catch SIGTERM" because that's what launchd will use when it wants to stop it to install the new version
[14:11] <mmcc> ralsina: I think it's stopping it correctly, because I can remove it correctly with the "SMJobRemove" call. The problem is that if I do that remove, I can't subsequently call the "SMJobBless" function to install the new one
[14:11] <mmcc> I can do *just* remove or *just* bless but not remove then bless
[14:11] <ralsina> mmcc: grmbl
[14:11] <mmcc> ralsina: seriously
[14:12] <ralsina> mmcc: I believe you!
[14:12]  * dobey wonders what to do about these icons
[14:13] <ralsina> dobey: saw my email?
[14:13] <dobey> yes
[14:13] <ralsina> dobey: chase marcus and see if we can get them fast. If we can't, then I need to say "we can't do it because we don't have the right sizes"
[14:14] <ralsina> mmcc: the thing is blessing's whole point is to keep the app drag-installable :-(
[14:14] <dobey> well, we can ship the sizes we're shipping already in ubuntuone-client; but then that's basically no change
[14:15] <mmcc> ralsina: yeah, it's frustrating. one "workaround is to call remove then tell
[14:15] <ralsina> dobey: don't follow. The icon looks different
[14:15] <mmcc> er, then tell the user to quit and restart U1, so it'll go ahead and install the new one
[14:15] <dobey> ralsina: looks different than what?
[14:15] <ralsina> dobey: than what we are shipping now?
[14:16] <dobey> ralsina: the -music icon is, but the ubuntuone icon is exactly the same, save for that 128x128 version, which we aren't shipping, because the "large" size to ship on Ubuntu is 256x256
[14:16] <dobey> which i've tried to ask for many times, but alas
[14:16] <ralsina> dobey: sigh
[14:17] <ralsina> dobey: ok, so let's ask marcus for the 256x and then we have a bit more time to get the other sizes
[14:22] <dobey> ralsina: do you know what the -music icon is supposed to be used for exactly?
[14:22] <dobey> or should we poke the uppers?
[14:22] <ralsina> dobey: the music store webapp
[14:23] <dobey> and not the rhythmbox plug-in?
[14:23] <ralsina> dobey: that one I am not sure
[14:23] <ralsina> dobey: so let's ask
[14:24] <ralsina> dobey: asking right now, will keep you posted
[14:24] <dobey> ah ok
[14:24] <dobey> thanks
[14:24] <ralsina> dobey: just the webapp
[14:25] <dobey> great
[14:25] <dobey> that does simplify the situation a little :)
[14:26] <mandel> ralsina, uploading the screencast to u1 and will send the email shortly
[14:26] <ralsina> mandel: awesome
[14:26] <ralsina> dobey: hehe yeah
[14:28] <dobey> alright; i'll poke about in inkscape and see if i can get something usable and quick.
[14:29] <ralsina> dobey: great, thanks
[14:40] <mmcc> ping chaselivingston - that log file is too new - it doesn't show that folder. can you send me the other files too? same path, syncdaemon.log.2012-09-* -- might want to zip them…
[14:40] <chaselivingston> mmcc: sure, one moment
[14:43] <chaselivingston> mmcc: sent
[14:43] <mmcc> chaselivingston: great, thanks again
[14:43] <chaselivingston> mmcc: np
[14:54] <mandel> ralsina, can you confirm me you got the mail with the video and that it works?
[14:57] <joshuahoover> ralsina, gatox: do you have an updated estimate on when our integration with the sync indicator will land in q? bug #1042343
[14:58] <gatox> joshuahoover, i'm finishing with that branch in order to propose it
[14:58] <gatox> i found some problems that i'm taking care of so everything works ok
[14:58] <joshuahoover> gatox: thanks
[14:58] <joshuahoover> dobey: are you doing a package of u1-client this week?
[14:59] <dobey> yes
[15:00] <mandel> me
[15:00] <gatox> me
[15:00] <briancurtin> me
[15:02] <dobey> me
[15:02] <thisfred> me
[15:02] <dobey> joshuahoover: plan is to do it today
[15:02] <joshuahoover> dobey: awesome, thanks :)
[15:02] <ralsina> otp, skipping
[15:03] <alecu> me
[15:03] <gatox> mandel, go
[15:04] <mandel> DONE: Sprint with the dx team to get the dash 'ready' to show payment previews. Recorded video for ralsina and cparrino with the current status.
[15:04] <mandel> TODO: Fix several ui issues with the preview, mainly make buttons be links and check with design the size of the fonts (they seem to be too big). Catch up with alecu to see where we are in the payment back-end story. Propose small fixes to unity so that our payment mp is not HUGE.
[15:04] <mandel> BLOCKED: no, but it seems I have compiling errors in one of my machines.. strange.
[15:04] <mandel> gatox, please
[15:04] <gatox> DONE:
[15:04] <gatox> Worked in the sync menu for u1-client, found some problems where the menu didn't work properly, fix them.
[15:04] <gatox> TODO:
[15:04] <gatox> Finish updating the tests. Propose.
[15:04] <gatox> BLOCKED:
[15:04] <gatox> No
[15:04] <gatox> briancurtin, go
[15:04] <briancurtin> DONE: more fiddling with tests
[15:04] <briancurtin> TODO: extra header tests, probably need to change dev-tools server impl
[15:04] <briancurtin> NEXT: dobey
[15:04] <dobey> DONE: reviews, poked more at webapps, bug #1034092, bug #1051025
[15:04] <dobey> TODO: releases, new old icons, webapp packaging
[15:04] <dobey> BLCK: None.
[15:04] <dobey> thisfred: go
[15:04] <thisfred> oops
[15:05] <thisfred> DONE: playlist metrics TODO: playlist migration code, BLOCKED: no NEXT: alecu
[15:05]  * thisfred fail
[15:06] <ralsina> thisfred: I'll let it pass because I am skipping ;-)
[15:06] <alecu> DONE: started with adding error handling to purchases
[15:06] <alecu> TODO: handle more errors, add some tests
[15:06] <alecu> BLOCKED: no
[15:06] <mmcc> oh shoot
[15:07] <mmcc> DONE: daemon upgrade battle
[15:07] <mmcc> TODO: daemon event processing bug with move, for real this time
[15:12] <dobey> gatox: is any of that sync indicator code in trunk yet?
[15:12] <gatox> dobey, noy in trunk..... i'm fixing the last stuff to propose it
[15:12] <gatox> not in trunk
[15:13] <dobey> ok
[15:13] <dobey> joshuahoover: i think you mistook my "yes i plan to make a release today" as "and it will include that code" :)
[15:14] <joshuahoover> dobey: heh, well, there's that
[15:14]  * mandel broke compiz again...
[15:15] <mandel> I need to try and fix it, will try to be fast :-/
[15:18] <ralsina> have to change location, will be back in a few minutes
[15:25] <dobey> ok, need to get lunch. bbiab
[15:27] <chaselivingston> mmcc: any luck w/ those older logs
[15:31] <mmcc> chaselivingston: no, the path you mentioned didn't show up there. but it's ok, i have a log where I saw the problem and I think I should be able to reproduce it too
[15:31] <chaselivingston> mmcc: ok, maybe it would help if i told you the path was /ubuntu one/sumsix/soa vocal?
[15:31] <mmcc> chaselivingston lowercase?
[15:32]  * mandel unlocked a new achievement, fix compiz 50 times!
[15:32] <chaselivingston> mmcc: no, sorry. /Ubuntu One/SumSix/SOA Vocal
[15:39] <mandel> I need to do some quick errand, I'll be back in 15 mins
[16:13]  * mandel back
[16:24]  * alecu will have lunch
[16:31] <chaselivingston> mmcc: now that folder seems to be uploading, change something on your end somehow?
[16:31] <mmcc> chaselivingston: no, did you restart the app?
[16:32] <chaselivingston> mmcc: yes, but i tried that before w/ no luck. seems to have worked this time
[16:32] <mmcc> chaselivingston: when you restart the syncdaemon, it does a full local re-scan and that should pick up anything that isn't synced.
[16:32] <chaselivingston> mmcc: ah ok, guess that's what happened
[16:33] <mmcc> chaselivingston: maybe your previous restarts didn't restart syncdaemon. if you did cmd-q instead of using the 'quit' menu item in the red u1 menu on the right of the menu bar, it might not have killed syncdaemon
[16:33]  * gatox lunch
[16:33] <chaselivingston> mmcc: gotcha, could very well be the case
[16:34] <mmcc> chaselivingston: also for future reference, there's nothing I can change that'd cause that kind of behavior change in the client. once I package the app ,the client code is frozen (it's even cryptographically signed)
[16:35] <chaselivingston> mmcc: cool, that's what i figured, just wasn't sure
[16:35] <mmcc> yep. no magic upgrades. it's good and bad :)
[16:35] <chaselivingston> mmcc: haha, i bet
[16:39] <mmcc> mandel | ralsina - a trivial review: https://code.launchpad.net/~mikemc/ubuntuone-client/fsevents-daemon-default/+merge/124738
[16:40] <mandel> ok
[16:45] <mandel> mmcc, approved
[16:46] <mmcc> thanks mandel
[16:46] <mandel> mmcc, what was wrong with the ipc?
[16:47] <mmcc> mandel: the code expected to be able to get the path from the file descriptor, but the fd that launchd gives you gives you an error when you do that
[16:47] <mandel> mmcc, ah, bummer.. how did you solve it?
[16:47] <mmcc> it doesn't need the path when it's launchd, so I just set the sockURL=nil
[16:48] <mmcc> the problem was that if it couldn't find the path, it bailed and didn't init any of the other data structures (but nothing was checking that)
[16:48] <mmcc> so there was a commsocketserver sitting there with all nil members, and sending messages to nil does nothing, so nothing was happening
[16:49] <mandel> mmcc, uh, well I never tested that case..
[16:49] <mandel> mmcc, nice find!
[16:50] <mandel> and with those great news, I'm EODing!
[16:50] <mmcc> yeah, it's hard to test until you have all the launchd crap hooked up.
[16:50] <mmcc> ttyl!
[17:08] <gatox_lunch> everyone, ralsina says that he is having problems with his internet connection, he is going to try to be back as soon as possible
[17:14] <dobey> gatox: *gasp* *surprise* :)
[17:17] <mmcc> clearly someone needs to confront ralsina about his pinball addiction
[17:17] <dobey> heh
[17:20] <ralsina> I'm back
[17:21] <ralsina> dobey: I am changing ISPs but it's going to take a while. I am considering if starting my own ISP company is faster :-/
[17:22] <dobey> hehe
[17:22] <dobey> i'm wondering why there is a shadow around the entire surface of this icon, and why it's trying so hard to look 3d
[17:32] <ralsina> mmcc: what day next week do you think would be a good day for a QA run?
[17:32] <mmcc> ralsina, monday
[17:33] <ralsina> mmcc: are we confident today? :)
[17:33] <mmcc> ralsina: I just fixed the upgrade problem, so yes, a little confident. Today I am a viking!
[17:33] <ralsina> mmcc: ok, tuesday it is ;-)
[17:34] <mmcc> :D sounds good
[18:18] <dobey> ralsina: hrmm, so i have all the <= 128x128 sizes "ready" at least, but the 128x128 is a bit more complicated than i was hoping it would be, so probably best if i don't try to tweak it into the larger sizes, since while I'm ok at making icons, i'm not that great, and i don't know what any of the branding specifics are :)
[18:18] <ralsina> dobey: ok
[18:19] <dobey> ralsina: so i guess we just wait and hope marcus replies in the morning (preferably with icons)?
[18:19] <ralsina> dobey: so, I got no response about the request from marcus, and now it's too late for him anyway
[18:19] <dobey> right
[18:19] <ralsina> dobey: so yes, that's the "plan"
[18:19] <dobey> ok, i'll hold off doing an ubuntuone-client release until tomorrow
[18:19] <dobey> and try to get some of the others done today
[18:19] <ralsina> dobey: cool.
[18:20] <dobey> and see about merging some of these translations in to our trunks
[18:55] <mmcc> do we have a test case base class that makes recording calls to multiple functions easy?
[18:56] <mmcc> I mean multiple patched functions…
[18:56] <dobey> not in dev-tools
[18:56] <mmcc> ok, thanks
[18:58] <ralsina> mmcc: no, I have seen a couple of cases that add a homebrew set_called clone in the test
[19:06] <dobey> ralsina: want to do some rubber stamping? :P
[19:06] <dobey> https://code.launchpad.net/~dobey/ubuntu-sso-client/update-po/+merge/124769
[19:06] <ralsina> dobey: have it right here!
[19:06] <dobey> https://code.launchpad.net/~dobey/ubuntuone-client-gnome/update-po/+merge/124770
[19:06] <dobey> https://code.launchpad.net/~dobey/ubuntuone-client/update-po/+merge/124771
[19:12] <ralsina> dobey: done!
[19:13] <dobey> thanks
[19:13]  * ralsina blows on smoking rubberstamp, cowboy-style
[19:19] <dobey> ralsina est gaucho?
[19:20] <ralsina> dobey: gauchos were more of a knife people
[19:20] <ralsina> And blowing on knifes is silly and dangerous ;-)
[19:21] <dobey> ralsina: another review for you: https://code.launchpad.net/~dobey/ubuntuone-client/drop-vapi/+merge/124774
[19:21] <dobey> a little actual review this time :)
[19:28] <ralsina> dobey: +1
[19:29] <mmcc> hey guys, I found this old bug that wasn't linked to the branch that fixed it - I linked it but I'm not sure how to close it and flip all the right switches: https://bugs.launchpad.net/ubuntuone-control-panel/+bug/1040727
[19:29] <mmcc> I did change the status, but is there more to do? also, this isn't high priority, just saw the browser tab now
[19:30] <ralsina> just set it to fix-committed
[19:30] <mmcc> ok, done then
[19:30] <ralsina> or even fix-released if it's in trunk for more than one week
[19:31] <mmcc> ok - did that. that was the step I was wondering about, when /how to set it to released
[19:31] <mmcc> by how, I meant if it was automatic somewhere
[19:33] <ralsina> mmcc: if the bug is linked to the branch, and targeted to the right branch (which this probably wasn't) then it will get flipped to fix-released when ... well, released
[19:33] <ralsina> mmcc: just linking the branch will make it fix-committed when the branch is merged to trunk
[19:34] <mmcc> I knew the fix-committed step (this bug wasn't linked when the branch was merged, so it was floating lost)
[19:35] <mmcc> still fuzzy on the mechanics of 'released' though. but that's probably ok
[19:35] <dobey> ralsina: linking the branch from the lp ui doesn't do anything to the branch
[19:35] <dobey> or to the bug, aside from just noting the link
[19:35] <ralsina> dobey: but tarmac marks it?
[19:35] <dobey> tarmac does if the link is done with bzr commit --fixes
[19:36] <dobey> but not if it was just linked on the lp UI
[19:36] <ralsina> dobey: I always assumed that was the same thing as doing it from LP!
[19:36] <dobey> nope
[19:36] <ralsina> dobey: corner cases for everyone! ;-)
[19:36] <dobey> bzr puts it in the branch metadata, LP just has it in the LP db
[19:36] <dobey> and anyone can link any bug to any branch on LP
[19:37] <dobey> with the bzr metadata, we can at least trace it to someone, if they got it wrong or tried to abuse the system :)
[19:37] <ralsina> dobey: if random people were actively trying to make things annoying for us on LP, they could drown us in stuff in 5 minutes :-(
[19:38] <dobey> they do; have you seen how many bug reports we have? :)
[19:39] <ralsina> dobey: hha
[19:39] <dobey> i want to automate a bunch more stuff, but it will take a *lot* of work to do :(
[19:39] <ralsina> dobey: those meant well
[19:39] <ralsina> dobey: I mean, we have had a couple of cases of people randomly changing bug state for instance
[19:39] <dobey> yeah
[19:39] <ralsina> dobey: if someone started doing that intentionally, it would be hell
[19:40] <dobey> a lot of those are accidental, thanks to the wonders of javascript
[19:40] <ralsina> ok, my ISP claims they are at my house's door with tools and equipment
[19:40] <dobey> heh
[19:40] <ralsina> I have to go there I suppose
[19:41] <ralsina> and this mail order gunsmith never delivers in time!
[19:42] <chaselivingston> mmcc: any idea when i might have a new build to try that fixes the events triggers issue?
[19:42] <ralsina> hopefully, will be back in 30'
[19:43] <mmcc> chaselivingston: no estimate yet. I'm adding tests to the code to upgrade the running daemon. I've looked at the events trigger issue but haven't started trying any fixes yet
[19:44] <chaselivingston> mmcc: cool, just curious, thanks
[19:44] <mmcc> chaselivingston: I'd say optimistically tomorrow, maybe wednesday for a fix
[19:44] <mmcc> this is where ralsina chimes in and adds 30%, or 2x, or something :)
[19:44] <chaselivingston> mmcc: ack, thanks. in the meantime, if i kill sd via activity monitor, will u1 automatically spawn a new instance and do a global scan again?
[19:46] <mmcc_> chaselivingston: it *should* if the control-panel app is running. it definitely will if you quit the control-panel, kill sd, and restart the control-panel
[19:46] <chaselivingston> mmcc_: gotcha, that works for me, thanks
[20:16] <gatox> eod here! time to rest, see you tomorrow people! bye
[20:26] <dobey> can someone review? https://code.launchpad.net/~dobey/ubuntuone-client-gnome/update-4-0/+merge/124787 it's all translations updates merged from trunk, so just a quick look and rubber stamp is fine
[20:35] <briancurtin> dobey: approved
[20:35] <dobey> thanks briancurtin
[20:54] <mmcc> lunch…
[21:00]  * alecu needs to EOD too
[21:00] <alecu> bye all!
[21:19] <dobey> doh
[21:35] <dobey> ok all, have a good evening. i'm off
[23:17] <mmcc> ok, done for now, going to come back tonight and finish this daemon install branch's tests…


[01:52] <istvanchung> hey, anyone in ubuntu bug control: bug #694644 (https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/694644) should be set to medium-importance
[01:52] <ubot2> istvanchung: Bug 694644 on http://launchpad.net/bugs/694644 is private
[01:52] <ubot2> Launchpad bug 694644 in python-pip (Ubuntu) "package python-pip 0.3.1-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/bin/pip', which is also in package pip 0:0.13-1 (affects: 1) (heat: 6)" [Undecided,Confirmed]
[06:34] <Yuhong> I mistakenly set this bug to Fix Released: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/455067
[06:34] <ubot2> Launchpad bug 455067 in linux (Ubuntu) "[113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x10000004 (affects: 4) (heat: 24)" [Undecided,Fix released]
[06:34] <Yuhong> Can anyone change it back to in progress?
[06:34] <Yuhong> I mistakenly set this bug to Fix Released: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/455067
[06:34] <Yuhong> Can anyone change it back to in progress?
[06:35] <yofel> Yuhong: are you working on this?
[06:36] <Yuhong> Nope. but read the bug in detail.
[06:37] <Yuhong> Until Bug #686158 is resolved, this should not be set to Fix Released, but I did it by mistake.
[06:37] <ubot2> Launchpad bug 686158 in linux (Ubuntu) "Maverick update to <IP_ADDRESS> stable release (affects: 1) (heat: 230)" [Undecided,New] https://launchpad.net/bugs/686158
[06:38] <yofel> Yuhong: sure, but it shouldn't be In Progress either until someone works on it
[06:39] <yofel> I'll expire it again since the information requested by jfo still wasn't added
[06:39] <Yuhong> But I know it will be fixed when bug 686158 is fixed.
[06:39] <ubot2> Launchpad bug 686158 in linux (Ubuntu) "Maverick update to <IP_ADDRESS> stable release (affects: 1) (heat: 230)" [Undecided,New] https://launchpad.net/bugs/686158
[06:40] <yofel> Yuhong: ok, but is anyone working on 455067 currently? That's what In Progress means, nothing else
[06:41] <Yuhong> I'm not sure, I will have to probably ask the kernel team.
[06:41] <yofel> Yuhong: please see https://wiki.ubuntu.com/Bugs/Status
[06:41] <Yuhong> Thanks.
[06:41] <yofel> Yuhong: as well as https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
[06:43] <Yuhong> How about changing it back to New?
[06:43] <Yuhong> I will post a link to the bug at bug 686156.
[06:43] <ubot2> Launchpad bug 686156 in gnome-session (Ubuntu) "[COSMETIC] shutdown conflict dialogue shows "Untitled window" in task bar (affects: 1) (heat: 246)" [Undecided,New] https://launchpad.net/bugs/686156
[06:43] <yofel> Yuhong: please add the information requested in #7 and that can be done
[06:44] <yofel> it's david that should do this though
[06:44] <Yuhong> Yep, I can't do it.
[06:44] <Yuhong> http://lkml.indiana.edu/hypermail/linux/kernel/1009.2/03143.html
[06:46] <Yuhong> Well, you see, bug 455067 will be resolved as a side effect of resolving bug 686158. What to do in this case?
[06:46] <ubot2> Launchpad bug 455067 in linux (Ubuntu) "[113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x10000004 (affects: 4) (heat: 24)" [Undecided,Expired] https://launchpad.net/bugs/455067
[06:46] <ubot2> Launchpad bug 686158 in linux (Ubuntu) "Maverick update to <IP_ADDRESS> stable release (affects: 1) (heat: 230)" [Undecided,New] https://launchpad.net/bugs/686158
[06:46] <yofel> not sure, I don't touch kernel bugs usually, either ask JFo when he's here or in #ubuntu-kernel
[06:47] <Yuhong> But Fix Released is certainly not the right status.
[06:48] <Yuhong> And I can't changed it to any other status since I don't have right privileges.
[06:49] <Yuhong> Very poor design IMO.
[06:50] <yofel> Yuhong: well, kernel bugs need to follow https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies - and according to that the bug can only be set to Incomplete, which will turn into Expired after a whlie
[06:50] <yofel> *while
[06:51] <Yuhong> But the poor design about is that it lets an user change status to Fix Released without any warning, but can't change it back.
[06:52] <yofel> that's deliberate, maybe a warning could be added though
[06:52] <yofel> it wasn't like that in the past, bug we had too many users mistakenly reopnening bugs so it was locked to bug supervisors
[06:53] <yofel> Yuhong: if you want you can file a bug at https://bugs.launchpad.net/launchpad/+filebug for a warning to be added there
[06:54] <Yuhong> Ok.
[10:08] <njin> please set importance hight to bug 694267
[10:08] <ubot2> Launchpad bug 694267 in unity (Ubuntu) "Unity Panel is not maintaining Single instance (affects: 2) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/694267
[14:42] <xteejx> bug 603385 - the retracer dosen't seem to be doing anything with it, any ideas/help?
[14:42] <ubot2> xteejx: Bug 603385 on http://launchpad.net/bugs/603385 is private
[14:48] <xteejx> I've added the need-i386-retrace tag to the bug report, hopefully apport-retracer will pick it up
[14:49] <charlie-tca> Won't let me see it, but retrace is not doing anything to 9.04 now
[14:51] <xteejx> charlie-tca: It's a maverick bug
[14:52] <xteejx> I think maybe there was a glitch somewhere there were no tags that apport usually puts on the report
[14:52] <charlie-tca> could be, if the reporter did file it with apport
[14:56] <xteejx> It was me,  and it was a standard apport crash, so I would've done the usual bug filing
[14:57] <xteejx> I guess I'll find out in a few hours if adding that tag has nudged it :)
[14:57] <xteejx> PS Merry Xmas and a happy New Year all :)
[16:24] <hggdh> anyone trying to install the current ISO for Natty?
[16:27] <hggdh> charlie-tca: ^
[16:28] <hggdh> and good morning ;-)
[16:31] <charlie-tca> good morning. Which one?
[16:31] <charlie-tca> alternate image is still looping back to the beginning
[16:31] <charlie-tca> desktop just installed
[16:32] <hggdh> I was trying the server ISOs, what I see is a sudden reboot in the middle of the base install
[16:32] <hggdh> repeated on bare metal and libvirt
[16:32] <charlie-tca> you made it that far? Mine are rebooting during partitioning
[16:32] <hggdh> oh, so you do see a reboot
[16:33] <hggdh> have a bug on it?
[16:33] <charlie-tca> and it affects both Ubuntu and Xubuntu
[16:33] <charlie-tca> alternate 386 and amd64
[16:33] <charlie-tca> been doing it for a week
[16:33] <hggdh> all reboot during partitioning?
[16:33] <charlie-tca> yup
[16:33] <hggdh> darn!
[16:34] <hggdh> mine consistently reboot *after* partitioning, on base system install
[16:34] <charlie-tca> and I have been trying to find someone else experiencing it, but no one seems to be testing the images
[16:34]  * hggdh is
[16:34] <hggdh> hum
[16:34] <hggdh> under which package you reckon we should have the bug?
[16:34] <hggdh> I am unsure here
[16:34] <charlie-tca> Is it still debian-installer?
[16:35] <hggdh> on alternate, I think yes
[16:35] <hggdh> for the server, certainly
[16:35] <charlie-tca> that would be the package, then.
[16:35] <hggdh> I will open one under d-i, then, and mark critical
[16:35] <charlie-tca> I will confirm it
[16:36] <hggdh> k, just a few min for me to open it
[16:36] <charlie-tca> I have asked in #ubuntu+1 and #ubuntu-testing both for confirmation, but no one has run the images
[16:43] <hggdh> charlie-tca: bug 694772
[16:43] <ubot2> Launchpad bug 694772 in debian-installer (Ubuntu) "Sudden reboot during server ISO install (affects: 1) (heat: 6)" [Critical,New] https://launchpad.net/bugs/694772
[16:44] <hggdh> so there are only both of us running tests now...
[16:44] <charlie-tca> near as I can tell. Maybe the hardware center is only running the desktop image?
[16:45] <hggdh> perhaps... IDK, but I was expecting them to be running the full gamut
[16:45] <charlie-tca> me too. I run them on Xubuntu, and if it fails, run Ubuntu
[16:48] <hggdh> but the desktop install succeeds, correct?
[16:51] <c2tarun> can anyone please look at bug 694776. I think its a wishlist. If so then can anyone please mark it as wish list.
[16:51] <ubot2> Launchpad bug 694776 in gnome-panel (Ubuntu) "On desktop, rightclick on DVD icon, clicking unmount, disables the DVD Drive (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/694776
[16:54] <charlie-tca> hggdh: yes, desktop installs are working
[16:54] <hggdh> c2tarun: why did you mark it as Opinion?
[16:54] <charlie-tca> c2tarun: that should be a duplicate
[16:55] <charlie-tca> I might be wrong, though
[16:55] <c2tarun> Sorry it was by mistake :(
[16:55] <c2tarun> What should I do on this bug>
[16:57] <c2tarun> \
[17:00] <c2tarun> charlie-tca: i think its not a duplicate
[17:01] <charlie-tca> okay, 2nd question: If it is clicking on desktop, why is the package "gnome-panel"?
[17:01] <charlie-tca> 3rd question: Does a restart let it work again? or is the only way to make it work again to remount the drive?
[17:02] <c2tarun> charlie-tca: oh! :P so its an invalid or incmplt bug
[17:02] <charlie-tca> 4th question: What does "unmount" mean if it does not mean unmount the drive? Is there an "eject" also, or did unmount replace it?
[17:03] <charlie-tca> 5th question:  What if you click unmount in places instead of the desktop?
[17:03] <charlie-tca> doesn't really seem triaged to me
[17:04] <c2tarun> actually i was trying to get these points ;) thnks 4 help
[17:10] <hggdh> c2tarun: another point, please always add a comment on why you set a Status
[17:11] <c2tarun> hggdh: sure. from next time i'll
[17:11] <hggdh> c2tarun: NP, and thank you for helping
[20:32] <psusi> does bug #694831 look like a good candidate for convert to question?
[20:32] <ubot2> Launchpad bug 694831 in ubuntu "log out/chat button on top right corner on the panel isn't there anymore (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/694831
[20:39] <charlie-tca> Has that button been replaced now? what version of Ubuntu is that?
[20:39] <charlie-tca> It is not really a question. If the button has been removed, it is probably a design change.
[20:40] <charlie-tca> Unfortunately, without knowing what release the reporter is using, it is not really possible to do much.
[20:41] <penguin42> hmm, that's twice exaile has crashed in the last half hour, hasn't done that in months - I wonder what changed
[20:41] <charlie-tca> we don't know if the button disappeared during an upgrade, running updates, new installation of new release, etc.
[20:44] <psusi> charlie-tca: it sounds to me like "help, I removed my pannel, how do I get it back"
[20:45] <charlie-tca> Is it the whole panel, the indicator app, or something else?
[20:46] <charlie-tca> do you know?
[20:46] <charlie-tca> We don't start triaging by trying to guess what the reporter means, we ask questions to find out
[20:47]  * penguin42 plugs his USB crystal ball in
[20:47] <micahg> All signs point to unsure :)
[20:48] <psusi> charlie-tca: sounds like the indicator app to me
[20:48] <charlie-tca> Do not guess
[20:48] <charlie-tca> please ask the reporter for more information.
[20:48] <psusi> k
[20:49] <charlie-tca> You also think he lost the whole panel. you can not guess at what any report really means. You have to ask question of the reporter to find out,.
[20:51] <psusi> no... just the indicator app.. at least I think that's the one that provides the buttons he is talking about
[20:53] <charlie-tca> hm, Please read https://wiki.ubuntu.com/Bugs/HowToTriage for information
[20:53] <charlie-tca> Also, https://wiki.ubuntu.com/Bugs/Responses helps a lot when triaging
[20:55] <psusi> ahh, it has been updated to cover questions.... sure sounds like this is a #4 to be, but I suppose it wouldn't hurt to confirm first
[20:55] <charlie-tca> If something disappeared, that is a bug unless it is a deliberate design decision to change it. The reporter did not ask a question.
[20:58] <psusi> he didn't say this happened when he upgraded or something.. I'm assuming not or he would have said so, but sure, it doesn't hurt to ask
[22:27] <BUGabundo> yo


[02:03] <pianonut> This is my maiden voyage into the world of instant messaging & I have no idea how the system works.
[02:03] <pianonut> I installed the deb package for xchat-gnome, then xchat and I seem to be broadcasting to this group right now.
[02:03] <pianonut> Is that correct?
[02:04] <pianonut> I take it other listeners are informed somehow by their system when a new message has been posted.
[02:05] <pianonut> Then they may choose to look at the new input or not.  If they do look at the new message, they may or may not respond.  Right?
[03:22] <sbalneav> Evening all
[03:23] <sbalneav> pianonut: We see what you type
[03:23] <sbalneav> And you see what we type :)
[03:33] <pianonut> That part I know.
[08:30] <Tirion> Hello! Did anyone have expiriense with LTSP5 in Edubuntu Gutsy?
[08:31] <Burgundavia> not in gutsy, but I have played with LTSP
[08:31] <Burgundavia> what is your issue?
[08:33] <Tirion> I just plan to use it. Will it work correctly with Xeon Quad core?
[08:34] <Burgundavia> that is a kernel issue. If Ubuntu/Edubuntu runs correctly on it without LTSP, it will work find with it
[08:38] <Tirion> And one more question. Thin clients need a RAM, isn't it?
[08:38] <Burgundavia> yes, due to the applications they are running
[08:39] <Burgundavia> basically, the more RAM the happier you are as a person, but then your server isn't swapping
[08:46] <Tirion> Thank you, Burgundavia
[11:30] <RichEd> hi ogra_cmpc
[11:30] <ogra_cmpc> hey
[11:31] <RichEd> just checked my tavel details ... 29h30 from my house to boston
[11:31] <ogra_cmpc> eeek
[11:31] <ogra_cmpc> mine must be below 13h this time
[11:31] <RichEd> and could not get any other seats apart from middle of the normal rows
[11:31] <RichEd> ughh
[11:31] <ogra_cmpc> 8h flight, 3h trainride plus hanging around at the aitrport
[11:32] <RichEd> not too bad ..
[11:32] <ogra_cmpc> but you switch planes, dont you ?
[11:32] <Kamping_Kaiser> hi all. i'm still getting that error checking out the bzr doco.
[11:32] <Kamping_Kaiser> kgoetz@wesnoth:~/public_html$ bzr branch http://bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-doc/edubuntu-hardy
[11:32] <Kamping_Kaiser> bzr: ERROR: Invalid http response for http://bazaar.launchpad.net/%7Eubuntu-core-doc/ubuntu-doc/edubuntu-hardy/.bzr/repository/inventory.knit: Bad status line received
[11:33] <Kamping_Kaiser> anyone got a clue?
[11:33] <ogra_cmpc> ask in #bzr ?
[11:33] <Kamping_Kaiser> ogra_cmpc, ok, i'll head in there
[11:33] <ogra_cmpc> they migth know more
[11:35]  * RichEd wonders if ogra's typing dyslexia tday is accountable to mental fatigue or adult fingers on the little classmate keyboard
[11:35] <ogra_cmpc> both i guess :)
[11:38]  * ogra_cmpc needs another reboot
[13:19] <Kamping_Kaiser> for the logs: my issues with bzr revolve arround my http-proxy. bypassing the proxy bzr is working
[13:30] <stgraber> oh, is lists.ubuntu.com laggy today, I answered 5 minutes ago to RichEd's mail and my mail isn't on the list yet :)
[13:30] <stgraber> usually it takes 5seconds :)
[13:33] <DeMoNSeEd> release announcements come via there?
[13:33]  * Kamping_Kaiser wonders how big the hardy docs will be
[13:34] <RichEd> Kamping_Kaiser: A4 ?
[13:34] <ogra> DeMoNSeEd, all mailing list mail comes via there ... (including the announcement lists indeed)
[13:34] <Kamping_Kaiser> RichEd, yay for standards
[14:00] <sbalneav> Morning all
[14:11] <DeMoNSeEd> hey ogra
[14:11] <DeMoNSeEd> how ya been
[14:28] <jsgotangco> RichEd-1 hi
[15:01] <musashi1> i'm still somewhat of a noob and i'm trying to installed gutsy server (on new HP proliant ML 350) and the install fails at "build chroot". any suggestions as to why and how to fix? just start the install again? or is it a known issue?
[15:01] <musashi1> s/installed/install
[15:10] <i> Hi, anyone around to answer questions
[15:10] <i> ?
[15:10] <sbalneav> i: yes
[15:11] <sbalneav> musashi1: Define "fail"?  Does it give you an error message?
[15:11] <i_> OK, have just recently upgraded (actually, fresh install) to Gutsy...
[15:11] <i_> Feisty server was more or less working fine
[15:12] <i_> Problem I'm having now is that I plug a USB flash drive into the server and it recognises fine ... but plug the same drive into any of the thin clients and no response
[15:12] <i_> Nothing in server's mtab or /media
[15:13] <sbalneav> Try creating a /var/lib/tftpboot/ltsp/i386/lts.conf that contains:
[15:13] <sbalneav> [Default]
[15:14] <sbalneav>    LOCALDEV=True
[15:14] <sbalneav> See if that makes a difference.
[15:14] <i_> OK, trying ...
[15:15] <bddebian> Heya
[15:16] <i_> Nope, nothing
[15:16] <musashi1> sbalneav: yes, i don't recall the exact warning but it's a nice red screen saying to the effect "installing failed at step build ltsp chroot you can try again" trying again also fails --> returns to error screen.
[15:17] <musashi1> sbalneav: i did just start the install again from the beginning so i'll see what happens
[15:18] <sbalneav> i_: Did you restart the terminal?
[15:18] <i_> Yes, 2 terminals, neither worked
[15:18] <sbalneav> You might want to run through: http://wiki.ubuntu.com/DebugLocalDev
[15:18] <i_> OK
[15:21] <i_> Does it matter that lsmod | grep fuse returns with a 1 as the final digit rather than a 3 as shown on that page?
[15:21] <sbalneav> No, just so long as it returns the line.
[15:21] <sbalneav> That means the module's loaded
[15:21] <i_> OK, still going ...
[15:23] <i_> All good up to step 4 ... continuing
[15:26] <i_> OK, having a problem @ Step 1: Setting a root password in the LTSP chroot
[15:27] <i_> Set the root password successfully but then can't log in on the text console of the terminal, even on the server - any ideas?
[15:27] <i_> Username is "root", right?
[15:29] <i_> sbalneav: Hello?
[15:30] <sbalneav> right
[15:30] <i_> OK, so can't login at the console - any idea what the problem might be?
[15:30] <sbalneav> Did you rebuild the image with ltsp-update-image?
[15:30] <i_> At what stage was I supposed to do that?
[15:31] <sbalneav> After the password change
[15:31] <sbalneav> Up on the server
[15:31] <i_> How do I issue that command?
[15:31] <sbalneav> ltsp-update-image :)
[15:31] <sbalneav> as root
[15:31] <i_> Sorry!
[15:32] <i_> OK to sudo, or do I have to chroot?
[15:33] <sbalneav> sudo ltsp-update-image
[15:33] <RichEd-1> jsgotangco: sorry dude leavin for airport
[15:33] <RichEd-1> bye guys
[15:33] <i_> OK, doing that now - 27%
[15:33] <jsgotangco> bye
[15:33] <RichEd-1> sbalneav ogra see you in boston
[15:35] <i_> It's still saying that the login is incorrect...
[15:38] <sbalneav> Have you rebooted since you rebuilt the image?
[15:38] <i_> No - shall I do that?
[15:39] <sbalneav> yes
[15:41] <i_> sbalneav: I've rebooted and I still can't login as root on the console.
[15:45] <sbalneav> ok, here's the complete overview of the procedure.
[15:45] <sbalneav> on the server
[15:45] <sbalneav> sudo chroot /opt/ltsp/i386
[15:45] <sbalneav> passwd
[15:45] <sbalneav> <enter password once>
[15:45] <sbalneav> <enter password again>
[15:46] <sbalneav> exit
[15:46] <sbalneav> sudo ltsp-update-image
[15:46] <sbalneav> wait
[15:46] <sbalneav> when done, reboot
[15:46] <sbalneav> ctl-alt-f1
[15:46] <sbalneav> text login as root/password
[15:47] <i_> OK, that's exactly what I did before but I'm in the process of doing it again (updating image @ 18%)
[15:48] <i_> Image @ 76%
[15:49] <i_> Rebooting ...
[15:50] <i_> sbalneav: Once again, I cannot login as root from the console ...
[15:50] <i_> Changing the password is fine - don't worry, it is the password for root that is being changed
[15:51] <i_> It just doesn't work from the console
[15:52] <musashi1> okay, build ltsp chroot failed again. is there anything i can check to see what it might be? i think i will also burn a new cd
[15:52] <sbalneav> i_: So, on the thin client, you're pressing control-alt-f1
[15:53] <sbalneav> getting a text login screen
[15:53] <i_> No, I've done all of this on the server
[15:53] <i_> Tried on the client earlier
[15:53] <sbalneav> Well, that's wrong
[15:53] <i_> Same problem
[15:53] <sbalneav> you do it on the thin client
[15:53] <sbalneav> on the thin client, control-alt-f1
[15:53] <sbalneav> login as root/password
[15:54] <i_> OK, it's working on the thin-client now
[15:54] <i_> Apologies for that.
[15:54] <stgraber> ogra, ogra_cmpc: Can you accept a mail I sent to the mailing-list with the wrong mail account or shall I resend ?
[15:55] <ogra_cmpc> which ml?
[15:55] <stgraber> edubuntu-devel
[15:55] <ogra_cmpc> ok
[15:55] <stgraber> looks like I'm subscribed with @stgraber.org instead of @ubuntu.com, I'm changing that now
[15:59] <stgraber> argh, in fact it seems that the mail address is correct so why hasn't the mail reached the ML (my SMTP server logs say it was correctly queue on lists.ubuntu.com MX ...)
[16:00] <ogra> i dont see anything in tewh queue
[16:01] <stgraber> ok, I'll send it again and if it doesn't show up in the hour I'll ping a sysadmin
[16:01] <i_> sbalneav: OK, stuck @ Step 3: Did the ltsp udev rules fire? ... Checked flash drive in server and it shows up as sdb1 ... just in case, I'll repartition it anyway and see if that helps
[16:01] <ogra> yeah, looks like something thats worth an rt ticket
[16:02] <juliux> stgraber, lists.ubuntu.com ist very slow this days
[16:04] <stgraber> yes, but someone sent a mail at 16:30 and it's now on the list, mine was sent at 14:00
[16:06] <agente87> hola
[16:06] <agente87> una pregunta
[16:06] <agente87> english better¿?
[16:08] <agente87> i want to use the same account with my pupils, but firefox, said that i have to close the program to load it again from another computer
[16:08] <agente87> how can i fix that
[16:08] <agente87> ?¿
[16:08] <ogra_cmpc> you cant
[16:09] <ogra_cmpc> firefox, openoffice and gnome really freak out if several processes use teh same config
[16:09] <agente87> aha
[16:09] <ogra_cmpc> create a user per client
[16:09] <ogra_cmpc> or so
[16:09] <agente87> and, using another web browser?¿
[16:10] <ogra_cmpc> not sure if there are any that can cope with that
[16:10] <agente87> puff, the problem is my pupils will not remember user and password
[16:10] <ogra_cmpc> use autologin ... its a bit work to set that up for every single client though
[16:10] <sbalneav> So, use autologin
[16:13] <agente87> ok, but the idea is to have a different desktop for every level
[16:13] <agente87> with specific icons for each one
[16:14] <sbalneav> What do you mean, a different desktop for every level?
[16:14] <agente87> yes i use edubuntu
[16:15] <agente87> so, i have exercisses for 3 grade in primary, prepared with icons in the desktop
[16:15] <agente87> and a account called "3grade"
[16:16] <sbalneav> Well, you can't run multiple terminals off of one login.
[16:16] <agente87> the log in by that account and uses the same made desktop
[16:16] <sbalneav> Gnome, openoffice, and firefox do not like that.
[16:17] <agente87> aha
[16:17] <agente87> and, may i use the same desktop for a group
[16:17] <agente87> ?¿
[16:17] <sbalneav> No
[16:17] <sbalneav> Well, you could set up a group in sabayon
[16:17] <sbalneav> but you'll still need individual userids
[16:17] <agente87> is that gentoo?¿
[16:18] <sbalneav> no
[16:18] <sbalneav> Sabayon's a tool to allow you to customize desktops
[16:18] <sbalneav> It can be installed in edubuntu
[16:18] <sbalneav> but you can't get away from creating multiple userids
[16:20] <i_> sbalneav: Step 2 (dmesg) shows that the client recognises the plug event but the ltsp udev rules don't seem to be firing; I've reformatted the flash drive twice, once using fdisk and mkdosfs as suggested in your page, and also using GParted to see if that helped ... no result
[16:21] <i_> This flash drive used to be recognised fine by both server and clients, when running the Feisty server
[16:21] <musashi1> bryang: the other console is empty (i.e. no infor or error messages).
[16:22] <musashi1> bryang: i am going to reboot and check the cd for errors
[16:23] <musashi1> bryang: wait, f4 has a bunch of output
[16:24] <sbalneav> i_: is there a /var/run/drives?
[16:24] <i_> Yes (on the client)
[16:24] <musashi1> bryang: ltsp-client-builder failed with error code 1
[16:25] <musashi1> there is a bunch of other "stuff" there. some about packeage doesn't exist - skipping
[16:25] <sbalneav> is there any subdir underneath /var/run/drives
[16:25] <musashi1> one about siocsifadder device doesn't exist. i have no idea what that means :)
[16:26] <sbalneav> musashi1: Something's wrong with your network interface
[16:27] <musashi1> sbalneav: any idea what? the dhcp part went off without a hitch. are we talking bad nic or something else?
[16:27] <sbalneav> No idea
[16:27] <i_> sbalneav: There are 4 (cdrom, floppy, and 2 scsidisks)
[16:28] <i_> sbalneav: Interesting result when I try to attempt Step 4: Can you manually issue a mount command? ...
[16:29] <i_> The command results in attempting to connect to the server but when I'm asked to supply the root password, permission is denied...
[16:30] <ogra_cmpc> you need to be logged in on the GUI screen for that
[16:30] <ogra_cmpc> else teh ssh tunnel isnt established and iut asks for teh root pw
[16:31] <i_> I'm already logged into the GUI ... just found one of the problems... changed root password using sudo passwd root and now granted permission but ...
[16:32] <ogra_cmpc> nooo
[16:32] <i_> As mentioned in Step 4, it's resulted in an error ...
[16:32] <ogra_cmpc> there is no root user involved anywhere
[16:32] <ogra_cmpc> if you get asked for a root PW the tunnel isnt working
[16:32] <i_> Sorry ogra, I meant I changed the root password on the server ...
[16:32] <i_> OK, here's the error I got:
[16:35] <i_> ogra_cmpc: Where exactly am I supposed to issue the command from?
[16:35] <ogra_cmpc> the console of teh client
[16:36] <i_> Ok, just tried that and it says ssh: server: Name or service not known
[16:36] <ogra_cmpc> but kdm is running ?
[16:36] <ogra_cmpc> err
[16:36] <ogra_cmpc> ldm
[16:36] <ogra_cmpc> and you are properly logged in through it
[16:36] <i_> How can I check?
[16:37] <ogra_cmpc> ps ax|grep ldm
[16:37] <ogra_cmpc> on the client console
[16:37] <ogra_cmpc> its the default login manager
[16:37] <ogra_cmpc> and one of teh core parts to make ltspfs work
[16:37] <i_> OK, got a standard result for ldm
[16:38] <ogra_cmpc> whats a standard result ?
[16:38] <ogra_cmpc> is it running or not?
[16:38] <i_> 7218 pts/2     S+     0:00 grep ldm
[16:38] <ogra_cmpc> no ldm running
[16:38] <ogra_cmpc> thats your problem then
[16:38] <i_> So what do I do now
[16:39] <ogra_cmpc> without the ssh socket ldm creates localdev wont work
[16:39] <ogra_cmpc> well, teh question is how you got in that state
[16:39] <i_> OK, I was originally running Feisty - everything was more or less OK
[16:39] <ogra_cmpc> did you tweak around in lts.conf ?
[16:40] <i_> No - not on Feisty at all
[16:40] <ogra_cmpc> so are you on feisty or gutsy ?
[16:40]  * ogra_cmpc doesnt understand
[16:40] <i_> Just tweaked the lts.conf in /var/... today for the first time - but never had flash drives working since upgrading to Gutsy
[16:41] <ogra_cmpc> how did you upgrade ?
[16:41] <musashi1> bryang: cd checks out okay. assuming that test works.
[16:41] <ogra_cmpc> did you properly rebuild the client root with ltsp-build-client ?
[16:41] <i_> Used the alternate CD first ... but didn't allow it to download new packages from the net
[16:42] <i_> That resulted in server that could only host 6-8 clients - and very poorly at that
[16:42] <i_> The remainder of the clients wouldn't even "see" the DHCP server when attempting to connect via the network
[16:43] <sbalneav> Something's wrong with something
[16:43] <sbalneav> I run 50 clients off my server.
[16:43] <sbalneav> One of my servers, I should say
[16:43] <i_> No, but now I did a fresh install of Gutsy and all 19 clients are working fine, except for this flash drive problem
[16:44] <sbalneav> Are the users members of the fuse group?
[16:44] <i_> When I say working fine, I mean they all connect and login - haven't really used it long enough to see if there are any other problems
[16:44] <i_> All users are members of the fuse group - checked that as per your instructions
[16:45] <ogra_cmpc> so thats a fresh gutsy install atm ?
[16:45] <ogra_cmpc> or an upgraded one ?
[16:45] <i_> Yes, that's a fresh install - there's only one thing I messed around with
[16:45] <i_> To save the original user accounts, I made a backup of /etc ... I already had /home on another partition ...
[16:46] <ogra_cmpc> are you using ldap ?
[16:46] <i_> When I rebuilt the server with the fresh Gutsy install ...
[16:46] <i_> No LDAP
[16:46] <ogra_cmpc> well, check that the number for teh fuse group wstill matches whats set in /etc/passwd and /etc/grou would be my first guess
[16:47] <i_> ... OK, checking...
[16:48] <ogra_cmpc> hmm, but still, no ldm is a bad thing and thats surely not caused by teh servers passwd file
[16:48] <i_> OK fuse group ID: 117 ...
[16:49] <ogra_cmpc> and /dev/fuse has teh right perms
[16:49] <ogra_cmpc> (owned by the fuse group)
[16:49] <i_> No, owned by root and group = fuse
[16:50] <ogra_cmpc> good
[16:50] <ogra_cmpc> thats all fine then
[16:50] <ogra_cmpc> so if ldm isnt running, i wonder how you log in on your clients
[16:51] <i_> Pretty quickly, actually!  Faster than in Feisty...
[16:51] <ogra_cmpc> i assume you had a graphical login window
[16:51] <i_> Yes
[16:51] <ogra_cmpc> hmm
[16:51] <sbalneav> What does the date and time look like in the bottom right?
[16:51] <ogra_cmpc> do you have SCREEN_07=startx or something similar werid in your lts.conf?
[16:52] <i_> Of the client login screen?
[16:52] <ogra_cmpc> yeah
[16:52] <i_> 25.10. 18:47
[16:52] <ogra_cmpc> no ip ?
[16:52] <i_> Sorry, IP is there as well <IP_ADDRESS>
[16:52] <sbalneav> yeah, ldm's running
[16:53] <ogra_cmpc> and (ltsp) or so in the front
[16:53] <i_> Yes ltsp (and not the name of the server as it used to be in Feisty)
[16:53] <ogra_cmpc> good, then ldm is running
[16:53] <ogra_cmpc> i wonder why you didnt see it in teh clients processlist
[16:53] <i_> I'll try again
[16:54] <i_> 7723 pts/2    S+     0:00 grep ldm
[16:55] <sbalneav> Where are you running this command?
[16:55] <i_> Terminal on the client
[16:55] <sbalneav> In the text screen? ctl-alt-f1?
[16:55] <i_> Not console (I mean Ctrl-Alt-F1)
[16:56] <i_> Sorry, I mean I'm running it from Applicatons-Terminal
[16:56] <ogra_cmpc> nah
[16:56] <sbalneav> right
[16:56] <sbalneav> that's wrong
[16:56] <ogra_cmpc> hehy
[16:56] <sbalneav> you need to do it on the ctl-alt-f1
[16:56] <i_> OK ...
[16:56] <i_> As root?
[16:56] <sbalneav> when you run it on the gnome-terminal, you're on the server
[16:57] <sbalneav> since the gnome terminal's running on the server, you're looking at server processes
[16:57] <sbalneav> everything you do on the graphic login is running on the server, NOT on the thin client itself.
[16:57] <sbalneav> as root, yes.
[16:58] <i_> OK, gettinga lot of output, what are you looking for?
[16:58] <sbalneav> ldm vt7 :6
[16:58] <i_> Right, got that
[16:58] <sbalneav> ok, so you're running ldm
[16:58] <i_> Good stuff
[16:59] <i_> I've noticed that the fuse group isn't listed in /etc/passwd
[16:59] <sbalneav> that's because it's a group
[16:59] <sbalneav> so it's listed in /etc/group
[17:00] <sbalneav> so, on the thin client
[17:00] <sbalneav> in ctl-alt-f1
[17:00] <i_> yes ...
[17:01] <sbalneav> you should have a /var/run/ldm_socket something file, yes?
[17:01] <i_> checking ..
[17:01] <highvoltage> hey sbalneav. I'm having trouble figuring something out, how does the client know that it should boot from the 386.img file? the only reference I can get to it is in /etc/inetd.conf. not in dhcpd.conf or pxelinux.cfg.
[17:01] <i_> Yes
[17:01] <sbalneav> highvoltage: it depends what port you go to, what image you get
[17:02] <i_> ldm_ocket_vt7_<IP_ADDRESS>
[17:02] <sbalneav> so 2000 is i386
[17:02] <i_> ldm_socket_vt7_<IP_ADDRESS>
[17:02] <sbalneav> ok, so on c-a-f1,
[17:02] <sbalneav> if you do a:
[17:03] <sbalneav> ssh -S /var/run/ldm_socket_vt7_<IP_ADDRESS> <IP_ADDRESS> ltspfsmounter /tmp add
[17:03] <sbalneav> what happens?
[17:03] <highvoltage> sbalneav: aaaaaaaaah
[17:05] <i_> Tried to write ...
[17:05] <highvoltage> sbalneav: how do the clients know that they should look at port 2000? is it built into the kernel?
[17:05] <i_> fuse: failed to exec fusermount: Permission denied
[17:05] <i_> Error: /tmp/.s1081-ltspfs/tmp is not mounted
[17:08] <sbalneav> ok
[17:08] <sbalneav> failed to exec fusermount: Permission denied
[17:08] <sbalneav> on the server
[17:08] <sbalneav> as a user
[17:08] <i_> On the client as a user
[17:08] <sbalneav> do an "id"
[17:08] <sbalneav> either or
[17:08] <sbalneav> paste the results
[17:09] <i_> uid=0(root) gid=0(root) groups=0(root)
[17:09] <sbalneav> No
[17:09] <sbalneav> on the graphical login
[17:09] <sbalneav> logged in as a regular user
[17:11] <i_> To make this a little easier, I'm just going to install XChat on the server so that I can paste the result
[17:11] <i_> I'm using my own laptop for this so far
[17:12] <i_> (I mean this chat, not the rest of the stuff!)
[17:13] <s1081> Right this is i_ here:
[17:13] <s1081> Here's the result:
[17:13] <s1081> s1081@BSCL02-SERVER:~$ id
[17:13] <s1081> uid=1081(s1081) gid=1082(s1081) groups=4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),29(audio),30(dip),46(plugdev),104(scanner),117(fuse),1082(s1081)
[17:15] <sbalneav> grep fuse /etc/passwd
[17:15] <sbalneav> grep fuse /etc/group, sorry
[17:16] <s1081> s1081@BSCL02-SERVER:~$  grep fuse /etc/group
[17:16] <s1081> fuse:x:117:s1001,s1002,s1003,s1009,s1014,s1016,s1004,s1006,s1008,s1012,s1013,s1015,s1017,s1005,s1011,s1018,s1019,s1020,s1021,s1022,s1010,s1024,s1007,s1023,s1025,s1026,s1027,s1035,s1029,s1037,s1039,s1030,s1031,s1032,s1034,s1038,s1036,s1040,s1028,s1041,s1042,s1043,s1044,s1045,s1046,s1047,s1048,s1049,s1050,s1033,s1051,s1052,s1053,s1054,s1055,s1056,s1057,s1058,s1060,s1059,s1061,s1062,s1063,s1064,s1065,s1066,s1067,s1072,s1068,s1070,s1074,s1078,s1075,s1071,s1073,s1
[17:16] <s1081> 076,s1077,s1079,s1080,s1069,s1081,s1082
[17:16] <bryang> musashi1, sorry, just back now, catching up on sb
[17:17] <sbalneav> You running ldap or something?
[17:17] <s1081> No
[17:17] <s1081> Perhaps the problems lies in how I transferred the user accounts over to Gutsy from Feisty ...
[17:18] <sbalneav> ls -la /bin/fusermount
[17:18] <s1081> I backed up the default files when I did the fresh install of Gutsy ... and then I copied over the files I had from Feisty (i.e. /etc/passwd, etc)
[17:18] <s1081> s1081@BSCL02-SERVER:~$ ls -la /bin/fusermount
[17:18] <s1081> -rwsr-xr-- 1 root messagebus 19668 2007-09-19 03:01 /bin/fusermount
[17:18] <sbalneav> yup
[17:19] <sbalneav> what you did was bad
[17:19] <sbalneav> Don't copy the whole file
[17:19] <sbalneav> extract out YOUR users and groups, and leave the systems stuff (uid/gids < 500) as is
[17:20] <sbalneav> as they get added, changed and removed.
[17:20] <sbalneav> Your fuse group is now different
[17:20] <sbalneav> and that's your problem
[17:20] <sbalneav> You, of course, saved the ones that come with gutsy, right? :)
[17:20] <s1081> OK, like I said, I've got the original files that were present when I first installed Gutsy ... I'll use the data in there and do what you said
[17:21] <sbalneav> yeah, what twigged me into it is, on my gutsy, fuse is 118
[17:21] <s1081> So to be precise: We're talking about /etc/passwd; /etc/shadow; /etc/groups ...
[17:21] <sbalneav> right.
[17:21] <s1081> Any other files?
[17:21] <s1081> I should look out for?
[17:21] <sbalneav> well, those are the only ones to bring over.
[17:21] <sbalneav> How much did you copy across?
[17:21] <sbalneav> just those 3?
[17:22] <s1081> Yes, just those
[17:22] <s1081> Just out of interest, what was the correct way of doing the transfer
[17:22] <s1081> ?
[17:22] <sbalneav> Well, here's what I do:
[17:22] <sbalneav> I make sure all my groups and users start at 1000
[17:23] <sbalneav> so what I do is:
[17:23] <sbalneav> make a copy of the existing
[17:23] <sbalneav> sort them, so it's all in numeric order
[17:24] <sbalneav> pull across all the stuff that's 1000 or greater from passwd, group
[17:24] <sbalneav> shadow, I just manually have to make sure there's nothing system-y mixed in with the regular users.
[17:25] <sbalneav> how many users do you have?
[17:26] <s1081> Just over 80
[17:26] <sbalneav> easy, then
[17:26] <sbalneav> I manage 250 :)
[17:26] <s1081> Now, the group file looks a little tricky ...
[17:26] <sbalneav> yeah, put back the origs, then just add your users on to the end.
[17:27] <s1081> (Done the passwd file)
[17:27] <sbalneav> as new features get added, new system uids/gids get added/removed, so copying the whole thing's not guarenteed to work.
[17:27] <s1081> In the Feisty group file, a lot of my users are members of groups with ID < 1000
[17:27] <s1081> I'm going to have to manually edit each of these lines afterwards, right?
[17:28] <s1081> Obviously, I can easily copy and paste their primary group details (> 1000)
[17:29] <sbalneav> Sure, but in the ling run, youmight want to get them all greater than 1000
[17:29] <s1081> By the way, fuse ID in my /etc/group file is 106 - is that OK?
[17:29] <sbalneav> then you could do cool things like:
[17:29] <sbalneav> awk '$3 > 999 {print $0}' /etc/passwd
[17:30] <sbalneav> which would show you all "your" entries
[17:30] <sbalneav> sorry:
[17:30] <sbalneav> awk -F: '$3 > 999 {print $0}' /etc/passwd
[17:30] <sbalneav> as for the fuse group, if that's the one that was there from the fresh install, it's fine.
[17:31] <sbalneav> when you look at /bin/fusermount is should be root:fuse
[17:31] <s1081> But I'll have to add all the users to the group, on that line, right?
[17:32] <sbalneav> right.
[17:32] <s1081> And for all the other groups they used to belong to?
[17:32] <sbalneav> yes
[17:32] <s1081> So waht
[17:32] <s1081> So what's the quickest, most efficient way of doing that?
[17:33] <sbalneav> Me? I'd write a script.
[17:34] <sbalneav> so something like:
[17:34] <sbalneav> (off the top of my head)
[17:34] <sbalneav> for ((I=1000; I<1099; I++)); do
[17:35] <sbalneav>   adduser s$I fuse
[17:35] <sbalneav>   adduser s$I someothergroup
[17:35] <sbalneav>   etc
[17:35] <sbalneav> done
[17:36] <s1081> OK, that's fairly straightforward but
[17:36] <sbalneav> or, do it from the results in awk:
[17:36] <musashi1> s1081, bryang wrote a nice script for adding users. maybe could be tweaked for what you need.
[17:36] <s1081> There's gotta be an easier way for the average teacher who wants to upgrade his server to Gutsy ...
[17:37] <musashi1> s1081: yeah, or one trying to install one :)
[17:37] <sbalneav> Sure, the gui manager
[17:37] <s1081> What, create all of the user accounts all over again, one by one?
[17:37] <sbalneav> System->Administration->Users and groups
[17:37] <sbalneav> Beleive it or not, that's what a lot of people do.
[17:37] <s1081> The only other idea I had was to write a script to use the useradd, groupadd commands to set it all up
[17:38] <sbalneav> That's another good way.
[17:38] <s1081> As in, forget about what I had from Feisty and just start fresh in Gutsy
[17:38] <sbalneav> A lot of teachers also use LDAP, and/or active drecktory, so they just re-attach to that.
[17:38] <bryang> or better yet have auth via a directory of some sort
[17:39] <ogra_cmpc> that will come at one point
[17:39] <s1081> OK, so what's with the Users and Groups that it doesn't sort the users alphabetically?
[17:39] <ogra_cmpc> ubuntu server is working on it
[17:39] <ogra_cmpc> once they are done we'll inherit it
[17:40] <ogra_cmpc> (likely to happen in hardy)
[17:41] <s1081> Right, I'm done editing the files - I'll just reboot and see how it all goes
[17:41] <i_> Or do I not need to reboot?
[17:42] <sbalneav> Shouldn't need to.
[17:42] <sbalneav> what's the ownership of /bin/fusermount look like now?
[17:42] <i_> Alright, client is rebooting at least ...
[17:44] <musashi1> bryang: would it be worth trying the network install you mentioned?
[17:45] <bryang> musashi1: not really, just references the same bits
[17:45] <musashi1> okay
[17:45] <bryang> what is current state  of server
[17:45] <musashi1> just looking for options
[17:45] <musashi1> waiting for me to give it something to do :)
[17:45] <musashi1> installed failed, checked cd, now just waiting
[17:46] <i_> Ahh, it hasn't worked - yet, at least
[17:46] <i_> I'm going to try to reboot the server as well
[17:46] <bryang> musashi1: so maybe do the install again, then at failure point, we can do some t/s on alt consoles
[17:47] <i_> But the group details look fine, though
[17:47] <musashi1> bryang: okay, will fire it up again.
[17:47]  * bryang wishes you had the iLO port going to make this easier ;)
[17:50] <musashi1> that would be cool
[17:50] <musashi1> but behind the firewall
[17:50] <musashi1> well, installation's away...
[17:51] <ogra_cmpc> musashi1: if thats a normal install thats failing it would probably make sense to keep /var/log/syslog from the installer environment and attach it to a bug ;)
[17:51] <musashi1> i moved to a different nic. someone said it might be a networking issue so worth a try
[17:51] <ogra_cmpc> what exactly does happen ?
[17:51] <musashi1> ogra_cmpc: i'll try that
[17:52] <musashi1> ogra_cmpc: it fails to install ltsp chroot
[17:52] <musashi1> i don't recall the exact warning but it's a nice red screen saying to the effect "installing failed at step build ltsp chroot you can try again" trying again also fails --> returns to error screen.
[17:52] <bryang> ltsp-build-client error
[17:52] <ogra_cmpc> thats the released iso ?
[17:52] <musashi1> right
[17:52] <musashi1> to both
[17:53] <ogra_cmpc> note there were bugs up to RC
[17:53] <musashi1> downloaded just the other day
[17:53] <ogra_cmpc> you can watch the client build process on console 4 while the progressbas sits at the 50% MARK
[17:54] <ogra_cmpc> just hit alt-f4
[17:54] <ogra_cmpc> that should revel at least the error
[17:54] <ogra_cmpc> note that moaning about pty not mounted and dbconf warnings are normal there
[17:54] <musashi1> checked that last time -->  ltsp-client-builder failed with error code 1
[17:54] <ogra_cmpc> *debconf
[17:55] <ogra_cmpc> well, the stuff that causes that error would be miore intresting :)
[17:55] <ogra_cmpc> it must be above in the log
[17:56] <musashi1> i'll try and find that when/if it fails again
[17:56] <cberlo> Hi folks.  got some speed issues I'm seeing in Edgy thin clients.  I think it relates to DRI, and I'm wondering if anyone knows how to activate this feature on thin clients with Edubuntu?
[17:56] <cberlo> ogra: Can't use scp-remote; on Edgy this command wasn't implemented yet!
[17:57] <ogra_cmpc> cberlo: you need to install the linux-restricted-modules package in teh chroot and follow the usual procedure to enable binary drivers
[17:57] <ogra_cmpc> cberlo: oh, right
[17:57] <ogra_cmpc> edgy is ancient :)
[17:57] <cberlo> The usual procedure?  As in list it in the lts.conf?
[17:57] <ogra_cmpc> NO AS DESCRIBED ON TEH WIKI
[17:57] <ogra_cmpc> OOPS
[17:57] <cberlo> ogra_cmpc: Hey, it's still supported!  :)  But I'd love to move to Gutsy.  Very tempting, but I need everything stable and tested....
[17:57]  * ogra_cmpc curses the tiny keyboard of teh classmate
[17:58] <cberlo> ogra_cmpc: Where on the wiki?  Didn't come across that...
[17:58] <ogra_cmpc> search for binary drivers
[17:58] <cberlo> ogra_cmpc: Thanks!  Will do!
[17:58] <ogra_cmpc> note that you will only be able to support either nvidia or ait ... both at the same time doesnt work
[17:59] <ogra_cmpc> *ati
[17:59] <ogra_cmpc> they both replace the GL libs with their own versions
[17:59] <cberlo> Ummm...  This is an Intel 810 chipset...
[17:59] <ogra_cmpc> that should just work out of teh box
[18:00] <musashi1> ogra_cmpc: i can't make heads or tails of all that log info. is there a way to output it to a file that i can paste somewhere?
[18:00] <cberlo> So I should be getting DRI already?  I specified i810 in the lts.conf as the default driver.
[18:00] <ogra_cmpc> musashi1: its savede to /var/log/syslog in teh installer
[18:00] <ogra_cmpc> on console2 you can start a shell
[18:01] <musashi1> but from a console how do i save it to say a flash drive?
[18:01] <ogra_cmpc> cberlo: yes, but it could be that we didnt install teh mesa dri libs in teh client chroot back then
[18:01] <ogra_cmpc> you should have teh kernel related stuff running
[18:01] <cberlo> ogra_cmpc: Okay.  So which package is that in and/or where can I check to see if that's in there?
[18:01] <ogra_cmpc> (i.e. DRI)
[18:02] <ogra_cmpc> something with mesa and dri in teh package name
[18:02] <ogra_cmpc> i have no briowser around
[18:02] <ogra_cmpc> so i cant look up stuff for you
[18:02] <cberlo> orgra:  Got this one in there:  libgl1-mesa-dri
[18:02] <ogra_cmpc> packages.ubuntu.com might help
[18:02] <ogra_cmpc> sounds about right
[18:03] <ogra_cmpc> install that in teh chroot
[18:03] <cberlo> It's already there...  :(
[18:04] <ogra_cmpc> look for mesa glx as well
[18:04] <cberlo> ogra_cmpc: Yep, that one's in there, too.
[18:05] <ogra_cmpc> hmm, no idea then
[18:05] <cberlo> Nothing else I'd have to do to enable DRI on the thin client?  It should "just work"?
[18:06] <ogra_cmpc> for i810 ? yes
[18:06] <ogra_cmpc> i didnt have any i180 cards during edgy development so i cant say much about ltsp and GL support there
[18:06] <ogra_cmpc> i know compiz works out of teh box here on gutsy on teh i810 client i have now
[18:07] <cberlo> Alright.  Guess I'll just have to play with it a bit and see if I can get it to work properly.    Wait -- you're using compiz on a thin client??
[18:10] <ogra_cmpc> yeah, its incredibly fast
[18:11] <cberlo> Well, guess I'll see if I can load up a test server here.  That sounds like it would fix that issue for me.  Running a Windows program on WINE and video update speed is glacial.  Runs great on my laptop here, though, so it's not a problem with WINE/Linux/good video.
[18:11] <cberlo> ogra_cmpc: Vanilla edubuntu install will work "out of the box"?
[18:12] <cberlo> gutsy, that is.
[18:12] <ogra_cmpc> yes
[18:12] <ogra_cmpc> yep
[18:24] <i_> sbalneav: ogra_cmpc: It's finally working - thanks for all your help - greatly appreciated ... I'm giving up for the day; You guys deserve gold medals - keep up the good work.
[18:24] <ogra_cmpc> :)
[18:25] <i_> Don't think you've seen the last of me ... now that I know where you guys are ...
[18:28] <effie_jayx> ogra_cmpc,  what's the wilress card again?
[18:29] <effie_jayx> wireless
[18:29] <ogra_cmpc> ??
[18:29] <effie_jayx> ogra_cmpc,  the one the classmate brings
[18:29] <ogra_cmpc> ralink
[18:29] <effie_jayx> you said it was not intel
[18:29] <ogra_cmpc> rt73usb based
[18:30] <effie_jayx> ogra_cmpc, thanks
[18:39] <musashi1> bryang: any suggestions on how to get the log to you (or anyone else)? it failed again
[18:39] <musashi1> bryang: could it be an acpi issue??
[18:41] <ogra_cmpc> musashi1: do you have an USB key you could store it on?
[18:42] <musashi1> yes
[18:42] <ogra_cmpc> so use that one :)
[18:42] <musashi1> but how do you mount a usb in a console
[18:42] <ogra_cmpc> with the mount command
[18:43] <ogra_cmpc> plug it in ... wait a second .... type: dmesg
[18:43] <musashi1> will fdisk -l tell me the dev name?
[18:43] <ogra_cmpc> at the end of teh output you should see teh device name
[18:43] <musashi1> hold on, it's in another room
[18:48] <cberlo> 8.04 is going to be pretty nice, I'm guessing.  LTS, feature-rich, well-tested....  Looks like things are coming along nicely for Edubuntu.  It may just have a future in my school board...
[18:49] <musashi1> great now my stupid win box won't read the flash drive.
[18:49] <shriphani> musashi1, ext3 fs or something like that ?
[18:49] <musashi1> well it was a fat32 drive
[18:50] <shriphani> ok..
[18:50] <musashi1> i think i fried it somehow. my ubuntu lappy won't read it either
[18:51] <shriphani> care to do a tune2fs -l <device> ?
[18:51] <ogra_cmpc> dont forget to unmount ;)
[18:52] <ogra_cmpc> if you unplugged it without unmounting, data can be corrupt
[18:52] <shriphani> yeah.
[18:52] <shriphani> i did that when I was using pcbsd.
[18:53] <shriphani> it refused to mount, had to use debugfs to kick out 'recover_needed
[18:53] <shriphani> or something like that from the features of the drive.
[18:54] <musashi1> it wont unmount
[18:54] <musashi1> invalid argument
[18:54] <shriphani> the command is umount
[18:54] <musashi1> right
[18:55] <musashi1> i did umount /dev/sda
[18:55] <musashi1> wrong?
[18:55] <shriphani> umount <dir where device is mounted>
[18:55] <musashi1> ah, right
[18:56]  * musashi1 wishes he was more cli literate :(
[18:58] <musashi1> uh, any idea where it's mounting? /mnt is empty
[18:58] <ogra_cmpc> where you told it to :)
[18:59] <ogra_cmpc> (in the mount command)
[18:59] <shriphani> did you mount in the first place ?
[19:00] <musashi1> no. thought it auto mounted
[19:00] <shriphani> ubuntu's udev i think mounts it in /media/##
[19:00] <musashi1> there is no /media
[19:00] <musashi1> it a busybox shell
[19:00] <musashi1> if that matters
[19:04] <shriphani> try doing blkid
[19:04] <shriphani> i mean typing blkid
[19:04] <musashi1> okay, created dir /mnt/usb and mounted. cp file to it. verified it's there. still can't umount
[19:04] <musashi1> used umount /mnt/usb
[19:05] <musashi1> says invalid argument
[19:06] <musashi1> oops, was still in that dir. d'oh
[19:10] <musashi1> for your reading pleasure  :) http://dpaste.com/23351/
[19:10] <musashi1> that's the whole log
[19:10] <musashi1> free virtual beer to who ever can pinpoint the problem :)
[19:13] <scrapbunny> Is there anyone here that can help an edubuntu newbie with thin client questions?
[19:13] <stgraber> ogra_cmpc: around ?
[19:14] <scrapbunny> i am trying to set up edubuntu 7.10 thin clients
[19:15] <stgraber> ogra, ogra_cmpc: the ML still doesn't like me, can I mail you and you forward it to the list ?
[19:21] <musashi1> line 6237 has the failure for build-ltsp
[19:22]  * musashi1 wonders what line 6235 means
[19:31] <musashi1> could it be a bad CD issue? i'm going to burn a new one and try (burning on ubuntu this time)
[19:50] <musashi1> starting install again with new CD. my laptop would only burn at 28x though. hope that isn't too fast. in the past it tended to cause problems.
[19:51] <musashi1> this line from syslog is puzzling --> "tsp-client-builder: ltsp-build-client options: --mirror file:///cdrom --security-mirror none --skipimage"
[19:52] <musashi1> then "(process:25542): SIOCSIFADDR: No such device"
[19:52] <musashi1> and then failure --> "WARNING **: Configuring 'ltsp-client-builder' failed with error code 1"
[20:20] <musashi1> bryang: if this fails again i'm going to cry
[20:25] <bryang> musashi1: hmm, that line 6235 looks like it was called incorrectly (and some of those options are not in the --help output)
[20:26] <bryang> at least on my running system
[20:27] <bryang> try grabbing this log next time
[20:27] <bryang> /var/log/ltsp-server-build.log
[20:28] <bryang> since that is where output goes according to the ltsp-server.postinst script
[20:31] <bryang> fwiw, ltsp-build-client is called with no options, so ignore that assessment ;)
[20:51]  * musashi1 cries, screams, puts fist through wall
[20:53] <sbalneav> You're not actually giving us any information on what your network is like.
[20:53] <musashi1> what would you like to know?
[20:54] <sbalneav> Maybe you could tell us a little bit about your network, internet access, what the machine is, how many nics you've got in the machine, how much ram, what kind of processor, you know.  Information :)
[20:54] <musashi1> there is no network connected yet, except for the uplink via dhcp
[20:55] <bryang> sys = dual zeon, 4GB RAM, 3 NIC, 3x160GB RAID5 LUN
[20:55] <musashi1> well, there is internet and the server does get a dhcp IP, machine is a hp proliant 350 with 1 on board nic and two others 4gb of ram 2 xeon dual core cpus. some of this info was supplied way above :)
[20:55]  * musashi1 too slow
[20:55] <bryang> model = HP ml350
[20:56] <sbalneav> So, there's 3 onboard nics
[20:56] <bryang> true
[20:56] <sbalneav> I didn't see it.
[20:56] <sbalneav> Have you tried disabling in bios all the nics that arent used?
[20:57] <musashi1> on one the mobo, two in pci slots (right bryang?)
[20:57] <musashi1> sbalneav: no
[20:57] <bryang> pci-express slots, but yes
[20:57] <sbalneav> They're in pci slots?
[20:57] <sbalneav> Maybe try yanking them, since the failure you're getting is a network related one.
[20:58] <bryang> worth a try musashi1, I haven't done any installs on pci-x nic systems
[20:59] <musashi1> okay
[20:59] <bryang> and worst case can swap some for those ;)
[21:02] <musashi1> okay, yanked and trying again...
[21:03] <bryang> sbalneav: you'll notice that all three NICS were found during bootup by hw-detect.hotplug
[21:03] <sbalneav> (process:25542): SIOCSIFADDR: No such device" means some interface address wasn't found.
[21:03] <sbalneav> We've tested on one nic and two nic systems
[21:04] <sbalneav> Maybe we've got a bug that causes it to fail on 3 nics
[21:04] <sbalneav> or, maybe something in the kernel doesn't like one of the cards
[21:04]  * bryang sees light turn on ;)
[21:04] <sbalneav> or, maybe some udev rule doesn't like 3 nics
[21:04] <sbalneav> or who knows.
[21:05] <bryang> fwiw, I did install feisty on a three nic system (so may in fact be a new issue)
[21:05] <sbalneav> What I *do* know is, neither the machine, or the edubuntu machine will respond do crying, screaming, or fists in plasterboard. :) So, we'll try this.
[21:06]  * bryang appreciates the help, for sure
[21:06] <sbalneav> And maybe this won't work either, but then that'll be another datapoint to add to the graph :)
[21:08] <musashi1> sbalneav: machine won't respond but makes me feel better. i've been at this for 6 hours now :)
[21:09] <bryang> sbalneav, it does look like possibly some NIC re-ordering is happening throughout the install
[21:09] <sbalneav> Entirely possible.
[21:10] <bryang> musashi1, was the log posted from when you did an install from one of the PCI NICs ?
[21:11] <musashi1> bryang: i think so
[21:11] <sbalneav> brb
[21:11] <cberlo> ogra_cmpc: Finally back from installing a test server here.  From a fresh load, I'm trying to connect a Dell GX100 over PXE/MBA (the one with the i810 video card I need to work with) and not getting any X at all.  Haven't even logged into the system once since installing.  Suggestions?
[21:11] <musashi1> sbalneav: if this works i owe you a virtual beer...or maybe bryang does :)
[21:12]  * musashi1 crosses fingers. installastion's away
[21:13] <bryang> musashi1, do you get the option to go to next step of installation ?
[21:19] <ogra_cmpc> cberlo: could be bug 149006
[21:19] <ubotu> Launchpad bug 149006 in ltsp "ltsp does not configure xorg.conf correctly" [Undecided,New] https://launchpad.net/bugs/149006
[21:19] <ogra_cmpc> create a /var/lib/tftpboot/ltsp/i386/lts.conf
[21:19] <ogra_cmpc> and make sure to have X_COLOR_DEPTH=24 in there
[21:19] <ogra_cmpc> if it doesnt work with 24, try 16
[21:20] <ogra_cmpc> RichEd: ??
[21:20] <RichEd> hi ogra ...
[21:20] <ogra_cmpc> shouldnt you be in the air ?
[21:20] <RichEd> yep ... international lounge at johannesburg airport
[21:20] <ogra_cmpc> trying th enew louge card ?
[21:20] <RichEd> thanks to the new lounge card
[21:20] <RichEd> indeed
[21:20] <ogra_cmpc> heh, snap
[21:20] <RichEd> free beer (as in free beer) ... snacks ... comfy chairs ... AND ... drum roll ....
[21:20] <RichEd> tdrrrrrrrrr
[21:21] <RichEd> smoking lounge
[21:21]  * ogra_cmpc dances wildly
[21:21] <cberlo> I have to make a new compressed image after?
[21:21] <ogra_cmpc> cberlo: not if you use /var/lib/tftpboot/ltsp/i386/lts.conf
[21:21] <RichEd> and of course ... internet access :)
[21:21] <ogra_cmpc> indeed
[21:21] <ogra_cmpc> wow, that makes travveling a lot easier
[21:21] <cberlo> ogra_cmpc: Alright, I'll give it a go.
[21:22]  * ogra_cmpc wished he had had that card back in warsaw
[21:22] <RichEd> me too in a number of crappy airports ...
[21:22] <RichEd> i guess warsaw executive lounge may have been as styling as say ... a small german village bus station ;)
[21:23] <ogra_cmpc> lol, yes
[21:24] <ogra_cmpc> i mamnageed my first successfull install btw ... i'll write a small gui tool for that during travel ... i still like the principle of the squashfs :) ....
[21:24] <cberlo> Hey, I see GUI!  :)
[21:25] <ogra_cmpc> so that way the image will only be 650M
[21:25] <musashi1> bryang: next step? you mean after failure on the chroot stuff? i didn't try. figured failure == failure
[21:25] <ogra_cmpc> and be installable from any kind of USB device
[21:26] <cberlo> ogra_cmpc: Okay, now that I'm Gutsy and have GUI, what do I need to get DRI?
[21:26] <ogra_cmpc> cberlo: congrats ... (i think that bug justifies a stable release upgrade it hits many ppl)
[21:26] <ogra_cmpc> cberlo: try to enable desktop effects in teh appearance settings
[21:26] <cberlo> Okay
[21:27] <cberlo> Desktop Effects could not be enabled.
[21:27] <ogra_cmpc> hmm
[21:27] <cberlo> Which, I am gonna guess probably means my card is too wimpy to pull this off?
[21:28] <ogra_cmpc> well, i dont know if there are i810 cards that are not dri capoable
[21:28] <ogra_cmpc> the ones i had in my hands all were
[21:28] <ogra_cmpc> but that were pretty recent ones
[21:28] <cberlo> Is there a way I can do something like "lspci" on the thin client?
[21:28]  * RichEd waves to ogra ... heading to flight #2 ... may chat to you from schipol
[21:29]  * ogra_cmpc waves
[21:31] <cberlo> Is it "X_SERVER" or "XSERVER" to set default server?
[21:32] <ogra_cmpc> no unde5rscore
[21:33] <ogra_cmpc> try the intel server btw, thats probably better
[21:33] <cberlo> Okay.  Thanks.  I'll play with it more tomorrow and let you know how it works out!  :)
[21:53] <musashi1> sbalneav: bryang no failure this time but now with only 1 nic i get a different msg (no interface for ltsp dhcpd config found). install is continuing.
[21:53] <musashi1> guess it didn't like the pcie nics or didn't like 3.
[21:55] <sbalneav> That's fine, so long as it completes, then we can fix up the nic and the dhcpd afterwards.
[21:56] <bryang> yupper, agreed
[21:56] <musashi1> success!! i now have a thin client server with 1 nic :) rebooting.
[22:00] <musashi1> the desktop has landed :)
[22:01] <bryang> schweet
[22:01] <musashi1> can i put one of the nics back to see if it likes pcie?
[22:02] <bryang> sure
[22:02] <musashi1> will it try to configure it?
[22:02] <bryang> we know how to get back here ... now ;)
[22:02] <musashi1> on a reboot that is
[22:02] <bryang> should see it, and assign it as eth1, likely
[22:03] <musashi1> okay, i'll stick one back in and see what happens
[22:03] <bryang> we will have to manually configure it to server clients
[22:03] <bryang> s/server/serve/
[22:04] <bryang> and for completeness we could try another install w/just two (to flesh out a bug report) ;)
[22:06] <musashi1> not another install...
[22:06] <bryang> heh, (at least) one more for the good of the community
[22:06] <musashi1> i think i did 5 today
[22:07] <musashi1> maybe tomorrow but not today
[22:07]  * bryang nods
[22:11] <musashi1> seems okay with the second nic. it boots and ifconfig shows eth0 and eth1
[22:15] <musashi1> i have to head out soon. thanks sbalneav, bryang. as promised :)  http://laughingsquid.com/wp-content/uploads/anchor_beer.jpg
[22:17] <bryang> priv msg has details to conf that interface
[22:19] <scrapbunny> hello- is there anyone here that has used dell gx110's as edubuntu thin clients?
[22:23] <Stormzoeker> /q
[22:26] <musashi1> cya. thanks again