[00:33] <len-1304> zequence, Not only is nautilus search pretty much useless, but thunar does the same thing any way... just start typing and the first file that matches high lights.
[00:38] <len-1304> catfish which we used to use as file search, does not have a complete list of depends it seems... or the packages it depends on have changed.
[00:38] <len-1304> $ catfish
[00:38] <len-1304> Error: The required module GError is missing.
[00:51] <zequence> len-1304: Feels like the reasoning might be that a file manager is less usefull these days, when you can do all the searching from a dash (if you have one)
[00:52] <len-1304> zequence, Ya, that is what I was thinking.
[00:52] <zequence> And in the spirit of i*, let the applications keep track of the docs
[00:52] <zequence> Or the files, I mean
[00:52] <len-1304> Not much help for developing or maintaining a system.
[00:53] <len-1304> catfish seems to be broken...
[00:54] <len-1304> Thing is, when you need a tool you need it... even if only once.
[00:56] <len-1304> mlocate is really quick
[01:01] <len-1304> Hmm we have both locate and mlocate installed by default. This is probably bad as each one has a cron task that runs once a day that save all the files names on the drive in a DB.
[01:08] <len-1304> zequence, gnome-search-tool seems to work... seems to have what nautilus now lacks
[08:53] <smartboyhw> Grrrrrrrrr where is the 3.7 (or 3.7.1) kernel for linux-lowlatency???????:(
[09:10] <zequence> There's no hurry for -lowlatency to be updated, since -generic is the same kernel in a respect, and from a testing point of view, at least initially, it's not that crucial for -lowlatency to be in sync
[09:10] <zequence> I'm hoping we can overtake maintenance long before release, so that it will be we who are responsible for this in the future
[09:10] <smartboyhw> zequence, the problem is: I simply can't use the newest kernel, and that gives me for a bad feeling
[09:11] <zequence> smartboyhw: What do you mean you can't use the newest kernel? What in the recent updates are so important for your system?
[11:50] <zequence> I'm getting further in understanding kernel maintenance. Starting with precise, and will be uploading to github
[11:50] <zequence> Next cycle, we'll probably be uploading to a PPA, and sync will be more automated
[12:12] <zequence> smartboyhw: you'll be glad to know that a new 3.7 lowlatency is on the way
[12:29] <smartboyhw> zequence, :D
[12:34] <smartboyhw> zequence, BTW when you do have builds in github tell me to test it:P
[12:34] <smartboyhw> or code or..
[12:35] <zequence> smartboyhw: For the time being, I'm just replicating the work of apw. Once he feels ok with it, he'll use my git tree as source
[12:36] <smartboyhw> zequence, :)
[12:36]  * smartboyhw has sure confidence in zequence maintaining the kernel:D
[12:37] <zequence> I'm just a monkey with his finger on the script button so far
[12:37] <zequence> But, hopefully in the long run, this will turn out to be a vivid part of Ubuntu Studio development
[12:37] <smartboyhw> zequence, no you're not
[13:15] <smartboyhw> PulseAudio 3.0 released!!!!!
[13:40] <zequence> hmm, yes. Let's hope it's not going to make our lives miserable :P
[13:47] <zequence> There have been times, and I guess it's still true, on account of both PA and systemd, when being him might not be the most thankful position.
[13:48] <zequence> Poettering, I mean
[13:52] <smartboyhw> zequence, ;P
[14:13] <len-1304> smartboyhw, from our point the new kernel has not been a good thing.
[14:14] <len-1304> It seems 2.6 performed better.
[14:20] <zequence> len-1304: All though, I'm not totally sure where the problem lies these days. I recently did some testing on 2.6.38 on a newer release than the original, and it was not much better
[14:21] <len-1304> There may be some system stuff that is getting in the way
[14:21] <zequence> There's most definately a performance diff since when we did testing on 2.6.37, but exactly what is an enigma to me
[14:21] <len-1304> Also, if you build 2.6 now, does it use the kernel modules that were available at the time or the newest kernel modules?
[14:23] <zequence> Only if you build the modules separately, I think. dkms
[14:25] <zequence> But they're still built against the source for the kernel
[14:26] <len-1304> When did upstart appear?
[14:27] <zequence> Read on wikipedia that it might have been for 9.10
[14:32] <smartboyhw> I will one day upload the 3.6.11-rt22 kernel (BTW the 3.6 kernel went EOL) and try to see how it works
[14:32]  * smartboyhw is building pulseaudio 3.0 so that everyone can try it out
[14:33] <smartboyhw> I mean after that I will upload to PPA:D
[14:53] <smartboyhw> Hmm got the package uploaded to PPA, and building:D
[14:56] <zequence> nice work. I might not be as eager as you to try it though. But, let us know if something is not working
[15:01] <smartboyhw> Damn the build failed
[15:01] <smartboyhw> Some problem with bluetooth it seem
[15:01] <smartboyhw> dh_install: pulseaudio-module-bluetooth missing files (usr/lib/pulse-*/modules/module-bluetooth-proximity.so), aborting
[15:01] <smartboyhw> I actually installed this and actually have the file so real weird


[00:01] <Unit193> The conference call, basically the agenda.
[00:23] <skellat> Conference call is to discuss release of Raring Ringtail on day of.  Agenda is open after some brief opening remarks.
[03:59] <skellat> Podcast is up with rough transcript all of which explains the release party conference call Thursday: http://ohio.ubuntu-us.org/node/144


[02:47] <araceli> asdsad
[02:47] <araceli> cdecasdcasc
[04:51] <spr3sso> Hola?
[07:30] <brendantcc> my laptop's flipping the bird at me and just won't connect to and use the wifi like a normal laptop... what to do...
[07:33] <akem> Maybe get a Wifi dongle :P
[07:34] <akem> It's weird if it used to work fine.
[07:34] <akem> It could be something parasiting the wifi signal, or signal too low.
[07:59] <brendantcc> update: total network reboot later and the router's happy with my laptop now.
[07:59] <brendantcc> (also, totally unrelated, but my 'server' is actually just a repurposed desktop in my household)
[09:00] <tomreyn> "the wifi [AP]", "router" and "server" could be very different things, or could point to the same system. if you want to be understaood, re-using the same terms to refer to the same things usually helps. ;-)
[09:34] <brendantcc> tomreyn: i referred to my server cause of the reconnect lol
[09:39] <tomreyn> oh :) you successfully got me confused there brendantcc ;)
[09:39] <brendantcc> aha sorry about that mate
[09:39] <tomreyn> hehe, i'm not sure that's your fault


