[02:46] hey everyone [06:34] Does anybody have a killer app they want to share for middle schoolers? I know lots of cool stuff for little ones and older ones, but the middle is hard [06:34] quake3? [06:34] lol jk [06:38] :P [06:39] i never had a computer in middle school [06:39] or access to one [06:39] that's including at home [06:40] didn't get my first computer til i was 17 [06:40] ie: 1998 [06:40] heh [06:41] and that was a "family computer" [06:41] didn't get my own til almost 2000 [10:04] hey [10:09] * robzhei needs help with LTSP problem after clean install of Edubundu! [10:56] anyone alive ? [10:58] Hey - has anyone here had any experience with edubuntu LTSP? I have some questions :) [11:07] hehe me 2 [11:07] just ask [11:07] if someone knows they'll answer [11:08] yeah, true enough. [11:08] My thin clients hang after trying to boot, they hang after the edubuntu logo with no error msg [11:09] aren't there debugging hints on the website? [11:10] I'm looking into setting up a (rather large) network in a school i do tech work for. At the moment, I've got a Win 2K network up and running and the place is getting on grand. I'm getting increasingly worried by the amount of licenses that they have to pay for whenever a new shipment of machines arrive or is donated, so I'm looking into the possibility of an LTSP project. [11:11] My biggest issue at the moment is calculating the hardware requirements. I've managed to source a dual xeon (800mhz if i remember correctly) and that's been chugging along happily as the PDC for the windows domain [11:12] there's a possibilty of me getting a second server of similar specs, but i want to be sure that i'm not getting in over my head here [11:12] so that's why i'm here to ask questions about edubuntu, ltsp, and anyones experiences [11:12] :) [11:12] * zoro stops typing [11:13] the ram is what you need more of [11:13] it's in the edubuntu handbook [11:13] recommendations that is [11:13] and depending on the thin clients, some apps can run locally.. which could change the balance of power [11:13] so think about your setup first [11:15] yeah i've read the handbook, but i find it lacking in a couple of areas. also, i dont fully understand how the locally-running apps system actually works - do i install edubuntu on those boxes as well as on the server? [11:15] at the moment there are 70-80 client machines, all of which would be able to run apps locally [11:15] i'm looking to make this as centrally controlled as possible so that the computers teacher can do basic admin things when i'm not there [11:18] no [11:18] you install the apps in the chroot [11:18] altho that's still in development to do it easier [11:18] problem seems to be getting the friggin clients to work at all [11:18] ;) [11:18] :) [11:18] just mentioning it, depends on your client specs [11:19] well look at the ram requirements [11:19] johnny: yeah, well ideally i'd like to push some of the load out to the clients, considering they're more than capable of it [11:19] the handbook does mention those [11:19] * zoro nods [11:19] yeah, but only briefly and it doesn't really go into much detail [11:19] anyway, thanks for your help - i'll idle in here incase anyone else has any input [11:21] it goes into enough detials imo [11:21] it even has an equation :) [11:21] use that as the very base line [11:21] yeah [11:22] is it possible to spread server load across more than 1 server? [11:23] ugh. i should really read before i jump in [11:24] join #ltsp if you want more info on that [11:24] yeah.. read some [11:24] and ask the folks in there [11:24] thanks for your help [11:24] you'll get more general ltsp folks in there [11:24] who manage large installs [11:24] and such [11:36] ogra: aufs is now in git thanks to juliank and it's working great with mythbuntu-diskless. (just need to wait for another patch to be applied and the next kernel upload) [11:37] nice [11:38] wtf is aufs ? [11:38] mdz was pretty pleased to hear about it btw, we talked a bit at the sprint last week [11:38] takes 27s from power-on to X in my VM. :) [11:38] johnny, another unionfs [11:38] aha [11:38] will it appear in the krnele? [11:38] yes [11:38] don't ask me how the e got transposed to the end :) [11:38] well, l-u-m [11:39] l-u-m ? [11:39] linux-ubuntu-modules package [11:39] aha [11:39] ah, nice [11:39] thanks guys [11:39] you rock [11:39] you make me very happy this lovely morning [11:40] ogra: you'll finally get my initramfs patch by the weekend. if you don't mind i'll add aufs support for tmpfs, too [11:41] as long as it stays optional i'm open for everything :) [11:41] sure. [11:42] * laga is really happy about aufs [11:44] hey ogra ... [11:44] edubuntu meeting in 15 ? [11:44] RichEd, hey [11:44] sigh, yes :) [11:45] * ogra is testing isos aside ... dont expect to much from me [11:52] === edubuntu meeting in #ubuntu-meeting == in 10 mins === [11:53] * ogra goes to prepare fresh coffee .... [11:57] RichEd, thanks for the reminder [12:00] === edubuntu meeting in #ubuntu-meeting == now === [12:10] johnny, no interest in the meeting ? [12:27] sorry.. i was playing guitar hero [12:27] wakeup music [12:59] ogra: I'm generating -i386 + -amd64 debs for iTalc so you can give it a try and see the bug by your own eyes. The debian/ dir is maintained in bzr [12:59] euhm... edubuntu server install hangs when installing britty-x11 anyone know why? :P [12:59] robzhei, try installing without, and then installing it later [12:59] as a quick fix [13:00] robzhei, which release/iso ? [13:00] 7.10 [13:00] * ogra hasnt seen anything like that [13:00] sounds like a borked iso [13:00] did you check the md5 sum after download ? [13:01] and also try the CD selfcheck from the CD menu [13:01] mm the imgage is fine, installed from it 5 times be4.. this is second cd burned from it... [13:01] at what speed ? [13:01] note the data is highly compressed ... [13:01] you shouldnt burn faster than 8x [13:01] first cd 52x hehe, second 16x [13:01] that can generate read errors [13:02] they would expose win the sleftest though, try that out first and see if it gets through [13:02] wellwell.. tryin again then ;) [13:15] hrmm, I just noticed I wasn't even in here [13:20] ogra: http://www.stgraber.org/download/ubuntu/italc/ [13:21] stgraber, hey thanks [13:21] i'll test it tonight .. (got to prepare for platform meeting now) .... [13:29] ogra: OK, what is up with the desktop files now [13:30] nixternal, well, on the classmatePc it takes very long to start apps ... [13:30] usually the timeout of the startup notification plus some seconds [13:31] the kdeedu apps all dont use startup notification [13:31] which is shown for about 15-20 secs [13:31] if it takes an app 25 secs users think te click didnt get through and click multiple times [13:32] which is really bad for a classmate with reduced ressources [13:32] gotcha [13:32] well, and generally i'd consider it a bug anyway ... :) [13:32] do some of the apps use the notification? [13:35] none of kdeedu [13:35] which is no prob in KDE i think [13:36] as it uses a different mechanism [13:38] hrmm, any suggestions on an easy fix at all? [13:38] adding StartupNiotify=True to all .desktop files [13:38] i was planning to look into that anyway ... but indeed appreciate if someone else takes the task :) [13:39] i need it fixed for the classmate image in any case [13:39] X-KDE-StartupNotify=true [13:39] actually I see those in quite a bit of the kde apps .desktop files [13:39] I will look into it [13:40] probably its enough to drop X-KDE- from taht ? [13:40] I will ask Riddell and see what he says [13:40] yeah [13:40] thanks :) [13:58] ouch, missed the meeting and forgot to join this channel [13:58] my bad [13:58] ogra: riddell wants to know by adding that, what exactly does it change and is this only for the classmate? [13:58] hmm.. there is a bug filed to sabayon [13:58] also is this recent or has it been ongoing? [13:58] with startup notify not working well with gksu [13:59] the busy icon sticks around for too long [13:59] but it happens on my other things in the admin menu too [13:59] and on my gentoo install as well [14:00] nixternal, it makes the gnome desktop startup notification work (turning the cursor into a clock/rotating circle until the app is up) [14:00] very much like the bouncing cursor in KDe [14:01] how come that still requires a flag? [14:01] does the app start up though? [14:01] it is just that the busy cursor sticks around until timeout is reached? [14:01] you're asking me? [14:01] ogra ^^ :) [14:02] ogra, would you know what to do about my bug tho:) [14:03] nixternal, if the app is faster than the timeout the notification lib gives feedback and switches the cursor ... else it stays until timeout [14:03] on classmate thats critical because apps definately exhaust the timeout [14:03] except when run via gksu.. [14:03] roger that [14:06] ogra: Riddell said that if effects all apps it sounds like they (you) should adjust their timeout rather than edit all apps...I hope I am not skewing this at all...maybe you should talk to him and make it clearer than I could possibly do :) [14:06] nixternal, what do i gain by adjusting the timeout to something thats never fired up ? [14:07] the missing var keeps startup niotification from firing at all [14:07] which means no feedback at all for a click [14:33] ogra, how come the files needed edited? [14:33] seems kinda backwards [14:33] shouldn't the default be for startupnotify [14:33] and then disabled in the .desktop files? [14:33] johnny, KDE vs GNOME ... [14:33] bastads [14:33] they have different notification implementaions it seems [14:35] hmm.. that's fine.. but they do they need seperate switches? :) [14:36] usually the X-DESKTOPNAME says to switch off a feature on the other desktop [14:37] and omitting that prefix makes it a global setting === freeflyi2g is now known as freeflying === RichEd-1 is now known as RichEdd === RichEdd is now known as RichEd [15:45] RichEd: you really here? [15:45] LaserJock: not all here ... but some of me :) [15:45] good enough [15:45] just read through the meeting logs [15:47] the question with the menus is whether to make alacarte handle the dynamic menu editing from within itself or to write a wrapper that calls alacarte and "fixes" stuff after its done [15:48] ogra, I think, (and me too really) prefers to have alacarte handle the whole thing [15:49] but that's a lot more hacking than doing a wrapper and it needs to be done upstream, which I'm not sure they'd take [15:49] so I guess perhaps what needs to be done is to ask upstream if they'd even consider patches for such a thing [15:50] ogra: is ^^ about right? [15:59] i need help i just installed ubuntu but i get a black screen i think it because i installed my pci card [16:00] chucky: did the install complete ? [16:00] yeah [16:00] so do you see all the booting, but then black screen follows ? [16:01] yeah [16:01] and did it work before you installed the pci card [16:02] this is after i installed my pci softwear [16:02] give me a minute [16:03] it told me to reboot then just got a black screen [16:04] and i cant even boot from cd [16:05] woops ... if you insert the CD: [16:05] #1 can you see options [16:05] #2 and select run as live CD [16:06] just black screen man [16:06] do you at least get the bios info before it starts the os [16:08] ok when i restart i get the bios then the loading ubuntu sereen the black [16:08] then* black [16:09] sounds like the text mode is okay with the display card/'adaptor ... but not the graphics mode [16:10] yeah is there a way to bypass that [16:10] or something [16:10] you may be able to boot to the terminal prompt, staying in text mode, and then run a command line display setup [16:11] i don't know how to [16:11] lol sorry im new at this [16:11] * RichEd is looking for some help for you [16:11] no problem :) [16:15] okay ... try this: boot the machine and wait until the hard drive activity stops [16:15] then: "ctrl+alt+f#" for a command prompt [16:16] then: log in with your username and password at the prompt [16:16] then: sudo dpkg-reconfigure xserver-xorg [16:16] that will allow you to reconfigure the graphics card setting [16:16] If you don't have the right video driver installed, try a basic VESA configuration to at least get the desktop going. [16:19] lol how do you i make the F#? [16:20] ctrl+alt+ any of your F keys (from 1 to 6) [16:22] ok i tryed it but i got lots of letters going down the screen but that it went black screen again [16:23] i can hit Esc and the first and brings up this recovery mode [16:24] thats all i can do [16:31] is there anything i can do from the recovery mode? [16:40] chucky: can you log in ? [16:41] no man [16:42] give me a minute [16:42] ok [16:45] chucky: so what do you have in front of you now ... a login prompt ? [16:45] black sereen [16:45] so recovery mode takes you to a black screen ? [16:46] it sounds to me like a hardware issue now ... [16:46] no hold on [16:49] ok i got 3 choices 1 kernal 2.6.22-14-generic "2"kernal 2.6.22-14-generic revoverymode and 3 memtest86 [16:52] i jumped in recovery and its says Root@chuck-desktop:~# [16:53] Root@chuck-desktop:~# and i think i sopose to put something here [16:53] lol [16:53] progress :) [16:53] now try this: [16:54] sudo dpkg-reconfigure xserver-xorg [16:56] ok it took me somewhere [16:57] it should give you a display set up ] [16:57] try that ... [16:58] this is the last bit of info from the forum post I have been using to help you: [16:58] "If you don't have the right video driver installed, try a basic VESA configuration to at least get the desktop going. [16:58] If it doesn't work, just repeat the process until you get somewhere (or give up....)" [17:00] lol it says Attempt to autodetect video hardware [17:00] ? [17:01] try it [17:09] holy F%%#&$ it worked [17:09] man thanks alot [17:09] * RichEd cheers [17:10] what did it find ? the correct name of the card ? [17:10] next time, do the hardware changes *before* the install ;) [17:12] no i know wnat kind of kind of card i have i remembered it took some thinking [17:12] lol [17:13] but i just installed any kind i think [17:15] but really RichEd thanks alot man [17:15] cool ... as a note: if yuou [17:15] bah [17:15] as a note: if yuou [17:16] ahem ... let me try that again [17:16] as a note: [17:17] if you now go into [System] [[Preferences]] [[[Screen Resolution]] [17:17] you should be able to select the best resolution for your screen/card combo [17:17] if you *cannot* get to a decent setting, you may have a funky display card that does not have a default driver [17:18] in which case, you may need to get the correct driver [17:18] ok [17:18] let me know if this applies to you ... i.e. if you are not happy with the screen resolutions available [17:20] everything is good [17:20] 1280X1024 [17:22] man im vary happy [17:22] thanks again [17:28] * RichEd takes a bow for ubuntu [17:56] LaserJock: I'm upstream for alacarte :) [17:57] I'm aware of that [17:57] ;-) [17:58] I also know that you've said before you were more interested in other things and so I wasn't sure if you'd be interested in hacking on this [17:58] but I suppose a ping wouldn't hurt [17:58] Amaranth: ping ;-) [17:58] heh [17:59] lol [17:59] I'm not interested in doing the work but I might be willing to take a patch [17:59] Amaranth: I'm not even sure how to go about it directly in alacarte [18:00] one of the problems I have with directly editing the menus from alacarte [18:00] is that the menus are dynamic and composed of different groups [18:00] so if I say "Edit this menu" what menu am I editing? [18:02] and then I'd also have to deal with creation of new menus/groups [18:02] I gotta run to a meeting, bbiab [18:03] Right, this would be an extension of root menu editing (which alacarte doesn't support yet) [18:04] A Novell guy got permission from me to work on this feature in a branch but the first thing he did was hack it up to add SuSEisms and then he added the feature in a horrible way and never came back to me for review [18:04] So someone still has to do that work [18:08] hmmpf [18:09] (no boss, short meeting) ;-) [18:09] well I can edit the menus sort of OK but giving XDG_CONFIG_HOME to alacarte [18:09] but that's sort of a round-about hack [18:09] hehe, yeah [18:09] that kinda works [18:10] Not sure if I'd trust pressing the Revert button [18:12] hmm, haven't tried that [18:12] my initial thought was to do a GUI that basically wrapped around that concept [18:12] so it gave you a list of menus you could edit, when you clicked on "edit" it'd fire up alacarte via XDG_CONFIG_HOME, and then after alacarte was done it'd "clean up" [18:14] yeah, i think we discussed this before [18:14] that was the easiest route [18:16] basically I'd love to see more dynamic menuing done upstream, like fd.o or gnome [18:16] but I'm not sure people see the need yet [18:18] Well, right now alacarte is basically unmaintained so... :P [18:19] I have a local version that's a rewrite using vala that's almost done, I'm not too interested in the current code [18:20] ogra: can you talk for a sec about squeak? I'm at a bit of a block [18:20] Amaranth: that's what I figured. [18:21] LaserJock, no way to handle it through transitional packages ? [18:21] you say the names are totally different anyway [18:21] so even conflicts/replaces should work [18:22] ogra: right, the names are different, different source packages build the same binaries [18:23] good stuff like that [18:23] so my idea was to completely remove squeak from the archives [18:23] and then upload the new ones with conflicts/replaces [18:24] *but* my problem is that the new packages use different start scripts, and different locations for storing stuff in ~/ [18:24] I don't see any easy way of making sure people who ran squeak in Gutsy can just dist-upgrade and run the same in Hardy [18:24] so I guess my question is if that is OK? [18:24] as much as i hate to say that ... debconf note [18:25] is the stuff binary compatible ? [18:25] yes [18:25] it's still squeak [18:25] i.e. can we move the content of eth user dirs over ? [18:25] it's just that squeak is such and aweful mess [18:25] yeah [18:25] that each time you package it you implement a new way of starting/storing [18:25] well, add a script to do the copying a user can execute [18:26] and add a debconf note if you detect an upgrage from an old squeak version [18:28] similar to the one alsa uses currently [18:28] ogra: hmm [18:28] ok, maybe I should get the old ones removed and new packages uploaded ASAP so I don't hit FeatureFreeze [18:28] then do the debconf thing as a bug fix [18:29] cause I dont' think I can get that all done before FF [18:30] dont forget FF is also UVF ... [18:30] well, that's what I'm saying [18:30] the valentine freeze :) [18:30] I can basically upload the new packages as-is [18:30] and then work the debconf/upgrade handling after [18:30] ogra: is this already implemented in ltsp-manager? http://people.ubuntu.com/~ogra/LTSPManager/ltsp-manager_building_client.png [18:31] basically assuming I can break Hardy a little bit before fixing it [18:31] laga, ltsp manager is only a gui ... no backend yet ... but that part i got separately .... [18:31] LaserJock, indeed ;) [18:31] ogra: i'd love to have that progress bar. :) [18:33] http://people.ubuntu.com/~ogra/gtk-build-client/ [18:34] https://code.launchpad.net/~ogra/ltsp/ltsp-build-client-gtk <-- code branch [18:34] thanks [18:36] there is also that ... https://code.launchpad.net/~ogra/ltsp/ltsp-image-shell ... shots: http://people.ubuntu.com/~ogra/ltsp-image-shell/ [18:38] ogra: thanks. is https://code.launchpad.net/~ogra/ltsp/hardy-trunk the right branch to generate patches against? [18:39] thats the package branch ... its a snapshot of the ltsp-upstream branch ... i plan to do one last upstrem pull before feature freeze (feb 14th) [18:39] until then making patches against the upstream branch is better [18:40] after FF thats the right one :) as i wont pull new upstream stuff [18:43] LaserJock, are you happy so far ? i tend to call it a day [18:44] ogra: hum. the upstream branch does not have a debian/ directory, right? [18:44] eg for packaging [18:44] right [18:44] for the debian stuff just take the package itself for now [18:44] k [18:44] i'll push a branch with its content this week ... [18:45] ogra: for now yes :-) I wanted to get an idea from you about squeak before I started doing all the removal requests, NEWing, etc. [18:45] but since usualyl i'm the only uploader dont worry :) [18:45] good :) [20:00] ogra: something is definitely wrong with the network part of italc [20:00] ogra: I'm doing local testing with the packages I uploaded earlier, when starting the standard way (ica -role teacher and italc -role teacher), both ports are opened on my laptop 5800 + 5900 [20:01] then once the italc UI is opened, I see some "unable to connect" errors and the 5900 port is now closed [20:02] a part from that italc seems to try connecting on the right ports, everything is fine from that side so my ltsp scripts will work correctly if the current bug is fixed [20:02] (but that's the VNC part of italc and it's scary :)) [20:10] hello [20:11] how can i find the problem with my sound? ive installed with this manual: http://developer.novell.com/wiki/index.php/Edgy/HOWTO:_PulseAudio [20:12] i use a ltsp5 on the current stable debian [20:13] when i log in local to the client and start: alsaconf, i can play wav with aplayer.... but i cannot start pulsesound on the client... it exit with this message "startup failed" [20:49] mcfloppy_: you running debian or edubuntu ? === reh is now known as mcfloppy [21:07] mcfloppy: you running debian or edubuntu ? === john_ is now known as john_s