**** BEGIN LOGGING AT Sat Jul 16 02:59:57 2011 Jul 16 03:00:14 elpollodiablo1, that's not a fatal error Jul 16 03:00:27 I get that on lots of things, but it doesn't stop them from building Jul 16 03:00:41 I'm not even sure it's an error, more like a notice Jul 16 03:00:52 after that is says exit2 error2 blah blah blah Jul 16 03:01:06 rwhitby, nm, I got X running; it was picking up old libs from /usr/local/lib Jul 16 03:01:06 it is a warning Jul 16 03:01:17 but it quits after that step with not details Jul 16 03:01:27 elpollodiablo1, are you parallel building? Jul 16 03:01:47 no,?? Jul 16 03:01:52 sometimes that can hide errors, at least then aren't at the end of the compile output Jul 16 03:01:58 what do you menan by parallel building? Jul 16 03:02:14 make -j(something) Jul 16 03:02:29 nope just make stage package Jul 16 03:02:58 in the package/x/xserver-package directory Jul 16 03:03:39 elpollodiablo1, which package is it exiting on? the x-server or a dep? Jul 16 03:04:31 I am trying to make xterm right now seeing if that works or not Jul 16 03:04:36 wil try again shortly Jul 16 03:04:38 elpollodiablo1, can you pastebin the last 100 or so lines of build output? Jul 16 03:05:30 I see the zombie. Jul 16 03:08:33 the zombie is a sh, but the parent of the zombie is /var/usr/sbin/org.webosinternals.xecutah Jul 16 03:10:23 * halfhalo goes to setup widk on his laptop. good times... Jul 16 03:12:11 jacques: confirmed Jul 16 03:19:34 so xterm built fine Jul 16 03:19:52 so I went back and tried xserver and it worked with no errors strange Jul 16 03:27:31 so how do you fine the zombie ? I have it all installed and xterm not loading Jul 16 03:29:48 ps will show it Jul 16 03:32:56 1 zombie (and then one will have a status of Z occasionally popping up.) Jul 16 03:36:38 ps only shows sh and ps Jul 16 03:36:40 also, in ps listing is has [] around it and after it Jul 16 03:36:45 ps -efwww Jul 16 03:36:58 oh, I have optware procps installed Jul 16 03:37:04 ps -e shows everything but I dont see any thing out of the ordinary Jul 16 03:37:50 ah I see it now Jul 16 03:38:01 sh Jul 16 03:38:07 in ps -ef Jul 16 03:39:18 I didnt know about that. cool thanks Jul 16 04:11:33 rwhitby, I'm ignoring the SIGCHLD and I don't get a zombie Jul 16 04:13:08 signal(SIGCHLD,SIG_IGN); // before the popen() call Jul 16 04:19:55 something is still not right though :-\ Jul 16 04:23:51 I get no zombie, but the xterm is not started by xecutah, nothing in log either Jul 16 04:24:15 if I start xterm manually with the xecutah script, it works, and still no zombie, so that's an improvement from before I guess Jul 16 04:42:23 jacques: running the script manually never gives a zombie Jul 16 04:43:13 rwhitby, I got a zombie before I made the change though Jul 16 04:43:29 and now I don't Jul 16 04:43:59 I don;t get a zombie from xecutah, but the xterm doesn't start either :-\ Jul 16 04:45:27 rwhitby, if I want to switch between xecutah service binaries manually, how do I do it? Jul 16 04:45:46 I want to try with and without the SIG_IGN Jul 16 04:46:17 jacques: stop org.webosinternals.xecutah ; overwrite binary ; /var/usr/sbin/org.webosinternals.xecutah to run it manually and see the command execution debug prints Jul 16 04:46:36 rwhitby, thanks! Jul 16 04:47:35 jacques: the binary location must match that path Jul 16 04:48:23 rwhitby, BTW, the xecutah ipk seems to have the source and intermediate object files for the c-service in it Jul 16 04:48:43 yep, that's probably true Jul 16 04:49:00 easy GPL compliance ;) Jul 16 04:50:00 heh, probably don't need the .o files though :-) Jul 16 04:50:22 that's in case there's any LGPL ;) Jul 16 04:50:44 lol Jul 16 04:59:51 rwhitby, when I do /var/usr/sbin/org.webosinternals.xecutah manually, I get no output and no xecutah Jul 16 05:00:07 oh nm Jul 16 05:00:16 that's just the service (duh) Jul 16 05:02:48 with original xecutah, as soon as I start the xserver I get a zombie, and then trying to start the xterm apparently does nothing (no output from xecutah) Jul 16 05:04:30 with the sig_ign xecutah, I *don't* get a zombie from starting the xserver, but I also get no output when trying to start xterm Jul 16 05:08:00 jacques: that's cause with a zombie, the service is blocked and will not accept another request from the app Jul 16 05:10:07 and for some reason, the behavior is different on 1.4.5 vs. later webos Jul 16 05:11:09 yep Jul 16 05:54:42 why not jsut set this stuff up through event.d and have xecutah just emit signals? Jul 16 06:15:14 cryptk: not a bad idea. Jul 16 06:40:54 then you would only have xecutah running one command, and we can do lots of cool things with emits and start-on's to do things like having xterm fire up it's own xserver if one isn't running already etc Jul 16 06:41:05 have an event.d for setting up and tearing down a chroot etc Jul 16 07:00:02 rwhitby, if we do it that way then it may even work on 1.4.5 Jul 16 08:30:07 cryptk: indeed it does (already tested) Jul 16 08:33:50 dtzWill: I'm going to change everything over to upstart. Jul 16 08:36:24 dtzWill: I think I'll rename the legacy repositories too, and change xlauncher to xserver and xterm-launcher to xterm Jul 16 08:50:10 pushed 0.7.0 to autobuilder Jul 16 09:09:33 rwhitby, AWESOME!!! so it worked! Jul 16 09:12:44 rwhitby, on a side note... the launcher doesn't report a version for Xserver or Xterm... and we should probably UIRev2 the headless app for those Jul 16 09:13:04 since there is no back button needed, we should be able to just throw UIRev2 in there and call it done Jul 16 09:37:11 rwhitby, I'm getting unknown job errors when trying to launch xserver or xterm from xecutah using the new testing feed versions Jul 16 09:38:51 yep, fixing that now Jul 16 09:44:29 0.7.1 in feeds now Jul 16 09:49:48 oops, xserver still coming Jul 16 09:50:15 yep Jul 16 09:50:48 and I still get unknown job org.webosinternals.xterm but that may be because there is no xserver running... not sure Jul 16 09:51:12 now xserver 0.7.1 is there Jul 16 09:51:57 gah, still wrong Jul 16 09:52:47 perhaps it needs tweaks ;) Jul 16 09:55:08 hmm 0.7.1 should work Jul 16 09:58:49 ah, upstart dir not copied Jul 16 09:58:53 yep Jul 16 09:59:02 I jsut novatermed in myself and didn't err the files in there Jul 16 09:59:07 s/err/see/ Jul 16 10:01:52 reinstall xterm and xserver 0.7.1 from the feeds (I didn't bother changing versions) Jul 16 10:02:38 kk Jul 16 10:06:03 rwhitby, is removing the headless app supposed to remove xterm and xserver? Jul 16 10:07:22 should do Jul 16 10:07:31 it didn't Jul 16 10:07:31 but since the control scripts weren't there it may not have had a prerm Jul 16 10:07:44 and starting xserver worked... can't get xterm to start though Jul 16 10:12:28 running it manually from nvaterm worked though Jul 16 10:12:47 yeah, i know the problem Jul 16 10:15:31 and while start starts them... stop doesn't stop them Jul 16 10:15:54 yep, they are one-shots at the moment, no daemons Jul 16 10:17:15 gotcha Jul 16 10:22:27 ok, try 0.7.2 of all three Jul 16 10:23:55 installing Jul 16 10:25:12 ok, those should be it Jul 16 10:25:27 still broken horribly Jul 16 10:25:31 just kidding, works great Jul 16 10:26:10 how is initctl knowing where to finc the upstart scripts at? Jul 16 10:26:26 since they aren't in /etv/event.d Jul 16 10:27:05 they are in /var/palm/event.d Jul 16 10:27:46 ahh, is that location set up my webOS already? Jul 16 10:27:55 yep Jul 16 10:28:05 sweet Jul 16 10:28:16 I will look into making them full daemon to where they can do start and stop etc Jul 16 10:28:31 but only if I can get all of the stupid out of my ticket queue Jul 16 10:29:46 that would be good, thanks. Jul 16 10:29:57 we need to think about how to run multiple instances though Jul 16 10:30:43 hrm... not sure if upstart can track multiple PID's.... Jul 16 10:30:50 it cannot Jul 16 10:31:11 I wonder if we can do one Xserver with multiple displays Jul 16 10:31:18 each display gets it's own card Jul 16 10:31:43 similar to a multiple monitor setup Jul 16 10:33:15 I think the next thing we should really do though is RandR Jul 16 10:33:24 so we can get orientation changes and be able to toggle the VKB Jul 16 10:34:44 and getting some start-on and emit action going Jul 16 10:34:56 so things like xterm can fire up the xserver themselves Jul 16 10:38:36 well, I'm going to wait a day to see if there are any other teething problems first. Jul 16 10:39:24 and deprecate the old X windows apps and repos Jul 16 10:39:40 good plan Jul 16 10:40:04 get everything stable with the correct names before going forward. Jul 16 10:44:08 * rwhitby bbt Jul 16 10:44:13 indeed Jul 16 11:34:01 rwhitby, whenever you get this... multiple xservers in cards does work Jul 16 11:34:31 just give them different display numbers and you are golden Jul 16 14:24:29 Good work guys... Jul 16 21:11:30 cryptk|offline: I know they work - the question is how to use upstart to create them and still be able to kill them using upstart Jul 16 21:42:30 dtzWill: ping Jul 16 21:56:43 morning rwhitby Jul 16 23:01:44 Dear Dropbox: PLEASE behave nicely with my bandwidth Jul 17 00:17:27 ok, I've got ubuntu-natty-chroot to build successfully in build.git Jul 17 00:17:53 now to work out how to do an upstart script to mount it Jul 17 00:26:51 rwhitby: does the homebrew documentation app bring in decent money? Jul 17 00:27:07 depends what you define decent Jul 17 00:28:05 I dont mean anything you can live on but just something to suport the hardware and resource need to keep webos-internals running Jul 17 00:28:24 normal donations do that Jul 17 00:28:55 PHD is my personal revenue stream (minus 10% which goes back to the group) Jul 17 00:29:24 oh alright, so is that just profit Jul 17 00:29:35 nice Jul 17 00:30:44 glad you are making some money through the official app catalog channel Jul 17 00:31:42 It has only just got to the point where it has paid for my laptop. Jul 17 00:31:53 you put so much time and effort into homebrew and this platform. Jul 17 00:32:18 well atleast it is some help Jul 17 00:53:20 ka6sox-farfarawa: ping Jul 17 00:53:33 yes? Jul 17 00:54:03 I now have an autobuilder package which can build and install a ubuntu chroot in /media/ext3fs/ubuntu-natty-chroot Jul 17 00:54:27 how shall we start the chroot and enter it? Jul 17 00:55:11 optimum would be an Xecutah button which opens an xterm with you sitting inside the chroot with DISPLAY set correctly and all bind mounts in place. then when you exit that xterm the chroot is torn down. Jul 17 00:55:48 unless we take the same approach as Palm jails and just leave all bind mounts in place Jul 17 00:55:50 can't tear down the chroot from inside. Jul 17 00:55:59 I'd rather not Jul 17 00:56:16 because palm knows about those. Jul 17 00:56:21 but not ours. Jul 17 00:56:44 ok, so I have an XServer running. I want to start a chrooted xterm in it, and I want the chroot to be torn down when I exit that xterm. Jul 17 00:56:54 what is your suggestion? Jul 17 00:57:13 are you leaving the xserver running afterwards? Jul 17 00:57:19 yes Jul 17 00:58:00 but if the card is thrown away, (and therefore the xterm exits), then the chroot should be torn down Jul 17 00:58:09 I want to test 1 thing before I say... Jul 17 00:58:23 I want to test a script in the base that calls the chroot and waits. Jul 17 00:58:36 waits till it exits and then continues Jul 17 00:58:52 I was thinking we have a script, which is called from upstart, which mounts, runs xterm, waits, then unmounts when xterm returns. Jul 17 00:59:04 agreed. Jul 17 00:59:23 its a question of whether we can have that script wait when we call the script in the chroot Jul 17 00:59:47 why would we be calling the script *in* the chroot? Jul 17 01:00:11 we would just be starting a shell in the chroot Jul 17 01:00:16 the script in the chroot binds the display and starts xterm Jul 17 01:00:38 I was going to do that outside, and have xterm do the chroot as the first command Jul 17 01:00:59 so xterm is running outside, but the shell it runs is inside Jul 17 01:01:26 I guess I'm thinking about it the other way around so you could start a WM Jul 17 01:02:08 or any random app in the chroot.... Jul 17 01:02:08 ok Jul 17 01:02:35 just wait for the exit after the app gets done Jul 17 01:02:54 that would break the chroot and get you back to the base Jul 17 01:02:58 I'm thinking that is a subsequent item to look at it. I was going to start simple. Jul 17 01:03:00 (or if the card dies. Jul 17 01:03:12 okay that would work. Jul 17 01:03:29 because it would wait till xterm dies and then continue Jul 17 01:03:58 let me try that...jas Jul 17 01:04:43 the other reason why I wanted xterm outside was so you didn't actually need X libraries in the minimal chroot Jul 17 01:05:13 what would the chroot gain you then? Jul 17 01:05:28 over a stock xterm. Jul 17 01:05:44 access to all the programs in the chroot Jul 17 01:05:52 without the xlibs? Jul 17 01:05:54 which you can choose to apt-get or not Jul 17 01:06:18 oh, you are talking command line stuff... Jul 17 01:06:19 if you want a program that uses xlibs, they get pulled in when you apt-get that program Jul 17 01:06:26 right. Jul 17 01:06:55 that would make the initial chroot much smaller to get Jul 17 01:07:22 since you could treat xterm as a "console" Jul 17 01:07:30 yes Jul 17 01:08:17 have you tried calling xclock and seeing if it pops up a new display window? Jul 17 01:10:47 what do you mean by 'display window' ? Jul 17 01:11:15 isn't our X-server rootless? Jul 17 01:11:39 no Jul 17 01:11:45 ok Jul 17 01:13:43 okay that works. Jul 17 01:13:53 call the chroot with a script.... Jul 17 01:14:04 when you are done and exit...it continues execution Jul 17 01:14:24 and tears down the bind mounts Jul 17 01:15:31 does this solve the 1.4.5 issue with not being able to call more than 1 thing? Jul 17 01:17:16 dunno Jul 17 01:17:30 hmm - touchpad keyboard now doesn't like shift keys Jul 17 01:17:32 okay let me see what happen when the chroot dies an ugly death. Jul 17 01:23:04 still works. Jul 17 01:23:15 how did you test that? Jul 17 01:23:23 rwhitby, you mean the real keyboard? I got mine in a strange stage where everything has capitalized :-\ Jul 17 01:23:42 ah, didn't work... Jul 17 01:23:48 I'm wrong Jul 17 01:24:29 if you kill -9 the thing in the chroot (which is what I'm told happens) the controling terminal is released and it doen't finish Jul 17 01:24:51 linuxjacques: if you press the shift key twice it should put it back to normal Jul 17 01:25:13 linuxjacques: I mean the on-screen keyboard when running 0.7.2 on a Touchpad Jul 17 01:25:14 elpollodiabo1, bt kb or onscreen? Jul 17 01:25:27 shouldnt matter Jul 17 01:25:58 ah Jul 17 01:26:10 I'll try that next time Jul 17 01:26:15 I believe they have the same functinoality. it is similar to how the pre shift works. Jul 17 01:26:27 ka6sox-farfarawa: I did: ./bin/xterm -display :0.0 -maximize -e "sh -x /media/ext3fs/ubuntu-chroot-wrapper.sh" Jul 17 01:26:51 where the chroot-wrapper does the mounts, then chroots, then unmounts Jul 17 01:27:02 also another thing I noticed is that if you hold a shift/modifier key in for a long period of time it makes it sticky and you have to hold it in again for a couple seconds to get it back to normal Jul 17 01:27:33 rwhitby, if you throw away the card it finishes? Jul 17 01:27:33 ka6sox-farfarawa: closing the card unmounted the chroot properly Jul 17 01:27:39 good. Jul 17 01:28:43 is this somewhere I can look at it? Jul 17 01:29:16 linuxjacques: that is one of the things I want to look into and change with the keyboard config Jul 17 01:32:45 rwhitby, I was thinking about starting the x-server, mounting the chroot, calling the chroot with chroot /media/ext3fs/natty-chroot/ /usr/bin/xdm, doing my thing then exiting out and unmounting outside Jul 17 01:33:23 or whatever app is supported inside. Jul 17 01:33:59 how does that scale? Jul 17 01:35:14 sorry, I meant to call a script inside that binds the chroot to display :0 and does what I want. Jul 17 01:49:53 what is the latest xterm in feeds (testing) Jul 17 01:50:55 yes Jul 17 01:51:13 (the latest xterm is in the testing feeds - 0.7.2) Jul 17 01:55:17 is your wrapper someplace? Jul 17 01:55:32 I want to compare it to mine. Jul 17 01:56:51 packaging it now Jul 17 02:03:53 ka6sox-farfarawa: look in nonworking/ubuntu-natty-chroot Jul 17 02:04:10 pushed Jul 17 02:04:14 kk Jul 17 02:04:17 let me pull Jul 17 02:07:42 okay ours are the same. Jul 17 02:08:01 I use -o bind but --bind works just as well. Jul 17 02:10:28 pushed a new postinst which preserves the chroot contents on upgrade Jul 17 02:10:52 Xecutah button works Jul 17 02:13:03 so we can't make this on our build server Jul 17 02:13:19 unless.. we add rootstock to our server Jul 17 02:13:40 and do we want to clone a server or a desktop? Jul 17 02:13:42 server needs to be running 11.04 too Jul 17 02:13:50 ya, Jul 17 02:13:55 so we can't autobuild this. Jul 17 02:14:05 unless I make a 11.04 chroot Jul 17 02:14:06 :D Jul 17 02:14:14 no, I have structured the Makefile so I can dump a tarball in there and it will use it Jul 17 02:14:19 kk Jul 17 02:15:05 but to follow the model I would debootstrap a minimal 11.04 system into a spot on the server Jul 17 02:15:12 then add rootstock Jul 17 02:15:19 then call that. Jul 17 02:16:19 which would let us autobuild it and be repeatable. Jul 17 02:22:45 so you just call the upstart and it takes care of the rest. Jul 17 02:23:02 is xecutah starting the x-server? Jul 17 02:27:26 nm Jul 17 02:41:25 okay setting up a test to see if I can get it to do what I want. Jul 17 02:45:01 cmake under widk is frustrating me. it can't find ncurses.h nor libncurses.so Jul 17 02:45:24 linuxjacques: WIDK setup page says to install cmake on the host Jul 17 02:45:47 rwhitby, yeah sorry, I meant using the host cmake to try to configure a widk package Jul 17 02:46:07 ubuntu-natty-chroot is in the feeds Jul 17 02:52:09 rwhitby, its ubuntu-11.04 chroot right? Jul 17 02:52:18 not ubuntu-natty-chroot. Jul 17 02:52:18 yep Jul 17 02:52:47 this ought to be interesting Jul 17 02:53:02 what? Jul 17 02:53:32 that package is org.webosinternals.ubuntu-natty-chroot Jul 17 02:53:33 I moved it... Jul 17 02:53:44 no I had to move mine out of the way Jul 17 02:53:52 it was at the same location Jul 17 02:54:17 (yes I know it wouldn't have bothered it) **** ENDING LOGGING AT Sun Jul 17 02:59:57 2011