=== asac` is now known as asac
=== tgm4883_ is now known as tgm4883
pittiGood morning04:36
tvoss_ScottK, ping05:07
tvoss_ScottK, for the effects/compositing setup: should be what comes as default when installing kubuntu-desktop05:09
ScottKtvoss_: OK.  Thanks.  In the video, the effects looked less transparent, but that may just be the video.  It would have been nice to see more actual compositing effects demonstrated and some KDE apps.05:14
ScottKI don't feel like I got much of a feel for it as it was.05:15
tvoss_ScottK, hmmm, I can try with vanilla X and see if I notice any changes05:20
tvoss_ScottK, any particular operation you want me to check except for playing around with it a little longer?05:20
ScottKI'd be interested to see various window switching effects, like present windows, , box switch, cover switch, as well as some of the other effects like the outline effect on a focused window and the dialog darken effect.05:24
ScottKI think seeing things like that are directly driven by kwin when using KDE apps would be more representative.05:24
ScottKsuperm1: Would you please update the mythbuntu metapackage/seeds: http://people.canonical.com/~ubuntu-archive/NBS/ttf-droid05:27
tvoss_ScottK, happy to do that, a screen cap is fine with you?05:34
ScottKtvoss_: Sure.  Just trying to get a better idea of it.05:35
=== ballock is now known as tokarbol
tvoss_ScottK, mind pointing me at the keyboard shortcuts to activate the effects you want to see?05:45
ScottKFor present windows, I normally move my cursor to the upper left corner.05:46
ScottKThe window switching ones are alt-tab05:46
ScottKI think ctrl f10 for present windows05:47
tvoss_ScottK, cool, thx :)05:47
ScottKthe outline effect should be visible if you have multiple overlapping apps in the screen and one has focus.05:47
ScottKFor the darken dialog one, you'll have to arrange to have something pop up a diaglog05:48
tvoss_ScottK, ack, any specific kde app you want to see?05:48
=== jono is now known as Guest59629
ScottKNo, it's more about the windeco/window than the contents.05:49
ScottKTrying to exercise the things that kwin has direct control over.05:49
tvoss_ScottK, sure05:51
* tvoss_ is off to kubuntu land for a minute or two :)06:00
tvoss_ScottK, uploading to u107:06
ScottKDoes that result in it going somewhere I can see it?07:06
tvoss_ScottK, hmmm, I assumed you would have a u1 account07:07
tvoss_ScottK, if not, where do you want me to put it?07:07
ScottKAnywhere public is fine.07:07
tvoss_ScottK, let me see, youtube should work07:07
ScottKI don't believe in storing data on systems I don't control.07:07
ScottKAt least not anything that shouldn't be public.07:08
tvoss_ScottK, fair07:08
tvoss_ScottK, I noticed that tracker is using quite a lot of cpu in the background. do you kick it off by default on session login?07:11
=== smb` is now known as smb
tvoss_ScottK, hth: https://www.youtube.com/watch?v=8sKQnDAPEA407:23
ScottKI don't think nepomuk uses that normally, but that's probably what it is.  It can bog things down a bit on first run.07:31
ScottKtvoss: Looks pretty good.  I get a much better sense of it from that.07:32
tvossScottK, cool, glad that I could help07:33
ScottKYou might want to mention that in the comments to the first one or something.07:33
tvossScottK, I will drop a mail to Jono07:33
dholbachgood morning07:48
seb128dholbach, good morning my german friend! wie gehts?07:48
dholbachhey seb128 - good good - yourself?07:50
seb128dholbach, I'm good thanks ;-)07:50
=== doko_ is now known as doko
brendandwhy is openssh-server not in saucy?09:55
pittibrendand: err, it better was.. and it is09:56
pittiopenssh-server |  1:6.2p2-5 |         saucy | amd64, armhf, i386, powerpc09:56
brendandpitti, apt-cache search doesn't find it09:56
brendandneither devscripts!09:57
brendandsomething is wrong with my install then (most recent daily image)09:57
xnoxbrendand: did you run apt-get update to get the package lists?!09:58
brendandnothing wrong with sources.list09:58
xnoxah, snap.09:58
brendandxnox, doing that now09:58
brendandxnox, that's a bug then, no?09:59
xnoxbrendand: apt-cache is fully offline, it only looks up things in the downloaded package files.10:01
brendandxnox, ah i know now - i couldn't get a connection during install because of a bug in ubiquity10:02
brendandxnox, ergo it didn't run apt-get update during install (succesfully anyway)10:03
xnoxbrendand: hence..... no caches. I do think that ubiquity in those cases should copy the stale cache from the cd though.10:03
xnoxbut not sure if this should be implemented or not.10:03
ogra_is there one ?10:03
xnoxogra_: let me check.10:03
ogra_i thought the cache is wiped during build10:03
ogra_to save space10:04
xnoxogra_: in /var/cache/apt/ pkgcache.bin is 5.1M and srcpkgcache.bin is 5.0M and nothing under archives/10:05
xnoxis that installed packages though?!10:05
xnoxogra_: all is there for main and restricted under /var/lib/apt/lists/ 12M10:06
ogra_hmm, could be a full cache should be bigger10:06
ogra_we wipe /var/lib/apt/lists/ though10:07
ogra_not sure the cache helps much without the list files10:07
xnoxbut lists files are there as well.10:08
ogra_oh ?10:08
ogra_inside the squashfs ?10:08
ogra_i always thought apt-setup handles them10:08
ogra_from casper10:08
xnoxogra_: http://paste.ubuntu.com/5807347/10:09
ogra_yeah, i see10:09
ogra_jodh, hey ho10:12
rbasakSo cgroups' kernel interface is changing, and non-systemd systems will need new code to cope: https://lwn.net/Articles/555920/10:16
rbasakHow much does this affect Ubuntu? Do we now need to write a cgroup manager?10:17
rbasakhallyn: ^^ will this affect LXC at all?10:18
pittirbasak: I don't think it affects upstart a lot, but ICBW; it will affect containers (but that's being discussed upstream) and logind (but that will be handled by upstream, too)10:18
xnoxpitti: rbasak: It would be interesting to know if/how it affects lxc on ubuntu and nested-lxc on ubuntu.10:18
pittiI asked stgraber about this the other day10:19
ogra_given an essential bit of our stuff today depends on lxc10:19
ogra_(touch, cloud)10:19
rbasakHow much do we need cgroup support in LXC?10:20
xnox.... all of it?10:20
ogra_without it it is just a chroot :)10:21
pittirbasak: for us this mostly amounts to pay attention to shipping matching kernel and lxc versions, AFAICS10:22
rbasakWithout cgroups there's still namespacing and apparmor10:22
rbasakI guess on phone it'll be bad if an app uses 100% CPU or something10:23
ogra_on the phone you will get issues with the running android init10:23
rbasakThanks for the comments anyway. I just saw the article and thought we might want to pay attention. I guess hallyn is the expert here for the LXC end of things10:23
jodhogra_: hi10:40
ogra_jodh, so we have some slight probs with the container handling on ubuntu touch ... and i was wondering if upstart could help us ...10:41
ogra_effectively we do not want the ubuntu system to handle certain things while android does the same inside the container10:41
ogra_i.e. see bug 119079210:41
ubottubug 1190792 in touch-preview-images "ueventd in a busy loop on container-flipped image" [High,Confirmed] https://launchpad.net/bugs/119079210:41
ogra_(we have plenty of such stuff)10:41
ogra_jodh, i was wondering if it would be possible to have something like an init-to-init-bridge between the two so we can see in upstart what happens inside the container to then adjust our event handling accordingly10:42
jodhogra_: so you're talking about having androids init in lxc emitting events to the host systems upstart?10:44
ogra_some kind of communication layer between host and container10:44
ogra_currently we have a lot of override jobs that i.e. look for the existence of a socket and then fire the ubuntu process ... thats horridly racy10:46
ogra_also bringing up the container on boot indeed costs several seconds, atm we can just wait for lxc-wait to make sure the OS inside the container is up, but that doesnt tell us if there is still stuff being processed ... racy again ...10:48
ogra_if we could instead have a listener for the specific in-conrainer job to start when the services inside the container runs we wouldnt have to wait for the whole container to be up and could start bits in parallel10:49
jodhogra_: I guess the hacky way might be to poll with tools like lxc-ls/lxc-ps/lxc-nestat, but awe mentioned that some android services aren't even ready when the sockets appear so maybe we'd need to consider some sort of android service that talks back to the host? don't know enough about this tbh.10:55
ogra_well, thats what i'm proposing :)10:56
ogra_have either a hook in androids init (if it knows enough to give us any info) or have a watcher process that tells upstart about started processes10:57
ogra_and yeah, apps can indeed create sockets before they are ready and fully attached, thats one of the probs we have10:57
ogra_what we currently plan (and wich is really ugly) is for i.e. ueventd have it create a file in a shared space once it is done (kind of a udevadm settle with files) and have udev have a file-bridge handler watching it11:00
ogra_i'm not proposing this for 13.10 but i think we should plan something similar for 14.0411:01
ogra_(unless you think it's super easy and a thing of a days work to implement :) )11:01
dokojamespage, could you have a look at all the maven build failures in the test rebuild?11:06
jodhogra_: you could do that now:11:07
jodhogra_: 'start on file FILE=/var/lib/lxc/raring/rootfs/tmp/foo EVENT=created'11:07
ogra_not really, /var/lib/lxc/raring/rootfs/tmp/foo would never show up11:08
jodhogra_: ?11:08
ogra_ /var/lib/lxc/raring/rootfs is only the input  your container runs somewhere in /proc11:09
ogra_so files created in /tmp would show up in /proc/$lxc-pid/root/tmp ...11:09
ogra_but we dont have $lxc-pid unless we explicitly process lxc-info output11:10
jodhogra_: a watcher process sounds like it would get more traction that hacking androids init, but I don't know what env is available to allow it to talk back to the host. maybe those that know lxc+android better than I could comment on a bp if you raise one?11:13
ogra_you can create a socket in /dev/socket, thats shared for example11:13
ogra_and /data will always be a shared dir since binary blobs depend on it on both sides11:14
ogra_but while we will likely use the file approach through /data i dont think thats a proper solution11:15
ogra_(in the long term)11:15
=== MacSlow is now known as MacSlow|lunch
ogra_jodh, oh, btw, i had tried to watch a socket with the file bridge ... seems i cant, it only seems to act on regular files, do you consider that a bug ?11:47
hallynrbasak: pitti: the actual kernel cgroups changes are somewhat independent of the systemd announcement12:35
hallynat some point it'll require a single unified hierarchy - that's no problem for us12:36
hallynlemme find the most soothing email in the thread,12:36
hallynrbasak: ^ tl;dr : we'll all be experimenting for awhile and coming up wtih a new api12:37
jodhogra_: the bridge is using inotify, so I guess it's a limitation of inotify.12:37
hallynthe api is to set on *top* of cgroupfs, and we do want such a thing.  But if we want to be phillistines, we can always keep using cgroupfs :)12:37
=== wedgwood_away is now known as wedgwood
=== MacSlow|lunch is now known as MacSlow
tvoss_didrocks, what is the blessed way to install a symlink from a packaging setup?13:19
didrockstvoss_: just do it like in a file, ship it, then dh_links will do the right thing for you :)13:19
=== _salem is now known as salem_
didrockstvoss_: you can force creating some shipping debian/<package>.links (man dh_link)13:20
tvoss_didrocks, thx13:20
didrocksyw :)13:20
roadmrxnox: hi! about bug 1194195, the binary package depending on gksu was checkbox-gtk, so all should be peachy if I remove that particular dep, right? (I'll be adding a depends on policykit-1 instead, in addition to code changes)13:53
ubottubug 1097816 in checkbox (Ubuntu) "duplicate for #1194195 Checkbox needs to use pkexec instead of gksu" [High,In progress] https://launchpad.net/bugs/109781613:54
=== kentb-out is now known as kentb
xnoxroadmr: yes.14:19
roadmrxnox: ok, great! thanks. A fix should land in a few days then :)14:19
xnoxroadmr: awesome.14:20
jdstrandmdeslaur: I've created a apparmor-easyprof-ubuntu package to ship our templates and policygroups14:22
infinitymterry: To be clear on bug #1188935, were you okay with that being promoted despite the testsuite bug, or did you want that fixed first?14:22
ubottubug 1188935 in python-secretstorage (Ubuntu) "[MIR] python-secretstorage" [Undecided,Fix committed] https://launchpad.net/bugs/118893514:22
mdeslaurjdstrand: ok14:22
jdstrandmdeslaur: the current version is 'ubuntu-0'. ie, things are installed in:14:22
mterryinfinity, I'm OK despite the test suite bug.  I just want the test suite bug fixed this cycle ideally14:22
mdeslaurjdstrand: version 0? :P14:23
mdeslaurjdstrand: odd choice :P14:23
infinitymterry: Check.  Promoting, then.14:23
mterryOr whenever gnome-keyring can be run under xvfb14:23
jdstrandmdeslaur: I used 'ubuntu-0' just for namespacing. ie, the json manifest would use '"policy_version": "ubuntu-0"'14:23
mdeslauroh, yuck14:23
mdeslaurwhy not just an integer there?14:24
mdeslaurcompating strings is painful14:24
jdstrandeasyprof supports that fine, I chose ubuntu-0 for namespacing14:24
jdstrandmdeslaur: eg, if Debian wanted to ship easyprof templates, we would need to not collide14:26
mdeslaurok, if you want to do that, then do policy_vendor and policy_version14:26
jdstrandjeez, you keep making me do more work :P14:26
mdeslaurbecause now we have to start parsing strings all over if we want to do "older than version 3" checks14:26
mdeslaurjdstrand: well, do it right the first time :)14:26
* mdeslaur hugs jdstrand14:27
sergiusenscjwatson: hey, recalling the question about sdk apps and click, the fat package format is supposed to solve the arch specific packages right? I see there's an architecture entry I could add to the manifest today to workaround that until it's ready if that's the case14:37
cjwatsonsergiusens: fat packages are only needed if you want to ship multiple arches.  if you just need to ship one then you can just say "architecture": "armhf"14:41
cjwatsonthe "problem" of shipping packages for a single architecture isn't one that needs solving :)14:42
sergiusenscjwatson: great, so my temporary hack would be to use arch: armhf, but these apps would eventually need to be fattened up14:43
cjwatsonor linked or something14:44
cjwatsonwe don't need to solve that problem just yet14:44
sergiusensone less problem to deal with for now, I'll table it14:45
=== kentb is now known as kentb-afk
evmanish: so this is going to be tricky. Since14:55
evactivity log manager by itself is only vala code, not a c shim like the control center integration, it means extern'ing enough c code in alm.vala to get the diagnostics page up14:56
evmanish: I'll keep at it, but can we release what we have? As the previous release disabled the diagnostics page, GNOME Ubuntu would be no worse off.14:56
jbichaev: that release wasn't in Ubuntu because it had a regression like that14:59
evjbicha: what's the regression?14:59
evthe diagnostics page never appeared in a-l-m standalone.14:59
jbichawhat I meant was that alm 0.9.5 wasn't in Ubuntu15:00
evoh, right15:00
jbichaev: based on what you've said, I'm ok with releasing to saucy now with bug 1192778 unfixed but I'd really like it fixed before saucy is released15:02
ubottubug 1192778 in Activity Log Manager "Diagnostics tab doesn't show in standalone mode" [Medium,Confirmed] https://launchpad.net/bugs/119277815:02
evjbicha: *nods* I'm working on it, I just don't want the release to block on it. :)15:03
barryjbicha: the debdiff in lp: #1194526 comment #4 doesn't apply cleanly to the current saucy branch of libgsf.  can you generate a new patch?  if not, i will adapt it15:13
ubottuLaunchpad bug 1194526 in libgsf (Ubuntu) "Merge libgsf 1.14.27-1 (main) from Debian unstable (main)" [Wishlist,In progress] https://launchpad.net/bugs/119452615:14
infinitybarry: Meh, I'll just do that merge myself right now, it's trivial.15:20
barryinfinity: thanks15:21
* infinity resurrects a lost changelog entry while he's at it.15:28
smoserslangasek, what would be in local-filesystems that is not in filesystems ?15:33
smoserie, i have a system hung where local-filesystems ahs fired but not filesystems15:33
=== kentb-afk is now known as kentb
=== jtechidna is now known as JontheEchidna
xnoxwhat is responsible for clearing /forcefsck after it's been done?15:57
slangaseksmoser: I guess you mean the other way around?  things in filesystem but not in local-filesystems; that would be network filesystems, by and large... 'filesystem' should be the union of 'local-filesystems' and 'remote-filesystems' IIRC15:58
smoserslangasek, do you have a minute16:01
jodhsmb: we even have a picture: http://upstart.ubuntu.com/cookbook/#mountall-event-summary :)16:01
slangaseksmoser: ok16:01
smoserssh test@gwaclhostblkhljy4re3yp9swkdwp63kswkss9bqhn0zm3f3gunipzu5vwdr8qzw.cloudapp.net16:02
smoserthat system i think has not run rc yet. and i *thoht* had not emitted filesystme, but i don thtink thats rignht16:02
slangaseksmoser: cannot resolve hostname16:03
jodhsmb: oops - should have been smoser ;)16:03
smbjodh, Very ..err nice. Why would we want that again. :)16:03
smoserslangasek, would it seem odd or bad for16:03
smoserlockfile-create /var/lock/ntpdate-ifup16:03
smoserto have been hung16:03
smoserjodh, that 'last spoken tab completion' thing causes problems when both smb and i are talking16:03
smoseri often say things to myself in that situation16:03
smbsmoser, Hey I haven't said a thing today. :)16:03
jodhsmb: we can hear your thoughts!16:04
smoserslangasek, sorry. test@cf96b6aab6fe4ca8943422ee34fbca4b.cloudapp.net16:04
smosermd5 hostnames for the win!16:04
smbjodh, must be a lot of <beep>ing16:04
jodhsmb: hey, I like techno :)16:05
slangaseksmoser: 'status mountall' -> stop/waiting; what do you see here that points to filesystem not having fired?16:05
smoserslangasek, well, i think i have retracted that thought16:07
smoser$ ls -altr /var/run/landscape16:07
smoserls: cannot access /var/run/landscape: No such file or directory16:07
smoserS45landscape should have created that.16:07
smoserso it would seem it didn't run16:07
slangaseksmoser: if you run the script manually, what do you get?16:08
smoseri haven tried. cause i didn't want ot ruin state16:09
slangasekI see that the script will exit before creading the pidfile if check_config() failed16:09
smoserah. ok. then maybe i'm barking up the wrong tree then.16:09
smoserwhy would lockfile hang ?16:09
smoserthe 2 instances i see hung like this have a lockfile pid hung16:09
evmanish, jbicha I think I've got it. Just cleaning it up.16:10
slangaseksmoser: /etc/default/landscape-client doesn't exist; therefore RUN==0, CLOUD==0, and landscape-client won't start16:10
smosergood enough.16:10
smoserlockfile ?16:10
slangaseknot sure16:11
slangasekfutex(0x7f06a7d1f720, FUTEX_WAIT_PRIVATE, 2, NULL16:11
slangaseklooking pretty broken16:11
smoseroh. the other thing . the otriginal thing that lead me to thinking filesystems hadnt been emited.16:12
smosercloud-init-config.conf hasn't run (or if it did, it didn't successfully log anything to /var/log/cloud-init.log)16:13
smoseri dont know16:13
smoseri'm messed up.16:13
smoserwait it did.16:14
smoseri'm sorry.16:14
slangaseksmoser: so if I run lockfile-create directly under strace, it gives me this:16:15
slangasekopen("/dev/tty", O_RDWR|O_NOCTTY|O_NONBLOCK) = 516:15
slangasekwritev(5, [{"*** glibc detected *** ", 23}, {"lockfile-create", 15}, {": ", 2}, {"malloc(): memory corruption (fas"..., 34}, {": 0x", 4}, {"00000000023e8100", 16}, {" ***\n", 5}], 7*** glibc detected *** lockfile-create: malloc(): memory corruption (fast): 0x00000000023e8100 ***16:15
slangasek) = 9916:15
slangasekrather rude of it to write to /dev/tty, I think16:16
smosercmdline has 'console=tty1 console=ttyS0'16:18
smoserand that is probably coming through a console output job i suspect16:18
smosermaybe ? trying to come up with some reason for it to be doing that.16:18
slangasekno, the console settings don't explain why it would open /dev/tty which is the generic device16:20
=== sraue_ is now known as sraue
=== salem_ is now known as _salem
xnoxhallyn: jdstrand: shadow with user name space support is in the archive ;-)16:46
jdstrandsarnold: ^16:51
sarnoldjdstrand: woo :)16:52
sarnoldxnox: thanks :)16:52
sarnoldhallyn: thanks :)16:52
hallynxnox: woot, thanks!16:57
xnoxthat's quite a party =)17:00
=== _salem is now known as salem_
slangasekinfinity: upstream found the plymouth problem... no prototype for ply_get_timestamp() means that the double being returned by the function plays silly buggers with the floating point state17:47
slangasekapparently we ought to be building plymouth with -Werror ;)17:47
sarnoldslangasek: wow...17:48
infinityslangasek: Ah-ha.17:48
ogra_root@ubuntu-phablet:/# dpkg -S /etc/rc6.d/S31umountnfs.sh18:13
ogra_dpkg-query: no path found matching pattern /etc/rc6.d/S31umountnfs.sh18:13
ogra_does anyone know from the top of his head where that comes from ?18:13
infinity(base)adconrad@cthulhu:~$ dpkg -S /etc/init.d/umountnfs.sh18:14
infinityinitscripts: /etc/init.d/umountnfs.sh18:14
infinityogra_: Following the symlink would help. :)18:14
ogra_silly me18:14
ogra_i should have looked in init.d18:14
ogra_i wonder how even it would be to divert it ... it causes issues on phones18:14
ogra_(reboot hangs at times)18:15
infinityPerhaps sorting out WHY it causes problems would be good.18:15
ogra_well, we will hopefully not offer nfs cloud access via mobile data :)18:16
ogra_but yeah, if i could find that out i'd be happy as well18:16
infinitySure, but it does a bit more than the name would imply.18:16
infinitySo, it would be good to sort out what's breaking.18:16
infinityAs it may also affect other LXC setups or even normal desktops in some cases, etc.18:17
ogra_http://paste.ubuntu.com/5808502/ is the processlist of a hanging boot18:17
ogra_http://paste.ubuntu.com/5808513/ is the tail end of syslog18:17
infinitysh -x /etc/rc6.d/S31umountnfs.sh stop ?18:18
infinityOh, wait.18:18
infinityIt's the very end that's hanging.18:18
infinitySo, blame it on upstart.18:18
infinityIndeed, that's not the only initctl call that's hung.18:19
infinitySo, yeah, that's something we really should want to fix, not hackishly work around.18:19
infinityI'd recommend filing an upstart bug and poking jodh and stgraber.18:20
ogra_well, i would like to work around it for dogfooders ... indeed i did plan to research the cause and get it fixed18:20
infinityogra_: The problem I have with workarounds is that they seem to persist for two years before anyone notices and backs them out again.18:20
ogra_or even become permanent18:21
ogra_for the phone stuff i have all of them in the lxc-android-config package ... and i expect the workaround part to be empty by release :)18:21
infinityAnyhow, that's pretty clearly either an upstart bug, or a self-imposed mess due to container madness.18:21
stgraberso if it's hanging on the emit for unmounted-remote-filesystems, that's because a job that's start on unmounted-remote-filesystems won't return18:21
ogra_i doubt the container is involved18:21
infinitystgraber: There's also a hung "initctl emit deconfiguring-networking" in his ps output.18:22
ogra_stgraber, why would we have such a job ?18:22
infinitystgraber: http://paste.ubuntu.com/5808502/ if you missed it.18:22
stgraberright, same thing, unless you call emit with --no-wait, a broken job can make the emit hang18:22
stgraberit's by design18:22
infinityI suspect that doesn't want to change to --no-wait in either case, before someone hunts down what's halting the process.18:23
stgraberso it's typically an issue with whatever job is started on that event more than upstart's fault (or maybe it's a case where we want it non-blocking, though for those two, I doubt it)18:23
stgraberyeah, I think we want those shutdown related events to be blocking as they're there to cleanly bring things down and unmount network fs before the kernel cuts the power18:23
stgraberin that ps dump, the problem appears to be dbus18:24
stgraberdbus is supposed to stop on deconfiguring-networking and based on that ps, it didn't18:25
ogra_thats why NM respawns18:25
ogra_(in the syslog above)18:25
ogra_i dont see much in the upstart log for dbus apart from moaning about no whoopsie user being present18:26
ogra_but i think thats from startup anyway18:27
stgraberjust looked a bit closer, unmounted-remote-filesystems causes networking to stop which causes deconfiguring-networking to be emitted which should cause dbus to go away and the system to shutdown18:27
stgraberso it looks like if we can figure out what's keeping dbus from stopping, the whole thing will be solved, all the blocking events will return and the system will shutdown18:28
stgraberogra_: btw, shutdown works fine here on mako, though that's a slightly older image (I don't appear to have powerd)18:30
slangasekstgraber, ogra_: yes, those events are absolutely supposed to be blocking; the whole reason they exist is to ensure ordering of shutdown, making them non-blocking would reintroduce races :P18:32
ogra_stgraber, it mostly seems to happen on maguro and also only every nth boot18:34
ogra_though i think awe said he also saw it on mako18:34
aweogra_, ack18:35
ogra_slangasek, into the races we have you mean ?18:37
slangasekogra_: well, the standard Ubuntu shutdown scripts are race-free, so whatever races you're seeing are bugs in your stuff ;-)18:38
ogra_right, seems something keeps dbus alive18:39
slangasekkeeps it alive, or respawns it somehow?18:39
ogra_hard to tell18:40
ogra_the info in the upstart dbus.log is pretty sparse, it doesnt show it respawned18:40
=== hggdh_ is now known as hggdh
ogra_only moans about whoopsie absence18:41
ogra_Unknown username "whoopsie" in message bus configuration file18:42
ogra_to be exact18:42
ogra_(and indeed it is right, no whoopsie on the phones)18:42
aweogra_, you might need to run upstart with --verbose or --debug to catch the respawning...18:44
slangasekor just run 'initctl log-priority info' after boot18:45
ogra_awe, well, i rather would think i want a verbose dbus that logs somewhere18:45
slangasekand this won't be logged to /var/log/upstart/dbus.log in any case, as that just captures the log output from dbus itself - it does not give you any information from upstart about the job respawning, etc.18:45
slangasekogra_: which image first introduced this problem?18:45
ogra_i think tony reported it with his first test of flipped18:46
ogra_i havent seen it until today18:46
slangasekwhich devices is it seen on?18:48
ogra_maguro more often than mako18:48
ogra_i have never seen it on grouper18:48
ogra_oh, wait18:49
ogra_doesnt powerd use dbus ?18:49
sforsheeogra_: yes18:49
ogra_its in the processlist as well18:49
slangasekwhat does that have to do with the dbus shutdown being blocked?18:50
ogra_powerd has no "stop on" stanza18:50
slangasekso?  dbus shouldn't care18:50
slangasekthat just means dbus will stop, and powerd will be left crying in the dark18:50
slangasekit's the things that *do* have 'stop on stopping dbus' that are going to be the problem18:50
ogra_oh, right18:51
ogra_root@ubuntu-phablet:/# stop dbus18:59
ogra_stop: Job has already been stopped: dbus18:59
ogra_root@ubuntu-phablet:/# ps ax|grep dbus18:59
ogra_  515 ?        Ss     0:00 dbus-daemon --system --fork18:59
slangasekogra_: 'status dbus'?19:02
stgraberogra_: that means it's busy shutting down and not stopped yet19:02
stgraberogra_: if it was really stopped and all events processed, you'd get "stop: Unknown instance:"19:02
ogra_root@ubuntu-phablet:/# status dbus19:02
ogra_dbus stop/stopping, process 51519:02
ogra_ah, k19:03
stgraberright, so stuck in the stopping event as we suspected19:03
* ogra_ adds some verbosity to dbus19:04
ogra_i bet now i cant reproduce the issue anymore ... :P19:04
slangasekwhat jobs are 'stop on stopping dbus'?19:06
stgraberogra_: can you also paste a full "initctl list" when the system's stuck19:08
ogra_likely something in the session then, but i dont see anything running19:08
slangasekwow, trying to turn on -Werror for plymouth is spectacular fail19:08
slangasekwhy is upstream building with -Wall by default and not cleaning up the resulting warnings?19:09
slangasekogra_: ofono stop/killed, process 86419:09
slangasekit's all awe's fault ;-)19:10
infinityslangasek: It seems that some people don't make the jump from -Wall to "I should fix those".19:11
infinityslangasek: I've been helping a friend off and on with his CompSci homework, where one prof insists they always build with -Wall.  The comment he got back after a few assignments was "you're the only student who actually makes sure everything builds cleanly and addresses all the warnings".19:12
infinityslangasek: Perhaps because I made him do so.19:12
awemy fault??  ;D19:13
slangasekawe: ofono is refusing to die on shutdown, which blocks dbus, which blocks /etc/rc6.d19:13
stgraberslangasek: well, actually it looks dead, I'm wondering if it's not a expect fork vs expect daemon issue19:13
ogra_i guess we could just leave it to sendsigs19:14
ogra_and pull the stop on stanza19:14
slangasekstgraber: presumably not, if ofono was working at all during the system's run19:14
awestgraber, slangasek... there's definitely an issue with ofono & upstart that I haven't been able to debug yet19:14
slangasekogra_: no, that's a wrong solution19:14
* awe is currently doing an evil ofono merge for PIN/PUK support19:14
ogra_slangasek, well, we rip the socket out underneath it19:15
slangaseksendsigs *deliberately* skips upstart jobs that don't have a 'stop' target19:15
slangasekyou want the opposite, you want to ensure the service shuts down19:15
ogra_if it needs a stop on, that should probably the container19:15
aweslangasek, I added code to ofono to exit on RILD socket errors, and was relying on upstart to respawn19:15
aweit does this once, and then seems to get confused19:15
slangasekawe: hmm, ok19:15
awe...thinking that ofono is still running19:15
slangasekawe: my devices are not at easy reach at the moment; could you pastebin /etc/init/ofono.conf?19:16
awe( ie. initctl status ofono returns a PID, and says it's running, when it's not )19:16
aweyea, one sec...19:16
slangasekinfinity: oh, so half of these warnings are actually from the ubuntu-text plugin, teehee19:17
aweslangasek, http://pastebin.ubuntu.com/5808742/19:18
stgraberawe: also paste the .override19:18
* awe knew someone was going to ask for that19:18
stgraberas the whole job is overriden19:18
aweone more sec...19:18
ogra_the override is my fault :)19:18
ogra_but that only adds a loop to wait for the socket19:19
ogra_(and a start on for the socket dir(19:19
stgraberogra_: you know that a .override doesn't need to duplicate anything that exists in the original conf right? :)19:20
ogra_stgraber, but its much more readable to have it all in the same file19:20
aweslangasek, stgraber... the expect is correct, as if ofono is running, the correct PID/status is returned... but after the first respawn, it seems upstart gets confused19:20
aweI see this on maguro, flipped19:20
stgraberogra_: until someone dumps a post-stop in the archive ofono.conf, then it's going to be very confusing :)19:20
ogra_stgraber, well, i have hope that we can somehow merge the jobs before release19:21
aweI checked and confirmed that ofono uses the daemon() call, so the 'expect fork' should be correct19:21
stgraberogra_, awe, slangasek: there's the problem, look at PID: http://paste.ubuntu.com/5808753/19:21
ogra_80% of lxc-android-config is throw away stuff19:21
slangasekright, that looks like it should actually be 'expect daemon'19:22
stgraberslangasek: well, strangely enough the initial startup worked with expect fork, but the second run appears to need expect daemon19:23
aweyea..that's what I originally thought too19:23
slangasekthat doesn't make much sense19:23
stgraberotherwise the PID for the instance running after boot would be wrong too and the first stop would hang19:23
awethat said, when upstart respawns, does that cause a double fork that's not accounted for?19:23
slangasekwell, in stgraber's example, it's not using an upstart respawn19:24
slangasekthis is a bug that was just reported on upstart-devel19:24
slangasekSubject: upstart shell magic for exec line19:24
slangasekI don't understand how a bug like that went unnoticed for as long as it did19:25
slangasekunless something regressed somewhere along the line19:25
slangasekawe: there's a one-line change proposed there (dropping line 268 of job_process.c); I haven't evaluated this, but I guess you could try it out and see what else might explode19:26
slangasekstgraber: can you follow up on bug #1181789, please?19:26
ubottubug 1181789 in upstart (Ubuntu) "second call of 'initctl start' leads to fork instead of exec ('mount: / is busy' during shutdown)" [Undecided,Confirmed] https://launchpad.net/bugs/118178919:26
stgraberslangasek: I think we did some changes in that part of upstart when fixing some build issues in 1.8 (or 1.7), so it's not impossible that we introduced the bug at that time19:27
infinityslangasek: is this expect daemon/fork thing new, or did I just not know about it when I tore a deamon() call out of something that was driving us insane?19:29
infinityslangasek: (And does it allow for a double-fork of 'exec shell-script-that-execs-daemon'?)19:30
ogra_it has been in the cookbook for a while19:30
stgraberslangasek: I'm fairly sure just dropping the line will cause test failures, finishing some loop-mount stuff and I'll take a look after that19:30
slangasekinfinity: you apparently just didn't know about it :P19:30
slangasekinfinity: exec shell-script-that-execs-daemon> there's a bug about that, I have a patch for it but I hadn't landed it because it was only useful to me if we fixed exit tracking at the same time; let me dig it up19:31
awestgraber, slangasek, I have to head out in ~20min or so, but can test later.  Totally explains the weirdness I was seeing with my socket retry scenario19:31
awealso fyi, I'm out next week19:31
infinityslangasek: Oh, kay, if that case still doesn't work, I don't feel bad about my workaround, then.19:32
stgraberslangasek: IIRC the bug that cause that change (and introduced this bug in the process) was when your working dir contains a shell character (like the ~ in our daily builds). That was the bug that drove us insane for a couple of days a while back (upstart failing for dailies but not for distro upload)19:32
slangasekinfinity: lp:~vorlon/upstart/lp.85501019:32
slangasekstgraber: right.  Can you please take care of fixing this? :)19:32
stgraberawe: well, the job is correct, once we fix upstart it'll just work (I expect the patch to be pretty easy to backport to saucy and raring).19:33
* awe spent lots of time reading, and re-reading the upstart cookbook this week19:34
infinityslangasek: I suppose shell-that-calls-daemon would be a triple-fork, which is the problem (and why it cleared up when I removed the daemon() call).  Couldn't one just allow 'expect fork' to take an integer argument, so I can say "dude, this forks 17 times, that last one's what you want"?19:34
slangasekinfinity: shell-that-calls-daemon would be a triple-fork, and that won't work; shell-that-execs-daemon *should* work fine and we just need to support that; letting things fork more than twice is a total non-starter until we properly add exit tracking19:35
slangasekwhich is bug #53077919:36
ubottubug 530779 in upstart (Ubuntu Precise) "init: does not wait for parent to exit when following forks" [Medium,Triaged] https://launchpad.net/bugs/53077919:36
aweand everyone on my team thought I was seeing pink elephants when I kept claiming shutdown was broken...19:36
slangasekthese are not mutually exclusive19:36
sergiusensawe: I didn't, I just couldn't reproduce it anymore until today19:36
stgraberawe: well, it's only broken if ofono crashes, so fix ofono and your shutdown will work reliably :)19:37
slangasekstgraber: ofono is exiting because of rild, I don't think that's ofono's fault ;)19:37
seb128stgraber, when do you guys plan to update upstart?19:37
ogra_but we love pink elephants19:37
* seb128 is getting tired of logout taking ages because init segfaults and apport block the logout while dealing with the issue19:37
stgraberseb128: I plan to land the fix for the respawn issue as soon as I have it but that's probably unrelated to what you're talking about19:38
ogra_seb128, come over to the phone team ... no apport here19:38
awestgraber, ofono wasn't crashing, it was exiting on purpose when the RILD socket operations returned errors while running in flipped19:39
awethis is 'cause we had no way to reliably know that RILD had started in the flipped container19:39
slangaseksee, upstart should supervise rild too :P19:39
seb128stgraber, I want http://bazaar.launchpad.net/~jamesodhunt/upstart/bug-1190526/revision/1481 in saucy ;-)19:40
ubottuLaunchpad bug 1481 in Scribus "outdated description for scribus" [Low,Fix released]19:40
infinityslangasek: Well, I'm "happy" enough with the 1-line hack we're carrying in the kernel source for now, this conversation just reminded me of it.19:40
awewell, now that chromeos an android are under the same mgmt, that's not too far-fetched...  ;)19:40
slangasekinfinity: ok.  but now that I know that bug has affected more than just cups, for which it's not a complete solution, I'll probably bump it up my list19:41
stgraberseb128: I should be able to cherry-pick that one at the same time assuming I debug the other issue before we upload 1.9 to Ubuntu19:41
seb128stgraber, thank you!19:41
ogra_slangasek, well, i was asking jodh today about an upstart-container-bridge for us :)19:43
slangasekogra_: no, that's not what I'm talking about19:43
slangasekI'm talking about rild being an upstart job that just happens to run in an android chorot19:44
ogra_thats what i wanted that bridge to be19:44
slangasekit shouldn't be done by any bridge at all19:44
slangasekyou just need an upstart job with a 'chroot' stanza19:44
bregmahey guys I'm trying to run valgrind on armhf under quemu (ie. in a pbuilder) but I always get an Out Of Memory error....  anyone else seen this?19:44
stgraberslangasek: I have a kernel patch here that'd let us do that but only for mako/manta19:44
slangasek(well, except you really need a container, but meh :P)19:44
ogra_heh, if chrooting would work that way into lxc containers19:44
* awe heads out19:45
ogra_but i see what you mean19:45
stgraberslangasek: exec lxc-attach -n android --clear-env -- /system/xbin/env PATH=/system/bin:/system/xbin INSERT-YOUR-COMMAND-HERE19:45
rsalvetithat would require changes in the android side as well19:46
rsalvetiI'd just prefer a way to know when it's up from the android side19:46
rsalvetiwhich you can get via properties, we just need to hook that up somehow19:47
slangaseksigh.  did firefox just change to no longer allow me to hide the tabs when I only have one tab in the window?19:56
lifelessslangasek: firefix is intent on becoming a copy of chrome19:56
lifelessslangasek: but badly; e.g. when you copy an http url it now copies it without the http://19:57
lifelessslangasek: so it looks like chrome, but behaves worse.19:57
slangasekchrisccoulson: ^^ do you know if this behavior is still controllable in ff 23? :/19:57
slangasekyeah, might as well switch to chrome now19:58
ScottKYou might want to consider how rapidly and consistently we get security updates out first.19:59
slangaseksurely it's simpler to assume that any browser is compromised20:00
ScottKThat would be one way to approach it.20:01
mlankhorstthat's what I assume anyway20:01
debfxlifeless: at least firefox has an about:config option to get the http:// in the location bar back20:02
chrisccoulsonlifeless, i've no idea why that doesn't work for you, but it works fine here...20:03
lifelessdebfx: yes, which is a saving grace20:04
lifelesschrisccoulson: let me double check then.20:04
lifelesschrisccoulson: and now my running ff makes a liar of me. NFI20:05
ScottKlamont: Can haz postfix 2.10.1?20:38
=== Amaranthus is now known as Amaranth
luistanyone familiar with multistrap?21:00
lamontScottK: added to my weekend fun21:07
ScottKlamont: Thanks.21:07
=== salem_ is now known as _salem
* xnox let's see if this works as well21:32
xnoxlamont: Can haz util-linux 2.23.1 ?21:32
=== wedgwood is now known as wedgwood_away

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!