[00:24] <RAOF> Good morning rickspencer3!
[00:25] <rickspencer3> RAOF, good evening, actually, but yeah ;)
[00:25] <RAOF> Fun Sunday?
[00:26] <rickspencer3> RAOF, yeah, I forgot to do my notes for the dreaded "monthly report"
[00:27] <rickspencer3> figured I'd knock it out now
[00:27] <RAOF> Do you get to do an even *bigger* monthly report now/soon? :)
[00:37] <rickspencer3> RAOF, well, I have to roll up all the Ubuntu Engineering stuff into the Canonical monthly report
[00:38] <RAOF> That sounds like quite a substantal undertaking.
[00:40] <rickspencer3> RAOF, not really
[00:40] <rickspencer3> it's just like a paragraph and some stats
[00:44]  * TheMuso waves to rickspencer3.
[00:44] <rickspencer3> hi TheMuso
[00:44] <rickspencer3> hope you guys are enjoying your Monday morning
[00:44] <rickspencer3> I guess without robert_ancell though :/
[00:51] <tremolux> TheMuso, RAOF, rickspencer3: hey mates
[00:52]  * tremolux waves
[00:52] <rickspencer3> hey tremolux
[00:52] <RAOF> Hey there.
[00:52] <rickspencer3> hey tremolux I got assigned this bug today: https://bugs.launchpad.net/bugs/578045
[00:52] <ubot2> Launchpad bug 578045 in software-center (Ubuntu) (and 2 other projects) "Upgrading packaged Ubuntu application unreasonably involves upgrading entire OS (affects: 5) (heat: 30)" [Undecided,Opinion]
[00:53] <rickspencer3> I hope I handled it okay
[00:53] <tremolux> rickspencer3: I noticed that, I think you handled it well  :)
[00:53] <tremolux> rickspencer3: I think that got assigned to you because it was linked from the blueprint
[00:53] <rickspencer3> we'll see
[00:54] <rickspencer3> well, I got my report updated, oh joy!
[00:54] <rickspencer3> now off to dinner
[00:54] <tremolux> rickspencer3: and it was showing up as a work item, I didn't realize that!
[00:54] <rickspencer3> oh really?
[00:54] <rickspencer3> it shouldn't be a work item
[00:54] <tremolux> rickspencer3: yep!  so, I think you just closed out your work item
[00:54] <tremolux> I think it's automatic
[00:54] <rickspencer3> whatever ;)
[00:54] <tremolux> haha
[00:54] <rickspencer3> but I thought only certain bugs got set as work items
[00:55] <rickspencer3> but in any case, it's hardly a "work item"
[00:55] <rickspencer3> :)
[00:55] <rickspencer3> TheMuso, RAOF how are things going for you guys?
[00:55] <rickspencer3> anything I should be aware of, etc... before I take off?
[00:55] <rickspencer3> anything I could take care of for you in the morning?
[00:56] <RAOF> Nope, I'm good (but cold, so it's time to move in front of the heater)
[00:57] <tremolux> rickspencer3:  ah, looks like mpt assigned it to you...anyway, I think it's all good
[00:57] <tremolux> I'm going to dinner too, have a good dinner rickspencer3
[00:57] <rickspencer3> later guyses!
[00:57] <rickspencer3> kenvandine, hi!
[00:58] <TheMuso> rickspencer3: Well thanks, all fine here atm.
[00:59]  * TheMuso was away going through the latest batch of bug mail...
[01:00] <rickspencer3> nice
[01:00] <RAOF> Bah.   I wish people wouldn't use damn X-Fi cards...
[01:03] <RAOF> It's because creative used to make the only decent sound cards for gaming.
[01:03] <RAOF> Back in the 90s ;)
[01:03] <TheMuso> Yeah.
[01:04] <TheMuso> Onboard hda sound is fine for just about anything these days.
[01:09] <TheMuso> ...and USB audio devices are more often than not a pain for users.
[01:11] <TheMuso> Thanks to lazy manufacturers.
[01:13] <RAOF> Onboard hda does tend to have annoying analog noise, though.
[01:13] <RAOF> Because it's *clearly* not important to have the speaker/headphone/microphone jacks isolated from the random electrical noise of your system.  Like pressing keys on the keyboard.
[01:14] <TheMuso> RAOF: This is true, some board manufacturers are better than others though. From experience, gigabyte are ok with this.
[01:14] <TheMuso> i.e headphones/speakers for me on gigabyte boards don't have any hum/hiss.
[01:15] <TheMuso> At least, so far as is annoying.
[01:15] <RAOF> :D
[01:15] <RAOF> I only really care about my laptops.  Although I may buy a new desktop system to play Civ V on…
[01:16] <RAOF> It's difficult to shop around for less noisy headsets on a laptop :)
[01:16] <rickspencer3> time to go see how my update to my mini 10v went
[01:16] <rickspencer3> it's weird how out of date the stable release always seems when we get near the end of a development cycle
[01:18] <TheMuso> rickspencer3: Aint that the truth./
[01:19] <TheMuso> Especially with hardware support.
[01:19] <TheMuso> RAOF: Yeah, I haven't used any notebook other than my MBP for a while now, and it certainly doesn't leak machine noise, nore did my previous Thinkpad which had an AC97 chip.
[01:20] <RAOF> This thinkpad isn't bad; my Asus laptop is pretty poor, though.
[01:34] <rickspencer3> Are any of you guys running unity right now?
[01:35] <rickspencer3> I can't figure out how to pull down the menus with the alt keys :/
[01:35] <TheMuso> No.
[01:39] <RAOF> rickspencer3: I am.
[01:39] <rickspencer3> RAOF, couple of questions:
[01:39] <rickspencer3> 1. can you use the keyboard to use the menus?
[01:39] <RAOF> 1) No
[01:39] <rickspencer3> like, use ALT-D to pull down the documents menu
[01:39] <rickspencer3> :/
[01:39] <rickspencer3> so, how are you supposed to use the menus?
[01:39] <RAOF> With a mouse, I expect.
[01:40] <rickspencer3> 2. Does ubuntu-bug work for you on unity?
[01:40] <RAOF> DX surely have some keyboard monkeys in there, though.
[01:40] <rickspencer3> for me, programs don't seem to be able to launch other programs
[01:40] <RAOF> “ubuntu-bug unity” seems to have worked.
[01:41] <RAOF> rickspencer3: Like the terminal, for example?
[01:41] <RAOF> Do's launching stuff fine here, the messaging menu launched evolution for me, etc.
[01:41] <rickspencer3> RAOF, hold on
[01:42] <rickspencer3> like quickly edit won;t launch gedit
[01:42] <rickspencer3> and ubuntu-bug won't launch the browser
[01:43] <RAOF> Ubuntu bug has launched chromium for me fine.  Is there something screwy in your env?
[01:44] <rickspencer3> RAOF, could be
[01:44] <rickspencer3> the keyboard thing is vexing me, though
[01:44] <rickspencer3> doesn't seem to be a bug logged for it or such
[01:44] <rickspencer3> maybe there's another way I'm supposed to do it
[01:44] <RAOF> It's probably a bug.
[01:45] <RAOF> I don't use the menu very much, and don't use the keyboard shortcuts when I do; it's quite possible that it's been missed / assumed someone else will fix it / assumed it's by design / apathy'd.
[01:47] <rickspencer3> whatever
[01:47] <rickspencer3> I logged a but
[01:47] <rickspencer3> a bug too
[01:47] <rickspencer3> I'll crack the whip tomorrow when people are around
[01:50] <rickspencer3> oh man, Photobomb is too wide to fit into Unity now :,(
[01:50] <rickspencer3> and it does funny things when it's supposed to maximize
[01:51] <TheMuso> rickspencer3: No keyboard for menu access? That worries me when something as basic as that is missing.
[01:51] <rickspencer3> TheMuso, right
[01:52] <rickspencer3> though I'm not sure it's missing, it might just be different
[01:52] <TheMuso> rickspencer3: Tried the Alt + F1 or such key combination?
[01:52] <TheMuso> I.e ALT + a functino key.
[01:52] <TheMuso> gah typing
[01:53] <rickspencer3> heh
[01:53] <rickspencer3> right, some of those close windows, apparantly ;)
[01:53] <TheMuso> wah
[01:53] <TheMuso> Alt + F4 does that
[01:53] <TheMuso> or should do that
[01:53] <rickspencer3> right :)
[01:53] <TheMuso> Thats a WM function afaicr.
[01:57] <TheMuso> Man its really starting to feel like spring here today.
[01:57] <rickspencer3> well, so far this Alt key thing seems to be the only missing feature
[01:57] <rickspencer3> some buggy behavior
[01:57] <rickspencer3> but it seems to be complete
[02:01] <RAOF> TheMuso: Windy, you mean?
[02:01] <TheMuso> RAOF: No, only a light breeze. The weather itself is very mild.
[02:01] <RAOF> It was hella windy last night here.  And is today, too.
[02:01] <TheMuso> Heh its already 20 degrees.
[02:01] <RAOF> Spring, and the associated winds, have hit Hobart :)
[02:03] <rickspencer3> mutter acts funny when your app is bigger than the destkop
[02:04] <TheMuso> RAOF: Spring I like. The winds, not so much.
[02:04] <RAOF> Unity handles fullscreen windows rather nicely, though.
[02:04] <rickspencer3> you mean like when you do F11>
[02:04]  * rickspencer3 tries
[02:04] <RAOF> It must have been even windier in the mountains.
[02:05] <TheMuso> Man I really like how apport tells you what installation media was used to install Ubuntu. I find it useful when people choose to use KDe apps in Ubuntu. :)
[02:05] <TheMuso> RAOF: I am no longer in the mountains.
[02:05] <TheMuso> But yes, I believe it was.
[02:06] <RAOF> TheMuso: Yeah, I know.  My memory, while bad, isn't quite that bad :)
[02:07] <TheMuso> heh ok
[02:10] <rickspencer3> see you guys tomorrow!
[02:25] <TheMuso> RAOF: I don't envy your xorg hardware juggling act. :S
[02:25] <TheMuso> Video hardware is worse than audio in some respects.
[02:25] <TheMuso> in terms of supporting.
[02:34] <RAOF> TheMuso: Yeah, seems like.
[02:34] <RAOF> It doesn't seem like support for older audio chips degrades nearly as fast as for older video chips.
[02:34] <RAOF> Probably because they're doing less interesting things.
[02:34] <TheMuso> Right.,
[02:43] <RAOF> Time to lock my GPU again.  For science!
[02:51] <TheMuso> heh
[03:09] <RAOF> GAH!
[03:09] <RAOF> Is launchpad down, broken, or just slow?
[03:10] <lifeless> right now? we thought we had it fixed.
[03:10] <lifeless> what happened
[03:12] <RAOF> I'm trying to file a bug; it comes up with the ‘waiting for apport stuff’, then that finishes.  I entered the bug title & the initial comment, hit “submit”, and then got a non-oops launchpad sorry page.
[03:13] <lifeless> are you using edge or lpent
[03:13] <lifeless> lpnet
[03:13] <RAOF> Edge
[03:13] <lifeless> also #launchpad please
[03:31]  * TheMuso -> lunch
[03:48] <RAOF> Hm, fun bug.  Maximising a terminal crashes it.
[04:28] <TheMuso> RAOF: fun indeed.
[04:28] <TheMuso> c/
[04:29] <RAOF> :)
[07:35] <pitti> Good morning
[07:36] <pitti> RAOF: how are you?
[07:36] <RAOF> pitti: Good morning.
[07:36] <RAOF> pitti: I'm pretty well.
[07:37] <RAOF> Yourself?
[07:37] <pitti> I'm great, had a nice week of vacation
[07:38] <pitti> I just got quite puzzled this morning, my external monitor stopped working as soon as X starts
[07:38] <pitti> the only relevant upgraded package that I saw is xserver-xorg-code, but that was just dependency changes
[07:39] <pitti> and I can manually do startx, then enable both (internal and dvi) side by side, but not the external one exclusively
[07:39] <pitti> RAOF: you didn't happen to hear similar reports already?
[07:39] <RAOF> No, I haven't
[07:39] <pitti> I'll continue to track this down later
[07:39] <pitti> RAOF: ok, thanks
[07:40] <RAOF> So you can't actually disable the internal screen at all?
[07:40] <pitti> I can
[07:40] <lifeless> pitti: welcome back!
[07:41] <pitti> DVI works on VTs, fails in gdm, and starts working again if I additionally enable it to the left or right of lvds
[07:41] <pitti> hey lifeless, thank you!
[07:41] <RAOF> Aaaah, yes.
[07:41]  * pitti posted photos at http://piware.de/fotos/Donauradtour-Sep10/
[07:41] <RAOF> That seems moderately similar to what happens here, except that it's only on gdm that it's disabled.
[07:42] <RAOF> IE: it works before and after.
[07:42] <pitti> RAOF: What I'm trying to find out is what changed; it worked well before my holidays, and something in yesterday's mega-dist upgrade broke it
[07:42] <RAOF> I suspect gdm.
[07:42] <pitti> but I didn't see a new *drm*, *mesa*, etc.
[07:43] <pitti> RAOF: no, it happens with startx, too
[07:43]  * RAOF hates having to kill his session to test things!
[07:43] <pitti> gdm did change, but also in a trivial way
[07:43] <pitti> RAOF: don't worry for now, I'll collect some more info later on
[07:43] <RAOF> Ta.
[07:44] <pitti> RAOF: we so much need xscreen :)
[07:44] <RAOF> That'd be sweet :)
[07:58] <didrocks> good morning
[08:06] <pitti> hey didrocks, how are you?
[08:06] <didrocks> pitti: I'm fine, thanks :) and you? how were you holidays?
[08:06] <didrocks> your*
[08:07] <pitti> didrocks: very nice; no broken spokes or flat tires, and Vienna is really enjoyable
[08:07] <pitti> didrocks: http://piware.de/fotos/Donauradtour-Sep10/ :)
[08:09] <didrocks> pitti: waow, really cute! Seems you had both nice and bad weather during your travel though
[08:10] <pitti> didrocks: yes, mixed; but only one day with heavy rain, the rest was actually quite nice for cycling
[08:11] <didrocks> pitti: ok, so overall the right week to get there :-)
[08:12] <pitti> didrocks: absolutely; the nights were quite chilly (and thus a lot of dew in the mornings), so we didn't have breakfast outside; but that worked well, most camping sites were next to a restaurant
[08:14]  * pitti finally beat the apport retracers into submission, as it seems
[08:14] <didrocks> pitti: happy that you enjoyed it! How many kilometers were you cycling this week?
[08:14] <didrocks> ahah :-)
[08:14] <pitti> didrocks: just 340, was quite easy
[08:14] <didrocks> pitti: still something ^^
[08:15] <didrocks> pitti: Julie saw a document on Vienna. She wants to get there to eat some confectionery ;)
[08:16] <pitti> didrocks: the deserts are absolutely amazing there
[08:16] <pitti> erm, "desserts"
[08:16] <pitti> no deserts in Austria, sorry
[08:16] <pitti> that was Australia :)
[08:16] <didrocks> I think that Julie prefers desserts to deserts ;)
[08:16] <didrocks> (so am I, btw)
[08:17] <pitti> ++
[08:27] <fta> pitti, hi, do you know if calibre will be upgraded in maverick? ours is old and doesn't support a bunch of new devices, including the new kindle 3 which is supported upstream
[08:30] <pitti> fta: yes, that's on my list
[08:30] <fta> pitti, great, i'm expecting my K3 today in the mail ;)
[08:31] <pitti> fta: probably later this week, though, today I have too much to do with post-holiday catchup
[08:31] <pitti> fta: whee!
[08:31] <pitti> fta: I'll see what I can do :)
[08:32] <fta> i hope it will be better than my old sony prs700
[08:35] <pitti> I still like my prs505
[08:37] <fta> pitti, the 700 has a touchscreen, which makes it tougher to reader (lots of glares)
[08:37] <fta> -reader+read
[08:37] <pitti> fta: right, I noticed that; I thought a touchscreen was overkill for something to read books with
[08:38] <pitti> it probably halves the battery life or so
[08:38] <fta> that too, right
[08:41] <fta> grrr, telepathy-gabble crashes when trying to send a file in empathy over gtalk
[08:42] <fta> rickspencer3, didrocks: hi, can i add stuff to the app-indicator menu using quidgets?
[08:43] <fta> rickspencer3, didrocks: i want to do something with that menu for a new app i've created
[08:45] <didrocks> fta: there is quickly add indicator from the quickly trunk
[08:46] <didrocks> nothing in quidgets AFAIK
[08:46] <ricotz> pitti, hello, would you consider a new bugfix-only release of openerp-server and -client for maverick?
[08:46] <pitti> ricotz: I don't have any idea what openerp is, but "bug fix only" sounds great for maverick :)
[08:47] <glatzor> mvo, hello, what do you think about lp #635547
[08:47] <ubot2> Launchpad bug 635547 in software-center (Ubuntu) (and 1 other project) "Simulate requires an authentication before (affects: 2) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/635547
[08:48] <ricotz> pitti, it has a fairly huge bugfix list but therefore a huge diff 3,5MB
[08:48] <seb128> hey pitti!
[08:48] <seb128> lut didrocks
[08:48] <didrocks> salut seb128
[08:48]  * pitti hugs seb128, ca va?
[08:48]  * seb128 hugs pitti
[08:48] <seb128> yes, and you? had nice holidays?
[08:49] <seb128> thanks for restarting the retracers during the weekend
[08:49] <pitti> seb128: yes, indeed I had; http://piware.de/fotos/Donauradtour-Sep10/ for some photos, or my blog if you fancy reading some German :)
[08:49] <seb128> ;-)
[08:49] <glatzor> mvo, This way you could run an Installpackages call if an application description in s-c would be opened. afterwards you make a simulate call and show the "download size" or possible problems in the description
[08:49] <pitti> seb128: I had to fiddle with them a bit, but now the i386 one is working and amd64 is consolidating
[08:49] <glatzor> mvo, if the user moves on, you can make a cancel call to the transaction
[08:50] <pitti> seb128: with which app did you get bug 632291 ?
[08:50] <ubot2> Launchpad bug 632291 in gdm-guest-session (Ubuntu Maverick) (and 1 other project) "the apparmor profile needs to be updated to allow mono use (affects: 1) (heat: 6)" [Low,New] https://launchpad.net/bugs/632291
[08:50] <seb128> pitti, what was wrong this time?
[08:50] <seb128> pitti, they have been running for some days without issue
[08:51] <mvo> glatzor: sounds cool, let me check it out
[08:51] <seb128> pitti, tried tomboy and f-spot iirc
[08:51] <pitti> seb128: they failed dist-upgrading in libglib postinst, and then the bad python modules again
[08:51] <pitti> seb128: but seems the attachment permission issue was fixed/worked around
[08:51] <seb128> yes
[08:51] <seb128> I spend at least 10 hours with the launchpad guys until we got there
[08:52] <seb128> they allow direct access from the retracer to the librarian
[08:52] <pitti> whee, thanks for that
[08:52] <seb128> but then we some firewall issues in the dc
[08:52] <pitti> just responding to the RT about that
[08:52] <seb128> then upload was broken
[08:52] <seb128> which was other firewall issues...
[08:52] <pitti> dup checking works, too
[08:52] <glatzor> mvo, who was the guy I should talk to about being allowed to change bug priorities of the aptdaemon package?
[08:52] <seb128> pitti, how did you fix the glib update one?
[08:52] <mvo> glatzor: so you are working on this currently? to make simulate not require a authentication?
[08:52] <mvo> glatzor: bdmurray
[08:52] <pitti> seb128: remove set -e from postinst, add exit 0 at the end
[08:53] <seb128> pitti, I logged in the retracer and moved the postinst away at each glib update
[08:53] <mvo> glatzor: he needs to add you to bugcontrol I believe
[08:53] <pitti> seb128: or that
[08:53] <glatzor> mvo, It would just be a simple copy&paste task
[08:53] <seb128> I don't understand why it doesn't find the symbol
[08:53] <seb128> the symbol is in this glib version
[08:53] <pitti> wah, i386 crashed again
[08:54] <seb128> on what error?
[08:54] <pitti> HTTP Error 412: Precondition Failed
[08:54] <mvo> glatzor: cool
[08:54] <pitti> seb128: but Diogo sent a branch for fixing the test suite (oauth stuff)
[08:54] <pitti> seb128: so I'll test that locally
[08:54] <seb128> ok
[08:54] <seb128> deryck though it would take some time before it lands
[08:54] <seb128> so we went for the workaround
[08:55] <glatzor> mvo, But I don't have god any idea about the performance
[08:55] <seb128> brb session restart
[08:55] <glatzor> mvo, But this would be async anyway. So "Calculating download size ..." :)
[08:58] <seb128> re
[08:58] <glatzor> mvo, whoa, installing kpackagekit on a default ubuntu desktop results in 336 MBytes of dependencies :)
[09:05] <mvo> glatzor: the current check for this is done async too, so that should be fine (and its not cheap either ;)
[09:05] <mvo> glatzor: impressive :)
[09:07] <dpm> good morning everyone
[09:08] <pitti> hey dpm
[09:09] <dpm> hey pitti, welcome back, had a good holiday?
[09:09] <pitti> dpm: I had, thanks!
[09:09] <dpm> cool :)
[09:10] <seb128> pitti, thanks for fixing the guest session ;-)
[09:10] <pitti> seb128: I hope it works; I couldn't reproduce the problem
[09:10] <seb128> weird
[09:11] <seb128> I will test and tell you
[09:11] <pitti> seb128: merci
[09:14] <fta> didrocks, i'll have a look thanks
[09:15] <glatzor> mvo, should we check privileges twice? Should an user be allowed to create and simulate a transaction if he/she isn't allowed to run it?
[09:16] <glatzor> but only asking for the pass at the Run call
[09:16] <fta> didrocks, remember i said my link was flappy? here's the new project i need the app-indicator menu for, it's called Flappy: http://paste.ubuntu.com/492972/
[09:16] <mvo> glatzor: hm, why not. it seems the user can do that already (if he wants to) with plain python-apt
[09:16] <mvo> glatzor: I don't see a risk in allowing simulation
[09:16] <mvo> glatzor: other than maybe DoS the daemon
[09:17] <glatzor> I should add some code to check for a DOS
[09:17] <didrocks> fta: hehe :-) ok, I'll have a look (but later, crazy morning here ;))
[09:18] <seb128> pitti, the amd64 retracer crash I think is when it tries to mark as dup something which is already a duplicate
[09:18] <seb128> pitti, I had a similar case the other day
[09:18] <seb128> or has duplicates
[09:18] <pitti> seb128: hm, I thought the code would already check for that case
[09:19] <pitti> seb128: ah, right, it doesn't check if it already has dupes
[09:19] <pitti> seb128: thanks for pointing out; I'll try to get the test suite running again, it has both cases, I think
[09:19] <mvo> glatzor: I guess its a bit theoretical :) but yeah, can't hurt
[09:19]  * mvo hugs glatzor
[09:19] <pitti> but it hasn't worked for half a year or so, due to the oauth changes
[09:19] <mvo> glatzor: I mean, there are other ways (python -c 'import os;while True: os.fork()'
[09:20] <seb128> pitti, bug #616852
[09:20] <ubot2> seb128: Bug 616852 on http://launchpad.net/bugs/616852 is private
[09:20] <seb128> pitti, weird, it just crashed on that one but you untagged it before?
[09:20] <seb128> KeyError: 'DistroRelease'
[09:20] <seb128> KeyError: 'DistroRelease'
[09:21] <seb128> bah I had that the other day
[09:21] <seb128> something drop new line chars in the description
[09:21] <seb128> the retracer is not robust against that
[09:21] <pitti> argh, I see
[09:21] <pitti> ProblemType: CrashDistroRelease: Ubuntu 10.10
[09:21] <pitti> WTH?
[09:22] <seb128> it's not on the original description
[09:22] <seb128> somebody or something edited it
[09:22] <seb128> that's twice in a week
[09:22] <seb128> I'm wondering if that's user errors or if editing description delete new lines
[09:23] <seb128> ie a bug in launchpad description editing
[09:23] <seb128> "ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35"
[09:23] <seb128> as well
[09:23] <seb128> seems a bug
[09:24] <pitti> why? that one looks fine
[09:25] <seb128> yeah, ignore me...
[09:26] <seb128> anyway let's see if it happens on other bugs
[09:26] <seb128> I remove the lock
[09:27] <pitti> thanks
[09:35] <pitti> bah, crashed again; something to look into later, I guess
[09:36] <fta> seb128, when you edit anything, even a simple typo in the original description of a bug, it seems lp now reformats all the lines
[09:37] <seb128> could be the issue
[09:37] <mvo> mpt: good morning - could you help me with two strings? I need one short description for the partner reposiroty and one for extras (independent). currently there is http://paste.ubuntu.com/492980/ - but that does not capture it quite I think
[09:37] <mpt> mvo, in a meeting right now, bbiab
[09:38] <seb128> pitti, hum, log was not updated for 3 days and log_dupcheck doesn't have details
[09:39] <seb128> pitti, I will restart it by hand to see the output
[09:40] <mpt> mvo, where are each of those strings used?
[09:41] <RAOF> Bah.  Does anyone else find that double-clicking on window titlebars in Unity, or hitting the “maximize” button causes the window to die?
[09:41] <mvo> mpt: they are display in software-properties-gtk when you click on the "other sources" tab
[09:42] <RAOF> pitti: Ah.  I see you've commented on bug #615549.  I was just about to ask someone with a nice fast boot to see how much boot time you lose by just waiting on stopped udevtrigger.
[09:42] <ubot2> Launchpad bug 615549 in gdm (Ubuntu Maverick) (and 1 other project) "Dell Studio XPS 13 no video (affects: 2) (heat: 136)" [High,Triaged] https://launchpad.net/bugs/615549
[09:42] <mvo> mpt: CompDescritptionLong is not used in the UI currently I believe, but the description and compDescription are, I can make you ca screenshot if you want
[09:42] <mpt> mvo, are any of them used in USC?
[09:43] <htorque> RAOF, yes seeing it too, but only sometimes
[09:43] <mvo> mpt: not currently and not for maverick. it does make sense to have them unified though for N
[09:43] <RAOF> htorque: Seeing it too?  As in: seeing the race between gdm starting X, and udev starting drm?
[09:43] <mvo> mpt: but software-properties is a different thing entirely (at last currently)
[09:44] <htorque> RAOF, oh sorry - no, i meant the unity window close thing
[09:44] <RAOF> htorque: Ah, ok.
[09:44] <RAOF> It just ate my emacs session, is all.
[09:44] <htorque> RAOF, there's also another bug when double-clicking the titlebars: 494096
[09:44] <htorque> bug 494096
[09:44] <ubot2> Launchpad bug 494096 in metacity (Ubuntu) (and 2 other projects) "Clicking the title of a window is bringing a window underneath it into focus (affects: 41) (dups: 5) (heat: 179)" [Low,Triaged] https://launchpad.net/bugs/494096
[09:45] <RAOF> Oh, that one.  Heh.
[09:45] <RAOF> That doesn't affect me.  Almost all the time :)
[09:46]  * RAOF runs “quilt pop -a” in xorg-server and is saddened by the multiple pages of output. :/
[09:48] <bilalakhtar> seb128: Sorry, I don't like poking people repeatedly, but the meeting is tomorrow!
[09:48] <seb128> bilalakhtar, oh right
[09:48] <seb128> will do that today then ;-)
[09:49] <bilalakhtar> thanks seb128 !
[09:49] <seb128> you"re welcome
[09:49] <mpt> mvo, where in Software Sources is CompDescription used?
[09:52] <glatzor> mvo, I broke the aptdaemon repositories :(
[09:52] <pitti> RAOF: I can do a comparison later on
[09:53] <mvo> glatzor: uh, how?
 mvo, where in Software Sources is CompDescription used? (sorry, lost connection)
[09:53] <mvo> mpt: there is a example http://people.canonical.com/~mvo/tmp/Screenshot-Software%20Sources.png
[09:53] <RAOF> pitti: Thanks.  None of my laptops boot particularly quickly, so I'm not likely to see the full impact.
[09:53] <pitti> fta: calibre 0.7.18 uploaded; let me know how it goes
[09:54] <pitti> RAOF: I guess the effect on the Dell mini 10 will be biggest; fast SSD, slow CPu
[09:54] <mvo> mpt: CompDescription is normally used for cases where we have multiple components (like main,universe). but for extras and archive.canonical.com we only have one, the screenshot has a lucid cdrom that shows what it looks like with multiple ones
[09:54] <RAOF> pitti: Seems like a reasonable guess.  None of my systems have an ssd :'(
[09:55] <mvo> glatzor: maybe I can help?
[09:55] <fta> pitti, thanks. will test tomorrow as i missed the shipment today, the ups guy didn't even show up :(
[09:56] <fta> well, i can test with my sony too
[09:57] <mpt> mvo, how about something like this? http://paste.ubuntu.com/492990/
[09:58] <mpt> The CompDescriptionLong changes don't matter obviously if it's not being used anywhere
[09:59] <mvo> mpt: excellent, thanks a lot
[10:03] <glatzor> mvo, an upgrade broke the repositories. I am already getting some help on #launchpad. 0.3 is repaired, but trunk still broken
[10:07] <seb128> pitti, the amd64 retracer is running
[10:07] <seb128> it retracer 2 bugs now
[10:07] <pitti> nice
[10:07] <seb128> let's see if it stays
[10:07] <mvo> glatzor: ok, they are the better people to help :)
[10:07] <mvo> glatzor: but pretty annoying :/
[10:08] <pitti> seb128: and i386 failed on #635034 with the precondition thing; I untag and restart
[10:08] <seb128> pitti, thanks
[10:08] <pitti> seb128: hm, this isn't a duplicate of anything, or has dupes
[10:09] <seb128> dunno why it doesn't like it then
[10:09] <seb128> just untag and see if it does the same on other bugs
[10:09] <pitti> yup; it already retraced a couple of other bugs in the morning, so I guess/hope not
[10:09] <pitti> (done)
[10:10] <seb128> I'm wondering what changed
[10:10] <seb128> they retraced for 3 days solid
[10:18] <pitti> seb128: poppler 0.14.3> If necessary I can probably get to that at some point this week, but if Robert or you beat me to it, I wouldn't be sad
[10:18] <glatzor> mvo, should work again
[10:18] <seb128> pitti, not likely, GNOME 2.31.92 today and I'm on holidays tomorrow
[10:19] <pitti> ack
[10:19] <seb128> until the end of the week after that
[10:19] <pitti> I'll keep it on my medium-prio list for now
[10:19] <seb128> thanks
[10:19] <didrocks> seb128: doing evince
[10:19] <seb128> didrocks, thanks
[10:23] <seb128> pitti, didrocks will help as well with updates
[10:23] <seb128> pitti, robert_ancell is away until release
[10:23] <seb128> he's taking one month holidays
[10:23] <seb128> starting today
[10:23] <pitti> oh, I see
[10:24] <seb128> bah, retracer crashed again
[10:24] <seb128> I guess I'm on to talk to launchpad guys again today
[10:25] <seb128> weirdly it crashed again on a nswrapper bug
[10:25] <seb128> I'm wondering if there is something about those making things unhappy
[10:26] <seb128> didrocks, the gnome-keyring updates are not to do
[10:26] <seb128> I will have a go to the gir update
[10:26] <seb128> then nautilus
[10:27] <didrocks> seb128: I already saw a revert in the package version, that's why I didn't touch it. (in any case, I'll be telling there before doing the update) :)
[10:28] <didrocks> hum, building some part in pbuilder as I'm not sure about the current status with gsettings vs gconf in packages this cycle
[10:46] <seb128> ok, I hate launchpad
[10:46] <didrocks> hum, evince FTBFS
[10:47] <seb128> oh?
[10:47] <seb128> didrocks, "saw a revert in the package version"
[10:47] <seb128> what package was that?
[10:48] <seb128> gnome-keyring?
[10:48] <didrocks> seb128: http://paste.ubuntu.com/493011/
[10:48] <didrocks> seb128: yeah, was talking about gnome-keyring
[10:48] <didrocks> sounds like a good way to begin the day :)
[10:49] <seb128> ld crash
[10:49] <seb128> great
[10:49] <seb128> try again to see if it happens every time
[10:49] <seb128> talk to doko if that's the case
[10:50]  * didrocks refreshes his pbuilder
[11:11] <fta> pitti, just got my K3! i'll test calibre later today
[11:11] <pitti> fta: whee! have fun
[11:17] <didrocks> seb128: no ld crash this time, just got undefinied reference. Looking at it
[11:17] <seb128> didrocks, ok
[11:25] <glatzor> mvo, If you want to test lp:~aptdaemon-developers/aptdaemon/auth-later. You have to symlink the defer module since it is now a standalone package in trunk
[11:25] <glatzor> mvo, lp:python-defer
[11:25] <milanbv> chrisccoulson: hi! would you mind merging a branch to fix bug 433654?
[11:26] <ubot2> Launchpad bug 433654 in pulseaudio (Ubuntu) (and 2 other projects) "Only one user gets sound with privilege "Use audio devices" (affects: 54) (dups: 11) (heat: 305)" [Medium,Invalid] https://launchpad.net/bugs/433654
[11:26] <milanbv> you had already pushed a fix, this is the second part
[11:26] <mvo> glatzor: thanks, after lunch I check it out
[11:27] <glatzor> mvo,  no high priority. It is for natty.
[11:31] <seb128> diwic, hi
[11:31] <diwic> seb128, the discussion seem to have faded as I joined the channel
[11:32] <seb128> it was just a milanbv asking chrisccoulson for sponsoring
[11:32] <seb128> but chrisccoulson didn't reply yet
[11:32] <diwic> seb128, cool, then it's being looked at.
[11:32] <seb128> not sure the fix though is different from yours
[11:32] <seb128> you might want to discuss it with milanbv
[11:33] <chrisccoulson> hi
[11:33] <seb128> hey chrisccoulson
[11:33] <diwic> milanbv, I was just afraid it would not go into Maverick due to endless discussions of whether the checkbox should be removed or just its label changed
[11:33] <milanbv> diwic: I don't think the discussion has slowed down things
[11:34] <milanbv> it's just that nobody stepped in to suggest a fix
[11:34] <diwic> milanbv, my favorite name would be "Use audio devices remotely"
[11:34] <diwic> milanbv, but I guess your name will do
[11:34] <milanbv> ugh - do you mean they don't work remotely without this group?
[11:35] <diwic> milanbv, being in that group means they can log in to the machine from remote and use its audio device
[11:35] <diwic> milanbv, but if you didn't interpret it that way, it was probably a bad suggestion ;-)
[11:35] <milanbv> ah - but that's a ConsoleKit bug
[11:36] <milanbv> I'd better fix CK to detect remote login as an active session
[11:36] <diwic> milanbv, hey wait
[11:36] <diwic> milanbv, sounds like you know more than I do about remote sessions then
[11:37] <seb128> chrisccoulson, milanbv: btw any idea on this g-s-d gdk crasher?
[11:37] <seb128> or icon crasher
[11:37] <milanbv> diwic: wait, I think there's a bug for that
[11:37] <milanbv> seb128: no, I forgot about it actually
[11:37] <milanbv> not sure it's still happening
[11:37] <seb128> ok
[11:37] <milanbv> seb128: should I close it then?
[11:37] <seb128> it's collecting dupllicate
[11:38] <seb128> check if those a recent
[11:38] <seb128> the retracers were down so it might just be leftover from old versions
[11:38] <chrisccoulson> seb128 - which one was that? that's not bug 630239 is it?
[11:38] <ubot2> Launchpad bug 630239 in gnome-settings-daemon (Ubuntu) "gnome-settings-daemon crashed with signal 5 in gkbd_keyboard_drawing_new_dialog() (affects: 42) (dups: 1) (heat: 186)" [Medium,Confirmed] https://launchpad.net/bugs/630239
[11:38] <diwic> milanbv, people in the audio group can use audio devices even if they're not in the active seat. I e, when they're logging in via SSH. Right?
[11:38] <milanbv> diwic: I've not checked, but I guess they should, since they always are allowed to
[11:39] <seb128> chrisccoulson, no, it's another one
[11:39] <diwic> milanbv, or if they have been switched out through e g fast-user-switching
[11:39] <seb128> bug #551809
[11:39] <chrisccoulson> hmmmm, running lintian at the same time as installing a package is not good
[11:39] <ubot2> Launchpad bug 551809 in gnome-settings-daemon (Ubuntu) (and 1 other project) "gnome-settings-daemon crashed with SIGSEGV (affects: 131) (dups: 32) (heat: 734)" [High,Triaged] https://launchpad.net/bugs/551809
[11:39] <seb128> chrisccoulson, ^
[11:39] <diwic> milanbv, so that's what I would like the label to reflect
[11:39] <fta> pitti, when i plug the k3 on ubuntu, it's auto-mounted (great), but it doesn't charge (and the kindle complains about it). i noticed that with the sony too.
[11:40] <milanbv> diwic: what I'm saying is that the SSH/remote login behavior is the result of a bug in ConsoleKit
[11:40] <pitti> fta: weird; that works with my 505
[11:40] <fta> pitti, and when i umount, nautilus crashes :P
[11:40] <milanbv> so the only valid description IMHO is for "Exclusive use" (i.e. against fast user switching)
[11:40] <pitti> fta: charging is weird there, too, since it only charges when it's hooked up to a real USB port, and not if I attach my mobile usb charger (i. e. an AC adapter with an USB jack)
[11:41] <diwic> milanbv, how would you like SSH behavior to be, compared to now?
[11:41] <milanbv> diwic: well, if no other user is logged in, take control of audio
[11:41] <milanbv> if there's already one, wait for him to log out
[11:42] <chrisccoulson> i'm not sure users should be directly accessing audio devices at all tbh, that's why default policies only allow access to the local active user
[11:42] <chrisccoulson> whats the use-case for this?
[11:43] <milanbv> none
[11:43] <fta> pitti, several times, i had to hook my sony to an XP box to recharge it, while it didn't work on the same PC running maverick. it also doesn't charge with my phone adapter.
[11:43] <diwic> chrisccoulson, use-cases are listed here: http://wiki.ubuntu.com/Audio/TheAudioGroup
[11:43] <chrisccoulson> sorry, i meant to say "i'm not sure users should be directly accessing audio devices remotely at all tbh"
[11:43] <milanbv> chrisccoulson: I only kept the group in the list to allow people to get out of it :-)
[11:43] <fta> pitti, so it's not the pc, it's ubuntu doing something different
[11:44] <diwic> milanbv, naah, I don't agree with that. Just as a remote SSH login can't access the monitor connected to the seat, it shouldn't access the sound card connected to the seat. That's at least upstream (as in PA upstream)'s policy.
[11:45] <milanbv> diwic: if you're using SSH, you're clever enough to do this using the commandline ;-)
[11:47] <diwic> milanbv, hmm, how about "use audio devices even when away", that's a little vague though
[11:48] <milanbv> diwic: and that doesn't explain that there are downsides
[11:48] <milanbv> else, people check everything "just in case"
[11:48] <milanbv> seb128: actually, duplicates are using gsd 2.29.91
[11:48] <milanbv> so people should upgrade, and I mark this as fixed
[11:49] <milanbv> (I asked vuntz for nothing...)
[11:49] <seb128> ok thanks
[11:49] <diwic> milanbv, "lock audio devices even when away", as a compromise?
[11:49] <milanbv> seb128: there's a report with 2.30.2, but the trace might be a little different
[11:49] <milanbv> Apport didn't merge it automatically
[11:50] <milanbv> diwic: could be nice too
[11:50] <milanbv> away also applies to local login, so that's OK
[11:51] <milanbv> diwic: but you'e the burden of changing the branch now :-p
[11:51] <milanbv> seb128: talked too fast
[11:51] <milanbv> there are reports with 2.30.2
[11:52] <milanbv> WTH the most recent are using older versions...
[11:52] <fta> pitti, lsusb shows the device as self-powered, and the bus shows a max power of 100mA, not sure it's enough
[11:53] <pitti> fta: 100 mA looks fine; that's the maximum specified current per USB port
[11:53] <fta> pitti, there are also 500mA ports and even more
[11:56] <pitti> fta: never seen those; AFAIK they are limited to .5 W
[11:56] <pitti> fta: 2.5 W on such a small port?
[11:56] <pitti> but anyway, I don't think a device should rely on such high-power ports
[11:56] <diwic> I think USB3 specs > .5W
[11:56] <seb128> didrocks, I guess you could build evince-gtk with dbus
[11:56] <diwic> But for USB2 .5W is maximum, or maybe .9W
[11:57] <seb128> didrocks, it's not likely anybody don't have dbus nowadays
[11:57] <didrocks> seb128: really? I find no information about that in debian/changelog
[11:57] <fta> pitti, http://www.maxim-ic.com/app-notes/index.mvp/id/3241  last paragraph
[11:57] <seb128> didrocks, ?
[11:57] <seb128> didrocks, I think it's you who added back evince-gtk to start
[11:57] <seb128> we dropped it at some point
[11:58] <seb128> it's doubtful anybody use it
[11:58] <didrocks> seb128: right, I was looking for why explicitely debian used --disable-dbus
[11:58] <seb128> new evince use gsettings
[11:58] <seb128> so there is no gnome specific depends left there
[11:58] <seb128> evince-gtk could be dropped
[11:58] <didrocks> seb128: as you want, I was building with a #if ENABLE-DBUS for the call
[11:58] <didrocks> #ifdef*
[11:59] <seb128> or maybe not
[11:59] <seb128> there is still the nautilus code
[11:59] <seb128> but in any case just enable-dbus for -gtk
[11:59] <seb128> should work
[11:59] <milanbv> diwic: new branch uploaded
[11:59] <milanbv> https://code.edge.launchpad.net/~nalimilan/ubuntu/maverick/gnome-system-tools/gnome-system-tools.fix-433654-2
[11:59] <diwic> milanbv, cool, thanks :-)
[11:59] <milanbv> chrisccoulson: now that we've agreed on a wording, do you also agree? :-)
[11:59] <didrocks> seb128: http://paste.ubuntu.com/493041/ seems safer, isn't it? can I keep that or changing debian/rules?
[12:00] <milanbv> "Lock audio devices even when away"
[12:00] <chrisccoulson> milanbv - yeah, makes sense
[12:00] <seb128> didrocks, well doing --enable-dbus doesn't seem risky
[12:00] <seb128> but either is fine there
[12:00] <seb128> your call ;-)
[12:00] <seb128> lunch time
[12:00] <seb128> bbl
[12:00] <milanbv> chrisccoulson: if you start working on the gst, beware! ;-)
[12:00] <milanbv> there's also another branch to merge:
[12:01] <milanbv> https://code.edge.launchpad.net/~nalimilan/ubuntu/lucid/gnome-system-tools/shares-services
[12:01] <didrocks> seb128: ok, as my pbuilder is already running and the build is almost finished, I will go that way, we'll see then :)
[12:01] <didrocks> seb128: enjoy!
[12:02] <didrocks> (I was sure I didn't need to ping you for that and that you'll see the bug report :-))
[12:03] <chrisccoulson> milanbv - ok, will look at that in a bit
[12:06] <fta> grrr, the nautilus crash is 100% reproducible when unmount the kindle :P
[12:08] <milanbv> chrisccoulson: thanks!
[12:08] <milanbv> seb128: actually, this is a GTK+ bug
[12:08] <milanbv> there is also one report with the same trace in gnome-bluetooth
[12:09] <milanbv> the icon cache seems to be the culprit
[12:34] <chrisccoulson> hi pitti, how are you?
[13:12] <pitti> hey chrisccoulson, I'm great, thanks! how are you?
[13:13] <chrisccoulson> pitti - i'm good thanks, but busy. you were on vacation last week weren't you?
[13:14] <pitti> chrisccoulson: right, we went bicycling along the Donau river, and spent 2.5 days in Vienna
[13:14] <chrisccoulson> nice!
[13:14] <pitti> chrisccoulson: http://piware.de/fotos/Donauradtour-Sep10/ :)
[13:18] <chrisccoulson> pitti - excellent, and it looks like the weather stayed nice for you too :)
[13:21] <pitti> chrisccoulson: mostly; we just had one bad rainy day, the rest was fairly nice
[13:26] <chrisccoulson> pitti, so, i know this might be a bit of a tall order, but is there any chance of me getting bug 531867 in to maverick?
[13:26] <ubot2> Launchpad bug 531867 in iceowl (Debian) (and 1 other project) "[FFe] [needs-packaging] Lightning 1.0 Beta for Thunderbird 3 (affects: 93) (dups: 5) (heat: 351)" [Unknown,Unknown] https://launchpad.net/bugs/531867
[13:29] <pitti> chrisccoulson: I defer to ~ubuntu-release for this
[13:29] <chrisccoulson> pitti - oh, you're not part of ubuntu-release?
[13:30] <pitti> well, I am, but with my limited platform time this cycle I rather leave those to the other members
[13:30] <chrisccoulson> ah, ok. that makes sense :)
[13:35]  * popey wonders if kenvandine has seen the latest comments on bug 519262 :D
[13:35] <ubot2> Launchpad bug 519262 in gwibber (Ubuntu) (and 1 other project) "Provide ability to Follow a user (affects: 45) (heat: 229)" [Wishlist,Triaged] https://launchpad.net/bugs/519262
[13:42] <kenvandine> hey popey
[13:42] <popey> hullo!
[13:42] <kenvandine> i hadn't seen the latest comment, too late for this cycle
[13:42] <popey> :( :(
[13:42] <kenvandine> and it isn't generic enough... imho
[13:43] <popey> I haven't looked at the code, sorry.
[13:43] <kenvandine> i actually want a view user profile, kind of thing
[13:43] <kenvandine> it only works for twitter
[13:43] <kenvandine> and gwibber has to handle multiple services
[13:43] <popey> true
[13:43] <kenvandine> however... that patch would only provide the follow feature to twitter users
[13:44] <kenvandine> so it won't break others
[13:44] <kenvandine> but... i would like to provide the identical feature to each service that provides that
[13:44] <kenvandine> so for 3.0/natty
[13:44] <popey> cool
[13:44] <kenvandine> i am hoping to have a user profile type view
[13:44] <kenvandine> we could add it like an action as well, like this patch does
[13:44] <popey> in addition have you considered an image viewer for twitpic type posts?
[13:45] <kenvandine> but clicking on a user should show you their profile for that service
[13:45] <kenvandine> twitpics should be displayed inline
[13:45] <fta> pitti, tested calibre, i works fine. imported a small part of my ebooks collection, exported it to the kindle, no problem
[13:45] <kenvandine> however, i want shotwell to have the ability to display all the images that have been posted
[13:45] <pitti> fta: yay
[13:45] <fta> pitti, that when using the usb port, not the gmail stuff
[13:45] <kenvandine> independant of the gwibber client
[13:46] <fta> -i+it
[13:46] <pitti> kenvandine, didrocks: I just installed today's netbook daily, and ubuntuone syncd starts by default (I didn't touch anything); known bug?
[13:46] <popey> kenvandine: i just want to have some way to click on an image and view it full size without having to spark up a browser and go to some ad-ridden place
[13:46] <kenvandine> popey, so you can browse them all just like any other set of photos
[13:46] <kenvandine> pitti, ewww
[13:46] <didrocks> pitti: not known by me at least
[13:46] <kenvandine> popey, ah...
[13:46] <kenvandine> well that wouldn't be hard
[13:46] <didrocks> pitti: did you check on desktop too? I don't see anything particular doing that on netbook only
[13:46] <popey> kenvandine: i dont want a collection of pics, just the one I am looking at right now in gwibber, but bigger
[13:47] <kenvandine> sure
[13:47] <kenvandine> popey, if there isn't a bug for that, please file it
[13:47] <popey> ok
[13:47] <pitti> didrocks: I suppose it's not unity/gnome specific; seems they just screwed up the autostart files
[13:47] <kenvandine> pitti, that shouldn't happen...
[13:47] <pitti> i. e. I think in earlier releases there wasn't one, and you just got one created if you actually enabled u1
[13:47] <didrocks> pitti: I'll have a look this week on that, can you file a bug, please?
[13:48] <pitti> didrocks: I guess it's not really "your" bug anyway
[13:49] <kenvandine> pitti, i looked at the start script, looks like it checks the existance of ~/Ubuntu One
[13:49] <kenvandine> if that doesn't exist, it exits
[13:49] <kenvandine> pitti, does that folder exist?
[13:49] <didrocks> pitti: right, but just for checking if that doesn't happen in desktop environment (or subscribe rather)
[13:49] <pitti> kenvandine: yes
[13:50] <kenvandine> humm
[13:50] <kenvandine> any idea what creates that now?
[13:50] <pitti> no, I don't
[13:50] <pitti> it's not in /etc/skel/
[13:54] <kenvandine> dobey, do you know?
[13:54] <htorque> fwiw, i just installed a desktop daily - ubuntu one folder is there and ubuntuone-syncdaemon is running
[13:56] <kenvandine> htorque, thx
[13:56] <kenvandine> we need to figure out what is creating that dir
[13:56] <pitti> kenvandine: perhaps the nautilus extension?
[13:56] <kenvandine> maybe
[13:57] <kenvandine> however, that wouldn't run that early in unity
[13:57] <pitti> nautilus is started by default
[13:57] <kenvandine> oh, then maybe
[13:58] <kenvandine> pitti, either way, please file a bug and we'll get it triaged asap
[13:58] <pitti> kenvandine: will do
[13:58] <kenvandine> thx
[13:58] <pitti> kenvandine: anyway, rm -r Ubuntu\ One, restart, it's back
[13:59] <kenvandine> ok... probably nautilus :/
[13:59] <pitti> yes
[13:59] <dobey> kenvandine: syncdaemon starts it. there is a known bug with the gsd plug-in and nautiuls starting it too early
[13:59] <kenvandine> ?
[14:00] <dobey> i think the fix is in ubuntuone-client trunk already, and rodrigo will be doing a release tomorrow
[14:00] <kenvandine> dobey, the issue is syncdaemon shouldn't get started
[14:00] <pitti> RAOF: no noticeable difference on the mini 10 if starting gdm on udevtrigger finished
[14:00] <dobey> kenvandine: yes, i know. that's why it is a bug :)
[14:00] <kenvandine> hehe
[14:00] <kenvandine> ok
[14:00] <kenvandine> dobey, thx
[14:00] <pitti> so either ~/Ubuntu One shouldn't be autocreated, or its existance isn't a viable condition for starting the sync daemon
[14:01] <kenvandine> i think it shouldn't get created
[14:01] <kenvandine> users don't want to see that if they don't use u1
[14:01] <dobey> pitti: it only exists because the gnome-settings-daemon plug-in is causing syncdaemon to start at log-in
[14:01] <dobey> which is a known bug, and should already be fixed in trunk
[14:02] <kenvandine> i think dobey is saying nautilus is causing syncdaemon to start, which is creating the folder
[14:02] <kenvandine> or gsd
[14:02] <dobey> both probably. they're both using libsyncdaemon, which is where the bug really was
[14:03] <pitti> kenvandine, dobey, didrocks : bug    4. 637100
[14:03] <ubot2> Launchpad bug 4 in ubuntu (and 1 other project) "Importing finished po doesn't change progressbar (affects: 1) (dups: 1) (heat: 10)" [Undecided,Invalid] https://launchpad.net/bugs/4
[14:04] <pitti> argh
[14:04] <pitti> bug 637100
[14:04] <ubot2> Launchpad bug 637100 in ubuntuone-client (Ubuntu) "[maverick] sync daemon gets started by default (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/637100
[14:04] <didrocks> pitti: thanks :) will follow it
[14:07] <popey> kenvandine: where's the best place to get oath capable gwibber for lucid?
[14:07] <kenvandine> popey, lucid-updates
[14:07] <popey> hmm
[14:08] <popey> so it is, ta
[14:08] <kenvandine> :)
[14:18] <dobey> kenvandine, pitti: son on Friday, i packaged up the latest libproxy release, to help debug a crash with it in ubuntuone-preferences that people were seeing on 64 bit. it doesn't seem to fix the issue itself, but i think it would be nice to have a modern version in the archive, rather than one from a year ago. should I just dput it and beg for sponsorship?
[14:20] <kenvandine> dobey, isn't there a soname change?
[14:20] <kenvandine> i think some stuff would need a rebuild
[14:20] <dobey> yes
[14:21] <dobey> kenvandine: libsoup and vlc are the only things that seem to depend on libproxy0
[14:21] <kenvandine> seb128, ^^
[14:22] <kenvandine> seb128, it would be nice to get the latest... the libproxy guys aren't too keen on looking at bugs for the really old version we have
[14:22] <kenvandine> seb128, and he said the only reason for the soname change was one function may return NULL now
[14:23] <seb128> dobey, kenvandine: if you did it properly it's ok
[14:23] <seb128> but it needs review
[14:23] <seb128> they switched to cmake iirc
[14:23] <seb128> there is also a new .so
[14:24] <seb128> did you split the binary?
[14:24] <dobey> split what binary?
[14:27] <rdesfo> does any one know how to generate a configuration file?
[14:27] <rdesfo> I'm trying to install brl-cad
[14:36] <seb128> dobey, dpkg -L libproxy...
[14:37] <seb128> dobey, when I gave it a try there was a new library or .so
[14:37] <seb128> so it would require a new binary
[14:37] <dobey> there are some new module .so files
[14:37] <dobey> but i just realized there's a circular dep now :-/
[14:38] <dobey> since libproxy apparently uses libsoup in a module now
[14:38] <dobey> i haven't split the modules out into a new binary pkg, but i could
[14:38] <seb128> those are not an issue
[14:38] <dobey> though i don't know what to do about the circular dep
[14:38] <seb128> there is a libmodman as well
[14:38] <seb128> which was the issue
[14:38] <dobey> seb128: i patched it to build statically
[14:39] <seb128> oh ok
[14:39] <seb128> why?§
[14:39] <dobey> because it's not the upstream libmodman package. if we want a libmodman package we should package that separately from the libmodman source
[14:39] <chrisccoulson> hi sabdfl - i'm not sure whether you've seen this e-mail yet on the tb-planning ML: https://mail.mozilla.org/pipermail/tb-planning/2010-September/000510.html
[14:39] <dobey> it simply includes libmodman in case it's not in the system
[14:39] <chrisccoulson> would you be interested in seeing some thunderbird guys at UDS?
[14:39] <dobey> the same reason we don't install libdb from evolution for example :)
[14:39] <sabdfl> chrisccoulson: hell yes
[14:40] <chrisccoulson> sabdfl - i emailed the developer of the indicator extension a few weeks back, and i've already planned to help him get it in to ubuntu
[14:40] <chrisccoulson> (and hopefully installed by default for thunderbird users too)
[14:40] <sabdfl> chrisccoulson: i'm running it, seems to work well
[14:40] <sabdfl> very nice!
[14:40] <sabdfl> how's the packaging?
[14:42] <chrisccoulson> yeah, the extension is quite nice. i had a recommendation for the extension to make it use jsctypes, which is a new technology in thunderbird 3.1, and ruben seems quite keen to use it
[14:42] <chrisccoulson> it means that there would be no need to run a separate python process to talk to the indicator
[14:44] <dobey> seb128: hrmm. upon a closer look, perhaps it could use a little tweaking still. and i'm not sure what to do about the circular dep
[14:47] <chrisccoulson> sabdfl, fyi - https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-natty-thunderbird-messaging-indicator (although it's only a template so far)
[14:51] <seb128> dpm, hi
[14:51] <seb128> dpm, do you know if new langpack updates are planned for maverick and when?
[14:52] <rickspencer3> seb128, hey, it's cyphermox's first official day on the desktop team!
[14:52] <seb128> oh right
[14:52] <seb128> cyphermox, welcome on board!
[14:52] <cyphermox> thx!
[14:52] <dpm> seb128, I was trying to enable them last week, without success. They are scheduled for every Wednesday and Sunday.
[14:53] <rickspencer3> bryceh, chrisccoulson, didrocks, kenvandine, pitti ^
[14:53] <rickspencer3> welcome cyphermox!
[14:53] <didrocks> welcome cyphermox!
[14:54] <seb128> cyphermox, nice part of the cycle to start ;-)
[14:54] <didrocks> something like "fix all bugs now? you have 3 weeks" :)
[14:54] <chrisccoulson> hi cyphermox!
[14:54] <rickspencer3> I guess start with triaging Network Manager bugs
[14:55] <kenvandine> welcome cyphermox!
[14:55] <seb128> right and spot ones that would be nice to fix for maverick and try to get some done ;-)
[14:55] <seb128> cyphermox, if you have any question feel free to just ask on the channel
[14:55] <seb128> you will usually find people at any hour though the channel is mostly busy during european and us work hours
[14:56] <cyphermox> yup
[14:56] <cyphermox> I've been hanging out here silently watching for a long while now :)
[14:57] <seb128> ;-)
[15:01] <fta> pitti, calibre used to live in the tray, it's no longer there, is it a regression?
[15:08] <didrocks> seb128: who do you think I should ping for getting a FFe for quickly-widgets (and then quickly), btw? (bug #637188) can't get a complete diff for that
[15:08] <ubot2> Launchpad bug 637188 in quickly-widgets (Ubuntu) "feature freeze exception for maverick (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/637188
[15:09] <didrocks> can* get a complete diff, but not sure it's relevant
[15:10] <seb128> didrocks, it's in universe you can ping me about it
[15:10] <didrocks> seb128: ok, so ping :-)
[15:10] <seb128> rational?
[15:10] <seb128> let me read the bug
[15:12] <seb128> didrocks, ok, acked
[15:12] <didrocks> seb128: thanks
[15:16] <cassidy> didrocks, seb128: kenvandine: it would be really nice to have https://bugs.edge.launchpad.net/ubuntu/+source/empathy/+bug/400485 fixed. Any chance one of you could badger the right person to add the missing sounds?
[15:16] <ubot2> Launchpad bug 400485 in ubuntu-sounds (Ubuntu Karmic) (and 3 other projects) "Empathy sounds not in default ubuntu theme (affects: 41) (dups: 5) (heat: 246)" [Low,Won't fix]
[15:16] <kenvandine> cassidy, indeed
[15:17] <seb128> kenvandine, can you do that?
[15:19] <kenvandine> seb128, i can... i haven't read all the comments yet
[15:19] <kenvandine> i guess they are in the freedesktop theme now?
[15:20] <seb128> kenvandine, not sure, I've no clue about the issue but I will not have time for that before tomorrow
[15:20] <seb128> kenvandine, if have no time that will be for next cycle
[15:21] <kenvandine> ok, apparently we could create links to the files provided by the freedesktop theme and add that as a dep
[15:21] <kenvandine> seb128, how does that sound?
[15:21] <seb128> not great
[15:21] <kenvandine> thought so
[15:21] <seb128> how much space would that add on the CD?
[15:21] <kenvandine> one sec
[15:21] <didrocks> seb128: taking gnome-bluetooth and totem, ok?
[15:21] <seb128> didrocks, ok, thanks
[15:22] <seb128> didrocks, I will do nautilus-sendto
[15:22] <kenvandine> the deb is 413K
[15:22] <didrocks> seb128: ok, thanks :)
[15:22] <seb128> kenvandine, no license issue?
[15:22] <kenvandine> doubtful, will have to verify
[15:24] <kenvandine> seb128, i'll look at it in a bit, not even certain it includes all the ones we need
[15:26] <seb128> thanks
[15:29] <rickspencer3> seb128, heya
[15:29] <rickspencer3> I'm suggesting that cyphermox concentrate efforts on NM, and leaves ConMan and such aside for Maverick
[15:29] <rickspencer3> thoughts?
[15:31] <chrisccoulson> rickspencer3, the only effort required on our side for connman so far has been occasional sponsoring of DX work
[15:31] <seb128> I think it makes sense
[15:31] <chrisccoulson> so, i think that makes sense too
[15:41] <pitti> cyphermox: welcome to the desktop team! great to have you
[15:41] <cyphermox> pitti: thanks!
[15:41] <pitti> fta: I think it was disabled by design; there might be an option now
[15:42] <pitti> RAOF: ok, tracked down the breakage of my external monitor; it's not a plymouth/X fault at all, but a regression in gnome-settings-daemon
[15:42] <pitti> it seems it now disables the external monitor by default
[15:42] <pitti> thus once gdm starts up, you get the screen powered off
[15:42] <pitti> you can configure it on again with a .config/monitors.xml; I reverted to the previous gnome-settings-daemon for now, and it works again
[15:43] <seb128> re
[15:43] <pitti> seb128: wb
[15:43] <pitti> seb128: FYI:
[15:43] <seb128> great I got that bug again when I can login but screen doesn't get activated
 RAOF: ok, tracked down the breakage of my external monitor; it's not a plymouth/X fault at all, but a regression in gnome-settings-daemon
 thus once gdm starts up, you get the screen powered off
