[00:04] <jhojho> 940230
[00:05] <jhojho> bug 940230
[04:16] <kees> micahg: so, this has regressed a while back, and I think you sent me to https://bugzilla.mozilla.org/show_bug.cgi?id=716110 but I can't make sense of it.
[04:17] <kees> basically, this doesn't work:
[04:17] <kees> /usr/lib/firefox/firefox -P Browsing -remote 'openURL(http://feedproxy.google.com/~r/MFLF/~3/WM7yqk8qY-U/)'
[04:17] <kees> Error: No running window found
[04:17] <kees> I've tried combinations of -new-tab and -new-window but they yell about there already being a copy of firefox running. :P
[04:19] <micahg> kees: first instance without -no-remote and subsequent with IIRC
[04:19] <kees> micahg: I run all my firefox process with: /usr/lib/firefox/firefox -ProfileManager
[04:20] <kees> so the "Browsing" instance is already running
[04:20] <micahg> kees: right, well, starting with Firefox 13 you can just pass -new-instace
[04:20] <micahg> oh, wait, I see the question now
[04:20] <kees> OOOOH the problem is with the initial, not the latter!
[04:21] <kees> yes! starting the initial with -new-instance fixes it! yay!
[04:22]  * kees hugs micahg
[04:22] <kees> now I just have to figure out how I tricked unity into launching my special firefox command instead of the real thing
[04:24] <kees> no idea :P
[05:10] <pitti> Good morning
[05:29] <pitti> Sweetshark: LibO uploaded now
[06:49] <pitti> infinity, cjwatson, RAOF, SpamapS: FYI, http://people.canonical.com/~ubuntu-archive/pending-sru.html is now showing non-DONE builds
[06:49] <pitti> for SRUs that's helpful to block -updates, and for precise-proposed it tells us when we can copy stuff over
[06:50] <RAOF> Nifty.
[06:51] <pitti> together with the new sru-release --release (or -r) switch, we now should have the basic tools to use precise as a staging area
[06:51] <pitti> we are still missing an installability check for -proposed, though
[06:52] <pitti> http://people.canonical.com/~ubuntu-archive/testing/precise-proposed_probs.html would be good to have, and I suppose not even particularly hard to set up
[06:53] <pitti> in fact, that looks pretty trivial
[06:53]  * pitti gives it a shot
[06:54] <pitti> and add the missing lucid..oneiric-proposed as well (we only have it for dapper and hardy)
[06:57] <cjwatson> pitti: to use it properly we'll need to be able to ask questions like "does moving this set of packages from -proposed to release make release less installable?", rather than just knowing whether -proposed is installable
[06:57] <cjwatson> not saying all these aren't improvements, but we did lay out a plan
[06:57] <cjwatson> of sorts
[06:57] <pitti> right, I wasn't saying it was perfect already
[07:01] <cjwatson> I have an LP branch for enabling -proposed outside freeze periods, which is just waiting for me to squeeze it in under the LoC requirements of the new LP maintenance policy before I submit an MP
[07:01] <pitti> cjwatson: I saw, thanks so much for this
[07:06] <broder> cjwatson: does your patch just enable proposed or other non-release pockets as well?
[07:14] <pitti> there http://people.canonical.com/~ubuntu-archive/testing/precise-proposed_probs.html
[07:14] <pitti> once LibO i386 finishes building on i386, it should have some stuff until the other arches catch up; I'll double-check it then
[07:19] <cjwatson> broder: just proposed
[07:20] <broder> aww :)
[07:20] <cjwatson> broder: hopefully makes it a bit easier to add other pockets in future though
[07:37] <tumbleweed> pitti: what is libreofficeu-core in the libreoffice upload you sponsored for Sweetshark? http://launchpadlibrarian.net/98802969/libreoffice_1%3A3.5.1-1ubuntu1_1%3A3.5.1-1ubuntu2.diff.gz
[07:37] <tumbleweed> err not that
[07:37] <tumbleweed> oh, no the url is right
[07:37] <micahg> no, that is right :)
[07:39] <pitti> tumbleweed: I suppose it's a typo
[07:39] <pitti> Sweetshark: ^
[07:39] <tumbleweed> he appears to be offline, I poked him an hour or two ago
[07:40] <pitti> yes, still a bit early for him
[07:51] <pitti> tumbleweed: let's say it's a (rather expensive) test case for http://people.canonical.com/~ubuntu-archive/testing/precise-proposed_probs.html :)
[07:55] <pitti> tumbleweed: curious though, the package was already tested in a PPA, including a full upgrade test; I guess it slipped in when building the suorce for precise :(
[08:02] <Daviey> pitti: Hey!  Can i talk to you about https://launchpad.net/ubuntu/+source/nova/2011.3+git20111117-0ubuntu1 ?
[08:03] <pitti> Daviey: ah yes, indeed; it seems that hasn't been tested much yet
[08:03] <Daviey> pitti: A few of the issues are not realistically going to get verified in Ubuntu, such as a Xen bug.  However, as previously discussed - we are putting more confidence into the upstream stable tree process (we are reviewers of it.)
[08:03] <Daviey> pitti: It has.. Trellis Has been using it..
[08:03] <Daviey> (and others obv.)
[08:03] <smb> Daviey, a Xen bug? Where? :)
[08:04] <Daviey> pitti: It's also been through our internal CI
[08:04] <Daviey> smb: A bug with nova usng Xen.
[08:04] <pitti> Daviey: AFAIR the proposal for the standing SRU exception was that the -proposed version has to be run through a large test suite and QA process which ensures that there are no regressions
[08:04] <pitti> Daviey: not necessarily to validate each individual bug, as that's rather impractical for so many
[08:05] <smb> Daviey, If you care to pass me the bug number, I may have a look too if needed. I just have missed it up to now
[08:05] <pitti> so if there was something like a QA process, it either wasn't posted to one of the bugs, or it slipped our attention
[08:07] <Daviey> pitti: The process is that we QA each commit upstream as it hits, and do so for milestones.
[08:08] <Daviey> Hmm, but the results don't seem to be posted public.
[08:08]  * Daviey investigates 
[08:08] <pitti> Daviey: and that still doesn't guarantee us that the bits in -proposed will actually work
[08:09] <pitti> we need to run integration/system test against the bits that are in -proposed, not against what landed in upstream trunk a long time ago
[08:09] <pitti> s/not/not just/
[08:09] <Daviey> pitti: True, but this is a large part of the reason we are involved in the upstream stable tree, to try to mitigate this.
[08:09] <pitti> and also consider differnent kinds of existing setups and configs
[08:28] <pitti> Daviey: so I think it's been in -updates long enough, and there are enough v-dones to justify moving to -updates if you feel comfortable with it
[08:29] <pitti> Daviey: but I don't think it was a good example of how things should go; it took too long, and there was not enough feedback about the global (not per-bug) regression testing with this
[08:29] <pitti> Daviey: shoudl go for the SRU exception, I mean
[08:34] <Daviey> pitti: Yeah, I agree with that.  We need to come up with a better process to do distro validation.
[08:34] <Daviey> pitti: I'm just crosschecking a few more things.
[08:35] <pitti> Daviey: ok, thanks; let me know when I should move to -updates
[08:38] <Daviey> pitti: It looks like it will superseed a security upload currently in -updates.. So it's a no-go
[08:38] <Daviey> dammit.
[08:38] <Daviey> ie, doesn't have the security fix.
[08:41] <micahg> wow, that was over 2 months ago
[08:43] <Daviey> micahg: 14 weeks is certainly more than 2 months :)
[08:44] <micahg> Daviey: was referring to the fact it was superseded by a security upload ~2 months ago
[08:46] <Daviey> micahg: Yeah, the SRU upload has been pending for 14 weeks.
[08:47] <micahg> Daviey: it was out of date when it was uploaded (6.3 actually had a fix not included, so it never could've gone to -updates anyway)
[08:47] <Daviey> micahg: Yep, just covered this :)
[09:44] <tumbleweed> pitti: :)
[10:31] <henrix> pitti: hi. it looks like some kernel packages landed on the wrong component
[10:31] <henrix> pitti: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965346/comments/2
[10:31] <pitti> henrix: thanks, will fix
[10:31] <henrix> pitti: great, thanks
[10:32] <pitti> weird, I moved the whole thing to main
[10:32] <pitti> oh, that's from -meta
[10:32] <pitti> henrix: it's in universe in -security and -updates as well, though
[10:33] <pitti> but the -14 binaries are in main indeed
[10:33] <henrix> pitti: strange...
[10:34] <pitti> henrix: I guess that was before we had these nice new checks
[10:34] <pitti> henrix: I'll fix it
[10:34] <henrix> pitti: yeah, that would be great.
[10:34] <henrix> pitti: please let me know once that's sorted out
[10:34] <pitti> henrix: done; I'll re-close the bug
[10:35] <henrix> pitti: cool
[10:50] <pitti> ev: FYI, dealing with the problem_types thingy now (to avoid duplicate work)
[10:51] <ev> pitti: cheers!
[10:51] <pitti> ev: I subbed you to the bug, so that you can follow the progress
[10:51] <ev> thanks muchly
[10:51] <vibhavp> What is best language to learn to start with Ubuntu development?
[10:59] <pitti> vibhavp: depends on the area you want to work on really, but all in all the two most common languages are C and Python
[11:04] <davmor2> pitti: I added the gvfs info you asked for to bug #952933 anything else likely to help?
[11:26] <pitti> davmor2: hm, this also looks correct
[11:26] <pitti> davmor2: do you see it in RB as a media player?
[11:27] <pitti> I tested that with my phone and my wife's Sony Walkman, and it seems to generally work okay
[11:27] <pitti> davmor2: do you also get this in a guest account? we had some problems with disabled plugins in RB
[11:29] <davmor2> pitti: yeap I see it and it has a a music player icon,  it just doesn't open in RB or trigger the normal open in dialog like it does in natty/oneiric
[11:30] <davmor2> I should say it doesn't auto open RB
[11:34] <pitti> davmor2: ah, thanks
[11:34] <pitti> davmor2: ok, I can check that part
[11:34] <pitti> davmor2: so I retitle to "media players do not trigger Open With Rhythmbox dialo"?
[11:36] <pitti> davmor2: done, thanks!
[11:36] <davmor2> pitti: yeap you can do, I merely assumed it was opening the nautilus window as it wasn't triggering the fact it was a media player
[11:52] <seb128> pitti, the default on media player connect is "ask what to do"
[11:52] <seb128> i.e it should display a dialog
[11:52] <seb128> that doesn't work?
[11:54] <jelmer> FreezeExceptionProcess documents that I should explicitly document that I'm uploading a new bugfix-only upstream release during FF
[11:54] <jelmer> Is there are recommended way of handling this when syncing, or should I do a merge in that case?
[11:57] <cjwatson> jelmer: don't avoid syncs just for the sake of extra changeloggery
[11:57] <cjwatson> syncs are good if possible
[11:58] <cjwatson> you can tell us on #ubuntu-release or something
[11:58] <cjwatson> or we can just look :)
[12:01] <jelmer> cjwatson: will do - thanks!
[12:25] <pitti> seb128: apparently it doesn't
[12:26] <seb128> pitti, I've the issue with my ipod, looking at it
[12:26] <pitti> my mobile phone asks me what to do with the photos
[12:26] <pitti> but nothing for the music
[12:26] <seb128> pitti, it seems to not detect it as a music player
[12:26] <seb128> pitti, i.e nautilus doesn't have the banner either
[12:26] <seb128> where a sd card with photos work
[12:26] <seb128> it displays a banner in nautilus "do you want to open with shotwell"
[12:34] <speakman> The flashplayer-installer update earlier today has ruined any flash content! Anyone else noticed?
[12:37] <pitti> ah, http://people.canonical.com/~ubuntu-archive/testing/precise-proposed_probs.html seems to work fine
[12:46] <davmor2> seb128: ref: music player. it isn't working here for me it just opens a nautilus window
[13:28] <fraviofii> hello, I would like to ask some advice regarding ubuntu-core
[13:28] <fraviofii> I'm trying to install opencv package in ubuntu-core distribution for arm
[13:29] <fraviofii> I'm using chroot, and the apt-get install is not finding the package. I changed source.list file from /etc/apt
[13:38] <geser> which error do you get?
[13:39] <fraviofii> package not found
[13:40] <geser> which command do you use? (which package exactly do you try to install?)
[13:40] <fraviofii> first I use apt-get update
[13:40] <fraviofii> and then, apt-get python-opencv
[13:40] <fraviofii> sorry
[13:40] <fraviofii> one minute
[13:41] <fraviofii> in fact, I used "apt-get install opencv"
[13:41] <fraviofii> probably that's the reason
[13:41] <geser> opencv is the source package name, python-opencv is one of the binary packages build from that source package
[13:42] <fraviofii> yes ... that's the problem ... i'm installing right now the python-opencv package, which is istalling the dependencies
[14:36] <bjf> pilot in
[14:38] <bjf> @pilot in
[14:45] <ogra_> wow, so if i (by accident or whatever) uninstall unity-greeter i'm completely left with a crashing Xserver in a loop, there is no fallback built into lightdm (not even an ugly one) ?
[14:46] <pitti> I think lightdm should not just recommend: a greeter, but depend on it
[14:47] <ogra_> well, that would have left me in a similar situation, though with a console login by default at least
[14:47] <ogra_> i think it should just have some unthemed fallback thing builtin or so
[14:47] <pitti> bdmurray: it seems your http://reports.qa.ubuntu.com/reports/bug-fixing/precise-fixes-report.html files don't count upload to precise-proposed, nor their copies to precise
[14:47] <pitti> seb128, didrocks ^
[14:48] <seb128> pitti, thanks
[14:48] <pitti> bdmurray: as we are going to use precise-proposed more and more for staging uploads, woudl it be possible to fix thaht?
[14:48] <seb128> ogra pitti, xfailsafe should kick in
[14:48] <didrocks> pitti takes the bug # countest quite seriously :)
[14:48] <seb128> ogra_, pitti: check with bryceh maybe
[14:48] <pitti> well, I also find it quite helpful for duplicates
[14:48] <bdmurray> pitti: I'll look into it
[14:48] <didrocks> indeed :)
[14:49] <pitti> when I see a bug report and I remember "I fixed tihs already", etc.
[14:49] <pitti> but yes, the competition is certainly the most interesting one, as well as judging applicants for upload privs
[14:49] <pitti> bdmurray: cheers
[14:49] <ogra_> seb128, thats another prob, failsafe doesnt get me back to lightdm at all, not even if i installed a greeter during having the failsafe stuff on the screen
[14:50] <pitti> bdmurray: e. g. https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.10-0ubuntu6 does not appear at all
[14:50] <seb128> ogra_, not failsafe mode, xfailsafe or whatever the x debugging mode is called
[14:50] <seb128> ogra_, the thing which should kick in when you get a broken xorg config
[14:51] <ogra_> seb128, well, i get a dialog telling me stuff about my xserver and dropping me into a selection menu to reconfigure etc
[14:51] <ogra_> funnily completely without mouse nor is any kbd management possible
[14:51] <seb128> ogra_, you said " i'm completely left with a crashing Xserver in a loop
[14:51] <seb128> ogra_, so which one it is?
[14:51] <seb128> does it loop segfault or does it display a dialog?
[14:52] <ogra_> i get that dialog, then X crashes trying to start lightdm, crashes because it finds no greeter and gets me back to the dialog
[14:53] <ogra_> i can exit the failsafe thing qith esc, but not select anything
[14:53] <seb128> ogra_, the dialog should let you fix your lightdm config
[14:53] <seb128> you have several bugs there...
[14:53] <seb128> handling broken configs and install is an hard job ;-)
[14:53] <ogra_> once i exit i'm left with a black screen and blinking cursor in the top left corner and the system seems to not take any kbd input
[14:54] <ogra_> (i can ping it, its not crashed, but something blocks the kbd so i cant switch to a tty)
[14:55] <ogra_> seb128, yeah, and i think its a corner case (i tried lxde on my netbook ... since g-s-d is so annoyingly crashy i removed it which pulled our unity-greeter and left me in that state)
[14:55] <ogra_> s/our/out/
[14:56] <seb128> ogra_, can you give me the bug number for your g-s-d issues so we can try to get them resolved?
[14:57] <ogra_> so how would i reconfigure lightdm from console ? dpkg-reconfigure doesnt seem to do anything
[14:57] <ogra_> seb128, its logged in the tracker (also reported by pgraner), thats a plain segfault iirc
[14:57] <seb128> ogra_, is that the wacom tablet one?
[14:57] <ogra_> nope
[14:57] <ogra_> arm
[14:57] <seb128> ogra_, reconfigure what?
[14:58] <ogra_> lightdm
[14:58] <seb128> ogra_, what option?
[14:58] <ogra_> the greeter
[14:58] <seb128> ogra_, I don't think there is a dpkg interface to reconfigure anything
[14:58] <seb128> just edit /etc/lightdm/lightdm.conf
[14:58] <ogra_> /etc/lightdm.conf points to unity-greeter even though thats not installed
[14:58] <seb128> ogra_, well install a greeter, the gtk one for example
[14:59] <seb128> ogra_, the postinst will update the config for you
[14:59] <ogra_> err /etc/lightdm/lightdm,.conf indeed
[14:59] <ogra_> i have the gtk greeter installed now
[14:59] <ogra_> since a while already, no change
[14:59] <ogra_> feels like the failsafe mode still gets in the way
[14:59]  * ogra_ reboots 
[15:00] <ogra_> hmm,. even reboot gets me back into failsafe
[15:00] <ogra_> and the second window doesnt takle any input
[15:02]  * ogra_ reinstalls the gtk greeter
[15:05] <ogra_> hmm, had to actually edit lightdm.conf but now it works
[15:26] <ogra_> seb128, just fyi, i think my g-s-d bug is bug 956824
[15:28] <seb128> ogra_, ok, thanks
[15:34] <seb128> ogra_, do you get that bug often? when doing what?
[15:34] <ogra_> every login
[15:34] <ogra_> it respawns immediately
[15:35] <seb128> ogra_, upstream says it happens if the call to gnome_rr_screen_new() fails, I wonder if that's a race or something
[15:35] <ogra_> smells very much like one
[15:35] <seb128> ogra_, I will include the upstream patch in my next upload, let me know how it goes
[15:35] <ogra_> i have all themes etc nothing looks weird
[15:35] <ogra_> so it must respawn in the bg
[15:35] <ogra_> will test, thanks "
[15:35] <ogra_> !
[15:36] <seb128> ogra_, yw
[15:37] <seb128> ogra_, on the lightdm greeter topic robert_ancell didn't want to build builtin fallback greeter, his idea was rather to send you to xfailsafe and that xfailsafe would have an option to restore a stock config and would reinstall the greeter if it's uninstalled
[15:38] <ogra_> hmm, it didnt give me any greeter rleated options
[15:38] <ogra_> probably that feature isnt done yet ?
[15:39] <ogra_> in any case i didnt have any kbd/mouse in failsafe after the first window so it wouldnt have helped
[16:07] <marsfligth> Just for your information http://www.zdnet.com/blog/open-source/linus-torvalds-would-like-to-see-a-gnome-fork/9347
[16:07] <cjwatson> Please can we not have a big advocacy war here?
[17:42] <apw> cjwatson, have we added anything to prevent VT handoff with encryption do you know?
[17:44] <cjwatson> apw: not explicitly, but seeing as grub can't read from encrypted devices yet it's quite possible that it takes you down different code paths
[17:44] <cjwatson> for example you may not have a font configured
[17:44] <cjwatson> oh, and indeed that causes us not to load gfxterm
[17:44] <cjwatson> so yeah, you probably won't get vt handoff with an encrypted /
[17:45] <cjwatson> but it's an nth-order consequence
[17:45] <apw> cjwatson, ahh ... well we do still tell the kernel we are doing it, even when we are not, which might not be good
[17:46] <cjwatson> so vt handoff will make the kernel upset if it gets entered in text mode?
[17:47] <apw> cjwatson, i'd not really expect it to no, and it seems to work ok for intel at least, but there are some complaints around ... though you are handing off in normal vt mode so they should be in a better place to cope
[17:47] <apw> cjwatson, will investigate further there are too many holes in my data
[17:48] <cjwatson> ok, well feel free to assign me a bug on that, shouldn't be desperately hard to fix up
[17:48] <cjwatson> if it's just a matter of ditching vt.handoff in that case
[19:23] <smoser> cjwatson, ping.
[22:20] <Awsoonn> d
[22:35] <bjf> @pilot out
[23:56] <SpamapS> W: Failed to fetch bzip2:/var/lib/apt/lists/partial/us-east-1.ec2.archive.ubuntu.com_ubuntu_dists_precise_main_source_Sources  Hash Sum mismatch
[23:56] <SpamapS> ugh
[23:57] <SpamapS> we really need to fix apt so mirrors can't get in this state