[00:47] <TheMuso> c
[01:57] <jamin> you guys concerned with regressions for non-default packages?  such as xfce
[01:58] <micahg> jamin: #xubuntu-devel for xfce* packages
[01:59] <jamin> micahg, cool will let them know.
=== dendro-afk is now known as dendrobates
=== cpg is now known as cpg|away
[02:54] <mfisch> I'm working on a bug and the filer left one of the repro steps as "install any package which adds a system user", anyone know any off hand?
[02:54] <mfisch> perhaps davfs2
[02:57] <elky> mfisch, postgres?
[03:05] <mfisch> I'll try it
[03:05] <mfisch> davfs2 also worked
[03:05] <mfisch> thanks elixey
[03:06] <mfisch> stupid tab, thanks elky
[03:06] <elky> yw
[04:36] <pitti> Good morning
[04:37] <pitti> doko_: I didn't reject it, it just didn't seem useful/appropriate for an SRU at that time; but it seems some third-party packages do need it, so fine for me
[04:37] <pitti> doko_: I didn't promote/demote any package
=== cpg|away is now known as cpg
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
=== dendrobates is now known as dendro-afk
[06:34] <dholbach> good morning
[06:35] <pitti> dholbach: guten Morgen, wie gehts?
[06:36] <dholbach> hey pitti - sehr gut - und bei dir? allet jut?
[06:36] <pitti> dholbach: jau, danke! had a nice relaxing weekend
[06:36] <dholbach> great :)
[06:40] <dholbach> hyperair, happy birthday :)
[06:40] <hyperair> dholbach: thanks :)
[06:47] <Techna_Rave_Pony> Hello?
[07:12] <pitti> doko_, stokachu: FYI, gdb has waited in the precise-proposed queue for over a week
=== henrix_ is now known as henrix
=== henrix is now known as henrix_
=== henrix_ is now known as henrix
[09:02] <dholbach> diwic, hey - how are you doing?
[09:04] <dholbach> diwic, I got a USB sound card a few days ago and plugging it in and having it immediately activated for sound works great. do you know if there's plans to also make the sound indicator and volume controls use a newly plugged in soundcard?
[09:05] <diwic> dholbach, hi! you mean activate a newly plugged in card to be the default input and output?
[09:05] <dholbach> yes
[09:05] <diwic> dholbach, because the sound indicator and media keys follow what you set as default in gnome sound settings.
[09:06] <dholbach> I'm not sure if that's feasible in every single circumstance, I just found myself using the audio preferences a couple of times before controlling volume and everything
[09:06] <diwic> dholbach, that's a design question. And one that sounds simple but it quite complex under the hood.
[09:06] <dholbach> yes, I can imagine :-/
[09:06] <diwic> dholbach, e g, upstream has the idea of role-based stuff, e g phone calls in your headset and music through your speakers
[09:07] <xnox> dholbach: but in the sound prefs, I can select the new usb card as default and then control it from the indicators & media icons...
[09:07] <dholbach> in any case I'm happy that it generally works, even if I have to use the gnome sound settings more often than I'd like :)
[09:07]  * xnox not great but....
[09:07] <dholbach> xnox, yes that works for me too - it's just that I have to do it whenever I plug it in :)
[09:07] <dholbach> diwic, ah, that might be interesting indeed
[09:07] <diwic> dholbach, add to that the kernel does not give us a clear signal after resume, so we don't know if we just plugged in the sound card right after resume, or if it showed up as part of the resume process
[09:08] <dholbach> in any case it's not a huge deal - I just wanted to hear what is planned :)
[09:08] <xnox> dholbach: time for you to learn udev rules & write one which will flip the setting for you. =)))))
[09:08] <dholbach> xnox, yes, so much to learn :)
[09:08] <diwic> dholbach, btw, this is one of the discussion topics on the pulseaudio mini-conference, colocated with UDS :-)
[09:08] <dholbach> excellent!
[09:11] <diwic> xnox, dholbach, as an option you can add "load-module module-switch-on-connect" to your /etc/pulse/default.pa
[09:12] <dholbach> alright, I'll note that down and experiment with it
[09:12] <diwic> I think it is shipped by default
[09:12] <dholbach> thanks a lot diwic
[09:12] <diwic> but it isn't activated by default because it would interfere with the rule-based stuff
[09:14] <dholbach> right
=== doko_ is now known as doko
[10:05] <jamespage> stgraber, around? I have an iscsi root query re bug 1057635
[10:05] <ubottu> Launchpad bug 1057635 in Ubuntu "initramfs does not use iscsiroot device presented by ipxe" [Undecided,New] https://launchpad.net/bugs/1057635
[10:08] <stgraber> jamespage: going for lunch now, I'll be back in 30-45min
[10:08] <jamespage> stgraber, ok - give me a ping when you are back
[10:08] <jamespage> ta
[10:42] <stgraber> jamespage: I'm back
[10:42] <jamespage> stgraber, hey!
[10:43] <jamespage> stgraber, so - bug 1057635
[10:43] <ubottu> Launchpad bug 1057635 in Ubuntu "initramfs does not use iscsiroot device presented by ipxe" [Undecided,New] https://launchpad.net/bugs/1057635
[10:44] <jamespage> stgraber, slightly odd-ish case in that I use ipxe to directly sanboot from iscsi volumes, rather than using a tftp accessible kernel and initrd
[10:44] <jamespage> within the initrd the iscsi initiator does not appear to be configured; so iscsistart stuff fails;
[10:45] <jamespage> I can work around it by specifying it a) on the commandline in grub (iscsi_initiator) or b) adding it to /etc/iscsi/iscsi.initramfs and updating accordingly
[10:45] <jamespage> stgraber, any thoughts?
[10:45] <stgraber> right, so the question is what happen if you add iscsi_initiator on the boot command line when booting that system without iscsi
[10:46] <stgraber> basically we don't want to regress the case where someone dumps their iscsi disk in a VM or standard system, IIRC that's why we don't put the iscsi_initiator in grub's config
[10:47] <stgraber> but if the initramfs detects that case and just ignores iscsi_initiator in such case, then it should be fine to just have iscsi_initiator set in grub too
[10:47] <jamespage> stgraber, I think that is entirely appropriate; however surely it would be better to set it up in the initramfs?
[10:48] <jamespage> stgraber, that way its all contained to open-iscsi; and does not pollute grub
[10:48] <stgraber> indeed, if we can just get rid of the boot parameter completely, that'd work too
=== cpg is now known as cpg|away
[10:50] <jamespage> stgraber, well it appears to work if I add it manually and update
[10:58] <jamespage> stgraber, hmm - odd - TBH I'm not sure why its not actually working
[11:02] <jamespage> stgraber, if I force a manual boot by specifying iscsi_initiator and then just update the initramfs it all works again...
[11:08] <jamespage> stgraber, it feels like /etc/iscsi/initiatorname.iscsi is not making it into the initramfs during install
[11:09]  * jamespage digs more
=== MacSlow is now known as MacSlow|lunch
=== dendro-afk is now known as dendrobates
[11:28] <jamespage> stgraber, eureka! I see the issue; the initiator is not generated until first start of open-iscsi
[11:29] <jamespage> so its "Generated=Yes" when the initramfs gets built
[11:29] <stgraber> jamespage: oh, fun
[11:30] <jamespage> stgraber, looks like this change "Generate the random initiatorname during postinstall rather than in the init script." got dropped on last merge
[11:33] <stgraber> doh, so my fault again right? :)
[11:33] <stgraber> we'll really need to forward those changes to Debian or the next merge will be as much of a pain as the previous one...
[11:36] <jamespage> stgraber, lol
[11:37] <jamespage> agreed
[11:37] <jamespage> stgraber: I've stuff details in that bug report - are you OK to fix? feels like something that needs fixing for release
[11:38] <stgraber> jamespage: if it's easy for you to fix, I'd prefer that you fix it and I do the review once it's in the queue (with my release team hat on). Otherwise I can certainly find some time to do it and nag someone else on -release to do the review
[11:39] <jamespage> stgraber, OK - on it now
=== _salem is now known as salem_
[12:02] <jamespage> stgraber, just uploaded to quantal-proposed queue
[12:02] <stgraber> jamespage: thanks
[12:16] <lamont> what package should I use for filing a bug that when I grab a window border and drag to resize the window, it gets horribly confused if the mouse moves before it gets around to noticing position, and suddenly I'm dragging a marker about an inch away from where the border of the window is (and the window never catches up to the cursor) (did that sentence even make sense?)
[12:45] <tsimpson> lamont: probably compiz
[12:47] <lamont> tsimpson: ta
=== MacSlow|lunch is now known as MacSlow
[12:58] <doko> jodh, so was upstart just build related?
[12:59] <jodh> doko: I believe so - cannot force the failure on scheat.
[13:04] <cjwatson> SpamapS: Do you guys have any idea what's happening with the zookeeper/armhf build failure?
[13:04] <cjwatson> SpamapS: I don't really want to remove it since it's a build-dep of juju
=== Ursinha-afk is now known as Ursinha
[13:06] <jdstrand> @pilot in
=== udevbot_ changed the topic of #ubuntu-devel to: Quantal Quetzal development | Beta 2 released! | Archive: Frozen | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and dicussion of hardy -> precise | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: jdstrand
[13:11]  * dholbach hugs jdstrand
[13:11] <jdstrand> heh
[13:11]  * jdstrand hugs dholbach :)
[13:11] <dholbach> :)
=== Quintasan_ is now known as Quintasan
=== BenC__ is now known as BenC
=== dendrobates is now known as dendro-afk
=== yofel_ is now known as yofel
[14:33] <cjwatson> jamespage: oh, any luck with eigenbase-resgen?
=== salem_ is now known as _salem
=== jbicha is now known as Guest58037
[15:37] <mvo> ev: is there a way to get instance for a problem from errors.ubuntu.com by version? i.e. I suspect that bug #1044141 is fixed or a different error with a similar backtrace but to be sure I would need some instance of the bug with the most recent versions or date. is there a way to get that?
[15:37] <ubottu> Launchpad bug 1044141 in software-center (Ubuntu) "software-center crashed with UnicodeDecodeError in __str__(): 'ascii' codec can't decode byte 0xc3 in position 29: ordinal not in range(128)" [High,Fix released] https://launchpad.net/bugs/1044141
=== _salem is now known as salem_
[15:54] <xnox> Laney: you are briliant =)
[15:54]  * Laney gets nervous
[15:55] <Laney> can xnox hear me singing along to this song?
[15:55] <xnox> Laney: maybe...
[15:55] <xnox> Laney: actually I was about reproducing bug 1057690
[15:55] <ubottu> Launchpad bug 1057690 in ubiquity (Ubuntu) "ubiquity crashed with KeyError in partman_dialog(): 'method_choices'" [Medium,Confirmed] https://launchpad.net/bugs/1057690
[15:55] <Laney> oh that
[15:55] <Laney> yeah it's annoying :P
[15:56] <xnox> Laney: basically the partition is locked, and you shouldn't click it. /me did disable the plus button, but not the double click action
[15:56] <Laney> what should I have clicked on?
[15:56] <Laney> the other one?
[15:57] <Laney> doesn't sound like Brian was doing that, so perhaps it can be triggered in other ways too
[15:57] <xnox> Laney: well it's locked, so you can't edit that one, instead you should edit the loop mount on the top =)
[15:58] <Laney> so very clear ;)
[15:58] <xnox> Laney: and by locked, I mean there isn't even an unlock button.... partman doesn't have it & I didn't code it yet.
[15:58] <superjoe> how hard would it be to convince you guys to upgrade this package to a newer release before QQ comes out? http://www.ubuntuupdates.org/package/core/quantal/universe/base/mpd
[15:58] <xnox> Laney: "anyone familiar with d-i interface will feel right at home"
[15:58] <Laney> also the automatic partitioner is a bit stupid when the drive is small
[15:58] <Laney> it creates a / which it can't installed onto
[15:58] <Laney> s/installed/install/
[15:59] <Laney> due to being too small
[15:59] <xnox> Laney: funny. It should check the prepare step and if that passes it should work. How small are we talking here?
[15:59] <Laney> 8G
[15:59] <Laney> it made a 2.7G /
=== Guest58037 is now known as jbicha_
[15:59] <Laney> and the error message told me that /I/ created it too small!
[15:59] <xnox> Laney: and how much RAM did you give your VM     :-?
[16:00] <Laney> err
[16:00] <Laney> xnox: 8G also
[16:01]  * Laney tosses RAM around like confetti
[16:01] <micahg> superjoe: you can request a backport to QQ once it gets into R
[16:01] <micahg> (or now if you really want to)
[16:01] <xnox> it works fine with 8GB drives here for me.... unless it created a (8 - 2.7G) ~= 5.3G swap. Aha. So it tried to go for 100% * RAM swap, but it had a minimum hard-code at 2.7 for / which is no longer enough.
[16:01] <xnox> Laney: can you file a bug about it?
[16:01] <superjoe> micahg, could you direct me to where I might do that? do I send an email to a mailing list?
[16:02] <Laney> xnox: clever. Will do
[16:02] <Laney> I assume you don't need logs for that?
[16:02] <micahg> superjoe: https://wiki.ubuntu.com/UbuntuBackports
[16:02] <Laney> well ...
[16:02] <Laney> that package looks to not be in sync
[16:02] <superjoe> thank you micahg
[16:02] <xnox> Laney: no logs, text only. just make sure you include "tossing RAM around like confetti" in the bug report please =)
[16:02] <Laney> so I'd check if it can be a straight backport from anywhere
[16:03] <Laney> xnox: ack :P
[16:04]  * xnox score update from the field of play: Laney 2 - 0 Partman
[16:05] <Laney> test installs are fun
[16:18] <Laney> xnox: bugs #1066964 (I didn't manage to use the keyword, soz)
[16:18] <ubottu> Launchpad bug 1066964 in ubiquity (Ubuntu) "Auto partitioner can create a root partition which is too small" [Undecided,New] https://launchpad.net/bugs/1066964
=== deryck is now known as deryck[lunch]
=== deryck[lunch] is now known as deryck
[17:50] <tkamppeter> slangasek, hi
[17:51] <slangasek> tkamppeter: hey there
[17:53] <tkamppeter> slangasek, I have uploaded a possible fix for bug 1034045 to quantal-proposed. It is not yet accepted. Can you test this as soon as possible.
[17:53] <ubottu> Launchpad bug 1034045 in dbus (Ubuntu) "cupsd assert failure: *** glibc detected *** /usr/sbin/cupsd: free(): corrupted unsorted chunks: 0x00007f3dc478c0f0 ***" [High,New] https://launchpad.net/bugs/1034045
[17:55] <slangasek> tkamppeter: I can probably get it into -proposed and test it today; though I don't think this is something we want to respin the CDs for, so don't panic if I don't get to it :)
[17:56] <jdstrand> @pilot out
=== udevbot_ changed the topic of #ubuntu-devel to: Quantal Quetzal development | Beta 2 released! | Archive: Frozen | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and dicussion of hardy -> precise | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
=== cpg|away is now known as cpg
[17:56] <tkamppeter> slangasek, Zero-Day-SRU would be good enough. If you quickly move it into -proposed and test it, we get it quickly into -updates for a zero-Day-SRU.
[17:57] <slangasek> yep
[17:58] <tkamppeter> slangasek, and in the positive case Apport will stop saying "Good Morning" to you ...
[17:58] <slangasek> quite :)
=== cpg is now known as cpg|away
=== Guest72485 is now known as dpb___
=== jbicha_ is now known as jbicha
=== bdrung_ is now known as bdrung
=== cpg|away is now known as cpg
=== salem_ is now known as _salem
=== _salem is now known as salem_
[20:01] <pitti> soren, kees, mdz, stgraber: ready for TB meeting in a bit? still waiting for the previous meeting ot finish
[20:01] <stokachu> is gnome-keyring out of sync when the code branch shows version 3.2.2 with last modification @ 4/26/2012 and the actual built package is 3.6.0 last modified on 9/27/2012?
[20:01] <pitti> stokachu: yeah, unfortunately a lot of UDD branches often go out of sync
[20:02] <stokachu> i was under the impression to alway swork from the latest dev branch though is this not the case during this time?
[20:03] <stokachu> and where would i find the latest code commits that show where gnome-keyring 3.6.0 was imported in the development branch
[20:05] <kees> pitti: yeah
=== cpg is now known as cpg|away
[20:07] <stokachu> do i need to open a bug about the branches being out of sync for gnome-keyring?
[20:07] <pitti> stokachu: you can also ping james_w and ask him to kick it
[20:08] <stokachu> ah ok
[20:08] <pitti> stokachu: for now I suggest the old way and apt-get source/change directly
[20:08] <stokachu> james_w: ping
[20:08] <stokachu> pitti: ok ill look into that
[20:08] <stokachu> i just like my workflow :D
[20:10] <james_w> hi stokachu
[20:10] <stokachu> james_w: hey there, was curious if you have some spare cycles to sync gnome-keyring branches?
[20:10] <stokachu> the quantal one is showing version 3.6.0 but the latest branch commit doesn't
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
=== _salem is now known as salem_
[20:56] <tkamppeter> slangasek, did you test my new cups package?
[20:57] <slangasek> tkamppeter: all in good time
[20:58] <tkamppeter> slangasek, sorry, I only asked because you moved around status bits of the bug report.
[20:59] <slangasek> tkamppeter: yes, I'm cleaning up the state of the bug wrt the SRU process :)
[21:01] <stokachu> james_w: thanks for getting that synced up
=== henrix is now known as henrix_
=== cpg|away is now known as cpg
[21:18] <james_w> stokachu, np
[21:44] <stgraber> pitti: oops, sorry for that, in Europe this week and completely forgot to check for my evening meetings as my phone was dead and I only just got back now...
[21:48] <slangasek> hggdh: server images being respun for maas
[21:48] <slangasek> (bug #1065763)
[21:48] <ubottu> Launchpad bug 1065763 in maas (Ubuntu) "UI URL displays "200 Error" page after CD install" [Critical,Fix released] https://launchpad.net/bugs/1065763
[22:09] <slangasek> barry: is bug #1066883 the same as your video-on-mac bug?
[22:09] <ubottu> Launchpad bug 1066883 in xorg (Ubuntu Quantal) "Fatal server error: Can not run in framebuffer mode on reboot" [Undecided,New] https://launchpad.net/bugs/1066883
[22:12] <barry> slangasek: i don't think so.  i never see an error message, just blank screen
[22:13] <slangasek> alrighty
[22:13] <slangasek> figured it was worth asking
[22:13] <barry> yep :)
[22:13] <slangasek> since the reporter mentions different behavior on first vs. second boot
=== salem_ is now known as _salem