[15:43] <seb128> pitti, yes I know, I've worked on that until 8pm with frederico on friday
[15:43] <pitti> seb128: oh, for you as well?
[15:43] <seb128> I've a workaround ready for upload
[15:43]  * pitti hugs seb128
[15:43] <pitti> I just spent about 2.5 hours of downgrading X, plymouth, udev, kernel to track down what's wrong
[15:44] <seb128> pitti, set /apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup
[15:44] <seb128> to true
[15:44] <pitti> is that a new "unbreak my computer" setting?
[15:44] <pitti> I mean, it actually turns it _off_ right now
[15:47] <seb128> pitti, I guess your issue is that lid close and external monitor give you no screen?
[15:47] <seb128> and yes that will fix it
[15:47] <seb128> by default it turns off external monitors
[15:48] <seb128> the issue is that xrandr returns that the laptop screen is connected
[15:48] <seb128> the policy sucks though federico agreed to change the default to true
[15:48] <pitti> seb128: right
[15:48] <pitti> well, of course the laptop screen is connecte
[15:48] <seb128> he did it this way because he said he did the change for hp and that's the way they wanted it
[15:48] <pitti> unfortunately we can't just check the lid status
[15:48] <seb128> right...
[15:48] <pitti> that was in the upstream kernel for a while, but they ripped it out again
[15:48] <seb128> that's why having all output on by default makes sense
[15:49] <pitti> because there are too many buggy BIOSes
[15:49] <seb128> sorry you waste time on that
[15:49] <seb128> I guess you discussed it before I joined this morning
[15:49] <pitti> i. e. lid _events_ are fine, but lid status right after boot is unreliable
[15:49] <pitti> seb128: no problem
[15:49] <pitti> c'est la vie
[15:50] <pitti> seb128: right, about 8 am; but I gave up after an hour and started working on my couch with just the laptop, to get something done :)
[15:50] <pitti> seb128: so we'd set that gconf value to true by default, to get back the previous behaviour?
[15:50] <pitti> seb128: I'd rather have g-s-d not touch xrandr at all, TBH
[15:50] <pitti> it takes an awful amount of time
[15:51] <pitti> gdm startup feels a lot slower now
[15:51] <seb128> not sure "previous behaviour"
[15:51] <seb128> btw you can open the lid of the dock
[15:51] <seb128> or log in without screen
[15:51] <seb128> it's just a display issue
[15:51] <seb128> or ctrl-fn-f7
[15:51] <seb128> or f8
[15:51] <seb128> I never know which one cycle xrandr
[15:53] <pitti> seb128: opening lid didn't help; I did that (and crouched under the desk) to see what's going on, but it didn't enable the main screen
[15:53] <pitti> seb128: previous behaviour> it didn't touch xrandr unless you had a ~/.config/monitors.xml
[15:53] <pitti> i. e. it kept whatever KMS set up, which is what we intended
[16:04] <seb128> pitti, can we easily change the retracers to not use edge?
[16:06] <pitti> seb128: production instead? yes, should be easy; would that help?
[16:06] <nessita> good morning/afternoon! could I have a sponsor for https://code.launchpad.net/~nataliabidart/ubuntu/maverick/ubuntu-sso-client/ubuntu-sso-client-1.0.0/+merge/35292, please?
[16:07] <james_w> seb128: is whatever problem with private attachments fixed on production as well as edge?
[16:07] <seb128> james_w, not sure
[16:08] <seb128> let me check
[16:09] <pitti> james_w: it's not really "fixed" on either
[16:09] <pitti> there's a workaround
[16:09] <pitti> which is specific to ronne and ~apport
[16:09] <james_w> right, just don't want to jump from one problem to another problem
[16:09] <seb128> pitti, not only
[16:15] <seb128> pitti, it's worth trying
[16:15] <Sarvatt> mvo, seb128: Do either of you have any problems with adding a few new devices to the compiz blacklist that do not work? Intel has some new machines coming out before 11.04 that will not have functional 3D support but mesa thinks they do and compiz screws everything up - https://bugs.edge.launchpad.net/ubuntu/+bug/633376
[16:15] <ubot2> Launchpad bug 633376 in compiz (Ubuntu) "Compiz does not work on Intel Sandybridge Integrated GPU's. (affects: 1) (heat: 10)" [Undecided,New]
[16:15] <seb128> pitti, james_w thinks that could help with the pre condition bug
[16:16] <Sarvatt> they boot into a black screen with a cursor if compiz is enabled
[16:18] <seb128> Sarvatt, seems to make sense
[16:23] <seb128> great I crashed gnome-keyring-daemon now, brb
[16:23] <kklimonda> :)
[16:24] <kklimonda> anyone here is familiar with Xlib?
[16:25] <kklimonda> is it possible for XGetWindowProperty to return with nitems set to 0 AND type set to expected atom type?
[16:38] <mpt> mvo, one of the things I would have asked about if my mic was working, was: Are you still happy with the idea of having a separate library for determining software item information (mapping from package name to title, icon, summary, description, category, etc) in Natty, so USC and update-manager and aptdaemon can all use it?
[16:54] <didrocks> seb128: taking gnome-system-tools
[16:58] <seb128> re
[16:58] <seb128> didrocks, ok
[16:58] <seb128> sorry I was still doing some tests
[16:58] <seb128> I should be done with sessions restarts for a bit
[16:59] <mvo> mpt: yes, I think now that its used in unity, u-m, s-c thats absolutely essential. it does mean that we need to be a lot more careful about the API though (which is good and bad :)
[16:59] <mvo> Sarvatt: compiz> did seb128 answer that already (sorry was on the phone) - if not I can review the changes
[16:59] <seb128> mvo, yes
[16:59] <Sarvatt> mvo: yeah he did, thanks!
[17:01] <mvo> Sarvatt: excelent, just remember to commit changes to bzr already when you upload ;)
[17:01] <Sarvatt> it's just adding a few new pci ids to the blacklist for the new sandybridge GPU's. I'm testing things daily on sandybridge and will keep on top of when it's fixed to revert it in natty because blacklists stink.
[17:21] <kenvandine> pitti, ping
[17:22] <kenvandine> pitti, how do you feel about bug 629216 for a freeze exception?
[17:22] <ubot2> Launchpad bug 629216 in ubuntu-wallpapers (Ubuntu) (and 1 other project) "[FFe] Replace Cosmos "bundle" with existing wallpaper bundle (affects: 1) (heat: 504)" [Undecided,New] https://launchpad.net/bugs/629216
[17:22] <kenvandine> not replacing though...
[17:22] <kenvandine> just adding a new bundle for the contest winners
[17:22] <kenvandine> i think removing the old one at this point might annoy people
[17:23] <kenvandine> but adding the new one is just a new xml file, so tiny and no risk
[17:45] <pitti> kenvandine: that's just new XML, right? i. e. no new pics?
[17:46] <pitti> kenvandine: does that change the default wallpaper, or just add more options to the chooser?
[17:46] <kenvandine> right
[17:46] <pitti> seems fine
[17:46] <kenvandine> it adds an entry for a bundle
[17:46] <kenvandine> and all the wallpapers are already there
[17:46] <kenvandine> mind ack'ing that bug?
[17:47] <pitti> just done
[17:47] <kenvandine> thx
[17:47]  * vish bzzzzttt!!
[17:47]  * vish ^ didrocks' alarm clock ringing :)
[17:47]  * vish <- clock ;p
[17:48]  * vish wonders if it is the right time to ping pitt-i , who seems to be getting pinged left-n-right.. on all channels ;)
[17:49] <vish> didrocks: maybe later? or should we ask pitt-i about Bug #587853 ?
[17:49] <ubot2> Launchpad bug 587853 in cheese (Ubuntu Lucid) (and 2 other projects) "After video recording, record/take photo button becomes disabled (affects: 2) (dups: 1) (heat: 24)" [Low,Triaged] https://launchpad.net/bugs/587853
[18:08] <seb128> bryceh, there?
[18:19] <asac> mvo: there?
[18:20] <asac> mvo: do you know that all the proxy setup is really busted ? one needs to configure that in 3 places to get everything going ;) ... e.g. bashrc, apt.conf, and some other place i cant remember :-P
[18:21] <mvo> asac: noooo, just use gnome proxy settings
[18:21] <mvo> asac: it will do the right thing
[18:21] <mvo> asac: it will setup http_proxy in gnome-terminals etc
[18:22] <mvo> asac: about apt.conf, complain to the sudo folks, the wipe http_proxy from the environment if you do sudo -s
[18:22] <mvo> asac: can we talk about it tomorow? gtg now
[18:27] <asac> hehe
[18:27] <asac> right
[18:28] <asac> not that i havent tried it ;)
[18:28] <asac> (gnome setting)
[18:35] <chrisccoulson> hi asac!
[18:35] <chrisccoulson> how are you?
[18:38] <ronoc> bl8: ping
[19:05] <ronoc> bl8, there was libindicate release last week which seems to be causing issues -> https://bugs.launchpad.net/indicator-sound/+bug/636253
[19:05] <ubot2> Launchpad bug 636253 in indicator-sound "banshee not work with sound menu (affects: 2) (heat: 10)" [Undecided,Confirmed]
[19:06] <ronoc> bl8, could you rebuild that extension ?
[19:24] <Laney> did you really need to bump the assemblyversion?
[19:25] <Laney> I am assuming not
[19:25] <Laney> ronoc: ^^^
[20:09] <didrocks> re
[20:09] <didrocks> back for tacklinkg some updates :)
[20:09] <seb128> didrocks, that was an earlier diner
[20:10]  * nessita still whispers hoping someone will be able to sponsor https://code.launchpad.net/~nataliabidart/ubuntu/maverick/ubuntu-sso-client/ubuntu-sso-client-1.0.0/+merge/35292
[20:10] <didrocks> seb128: yeah, and when we left, a lot of people waiting for a table :)
[20:10] <seb128> ;-)
[20:10] <seb128> nessita, ok
[20:11] <seb128> nessita, "still", did you whisper before?
[20:11] <seb128> nessita, hey btw ;-)
[20:11] <didrocks> kenvandine: I got an upload reject from dpkg-source not beeing able to extract gnome-bluetooth. seb128 told me that he thinks you got that last week, how did you fix it?
[20:11] <nessita> seb128: hey! yes, I ask for a sponsorship a while back. I'm not in a hurry, so no worries :-)
[20:11] <kenvandine> didrocks, i extracted the tarball and created it again
[20:12] <seb128> nessita, sorry I didn't notice it, I will do the sponsoring
[20:12] <nessita> seb128: thanks!
[20:12] <didrocks> kenvandine: ok, trying that :)
[20:12] <seb128> didrocks, can you try to ping cjwatson about it before doing that?
[20:12] <seb128> nessita, you're welcome
[20:12] <kenvandine> we should get to the botton of that bug
[20:13] <seb128> right
[20:13] <nessita> seb128: one thing i don't fully understand (and you may be able to help me with): when building the tarball with setup.py sdist, the removal from PKG-INFO appeared (lines 16-27 in the launchpad diff). Shall I be worried?
[20:14] <didrocks> seb128: sure
[20:14] <seb128> nessita, I don't know why it's cleaned but it's not an issue no
[20:14] <seb128> didrocks might know better
[20:14] <seb128> I didn't use setup.py a lot
[20:15] <nessita> seb128: awesome
[20:15] <didrocks> (backlogging)
[20:15] <didrocks> hey nessita
[20:15] <nessita> hey didrocks, how are ya?
[20:15] <didrocks> hum no, I don't think about PKG-INFO and eggs thing :)
[20:15] <didrocks> nessita: I'm fine, thanks, you?
[20:16] <nessita> didrocks: pretty good. OK then, I'll investigate the PKG-INFO issue in the web. Thanks!
[20:16] <didrocks> nessita: it seems that most of python module are distributing it though
[20:16] <nessita> yeah
[20:19] <didrocks> nessita: it seems to be pure changelog + some medata for library you ship, only used with egg system
[20:29] <didrocks> kenvandine: ok, postponing the upload, james is looking at it right now. I'll use the workaround if no other solution. Thanks :)
[20:29] <kenvandine> good
[20:29] <kenvandine> :)
[20:36] <seb128> didrocks, do you want other updates to do?
[20:37] <didrocks> seb128: I'm finishing my backlog of bug triage and will do then. If you have suggestions, you are welcome :) (I connected for that purpose)
[20:38] <seb128> didrocks, you can do totem-pl-parser gexiv2 folks
[20:38] <seb128> if you want
[20:38] <seb128> thanks ;-)
[20:38] <bilalakhtar> good evening
[20:38] <didrocks> seb128: will do them, thanks!
[20:38] <seb128> hi bilalakhtar
[20:39] <ronoc> laney: ?
[20:41] <Laney> ronoc: You shouldn't bump the AssemblyVersion for each release
[20:42] <Laney> it's like the SONAME
[20:44] <ronoc> laney, are you talking about that libindicate release ?
[20:44] <Laney> yes
[20:44] <Laney> I saw you highlight bl8 about broken soundmenu in banshee
[20:44] <seb128> tedg, ^
[20:45] <Laney> it's caused by libindicate bumping the assemblyversion
[20:45] <seb128> libindicate is ted's
[20:45] <Laney> you dont' need to do that unless you break ABI
[20:45] <Laney> ok sorry
[20:45] <ronoc> Laney, ok cool
[20:45] <seb128> Laney, http://bazaar.launchpad.net/~indicator-applet-developers/libindicate/trunk/revision/388 is the only commit between versions
[20:46] <Laney> seb128: maybe it's generated by the autofoo
[20:46] <seb128> Laney,
[20:46] <seb128> http://launchpadlibrarian.net/55206785/libindicate_0.4.1-0ubuntu3_0.4.1-0ubuntu4.diff.gz
[20:47] <seb128> would that break it?
[20:47] <Laney> seb128: I'm seeing 0.4.2 in Maverick now
[20:47] <seb128> right but that was a change around the time it broke
[20:48] <seb128> ie the same day
[20:48] <Laney> [assembly: AssemblyVersion ("@VERSION@")]
[20:49] <didrocks> seb128: did you have a look on bug #626040? I see some people on French forum reporting regular segfault on apps too, you telling evolution is crashing, some weird stuff in unity and application closing… do you think it can be related?
[20:49] <ubot2> Launchpad bug 626040 in gtk+2.0 (Ubuntu) (and 1 other project) "libgtk 2.21.6 random segfault with many gdk functions (affects: 1) (heat: 302)" [Medium,Triaged] https://launchpad.net/bugs/626040
[20:50] <Laney> seb128: b-c-e build against 0.4.1, 0.4.2 was uploaded and broke it because they bumped the assemblyversion which means that mono will refuse to load th[D[De library
[20:50] <seb128> didrocks, not really, I've no clue what could be wrong but evo is not crashing there just hanging
[20:50] <seb128> Laney, ok, thanks
[20:50] <didrocks> ok, different issue so
[20:50] <seb128> tedg, ^
[20:50] <seb128> bratsche, hey
[20:50] <seb128> bratsche, do you think you could quickly read the bug didrocks pointed and see if you have any clue about it?
[20:51] <Laney> so yes b-c-e needs a rebuild, but it's unnecessary because i doubt they broke ABI compatibility
[20:51] <Laney> i'll get that done
[20:51] <didrocks> in case, I asked for people pointing that on unity bug to try downgrade and look if they still get this kind of issue
[20:51] <bratsche> seb128, The libgtk random segfault one?
[20:52] <seb128> bratsche, yes
[20:52] <bratsche> Sure.
[20:52] <seb128> thanks!
[20:52] <didrocks> thanks bratsche :)
[20:55] <didrocks> kenvandine: did you remove something in repacking or just tar xzf && tar czf?
[20:55] <bratsche> didrocks, seb128: I don't suppose there's an easier way to reproduce than just wait for it to randomly happen?
[20:56] <kenvandine> didrocks, that' s it
[20:56] <didrocks> kenvandine: still rejected
[20:56] <kenvandine> weird
[20:56] <didrocks> james_w: any idea? ^^ :/
[20:56] <didrocks> same sha256sum
[20:56] <seb128> bratsche, no, didrocks^
[20:56] <kenvandine> interesting
[20:56] <kenvandine> mine was different
[20:56] <didrocks> bratsche: yeah, unfortunately, it seems to be just waiting :/
[20:57] <bratsche> Okay, no worries.  I'll look in the code and see what's going on.
[20:57] <seb128> bratsche, thanks!
[20:57] <bratsche> It's nice that there are stack traces. :)
[20:57] <james_w> didrocks: your repacked tarball is the same as the one on gnome.org?
[20:57] <didrocks> james_w: exactly
[20:57] <james_w> didrocks: um, how did you repack?
[20:57] <didrocks> james_w: tar czf
[20:57] <Laney> same contents i guess
[20:57] <kenvandine> did you copy it back over the .orig?
[20:58] <didrocks> kenvandine: well, I removed the .orig and repack the directory extracted
[20:58] <kenvandine> i did xvf and cvf on the upstream tarball and then copied it to .orig.tar.gz
[20:58] <didrocks> james_w: hum, maybe something with bzr and build-area
[20:58] <kenvandine> mine was different
[20:58] <james_w> didrocks: oh probably
[20:59] <kenvandine> oh, delete that
[20:59] <didrocks> james_w: I bet I got trap with that :)
[20:59] <james_w> didrocks: plus, the pristine-tar will still have the old one
[20:59] <james_w> didrocks: or did you re-merge-upstream?
[21:00] <didrocks> james_w: not for that one, just bzr bd -S in the packaging branch (it's a debian directory only branch)
[21:00] <james_w> didrocks:
[21:00] <didrocks> james_w: but yeah different sha256 now :) was again build-area which copy it back!
[21:00] <james_w> ah, yeah, delete ../build-area and all should be well
[21:00] <didrocks> james_w: sorry for the noise
[21:00] <james_w> np
[21:00] <didrocks> :)
[21:00] <james_w> I realise it's confusing having multiple copies
[21:01] <didrocks> yeah, a symlink will make sense
[21:01] <didrocks> maybe the same for .deb also
[21:01] <james_w> didrocks: good idea, file a bug please
[21:01] <didrocks> james_w: sure, which project bzr-builddeb?
[21:01] <james_w> I might also remove the silly warning from apt and so abolish ../build-area
[21:01] <james_w> didrocks: yes please
[21:01] <didrocks> james_w: doing now, thanks :)
[21:02] <james_w> thank you
[21:15] <james_w> also, https://code.edge.launchpad.net/~mrand/ubuntu-seeds/platform.lucid/+merge/22567 <- if someone could look at that, it would be great
[21:28] <seb128> didrocks, doing the file-roller update
[21:28] <seb128> btw let's not do the gobject introspection update
[21:28] <seb128> it seems to bring issues or require source changes
[21:28] <seb128> it's late in the cycle for that
[21:29] <seb128> so let's revert the commits which port to the new version in the GNOME updates if there is any
[21:29] <seb128> it seems the sort of changes which will bring lot of work and potential trouble for now win
[21:29] <seb128> it probably means we should stay away from some updates
[21:30] <seb128> or just revert commits if those are easy
[21:30] <didrocks> seb128: ok. are you speaking about the libsoup change for gobject introspection?
[21:30] <seb128> not especially
[21:31] <bratsche> didrocks: I don't notice anything changed in gtk+ that would cause this to happen.  The stacktrace shows gdk_gc_set_rgb_fg_color() failing on g_return_if_fail (GDK_IS_GC (gc)), and just below it in the stack trace is setup_gc_with_fg() in nautilus-icon-container.c, where it's doing gc = gdk_gc_new (gtk_layout_get_bin_window (GTK_LAYOUT (container))) the line before.
[21:31] <seb128> didrocks, http://git.gnome.org/browse/libsoup/commit/?id=7f746c10ae683923cc49a923c88996e8c9517094
[21:31] <seb128> seems it's just reverting that change though
[21:31] <didrocks> seb128: yeah, will do libsoup if you aren't on it (finishing folks first)
[21:31] <bratsche> didrocks: What I'm wondering is if there's any chance the icon container hasn't been realized yet, because that would cause gtk_layout_get_bin_window() to fail, and blow up the whole thing.
[21:31] <seb128> didrocks, ok thanks, I'm not on it
[21:32] <didrocks> seb128: you're welcome
[21:32] <bratsche> And I see some other entry points for setup_gc_with_fg() other than the realize() method.
[21:32] <seb128> bratsche, is there any way to figure that?
[21:32] <didrocks> bratsche: hum, would make sense
[21:33] <bratsche> seb128, didrocks: I'm thinking that we could add a check to see if the widget is realized before doing this.. if it's not realized, exit.  This will be called later from the realize() method in NautilusIconContainer
[21:33] <bratsche> didrocks, seb128: The confusing thing is that the reporter claims the error went away when he downgraded to gtk+ 2.21.5
[21:33] <didrocks> and no code change there?
[21:33] <bratsche> But so far I can't reproduce the crash, and I don't know how reliably he could reproduce it either.
[21:33] <seb128> is the issue specific to nautilus?
[21:34] <bratsche> Alex Larsson has some code changes related to clipping.. but the thing is that the error is happening here:
[21:34] <bratsche>         gc = gdk_gc_new (gtk_layout_get_bin_window (GTK_LAYOUT (container)));
[21:34] <bratsche> 	gdk_gc_set_rgb_fg_color (gc, &gcolor);
[21:34] <bratsche> On the second line of that.
[21:34] <bratsche> It wouldn't have gotten to Alex's clipping code yet, so I can't see how it would have affected it.
[21:35] <bratsche> seb128: The poster only mentions Nautilus, and gives vague hints that it could be affecting other stuff.
[21:36] <bratsche> Uhh..
[21:36] <bratsche> Actually setup_label_gcs() already checks if !gtk_widget_get_realized() then it returns.
[21:37] <seb128> bratsche, hum, ok...
[21:37] <seb128> didrocks, bug #637412
[21:37] <ubot2> Launchpad bug 637412 in evince (Ubuntu) "evince-gtk_2.31.92-0ubuntu1 uninstallable (affects: 1) (heat: 8)" [Low,Confirmed] https://launchpad.net/bugs/637412
[21:38] <didrocks> seb128: you see, some people are using evince-gtk :)
[21:38] <seb128> ;-)
[21:38] <didrocks> seb128: will fix it then
[21:38] <seb128> I bet that if you would do an identic copy of evince named evince-gtk people would use it
[21:38] <seb128> just because they can ;-)
[21:39] <didrocks> seb128: hehe, excellent idea! :-)
[21:40] <bratsche> didrocks: Okay, I'm not sure what to do.  I just commented and asked if he can post his .xsession-errors file prior to the crash, maybe that will give some hints with some GLib errors.
[21:40] <seb128> bratsche, thanks!
[21:40] <seb128> bratsche, thank you for investigating it
[21:40] <didrocks> bratsche: great, thanks! It was just a rough guess if that can be related to recent crashes in unity
[21:41] <bratsche> fwiw, I'm not running a Unity session.
[21:41] <bratsche> I dunno if that affects it.
[21:42] <bratsche> didrocks, seb128: Also it looks like all this code went away in git master Nautilus anyway.  Not sure if we'll be getting that in Meerkat though.
[21:43] <seb128> bratsche, we will not
[21:43] <seb128> that's gtk3 work
[21:43] <didrocks> bratsche: not sure people are reporting using unity, just that we got recently a lot of apps crashing under unity particularly and was checking from where it can comes from (weird random issues with apps crashing)
[21:53] <seb128> didrocks, http://yorba.org/download/shotwell/0.7/shotwell-0.7.2.tar.gz
[21:54] <didrocks> seb128: adding to the list :)
[21:54] <seb128> didrocks, want to do that one as well?
[21:54] <seb128> didrocks, then we should be done for today
[21:54] <seb128> thanks
[21:54] <didrocks> seb128: you're welcome
[22:31] <cyphermox> bbl
[22:52] <seb128> ok, enough for today, 'night
[23:07] <didrocks> ok, time for bed, good night everybody!
[23:09] <GrueMaster> Hey, out of curiosity, has anyone thought of adding x86_64 to the UNE build list?  Obviously too late for maverick, but might be something to consider for N.
[23:09] <GrueMaster> I'm running today's amd64.iso on my Acer Aspire One 532H now.
[23:14] <RAOF> pitti: Really?  Starting gdm on (stopped udevtrigger) doesn't regress startup time for the mini 10?  We should switch to that, then; it's safer.


