/srv/irclogs.ubuntu.com/2012/04/21/#ubuntu-devel.txt

sgCoderhi01:24
hyperairhuh there's a really huge multiarch breakage today in the archive01:48
hyperairall my :i386 packages got removed01:49
hyperair...even nautilus got removed?!01:52
hyperairoh it looks like it's fixed01:53
cyphermoxSpamapS: poke04:42
cyphermoxre bug 211631: I'm not certain your comment is true. I think the binaries that run the VPN plugins would get killed by sendsigs.04:43
ubottuLaunchpad bug 211631 in wpasupplicant (Ubuntu Natty) "Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)" [Undecided,New] https://launchpad.net/bugs/21163104:43
cyphermox(and I should fix that ;)04:44
=== jalcine is now known as JackyAlcine
=== JackyAlcine is now known as jalcine
SpamapScyphermox: Ah so just like dnsmasq, they need to add themselves to the whitelist05:49
cyphermoxSpamapS: possibly. It depends at what point the stuff gets unmounted. if it's a SysVinit script, it would get unmounted before sendsigs, then the vpn plugin binary XYZ would get killed, and all is well05:50
cyphermoxif it's an upstart job, then all is not well; but that's easy enough to fix05:50
cyphermoxI just don't remember and didn't bother to look at the setup again to make sure, yet ;)05:50
trijntjeping pitti: I'm trying to build a localised image using a PPA, but ubuntu-defaults-image returns "Invalid fingerprint returned by launchpad"05:51
cyphermoxSpamapS: I think regardless it makes sense to avoid the plugins getting killed before NM turns interfaces and VPNs off, which would get stop these processes anyway05:51
=== jalcine is now known as JackyAlcine
=== Whoopie_ is now known as Whoopie
slangasekcyphermox: sendsigs is run from a sysvinit script, one which deliberately runs before unmounting network filesystems06:27
slangasekthat's the same root issue as it's been all along, just now with a different type of network helper being killed06:28
cyphermoxslangasek: right, because the processes could have been started from a remote FS or depend on it06:28
slangasekyes06:28
cyphermoxaye aye, will just need to make the processes spawned by NM be omitted for that too06:28
slangasekyep - *any* process NM spawns, that it expects to keep running and reap on its own at shutdown, should be in the omit list06:29
cyphermoxthat's a fix in each of the vpn plugin packages, there are only for.06:29
cyphermox*four06:29
slangasekok06:29
trijntjepitti: Nevermind, I was using the wrong name for the ppa06:30
rectecHow are you guys? Before I ask for help, I just want to ask how development is going along. We have only 5 days until release and currently my installation looks a bit shabby...08:21
rectecanyone?08:23
rectecok, well... I have a problem in which the text inside dialog boxes is too light to read. This affects the Ambiance theme and one other theme. (The Hope theme, only 3rd-party theme I've tested.) The Radiance theme doesn't seem to have this issue.08:28
rectecI don't know if this is a known issue and has/has not been solved, or if I'm the only one with this issue.08:29
vibhavIve updated a package (onboard) to 0.97-0-0ubuntu3 locally, How Do I get it into oneiric?10:35
jtaylordoko_: numpy -8 merge: https://code.launchpad.net/~jtaylor/ubuntu/precise/python-numpy/merge-8/+merge/10297013:56
jtaylorits not very important so if its to late feel free to reject it13:57
jeinorslangasek: I got the Cubox up and running with kernel 3.3.1 and Ubuntu Core 12.04 beta 2 :D14:52
jeinorslangasek: got some (a lot) of help from ogra_ in #ubuntu-arm, and with his directions I finally got a login console!14:53
jeinorslangasek: thanks for all your help too, really helpful!14:53
SpamapSvibhav: You need to file a bug, make sure that bug is fixed in the latest dev release (precise still.. soon "q"), and then choose 'Nominate for series' in launchpad and choose Oneiric.  https://wiki.ubuntu.com/StableReleaseUpdates#Procedure14:59
=== jsjgruber is now known as Guest18144
hdon-hi all :) in many months using the latest ubuntu LTS i have noticed that all my CPU cores are rarely used. even if i am building large software packages with -j5 only 1/4 CPU cores are being fully utilized. i'm certainly not I/O bound at the hard disk. if anyone has any advice for me i would be very thankful19:08
penguin42how many cores do you have?19:18
infinitypenguin42: I'm assuming 4.19:33
infinityhdon-: How are you determining if your cores are being "used"?19:33
infinityhdon-: If you make -j5, you should get 5 forks of make (assuming the Makefile can parallelize well, the kernel's always a good test).19:33
infinityhdon-: That doesn't mean each CPU will get pegged at 100%, but it does mean each will get "used".19:34
hdon-infinity, the system monitor application19:34
hdon-infinity, it seems to my eye that only one CPU is being used fully at a time. the others all hover around 20%, and of course they switch off. one core isn't always the same one on duty19:34
infinityIf you make a kernel with -j4 (or higher), you should see a system load in top >= 4.19:35
infinitySnapshots of system use are rarely accurate.19:35
infinity(For instance, in the above kernel scenario, with -j4, you'll often see 4 instances of "cc1", but they won't necessarily all report using 100% CPU at all times)19:35
=== Guest94473 is now known as JackyAlcine
IntuitiveNippleWhat's the procedure for requesting a freeze exception for a bug-fix at this stage? I've subscribed ubuntut-release as per one wiki recommendation (bug #927828 in sudo) ?20:00
ubottuLaunchpad bug 927828 in sudo (Ubuntu) "sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed." [Undecided,In progress] https://launchpad.net/bugs/92782820:00
cjwatsonIntuitiveNipple: that sounds like a good candidate for an SRU, I think, rather than trying to squeeze a fix in a few days before release when we don't have much time for validation or for recovering if something goes wrong20:46
cjwatsonI assume it only affects people with pam-mount installed (?), so perhaps it's release-note and fix for .120:46
maxbcjwatson: Oh, about the subversion FTBFS - I've been slowly slowly plodding through building a set of backported patches, but every time I think I'm done, another test randomly fails.20:47
IntuitiveNippleIt affects all pam modules... its just that pam_mount complains with an assert20:47
IntuitiveNippleThe key issue is, that the bug revealed, pam_open_session() isn't called when sudo has a valid timestamp20:47
IntuitiveNippleSo pam modules that are hooking the begin_session won't get triggered20:48
IntuitiveNippleI suppose a work-around would be to temporarily set "timestamp 0"20:48
cjwatsonmaxb: I know the feeling20:50
cjwatsondoesn't help that it's a slow build20:50
maxbIt builds quite quickly on my desktop; the testsuite is a bit slow, though20:51
cjwatsonIntuitiveNipple: well, what I mean is, this bug was reported in February, and *I* haven't been seeing the second use of every sudo ticket fail20:51
cjwatsonIf it were doing that for everyone, this would be High or Critical and likely a showstopper - but it isn't20:51
IntuitiveNippleMaybe it affects Oneiric->Precise upgrades ?20:51
cjwatsonThen it would affect me20:51
cjwatsonThis is the first I've heard of this bug, in fact20:52
IntuitiveNippleyeah, I was trying to figure out what it is that is causing it. For those that it affects, it occurs whenever there's a valid timestamp20:52
cjwatsonSo it must have some kind of narrowed criteria20:52
IntuitiveNippleMaybe it's something to do with PAM configuration20:52
cjwatsonHence my comment about libpam-mount, if that's the only thing that fails hard20:53
cjwatsonAnd since that's an add-on not installed by default, IIRC ...20:53
IntuitiveNippleReally? I didn't know anything about it until this bug then I found it installed20:53
IntuitiveNippleHmmm!20:53
IntuitiveNippleMaybe it's to do with if encrypted home is in use?20:54
cjwatsonI don't see anything like that in its reverse-depends20:54
IntuitiveNippleInteresting - I assumed it was part of the standard installation since I didn't recognise it20:54
cjwatsonJust sadms, which isn't by default either20:55
cjwatsonIt's been in server-ship since hardy, but that's all I see immediately - can look a bit harder later20:57
IntuitiveNippleI've just grepped all of /var/log/apt/* which goes back to Dec 5th without seeing libpam_mount ... so maybe it was installed originally by oneiric on my system, since Oneiric was a clean install20:57
IntuitiveNippleOK .. so I should write up an SRU for it?20:58
maxbsubversion-wise, I think we just have to release precise with it FTBFS; there'll be a SRU soonish for 1.6.18, so it's not completely horrid to do so20:58
cjwatsonmaxb: I really want to reach zero out-of-date binaries - perhaps I could help on Monday given your state so far?21:01
cjwatsonalthough it's on some images I guess, argh21:01
slangasekIntuitiveNipple, cjwatson: I certainly think not opening pam sessions for authentications with an existing ticket is SRU-worthy but not a show-stopper; in fact there are several bugs in sudo session handling that I think need sorted out in SRU, and this is among them.  But yes, pam-mount isn't stock.21:05
IntuitiveNippleIt must be have been sadms that brought it in - I _vaguely_ recall looking at that package for some reason last year21:06
IntuitiveNippleslangasek: Well it looks like the sudo author accepts there is an issue now, despite initially saying my analysis was wrong, so maybe now's the time to push bugs upstream21:07
slangasekIntuitiveNipple: where is the upstream discussion happening?  bug tracker / list / private email?21:08
IntuitiveNippleWell I found the sudo bugzilla and there were only a handful of bugs in it, so it looks like folks rarely use it. It's linked to the launchpad sudo project though, and I've linked it on the bug itself21:09
slangasekwhich bug is that?21:10
IntuitiveNipplebug #92782821:10
ubottuLaunchpad bug 927828 in sudo (Ubuntu) "sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed." [Undecided,New] https://launchpad.net/bugs/92782821:10
slangasekok21:10
IntuitiveNippleRich Miller _is_ the upstream author, was very quick and precise in responding21:11
slangasekpitti: so we've worked out with some difficulty that a client-side apport dupe check is causing update-manager crash reports to be treated as duplicates of a closed bug (bug #628104) and we want to have them *not* treated that way so we can get full clean backtraces from bug submitters.  How do we do that?21:22
ubottuLaunchpad bug 628104 in Aptdaemon "update-manager crashes: AptDaemonError: org.debian.apt: Could not cancel transaction" [Undecided,Confirmed] https://launchpad.net/bugs/62810421:22
slangasekwell, a bug that /was/ closed21:23
slangasekpitti: I don't have confidence here that the duplicate signature is accurate and would like to see a recent backtrace21:23
slangasekpitti: or at least get a better understanding of the duplication algorithm :)21:24
=== Nisstyre is now known as nisstyre
=== nisstyre is now known as Nisstyre
maxbcjwatson: Sorry, was away; yeah, I figured it was already too late what with it being seeded22:29
=== Ursinha` is now known as Ursinha
=== Ursinha is now known as Guest65814

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