[15:57]  * marjo waves
[15:59]  * bladernr_ waves back
[15:59]  * ameetp waves
[16:00]  * ttx waves
[16:00] <robbiew> \o/
[16:00]  * apw looks acout blearily
[16:00] <cjwatson> hi
[16:01]  * slangasek waves
[16:01] <slangasek> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is slangasek.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:01] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-02-26
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-02-26
[16:01] <slangasek> [TOPIC] QA Team
[16:01] <MootBot> New Topic:  QA Team
[16:02] <slangasek> marjo: you're on :)
[16:02] <marjo> * Lucid Alpha 3 Test Report
[16:02] <marjo> 2010-02-26
[16:02] <marjo> = Summary =
[16:02] <marjo> == Test Coverage ==
[16:02] <marjo> Mandatory Testcase Coverage: 138/180 = 76.67%
[16:02] <marjo> Optional Testcase Coverage: 3/19 = 15.79%
[16:02] <marjo> Image Coverage: 32/32 = 100%
[16:02] <marjo> [16:02] <marjo> 19 Test Failures
[16:02] <marjo> Failure Rate 19/141 = 13.48%
[16:03] <marjo> please note image coverage of 100% thx to everyone who helped out!
[16:03] <seb128> hi
[16:03] <marjo> even with late respins of images
[16:03] <marjo> == Bugs summary ==
[16:03] <marjo> [16:03] <marjo> 59 bugs unfixed
[16:03] <marjo> High - 7
[16:03] <marjo> Medium - 6
[16:03] <marjo> Low - 2
[16:03] <marjo> Undecided - 44
[16:04] <marjo> [16:04] <marjo> 9 bugs fixed
[16:04] <marjo> High - 1
[16:04] <marjo> Medium - 4
[16:04] <marjo> Low - 1
[16:04] <marjo> Undecided - 3
[16:04] <slangasek> next time, we'll have DVDs working to make it more of a challenge ;)
[16:04] <marjo> Here's the list of bugs that were marked as "serious" by testers
[16:05] <marjo> == Serious bugs found during testing ==
[16:05] <marjo> Sorted by status from New to Fix Released
[16:05] <marjo> #527828 | kubuntu oem-config 'No valid steps.'
[16:05] <marjo> ubiquity (Ubuntu)                      | Undecided | New
[16:05] <marjo> #528331 | [Lucid Kubuntu] Ubiquity crashes in PartMan.py when choosing manual partitioning and creating new partition - NameError: global name 'partman' is not defined
[16:05] <marjo> ubiquity (Ubuntu)                      | Undecided | New
[16:05] <marjo> #528346 | Impossible to select in wich disk install to (resize)
[16:05] <marjo> ubiquity (Ubuntu)                      | Undecided | New
[16:05] <marjo> #526626 | [Alpha 3 Testing] Ubuntu Logo on UNE doesn't minimize applications and show Launcher anymore
[16:05] <marjo> go-home-applet (Ubuntu)                | Undecided | New
[16:05] <marjo> #527447 | [Lucid Netbook Alpha 3] env crashed with SIGSEGV in setlocale()
[16:05] <marjo> coreutils (Ubuntu)                     | Medium    | New
[16:05] <marjo> #527972 | [Lucid Alpha 3] usb-creator.exe does not accept ISO selection on Windows XP system
[16:05] <marjo> usb-creator (Ubuntu)                   | Undecided | New
[16:05] <marjo> #527148 | dove fails to shutdown
[16:05] <marjo> linux-mvl-dove (Ubuntu)                | Undecided | New
[16:05] <marjo> #527870 | karmic -> lucid CDROM only upgrade fails
[16:05] <marjo> libsdl1.2 (Ubuntu)                     | Undecided | New
[16:05] <marjo> update-manager (Ubuntu)                | Undecided | New
[16:05] <marjo> libsdl1.2 (Ubuntu Lucid)               | Undecided | New
[16:05] <marjo> update-manager (Ubuntu Lucid)          | Undecided | New
[16:06] <marjo> #527848 | [Lucid] ubi-partman failed with exit code 141 during manual partitioning
[16:06] <marjo> ubiquity (Ubuntu)                      | Undecided | New
[16:06] <marjo> #527115 | [Lucid Xubuntu] Can not perform an upgrade using "update-manager -d"
[16:06] <marjo> update-manager (Ubuntu)                | Undecided | New
[16:06] <marjo> #524439 | 20100219 Server ISO fails to set up console keyboard correctly
[16:06] <marjo> console-setup (Ubuntu)                 | High      | Triaged
[16:06] <marjo> console-setup (Ubuntu Lucid)           | High      | Triaged
[16:06] <marjo> #528034 | Ubiquity crash on Lucid alpha 3 20100225 Kubuntu
[16:06] <marjo> ubiquity (Ubuntu)                      | Undecided | Incomplete
[16:06] <marjo> #527377 | on resize mode i can't choose in which disk install to
[16:06] <marjo> gparted (Ubuntu)                       | Undecided | Incomplete
[16:06] <marjo> #527377 | on resize mode i can't choose in which disk install to
[16:06] <marjo> gparted (Ubuntu)                       | Undecided | Incomplete
[16:06] <marjo> #458482 | usb drives imaged with usb-creator fail to boot on some systems
[16:06] <marjo> usb-creator (Ubuntu)                   | High      | Confirmed
[16:06] <marjo> #510524 | Multiple freeze during boot
[16:06] <marjo> plymouth (Ubuntu)                      | High      | Confirmed
[16:06] <marjo> #510524 | Multiple freeze during boot
[16:06] <marjo> plymouth (Ubuntu)                      | High      | Confirmed
[16:06] <marjo> #527832 | [Lucid] Ubiquity shuts off my monitor during the startup to live environment
[16:06] <marjo> ubiquity (Ubuntu)                      | Undecided | Confirmed
[16:06] <marjo> #527932 | [Lucid Kubuntu] Ubiquity crashes in PartMan.py when choosing manual partitioning - AttributeError: 'PartMan' object has no attribute 'allow_change_step'
[16:06] <marjo> ubiquity (Ubuntu)                      | High      | Fix Committed
[16:06] <marjo> #527722 | pre depends loop
[16:06] <marjo> upstart (Ubuntu)                       | Medium    | Fix Committed
[16:06] <marjo> sorry about very long listing!
[16:07] <marjo> * Hardware testing
[16:07] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:07] <marjo> Netbook:
[16:07] <marjo>   	passed:   9 (70%) failed:   1 (15%)	untested: 3 (15%)
[16:07] <marjo> Laptop:
[16:07] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:07] <marjo> 	passed:   26 (100%) failed:    0 (  0%) untested:  0 (  0%)
[16:07] <marjo> Server:
[16:07] <marjo>   	passed:   52 (96%) failed:    0 ( 0%) untested:  2 ( 4%)
[16:07] <marjo> Desktop:
[16:07] <marjo> 	passed:   11 (92%) failed:    0 ( 0%) untested:  1 ( 8%)
[16:07] <marjo> the untested netbooks will be tested next week
[16:07]  * mvo will look at the update-anager problems
[16:07] <slangasek> I'm puzzled by some of those new Kubuntu partman bugs, I thought those were fixed in ubiquity before our respin
[16:08] <marjo> so, will be closer to 100%
[16:08] <cjwatson> the plugin migration in ubiquity had a fair bit of fallout, and I think we have a lot of tidying up to do there
[16:09] <marjo> cjwatson: thx for that info; will keep an eye on developments
[16:09] <marjo> for beta-1
[16:09] <mvo> http://people.ubuntu.com/~mvo/automatic-upgrade-testing/current/ <- also does not look great
[16:09] <MootBot> LINK received:  http://people.ubuntu.com/~mvo/automatic-upgrade-testing/current/ <- also does not look great
[16:10] <marjo> mvo: would like to follow up w/ you and ara on upgrades topic
[16:10] <mvo> marjo: sure, stepmaker opens up a vastly cool new test area, I'm very excited
[16:10] <slangasek> cjwatson: is that mostly affecting Kubuntu because of difference in how much testing it's gotten?  Does it make sense to have people doing tests of desktop dailies as these bugs get fixed?
[16:11] <marjo> mvo: +1
[16:11] <cjwatson> slangasek: more because of differences in code layout, but yes, if it's not entirely ridiculous I think desktop daily testing would be valuable
[16:12] <slangasek> cjwatson: for both Ubuntu and Kubuntu, or is it primarily Kubuntu we need to worry about?
[16:12] <cjwatson> I'm more worried about Kubuntu
[16:13] <slangasek> marjo: is it possible for you guys to commit some resources to doing daily install tests of Kubuntu desktop over the next few weeks?
[16:13] <slangasek> (generally only needed after there's been an ubiquity upload...)
[16:14] <marjo> slangasek: yes, we are also working w/ rickspencer3 on desktop bug finding anyway
[16:14] <marjo> slangasek: agree
[16:14] <slangasek> ok
[16:14] <slangasek> [ACTION] QA Team to retest Kubuntu desktop after ubiquity uploads
[16:14] <MootBot> ACTION received:  QA Team to retest Kubuntu desktop after ubiquity uploads
[16:14] <marjo> Specs Status
[16:14] <marjo> http://people.canonical.com/~pitti/workitems/canonical-platform-qa-lucid-alpha-3.html
[16:14] <marjo> http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
[16:14] <marjo> * Checkbox Desktop Experience Tests
[16:14] <marjo>    Remaining work items moved to Beta 1
[16:14] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa-lucid-alpha-3.html
[16:14] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
[16:14] <marjo>    - Extract CPU- and I/O-data provided by bootchart
[16:14] <marjo>    - Improve test reporting for boot times
[16:14] <marjo> * Identify and implement kernel test cases to automate
[16:15] <marjo> 	Last work item moved to Beta 1
[16:15] <marjo>    - Evaluate EC2/UEC integration
[16:15] <marjo> * lucid-qa-bugs-hwdb-querying
[16:15] <marjo> 	Medium priority blueprint – work items moved to Beta 1
[16:15] <marjo> that's all folks!
[16:16] <slangasek> ok, thanks!
[16:16] <slangasek> [TOPIC] Server Team
[16:16] <MootBot> New Topic:  Server Team
[16:16] <slangasek> ttx: hi
[16:16] <ttx> slangasek: o/
[16:16] <ttx> Our updated status at : https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:16] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:16] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:17] <ttx> Alpha3 end status, a few work items have been deferred to beta1, a few others simply postponed to lucid+1 or never
[16:17] <ttx> Nothing left in alpha3
[16:17]  * slangasek nods
[16:17] <ttx> Beta1 planning is believed to be complete
[16:17] <ttx> http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04-beta-1.html
[16:17] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04-beta-1.html
[16:18] <ttx> should show what we are aiming at for beta1
[16:18] <ttx> The most impacting thing in there is probably "EBS root"
[16:18] <slangasek> hmm, when did pitti say he was resetting those lines? :)
[16:19] <ttx> slangasek: something like, today :)
[16:19] <slangasek> ah, but he's off today, oops :)
[16:19] <ttx> EBS root will probably impact EC2 deliverables
[16:20] <ttx> The rest is mostly QA/Doc/Bugfixing
[16:20] <ttx> Beta1-targeted bugs:
[16:20] <ttx> I listed those in the report, they don't all have assignees yet
[16:20] <ttx> That will be fixed by next week, obviously
[16:20] <slangasek> ttx: impact EC2 deliverables how?
[16:21] <ttx> slangasek: IIUC we would also publish a EBS root system
[16:21] <ttx> (rather than just an AMI)
[16:21] <ttx> smoser: around ?
[16:21] <smoser> here
[16:22] <ttx> could you explain impact of EBS root deliverables, if any ?
[16:22] <smoser> the end result is more ami-XXXXXXXX numbers
[16:22] <ttx> (on the release process)
[16:22] <slangasek> ah :/
[16:22] <smoser> and, then, ISO testing on those.
[16:22] <slangasek> doubles the current number?
[16:22] <smoser> yeah.
[16:23] <ttx> slangasek: other questions on that part ?
[16:24] <slangasek> are we sure that supporting both types of images as first-class Ubuntu images is the right thing to do?
[16:24] <ttx> slangasek: we expect most people to use those instead of the regular ones in a few
[16:24] <slangasek> ok
[16:24] <ttx> since they basically allow persistence for a reasonable cost
[16:25] <ttx> smoser: correct me if I'm wrong here
[16:25] <ttx> Ok, moving on to bugs affecting server, in other teams:
[16:25] <smoser> there is extremely little reason to prefer instance-store images.
[16:25] <slangasek> [ACTION] slangasek to record server-lucid-ec2-ebsroot work items related to ISO testing integration
[16:25] <MootBot> ACTION received:  slangasek to record server-lucid-ec2-ebsroot work items related to ISO testing integration
[16:25] <smoser> so, yes, we expect high usage of ebs root ami
[16:26] <ttx> bug 506297
[16:26] <ttx> That one was already revealed in alpha2 ISO testing
[16:26] <ttx> bug 524439
[16:26] <ttx> That one is more recent.
[16:27] <ttx> Both are linked to plymouthization if my understanding is correct.
[16:27] <ttx> That's about all for me. Questions ?
[16:27] <slangasek> yes; the former is covered by Keybuk's work this week (and next) to Fix Plymouth
[16:28] <slangasek> the latter will take a back seat to this for the moment, AIUI, since it has the same assignee
[16:28] <cjwatson> oh, I took over the latter
[16:28] <slangasek> oh, ok
[16:28] <cjwatson> I'll take over the bug too
[16:28] <ttx> slangasek: cool, we need those cosmetic issues fixed for beta1, since we want to call for testing quite widely
[16:28] <slangasek> wasn't sure if you had taken it and assigned it back again
[16:29] <slangasek> ttx: the plymouth stuff is so very much more than cosmetic :-)
[16:29] <slangasek> fortunately, your cosmetic issue will get fixed in the process :)
[16:29] <ttx> slangasek: the bugs are, though :)
[16:29] <slangasek> only on server; for everyone else they're crasher bugs
[16:29] <ttx> I mean, their symptoms are easily workaroundable
[16:29] <ttx> right :)
[16:29] <cjwatson> the console-setup one is chiefly complicated by the kernel sucking
[16:29] <cjwatson> I've been trying to see if I can make the kernel not suck
[16:30] <ttx> cjwatson: interestingly enough, I can't reproduce it if I have a crypted LVM
[16:30] <ttx> cjwatson: looks like the keyboard setup for password prompt kinda sticks to console
[16:30] <ttx> (not sure if that helps in any way)
[16:30] <Keybuk> that's an interesting issue
[16:31] <Keybuk> setting the keyboard layout so you can type your plymouth passphrase, but while plymouth is running
[16:31] <Keybuk> eep
[16:31] <cjwatson> ttx: that's because then the console is set up in the initramfs
[16:31] <ttx> cjwatson: ack, makes sense
[16:33] <slangasek> ok - anything further on server?
[16:33] <slangasek> [TOPIC] Mobile Team
[16:33] <MootBot> New Topic:  Mobile Team
[16:33] <slangasek> ttx: thanks
[16:33] <slangasek> asac: hi
[16:33] <asac> hey
[16:33] <asac> https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:34] <asac> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:34] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:34] <asac> summary:
[16:34] <asac> * rootstock/qemu stabilization ... this is what occupied ogra for quite some time ;)
[16:35] <ogra> still doing
[16:35] <asac> it works, but seems qemu goes up and down a bit ... (nothing i would be worried about)
[16:35] <ogra> qemu is messy
[16:35] <asac> * thumb2 porting sprint and porting  -> we had another mini sprint this week, where we managed to scratch a few more packages from our thumb2 list
[16:36] <asac> * obviously we had alpha3 testing ... which didnt reveal really bad regressions, yay!
[16:36] <ogra> no, it rather improved :)
[16:36] <ogra> apart from the openoffice issue :)
[16:36] <asac> * openoffice "uno" investigation - round 2 - started (417009)  -> this about a bug we carry since karmic and we try to put resources in now that we are past FF
[16:36] <ogra> but that was fixed in time
[16:37] <asac> webservice specs - implementation started --- not much to implement, but we are getting pulled into other projects these weeks so we are not yet ready to upload
[16:37] <ogra> seems NCommander is on something there ... not sur its the actual issue but seems to be narrowed down a bit more
[16:37] <asac> howver, the office glue code seems to work quite well so i hope this will happen once we come back next week from a mini summit
[16:38] <asac> e.g. just a matter to package .desktop files up together with it and ensuring we dont claim too many mime-types etc.
[16:38] <asac> Image Status:
[16:38] <asac> * imx51 and dove in usable shape
[16:38] <asac> ok on Specs:
[16:38] <asac> [LINK] http://people.canonical.com/~pitti/workitems/canonical-mobile.html
[16:38] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile.html
[16:38] <asac> [LINK] http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html
[16:38] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html
[16:39] <slangasek> asac: what about these specs that still have outstanding workitems for alpha-3?
[16:39] <asac> i thought i cleaned them up ... most likely some have still a bad label next to the Work items (...) and hence show up there
[16:40] <ogra> yeah, the powermanagement spec should be sorted
[16:40] <slangasek> https://blueprints.launchpad.net/ubuntu/+spec/mobile-lucid-arm-lightweightbrowser still shows as outstanding
[16:40] <asac> slangasek: that has one TODO left ... which is to complete the feature comparison (that isnt really relevant anymore)
[16:41] <slangasek> the "bad labels" are precisely what gets tracked on work item status, so please clean these up :)
[16:41] <asac> i can mark that as posponed
[16:41] <slangasek> is there a final decision there to ship firefox, then?
[16:41] <asac> slangasek: yes.
[16:41] <slangasek> ok
[16:41] <asac> slangasek: unless someone jumps in and forces us ;)
[16:42] <asac> (not expected atm)
[16:42]  * slangasek nods
[16:42] <asac> so RC Bugs:
[16:42] <asac> list grew a bit this week and we have a few more candidates which wait for verification
[16:42] <asac> we got from a3 testing
[16:43] <asac> porting list is not moving as fast as we would like to, but the list is small enough to not to be considered a risk
[16:43] <asac> main point i wanted to rais is the thumb2 rebuild we will now do
[16:43] <asac> thats not RC Bugs anymore ;)
[16:44] <asac> i will coordinate the final package list with doko who wanted to include libs in that rebuild ... then we will split it up in chunks
[16:44] <slangasek> how soon do you think the rebuilds will start, and how long is it expected to take to finish?
[16:44] <asac> and send out an announce to ubuntu-devel before starting ... also i will keep you updated before each batch
[16:44] <asac> slangasek: start on monday.
[16:44] <ogra> ... universe looks bad wrt FTBFS and thumb porting ... would be nice if there would be a MOTU team somehow that would be intrested in arm help
[16:45] <slangasek> what's the reason for splitting the rebuild into chunks?
[16:45] <asac> slangasek: time it will take: thats difficult to estimate. i hope 2- 3 month
[16:45] <asac> slangasek: in case we underestimate how long it will take i thought it might be beneficial to not pump everything in one batch
[16:46] <slangasek> oh, well, we don't have 3 months before release, even
[16:46] <slangasek> so yeah, we wouldn't want to leave a bunch of stuff in the queue still at release time
[16:46] <asac> right. thats the idea ... do it in chunks ... so we dont have stuff building when release happens ;)
[16:46] <slangasek> is this 2-3 months whole-archive, or just main?
[16:46] <asac> or even at milestones (which proabably would hit us hardest)
[16:46] <asac> slangasek: sorry 2-3 weeks ;)
[16:46] <slangasek> oh
[16:46] <seb128> you need to rebuild everything?
[16:46] <ogra> heh
[16:47] <slangasek> that's saner
[16:47] <asac> thats an optimistic estimate
[16:47] <seb128> or just thing which didn't get uploaded in lucid?
[16:47] <asac> but it shouldnt take much longer
[16:47] <ogra> seb128, only stuff that wasnt built yet
[16:47] <slangasek> and I guess that's definitely just main, then
[16:47] <seb128> ok
[16:47] <asac> seb128: just things that were not uploaded
[16:47] <asac> slangasek: right. just main
[16:47] <asac> we wont do that for universe this cycle
[16:47] <ogra> seb128, nothing from your desk for sure :)
[16:47] <asac> unless things go really quick and we see that we can push more chunks
[16:48] <slangasek> asac: will you cross-check against the list of out-of-date packages, to make sure we're not getting unnecessary reuploads of packages that already FTBFS? http://people.canonical.com/~ubuntu-archive/testing/lucid_outdate.html
[16:48] <asac> seb128: also libs that were build before some date that doko has to give me (there was a toolchain bug we need to wipe)
[16:48]  * asac checks
[16:49] <asac> slangasek: yeah we should take that into account
[16:49] <slangasek> in the meantime, we should move on, unless there's anything else to cover for Mobile?
[16:49] <asac> i will try to get those removed from the list
[16:49] <asac> not from us
[16:49] <slangasek> [TOPIC] Kernel Team
[16:49] <MootBot> New Topic:  Kernel Team
[16:49] <slangasek> asac: thanks
[16:49] <slangasek> apw: hi
[16:49] <apw> hi
[16:49] <asac> thanks
[16:50] <apw> Overall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  Alpha-3 activity shows 100% complete, I have pushed out a number of items which are highlighted in the release status.  Beta-1 activity is summarised at the second URL below, with those item pushed out shown as At Risk.  Out burndown chart is at the third URL:
[16:50] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:50] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
[16:50] <apw> [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:50] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:50] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
[16:50] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:50] <apw> Of the pushed out items most are not critical to the release.  The main issues are well progressed, patches for the readahead scanning are in testing, discussions on builtin modules are in progress, and we hope to have the majority closed out soon.
[16:50] <apw> The bugs picked out in the agenda are progressing well.  The first we have fixes for and they should be uploaded today.  The second is likely fixed by upsteam DRM which are testing at the moment, another stong indicator that we need a drm update in lucid.  Discussion on that should be concluded by early next week.
[16:50] <apw> ..
[16:51] <slangasek> is '..' and EOF marker I'm unfamiliar with? :)
[16:52] <slangasek> (I guess so!)
[16:52] <slangasek> any questions for kernel?
[16:52] <apw> heh yeah .. is an EOF  we use that in our meetings sorry!
[16:52] <apw> i've updated the first one to fix the pushed items formatting
[16:53] <slangasek> [TOPIC] Desktop Team
[16:53] <MootBot> New Topic:  Desktop Team
[16:53] <slangasek> apw: thanks
[16:53] <slangasek> seb128: hi
[16:53]  * ScottK is here for Kubuntu
[16:54] <seb128> slangasek, hey
[16:54] <seb128> status is on https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:54] <seb128> the weekly summary for the team:
[16:54] <seb128> desktop-lucid-startup-speed considered done now (pitti still tracking one udisks item)
[16:54] <seb128> DX integration: integrated new releases, gnome-power-manager ported to the application-indicator system
[16:54] <seb128> OLS integration: rhythmbox music store in main and on by default (but server side not activated yet)
[16:54] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:54] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:54] <seb128> Desktop changes: GNOME 2.29.91, gtk client side decoration, new gnome-keyring, gwibber installed by default now (but not autostarted yet)
[16:54] <seb128>
[16:55] <seb128> the alpha3 work items are on http://people.canonical.com/~pitti/workitems/canonical-desktop-team-lucid-alpha-3.html
[16:55] <seb128> Overall status: all alpha3 work items done excepted one desktop-lucid-social-from-the-start documentation item which can be delayed to beta;
[16:55] <seb128>
[16:56] <seb128> the beta1 list is on http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04-beta-1.html
[16:56] <slangasek> seb128: there was also an outstanding workitem for #
[16:56] <slangasek> desktop-lucid-new-firefox-support-model
[16:57] <seb128> (sorry got wireless disconnected and reconnected)
[16:57] <seb128> slangasek, the desktop-lucid-new-firefox-support-model items got done I think
[16:57] <slangasek> seb128: well, it's not marked as done
[16:57] <seb128> (from what pitti told me, checking)
[16:58] <slangasek> identify extensions to be kept in archive - binary components or importance can qualify an extension: TODO
[16:58] <seb128> hum, it's not on http://people.canonical.com/~pitti/workitems/canonical-desktop-team-lucid-alpha-3.html for some reason
[16:59] <slangasek> oops :)
[16:59] <seb128> asac, ^ do you know about that one?
[16:59] <seb128> slangasek, I don't have an answer about this one right now, will check and come back to you later
[16:59] <slangasek> seb128: sounds good
[17:00] <slangasek> [ACTION] seb128 to check on status of outstanding a3 wi for desktop-lucid-new-firefox-support-model
[17:00] <MootBot> ACTION received:  seb128 to check on status of outstanding a3 wi for desktop-lucid-new-firefox-support-model
[17:00] <seb128> otherwise for beta1
[17:00] <seb128>     * desktop applications are being ported to the new appindicator systemn around 6 of those changes are waiting for review now or will be soon and should go in lucid before beta-1
[17:00] <seb128> we should get those done next week
[17:01] <seb128> + we will need extra testing on gtk client side decoration
[17:01] <seb128> that's still new technology and could create issues
[17:01] <seb128>
[17:01] <seb128> otherwise kubuntu summary is on the wiki too
[17:01] <seb128> not sure if somebody from the kubuntu team usually speak for those ;-)
[17:02] <slangasek> ScottK: anything you want to add regarding Kubuntu?
[17:02] <ScottK> For Kubuntu the main thing is getting kdebindings fixed on armel
[17:02] <ScottK> That's planned for next week.
[17:02] <ScottK> We're also still looking to get the KDE Firefox patches in.
[17:02] <slangasek> that should help clean up http://people.canonical.com/~ubuntu-archive/testing/lucid_outdate.html :)
[17:02] <ScottK> I know asac and Riddell` were working on that, but don't know exactly where se stand.
[17:02] <ScottK> Yes
[17:02] <ScottK> We're dead on armel at the moment
[17:03] <ScottK> koffice is updated to koffice2 in Universe
[17:03] <ScottK> We won't have a koffice in Main this cycle (upstream isn't confident enough)
[17:03] <ScottK> Riddell removed kdevelop since it's KDE4 release doesn't happen until May
[17:04] <ScottK> We are very, very close to moving kdelibs (the KDE3 one) to Universe
[17:04] <ScottK> That's it.
[17:04] <slangasek> ok, thanks
[17:05] <slangasek> anyone with questions on desktop?
[17:06] <slangasek> [TOPIC] DX Team
[17:06] <MootBot> New Topic:  DX Team
[17:06] <slangasek> seb128, ScottK: thanks
[17:06] <slangasek> davidbarth, njpatel: hi
[17:06] <davidbarth> hi slangasek
[17:06] <davidbarth> so not much to say this week
[17:06] <davidbarth> report at: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus as usual
[17:07] <njpatel> slangasek, hey
[17:07] <davidbarth> mostly work on bug fixing system indicators further
[17:07] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:07] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:08] <davidbarth> of note, is the actual landing of cs-deco, after some last minute performance issues were solved by seb128 and bratsche
[17:08] <davidbarth> oops, the content of the report should be good now; i forgot to save
[17:08] <davidbarth> be sure to relead in a few secoinds
[17:08] <davidbarth> dx-lucid-gtk-improvements
[17:09] <davidbarth> further bug fixes
[17:09] <davidbarth> reminder: use the 'gtk-csd' tag for bugs related to that change
[17:09] <davidbarth> dx-lucid-xsplash - further work on that is being postponed to L+1
[17:09] <davidbarth> dx-lucid-session-menu: #506683 is fixed and released
[17:10] <davidbarth> dx-lucid-notifications: we have a patch for the closenotification api in testing right now; should land next week before b1
[17:11] <davidbarth> we had not planned to do major releases this week, still tedg made tarballs for 6 of our projects to release more bug fixes
[17:11] <davidbarth> questions?
[17:12] <cjwatson> dx-lucid-netbook-launcher-startup-speed is marked as todo in foundations-lucid-boot-performance - are you tracking that as well?
[17:12] <davidbarth> cjwatson: that part is done as far as we're concerned
[17:13] <davidbarth> cjwatson: i should mark it so, unless some stakeholder has a different feedback
[17:14] <slangasek> davidbarth: I gather from emails that foundations-lucid-gfxboot-update is still blocked on having the new graphics, can we talk about this?
[17:14] <davidbarth> cjwatson: hmm, actually, let me check that again, as i haven't seen recent charts with the results of netbook-launcher
[17:14] <cjwatson> davidbarth: it's only supposed to be marked done once it's been confirmed as hitting its budget
[17:14] <davidbarth> cjwatson: as a reminder for next week, ie there should be no regressions
[17:14] <cjwatson> slangasek,davidbarth: I'll cover that in our section - we revisited that with the design team today
[17:14] <slangasek> ok
[17:14] <cjwatson> and we're going to take a different approach
[17:14] <davidbarth> cjwatson: right, so let's put that as an action item for me for next week
[17:15] <davidbarth> slangasek: yes, the new graphics are blocked
[17:15] <davidbarth> cjwatson: ah ok fine
[17:16] <cjwatson> (no disrespect intended etc., new plan just seems more viable)
[17:16] <slangasek> anything else on DX?
[17:17] <slangasek> [ACTION] davidbarth to check on budget status of dx-lucid-netbook-launcher-startup-speed
[17:17] <MootBot> ACTION received:  davidbarth to check on budget status of dx-lucid-netbook-launcher-startup-speed
[17:18] <slangasek> [TOPIC] Foundations Team
[17:18] <MootBot> New Topic:  Foundations Team
[17:18] <slangasek> davidbarth: thanks
[17:18] <cjwatson> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:18] <cjwatson> [LINK] http://people.canonical.com/~pitti/workitems/canonical-foundations-ubuntu-10.04-beta-1.html
[17:18] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:18] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-foundations-ubuntu-10.04-beta-1.html
[17:18] <cjwatson> Beta-1 work items are mostly composed of deferrals from alpha-3 (the alpha-3 list should be at zero after the next refresh), so there are several specs there with one or two tail-end work items to tidy up.
[17:18] <cjwatson> (and sorry I hadn't cleaned up the alpha-3 list before now)
[17:18] <cjwatson> Boot speed doing well, with kernel+plumbing+X down to 6 seconds on reference hardware.
[17:18] <cjwatson> parted 2.1 migration in progress, following FFe.  With a little bit of partman work on top, this will give us non-512-byte sector support and better alignment, so should hopefully clear up a lot of "doesn't wor
[17:18] <cjwatson> k with Windows 7" bugs.
[17:18] <cjwatson> Plymouth still a hot button; lots of bugs related to that.
[17:18] <cjwatson> The plugin migration in ubiquity has been a bit rough, and we're knocking off bugs related to that as fast as possible.  They're mostly small.
[17:18] <cjwatson> We need a volunteer to clear up the rest of foundations-lucid-supportable-binaries.
[17:19] <cjwatson> Java and X versions still need to be confirmed for foundations-lucid-release-collaboration-with-debian.
[17:19] <cjwatson> foundations-lucid-gfxboot-update discussed with design team today.  Backing off from previous pre-greeter approach, which was going to take too long to polish up UI-wise, and planning to use ubiquity's language selector instead; this will involve a lot less new code.
[17:19] <cjwatson> Still a number of software-center tasks open, but the list is beginning to look under control.
[17:19] <cjwatson> --
[17:19] <slangasek> I had volunteered to follow through on foundations-lucid-supportable-binaries, it's just been getting pushed down the stack by other fires
[17:20] <cjwatson> ok, shall I assign the remaining work items to you?
[17:20] <slangasek> sure
[17:20] <slangasek> gfxboot-update> doesn't that mean we have the problem of the UI not being translated in the live env?
[17:21] <cjwatson> no, it shouldn't do - standalone ubiquity language selector -> try/install choice -> if you select try, starts live env
[17:21] <cjwatson> if you select install, continues
[17:21] <slangasek> oh, ok
[17:22] <slangasek> neat, then :)
[17:22] <cjwatson> this is all from discussion today, but I'm feeling a lot happier about it after that
[17:23] <slangasek> all looks sane to me - anything else on Foundations?
[17:24] <cjwatson> we're mostly hunkering down for bugfixing now, I think.
[17:24] <slangasek> indeed
[17:24] <slangasek> [TOPIC] Security Team
[17:24] <MootBot> New Topic:  Security Team
[17:24] <slangasek> cjwatson: thanks
[17:24] <slangasek> jdstrand: hi
[17:24] <jdstrand> hi
[17:25] <jdstrand> you can see our status here: https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:25] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:25] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:25] <jdstrand> as far as dev work is concerned, we were done with alpha-3 stuff last week. that did not change this week :)
[17:26] <jdstrand> and the team as a whole worked on security stuff in stable releases this past week, so nothing new to report
[17:26] <slangasek> phew :)
[17:26] <jdstrand> that's pretty much it
[17:27] <slangasek> anything of concern for beta1?
[17:27] <jdstrand> no
[17:27] <slangasek> ok, cool
[17:27] <jdstrand> we are in bug fixing mode
[17:27] <slangasek> [TOPIC] MOTU
[17:27] <MootBot> New Topic:  MOTU
[17:27] <slangasek> jdstrand: thanks
[17:27] <jdstrand> the bps that are left are either not dependent on a milestone or are bug fixes
[17:27]  * sistpoty|work waves
[17:27] <ScottK> sistpoty|work: You around?
[17:27] <jdstrand> np
[17:27] <slangasek> ScottK, sistpoty|work: hi
[17:27] <ScottK> sistpoty|work: You go first
[17:28] <sistpoty|work> we got a haskell and an ocaml transition waiting to be finished
[17:28] <sistpoty|work> Laney tracks haskell, and makes good progress afaict
[17:28] <ScottK> ocaml is making progress too (I see the bug reports)
[17:28] <sistpoty|work> ocaml is also tracked, could need some more people uploading rebuilds
[17:29] <slangasek> ocaml I've been seeing bug reports for; haskell I have not - perhaps because there are no FFes needed there?
[17:29] <sistpoty|work> others than that, FFe handling started quite smooth
[17:29] <slangasek> I could take some ocaml rebuilds, where's the list?
[17:29]  * sistpoty|work looks
[17:30] <ScottK> Watching the Debian Python 2.6 tranisition work, I'm a little nervous about our status, but don't have specifics.
[17:31] <sistpoty|work> bug #526073
[17:32] <slangasek> sistpoty|work: thanks
[17:32] <sistpoty|work> others than that, thanks for driving motu-release <-> ubuntu-release merge, slangasek
[17:32] <slangasek> ScottK: python> you're concerned about latent bugs in Ubuntu's python 2.6 that aren't getting picked up?
[17:32] <ScottK> slangasek: Yes.
[17:32] <antihacker> anyone know what axel.dav is.
[17:33] <slangasek> ScottK: what are the chances those bugs were marked release-critical in Debian?
[17:33] <ScottK> slangasek: Once we get a little further along we should have another look at sync/merge candidates
[17:33]  * slangasek nods
[17:33] <ScottK> slangasek: Some, but many are just getting fixed without bugs being filed
[17:33] <slangasek> ScottK: yep, figured
[17:34] <ScottK> I'm sure once python2.6 is default in Debian we'll get more
[17:34] <slangasek> ScottK: at what point further along should we review the sync/merges for python?
[17:34] <antihacker> anyone know what axel.dav is?   low level format access violation  DAV
[17:34] <ScottK> antihacker: You're in the wrong channel
[17:34] <antihacker> k, sorry
[17:34] <ScottK> slangasek: Let's say two weeks.  Not sure really.
[17:34] <slangasek> ok
[17:35] <slangasek> [ACTION] ScottK, slangasek to review python sync/merge candidates ~Mar 12
[17:35] <MootBot> ACTION received:  ScottK, slangasek to review python sync/merge candidates ~Mar 12
[17:35] <slangasek> noted :)
[17:35] <slangasek> anything else to discuss?
[17:36] <ScottK> Not from me
[17:36] <slangasek> [TOPIC] AOB
[17:36] <sistpoty|work> don't think so
[17:36] <MootBot> New Topic:  AOB
[17:36] <slangasek> sistpoty|work, ScottK: thanks, as always
[17:36] <slangasek> anything else someone wants to cover here today?
[17:37] <slangasek> #endmeeting
[17:37] <MootBot> Meeting finished at 11:37.
[17:37] <slangasek> thanks, folks!
[17:39] <marjo> slangasek: thx


[00:10] <hicham> lets use geistest and see ...
[00:15] <joh> Hi, are there any API reference docs for Unity Lenses? Something more detailed than https://wiki.ubuntu.com/Unity/Lenses
[00:20] <nhaines> sladen: I'm curious, maybe you know... why were gnome-terminal's scrollbars turned dark in the last light-themes release in Ambience?
[00:21] <nhaines> sladen: also, curious about the status of Ubuntu Monospace font these days.
[00:21] <nhaines> Just a friendly ping.  :)
[00:22] <davidcalle> When my lens is launched at startup, it crashes on utf8 strings. When it's launched during a session it doesn't.
[00:22]  * davidcalle is scratching is head.
[00:23] <joh> davidcalle: Do you have some experience with lens development? :)
[00:23] <davidcalle> joh, I'm developing the Books one.
[00:24] <joh> davidcalle: Ah cool, then maybe you can help me..?
[00:24] <joh> davidcalle: I'm writing a Tomboy lens
[00:24] <davidcalle> joh, sure!
[00:24] <joh> davidcalle: And in order to display a note when clicked in the lens, I need to perform a DBus method call.
[00:25] <joh> davidcalle: However, from the examples I've found, it seems the lens entries can only point to valid URIs?
[00:25] <joh> davidcalle: I.e. they cannot be used to perform arbitrary actions...
[00:25] <davidcalle> joh, have you looked at kenvandine's code (gwibber lens) ?
[00:26] <joh> davidcalle: Just briefly... I'll look again :)
[00:28] <davidcalle> joh, you should talk to him about that, as I won't be able to help you with dbus calls. ;) Also, you should try to ping njpatel about what a lens can call.
[00:29] <joh> davidcalle: Well, I know how to make the dbus calls, I just don't know how to glue it together with the unity lens.
[00:30] <joh> davidcalle: ok thanks :
[00:30] <joh> *:)
[00:30] <davidcalle> joh, good luck with your lens. Is the code somewhere? :)
[00:31] <joh> davidcalle: Thanks, the code isn't up yet, but will be on bzr once I get it working :)
[00:31] <joh> *on launchpad
[00:31] <davidcalle> joh, ok, good luck then :)
[00:36] <zniavre> good evening i just unistalled-reinstalled unity but still no icons inside the launcher what can i do please?
[00:36] <joh> Meh, I can't get the gwibber lens to work :P
[00:40] <hicham> oh, nice, unity kinda works
[00:48] <nhaines> hicham: congrats.  :D
[00:49] <hicham> nhaines: thanks :)
[00:49] <hicham> nhaines: http://img33.imageshack.us/i/screenshot1yl.png/
[00:51] <nhaines> Looking good.  :)
[00:56] <hicham> is gnome-panel supposed to be launched in unity ?
[00:57] <nhaines> hicham: no, it uses unity-panel-service instad.
[00:57] <nhaines> instead.
[00:57] <hicham> nhaines: did you see the screenshot ?
[01:00] <nhaines> hicham: yes I did
[01:00] <hicham> adamw: how do you start unity in ubuntu ?
[01:00] <hicham> oops
[01:00] <nhaines> hicham: it's just sort of automatic.  :)
[01:00] <hicham> nhaines: do you have a custom session for it ?
[01:01] <spikeb> yes
[01:01] <hicham> spikeb: what is the package for it ?
[01:01] <spikeb> i have no idea, honestly.
[01:03] <hicham> spikeb: what do you have in /usr/share/gnome-session/sessions ?
[01:05] <spikeb> i have an ubuntu.session (that'd be the unity session)
[01:05] <nhaines> hicham: http://pastebin.ubuntu.com/592891/
[01:12] <hicham> nhaines: thanks a lot
[01:13] <hicham> how I am supposed to log out of unity ?
[01:15] <nhaines> hicham: you're not supposed to, like any other window manager, I think.  :)
[01:16] <nhaines> Oh!  no, sorry, I understand.  There's an application indicator applet that lets you log out.
[01:16] <hicham> nhaines: what is its name ?
[01:17] <nhaines> hicham: I don't know... I can never remember.  :(
[01:17] <jcastro> kenvandine: any luck with the lens?
[01:17] <nhaines> SysRq-K will kill the X server.
[01:20] <zniavre> indicator-session?
[01:22] <jcastro> joh: http://developer.ubuntu.com/api/
[01:22] <jcastro> joh: ^^ should be there
[01:33] <hicham> zniavre: thanks
[01:37] <coz_>  hey
[01:50] <LLStarks> i'd like a second opinion on evince not being user accesable as a design decision.
[01:50] <LLStarks> bug 743383
[02:09] <joh> jcastro: great, thanks
[02:41] <MaximLevitsky> Unity is usable?
[02:41] <MaximLevitsky> I sure assume it is
[02:42] <MaximLevitsky> I open a vdesktop with my homework
[02:42] <MaximLevitsky> I open a browser
[02:42] <MaximLevitsky> couple of PFS
[02:42] <MaximLevitsky> PDFs
[02:42] <MaximLevitsky> text editor
[02:42] <MaximLevitsky> Now I want to rest a bit, so I switch desktop, and try to open firefox
[02:43] <MaximLevitsky> And guess what I get
[02:43] <MaximLevitsky> That is usable?
[02:44] <MaximLevitsky> When to see cube and unity?
[02:45] <hicham> I have unity and the cube
[02:45] <MaximLevitsky> how?
[02:45] <hicham> enable it from ccsm
[02:45] <MaximLevitsky> unity depends on desktop wall
[02:45] <MaximLevitsky> in 11.04 of course
[02:46] <ion> What *did* you get?
[02:47] <MaximLevitsky> If I enable cube, it first tell me to disable wall
[02:47] <MaximLevitsky> I answer yes
[02:47] <MaximLevitsky> It tells me that unity depeands on wall and asks me to disable it
[07:40] <didrocks> good morning
[08:01] <oSoMoN> good morning
[08:07] <MacSlow> greetings everybody
[08:16] <zniavre> good morning
[08:17] <zniavre> im still stuck with my missing icons inside the launcher i hav re-installed all nux-unity related package im wondering what i did wrong ?
[08:59] <magcius> gah, what's happening
[08:59] <magcius> my recent experience:
[09:00] <magcius> all windows freeze
[09:00] <magcius> alt+f2, "pkill notify-osd"
[09:00] <magcius> magically, all windows start to work again
[09:00] <magcius> is there something weird where when you can't ACK dbus message, gtk+ freezes or something?
[09:01] <RAOF> No.  There *is* a weird bug where one of compiz's X connections sits around waiting for input that never comes, though.
[09:02] <aquarius__> hey didrocks
[09:02] <didrocks> RAOF: auquarius is just stuck in that case
[09:02] <didrocks> wb aquarius__
[09:02] <didrocks> RAOF: needs someone for testing/hammering his system? :)
[09:03] <aquarius__> RAOF: I have X (or compiz, or something, I don't know) wedged, so if there's anything you want me to try running, commands to do, logs to provide, I am happy to do so.
[09:04] <RAOF> aquarius__: If you attach gdb to compiz, is it waiting in poll()?  If so, yeah, I know *about* that problem (but not what's causing it, precisely where it is, or how to fix it).
[09:04] <aquarius__> you'll have to tell me how to do that
[09:04] <RAOF> sudo gdb compiz $(pgrep compiz); bt
[09:04] <aquarius__> (njpatel's told me before, but I don't have easy access to previous conversations in this VC :))
[09:05] <RAOF> You need to wait for gdb to come up for the bt command to do anything interesting.
[09:06] <RAOF> But the *problem* is (likely to be) that compiz is sitting, waiting, for X to reply to it's request.  And the server doesn't.
[09:06] <aquarius__> top of the compiz backtrace is __kernel_vsyscall, and the second line is __poll, and then third is ?? in libxcb
[09:07] <aquarius__> is that what you meant?
[09:07] <RAOF> Yeah.
[09:07] <RAOF> That's what I meant.
[09:07] <aquarius__> ok. If there's any other information I can provide to you, having a system *in* this wedged state, I'm happy to... but it sounds like you already have all the info you need?
[09:08] <RAOF> Yeah, I think so.  And I can reproduce at least one version of that hang at will.
[09:08] <aquarius__> interestingly, when I've had this before, killing compiz and then restarting it (or starting metacity with --replace from a VC) doesn't seem to recover; normally what happens is that X quits and I have to log in again
[09:09] <RAOF> *That's* probably an X bug to do with closing down clients.
[09:10] <aquarius__> Is there any way to work around it? Today, I don't mind -- I've only just turned my machine on (well, resumed from suspend). But other days I have work in windows that I don't really want to lose, and then end up losing them.
[09:10] <aquarius__> so today I can just service gdm restart and be fine
[09:10] <RAOF> Attaching gdb to Xorg and acquiring a backtrace for *that* would be quite useful :)
[09:10] <aquarius__> right now?
[09:11] <aquarius__> that is, while still wedged?
[09:11] <RAOF> Yeah, if killing compiz is going to cause it.
[09:11] <aquarius__> OK. how do I quit the gdb I have looking at compiz without killing compiz?
[09:12] <RAOF> Just type  ‘quit’; gdb won't kill compiz.
[09:12] <aquarius__> oh, I can't read. It says it'll detach from the inferior process, not kill it :)
[09:12] <RAOF> :)
[09:13] <aquarius__> ok, so I should gdb into the /usr/bin/X process?
[09:13] <RAOF> Yeah.
[09:13] <RAOF> First could you install some debugging symbols?
[09:13] <RAOF> xserver-xorg-core-dbg is the most important package.
[09:13] <aquarius__> ah
[09:14] <RAOF> Then xserver-xorg-video-$YOUR_CARD-dbg
[09:14] <RAOF> But that's not as critical.
[09:15] <aquarius__> ah. I do not have the latest version of xserver-xorg-core
[09:15] <aquarius__> damn.
[09:15] <RAOF> Ah.
[09:15] <aquarius__> so I can't install -core-debug without upgrading -core, which means that a gdb backtrace won't be useful, correct?
[09:15] <RAOF> What version do you have?  I'll rustle up a link for you.
[09:16] <RAOF> aquarius__: Correct.  You need to have the -core-dbg version that corresponds to whatever is about to hang now :)
[09:16] <aquarius__> 2:1-10.0-0ubuntu3
[09:17] <aquarius__> and it's about to install 2:1-10.0.902-1ubuntu1
[09:17] <aquarius__> I only upgraded everything about a week ago! There have been nine hundred versions of X since? :)
[09:19] <RAOF> That's just one version out of date; the new one was uploaded yesterday.
[09:19] <aquarius__> :)
[09:19] <RAOF> Oh - what arch do you need?
[09:19] <aquarius__> uname -p says i686
[09:20] <davidcalle> kamstrup, hello. What can make a Lens do this: when it's launched at startup, it crashes on utf-8 strings ("ascii codec can't encode..."), but when it's launched during a session, it handles them well.
[09:20] <RAOF> aquarius__: http://launchpadlibrarian.net/67866223/xserver-xorg-core-dbg_1.10.0-0ubuntu3_i386.deb
[09:21] <aquarius__> (oh, and syndaemon is eating 100% CPU as well, again. Is that likely to be related?)
[09:21] <RAOF> aquarius__: I don't think so.
[09:21] <RAOF> Although it might make the deadlock more likely to happen.
[09:22] <aquarius__> ok. I'm happy to provide information about syndaemon as well if that's useful?
[09:22] <RAOF> Not for me, although the ubuntuone guys might be interested :)
[09:22] <aquarius__> ahem!
[09:22] <aquarius__> syndaemon. Not syncdaemon.
[09:22] <RAOF> Oh!
[09:22] <aquarius__> if it were syncdaemon I'd know who to talk to :)
[09:23] <magcius> RAOF, was "No.  There *is* a weird bug where one of compiz's X connections sits around waiting for input that never comes, though." addressed to me?
[09:24] <RAOF> magcius: Indeed it was.
[09:24] <magcius> Why would killing notify-osd fix it?
[09:24] <RAOF> aquarius__: is in such a state ;)
[09:24] <aquarius__> RAOF: that's why I thought it might be related; syndaemon is sort of an X thing, no?
[09:24] <magcius> RAOF, also, I'm running metacity and gnome-panel, not compiz.
[09:24] <RAOF> aquarius__: syndaemon is an X-ish thing, yeah.
[09:25] <RAOF> aquarius__: File a bug; Chase Douglas is super-smart and up with the whole X input stack - he's who you want to talk to there.
[09:25] <magcius> So I assume notify-osd froze, and it's not ACK-ing D-Bus notifications, which makes GTK+ freeze.
[09:25] <aquarius__> RAOF: OK, gdb into X says "Cannot access memory at address <blah> / <address> in __kernel_vsyscall ()". (I haven't made it restart yet.) Is that what you'd expect it to say at this point?
[09:26] <RAOF> aquarius__: Hm, no.
[09:26] <RAOF> aquarius__: You need to do  “sudo gdb Xorg $(pgrep X)”, due to the slightly crazy way we do things.
[09:26] <aquarius__> ah
[09:27] <RAOF>  /usr/bin/X is a little wrapper; Xorg is where the fun is.
[09:27] <aquarius__> ok, that makes sense. Now done that; X is still in __kernel_vsyscall
[09:27] <RAOF> Yeah; it'll be polling.
[09:27] <aquarius__> (but now I get much more sensible-looking output :))
[09:27] <RAOF> Well, it'll be select()ing
[09:27] <aquarius__> right, so now I should kill -9 compiz and start metacity, yes? And then if X dies, get a backtrace from gdb
[09:27] <aquarius__> ?
[09:28] <aquarius__> (I'm not good with this sort of debugging, so sorry you have to give me a remedial class in it :))
[09:28] <RAOF> First you probably want to ‘handle SIGPIPE nostop noprint’ in gdb, or you'll get a bunch of spurious SIGPIPEs.
[09:28] <aquarius__> done
[09:28] <RAOF> Then, yeah; kill compiz and start metacity.
[09:32] <aquarius> well, *that* was less than successful.
[09:32] <RAOF> Oh.
[09:32] <aquarius> RAOF, I killed compiz fine, and then on running "DISPLAY=:0 metacity --replace" in a VC...the machine hung.
[09:32] <RAOF> Um.  You weren't trying to gdb on the same machine as X was running on?
[09:33] <aquarius> I don't know whether the machine itself was locked up or whether just the screen wouldn't change.
[09:33] <magcius> RAOF, any other suggestions, or should I ping MacSlow?
[09:33] <magcius> (well, I just did)
[09:33] <aquarius> RAOF, I was.   So, what happened *there* was that gdb stopped X while it was handling the VT switch.
[09:33] <magcius> MacSlow, running gnome-panel and metacity
[09:34] <magcius> occasionally, gtk+ windows lock up
[09:34] <RAOF> aquarius: Leading to *hilarious* consequences!
[09:34] <magcius> pkill notify-osd
[09:34] <magcius> everything works
[09:34] <aquarius> RAOF, heh. :)
[09:34] <MacSlow> magcius, hm... that's new
[09:35] <RAOF> It is kinda possible to run gdb against X on the same machine, but it's not particularly reliable.
[09:35] <magcius> MacSlow, I'm running: xchat, gnome-terminal, banshee, emacs
[09:35] <magcius> also firefox
[09:35] <aquarius> RAOF, ah. So, then, what we're suggesting here is: someone else has to get you your backtrace :)
[09:35] <magcius> it seems to happen the most with banshee's track change notifications
[09:35] <MacSlow> magcius, do you have a ~/.cache/notify-osd.log handy somewhere?
[09:35] <magcius> but that's usually the notifications i get
[09:35] <RAOF> aquarius: Indeed :)
[09:36] <magcius> MacSlow, yes.
[09:36] <MacSlow> magcius, can you paste it somewhere?
[09:36] <magcius> MacSlow, all it has is the latest notification: [2011-04-12T03:59:08-00:00, notify-sharp ] Coastal Brake
[09:36] <magcius> by 'Tycho' from 'Coastal Brake'
[09:36] <magcius> could be ndesk-dbus or notify-sharp that's being dumb
[09:36] <MacSlow> magcius, hm... ok that's a dead end then...
[09:37] <aquarius> RAOF, thanks for the help thus far, though. Given that you know about the compiz problem, and I can't debug X dying without a second machine, is there anything else that I can provide you the next time this happens? Or should I just restart X, confident in the knowledge that you're working on it? :)
[09:37] <MacSlow> magcius, do you perhaps know any method to forcefully cause this lockup?
[09:37] <magcius> MacSlow, nope.
[09:38] <magcius> I'll try some more
[09:38] <magcius> but when it happens again, is there anything I should do?
[09:38] <MacSlow> magcius, that would be very helpful... otherwise it's very hard to guess what's going wrong.
[09:38] <RAOF> aquarius: I think you're off the hook :).  No further debugging questions, y'rhonour.
[09:38] <magcius> get a gdb backtrace and see what it's polling for?
[09:38] <aquarius> RAOF, sorry I can't be more helpful!
[09:38] <MacSlow> magcius, yes
[09:38] <zniavre> sorry to ask again but what can i do for this please ?  > http://i.imgur.com/kxkxz.png <
[09:38] <magcius> zniavre, looks like a driver bug
[09:39] <MacSlow> magcius, and try to save the ~/.cache/notify-osd.log as it gets overwritten when notify-osd is restarted
[09:39] <zniavre> ho ? im using nouveau
[09:39] <magcius> As I said, looks like a driver bug
[09:39] <zniavre> that s a good new
[09:40] <akshatj> zniavre, unity has many problems with nouveau for me
[09:40] <RAOF> zniavre: How new is your compiz?  I've had approximately that bug a couple of times over teh cycle; a new compiz fixed things.
[09:40] <zniavre> i experience this since yesterday update compiz/nouveau/unity
[09:41] <dbarth> rodrigo_: hey rodrigo, i've noticed this bug about accessible descriptions
[09:41] <dbarth> https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/726005
[09:41] <dbarth> is there something in the code that looks wrong?
[09:42] <rodrigo_> dbarth, looking
[09:42] <zniavre> RAOF,  i hav filled a bug report yesterday https://bugs.launchpad.net/ubuntu/+source/unity/+bug/757990
[09:42] <magcius> MacSlow, not *quite* sure how to do that considering anything gtk+-based dies, including gnome-terminal
[09:43] <magcius> and nvidia broke ttys :(
[09:43] <MacSlow> magcius, argl²
[09:43] <MacSlow> magcius, can you still ssh into that machine from elsewhere?
[09:43] <RAOF> zniavre: (Fortunately?) We're not supporting nouveau's 3D, and it's likely to be a driver bug…
[09:43] <magcius> does notify-osd log to stderr?
[09:43]  * RAOF updates his nouveau machine to check.
[09:44] <rodrigo_> dbarth, TheMuso should know better
[09:44] <magcius> I could do "/usr/libexec/notify-osd 2> ~/crashing.log" and let the system restart it when I pkill notify-osd
[09:44] <magcius> MacSlow, and no, no laptop nearby. This is my desktop.
[09:44] <rodrigo_> TheMuso, around?
[09:44] <zniavre> RAOF,  ok thank you answering  do i cancel my report  ?
[09:45] <RAOF> zniavre: Leave it there; we might get around to doing something about it.
[09:45] <RAOF> zniavre: And we'll *eventually* want to support nouveau's 3D
[09:45] <zniavre> \o/
[09:46] <MacSlow> magcius, well... if you start it from a shell/terminal (after killing the current one running) you could capture it's output to a file
[09:46] <magcius> MacSlow, right, does it log to stderr?
[09:47] <magcius> MacSlow, ok, I think I may have found something
[09:47] <magcius> loading icon 'notification-/home/jstpierre/.cache/media-art/album-d50f662d41e1699e07f0baefbc6fd145.jpg' caused error: 'Icon 'notification-/home/jstpierre/.cache/media-art/album-d50f662d41e1699e07f0baefbc6fd145.jpg' not present in theme'**
[09:48] <magcius> MacSlow, icon still displays fine though
[09:48] <magcius> so not sure if it's just a dumb warning
[09:48] <MacSlow> magcius, that looks nasty -> "notification-/"
[09:49] <magcius> DEBUG: [2011-04-12T04:48:46-00:00, notify-sharp, id:1, icon:/home/jstpierre/.cache/media-art/album-d50f662d41e1699e07f0baefbc6fd145.jpg]
[09:49] <MacSlow> trying to replace a normal (icon) file-name with symbolic one
[09:49] <magcius> looks like it's sending it across D-Bus fine
[09:49] <MacSlow> magcius, which icon-theme are you using?
[09:50] <magcius> Ubuntu-Mono-Dark
[09:50] <magcius> according to gnome-appearance-properties
[09:50] <MacSlow> magcius, this "notification-/" indicates that the symbolic icon-name-substitution is getting in the way
[09:51] <magcius> uh, OK
[09:51] <MacSlow> there's a workaround in place in notify-osd that I've never had time to solve properly
[09:52] <MacSlow> magcius, just can't say why it's triggered for a normal album-art icon/image
[09:52] <magcius> who is doing that
[09:53] <MacSlow> magcius, notify-osd
[09:53] <magcius> I mean the "notification-" prepending?
[09:53] <MacSlow> magcius, notfy-osd is doing that
[09:53] <magcius> OK
[09:54] <MacSlow> magcius, are you at home with compiling stuff yourself?
[09:54] <magcius> Of course.
[09:54] <MacSlow> magcius, if you want you could quickly compile notify-osd without that workaround
[09:54] <MacSlow> magcius, apt-get source notify-osd
[09:54] <magcius> MacSlow, https://code.launchpad.net/~jstpierre/notify-osd/365162 :D
[09:54] <magcius> I did that a loong time ago
[09:55] <MacSlow> magcius, notify-osd/src/bubble.c:122 set it to 0
[09:56] <MacSlow> magcius, recompile
[09:56] <magcius> OK
[09:56] <MacSlow> magcius, run the resulting notify-osd binary from that and see if that solves your issue
[09:56] <MacSlow> magcius, which I'm very certain it will
[09:57] <magcius> The image loads fine in the end.
[09:57] <magcius> It was just something I saw.
[09:57] <MacSlow> magcius, still I wish we could get rid of such workarounds to fix others issues :)
[09:58] <magcius> Technically, they shouldn't be using icon, but image_path instead, right?
[09:59] <magcius> Er, wait
[09:59] <magcius> the "icon" property doesn't exist?
[09:59]  * magcius looks at http://people.gnome.org/~mccann/docs/notification-spec/notification-spec-latest.html#icons-and-images
[10:00] <MacSlow> magcius, I need to switch back to unity... anything else is better handled via sending email
[10:01] <magcius> OK.
[10:01]  * MacSlow looks at all the unread email
[10:01] <MacSlow> *rolling.eyes*
[14:33] <om26er> good morning lamalex
[14:35] <lamalex> morning om26er
[14:35] <lamalex> morning cdbs,
[14:36] <om26er> lamalex, I am back to triage btw
[14:37] <kenvandine> tedg, uh oh... distro patching that dbusmenu branch from mterrry broke quicklists
[14:37] <kenvandine> tedg, at least for apps that don't have an app running associated with the desktop file
[14:38] <tedg> kenvandine, I'm on a call, but I'm surprised that happened... I didn't realize that stuff was using dbusmenu....
[14:38] <kenvandine> yup
[14:38] <kenvandine> dynamic quicklists
[14:38] <tedg> kenvandine, I'd be suspicious that was it.
[14:38] <kenvandine> i just verified, downgrading dbusmenu fixed it
[14:39] <tedg> kenvandine, You lie!  ;-)
[14:39] <kenvandine> perhaps the bug is really somewhere in unity :)
[14:39] <kenvandine> this is just uncovering it
[14:41] <kenvandine> tedg, ok... i take that back
[14:41] <kenvandine> i must be lying :)
[14:41]  * tedg dances the kenvandine is a lier dance ;-)
[14:41] <kenvandine> tedg, it worked twice in a row after downgrading
[14:41] <kenvandine> but now it failed again
[14:42] <kenvandine> must be racy
[14:53] <kvalo> kenvandine: hi. a quick question, any hope of gwibber ever supporting a push method for new messages?
[14:53] <kenvandine> kvalo, you mean like twitter live stream?
[14:54] <kvalo> kenvandine: something which doesn't poll :)
[14:54] <kenvandine> or real time feed, whatever they call it :)
[14:54] <kenvandine> kvalo, yes... for services that support it
[14:54] <kenvandine> and... only if i get to do the refactoring work i want to do
[14:54] <kvalo> kenvandine: cool, so there's hope! :)
[14:55] <kenvandine> indeed :)
[14:55] <kvalo> kenvandine: thanks
[14:55] <kenvandine> we'll be talking about that kind of stuff at UDS, so you should try to show up to show support :)
[14:55] <kenvandine> our current scheduling mechanism wouldn't really handle that kind of thing well
[15:00] <om26er> njpatel_, Hi! bug 734900 thoughts?
[15:05] <lamalex> om26er, just do an ayatana-design task
[15:05] <lamalex> normal design bug workflow
[15:05] <njpatel_> om26er, fixing today
[15:05] <lamalex> heh, oh ok or not
[15:05] <om26er> lamalex, ;)
[15:05] <om26er> njpatel_, thanks
[15:35] <nerochiaro> smspillaz|z: can you please ping me when you have a spare minute ?
[15:53] <lamalex> tedg, should i wishlist or wontfix thishttps://bugs.launchpad.net/unity/+bug/756434
[15:54] <lamalex> tedg, should i wishlist or wontfix this https://bugs.launchpad.net/unity/+bug/756434
[15:56] <tedg> lamalex, bug 756434 shoudl be wishlist -- but for indicator-datetime
[15:56] <tedg> Oh, those were the same :-)
[15:57] <lamalex> tedg, right
[15:57] <lamalex> i was just fixing the space, sorry :P
[15:57] <tedg> lamalex, I can't imagine a reason to really have that map in there -- it seems like eye candy to me.  But, it's definitely a feature request.
[15:58] <lamalex> yah
[15:58] <lamalex> it was definitely eye candy
[15:59] <lamalex> but it /was/ nice in gnome 2.x
[15:59] <lamalex> had your locations on it with daylight. i enjoyed it
[15:59] <lamalex> was helpful for day dreaming about the weather hawaii
[17:18] <kenvandine> cdbs, i see you noticed dynamic quicklists have stopped working
[17:18] <kenvandine> sort of
[17:18] <kenvandine> i've been trying to bi-sect that today... they worked last week
[17:18] <cdbs> kenvandine: :o
[17:18] <cdbs> kenvandine: so I'm not alone
[17:18] <kenvandine> it works like 1 out of 10 tries :)
[17:18] <cdbs> kenvandine: In my case they worked a few hours ago
[17:18] <kenvandine> so not completely broken, must be race condition of some sort
[17:19] <cdbs> kenvandine: and now they won't work, I tried around 15-20 times
[17:19] <didrocks> I didn't change the code there in unity
[17:21] <jcastro> didrocks: any idea what's up here: https://bugs.launchpad.net/unity/+bug/692462/
[17:22] <kenvandine> didrocks, i ruled out the bamf and dbusmenu updates
[17:22] <jcastro> didrocks: I can reproduce on a clean install, I just don't know where to reopen, bamf or unity.
[17:23] <kenvandine> didrocks, so i am guessing either libunity or unity
[17:23] <kenvandine> but leaning towards unity
[17:23] <kenvandine> i tried the 3.6.8 gir with libunity3 and it fails too
[17:24] <didrocks> jcastro: DBO revert a part of the merge for latest release
[17:24] <kenvandine> but that might not be a great test
[17:24] <kenvandine> since unity is using libunity4
[17:24] <didrocks> jcastro: it was wrong IIRC, better to check with him
[17:24] <jcastro> didrocks: ok so is it a bamf problem or a unity problem?
[17:24] <jcastro> ok
[17:24] <didrocks> kenvandine: libunity didn't get any update, bamf update isn't linked to that part
[17:24] <jcastro> DBO: yo
[17:24] <didrocks> jcastro: bamf
[17:24] <kenvandine> didrocks, there was the API change last week...
[17:25] <didrocks> kenvandine: yeah, but that happened since yesterday, isn't it?
[17:25] <DBO> jcastro, what?
[17:25] <kenvandine> didrocks, yeah, just trying to narrow down the field
[17:25] <kenvandine> didrocks, i am not sure it worked consistently yesterday
[17:25] <kenvandine> i know it worked consistently last week
[17:25] <jcastro> DBO: https://bugs.launchpad.net/unity/+bug/692462/ this isn't Fix Released anymore
[17:25] <kenvandine> now it works rarely
[17:25] <kenvandine> fails in both vala and python for sure
[17:25] <DBO> jcastro, yeah I need to speak with trevino
[17:25] <kenvandine> so not pygi
[17:25] <jcastro> DBO: this is related: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/744972
[17:25] <DBO> his work is crashing
[17:25] <jcastro> ah ok
[17:26] <DBO> i am about to revert the whole shooting match
[17:26] <jcastro> thanks for the update
[17:26]  * didrocks is happy to not merging that himself and let DBO handle it :-)
[17:26] <DBO> didrocks, dont touch bamf right now
[17:26] <didrocks> DBO: oh, I don't! :-)
[17:27] <DBO> jcastro, if you can get me in touch with him
[17:27] <DBO> that would be good
[17:27] <didrocks> that's exactly why I told jcastro the other day I didn't want to touch this merge :-)
[17:27] <jcastro> I just panged him on irc
[17:34] <jono> are you folks aware of a bug with multiple icons on the Launcher?
[17:35] <kenvandine> didrocks, i am suspicious of rev 1105 of unity
[17:35]  * DBO rips jonos head off
[17:35] <jono> for the same app, I mean
[17:35] <kenvandine> "merge neils branch of epic win"
[17:35] <jono> DBO, :-)
[17:35] <didrocks> kenvandine: it's the one merging the urgent icons new API and removing the other one
[17:35] <DBO> kenvandine, neil needs to learn to name his branches better
[17:35] <didrocks> jono: happens when bamfdaemon is restarting
[17:36] <kenvandine> -  DbusmenuMenuitem* item   = NULL;
[17:36] <jono> didrocks, ahhh
[17:36] <kenvandine> +  QuicklistMenuItem* menu_item = NULL;
[17:36] <kenvandine> +  DbusmenuMenuitem*  item   = NULL;
[17:36] <kenvandine> it seems to be touching that area
[17:36] <didrocks> kenvandine: argh
[17:36] <didrocks> let me kill Neil to remove my work :)
[17:36] <kenvandine> hehe
[17:38] <kenvandine> then
[17:38] <kenvandine> +  menu_item = GetNthItems (index);
[17:38] <kenvandine> +  if (!menu_item)
[17:38] <kenvandine> +    return false;
[17:38] <kenvandine> perhaps dbusmenu isn't finished setting up when he does that check?
[17:38]  * kenvandine really has no clue, just random guesses here
[17:38] <kenvandine> but this looks suspicious
[17:38]  * kenvandine goes to lunch :)
[17:39] <didrocks> kenvandine: probably, and so we are back to first point, with the race (the one mterry fixed)
[17:45] <DBO> jono, if you have a reliable method of reproducing the bamf crash
[17:45] <DBO> please tell me
[17:46] <jono> DBO, I didn't see a bamf crash, I started Gwibber and saw three icons :-)
[17:46] <DBO> jono, what else do you have running?
[17:46] <DBO> what favorites do you have
[17:47] <jono> DBO, in my launcher?
[17:47] <DBO> yes
[17:48] <jono> Nautilus, Firefox, Terminal, Tomboy, USC, XChat-GNOME, GTG, Thunderbird, GTK-Record-My-Desktop, GEdit, Skype, Gimp, Ubuntu One Control Panel, and I have Evolution open (three icons) and Gwibber (three icons)
[17:48] <jono> DBO, ^
[17:49] <jono> I have also seen multiple banshee icons before
[17:49] <DBO> whcih ones have you pinned?
[17:49] <jono> it seems to be apps started from the indicators that have muiltiple icons
[17:49] <jono> all those apps are ones I have pinned to my launcher
[17:50] <jono> I think it is something to do with starting apps from indicators
[17:50] <jono> I haven't noticed this issue with other apps
[17:50] <DBO> you dont have any non-pinned apps running?
[17:50] <jono> DBO, I do, Gedit, GTG, XChat, Firefox
[17:50] <jono> oh hang on
[17:50] <jono> no
[17:50] <jono> non-pinned apps, no
[17:50] <jono> well
[17:51] <jono> Evo and Gwibber are not pinned, I start them from the indicators, and I have them running
[17:53] <didrocks> lamalex: set-lp-dup is what you want
[17:53] <seb128> DBO, the comments suggest quite some users got it while using file selector dialog
[17:53] <DBO> seb128, k
[17:54] <DBO> I need all of these dupes traced
[17:54] <DBO> can i get some retracing done?
[17:57] <DBO> why the shit cant I get bamf to crash
[17:57] <seb128> DBO, the retracers are working
[17:57] <DBO> if I fail to fix this bug for a 3rd time I think seb128 will just kill me
[17:57] <seb128> not sure what you mean
[17:58] <DBO> maybe I looked at the wrong dupe
[17:58] <seb128> the thing is that they just clean and close the new bugs since they have the same stacktrace
[17:58] <seb128> that's the best way to avoid making public private infos
[17:58] <seb128> the duplicates are cleaned and turned public
[17:59] <DBO> with different strings
[17:59] <DBO> which I need to see
[17:59] <seb128> no luck for you then
[17:59] <DBO> :(
[17:59] <DBO> thats crap
[18:00] <seb128> well jono had the issue
[18:01] <seb128> he probably has the .crash locally and can give you some infos
[18:01] <jono> bamf has crashed for me
[18:01] <jono> I saw an error dialog
[18:02] <jono> seb128, where would I find a .crash ?
[18:02] <seb128> jono, in /var/crash
[18:02] <jono> _usr_lib_bamf_bamfdaemon.1000.crash
[18:02] <jono> I have that
[18:02] <seb128> right
[18:02] <seb128> jono, so can you do that
[18:02] <seb128> install bamfdaemon-dbgsym
[18:02] <jono> seb128, what do you want me to do?
[18:02] <seb128> then double click on that .crash in nautilus
[18:03] <seb128> or use ubuntu-bug -c on it
[18:03] <jono> ok, one sec
[18:03] <jono> E: Unable to locate package bamfdaemon-dbgsym
[18:03] <jono> seb128, ^
[18:04] <seb128> jono, what arch do you use?
[18:04] <jono> seb128, x86
[18:04] <seb128> how come people there don't have a ddeb source configured ;-)
[18:05] <seb128> jono, so either configure a ddeb apt source as described on https://wiki.ubuntu.com/DebuggingProgramCrash or wget http://ddebs.ubuntu.com/pool/main/b/bamf/bamfdaemon-dbgsym_0.2.86-0ubuntu1_i386.ddeb and dpkg -i it
[18:05] <seb128> jono, ddeb source is basically adding "deb http://ddebs.ubuntu.com natty main restricted universe multiverse" to your sources.list
[18:06] <jono> seb128, ok, I installed it and double-clicked on it in FF and now it is filing a bug
[18:07] <seb128> jono, thanks, can you make the bug public and give the number when it's filed? or if you don't want to make it public subscribe me to it
[18:07] <seb128> jono, bamf shouldn't have any private data out of the name of running applications if you are fine making those infos public
[18:08] <jono> np, one sec
[18:09] <jono> seb128, so it is registering "bamfdaemon crashed with SIGABRT in dbus_g_connection_register_g_object()" of which there are other bugs and dupes
[18:09] <jono> should I file it anyway
[18:09] <jono> ?
[18:09] <seb128> jono, yes
[18:09] <seb128> jono, DBO needs info from a new bug
[18:10] <jono> seb128, DBO https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/758965
[18:10] <seb128> the other ones got cleaned by the retracers
[18:10] <didrocks> seb128: can you stop the retracer from cleaning this one?
[18:10] <seb128> DBO, https://launchpadlibrarian.net/69148113/Stacktrace.txt
[18:10] <seb128> didrocks, we can once, but it will add the first one it retracers to the stacktraces db and dup the next ones from it
[18:10] <DBO> thank you seb128
[18:10] <seb128> DBO, thanks jono
[18:11] <DBO> thanks jono
[18:11] <jono> np
[18:11] <jono> let me know if there is anything I else I can do to help
[18:11] <seb128> #10 0x080561bc in open_office_window_setup_timer (args=0x90f4198) at bamf-matcher.c:1347
[18:11] <DBO> yes its always open office
[18:11] <seb128> DBO, other bugs suggested they were using libreoffice to open a document when they got it
[18:12] <seb128> DBO: you got the gdb crashdump on the bug as well if you have an i386 install and want to play withit
[18:13] <DBO> amd64
[18:13] <DBO> but thank you
[18:17] <DBO> seb128, can you confirm this
[18:17] <DBO> open libre writer, and then libre calc
[18:17] <DBO> then open the FIle Open from writer
[18:17] <DBO> does that crash it?
[18:19] <seb128> DBO, just having one librewriter opening the fileselector and closing it seems enough
[18:20] <seb128> or rather just opening the fileselector seems enough
[18:20] <DBO> for me i need both
[18:20] <DBO> either way this gives me what I need
[18:21] <DBO> and I can confirm the duplication
[18:22] <seb128> DBO, it's not specific to libreoffice by reading the comments though, this stacktrace seemed specific to it
[18:22] <DBO> every stacktrace I have seen has had the open office delay timer in it
[18:22] <DBO> sometimes the apport window pops late
[18:23] <seb128> ok
[18:26] <jcastro> kamstrup: any idea what could be going on here? our lens stopped working on login: https://bugs.launchpad.net/askubuntu-lens/+bug/758839
[18:28] <kamstrup> jcastro: anything in .xsession-errors?
[18:28] <seb128> DBO, ok, can you do that: wget https://launchpadlibrarian.net/69149337/_usr_lib_bamf_bamfdaemon.1000.crash, apport-unpack _usr_lib_bamf_bamfdaemon.1000.crash dir; cd dir; and use gdb on the crashdump there?
[18:28] <seb128> DBO, it's the crash from skaet, she just added it and she said she didn't use libreoffice
[18:28] <seb128> DBO, so might be worth checking the stacktrace from this one
[18:28] <DBO> where is the trace?
[18:29] <seb128> DBO, I just copied the commands for you to use gdb on it
[18:29] <seb128> DBO: then type "bt"
[18:29] <DBO> yeah, thanks :)
[18:29] <seb128> DBO, it's not retraced but that way you can get debug infos locally
[18:30] <seb128> DBO, can you let me know if the stacktrace is a libreoffice one as well or if it's a different case. skaet think she didn't use libreoffice
[18:30] <seb128> DBO: quite some of the duplicates suggest it happen with firefox in some cases as well
[18:31] <seb128> oh it does
[18:31] <seb128> DBO, opening a fileselector in firefox crash bamf here
[18:31] <DBO> seb128, confirmed
[18:31] <seb128> DBO, ok, so I think you got what you need
[18:31] <seb128> DBO, happy debugging
[18:32] <DBO> yeah
[18:32] <DBO> thanks
[18:37] <seb128> DBO, r-t is asking when you think you can get a fix? they would like to get it fixed in beta2 if possible seeing the number of users running into it and the easy way to trigger it
[18:37] <DBO> seb128, today
[18:38] <seb128> DBO, ok, please let me or didrocks know when you have a fix to try or that we can backport to natty
[18:38] <seb128> didrocks, ^
[18:38] <didrocks> seb128: yeah, I'll upload right away in case of a respin
[18:38] <didrocks> DBO: ^
[18:39] <seb128> didrocks, thanks
[18:39] <seb128> didrocks, upload right away in any case, I told skaet we would get it in the queue for them once it's ready
[18:39] <seb128> didrocks, then they can do what they judge right
[20:36] <kenvandine> cdbs, i have a fix for the broken quicklists
[20:36] <kenvandine> https://code.launchpad.net/~ken-vandine/unity/make-quicklists-work-again/+merge/57386
[20:37] <kenvandine> it looks like mterry's previous fix got reverted accidentally
[20:39] <cdbs> kenvandine: :o
[20:40] <cdbs> kenvandine: nice catch
[20:40]  * cdbs 'll test it
[21:22] <cdbs> kenvandine: ping
[21:22] <kenvandine> cdbs, pong
[21:22] <cdbs> kenvandine: the fix worked, but a new problem, if the dbusmenu specified contains a hidden menuitem, then unity crashes
[21:22]  * cdbs reports
[21:22] <kenvandine> ugh
[21:22] <kenvandine> thx
[22:03] <lamalex> DBO, what do we know about the ivisible windows bug?
[22:04] <lamalex> i have a guy who says he can trigger it with the grid plugin
[22:04] <DBO> it should be mostly resolved
[22:06] <lamalex> DBO, as of when
[22:06] <lamalex> this was filed on the 10th
[22:06] <DBO> link?
[22:07] <lamalex> https://bugs.launchpad.net/unity/+bug/756765
[22:07] <DBO> that is the grid clipping bug
[22:07] <DBO> its fixed on the 11th
[22:11] <lamalex> k
[22:11] <lamalex> thanks
[22:13] <LLStarks> didrocks wanted this but whatever
[22:13] <LLStarks> bug 759198
[22:13] <LLStarks> ubot fails
[22:13] <LLStarks> https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/759198
[23:13] <Omega> The lockscreen is ugly.
[23:14] <Omega> It's probably what I hate most about my Ubuntu experience.
[23:19] <Daekdroom> bamfdaemon just crashed out of the blur.
[23:19] <Daekdroom> But instead of getting the backtrace I closed the window unconsciously, heh.
[23:23] <Omega> I just got a GPU lockup and apport crashing while submitting.
[23:36] <sergio__> I'm wondering if this is worth submitting a bug to Ayatana. The launcher in unity recognizes input with a control key as a garabge character. For example, typing Ctrl+V or Ctrl+A into the launcher results in garbage text being shown.
[23:39] <sergio__> This is in the natty beta btw
[23:42] <Omega> sergio__: submit the bug to unity
[23:42] <Omega> (check if it's submitted)
[23:42] <Omega> I'll confirm it
[23:43] <sergio__> Omega, i havent seen one, so i was just wondering if it seemed bug worthy
[23:44] <delac> affects mee too. I would say it's quite worth a bug report
[23:44] <delac> I mean, I really would like to be able to paste into the thing
[23:53] <Omega> Something actually shows up when you search for .,,ctrl+/
[23:53] <sergio__> not for me
[23:53] <sergio__> ctrl+i gives a big space
[23:54] <sergio__> ctrl+a does select all
[23:54] <sergio__> ctrl+j is little space?
[23:55] <sergio__> as wel as ctrl m
[23:56] <Omega> And we have a crash!
[23:59] <sergio__> go figure any combination of ctrl and , . ; ' works fine