[01:05] <thafreak> Unit193: yep...still have some g3 ppc's
[01:06] <thafreak> gutted the all in one imac or emac or whatever it was...blueberry thing
[01:06] <thafreak> but still have a beige desktop and a blue and white tower
[01:12] <Unit193> Asking because Lubuntu is the only PPC *ubuntu left and needs testers.
[01:20]  * canthus13 read tasers.
[01:25] <Unit193> That could be fun though.
[01:30] <canthus13> taser-armed fringe ubuntu distros?
[01:38] <Unit193> Na, fringe is gnome-shell or openbox-desktop Ubuntu'ers. ;)
[01:40]  * canthus13 is barely a ubuntu-er anymore. :/
[01:41] <Unit193> IIRC, your wife is, you aren't?
[11:52] <canthus13> Unit193: I use Mint, my wife uses Mint.  One of my kids' computers still has 10.04 on it.
[11:56] <Unit193> Ah, thought you had another, guess not.
[11:57]  * canthus13 also has 3 servers running Debian.
[15:18] <canthus13> How would I restrict users so that they can only view their own home folders? I'd like to give my kids access to a shell on the server, but I don't want them being able to cd into another user's home folder and view whatever's in that top level.
[19:42] <thafreak> lxc containers or simple chroot jail i'd say
[19:43] <thafreak> i'm pretty sure ssh has chroot support.
[19:53] <dzho> then again, just using regular permissions ought to be enough at a first level
[19:53] <dzho> if the kids directories are 700 or 755
[19:54] <dzho> er, 750
[19:54] <dzho> in the case of 750 assuming group ownership to a group specific to the kid
[19:54] <dzho> though, of course, your account would be a member of the group, too :-)
[20:08]  * canthus13 was just wondering if changing /home to 700 would be enough.
[20:10] <canthus13> hmm.. it worked, but I get bash: /home/canthus13/.bashrc: Permission denied
[20:11] <canthus13> on login.


[16:16] <Kilos> .
[16:49] <hibana> Kilos: it works :-)
[16:50] <hibana> Kilos: what do you want in the topic line?
[16:50] <Kilos> lol yes thank you
[16:50] <Kilos> can you remember what was in there
[16:51] <hibana> topic #Ubuntu-Africa Ubuntu Africa
[16:53] <hibana> Kilos: no idea what was there
[16:53] <Kilos> hmm...
[16:53] <Kilos> something like thi channel is for ubuntu/linux users all over africa.
[16:55] <Kilos> and maybe to get together to share experience and make friends from all the african countries
[16:56] <Kilos> i dunno, you the brain
[16:57] <hibana> Kilos: ask your buddies and let me know then I'll change it
[16:57] <Kilos> that WaVeR  guy i think is on one of the islands. maybe  maldives or one of those groups
[16:57] <hibana> anyone still on IRC is probably still also in another channel
[16:58] <Kilos> too much work waiting for mails. some of them hardly speak english
[16:58] <Kilos> none of them used irc before we started this
[16:58] <Kilos> maybe elacheche
[16:59] <Kilos> he was in tunisia back then but now in paris
[17:01] <Kilos> and of course telegram, whatsapp and the rest are more popular
[17:06] <me12345> hi
[17:11] <hibana> fixed the line at https://wiki.ubuntu.com/AfricanTeams to join us on #ubuntu-africa at irc.libera.chat
[17:17] <Kilos> well done
[17:17] <Kilos> you still handy to have around i see
[17:20] <Kilos> oh my. who did all of that


[17:36] <zaki> hi pavlushka
[17:37] <zaki> how are you ?
[17:37] <pavlushka> zaki: Hey, I am good, you?
[17:37] <zaki> fine.
[17:37] <pavlushka> So, anything up?
[17:38] <zaki> how is your weather station working ?
[17:38] <zaki> nah,
[17:38] <pavlushka> zaki: any new servers? and what about the CCNA?
[17:38] <zaki> hehe.
[17:38] <pavlushka> zaki: my weather station is working good
[17:39] <zaki> pavlushka, I was working on observium.
[17:39] <zaki> http://www.observium.org/
[17:40] <pavlushka> zaki: wow, cool
[17:45] <pavlushka> zaki: So it is clear that you opted to networking as your expertise, good thing :)
[17:47] <zaki> he he
[17:47] <zaki> pavlushka, yes
[17:48] <pavlushka> zaki: way to go
[17:48] <zaki> pavlushka, we use "The Dude" for monitoring nodes
[17:48] <zaki> it's a free tool, but great
[17:49] <zaki> and PRTG for graphing but this one not free.
[17:49] <zaki> tried cacti, but আল লাগে নাই
[17:49] <zaki> ভাল*
[17:49] <pavlushka> zaki: MRTG?
[17:51] <zaki> also tried.
[17:51] <pavlushka> zaki: and?
[17:53] <zaki> এটা ও ভাল লাগে নাই।
[17:54] <pavlushka>  ha ha ha
[17:57] <zaki> btw MRTG is a bit old :P
[17:58] <pavlushka> zaki: hmm, probably :)
[18:05] <zaki> pavlushka, whatever I am testing one after one. :D
[18:06] <pavlushka> zaki: not bad, ha ha
[18:06] <pavlushka> zaki: I do that too :)


[00:02] <ali1234> this whole thing is one big circular reference
[00:26] <ali1234> right, finally it's fixed
[00:26] <ali1234> http://bug-attachment.xfce.org/attachment.cgi?id=5747
[09:58] <elfy> ochosi: not sure if this is expected or not, can you see where to enable an item here - http://www.zimagez.com/zimage/screenshot-121114-095725.php
[09:59] <elfy> you have to guess - http://www.zimagez.com/zimage/screenshot-121114-095752.php
[10:01] <dkessel> lol elfy :)
[10:01] <elfy> see the same in synaptic - so it's not just transmission
[10:01] <dkessel> sure, why not there? it is obvious :)
[10:01] <elfy> hey dkessel - good morning to you
[10:02] <dkessel> hey elfy
[10:02] <dkessel> good morning to you too :)
[10:02] <dkessel> i mean, it has been there the previous versions... ;) just kidding
[10:07] <elfy> possibly - the last cycle I took a lot of notice was 14.04
[11:01] <elfy> slickymasterWork: I looked at the task manager testcase - bug 1391636
[11:01] <elfy> just needs checking over and I'll get on and deal with it
[11:02] <elfy> or dkessel even - anyone in -qa :)
[11:03] <slickymasterWork> I can make a MP tonight if you want me to, elfy
[11:03] <elfy> I can do it - not working this week
[11:04] <slickymasterWork> s/it/if
[11:05] <slickymasterWork> ok, I can review it if you want
[11:05] <elfy> ta :)
[11:05] <slickymasterWork> the bug description pretty much sums it all elfy
[11:12] <elfy> :)
[12:45] <dkessel> bluesabre: looks like I can just use the "BuilderName" property of the widgets to identify them in autopilot. I guess there is no need to give everything an ID then - as long as the "BuilderName" does not change
[12:51]  * dkessel feels so stupid
[12:51] <dkessel> I should have seen that converting the manual catfish test requires the adminstrator password... I don't think this will work
[12:54] <elfy> dkessel: mmm
[12:54] <dkessel> i can build it... but it won't work without the correct password
[12:54] <elfy> dkessel: you're directly converting manual to auto?
[12:55] <dkessel> elfy: yes
[12:55] <elfy> I'll just pull up the manual one
[12:57] <elfy> dkessel: so why not get it to search for files that are just always going to be there regardless instead of creating some then updating db
[12:59] <dkessel> elfy: sure, why not.
[12:59] <elfy> the only issue then would be being unable to check case sensitivity
[12:59] <dkessel> but it takes away some of the test's value
[12:59] <dkessel> i'll ask in the autopilot channel if they have an idea
[13:00] <elfy> ok
[13:57] <jjfrv8> elfy, I posted a comment on bug 1391636
[13:57] <jjfrv8> elfy, did you see bug 1391357 yet?
[14:02] <jjfrv8> I did not include the suggested revisions in that one ^^ like you did in yours. I was going to ask if you wanted me to draft an MP.
[14:10] <elfy> jjfrv8: go ahead :)
[14:10] <elfy> and no I'd not seen that bug
[14:12] <elfy> jjfrv8: thanks for comment in the task manager one
[14:18] <jjfrv8> ok, will do.
[14:24] <slickymasterWork> hey jjfrv8 did you get anywhere with http://irclogs.ubuntu.com/2014/10/29/%23xubuntu-devel.html#t12:11
[14:27] <jjfrv8> slickymasterWork, I figured that was a dead issue. The vote seemed to be that things were okay as they were.
[14:31] <ochosi> elfy: that is a "bug" in our gtk themes (yeah, gtk devs decided to change some theming properties' names again in 3.14) which is already taken care of in git
[14:32] <ochosi> i suppose you're not using the shimmer-daily PPA for themes? if not, no worries, i guess we can arrange an update of the themes packages for V soonish
[14:32] <ochosi> (but just so you know it should already be taken care of. and thanks for noticing/notifying)
[14:33] <elfy> ochosi: thanks - and yes I have -staging and shimmer ppa's
[14:33] <ochosi> hmm, odd. let me check when that last built...
[14:33] <elfy> no need for a pointless bug report then - that's good :)
[14:34] <elfy> I got shimmer updates a day or so ago iirc
[14:34] <ochosi> humm, supposedly it should be fixed in the last build, so that's odd
[14:34] <ochosi> aaaaah, ofc
[14:34] <ochosi> you're still having gtk3.12
[14:34] <ochosi> and the themes are already prepped for 3.14
[14:34] <ochosi> so you get the regression you'd get without the patch in 3.14 in 3.12 :>
[14:35] <ochosi> so i guess i was "too fast" there
[14:35] <ochosi> as soon as 3.14 lands, things should be back to normal
[14:35] <elfy> ok - cool, as long as there is a reason - I can just wait for 3.14 and watch in wonder as all is fixed as if by magic then :)
[14:35] <ochosi> indeed
[14:36] <elfy> if it's March and we've not for gtk3.14 I will let you know you need to reverse course :D
[14:37] <ochosi> yup, good to keep that on the radar :]
[14:37] <ochosi> but i suppose this time 3.14 is bound to land
[14:37] <ochosi> i saw some folks in -desktop messing with patches for it already
[14:37] <elfy> he he he
[14:42] <slickymasterWork> jjfrv8, well it wasn't a proper vote. If on one hand ochosi doesn't really have any strong on dropping the icon from whisker, on the other knome thinks that it's better to keep it and solve the ambiguity docs-internally
[14:42] <slickymasterWork> and no one else in -team besides them had reaaly pronounce on the subject
[14:42] <slickymasterWork> s/reaaly/really
[14:44] <ochosi> slickymasterWork: you can also ask around at tomorrow's meeting
[14:44] <ochosi> can't promise yet i'll make it, i'm travelling abroad again
[14:45] <ochosi> but as i have no strong opinion, it probably doesn't matter too much
[14:45] <slickymasterWork> I think all add it to the meeting agenda
[14:47] <Unit193> I can that I'll miss.
[14:48] <slickymasterWork> buuu
[15:01] <jjfrv8> slickymasterWork, I won't be able to make the meeting. My proxy would be to abstain. If you decide to proceed with something, I don't think I would be a good candidate to work on it.
[15:01] <jjfrv8> I'd probably end up adding confusion to something that other folks don't really see as an issue in the first place.
[15:02] <Unit193> ochosi: If you want to track more gst0.10 bugs, https://github.com/squentin/gmusicbrowser/issues/76
[15:02] <jjfrv8> bbl
[15:02] <elfy> personally - removing something from the menu because docs look wrong is not the right way to do things
[15:03] <knome> necessarily
[15:03] <elfy> wut?
[15:03] <elfy> why is Unit193 posting one word comments as knome :p
[15:03] <knome> it's not necessarily wrong
[15:04] <knome> i mean...
[15:04] <elfy> I know what you mean :)
[15:04] <knome> doing it for that sake is wrong, but the action itself is not necessarily wrong :P
[15:04] <elfy> yep
[15:04] <knome> i don't have a strong opinion on this
[15:05] <knome> the only argument i have for keeping what we have is that some users have learned this way
[15:05] <knome> we don't want to mess that up now
[15:05] <elfy> yep - that would be my position
[15:05] <knome> whether that'd balance out with new users not having at all ambiguity is a different thing
[15:06] <elfy> well
[15:07] <elfy> most people would look at what they see -> docs if they can't find something
[15:07] <elfy> in my experience
[15:07] <knome> mhm
[15:07] <Unit193> Or when we tell them to.
[15:16] <slickymasterWork> ok, got it jjfrv8. Thanks for the feedback
[19:19] <Noskcaj> elfy, ochosi: gtk 3.14's blocker list is at http://pad.ubuntu.com/gtk-update-v if you're wondering what we're waiting for
[20:20] <brainwash> bluesabre: there is a patch attached to bug 1211933
[20:21] <brainwash> for xubuntu-live-settings
[20:22] <brainwash> should we apply this patch? or close the report as won't fix?
[23:54] <skellat> brainwash: I'll say WON'TFIX as this appears unrelated to the original bug -- https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1211933/comments/8


