[00:00] <robert_ancell> ok
[00:00] <rickspencer3> my fault, sorry guys
[00:00] <TheMuso> np
[00:02] <bryceh> heya
[00:02]  * bryceh grabs coffee
[00:07]  * RAOF will need to get milk before coffee is a viable option.
[00:08] <TheMuso> heh
[00:09] <jasoncwarner> TheMuso bryceh RAOF robert_ancell
[00:09] <jasoncwarner> back...ready for https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-04-05
[00:09] <jasoncwarner> ?
[00:09] <jasoncwarner> :)
[00:09] <RAOF> Wooo!  My long, long delayed patch to make dh_clideps error out when it can't resolve dependencies has landed!
[00:09] <bryceh> ayup
[00:09] <TheMuso> RAOF: nice.
[00:10] <RAOF> TheMuso: Yeah.  Now things will fail to build rather than fail to run on systems without the appropriate -dev packages installed :)
[00:10] <jasoncwarner> RAOF: nice :) (not that I know what that is, but I'm happy you're happy)
[00:10] <TheMuso> Its mono related.
[00:10] <jasoncwarner> anyway...jumping into meeting
[00:10] <jasoncwarner> [TOPIC] X.org
[00:11] <bryceh> bugs consuming most of the time these days
[00:11] <RAOF> Bugs, bugs, bugs, bugs…
[00:11] <bryceh> I've been focusing heavily on -intel gpu lockup bugs since they're still coming in at a high rate
[00:12] <bryceh> mostly been trying to push them upstream quickly, so we can get patches to give to the kernel team
[00:12] <RAOF> I'm testing libdrm 2.4.24; it's got a bunch of intel bugfixes which resolve some bugs.
[00:12] <bryceh> RAOF, for the one bug we know about, I cherrypicked and uploaded the patch
[00:13] <bryceh> 2.4.24 has some other fixes but they look to me less relevant for natty
[00:13] <TheMuso> I really should hammer my recently acquired intel GPU more...
[00:13] <bryceh> and there were some instances of fixes-for-the-fixes ;-)
[00:13] <TheMuso> But when at home and working, I tend to prefer my desktop...
[00:14] <bryceh> RAOF, anyway so I'm wondering if maybe we should just hold off on updating libdrm and just pull in specific fixes if/when needed?  but I don't have strong feelings
[00:14] <RAOF> bryceh: Yeah.  Some of the 2.4.24 fixes are for new userspace on old kernels, which we don't much care about.
[00:14] <bryceh> today I also went through all of the -ati bugs and pushed about half upstream, and made a pass through -fglrx but most bugs there are invalid things from weird self-installs or whatnot
[00:15] <TheMuso> I thought things had to be rather tightly in sync for intel...
[00:15] <bryceh> TheMuso, sometimes
[00:15] <RAOF> If you want it to *work* :)
[00:15] <bryceh> TheMuso, libdrm 2.4.24 is mainly just a small handful of bug fixes
[00:15] <TheMuso> Ah ok.
[00:16] <jasoncwarner> hey bryceh, is the new fglrx driver included for those systems? I have a system running radeon and would like to try latest binary driver
[00:17] <bryceh> jasoncwarner, yes you should be able to update to latest and then use jockey to install fglrx
[00:17] <bryceh> since fglrx arrived with so little time before beta1 we were able to get it in, but not update jockey
[00:17] <jasoncwarner> bryceh: awesome!
[00:17] <jasoncwarner> thanks
[00:17] <bryceh> so you need to update past beta1 and then can install it normally
[00:18] <jasoncwarner> cool...I'm upto date as of this morning so I should be fine...computer is media center upstrairs so I'll give that a go when we are done here
[00:18] <bryceh> anyway, the rate of incoming bugs is starting to exceed my capacity to keep up with them
[00:18] <bryceh> http://www.bryceharrington.org/Arsenal/Reports/ubuntu-x-swat/totals-natty-workqueue.svg
[00:18] <bryceh> help would be appreciated.  I figure by beta2 the rate will just be too high to be able to stay on top of the bugs any further
[00:20] <RAOF> I'll do some more bug work, then.
[00:20] <jasoncwarner> Yikes! Ok...anyone that can give bryceh a hand, that would be awesome...seems that trend line is going crazy
[00:20] <RAOF> That's a terribly impressive graph, though.
[00:21] <bryceh> RAOF, thanks; in particular I haven't kept up with mesa, nouveau, or input drivers.
[00:21] <bryceh> although numbers for those are small
[00:22] <bryceh> I figure once we shut off the apport gpu and crash hooks that'll ease a little bit of pressure
[00:22] <bryceh> but probably should wait until post-beta2 to do that
[00:22] <TheMuso> Actually interesting you should mention that, for natty beta there hasn't been the super influx of audio bugs like usual, so thats good news. :)
[00:22] <bryceh> jasoncwarner, anyway I'm rambling now.  I'm done :-)
[00:23] <jasoncwarner> :)
[00:23] <jasoncwarner> cool
[00:23] <jasoncwarner> next topic [TOPIC] AOB
[00:23] <jasoncwarner> anythign else anyone wants to talk about?
[00:24] <micahg> o/
[00:25] <RAOF> Have other people noticed moderately high CPU usage in Banshee?  ~10% when playing with the window open?
[00:25] <jasoncwarner> RAOF: ;) you know I did yesterday :)
[00:25]  * TheMuso doesn't use banshee, there are still a11y issues with that, I really ort to dig into that a bit deeper.
[00:25] <TheMuso> But I was personally happy with rhythmbox.
[00:25] <TheMuso> s/was/am/
[00:26] <RAOF> There's no smoking gun in the profile, but since it doesn't seem to occur when the window is closed there are some good leads.
[00:27] <jasoncwarner> thanks, RAOF....keep digging..seems weird that it would jump to that much CPU just to play music...weird...
[00:27] <jasoncwarner> thanks!
[00:27] <jasoncwarner> Sounds like we are about done...Anything else before we call the meeting?
[00:27] <micahg> o/
[00:27] <TheMuso> Its mono. What else do you expect? :)
[00:27]  * TheMuso ducks.
[00:27] <jasoncwarner> micahg: ?
[00:27] <micahg> I wanted to ask about webkit 1.4
[00:27] <jasoncwarner> micahg: go ahead
[00:28] <micahg> is robert_ancell planning on working on that?
[00:28] <robert_ancell> micahg, yes, there's a problem with the documentation build, working on that today
[00:28] <micahg> robert_ancell: ok, great thanks
[00:28] <robert_ancell> 1.3.13 that is, still waiting for 1.4.0...
[00:29]  * micahg thought 1.4.0 would come with GNOME3 this week
[00:29] <TheMuso> Do I read the release schedule incorrectlyk, or is there no beta freeze for beta 2?
[00:29] <micahg> jasoncwarner: that's it, thanks :)
[00:29] <micahg> TheMuso: apr 11
[00:30] <TheMuso> Ah makes sense.
[00:30] <TheMuso> Thats kinda cool, because it means I have some, if not all of Monday to do work. :)
[00:30] <micahg> actually, I think almost everyone has all of monday
[00:30] <RAOF> :)
[00:31] <TheMuso> ah ok.
[00:31] <TheMuso> So its EOD Monday.
[00:31]  * micahg thought freeze was 23:00 UTC monday
[00:31] <TheMuso> Could very well be.
[00:31] <RAOF> Oh, so I'll have time to work on my birthday, too. :)
[00:31] <TheMuso> lol
[00:32] <micahg> robert_ancell: I'm assuming there haven't been any unplanned ABI breaks for webkit?
[00:32] <robert_ancell> micahg, in 1.3.13?
[00:32] <jasoncwarner> RAOF: nice...now none of us have excuses for not remember your bday ;)
[00:32] <micahg> robert_ancell: yes
[00:33] <robert_ancell> micahg, I didn't see any
[00:33] <TheMuso> jasoncwarner: My thoughts exactly.
[00:33] <jasoncwarner> ( RAOF : not saying we will...we just don't have excuses)
[00:33] <RAOF> jasoncwarner: It's a cunning ploy!
[00:33] <micahg> robert_ancell: also, could 1.2 be installed alongside 1.4?
[00:33] <jasoncwarner> Ok...going to call the official meeting...[END MEETING]
[00:34] <bryceh> thanks
[00:34] <seb128> hey robert_ancell
[00:34] <robert_ancell> micahg, looking, I think not though
[00:34] <robert_ancell> seb128, hey
[00:34] <TheMuso> thanks.
[00:34] <seb128> robert_ancell, just a reminder, if you update gvfs it uses merge-upstream so don't just run dch ;-)
[00:35] <robert_ancell> seb128, yeah, I know!  I'll probably just do something wrong though...
[00:35] <seb128> lol
[00:35] <robert_ancell> seb128, so the process is to run merge-upstream, then debcommit -r? or just bzr commit?
[00:36] <seb128> robert_ancell, debcheckout gvfs; cd gvfs; bzr merge-upstream --version 1.8.0 tarball_url
[00:36] <robert_ancell> micahg, no, they would conflict
[00:36] <seb128> robert_ancell, then dch -i, do you packaging tweaks
[00:36] <seb128> debcommit -r, push, upload
[00:37] <robert_ancell> seb128, yeah, I think I keep forgetting the -r, then it doesn't tag and it gets confused
[00:37] <seb128> robert_ancell, if you do gvfs maybe include http://bugzilla-attachments.gnome.org/attachment.cgi?id=185180
[00:37] <seb128> robert_ancell, it's an upstream patch for bug #682850
[00:38] <seb128>
[00:38] <seb128> otherwise out of gvfs
[00:38] <robert_ancell> bug 682850
[00:38] <seb128> https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/682850
[00:38] <seb128> no bot?
[00:38] <robert_ancell> seb128, you're the bot today?
[00:39] <seb128> lol
[00:39] <seb128> no :p
[00:39] <seb128> well we can as well wait for that on to land in git
[00:39] <seb128> so don't bother maybe for that update
[00:39] <micahg> robert_ancell: ugh, that will make migrating away from xulrunner a little harder in the stable releases
[00:39] <robert_ancell> micahg, didn't upstream just say "no more xulrunner?". So hopefully everyone will be migrating away from it anyway!
[00:40] <seb128> robert_ancell, other topic while I'm still around, did you figure the documentation index ?index... error thing? I saw you fixed it for nautilus but other components have similar bugs
[00:40] <robert_ancell> seb128, which other components?  gedit seemed fine, and I haven't seen any others
[00:40] <seb128> robert_ancell, it was reported on gnome-panel at least
[00:41] <robert_ancell> the issue seemed to be anything accessing documentation from gnome-user-guide (which is V3 now)
[00:41] <micahg> robert_ancell: yes, so I was going to try to backport some of the newer versions of apps based on webkit, but most require some version of 1.3 as the minimum, I was thinking to rename 1.4 to like webkit-1.4 or something in the stable releases so these apps can basically be forklifted in
[00:41] <robert_ancell> micahg, renaming causes so many ongoing issues...
[00:42] <micahg> robert_ancell: well, it would just be for lucid and maverick and only for xul rdepends, I wouldn't want to touch the regular webkit aside from upgrading it :)
[00:42] <micahg> upgrading from the same branch 1.2.x
[00:42] <seb128> robert_ancell, urg, side effect of upgrading I guess, but it means we have user documentation describing GNOME3 on a GNOME 2.32?
[00:44] <robert_ancell> seb128, yes it's a bit of a mess. I'm hoping our doc people will modify it to fit.  In the case of nautilus some deprecated feature documentation was gone, but that's not a big issue for us
[00:44] <seb128> it's not like the documentation was uptodate or than users read it anyway...
[02:00] <RAOF> Ah.  *That's* why the overlay scrollbars are ugly on banshee!
[02:03] <RAOF> Incidentally, if we felt like making banshee start up faster we should really look into AOT compilation for some mono stuff; Banshee spends a bit more than 2 seconds JITing code on my machine.
[02:06] <TheMuso> youch
[02:06] <TheMuso> RAOF: Something for next cycle.
[02:06] <RAOF> Yup.
[02:06] <TheMuso> I can only imagine how mono performs on atom CPUs.
[02:06] <TheMuso> Or arm for that matter.
[02:07] <RAOF> Not all of that is during startup, though; that's for an entire run.  Much of it will be during startup, though.
[02:07] <TheMuso> Yeah.
[02:07] <RAOF> Yeah.  They'd *really* want AOT wherever possible.
[02:35] <TheMuso> Wow, I wonder if the international issues are biting others on here... Appears to be between US/EU, or somewhere in the US.
[02:36] <RAOF> TheMuso: What are you seeing?  Unable to resolve canonical.com again?
[02:36] <TheMuso> RAOF: Yeah. From what I've been reading, there are some major issues with a teer 1 provider in the US, level 3 or another of the big providers.
[02:37] <TheMuso> They were ok overnight it seems, but are falling over again, as evidence by me no longer being able to resolve ubuntu/canonical.com again.
[02:37] <TheMuso> ...and my several freenode and other IRC network dropouts.
[02:37] <RAOF> Eh.  Whatever it is, it's not hitting my internode connection.
[02:38] <TheMuso> No, since Internode takes other paths out of Oz.
[02:38] <TheMuso> SOmething which I wish Telstra would do...
[02:38] <TheMuso> But overall I am on a good bundle with telstra atm for phone/mobile/net, and can get cable so, that makes things difficult if I want to move.
[02:39] <TheMuso> I'd go internode in a heartbeat if the line I had here was deacent quality/speed.
[02:44] <TheMuso> I actually find it weird that for Telstra, we go via the US to get to EU.
[02:51] <RAOF> I find it a bit weird that there are different routes for different carriers.
[02:51] <RAOF> It's not like we've got a huge web of intercontinental links.
[02:51] <TheMuso> Yeah. A deacent provider should depend on multiple routes.
[02:52] <TheMuso> Trouble is, Telstra half owns Reach, one of the major teer 1 providers for Aus, so...
[02:52] <TheMuso> They aren't likely to use anybody else.
[08:02] <didrocks> good morning
[08:06] <jasoncwarner> morning didrocks!
[08:06] <pitti> good morning everyone!
[08:06] <jasoncwarner> morning pitti
[08:06] <pitti> hey jasoncwarner, how are you?
[08:06] <jasoncwarner> pretty good.., you ?
[08:07] <jasoncwarner> btw...looks like with you springing forward, and me falling back...the 1:1 is now 2 hours earlier ;) what do you think? want to jump on mumble?
[08:08] <pitti> jasoncwarner: sure
[08:08] <pitti> jasoncwarner: I'm in
[08:08] <jasoncwarner> just realizsed...never setup mumble after installing SSD...give me a few minutes
[08:10] <didrocks> morning jasoncwarner, pitti!
[08:34] <ricotz> pitti, good morning
[08:35] <ricotz> pitti, could you take a look at https://edge.launchpad.net/ubuntu/+source/libgtop2/2.28.3-0ubuntu1
[08:41] <rodrigo_> morning
[08:41] <desrt> rodrigo_: hihi
[08:42] <rodrigo_> hey desrt
[08:44] <ricotz> rodrigo_, hey
[08:46] <rodrigo_> hi ricotz
[08:47] <ricotz> rodrigo_, feel free to update some ppa packages :), i will stop for now, but i will take care of gedit
[08:48] <glatzor> moring mvo
[08:48] <pitti> ricotz: what about it? (sorry, was on phone)
[08:48] <mvo> hey glatzor!
[08:48] <pitti> ricotz: you want it NEWed?
[08:48] <glatzor> mvo, I am not sure which lintian tags to use by default.
[08:49] <pitti> meh, LP going down?
[08:49] <rodrigo_> ricotz, I have updated a few in some spare moments, but I'm bug fixing, so going slowly
[08:49] <didrocks> rodrigo_: hey
[08:49] <ricotz> pitti, hi, yes ;)
[08:49] <glatzor> mvo, I already added the option to load distro specific tags files
[08:49] <rodrigo_> hi didrocks, pitti
[08:49] <didrocks> rodrigo_: any idea why a gobject_new can crash apart from "no more memory"? https://launchpadlibrarian.net/68241093/Stacktrace.txt
[08:49] <didrocks> rodrigo_: the line is   child = g_object_new (NA_TYPE_TRAY_CHILD, NULL);
[08:50] <rodrigo_> didrocks, looking
[08:50] <mvo> glatzor: oh, I did not see that in the code
[08:50] <didrocks> (and yeah, it's not a computing error, we are using that functions hundreds of time)
[08:50] <mvo> glatzor: look at the data/lintian-checks from my branch, its a subset of the ftp-master tags from lintian
[08:50] <mvo> glatzor: but I removed the ones that where obviously not good
[08:51] <mvo> glatzor: like /opt in the package
[08:51] <mvo> thats fine for us
[08:51] <xclaesse> argh, postinst of the new kernel has a stupid typo
[08:51] <ricotz> rodrigo_, no problem, i wont upload to it for some hours
[08:51] <xclaesse> && die
[08:51] <xclaesse> instead  of || die
[08:51] <rodrigo_> didrocks, hmm
[08:51] <didrocks> rodrigo_: puzzling, isn't it? ;)
[08:51] <mvo> glatzor: just fyi, I look at #742935 next
[08:51] <pitti> ricotz: done
[08:52] <ricotz> pitti, thanks
[08:52] <mvo> glatzor: looks like a double release of a fd or something
[08:52] <rodrigo_> didrocks, if it's not a coding error, it's either out of memory or memory corruption
[08:52] <glatzor> mvo, I would like to make the changes more transparent. so not removing checks but commenting them out. But how to handle overrides? should we call lintian twice? once with --no-override and the fatal tags and once with the non-fatal ones?
[08:52] <rodrigo_> although the object pointer (0x1000000) looks weird indeed
[08:52] <mvo> glatzor: that sounds sensible
[08:53] <mvo> glatzor: did you merge my other stuff as well? like the exitcode check ? currently we report bad-quality even if its lintian itself that is failing :)
[08:53] <rodrigo_> didrocks, can you easily replicate?
[08:53] <didrocks> rodrigo_: not at all
[08:54] <rodrigo_> didrocks, memory corruption then?
[08:54] <didrocks> rodrigo_: yeah, the new object pointer adress is what tell me it's out of memory
[08:54] <didrocks> rodrigo_: I would say so
[08:54] <didrocks> rodrigo_: will confirm with Neil as well, thanks :)
[08:54] <rodrigo_> didrocks, no problem :)
[08:54] <rodrigo_> didrocks, if someone can replicate, running it with valgrind will give the answer
[08:57] <didrocks> rodrigo_: yeah, but it seems $random, even if I try to add/remove a lot of apps appearing in the systray
[08:57] <rodrigo_> ok
[09:02] <seb128> hey
[09:02] <rodrigo_> hi seb128
[09:02] <seb128> hey rodrigo_, how are you?
[09:04] <rodrigo_> seb128, I'm fine, and you?
[09:04] <seb128> I'm a bit tired today, I stayed up quite late, but otherwise ok
[09:05] <seb128> getting some coffee so it should be better after that ;-)
[09:07] <rodrigo_> yeah, saw last night you were late working
[09:20] <seb128> pitti, hey
[09:21] <pitti>  bonjour seb128
[09:21] <seb128> pitti, how are you?
[09:22] <pitti> seb128: pretty well, thanks! et toi?
[09:22] <seb128> I'm a bit tired but fine otherwise
[09:22] <seb128> pitti, did you already see the retracers crash on what is current in the amd64 log?
[09:22] <seb128> in get_source_tree
[09:22] <pitti> I didn't, no
[09:23] <seb128> pitti, do you want apport bugs for such cases or should I just declare the bug buggy untag and restart?
[09:23] <pitti> AssertionError: could not determine source tree root directory
[09:23] <seb128> (well restart when launchpad will be back to rw)
[09:23] <pitti> seb128: I think this is worth fixing
[09:24] <pitti> seb128: in particualr, it should just skip the source stack trace here, as it usually seems to work
[09:24] <pitti> seb128: I'll fix it right now
[09:24] <seb128> pitti, ok, thanks a lot!
[09:25] <pitti> hm, hang on
[09:25] <pitti> this assertion is really justified, I guess it's a special case with a weird naming
[09:25] <seb128> oh?
[09:29] <pitti> PYTHONPATH=. python -c 'import apport; print apport.packaging.get_source_tree ("indicator-weather", "/tmp/x", "11.03.27+repack-0ubuntu1")'
[09:29] <pitti> hm, that doesn't crash here :/
[09:29]  * pitti tries in teh chroot
[09:30] <pitti> ImportError: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by /tmp/tmpfREm2I/usr/lib/libapt-pkg.so.4.10)
[09:30] <pitti> le huh?
[09:31] <pitti> apt-get itself is broken now :/
[09:31] <pitti> ah, ignore me; was in the lucid dchroot
[09:33] <pitti> seb128: meh, NFC I'm afraid; I can't reproduce it in the chroot either :/
[09:34] <pitti> and now we need to wait for LP to come back anyway, once it does I'll try a manual apport-retrace
[09:34] <seb128> pitti, ok
[09:44] <seb128> does anyone know if geoclue will activate on demand?
[09:45] <seb128> bug #740484 is a crasher that some users seem to get when it start but the computer is not online yet
[09:45] <seb128> but that's a non issue if it get respawned later I guess
[09:46] <seb128> https://bugs.launchpad.net/ubuntu/+source/geoclue/+bug/740484
[09:46] <seb128> other polkit-gnome has an assert quite some users are running into: https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/741425
[09:46] <seb128> could be a crash on logout though
[09:50] <chrisccoulson_> good morning everyone
[09:53] <glatzor> mvo, since lp is down I will merge the lintian branch in the evening.
[09:53] <mvo> glatzor: thnx
[09:53] <mvo> glatzor: yeah, its a bit anoying for me as well, if only bzr would stay up
[09:54] <glatzor> mvo, you can now ship a separate data/lintian-nonfatal.tags.Ubuntu and data/lintian-fatal.tags.Ubuntu
[09:54] <seb128> hey chrisccoulson_
[09:54] <seb128> hey glatzor mvo
[09:54] <chrisccoulson_> hi seb128, how are you?
[09:54] <glatzor> mvo, I recently discovered "import lsb_release; lsb_release.get_distro_information()". Makes life easier.
[09:54] <seb128> chrisccoulson_, I'm fine though a bit tired, what about you?
[09:55] <glatzor> hello seb128 !
[09:55] <glatzor> seb128, mvo, see you guys! have to go to work now.
[09:55] <seb128> have fun ;-)
[09:56] <chrisccoulson_> seb128 - yeah, a bit tired too. bug 663294 is giving me a real headache now
[09:57] <rodrigo_> oh, lp in read-only mode
[09:57] <mvo> glatzor: great work!
[09:57] <mvo> glatzor: thanks and see you
[09:59] <glatzor> mvo, I plan to revert 596.1.1 and just switch to a non-interactive session if the controlling terminal cannot be attached
[09:59] <glatzor> mvo, it was a stupid idea to keep the tty open all the time.
[10:00] <glatzor> have a nice day!
[10:00] <GunnarHj> pitti: Good day, Martin!
[10:00] <GunnarHj> pitti: Even if you seem to be busy, do you have time to sponsor the l-s side of bug 742857? Basically you already read to document last Friday.
[10:00] <GunnarHj> pitti: While I think the document should be uploaded for Natty, I suggest that translations are postponed as explained in comment #7.
[10:11] <mvo> dpm: hello! sorry if I missed your answer yesterday, but when is the next natty langpack upload planned?
[10:11] <mvo> dpm: there is a file overwrite issue (with packagekit.mo) in the current ones
[10:12] <pitti> mvo: do you need one urgently? I was planning to do a new -base one for beta-2
[10:12] <mvo> not urgently, just would be nice to know when to expect the auto-upgrade-tester to go more "non-red" again
[10:12] <dpm> mvo, sorry, it was me who missed the question, pitti can answer this one best ^
[10:12] <pitti> mvo: bug 744831 you men?
[10:12] <pitti> mean
[10:12] <pitti> hey GunnarHj
[10:13] <mvo> yes
[10:13] <didrocks> Sweetshark: hey, did you get to the static unity Quicklist bug on libreoffice?
[10:13] <pitti> GunnarHj: oh, sure, I'll be happy to
[10:14] <pitti> GunnarHj: let's see how far I get while LP is readonly
[10:14] <pitti> ssh: connect to host bazaar.launchpad.net port 22: Connection refused
[10:14] <pitti> meh
[10:14] <pitti> GunnarHj: I'll do that as soon as it comes back online
[10:14] <Sweetshark> didrocks: bug 720716?
[10:14] <GunnarHj> pitti: Thanks!
[10:15] <pitti> GunnarHj: it's still sitting in my mailbox, was planning to do that anyway today (was busy with a rather big patch/debugging session Mo/Tu, sorry)
[10:15] <Tommeh> Hi all. Currently having fun with gnome-shell, but missing all the themes (and no apparent application to switch themes either)
[10:15] <Sweetshark> didrocks: I will give it a try today.
[10:15] <Tommeh> Currently have gnome-shell installed via the gnome3 ppa, on Natty 11.04 Beta.
[10:15] <seb128> launchpad is back
[10:15] <didrocks> Sweetshark: yeah, this is important to design and we should give time to translator
[10:15] <GunnarHj> pitti: No problem. I understand that you always are busy with about 100 things. :)
[10:15] <Tommeh> The following packages have unmet dependencies:
[10:15] <Tommeh>   gnome-themes: Depends: gtk3-engines-pixbuf which is a virtual package.
[10:16] <Sweetshark> didrocks: backports were a bit nasty this time around.
[10:16] <Tommeh> That's what I get when I try to install gnome-themes from the PPA.
[10:16] <didrocks> I think natty > backports :)
[10:16] <seb128> Tommeh, hi, try #ubuntu for user questions but basically GNOME dropped the appearance capplet and there is only one theme available for the new gtk
[10:17] <desrt> Tommeh: and gnome-tweak-tool is your friend
[10:17] <seb128> right, natty > backports, I agree with didrocks
[10:17] <Sweetshark> didrocks: me too. But my inbox disagrees usually.
[10:17] <desrt> Tommeh: you can just check it out of git and run it directly from the checkout.  no need to compile.
[10:18] <Tommeh> desrt/seb128: thanks.
[10:18] <desrt> Tommeh: it lets you change quite a lot of things, including the theme
[10:18] <didrocks> Sweetshark: check with chrisccoulson_ and dpm for translation btw, they dealt with that in the same case than yours (meaning: translation not in launchpad)
[10:18] <seb128> pitti, I'm restarting the i386 retracer and let the amd64 down for you to debug
[10:18] <pitti> seb128: oh, LP back up?
[10:18] <desrt> Tommeh: changing the theme of the shell itself is somewhat more complicated -- it involves replacing a directory in /usr... but it is possible
[10:18] <pitti> seb128: I'm currnetly logged into the amd64 one
[10:18] <Tommeh> Currently I'd be happy with the stnadard theme
[10:18] <seb128> pitti, yes, it's back
[10:18] <pitti> nice
[10:19] <Tommeh> I'm on some form of horrid 'fallback' gnome theme at the minute :)
[10:19] <pitti> awesome
[10:19] <desrt> Tommeh: oh.  install the gnome-themes-standard package
[10:19] <desrt> it has adwaita in it
[10:19] <Tommeh> Ah, I've done that since removing a conflicting package (gnome-accessibility-themes)
[10:19] <Tommeh> But gnome-themes won't install from the PPA
[10:19] <Tommeh> It's still the natty version.
[10:19] <Tommeh> Due to the error above
[10:19] <desrt> don't worry about that one.  gnome-themes-standard is what is necessary
[10:20] <Tommeh> Depending on a package that isn't in the PPA
[10:20] <Tommeh> Ahh, OK
[10:20] <Tommeh> Logout time -- brb :)
[10:20] <desrt> just logout -> back in
[10:20] <desrt> ya :)
[10:20] <pitti> seb128: hm, did you just rm the log file?
[10:20] <seb128> pitti, rotated it sorry
[10:20] <pitti> ah
[10:20] <seb128> pitti, it's log_20110406.gz
[10:21] <pitti> yep, thanks
[10:21] <Tommeh> Bang, I has a theme.
[10:21] <Tommeh> Many thanks desrt :)
[10:21] <seb128> pitti, I want a clean log will make easier to run my "get recent bugs which get duplicates"
[10:21] <pitti> *nod*
[10:24] <desrt> Tommeh: no problems :)
[10:25] <pitti> GunnarHj: great job!
[10:25] <Tommeh> It doesn't seem to like letting me manage two screens .. I have one screen that I can switch between workspaces, and one that's just 'stuck' with one workspace... Almost like it was never intended to be managed.
[10:25] <pitti> GunnarHj: one question, why did you add a no-op on_button_load_help_clicked()?
[10:25] <pitti> GunnarHj: isn't setting the uri button propery enough?
[10:25] <Tommeh> But that's almost nice, as I can have persistant applications (like xchat) in on screen, whilst switching others.
[10:28] <pitti> GunnarHj: it works fine without; do you mind if I remove the dummy handler while merging?
[10:29] <GunnarHj> pitti: If it works, I don't mind at all.
[10:29] <GunnarHj> pitti: GTK is another area I know very little about. :(
[10:30] <pitti> GunnarHj: uploaded, thanks a lot!
[10:30] <desrt> Tommeh: multi-monitor is a sore spot in the shell. a bunch of changes landed recently (a couple of weeks ago) to vastly improve the situation but it still leaves quite a bit to be desired
[10:31] <desrt> Tommeh: i sense that it's not a priority for them right now
[10:38] <Tommeh> desrt: I guess so! Well, at least it's not just me :)
[10:38] <Tommeh> I'm happier to know things are weird/broken for everyone, rather than just on my machine.
[10:39] <desrt> Tommeh: the gnome3 PPA is, frankly, one of the worst ways to try gnome3 at the moment
[10:39] <desrt> it's very deeply broken
[10:39] <Tommeh> Yep :(
[10:39] <desrt> which is quite understandable, given that the people behind it have their concerns in other places at the moment
[10:39] <desrt> i expect it will get quite a lot better after the ubuntu release
[10:40] <Tommeh> Finger's crossed :)
[10:40] <pitti> desrt: FWIW, currently writing GNOME30-Live-latest.iso to an USB stick; I'm curious :)
[10:41] <desrt> pitti: i understand the fedora 15 beta is one of the best choices...
[10:44] <cassidy> seb128, since I updated to Natty, Evolution took the bad habit to be confused with some of my imap mails: the title of the mail is correct, but when I click on it it displays a unrelated old mail. Is that a known issue ?
[10:44] <seb128> not that I know about
[10:45] <seb128> like the preview doesn't match you select in the list?
[10:45] <seb128> what protocol do you use?
[10:45] <desrt> pitti: let me know what you think, in any case
[10:45] <pitti> desrt: the mini 10 touchpad still sucks even with gnome 3!
[10:45] <pitti> j/k
[10:45] <cassidy> seb128, imap+.  The preview is correct but the displayed mail is not
[10:46] <desrt> pitti: and the trackpoint on my thinkpad is still red!  i thought this new CSS theme would allow me to customise that!
[10:46] <desrt> where is my refund?!
[10:46] <seb128> cassidy, like if you double click to open it?
[10:46] <seb128> cassidy, I never open email I just read them in the preview
[10:47] <cassidy> seb128, oh yeah. By preview I meant the title in the treeview
[10:47] <cassidy> seb128, the mail is wrong in the pane displaying the full mail and if I double click on it
[10:47] <seb128> cassidy, then no, works correctly there
[10:47] <seb128> check on #evolution on the gnome irc maybe
[10:48] <cassidy> seb128, how hard are you patching evolution? ie, should I open an upstream or lp bug ?
[10:49] <seb128> upstream
[10:49] <cassidy> k
[10:49] <seb128> or ask on #evolution if you want to start
[10:49] <seb128> we do patch a bit but only for ui tweaks
[10:49] <seb128> we don't do anything which has to do with the mailer
[10:49] <pitti> desrt: hm, I see the initial throbber, then nothing happens any more, got some trouble booting
[10:49] <seb128> pitti, wait a bit I guess
[10:50] <seb128> pitti, how much did you wait?
[10:50] <pitti> a minute or so
[10:50] <pitti> but the first time I tried it it booted in some 15 s
[10:50] <pitti> but then I tried suspend, and it crashed, so I rebooted
[10:50] <pitti> and now it doesn't come back
[10:50] <seb128> I need to try it again as well
[10:50] <pitti> let me fiddle a bit
[10:52] <seb128> but I think I'm going to miss having a launcher on screen with GNOME3
[10:52] <pitti> ah, coming back now; took a lot longer, though
[10:56] <pitti> desrt: so, works pretty well here! not too much fun without wifi, though (bloody broadcom chipset..)
[10:56] <pitti> desrt: by now I got used to Windows - search term - enter to launch apps, so that's pretty familiar :)
[10:57] <desrt> pitti: did you at least take a peek at the new networkmanager integration?
[10:57] <pitti> the theme is too generous with spacing/sizing for a small netbook screen, but otherwise this looks quite nice :)
[10:57] <desrt> (even without networks)
[10:57] <desrt> pitti: yes.  i agree quite a lot on the theme.  i just switched to another -- inset.
[10:57] <pitti> desrt: I did, yes; I really like the status message there
[10:58] <desrt> pitti: i mean about the menu
[10:58] <desrt> network-manager with the translucent shell theme for menus
[10:58] <desrt> pretty neat
[10:58] <pitti> desrt: the "wired - cable unplugged" and "wireless - firmware missing", that's quite clean
[10:58] <desrt> pitti: actually, those notifications are still annoying in some cases
[10:58] <pitti> desrt: yeah, very glossy
[10:58] <pitti> desrt: I didn't get any notification yet
[10:59] <desrt> you still often see the "disconnected from network xyz" when opening your laptop after having disconnected from the network a long time ago
[10:59] <desrt> and the "don't show this again" button doesn't actually work :/
[10:59] <pitti> the black translucent windows look very elegant (I'm just not a big fan of dark themes, but still)
[10:59] <desrt> pitti: i agree quite a lot.  the black is just too... black
[10:59] <desrt> but the gloss isn't so bad
[10:59] <pitti> desrt: is there a way to quick launch your favourite apps? such as Windows+1 or so?
[11:00] <desrt> i think the idea was so that it would fade into the background and let you focus on the work
[11:00] <desrt> pitti: no.
[11:00] <desrt> this is a point that unity wins on, i think
[11:00] <desrt> at the same time, it's not so important
[11:00] <desrt> since windows+f+enter is sufficient to get firefox
[11:00] <pitti> right
[11:00] <desrt> and the search gives higher preference to items that you've marked as favourites (ie: on the dash)
[11:00] <pitti> desrt: work flow wise they are really quite similar to me
[11:01] <desrt> so that helps
[11:01] <pitti> the indicator layout, the windows/overlay dash handling, etc.
[11:01] <desrt> ya
[11:01] <pitti> how do I opena nautilus window, though?
[11:01] <desrt> there are quite some similarities
[11:01] <desrt> pitti: add 'files' to your dash
[11:02] <desrt> (should be there by default?)
[11:02] <pitti> apparently I'm too blind to see a 'Home' button or so
[11:02] <desrt> pitti: i think it's not there, actually
[11:02] <desrt> and the apparent lack of meaningful desktop is also somewhat distressing
[11:02] <pitti> win+hom+enter works
[11:03] <pitti> oh, I can't dnd to the background
[11:03] <desrt> no.  the desktop is no longer shown as the background
[11:03] <desrt> it's just some folder in ~ now, with no special meaning
[11:03] <desrt> (wtf?)
[11:03] <desrt> you can turn the desktop back on with gnome-tweak-tool but apparently the designers found the idea of a desktop to be distracting
[11:03] <pitti> ah, I saw a notification now, from RB
[11:03] <desrt> so it's off by default
[11:04] <seb128> I like having a desktop ;-)
[11:04] <desrt> seb128: ya... no kidding
[11:04] <desrt> i also like having a minimise button
[11:04] <seb128> that I don't care much about
[11:04] <desrt> fortunate it's still possible to get both of them back again
[11:04] <pitti> well, it tends to make people not care about where they put their files, though
[11:04] <pitti> my mother's desktop looks horrible
[11:04] <pitti> basically everything she ever touched
[11:04] <desrt> pitti: that's sort of the point, actually
[11:04] <pitti> right
[11:05] <desrt> 3.2 is going to bring some tracker/zeitgeist love
[11:05] <pitti> I think the zeitgeist approach and search is a better long-term strategy
[11:05] <desrt> yup
[11:05] <pitti> desrt: I've never been a big fan of these tracker/indexer/etc. stuff, I know where my stuff is
[11:05] <pitti> but admittedly zeitgeist feels pretty good and magic to me
[11:05] <desrt> i almost get the impression that the desktop was disabled to increase the pain-level to push us in that direction faster
[11:05] <pitti> it even digs out some images I recently looked at from the evolution cache (email attachment), etc.
[11:06] <desrt> magic is magic!
[11:06] <pitti> desrt: well, if people need to be taught to get used to a new workflow, why not do it all the way through :)
[11:06] <desrt> pitti: i won't comment on the motiviations of the designers of the shell
[11:06] <pitti> being an old fart in this the concept of files and folders is deeply molten into my brain
[11:06] <desrt> because they're a bit of a mystery to me, to be honest
[11:06] <pitti> but then again, on my Android phone I never think in terms of files and folders
[11:07] <pitti> (where I'm only a user, not a developer)
[11:07] <pitti> and it really feels right
[11:07] <desrt> thus far i've managed to avoid getting a smartphone
[11:07] <desrt> but i guess that will end quite soon -- nexus S is in canada on april 14
[11:08] <pitti> desrt: that's the problem -- once you have one, you won't ever go back :)
[11:08] <desrt> which means that from april 14 to april 24th or so, i'll get no work done because of angry birds
[11:08] <pitti> that would have been a nice bday present :)
[11:08] <desrt> funny you should mention that because my birthday is quite soon
[11:08] <desrt> but i don't think i can wait :)
[11:08] <pitti> desrt: so I think the biggest thing that I miss from the current live image is a good files/document search/log integration (or maybe I haven't found it yet)
[11:09] <pitti> desrt: when?
[11:09] <pitti> mine is April 14th
[11:09] <desrt> pitti: i think you don't miss it -- it's just not there
[11:09] <desrt> may 3
[11:09] <pitti> natty beta 2, nexus S
[11:09] <desrt> same as david barth :)
[11:10] <pitti> desrt: hm, I thought pushing people to work more document and less app centric was a major goal?
[11:10] <desrt> pitti: ya.  i think that's complete BS to be honest
[11:10] <desrt> gnome-shell SCREAMS app-centric
[11:10] <pitti> there should at least be some links to the standard XDG dirs
[11:10] <desrt> (as does unity)
[11:10] <pitti> documents/photos/etc.
[11:10] <desrt> i'm not a fan
[11:10] <pitti> unity+zeitgeist is sort of a hybrid
[11:11] <pitti> if you search stuff, it comes up with files and apps
[11:11] <pitti> still no xdg dir links, though
[11:11] <desrt> this is not usually what i think of when i think doc-centric
[11:11] <pitti> yes, I agree
[11:11] <desrt> finding docs is one thing, sure
[11:11] <desrt> but the *identity* of what is open already, and what you're working with
[11:11] <desrt> in both unity and g-s, it's very much tied to the application icon
[11:12] <pitti> I mean, I don't need/want it to find all my source checkouts etc., but finding music or LibO files would be great
[11:12] <desrt> which i think is extremely wrong on a very fundamental level
[11:12] <pitti> windows + floyd wall enter
[11:12] <pitti> should kick me right into RB with The Wall playing
[11:12] <desrt> you could pick a better album :)
[11:13] <desrt> (jokes)
[11:13] <pitti> windows + apo should show me my Apocalyptica albums, etc.
[11:13] <desrt> ah.  that's good stuff, now!
[11:13] <pitti> or windows + tagname all my photos which are tagged with that
[11:13] <pitti> but I guess that's still a looong way to go
[11:13] <desrt> i think we'll see this happening quite soon
[11:13] <desrt> (or things like this)
[11:14] <desrt> it's a big feature item for 3.2
[11:14] <pitti> that sounds all very zeitgeist/trackerish indeed
[11:14] <seb128> you guys are keyboard freaks, I'm wondering what normal user want ;-)
[11:14] <desrt> i think i want to kill the dash
[11:14] <desrt> not sure what i'd replace it with, though
[11:14] <desrt> maybe nothing
[11:15] <desrt> the window switcher applet was actually sort of nice :)
[11:15] <desrt> it listed the windows you had open (ignoring tabs, this is equivalent to documents)
[11:15] <desrt> so.. quite good!
[11:15] <pitti> desrt: the alt+tab one looks suspiciously like the XFCE one :)
[11:16] <desrt> ya.. don't get me started on alt+tab
[11:16] <desrt> that's the other thing on my gnome-shell hate list :)
[11:16] <desrt> again -- application centric.  lame.
[11:16] <pitti> desrt: I guess I'm enough of a design philistine to not care too much :)
[11:16] <desrt> i fail to understand how gmail is any more related to facebook than it is to my word processor document
[11:18] <desrt> (which to drive the point home could very easily be either google docs or libreoffice)
[11:19] <seb128> pitti, hum, the i386 retracer crashed on the same assertion
[11:19] <pitti> seb128: ok, I'll stop playing with gnome3 now, and turn my attention to this :)
[11:19] <seb128> pitti, thanks
[11:19] <pitti> seb128: I can reproduce it in the chroot, now need to track it down
[11:19] <desrt> pitti: thanks for your opinions, btw
[11:20] <rodrigo_> pitti, what was the nvidia's GL problem you talked about yesterday?
[11:20] <rodrigo_> pitti, http://paste.ubuntu.com/590160/ <- could it be this?
[11:21] <seb128> rodrigo_, what problem? the cairo one?
[11:21] <cassidy> seb128, #evolution has been surprisingly  helpful. I fixed the issue by dropping my mail cache and opened https://bugzilla.gnome.org/show_bug.cgi?id=646898
[11:21] <rodrigo_> seb128, yes
[11:21] <seb128> cassidy, they usually are ;-)
[11:21] <pitti> desrt: so in summary, I really like the simplified network/bluetooth/a11y settings and the general design; more netbook friendly theming/window sizes and better file/XDG dir access are the main quirks that I see
[11:22] <seb128> rodrigo_, the nvidia binary driver create quite some ram use for each process using gl
[11:22] <seb128> rodrigo_, which is basically every gtk application when cairo is built with gl
[11:22] <desrt> pitti: nice to hear from positive words from "the other team" :p
[11:22] <pitti> rodrigo_: I'm afraid not; I was talking about bug 725434
[11:23] <pitti> desrt: well, it's not like we wouldn't have these problems :)
[11:24] <rodrigo_> pitti, but a cairo app (evo in this case) might crash with out-of-memory conditions because of that bug, right?
[11:24] <pitti> rodrigo_: ah, yes
[11:25] <rodrigo_> pitti, ok, thanks
[11:46] <cdbs> rodrigo_: Your work on the PPA looks nice, now that GNOME 3 is close to release. You can take a look at my own packaging of gdm at ppa:bilalakhtar/gnome-builds
[11:47] <cdbs> rodrigo_: I don't think that version of gdm is okay, but somehow it builds and runs
[11:47] <cdbs> hence I didn't upload it to the PPA
[11:47] <cdbs> where the PPA is the GNOME3 ppa
[11:51] <rodrigo_> cdbs, cool, and yes, we need more testing, so keep it there for now
[11:51] <rodrigo_> cdbs, I'll install and test it as soon as I've got a minute free
[11:51] <cdbs> rodrigo_: thanks
[11:51] <cdbs> rodrigo_: don't add that PPA, just manually download the package and try it
[11:54] <rodrigo_> cdbs, yes
[12:25] <rodrigo_> can someone please merge this -> https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/evolution-couchdb/correct_cache_dir/+merge/56551 (already uploaded)
[12:38] <seb128> pitti, do you still work on the retracers?
[12:39] <seb128> rodrigo_, ok
[12:39] <rodrigo_> seb128, thanks
[12:39] <seb128> rodrigo_, you're welcome
[12:40] <rodrigo_> :)
[13:04] <pitti> seb128: yes, it's quite a bit more difficult than I thought, I'm afraid
[13:05] <pitti> seb128: was at lunch now, and had some IRC discussions before, too
[13:05] <seb128> pitti, ok, is that specific to a bug? it started before the launchpad update so shouldn't be it
[13:05] <seb128> hello mterry
[13:06] <mterry> seb128, hi!
[13:06] <seb128> mterry, thanks for the geoname update email, nice to see that you managed to get locations filtered ;-)
[13:07] <mterry> seb128, yeah, i was excited
[13:07] <pitti> seb128: if the i386 retracer crashed as well, it doesn't sound too specific
[13:08] <pitti> seb128: did the i386 one crash on indicator-weather as well?
[13:08] <seb128> pitti, it's weird it just started today
[13:08] <Sweetshark> didrocks: Could you give me a hint on how the mapping of application windows to desktop entries works? I removed the libreoffice-javafilter.desktop file here (which is problematic in itself it seems) and ran update-desktop-cache. Unfortunately, my writer windows have now neither a name, nor a icon in the launcher.
[13:08] <seb128> pitti, dunno, I haven't check the bug it crashed on
[13:08] <pitti> it's certainly mvo's fault!
[13:08] <seb128> it's always mvo's fault
[13:09] <pitti> seb128: the fun thing is that it shouldn't even get that far
[13:09] <pitti> we don't currently have deb-src lines in the chroots
[13:09] <pitti> so apt-get source should already fail
[13:09] <mvo> hmm?
[13:09] <seb128> oh, so it is mvo's fault!
[13:10] <pitti> still too early to point blame, let me dig deeper
[13:10]  * pitti hugs mvo
[13:10] <seb128> mvo, no worry, retracers crashing again, nothing special ;-)
[13:11] <mvo> ohhh
[13:11]  * mvo hides, just in case
[13:11] <seb128> mvo, but pitti suggested the apt-get source behaviour could have changed if you don't have a deb-src source
[13:11] <seb128> mvo, but well let him confirm it before investigating ;-)
[13:11] <mvo> that might be possible, there were changes in this area. from what version to what version?
[13:12] <seb128> mvo, that started this night so something uploaded yesterday?
[13:12] <seb128> they update daily
[13:13] <didrocks> Sweetshark: the mapping is made by bamf, there is a debug interface to know where the mapping is done. Anyway, just edit the default desktop files we set it the launcher (you don't need libreoffice to be running for that)
[13:14] <mvo> seb128: hm, there is a new apt and a new python-apt but it *should* only affect multiarch setups
[13:14] <mvo> seb128: can I see the trace of the crash?
[13:14] <seb128> mvo, well as said it might be something else, it's just what pitti wrote before
[13:15]  * rodrigo_ lunch
[13:15] <seb128> mvo, it's not "crashing", it's that apt-get source should fail because there is no deb-src source but it doesn't apparently
[13:16] <seb128> mvo, where "fail" might be the return value changed
[13:16] <mvo> ok
[13:16] <seb128> mvo, but wait for pitti to debug it before spending time on that
[13:16] <mvo> ok
[13:17] <seb128> nessita, hola seniorita ;-)
[13:17] <pitti> a mere apt-get source exits with 100, that looks fine
[13:17] <nessita> seb128: bon jour monsieur!
[13:17] <seb128> nessita, how are you?
[13:17] <nessita> pretty good! having some net issues, but good :-)
[13:17] <nessita> you?
[13:17] <seb128> I'm fine thanks ;-)
[13:18] <pitti> meh, as soon as I add some debugging it crashes
[13:19] <pitti> or hangs, or immediately exits with 0
[13:19] <Sweetshark> didrocks: well, my writer window showed up as "LibreOffice Small Device Import Filter", which it seems to get from /usr/share/applications/libreoffice-javafilter.desktop. So I removed that and ran update-desktop-cache hoping I would now get the entry from /usr/share/applications/libreoffice-writer.desktop. Unfortunately, now I get neither an icon nor a title.
[13:20] <seb128> Sweetshark, how do you start those?
[13:20] <didrocks> ok, letting seb128 dealing with it, back to hack! ;)
[13:21] <seb128> didrocks, ;-)
[13:21] <seb128> didrocks, that's the spirit!
[13:21] <didrocks> seb128: well, I hate X, it's definitive :)
[13:21] <Sweetshark> seb128: Launcher->Applications->LibreOffice Writer (in "Most Frequently Used")
[13:22] <seb128> hum
[13:22] <seb128> can you try to double click on an odt from nautilus for example
[13:22] <seb128> just to see if it behaves the same?
[13:24] <Sweetshark> seb128: still "LibreOffice Small Device Import Filter"
[13:24] <seb128> did that issue start recently?
[13:25] <Sweetshark> seb128: no, I think its older.
[13:26]  * Sweetshark builds LO much more than using it.
[13:27] <Sweetshark> both libreoffice-javafilter.desktop and libreoffice-writer.desktop suspiciously have the same "Exec:" line.
[13:27] <seb128> right, it tries to match running binaries to .desktop
[13:28] <seb128> but when started with something gio it should get the information on what .desktop to use from gio directly
[13:29] <seb128> Sweetshark, bug #751025
[13:30] <seb128> mterry, do you feel like debugging the crash you just reported? it seems like bug #434825 and a downstream crash likely
[13:30] <seb128> mterry, the call is coming from libindicate
[13:31] <mterry> seb128, sure, I can look at it
[13:31] <seb128> mterry, thanks
[13:32] <seb128> mterry, do you have things to do otherwise or do you want extra bug?
[13:32] <seb128> mterry, if I don't ping you with anything specific maybe just tackle indicator bugs if you feel like working on
[13:32] <mterry> seb128, I've got a couple things, but if you have extra bugs just lying around, I can queue them up
[13:33] <seb128> mterry, ok, I've nothing specific right now but I will do another indicator stack bug review today so I might bounce a few your way
[13:33] <mterry> k
[13:34] <pitti> seb128: erk, I ran it locally on bug 751695, which worked, so I now killed the core dump; but the i386 crashed on teh same problem, so I'll now move on to that and will restart the amd64 one in the meantime
[13:34] <seb128> mterry, having the geonames translation thing sorted would be nice but I'm not sure how doable that is for natty
[13:34] <seb128> pitti, ok
[13:34] <seb128> pitti, let me know if I can help there
[13:35] <seb128> Sweetshark, so yeah, seems there is an unity bug there, I will get Jason to join the channel to discuss it when he comes online (he's in the U.S)
[13:35] <mterry> seb128, I feel like it's close
[13:36] <seb128> mterry, btw ev said yesterday he would do a db update and ask I.S to roll it
[13:36] <seb128> mterry, I want to see if that fixes case like san francisco or lima not having any matching result
[13:36] <mterry> seb128, oh ok.  hopefully after merging my filter branch?
[13:36] <seb128> mterry, he said your review was on his list for today
[13:37] <seb128> so yeah, that should land as well
[13:37] <mterry> seb128, I think my filter will.  I *think* lima for example was just dropping off after too many hits.  Sorting by population brings it to the top
[13:37] <Sweetshark> seb128: #751025 is close on it. I also get the window show up as "LibreOffice Small Device Format Importer". If I "apt-get remove libreoffice-filter-mobiledev" I get no title to the window at all. Calc on the other hand just works fine.
[13:37] <seb128> mterry, oh, great!
[13:38] <seb128> Sweetshark, https://code.launchpad.net/~pitti/bamf/libreoffice-705461/+merge/49245
[13:38] <seb128> Sweetshark, if that's of any use that's the commit pitti did to get libreoffice to work
[13:39] <pitti> I might have missed a few cases, I more or less just adapted teh OO.o bits
[13:40] <pitti> seb128: hm, how can the i386 one have crashed in the log and yet the process is still running?
[13:40] <pitti> ooh
[13:40] <pitti> 1000     25626  0.0  0.0  25632  1940 ?        D    00:08   0:00 apt-get --assume-yes source indicator-weather=11.03.27+repack-0ubuntu1
[13:40] <pitti> that thing has hanged for 14 hours now
[13:40] <seb128> pitti, weird
[13:41]  * pitti kills all stuff and starts over
[13:41] <seb128> Sweetshark, I've a suspicion something broke broke the gio .desktop matching logic
[13:41] <seb128> Sweetshark, but in any case seems an unity issue, not one on your side
[13:44] <Sweetshark> seb128: well, it seems to work for Calc windows, but fails for writer. The desktop files look the same though.
[13:46] <Sweetshark> (modulo the issue with the libreoffice-javafilter.desktop file, but I still get no icon after uninstalling libreoffice-filter-mobiledev)
[14:15] <ameyJ> hi, where should I look for,
[14:15] <ameyJ> if I want indicator applet session apis
[14:16] <seb128> ameyJ, hey, what api exactly? what are you trying to do?
[14:16] <ameyJ> @seb128, I want to set MeMenu to away when I am locking my computer either via menu or via ctrl+alt+L
[14:17] <seb128> there is no indicator specific api for that
[14:17] <seb128> your im client likely has dbus apis to do that though
[14:18] <ameyJ> ok, so you mean to say. I should look for dbus event
[14:18] <ameyJ> ok cool
[14:18] <ameyJ> thansk seb128. will work on this direction now
[14:25] <pitti> seb128: this is really driving me mad.. I run "apport-retrace -uvo /tmp/x.crash --auth /tmp/auth 752174" and get that crash, with a dubious debugging output
[14:25] <pitti> I run it again, and it exits (with 0!) immediately
[14:27] <pitti> kenvandine, didrocks, seb128: do you know what needs to happen to make the new overlay scrollbars the default?
[14:28] <pitti> besides the GTK patch (which we have now), there's liboverlay-scrollbar-0.1-dev, but merely installing the library won't magically enable them, or will it?
[14:28] <pitti> do we need to build something against liboverlay-scrollbar-0.1-dev?
[14:28] <seb128> pitti, nothing, just install overlay-scrollbar
[14:28] <kenvandine> that is it
[14:29] <seb128> pitti, gtk will open it and use it available
[14:30] <pitti> *scratches head*, which package is that?
[14:30] <pitti> the overlay-scrollbar source only builds the library
[14:30] <pitti> Package: overlay-scrollbar
[14:30] <pitti> Binary: liboverlay-scrollbar-0.1-0, liboverlay-scrollbar-0.1-dev
[14:31] <didrocks> liboverlay-scrollbar-0.1-0 is enough for the current gtk
[14:31] <didrocks> liboverlay-scrollbar-0.1-dev isn't needed because it's a dlopen
[14:32] <pitti> ah I remember that hack (aside from the fact that I missed the bad packaging (non-SONAME-specific files in the library)
[14:32] <TeTeT> seb128: hi, would you know anything about a replacement for vinagre in 11.04 or 11.10?
[14:33] <pitti> didrocks: do you have time to fix it, or want me to?
[14:34] <pitti> so anyway, I'll deal with the MIR and seeding
[14:34] <didrocks> pitti: go on with it, of course :) what about the soname?
[14:34] <seb128> pitti, talk to kenvandine about those please
[14:34] <pitti> didrocks: /usr/share/apport/general-hooks/ayatana-scrollbar.py
[14:34] <seb128> pitti, didrocks has enough to do with unity he doesn't work on scrollbars
[14:34] <pitti> we can't ship that in a soname package
[14:34] <pitti> seb128: *nod*
[14:34] <seb128> pitti, kenvandine is handling the scrollbars
[14:34] <seb128> kenvandine, ^
[14:34] <didrocks> pitti: I didn't add the apport hook, so yeah, kenvandine :p
[14:34]  * kenvandine reads back
[14:35] <kenvandine> pitti, ok, so we want a separate binary with the apport hook?
[14:35] <pitti> kenvandine: so, we could do a proper "overlay-scrollbar" package which ships the apport hook and depends on the library (to avoid having to seed a particular abi of the library), or rename the hook to be ayatana-scrollbar-0.1.py
[14:35] <kenvandine> i'll do that
[14:36] <pitti> the latter is easier, the former cleaner IMHO
[14:36] <pitti> but like that it won't pass MIR
[14:36] <kenvandine> i'll do the former
[14:36] <kenvandine> makes more sense
[14:36] <pitti> kenvandine: awesome; please let me know when you upload, I'll shepherd it through NEW then
[14:36] <kenvandine> will do
[14:36] <pitti> and I'll do the MIR review in the meantime
[14:36] <pitti> kenvandine: cheers!
[14:42] <seb128> Sweetshark, is the matching bug blocking you for other things?
[14:53] <pitti> root@osageorange:/# apt-get --assume-yes source update-manager=1:0.147.1
[14:53] <pitti> Reading package lists... 0%
[14:53] <pitti> seb128: ^FYI, I think I'm getting closer..
[14:53] <pitti> it just stays at 0% without any progress
[14:53] <seb128> oh
[14:54] <seb128> so it's mvo's fault!
[14:54] <pitti> when I downgrade to 0.8.13ubuntu2, it works
[14:54] <pitti> E: You must put some 'source' URIs in your sources.list
[14:54] <pitti> and immediately returns
[14:55] <pitti> root@osageorange:/# apt-get --assume-yes source update-manager=1:0.147.1
[14:55] <pitti> root@osageorange:/# s... 0%
[14:55] <chrisccoulson_> ok, this -pie issue with firefox is driving me crazy now, time to look at something else ;)
[14:55] <pitti> that looks even funnier
[14:55] <pitti> chrisccoulson_: doesn't work with gcc 4.4?
[14:55] <chrisccoulson_> pitti - i'm not sure it's entirely a gcc issue
[14:55] <seb128> chrisccoulson_, how come we don't get the stable version in natty btw? it's still red on versions ;-)
[14:55] <chrisccoulson_> it might be partly a binutils issue
[14:56] <chrisccoulson_> seb128 - the version we have is stable already ;)
[14:56] <seb128> chrisccoulson_, I'm surprised you don't get lot of users complaining about the version ;-)
[14:56] <chrisccoulson_> seb128 - i do ;)
[14:56] <seb128> they usually tend to do that
[14:56] <mvo> pitti: hm, I just tried to reproduce on my natty box but I don't get this error
[14:56] <seb128> even if the code is the same ;-)
[14:56] <seb128> mvo, did you use a non available version?
[14:56] <pitti> mvo: I don't get it either locally, just in the retracer chroots :/
[14:57] <chrisccoulson_> seb128 - it's just not worth a new upload to change the version number ;)
[14:57] <chrisccoulson_> i'll probably do it before release, but it means i have to upload a new tarball too
[14:57] <chrisccoulson_> and they're big ;)
[14:57] <pitti> mvo, seb128: the version is fine, the chroot jsut doesn't have any deb-src
[14:57] <pitti> but I tried that locally as well
[14:57] <seb128> pitti, which makes it "non available" ;-)
[14:57] <pitti> in fact this is the only apt-get call that I have in apport
[14:57] <pitti> the rest is python-apt
[14:58] <pitti> but when I wrote that, there was no python-apt way of downloading a source package
[14:59] <pitti> oh, I figure installing debug packages somehow causes it to act up
[14:59] <pitti> after logging into the chroot it works
[14:59] <pitti> but not after retracing something (which installs packages)
[14:59] <pitti> mvo: is there a python-apt way of doing apt-get source?
[15:00] <kenvandine> pitti, overlay-scrollbar uploaded
[15:00] <pitti> mvo: so it's not really your fault, just the new apt seems to have become a lot more sensitive to broken packages
[15:00] <pitti> kenvandine: \o/ thanks
[15:01] <kenvandine> np
[15:03] <mvo> pitti: sorry, on the phone, I follow up in a minute
[15:11] <pitti> ok, not related to apport-retrace after all, the chroots previously had an older apt, and as soon as I upgrade to <IP_ADDRESS>ubuntu1 things fall over
[15:11] <seb128> pitti, we can pin the old one for now maybe?
[15:11] <pitti> yes, that's what I'll do right now
[15:17] <seb128> mterry, one other thing you can to your buglist if you want that would be nice is the gvfs, libgnome-keyring sibabort issue
[15:17] <seb128> sig
[15:18] <mterry> seb128, bug me?
[15:18] <mterry> bug number me rather :)
[15:18] <seb128> mterry, the one you opened
[15:18] <seb128> mterry, 743497
[15:18] <mterry> seb128, heh, I'm a fire and forget bug reporter
[15:19] <seb128> mterry, if you don't fix it at least maybe try to open an upstream bug with the debug info upstream mentioned
[15:19] <mterry> sure
[15:19] <mterry> i'll give it a pass
[15:19] <seb128> mterry, upstream is stefw on #gnome-hackers if you want to talk to him about it
[15:19] <seb128> thanks
[15:22] <pitti> seb128: ok, I think I have reasonably clean chroots again with pinned apt; restarting, cross fingers :)
[15:25] <seb128> pitti, \o/
[15:29] <pitti> seb128: seems to work
[15:33] <pitti> kenvandine: mind to upload a followup which adds the necessary Replaces:Breaks: (<< 0.1.5-0ubuntu1)?
[15:33] <rodrigo_> hey Laney
[15:33] <kenvandine> pitti, whoops
[15:33] <kenvandine> yeah, sorr
[15:34] <pitti> kenvandine: (and perhaps fix the overlay-scrollbar desscription while you are at it -- it's not a devel package)
[15:42] <rodrigo_> jcastro, ping
[15:43] <jcastro> rodrigo_: hi!
[15:43] <rodrigo_> jcastro, about http://askubuntu.com/questions/22946/how-do-i-install-the-latest-version-of-gnome-3
[15:44] <rodrigo_> jcastro, it's better if people just run apt-get dist-upgrade
[15:44] <jcastro> ok
[15:44] <rodrigo_> jcastro, and maybe a separate 'apt-get install gnome-shell' if the want g-shell
[15:44] <jcastro> is there one metapackage or does the dist-upgrade just take care of that?
[15:44] <rodrigo_> jcastro, dist-upgrade should take care of that
[15:44] <rodrigo_> jcastro, that's why we didn't add the metapackage
[15:45] <jcastro> ok fixed
[15:45] <jcastro> I added a scarier warning up top too
[15:45] <kenvandine> pitti, uploaded
[15:45] <jcastro> since downgrading looks like, horrible
[15:45] <rodrigo_> jcastro, yes, good idea
[15:46] <rodrigo_> jcastro, hmm, on the UI, no way to do a dist-upgrade?
[15:48] <pitti> kenvandine: thanks!
[15:49] <Sweetshark> seb128: Im on bug 720716 . But I will test it with Calc and hope it will work for writer the same way.
[15:50]  * Sweetshark starts on patch 18 for libreoffice packaging.
[15:50] <seb128> Sweetshark, you can try to downgrade bamf to 0.2.80-0ubuntu1
[15:50] <jcastro> rodrigo_: the button works that out as far as I know.
[15:50] <seb128> Sweetshark, https://launchpad.net/ubuntu/+source/bamf/0.2.80-0ubuntu1
[15:51] <rodrigo_> jcastro, ok then
[15:51] <seb128> Sweetshark, if you downgrade it and restart bamfdaemon and unity and let me know if that fixes your issue that would be nice
[15:51] <seb128> Sweetshark, well no hurry but when you will have some time
[15:52] <Sweetshark> seb128: heh.
[15:52] <Sweetshark> seb128: but yes, I will try.
[15:54] <fta> seb128, hi, didn't you say last week that the weird locations dialog of the datetime applet was fixed? or did I dream it?
[15:55] <seb128> fta, what about it? mterry said that the "no listing any result during typing issue" was fixed
[15:56] <mterry> yeah
[15:56] <fta> seb128, it's not here, "san francisco" shows nothing between "san" and the "o", then i only get unknown (to me) location, nothing in california
[15:56] <fta> locationS
[15:57] <mterry> fta, san francisco is a known bug, I believe due to us not sorting by population yet
[15:58] <fta> same for sydney.. it have to add "airport" or "international airport", and i end up with a list of hotels or universities close to those airports :P
[15:59] <fta> hence, very long names, making the indicator too wide :P
[16:00] <seb128> mterry, is the server limiting the number of returns?
[16:00] <seb128> mterry, because http://geoname-lookup.ubuntu.com/?query=san francisco doesn't list it either
[16:00] <mterry> seb128, yes
[16:00] <seb128> ok
[16:00] <mterry> seb128, that's why the filtering and sorting branch should make this a lot better
[16:00] <mterry> no more hotels, and better results on top
[16:00] <seb128> right, I got those advantage
[16:00] <mterry> fta, ^
[16:01] <fta> ok
[16:01] <seb128> but I didn't know we were dropping locations because of the lack of sorting
[16:01] <mterry> fta, basically, a fix is in, we just wait for it to be deployed server side
[16:01] <mterry> seb128, it's a big limit, like 1000 or so, but yeah
[16:01] <mterry> (I think, would have to look at code)
[16:01] <seb128> mterry, "http://geoname-lookup.ubuntu.com/?query=san francisco" returns a small list
[16:01] <mterry> seb128, then maybe the limit is smaller :)
[16:01] <seb128> but anyway I will try when the server update is rolled
[16:03] <fta> another weirdness of that datetime indicator, the calendar. the highlighted/selected day is the day of the last desktop restart (useless imho), it used to be the current day
[16:04] <tedg> seb128, Can you mark the appmenu-gtk part of this as Invalid for Natty?  I can't seem to :-/  https://bugs.launchpad.net/ubuntu/+source/wxwidgets2.8/+bug/722375
[16:05] <seb128> tedg, done
[16:05] <tedg> seb128, Thanks!
[16:05] <seb128> fta, known bug as well, karl is working on it
[16:05] <seb128> it might be fixed in trunk
[16:05] <seb128> tedg, yw
[16:09] <fta> good
[16:12] <fta> mterry, after a restart/reboot, i have to open the locations dialog 2 or 3 times to be able to use it, the 1st call, i get nothing, the 2nd, it disappears immediately, the 3rd time, i see it for a few seconds then pooff, after that it works fine. is that known?
[16:13] <seb128> fta, seems like it crashed?
[16:13] <mterry> fta, huh...
[16:13] <jcastro> rodrigo_: does the dist-upgrade include gnome-shell?
[16:13] <rodrigo_> jcastro, no
[16:13] <jcastro> or does the user have to install that explicitly?
[16:13] <mterry> fta, if you click elsewhere in the dialog, the locations dialog disappears
[16:13] <seb128> fta, did you try to start it before being online?
[16:13] <rodrigo_> jcastro, so add a 'apt-get install gnome-shell' to the instructions
[16:13] <jcastro> ok
[16:14] <fta> lets see if it crashed...
[16:14] <mvo> pitti: still in a meeting (its meeting day today). but you can get the urls for the source via python-apt
[16:15] <fta> nope: http://paste.ubuntu.com/590294/
[16:15] <mvo> pitti: I can write some test code in a bit (please kick^Wremind me if I doN't do it)
[16:15] <pitti> mvo: don't worry for now; apt itself is broken in the chroots, so the python-apt source code retrieval isn't urgent at all
[16:16] <fta> seb128, i'm always online ;)
[16:17] <rodrigo_> jcastro, ok, I think they look great now
[16:17] <rodrigo_> jcastro, let's see what people report
[16:17] <jcastro> I'm asking a guy to test right now
[16:17] <fta> difficult to see anything in .xsession-errors. i wish everything was timestamped
[16:18] <jcastro> rodrigo_: I'll watch this with great attention today to make sure it's kept up to date
[16:18] <mvo> pitti: ok
[16:18] <rodrigo_> jcastro, ok, cool
[16:36] <seb128> rodrigo_, https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/750660
[16:36] <seb128> rodrigo_, is that the evolution-couchdb issue you fixed the other day?
[16:36] <seb128> rodrigo_, https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/744464
[16:36] <seb128> same
[16:37] <rodrigo_> seb128, no, but seems related to a problem rye (on #ubuntuone) is having
[16:37] <seb128> rodrigo_, can you add those to your buglist?
[16:38] <seb128> seems frequent crashers
[16:38] <rodrigo_> ok
[16:38] <seb128> rodrigo_, https://bugs.launchpad.net/ubuntu/+source/evolution-data-server?field.searchtext=e-addressbook-factory&orderby=-datecreated
[16:38] <rodrigo_> they are duplicates, right?
[16:38] <seb128> if you want to review, clean it a bit as well
[16:38]  * rodrigo_ looks for the 2nd one
[16:38] <seb128> rodrigo_, they seem similar yes
[16:39] <seb128> rodrigo_, let's use bug #744464 for it, I assign it to you
[16:39] <rodrigo_> ok
[16:39] <seb128> cyphermox, hey
[16:39] <seb128> cyphermox, did you say you were working on e-d-s crashers? did you work on those e-addressbook-factory ones? just to make sure rodrigo doesn't start on something you already work on
[16:40] <fta> http://people.ubuntu.com/~fta/lazy-unity.ogv
[16:41] <seb128> fta, what about it?
[16:41] <seb128> fta, you need to hit 0,0 for the launcher to stick
[16:43] <rodrigo_> seb128, wow, lots of e-d-s crashes, I'll go over the list
[16:45] <cyphermox> seb128, I have a merge up for the addressbook ldap bug, looking into the google one now
[16:45] <seb128> rodrigo_, those are only the addressbook ones ;-)
[16:45] <rodrigo_> seb128, oh :)
[16:46] <seb128> cyphermox, ok, I will review and merge that later on, I will probably wait for other fixes before uploading though
[16:46] <cyphermox> rodrigo_, seb128, not necessarily looking at crashers per se, but I'll look at the evo/eds bugs in general to make sure we're not dropping the ball
[16:46] <cyphermox> seb128, sure
[16:46] <seb128> cyphermox, thanks
[16:46] <seb128> if you stop couchdb or contact synced issue ping rodrigo_ about those
[16:46] <cyphermox> I'd like to include the fix for google if possible, but i think it will be in eds, not evo
[16:48] <rodrigo_> cyphermox, ok, leave this list -> https://bugs.launchpad.net/ubuntu/+source/evolution-data-server?field.searchtext=e-addressbook-factory&orderby=-datecreated to me if you want
[16:49] <rodrigo_> seb128, along with the evo-couchdb branch I pasted before, can you also merge this https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/couchdb-glib/enable-debug-messages/+merge/56597 ? (already uploaded also)
[16:49] <cyphermox> rodrigo_, ok. well, looks like there may be a few overlaps there -- let me know if down the road you see that we could split them up between us to fix it all ;)
[16:50] <rodrigo_> cyphermox, ah, you're looking at those bugs also?
[16:50] <rodrigo_> cyphermox, since seb128 said those were only the addressbook crashes, I assumed there are lots of other e-d-s bugs
[16:51] <seb128> rodrigo_, https://bugs.launchpad.net/ubuntu/+source/evolution-data-server?field.searchtext=crashed&orderby=-datecreated
[16:51] <seb128> rodrigo_, https://bugs.launchpad.net/ubuntu/+source/evolution-data-server?field.searchtext=SIG&orderby=-datecreated
[16:51] <cyphermox> rodrigo_, ok. I was going to look at them, but I'll leave them to you and look at the other e-d-s crashers
[16:51] <seb128> rodrigo_, try that url
[16:51] <seb128> hum
[16:51] <rodrigo_> seb128, why do you make this to me??? :)
[16:51] <rodrigo_> lots of crashes man!
[16:51] <rodrigo_> cyphermox, yes, unless you want some explicti addressbook ones, leave those to me
[16:52] <rodrigo_> there are plenty for both of us :)
[16:52] <cyphermox> ok
[16:52] <cyphermox> yes, there are ;)
[16:52] <rodrigo_> cyphermox, do you want me to leave the google related ones to you?
[16:52] <cyphermox> ah, up to you
[16:52] <seb128> lot of noise and duplicates likely
[16:52] <rodrigo_> yes
[16:52] <cyphermox> I was going to ask whether you wanted to look at the issue with google addressbook at the same time
[16:52] <seb128> well don't bother cleaning old ones
[16:53] <seb128> but seems that most of recents crashes are e-addressbook-factory ones
[16:53] <rodrigo_> cyphermox, ok, let's use the last list
[16:53] <rodrigo_> cyphermox, ok, let's use the last 2 lists seb128 posted for both of us
[16:53] <rodrigo_> cyphermox, just assign to you the bugs you're working on and I'll do the same
[16:53] <seb128> those didn't work ;-)
[16:54] <seb128> but just type SIGSEGV in the search entry and sort by newest
[16:54] <rodrigo_> seb128, hmm, it works for me, 182 bugs
[16:55] <seb128> ok great ;-)
[16:55] <seb128> well don't try clean the buglists, just try to spot things worth fixing for natty
[16:55] <rodrigo_> ok
[16:55] <seb128> we have pedro to clean ;-)
[16:55] <seb128> hey pedro_! ;-)
[16:55] <rodrigo_> heh
[16:56] <seb128> I should start running before pedro throw something in my direction ;-)
[16:56] <rodrigo_> hehe
[16:58] <rodrigo_> ugh, we have a lot of patches in the evo package
[16:59] <rodrigo_> what do you think about doing some patch upstreaming/cleaning days when natty is released?
[16:59] <rodrigo_> it makes upgrading packages a lot harder
[17:01] <cyphermox> rodrigo_, yes, but I think there may be quite a few which are backports
[17:01] <rodrigo_> yes
[17:01] <rodrigo_> those are ok, as they are removed when we move to the next major version, right?
[17:01] <cyphermox> afaik they should be well identified as such in changelog and even the file name, so when we're at uploading 2.91. whatever or 3.2 we can drop them
[17:01] <cyphermox> yeah
[17:02] <rodrigo_> yeah, right
[17:02] <rodrigo_> I remember in opensuse we had packages with more than 20 patches, so we upstreamed/cleaned a lot of them, and upgrades were much easier
[17:03] <rodrigo_> evolution had, iirc, over 100 patches!
[17:24] <Sweetshark> rodrigo_: well, LO still has >500 "shared patches" used by all distros. The 18 patches are just our private debian/ubuntu patches on top of that (some patching the patches).
[17:30] <seb128> dobey, bug #724882 is getting some duplicates recently
[17:31] <seb128> rodrigo_, evo doesn't have a lot of distro patches
[17:35] <rodrigo_> Sweetshark, ugh
[17:43] <seb128> does anybody has interest in geoclue?
[17:43] <seb128> bug #738584
[17:44] <seb128> hum no bot
[17:44] <seb128> that's an assert crash which seens to happen on resume
[17:44] <seb128> it's likely not a real user situation issue if it respawn when needed though
[17:44] <seb128> kenvandine, cyphermox: ^
[17:44] <seb128> https://bugs.launchpad.net/ubuntu/+source/geoclue/+bug/738584
[17:45] <seb128> if one of you want to have a go to it that would be nice
[17:46] <ry> ok, i'm using the small apple aluminum bluetooth keyboard, and it's lacking an insert key, i'm wondering how i can make a shortcut to issue "insert" as if i was hitting the key-- like ctrl+shift+i (random example)
[17:47] <ry> ubuntu 10.10/2.6.35.x/gnome/pc
[17:47] <seb128> try #ubuntu for user questions
[17:47] <ry> ok, thanks
[17:51] <cyphermox> seb128, sure, I'll take that too
[17:51] <seb128> cyphermox, thanks
[17:52] <cyphermox> isn't it indicator-datetime which uses geoclue?
[17:53] <bcurtiswx> cyphermox, eventually empathy will (i would assume)
[17:53] <cyphermox> bcurtiswx, cool
[17:53] <cyphermox> I know redshift does not, but not in the natty package ;)
[17:53] <cyphermox> not, = now,
[17:54] <seb128> right the indicator use it
[17:59] <seb128> mvo, #741370
[17:59] <seb128> mvo, it's an aptdaemon bug with quite some duplicates
[18:00] <mvo> ok
[18:00] <seb128> tremolux, bug #728713
[18:00] <seb128> can you check on it? it's a s-c crash with some duplicates
[18:03] <tremolux> seb128: yep, we've been watching that one, I will check on it
[18:03] <tremolux> seb128: thx
[18:03] <seb128> thanks
[18:03] <seb128> tremolux, can you make sure it's assigned to somebody?
[18:03] <tremolux> seb128: yep
[18:19] <dobey> seb128: ok, i'll look at it
[18:19] <seb128> thanks
[18:37] <nessita> pitti: hey there, would you have some minutes? I have a question regarding feature freeze
[18:38] <pitti> nessita: about to run out, but shoot
[18:38] <seb128> nessita, others can reply
[18:38] <seb128> just ask
[18:38] <nessita> so, we're having an internal discussion about what is an API change and what isn't. We need to add a new parameter to an internal method in syncdaemon, we're saying is not an API change but others disagree
[18:39] <nessita> so, from our point of view, syncdaemon API is the dbus api only
[18:39] <nessita> but the whole implementation is somehow available in /usr/lib
[18:39] <seb128> nessita, well it's an internal api chance, not an external one then?
[18:39] <nessita> seb128: right
[18:39] <seb128> is whatever provide the api public?
[18:39] <seb128> you say it's in /usr/lib
[18:40] <pitti> nessita: I think the question here is: can it break anything that both consumers in Ubuntu as well as third-party developers are using?
[18:40] <nessita> seb128: syncdaemon implementation is in ubuntuone/syncdaemon module as a python module, but end users are not supposed to use that
[18:40] <pitti> nessita: i. e. can they call the function you are about to change?
[18:40] <nessita> pitti: they can call it, in the sense that is publicly accessible code
[18:41] <nessita> pitti: but anyone is supposed to use those things outside syncdaemon
[18:41] <seb128> do you know of anybody using it?
[18:41] <nessita> no, I don't
[18:41] <seb128> nessita, "anyone" -> "no one"?
[18:41] <pitti> nessita: i. e. the official API is the d-bus one, and that's also what our ubuntu packages use?
[18:41] <nessita> seb128: yes :-)
[18:41] <nessita> pitti: yes
[18:41] <pitti> nessita: sounds fine to me then
[18:41] <nessita> great, thanks
[18:42] <pitti> Python code is by nature very "open", but that doesn't mean that everything is public API automatically
[18:42] <pitti> anyway, Taekwondo o'clock, see you tomorrow!
[18:42] <seb128> seems like it's a private api not supposed to be used and those who (abu)sed it will get what happens in such cases ;-)
[18:42] <seb128> pitti, see you
[18:42] <dobey> i prefer my solution to that problem; just avoid python
[18:42] <nessita> pitti: thanks!!!
[18:42]  * nessita hugs seb128
[18:43]  * seb128 hugs nessita
[18:43] <seb128> nessita, you trapped me with your u1 btw, even didrocks made fun of me because I share bug screenshots by publishing them on u1 now!
[18:43] <seb128> ;-)
[18:44] <didrocks> nessita: you finally won \o/
[18:47] <nessita> YEAH
[18:47]  * nessita happily dances
[18:59] <cyphermox> seb128, I haven't been able to reproduce the geoclue crash, but I guess I have a fix that makes some sense anyway.
[19:00] <cyphermox> i'll do some more testing and checking first though -- but now, lunch time :)
[19:00] <seb128> cyphermox, ok thanks
[19:00] <cyphermox> did you personally experience it?
[19:28] <bcurtiswx> seb128, any trivial empathy bugs you've run across?
[19:33] <seb128> bcurtiswx, no
[19:33] <bcurtiswx> seb128, OK thanks :)
[20:03] <bcurtiswx> kenvandine, everytime i bring up the gwibber window it eats CPU, but when its minimized, it doesn't....
[20:03] <bcurtiswx> seen this?
[20:03] <kenvandine> bcurtiswx, does it keep eating CPU while it is up?
[20:03] <bcurtiswx> only when the window is unminimized
[20:04] <bcurtiswx> it takes a little bit too, but it does eventually
[20:05] <bcurtiswx> yup, now at 100% CPU
[20:05] <bcurtiswx> maybe since i have a refresh rate in the quick end... seems to me
[20:05] <kenvandine> weird
[20:05] <kenvandine> you mean the gwibber client window right? not the lens?
[20:06] <bcurtiswx> i dont' use the lens
[20:06] <kenvandine> ok
[20:06] <kenvandine> i can't see why the client would use CPU
[20:06] <kenvandine> it doesn't do anything, except when it gets the signal to refresh the WebView
[20:07] <bcurtiswx> hmm, i have a lot of services it checks with facebook having a TON of friends.. i wonder if its shear quantity causing it..
[20:07] <bcurtiswx> which is my own fault TBH
[20:07] <bcurtiswx> i need less friends... <hangs head in shame>
[20:08] <bcurtiswx> yup thats it, gwibber-service on a refresh
[20:09] <bcurtiswx> kenvandine, ^^
[20:09] <kenvandine> oh, it isn't the client then
[20:09] <kenvandine> rickspencer3, fix for bug 739923 being uploaded now :)
[20:09] <bcurtiswx> yes, sorry for the lack of -service :X
[20:09] <kenvandine> bcurtiswx, how big is your db?
[20:10] <kenvandine> ls -lah ~/.config/gwibber/gwibber.sqlite
[20:10] <bcurtiswx> 175m
[20:10] <bcurtiswx> 175M*
[20:11] <kenvandine> ugh
[20:11] <kenvandine> that is why :)
[20:11] <kenvandine> what version of gwibber?
[20:11] <bcurtiswx> 3.0.0-0ubuntu1
[20:11] <kenvandine> that number should be much lower
[20:11] <kenvandine> wow
[20:11] <kenvandine> how many accounts do you have?
[20:11] <bcurtiswx> Twitter, Facebook, Identi.ca
[20:12] <kenvandine> hummm
[20:12] <kenvandine> it should keep the latest 2000 posts for each account
[20:12] <kenvandine> and purge the rest
[20:12] <kenvandine> so it shouldn't be nearly that big
[20:12] <kenvandine> bcurtiswx, can you post your log somewhere?
[20:13] <bcurtiswx> sure, which log?
[20:13] <kenvandine> ~/.cache/gwibber/gwibber.log
[20:15] <bcurtiswx> kenvandine, sent in IM
[20:15] <kenvandine> got it
[20:15] <kenvandine> thx
[20:17] <kenvandine> dude... what is your interval set to?
[20:17]  * kenvandine should really cap the interval at like 5 or 10m
[20:18] <kenvandine> i've added protect in so it doesn't overlap anymore, but you still have basically a constant state of refreshing
[20:18] <kenvandine> s/protect/protection
[20:19] <kenvandine> bcurtiswx, ^^
[20:19] <bcurtiswx> kenvandine, 1 O:-)
[20:19] <kenvandine> please bump that up
[20:20] <kenvandine> :)
[20:20] <bcurtiswx> kenvandine, OK
[20:20] <kenvandine> pitti, do you think i would need a FFE to prevent people from setting their refresh interval so low?
[20:20] <kenvandine> in gwibber that is
[20:21] <kenvandine> 1) change the selector in preferences so it bottoms out at 5m and migrate existing settings of less than 5m to 5m
[20:21] <kenvandine> this intervals i think cause a fair number of problems
[20:22] <bcurtiswx> kenvandine, can i play devils advocate for a minute?
[20:22] <kenvandine> sure
[20:23] <bcurtiswx> there's a lot of us that like quick refresh rates, (like the auto-updating twitter).. is saving 2000 really needed?
[20:23] <kenvandine> yeah... you'd be surprised how few that is
[20:23] <kenvandine> regardless though... it isn't about how much is being saved
[20:23] <kenvandine> your are beating on it constantly
[20:24] <kenvandine> multiple parallel threads download data, doing stuff with it and insert/updating the db
[20:24] <kenvandine> and as soon as it is done, it does it again
[20:24] <bcurtiswx> kenvandine, what causes the high CPU? it has to read the 2000 and do something with it?
[20:24] <kenvandine> multiple parallel threads... blah blah
[20:24] <kenvandine> no
[20:24] <kenvandine> it is the refreshing
[20:25] <kenvandine> and actually a db that big doesn't cause a problem for the service
[20:25] <kenvandine> not CPU wise
[20:25] <bcurtiswx> well, if i delve any deeper into the cause we'll get into stuff that can be mentioned at UDS (so i won't go any further). :)
[20:25] <kenvandine> it was causing slowness for the client though
[20:27] <kenvandine> i think regardless of any future improvements, preventing intervals < 5m would alleviate a fair bit of pain
[20:27] <kenvandine> bcurtiswx, i have ideas how we can get the twitter realtime feed pretty easily for 3.2
[20:27] <kenvandine> we'll talk about that at UDS
[20:28] <bcurtiswx> kenvandine, i can't wait to be involved then :)
[20:29] <bcurtiswx> i agree, no need to argue <5 mins should be discouraged for natty :)
[20:30]  * kenvandine prepares a branch with the interval tweak
[20:38] <rickspencer3> bug #739923
[21:03] <kenvandine> rickspencer3, the bot isn't very happy now
[21:03] <kenvandine> rickspencer3, the pango_overlay thing in GwibberPosterVBox :)
[21:08] <kenvandine> rickspencer3, after i get out of this meeting, i'll post an example
[21:14] <nperry> Are you aware of   gnome-icon-theme-symbolic: Depends: gnome-icon-theme (< 2.92) but 3.0.0-0ubuntu1~build1 is installed.
[21:15] <nperry> IN the gnome3 stack?
[22:00] <nessita> hi there, any ideas why a launchpad build is failing with:
[22:00] <nessita> dpkg-deb: error: control directory has bad permissions 700 (must be >=0755 and <=0775)
[22:00] <nessita> ?
[22:03] <dobey> nessita: ask on #launchpad instead
[22:03] <nessita> ok
[22:31] <cyphermox> nessita, there is something about umask being discussed on #ubuntu-devel, seems like it might be relevant
[22:35] <chrisccoulson_> tedg, did mterry's changes to dbusmenu to provide a menu closed signal ever land?
[22:35] <chrisccoulson_> i couldn't find it here, unless i just need to update my machine ;)
[22:35] <tedg> chrisccoulson_, Honestly, I'm loosing track.  I think so :-)
[22:35] <nessita> cyphermox: thanks!
[22:36] <tedg> chrisccoulson_, This week the parser side should land, but I dont' think you'll need that.
[22:38] <chrisccoulson_> tedg - yeah, i don't use the parser
[23:22]  * nessita -> eods