/srv/irclogs.ubuntu.com/2009/04/28/#ubuntu-desktop.txt

pace_t_zulucan someone help me find the code responsible for changing screen resolution?04:42
=== racarr_ is now known as racarr
=== pace_t_zulu_ is now known as pace_t_zulu
pittiGood morning07:09
pittibryce: can we even be sure that the bug is still the same with 2.6.30 and new libdrm?07:11
pittibryce: when I wanted to test the freezes I get on the 945, these new packages change behaviour completely07:11
asachi07:20
pittihey asac07:25
* pitti hugs seb12808:30
* seb128 hugs pitti08:30
seb128how are you today?08:30
robert_ancellseb128: pitti: do you guys have any ideas about bug 322714 and bug 328885.  There seems to be a lot of vague dpkg type bugs in avahi08:33
ubottuLaunchpad bug 322714 in avahi "package libavahi-common3 0.6.22-2ubuntu4 failed to install/upgrade: " [Undecided,New] https://launchpad.net/bugs/32271408:33
pittiseb128: pretty good, and you?08:33
ubottuLaunchpad bug 328885 in avahi "package libavahi-qt3-1 0.6.23-2ubuntu2.1 failed to install/upgrade: package libavahi-qt3-1 is already installed and configured" [Undecided,Incomplete] https://launchpad.net/bugs/32888508:33
pittihey robert_ancell08:33
seb128hey robert_ancell08:33
robert_ancellgood morning guys08:33
seb128looking08:33
seb128pitti: pretty good thanks!08:33
seb128those seems bugs for mvo08:35
seb128robert_ancell: the first one seems a local corruption rather than a bug08:35
robert_ancellseb128: what is the best thing to do with them?  i.e. how should they be marked (I can't see anything avahi specific about them)08:36
seb128that's a very good question08:36
seb128I tend to close them or switch them to questions08:36
seb128which is not really "right" and mvo will not agree with me there08:36
seb128I tried to argue for getting an "upgrade issues" components08:37
seb128but other people didn't like the idea08:37
robert_ancellI want to assign them to "dkpg" or something08:37
seb128other people being mvo and pitti I think ;-)08:37
seb128yeah, you can do that too08:37
robert_ancell(but that feels like passing the buck.  A bit like assigning to the great black hole of compiz)08:38
robert_ancellso, do you close as "invalid"?08:38
seb128convert it to a question saying that's a local issue and not a software bug08:38
seb128that's what I do usually08:39
seb128or invalid08:39
mvorobert_ancell: I analyized a bunch of them08:39
mvothe one: 32271408:39
seb128question let the possibility that answer tracker guys will give advices to the guy on how to sort the issue08:39
mvodpkg complains that its missing a final newline, so I usually ask for the file08:39
mvoand typically it contains either garbage or a bit flip error08:39
robert_ancellmvo: hey08:40
* pitti wishes it was easier to see the actual problem in the plethora of logs08:40
mvorobert_ancell: hi08:40
mvopitti: good point08:40
pittirobert_ancell: I'd set 322714 to incomplete, asking for an fs check and attaching the .list file in question (sounds like corrupted fs or full disk to me)08:41
pittiseb128: I still stand to this opinion08:41
pittigenerating large amounts of bug spam and then directing it into a black hole where nobody looks doesn't help anyone08:41
seb128pitti: which one? not having an upgrade issues component?08:41
seb128pitti: because that one is clearly an avahi bug? *g*08:42
pittieither we make those reports better, or we stop collecting them08:42
mvoit should more be a package install/upgrade component08:42
seb128stop collection them08:42
robert_ancellok, but when you get the .list file back what can we do with it?08:42
seb128I'm that near > < of adding a piece of code which close all of those on GNOME packages08:42
pittirobert_ancell: see if it's obviously broken/truncated08:42
seb128I've enough of getting 95% of useless bugs assigned on the wrong component08:43
pittiseb128: I think ignoring/not collecting them is a valid option08:43
mvorobert_ancell: it should contain just file names, it will probably contain a bunch of garbage in between. clear sign of either filesystem correuption, memory corruption or (heaven forbit) a bug in dpkg08:43
robert_ancellpitti: and if it is, all we can say is your system is corrupted, please delete and reinstall that package?08:43
pittirobert_ancell: I usually ask people to start the rescue system from grub and then start fsck08:43
seb128reinstalling the package will not solve the corruption issue08:43
mvoI think not collecting them is not a good option08:43
pittimvo: we shouldn't ask people to file those reports if we are just going to ignore them08:44
seb128we already had this discussion, we will just never agree08:44
pittiit's raising false expectations and just leads to frustrations like "ubuntu bug reports are never looked at"08:44
robert_ancellI feel if I was sending in the report a link to a "fixes for dpkg issues" wiki page would make me happy08:44
mvoI don't want to ignore them either, I do check a lot of them and act.  half of them a bad. but the other half is not08:44
seb128what can we do to reduce this bad half to be less than that?08:45
pittiI'd like to see some more specific data collection from them, so that we can sanely auto-duplicate them08:45
mvorobert_ancell: there is a fsck and fix broken package option in friendly-recover (the menu in the rescue option in grub)08:45
pittiand then just look at the ones which have several dupes (the real ones)08:45
seb128pitti: it's hard to autoduplicate random corruption08:45
pittiseb128: right, those fall into the "ignore because of missing duplicates" part08:45
seb128robert_ancell has a good point, we should have a stock reply and wiki page about corruption08:45
pittibut if a package's postinst fails with exit status 99 for 50 people, that's something worth looking at08:45
robert_ancellmvo: I haven't been in grub for a while now it seems.  Is there a user-friendly wiki page about how to use it?08:46
mvoI'm fine with collecting them into a special category as long as we keep collecting them08:46
mvorobert_ancell: I don't iknow (I think its not)08:46
seb128pitti: when you know what status nn means, 90% of the time it's something crashing but you don't know what, though mvo probably fixed that one now08:46
mvoI mean, it sounds silly to me that we collect bugs that there are typos in the help widnow of synaptic, but we ignore errors that make package installation impossible at the users machine and say this is not a bug08:46
seb128ie we get lot of random issues being scrollkeeper-update crashing08:46
pittiseb128: but if it affects 50 people in our testing community, it's _still_ worth looking at it surely? (even if it is mistitled/misassigned)08:47
mvoit will attach the dmesg logs now08:47
seb128mvo: but it's not a bug, it's an installation issue08:47
mvoright, but it still deserves attention, no?08:47
mvoand often its bugs08:47
seb128we already had this discussion08:47
seb128I agree on that08:47
seb128I just don't think forcing me to keep those bugs on my component work08:48
mvothats ok08:48
seb128I just close them now because you don't force things over people when that's not something they are responsive for there08:48
pittino clue about 328885, this looks indeed like a weird apt/debconf issue08:48
seb128ie I've no clue what to do about dpkg index corruptions08:48
mvoso what should we do a) have a discussion (with more people) at uds again b) discuss on the ML c) just move them all to a new category?08:48
seb128and I don't care enough to keep those on my components08:48
seb128that would work for me08:49
pittiseb128: those aren't really the ones worth looking at indeed, which is why I'm eager to get more specific data into the bug reports08:49
seb128but you and pitti already expressed that you are against reassigning those to an "upgrade issue" place08:49
mvoyeah, 328885 is one of the useless ones :/08:49
seb128which means you force them at the wrong place where it will angry the maintainer only and not being worked anyway08:49
pittiseb128: I didn't say _re_assigning is a bad thing (although I'd prefer "invalid")08:50
pittiseb128: I'm just against reporting them all against a "package failures" project initially08:50
seb128pitti: where do we reassign those bugs? ie the avahi one08:50
pittisince that will just be one honking big mess nobody ever looks at08:50
pittiseb128: perhaps we misunderstood each other then08:50
seb128and why wouldn't we have some bugsquad ressource dedicated to triage that component ?08:50
pitti^ no reason not to, we just don't have it08:51
seb128you seem to have the illusion that people actually triage those when they are on random components08:51
seb128looking at desktop packages bug triagers just ignore those08:51
seb128because they don't know what to do08:51
pittiwell, I triage them on my pacakges08:51
pittibut I don't think that everyone does, and that's fine08:52
pittiseb128: what are you trying to convince me about?08:52
seb128pitti: that letting them assigned to random component is not efficient08:52
pitti(and no, I don't think we can tell the community "please go triage those 20.000 bugs against "install-failures", that won't work)08:52
seb128and that we should have an "upgrade issue" component08:52
pittiseb128: as I said, I can live with _re_assigning08:53
pittijust not with apport reporting them all against that component initially08:53
seb128ok, we started wrongly08:53
seb128let's restate what the problem is and what we need to do08:53
pittiif you look at a bug, say "oh crap, NFC", and reassign, that's fine08:53
pittibut then you looked at it and determined that you didn't see that issue 30 times already, and it's rarian which segfaults for half of the people08:54
seb128- we need an easy way to move the random corruption bugs out of the way08:54
pitti"invalid"?08:54
pitti(or "wontfix")08:54
robert_ancellre-assigning would make me happy as long as I could attach some sort of clue to the reporter on what they should do08:54
pittireassigning to a garbage dump is not ideal, but WFM, too08:54
seb128ok, so course of action08:54
seb128- get a stock reply and wiki page for corruption cases08:55
pitti+108:55
seb128and use those to close those bugs08:55
robert_ancell+108:55
didrocksseems a good way to track them (hello o/)08:55
seb128- improve the information collecting process and auto-duplication08:55
seb128can we automatically detect and tag in a special file conflicts?08:56
seb128can we automatically detect and tag in a special way file conflicts?08:56
seb128those are usually valid and useful bugs08:56
seb128mvo: ^08:56
pittiright, and they sound like something we should be able to detect automatically08:56
mvoI think we can detect it in the error message08:56
pittialso, I'd really like to avoid filing a package install bug if something in postinst segfaulted, since that should rather create a proper .crash file08:57
mvomaitnainer script failures is something we can probably detect relatively easily as well08:57
seb128where do we keep note of those action items?08:57
mvothat would mean to enable apport again for all upgrades (stable->stable too)?08:57
seb128ok, so let me take notes08:58
* pitti edits Bugs/Responses08:58
seb128mvo, pitti, robert_ancell: you agree with closing corruption bugs are invalid?08:58
pittiseb128: fine for me08:58
seb128are -> as08:59
mvoI'm still not comfortable with it, those might be dpkg errors (rare ones). but yeah, its ok with me08:59
seb128mvo: other option is to get a "upgrade issues" component08:59
asacwhat are "corruption" bugs? bad backtraces?08:59
seb128and reassign those there08:59
robert_ancellseb128: yes, as long as users get some info on how to save their system (i.e. don't think we're telling them it's not a problem)08:59
seb128asac: no, dpkg status corrupted for example08:59
asacoh. yeah08:59
seb128asac: or weird dpkg errors about new lines, or parsing issues08:59
mvoseb128: lets call it pkg failures or something, its not limited to upgrades IME08:59
seb128mvo: works for me09:00
asacseb128: do we have webkit ephy somewhere?09:01
asac(recent)09:01
seb128mvo: do you want a bug about the "would be nice to autotag file conflicts"?09:01
seb128asac: no but I think there is a ppa and the packaging is in debian pkg-gnome svn09:02
YokoZarmvo: I've been looking through the code of gnome-app-install and I have a design for how I'd like to extend it to support removing Wine applications.  Mind if I run it by you?09:02
mvoseb128: yes please09:02
YokoZarAlso good evening ;)09:02
YokoZarOr morning ;)09:02
asacseb128: ok. i think i am member of the webkit team in launchpad ... let me check what those folks are doing actually09:03
mvoYokoZar: good evening09:03
seb128mvo: where should I open this bug?09:03
seb128mvo: apt?09:03
mvoseb128: yes09:04
pittiseb128, mvo, robert_ancell: first cut at a stock response: https://wiki.ubuntu.com/Bugs/Responses#Package%20installation%20failure09:05
seb128pitti: looks a good start to me thanks09:06
robert_ancellpitti looks good09:06
brycepitti: I've tested with both 2.6.28 and 2.6.30 and have not noticed a difference in behavior09:07
pittibryce: ok, good09:08
robert_ancellhere's another question for everyone:  Bug 361622 requests that avahi provide a firewall rule - this seems crazy to me, if anything the firewall should have a default rule for avahi.  Do others agree?09:10
ubottuLaunchpad bug 361622 in avahi "Add application rules for the ufw firewall " [Undecided,New] https://launchpad.net/bugs/36162209:10
seb128mvo: bug #36843509:13
ubottuLaunchpad bug 368435 in apt "could tag file conflicts installation issues" [Undecided,New] https://launchpad.net/bugs/36843509:13
mvothanks seb12809:13
seb128mvo: thank *you* and sorry for ranting again there09:14
seb128mvo: good that we are moving in a way where everybody is happy about the change though09:14
mvoseb128: yeah09:14
didrocksrobert_ancell: you can provide in application packages ufw rules, which are activated or not considering the local policy. So, it doesn't sound too crazy for me :-)09:15
robert_ancelldidrocks: thanks, not very familiar with ufw.  Will confirm it then09:15
seb128robert_ancell: talk to jdstrand on IRC when he's around09:16
seb128robert_ancell: I think the idea is that packages are shipping their firewall rules, ie when you install avahi that's to get it used and the firewall rule to allow that would be there09:16
didrocksseb128: exactly. I can handle it. I did for a bunch of packages when jdstrand asked some help for intrepid09:17
robert_ancellcool, thanks guys09:17
didrocksseb128: FYI, the desktop team presentation tomorrow at OpenWeek will be largely inspired by your last talk :)09:18
seb128didrocks: good ;-)09:18
seb128robert_ancell: you got a reply on this rhythmbox codec bug btw09:19
seb128robert_ancell: I'm looking the glade upgrade bug09:21
seb128robert_ancell: no need to nominate bugs for karmic that early in the cycle09:21
robert_ancellseb128: ok, wasn't sure when to do that.09:21
seb128you also want to add a debdiff for the update to the bug09:21
robert_ancellseb128: excellent, the rb response reproduces for me09:21
seb128gzipped if required09:21
robert_ancellseb128: I couldn't remember how to make the debdiff...09:22
seb128it makes review easier since the diff is on the bug09:22
seb128debdiff *.dsc09:22
robert_ancellthanks09:22
seb128in the dir where you have the jaunty version and your update09:22
robert_ancellseb128: there now09:24
seb128robert_ancell: thanks09:24
robert_ancellseb128: should have gzipped it as you said though...09:25
seb128robert_ancell: do you already have enough work for tomorrow?09:25
robert_ancellseb128: I have various stuff to do.  If there's something you want me to look at pass it over09:26
seb128robert_ancell: bug #368252 assigned to you09:26
robert_ancell(I've never found nothing to do :) )09:26
ubottuLaunchpad bug 368252 in totem "Totem firefox plugin can't launch apple HD trailers" [Low,New] https://launchpad.net/bugs/36825209:26
seb128robert_ancell: that seems another totem-pl-parser issue09:26
seb128not a high priority issue, but in case you get bored ;-)09:27
seb128the user claims that was working in intrepid09:27
=== andreasn_ is now known as andreasn
didrocksseb128: do you me to rename jaunty/karmic in my waiting to be sponsored bug (as karmic repos are opened now)?09:40
seb128didrocks: feel free to do that09:40
seb128didrocks: I'm still on jaunty and trying to deal with the current bug flood so those uploads will wait09:41
didrocksseb128: oki, if I can do anything to help, do not hesitate (even if I'm quite busy now until middle of may ;))09:41
pittijust in case you missed it in -devel: karmic is open, go wild!09:41
seb128pitti: apparently we have some crack addicts, didrocks is already on it ;-)09:42
didrocksseb128: :-)09:42
pittihehe09:42
pittigo didrocks!09:42
* seb128 stills dealing with jaunty bugs09:42
didrockspitti: just began ^^09:42
pittiplease everyone remember to sub to karmic-changes@09:43
didrockspitti: already done this morning :D09:43
* pitti uploads new hal and dk-power09:43
Tm_Tpitti: so you can spam our mailboxes down?09:44
pittimuhaha09:44
Tm_T"busted"09:44
* didrocks is setting up a filter right now :)09:44
Tm_TI revealed your evil plan!09:44
pittiI have about 20 "fix committed" bugs, I want to clean my +assignedbugs list09:44
* seb128 is always impressed by how early people switch to new crack ;-)09:45
pittiseb128: I wonder if you would mind if I'd upload the new gnome-power-manager with DK-power support09:45
seb128I must be the only of to still have a stack of jaunty bugs to get fixed09:45
seb128pitti: not at all, as said I'm still stucked in jaunty mode there ;-)09:45
seb128we have some evolution crasher issues09:46
seb128and lot of desktop bugs coming09:46
pittiseb128: please don't put too much effort into jaunty SRUs09:46
seb128feel free to upload anything you want to karmic09:46
seb128pitti: we got at least 15 people complaining about evolution calendar hanging evo since jaunty09:46
pittiyeah, I heared about that09:46
pittithat's indeed an important thing09:46
seb128pitti: I want to get that fixed, then I can switch to karmic09:46
mvopitti: could you nag about about a sru approval for update-manager again? sorry that its such a sru intensive beast09:46
pittiseb128: I just don't think we should do a lot of work wrt. uploading all the point releases unless they fix something truly critical09:47
pittimvo: of course09:47
seb128pitti: I'm almost done with srus on my list, I don't intend to spend much time on jaunty09:47
mvothanks09:47
seb128pitti: right09:47
* pitti hugs seb128, seems we're on the same page09:47
seb128pitti: karmic will be busy enough09:47
* seb128 hugs pitti09:47
didrocksmvo: I add a karmic task to bug #361053 too09:48
ubottuLaunchpad bug 361053 in gnome-terminal "Please, sponsor gnome-terminal 2.26.1 to jaunty" [Wishlist,In progress] https://launchpad.net/bugs/36105309:48
mvodidrocks: ok09:49
seb128didrocks: don't09:49
didrocksoupsss09:49
seb128jaunty-updates are pocket copied to karmic09:49
didrocksoh, didn't know that :/ It's done until which milestone?09:50
seb128it's done when the versions are identic09:50
seb128in jaunty and karmic that is09:51
seb128it makes sense to have only one upload09:51
pittiyes, I regularly do that with SRUs09:51
didrocksok, sorry, I can't revert the release nomination. I will just put a comment, so...09:51
seb128didrocks: that's ok, it's a detail09:52
robert_ancellmvo: here's one you might have an idea about: bug 29148409:52
ubottuLaunchpad bug 291484 in avahi "package libavahi-common3 0.6.23-2ubuntu2 failed to install/upgrade: " [Undecided,Incomplete] https://launchpad.net/bugs/29148409:52
seb128didrocks: just no need to create paper work where it's not required09:52
didrocksseb128: good to know, though :)09:52
robert_ancellsee you all tomorrow10:09
seb128robert_ancell: good evening, see you tomorrow10:10
pittididrocks: your gnome-terminal upload refers to LP: #572414, that doesn't exist10:59
didrockspitti: let me check if I just mixed with the corresponding GNOME bug11:00
* didrocks is confused :/11:00
didrockspitti: it's bug #33129511:00
ubottuLaunchpad bug 331295 in gnome-terminal "'Close this terminal' warning labels button as 'Close Window'" [Low,Fix committed] https://launchpad.net/bugs/33129511:00
didrockspitti: do you want I change it?11:00
pittithis doesn't really match our SRU criteria, and the session fix is quite intrusive11:01
pittididrocks: please; also add a real changelog line for it which refers to the bug11:01
pittithe "new upstream release" one should just close the sponsoring bug11:01
didrockspitti: ok, I am quite unconfortable to add lines that are not on NEWS file, but I will :)11:01
didrockspitti: do you think the gnome-session handling goes against the SRU criteria.11:02
pittiI don't think bug 333603 is of any SRU concern11:02
ubottuLaunchpad bug 333603 in gnome-terminal "gnome-terminal does not honor new gnome session protocol" [Medium,Fix committed] https://launchpad.net/bugs/33360311:02
pittisession saving is _terminally_ broken in current gnome11:02
james_wheh :-)11:02
pittiand changing that behaviour in an SRU is not really appropriate IMHO11:03
pittiI'd upload that to karmic and consider it done11:03
didrockspitti: ok, so, we just postpone in a regular update to karmic :)11:03
crevettehi gentlemen11:03
didrockshey james_w ;)11:03
didrocksand crevette11:03
crevettesorry for not very active theses days11:03
crevette:)11:03
crevette+being11:03
james_wsalut11:04
pittididrocks: ok, thanks11:05
pittiember: please prepare bugs for SRUs properly (brasero)11:09
pittifixing bugs to be SRU compliant is an awful lot of work for me11:09
didrockspitti: done. I removed also the release tag in bzr and changed the bug title. Sorry for the extra useless work in candidating it for SRU11:11
pittididrocks: n/p; just be very conservative about SRUs11:11
didrockspitti: understood11:11
huatshello everyone !11:14
pittimvo: wow, fixing all kinds of random broken universe stuff?11:22
* pitti wishes there was a way to make the upgrade more robust instead of forcing us to do those updates11:22
mvopitti: yeah, I was going over the apport-package list and noticed those issues (some pretty simple to fix)11:24
mvopitti: and yes, its anoying :/11:24
pittimvo: what concerns me is that those aren't really "simple fixes"11:25
pittionce you do them, you need to feed them to Debian, get them applied, fix them in karmic, etc.11:25
pittithose aren't just "fire and forget" updates11:25
mvopitti: I have some hopes for the aufs based upgrader, but that will still mean that a broken package would prevent the upgrade (it would just be a rollback)11:25
mvopitti: right11:25
pittiand I wouldn't like you to get even more swamped in this stuff11:25
mvopitti: yeah, the cost is relatively high :(11:25
pittimvo: we don't do auto-upgrade tests with universe?11:26
mvopitti: we have code for this, it just takes ages. I did a ugprade with a image of ~15.000 packages installed, dpkg was 500mb real mem11:28
mvoand reading the file list took ages11:28
mvoit whole thing lastet a couple of days11:28
mvobut we definitely should do more for karmic (there is a spec about a ec2 based tester planned)11:29
pittiI thought u-m already does some tricks to continue the update if there is a single broken package, or by and large ignore file conflicts11:29
mvopitti: it does ignore all file conflicts and it will continue on error, but that only help if the error is not too deep down in the dependency chain12:03
mvowhy was the gnome-terminal jaunty-proposed upload rejected?12:05
pittiwrong bug attribution in changelog, and general unsuitability for SRU12:14
pitti(I followed up in the bug)12:14
mvoaha, ok12:17
mvoI kind of assumed gnome updates where ok, but I'm fine with that12:17
pittiactually we only had this exception in hardy, we just continued to practice it in intrepid12:18
pittiand I'm still generally fine with it, but this one was a bit too intrusive for my taste12:18
pittipoint releases should fix bugs, not fundamentally change behaviour12:18
=== nhandler is now known as Guest21024
jtholmespopey, are you on12:46
popeyjtholmes: hi12:59
jtholmespopey, good day i just discovered last night that you are the screencasts person, nice job btw you and your team13:00
popeywhere unfortunately the team has been somewhat dormat for a while13:01
popeyneeds reviving13:01
jtholmesi am having problems downloading and saving any of the screencasts and wondered what i am doing wrong13:01
popeyany in particular?13:01
jtholmeslet me get the  name13:02
jtholmeslets start with installing ubuntu part 113:02
popeythey're quite old and could do with updating :)13:02
popeywhich is on my todo list13:02
jtholmesyes but they do server a very useful purpose13:03
jtholmesI click on the download 1280X720 vorbis... and it plays but will not download any ideas13:03
popeyhttp://static.screencasts.ubuntu.com/13:03
popeygrab them from there13:03
jtholmesah, oh let me try that13:04
popeyhttp://static.screencasts.ubuntu.com/20070909_installing_ubuntu_part_1_theora_400k_vorbis_1280x720.ogg13:04
popeythats probably the one you want13:04
jtholmesgood thanks, one more thing have you done a wubi sc13:05
popeyno13:05
jtholmesok i will let you get back to your work, thanks13:05
popeynp13:05
jtholmespopey question pls13:10
popeyfire away13:10
jtholmesat static...  it still only plays doesnt download what am i doing wrong using FF13:11
popeyright click, save link as13:11
jtholmesso then the link is saved but how do i then get the contents to my machine13:12
popeysorry, save target as :)13:12
jtholmesok let me try thx13:12
popeynp13:13
jtholmessave link as is doing it not familiar with that, interesting thanks again i have a situation where i cant go to the inet to get it must have it locally appreciate you help13:15
popeyno problem13:17
seb128hey rickspencer313:52
rickspencer3seb128: nice to see you today13:52
seb128nice to see you too!13:53
seb128did you have a good trip back in the us?13:53
rickspencer3yes13:53
seb128good ;-)13:53
pittihey rickspencer313:53
rickspencer3I stopped in Washington D.C. to visit my new nephew13:53
pittirickspencer3: enjoyed the long weekend?13:53
rickspencer3yes13:53
seb128excellent13:53
rickspencer3I love D.C. it is a wonderful city13:53
pittihah, /me runs 2.6.30rc3, -intel 2.7.0 and UXA now13:54
pittilet's see where this leads me to13:54
rickspencer3fortunately, my sister in law clearly did not want company, so had plenty of time to sight see and such13:54
rickspencer3pitti: thanks for that13:54
rickspencer3I hope it works13:54
pittirickspencer3: I survived the first 5 minutes ;)13:54
pittirickspencer3: anyway, quick update on the 965 issue13:54
rickspencer3I've seen a couple of bugs related to freezes on i945 too :(13:54
seb128pitti: interesting but bryce_ was trying to get the hang using a virtual setting yesterday13:55
pittirickspencer3: meeting on Friday didn't yield anything significant13:55
pittiseb128: right13:55
seb128and seems to confirm that it workaround the bug13:55
seb128at least as said I'm using a virtual setting and never got any issue13:55
pittirickspencer3: setting a virtualsize by default sounds like a promising workaround right now13:55
rickspencer3hmmm13:56
* seb128 notes that I suggested that some weeks ago13:56
rickspencer3seems hacky to me without knowing the root cause13:56
seb128rickspencer3: disabling compiz is hacky too ...13:56
rickspencer3seb128: good point13:56
pittiif we can do that only on the 965, it's acceptable IMHO13:56
pittiit's not acceptable to set it as default on all intel chips, of course13:56
seb128what are the drawback of that?13:56
seb128it allows to use multiple screen too13:56
pittibryce and I had a quick discussion of that, he wanted to prepare a test package and toss that back to upstraem13:56
pittiseb128: we don't know what it breaks on other chipsets13:57
rickspencer3are they still trying to pursue the root cause though?13:57
seb128I meant on 96513:57
pittirickspencer3: not really, at least not on stuff which can't be reproduced on 2.7.0/uxa13:57
rickspencer3so basically exa is a lost cause in their mind, and we need to mitigate until we can get users to uxa?13:58
pittiright13:58
pittiso we'll probably end up with keeping a workaround for jaunty13:58
pittilike setting virtualsize or whatever we come up with13:58
pittiright now we have no clue _why_ it works13:58
rickspencer3in a way, we've worked around it now13:59
pitti(or whether it works for everyone, thus creating the test package)13:59
pittiunfortuantely, my guess with the pipe underrun patch was wrong13:59
pittiit was a shot in the dark only, but at least worth trying13:59
rickspencer3we should discuss whether we should make a change, or just share how to workaround?13:59
pittirickspencer3: let's give this some more testing days with a new package with vsize14:00
rickspencer3I'm a bit uneasy about changing people's xorg.conf now that it's in the wild14:00
rickspencer3pitti: ack14:00
pittirickspencer3: nooo14:00
pittirickspencer3: I mean changing the driver to _default_ to vsize 4096 by default on i96514:00
rickspencer3oh14:00
rickspencer3ok14:00
pitti(or 2048, or whatever turns out to be best)14:00
rickspencer3that makes much more sense14:00
pittichanging xorg.conf in an update -> impossible14:00
rickspencer3heh .. update manager just opened :)14:01
rickspencer3pitti: thanks for driving this14:01
rickspencer3and helping bryce14:01
pittiwell, I couldn't do a lot, just throw in some ideas and prod some people14:02
* pitti hugs bryce14:02
rickspencer3It sounds like changing the default virtual size in the driver would make it more robust in any case14:02
pittiwell, we don't know for sure yet, but we have two positive results14:02
pittiI'd like to see that being confirmed by the other testers14:02
rickspencer3I agree with seb128 though, it seemed likely from when we were first collecting data about the bug14:03
rickspencer3I'll be glad to test bryce's patch later today14:03
pittirickspencer3: no patch yet, we just talked about it14:04
rickspencer3I know14:04
pittirickspencer3: but you can set VirtualSize manually to test14:04
kenvandine_wkhey rickspencer314:04
rickspencer3kenvandine_wk: hi14:04
rickspencer3good morning14:04
pittiI need to go to a doctor appointment now14:04
pittiI should be back well before the meeting14:04
rickspencer3pitti: let me know what to do to help14:04
pitticu!14:04
rickspencer3laters! and thanks again14:04
rickspencer3so much email!14:05
* rickspencer3 gets shovel from shed14:05
seb128rickspencer3: are you subscribed to bug emails too?14:05
rickspencer3seb128: I am subscribed to many bugs, yes14:06
rickspencer3if that's what you mean14:06
seb128ok, because the week after a new version is always crazy14:06
seb128I meant rather subscribed to ubuntu components14:07
seb128ie any source package will generate lot of bugmails this week14:07
rickspencer3seb128: no, I don't subscribe to components14:08
seb128ok14:08
rickspencer3I can only imagine what it's like for you at this point14:08
* kenvandine_wk hugs pitti's mail filters :)14:09
rickspencer3seb128: are there packages that you think I should be subscribed to? I thought subscribing to the whole ubuntu desktop would be a bit much14:09
seb128rickspencer3: not really no, I guess you have enough on your plates already and there is no real point for you to read bugs emails now14:10
seb128ie there is nothing urgent for karmic which just started and jaunty is stable now14:10
rickspencer3I do review all the change mail for Jaunty14:11
rickspencer3there is a lot more than I thought there would be14:11
seb128it's always that busy14:11
seb128there is quite some bug fixes that we want but where the freeze blocked us14:12
rickspencer3mm14:12
seb128so we tend to queue those and upload just after stable14:12
rickspencer3seems that we are not necessarily the most active team in the proposed changes14:12
seb128and still so issues not raised before but showing in post stable feedback14:12
seb128so -> some14:13
rickspencer3I'm still learning the whole release process, it will be another month until I've had one release under my belt, and that will only be one release :)14:13
seb128"not the most active team"14:14
rickspencer3make me grateful to be on a such a great team14:14
seb128that's good ;-)14:14
seb128that means that we are not the team with all the bugs ;-)14:14
rickspencer3heh14:14
seb128for my part I'm mostly done with jaunty updates14:15
seb128I usually spend the freeze time14:15
seb128and the week before +1 opening14:15
seb128on stable updates and then switch to the new version14:15
seb128ie karmic just opened today14:15
* rickspencer3 is down to 431 unread emails :'(14:33
Ampelbeinseb128: hi. can you sponsor bug 366723?14:37
ubottuLaunchpad bug 366723 in alacarte "the properties button does nothing on categories" [Low,Triaged] https://launchpad.net/bugs/36672314:37
seb128Ampelbein: hi, will do when I start on karmic uploads14:37
Ampelbeinok14:37
D0paminehai all14:37
seb128mvo: hum, the python-apt api changed?14:44
seb128mvo: is there an equivalent to sources.Binaries now?14:45
seb128sources = apt_pkg.GetPkgSrcRecords()14:45
seb128    sources.Restart()14:45
seb128    sources.Lookup(package)14:45
seb128    binaries = sources.Binaries14:45
seb128mvo: ^ that's what I was doing14:45
mvothis bit should not have changed in ages, let me check14:47
seb128mvo:14:48
seb128    binaries = sources.Binaries14:48
seb128AttributeError: Binaries14:48
seb128mvo: is what I get on jaunty14:48
seb128that was working in intrepid14:48
mvoseb128: what python-apt version do you run? that seems to work for me14:49
seb128ii  python-apt                                 0.7.9~exp2ubuntu10                   Python interface to libapt-pkg14:49
seb128hum14:50
seb128mvo: ok, that's an error in my code then14:51
mvoseb128: I tried: http://paste.ubuntu.com/160023/14:51
seb128mvo: yeah, I've a source package listed in my table which is not in jaunty14:51
seb128the error is not obvious though14:51
mvoseb128: yeah, the error sucks14:51
seb128mvo: sorry for the noise, thanks for looking into it14:51
mvoLookup() will return a bool if it was successful or not14:52
mvoseb128: no problem14:52
mvo(re: noise :)14:52
seb128right, I don't check the return code14:52
seb128will teach me to write quick and ugly code14:52
seb128that's to list versions of GNOME packages newer in debian14:52
seb128to now what needs to be merge in karmic14:52
=== jorge_ is now known as jcastro
pittihello again15:33
pittikenvandine_wk: are they useful to you? :-)15:33
kenvandine_wkpitti: they?15:34
pittikenvandine_wk: mail filters15:34
kenvandine_wkoh15:34
kenvandine_wkhehe15:34
kenvandine_wkyeah15:34
kenvandine_wkvery15:34
kenvandine_wki recreated them all in evo though15:34
kenvandine_wk:)15:34
kenvandine_wkbut used the same critiria  you did15:34
kenvandine_wkwould have taken me months to figure out what to do with stuff without your guide :)15:35
kenvandine_wkof course the launchpad headers rock!15:35
popeyvuntz: do you have a moment to explain what the blocker on http://bugzilla.gnome.org/show_bug.cgi?id=346162 is?15:37
ubottuGnome bug 346162 in notification area "notification areas on 2nd, 3rd X screens don't work at all" [Major,New]15:37
pittinice, two of my u1 filed bugs got closed as fixed now, and three more triaged15:45
pitti. o O { gosh, compiz with uxa/dri2 is FUN! }15:46
tedgpopey: I'm not sure, but if I was to guess I'd guess the issue is XEmbed going across screens, which is how the notification area is implemented.15:46
popeythanks for the prompt reply tedg, I have a frustrated user in #ubuntu-uk who is willing to do whatever testing is necessary to help move this bug along. He uses 4 screens on two cards and would dearly love this to work. Is there anything he/we can do?15:48
popeyhe obviously realises that 4 screens is something that the xorg devs may not have access to15:48
tedgpopey: I don't think so, I think this may be an X limitation.  There is a KDE proposal to change the notification area spec to use DBus instead of XEmbed that will probably hit KDE for 4.3....  but I haven't seen any GNOME folks reply to the thread.15:51
popeytedg: thats a shame. He tells me that other options such as "stalonetray" (in the repo) works, would that be one that is DBus based then?15:53
vuntzpopey: the blocker on my side is time & difficulties to test15:53
popeyhi vuntz15:54
hggdhquestion: having had my first debdiff approved, I found myself receiving about 20 emails from Rosetta complaining about translations. Is this normal?15:54
vuntzpopey: the annoying thing is that it might only be a tiny detail that is wrong :/15:54
seb128hggdh: yes15:54
seb128hggdh: rosetta bug15:54
popeyvuntz: would it be worth trying to raise the profile of that bug, to see if any other developers are able to look at it, i.e. have time and equipment?15:55
hggdhseb128, thanks. So I can filter to trash without any guilt, correct?15:56
seb128hggdh: yes15:56
hggdhthanks15:56
seb128you're welcome15:56
vuntzpopey: what do you mean with "raise the profile"?15:58
popeywell if you dont have the time/equipment to resolve the issue, perhaps someone else might?15:59
vuntzpopey: other developers would fix the bug if they were hitting it16:00
vuntz(since it's a pretty annoying one, I'd say)16:00
popeytrue16:00
vuntzpopey: so I don't quite know what we can do to raise the profile16:00
popeyok, thanks vuntz / tedg for taking the time to talk to me about it, it's appreciated16:03
rickspencer3hi Yingying_Zhao16:13
asacneed answer: (a) meeting starts now, (b) meeting starts in 30 min, (c) meeting starts in 1h, (d) none of the above _____16:30
pittiasac: I pick (c)16:30
pittidid I win 1M EUR now?16:30
asac;)16:31
asacthx16:31
calc_hehe16:40
* calc_ hopes his car starts up the next time he tries... had to drive it through water at full acceleration yesterday :(16:40
calc_i thought i was going to hit my garage door because i had to drive at full accel even into my driveway so i wouldn't stall out my car, was borderline floating :\16:42
mvoseb128: geh, the code to do the file-overwrite error detection is going to be ugly :/16:43
seb128mvo: why?16:43
mvoseb128: dpkg sends a localized error message with %.250s in it16:44
seb128can we stop translating it? ;-)16:44
mvohaha16:44
seb128or do print an extra line only for that purpose?16:44
mvothat would be a good start ;)16:44
mvoyeah, best is to have dpkg give better status message, I have some code that should work with the string too, but its really not ideal16:45
mvo(works, but ugly)16:45
asaccalc_: sounds wet ;)16:46
seb128mvo: ok16:46
calc_asac: yea, still raining today as well, but luckily the water has gone down at the moment16:47
calc_i'm surprised we haven't hit the saturation point again16:47
calc_hmm lots of warnings to stay away from any river in the area :\16:48
calc_satellite service appears to be knocked out so i can't see the local weather warnings about flooding :\16:49
calc_seb128: do you know if there is a bug report about this yet http://ubuntuforums.org/showthread.php?p=7152067 ?16:55
* calc_ just ran into that bug himself trying to watch local news since his sat is down16:55
calc_shit my wife went to the doctor without a cellphone for me to tell her to come home :\16:57
calc_apparently all schools are closed, it appears it is very serious16:57
seb128this post suggests that's not a bug16:58
seb128it just needs non free codecs not installed by default16:58
calc_well isn't totem supposed to find them for you?16:58
calc_it doesn't do that as it did prior to 9.0416:58
calc_currently it just tells you the protocol support is missing and leaves the user to figure out what to do about it themselves16:59
seb128totem does the mozilla plugin doesn't17:02
seb128that's a known issue17:02
calc_hmm well spawning a full totem from the mozilla plugin still didn't find it for me17:03
calc_i'll try testing it again on my other system and reporting the bug with an example site to use later today (assuming i don't lose power again)17:04
calc_25cm of rain overnight17:05
seb128could be gnome-codec-install being buggy17:07
seb128but I don't know about this code17:07
seb128that's a slomo thing17:07
calc_ok i'll report it there along with the details once i test it again17:09
* calc_ wonders if he still has internet access17:13
calc_wow 27s ping response i'm very lagged17:14
=== calc_ is now known as calc
mvodidrocks: so g-t 2.26.1 should go to karmic?17:20
rickspencer3kenvandine_wk: could you please add notes and links to the wiki regarding U1 before we start?17:22
* pitti tosses some TCP packets to calc17:22
calcit seems to be mostly working atm17:25
calconly 3s now17:26
pittiseb128: can we cowtrade merges? I do gconf for you, you do rarian for me?17:29
bryceheya rickspencer3, wb!17:29
seb128pitti: ok17:29
rickspencer3tx17:29
seb128pitti: I didn't even notice that you had gconf assigned, I don't use merge.ubuntu.com usually17:29
pittiseb128: merci; I still pretty much don't have a clue what scrollkeeper/rarian are doing in the first place :/17:30
pittiseb128: well, you have gconf assigned, but I have rarian17:30
kenvandine_wkrickspencer3: sure17:30
pittibecause I'm TIL (small dependency fix or so)17:30
seb128pitti: ok, let's trade then ;-)17:30
calcmeeting?17:30
rickspencer3meeting time?17:30
* pitti sits down17:30
rickspencer3heh17:30
* rickspencer3 slaps desk with ruler17:31
rickspencer3https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-04-2817:31
rickspencer3unfortunately, I'm still catching up, so not quite as organized as I like to be17:31
pittiugh, activity reports are a bit thin17:31
rickspencer3pitti: right, I haven't had a chance to put them in the wiki yet17:32
pittibut I saw them fly by in mail17:32
rickspencer3it's all my fault17:32
pittin/p :) *hug*17:32
pittirickspencer3: hope you enjoyed the long weekend17:32
rickspencer3well, I've been working non-stop since like 5:30am, so am not feeling too guilty ;)17:32
rickspencer3I hope everyone is feeling good about Jaunty17:32
pittimy clock does not have 5:30 _AM_17:32
rickspencer3the buzz in the office in London was *very* positive17:32
rickspencer3Gerry told me "best reviews ever!"17:33
kenvandine_wkrickspencer3: done17:33
rickspencer3so, first topic17:33
pittia friend of mine is very pleased with it, told me to pass on the "thank you"17:33
rickspencer3State of Jaunty17:33
pittiwe have tons of SRUs17:33
rickspencer3general feedback about quality17:33
rickspencer3?17:33
rickspencer3pitti: is that normal?17:33
pittibut none of them really OMGkittensdie17:33
pittirickspencer3: yes, very17:33
seb128pitti: "tons" .. the normal amount I would say17:33
pittia few major upgrade issues17:33
pittiseb128: we normally have "tons and tons" :)17:34
seb128;-)17:34
pittiand some polish17:34
rickspencer3lol17:34
pittiI was pretty liberal in the first few days after jaunty17:34
pittibut now I'll raise the bar pretty high17:34
pittisorry, davmor/mvo :)17:34
rickspencer3as discussed, I would like to transfer effort to Karmic as rapidly as possible17:35
pittiwe still have a major e-d-s crasher and the 965 issue, otherwise I wouldn't waste too much work on it17:35
rickspencer3pitti: good17:35
seb128pitti: e-d-s crasher -> libical waiting for you17:35
seb128pitti: I turned of the crashing warnings17:35
pittiseb128: you rock17:35
pittihah17:35
rickspencer3pitti: bug #?17:35
seb128pitti: which is what fedora does and upstream recommends doing17:35
rickspencer3for those following along?17:36
pittibug 36850817:36
seb128rickspencer3: e-d-s crasher? look to recent bugs there17:36
ubottuLaunchpad bug 368508 in libical "don't crash on incorrect values or errors" [Wishlist,Confirmed] https://launchpad.net/bugs/36850817:36
pittiI presume17:36
seb128there is several bugs which are probably duplicates17:36
pittiyou guys upload faster than I can process SRUs :)17:36
seb128pitti: yes17:36
brycehehe17:36
seb128pitti: I switched to karmic this afternoon ;-)17:36
seb128so expect less SRUs from me17:36
pittiseb128: would be nice if you could dupe some real bug reports to that one, to get some testers subscsribed17:37
seb128"switched", ie I'm not using it yet17:37
seb128but I'm working on it17:37
pittianyway, no meeting issue17:37
seb128pitti: will do17:37
pittianyone else aware of somethign major which needs fixing in jaunty?17:37
rickspencer3I feel that we still have this i965 nut to crack, and that as a team we won't really be done with Jaunty until we have compiz working again17:37
pittiasac: did anything pop up on the nm/ff front?17:37
pittibryce: and any other kitten killers besides 965?17:37
brycenot really17:38
pittikenvandine_wk: or major breakage in notify-osd?17:38
brycewell, lots of X bugs kill kittens17:38
brycebut none that are on a rampage17:38
pittiok, good17:38
pittibryce: all will be better with DRI2/UXA, right? :-)17:38
pitti(famous last words)17:38
kenvandine_wkpitti: not really17:38
bryceI've talked to colin king about the performance issue, so we may see some progress there, but that's mainly kernel side stuff17:38
brycepitti: yes, we get to exchange all our nasty old bugs17:39
brycefor fresh new ones17:39
* pitti is running 2.6.30rc3/uxa/dri2/2.7.0 happily17:39
pittiok, seems the "jaunty state" topic is done?17:39
rickspencer3yes17:39
rickspencer3except ... if you have an i965, or access to one, please be highly responsive to requests for assistance17:40
rickspencer3kenvandine_wk: U1?17:40
kenvandine_wkok17:40
kenvandine_wkso U1 beta is coming up soon17:40
kenvandine_wkand I don't think we have had enough testing... so I have been turning up the heat17:40
seb128what is U1?17:40
pittiubuntu one17:40
kenvandine_wkI even went cold turkey from dropbox17:40
kenvandine_wkserious dogfooding17:41
seb128ah ok17:41
kenvandine_wkthere are instructions on the meeting wiki page for setting it up, everyone on the desktop team needs to kick the tires and report bugs17:41
kenvandine_wkbut wait until tomorrow please :)17:41
kenvandine_wkmajor bug fixes are landing today as well as ppa changes17:41
kenvandine_wkthanks, lets help make sure U1 rocks!17:42
rickspencer3kenvandine_wk: thanks17:42
rickspencer3all - please note that the U1 team is trying *very* hard to be easy to work with here17:42
rickspencer3so I ask that we support them in kind by running their bits17:43
rickspencer3I'll ask kenvandine_wk to set up some kind of test or something that we can all participate in for the next team meeting17:43
rickspencer3next topic17:43
rickspencer3Launchpad Team and Kubuntu17:43
rickspencer3I just wanted to point out that three of the leads are serious Kubuntu fans17:43
rickspencer3Riddell: ^^^17:44
rickspencer3I'm trying to get them to join #kubuntu-devel and support the project17:44
rickspencer3next topic: Launchpad Team and Kubuntu17:44
rickspencer3oops ... copy paste error ;)17:44
rickspencer3All Hands17:44
rickspencer3everyone ready?17:44
pittiI brought my two hands17:45
Riddellcool17:45
pittistill need to prep the talks, though17:45
rickspencer3anyone else doing a talk?17:45
* rickspencer3 raises hand17:45
calci am, need to finish it up still17:45
ArneGoetjeany information in which format the talks should be? I didn't see anything announced17:45
ArneGoetjeme too17:45
pittihm, it came through the lists17:45
rickspencer3ACTION: rickspencer3 to dig up info on all hands talk and resend to desktop team17:46
pittiI got two "talk approved" mails with some details, you didn't?17:46
bryceI'm doing a talk but I've not even had a moment to think about UDS :-(17:46
ArneGoetjeI only saw the announcement for the talks, but I haven't seen anything about the preferred file format17:46
rickspencer3seb128: you're doing one if I recall correctly17:46
seb128rickspencer3: I got no email17:46
rickspencer3hmmm17:46
seb128so I guess my talk didn't get approved17:46
rickspencer3ACTION: rickspencer3 to check on seb128's talk17:47
kenvandine_wkseb128: i got a no thanks mail :)17:47
rickspencer3seb128: I thought I was cc'ed on one for you17:47
seb128rickspencer3: could have been spammed then17:47
rickspencer3seb128: ack, I'll check it out asap17:47
* pitti wonders about the spammy topic seb128 will talk about then17:47
seb128if it got spammed I deleted it17:47
seb128or "marked as spam" rather17:48
rickspencer3seb128's topic was about about canning spiced ham, so it may have been diverted17:48
seb128I've difficulties to keep my boxes spam free at the moment17:48
rickspencer3ready to talk a little about UDS?17:48
seb128yes!17:48
kenvandine_wki've had my email addy for 2 months now... and get a ton of spam already, can only imagine what seb128 gets17:48
rickspencer3a key change for Karmic is that we have two rooms17:49
* pitti gets about 5000 a day through SpamAssassin, and about 70.000 per day which are rejected earlier on17:49
calcthe canonical filter seems to catch most of my spam17:49
rickspencer3also, we are "hosting" Dx and Design in our track17:49
rickspencer3you may notice that I have added a bunch of blueprint "stubs"17:50
ArneGoetjemie didn't get approved yet17:50
ArneGoetjemine17:50
rickspencer3essentially placeholders that I could use to subscibe folks to and for scheduling17:50
rickspencer3ArneGoetje: no problems. These initial ones were based on internal partners and other things17:50
ArneGoetjeok17:51
rickspencer3folks from the community and Ubuntu engineers, still have time to create blueprints17:51
ArneGoetjeuntil when?17:51
seb128do we need to create blueprints or only to suggest topics?17:51
rickspencer3ideally, you would all get them stubbed out by eow17:51
rickspencer3seb128: go ahead and create them, I think17:52
rickspencer3I haven't been through this before, so I thought I would let you all tell me how you want to do it17:52
rickspencer3I'17:52
rickspencer3ll create them for you if you want, but it seems more efficient just to let you do it17:52
rickspencer3pitti: what do you think?17:52
pittiwould be good to have the blueprints created in a week, so that we can still schedule them appropriately17:52
kenvandine_wkrickspencer3: i have a few i proposed, which don't show up on the list yet... not sure what has to happen there17:53
seb128right, I was just wondering if we were filtering topics before17:53
pittiyes, everyone should create their "own", which you are interested in17:53
seb128to not create blueprint for things which are not scheduled or accepted17:53
pittiset drafter to you, approver to me, and propose for uds-karmic17:53
seb128ok17:53
pittiblueprints need to have a good summary and title17:54
kenvandine_wkpitti: if i find one that exists already, how can i set myself to drafter?17:54
pittino need to create wiki pages yet, although of course having them is nice17:54
pittikenvandine_wk: "change people"17:54
pittikenvandine_wk: prod me to do it if you can't17:54
kenvandine_wkok17:54
kenvandine_wki have a couple i can't17:54
pitti(it's restricted to some group I can't remember)17:54
pittior prod rickspencer3, whoever is available17:55
kenvandine_wki'll poke you after the meeting17:55
rickspencer3In terms of title, I would ask that folks also start the name with "desktop"17:55
pittiso before next meeting, rick and I will go through the karmic proposed ones and approve them17:55
rickspencer3this makes the list much easier to use, I also have to manage dx and design sessions17:55
pittiso that we can talk about the list in next week's meeting17:55
kenvandine_wkcan we rename the existing ones?17:56
pittiright, good to bring that up17:56
kenvandine_wkor have you guys rename them?17:56
rickspencer3kenvandine_wk: yes17:56
pittiplease prefix the spec identifiers with desktop-karmic-*17:56
pittikenvandine_wk: retitling is easy, I don't know if the identifier can be changed17:56
pittianyone should be able to update title/description17:56
kenvandine_wki can't for the ones i didn't create17:57
kenvandine_wkat least the one i tried17:57
pittikenvandine_wk: ok, let rickspencer3 or me reassign, then you will be able to17:57
kenvandine_wkok17:57
rickspencer3next topic is easy: Desktop Summit17:58
rickspencer3let me know if you're going, or want to go17:58
tkamppeterI will not be there.17:58
rickspencer3also, Canonical is hosting the welcoming party, so if you're going, make sure you get there in time for that, it should be a blast17:58
bryceme neither17:58
rickspencer3:(17:58
calcrickspencer3: i emailed you last week about it17:58
ArneGoetjeme neither17:58
calcrickspencer3: i'm interested in going but didn't have time to submit a paper before the deadline17:59
rickspencer3okay, let me know *off list* if you're going or want to go :)17:59
rickspencer3calc: ping me later and we can talk17:59
calcok17:59
rickspencer3next: OEM team swapperoo17:59
rickspencer3reminder that calc will be working with OEM services starting next week!17:59
rickspencer3and we'll have a new team member as well (Tony, I think)17:59
brycehave fun calc18:00
calcbryce: heh :)18:00
brycewill tony be working on openoffice then, or general desktop stuff?18:00
calci get to learn lots of new things and bring back my knowledge to the desktop crew in november :)18:00
rickspencer3bryce: both18:00
rickspencer3I think we'll have to basically slow down OOo development (which given the Sun buyout may be prudent anyway) and spread the work around a bit18:01
rickspencer3also, calc will have some time to help us18:01
calcthe biggest chunk of OOo work is getting bugs properly triaged due to having two upstreams18:01
calcwe are pretty much caught up at the moment but get lots of new bugs every day :)18:01
rickspencer3calc: We'll miss you, but I think you'll have a great time, and learn tons18:01
rickspencer3any other business?18:02
calcyep :)18:02
bryceoh I have one thing18:02
bryceI already mentioned it on the ubuntu-devel@ mailing list, but the X team has a PPA set up now with updates for all the major video drivers18:03
pitticalc: good luck!18:03
brycehttps://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/18:03
rickspencer3bryce: notice that Yingying_Zhao has started haning out in #u-d?18:03
bryceI'm sure everyone here will be on karmic so will be getting these automatically, but please pass word around about this to anyone sticking to Jaunty.18:03
brycerickspencer3: no I hadn't18:04
rickspencer3hi Yingying_Zhao o/18:04
* bryce waves to Yingying_Zhao18:04
pittihi Yingying_Zhao, nice to see you here!18:04
bryceI'm formulating plans for -intel focus work for karmic, but more on that later.18:04
rickspencer3schweet18:04
brycenaught else from me.18:04
rickspencer3meeting adjourned?18:05
calcoh is Tony from the OEM team swap or a new hire?18:05
pittihave fun everyone with karmic syncs and new crack!18:06
rickspencer3calc: swap18:06
pittis/syncs/merges/18:06
calcok18:06
rickspencer3thanks all18:06
ArneGoetjethanks18:06
pittithanks all18:06
brycecalc: iirc tony is the guitarist in the allhands jam18:06
seb128thanks all18:06
rickspencer3ArneGoetje: good night :)18:06
calcbryce: ah18:07
calcthanks18:07
ArneGoetjerickspencer3: thanks... soon :)18:07
brycethanks all18:07
asacthx18:08
* calc loves the huge influx of bugs a release causes, heh18:09
brycecalc: yeah the slope on my curve is steeper than it's ever been18:09
pitticalc: strange kind of love :)18:09
brycehttp://people.ubuntu.com/~bryce/totals.svg18:10
brycelooks like a jet taking off18:10
bryceof course, I've been focusing on like TWO bugs exclusively the past couple weeks, but still...18:11
pittieveryone's bug mailbox is exploding indeed18:11
pittibut I think that's mostly due to ever-more people reporting feedback, not necessarily because we get worse18:11
seb128that's for sure18:13
seb128desktop bugs are mostly small details18:13
seb128but there is just of enthousiastic users reporting anything they find18:13
seb128+lot18:13
calcbryce: i keep beating mine down but they pop up as quickly as i can squash them18:14
pittimvo: still remember why you applied the gconf patch 05_from_vuntz_gconf2-pk-default-path.patch ?18:21
pitti+    - use xml:merged:/etc/gconf/gconf.xml.defaults as default18:22
pitti+      location for system settings (thanks to vuntz)18:22
seb128pitti: because that's the right directory to use on debian or ubuntu18:22
pittiokay18:22
pittiseb128: but then, why do we carry a patch which adds /etc/gconf/gconf.xml.system/ and adds a change to debian/default.path to include xml:readonly:/etc/gconf/gconf.xml.system?18:23
pittithat directory is empty here18:23
seb128pitti: that's probably a leftover from the time where we didn't have this patch you just listed18:24
pittiright, I wondered why we have both, we should drop one18:24
pittiand it looks to me like we could drop gconf.xml.system18:24
seb128we need to check when we used the wrong directory18:24
seb128ie did it make to a stable?18:24
seb128in which case people might have settings there18:24
pittiseb128: okay, I'll do that then18:25
pittiseb128: if I find anything, I keep the default.path addition18:25
pittiit doesn't really hurt anyway18:25
seb128right18:25
pittiseb128: thanks for the heads-up18:25
pittiwell, I'll just keep it18:25
seb128you're welcome18:25
pitti+# new system defaults mechanism (deprecated, but we need to keep it18:26
pitti+# for compatiblity with intrepid (8.10) were this was the default18:26
pitti+# for the system wide gconf settings (via org.gnome.GConf.Defaults)18:26
pittiah18:26
pittiI'm off for the evening, we meet for preparing a friend's wedding18:32
pittisee you tomorrow!18:32
brycecya pitti18:33
seb128pitti: have fun, see you tomorrow18:35
chrisccoulsonhey seb128 - got any karmic updates for me to do? ;)18:58
* chrisccoulson is liking the thunderstorm outside18:59
seb128chrisccoulson: hello19:34
seb128chrisccoulson: yeah, lot of things to do, I need to do a list19:34
seb128chrisccoulson: do you want to sync gnome-session on debian?19:34
chrisccoulsonseb128 - yeah, i can do that19:34
seb128sync or merge whatever is required19:34
seb128chrisccoulson: you can look to merge nautilus too if you want19:35
chrisccoulsoni'll take a look at it19:35
calci think was are past the saturation point now it hasn't rained in an hour or so and the water level on the street isn't receding :(19:36
* calc hopes it doesn't rain any more19:36
seb128chrisccoulson: cool, I will try to make a team todolist tomorrow for other updates and work19:38
chrisccoulsonthanks, that would be useful:)19:38
seb128chrisccoulson: any package which has not been merged with debian yet is a good candidate to clean19:38
seb128ie we want to send changes upstream or to debian when it makes sense19:39
seb128and rebase the version on debian19:39
=== rickspencer3 is now known as rickspencer3-afk
crevetteheya20:04
crevettehey huats20:04
crevettehello seb12820:04
seb128hi crevette20:04
huatshello crevette20:04
mahendrahello20:10
mahendrai need some help20:10
crevetteseb128: I wonder how you do to not get lost in update between upstream one and debian sync20:12
crevette:)20:12
mahendrai just upgraded my ubuntu 8.04 to 8.10. but now there is no title bar to any of the windows.20:12
crevetteit's a kind of sport20:12
mahendrai tried changing themes but its not working20:13
seb128crevette: you need to know where to look ;-)20:13
seb128mahendra: try #ubuntu20:13
mahendraok20:13
seb128mahendra: that channel is a work one not an user question one20:13
mahendrathanks20:13
seb128mahendra: and I would recommend using 9.04 it's much better than 8.1020:13
crevette:)20:14
mahendrai am going to upgrade to 9.04 but i need to solve this problem first20:14
crevetteseb128: sorry for not bein that active20:15
seb128crevette: no need to be sorry20:15
crevetteI seriously lack some times :/20:15
crevettebah, I feel totally inefficient :/20:15
seb128you have enough to do20:16
crevetteI'll try to get some time later to help you for some packaging :)20:17
seb128cool20:18
seb128bbl20:18
crevettethat was quick20:19
seb128yeah just forgot to write something on an another channel20:19
seb128bbl for now20:19
crevettesee uou20:19
dobeyvuntz: is that intltool fix sufficiently good for you?21:00
=== jorge_ is now known as jcastro
calcugh my wife and son are stuck in another part of the city and can't get back due to the flooding :\21:40
=== seb128_ is now known as seb128
=== rickspencer3-afk is now known as rickspencer3

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!