[01:07] <hernejj> Hello :) I'm testing Natty daily build 20101130 and I'm not seeing any panels/Unity.
[01:08] <hernejj> This bug #683403 appears to address this problem, but comment 1 states it is "not as a bug report."
[01:08] <ubot2> Launchpad bug 683403 in gnome-session (Ubuntu) "natty 20101130.1 without panel (affects: 1) (heat: 8)" [Low,Incomplete] https://launchpad.net/bugs/683403
[01:08] <hernejj> Can anyone shed any light on this situation?
[01:08] <charlie-tca> Are you on hardware or VM
[01:09] <hernejj> VirtualBox
[01:10] <RAOF> And do you actually have 3D working in VirtualBox?
[01:10] <charlie-tca> the fallback is not in the alpha1 images. It won't happen until alpha2. If you choose classic desktop session at login, it will give you panels.
[01:10] <charlie-tca> It just doesn't happen automatically
[01:10] <hernejj> I know I enabled 3d acceleration in my VM options, but I've not done anything else to configure it.
[01:11] <RAOF> You also need support in the guest; the (pastebinned) output of glxinfo would be instructive
[01:11] <hernejj> So the problem is that I apparently do not have proper 3d acceleration therefore Unity is failing to start. ?
[01:12] <RAOF> Yup.
[01:12] <RAOF> Currently, the failure mode of unity is a blank desktop.
[01:13] <hernejj> I see.  I'll use classic mode to install guest additions and then try again.  Thank you both for the helpful information:) Happy bug hunting!
[01:17] <RAOF> Fun fact: gnome-do loads successfully in the Unity fallback mode, meaning you can still have a useful launcher :)
[01:55] <kenvandine> robert_ancell, DUDE!  You ARE my hero!
[01:55] <kenvandine> just got a new wifi all-in-one printer... i launched simple-scan and it just worked!
[01:55] <kenvandine> no config at all!
[01:56] <robert_ancell> kenvandine, ?
[01:56] <robert_ancell> oh simple-scan - you're welcome!
[01:56] <kenvandine> :-D
[01:56] <kenvandine> half of the manual is dedicated to how to make the scanner work from windows :)
[02:11] <TheMuso> kenvandine: That makes it all the sweeter. :)
[02:11] <kenvandine> yup
[02:11] <kenvandine> setting up the printer was pretty damn simple...
[02:11] <kenvandine> but simple-scan was even better
[02:11] <kenvandine> it just worked :)
[02:21] <TheMuso> Hrm launchpad being down may be a good sign that I shoudl have a break. Back soon
[05:59] <pitti> Good morning
[06:00] <pitti> bryceh: ah, thanks for the heads-up
[06:07] <robert_ancell> pitti, hey, could you let yelp-xsl (gnome-doc-utils replacement) and lightdm (...) out of the NEW queue?
[06:10] <pitti> robert_ancell: will do in a minute
[06:10] <robert_ancell> pitti, cheers
[06:19] <bilalakhtar> robert_ancell: Why valac-0.10 for shotwell? Why not 0.12?
[06:20] <robert_ancell> bilalakhtar, it doesn't compile with 0.12 and the patch would be non-trivial.  I believe they want to stick with 0.10 for now so they can backport to lucid
[06:20] <bilalakhtar> robert_ancell: okay
[06:20] <robert_ancell> (a lot of GTK common symbols changed name)
[06:20] <robert_ancell> common GTK
[06:43] <pitti> robert_ancell: thanks for fixing the shotwell crash!
[06:48] <pitti> argh compiz pain
[06:52] <robert_ancell> pitti, you felt it from there (my compiz just crashed)
[06:59] <robert_ancell> bye all
[06:59] <pitti> robert_ancell: good night!
[06:59] <pitti> robert_ancell: that was a short night!
[07:25] <bryceh> pitti, yeah in fact I think that bug just "inherited" its natty nomination because it had a maverick nomination
[07:25] <pitti> right
[07:26] <bryceh> I'm not certain anyone actually tested it on natty and took an action to target it to natty
[07:26] <bryceh> still, worth getting it cleaned up
[07:27] <pitti> if it was fixed by a kernel point release, it sohld also be in .37
[07:27] <bryceh> theoretically, yeah
[07:28] <bryceh> pitti, btw at the eastern meeting we ended up talking a bit about http://www2.bryceharrington.org:8080/X/Reports/ubuntu-x-swat/totals-natty-workqueue.svg
[07:28] <bryceh> pitti, particularly around the workflow of focusing on bugs that are tagged $release
[07:29] <bryceh> pitti, I know ubuntu-bug adds 'natty' tags for xorg (thanks!) but I wanted to ask if apport-collect does this as well, and if not, whether it should?
[07:30] <pitti> ubuntu-bug adds natty tags for any bug report
[07:30] <pitti> I'm not that sure about collect, as people might run it on different releases
[07:30] <pitti> my gut feeling is that we only want to know for the original reporter
[07:30] <bryceh> yeah I was gonna suggest the same
[07:30] <pitti> but of course if the bug doesn't have a release tag at all (i. e. was reported without apport) it might
[07:31] <bryceh> I think as long as it's limited to the original reporter, it does make sense to add the tags for other releases
[07:31] <bryceh> there's no problem (from my perspective) for a bug to be tagged for multiple releases
[07:31] <bryceh> in fact it might come to be a good way to mechanically measure how long the bug has been a problem or something
[07:31] <pitti> the retracer gets confused by this, but usually it shold get to the initial report quickly
[07:33] <didrocks> good morning
[07:34] <pitti> hey didrocks
[07:34] <didrocks> hey pitti, how are you?
[07:34] <pitti> much better than my current natty desktop, anyway :)
[07:34] <didrocks> pitti: oh?
[07:34] <pitti> bit tired (still getting used to getting up early), but fine
[07:34] <pitti> didrocks: compiz and panel applet/indicator crash-o-rama
[07:35] <pitti> I just switched to metacity, to be able to start mumble
[07:35] <didrocks> it's just for that week that you get up early, isn't it?
[07:35] <didrocks> is it unity or compiz crashing?
[07:36] <pitti> didrocks: get up> yes
[07:36] <pitti> didrocks: compiz; it also crashes with classic
[07:36] <didrocks> ok, did you post some stactrace?
[07:36] <didrocks> pitti: there is a fix in trunk for OOo, not sure if it can help you
[07:37] <jasoncwarner> didrocks: did you do the fix for OOo?
[07:37] <pitti> didrocks: the crash dump is 55 MB
[07:37] <didrocks> pitti: I just didn't take it because I have to take a lot of others things in trunk for the patch to apply
[07:37] <didrocks> jasoncwarner: ^^
[07:37] <pitti> didrocks: so I didn't upload it yet, as it would make my internet link unusable for about an hour
[07:37] <didrocks> pitti: ok :)
[07:37] <pitti> didrocks: I can upload it over lunch
[07:37] <pitti> didrocks: but I guess it's already reported; it crashes like 10 times a day
[07:37] <didrocks> from my experience, "make dist" in compiz trunk is alwas fun :)
[07:38] <didrocks> pitti: well, I have rarely one to 2 crash a day here…
[07:38] <didrocks> even on mumble
[07:38] <didrocks> seems to be a race issue
[07:40] <pitti> "apport-crash natty" -> plenty :)
[07:55] <didrocks> pitti: hum? I think I don't know how to use advanced search in launchpad then :)
[07:55] <didrocks> (I'm looking on compiz)
[07:56] <didrocks> and looking at the tags
[07:57] <pitti> didrocks: well, "3", but bug 677906  has some dupes
[07:57] <ubot2> Launchpad bug 677906 in compiz (Ubuntu) "compiz crashed with SIGSEGV in GLTexture::bindPixmapToTexture() (affects: 8) (dups: 4) (heat: 42)" [Medium,New] https://launchpad.net/bugs/677906
[07:58] <didrocks> pitti: I think this one is the OOo one which is fixed in trunk
[07:58] <didrocks> but as said, I'm not confident breaking everything for alpha1 :)
[07:59] <didrocks> oh no, it's not
[07:59] <didrocks> it's an old one
[07:59] <didrocks> well, it should be invalid, not sure why david set it
[07:59] <didrocks> the eventloop is totally different in natty
[08:00] <pitti> jasoncwarner: hang on, push-to-talk button broken; fixing
[08:05] <didrocks> pitti: do you have an handy link to the Release note?
[08:05] <didrocks> I'll document the "no panel" cases
[08:06] <pitti> didrocks: https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverview
[08:07] <pitti> didrocks: merci
[08:07] <didrocks> pitti: thanks :)
[08:14] <didrocks> ok, should be descriptive enough
[08:30] <pitti> didrocks: thanks!
[08:31] <pitti> mvo: good morning!
[08:31] <pitti> mvo: can we make another attempt at defer, or do you want me to do that?
[08:31] <didrocks> pitti: Bitte Schön (got it correctly this time? :))
[08:32] <pitti> didrocks: de rien :) (was correct, except for the capitalization)
[08:32] <didrocks> argh! ;)
[08:32]  * didrocks will add a tomboy note "how to answer to pitti" :)
[08:34] <mvo> pitti: sure, I can do it in a bit, I had hoped that glatzor would comment, but I guess its not a big deal
[08:35]  * pitti tries to hammer gir-repository to build again
[08:35] <didrocks> it's reluctant it seems :)
[08:38] <pitti> seems that seb128 threw out the dbus bindings, but they are still needed
[08:50] <rodrigo_> morning
[09:05] <pitti> hey rodrigo_
[09:05] <rodrigo_> hi pitti
[09:05] <mvo> pitti: I pushed a updated debian/copyright to https://code.launchpad.net/~mvo/python-defer/ubuntu-natty but I can not commit a COPYRIGHT.MIT (or similar) to trunk, what do you think how this should be handled?
[09:07] <pitti> mvo: the MIT/BSD license is already fully included in the source code headers
[09:07] <pitti> so a separate copy isn't needed
[09:11] <mvo> pitti: ok, then I think its ready for re-uploading
[09:11]  * pitti hugs mvo
[09:13]  * mvo hugs pitti
[09:22] <pitti> mvo: btw, did you hear about the python/gnome hackfest? http://live.gnome.org/Hackfests/Python2011
[09:22] <pitti> mvo: is that something you'd be interested in?
[09:22] <pitti> I'd really like to go
[09:23] <mvo> pitti: let me have a look
[09:23] <mvo> is it known that a upgrade with non 3d (kvm) gives you desktop with nothing (no panel, no nothing) after the upgrade to natty?
[09:25] <pitti> jasoncwarner: ^ I'll reply to Barry's email about the python hackfest; I just got pinged by one of the initiators, they'd like me to join
[09:26] <mvo> bug #683531 - pretty unusable
[09:26] <ubot2> Launchpad bug 683531 in gnome-panel (Ubuntu) "panel not there after maverick -> natty upgrade (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/683531
[09:27] <mvo> pitti: hm, server is not responding, odd
[09:27] <didrocks> mvo: look at https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverview
[09:28] <didrocks> no 3D or "none effect" selected?
[09:28] <seb128> hello
[09:28] <didrocks> hey seb128
[09:28] <pitti> mvo: hm, indeed, dropped out for me as well
[09:28] <seb128> sorry I'm a bit late this week
[09:28] <seb128> having a start of a cold so I overslept a bit
[09:28] <pitti> hey seb128
[09:28] <mvo> didrocks: aha, ok. well, default
[09:29] <pitti> oh, hope you feel better soon!
[09:29] <seb128> thanks ;-)
[09:29] <pitti> mvo: http://people.canonical.com/~pitti/tmp/hackfest.html
[09:29] <pitti> ^ temporary copy
[09:29] <seb128> it's already a bit better after some extra hours in bed
[09:29] <didrocks> tare care seb128 :)
[09:29] <seb128> just my head hurting a bit now
[09:30] <mvo> didrocks: hmmmm, could we at least show a zenity dialog?
[09:30] <mvo> seb128: oh? cold?
[09:30] <seb128> mvo, not sure, feeling a bit dizy and head hurting a bit
[09:30] <mvo> get well seb128
[09:31] <seb128> pitti, why do you have that copied on your people site?
[09:31] <didrocks> mvo: we discussed that with seb128 and was thinking it's good enough for alpha1…
[09:31] <seb128> mvo, thanks ;-)
[09:32] <didrocks> but seems that a lot of people is starting whinning about it :)
[09:32] <mvo> well, I disagree with that, a lot of people will try it in a VM
[09:32] <mvo> but *shrug*, not my call
[09:32] <seb128> what is the issue?
[09:32] <didrocks> seb128: the fact the gnome-panel isn't started if you are in metacity
[09:32] <mvo> upgrading/running without 3d
[09:32] <mvo> https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/683531
[09:33] <ubot2> Launchpad bug 683531 in gnome-panel (Ubuntu) "panel not there after maverick -> natty upgrade (affects: 1) (heat: 6)" [High,New]
[09:33] <pitti> seb128: server currently doesn't respond
[09:33] <pitti> mvo, seb128: ah, seems it's back up now
[09:33] <seb128> pitti, oh ok, you are thinking to go there?
[09:33] <didrocks> mvo: the thing is that it will be hackish and tricky… and you can have the ubuntu classic session
[09:33] <pitti> seb128: I'd love to
[09:33] <pitti> seb128: just sent out the reply and request
[09:33] <didrocks> mvo: a workaround for alpha1 that we will remove later isn't maybe the best call, that was the conclusion
[09:34] <seb128> pitti, it's a short trip for you :-)
[09:34] <pitti> indeed
[09:35] <seb128> didrocks, mvo: is the concern that there is no way to logout to start a GNOME session in the 2d case?
[09:36] <mvo> yes, no way to logout plus no indication what is going on
[09:36] <didrocks> seb128: from people bug's report, there are surprized about having an "empty desktop"
[09:37] <seb128> well it's only a1...
[09:37] <seb128> you can click on the ubiquity icon on the desktop to install
[09:38] <seb128> starting the installed system will give you gdm where you can pick the classic session if you do vm testing
[09:38] <seb128> it's a bit annoying but people trying an alpha1 should be able to deal with that?
[09:39] <mvo> like I said, its not the end of the world, but I expected that we can do better. we launch compiz, right? and if that does not run then there is no way to use unity? so why not hook into that, we did that before
[09:40] <didrocks> mvo: read https://lists.ubuntu.com/archives/ubuntu-desktop/2010-November/002689.html
[09:41] <didrocks> and for alpha2, we will have a new gnome-session backport with a different mecanism
[09:41] <seb128> mvo, well the issue was raised last week for comments on the list but nobody came with a suggestion...
[09:41] <seb128> mvo, I agree it's suboptimal but it's not an easy issue
[09:42] <seb128> mvo, part of it is that fallbacking from unity to compiz is still using compiz but in different modes
[09:42] <seb128> mvo, well, fallbacking to another wm is one thing, starting other components is another one...
[09:44] <seb128> I guess we could display a "3d not supported, you need to logout"
[09:44] <seb128> with a "logout" button on the dialog
[09:46] <mvo> I'm not asking for fallback and coolness, just a zenity dialog in gnome-wm if launching compiz fails and we are in ubuntu-desktop session. is that really more than "if [ "$GDMSESSION" = "unity" ] -a [ "$WINDOW_MANAGER" = "/usr/bin/comiz" ]; then zenity --info "fail"
[09:47] <mvo> (well, fail should probably have a little bit more text ;)
[09:47] <mvo> I can hammer out a dirty proof of concept patch, I think the 30min it takes to write it is well spend, even if we throw it away later
[09:47] <didrocks> seb128: we can run gnome-panel in that case…
[09:47] <mvo> or that :)
[09:48] <didrocks> that was part of my proposal, but doing that for removing it later…
[09:48] <seb128> mvo, that doesn't solve the case where unity doesn't work but compiz can be used
[09:48] <mvo> that is added sugar, i will be happy with just a dialog
[09:48] <didrocks> and doesn't solve last case, right
[09:48] <mvo> right, its not 100% solution, just 80%
[09:48] <mvo> how often is it that compiz works and unity dosn't? it seems the majority of people will just have no 3d at all (vm, nvidia)
[09:49] <seb128> do we still use gnome-wm?
[09:49] <mvo> (at least that is the assumption I have)
[09:49] <didrocks> mvo: gnomewm isn't called if people choose "none effect"
[09:49] <didrocks> mvo: it's directly metacity
[09:49] <seb128> we don't care about much about corner cases
[09:49] <seb128> let's just make starting the iso in a vm work
[09:49] <mvo> seb128++
[09:49] <mvo> didrocks: hmmmmm
[09:50] <seb128> didrocks, do we still use gnome-wm by default?
[09:50] <seb128> I though you wanted to change that?
[09:50] <didrocks> seb128: yes, by default
[09:50] <seb128> ok
[09:50] <seb128> mvo, go for your cheap hack ;-)
[09:50] <didrocks> that's why I proposed the cheap hack yesterday :)
[09:50] <mvo> what is the gdmsession name for it?
[09:50] <didrocks> mvo: gnome
[09:50] <mvo> ha! my hack is even more cheap than yours ,)
[09:51] <seb128> lol
[09:51] <mvo> thanks
[09:51] <didrocks> just the dialog?
[09:51] <didrocks> or gnome-panel?
[09:51] <seb128> didrocks, I didn't understand that yesterday
[09:51] <didrocks> seb128: oh sorry then :)
[09:51] <pitti> argh, gir-repository is a mess
[09:51] <seb128> didrocks, I though your fallback was not as trivial as adding 2 lines to gnome-wm
[09:51] <didrocks> so, we won't handle upgrade… just new install with no 3D
[09:51] <pitti> I threw three patches at it, each of which just uncovers the next build failure
[09:51] <seb128> didrocks, I though you would be hacking sessions or compiz
[09:51] <didrocks> seb128: well, we will have to remove that then… but just keep that in mind
[09:52] <mvo> zenity  --info --text "sorry, no 3d, your computer sucks, thnxbye"
[09:52] <seb128> pitti, stop wasting time on that
[09:52] <seb128> pitti, we should remove the source
[09:52] <seb128> pitti, I just didn't have time to rebuild all the things build-depending on it yet
[09:52] <didrocks> mvo: do you want to do it? I can do it if needed
[09:52] <seb128> pitti, we have nothing in the archive which needs it
[09:52] <pitti> seb128: ok, I'll rather do that then
[09:52] <mvo> didrocks: lets make a deal, i give you what I have and you make it work :) its probably jsut a couple of minutes, especially if you have the test env
[09:53] <seb128> pitti, all the gir it builds are unused
[09:53] <didrocks> mvo: tell them to switch to the gnome-classic session
[09:53] <didrocks> mvo: ok :)
[09:53] <seb128> pitti, there is only some source coming from debian which build-depends on gir-repository-dev because debian didn't build the gir from gtk itself etc
[09:53] <seb128> pitti, we just need to update those build-depends in ubuntu
[09:53] <seb128> pitti, I started last week and got half of main done
[09:53] <pitti> seb128: ok; sorry that I wasted an hour on this
[09:54] <mvo> thanks seb128 and didrocks!
[09:54] <seb128> mvo, didrocks: thanks ;-)
[09:54]  * seb128 hugs didrocks mvo pitti
[09:54]  * didrocks hugs mvo seb128 pitti :)
[09:54] <mvo> didrocks: if you make it work by calling gnome panel or something crarzy, fine wiht me too
[09:54]  * mvo hugs the gang didrocks pitti seb128
[09:55] <didrocks> mvo: let's call gnome-panel as well and tell "hum, you should change your session as well" :)
[09:55] <seb128> pitti, sorry I should have commented on the bug saying that
[09:55] <pitti> no problem
[09:55] <fta> pitti, hi. everywhere i have calibre/natty, i see bug 669430, do you?
[09:55] <ubot2> Launchpad bug 669430 in apt-xapian-index (Ubuntu) "update-apt-xapian-index crashes with "InvalidArgumentError: Term too long (> 245): XSlibdevel" (affects: 1) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/669430
[09:55] <didrocks> (a second, on a call)
[09:56] <pitti> fta: I haven't noticed that yet; let me run it manually
[10:00] <mvo> didrocks: cool, I msged you the quick hack I did in between the irc chat
[10:01] <njpatel> mvo, update-apt-xapi takes 10minutes everyday at 100% cpu
[10:02] <pitti> seb128: I added tasks for the remaining rdepends
[10:02] <seb128> pitti, ok
[10:03] <mvo> njpatel: hm, that used to be a weekly job :/
[10:04] <mvo> njpatel: what machine are you using? slow/fast? netbook?
[10:04] <njpatel> mvo, natty, with 2.4ghz Intel core 2, 4gb ram, Intel SSD
[10:04] <fta> it's not particularly fast on a brand new quad core either
[10:05] <mvo> njpatel, fta: hm, not fast, but 10min seems excessive on my (similar speced) system its more like 1min
[10:06] <mvo> njpatel: are you using the latest apt in natty? we had a slow version in for a couple of days
[10:06] <mvo> time (on ssd): real	0m56.247s
[10:06] <mvo>  
[10:06] <mvo> (for my system)
[10:07] <njpatel> mvo, not sure, let me update and then I'll let you know if it still happens tomorrow :)
[10:07] <njpatel> mvo, thanks
[10:08] <mvo> njpatel: ok, hunt me down if the latest apt does not fix it
[10:08] <mvo> eh, remind me gently I mean
[10:09] <njpatel> no, hunt you down!
[10:10] <seb128> pitti, I've assigned some of the tasks for this gir bugs, I will clean some of the others today
[10:11] <pitti> seb128: I'm also doing a few of them right now
[10:11] <seb128> pitti, ok, I will let you do those you want to do
[10:12] <seb128> pitti, I got blocked for a few last week due to build issues with the new vala gir stacks
[10:12] <seb128> pitti, I will pick later remaining ones if you let some ;-)
[10:14] <pitti> hm, seems gir stuff is quite broken in current sid :(
[10:18] <seb128> pitti, the gir version is 0.6 there
[10:18] <seb128> which is ages old for gir
[10:19] <pitti> I'll just fix it in Ubuntu for now
[10:19] <njpatel> erm, should installing software-centre hang apt?
[10:19] <seb128> they don't build the gir from sources as well
[10:19] <njpatel> 18214 root      20   0  268m  84m  11m R  101  2.2   2:52.34 update-software
[10:19] <seb128> so they still need to use gir-repository-dev
[10:19] <seb128> pitti, you can get fixes in experimental I guess
[10:19] <njpatel> oh, wait, it works!
[10:19] <seb128> pitti, the gir stack is mostly uptodate there
[10:20] <pitti> ah
[10:20] <seb128> there = experimental
[10:24] <pitti> seb128: so for libgdata I'd like to update to 0.7.0, which fixes building the GIR; it's an ABI bump, though
[10:24] <pitti> seb128: is there a reason not to do it, and instead fix the gir build locally? (it's easy to do)
[10:24] <seb128> oh please do it
[10:25] <seb128> it was on my list of upgrade we need to do
[10:25] <seb128> was -> is
[10:25] <seb128> it fixes some evolution google calendar integration issues it seems
[10:25] <pitti> ok, nice
[10:25] <pitti> seb128: I'll upload it, but won't binNEW before alpha-1
[10:25] <seb128> ok
[10:25]  * pitti uses lp:ubuntu/libgdata
[10:26] <fta> pitti, so, did it crash for you too?
[10:26] <pitti> fta: no, apparently not
[10:26] <fta> hm
[10:27] <fta> mvo, any idea? bug 669430
[10:27] <ubot2> Launchpad bug 669430 in apt-xapian-index (Ubuntu) "update-apt-xapian-index crashes with "InvalidArgumentError: Term too long (> 245): XSlibdevel" (affects: 1) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/669430
[10:27] <rodrigo_> hey seb128
[10:27] <seb128> rodrigo_, hey
[10:27] <rodrigo_> seb128, the version of the g-keyring package in the PPA is wrong
[10:28] <seb128> rodrigo_, how so?
[10:28] <rodrigo_> seb128, it should be 2.92.91.is....
[10:28] <seb128> gnome-keyring 	2.92.92.is.2.91.2-0ubuntu2~build2 	Rodrigo Moya (2010-11-22)
[10:28] <rodrigo_> 2.92.92.is.2.91.xxx
[10:28] <seb128> rodrigo_, ?
[10:29] <seb128> that's what I see on https://edge.launchpad.net/~ubuntu-desktop/+archive/gnome3-builds
[10:29] <rodrigo_> hmm
[10:29] <rodrigo_> oh, I got confused by gnome-bluetooth
[10:29] <seb128> right
[10:29] <seb128> I screwed and uploaded to natty
[10:29] <seb128> I fixed natty but I had to run after that
[10:29] <seb128> I will fix the ppa now
[10:29] <seb128> thanks for the reminder
[10:30] <seb128> I will sponsor your pending updates as well
[10:30] <mvo> fta: I have a look, looks like it reading the section in some funny way
[10:30] <rodrigo_> no problem, and sorry for the confusion :)
[10:30] <rodrigo_> g-bluetooth failed building, seems it still needs gconf
[10:30]  * rodrigo_ submits a fixed branch
[10:30] <seb128> rodrigo_, can you fix the version in the changelog as well? ;-)
[10:30] <seb128> I will review and sponsor that
[10:31] <rodrigo_> seb128, what is wrong in the version?
[10:31] <seb128> rodrigo_, <rodrigo_> seb128, it should be 2.92.91.is....
[10:31] <rodrigo_> ah, that was for gnome-keyring, sorry
[10:31] <seb128> hum
[10:31] <seb128> I'm really confused now ;-)
[10:31] <seb128> which one requires gconf?
[10:31] <rodrigo_> g-bluetooth
[10:32] <seb128> and g-bluetooth has the buggy version as well
[10:32] <seb128> so I was suggesting you could fix both issues while you are at it :p
[10:32] <rodrigo_> it has the buggy version?
[10:32]  * rodrigo_ looks
[10:32] <seb128> that discussion becomes weird
[10:34] <seb128> rodrigo_, sorry let's start that discussion again
[10:34] <rodrigo_> :)
[10:34] <rodrigo_> yes
[10:34] <seb128> rodrigo_, did you have a version issue? you pinged about g-k but said you confused it with gnome-bt
[10:35] <seb128> the gnome-bt is the ppa is older than the natty one
[10:35] <seb128> since I did a 2.91...is..2.32 in natty to fix the wrong upload
[10:35] <rodrigo_> right
[10:35] <seb128> g-k should be ok
[10:35] <rodrigo_> yes
[10:35] <seb128> rodrigo_, so we need to fix gnome-bt to update the version and use gconf
[10:35] <seb128> right?
[10:35] <rodrigo_> update it to what, 2.91.2.is.2.91.2?
[10:37] <rodrigo_> right, ok, now I get it, didn't see the version in natty
[10:37] <rodrigo_> so, you uploaded the PPA one to natty?
[10:38] <seb128> rodrigo_, yes
[10:38] <rodrigo_> ok, so I'll call it 2.91.2.is.2.91.2-0ubuntu1
[10:38] <seb128> I was in a call and cleaning at the same time and I did dput at the wrong location
[10:38] <seb128> that had to happen :p
[10:38] <rodrigo_> :)
[10:43] <seb128> rodrigo_, g-s-d... should I wait for .1?
[10:43] <seb128> "Handle rename of org.gnome.media-handling"
[10:43] <seb128> rodrigo_, cosimoc fixed that and tagged a .1
[10:44] <rodrigo_> yes, packaging it in a minute, so yeah, don't merge/upoload the branch
[10:44] <seb128> ok
[10:46] <rodrigo_> seb128, the bluetooth one -> https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/gnome-bluetooth/add-missing-gconf/+merge/42343
[10:47] <rodrigo_> submitting the g-s-d in a bit
[10:47] <seb128> rodrigo_, thanks
[11:07] <rodrigo_> seb128, g-s-d pushed also
[11:07] <seb128> rodrigo_, ok
[11:08] <cjwatson> https://launchpad.net/ubuntu/+source/empathy/2.32.2-0ubuntu1/+build/2061085 is failing because libebook1.2-dev doesn't depend on libcamel1.2-dev but its pkg-config file lists camel-1.2.  however, that dependency was missing in maverick too.  am I missing something?
[11:15] <seb128> cjwatson, libebooks Requires: libedataserver-1.2 dbus-glib-1
[11:15] <seb128> cjwatson, that's the 2.30 .pc
[11:15] <didrocks> pitti: for the detection fallback, it will need a new compiz upload. I can maybe sneak the OOo fix as well. Do you think it's ok
[11:15] <seb128> cjwatson, so I guess that dependency is new in 2.32
[11:16] <cjwatson> seb128: ah, right
[11:16] <seb128> does that need to be fixed for a1?
[11:16] <seb128> ie now
[11:16] <didrocks> seb128: cjwatson ^^
[11:16] <seb128> or just in the next upload?
[11:16] <cjwatson> so http://paste.ubuntu.com/538605/ then?
[11:16] <didrocks> in that case, I'll sneak the compiz upload as well :)
[11:16] <cjwatson> powerpc isn't a blocker for alpha-1, it would just be nice for me to stop getting failure mails
[11:17] <seb128> cjwatson, seems fine, feel free to commit to the vcs and upload if you want
[11:17] <cjwatson> didrocks: what's this upload for?
[11:17] <seb128> cjwatson, ups, control.in
[11:17] <seb128> cjwatson, not control ;-)
[11:17] <cjwatson> there isn't a control.in
[11:17] <didrocks> cjwatson: people running a fresh install without 3D acceleration got a session with metacity and no panel
[11:18] <didrocks> cjwatson: this will be a temporary workaround as the correct fix with a new gnome-session will come from A2
[11:18] <cjwatson> I'm OK with that
[11:18] <didrocks> it will still not deal people upgrading with "metacity" set by default (they will have no panel in the "gnome" session)
[11:18] <seb128> cjwatson, sorry I got confused with other pkg-gnome sources
[11:18] <pitti> didrocks: sure, as long as you don't introduce ABI breaks during the A1 prep time
[11:18] <seb128> cjwatson, so feel free to commit and upload if you want
[11:18] <cjwatson> http://launchpadlibrarian.net/59868659/buildlog_ubuntu-natty-powerpc.ubuntuone-client_1.5.0-0ubuntu1_FAILEDTOBUILD.txt.gz is broken too, haven't investigated yet
[11:18] <cjwatson> seb128: ok, will do, thanks
[11:18] <seb128> cjwatson, we will probably do an upload this week anyway if you want to wait
[11:19] <didrocks> pitti: the OOo fix doesn't, I checked that
[11:19] <cjwatson> I'll upload it now, would be a bonus if powerpc started to work
[11:19] <didrocks> and my workaround is small, just building the package and testing in vb
[11:20] <didrocks> (so, just to warn again, this doesn't deal with people upgrading having a wm != gnomewm or compiz, typically those selecting "none effect" in the capplet)
[11:21] <seb128> cjwatson, let me check for the ubuntuone-client issue
[11:21] <cjwatson> I'm test-building it on davis now
[11:22] <cjwatson> same issue I think
[11:22] <cjwatson> PKG_CHECK_MODULES(NAUTILUS, [libnautilus-extension >= 2.6.0 libebook-1.2 gconf-2.0])
[11:23] <cjwatson> if I install libcamel1.2-dev, that comes out with a proper GTK include path
[11:23] <seb128> cjwatson, I'm wondering what was bringing gtk in
[11:23] <cjwatson> the entire pkg-config command fails there
[11:24] <cjwatson> (if camel-1.2.pc isn't installed)
[11:25] <cjwatson> so e.g. libnautilus-extension.pc's 'Requires: ... gtk+-2.0' didn't take effect
[11:25] <seb128> cjwatson, ok, the configure should stop on such errors
[11:25] <seb128> seems a bug in their source as well
[11:25] <cjwatson> yeah, both that and empathy
[11:25] <didrocks> let's try to spawn a warning as well
[11:25] <seb128> cjwatson, but isn't PKG_CHECK supposed to bail out on error?
[11:26] <cjwatson> it ought to, yes, I don't know why it isn't
[11:27] <cjwatson> ah, I think I see
[11:27] <seb128> "the default action-if-not-fault will end the execution with an error for not having found the dependency. "
[11:27] <cjwatson> it doesn't fail if pkg-config --exists works but pkg-config --cflags fails
[11:27] <cjwatson> i.e. the .pc is broken (from its point of view) not merely missing
[11:27] <seb128> oh, ok...
[11:28] <seb128> it's a bit confusing
[11:28] <seb128> cjwatson, thanks for investigating those issues ;-)
[11:30] <cjwatson> no problem.  I can't fix the KDE/powerpc failures but maybe I can at least make Ubuntu work :)
[11:33] <mpt> pitti, hi, how often are the burndown charts updated? Once a day?
[11:35] <pitti> mpt: every two hours mostly; changes in team memberships are only updated daily, thogh
[11:35] <mpt> pitti, so if one's not being updated, should I report a bug somewhere, or ask you, or something else?
[11:36] <cjwatson> didrocks: let me know when you've uploaded compiz, please?
[11:38] <pitti> mpt: you should ping a WI tracker developer, such as me or apw
[11:39] <mpt> pitti, ok. On <https://blueprints.launchpad.net/ubuntu/+spec/packageselection-foundations-n-ratings-and-reviews-in-software-center>, the first item has been INPROGRESS for about three days, but still shows up as "todo" on <http://people.canonical.com/~platform/workitems/natty/canonical-ux.html>.
[11:41] <didrocks> cjwatson: sure, just 20 minutes, time to build + test
[11:41] <didrocks> thanks :)
[11:48] <pitti> mpt: (will look later, I have a long phone call in a few mins)
[11:49] <seb128> chrisccoulson, did you investiage the firefox, compiz issue yet?
[11:49] <seb128> chrisccoulson, do you want a bug report about it?
[11:49] <chrisccoulson> seb128 - not just yet. yeah, please open a bug report about that
[11:50] <seb128> chrisccoulson, on firefox or compiz?
[11:50] <chrisccoulson> seb128 - on firefox for now please
[11:50] <seb128> ok
[11:56] <njpatel> seb128, can you still reproduce this on latest unity? https://bugs.launchpad.net/unity/+bug/682769
[11:56] <ubot2> Launchpad bug 682769 in unity (Ubuntu) (and 1 other project) "the launcher doesn't focus minimized dialogs on empty workspaces (affects: 1) (heat: 6)" [Undecided,New]
[11:57] <njpatel> I can't seem to reproduce it at all
[11:57] <seb128> didrocks doesn't get it either
[11:57] <njpatel> on empty and non-empty workspaces
[11:57] <njpatel> seb128, but you still do?
[11:57] <seb128> not sure what is different there, I cleaned all my compiz configs
[11:57] <seb128> njpatel, yes
[11:58] <seb128> njpatel, well I didn't upgrade today yet
[11:58] <njpatel> seb128, have you got any FPS enabled?
[11:58] <seb128> but I had it yesterday
[11:58] <seb128> njpatel, fps?
[11:58] <njpatel> FSP
[11:58] <njpatel> focus strealing prevention
[11:58] <njpatel> stealing*
[11:58] <njpatel> man
[11:58] <seb128> hum?
[11:58] <seb128> I've a stock compiz
[11:58] <njpatel> I'm imagining not
[11:58] <seb128> I cleaned the .compiz* and compiz* in gconf
[11:59] <seb128> so whatever comes with it
[11:59] <njpatel> seb128, ccsm -> General Options ->Focus & Raise Behaviour -> Focus Prevention Level
[11:59] <njpatel> mine is "low"
[11:59] <seb128> low
[11:59] <seb128> but as said didrocks doesn't get it either
[12:00] <seb128> it only does it on empty workspace
[12:00] <seb128> like I'm on this workspace which has IRC
[12:00] <njpatel> yeah, I tried on empty workspace
[12:00] <seb128> I do ctrl-alt-right (next workspace is empty)
[12:00] <seb128> xchat still had the "<" to indicate it has the focus
[12:01] <njpatel> hmm, no, that's not happening here at all
[12:01] <seb128> ups, I'm confusing 2 bugs now
[12:01] <njpatel> the arrow goes away
[12:01] <njpatel> seb128, I'm going to mark this one as incomplete
[12:01] <seb128> ok
[12:02] <seb128> njpatel, sorry I was speaking about https://bugs.launchpad.net/unity/+bug/683134
[12:02] <ubot2> Launchpad bug 683134 in unity (Ubuntu) (and 1 other project) "the launcher doesn't bring you to the selected applications when it's focussed on a different ws (affects: 1) (heat: 6)" [Medium,Triaged]
[12:02] <seb128> njpatel, which is similar
[12:02] <seb128> when I described the <
[12:02] <seb128> njpatel, do you get this one?
[12:02] <seb128> I've to run for some minutes, brb
[12:03] <njpatel> seb128, nope, I don't get that one
[12:04] <njpatel> seb128, I'll mark this as incomplete until you've had a chance to test latest unity
[12:09] <htorque> seb128, do you have the "Desktop Wall" plugin enabled? without it there's no workspace switching to the focused application.
[12:10] <seb128> htorque, sure, it's the default ws switcher
[12:10] <seb128> njpatel, ok, though didrocks had it on the latest unity yesterday
[12:10] <seb128> njpatel, so I doubt it's fixed
[12:11] <njpatel> seb128, you said didrocks doesn't get it...
[12:14] <mvo> he dosn't get it, eh?
[12:15] <seb128> njpatel, he doesn't get the minimizing one
[12:15] <seb128> he gets the second one I pointed though
[12:17] <njpatel> okay
[12:18] <njpatel> I haven't got to the second one, yet
[12:18] <htorque> seb128, is the application window completely on one workspace? i can reproduce what you're seeing if there's a tiny bit of the window on the other workspace ("<" stays, click on launcher does nothing)
[12:18] <njpatel> oh, yeah, that would happen because it's spanning two
[12:19] <njpatel> htorque, hi, btw, thanks for the testing and the bug reports :)
[12:19] <htorque> yw :)
[12:22] <njpatel> htorque, do you mind if I hi-jack https://bugs.launchpad.net/unity/+bug/683547 for the edge-scrolling feature?
[12:22] <ubot2> Launchpad bug 683547 in unity (Ubuntu) (and 1 other project) "Bottom launchers hard to expand with filled launcher bar (affects: 1) (heat: 6)" [Undecided,New]
[12:22] <njpatel> (I added a comment explaining why)
[12:23] <mvo> didrocks: upgraded session works fine now with the patch you suggested, thanks a lot
[12:24] <htorque> njpatel, sure, no problem
[12:24] <njpatel> thanks
[12:24] <mvo> didrocks: I updated the bugreport as well
[12:24] <seb128> htorque, yes it's one workspace
[12:25] <seb128> like I run gconf-editor and put in the middle of a workspace
[12:25] <seb128> ctrl-alt-left
[12:25] <seb128> assuming the left one is empty
[12:25] <seb128> then click on the launcher
[12:25] <seb128> (which still has the <)
[12:25] <seb128> that doesn't bring me to the other workspace
[12:25] <didrocks> mvo: nice
[12:26] <didrocks> mvo: I close another one in the changelog
[12:26] <njpatel> seb128, just did that and it works fine, including the arrow
[12:26] <mvo> great
[12:26]  * njpatel wonders what's going on
[12:26] <didrocks> mvo: just adding the zenity dialog under the right env variable as well to avoid too many "I don't have unity" bug reports
[12:26] <htorque> seb128, wfm too, sorry :(
[12:30] <mvo> didrocks: cool
[12:30] <mvo> didrocks: great work here, that make me (and a lot of users happy, I'm sure) :)
[12:31] <didrocks> mvo: nice, we will just have to think to remove it once the new gnome-session interesting commits backported + new configuration profile there
[12:31] <mvo> didrocks: right, we should add it to google calendar so that it can mail you ;)
[12:32] <didrocks> :)
[12:50] <GunnarHj> Uploaded a revised version of the gdm package to my ppa, but it failed to build for Natty. https://launchpad.net/~gunnarhj/+archive/locale-test/+build/2071744 Someone who can look into it?
[12:50] <didrocks> cjwatson: ok, sorry, my vb was really slow, I just pushed compiz 0.9.2.1+glibmainloop2-0ubuntu4 with that + some crash fixes that a lot of people seems to get
[12:50] <didrocks> will change the Technical Overview as well, then
[12:53] <didrocks> done
[12:56] <seb128> re
[12:56] <seb128> got it!
[12:56] <seb128> njpatel, sorry I crashed gnome-session while trying to debug it and I figured I would rather not start and stop IRC while I was doing session testing
[12:56] <seb128> njpatel, ok, it happens when nautilus is not running
[12:57] <seb128> njpatel, which happens on my box due to GNOME3 library mismatches which made nautilus crash...
[12:57] <seb128> didrocks, ^
[12:57] <didrocks> seb128: ahah! you are not running the default :p
[12:57]  * didrocks runs…
[12:57] <didrocks> ok, make sense now why I couldn't get it
[12:58] <didrocks> weird that nautilus is impacting this though
[12:58] <njpatel> seb128, you mean the arrows or raising the minimised window?
[12:59] <seb128> njpatel, both
[12:59] <njpatel> seb128, can you add that to the bug report and mark it new please, I'll take a look and assign to jason
[12:59] <njpatel> seb128, thanks
[13:00] <seb128> njpatel, thank you
[13:00] <didrocks> well, even triaged if you want me to confirm
[13:01] <didrocks> (not sure why people getting back from triaged to confirmed, for me triaged > confirmed as only triagers can set that state, not a big difference though…)
[13:01] <seb128> didrocks, can you try by unsetting the draw background?
[13:02] <didrocks> seb128: sure, one sec, finishing marking some duplicates and get back to that
[13:08] <didrocks> seb128: confirmed :)
[13:08] <seb128> \o/
[13:08] <didrocks> you're not alone :)
[13:08] <didrocks> do you have the bug # handy?
[13:14] <seb128> didrocks,
[13:14] <seb128> https://bugs.launchpad.net/unity/+bug/683134
[13:14] <ubot2> Launchpad bug 683134 in unity (Ubuntu) (and 1 other project) "the launcher doesn't bring you to the selected applications when it's focussed on a different ws (affects: 1) (heat: 6)" [Medium,Triaged]
[13:14] <didrocks> seb128: thanks, confirming
[13:15] <seb128> didrocks, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/682769
[13:15] <ubot2> Launchpad bug 682769 in unity (Ubuntu) (and 1 other project) "the launcher doesn't focus minimized dialogs on empty workspaces (affects: 1) (heat: 6)" [Undecided,New]
[13:15] <seb128> as well
[13:15] <didrocks> seb128: hum? wasn't it the minimize issue?
[13:15] <didrocks> ok :)
[13:15] <didrocks> for the first one, I got it with or without nautilus drawing the desktop
[13:15] <seb128> ok
[13:18] <mvo> pitti: jockey-gtk crashes for me on natty? know - or should I start debugging
[13:18] <cyphermox> is it a known issue for compiz to segfault after a few minutes logged in?
[13:19] <rodrigo_> new gnome-keyring for the gnome3 ppa -> https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/gnome-keyring/2_91_3_release/+merge/42356
[13:20] <rodrigo_> seahorse coming
[13:20] <didrocks> cyphermox: depends on graphic card and some software issues. You can first try to upgrade to -0ubuntu4 and report a stacktracec if it's happens
[13:21] <didrocks> (this version should be built/published soon)
[13:21] <cyphermox> didrocks, thanks
[13:21] <cyphermox> I can wait.. nothing stops me from switching to a text vt and attempt to restart it ;)
[13:21] <seb128> rodrigo_, ok
[13:21] <didrocks> hehe
[13:22] <didrocks> seb128: btw, the other kind of crash are x damage errors, from what dbarth__ told me, it's frequent on intel and ati and nvidia didn't get them
[13:22] <didrocks> seb128: I think I should start testing on intel then…
[13:22] <didrocks> (that would explain why I only get few crashes a day)
[13:22] <seb128> didrocks, xdamage errors sound like something which would end in an xerror
[13:22] <seb128> not in a segfault
[13:22] <seb128> no?
[13:23] <didrocks> seb128: right, but apparently, compiz try to catch it and got confused
[13:23] <didrocks> that's about the limited of my X protocole knowledge, don't get too high :)
[13:23] <seb128> didrocks, I don't think it's the crashes I get
[13:24] <seb128> the stacktrace has only compiz and glibmm functions
[13:24] <seb128> nothing x-ish
[13:24] <didrocks> seb128: ok, so this kind of crashes should be fixed by the new upload
[13:24] <seb128> do you have an example of stacktrace on thos xdamage errors?
[13:24] <didrocks> seb128: dbarth__ have them
[13:24] <seb128> didrocks, ok great, I will let you know how it works
[13:24] <didrocks> seb128: there is none in LP
[13:24] <didrocks> nice :)
[13:25] <mvo> pitti: pushed (trivial) fix to lp:~mvo/jockey/mvo, let me know if I should just commit directly to trunk
[13:27] <seb128> mvo, that location is not valid?
[13:28] <mvo> https://code.launchpad.net/~mvo/jockey/mvo
[13:28] <mvo> its still crashing :) but now at a different spot
[13:29] <seb128> mvo, ok, it's there now
[13:29] <seb128> was maybe a launchpad being slown
[13:29] <mvo> probably
[13:29] <mvo> or my network a bit slow
[13:31] <dbarth__> seb128: this is an example stack trace: http://pastebin.ubuntu.com/538304/
[13:31] <dbarth__> seb128: and here is the one i reported this morning: https://bugs.launchpad.net/unity/+bug/683523
[13:31] <ubot2> Launchpad bug 683523 in compiz (Ubuntu) (and 1 other project) "compiz crashed with SIGSEGV in CompPlugin::windowInitPlugins() (affects: 1) (heat: 8)" [High,Confirmed]
[13:31] <seb128> dbarth, thanks
[13:32] <seb128> hum, no retracing yet?
[13:32] <seb128> let me see if those crashed
[13:34] <cjwatson> didrocks: righto, thanks
[13:35] <didrocks> cjwatson: you're welcome
[13:41] <dbarth> seb128: do you have a new build with your fix?
[13:42] <seb128> didrocks, ^ I think that was for you
[13:42] <didrocks> dbarth: hum, new build for what and for which componenent? :)
[13:43] <dbarth> unity?
[13:43] <dbarth> compiz, sorry
[13:43] <dbarth> i thought you were talking about glibmm fixes that went in
[13:44] <didrocks> dbarth: well, there is the glibmm fix which is built and should be published soon
[13:44] <didrocks> it will be in A1
[13:45] <dbarth> ok, i'll wait for this one to upgrade my system and see if that does anything to my problems
[13:45] <dbarth> there is a glibmm func in the stack, but i'm not expecting it to be the culprit
[13:47] <didrocks> let's see, right
[13:47] <didrocks> weird in any case that unity/compiz is strong there for the two last weeks (since the bamf issue is fixed)
[13:56] <mvo> hrm, hrm, so what is it in gnome-session that sets my screen forcefully to 800x600 on nvidia?
[13:56] <seb128> mvo, cat .config/monitors.xml?
[13:57] <mvo> seb128: what wrote that in the first place?
[13:57] <mvo> I killed it now, that helped
[13:57] <mvo> thanks seb128!
[13:57] <mvo> didrocks: so how to debug if unity is not starting on a nvidia upgraded system :) ?
[13:57] <mvo> nautilus is there
[13:58] <didrocks> mvo: compiz is there?
[13:58] <pitti> mvo: re (sorry, long phone interview)
[13:58] <pitti> mvo: no, I don't know
[13:58] <seb128> mvo, you're welcome
[13:58] <mvo> pitti: I filed (two) bugs and a branch, should be trivial the crash
[13:59] <pitti> mvo: "AttributeError: 'NoneType' object has no attribute 'record'"?
[13:59] <mvo> not sure about the other one
[13:59] <seb128> mvo, the display capplet
[13:59] <nessita> seb128: hey there! question, will ubuntuone-control-panel make it to alpha1? (https://launchpad.net/ubuntu/natty/+queue?queue_state=0&queue_text=control-panel)
[13:59] <seb128> mvo, system, preferences, display
[13:59] <mvo> seb128: why did it do that? I don't think I asked for this :)
[13:59] <seb128> nessita, hey, no
[13:59] <seb128> mvo, because you runned it?
[13:59] <seb128> mvo, it's a capplet, nothing that can do anything without you opening it and changing your resolution
[13:59] <mvo> didrocks: ha! compiz was it
[13:59] <seb128> mvo, because it assumes that you want to keep your screen config between sessions
[14:00] <pitti> mvo: seems you proposed a merge of the ubuntu branch into trunk, but I'll sort it out
[14:00] <mvo> seb128: but I never set it to 800x600 :)
[14:00] <didrocks> mvo: so, yeah, if you have metacity by default right now it's "no luck" until alpha2 :)
[14:00] <mvo> pitti: hrm, sorry
[14:00] <pitti> mvo: don't worry; thanks for the fix!
[14:00] <seb128> mvo, well what was in that .xml when you cleaned it?
[14:00] <didrocks> mvo: I posted a note in the technical overview
[14:00] <milanbv> has somebody experienced a bug in which GDM changes users list order randomly across reboots?
[14:01] <seb128> nessita, I don't think it will, that was uploaded after the freeze
[14:01] <pitti> mvo: ah, did the returned exception change recently in python-apt? I've never seen that before
[14:01] <pitti> mvo: and now it seems to crash everywhere
[14:01] <nessita> seb128: when was the freeze?
[14:01] <seb128> nessita, monday
[14:01] <mvo> seb128: 800x600 was in it I *think*
[14:02] <mvo> seb128: but that does not make sense, does it?
[14:02] <seb128> mvo, well, you must have ran gnome-display-properties some day
[14:02] <mvo> didrocks: ok, that is fine, thanks for your help
[14:02] <pitti> mvo: merged and pushed, thanks! trying now
[14:02] <seb128> mvo, and played with it
[14:02] <didrocks> mvo: yw :)
[14:02] <pitti> mvo: so you have another crash?
[14:02] <mpt> mvo, hi, what was the original link for that remove vs. purge Brainstorm idea?
[14:02] <mvo> seb128: ok
[14:02] <nessita> seb128: ah, ok
[14:02] <nessita> thanks for the info!
[14:02] <seb128> nessita, no problem
[14:03] <mvo> pitti: that was a side effect of the earlier one. the api changed insofar that package.candidate can be None now
[14:03] <mvo> mpt: the original is http://brainstorm.ubuntu.com/idea/24963/
[14:03] <pitti> mvo: ah, right; that explains why it's an attributeError now
[14:03] <mpt> thanks
[14:04] <mvo> no alt-f2 anymore :/
[14:04] <pitti> mvo: ctrl-alt-t for the rescue
[14:04] <mvo> pitti: yeah, you could test for if package.candidate, whaever style you prefer
[14:04] <mvo> pitti: dosn't work for me neither
[14:04] <pitti> AttributeError: 'Backend' object has no attribute 'handlers'
[14:04] <pitti> mvo: ^ I now get this
[14:04] <pitti> looks unrelated
[14:05] <mvo> odd, I had this too
[14:05] <pitti> or it's because of some local g-i hackery I've been doing, checking
[14:05] <mvo> but then a couple of minutes later it went away
[14:05] <pitti> mvo: ah, of course; the old backedn was still running
[14:05] <pitti> (dbus service)
[14:05] <mvo> pitti: yeah
[14:05] <pitti> all fine now
[14:05]  * pitti hugs mvo
[14:05] <mvo> great
[14:05]  * mvo hugs pitti
[14:06] <mvo> hm, and clicking on the hud does open a nautilus window with /usr/share/applications ?
[14:06] <mvo> (the thing in the left top corner)
[14:06] <pitti> mvo: oh, it does for you? clicking on the icon just unhides the launcher for me
[14:07] <mvo> odd
[14:07] <mvo> focus-follow-mouse & global-menu is not a good fit :)
[14:08] <pitti> mvo: bug 674138
[14:08] <ubot2> Launchpad bug 674138 in unity ""Global" appmenu breaks sloppy focus (affects: 8) (heat: 42)" [Low,Triaged] https://launchpad.net/bugs/674138
[14:09] <seb128> mvo, <mvo> hm, and clicking on the hud does open a nautilus window with /usr/share/applications ?
[14:09] <seb128> mvo, that's right
[14:09] <pitti> mpt: ah, we usually don't consider "inprogress" different from "todo" on the charts
[14:09] <seb128> mvo, the dash is not done yet
[14:09] <seb128> that's for a2
[14:09] <pitti> mpt: whoever implemented this made this optional
[14:10] <pitti> (since for the point of burndowns it's irrelevant)
[14:10] <pitti> I'm not too fussed either way, we can just globally enable it
[14:10] <mpt> pitti, I think if that was the problem, the item would be showing up as "in progress" in the table. But it's showing up as "todo" there too.
[14:10] <didrocks> mvo: it's just a workaround for you to start apps :)
[14:10] <pitti> mpt: right, that's what I mean
[14:10] <pitti> mpt: I'd prefer if "in progress" wasn't even there on any of the charts/reports
[14:11] <mvo> oki, thanks guys! I have a working unity & compiz now
[14:11] <pitti> mpt: but *shrug*, I'll just remove the configurability and turn it on globall
[14:11] <pitti> y
[14:12] <mpt> pitti, I don't really mind either way. But if "in progress" is supposed to show up identical to "todo", the chart legend shouldn't shows it with a different color.
[14:40] <mterry> TheMuso, hello!  What do I have to do to get gtk3 apps to show up in accerciser today?  I thought it would be install libatk-adaptor and at-spi2-core, but no go
[15:08] <rodrigo_> seb128, not proposing this for merge, as there is no ubuntugtk3 branch -> https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/seahorse/2_91_2_release
[15:09] <seb128> rodrigo_, ok, I'm done with other things, catching up on GNOME
[15:09] <seb128> GNOME3 now
[15:09] <rodrigo_> seb128, or can you just create the branch from the ubuntu one?
[15:09] <seb128> sorry for the backlogging
[15:10] <seb128> rodrigo_, what do you mean?
[15:10] <seb128> rodrigo_, I will get yours and push as ubuntugtk3
[15:11] <rodrigo_> ah, ok
[15:11] <rodrigo_> I just meant if you could just push lp:~u-desktop/seahorse/ubuntu to ubuntugtk3, so that I could propose this branch for merging into ubuntugtk3
[15:11] <seb128> oh right
[15:11] <seb128> will do that, that's better ;-)
[15:11] <rodrigo_> but as you want
[15:11] <rodrigo_> ok
[15:26] <bilalakhtar> seb128: updates opened? Seahorse being updated?
[15:26] <seb128> bilalakhtar, what?
[15:27] <seb128> it's the gnome3 ppa
[15:27] <seb128> rodrigo_, btw I pushed it
[15:27] <bilalakhtar> seb128: Can I make packages for the PPA?
[15:27] <rodrigo_> bilalakhtar, please :)
[15:27] <seb128> if you want to
[15:27] <bilalakhtar> of course I want to :)
[15:27] <rodrigo_> seb128, to ubuntugtk3?
[15:27] <seb128> rodrigo_, yes
[15:28] <rodrigo_> seb128, ok, proposing my branch for that then
[15:28] <rodrigo_> seb128, https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/seahorse/2_91_2_release/+merge/42375
[15:29] <seb128> rodrigo_, thanks
[15:29] <rodrigo_> bilalakhtar, then, see http://people.canonical.com/~platform/desktop/versions.html and pick what you want :-)
[15:29] <seb128> (hate url hanging the applications in natty)
[15:29] <bilalakhtar> thanks rodrigo_
[15:30] <rodrigo_> bilalakhtar, note that most modules don't have a ubuntugtk3 branch, so ask someone to push the ubuntu one to ubuntugtk3 so that you can propose merges
[15:30] <bilalakhtar> rodrigo_: okay then
[15:47] <seb128> rodrigo_, hum, did you build seahorse?
[15:47] <rodrigo_> yes
[15:47] <seb128> weird
[15:47] <rodrigo_> running it also
[15:47] <seb128> patching file configure.in
[15:47] <seb128> Hunk #1 FAILED at 50.
[15:47] <seb128> 1 out of 1 hunk FAILED -- saving rejects to file configure.in.rej
[15:47] <seb128> I get this
[15:47] <rodrigo_> hmm
[15:48] <rodrigo_> I didn't get that
[15:49] <rodrigo_> seb128, in 01_lpi.patch?
[15:49] <seb128> yes
[15:49] <seb128> you didn't update it
[15:49] <seb128> it's still having gtk2 etc
[15:49] <rodrigo_> hmm
[15:49]  * rodrigo_ rebuilds
[15:49] <rodrigo_> hmm, patches are not being applied here, it seems
[15:49] <cdbs> lpi -> LP integration?
[15:50] <rodrigo_> hmm, how so?
[15:50] <rodrigo_> cdbs, yes
[15:50] <seb128> rodrigo_, how do you build?
[15:50] <rodrigo_> bzr bd ...
[15:51] <seb128> it has a series
[15:51] <rodrigo_> yes
[15:51] <rodrigo_> not sure why they're not applied
[15:52] <rodrigo_> hmm, maybe it needs simple-patchsys include or a build dep on quilt?
[15:54] <mterry> seb128, I'm thinking I'll update anjuta and gedit in natty after alpha1, but I wanted to ask you a question about packaging re: gedit.  It now includes a private shared library, libgedit-private.so.  I've been putting it in the same package as the gedit executable.  I'm not sure yet why it's a shared library, as it (predictably) doesn't seem for outside use.  But I assume it's reasonable to stick it in the same package and not creat
[15:54] <mterry> e a libgedit-private?
[15:56] <rodrigo_> seb128, will look at it later, I need to go now for a while, so bbl
[15:56] <seb128> mterry, I would stick it in to start
[15:57] <seb128> mterry, we can still create a new binary if a need comes later on
[15:57] <seb128> rodrigo_, ok
[15:57] <seb128> rodrigo_, <rodrigo_> hmm, maybe it needs simple-patchsys include or a build dep on quilt?
[15:57] <seb128> rodrigo_, no, it's using source v3
[15:57] <seb128> which does quilt by default
[15:57] <mterry> seb128, true
[15:57] <seb128> doing a bzr do there does the right thing
[15:57] <seb128> mterry, the new gedit is using gtk3 I guess?
[15:58] <mterry> seb128, right
[15:58] <seb128> mterry, is there anything which should make us be careful about it?
[15:59] <mterry> seb128, I've been using it for a while, and 2.91.2 is in the PPA for testing.  I'm about to put .3 in there.  All plugins need to be rewritten.  And we'll probably want to sort theme and a11y issues as/before it drops
[15:59] <seb128> like having it read settings in gsettings where we will probably not get the new g-c-c and g-s-d
[15:59] <mterry> seb128, my point about using it for awhile is that it is reasonably stable on its face.  So the issues are just the plugins and general gtk3 issues like theme and a11y
[16:00] <seb128> I'm rather concerned about desktop settings it might read
[16:00] <mterry> seb128, I haven't noticed any such gsettings use.  Let me do a more intensive search
[16:00] <seb128> thanks
[16:02] <mterry> seb128, the filebrowser plugin does use external gsettings from nautilus and from desktop-gsettings
[16:02] <mterry> seb128, but not the main exec
[16:03] <mterry> seb128, nope, I lied.  It also uses some of those
[16:03] <seb128> do we need the new gedit for the new anjuta?
[16:04] <mterry> seb128, it uses lockdown and interface schemas from desktop-gsettings
[16:04] <mterry> seb128, no.  they were just the two gtk3 apps I was mostly working on
[16:04] <seb128> mterry, I would put gedit in the ppa for now
[16:04] <seb128> I don't think locking keys are an issue
[16:04] <pitti> good night everyone
[16:04] <seb128> we don't have an editor for those anyway
[16:05] <seb128> and the value will be migrated from gconf on update
[16:05] <seb128> pitti, 'night
[16:05] <dpm> hi pitti, I'm trying to see if the new maverick language packs from yesterday's export are building ok, so that we can start testing them in -proposed. I'm looking at https:/launchpad.net/~ubuntu-langpack/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=maverick and I can't see any pending a build. Is there any way to check out if they're building ok?
[16:05] <mterry> seb128, I thought we had ported the new desktop gsettings stuff.  I remember the package hitting NEW. Is it just a question of UI (gnome-control-center?)
[16:05] <pitti> dpm: you can pick any of the packages in the PPA and check if they have a recent date, and built ok
[16:05] <pitti> they are all uploaded at the same time
[16:06] <pitti> dpm: and I get mail if they fail to build, too (I didn't get any)
[16:06] <seb128> mterry, we have gsettings-desktop-schemas in
[16:06] <dpm> pitti, I can only see the ones from last week
[16:06] <seb128> mterry, the issue is for things which can be edited by gnome-control-center
[16:07] <kenvandine> looking at porting gwibber from gconf to gsettings... man we have some ugly code in here for our gconf settings
[16:08] <mterry> seb128, ok, well, I'll only do anjuta for now
[16:08] <seb128> mterry, we will probably not get the ppa updates in natty proper this cycle
[16:08] <seb128> mterry, well land gedit in the ppa anyway
[16:08] <seb128> mterry, the plan for now is to get GNOME3 in the ppa
[16:08] <seb128> we will decide at the rally if we move that to natty or not
[16:08] <mterry> aw bummer
[16:09] <pitti> dpm: ah, the run on Nov 27 failed
[16:09] <pitti> dpm: I have the log, will investigate tomorrow morning
[16:09] <mterry> seb128, so should I bother pushing anjuta to natty, or does it not matter so much since it's universe and sorta standalone
[16:09]  * pitti waves
[16:09] <seb128> mterry, what is bummer? not taking GNOME3 yet?
[16:10] <seb128> mterry, sorry it's not easy, but it turns out we can't take easily pieces of GNOME3 without taking everything
[16:10] <seb128> mterry, and we don't think we will be able to have great GNOME3 integration in one cycle
[16:11] <seb128> still lot of work upstream to do
[16:11] <seb128> lot of patches to port
[16:11] <seb128> things that changed and for which we need to figure what to do
[16:12] <seb128> so likely lot of work, and we are not sure we will have time for that and unity
[16:12] <mterry> seb128, yar, I wasn't depressed or anything about it, but it will probably exacerbate the tension over unity within GNOME
[16:13] <seb128> well we do what we can in the ppa and we welcome contributions
[16:13] <dpm> pitti, thanks, we'll talk about it tomorrow. Weird, according to the schedule at https://dev.launchpad.net/Translations/LanguagePackSchedule, the build should have started today, and not on the 27th
[16:13] <seb128> if it's ready on time it will land in natty
[16:13] <seb128> mterry, you can argue that using the ppa makes work easier
[16:13] <seb128> we don't have to stop on freezes, etc
[16:13] <seb128> we can get extra contributors there
[16:14] <mterry> seb128, yar
[16:14] <seb128> mterry, about anjuta, your call, land it in the ppa if you are unsure
[16:14] <mclasen> seb128: heh, we welcome contributions too
[16:14] <mterry> seb128, it's in PPA for now, no rush really
[16:15] <seb128> mclasen, no discussion about that ;-)
[16:15] <seb128> mclasen, I was stating that it's easier to contribute to the ubuntu-desktop ppa than to land updates in Ubuntu proper
[16:15] <seb128> different acls, etc
[16:15] <seb128> it's less restrictive
[16:15] <seb128> so easier to get extra people having access
[16:16] <seb128> mclasen, that was an ubuntu organization comment, nothing against upstream or other distros
[16:16] <mclasen> I didn't take it that way, anyway
[16:16] <seb128> ok ;-)
[16:19] <cyphermox> seb128, could you update the topic if the versions page is now under the platform user on p.c.c?
[16:22] <cyphermox> thanks :)
[16:22] <seb128> ok, got it :p
[16:22] <cyphermox> hehe
[16:22] <seb128> cyphermox, thanks for pointing it
[16:22] <seb128> cyphermox, hey, how are you btw?
[16:22] <cyphermox> pretty good
[16:23] <cyphermox> just hopefully finished discussing how to fix some issues in NM with mbiebl, going back to the thousands of session erros nm-applet spews out :/
[16:23] <seb128> great work recently, I think you made quite some people happy ;-)
[16:23] <cyphermox> seb128, ahah, i'll only be happy when it doesn't use 1G of RAM at the end of the day :)
[17:06]  * mterry looks into hacking on the unity source for the first time
[17:10]  * jasoncwarner likes mterry looking into hacking on the unity source...wishes him luck!
[17:13] <didrocks> jasoncwarner: mterry: that's quite easy for the preferences settings :)
[17:13] <didrocks> and for the basic compiz stuff
[17:13] <didrocks> then, came nux
[17:13] <didrocks> and that's where it becomes horrible :)
[17:15] <seb128> mterry, is the workspace switcher a workspace "switcher"?
[17:15] <seb128> or is it an expose mode where you might want to dnd things around?
[17:23] <didrocks> mterry: if I remember, left click is what you look for
[17:23] <didrocks> mterry: in any case, it's the compiz wall plugin you want hack in
[17:23] <didrocks> not unity
[17:44] <and471> mpt, <kvalo> hi. you asked about wifi signal yesterday
 the values can be between 0 and 100
 so yes, value 100 is very well possible
