[06:34] <jacobw> bad webpigeon
[06:41] <MartijnVdS> Azelphur: Gnome 15?
[06:42] <MartijnVdS> Azelphur: I thought it was only up to 3.x
[06:42] <MartijnVdS> Or are they using Chrome-style versions now
[06:48] <jacobw> if DEVELOPER_BORED { version++; }
[06:48] <jacobw> the german keyboard layout is a little unfriendly
[06:49] <jacobw> why is the / shift+7 and @ alt-gr+q ?!
[06:50] <MartijnVdS> jacobw: You can just set the layout to something you like more :)
[06:50] <MartijnVdS> jacobw: the pictures on the keys don't matter
[06:51] <jacobw> i'm making an effort to learn the german keyboard layout
[06:51] <MartijnVdS> DAS DEUTSCHE LAYOUT
[06:51] <jacobw> my keyboard is has a UK layout, i've purposefully changed it
[06:55] <jacobw> here's another thing, { is alt-gr+7 and } is alt-gr+0
[06:55] <dwatkins> The German kezboard lazout is easz to learn...
[06:55] <jacobw> not even consequetive keys!
[07:01] <jacobw> at least the € is alt-gr+e which actually makes sense
[07:10] <MartijnVdS> also AltGr+5 I think?
[07:20] <jacobw> ½
[07:21] <jacobw> alt-gr+4 on gb
[07:24]  * MartijnVdS uses US-Intl-Nodeadkeys
[07:24] <MartijnVdS> Most keyboards in NL have US layout instead of NL layout
[07:26] <jacobw> being in vim and not being able to find ':' is the most distressing ting
[07:27] <MartijnVdS> at least ESC is in the same palce
[07:27] <jacobw> when i tried to learn dvorak, the vim problem sapped my motivation
[07:41] <czajkowski> https://tbe.taleo.net/NA3/ats/careers/requisition.jsp?org=CANONICAL&cws=1&rid=502  if anyone is job hunting we have 4 soft eng roles open on my team
[07:48] <dwatkins> We have 4 support roles if anyone in Edinburgh is looking for a technical role.
[07:58] <MooDoo> hello all
[08:00] <jacobw> hey MonsterKiller
[08:01] <jacobw> MooDoo even
[08:01] <MooDoo> lol
[08:02] <AlanBell> morning all
[08:02] <AlanBell> Wolverhampton on the telly
[08:03] <popey> morning
[08:04] <czajkowski> herro
[08:08] <MooDoo> AlanBell: olympic flame?
[08:10] <brobostigon> good morning everyone.
[08:10] <MooDoo> brobostigon: morning
[08:10] <brobostigon> morning MooDoo
[08:12] <MooDoo> another fab day of stuff in nottingham and i'm at work lol
[08:12] <brobostigon> :(
[08:13] <AlanBell> MooDoo: yeah Blue Peter live event and flame
[08:14] <jacobw> ah, flame
[08:15] <MooDoo> AlanBell: yeah saw it yesterday in Bakewell
[08:16]  * brobostigon has his own flame, he waves his lighter in the air.
[09:13] <MooDoo> what's everyone doing this weekend?  Anything exiting?
[09:13] <brobostigon> no plan as of yet.
[09:15] <MartijnVdS> Replacing a Win 98 machine for moneys :)
[09:17] <MartijnVdS> We've guesstimated (based on the CPU) that the machine is really 14 years old
[10:47] <popey> quiet day today
[10:47] <Seeker`> ssssshhhhhhhhhh
[10:48] <Seeker`> how are you?
[10:48] <popey> fine thanks :)
[10:50] <MooDoo> it's just started raining up here :S
[11:40] <popey> bigcalm, happy birthday ! :D
[12:27] <mattt> HAAAAAAI
[12:47] <christel> happy bigcalm day!
[13:14] <Joeboy> Hi. Anybody here able to help me with a packaging proglem? Trying to rebuild gdb-msp430 and (I think) it's failing at patching the source. See
[13:14] <Joeboy> http://pastebin.com/c6FjSFrm
[13:15] <ali1234> why you use debuild?
[13:15] <Joeboy> Is that not right?
[13:15] <ali1234> use fakeroot dpkg-buildpackage
[13:15] <ali1234> this never failed for me
[13:15] <Joeboy> Because I don't really know what I'm doing :-)
[13:15] <ali1234> not the first time anyway
[13:15] <ali1234> sometimes packages are broken and will only build once, then you have to delete the source to build it again
[13:16] <Joeboy> Yeah, just doing that
[13:16] <ali1234> if you find a package like that do report it as a bug
[13:16] <ali1234> it probably won't get fixed, but it is still a bug
[13:16] <Joeboy> I'm  bit unconfident about reporting build bugs as I suspect they'll mostly be pebcak errors, until I know what I'm doing a bit better
[13:17] <Joeboy> ali1234: That gives me exactly the same error as in the paste ^
[13:18] <ali1234> ok, is it the second build?
[13:18] <Joeboy> Well, not exaclty, but very similar
[13:18] <ali1234> dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting.
[13:18] <Joeboy> aha
[13:18] <ali1234> dpkg-checkbuilddeps: Unmet build dependencies: gdb-source (>= 7.2)
[13:18] <Joeboy> sorry, I suck
[13:18] <ali1234> sudo apt-get build-dep
[13:20] <ali1234> oh wait you did that
[13:20] <Joeboy> Yeah, I did
[13:21] <Joeboy> Just did it again, gratuitously, and unsurprisingly it didn't help
[13:21] <ali1234> ok lemme try to build this
[13:22] <Joeboy> Thanks
[13:22] <Joeboy> Just to warn you... if I manage to build it at all I'm going to be trying to patch it next
[13:22] <directhex> ali1234 is correct, the "clean" rule should always return a source tree to pristine state
[13:22] <directhex> often won't but should
[13:22] <Joeboy> For the moment I'm just going to go with rm -rf
[13:23] <Joeboy> cos I trust it
[13:24] <Joeboy> I'm running 12.04, btw
[13:24] <ali1234> ok it failed here
[13:24] <Joeboy> w00t
[13:24] <ali1234> same error, patches fail to apply
[13:24] <Joeboy> Is that a but I could legitimately report then?
[13:25] <ali1234> yes
[13:25] <Joeboy> s/but/bug/
[13:25] <Joeboy> Cool
[13:25] <Joeboy> Thanks
[13:25] <Joeboy> Glad it's not just me :-)
[13:25] <ali1234> msp430 is the TI low power chip, right?
[13:25] <Joeboy> Yeah
[13:26] <Joeboy> There's a popular dev board for it (launchpad)
[13:26] <Joeboy> Kinda like an even lower end arduino
[13:26] <ali1234> bug is already reported
[13:26] <ali1234> bug 935098
[13:27] <Joeboy> Thanks
[13:27] <ali1234> FTBFS = fail to build from source
[13:28] <ali1234> there's an upstream fix
[13:29] <Joeboy> Does "fix releaased" mean there's a package, or just a commit on github somewhere?
[13:29] <ali1234> in this case it means it's fixed in debian
[13:29] <Joeboy> Cool
[13:29] <Joeboy> Hi Hornet
[13:29] <ali1234> that likely means it will be fixed in quantal when the newer packages are imported
[13:30] <Joeboy> Cool. So, if I wanted to get this working nowish... what would you do if you were me?
[13:30] <ali1234> you need to regenerate those patches
[13:31] <ali1234> actually there is only 1 patch
[13:34] <Joeboy> Thanks for all your help ali1234
[13:35] <ali1234> ok
[13:35] <ali1234> this should fix it
[13:35] <ali1234> edit gdb/sim/configure
[13:36] <ali1234> search for "microblaze"
[13:37] <Joeboy> ...add msp430 ?
[13:37] <ali1234> no
[13:37] <Joeboy> k
[13:37] <ali1234> delete the line that says r178
[13:37] <Joeboy> k
[13:38] <ali1234> the patch will add msp430 but the patch expects that r178 line to not be there
[13:38] <ali1234> so it fails
[13:38] <ali1234> you could also do the reverse and add r178 to the patch but editing patches is harder
[13:39] <Joeboy> It still fails after doing that
[13:39] <ali1234> yeah
[13:39] <ali1234> is it unpacking something?
[13:40] <ali1234> it must be runing autotools to generate configure before patching
[13:40] <Joeboy> There's a tar xjf /usr/src/gdb*.tar.bz2 in the output
[13:41] <ali1234> so there is
[13:41] <ali1234> ok, let's fix the patch, that can't fail
[13:41] <Laney> ag
[13:41] <Laney> my glorious sunny day turned rainy
[13:42] <Joeboy> Laney: We got tempestuous rain here a while ago, but only for about 10 minutes
[13:42] <ali1234> so open msp430-gdb-7.2-20110103.patch and find the line from configure, with microblaze
[13:42] <Joeboy> I'm there
[13:43] <Laney> Joeboy: i'm holed up in a coffee shop in shorts + tshirt
[13:43] <Laney> with 5 miles to bike home
[13:43] <Laney> better stop!
[13:43] <ali1234> after "+msp430" and a line with " r178" (note leading space)
[13:43] <ali1234> now dpkg-source fails because we edited that patch
[13:45] <ali1234> commit that with dpkg-source --commit
[13:45] <ali1234> and it still fails
[13:45] <Joeboy> ali1234: This is the most awesome free tech support ever
[13:48] <ali1234> unbelievable it still fails
[13:49] <ali1234> i recommend you just build this stuff manually and do not use the packaging
[13:49] <Joeboy> :-)
[13:50] <ali1234> this whole "untar gdb source from /usr/src and then patch it using one giant patch"
[13:50] <Joeboy> Thanks again for your efforts
[13:50] <ali1234> it's going to make it unworkable if you try to add more changes
[13:50] <ali1234> you should untar gdb somewhere, initialize it as a git repo, apply the linaro msp430 patch, fix the rejects by hand (easy), and then make whatever changes you need and install it to /usr/local
[13:54] <Joeboy> Ok, I just installed the debian package. No obvious ill-effects so far.
[13:54] <ali1234> yeah... you won't be able to patch it though :)
[13:54] <ali1234> not easily anyway
[13:55] <Joeboy> It doesn't seem to have the bug the ubuntu package did though
[13:55] <Joeboy> so it's all good :-)
[15:01] <ggg4444> can someone help me with my void 11 problem?
[17:04] <gord> i think webpigeon* may be having troubles ;)
[17:04] <brobostigon> agreed.
[18:35] <Prisoftware> hello
[20:20]  * penguin42 wonders is anything won't survive tonights leapsecond
[20:30] <Azelphur> MartijnVdS: "gnome15" rather than gnome version 15
[20:30] <Azelphur> MartijnVdS: http://gnome15.org
[21:09] <ball> Is it difficult to have an Ubuntu (in my case Xubuntu) host join a Windows Workgroup?   I want to share my printer.
[21:13] <directhex> ball: workgroup? no.
[21:13] <ball> directhex: What's the secret incantation? ;-)
[21:15] <directhex> ball: install samba, and i think you can set the workgroup name via  agui (if not it's a 1-line setting in smb.conf)
[21:16] <ball> directhex: Thanks, I have a Samba book at home so I'll grep that when I get home.


[00:05] <cjwatson> stokachu: are you planning to get the fix for bug 1169740 into raring, as well as SRU?
[00:11] <nemo> oh. one more thing for you guys. I think this UEFI nonsense is going to be a big stumbling block
[00:11] <nemo> there's no way around it anymore
[00:11] <nemo> so, some clearer guides, online and in installer, on what to do, would be nice
[00:12] <cjwatson> we've put a great deal of effort into UEFI already; it would be best if you could file bugs about specific things you feel are missing, rather than a general comment ...
[00:12] <nemo> cjwatson: heh. was just typing something longer :)
[00:12] <nemo> cjwatson: but. specifically, the installer was aware Windows 8 was there
[00:13] <cjwatson> (also, distinguish plain UEFI from UEFI Secure Boot, as the issues are quite different)
[00:13] <nemo> but did not warn me I was not in EFI mode
[00:13] <cjwatson> hey, I'm not going to try to understand anything UEFI-related at 1am local
[00:13] <nemo> only my own paranoia made me halt before blowing away existing setup
[00:13] <cjwatson> that's why I suggested filing bugs :)
[00:13] <nemo> also. none of the docs explain how to get to EFI boot from Windows 8 - which was what I had to do. BIOS failed horribly in this regard
[00:14] <cjwatson> (I'll have forgotten this conversation by the morning ...)
[00:14] <nemo> oh well
[00:14] <cjwatson> these are useful comments and I heartily encourage you to file them as bugs so they don't get lost
[00:18] <nemo> Oh. Also, getting this information to someone who is in Windows 8 and just plugged in USB drive or CD. 'cause booting straight off it sure didn't work.
[00:18] <nemo> relative to where they are at that moment.  that's similar to (2) I guess
[00:18] <nemo> And. Man, is it hard to get into the BIOS screen on one of these fast-booting UEFI setups these days :(
[00:18] <cjwatson> Booting to UEFI from USB is certainly meant to work, and has in the past
[00:19] <nemo> cjwatson: well. Depends on BIOS setup possibly
[00:19] <cjwatson> Perhaps
[00:19] <cjwatson> Lots of room for intersection of our bugs and firmware bugs
[00:19] <nemo> thise was a lenovo g780
[00:19] <cjwatson> No idea about the specifics of that
[00:19] <nemo> when I finally got into BIOS screen there were options for boot order. I made sure USB was on top
[00:19] <nemo> there was also, under UEFI, windows boot loader and some USB boot loader
[00:20] <nemo> I put the USB one on top.  Unfortunately, that still sent me straight to windows.
[00:20]  * cjwatson -> overdue sleep
[00:20] <nemo> When I went to bios, the boot sequence was right, but windows was back on top
[00:20] <nemo> setting boot to USB from the windows 8 options was the only way to get it to work
[00:20] <nemo> well. actually legacy mode worked too, but that's how I got to a point in the installer that would have completely screwed everything up
[00:21] <nemo> oh well. g'nite
[00:37] <stokachu> cjwatson: i have debdiffs ready for precise, quantal and raring
[00:37] <stokachu> cjwatson: do you want me to attach raring, quantal? i was waiting on the OP to return with his testing
[00:37] <stokachu> and i see he updated
[00:54] <stokachu> cjwatson: if you see this and im not here i went ahead and filled out most of the SRU, waiting on OP to send me his test case and ill submit it up
[00:56] <stokachu> cjwatson: and to answer your original question (sorry its late) precise is my main concern as raring can be after release
[03:53] <pitti> Good morning
[04:33] <tjaalton> doko_: pong
[06:42] <dholbach> good morning
[07:41] <ev> apw: interestingly, we've only ever received 23 KernelOops reports with an OopsText field in them.
[07:41] <ev> It doesn't include 12.04, which doesn't have the version of whoopsie that sends the OopsText field, but I wonder if we're failing to correctly process these crashes at an earlier stage.
[08:06] <ev> apw: http://paste.ubuntu.com/5718063/ - you can look those up individually by going to https://errors.ubuntu.com/oops/$the_oops_id
[08:15] <apw> ev, indeed they mostly look reasonable, a couple seem truncated to the left ... and 23, i have had more than 23 this cycle i would think
[08:15] <ev> apw: truncated to the left?
[08:15] <apw> ('d4ae7486-568d-11e2-a835-2c768aafd08c', OrderedDict([(u'OopsText', u'ence at 00000004\nIP
[08:16] <ev> and yeah, I have no doubt that we're missing a lot, but I'm not sure why. The daisy.ubuntu.com frontend is very liberal in the reports it'll insert into the database.
[08:16] <ev> oh interesting
[08:16] <apw> i don't know of any bugs or oopses which start that way
[08:16] <ev> right
[08:16] <apw> in fact i think they probabally all start bug or oops
[08:16] <ev> so I'm wondering if this is some corner case in apport / whoopsie. (why we have so few)
[08:16] <ev> right
[08:17] <apw> you should be able to trigger them i think, isn't there a sysrq for that
[08:20] <apw> no it always forces a complete reboot.  we could so with a mechanism in our kernel to allow you to trigger them for testing me thinks
[08:20] <StevenK> apw: I think there is a magic sysrq for it, but I can't remember what it is either.
[08:21] <apw> StevenK, sadly it sets panic_on_oops before it oopses, which is a hard fatal reboot jobbie
[08:21] <apw> i cannot sensibly find one to trigger them quietly
[08:21] <StevenK> That isn't playing fair
[08:29] <doko> tjaalton, any reason not to merge the JITEmitter.patch in llvm-3.2?
[08:32] <tjaalton> doko: is it from debian?
[08:32] <doko> tjaalton, yes
[08:35] <tjaalton> doko: hmm can't find it on 3.2-4?
[08:36] <doko> tjaalton, because it's in -5?
[08:36] <tjaalton> ah
[08:37] <tjaalton> packages.d.o is lagging behind..
[08:37] <doko> tjaalton, or #1160587. note that Sylvestre mostly complains about stuff not being in Debian, but he's not caring much for the other way around :-/
[08:38] <tjaalton> right..
[08:39] <tjaalton> I guess it's fine
[08:39] <tjaalton> doko: are you merging it with -5?
[08:39] <tjaalton> getting the r600 updates would be nice too
[08:40] <tjaalton> although we didn't get radeonsi support included in raring, glamor-egl isn't uploaded yet and I doubt it would make it in main on such short notice :/
[08:40] <tjaalton> then a couple of commits to x-x-v-radeon to use these
[08:45] <doko> tjaalton, well, I can apply the jitemitter patch
[09:08] <tjaalton> tkamppeter: did you pull the whole touch-grab branch from whot, or just that one commit?
[09:09] <tjaalton> tkamppeter: I can still crash it easily by changing between the dash icon and indicator menus
[09:17] <tkamppeter> tjaalton, I only picked that one commit.
[09:19] <tjaalton> ok
[09:19] <tkamppeter> tjaalton, what sequence of finger clicks I have to do exactly? I clicked the dash icon (Ubuntu symbol at the upper left) and after that one of the indicator icons (Network Manager) and again the dash icon and nothing crashed for me (on the Lenovo Thinkpad Twist).
[09:19] <tjaalton> tkamppeter: doing that a few times crashes it here with the branch
[09:19] <tjaalton> i'll try without
[09:36] <doko> tjaalton, llvm-3.2 waiting in the queue
[09:36] <didrocks> diwic: I'm seeing quite some people complaining about pulseaudio taking 99% of their CPU since last update. I wonder if inotify doesn't go crazy if /run isn't there or something is tweaked. Heard about it?
[09:37] <diwic> didrocks, no, not yet
[09:37] <tkamppeter> tjaalton, I cannot reproduce the crash, I tried on both the Nexus 7 and the Thinkpad Twist.
[09:37] <diwic> didrocks, do you have a bug or person affected that I can work with?
[09:38] <seb128> diwic, seems like ricotz has it
[09:38] <seb128> ricotz, ^
[09:38] <didrocks> diwic: do you speak french? ;) (a lot of people on the unstable part of the french forum are complaining, so not just one isolated case)
[09:38] <didrocks> diwic: I can get them opening a bug report, is there anything I should add in addition to what ubuntu-bug will bring to them?
[09:39] <didrocks> if ricotz can do live debugging, that's even better
[09:39] <didrocks> ricotz: diwic: FYI, people report that if they kill pulseaudio in their session, then it works fine
[09:39] <tjaalton> tkamppeter: i'm building with your patch now
[09:39] <didrocks> I wonder if it's a race before /run is set for the user or anothing…
[09:39] <diwic> didrocks, I guess attaching to the process and seeing where it's stuck would be the first thing
[09:40] <didrocks> diwic: yeah, they are not *that* technical :p
[09:40] <ricotz> didrocks, diwic, i killed pulseaudio several times and it constantly uses 100% of one cpu again
[09:40] <didrocks> ricotz: ah, at least, it's more reliable for you, mind helping diwic? ^
[09:41] <diwic> ricotz, can you attach to it with gdb?
[09:41] <ricotz> didrocks, already downgraded :\, to be able to use my laptop
[09:41] <tkamppeter> tjaalton, you do not need to build. For Intel I have packages on my PPA and for Nexus 7 there is the tarball attached to the bug. To try without patch, go back to the official packages.
[09:41] <ricotz> diwic, i will give it a try in a moment
[09:42] <tjaalton> tkamppeter: building already
[09:42] <diwic> ricotz, or run sysprof on it could work too, if that easier
[09:42] <ricotz> diwic, although i am running an older kernel here
[09:44] <darkxst> I am not seeing the cpu issue, but why would pulseaudio be using 3GB of ram ....
[09:50] <ricotz> diwic, http://paste.debian.net/plain/250235
[09:51] <diwic> ricotz, all threads appear sleeping in that post
[09:53] <ricotz> diwic, seems like attaching to it released the "loop"
[09:53] <diwic> ricotz, oh.
[09:53] <diwic> ricotz, maybe you can try sysprof instead? Have you used it?
[09:53] <tjaalton> tkamppeter: it's trivial to get the grab hang with it
[09:54] <tjaalton> tkamppeter: just hit the indicators with two fingers a few times
[09:54] <ricotz> diwic, not yet
[09:57] <tkamppeter> tjaalton, you mean, clicking two indicators at the same time?
[10:01] <ogra_> stgraber, i forwarded your mail to the ubuntu phone list
[10:04] <ricotz> diwic, http://people.ubuntu.com/~ricotz/pulseaudio/
[10:05] <ricotz> diwic, not sure how to interpret it
[10:05] <stgraber> ogra_: thanks. I guess I probably should subscribe to some of those lists...
[10:09] <diwic> ricotz, hmm, what does the screenshot look like?
[10:12] <ricotz> didrocks, http://people.ubuntu.com/~ricotz/pulseaudio/sysprof.png
[10:13] <didrocks> I think this is for diwic ^
[10:13] <ricotz> ah sorry
[10:16] <diwic> ricotz, hmm, I loaded your log in my sysprof. It seems to point at e1000e_poll_eerd_eewr_done, but isn't that some kind of network related thing?
[10:16] <ricotz> diwic, actually yes, does pulseaudio probe those for something
[10:17] <ricotz> like discovering bluetooth adapters
[10:17] <tjaalton> tkamppeter: no, but rapidly change between two or more indicators by tapping on them with two fingers
[10:17] <diwic> ricotz, you haven't mounted /run/user on a network drive or something?
[10:17] <ricotz> diwic, no
[10:20] <ricotz> diwic, maybe you missed some prerequisite for the cherry-picked patch
[10:21] <diwic> ricotz, I wrote the inotify patch yesterday myself
[10:21] <ricotz> diwic, ah i see, alright
[10:22] <ricotz> +-        valid_pid_file = TRUE;
[10:22] <ricotz> ++        valid_pid_file = true;
[10:23] <diwic> ricotz, yeah, I changed pa_bool_t to bool too
[10:26] <diwic> ricotz, argh, I don't get it. Why would adding an inotify watch cause the e1000 driver to eat cpu?
[10:28] <tkamppeter> tjaalton, https://blueprints.launchpad.net/ubuntu/+spec/client-1305-convertibles-and-touch-desktop
[10:31] <tkamppeter> mlankhorst, bryc: ^^
[10:31] <diwic> ricotz, if you do "sudo fuser -v /run/user/ricotz/pulse/pid" a few times, does anything show up?
[10:31] <tkamppeter> bryce, ^^
[10:31] <diwic> ricotz, (assuming your logged in user is "ricotz")
[10:34] <ricotz> diwic, nothing shows up
[10:35] <ricotz> diwic, /run/user/*/pulse/pid contains the correct pid
[10:35] <mlankhorst> tkamppeter: we're aware of the touch problem, if it was easy to fix, or even not that hard to fix by the upstream maintainer it would already have been fixed
[10:37] <diwic> ricotz, hah! I reproduced it here: If I edit the pid file manually (with gedit), PulseAudio starts taking up 100% CPU
[10:39] <diwic> ricotz, probably there is some software on your machine that accesses it in some way
[10:39] <mlankhorst> Anyway I have a fix for bug 1170074, it seems nobody tests on x86 these days but it would be unsurprising if x86 was completely broken for nouveau/radeon because of it. :s
[10:39] <diwic> ricotz, and that triggers the loop
[10:39] <ricotz> diwic, hmm, i see, running gdm/gnome-shell here
[10:41] <diwic> ricotz, anyway, if I can reproduce it here, I can hopefully come up with a fix too with some analysis
[10:41] <diwic> ricotz, thanks so far!
[10:42] <ricotz> diwic, yeah, touching the file triggers it too while running in gdb
[10:42] <ricotz> diwic, ok, yq
[10:42] <ricotz> yw
[11:03] <rbasak> jodh: seen the LWN article on upstart?
[11:03] <rbasak> (just FYI, in case you're interested)
[11:03] <jodh> rbasak: not yet :)
[11:32] <zyga> is there a way to select apt-proxy via ubiquity somehow?
[11:33] <xnox> zyga: i'm considering to seed squid-deb-proxy-client package to desktop CDs....
[11:53] <diwic> didrocks, ricotz, ok, I believe I have fixed it now. Since this is last minute, what precautions do you suggest I take before pressing the "upload" button?
[11:54] <ricotz> diwic, i guess you can put it in a ppa and let someone test it
[11:54] <diwic> ricotz, are you volunteering? :-)
[11:55] <diwic> ricotz, I don't know exactly when Final Freeze is, but some time today I believe
[11:55] <didrocks> diwic: is there any risk of things going worse?
[11:55] <ricotz> didrocks, ^
[11:55] <ricotz> diwic, just put the source package somewhere
[11:55] <didrocks> diwic: I can get some people testing from a ppa if you want
[12:00] <diwic> didrocks, ricotz uploaded to ppa:diwic/pulseaudio-testing
[12:02] <ricotz> diwic, alright
[12:03] <diwic> build starts in 2 hours
[12:04] <didrocks> pitti: can we have a small bump on https://launchpad.net/~diwic/+archive/pulseaudio-testing/+build/4501878?
[12:05] <didrocks> diwic: forum updated, they will install it once it's available, will keep you posted
[12:05] <diwic> didrocks, thanks, I'll go for lunch in the mean time
[12:05] <didrocks> diwic: enjoy, thanks! :)
[12:08] <pitti> didrocks: done, it's now next in line
[12:09] <didrocks> thanks pitti :)
[12:15] <diwic> didrocks, as for risks for things going worse, I guess the risks are 1) PA crashing or 2) bringing back the original bug (stale PA processes after logout/login)
[12:16] <didrocks> diwic: ok
[12:35] <ricotz> diwic, looks good, can't reproduce it so far
[12:43] <didrocks> diwic: one confirmation on the forum as well :)
[12:54] <Kalidarn> not sure if this is the place, i'm currently testing raring ringtail and have had some problems getting it to boot.
[12:55] <Kalidarn> while it is kubuntu (i think its actually pre to any distro stuff)
[12:55] <Pici> Kalidarn: #ubuntu+1 is probably a better place if you're looking for support/
[12:55] <Kalidarn> basically comes up with grub menu, and then when you select "Start Kubuntu" it says you need to load the kernel first.
[12:55] <Kalidarn> yeah i think it might be a bug actually.
[12:56] <Kalidarn> unfortunately the error doesn't really tell me that much, the media is fine, already checked that.
[12:57] <Kalidarn> the error i get is:
[12:57] <Kalidarn> error: failure reading sector 0x6d500 from `cd0'.
[12:57] <Kalidarn> error: you need to load the kernel first.
[12:57] <Kalidarn> i might actually try with standard ubuntu media not kubuntu to test that as well
[12:57] <Kalidarn> i think it probably affects all variants
[13:00] <diwic> didrocks, ricotz, ok, I'm uploading it now then
[13:00] <didrocks> diwic: \o/ thanks a lot :)
[13:01] <Kalidarn> Pici: would it be recommended to get the latest beta or current daily?
[13:01] <didrocks> diwic: 3 people confirmed on the forum now :)
[13:02] <cjwatson> you should certainly try a current daily, although I don't know how much difference it'll make
[13:02] <cjwatson> "you need to load the kernel first" is a consequent error and not the real cause - you should generally look at the first error not the last
[13:02] <diwic> didrocks, thanks for organising the testing!
[13:03] <didrocks> yw ;)
[13:03] <diwic> didrocks, uploaded, fingers crossed
[13:03] <didrocks> heh ;)
[13:03] <Kalidarn> yeah cjwatson i wonder why its failing to read that particular sector though :) the drive works fine and the media burnt fine hmm.
[13:03] <cjwatson> evidently the boot loader is having genuine trouble with one or the other
[13:04] <cjwatson> it tried asking the BIOS to read that sector three times, and it failed every time
[13:05] <cjwatson> it's a fairly straight INT 13h Function 42h, and I doubt that that was the first sector it tried to read, so my money would be on a drive and/or media failure that your tests didn't pick up, with a backup option of some problem in your BIOS
[13:05] <cjwatson> the error here is close enough to the firmware call that I don't think it's likely that this is our bug
[13:07] <Kalidarn> cjwatson: yeah that's rather odd because ive burnt it twice (two dvds) and the drive does work as other distros have no issue
[13:07] <Kalidarn> so ill try booting off a usb stick
[13:08] <cjwatson> Kalidarn: well, it could be that other distros just happen to miss the problematic bit, or maybe Linux tries harder to read it than your BIOS does and the other distros have no need to read that sector with raw firmware calls
[13:09] <cjwatson> Kalidarn: sadly, experiment does not actually rule out faulty drive/media
[13:09] <Kalidarn> this includes previous versions of kubuntu such as quantal or ubuntu so yeah
[13:09] <cjwatson> Kalidarn: sure, but it could depend on exact position of data on the disk
[13:09] <Kalidarn> ill try a different type of media entirely and see if it occurs, the debian wheezy bug (pre RC1) happened the same to me on both optical and usb drive
[13:10] <cjwatson> Kalidarn: drive cleaning kits are IME worth a shot as well, but yes, you probably stand a better chance with USB
[13:10] <Kalidarn> yeah, i doubt the drive has anything wrong with it. but i guess ill know soon enough
[13:10] <Kalidarn> it's just rather odd i only seem to be having that issue with raring ringtail
[13:12] <cjwatson> the boot loader code in question hasn't changed for a year or more (I did go and read it before replying to you).  Random chance can produce odd things sometimes
[13:12] <Kalidarn> i guess :) time for more experimentation! :D
[13:13] <cjwatson> the boot loader code *is* Ubuntu's responsibility, but I think in this case whatever the bug actually is is out of our hands
[13:13] <Kalidarn> i figured at that point it wouldn't matter what variant of buntu was being used.
[13:14] <dholbach> lool, ready?
[13:15] <cjwatson> Kalidarn: the boot loader code is identical, but the different flavours of Ubuntu might happen to have the kernel in a different position on the disk
[13:15] <cjwatson> which in this case could make a difference
[13:16] <lool> dholbach: eh was just joining #ubuntu-on-air and just moved the invite 5 mn earlier to make sure people join on time
[13:17] <Kalidarn> thanks for your time cjwatson.
[13:17] <dholbach> cool
[13:20] <stokachu> cjwatson: hey did you see my messages from last night? (not sure if you logged off to sleep by then)
[13:21] <cjwatson> Oh, I did but hadn't quite got round to them yet - I'll look shortly, thanks
[13:21] <stokachu> cjwatson: ok no problem just making sure they made it to you
[13:21] <cjwatson> stokachu: We're before final freeze (just), so I'd like to get the raring fix in if possible
[13:21] <cjwatson> Since it ought to be there before precise
[13:22] <stokachu> cjwatson: ah ok, ive got everything attaached to the bug and sru template done
[13:22] <stokachu> cjwatson: so not sure if you want to just pull that raring one in before freeze
[13:23] <cjwatson> Right, I see.  I will stare at it a bit
[13:41] <cjwatson> mlankhorst: http://paste.ubuntu.com/5718775/ is a rather bigger diff than the changelog suggests - is that intentional?
[13:41] <cjwatson> 14:37 <seb128> tjaalton, slangasek, Laney: the libgl1-mesa-dri update makes unity segfault on start in vms
[13:41] <cjwatson> mlankhorst: ^- and is it likely to fix that?
[13:44] <mlankhorst> are they i386 vms?
[13:44] <seb128> mlankhorst, yes
[13:44] <cjwatson> the one I tried was
[13:44] <mlankhorst> cjwatson: it was a result of a merge back to ubuntu branch from ubuntu+1, the patches that were dropped were already no longer applied.
[13:44] <mlankhorst> hm I think it might
[13:45] <mlankhorst> I have it on my ppa anyway
[13:45] <seb128> mlankhorst, do you have a deb handy ?
[13:45] <mlankhorst> https://launchpad.net/~mlankhorst/+archive/ppa?field.series_filter=raring
[13:46] <rbasak> Would it be worth sorting the rebuild failure reports in popcon order? I'm still struggling to prioritise what to look at.
[13:46] <Laney> popcon doesn't get updated any more
[13:46] <rbasak> :-(
[13:46] <rbasak> How about Debian popcon?
[13:47] <seb128> cjwatson, mlankhorst: libgl1-mesa-dri_9.1.1-0ubuntu3~ppa1_i386.deb from that ppa fixes it
[13:47] <mlankhorst> good
[13:47] <mlankhorst> and what I expected
[13:48] <seb128> mlankhorst, still a bit annoying that this slept through, we should have at least one people running unity under a vm on i386 and amd64 before upload
[13:48] <seb128> mlankhorst, thanks for the fix ;-)
[13:49] <mlankhorst> seb128: it was a case of conflicting symbols specifically for i386
[13:49] <seb128> mlankhorst, well, it means nobody tested on i386...
[13:49] <mlankhorst> and only happened specifically on nouveau < nvc0, or llvmpipe i386
[14:01] <freeflying> wonderding do we have latest kde ppa for 12.04?
[14:02] <freeflying> sorry, wrong channel
[14:04] <mitya57> freeflying: ppa:kubuntu-ppa/backports
[14:04] <freeflying> mitya57: thanks, typed in errors here, meant to ask in kubuntu-devel :)
[14:20] <Sweetsha1k> achiang: ping?
[14:21] <achiang> Sweetsha1k: hey, in a hangout-on-air now, but what's up?
[14:21] <slangasek> mlankhorst: so what's the plan for getting the fixed mesa uploaded?
[14:22] <mlankhorst> erm it's already been uploaded before everyone was panicking about it ?
[14:22] <mlankhorst> :P
[14:22] <mlankhorst> so I guess poking you until you accept it
[14:23] <mlankhorst> oh was already accepted 7 minutes ago
[14:23] <mlankhorst> no plans, then..
[14:23] <Laney> the plan is to kick back with a nice jug of sangria
[14:24] <mlankhorst> mmm I think I'll go biking
[14:24] <mlankhorst> while the weather is nice
[14:24] <Laney> so dutch
[14:24] <mlankhorst> and the storm hasn't calmed down yet
[14:48] <mitya57> running ReText under qt5 makes gnome-session crash... interesting
[14:49] <mitya57> s/gnome-session/Xorg/g, which is even more interesting
[15:19]  * mitya57 installs Xorg dbg symbols, fastens seat bells and tries again
[15:22] <bdmurray> slangasek: could you have a look at bug 1169621?
[15:23] <xnox> bdmurray: i can test it again. there have been updates to kernel and/or qemu as e.g. background is now colorful.
[15:26] <slangasek> bdmurray: that's been a problem for a couple of cycles, IIRC there was a change in the kernel that triggered this... it's not going to get fixed for r
[15:27] <bdmurray> slangasek: got it, thanks
[15:36] <mitya57> FWIW I've found the issue: it's bug 1005677, for which we have a patch only in Qt 4, not in Qt 5.
[15:55] <GunnarHj> cjwatson: ping?
[15:55] <cjwatson> GunnarHj: pong
[15:56] <GunnarHj> cjwatson: Hi Colin. I just posted a comment on bug 1160441. I do disagree on that change.
[15:57] <cjwatson> Sigh, "not discussed with you" != "without discussion"
[15:57] <GunnarHj> cjwatson: Ok, true, but...
[15:58] <cjwatson> I can't wait indefinitely for feedback about every change
[15:58] <cjwatson> You haven't actually refuted my point about LC_TIME being a conflation of language-dependent and language-independent data
[16:00] <cjwatson> glib and indicator-datetime notwithstanding, anything that does even just something as simple as ctime() will have day/month abbreviations from the wrong language
[16:00] <cjwatson> "wrong", anyway
[16:00] <GunnarHj> cjwatson: It's true, no doubt. But given that we won't change the fundamentals easily, such as splitting LC_TIME into two locale categories, we need to do our best to meet user expectations.
[16:00] <cjwatson> I think day/month from "wrong" language is more likely to break those expectations than other parts of the format
[16:02] <GunnarHj> cjwatson: Possibly. But the conflict typically gets visible in the calendar, and I have an idea - admittedly hackish - how to deal with that.
[16:02] <cjwatson> I really profoundly disagree with the notion of hacking around locale categories in individual applications
[16:03] <cjwatson> All it will do is introduce inconsistency among applications
[16:03] <cjwatson> psivaa: ^- since this was your bug
[16:03] <cjwatson> bdmurray: ^- and you were investigating it
[16:04] <cjwatson> If I revert this for raring, I'm not sure how anything will change in future releases; we will still have the fundamental issue of a conflated locale category
[16:06] <GunnarHj> cjwatson: Well, it's better IMO than doing nothing. At the same time I think that doing nothing is better than preventing the users from controlling the date and time format, which is what LC_TIME primarily is about.
[16:06] <cjwatson> I'm not preventing users from doing anything!
[16:07] <cjwatson> They can change the categories themselves if our guess (and it can be no better than a guess) was wrong
[16:07] <GunnarHj> cjwatson: Well, currently they will do so automatically if they use language-selector to set the region. So it's inconsistent.
[16:08] <cjwatson> If we start changing individual applications then we're just going to have a succession of bugs like the one psivaa reported; the system will get more complex as we add more and more and more manual workarounds
[16:08] <cjwatson> This is how things get to the point where nobody understands them
[16:08] <bdmurray> cjwatson: I believe the change makes sense
[16:08] <cjwatson> I agree that we have an inconsistency here
[16:08] <cjwatson> That's the only reason I'm considering reverting
[16:08] <cjwatson> If I reverted for raring, I haven't seen any reason yet why I wouldn't put the change back in the first upload for S
[16:09] <cjwatson> And I'm not at all convinced that I would consider that indicator-datetime change acceptable for raring
[16:10] <GunnarHj> cjwatson: At least it would give us a possibility to consider the issue more carefully.
[16:10] <cjwatson> Unfortunately we have already changed something from quantal, namely the mixed-locale improvements in ubiquity, and the handling of LC_TIME was one of them
[16:11] <cjwatson> So we don't get to say "let's just leave it how it was in quantal and consider more carefully later"
[16:12] <GunnarHj> cjwatson: But language-selector has considered LC_TIME a region thing for many, many cycles.
[16:12] <cjwatson> And we probably only didn't notice that was a problem because relatively few people set their language through language-selector rather than setting it once in the installer and leaving it there.
[16:12] <cjwatson> So it didn't come up in this kind of test.
[16:14] <GunnarHj> cjwatson: Those who distinguish between language and region have typically used language-selector, I think, considering that the installer only lately has made a similar distinction.
[16:14] <xnox> GunnarHj: i live in the uk, but on many machines want Russian UI, and that means my calendar should say Четверг and not Thursday. Just because my current timezone is here, doesn't magically make me understand that language.
[16:14] <cjwatson> Perhaps.  Some of them have probably set the locale categories manually ...
[16:14] <GunnarHj> cjwatson: That too.
[16:14] <xnox> GunnarHj: Or are you proposing that we print time in German, when the timezone is set to Berlin? even if the rest of the UI is French?!
[16:15] <cjwatson> xnox: Gunnar is proposing that we do the language parts of this at the application level, I believe
[16:16] <GunnarHj> https://code.launchpad.net/~gunnarhj/indicator-datetime/days-months/+merge/159214
[16:16] <cjwatson> Which I think is really dangerously wrong
[16:17] <cjwatson> For reasons given above
[16:17] <xnox> cjwatson: I mean the ultimate incornation of this bug is how currencies are displayed by default in Libreoffice calc. Cause when a Russian UI in the UK one would want £ currency & Четверг as name of the day.
[16:17] <cjwatson> No, don't drag currencies into this
[16:17] <cjwatson> Those are LC_MONETARY which is different
[16:18] <cjwatson> I don't believe anyone disagrees that LC_MONETARY should be location-dependent
[16:18] <cjwatson> And it is, with current installer and language-selector code
[16:18] <xnox> ok, good.
[16:20] <GunnarHj> cjwatson, xnox: Personally I think I won the debate at https://bugzilla.gnome.org/687945, but Matthias had access to the button...
[16:20] <cjwatson> GunnarHj: Exactly the same argument applies to glib as to applications - it's the wrong place, fixing this belongs at the standards / C library level
[16:21] <cjwatson> Which is certainly harder, but ...
[16:21] <GunnarHj> cjwatson: So the question is what's the best thing to do until the standards are changed.
[16:22] <xnox> GunnarHj: the questions is did you raise it for standards to consider fixing yet?
[16:22] <Kalidarn> cjwatson: works off USB ;)
[16:22] <cjwatson> Kalidarn: excellent
[16:22] <Kalidarn> i should try another cd drive actually.
[16:22] <Kalidarn> cos i don't believe the media is bad.
[16:23] <Kalidarn> i don't like problems that go away by themselves.
[16:23] <Kalidarn> (especially as two seperate discs had exactly the same issue)
[16:23] <Kalidarn> i wouldn't mind betting though cjwatson it's probably my dodgy BIOS
[16:24] <GunnarHj> cjwatson: I have discussed the issue quite a lot the past few months. Winows and Apple are said to fix the distinction in accordance with the users' expectation, i.e. despite of the standards.
[16:24] <Kalidarn> i've had nothing but trouble with this GA-X58A-UD3R
[16:25] <GunnarHj> xnox: No, I haven't. Isn't that a 'mission impossible'? ;-)
[16:26] <xnox> GunnarHj: i haven't pushed anything into C std library, but e.g. ubuntu community did push a few things into other standards and languages.
[16:26] <cjwatson> GunnarHj: I really don't see how Windows or Apple are relevant to a discussion of POSIX standards :-)
[16:27] <cjwatson> Sure, they're big OSes, but they're not exactly well-known for POSIX compliance in general
[16:27] <Kalidarn> isn't OSX more posix compliant than linux?
[16:28] <cjwatson> GunnarHj: If we don't try then *certainly* nothing will happen
[16:28] <xnox> GunnarHj: it's a valid problem, and needs a solution that works =) standards committees are suppose to be good at resolving such things, or at least defining/clarifying the expected when mixed LC_* locales are set.
[16:28] <xnox> s/expected/expected behaviour/
[16:28] <GunnarHj> cjwatson: Their success is probably partly because they set user expectation before bad standards.
[16:29] <cjwatson> GunnarHj: Sigh, I guess this discussion is useless if we're going there
[16:29] <cjwatson> False dichotomies 'r' us
[16:30] <GunnarHj> cjwatson: For now, can't you please take a step back and revert?
[16:30] <cjwatson> GunnarHj: I'll revert this change in the installer for raring, but only because it has additional interactions I hadn't thought of which are now too late for 13.04.  I intend to reinstate it as soon as raring is out.
[16:30] <cjwatson> Unless there is a better option, and I don't count application-level changes ...
[16:31] <GunnarHj> cjwatson: Good, then I can sleep well tonight, at least. ;-)
[16:31] <psivaa> cjwatson: sorry was still trying to understand the conflict and the inconsistency. i like the correct language to be displayed but if that's going to change the timezone, then i dont have a preferance :)
[16:31] <cjwatson> psivaa: It's not about changing the timezone
[16:32] <jtaylor> barry, doko: ubuntu python now has native access to the multiarch tuple right?
[16:32] <jtaylor> where was i again?
[16:32] <jtaylor> sys._multiarch is only py2 :/
[16:32] <doko> jtaylor, depends on what you want to use it for
[16:32] <jtaylor> to find tk/tcl
[16:33] <doko> if you can, use sysconfig.get_config_var('MULTIARCH')
[16:33] <jtaylor> ok seems to work, thx
[16:35] <psivaa> cjwatson: ok, I think its safe for me to leave the decision to you guys then :)
[16:35] <jtaylor> or is there a compat package one can use for tk/tcl build dependencies?
[16:36] <cjwatson> GunnarHj: Reverted. :-(  Now I really do have to go.
[16:37] <cjwatson> Oh blast, I have to wait until localechooser is approved before reuploading ubiquity.
[16:37] <cjwatson> So that will probably miss final freeze now.
[16:37] <nemo> Hrm. I wish ubuntu software centre offered a way for devs to get in contact w/ users who give bad reviews
[16:37] <GunnarHj> cjwatson: Thanks. :)
[16:37] <stgraber> cjwatson: I can review it now if you want
[16:37] <nemo> I mean. I don't *care* that much, I just feel sorry for poor "John" who was having trouble starting the game which was almost certainly due to bad gfx driver
[16:37] <nemo> and could probably have been fixed w/ application of jockey-gtk
[16:38] <nemo> and might be having bad exp w/ other games too
[16:38] <xnox> nemo: wrong channel =)
[16:38] <stgraber> cjwatson: accepted (confirmed that diff from ubuntu2 to ubuntu4 is only removal of .gitignore)
[16:38] <nemo> xnox: oh?
[16:39] <xnox> nemo: i'm not sure where you can discuss apps published in the software center. Wait is that about a review on a package from Ubuntu OS or about an app you published in Software Center as a developer?
[16:39] <nemo> Hedgewars. 2nd FOSS game in Games category :)
[16:40] <nemo> xnox: but. it wasn't really about the game itself
[16:40] <nemo> was more about ubuntu software centre - I wish it offered a way for me to somehow help john is all
[16:40] <nemo> every time I go to the game, his review is there, and I feel bad
[16:40] <xnox> nemo: hmmm...
[16:41] <nemo> I know what is happening. hwengine is crashing.  which is usually due to opengl probs, thus need for another driver. well, it sometimes is 'cause people screwed w/ sound system or pulseaudio is crashing
[16:41] <nemo> but john doesn't seem like the type to screw w/ sound system, and pulseaudio is better behaved these days
[16:42] <nemo> if john had linked to a launchpad issue, I would have commented there :)
[16:42] <nemo> but given cjwatson's complaints yesterday, I guess I shouldn't talk about filing issues :-p
[16:46] <stokachu> cjwatson: that version change you made in rsyslog was that the only thing I should be aware of? i couldnt find versioning schemes for development in the wiki anywhere
[16:47] <nemo> xnox: and. I can't just write another review rebutting him, since I already did that once for the guy who said we work better on windows machines :D :D
[16:47] <nemo> er. s/rebutting/replying/  - my first review was a rebuttal./
[16:49] <cjwatson> stokachu: Yeah
[16:49] <cjwatson> stokachu: dch -i usually does the right thing for development releases
[16:50] <stokachu> cjwatson: ah ok, yea it did do that but i manually altered it :X
[16:55] <sabdfl>  let me know which is the best image version to demo on N4 and N10?
[16:55] <sabdfl> gack
[20:27] <weasel> please excuse my intrusion, but does ubuntu/canonical have porting machines that give developers various chroots to interactively debug stuff?
[20:33] <roadmr> weasel: not to my knowledge :/ I may be wrong though...
[20:33] <weasel> what a shame.  I wondered how they were maintained :)
[20:34] <infinity> weasel: We do internally, yes.
[20:35] <weasel> ISTR elmo mentioning many years ago some tool that gives otherwise unprivileged developers the means to install packages from the archive in a reasonably secure way
[20:35] <weasel> but I can't find that email anywhere
[20:35] <infinity> weasel: chapt-get
[20:35] <infinity> Or, no.  What did I name that project?
[20:35] <infinity> Bah.
[20:35]  * infinity goes hunting.
[20:35] <weasel> hah
[20:36] <infinity> rapt.  That's it.
[20:36] <infinity> Failing old brain.
[20:36] <infinity> weasel: https://launchpad.net/rapt
[20:36] <weasel> not packages for debian.  what a shame
[20:36] <weasel> thanks
[20:36] <infinity> weasel: It ain't pretty.  Just a quickie hack by mvo and I over a few days/weeks.
[20:36] <infinity> weasel: But it basically does the job.
[20:37] <weasel> yeah, we're mostly worried about tty/stdin interaction during the install process
[20:37] <infinity> weasel: The idea is to install it as /usr/local/bin/apt-get and then provide sudo access to it.
[20:37] <weasel> or at least that was one obvious attack vector
[20:37] <infinity> Which is sketchy.
[20:37] <infinity> But less sketchy than giving someone apt-get raw.
[20:37] <infinity> Though, it might not meet your use-case.
[20:38] <infinity> Our use case was "we don't want people removing packages", basically.
[20:38] <infinity> Not so much about security as developers not stomping on each other.
[20:38] <weasel> hmm.  might not be a perfect fit then
[20:39] <weasel> not too different from the apt-in-chroot wrapper we already have for porters
[20:39] <infinity> Possibly not, no.
[20:39] <weasel> I'm just glancing over the code, but there's nothing stopping me from say installing a pager, apt-listchanges, and then execing a shell from the pager while apt-listchanges shows me stuff, right?
[20:40] <weasel> ah.  there's a pty.fork()
[20:40] <weasel> that's good
[20:41] <weasel> thanks
[20:51] <hallyn> infinity: bug 1170489 , does that suggest we should always have group admin in /etc/group?
[20:52] <stgraber> ubuntu@lxc-testing01:~$ grep admin /etc/group
[20:52] <stgraber> ubuntu@lxc-testing01:~$
[20:52] <stgraber> hallyn: ^ clean raring system
[20:53] <hallyn> right
[20:53] <stgraber> my guess is that you probably want to look at the sudo group instead
[20:53] <stgraber> assuming you want the list of people who are able to become root on a standard ubuntu system
[20:53] <hallyn> stgraber: the problem is the system may have been installed with lucid and upgraded
[20:54] <hallyn> so libvirt postinst does both groups admin and sudo
[20:54] <hallyn> (i originally switched to only sudo, but mdeslaur pointed out the problem with that)
[20:55] <stgraber> hallyn: hmm, then it depends what you want to get, if you just want the local users and ignore network sources, just parse /etc/group directly. If you don't care about network group membership but want to check that the group exists locally, then use grep -q + getent group
[20:55] <hallyn> was pinging infinity bc he originally did the switch from grep to getent, so he might have thought about it already and know of a reason why it's a non-issue
[20:56] <hallyn> i haven't used NIS since 1998 on an iris box...
[20:57] <hallyn> can't quite decide if, if you give yourself an NIS group called 'admin', how that's supposed to be handled
[20:58] <stgraber> ah, actually, I thought NSS would aggregate when the group is provided by more than one backend, but it's not, it just returns the first one, so if you have the group in /etc/group + NIS, it'll just return the members listed in /etc/group
[20:58] <hallyn> what if you list NIS before files?
[20:58] <hallyn> course, then, again, it's what you wanted...
[20:58] <stgraber> so if you want to fix what's described in this bug, you can get away with "grep -q admin /etc/group && getent group admin" (and same for sudo)
[20:59] <hallyn> but do i want to :)
[20:59] <stgraber> yeah, if you list NIS before files, then if the group exists in NIS only those members will be returned, even if you have some extra in /etc/group locally
[21:01] <infinity> hallyn: I'm puzzled as to what the bug is.
[21:01] <hallyn> so if you do have an nis group called admin, why shouldn't those users be added to group libvirtd?
[21:01] <infinity> hallyn: I've never seen someone complain before about NIS working exactly as advertised.
[21:02] <hallyn> that's bc it's been 15 years since anyone used it, working or not
[21:02] <stgraber> so usually people don't really like postinst scripts adding possibly hundreds of network users directly to the local /etc/group
[21:03] <stgraber> and I think that's what the reporter is complaining about
[21:03] <infinity> It's only a complain because it's an ambiguously vague group name.
[21:03] <hallyn> stgraber: but won't adduser use NIS to add the users to (NIS) group libvirtd
[21:03] <infinity> hallyn: It can, depending on how you've set it up.
[21:03] <infinity> By default though, no.
[21:03] <stgraber> if you have a company with a NIS (or LDAP or whatever) group called "admin" with users in there and don't have the group locally (because it's a clean raring system), then all those users will end up being hardcoded in /etc/group
[21:05] <stgraber> so yeah, I guess the grep + getent change would be reasonable. It won't cause any change for standard systems and for systems using network auth, it won't give extra rights to "random" users.
[21:06] <hallyn> well if we do want to undo this, i'd say falling back to 'grep "^admin:"' makes more sense than using both grep and getent
[21:06] <hallyn> IF we want to undo it
[21:32] <pedahzur> I am trying to use a latest mainline kernel to debug an issue.  The 3.9-rc6 has a linux-image-extra package, but 3.9-rc7 does not.  Has everything in the extra package been integrated into the main kernel package?
[22:24] <gotwig> Does anyone know something about GeoClue?
[22:24] <gotwig> its death, isnt it? No maintainer, no new code, no bug fixes for several months
[22:30] <gotwig> tvoss, hey there
[22:30] <tvoss> gotwig, about to leave :) how can I help, though?
[22:31] <gotwig> tvoss, hallo erstmal ;D
[22:31] <gotwig> tvoss, I saw your blueprint about geoclue2
[22:31] <gotwig> tvoss, do you work on it, or is it death²?
[22:31] <tvoss> gotwig, the blueprint itself is alive, geoclue2 as presented on the bp is quite unlikely at this point


[14:14] <rhpot1991> quick question guys, I'm looking to upgrade my EEE1000 to Jaunty, and hopefully switch to a lpia kernel in the process, I prefer the full desktop as opposed to NBR.  What is the best way for me to go about this, the lpia alternate installer cd?
[14:27] <persia> rhpot1991, probably, although I'd recommend i386 over lpia.
[14:27] <rhpot1991> persia: care to discuss why?
[14:28] <persia> Sure.
[14:28] <persia> Firstly, the lpia kernels didn't get quite as much testing, and some significant regressions from the merge into the main kernel tree were reported quite late in the cycle.
[14:28] <persia> Contrariwise, the i386 kernel got the most testing of any variety.
[14:29] <persia> So I would expect the i386 kernel to be more robust.
[14:29] <rhpot1991> hmmm thats unfortunate, I heard good things about running lpia on netbooks from someone who works for dell
[14:29] <persia> And last I looked, both kernels were i586+, so there oughtn't be significant i686 optimisation in the lpia kernel.
[14:30] <persia> Well, there's a bit of an improvement, sometimes.
[14:30] <persia> At one point, lpia was configured to be i686, so you saw the ~5% improvement you'd expect over the generic kernel.
[14:31] <persia> And at one point, some of the compilations were i686 optimised as well, which gave a bit more of an improvement.
[14:31] <rhpot1991> persia: currently I run the array.org kernel as that works OOB for all the hardware on this, any idea if the support should be there in the ubuntu kernel for Jaunty?
[14:31] <persia> Somewhere in the middle, people wanted to run lpia on the via C7M and similar chips, for instance the early Eee PCs.
[14:32] <persia> I'm not familiar with the array.org kernel.  I believe that the test results for the Eee 1000 showed everything as working.
[14:32] <persia> But I do know that the netbook images on cdimage.ubuntu.com are all i386.
[14:34] <persia> And I believe most of the testing that was done on the Eee 1000 was done with i386.
[14:34] <persia> So, if I had an Eee1000, and I was installing Jaunty, I'd use http://cdimage.ubuntu.com/ubuntu-netbook-remix/daily-live/current/jaunty-netbook-remix-i386.img
[14:35] <rhpot1991> persia: I'd prefer the full desktop over NBR though, or is there some easy way to modify the UI?
[14:35] <rhpot1991> currently have intrepid on here so I can just update-manager -d
[14:36] <persia> There's some way to modify the UI, but I forget what it is, and all the applications are the same anyway.
[14:36] <persia> You should be able to just run update-manager -d
[14:36] <rhpot1991> thought so
[14:37] <persia> I'd recommend giving the Ubuntu kernel a try again: I think it supports the Eee 1000, and that way you get the updates, etc. automatically.
[14:37] <rhpot1991> persia: I think I'll install lpia to my SDHC and mess with that some, and keep my main install in tact so I can always upgrade that if I don't like the lpia
[14:37] <rhpot1991> persia: thats the plan, thanks
[14:38] <persia> Please report bugs if you find them with lpia.  I doubt you'll notice much difference other than a few missing packages, but I could be wrong.
[14:38] <rhpot1991> are there many missing packages?
[14:39] <persia> Well, the list of FTBFS for lpia is longer than the list for i386, by a fair bit.
[14:39] <persia> There's also a set of packages that are only compiled for specific architectures.  I've added "lpia" to a bunch of those, but I suspect I've missed quite a few.
[14:42] <rhpot1991> persia: I'll give it a run and report what I find
[14:43] <persia> rhpot1991, Cool.  I always like it when someone tests lpia, because they usually find something I missed, but because I always recommend people use i386 instead, not everyone takes me up on it :)
[14:45] <ogra> settings-change desktop mode
[14:45] <ogra> s/-/->/
[14:45] <ogra> that switches immediately to a classic ubuntu desktop
[14:46] <ogra> (under netbook remix)
[14:47] <rhpot1991> ogra: any reason not to just use update-manager -d from a regular ubuntu install, IE does NBR give you anything different?
[14:48] <ogra> no, i just saw that persia suggested to use jaunty-netbook-remix-i386.img ans you asked about a way to easily change the UI ...
[14:49] <ogra> there is a "one button" way included by default in UNR now
[14:49] <rhpot1991> ogra: ok, just checking
[14:49] <persia> So it's useful to me, even if not to you, because I can answer the question next time :)
[16:13] <rhpot1991> persia: any idea if the intel drivers in Jaunty are an issue, I'm seeing some words about regression happening there
[16:14] <rhpot1991> also can you verify that there is no lpia live cd, just an alternate installer
[18:28] <steveire> Hi. I'm installing a kubuntu desktop system on my eee, and I noticed there's an ubuntu netbook remix. I want to make sure that if there's any under the hood differences in the UNR I can get the same on my kubuntu system. Most info pages I see on it are just about ui differences.
[18:32] <lool> It's mostly UI related
[18:35] <Riddell> also it's a USB image not an ISO
[18:35] <Riddell> and it's about 200MB larger surprisingly
[18:42] <steveire> OK so. I guess there's nothing extra for me to benefit from.
[18:44] <ogra> Riddell, it has a bunch of langpacks included
[18:47] <ogra> and the UNR desktop bits including their deps
[18:47] <ogra> beyond that its not much different
[19:57] <rhpot1991> persia: seems there is no kernel/drivers/staging for lpia, and thats where the realtek wifi drivers live


[03:40] <lotuspsychje> good morning
[12:06] <matt3> my colors : https://imgur.com/a/h2tzkk4
[12:08] <matt3> ok ?