[01:45] <thumper> babbageclunk: how's things?
[01:46] <babbageclunk> thumper: middling
[01:46] <thumper> got time for a quick chat?
[01:46] <babbageclunk> thumper: sure - 1:1?
[01:46] <thumper> ack
[04:47] <thumper> jam: ping
[04:47] <jam> hi thumper
[04:47] <thumper> jam: are you able to make our 1:1 tomorrow given NZ is now in DST?
[04:47] <jam> sorry I missed tech board, time change through me off
[04:48] <jam> thumper: I will probably be slightly late because of bus drop off, but I think I can make it
[04:48] <thumper> jam: ok
[05:22] <wallyworld> jam: i'd love to be able to land this before we go to beta tomorrow if you had a chance to review https://github.com/juju/juju/pull/7906 ; it's an enhancement to the juju list-offers command
[05:23] <jam> in standup now, will try to give it a look
[05:23] <wallyworld> ok, thanks
[05:56] <wallyworld> anastasiamac: can i have a review for a small PR? i'd like to land it before tomorrow's beta. it removes an unneeded status doc from the db https://github.com/juju/juju/pull/7907
[06:01] <anastasiamac> wallyworld: of course u can... :D
[06:01] <wallyworld> yay
[11:06] <wallyworld> jam: thanks for review; i think toy are right it was confusing. i've updated the param names and help test - hopefully it is clearer now? could you PTAL?
[11:09] <jam> wallyworld: what is read permission on an offer if not the right to consume it? You have the right to know the offer exists?
[11:09] <wallyworld> correct
[11:09] <wallyworld> it will show in search results
[11:09] <wallyworld> we have read, consume, admin
[11:12] <jam> wallyworld: lgtm
[11:14] <wallyworld> jam: yay, tyvm
[11:14] <wallyworld> thanks for asking for the clarifications
[21:31] <wallyworld> thumper: we having release call?
[21:31] <thumper> yeah
[21:34] <mup> Bug #1721159 opened: partial sync when leader_id is empty, yielding inconsistent mirror <juju:New> <juju-core:New> <ubuntu-repository-cache (Juju Charms Collection):New> <https://launchpad.net/bugs/1721159>
[21:43] <mup> Bug #1721159 changed: partial sync when leader_id is empty, yielding inconsistent mirror <juju:Incomplete> <juju-core:Won't Fix> <ubuntu-repository-cache (Juju Charms Collection):New> <https://launchpad.net/bugs/1721159>
[21:48] <wpk> balloons: Do we have any juju CI tests on Artful?
[21:48] <balloons> wpk, we do a deploy, and can target anything you wish
[21:49] <mup> Bug #1721159 opened: partial sync when leader_id is empty, yielding inconsistent mirror <juju:Incomplete> <juju-core:Won't Fix> <ubuntu-repository-cache (Juju Charms Collection):New> <https://launchpad.net/bugs/1721159>
[21:51] <wpk> balloons: with netplan merged I'd test artful as a host for container and as a container, in different combinations with xenial (artful on xenial, xenial on artful, artful on artful)
[21:51] <balloons> wpk, we have some of what you are after
[21:52] <balloons> artful on artful
[21:52] <wpk> and it worked? (it shouldn't :)
[22:04] <mup> Bug #1721159 changed: partial sync when leader_id is empty, yielding inconsistent mirror <juju:Incomplete> <juju-core:Won't Fix> <ubuntu-repository-cache (Juju Charms Collection):New> <https://launchpad.net/bugs/1721159>


[01:44] <znf> JanC, nah, just got a 100Gbit broadcomm adapter with RDMA/SRV-IO enabled
[08:04] <nibbon_> cpaelzer: I cracked the Windows issue
[08:05] <nibbon_> the problem is due to this change: https://github.com/qemu/qemu/commit/af1b80ae56c9495999e8ccf7b70ef894378de642
[08:05] -ubottu:#ubuntu-server- Commit af1b80a in qemu/qemu "i386/acpi: fix inconsistent QEMU/OVMF device paths"
[08:07] <nibbon_> upstream proposed a workaround to make it work up to 5.1 https://github.com/qemu/qemu/commit/0a343a5add75f9f90c65e932863d57ddbcb28f5c
[08:07] -ubottu:#ubuntu-server- Commit 0a343a5 in qemu/qemu "i386/acpi: restore device paths for pre-5.1 vms"
[08:08] <nibbon_> tl;dr if you migrate a Windows instance from Focal (4.2) to Jammy (6.2), as long as the instance is restarted with machine type = "xxx-6.2", creates new network interfaces. If they rely on DHCP, no problem, but any static configuration is lost in the void
[08:11] <cpaelzer> nibbon_: so a migration without changing the type works, but the upgrade of the type switches the pci-id and due to that it is lost - is that the right summary?
[08:12] <nibbon_> cpaelzer: yeah, live migrating a workload persist the machine type; when the workload is stopped and started back, may take the new machine type which leads Windows to create new interfaces - screwing up those with static configuration
[08:13] <nibbon_> solution are: either persist the machine type when the instance is restarted or introduce this patch https://paste.debian.net/hidden/964a45eb/
[08:13] <nibbon_> I'm currently testing the latter in my env, and it's working fine
[08:14] <cpaelzer> nibbon_: even stop/start should keep the machine type as it is in the guest XML definition of libvirt. Or are you running qemu directly (sorry if you told me before I forgot that detail)
[08:15] <nibbon_> cpaelzer: our custom orchestrator uses the greatest machine type available and it's out of my reach changing that :/
[08:16] <cpaelzer> nibbon_: ah I see, well bumping the machine type will imply changing virtual hardware
[08:16] <cpaelzer> which is just what you see
[08:16] <cpaelzer> I mean, it is great to change to later types as a well controlled update (like when you qualify and switch to a new generation of silicon)
[08:16] <cpaelzer> But switching the type => give me the new things
[08:18] <nibbon_> cpaelzer: I'm aware of that; however, we have been doing that for ages and it's the first time we hit such an issue
[08:18] <cpaelzer> And that patch is very specific (just 6.2 is changed) and would likely break live migrations as they would have 0 on the source and 1 on the target node. So we would change that underneath their feet even if they kept the machine type.
[08:18] <cpaelzer> That sounds like something that can't be applied to Ubuntu that tries to work for everyone and every use-case
[08:19] <cpaelzer> I've seen issues like this a few times, maybe once every year. But that very much depends on whic huse case and (virtual) HW you are using.
[08:19] <cpaelzer> essentially each change to a type in the file you patched there is such a change - and they have a lot more via the compat entries.
[08:20] <cpaelzer> TL;DR I'd love to help you but a) your suggested change will likely break others and b) you are switching type so you can not really insist on virtual HW being the same as before
[08:22] <nibbon_> hmm, you have a point wrt live migration; nevertheless, I haven't spotted any issue while performing tests in my env (being linux or windows workloads involved). I'll perform more tests
[08:23] <nibbon_> can you articulate more about the compat entries?
[08:24] <nibbon_> (asking for a friend who's likely left alone in this endeavor :P)
[08:25] <cpaelzer> hehe
[08:28] <cpaelzer> what I mean is people often look at e.g. hw/i386/pc_q35.c (or piix) and think that is all that changed. But you also have the entries in hw/i386/pc.c representing "changes in virtual HW when changing machine type"
[08:31] <nibbon_> right
[21:17] <oramirez> Hi all,  I got a question to anyone. I have install pro and attached the token to the computer. I was able to add the machine to the landscape server, however when I look in the Ubuntu Pro Tab, I get the message that This computer is not attached to an Ubuntu Pro entitlement. I might be misunderstanding this. Does Landscape is unable to see that I
[21:17] <oramirez> do have a Pro subscription?
[21:20] <JanC> you probably better ask Landscape/Canonical support about that