[17:46] <mpt> so it can't be greater than 100
[17:46] <and471> yup
[17:47] <mpt> Hm, I still don't think we need the background or border :-)
[17:47] <and471> mpt, if you pull my branch, I have added in the signal indicator stuff
[17:47] <and471> it needs a bit of polish but it is working
[17:48] <mpt> nice
[17:51] <and471> :)
[17:56] <and471> mpt: I am just worried of a situation like http://imagebin.org/125630 where there are similar signal strengths
[17:57] <and471> mpt, without the background bar there isn't enough context in my mind
[17:57] <and471> whereas with it: http://imagebin.org/125631
[17:57] <and471> mpt, I know this is not a common situation but it highlights my point
[17:58] <mpt> and471, do you think that the background bar makes it easier to see which of those three is strongest?
[17:58] <and471> mpt, well they are actually all the same, I rigged them :)
[17:58] <mpt> They look the same to me either way
[17:58] <mpt> uh-huh
[17:58] <mpt> So, what do you mean by context?
[17:58] <and471> mpt, what I think it does is show what they represent better
[17:59] <and471> i.e. what it could be, what is is, how good it is compared to what it could be
[17:59] <mpt> You mean, shows that they're gauges, as opposed to odd blobs?
[17:59] <and471> mpt, yes almost, but I also feel with the background it conveys more information, which I feel would eb useful for the user
[18:00] <mpt> and471, http://images.google.com/images?q=equalizer
[18:01] <mpt> Hardly any of them show where the maximum is, but it's obvious that they're gauges, because of the ||||||||| pattern they use.
[18:01] <and471> mpt, I appreciate your point, however i feel that is different, as there is more than one bar and they are constantly changing
[18:02] <and471> the user can work out the maximum and other information due to the other bars and the change in height
[18:02] <and471> whereas our gauge is static
[18:02] <mpt> Here, it's from the column width.
[18:02] <mpt> but, meh
[18:02] <mpt> minor point
[18:03] <mpt> I was thinking about how to present proxies
[18:03] <mpt> and thinking of some extension of the current Gnome location menu in the proxy settings window
[18:03] <and471> mpt, hehe, I think we will need more input from other on this point of gauges :)
[18:03] <and471> mpt, ok
[18:03] <mpt> but not sure entirely how to do it yet
[18:04] <and471> well I have no clue either :)
[18:04] <and471> tho I don't use a proxy server
[18:04] <mpt> A proxy for just one particular network is easy
[18:04] <mpt> Proxy for: [ This connection          :^]
[18:05] <and471> yeah
[18:05] <mpt> A proxy for all connections that don't have specific proxies is easy
[18:05] <mpt> Proxy for: [ All other connections          :^]
[18:05] <and471> mpt, yeah it is when you have those two data sources, per device and per location
[18:05] <mpt> The hard part is how to share a proxy across, for example, Ethernet and wi-fi connections at an office, but not other places
[18:05] <and471> it is hard to get them to combine well
[18:07] <and471> mpt, well have fun thinking about that, I have to go now :)
[18:07] <and471> mpt, see ya (I know you'll think of something good) :D
[18:07] <mpt> likewise
[18:18] <mterry> seb128, the switcher is a switcher in my mind.  But surely we can tell between a drag and a click and support both.  I just don't see the point in preferring the ability to adjust the z-order of windows to actually switching
[18:19] <seb128> mterry, you have a point, I've been confused as well by having to double click
[18:19] <seb128> I was just wondering if some of things you can do in the overview mode wouldn't work in the simple click case
[18:19] <seb128> and if we care
[18:19] <mterry> seb128, yar
[18:20] <seb128> if it activates on click release I guess you can still do dnd etc
[18:20] <seb128> so it should be fine for both usecase
[19:09] <bcurtiswx> seb128, BGO bug 636232 is my nautilus crash, FYI.  it's been upped to critical, so i'm assuming they didn't know about it until today
[19:09] <ubot2> Launchpad bug 636232 in xserver-xorg-input-synaptics (Ubuntu) "Touchpad appears as ImPS/2 Logitech Wheel Mouse (affects: 1) (heat: 49)" [Low,Invalid] https://launchpad.net/bugs/636232
[19:10] <bcurtiswx> gnome bug 636232
[19:10] <ubot2> Gnome bug 636232 in general "Nautilus crashes with SIGSEGV in nautilus_window_get_preferred_width" [Critical,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=636232
[19:16] <bcurtiswx> did I kill seb128 again ?
[19:42] <mterry> w00t first unity patch
[19:48] <highvoltage> hi! is there a good reason for ubuntu-desktop to depend on unity?
[19:49] <highvoltage> as apposed to recommending it?
[19:51] <highvoltage> unity needs to be optional in edubuntu, and that gets tricky when edubuntu-desktop depends on ubuntu-desktop in natty
[19:55] <mterry> TheMuso, ping about at-spi for gtk3
[20:29] <ari-tczew> omg... new gnome style is horrible!
[20:30] <highvoltage> ari-tczew: I guess whatever you're seeing is probably just unthemed
[20:31] <ari-tczew> highvoltage: dunno. just upgraded all packages (since a couple of days my natty was outdated). I'd like to back into 2 panels ;(
[20:31] <ari-tczew> I'm lost at the gnome
[20:33] <bcurtiswx> anyone know if not having nautilus-sendto would cause nautilus to crash ?
[20:34] <highvoltage> ari-tczew: yeah there's quite a lot of transition going on atm
[20:35] <ari-tczew> highvoltage: I hope that it will be better soon. if it's a final result, Ubuntu users could leave using linux!
[20:35] <cyphermox> bbl
[20:36] <highvoltage> ari-tczew: it's a bunch of big transitions (involving compiz, gnome and unity) during an early alpha, I don't think anyone rational would expect it to be anything resembling a final product :)
[20:37] <ari-tczew> highvoltage: I have to reconsider back to maverick.
[20:37] <highvoltage> ari-tczew: I made that mistake too and re-installed last night
[20:38] <ari-tczew> highvoltage: mistake?
[20:38] <TheMuso> mterry: Just ask your question and I will respond when I am around.
[20:38] <TheMuso> mterry: But I am here now, so shoot.
[20:38] <highvoltage> ari-tczew: dist-upgrading before checking the state of things
[20:39] <mterry> TheMuso, I asked it this morning (my time), was just pinging (apparently uselessly :)) again.   "TheMuso, hello!  What do I have to do to get gtk3 apps to show up in accerciser today?  I thought it would be install libatk-adaptor and at-spi2-core, but no go"
[20:40] <TheMuso> mterry: Sorry just saw that in my away log. Yes you need at-spi v2, and you also have to make sure at-spi v2 is the version used, by setting a gconf key. Let me grab the key you need, and things should just work once you are running the new stack.
[20:41] <TheMuso> mterry:
[20:41] <TheMuso> /desktop/gnome/interface/at-spi-dbusmt/desktop/gnome/interface/at-spi-dbus
[20:42] <TheMuso> gah
[20:42] <TheMuso> mterry: /desktop/gnome/interface/at-spi-dbus
[20:42] <TheMuso> that is the gconf key you need to set. You then need to log out and back in again.
[20:42] <mterry> TheMuso, awesome, will try.  Thanks!
[20:43] <TheMuso> np
[20:43] <TheMuso> When we move to at-spi over dbus exclusively, this will no longer be needed, but this allows both stacks to co-exist.
[20:43] <mterry> gotcha
[20:45] <TheMuso> ~/c
[20:51] <mterry> TheMuso, it seems python-pyatspi2 (which accerciser now needs) is missing a dependency on python-xlib
[20:51] <Sarvatt> can anyone tell me what should be in /desktop/gnome/session/required_components/panel for a unity session?  i'm stuck with " breaking things
[20:51] <mterry> mterry, but worked besides that.  Thanks!
[20:52] <TheMuso> mterry: Hrm I thought I fixed that...
[20:52] <james_w> Sarvatt, I have '' on maverick
[20:53] <htorque> Sarvatt, it's the same here
[20:53] <htorque> but compiz/unity works for me
[20:53] <TheMuso> mterry: Seems not...
[20:53] <Sarvatt> hmm
[20:53] <Sarvatt> I get this after the latest round of updates today, compiz doesn't even try to start http://pastebin.com/m1cAUkMg
[20:54] <TheMuso> mterry: mterry So install it for now and see if that helps.
[20:55] <TheMuso> gah my typing si already sucking today, and its the morning.
[20:55] <mterry> TheMuso, yeah, I did install and it works
[20:55] <TheMuso> Ok, will fix pyatspi then.
[20:55] <Sarvatt> ah maybe it was the /desktop/gnome/session/required_components/windowmanager being metacity screwing it up
[20:56] <mterry> TheMuso, I got several tracebacks from pyatspi2 though when running accerciser if you're interested.  An AttributeError and a ValueError
[20:56] <Sarvatt> yep that was the problem, thanks guys
[20:56] <htorque> Sarvatt, i have windowmanager = compiz and /desktop/gnome/session/required_components_list does not contain panel
[20:57] <TheMuso> mterry: Upstrea would be interested.
[20:57] <TheMuso> upstream
[20:57] <TheMuso> I don't know pyatspi internals myself, so would only be forwarding straight upstream.
[20:57] <mterry> OK
[21:00] <rickspencer3> hey all
[21:00] <rickspencer3> so it seems that perhaps the current image that we wanted to release tomorrow for A1 may not be working for folks
[21:00] <rickspencer3> mterry, TheMuso, bryceh, who ever is around
[21:00] <mterry> rickspencer3, hiyo
[21:01] <rickspencer3> could I ask you guys to create an image and see if it runs?
[21:01] <rickspencer3> join #ubuntu-testing and report the results
[21:01] <rickspencer3> ?
[21:01] <mterry> rickspencer3, OK
[21:01] <vish> rickspencer3: from today's iso, it seems like Bug 683840 …
[21:01] <ubot2> Launchpad bug 683840 in compiz (Ubuntu) "compiz crashed with SIGSEGV in nux::ResourceData::GetResourceIndex() (affects: 3) (dups: 3) (heat: 34)" [Medium,New] https://launchpad.net/bugs/683840
[21:02] <vish> or maybe you are mentioning a whole new different bug.. :)
[21:02] <rickspencer3> vish, I dunno
[21:03] <mterry> rickspencer3, we're talking Desktop image 20101201.1 ?
[21:03] <rickspencer3> mterry, I believe so, yes
[21:04] <TheMuso> Sure.
[21:04]  * TheMuso goes and downloads.
[21:07] <bryceh> rickspencer3, sorry I'm patch pilot today
[21:07] <rickspencer3> bryceh, ack
[21:07] <rickspencer3> bryceh, good call, btw
[21:07] <rickspencer3> the correct response!
[21:08] <rickspencer3> :)
[21:08] <bryceh> :-)
[21:08] <htorque> bug 683840 looks like bug 682345
[21:08] <ubot2> Launchpad bug 683840 in compiz (Ubuntu) "compiz crashed with SIGSEGV in nux::ResourceData::GetResourceIndex() (affects: 3) (dups: 3) (heat: 34)" [Medium,New] https://launchpad.net/bugs/683840
[21:08] <ubot2> Launchpad bug 682345 in unity (Ubuntu) (and 3 other projects) "SEGSEGV in nux::ResourceData::GetResourceIndex() const () (affects: 2) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/682345
[21:24] <vish> htorque: how did you identify which were the missing .desktop files?
[21:32] <htorque> vish, http://launchpadlibrarian.net/59743520/console.log
[21:32] <vish> ah ha!
[21:42] <ari-tczew> wrrrrrrrrrrrrrr, kadu doesn't work on latest gnome
[21:45] <htorque> vish, i see this in those apport bugs: ** (<unknown>:3469): WARNING **: Unable to load GDesktopAppInfo for 'ubuntuone-control-panel-gtk.desktop'
[21:46] <htorque> so this would cause the segfault in the live cd, once installed you'd probably see the same with this entry and i guess also ubiquity-gtkui.desktop
[21:46] <vish> htorque: where did you add the files?
[21:47] <Sarvatt> oddly I have no segfault with those two warnings http://pastebin.com/t9CdZspX
[21:47] <htorque> oh
[21:48] <htorque> vish, i did not add them, i removed them from the launcher's favorites list (using gsettings)
[21:52] <htorque> vish, 'gsettings get com.canonical.Unity.Launcher favorites' to get the current list
[21:52] <htorque> vish, 'gsettings set com.canonical.Unity.Launcher favorites "['a', 'b', 'c']"' to write
[21:52] <vish> yea.. just having a look at it..
[21:52] <seb128> htorque, does that fix it?
[21:53] <htorque> it fixes it on my installation, not sure about the iso
[21:54] <htorque> alex launi confirmed it in bug 682345
[21:54] <ubot2> Launchpad bug 682345 in unity (Ubuntu) (and 3 other projects) "SEGSEGV in nux::ResourceData::GetResourceIndex() const () (affects: 5) (dups: 4) (heat: 48)" [Undecided,Confirmed] https://launchpad.net/bugs/682345
[21:54] <vish> that's lamalex
[21:54] <seb128> htorque, ok, thanks
[21:54] <htorque> vish, thanks :)
[21:55] <htorque> but it's odd that Sarvatt doesn't get the crash with those messages :-/
[21:56] <Sarvatt> ['ubiquity-gtkui.desktop', 'nautilus.desktop', 'firefox.desktop', 'ubuntuone-control-panel-gtk.desktop', 'tomboy.desktop', 'gnome-terminal.desktop', 'evolution.desktop', 'cheese.desktop', 'pidgin.desktop', 'yelp.desktop']
[21:57] <vish> nope.. removing them does *not* fix the issue..
[21:58] <vish> i removed the 2 mentioned in the bug..
[22:02] <Sarvatt> turns out its the '/home/ubuntu/Desktop/examples.desktop' on the livecd for vish
[22:02] <Sarvatt> (sorry, discussion was split between two channels)
[22:03] <seb128> Sarvatt, other people on #ubuntu-testing get it fixed by removing the 'ubuntuone-control-panel-gtk.desktop' entry
[22:07] <Sarvatt> would it matter that his examples entry didn't have a space in front of it? <vish>  ['ubiquity-gtkui.desktop', 'nautilus.desktop', 'firefox.desktop', 'ubuntuone-control-panel-gtk.desktop', 'tomboy.desktop','/home/ubuntu/Desktop/examples.desktop']
[22:07]  * Sarvatt is clueless about it
[22:08] <vish> Sarvatt: i typed it in xchat.. so i might have missed a space :)
[22:08] <vish> the AOA is a separate lappy..
[22:16] <Amaranth> well dang
[22:16] <Amaranth> unity and nux crash bugs are going to go to compiz
[22:18] <seb128> easy to fix
[22:18] <seb128> we can make a "if crash is in unity.so report on unity"
[22:18] <seb128> tweak apport to be clever on the stacktrace
[22:18] <seb128> we do that for nautilus for example
[22:19] <seb128> if it crashes in something in /usr/lib/nautilus it assign to the corresponding source
[22:19] <Amaranth> Although with the current setup the unity folks have to look through compiz bugs so it's not all bad
[22:19] <seb128> right
[22:20] <seb128> we can still do better with apport
[22:20] <Amaranth> wow, 12MB of stacktrace
[22:20] <Amaranth> my browser is crying
[22:20] <Amaranth> nux seems to be carrying static color data around everywhere, that seems bad
[22:21] <Amaranth> IndianRed, Salmon, etc
[22:21] <Amaranth> Either that or gdb isn't reading things correctly
[22:22] <Amaranth> considering the message about stack corruption that seems likely
[22:22] <vish> ! yay.. nm applet's been ported to indicator!
[22:22] <ubot2> vish: Error: I am only a bot, please don't think I'm intelligent :)
[22:23] <vish> silly stupid bot's been bothering me all day today.. :/
[22:28] <Sarvatt> RAOF: did you see https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/683361 ? not sure if you were hitting that on r600
[22:28] <ubot2> Launchpad bug 683361 in mesa (Ubuntu Natty) (and 3 other projects) "compiz crashed with SIGSEGV in radeon_bo_get_tiling() (affects: 1) (heat: 10)" [Medium,Triaged]
[22:28] <RAOF> Sarvatt: No, that's not what I'm hitting.
[22:29] <RAOF> I'm hitting a SIGSEGV in the mipmapping bug on edgers (because I'm testing on cedar)
[22:29] <RAOF> But that bug also happens on edgers on r700, so...
[22:29] <Sarvatt> there is also http://cgit.freedesktop.org/mesa/mesa/commit/?h=7.9&id=773e8fadc8b19aaba5d13f75ac5810badb3968c4
[22:29] <Sarvatt> ah on edgers too? gotcha
[22:32] <RAOF> Right.
[22:32]  * Amaranth throws random things at launchpad
[22:32] <RAOF> Because we'll be switching to mesa 7.10, I might as well test it and fix what I can there :)
[22:34] <Sarvatt> RAOF: are you getting [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! in dmesg when it happens?
[22:34] <RAOF> No.
[22:34] <RAOF> It's trying to dereference a null pointer.
[22:35] <Amaranth> I've now spent 10 minutes trying to get launchpad to let me do what should be a 30 second process
[22:36] <seb128> which is?
[22:36] <seb128> robert_ancell, hey
[22:36] <robert_ancell> seb128, hello
[22:36] <seb128> robert_ancell, how are you?
[22:36] <Amaranth> It finally let me sign in!
[22:36] <robert_ancell> seb128, good
[22:36] <Amaranth> I was trying to mark a bug as a dupe
[22:37] <Amaranth> We got a bit flooded with compiz bugs today :/
[22:37] <seb128> that's only the start with unity using it ;-)
[22:38] <seb128> robert_ancell, I noticed you changed shotwell to use vala 0.10...
[22:38] <robert_ancell> seb128, yes
[22:38] <seb128> robert_ancell, is that a temporary hack?
[22:38] <seb128> robert_ancell, you are abusing a soyuz bug there in some way :p
[22:38] <robert_ancell> seb128, well, it didn't build anymore, and the patch required to make it work with 0.12 is non-trivial
[22:38] <seb128> ok
[22:39] <seb128> I was wondering if replace vala-0.10 with the new one was the best thing to do
[22:39] <seb128> rather than adding a new source
[22:39] <robert_ancell> but it's something I'll need to take up with upstream, as we can't keep using 0.10 indefinitely
[22:39] <seb128> since the 2 versions can be installed together
[22:39] <seb128> 0.10 binaries should not be available in the archive since nothing build those
[22:39] <robert_ancell> yes, we should have two source, I didn't think of that at the time
[22:39] <seb128> ok
[22:39] <seb128> I will check with slomo what he does for debian
[22:40] <robert_ancell> though, the issue is the other libraries, as they only install one .vapi file - so they're all installing them into 0.12 atm
[22:40] <seb128> so we can maybe get back on sync with sources naming
[22:40] <robert_ancell> Ideally we'd just like to drop 0.10 and forget about it...
[22:40] <seb128> robert_ancell, if any source does that it should be fixed
[22:40] <Amaranth> "Application error.  Unauthenticated user POSTing to page that requires authentication."
[22:40] <Amaranth> Screw you Launchpad. Go die in a fire.
[22:40] <seb128> robert_ancell, vapi should be installed in the non versioned dir
[22:40] <robert_ancell> seb128, but what is the correct behaviour?  Libraries are not going to support two versions of vala
[22:41]  * Amaranth gives up on it
[22:41] <robert_ancell> seb128, and what if they use a feature that's not available in the old version?
[22:41] <seb128> robert_ancell, ok, in this case they should be in the new version
[22:41] <seb128> but we don't have many in this case now
[22:41] <seb128> do we have any out of vala itself?
[22:41] <Amaranth> This would be much simpler if libraries shipped their own vapi
[22:43] <robert_ancell> Amaranth, they do, but they're built using vapigen normally.  So they may be dependant on a certain version of vala
[22:43] <robert_ancell> seb128, hmm, I see gexiv2 and lightdm on my system
[22:43] <robert_ancell> I think there's something else - where is the policy that says they should be in the unversioned location?
[22:43] <seb128> robert_ancell, ok, one is for shotwell and the other one is yours ;-)
[22:43] <seb128> robert_ancell, dunno if there is a policy
[22:44] <robert_ancell> seb128, I have a feeling there are some others (which I would have done), but I can't remember
[22:44] <seb128> we had the discussion on the IRC channel when they did the versioning last cycle
[22:44] <seb128> robert_ancell, we did undo a bunch of those you moved
[22:44] <seb128> like dee
[22:44] <robert_ancell> Amaranth, but yes, it would be nice to get rid of the ones that valac provides
[22:44] <seb128> on the upstream #vala channel I mean
[22:44] <robert_ancell> seb128, ah, that would be it - you should have told me off!
[22:44] <seb128> upstream said that everything should be in the non versioned dir if there is not a strong reason to version it
[22:44] <robert_ancell> ok, I'll fix my stuff
[22:45] <seb128> robert_ancell, sorry, one of those things that slept through because we don't overlap much
[22:45] <seb128> robert_ancell, like I wanted to tell you off for dropping a symbol from gtk .symbol and uploading ;-)
[22:46] <seb128> robert_ancell, never drop a symbol, it's an abi break ;-)
[22:47] <robert_ancell> seb128, oh, that's ok with gtk+3 right though?
[22:47] <robert_ancell> yeah, my bad with gtk2 (or was it glib?)
[22:48] <seb128> robert_ancell, gtk 2.23
[22:48] <seb128> the buggy version which was rolled from a wrong git
[22:49] <robert_ancell> yay, I can finally remove stuff from the unity dock (or whatever it's called)
[22:49] <seb128> robert_ancell, can you backport http://paste.ubuntu.com/538831/?
[22:49] <seb128> ups
[22:50] <seb128> bug #682345
[22:50] <ubot2> Launchpad bug 682345 in unity (Ubuntu) (and 3 other projects) "SEGSEGV in nux::ResourceData::GetResourceIndex() const () (affects: 8) (dups: 4) (heat: 60)" [Undecided,Confirmed] https://launchpad.net/bugs/682345
[22:50] <seb128> robert_ancell, ^
[22:50] <seb128> the fix I mentioned there
[22:51] <seb128> robert_ancell, I'm on a maverick laptop and can't do the update
[22:51]  * robert_ancell reading
[22:51] <seb128> robert_ancell, it's just the current revision to merge and upload
[22:51] <seb128> it's a fix for an a1 crasher
[22:51] <seb128> the unity code import the examples .desktop from nautilus
[22:52] <robert_ancell> seb128, so this is just a standard "apply patch and make a new release for natty"?
[22:52] <seb128> robert_ancell, apply and upload
[22:52] <seb128> we can sort if with didrocks tomorrow
[22:52] <robert_ancell> ok
[22:52] <seb128> if ->it
[22:52] <seb128> the vcs part
[22:52] <seb128> or merge in lp:~unity-team/unity/packaging
[22:52] <seb128> if you want to do it properly
[22:52] <seb128> though I guess you are not in the team for that
[22:52] <seb128> cyphermox, wb
[22:53] <seb128> cyphermox, robert_ancell is handling the update since he's around and has upload rights
[22:53] <robert_ancell> looks pretty safe
[22:53] <skaet_> and lets us know in #ubuntu-release that its ready to have a buuild started...
[22:53] <seb128> robert_ancell, cyphermox confirmed the fix
[22:53] <seb128> skaet_, will do
[22:53] <cyphermox> seb128, cool
[22:53] <robert_ancell> seb128, is unity packaging in bzr somewhere?
[22:53] <TheMuso> yes it is.
[22:53] <seb128> robert_ancell, cf what I just wrote
[22:54] <skaet_> seb128, robert_ancell - thanks!
[22:54] <TheMuso> ...or not
[22:54] <TheMuso> debcheckout doesn't show anything.
[22:54] <robert_ancell> seb128, oh, they have no Vcs-Bzr link, I'll fix that too
[22:54] <seb128> robert_ancell, don't
[22:54] <robert_ancell> ?
[22:55] <seb128> robert_ancell, it's pending being move to lp:ubuntu/unity
[22:55] <seb128> it's just a matter of having didrocks to catch james_w about it
[22:55] <robert_ancell> then they can update the link when they do that...
[22:55] <seb128> ok
[22:57] <cyphermox> robert_ancell, if you need testing once it's uploaded I'll be happy to help, but i may be offline for a few hours soon.
[22:57] <seb128> let's get testing with the iso once it's uploaded
[22:58] <seb128> there is also mterry who said he would be back and can test
[22:58] <robert_ancell> cyphermox, cheers, should be uploaded soon
[22:58] <cyphermox> seb128, yeah, I meant I'd get back to the iso I have burned, then upgrade
[22:59] <seb128> cyphermox, ok
[23:01]  * robert_ancell building...
[23:02] <chrisccoulson> hmmm, my washing machine has just died!
[23:02] <TheMuso> chrisccoulson: that sucks.
[23:02] <chrisccoulson> it went bang a couple of times and then popped the 15A breaker under the stairs
[23:03] <chrisccoulson> made me jump!
[23:03] <TheMuso> I'll bet.
[23:04] <jcastro> hey, did you guys notice shotwell also has an eog-esque picture viewer?
[23:05] <robert_ancell> jcastro, yup
[23:06]  * robert_ancell logs out to check new unity....
[23:07] <rickspencer3> seb128, so it seems you guys got Alpha 1 all in order
[23:07]  * rickspencer3 knocks wood
[23:07] <seb128> rickspencer3, well let's hope
[23:07] <seb128> the patch is a workaround but that will do
[23:07] <rickspencer3> what's the hope factor?
[23:07] <seb128> well the crash issue is fixed
[23:07] <seb128> not sure what other issues unity has
[23:08] <rickspencer3> you patched Unity to work around a compiz crasher?
[23:08] <seb128> but it should be enough to get it as stable as it is for people running it
[23:08] <seb128> rickspencer3, no, it's an unity crasher
[23:08]  * rickspencer3 crosses fingers
[23:08] <seb128> rickspencer3, it has migration code to import favorite launchers
[23:08] <seb128> rickspencer3, it does import the examples.desktop icon from the livecd
[23:08] <rickspencer3> aha
[23:08] <rickspencer3> so it's livecd only
[23:08] <seb128> but it doesn't like it since it's not a software
[23:09] <seb128> seems nobody tested added a non application desktop before ;-)
[23:09] <seb128> rickspencer3, yes
[23:09] <rickspencer3> I'll be happy to test the live cd later tonight
[23:09] <seb128> ok great
[23:09] <seb128> I will be to bed before livecd respins are done
[23:09] <cyphermox> I'm not certain it's livecd only...
[23:10]  * rickspencer3 join #ubuntu-release
[23:10] <rickspencer3> haha
[23:10] <seb128> cyphermox, why?
[23:10] <cyphermox> anybody who didn't remove examples.desktop would get it, no?
[23:10] <robert_ancell> seems to work...
[23:10] <seb128> cyphermox, examples.desktop is not in the default list
[23:10] <seb128> cyphermox, it's just imported from the livecd user
[23:10] <robert_ancell> seb128, cyphermox, any special testing I should do before uploading?
[23:10] <cyphermox> heh, I thought it was always installed after install
[23:10] <seb128> unity imports the .desktop from the user config to build the launcher
[23:10] <cyphermox> (or used to be)
[23:11] <seb128> on the desktop?
[23:11] <seb128> or in the user dir?
[23:11] <seb128> I though it was in the user dir
[23:11] <cyphermox> I can't recall
[23:11] <seb128> robert_ancell, no
[23:11] <cyphermox> I always remove it ;)
[23:11] <seb128> robert_ancell, it's a trivial fix, just upload ;-)
[23:11] <robert_ancell> famous last words :)
[23:11] <rickspencer3> oh man, how many times have I heard that!
[23:11]  * rickspencer3 cries
[23:12] <cyphermox> heheh
[23:12] <seb128> robert_ancell, well if you want to test the bug add a .desktop which is not a software to your launcher
[23:13] <robert_ancell> the +junk in the url for lp bzr branches makes my software feel useless :(
[23:13] <seb128> robert_ancell, http://paste.ubuntu.com/538831/?
[23:13] <seb128> robert_ancell, you can try to add that to the launcher
[23:13] <cyphermox> seb128, you are right, it would be in the user's directory, not on the desktop, from what I can tell from /etc/skel/
[23:13] <seb128> the list of launchers is in gsettings
[23:13] <seb128> just create a .desktop with it
[23:13] <seb128> cyphermox, ok, great, in any case the fix should work on the installed system as well
[23:14] <cyphermox> right
[23:14] <cyphermox> o
[23:14] <robert_ancell> seb128, how do I add to the launcher?
[23:14] <htorque> seb128, i'm still not sure how i fixed it on my installation by removing the missing .desktop entries from the launcher list - that alone doesn't seem to be a problem (eg. i removed the examples.desktop in the live session and it worked fine)
[23:14] <cyphermox> robert_ancell, btw, you can test it by putting the file from /etc/skel  on the desktop
[23:14] <seb128> robert_ancell, com.canonical.Unity.Launcher
[23:14] <seb128> robert_ancell, in gsettings
[23:15] <seb128> there is a launcher list
[23:15] <cyphermox> gsettings set com.canonical.Unity.Launcher favorites whatever
[23:15] <seb128> just add the /tmp/examples.desktop or something
[23:16] <seb128> htorque, no sure but we can investigate that tomorrow with the unity guys
[23:16] <robert_ancell> cyphermox, then restart?
[23:16] <cyphermox> huh yeah, it seems unity knows about favorites but doesn't apply the changes ;)
[23:16] <cyphermox> restart compiz
[23:16] <seb128> don't copy the .desktop only
[23:17] <seb128> the migration happens only once
[23:17] <seb128> or import
[23:17] <seb128> you need to add it manually in the list
[23:17] <seb128> robert_ancell, compiz --replace
[23:18] <seb128> robert_ancell, that should give you an empty launcher (no icon or text in it)
[23:18] <seb128> but not crash
[23:19] <robert_ancell> I get ** (<unknown>:2507): WARNING **: Unable to load GDesktopAppInfo for 'examples.desktop'
[23:19] <robert_ancell> but no crash
[23:19] <seb128> hum
[23:19] <seb128> what did you add to the list?
[23:19] <seb128> you need to path
[23:19] <seb128> or it needs to be in the xdg data dir
[23:19] <seb128> like /tmp/examples.desktop
[23:20] <robert_ancell> examples.desktop but it doesn't exist
[23:20] <seb128> it seems it just doesn't find the desktop in your case
[23:20] <seb128> right
[23:20] <robert_ancell> test
[23:20] <seb128> create a examples.desktop with the pastebin from before
[23:20] <robert_ancell> /tmp is a data dir?
[23:20] <seb128> no, but either you specify the path
[23:20] <seb128> or you put it in xdg_data_dir
[23:21] <seb128> your choice
[23:21] <seb128> I would just create a /tmp/examples.desktop
[23:21] <seb128> then add '/tmp/examples.desktop' to the gsettings list
[23:21] <robert_ancell> ok did that - black icon, no crash
[23:22] <seb128> ok great
[23:22] <seb128> it was crashing before the update ;-)
[23:22] <seb128> you can install --reinstall unity/natty
[23:22] <seb128> if you want to confirm the crash
[23:22] <seb128> but confirming the fix should be enough
[23:22] <seb128> let's upload
[23:23] <seb128> so release people can start handling the build and iso respin
[23:23] <robert_ancell> it's uploaded
[23:23] <seb128> thanks
[23:23] <robert_ancell> hmm, lp doesn't allow me to do a merge request into that branch though
[23:24] <cyphermox> ok, I'll boot back into live and wait for it to be built
[23:24] <htorque> seb128, ah, i know - it seems the migration thing has been run on my system as the 'favorite-migration' value was set - that probably added a non-app .desktop which i later overwrote by setting a new launcher list
[23:24] <robert_ancell> https://edge.launchpad.net/ubuntu/+source/unity/3.2.2-0ubuntu2
[23:24] <seb128> robert_ancell, which one?
[23:24] <seb128> robert_ancell,
[23:24] <cyphermox> wow, already done
[23:24] <seb128>   * debian/source:
[23:24] <seb128>     - Use source version 3.0
[23:24] <seb128> robert_ancell, didrocks will kill you :p
[23:25] <cyphermox> hahha
[23:25] <robert_ancell> seb128, I did a bzr pull on lp:~unity-team/unity/packaging, pushed to +junk, then tried to merge request from lp
[23:25] <seb128> robert_ancell, you can push to ~user/unity/fix
[23:25] <robert_ancell> seb128, heh, it didn't have a patch system, and I didn't want to muck around with debian/rules
[23:25] <seb128> robert_ancell, you should have applied it inline
[23:26] <seb128> robert_ancell, well the way they do is to bzr merge -c <revision>
[23:26] <htorque> seb128, yep that's it, I re-ran the migration script and compiz crashes again (with a link type .desktop file from my home dir in the list) - case closed :)
[23:26] <seb128> robert_ancell, so it's transparent
[23:26] <seb128> robert_ancell, bzr will know the fix is a merged revision and just handle it at the next update
[23:26] <seb128> htorque, ok, great
[23:26] <htorque> sorry for the noise
[23:26] <seb128> no worry
[23:26] <seb128> thanks for helping getting it fixed
[23:27] <seb128> robert_ancell, sourve v3 doesn't play nice with source in a vcs
[23:27] <robert_ancell> seb128, oh, really?
[23:27] <seb128> robert_ancell, but no worry, I was joking, I'm just sure didrocks will drop it
[23:28] <seb128> robert_ancell, yeah because it applies the patches when unpacking
[23:28] <seb128> robert_ancell, which the vcs doesn't like
[23:28] <robert_ancell> oh, that makes sense
[23:29] <seb128> so the normal way for unity is
[23:29] <seb128> bzr pull
[23:29] <seb128> bzr merge -c
[23:29] <seb128> and be done
[23:29] <seb128> robert_ancell, what error do you get when you try doing a merge request?
[23:29] <robert_ancell> what's the arg to -c
[23:29] <seb128> rev_number
[23:29] <seb128> it's to merge one revision
[23:30] <seb128> or -r if you want to merge trunk up to a revision
[23:30] <robert_ancell> it was something about the branch not being compatible, I suspect it wasn't stacking
[23:30] <seb128> well usually then
[23:30] <seb128> bzr pull lp:~unity-team/unity/packaging
[23:30] <seb128> cd packaging
[23:31] <seb128> bzr merge lp:~user/unity/yourfix (-c rev)
[23:31] <seb128> or lp:unity if it's from trunk
[23:31] <seb128> commit, be done
[23:31] <seb128> the next merge-upstream from a tarball will just know it was a trunk revision and not even ask about it
[23:31] <seb128> no patch to add or remove
[23:32] <robert_ancell> seb128, oh, so they will pull my changes in?
[23:34] <seb128> robert_ancell, "they"?
[23:34] <robert_ancell> the unity team
[23:34] <seb128> no, I explained how usually didrocks would backport a fix
[23:34] <seb128> without using source v3 or patch systems
[23:35] <seb128> I guess didrocks will manually import you changelog entry, ignore the source v3 and patches and do merge the upstream commit
[23:35] <robert_ancell> We're talking about two merges here - one pulling from the unity-team packaging branch a change from another branch, the other, requesting the released changes (i.e. the debian/changelog) are pushed back to that branch
[23:36] <robert_ancell> right, I get you now
[23:36] <seb128> well ideally you would request a merge request from lp:~robert-ancell/unity/bugfix to lp:~unity-team/unity/packaging
[23:36] <seb128> but if you say launchpad doesn't like it don't bother much
[23:36] <seb128> either drop an email to didrocks or catch him on IRC tomorrow
[23:36] <seb128> I think he starts early enough that you guys overlap a bit
[23:37] <cyphermox> things are looking good from my end -- downloaded and installed the .debs directly.
[23:37] <seb128> great
[23:42] <bcurtiswx> more going into desktop PPA ?
[23:43] <seb128> bcurtiswx, what?
[23:43] <seb128> robert_ancell, ok, thanks for helping on the unity upload
[23:43] <seb128> time to go to bed here
[23:43]  * cyphermox logs off for a while
[23:43] <seb128> bye
[23:44] <cyphermox> ciao seb128
[23:44] <bcurtiswx> seb128, j/w if there were changes going to the desktop gnome 3 ppa right now.. just anxious to get nautilus not crashing.. upstream made my bug report critical, im assuming its not known yet
[23:44] <bcurtiswx> good night seb128 :)
[23:44] <seb128> ok
[23:44] <seb128> dunno about upstream nautilus
[23:44] <seb128> it's the setting status they give to crash issues
[23:45] <seb128> you can try to check on #nautilus on irc.gnome.org
[23:45] <bcurtiswx> ah, well.  i've seen people using nautilus on unity
[23:45] <seb128> though now is probably not the perfect time for that
[23:45] <seb128> you can probably go back to the natty version
[23:45] <seb128> rather than the ppa one
[23:45] <seb128> that should work
[23:46] <bcurtiswx> well, i type sudo apt-get install nautilus/natty, and it doesn't change anything
[23:46] <seb128> you need to downgrade the library as well
[23:46] <seb128> but I'm off for today
[23:46] <bcurtiswx> easy way to go about that?
[23:46] <seb128> use synaptic?
[23:46] <bcurtiswx> yuppers, nite seb128