[00:01] <knome> Unit193, again
[00:01] <knome> look at the right/left aligned images when going very narrow
[00:02] <Unit193> Oi, big jump indeed.
[00:05] <knome> wondering if i should do some more optimization, but i guess i'll leave that for another day/night
[00:26] <knome> Unit193, http://bazaar.launchpad.net/~xubuntu-website/xubuntu-website/theme/revision/45
[00:34] <knome> time to go fill some crosswords, then to bed
[00:34] <knome> nighty!
[00:57] <ali1234> if you want columns, and you want it to not suck at low resolutions, then use bootstrap
[01:53] <pleia2> ochosi: your tahr is in the wild (hehe) http://www.noobslab.com/2014/04/ubuntu-1404-trusty-tahr-lts-has-been.html
[02:06] <jphilipz> hi all, i was trying the xubuntu 14.04 and noticed when i disable bluetooth from the panel, it didnt change to a dimmed icon
[04:09] <waymon> hi guys sorry for the noob question but i've installed 14.04 and am looking to install the latest dev version. been having trouble finding it
[04:10] <holstein> waymon: ?
[04:10] <holstein> waymon: you are looking for 14.10?
[04:10] <holstein> you'll need to wait a while..
[04:10] <waymon> ooo, yeah, 14.10 would be great
[04:10] <holstein> waymon: *will* be great
[04:10] <holstein> waymon: its not available yet
[04:11] <waymon> i know it's not stable, i just wanna play with it
[04:14] <waymon> no dice?
[04:16] <holstein> waymon: its not that its not stable, friend.. it literally doesnt exist yet
[04:16] <holstein> waymon: if you want the freshest ubuntu code, install 14.04 and update
[04:16] <holstein> waymon: if you want newer/relevant, try debian testing
[04:17] <waymon> oh okay, i see
[04:21] <Unit193> holstein: Debian unstable or experimental, testing isn't as new as those.
[04:21] <holstein> Unit193: i think its unstable i was thinking of
[04:21] <holstein> waymon: ^
[04:22] <holstein> i forget that testing isnt the newest...
[04:24] <waymon> side question: has anyone tried to install gnunet?
[04:25] <holstein> !info gnunet
[04:25] <holstein> waymon: should be as easy as "sudo apt-get install gnunet"
[04:25] <waymon> you'd think so
[04:25] <waymon> it's not the latest version tho
[04:25] <waymon> 0.10 is the new shit
[04:27] <holstein> !language
[04:27] <holstein> waymon: you can ask them for the latest version for the operatin system you are using
[04:27] <waymon> my bad
[04:27] <Unit193> Debian doesn't have the new version, thus Ubuntu doesn't either (Yes, Ubuntu can get newer versions, and does all the time, but that's not high priority.)
[04:28] <holstein> waymon: *buntu typically "freezes" versions, and gets security updates.. rolling releases would get the latest as they come out
[04:28] <holstein> you can add ppa's, or build whatever you like
[04:32] <waymon> yeah, i'm just trying to figure out where to get the latest gnunet
[04:32] <waymon> it has a bunch of dependencies that are super high versions
[04:34] <holstein> waymon: ppa
[04:34] <holstein> waymon: try ppa, then ask them for a package, or for what you are supposed to do
[04:42] <waymon> oooo found this if anyone else is interested https://gnunet.org/content/installing-gnunet-0101-ubuntu-1404
[04:42] <holstein> im ok with the repo version..
[04:43] <Unit193> I've never used gnunet once in my life.  Though, not much of a development question.
[06:19] <jphilipz> hi all, just tweeting a number of problems i saw during trying out 14.04 like network links not showing on desktop - http://img.ly/yEij - https://twitter.com/jphilipz/status/457396969363607552
[06:24] <Unit193> Correct gvfs tools installed?  Find them in Thunar alright?
[06:35] <Unit193> Logan_: Awwh dang man, you're not in ~ubuntu-backporters! :(
[07:04] <Logan_> Unit193: I feel like backporting is kinda dead
[07:05] <Unit193> Considering they pinned it at 100?  Yeah, stuck with stale applications for good. :/
[07:20] <Logan_> Unit193: having them install automatically would imply that they're supported :P
[07:22] <Unit193> Logan_: I suppose no better way now or in the works?
[07:22] <Logan_> PPAs?
[07:23] <Unit193> I said better. :P
[07:23] <elfy> hi Logan_
[07:23] <Logan_> you need the user to explicitly realize that they are installing unsupported software
[07:23] <Unit193> Logan_: Shouldn't you be sleeping, prepping for class? :P
[07:23] <Unit193> Indeed.
[07:23] <Logan_> if we can hack apt to say "this is available, but it's not supported because it's a backport," then I think we have a plan on our hands :)
[07:24] <Logan_> and hey elfy
[07:24] <Unit193> Though, the source should be pretty good, not just some random joe.
[07:24] <Logan_> and no, it's a Friday night, silly
[07:24] <Logan_> I do what all college students do on Friday nights
[07:24] <Logan_> go on IRC
[07:24] <Unit193> :P
[07:24] <elfy> lol
[07:24] <Logan_> well, I was invited to a party
[07:24] <elfy> Unit193 calls the kettle black - unbelievable :p
[07:25] <Unit193> elfy: Nah, he's just more sane than I am.
[07:25] <elfy> :)
[07:25] <Logan_> me? sane? :P
[07:25] <Unit193> elfy: To me, you normally get on at 2am, which is "morning there", but still considered 2am. :P
[07:25] <elfy> ha ha ha
[07:25] <Unit193> Logan_: I actually remember your TZ, because it's same here.
[07:26] <Logan_> are you in the US?
[07:26] <Logan_> actually, I probably shouldn't bother asking because you're anonymous
[07:26] <Logan_> so clearly you keep your identity private :P
[07:26] <Unit193> Logan_: Ohioooooooooo.
[07:27] <Logan_> ah
[07:27] <Logan_> by the way, I didn't mean to offend you if your legal name is in fact "Unit 193"
[07:27] <elfy> I'm not anonymous - I really are elfy and forestpiskie
[07:27] <Unit193> Logan_: Hey, even Debian considers me "Unit 193"
[07:45] <Unit193> Logan_: ...Having fun with ubottu now? :P
[07:45] <Logan_> there are some weird factoids that need to be deleted
[07:45] <Logan_> see http://ubottu.com/factoids.cgi?search=love
[07:47] <Logan_> run those commands in order, and we should be good :)
[07:48] <Logan_> night all
[07:48] <Unit193> G'night.
[07:48] <elfy> night Logan_
[08:14] <elfy> brainwash: morning
[08:14] <brainwash> good morning elfy
[10:07] <starrats> good morning everyone!
[10:26] <knome> Unit193, i just figured out how to link that style with the wordpress gallery. yay!
[10:32] <knome> elfy, poke
[10:32] <knome> elfy, check out http://xstaging.lallinaho.fi/2014/04/18/image-alignment-testing-post/
[10:33] <elfy> what am I looking at that for?
[10:33] <knome> resize the screen horizontally
[10:33] <knome> and look at the images
[10:33] <knome> err, s/screen/window/
[10:34] <elfy> that appears to work :)
[10:34] <knome> cool
[10:34] <knome> looking to land that stuff soonish
[10:35] <knome> i've now figured a miles better way to do it than late yesterday night
[10:35] <elfy> :)
[10:35] <knome> the editor side still needs working though
[10:35] <knome> :|
[10:36] <knome> not sure if i'm able to get that completely right, it seems to have some quirks
[10:36] <knome> (not showing medium-sized images, while the shortcode defines that, and works on the public facing side)
[10:36] <knome> but i guess that's a minor issue
[10:37] <elfy> I'd guess that you're guess is better than mine :)
[10:38] <knome> *your
[10:38] <knome> :P
[10:38] <knome> well it is a minor annoyance
[10:38] <elfy> :p
[10:38] <knome> but there doesn't seem to be much to do about it unless you want to poke the wordpress core... and that's meh
[10:38] <knome> and not possible with canonical IS
[10:39] <elfy> ...
[10:39] <knome> but yeah, i wouldn't do that with my clients' sites either
[10:39] <knome> it would break upgrades completely
[10:39]  * elfy is looking at rejigging the package testsuites for unicorn
[10:39] <elfy> smaller
[10:40] <knome> hehe
[12:03] <knome> bluesabre, whatever... fix it.
[12:03] <knome> :)
[12:04] <bluesabre> gotta know what's broken
[12:04] <bluesabre> since it worked for me all the way to release day
[12:04] <bluesabre> haven't tested today
[12:04] <knome> ;)
[12:04] <bluesabre> but I don't see why anything would have changed
[12:04] <knome> yeah... we should fix it for "people".
[12:05] <knome> but afaik, my suggestion is a working workaround
[12:05] <knome> so if you don't happen to be around, i will tell them that
[12:07] <bluesabre> but that won't help... since xscreensaver doesn't control suspending
[12:08] <knome> if it won't help, they will come back
[12:33] <knome> bluesabre, ping, #xubuntu
[13:31] <elfy> knome: does adding the guest session stuff to lightdm.conf actually work? https://help.ubuntu.com/stable/ubuntu-help/shell-guest-session.html
[13:31] <knome> elfy, yes, but the link you pasted has a better way to do it
[13:31] <elfy> ok
[13:31] <knome> basically, it does the same thing, outside the xubuntu file
[13:31] <elfy> didn't want to spam #xubuntu
[13:31] <knome> and is removable as is
[13:32] <knome> and since the setting probably covers all flavors anyway...
[13:32]  * elfy still has 'what DID they do to lightdm" on his list
[13:32] <knome> heh
[13:33] <knome> amigamagic, actually, redirecting to the page elfy noted
[13:34] <amigamagic> knome, ok I didn't find that...
[13:34] <knome> amigamagic, oh me, that's not working properly
[13:34] <knome> >__<
[13:34] <amigamagic> what is that doesn't work?
[13:34] <knome> works now
[13:34] <knome> the redirect, but i fixed it
[13:35] <amigamagic> on that page elfy pasted, the method is slightly different... It works on 14.04 ?
[13:36] <elfy> amigamagic: those lightdm files are all new to 14.04
[13:36] <knome> amigamagic, it does practically the same thing
[13:37] <knome> amigamagic, but instead of editing the xubuntu file, it creates a new one
[13:37] <knome> amigamagic, which works, like the xubuntu file, for all flavors
[13:37] <knome> amigamagic, also, this means the xubuntu conf file is upgradeable by future xubuntu upgrades without having to worry/ask the user which version they want
[13:38] <amigamagic> ok
[13:39] <knome> the .d directory works like /etc/apt/sources.list.d/
[13:39] <knome> all the files in that are read as if they were in /etc/apt/sources.list
[13:39] <knome> in this case, as if they were in /etc/lightdm/lightdm.conf
[13:39] <knome> the numbers in the files determine the order they are ran in
[13:39] <knome> elfy, ^
[13:41] <amigamagic> why 50 and 60 as numbers?
[13:41] <knome> elfy, does that answer some of your questions?
[13:41]  * elfy thought as much - but hadn't tracked the info down yet - thanks :)
[13:41] <knome> amigamagic, well, consider you had 1, 2, 3 and wanted to add something between 1 and 2
[13:41] <knome> amigamagic, you would have to rename files 2 and 3 to 3 and 4
[13:42] <amigamagic> ok, I understand, but... 50?
[13:42] <knome> well, why not?
[13:42] <knome> the bigger the number, the bigger the chance the modification is taking preference
[13:42] <amigamagic> so you could make run 49 configuration files before it?
[13:42] <knome> yes.
[13:42] <knome> practically, yes..
[13:43] <knome> the number itself is irrelevant...
[13:43] <amigamagic> ok
[13:43] <knome> but from the users point of view, it's better that it is 50 than 20
[13:43] <knome> because if in 14.10, people decided to force guest sessions, and it happened to be 20...
[13:44] <knome> it would be a race condition; whichever file had the "bigger" filename
[13:44] <knome> 20_xubuntu_enable_guest.conf would take preference
[13:44] <knome> while 20_enable_guest.conf would not
[13:44] <knome> the developers can't know what files the user has in their directory
[13:44] <knome> so they will most probably just add the next incremental number (*10)
[13:46] <amigamagic> so, after the number, the precedence it's given to the longer filename?
[13:47] <knome> well, the "bigger" when compared...
[13:47] <knome> x > aaa
[13:48] <amigamagic> ok, so it's a standard sorting method based on the filename
[13:48] <knome> yes
[13:49] <amigamagic> thanks for the info
[13:49] <knome> np
[14:35] <knome> bbl ->
[17:29] <Aurvandill> i learned the basics of c++ and now i want to learn how to develop for linux. what is the next step to learn or to do?
[17:39] <kajair> 4. i want to resize windows. you should point in the exactly same pixel to resize or close or move
[17:39] <kajair> 5. there is not able to connect lubuntu and xubuntu in ssh
[17:39] <kajair> 6. double click in titlebar or drag to up wont set to maximize
[17:40] <kajair> *6: only drag it to upper side
[18:49] <brainwash_> bug 1310045
[18:49] <brainwash_> ^ :D
[18:50] <brainwash_> bluesabre: should we merge https://code.launchpad.net/~thad-fisch/lightdm-gtk-greeter/zoomed ? I planned to add more resize methods and so on, but lost the interest
[18:54] <ali1234> lol
[18:56] <brainwash_> so we are 1 step ahead :)
[19:01] <ali1234> what exactly does that do?
[19:02] <brainwash_> my branch?
[19:03] <ali1234> yes
[19:03] <brainwash_> it zooms the background AND puts it in the center of the screen
[19:03] <brainwash_> like xfdesktop does
[19:03] <brainwash_> currently the greeter only zooms it
[19:05] <brainwash_> so you see the top part if your background pic does not fit your screen
[19:07] <starrats>  to that channel
[19:08] <brainwash_> ?
[19:09] <starrats> hit the wrong button, lol, sorry
[19:09] <brainwash_> ah ok
[19:10] <starrats> was typing in another channel and it must have popped over here
[19:16] <23LAAFBCU> I have a Xubuntu 13.10 install on an old machine that insists on locking the screen after suspend/resume.  I've checked settings for xscreensaver and power management, and even removed those packages.  I updated to 14.04 and the problem persists.  I disabled light-locker, and even removed it as well.  I still get a locked screen after resuming.  I asked in #xubuntu channel but someone suggested I ask here.  Google
[19:16] <23LAAFBCU> was not helpful, too much fodder.
[19:17] <23LAAFBCU> What else could be locking my screen?
[19:18] <brainwash_> how does the lock screen look like?
[19:20] <23LAAFBCU> it looks just like the screen i get if i log out, so lightdm i think
[19:21] <brainwash_> ok, but didn't you remove light-locker already?
[19:21] <23LAAFBCU> bar at the top..computer name on the left top, a few buttons at the top left with session, logoff buttons
[19:21] <23LAAFBCU> yes i tried that out of desperation
[19:22] <brainwash_> and did you relog once after removing it?
[19:22] <23LAAFBCU> removed xfce-power-manager, xscreensaver, and light-locker after making sure they werent set to lock the screen
[19:22] <23LAAFBCU> yes, rebooted
[19:23] <brainwash_> that's odd
[19:25] <23LAAFBCU> let me try another reboot just to make sure
[19:25] <brainwash_> just to make sure, it's the lightdm lock screen and not the normal login screen, right?
[19:25] <23LAAFBCU> it looked jsut like the screen i see if i logout
[19:25] <brainwash_> so you unlock you user account and get redirected to your running session?
[19:25] <brainwash_> your user account
[19:26] <23LAAFBCU> im using autologin with light dm, there's no prompt when i boot up.  Only fater a suspend
[19:26] <23LAAFBCU> after**
[19:27] <brainwash_> does "pgrep light-locker" return any output?
[19:27] <23LAAFBCU> ill check here when it finishes rebooting
[19:28] <23LAAFBCU> im not sure if this is realted but i should mention it....it also doesnt seem to save the state of opened windows..that would be the saved session right?
[19:28] <brainwash_> after you unlock?
[19:29] <23LAAFBCU> yes
[19:29] <brainwash_> this indicates that your running session crashed
[19:29] <brainwash_> so the system returns to the login screen
[19:30] <23LAAFBCU> oh
[19:30] <23LAAFBCU> i see
[19:30] <23LAAFBCU> is there a log i can find info in to confirm this is happening
[19:31] <brainwash_> there are a few, like the general system log file /var/log/syslog
[19:31] <brainwash_> or lightdm related logs in /var7log/lightdm/
[19:31] <brainwash_> /var/log/lightdm/
[19:31] <23LAAFBCU> its an old beast of a computer...should probably have died long ago but, it supports s3 and s1
[19:31] <brainwash_> and X session related ones in ~/.cache/upstart/
[19:32] <23LAAFBCU> i think ive looked in syslog, and found nothing that stood out to me
[19:32] <brainwash_> mmh
[19:33] <brainwash_> also check /var/log/pm-suspend.log to get some info about the actual suspend/resume cycle
[19:34] <brainwash_> suspend issues can be an annoyance
[19:36] <23LAAFBCU> yeah....i seem to recall it working properly at first though i cant be sure anymore
[19:37] <jphilipz> hi all, i just tried out xubuntu 14.04 and noticed a few things that i wanted to bring to the dev team
[19:38] <23LAAFBCU> it didnt occur to me it could be the session crashing though..at least I have another way to look at the problem now..thank you
[19:39] <23LAAFBCU> I'll see what i can find and get back to you if I have any more info a bit later if youre areound..thanks sir
[19:43] <jphilipz> firstly i had noticed that the country i'm living in 'United Arab Emirates' had incorrect time information - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1310065
[19:45] <jphilipz> ubottu: yet thats the first problem i found
[19:45] <jphilipz> ubottu: glad to know it :)
[19:46] <knome> Aurvandill, get to know the xfce code. aiui, it's mostly in pure C though.
[19:46] <jphilipz> while on the live cd as well as after the installation, the bluetooth icon doesnt go dim after i disable bluetooth - http://img.ly/yEi5
[19:48] <jphilipz> also in the installer, the scrollbars need to be disable for the slide show - http://img.ly/yEiC
[19:49] <Aurvandill> knome thx
[19:50] <jphilipz> during the slide show i noticed that some headings were smaller than text underneath it - http://t.co/u30Hupb2MZ
[19:50] <knome> jphilipz, i'm not sure if the bluetooth icon should dim or not when it's not enabled... but i would check if there is a bug for that, and file if not. it's a wishlist/low level one though
[19:51] <knome> jphilipz, the installer scrollbars are known, but we are unable to triage it since many cycles. it's disappeared for most people though, so not a high-priority bug either... what was your installation resolution?
[19:51] <jphilipz> knome: what package should i file that under
[19:51] <knome> jphilipz, headings, not a bug.
[19:52] <knome> jphilipz, indicator-bluetooth
[19:52] <jphilipz> knome: not a tech bug, likely a design issue
[19:52] <knome> it's a design decision
[19:52] <knome> the header text itself isn't very important, but splits the two paragraphs nicely
[19:53] <jphilipz> well another design decision i thought i'd bring up was such small icons on the 'ready to go' slide when there is alot of space on the slide - http://t.co/6BTzrqDJ93
[19:54] <jphilipz> well as the heading is 'We need your help!' it being larger might catch peoples attention
[19:55] <jphilipz> is there a particular indicator-bluetooth package for xubuntu
[19:55] <knome> jphilipz, i rather have smaller icons and plenty of padding that a too packed slide
[19:55] <knome> jphilipz, "particular" package?
[19:56] <jphilipz> knome: well i landed at https://launchpad.net/ubuntu/+source/indicator-bluetooth
[19:56] <knome> that's it.
[19:56] <jphilipz> and that seems to be for ubuntu
[19:56] <knome> xubuntu uses the same package repositories as ubuntu, so every "xubuntu package" is a ubuntu package
[19:57] <knome> jphilipz, you can run 'ubuntu-bug indicator-bluetooth' in the terminal, and relevant information is posted to the bug report.
[19:58] <jphilipz> knome: i'll give that a shot
[19:59] <jphilipz> knome: you asked about my screen size, its 1280x768
[20:01] <knome> jphilipz, can you "me too" bug 986283 and add your resolution as a comment
[20:01] <knome> as you see, that bug is filed two years ago and there hasn't been too much activity...
[20:03] <jphilipz> knome: i've me too'd
[20:04] <knome> tbh, i thought that bug was gone...
[20:06] <jphilipz> about the small icons, ye most of them are still recognizable but abiword and gnumeric arent really
[20:08] <jphilipz> bumping them up from 16 to 22 will make them easier to see
[20:08] <jphilipz> especially as these days, screen are getting bigger and bigger
[20:08] <jphilipz> :)
[20:12] <knome> screens are bigger, but resolutions usually not
[20:13] <knome> so 16px might even be bigger than before...
[20:13] <ali1234> i bet that installer scrollbar issue is related to screen DPI, ie not directly related to resolution
[20:14] <knome> ali1234, if you can confirm that, it's a step forward...
[20:14] <ali1234> forcing 96 DPI is pretty much a requirement everywhere
[20:14] <ali1234> jphilipz: do you happen to know the DPI on your monitor?
[20:15] <ali1234> knome: do we have a screenshot of the installer looking "correct" somewhere?
[20:17] <jphilipz> ali1234: let me get that for you, have to turn the laptop on again
[20:17] <ali1234> jphilipz: if you could check it in the livecd that would be even better...
[20:17] <jphilipz> okay, let me burn the iso to a usb
[20:18] <ali1234> also, did you run the installer from desktop session?
[20:18] <ali1234> "install now" or "try ubuntu"
[20:18] <jphilipz> yes from desktop session
[20:18] <ali1234> okay
[20:19] <ali1234> knome: how are the slides done? are they just bitmaps?
[20:19] <knome> ali1234, ergh, they are html
[20:19] <knome> ali1234, lp:ubiquity-slideshow-ubuntu
[20:20] <ali1234> ah, okay then. so that makes DPI issue more likely...
[20:21] <ali1234> is there someway to run that as a "preview" fromt he desktop?
[20:22] <ali1234> ie without having to boot the livecd?
[20:22] <knome> ali1234, yep, get the branch, then run ./test-slideshow.sh xubuntu
[20:23] <ali1234> thanks
[20:25] <ali1234> yup, works fine here...
[20:25] <jphilipz> well about resolutions not getting bigger, w3schools.com has 78% of users above my laptop resolution and on my desktop (1440x900), the 16px icons are similarly as small if not smaller, as i'm farther away from the screen
[20:25] <ali1234> w3fools.com
[20:26] <ali1234> jphilipz: yeah it's not the resolution though, it's the DPI
[20:26] <ali1234> if the DPI is different, elements may grow, causing the scrollbars
[20:26] <jphilipz> well the scrollbars were one thing, and the icons were a different thing
[20:27] <ali1234> okay. i didnt read all the log :)
[20:28] <jphilipz> where do i go for the dpi
[20:28] <ali1234> xdpyinfo | grep dots
[20:29] <jphilipz> forgot to modify grub for my keyboard, need restart again
[20:30] <knome> ali1234, is there a way to reproduce the bug with any monitor?
[20:30] <ali1234> xfce has a "DPI override"
[20:30] <ali1234> look at this: http://imagebin.org/306533
[20:30] <knome> ali1234, pumping up the DPI only made the text so big it was outside the visible area
[20:30] <jphilipz> 96
[20:30] <ali1234> hmm
[20:31] <ali1234> okay it isn't DPI then
[20:31] <ali1234> does it happen on every page of the slideshow?
[20:31] <knome> when it does, it does
[20:31] <jphilipz> every page for me
[20:31] <ali1234> in my screenshot, the text is further down the page
[20:32] <knome> ali1234, if i could reproduce, i could look at things to do to make that not happen
[20:32] <knome> but since i can't...
[20:32] <ali1234> how about making #slideshow width and height 100% instead of fixed px?
[20:32] <jphilipz> knome: you want me to run any command to help your testing
[20:32] <ali1234> i can't reproduce either, at least not without booting up a livecd
[20:33] <ali1234> jphilipz: you could check if it happens with a regular unity iso
[20:33] <ali1234> if it doesn't, we can just steal their CSS :)
[20:33] <jphilipz> no it didnt happen when i installed ubuntu 14.04, if i remember correctly
[20:34] <knome> jphilipz, bzr branch lp:ubiquity-slideshow-ubuntu
[20:34] <knome> jphilipz, cd ubiquity-slideshow-ubuntu
[20:34] <knome> jphilipz, ./test-slideshow.sh xubuntu
[20:34] <knome> jphilipz, and tell if the scrollbars are visible now
[20:34] <ali1234> it looks like the test thing never shows scrollbars
[20:35] <jphilipz> the slideshow only happens after the installation files have started copying and i've answered all the dialogs
[20:35] <knome> jphilipz, no, in your installed system...
[20:36] <knome> i think i know what to do to fix that, but i'm not sure how to test if it works....
[20:37] <ali1234> hmm look at slideshow.conf for ubuntu
[20:37] <ali1234> width:752 height:442
[20:37] <jphilipz> knome: okay let me boot the os then
[20:37] <ali1234> they added 2 pixels to each
[20:37] <ali1234> i wonder why? ;)
[20:37] <knome> ali1234, but their css says the same widths.
[20:37] <jphilipz> wouldnt it be simpler to disable scrollbars in the window and that would solve it
[20:38] <knome> jphilipz, that's what we're doing. but it's not working
[20:38] <jphilipz> knome: okay
[20:38] <ali1234> what we really need to do is enable scrollbars on the test app
[20:39] <ali1234> because disabling them there does work
[20:39] <ali1234> and it is masking the problem
[20:40] <knome> ali1234, bzr branch lp:~knome/ubiquity-slideshow-ubuntu/scrollbar-fix-986283
[20:40] <knome> http://bazaar.launchpad.net/~knome/ubiquity-slideshow-ubuntu/scrollbar-fix-986283/revision/628
[20:40] <knome> that looks like something that could very well fix the bug.
[20:41] <ali1234> ah i noticed that difference too :)
[20:41] <ali1234> just saw it...
[20:41] <knome> but since i can't reproduce... :)
[20:42] <ali1234> the test app runs inside this Slideshow.py
[20:47] <jphilipz> okay i ran the commands and there is scrollbars
[20:48] <ali1234> hmmmm
[20:48] <jphilipz> there is no scrollbars, sorry
[20:48] <ali1234> okay, that makes more sense
[20:49] <ali1234> knome: is ubiquity proper Qt now or still Gtk?
[20:49]  * knome shrugs
[20:50] <jphilipz> i can run another installation and run any commands if you like
[20:50] <xnox> ali1234: ubiquity has two frontens - qt and gtk. xubuntu uses gtk
[20:50] <ali1234> hi xnox. any idea about these scrollbars?
[20:51] <knome> jphilipz, since the bug isn't reproducible with the testing script, not sure if that would help much...
[20:51] <xnox> ali1234: no idea what you are asking about.
[20:51] <knome> bug 986283
[20:51] <ali1234> xnox: ubiquity-slideshow web component has scrollbars
[20:52] <knome> damn memory, now i'll remember that bug number for a week :|
[20:52] <ali1234> xnox: which frontend does ubuntu use?
[20:56] <ali1234> it should be possibly to instrument gtk_ui.py from real ubiquity and try to reproduce that way
[20:57] <xnox> ali1234: is it reproducible in english locale, only only in longer languages - e.g. french like in the bug report?
[20:58] <ali1234> not sure but the bottom comment has a screenshow that is in english
[20:58] <knome> tbh, i think my branch linked to the bug should fix the issue.
[20:58] <xnox> ali1234: it is related to the default theme, lack of overlay scrollbars, slideshow itself, and the size metrics declared by the slideshow.
[20:58] <knome> but somebody should be able to reproduce that bug, then run the same environment with the new branch
[20:58] <xnox> ali1234: try tweaking the declared sizes of the slideshow it it's manifest.
[20:58] <jphilipz> i filled this bug at xfce after seeing it in xubuntu - https://bugzilla.xfce.org/show_bug.cgi?id=10831
[20:59] <ali1234> xnox: the problem is we can't reproduce it with the test-slideshow.sh from the slideshow package
[20:59] <ali1234> because it is hardcoded to never show scrollbars
[20:59] <knome> xnox, ^ see my comments. this is the first time i hear about this bug in probably two years, and i thought it was already gone...
[21:00] <ali1234> if you google "xubuntu installer" and look at image results there a screenshot supposedly from 13.10 showing this bug :)
[21:00] <knome> possibly
[21:01] <jphilipz> knome: about the bluetooth icon dimming, i just tried ubuntu and their icon dims
[21:03] <xnox> knome: i fix it with ubuntu slideshow every gtk update, every theme update, and every unity update....
[21:03] <knome> xnox, >__<
[21:03] <ali1234> xnox: but how do you test it without rebuilding a full iso?
[21:04] <xnox> ali1234: in a live cd, you can modify files in place and restart the installer.
[21:04] <xnox> ali1234: also probably easier to do an oem install and keep on restarting oem client config.
[21:04] <ali1234> okay. i'm going to try to make a test harness which is more similar to real ubiquity
[21:04] <knome> xnox, i don't think oem installations work for xubuntu...
[21:07] <jphilipz> another bug i reported with xfce after trying xubuntu - https://bugzilla.xfce.org/show_bug.cgi?id=10834
[21:07] <knome> jphilipz, yes, we noticed the bug
[21:07] <ali1234> hey at least they show up in plugin-places now
[21:07] <jphilipz> knome: both of them
[21:07] <knome> hmm, right
[21:08] <knome> jphilipz, %20 is space, so it might be normal
[21:08] <jphilipz> well if you look at the screenshot, it only happens in thunar
[21:09] <jphilipz> was wondering, can you install grub on an extended partition
[21:10] <jphilipz> was also wondering why the search for time zones in ubiquity is case sensitive
[21:11] <knome> bluesabre, i just filed two new bugs against menulibre. minor, but nonetheless.
[21:11] <jphilipz> must be mistaken, it must be just slow
[21:14] <jphilipz> does ubiquity time zone search also search for cities?
[21:14] <xnox> jphilipz: depends f you are online
[21:18] <jphilipz> xnox: i meant at the 'where are you?' page, where i can type in a country but only a few cities that i type in come up
[21:18] <jphilipz> those same cities i can click on the map and get but if i search for them, they dont come up
[21:19] <jphilipz> as an example, i can click on the city Dubai, but cant search for it
[21:22] <jphilipz> also found at the same page that they had wrong time zones for United Arab Emirates and Bahrain - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1310065
[21:23] <jphilipz> knome: bluetooth dim has been filed - https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1310101
[21:25] <jphilipz> running the ubuntu installer now and no scrollbars
[21:26] <jphilipz> after looking at the screenshot some more, its possible the '>>' arrows might be causing it
[21:26] <knome> jphilipz, no, that's not it really...
[21:26] <knome> jphilipz, it's something out of the "ordinary"
[21:27] <jphilipz> knome: quite funny that on the same pc, with the same installer, i get two different behaviours
[21:28] <brainwash_> isn't that blueman's tray icon? or is this indeed indicator-bluetooth?
[21:33] <ali1234> okay i reproduced it
[21:33] <ali1234> but it is tricky
[21:38] <knome> jphilipz, well there is a code difference...
[21:38] <jphilipz> you mean the html slides
[21:38] <ali1234> how do i push to lp scratch again?
[21:38] <knome> scratch?
[21:39] <ali1234> yeah, like private junk repo
[21:39] <knome> bzr push lp:~user/+junk/poop
[21:39] <knome> ?
[21:39] <knome> jphilipz, yep
[21:39] <ali1234> yeah that's it
[21:42] <ali1234> knome: http://bazaar.launchpad.net/~a-j-buxton/ubiquity-slideshow-ubuntu/scrollbar-issue/revision/642
[21:42] <ali1234> in real ubiquity the webkit object is put inside a GtkScrolledWindow. i made the test harness do the same thing, and i can make it show scrollbars
[21:43] <ali1234> but only if i make the window bigger and then make it smaller
[21:43] <jphilipz> was wondering why none of the ubuntu derivatives put their own name in grub
[21:44] <jphilipz> i guess mint is an exception
[21:44] <Unit193> jphilipz: Kubuntu does, but it can break UEFI.
[21:44] <Unit193> Ah, right, derivs, not flavors.
[21:44] <ali1234> same applies to them
[21:45] <Unit193> Sure, but they're in more of a position to fix that.
[21:45] <jphilipz> i heavily distro hopping and trying out as many distros as i can on a 500gb hard disk with 10gb per installation and i get to many duplicates
[21:45] <jphilipz> yes i see kubuntu in my list :)
[21:47] <knome> ali1234, i don't think that's the problem
[21:48] <ali1234> sure it is
[21:48] <knome> ali1234, or, well, maybe it can be "fixed" with my branch
[21:48] <ali1234> if ubiquity didn't put it in a scrolled window, there would be no scrollbars
[21:48] <knome> ali1234, but being *too small* doesn't happen in the slideshow
[21:48] <knome> ali1234, anyway, test my branch with that.
[21:49] <xnox> ali1234: ubiquity uses scrolled window, to make sure slideshow doesn't arbitrary expand the installer window into full-screen.
[21:49] <ali1234> the scrollbars triggers randomly if the webkit window is bigger than client area - size of scrollbar
[21:52] <jphilipz> all right all, i'm off, it was fun chatting with you all and submitting the bugs, likely wouldnt have submitted them to launchpad if you guys werent here
[21:52] <jphilipz> i normally just tweet my bugs and mention the distro
[21:53] <ali1234> knome: your branch doesn't fix it, i can still trigger the scrollbars. it may fix it in real ubiquity of course
[21:54] <jphilipz> i had sent in this bug to xfce and it effects xubuntu as well - https://bugzilla.xfce.org/show_bug.cgi?id=10762
[21:56] <jphilipz> keep up the great work, as an ex-windows XP user i jumped at lxde and mate but i think my home is with xfce, i look forward to converting soon
[22:02] <knome> ali1234, hmph.
[22:02] <ali1234> i don't think my test case is valid tbh
[22:02] <ali1234> it's not 100% reproducable
[22:02] <knome> yeah, as i said, i don't think it's exactly the same thing really
[22:03] <knome> i see why it can appear to be a valid test, but it really isn't
[22:03] <knome> because the window is always the same size
[22:03] <knome> that means there seems to be something really weird going on.


[03:01] <kenvandine> any archive admins around that can look at some packages in binNEW that are holding up builds?
[03:18] <AbsintheSyringe> cjwatson, about recent talks about "slashdot" releasing false claims that ubuntu was moving to rolling releases, this is what I had in my mind when I supported this idea of being future for all linux platforms not just ubuntu http://theravingrick.blogspot.com/2010/11/ubuntu-is-not-moving-to-rolling-release.html
[03:18] <AbsintheSyringe> google picked it up
[07:03] <didrocks> good morning
[07:04] <axp2> Hi didrocks
[07:04] <didrocks> hey axp2
[07:04] <axp2> Or good afternoon
[07:45] <dholbach> good morning!
[08:00] <didrocks> hey dholbach!
[08:01] <dholbach> salut didrocks
[08:01] <cdbs> Hi dholbach !
[08:02] <dholbach> heya cdbs
[08:05] <dholbach> pitti, james_w: could it be that the workitems tracker is a bit broken right now?
[08:05] <dholbach> it tells me that we have all kinds of unknown milestones
[08:17] <cdbs> Can someone please look at bug #688002 and its attached patch? Currently the hplip package is uninstallable and broken. This patch fixes it. Thanks!
[08:20] <cdbs> s/uninstallable/non installable/
[08:24] <cdbs> its a debdiff
[08:42] <tumbleweed> tkamppeter: cdbs's fix isn't right
[08:44] <pitti> good morning
[08:45] <pitti> ScottK: kdegraphics> built now
[09:01] <micahg> pitti: could you please take a look at bug 685421
[09:09] <pitti> micahg: ah, thanks; will respond in the bug report
[09:11] <micahg> pitti: thanks
[09:14] <pitti> micahg: I'll get to it today
[09:14] <pitti> dholbach: yes, over night I got tons of cron mail from it; I'll have a look later on
[09:15] <micahg> pitti: great, thanks, let me know if there need to be any rebuilds because of it, I'll be happy to help
[09:15] <dholbach> super
[09:15] <pitti> micahg: I'll care about hedgewars; if you see another one being affected, feel free to upload a rebuild once the fixed mangler is in natty
[09:16] <micahg> pitti: ok, I was just wondering if there's any way to tell if something would've been affected
[09:16] <pitti> micahg: not without actually trying to run the game, I think
[09:16] <micahg> I'll keep an eye out for bugs though
[09:17] <pitti> but I guess we should hear about the games people care about
[09:29] <ev> @pilot out
[09:55] <pitti> ogra: I can't help it, but kiko's mugshot on https://launchpad.net/~kiko just looks like you
[09:58] <cdbs> @pilot in
[09:58] <cdbs> :)
[09:58] <dholbach> cdbs, woohoo!
[09:58]  * dholbach hugs cdbs
[09:58] <dholbach> hey sabdfl
[09:59]  * cdbs hugs dholbach
[09:59] <sabdfl> good morning, /hugs back :-)
[09:59]  * cdbs hugs sabdfl
[09:59] <sabdfl> prescience
[09:59] <dholbach> cdbs, thanks for patch piloting
[10:00]  * dholbach hugs sabdfl too
[10:00] <sabdfl> i love visiting here, /hugs dholbach
[10:00] <dholbach> :-)
[10:00] <cdbs> dholbach: yup, but there's barely anything in the sponsor queue for universe packages
[10:00] <cdbs> :)
[10:00] <dholbach> http://reqorts.qa.ubuntu.com/reports/sponsoring-stats/ looks GOOD if you ask me :)
[10:01] <cdbs> Its like the stock market during the recession :D
[10:01] <tumbleweed> cdbs: you can also help pilot things that you don't have upload rights for
[10:01] <cdbs> tumbleweed: which is what I am doing ATM
[10:01] <dholbach> the sponsoring queue is getting emptier, but we still have LOADS of patches sitting in launchpad
[10:01] <dholbach> and branches for that matter :)
[10:02] <cdbs> yup, UDD merges need attention
[10:02] <dholbach> I hope that harvest can help with that in the future: http://harvest.ubuntu.com/opportunities
[10:02] <dholbach> and people will pick up opportunities when doing an upload anyway
[10:05]  * dholbach releases a new harvest
[10:11] <pitti> james_w: what was the rationale of this "extra-projects" branch? if there are blueprints which aren't against the ubuntu project for linaro, why not just track them in a separate linaro.cfg and output?
[10:11] <pitti> james_w: otherwise we'll have to either ignore one set of milestones, or merge them, which is also confusing (and would break the auto-reset, etc.)
[10:39] <Riddell> cdbs: aren't I ment to be the patch pilot today?
[10:39] <dholbach> Riddell, there can be more than one :)
[10:39] <cdbs> Riddell: I think many people can patch pilot at once
[10:40] <Riddell> @pilot in
[10:40] <dholbach> woohoo!
[10:40]  * dholbach hugs Riddell
[10:40]  * cdbs hugs Riddell
[10:40] <cdbs> though this channel topic just hit its maximum char limit
[10:41] <cdbs> Riddel is written, not Riddell
[10:41] <cdbs> I think it would be good to remove the Natty GDM login broken thing
[10:41] <seb128> you can drop the natty gdm login issue
[10:52] <cdbs> tkamppeter: Thanks for those uploads :)
[11:00] <cjwatson> hallyn_: I switched to quilt for later versions of grub2, but if you're looking at lucid then yes it's cdbs-edit-patch
[11:01] <cjwatson> kenvandine: it helps if you give specific package names when asking that sort of thing
[11:01] <cjwatson> no idea what to prioritise here
[11:03] <seb128> cjwatson, what did kenvandine ask to do?
[11:08] <cjwatson> 03:01 <kenvandine> any archive admins around that can look at some packages in binNEW that are holding up builds?
[11:08] <seb128> cjwatson, ok, pîtti sorted it since
[11:08] <seb128> it was libdbusmenu I think
[11:09] <cjwatson> ok
[11:11] <ogra> pitti, you mean like http://www.grawert.net/230405_030.jpg ?
[11:11] <ogra> (sorry, missed to scale it down)
[11:13] <pitti> ogra: 'zactly :)
[11:14] <ogra> *g*
[11:17] <cdbs> g2g, did some patch-piloting on -motu
[11:18] <cdbs> and elsewhere
[11:18] <cdbs> @pilot out
[11:34] <Q-FUNK> is anybody taking care of doing a rebuild upload for eog and gedit?  they seem to be the last two bits of gnome that use python2.6 here.
[11:34] <Q-FUNK> I can only upload to main for one package, so I cannot act upon these myself.
[11:36] <Laney> seb128: ^^^
[11:38] <seb128> Laney, thanks
[11:52] <kenvandine> cjwatson, doko_ did it fo me last night
[11:52] <kenvandine> s/fo/for
[11:54] <mbiebl> superm1: hi
[11:54] <mbiebl> superm1: you wrote the upstart job for mysql?
[11:58] <mbiebl> looks like there is a race condition on shutdown
[11:58] <mbiebl> mysql.conf has stop on runlevel [016]
[11:59] <mbiebl> I have /var/lib/mysql on a separate partition
[12:01] <mbiebl> and the rc.conf job is basically run at the same time on shutdown as the mysql.conf job
[12:01] <mbiebl> as shutting down mysql takes quite a bit of time here, the umount scripts try to unmount /var/lib/mysql before mysqld is down
[12:01] <mbiebl> that leads to a correupted fs on every boot
[12:02] <mbiebl> superm1: want a bug report for that?
[12:04] <mbiebl> seems other jobs have the very same problem (dbus, rsyslog) but probably nobody noticed because stopping those jobs should be rather quick
[12:14] <mbiebl> So I'd say it is a general problem of using "stop on runlevel [016]" because it is not race-free
[12:54] <sladen> rickspencer3:
[13:09] <didrocks> jdstrand: hey, can you binary new unity-common please?
[13:10] <doko> james_w: how do I make sure that I get the unmodified upstream tarball for merge requests? e.g. #685180
[13:17] <jdstrand> didrocks: hey, sure
[13:17] <didrocks> jdstrand: thanks :)
[13:24] <jdstrand> didrocks: done
[13:24] <jdstrand> didrocks: fyi, only i386 was needed, the other three were already accepted
[13:25] <pitti> jdstrand: (it's presumably an arch-all package, and thus only gets built on i386)
[13:25] <didrocks> jdstrand: it's arch:all, hence only i386 :)
[13:25] <jdstrand> oh duh
[13:25] <jdstrand> that is precisely it
[13:25] <didrocks> :)
[13:25]  * pitti ^5s didrocks
[13:26]  * didrocks ^5s pitti back
[13:26] <pitti> jdstrand: thanks
[13:26] <didrocks> jdstrand: thanks a bunch ;) you will make a lot of user happy with intellihide available now :)
[13:26] <jdstrand> nice!
[13:28] <fbond> c
[13:29] <pitti> didrocks: no more fiddling in ccsm to get rid of it? indeed!
[13:30] <didrocks> pitti: it's not the default yet, will be next week normally. You still have to enable autohide :)
[13:31] <didrocks> (autohide is now "intellihide" even if the name of the option is the same)
[13:31] <pitti> didrocks: a day, a week, doesn't matter; I'm just happy to see the feature
[13:31] <didrocks> :)
[13:31] <didrocks> I recommend particularly the new effect on minimize now, with the launcher visible
[13:32] <pitti> didrocks: in classic gnome my screen "overhead" is just the top panel right now; with that, we're getting back to that state
[13:32] <didrocks> pitti: exactly
[13:36] <udienz> hello ubuntu-devel
[13:36] <udienz> i have merge proposed
[13:37] <udienz> https://code.launchpad.net/~udienz/ubuntu-docs/natty-ubuntu-docs.fix677998/+merge/42857
[13:37] <udienz> fixing #42857
[13:37] <udienz> bug 42857
[13:39] <udienz> and here https://code.launchpad.net/~udienz/ubuntu/natty/aspell-en/aspell-en.fix687483/+merge/43124
[13:39] <udienz> my pleasure if you want to reviewing it
[13:41] <Daviey> doko: I don't suppose you have thoughts on bug #688522?  It's pretty urgent, that one :/
[13:41] <Daviey> doko: I wondered if we need something similar to http://icedtea.classpath.org/hg/release/icedtea6-1.8/file/eab926d1eb04/patches/openjdk/6650759-missing_inference.patch
[13:53] <G__81> is there a separate channel for unity where in i could submit patches etc to unity ?
[13:54] <beuno> G__81, try #ayatana
[13:54] <G__81> ok
[13:58] <cjwatson> Riddell: why did you merge the patch in bug 686607?  I already followed up to the merge review asking for it to be sent upstream instead, and wanted to wait for a response there.
[13:58] <cjwatson> not happy about that, really
[13:59] <cjwatson> it's a low-priority bug, we don't need to rush on it
[14:01] <Riddell> cjwatson: oh sorry, I saw that it had been submitted upstream and thought that would satisfy your request
[14:02] <cjwatson> as I said in the merge request, I'm generally trying to reduce the number of distribution-specific patches we carry.  openssh upstream often doesn't accept patches anything like verbatim
[14:03] <cjwatson> and if they don't accept it I have the choice between carrying the patch forever, or regressing, either of which is worse than not applying the patch to start with
[14:06] <cjwatson> doko: taking bug 687488
[14:08] <james_w> pitti, because linaro has blueprints spread over multiple projects, and we would like to track them together
[14:08] <pitti> james_w: I updated the merge proposal with some details
[14:08] <james_w> thanks
[14:10] <james_w> pitti, which merge proposal? I don't see your comments on either of mine
[14:12] <james_w> oh, found it
[14:12] <pitti> james_w:
[14:12] <pitti> https://code.launchpad.net/~james-w/launchpad-work-items-tracker/multi-project/+merge/43221
[14:15] <doko> cjwatson: thanks
[14:20] <james_w> doko, if you do a "bzr builddeb -S" in that branch, you can compare the checksum in the .dsc with the upstream one
[14:23] <doko> lamont, cjwatson: we need an update of the chroots. every build still has python2.6-minimal installed, which lets builds fail ...
[14:23] <doko> james_w: thanks
[14:24] <lamont> doko: awesome
[14:24] <lamont> doko: so I assume you'd like that "now"?
[14:24] <doko> :-) well, it's just failing builds
[14:25] <doko> lamont: does python2.6-minimal need the priority changed for that (still required)?
[14:27] <lamont> I'll tell you in a few min
[14:29] <lamont> doko: shure looks like debootstrap grabs required and base..., and it defintitely grabbed python2.6-minimal
[14:29] <lamont> so... fix that and poke me when it's clear?
[14:29] <doko> ok
[14:30] <cjwatson> also python2.6 -> standard
[14:30] <cjwatson> and python2.7-minimal -> required, python2.7 -> important
[14:30]  * lamont wanders off for a few
[14:30] <doko> standard? not optional?
[14:30] <cjwatson> http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt
[14:30] <cjwatson> except that much of that should be ignored due to the temporary python2.6-dev dependency
[14:31] <cjwatson> I assume something in standard still wants python2.6.  it'll drop out once the rebuilds complete, probably
[14:34] <lamont> The following packages will be REMOVED:
[14:34] <lamont>   python2.6-minimal
[14:34] <lamont> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
[14:34] <lamont> cjwatson: ^^
[14:34] <cjwatson> ack
[14:34] <chrisccoulson> does anyone have any idea why this link fails: http://paste.ubuntu.com/541643/
[14:34] <chrisccoulson> i've tried pretty much everything i can think of now, and still can't get it to work :/
[15:07] <cr3> cjwatson: to follow up on yesterday, might you have a bug number for the mac_address feature request to d-i?
[15:07] <jcastro> mdz: do you have a method of updating the brainstorm ideas to point people to the answers?
[15:08] <jcastro> and also resolving the ideas when they've been reviewed?
[15:09] <cjwatson> cr3: bug 56679
[15:09] <mdz> jcastro: I don't; is that something you could help coordinate?
[15:10] <jcastro> I can do them all now.
[15:10] <mdz> jcastro: awesome, thanks
[15:11] <jcastro> mdz: I just update the status and add a link in the developer response area so I can just take that recurring WI
[15:17] <mdz> jcastro: cool, I'll mention that to the TB for future editions
[15:23] <ogra> pitti, i'm getting WI tracker spam like " [WARNING] milestone "natty-alpha-2" is unknown/invalid" same for ubuntu-11.04-beta and ubuntu-11.04 milestoned specs ... any idea why ?
[15:23] <pitti> ogra: please ignore, I fixed this this moring
[15:23] <ogra> ah, thanks
[15:31] <pitti> erm, bzr, where are thou? "ImportError: No module named bzrlib"
[15:31] <pitti> doesn't work with python2.6 either
[15:32] <pitti> but the package ships it for both versions, hmm
[15:36] <jdstrand> I've got a bit of an emergency security update I need to work on and my archive admin duties will be likely postponed (I typically focus on NEW). if anyone really needs something deNEWed today, feel free to ping me
[15:47] <cjwatson> doko: what's happening with bug 605042?  last comment from you was moving it to maverick-updates
[15:48] <cjwatson> mvo: what more is needed to close bug 671016?  just getting the new page written?
[15:49] <doko> cjwatson: I think this is still blocked on the kernel side. I don't know what I can do more than backing out this upstream change
[15:51] <cjwatson> bjf: could you please look at bug 605042?  see above
[15:57] <mvo> cjwatson: yes, the page is missing, a bit more testing and then it should be done.
[15:58] <bjf> cjwatson, afraid i've not done arm for a couple cycles now and have no HW
[15:59] <dvanstone> how do I add a disk that was solo to current boot options
[15:59] <cjwatson> bjf: who should be responsible for that bug?  it's assigned to canonical-kernel-team but nobody has taken responsibility
[15:59] <cjwatson> bjf: and it's blocking something that the foundations team is being asked about every release meeting
[16:00] <bjf> cjwatson, well, we lost our ARM devs to linaro, i'll send some email and see if I can get it on someones radar (will cc you)
[16:00] <cjwatson> thanks
[16:01] <cjwatson> given that this is the hardware that runs our buildds on the LTS release, we have to be able to support those kernels somehow
[16:06] <cjwatson> lamont: are the chroots updated now?
[16:07] <lamont> cjwatson: was in a meeting.  kicking things now
[16:14] <lamont> cjwatson: debootstrap --variant=buildd still gives python2.6-minimal in the resulting chroot
[16:15] <cjwatson> doko changed that I believe, maybe it hasn't finished publishing yet
[16:15] <cjwatson> that would be odd though
[16:15] <cjwatson> I've given it a kick
[16:15] <cjwatson> should be available in <1.5 hours
[16:16] <doko> was just published with the last publisher run. amd64, i386, powerpc, but not yet armel
[16:16] <cjwatson> /home/lp_archive/ubuntu/indices/override.natty.main:python2.6-minimal   required        python
[16:16] <cjwatson> disagrees
[16:16] <doko> cjwatson: does the overwrites file need patching?
[16:17] <cjwatson> I ran change-override.py
[16:17] <cjwatson> did you try to upload to fix that?
[16:17] <doko> http://launchpadlibrarian.net/60435630/buildlog_ubuntu-natty-i386.python2.6_2.6.6-6ubuntu4_BUILDING.txt.gz says optional:
[16:18] <cjwatson> uploading to change Priority has zero effect
[16:18] <cjwatson> Priority and Section are set in overrides
[16:18] <doko> no, didn't change anything there
[16:19] <lamont> bzr branch lp:~lamont/launchpad-buildd/chroot-scripts; sudo chroot-scripts/make-chroot.sh -d natty --lp  <-- should you care to duplicate
[16:20] <cjwatson> ok, well I've fixed it in the archive now
[16:20] <lamont> cjwatson: I assume we need a publisher run?
[16:21] <smoser> i thought htat i had seen a way to transparently cat a file that was compressed or uncompressed.
[16:22] <cjwatson> lamont: yes
[16:22] <smoser> ie, something like an option to zcat or something.
[16:22] <cjwatson> zcat will cat uncompressed files
[16:22] <smoser> $ zcat foo
[16:22] <smoser> gzip: foo: not in gzip format
[16:23] <cjwatson> hm, my mistake
[16:23] <smoser> ah. --force will do it
[16:23] <cjwatson> zcat -f, yes
[16:41] <tgardner> is there a known way to work around the python2.7-minimal install problem?
[16:48] <cjwatson> tgardner: what's the error message?
[16:48] <cjwatson> installed fine for me
[16:49] <cjwatson> bug 687524 I suppose
[16:49] <tgardner> cjwatson, I got caught by the archive being unbuildable earlier this week (I missed the memo). Now I consistently get:
[16:49] <tgardner> dpkg: error processing python2.7-minimal (--configure):
[16:49] <tgardner>  subprocess installed post-installation script returned error exit status 3
[16:49] <tgardner> No apport report written because the error message indicates its a followup error from a previous failure.
[16:49] <tgardner>  dpkg: dependency problems prevent configuration of python2.7:
[16:49] <tgardner>  python2.7 depends on python2.7-minimal (= 2.7.1-1); however:
[16:49] <cjwatson> (and bug 687658)
[16:49] <tgardner>   Package python2.7-minimal is not configured yet.
[16:49] <tgardner> dpkg: error processing python2.7 (--configure):
[16:50] <tgardner>  dependency problems - leaving unconfigured
[16:50] <cjwatson> the operative line from the bug reports is actually "E: pycompile:240: Requested versions are not installed", which is before the output you showed
[16:50] <cjwatson> but anyway
[16:50] <cjwatson> doko: ^- could you have a look at that please?
[16:51] <tgardner> cjwatson, yep 'E: pycompile:240: Requested versions are not installed'
[16:51] <doko> looking ...
[16:51] <cjwatson> in general anything from "dpkg: error processing ..." onwards is just like "make: error 1" - follow-on errors
[16:51] <tgardner> cjwatson, ack
[16:52] <doko> tgardner: which versions of python and python-minimal are installed?
[16:53] <tgardner> python-minimal                  2.6.6-2ubuntu1
[16:53] <tgardner> python2.6                       2.6.6-6ubuntu3
[16:54] <tgardner> python2.6-minimal               2.6.6-6ubuntu3
[16:55] <doko> tgardner: could you unpack python and python-minimal (2.7.1-*) and try again?
[16:55] <tgardner> doko, what do you mean 'unpack' ? apt-get install ?
[16:56] <doko> aptitude download python python-minimal, then dpkg --unpack these
[16:57] <doko> then dpkg --configure --pending
[16:57] <doko> looks like http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605356
[16:58] <lamont> cjwatson: guesses on eta to publisher being done?
[16:58] <doko> I should fix that in maverick-proposed
[17:00] <Riddell> @pilot out
[17:00] <cjwatson> lamont: 16:15 <cjwatson> should be available in <1.5 hours
[17:01] <cjwatson> lamont: it'll be the publisher run that's about to start
[17:03] <doko> tgardner: did that work?
[17:05] <tgardner> doko, no, but I might just be caught in some intermediate state. I can just reinstall this server...
[17:15] <cjwatson> soren: do you have an example case for bug 687584 to hand?
[17:29] <lamont> cjwatson: afk for a few hours, and then I'll get the chroots updated, will advise :(
[17:32] <cjwatson> ok, thanks
[17:35] <pitti> slangasek: ah, thanks for the clarification in bug 395281
[17:42] <pitti> sconklin: should I reject the linux-lts-backport-maverick upload sitting in the lucid-proposed queue? this was already copied from the PPA
[17:43] <pitti> sconklin: in fact, it's older (23.40, where 23.41 is in -proposed); rejecting, FYI
[17:44] <bdmurray> barry: is bug 688655 python2.7 related?
[17:50] <barry> bdmurray: it could be some dependent package is broken or different in 2.7.  doesn't strike me as immediately caused by 2.7, but i'll add the tag and take a look
[17:51] <doko> janimo: ping
[17:52] <janimo> doko: pong
[18:09] <smoser> ok. so i'm writing a utility that stuffs a MBR in front of a partition image.  failing 'splice' from the kernel, i basically have to write the MBR, then append the data from the source to the destination.
[18:09] <smoser> it appears dd with 'conv=sparse' never happened<EMAIL_ADDRESS>[18:10] <smoser> can anyone think of a way that i can keep the destination file sparse using utilities in ubuntu (ideally main)
[18:10] <smoser> basically i need something to open a file for append and copy sparsely from another.
[18:16] <slangasek> pitti: n/p - not sure what the explanation is for the currently reported behavior, though
[18:19] <sladen> smoser: suggestions are that cp /dev/fd/0 /dev/fd/1  or something
[18:20] <sladen> smoser: but I do really wish that they would accept the desire for conv=sparse
[18:20] <ebroder> sladen: You'd need some way to talk cp into opening /dev/fd/1 with O_APPEND
[18:21] <sladen> ebroder: I ended up writing a tool
[18:22] <sladen> ebroder: turned into this  http://blog.alex.org.uk/2010/12/02/copying-sparse-files/
[18:24] <smoser> sladen, i didn't realize you were involved in that.
[18:24] <smoser> i had talked to alex and he pointed me at it.
[18:27] <sladen> smoser: perhaps we should get that into the distribution now it's been released separately
[18:27] <sladen> smoser: it should already be packaged ;-)
[18:27] <smoser> sladen, right. thats definitely an option.
[18:47] <alexbligh> smoser: ok I was quietly betting you'd get no replies on alternatives, but did not anticipated sladen would point you back at the same thing :-)
[18:47] <smoser> entrapment!
[19:00] <cjwatson> smoser: is conv=notrunc not sufficient?  I wouldn't have thought that would have changed anything after the endpoint of the write?
[19:04] <smoser> cjwatson, conv=notrunc works, but if it reads 1G worth of zeros , it will (i assumed) write 1G worth of zeros
[19:04] <smoser> rather than seeking.
[19:07] <cjwatson> oh, I read your problem the wrong way round
[19:07] <cjwatson> thought you were overwriting data at the start, not inserting
[19:08] <cjwatson> is inserting really the right way to go about it?  perhaps reframe your design
[19:08] <cjwatson> after all the distance between the boot sector and the partition will not always be the same, probably
[19:09] <smoser> cjwatson, i'm probably messing this up badly. but http://paste.ubuntu.com/541997/ is what i have.
[19:09] <ScottK> cjwatson: Would you please rescore the gtkglextmm build (only affects powerpc) - I think that's the blocker on getting python-visual built.
[19:10] <smoser> i've got process in place that builds partition images, i want to be able to produce disk images from those, and have those disk images boot in a full virt env
[19:10] <ScottK> (which in turn blocks boosts1.40 removal)
[19:12] <ebroder> smoser: Does this need to work as not-root? If it can be root-only, will cp work if the destination is a block device? You could use kpartx to create a device-mapper object for the partition, and cp --sparse=always onto that
[19:13] <smoser> i just really dont want to be root.
[19:14] <ebroder> smoser: btw, you know about blockdev(8) for probing for things like the size of block devices?
[19:15] <smoser> ebroder, i'd seen it, but didn't worry to much at this point about block devicesa
[19:31] <cdbs> IS python-webkit working properly with python 2.7 ?
[19:32] <barry> cdbs: working, or building?
[19:32] <cdbs> barry: working
[19:32] <cdbs> I don't know about its build status
[19:32] <kirkland> cjwatson: hi...  i just did two preseeded installations of natty;  one on ext3 and the other on ext4
[19:33] <kirkland> cjwatson: the ext3 one took <6 minutes, the ext4 one took 12 minutes
[19:33] <cdbs> Since I am getting ImportError: AttributeError: 'module' object has no attribute 'WebView'
[19:33] <kirkland> cjwatson: what ever happened with that dpkg issue?
[19:33] <cdbs> barry: ^
[19:33] <kirkland> cjwatson: did we get that fixed?  or decided not to?
[19:34] <barry> cdbs: it's possible.  i haven't looked at it yet.  can you file a bug and tag it with python27?
[19:34] <barry> i can at least look
[19:34] <cdbs> barry: okay then
[19:35] <barry> cdbs: thanks
[19:35] <cjwatson> ScottK: done
[19:36] <cjwatson> kirkland: it's in progress.  dpkg has a --force-unsafe-io option now, and there are other changes in progress.  I'll adjust the installer before natty to use that
[19:36] <cjwatson> (or something similar)
[19:36] <cjwatson> kirkland: Debian is thoroughly on top of the issue at this point.
[19:37] <kirkland> cjwatson: okay thanks;  i'll set my preseeds to use ext3 for speed for now, and test ext4 once you get a fix committed
[19:38] <ScottK> Thanks for the rescore on gtkglextmm.
[19:39] <cdbs> barry: will file tomorror, thanks!
[19:41] <cjwatson> kirkland: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605009 in particular - finally got some proper attention from tytso, including a specific suggestion to use sync_file_range which will be implemented in the next dpkg release
[19:41] <cjwatson> kirkland: so I'm holding off doing anything with --force-unsafe-io in the installer until I see whether that makes a difference
[19:42] <kirkland> cjwatson: okay, thanks;  i'm now subscribe to that debian report
[19:42] <kirkland> cjwatson: i'll monitor it there;  please poke my if and when you specifically want my testing feedback
[19:49] <cjwatson> ok
[19:49] <cjwatson> kirkland: no need to tell me when it gets closed though, I'll get e-mailed
[19:49] <kirkland> cjwatson: ack
[19:50] <kirkland> cjwatson: somewhat related to that ...
 cjwatson: so i have a preseed with "d-i partman-lvm/confirm boolean true"
 cjwatson: but I'm being held at that question anyway
 cjwatson: any hints?
 cjwatson: full preseed at http://pastebin.com/ME2CDpnx
[19:52] <cjwatson> kirkland: I can help if and only if I see a DEBCONF_DEBUG=developer syslog
[19:53] <kirkland> cjwatson: okay, i'll get you one
[19:54] <kirkland> cjwatson: the only thing odd i see is that the root disk where the installation is taking place is registered as sdb (instead of sda) in the installer
[19:54] <kirkland> cjwatson: post install, it's sda in runtime
[19:54] <kirkland> cjwatson: and the installation proceeds just fine as sdb
[19:54] <cjwatson> anything that that breaks is a bug in its own right
[19:54] <kirkland> cjwatson: okay
[19:54] <kirkland> cjwatson: i can't find anything else odd going on there
[19:55] <kirkland> cjwatson: i'm working around this for now with:
[19:55] <kirkland> -       preseed_file.write("d-i partman-auto/method string lvm\n")
[19:55] <kirkland> +       preseed_file.write("d-i partman-auto/method string regular\n")
[19:55] <cjwatson> it's not worth speculating.  it's about a hundred times quicker to look at a debug log
[19:55] <kirkland> cjwatson: okay, i'll send another install through with that cmdline option
[20:01] <jono> hey all
[20:02] <jono> I have a USB keyring running natty, but persistence is not working, can anyone recommend how I fix it
[20:02] <jono> ?
[20:09] <kirkland> cjwatson: well darn;  not reproducing it today :-/  happened several times yesterday
[20:09] <kirkland> cjwatson: i'll keep the cmdline debug parameter on there though, and grab the syslog if it shows up again
[20:10] <d-kessel> barry: considering python 2.7/natty - what do you guess when it will be safe to upgrade packages?
[20:26] <barry> d-kessel: you can upgrade packages now.  which one in particular are you thinking about?
[20:29] <d-kessel> thanks. well all ~170 update manager tells me to
[20:33] <d-kessel> barry: thanks. well all ~170 update manager tells me to
[20:36] <barry> d-kessel: i've been updating my vms today and it seems okay to me
[20:37] <micahg> hi robbiew, do you have time for a PM?
[20:37] <robbiew> micahg: sure
[20:39] <d-kessel> barry: thx, I'll see what it does to my "real" netbook installation
[20:42] <ebroder> jono: Honestly, if you have a spare USB key, running usb-creator on one key, then using that to do an actual install onto another key is going to be a truer testing environment. It will also get testing for things like the text-free boot changes
[20:42] <ebroder> I think I saw some discussion about expanding testdrive to install onto a USB key, which would remove the need for the spare
[20:46] <ebroder> jono: In the mean time, can you start by pastebining the syslinux/syslinux.cfg file on the USB drive?
[20:46] <jono> ebroder, I just talked with ev about this
[20:46] <jono> I am not entirely sure what the issue is
[20:46] <jono> and I have just wiped the stick to install it another way
[20:47] <ebroder> jono: Ah, ok
[20:47] <jono> ev would you mind filing a bug for this?
[20:47] <jono> as you have the outputs I pasted
[20:47] <ev> jono: those all just show that it isn't a problem in usb-creator
[20:47] <jono> gotcha
[20:47] <ev> what we need is something with the issue to post a bug against casper with their /var/log/casper.log attached
[20:48] <ev> preferably with debug set on the kernel command line
[20:54] <d-kessel> barry: upgrading failed, it is running dpkg --configure -a now
[20:55] <barry> d-kessel: dang
[21:12] <Keybuk> The next time Lennart sarcastically suggests it only took him a year to write systemd, I'm going to reply that it only took me *two hours* to add socket activation to Upstart
[21:13] <ebroder> Oooh, looks like fun
[21:14] <Keybuk> https://code.launchpad.net/~scott/upstart/bridges
[21:14] <Keybuk> adds an upstart-socket-bridge binary
[21:15] <ebroder> Keybuk: Yeah, I was skimming that and the session-support branches
[21:15] <Keybuk> if you stick "start on socket PROTO=inet PORT=1234" in your job, the bridge makes a listening socket on port 1234 for you, and when it gets a connection, sends the event with the socket
[21:19] <ebroder> Keybuk: Uh, don't you need to deal with SOCK_DGRAM vs. SOCK_STREAM?
[21:19] <Keybuk> ebroder: sure, at some point :p
[21:19] <Keybuk> that'd be just adding an int type to the Socket structure
[21:20] <Keybuk> defaulting to SOCK_STREAM
[21:20] <Keybuk> then adding
[21:20] <ebroder> socket(2) talks about AF_INET being a "domain", not a protocol
[21:20] <Keybuk> SOCK=STreaM
[21:20] <Keybuk> SOCK=DGRAM
[21:20] <Keybuk> etc.
[21:20] <Keybuk> yeah, I think I picked up "proto" from inetd
[21:20] <ebroder> Sure, I agree it's easy, I'm just nitpicking your terminology before anybody commits to it
[21:20] <Keybuk> noted, shall check I'm using the right thing there
[21:23] <ebroder> Keybuk: What's the plan for dealing with "start on socket PROTO=unix PATH=/var/run/dbus/system_bus_socket" having an implicit dependency on /var/run being mounted? Do you force the developer to make that explicit by adding an " and local-filesystems" or whatever?
[21:23] <Keybuk> hmm
[21:23] <Keybuk> that'd need to be a depedency on the socket bridge for now
[21:23] <Keybuk> I think the best thing is just to have the socket bridge started on virtual-filesystems
[21:23] <Keybuk> so /var/run is always available for it
[21:24] <Keybuk> 0.10 handles this stuff rather better
[21:24] <Keybuk> but we wanted to have it in 0.6 for fun
[21:25] <ebroder> I'm not familiar with the changes for 0.10. I'm guessing it rolls mountall into upstart and gives upstart stronger filesystem awareness?
[21:25] <Keybuk> nah
[21:25] <Keybuk> but it does actually roll the socket listening into upstart itself
[21:25] <Keybuk> where this is using a bridge
[21:26] <ebroder> How does that help?
[21:26] <Keybuk> because then upstart knows when it should be listening on the socket and when it shouldn't
[21:26] <Keybuk> e.g.
[21:26] <Keybuk> while apache
[21:26] <Keybuk> listen inet 80
[21:26] <Keybuk> exec ...
[21:26] <Keybuk> says to only listen while apache is running
[21:26] <Keybuk> and to only exec on connection
[21:26] <ebroder> Oh, interesting
[21:26] <Keybuk> it's the whole "while" thing that helps
[21:27]  * ebroder nods
[22:06] <kirkland> jjohansen: hey, would you mind joining #ecryptfs on OFTC?
[22:13] <lamont> cjwatson: doko: building tarballs now
[22:40] <lamont> cjwatson / doko: new python2.6-minimal-free tarballs uploaded
[22:40] <lamont> have a nice day
[22:41] <doko> lamont: available for builds *now* ?
[22:49] <doko> lamont: yes, and hurray! seeing now different build failures ;p
[22:50] <lamont> doko: uploaded == what LP will serve to the buildds the next time they ask