/srv/irclogs.ubuntu.com/2009/03/10/#ubuntu-desktop.txt

Pirate_kinganyone using a Quick cam for notebooks in ubuntu 8.10 with skype?03:30
Pirate_kingworks in ekiga03:30
=== bluesmoke is now known as Amaranth
=== bluesmoke is now known as Amaranth
=== asac_ is now known as asac
pittiGood morning07:52
=== tkamppeter_ is now known as tkamppeter
crevettehello08:17
crevettegood morning08:17
didrockshey seb128 & crevette08:23
crevettehey didrocks08:23
seb128lut didrocks crevette08:23
didrockscrevette: did you see my comments this week-end?08:23
crevettedidrocks, I didn't had time to looke to the package08:23
crevetteI was tired due to some birthday party08:24
didrocksseb128: if there is some update/things to do, do not hesitate (even if it will be updated after the soft freeze)08:24
seb128hey mvo08:24
mvohey seb12808:25
seb128didrocks: there is a gnome-netstatus update you can look at if you want08:25
seb128mvo: your compiz updates were not installable, did you forgot to upload package renames?08:25
crevettesalut seb12808:25
didrocksseb128: oki08:26
didrockshi mvo08:26
mvoseb128: hrm, what packages were not installalble?08:26
seb128mvo: slangasek fixed it08:26
seb128mvo: "  * Depend still on compiz-fusion-plugins-{main,extra} instead of on08:26
seb128    compiz-plugins-{main,extra}, as the package names have not changed in08:26
seb128    0.8.2."08:26
mvoohhh08:27
mvoI had planned to rename them (upstream renamed them) but didn't in the end to avoid NEW and all this08:27
mvohey didrocks08:27
mvoseb128: but one most have made it into bzr :(08:28
didrockscrevette: ok, just tell me when you fixed those :)08:29
crevettedidrocks, yeah, I'll update bugs when it's ready, I'll try to do nautilus-sendto-universe quickly08:29
seb128pitti: I've untagged yet another firefox bug and removed the retracer lock08:33
pittiseb128: thanks; I'm about to fix it once and for call in crash-digger08:33
pittijust need another 5 mins to finish the morning email08:33
seb128pitti: thank you08:33
seb128brb restarting session08:34
mvo456 mails from rosetta, not bad for the night08:42
huatsmorning everyone08:45
didrocksmorning huats08:46
seb128mvo: I got rosetta and bug watch spam this night08:47
seb128lut huats08:47
huatshello seb12808:48
didrocksmvo, seb128: so do I08:54
didrocksseb128: gnome-netstatus update is finished. I will test it this evening and try to push it to alioth too as it is a stable release09:00
seb128didrocks: we are on sync with debian?09:01
didrocksseb128: not for this package. There is only a few remaining patches that seems to not be ubuntu specific and I have to seek if they have been reported to debian and refused, or just not been reported09:02
asactoo bad. i think the update yesterday killed my window decorations :/09:05
* asac checks whether there are more updates ;)09:06
asack ... so compiz is not running and there are new compiz bits coming09:07
pittididrocks: great, you'll look into the pidgin backport? I added stable tasks to that bug which originally asked for 2.5.5 update09:09
crevettehey pitti09:09
crevettepitti, if you want to test gnome-bluetooth 2.27.1 which can replace bluez-gnome (and hence fix the pin code problem) you can try my package in my ppa (https://edge.launchpad.net/~bmillemathias/+archive/ppa)09:10
crevetteseb128 suggested to push in universe to have time to test it, I think this is a very good idea09:11
pitticrevette: oh, the entire bluez-gnome is obsolete then?09:12
pitticrevette: is g-b an entirely different project, or was b-g renamed?09:12
crevettepitti, not sure..., bastien didn't expected new release from bluez-gnome09:12
pittiI don't think it's appropriate to switch at this time09:13
crevettegnome-bluetooth has a different purpose before, but it was superseded by gnome-user-share09:13
pittiI just want this silly bug fixed, but that can't be too hard with the current version either09:13
crevetteso bastien decided to fork bluez-gnome and use the name gnome-bluetooth09:13
crevetteso the code base is almost the same than bluez-gnome with a lot of enhancements, but still rough09:14
asacmvo: compiz is really dead for me ;)09:17
mvoasac: oh?09:17
mvoasac: I was just about to ask you what to do with n-m on ugrdae. should I add code that detects if n-m is being used and refuse upgrades over ssh (because at some point n-m will stop the interface?)09:18
asacmvo: yes. no window decorations on my intel chipset09:18
mvoasac: could you please check if "compiz" (the meta-package) is installed09:18
asacmvo: please try to disable hal getting torn down09:19
asacalso ensure that udev is not restarted/shutdown09:19
asacmvo: no09:19
mvoasac: and then put a ps afx into a pastebin09:19
asacits pn09:19
mvoasac: could you please install it ?09:19
mvoand re-login into the session09:19
asacmvo: well i have metactiy running. should i get back to no-decoration state?09:20
asacmvo: i looked and compiz wasnt running iirc09:20
asacmvo: was compiz removed by accident?09:20
mvopitti: do you have any opinion on the "hal/udev" should not be restarted so that n-m keeps its interfaces09:20
pittioh? I restart hal all the time09:21
mvoasac: yes, there was a transient issue with the update09:21
asacmvo: i dont even say it shouldnt be restarted. hal should not be stopped like in the beginning of the upgrade process09:21
asacand then being down for 20 minutes09:21
pittiah09:21
pittiright09:21
asacat least i would like to try that09:21
pittiit should be restarted in the postinst only09:21
mvoyeah09:21
asacmvo: also check what udev does ;)09:22
pittiit would wreak havoc if d-bus changed underneath us, but it hasn't changed since 1.009:22
pittiso I think it's okay09:22
pittiif you need it, please file a bug against hal and assign it to me09:22
pitti(or commit it into the hal bzr, of course :) )09:23
mvoI will do a local version and try it there, I still ahve a test-image09:23
pittiah, convenient: dh_installinit -R09:23
pittiso this should just be a DEB_DH_INSTALLINIT_ARGS=-R in debian/rules09:23
asacmvo: ok. i so i am now installing compiz meta package and re-login?09:25
mvoasac: please do09:25
mvopitti: sweet09:26
asacso do we restart dbus during upgrade?09:28
asacmvo: any clue why hal disappears/reappears multiple times in the syslog?09:28
asachttp://launchpadlibrarian.net/22876290/nm-upgrade-syslog09:29
* asac relogin09:30
asacmvo: so i dont have desktop effects enabled. if i enable it everything gets so slow that i cannot even click the "keep previous settings" thing09:32
asachave to wait 45 seconds09:32
asaci will reboot now. who knows whats going on in the driver09:33
asacmvo: ok. so nothing helps. compiz dead on my X61 ;)09:38
pittiseb128: bug 337110 :-)09:38
ubottuBug 337110 on http://launchpad.net/bugs/337110 is private09:38
mvoasac: could you please put your .xsession-errors log into some pastebin? or the startup stuff it outputs (if you run it from a terminal)09:39
seb128pitti: \o/09:39
didrockspitti: I will have a look at it within the day, yes09:39
pittididrocks: you rock09:39
pittiit's pretty urgent, I think09:39
asacmvo: ok i will try to run it from terminal09:39
didrockspitti: thanks for the task :-)09:39
seb128didrocks, pitti: the icq issue?09:39
didrocksseb128: yes09:39
pittididrocks: I wish I could help you, but I have so many tasks to do ATM that I'd need to fork three times..09:39
mvopitti: oh, babies ;) ?09:40
pittiseb128: I also committed a change to drop CoreDump et al from invalid bugs09:40
didrockspitti: no problem. I will give a first status about it this evening :)09:40
pittimvo: eventually :) but training lasts quite a bit09:40
asacmvo: http://pastebin.com/f12055dbb09:40
seb128pitti: waouh ;-)09:40
mvoheh :)09:41
didrocksmvo: I told that to a friend yesterday "oh, you had babies, you forked? " ;)09:41
asacso .xsession-erros is completely cluttered by Gsm things09:41
asachow can i disable that=09:41
asacx-session-manager[4454]: DEBUG(+): GsmManager: disconnect client09:41
mvodidrocks: is he a geek, did he get the joke?09:42
mvoasac: hm, that looks ok, but its still dog-slow?09:42
asacmvo: didnt work at all09:42
didrocksmvo: yes, he is a geek, otherwise, I would not have told him that. Not *so* crazy :)09:43
mvo:)09:43
asacmvo: now i am without decorations09:43
asaccould be that i hit ctrl-c09:43
asaclet me run again09:43
mvoasac: could you run gconftool --unset /apps/compiz/general/allscreens/options/active_plugins09:44
mvoplease ?09:44
asacmvo so yes. its gdog slow09:44
asacswitching gnome terminal tab takes 20 seconds09:44
seb128didrocks: let me know if you need testing or sponsoring, I use ICQ and have intrepid and hardy boxes09:44
asactyping this line takes like 10 seconds09:44
mvoasac: that is strange, I want your Xorg.0.log09:44
asaclet me kill compiz first09:45
mvoasac: what is super strange is that hardly anything in the graphic code changed due to the update09:45
asacmvo: indeed.09:45
didrocksseb128: yes, I will appreciate: I guess last time I connected to ICQ, it was something like 2001 :)09:45
didrocksso, what can be my ICQ number? :p09:46
* mvo has his first cup of japanese tea after days of stomach suffering - what a delight09:46
asacmvo: http://pastebin.com/f5d8a3cd409:46
didrocksmvo: be careful with your stomach in this case, tea can be more harmful than coffee09:46
pittiseb128: new apport uploaded (with fixed apport-retrace); next time it fails, please ignore; I'll update the chroots when it built/published, and restart09:47
mvodidrocks: yeah, I'm just having one cup (to be on the safe side)09:47
mvobut its *so* good :)09:47
* mvo is happy09:47
* asac not happy ;)09:47
seb128pitti: ok09:48
mvoasac: #09:48
mvo[    0.619738] (**) intel(0): Using UXA for acceleration <- was that working before09:48
asacmvo: i used this since berlin. yes.09:48
mvook09:48
asacmvo: its the new default for intel i think09:48
seb128pitti: if you log into the chroots please add a deb-src source there so source retracing works again09:48
asacmvo: i can check if thats the reason. but EXA was severly broken lsat time09:48
mvo#09:48
mvo[    2.455715] (II) intel(0): direct rendering: DRI2 Enabled <- and that was ok too?09:48
asacso i assumed its just not supported for intel anymore09:48
pittiseb128: ah, will do09:49
asacmvo: i never explcitly did anything with DRI09:49
mvoasac: its fine, I'm just poking09:49
asacmvo: so no idea.09:49
asacmvo: how can i disable it ?09:49
mvoI don't know, I need to check the driver09:50
asacok i will disable the expclitit UXA now and re-login09:50
asacmvo: ok UXA it is indeed09:51
asacbryce_: ^^09:51
asacbryce_: UXA breaks compiz since yesterday09:52
asacseb128: can i bribe you to NEW pywebkitgtk?09:54
seb128asac: yes, let me have a look09:54
asacseb128: or reject09:54
seb128asac: why reject?09:55
asacseb128: its broken since doko didnt care09:55
seb128it's not binary NEW?09:55
asacseb128: its binary NEW09:55
asacseb128: dont know. its a new upstream version that huats prepared09:55
asacif you didnt hand out FFe09:55
asaci hope you can just new it ;)09:55
seb128yeah, I grant it and will new it09:56
asacseb128: thats so precious. maybe after all these weeks gwibber will finally work then ;)09:56
huatsasac: it is accepted already I think09:56
seb128what is all the buzz about this thing ;-)09:56
huats(since this night)09:56
asachuats: since when?09:56
asachuats: hmm.09:56
asaclet me check09:56
huatsat least it is not in new anymore from my point of view09:57
asacseb128: its the main app for using twitter with gtk09:57
asacseb128: yes. scratch that09:57
seb128what is all the buzz about twitter09:57
asacseb128: it was still in new yestrerday night09:57
seb128ok, good ;-)09:57
huatsasac: it was yesterday indeed09:57
seb128slangasek probably cleaned09:57
asacseb128: twitter (identi.ca) is good for bonding09:57
asacseb128: and if you dont like writing prosa blogs ;)09:57
asacbut still want to get news out09:58
seb128I'm so not into all those web2 social website things09:58
asacseb128: get an identi.ca account ;)09:58
seb128but if people enjoy writting their life on the web and sharing all their privates datas there good for them ;-)09:58
asacseb128: start doing it. i wondered about it before i started doing it too09:58
asacand thought it was senseless ;)09:59
seb128and they got you now? ;-)10:00
asacseb128: yeah ;) ... since three month already.10:00
asacseb128: not sure if i will continue to do that forever10:00
asacat least i managed to find some firefox security testers through that channel ;)10:00
asacseb128: good thing is you can create a search for keywords (like ubuntu, gnome, firefox)= and then you see if someone has to say something about it ;)10:01
asacso you get news you would miss otherwise10:01
asacalso the new notifications are good for that ;) (lots of notifications that shouldnt get in your way)10:02
seb128I will give it a try and test gwibber too10:02
cassidyseb128: hi! When you have some time, could you take a look on https://bugs.edge.launchpad.net/ubuntu/+source/telepathy-farsight/+bug/337195 please? We need it to upload latest Empathy to Jaunty10:02
ubottuUbuntu bug 337195 in telepathy-farsight "[UVFe] Please allow merge for telepathy-farsight 0.0.4" [Wishlist,New]10:02
asacseb128: :-P10:02
seb128cassidy: do you need a merge or a sync?10:03
asacseb128: let me and jorge know when you have an account so you can be properly introduced ... that will give you a bunch of subscribers/followers right away ;)10:03
asacok back to nss10:03
cassidyseb128: a sync I think.10:03
seb128asac: ok ;-)10:03
asacbryce_: let me know if you need anything for the UXA-compiz bustage10:04
cassidyseb128: if the pkg has no ubuntu change, that's a sync, right?10:04
seb128cassidy: right, the bug seems to suggest that but the title doesn't10:04
cassidyseb128: indeed. Let me ask confirmation to bigon10:04
seb128cassidy: synced10:05
cassidythanks!10:05
seb128you're welcome10:05
cassidygreat, hopefully we should have an Empathy with working/reliable audio/video in Jaunty :)10:05
seb128cassidy: excellent ;-)10:06
pittiseb128: do you have your script somewhere which debdiffs a built .deb against dpkg -L?10:14
seb128pitti: http://people.ubuntu.com/~seb128/diff-symbols.py10:15
seb128pitti: just run diff-symbols.py in the src dir after the build10:15
seb128pitti: dholbach had an another variant which takes 2 debs and compare those10:16
pittiseb128: hm, that's for shlib symbols10:16
seb128oh10:16
pittiseb128: I mean .deb contents10:16
pittilike debdiff old.deb new.deb10:16
seb128pitti: http://people.ubuntu.com/~seb128/debnbfiles10:16
pittibut old.deb being dpkg -L10:16
asacmvo: "asac:Modify Update Manager so that it does not automatically download new indexes when connected to a 3G network:started "10:16
asacmvo: whats the status on this? is that postponed?10:16
pittiseb128: that very; merci!10:16
seb128pitti: run "debnbfiles" in the directory which has the debs10:17
seb128pitti: you're welcome10:17
seb128asac: any opinion on bug #332253?10:26
ubottuLaunchpad bug 332253 in epiphany-browser "Epiphany doesn't mention Ubuntu in user agent string" [Wishlist,Confirmed] https://launchpad.net/bugs/33225310:26
mvoasac: I hope to still get to it, but a lot of stuff kept me busy10:26
mvohey MacSlow10:28
MacSlowmvo, hey there10:28
MacSlowseb128, pitti yo10:28
* MacSlow is so happy to have working network on his laptop again10:29
seb128hello MacSlow10:29
cassidyseb128: we'll need gabble .22 too for proper audio/video support. See https://bugs.edge.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/33736110:30
ubottuUbuntu bug 337361 in telepathy-gabble "[UVFe] Please sync telepathy-gabble 0.7.22-1 from debian unstable (main)" [Wishlist,New]10:30
mvoasac: hrm, I blew away my image with the nm settings, what was the magic to tell it to do a dhcp connection again? I think you had it on your server in tmp somewhere10:30
seb128cassidy: I trust you guys to follow on issues due to updates, synced10:31
asacseb128: gave input on how to do that10:31
seb128asac: thanks10:31
cassidyseb128: thanks. I want it working and think for now we still have time to sync version10:32
cassidyseb128: FYI, I created a small script generating http://people.collabora.co.uk/~cassidy/tp-versions.html10:32
seb128cassidy: right before beta is still fine10:32
seb128cassidy: do you need some other syncs on this list?10:33
asacmvo: http://people.ubuntu.com/~asac/tmp/mvodhcp10:33
asacmvo: put that in /etc/NetworkManager/system-connec*/10:33
cassidyseb128: Salut would be good if we care about file transfer https://bugs.edge.launchpad.net/ubuntu/+source/telepathy-salut/+bug/33307010:33
ubottuUbuntu bug 333070 in telepathy-salut "Please sync telepathy-salut 0.3.8-1 (universe) from Debian unstable (main)" [Wishlist,Incomplete]10:33
seb128cassidy: synced10:34
cassidyseb128: great, thanks10:35
cassidyseb128: what's the deadline until which we can push new versions btw?10:35
mvoasac: excellent, thanks a lot10:35
seb128cassidy: syncing -glib too10:35
seb128cassidy: one month ago? ;-)10:36
mvoasac: I'm building new images now, lets see how it goes10:36
seb128cassidy: beta is in 2 weeks, so you still have until end of next week for reasonable changes I would say10:36
cassidyseb128: right but in practice :)  I guess the TP stack is a bit different as it's basically use only by Empathy atm10:36
cassidyok10:37
seb128cassidy: right, that'w why I'm doing syncs now without asking too much10:37
cassidyand we did lot of audio/video stabilizing work these last weeks so it would a shame to miss them in Jaunty10:37
seb128cassidy: but still we are past the freeze and beta is a good time to stop getting new versions10:37
cassidyok. I'll try to make some tests with current jaunty packages10:38
seb128cassidy: do you want telepathy-python 0.15.7 too?10:38
seb128cassidy: so we can get your list back to mostly green ;-)10:38
cassidylet me check the release ntoes10:39
cassidyseb128: yeah, it's a safe and good to have one10:39
seb128cassidy: ok, syncs done, now get the current empathy version in jaunty ;-)10:43
Zdra\o/10:43
cassidyseb128: yep, I'll ask to bigon to merge the pacakge10:43
seb128thanks10:43
asacseb128: i think I will upload the simple default for subpixel now so we get it on alpha CD (and see how many complain) ... the other big fix i will put in some PPA the other day.10:50
seb128asac: oh good idea I wanted to ping you about that yesterday and forgot, thanks10:50
asacshout if you disagree ;) (e.g. greyscale vs. rgba in gnome-settings-daemon font schema)10:50
asacok10:50
seb128asac: just add a .gconf-defaults to gnome-settings-daemon10:52
asacseb128: hmm. i wanted to do something like this: # asac:Communicate with Mozilla upstream that they should start responding:done10:54
asacoops ;)10:54
asacsomeone fix paste10:54
asacseb128: http://pastebin.com/f4f60f27e10:54
seb128asac: right, that's why I wrote to use a .gconf-defaults, they are made for that10:55
seb128asac: echo "/desktop/gnome/font_rendering/antialiasing rgba" > debian/gnome-settings-daemon.gconf-default10:55
seb128asac: echo "/desktop/gnome/font_rendering/antialiasing rgba" > debian/gnome-settings-daemon.gconf-defaults10:55
asacoh10:56
seb128asac: dh_gconf does the installation, registration etc10:56
asacnice10:56
* asac reverts stuff10:56
seb128asac: ls /usr/share/gconf/defaults for some example10:56
seb128asac: that allow use to have a "clean upstream" set of default and an another layer with distro changes10:57
seb128use -> us10:57
asacyes, I see the benefit. didnt know about that hook10:57
pittitedg: *hug* @ bug 33981810:58
ubottuLaunchpad bug 339818 in indicator-applet "do not display tray handle, but add back standard right-click menu" [Medium,Confirmed] https://launchpad.net/bugs/33981810:58
seb128pitti: ;-)10:58
seb128pitti: retracer crashed, good update ;-)11:17
pittiseb128: I'm just updating right now11:20
pittiadded deb-src, too11:20
* seb128 hugs pitti11:20
cassidyseb128: thanks to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474053  most of the packages FTBFS :(11:25
ubottuDebian bug 474053 in python2.5-minimal "python2.5-minimal: looks like Python 2.5, but isn't" [Normal,Open]11:25
seb128cassidy: shouldn't those build-depends on python2.5 then?11:26
loolasac: Just commented on the moz bug (was travelling yesterday evening; just came at the oxford sprint)11:27
cassidyseb128: don't know. I'm just an upstream dev. :)  bigon: ^11:27
bigoncassidy: rohh11:27
bigonI'm fixing tp-farsight right now11:28
asaclool: oxford sprint?11:28
asaclool: no problem ;)11:28
cassidybigon: what's the right fix?11:28
bigons/site-packages/*-packages11:28
bigonI think it's the thing to do11:29
seb128right11:31
bigonrahh xchat has crashed11:31
loolasac: The QA Desktop Automation sprint11:32
pittiseb128: retracers updated and unlocked; shoul be fixed for good now, hopefully11:33
seb128pitti: you rock!11:34
seb128lool: automatic bugs fixing? ;-)11:34
loolseb128: Press reboot!11:35
loolHmm no11:35
pittimvo: bwah, I lost my window decorations after latest dist-upgrade (new compiz)11:36
pittimvo: known problem already? or shall I file a bug?11:36
mvopitti: do you have compiz (the meta-package) still installed? there was a transient problem during the upgrade11:37
pitti. o O { wow, metacity feels fast }11:37
asacthe inability to stack notifications is really annoying if you get many notifications11:38
asace.g. add a search in gwibber on "Ubuntu" in twitter and you will constantly see notifications ;)11:38
asacnot sure if it would be better if they get stacked ;)11:39
pittimvo: oops, indeed not11:41
pitti  compiz: Hängt ab: compiz-gnome soll aber nicht installiert werden11:42
pitti          Hängt ab: libcompizconfig0 (>= 0.8.2) soll aber nicht installiert werden11:42
pittimvo: ^11:42
asacich haenge auch immer ab ;)11:42
mvopitti: oh? is your mirror up-to-date, that should be fine11:42
mvohaha@asac11:42
pittimvo: well, as up to date as archive.u.c. can be..11:42
* pitti hugs assasc11:42
pittiand asac, too11:42
* asac hugs all ;)11:42
* pitti hugs the German mafia11:43
* mvo scratches his head11:43
mvopitti: maybe because of the new libprotobuf3 dependency? but you have universe enabled, right?11:44
didrocksseb128: pidgin seems to build successfully with no change. I will give some basic tests this evening in intrepid (without ICQ) before giving it to you for ICQ testing.11:45
didrocks(it builds on both intrepid & hardy)11:46
seb128didrocks: ok11:46
seb128didrocks: "with no change"?11:46
didrocksseb128: yep, just backporting it (I saw that there is already one backported version in hardy for 2.5.2)11:47
seb128ah ok, good11:47
pittiwhat's ls -l /etc/fuse.conf for you guys?11:48
pittiand are you in the "fuse" group?11:49
pittiand do you have ~/.gvfs mounted and gvfs-fuse-daemon running?11:49
seb128didrocks: I'm fine doing build and test this afternoon if you want, I've access to my hardy and intrepid install easily today but not this evening11:49
seb128didrocks: and I've nothing special to do due to alpha freeze11:49
asacpitti: yes. i am in fuse group11:49
pittihm, anyone who is *not* in the fuse group?11:50
seb128no11:50
asaclet me check my other system11:50
pittihmm11:50
didrocksseb128: ok, let me push the branch somewhere if it's easier for you, (ok, that's a little bit overkill for only a changelog change ;))11:50
pittiah, it seems the permissions of /etc/fuse.conf don't atually matter11:50
seb128pitti: I can start a test user if you want11:50
asacpitti: yes11:50
asacpitti: my other system isnt in fuse11:50
pittimy unmounted ~/.gvfs was not writable for me, so I couldn't mount11:50
seb128didrocks: only a changelog log? there is no code change, what fixes the bug?11:50
pittithat was the reason why gvfs-fuse-daemon didn't start, not the /etc/fuse.conf permissions11:50
asacbut i logged in through ssh (i doubt that this matters)11:51
pittiasac: ok, thanks11:51
didrocksseb128: I just rebuilt the last version (1:2.5.5-1ubuntu1) against a hardy and intrepid chroot. I thought we just wanted to backport it, not doing a update (maybe I was not clear enough in my previous sentence)11:52
didrocksbut if you prefer, we can prepare a proper update and cherry picking the fix11:52
seb128didrocks: we want to backport the code change which fixes that specific issue11:52
seb128didrocks: not to update hardy to 2.5.511:52
didrocksseb128: ok. because that what was done in hardy-backports already (they have 2.5.2 although hardy is at 2.4.1), so, people who uses backport will not have the fix11:53
seb128didrocks: backport is not my issue, I want to get those fixes to -updates, everybody doesn't use backports11:54
seb128didrocks: I consider backport as crack usually ;-)11:54
didrocksseb128: ok, I was mislead by the "backport" term used there lately :)11:54
seb128pitti: retracer crashed again11:54
didrocksseb128: I am on it right now :)11:54
seb128didrocks: thanks!11:54
seb128pitti: oh, new error11:55
seb128pitti: seems an apport bug now11:55
asacmvo: compiz somehow makes firefox 3.1 and trunk behave bad. seems that XQueryTree gives error:11:58
asacThe error was 'BadWindow (invalid Window parameter)'. (Details: serial 1247 error_code 3 request_code 20 minor_code 0)11:58
asacmvo: takes about 20 seconds to go away ... feels like it doesnt remove a not existing window instantly when proces goes away11:58
pittiseb128: bwaaah, my stupidity12:01
pittiseb128: will fix in a bit12:01
seb128thanks12:02
didrocksseb128: I will do it this evening. Unfortunately, my company firewall prevents me to go to pidgin.im website (I wanted to follow the commits and to search through the bugtracker)12:03
seb128didrocks: ok12:04
pittiseb128: fixed locally in i386 retracer, restarted, committed to trunk12:07
kenvandine_wkpitti: python-mechanized was fun :)12:07
mvoasac: how can I reproduce this?12:08
pittikenvandine_wk: oh indeed; took me a while to figure it out, too12:08
kenvandine_wk:)12:08
kenvandine_wkmakes me feel a little better :)12:08
kenvandine_wkand your fix is of course better than mine12:08
kenvandine_wkbut i am glad i got as far as i did with it :)12:08
asacmvo: install firefox-3.1 from universe should work12:09
asacthen run firefox-3.112:09
asacstop it12:09
asacthen start it again and see the error12:09
seb128pitti: danke12:10
asacmvo: 3.1 uses its own profile so you can safely use it in parallel12:10
mvoasac: thanks, doing that now12:13
mvostop it as in click on "file/quit" ?12:13
mvoor close it via the decoartions?12:13
asacmvo: doesnt matter i think12:13
asacmvo: just stop it regularly or even thorugh ctrl-c12:13
asacmvo: i probably can trap the error and loop till it works, but that would be a bad hack and i dont know how long to loop ;) (1 minute?)12:14
mvoasac: gehh, ff-3.1 is pretty heavy on io, brings my machine to a crawl here :/12:20
asacmvo: interesting. consider to stop ffox 3 first ;)?12:23
asacmvo: also ffox 3.1 copies your whole ffox 3.0 profile on first start. so if thats huge it might be the cp12:24
mvoasac: yeah, thats it probably12:25
seb128didrocks: http://download.gnome.org/sources/pangomm/2.24/pangomm-2.24.0.tar.gz is yours12:35
kenvandine_wkseb128: libgtop is still waiting to be sponsored12:35
kenvandine_wkseb128: i am anxious for feedback... see if i did things right :)12:36
seb128kenvandine_wk: right, I've been swamped in other tasks sorry and now main is soft frozen for alpha612:36
kenvandine_wkok12:37
seb128kenvandine_wk: I will let you know when I've a look later today or tomorrow12:37
kenvandine_wknp12:37
kenvandine_wkseb128: can i have another gnome pacakge to bump?12:37
seb128kenvandine_wk: there is no so many updates right now, new GNOME due next week, you can do http://download.gnome.org/sources/libgda/3.99/libgda-3.99.13.tar.gz (and http://download.gnome.org/sources/libgdamm/3.99/libgdamm-3.99.13.tar.gz) if huats is not doing those already12:38
seb128didrocks: do you know if huats is doing any ubuntu work atm or started on the libgda update?12:38
kenvandine_wkseb128: ok, thx12:38
seb128kenvandine_wk: do you know if the ekiga guys aim 3.2 or something for 2.26?12:39
kenvandine_wkseb128: i don't know... they are usually off the gnome schedule12:40
seb128we have 3.0 and there is some new 3.1 tarballs12:40
seb128dunno if we should do the updates for jaunty12:40
seb128can you try to figure about that?12:40
kenvandine_wkseb128: sure12:40
seb128thanks12:41
mvoasac: hm, I can not reproduce it, I open/close it and its about as fast to open as before12:41
pittididrocks: ah, bug 340151 just got a patch12:42
ubottuLaunchpad bug 340151 in pidgin "ICQ protocol update [March 2009]" [High,Fix released] https://launchpad.net/bugs/34015112:42
seb128didrocks, pitti: ^ I will give a try to the hardy and intrepid backports now, I've access to computer with those versions right now and nothing special to do due to the freeze12:43
asacmvo: hmm12:43
asacmvo: which version is it?12:43
* pitti hugs seb12812:44
* seb128 hugs pitti back12:44
pittiseb128: you mean backports of the patch?12:44
asacmvo: try to killall -KILL firefox-3.1 to stop it ... maybe that helps to reproduce it12:44
seb128pitti: I mean sru updates with this changeset applied12:45
pittiright12:45
* seb128 knows how to do a sru don't worry ;-)12:45
pittiseb128: right, I thought you'd prepare *-backports12:45
seb128no, I don't touch those12:46
seb128I still consider backport as crack ;-)12:46
asacmvo: if not i will have to check code. maybe you need multiple profiles or something to hit the XQueryTree code involved here12:47
asacits arguably low prio. except that i fear this will happen on upstream builds when they release 3.112:48
mvoasac: right, not sure if I hit it or not, it takes some seconds to start, but strace shows it doing a lot of $stuff with sqlite12:48
asacmvo: if it starts you dont hit the bug12:49
asacmvo: it will just abort12:49
asace.g. symptoms are: you cannot start firefox for 20-40 seconds after stopping it12:49
asacmvo: it will always bail out with the BadWindow error from above12:49
mvoasac: aha, ok. no that did not happen12:50
asacmvo: its not even 20-40 seconds. now it doesnt start at all anymore here ;) ... anyway. i will check code12:50
sivanghi all12:54
sivangis there anywhere to read about the current state of notification stuff and where help is needed?12:55
asacsivang: what kind of help?12:56
sivangasac: well, do you require any? I read sabdfl 's posts about new notification framework and he suggested there work is needed to put things in place. I'm curious to see if I can help and explore where.12:58
seb128ask on #dx12:59
seb128there is a wiki page about that12:59
sivanghi seb128 ! thanks13:00
sivangseb128: what is 'dx' ?13:02
seb128desktop experience, the team working on those changes13:02
seb128didrocks: there?13:13
didrocksseb128: yep, not for too long, but there :)13:31
seb128didrocks: I'm doing a testbuild on intrepid with the pidgin change pointed on the bug13:32
seb128didrocks: I will let you know if that works if you still want to do the sru uploads13:32
didrocksseb128: he basically backport the new version, what I have done, no?13:34
didrocksok, ok, there is a patch13:34
seb128didrocks: no, there is one comment pointing an upstream changeset13:34
didrocksseb128: yep I saw it now, keep me in touch, thanks :)13:34
seb128you're welcome13:34
seb128hum13:42
seb128pitti:13:42
seb128"    raise IOError, "The importance of this bug can't be edited, maybe because this bug is a duplicate of an other one""13:42
seb128I guess the retracer will not pick that bug again?13:43
* seb128 rm lock13:43
seb128didrocks: I can confirm that the change works on intrepid and apply cleanly14:01
didrocksseb128: ok, do you want I do a clean package with it?14:04
seb128didrocks: do you want to do it or should I just upload my version?14:05
pittiseb128: huh, weird; if it gets stuck, please poke me14:06
seb128pitti: no news since, seems to be working ;-)14:07
pittiphew14:08
pittinot much luck with apport recently..14:08
seb128vuntz: there?14:10
mvoasac: hm, the restart in postinst did not really help :/14:12
mvoasac: I check a bit further, but its not enough of a workaround14:12
asacmvo: when is the interface torn down now?14:12
didrocksseb128: as you wish. I can handle it, but if it's just extra work for you, you can do it now :)14:13
mvoasac: the ssh from the virtual machine stopped, I'm checking whats going on now14:13
asacmvo: so the syslog hopefully stopped when this happened14:13
mvoasac: yes, network interface is gone14:13
asacmvo: plesae capture it before the iface comes up14:13
asacmvo: the last log was not really informative about the reason, but maybe just because i failed to spot the time when things go wrong14:14
seb128didrocks: when will you do it? I don't really care either way but that would be nice to get that uploaded today ;-)14:14
asacseb128: how can i disable DEBUG for x-session-manager?14:14
asacall my syslog is flooded with that now ;)14:14
seb128asac: wait for 2.26 or rebuild it14:14
seb1282.26 is due next week14:15
asacseb128: ok14:15
didrocksseb128: let's say it's done at 6PM14:17
seb128didrocks: ok excellent thanks14:17
didrocks(sorry for the delay, I am in a meeting right now)14:17
mvoasac: hm, the log looks interessting14:17
mvohttp://paste.ubuntu.com/129329/14:17
asaclet me look14:20
seb128pitti: do you remember the specifics about f-spot import?14:23
asacmvo: so does the time of the hal reappearing really match the time when hal postinst is run?14:23
seb128pitti: nautilus is calling it using the .gvfs fuse path right now14:23
asacmvo: or maybe something else triggers this?14:23
seb128pitti: do we want to disable that and use the gphoto uri rather?14:23
pittiseb128: I thought we already did that, because gvfs was so slow (especially with thumbnails)14:24
asacmvo: i mean: reason 36 just means that the device has been removed. so hal probably doesnt have that device after coming up14:24
mvoasac: hm14:24
asacmvo: which probably will make us come back to the bogus lshal output with just 3 devices14:24
asacas the root cause of the bug14:24
seb128pitti: well it's currently using fuse in jaunty, I've a fix I just wanted to check with you before uploading14:24
pittiseb128: the other day, David was reasoning about thumbnail support in gvfs14:24
pittiif that's there now, why not14:25
pittiseb128: I can't test it right now, I'm afraid; I gave my camera to my wife, and she's in Italy this week14:25
seb128pitti: glib understand X-GIO-NoFuse keys in desktop files now14:25
asacmvo: one theory would be that udev was unpacked before and then something triggers event registration14:25
pittiseb128: what kind of magic does that do?14:25
seb128pitti: I've just tested, adding that to the .desktop makes it work14:25
asacmvo: and new udev needs new kernel or whatever. mysterious14:26
seb128pitti: it just tells glib to not pass the fuse path when %u or %U is used14:26
pittiseb128: "work" -> it supplies the gvfs path instead of the fuse path?14:26
pittiah, nice14:26
seb128yes14:26
asacmvo: for now i would really like to know if its hal that restarts hal at that time or something else ;)14:26
mvoasac: you are right, its hal triggers that generate the restarts14:31
mvoasac: at points where udev is unpacked but not configured14:31
pittimvo: oh, you are saying that some package installs an .fdi, and the hal package trigger is called at a point where hal isn't configured yet?14:48
pittithat sounds very strange to me14:49
mvopitti: yes14:49
pittiI thought triggers would run after all pckages are configured14:49
mvopitti: eh, I wanted to say at a point where udev is not configured14:49
pittihm, hal is configured, but not udev?14:49
mvoduring the last test I did lshal return really strange output in the middle of a upgrade14:49
pittibut hal depends on udev...14:49
mvojust 3 device14:49
pittimvo: if hal was not running during that time, then I think we can just fix the trigger to not restart hal if it isn't running14:50
pittithe main part of the trigger is to delete the fdi cche14:50
pitticache14:50
mvopitti: hal is running at this point (the old version)14:51
mvothe trouble seems to be that the restart causes it to get incorrect devices and then it thinks the network device disappared14:51
pittimvo: hm, I think I know too little about the origial problem to understand it properly14:51
mvopitti: we (asac and I) are in the middle of diagnosing it, there is no real understanding yet what the actual problem is :/14:51
pittimvo: but ideally, the trigger would be deferred util after all packages got configured14:52
mvopitti: but the issue at hand is that network manager kills network interfaces during a upgrade14:52
mvoand we would like it not to do that (or if it does, for as short as possible)14:52
asacmvo: sorry was on a call14:54
asacmvo: so is it udev trigger?14:54
mvoasac: no, hal trigger (old version)14:54
asacmvo: oh. so its coming from the intrepid package? that sound bad14:54
asacmvo: did you see which package runs the hal trigger thing?14:55
rickspencer3pitti: our team meeting is too late for folks in  capetown14:56
pittirickspencer3: no problem14:56
asacrickspencer3: capetown is in almost the same timezone that we are14:57
mvoasac: no, but let me try a (crude) workaround14:57
asacrickspencer3: at least i think they are just a week off14:57
asacan hour ;)14:57
rickspencer3asac: yeah, well, they have dinner meetings and such after the sprint14:57
asacok ;)14:58
asacmvo: so you want to hack the hal init script?14:58
mvoasac: just temporarely to see if that fixes the problem or triggers (haha) a new one15:00
vuntzseb128: pong15:04
seb128vuntz: hey15:04
seb128vuntz: gnome-desktop-edit-item doesn't create +x desktop so launchers are unsecure according to nautilus standards15:05
seb128vuntz: that's a known issue? will you fix for 2.26? do you want a bug?15:05
vuntzseb128: that was unknown, but it should be fixed for 2.26, yes15:06
seb128vuntz: do you want a bug? alex said you were supposed to work on that15:06
rickspencer3kenvandine_wk: tkamppeter: seb128: the desktop team meeting is scheduled for one hour and twenty-four minutes from now, right?15:07
rickspencer3(we already changed to daylight savings time, and it scrambled my calendar a bit)15:07
seb128rickspencer3: twenty-three minutes according to my clock15:07
seb128;-)15:07
asacrickspencer3: i would think its scheduled for in 23 minutes15:07
asacack15:07
rickspencer3*sigh*15:07
asaclet me look in calendar15:07
pittiack15:07
seb1281h23min15:07
seb128just to be clear15:07
rickspencer3seb128: thanks15:08
seb128np15:08
rickspencer3actually 1h22min15:08
rickspencer3:)15:08
seb128heh15:08
vuntzseb128: feel free to open a bug and make it a blocker15:08
pitti1630 UTC15:08
pittirickspencer3: ^15:08
seb128vuntz: ok15:08
pittii. e. in 82 mins, yes15:08
rickspencer3heh15:08
asacack 81 minutes :-P15:08
kenvandine_wkrickspencer3: oh... good point :)15:08
rickspencer3pitti: seb128: thanks for catching and following up on the MI problems15:09
kenvandine_wki forgot that... i i can eat lunch on time :)15:09
seb128rickspencer3: np15:09
rickspencer3great work15:09
seb128vuntz: gnome-desktop or gnome-panel bug?15:09
vuntzseb128: panel15:09
seb128pitti: ok, camera import working fine for me again in jaunty, one icon displayed only by gvfs and f-spot import correctly15:21
pittiseb128: hurray15:22
mvoexcellent news :)15:25
tkamppeterrickspencer3, yes, it is.15:27
mvoasac: hrm, so I now deteted the (old) triggers file in my test upgrade, but this did not help, the same problem, just 2 devices15:30
asacmvo: is udev unpacked by then?15:33
mvoyes15:38
mvounpacked but not configured15:38
asacmvo: i would guess its udev then15:40
* kenvandine_wk -> lunch15:41
asacmvo: most likely hacked to death to tune boot time15:41
asacmvo: grepping through udev: ./udev/udevd.c:inotify_add_watch(inotify_fd, SYSCONFDIR "/udev/rules.d",15:46
asacso probably the new rules cause issues when unpacked15:46
pittithat's to load new rules15:46
pittibut they only do something when a new device appears15:46
pittior changes15:46
asacmvo: another idea would be to try to stop hal right in the beginning and then take care that it never comes up again until its finished?15:49
asaci mean as long as hal doesnt reappear in this broken state all should be fine. i can use NM happily with hal stopped15:51
mvoasac: hm, interessting idea, to just not let it restart in release upgrades15:53
asacmvo: well. in the end i would like to find the root cause. something must trigger hal or udev15:55
asacand we should prevent that15:55
seb128pitti: the amd64 retracer crashed on the same "ups" bug you fixed in trunk and i386 some hours ago16:05
pittiseb128: ok; I'll do an upload later today, and ensure it gets rolled out16:06
pittiseb128: do you think it's urgent to fix it?16:06
pittiI was too lazy to manually fix the chroot16:06
Amaranthmesa needs to not be as good16:13
AmaranthI liked it better when it didn't implement everything so software wouldn't think you've got hardware accel16:14
pittiheh16:15
seb128pitti: no16:16
seb128pitti: the amd64 was running normally for days so there is no catchup to do on this one16:16
pittiok, what I thought16:17
cjAmaranth: we're living in difficult times16:19
cjnice to have a complete fallback, though :)16:19
cjseb128: you know if y'all have found a candidate for the opengl position yet?  I see it's still open on the jobs page.  I'd sure like to have a job where I could hack on that stuff as a day job.  Weekends don't provide enough contiguous time to get much done...16:21
asacpitti: err, since when does apport close bugs on its own?16:22
asac33885116:22
asacAI ;)16:22
pittiasac: it has done that for a couple of weeks already, for outdated reports16:22
pittiI got lots of complaints of those reports being useless16:23
asacpitti: well the one above was submitted my mvo a few days ago16:23
seb128cj: no idea, talk to davidbarth about that16:23
cjseb128: alrighty.  thanks.16:23
pittiasac: well, stack trace is useless..16:23
pittiasac: do you want apport to keep them open?16:24
pittiasac: I can add a kind of "don't invalidate reports" whitelist16:24
asacpitti: yeah. i think its ok in general. just wonder if i missed an annonucement about that or something (because i was confused that i couldnt find his bug anymore ;))16:24
seb128asac: we crawl under incomplete crash bugs16:24
pittiseb128: ITYM "drown" :)16:24
seb128pitti: thanks ;-)16:24
asacpitti: no no ... just close ;) for me crashes as bugs has always been kind of wrong ;)16:25
seb128asac: the idea was to only keep those which are useful16:25
pittiasac: *phew* :)16:25
asacseb128: good idea and i am completely supportive16:25
seb128good ;-)16:25
pittiI tried to be nice in the close message16:25
asacits just that i think some backtraces have some ?? in it for firefox16:26
pittibut of course, a bot closing those bugs is always better than having it yourself16:26
pittiless bad conscience :)16:26
pittiasac: that's fine16:26
asacand still seem to be correct. havent checked if the heuristic properly catches tem16:26
pittiasac: it has three stages16:26
pittiasac: "perfect" -> no ??16:26
pittiasac: "useful" -> more than half of frames have function names16:26
pittiasac: "useless" -> rest16:26
pittito be precise16:27
pitti    def has_useful_stacktrace(self):16:27
pitti        if len(unknown_fn) < 3:16:27
pitti            return unknown_fn.count(True) == 016:27
pitti        return unknown_fn.count(True) <= len(unknown_fn)/2.16:27
Amaranthcj: do you really have the source code from your a modeler you made in 1999?16:27
Amaranths/your//16:27
cjAmaranth: yes, but I just moved all the servers.  I can put up a tarball if you want it16:28
asacpitti: err. what does count(True) do?16:28
Amaranthcj: nah, just impressed16:28
AmaranthI would have tossed it16:29
Amaranthor lost it16:29
cjAmaranth: I'm pretty good about keeping track of that stuff.  I also have all of my email since then.16:29
rickspencer3desktop team meeting in  1 minute!16:29
* cj takes position as fly on wall16:29
mvoasac: so my crash report does not contain anything useful?16:29
mvohmm16:29
pittiasac: the number of Trues in the unknown_fn list16:29
asacmvo: seems not. you could try to retrace it manually locally16:29
seb128mvo: versions might have changed between report and retracing ...16:29
pittiasac: don't worry, that's implementation detail16:29
asacmvo: in the same system16:30
pittiasac: it says "if the stack trace is shorter than 3, all functions need to be known"16:30
asacpitti: ah so unknown_fn is a list of booleans16:30
asacok16:30
rickspencer3https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-03-1016:30
ArneGoetjeHi all16:30
pittiasac: and if it's >= 3 and <= 5, at least half of them need to be known16:30
pittiasac: right16:30
seb128hey rickspencer316:30
pittiasac:         unknown_fn = [f.startswith('??') for f in self['StacktraceTop'].splitlines()]16:30
rickspencer3I think Riddell is traveling back from Nigeria today16:30
asacpitti: yeah. thought unknown was a filtered list and not a boolean indiciation thing16:30
seb128*** MEETING ***16:30
calchi16:31
rickspencer3hi calc16:31
bryce_hi16:31
tkamppeterhi16:31
pittirickspencer3: wow, no other outstanding items? nice16:31
rickspencer3kenvandine_wk: ?16:31
rickspencer3still having lunch :)16:31
rickspencer3ready to go?16:31
asacyes16:31
rickspencer3from last meeting, there was only one action: ACTION: rickspencer3 to post ideas from last week to the marketing team's wiki page.16:32
rickspencer3this is done16:32
rickspencer3feel free to add more16:32
kenvandinerickspencer3: i'm here16:32
rickspencer3pitti: had a three agenda items, which I think were related16:32
pittiright, but we discussed them with the DX team already16:32
asacrickspencer3: where is the marketing wiki page again?16:32
rickspencer3Indicator applet woes, MI bugs. I don't get any pidgin messages16:32
pittiso, as a summary, the current state of MI leaves several things to be desired16:33
pittiI'll convert the remaining ones to bug reports16:33
pittiso from my POV we can skip this now16:33
rickspencer3ok16:33
rickspencer3asac: internal wiki - https://wiki.canonical.com/Marketing/Launches/9.04/Messaging16:33
rickspencer3moving on then16:34
asacthx16:34
pittiI wasn't sure what *should* happen for pidgin messages16:34
rickspencer39.10 planning process16:34
rickspencer3this is just an fyi16:34
rickspencer3We (the platform team) are hosting a series of meetings with other canonical teams, called road map meetings. Some of you may be booked into one or two of them. There are 22 altogether. This will be very good fodder for UDS.16:34
rickspencer3that's 22 for the desktop team! though some meetings are only 15 minutes16:34
pitti22 for the desktop team, right?16:34
rickspencer3next item is all hands16:35
* pitti can contribute two16:35
rickspencer3everyone has submitted a talk for all hands, right?16:35
seb1281 or 2 or 5 ;-)16:35
kenvandinerickspencer3: i will today :)16:35
pittiseb128: 5 hands?16:35
kenvandinehaha16:35
rickspencer3a little zaphod beeblebrox action?16:35
* seb128 slaps pitti16:35
ArneGoetjeI did already16:35
rickspencer3three hands?16:35
rickspencer3asac: ?16:36
pittiI have two now16:36
pitti(talks)16:36
calcrickspencer3: i need to send mine in still, any suggestions for what i should do (anyone)?16:36
seb128rickspencer3: is that mandatory?16:36
asacrickspencer3: me and mvo and brian are doing a talk.i think there was a miscommunication who should submit that16:36
seb128the allhand talks16:36
asacrickspencer3: as we found out today. so we will do that now ;)16:36
rickspencer3seb128: this is one of the rare cases where I will say that something is mandatory16:36
pitticalc: personally I'd be interested in an "on par" feature comparison between current MS Office and OO.o16:36
rickspencer3mandatory to submit, obviously16:37
pitticalc: and a pony :)16:37
rickspencer3at least one16:37
calcpitti: heh16:37
seb128hum, I've no clue what to talk about16:37
mvoseb128: efficient bug triage16:37
pittiseb128: "how to deal with 2304823049320432 bugs every day" :)16:37
rickspencer3calc: besides the pony, also I think many people may be interested in how OO is released, the deal with Sun and Go OO16:37
* pitti ^5s mvo16:37
calcok16:37
rickspencer3seb128: yes, exactly16:37
mvoseb128: crash diagnosinis, valgrind16:37
rickspencer3what they said16:37
pittimvo: that's my talk already, though :)16:37
mvooh :)16:38
asacpitti: you can do that with seb128 together16:38
asac;)16:38
seb128pitti is already doing that?16:38
pittibut I have 50% presentation and 50% discussion with audience16:38
mvoseb128: valgrind is probably a good idea16:38
rickspencer3you guys can team up, and show different ways of doing bug management16:38
pittithat was my idea16:38
pittipresent how I handle them, collect experience from others16:38
pittiand in the end sum it up in a "best practices" wiki page16:38
asaci would appreciate to get pitti and seb128 on the stage in that talk, really16:38
seb128I can do one on GNOME regular schedules and how we handle updates otherwise I guess16:38
* kenvandine makes a note to attend pitti's talk16:38
rickspencer3calc: OO, and your job, are very important to the company and to our users, I think there would be a lot of interest in hearing what interests *you* about OO16:38
calcok16:39
rickspencer3new deadline to submit is March 13th16:39
pitticalc: or, "cool features unique to OO.o" perhaps?16:39
* rickspencer3 whip cracking noises16:39
calcyea friday the 13th :)16:39
pittihehe16:39
kenvandinenice16:39
rickspencer3for those of you who have already submitted, the track leads are reviewing and will let us know what topics are accepted.16:39
rickspencer3(I should create a whip cracking noises plugin for pidgin)16:40
rickspencer3any more questions regarding all hands?16:40
rickspencer3moving on then ...16:40
rickspencer3release status16:40
pittihttps://wiki.ubuntu.com/DesktopTeam/ReleaseStatus16:41
pittiI don't really envy bryce_ ..16:41
rickspencer3looks like our RC list has grown quite a bit :(16:41
bryce_:-/16:41
pittianyway, I believe we won't be able to fix each and every X.org bug/regression, so we should think about fallback plans16:41
calci think we should demote 305790 unless someone knows how to backport just the code changes to fix jaxme16:41
pittirickspencer3: grown> partly my fault; I went through the jaunty/milestoned bugs and added proper assignees, and such16:42
calcotherwise the new jaxme which uses maven will pull in a lot of other universe packages due to maven16:42
rickspencer3pitti: ack - but that's very good to know what is really there16:42
pitticalc: what would break in OO.o without jaxme?}16:42
pittirickspencer3: right16:42
rickspencer3bryce_: is there anything we should be doing to help with x?16:42
calcpitti: probably lots of stuff since it is a lower level dep, OOo doesn't use it directly aiui but through libdom4j-java (iirc)16:43
bryce_rickspencer3: do you mean like helping report these bugs upstream?  That could help a lot16:43
pitticalc: if it breaks something important, I'll connect with doko and try to help out16:43
asaccalc: what is jaxme?16:43
calcasac: some sort of java xml compiler16:44
bryce_most of the bugs on this list are already on progress, we're just waiting for someone external to finish doing fixes16:44
asaccalc: yeah. seems like its xml bindings16:44
kenvandinecalc: probably breaks the docs?16:45
calcpitti: i think it would break search among other things16:45
pitticalc: ugh, let's not then16:45
bryce_hmm, 2328035  is not a real bug... is that a typo?16:45
calcpitti: since libsaxonb-java -> libdom4j-java -> libjaxme-java16:45
pittibryce_: yeah, just trying to figure out the correct number; I saw it, but typoed16:45
calcpitti: its so interconnected it might break just about all of OOo's java bits, heh16:46
bryce_seems to be 32803516:46
calcpitti: it also is depended on by libjaxen which in turn is by libxom-java, etc16:46
pittibryce_: it's bug 32803516:47
bryce_ok, that one we're still waiting on further testing from steve16:47
ubottuLaunchpad bug 328035 in xserver-xorg-video-intel "*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call" [High,Triaged] https://launchpad.net/bugs/32803516:47
pittieek, it detected a glibc!16:47
seb128lol16:47
calcbryce_: i've seen 328035 again since last week but it seems much less common than in the past for some reason16:47
seb128let's uninstall that and see if that fixes the bug ;-)16:47
rickspencer3I'm detecting glibc right now16:47
bryce_267241 I need to set up a system and reproduce; I wrote a patch that I think fixes it, just need to test it to be sure16:48
seb128bug #26724116:48
ubottuLaunchpad bug 267241 in xorg-server "Xorg fails to start with more than one display adapter" [Undecided,Confirmed] https://launchpad.net/bugs/26724116:48
calcwell maybe not 328035 but the intel video crash on resume anyway16:48
pittibryce_: rocking16:48
rickspencer3bryce_: sweet16:48
bryce_rickspencer3: there is one bug I could use seb128's help on though16:48
seb128which one?16:49
bryce_give me a minute to locate it16:49
cjI've got an intel video card in my laptop.  if you need someone to attempt a repro, I've been meaning to test out jaynty anyway.16:49
seb128there is GNOME 2.26 due next week though16:49
seb128so I expect to be busy a lot soon16:49
rickspencer3cj: you should test out Jaunty ... while we are discussing bugs, it's actually in quite good shape imho16:49
rickspencer3seb128: ack16:50
rickspencer3while bryce_ is looking for that bug, may we move on to work items?16:50
calcrickspencer3: the OOo gvfs bug with smb not saving appears to be ooo-build related, it works with sun version, so i filed a novell ooo-build bug about it and will look into the patches that might cause it16:50
pittiseb128: I think kenvandine and I can help with the updates, and I with sponsoring16:50
bryce_bug 67188 - which is actually a whole bunch of unrelated bugs, but we can't debug them because GNOME is hiding the error messages.  So seb128 I need your help solving #328980 first16:51
ubottuLaunchpad bug 67188 in mactel-support ""Error activating XKB configuration." - Requires manual xorg.conf editing" [Undecided,Confirmed] https://launchpad.net/bugs/6718816:51
rickspencer3ug16:51
seb128bryce_: should be easy enough to patch that redirect to null out no?16:51
seb128let's talk about that after the meering16:51
seb128meeting16:51
calcrickspencer3: also caolan (redhat OOo) gave me a hint on what to do that might help make disabling gvfs entirely in OOo work via gvfs fuse16:52
bryce_seb128: ok16:52
rickspencer3calc: sweet16:52
bryce_seb128: I do think it's easy, I am just up to my eyeballs an don't have time to work on it myself16:52
seb128pitti: thanks, we have a good team of contributors nowadays so good part of the work is sponsoring indeed, help on that is appreciated ;-)16:52
seb128bryce_: oh, known feeling ;-)16:52
seb128but it should be easy to get one of those people running into the issue to do a rebuild to get debug informations16:53
rickspencer3calc: I think it might help for you to go over your ideas with a colleague before you dive in. Sometimes a sanity check can really help16:53
bryce_rickspencer3: also I'm waiting on feedback from asac on one of the bugs he reported that I put in a fix for last week.  I'd love to just get his thumb's up so I can upload the fix.16:53
calcrickspencer3: yea seb128 might know something about the fix caolan mentioned :)16:53
asacbryce_: the xhost thing?16:54
pitticalc: is the gvfs fuse daemon working for you, in general? or is that the problem?16:54
pitticalc: I'm asking because it wasn't working for me either, and it took me a bit to find out why16:54
asacbryce_: thumbs up. and no, i really dont think we need to enable tcp16:54
bryce_asac: yep16:54
bryce_asac: great thanks.16:54
calcpitti: fuse works but (i think) i need to convince the file dialog to give OOo the local url instead of the remote uri to the file16:55
asacbryce_: if you want me to verify the fix in practice wait till tomorrow. but i can check that once it arrives here imo16:55
seb128calc: I have difficulties to parse your " that might help make disabling gvfs entirely in OOo work via gvfs fuse"16:55
calcpitti: ie saving to ~/.gvfs/foo inside OOo works, but clicking the left side gvfs mount does not16:55
calcseb128: i tried disabling gvfs in OOo and have it fall back to using fuse support only, but that doesn't work since it appears it is giving remote uri's to internal OOo via its file dialog still16:56
seb128calc: does ooffice tries to use gvfs uris or does it rely on the fuse mounts?16:56
calcseb128: caolan mentioned gtk_file_chooser_set_local_only might make it use the fuse urls16:56
seb128right16:56
calcif that does work i just need to determine where to stick that line :)16:56
calci just got that email this morning so haven't had a chance to dig around in it yet16:57
* kenvandine has a crashy desktop he needs to collect info for and file a bug16:57
kenvandinehard lock right before the meeting started16:57
calci think relying on fuse would be much better than trying to use the gvfs/gio support in OOo anyway since it appears to be very buggy in general16:57
seb128do you switch users or use guest session?16:57
asackenvandine: like the mouse worked, but was in kind of "select" text mode?16:57
kenvandinenot that bug16:57
asack16:57
kenvandinei have seen that too16:57
kenvandineseb128: and when i switch users Xorg crashes16:58
rickspencer3so, good discussion, and actions to take out of the bug conversation?16:58
seb128calc: gvfs is not that buggy, the ooffice use of it might be16:58
kenvandineknown bugs16:58
calcseb128: yea sorry if that parsed wrong, the gvfs/gio support in OOo is the buggy bit16:58
pitticalc: *nod*16:58
calci think i got the parts of gvfs fuse that were causing problems for OOo resolved with gvfs 1.1.816:59
rickspencer3is someone going to try to get more debugging info for bug 67188?16:59
ubottuLaunchpad bug 67188 in mactel-support ""Error activating XKB configuration." - Requires manual xorg.conf editing" [Undecided,Confirmed] https://launchpad.net/bugs/6718816:59
seb128calc: ok good so let's do that16:59
asacrickspencer3: bryce_ talked about that above16:59
seb128rickspencer3: I will discuss that was bryce_ after the meeting16:59
rickspencer3asac: yeah, but I didn't see an action16:59
bryce_asac: your xauth fix is uploaded now16:59
rickspencer3seb128: ok16:59
calcseb128: yep will do, just need to patch it to see fuse urls and then it will be good to go :)16:59
asacbryce_: thanks. i will check the hostname changes toomrrow17:00
rickspencer3ACTION : seb128 and bryce_ to work on getting more debugging info for bug 6718817:00
ubottuLaunchpad bug 67188 in mactel-support ""Error activating XKB configuration." - Requires manual xorg.conf editing" [Undecided,Confirmed] https://launchpad.net/bugs/6718817:00
rickspencer3shall we move on to the work items?17:00
asacyes. please.17:00
seb128yes17:00
calcyes17:00
kenvandineyup17:00
rickspencer3pitti: shall I set these as "done", "postponed"?17:00
rickspencer3pitti:Advice Dx Team Regarding where to store assets such as icon:not started pitti:Advice Dx Team Regarding “Do not disturb systems”:not started17:00
rickspencer3pitti:Advice Dx Team Regarding where to store assets such as icon:not started17:01
rickspencer3pitti:Advice Dx Team Regarding where to store assets such as icon:not started pitti:Advice Dx Team Regarding “Do not disturb systems”:not started17:01
rickspencer3sorry :P17:01
rickspencer3there are two in any case17:01
pittirickspencer3: I still want to talk to ted about those17:01
rickspencer3ok17:01
rickspencer3Riddell is not here, so we'll have to skip his for now17:01
rickspencer3bryce_: should this be postponed? bryce:Support the Dx team by consulting and helping with low level packages.:blocked17:02
bryce_rickspencer3: honestly I don't know what that task is17:02
rickspencer3hehe17:02
rickspencer3ok17:02
bryce_rickspencer3: as far as I know, I have nothing to do there, so mark it done?17:02
rickspencer3bryce_: I think the Dx team wanted help with something, so I'll follow up with them and make sure they are good17:02
bryce_I'm of course happy to help if they need it, but they've not asked for anything17:02
rickspencer3pitti: this should be postponed: pitti:Refactor packages and build system to support moving help files to language packs:blocked17:03
rickspencer3asac:Adobe Flash in partner repository with apturl:started17:03
rickspencer3when should that be "done"?17:03
pittirickspencer3: ack17:04
rickspencer3bryce_: should these be postponed?17:04
asacrickspencer3: we have to do the next step this week. luckily its not really a freeze thing because the technology is already in17:04
rickspencer3bryce:Create X Historical Package Pages:started17:04
rickspencer3bryce:Create X Smoke Tests:started17:04
rickspencer3asac: ack17:04
rickspencer3in general, I think we are in great shape17:04
rickspencer3except for Kubuntu, many of the remaining items are almost done, trivial, or aren't critical for Jaunty17:05
bryce_rickspencer3: okay.  I'd like to get them off the list though.  I just can't seem to find a good solid week or two to work on them.17:05
=== stevel_ is now known as stevel
rickspencer3bryce_: n/p17:06
calcpitti: the libxom-java and libjaxme-java as mentioned before probably need doko to examine them, would you like me to ping him about the issues or do you want to?17:06
calcpitti: the libxom-java case seems to be it fails on buildds but not on developer machines due to a resources issue of some sort17:06
rickspencer3they don't really block Jaunty, right? So we can just postpone them and you can pick them up later17:06
rickspencer3everyone sent an activity report, so thanks for that17:06
bryce_they don't block jaunty; neither actually go into ubuntu, they're just test stuff17:06
rickspencer3any other business?17:06
pitticalc: you have more context about what's needed, so if you could?17:07
bryce_like documentation, test stuff is always the last thing to get done ;-)17:07
calcpitti: ok17:07
asacrickspencer3: last cylcle the roundtable calls not always had an agenda17:07
asacrickspencer3: i even had one call where all parties didnt know who wanted that call ;)17:07
rickspencer3asac: ack17:07
rickspencer3this should be significantly improved this time around17:07
rickspencer3we have a template and everything :) !17:08
asacrickspencer3: would be good if any invite has a clearly marked leader who takes responsibility for the agenda too17:08
asacrickspencer3: great.17:08
rickspencer3asac: that's already covered. mdz sent everyone a list of their responsibilities17:08
rickspencer3of course, you can't guarantee everyone actually fulfills the expectations, but none the less ...17:09
pitticalc: let's disuss that in the MIR bug, and I'll poke doko about it17:09
asacsure17:09
rickspencer3one last word17:09
pitticalc: I'm subscribed; so please just summarize the current situation there17:09
rickspencer3I know that everyone is working very hard right now ...17:09
rickspencer3but I can tell you from where I am sitting, it is paying off17:09
kenvandine;)17:09
seb128rickspencer3: thanks ;-)17:09
calcpitti: ok17:09
rickspencer3I think Jaunty is going to be a really solid release and really mean a lot to our users17:09
seb128+117:10
pitti\o/17:10
rickspencer3I know they will appreciate the extra attention to quality this release, and there are some cool new features17:10
pittifix...more...bugz17:10
bryce_I hope so, so far it seems like just an endless stream of bugs17:10
rickspencer3hehe17:10
seb128I'm pretty happy how things shaped this cycle, upstream codebase didn't change too much and the focus on fixing has been good17:10
pittibtw, we should get an update to http://qa.ubuntu.com/reports/bug-fixing/jaunty-fixes-report.html17:10
pittiit's pretty old now17:10
kenvandinebryce_: that is always the case for Xorg :)17:10
rickspencer3hmmm17:10
rickspencer3kenvandine: do you know anything about X?17:11
bryce_kenvandine: indeedy17:11
kenvandinerickspencer3: not enough17:11
pittikenvandine: run!17:11
rickspencer3I think we should all try to peel off an hour or two over the next week and see if there is some little thing we can do to help bryce_ out17:11
bryce_lol17:11
kenvandinebest i can do is help test bugs and report them17:11
asacso even more bugs ;)17:11
kenvandineyup :)17:11
kenvandineand maintain packages17:12
rickspencer3kenvandine: that helps, actually17:12
kenvandinexorg hurts me17:12
bryce_getting backtraces on any crash or hang you've reported would help a lot.  Or even just assisting with bug triage in any of the X packages would be quite welcomed.17:12
kenvandinerickspencer3: yup...  i know17:12
rickspencer3so does testing out bugs as they get fixed, etc...17:12
kenvandinebryce_: jaunty is also stressing Xorg more... enabling compiz by default17:12
pittiand if you file a bug, file it upstream as well, and link it17:12
kenvandineso uncovering more crap i bet17:12
kenvandinesure17:12
asacbryce_: is UXA off the table for this cycle or do you want me to keep using it (its broken since yesterday)17:12
pittieveryone here needs a bugzilla.{freedesktop,gnome}.org account anyway17:13
kenvandineasac: broken?17:13
kenvandineworking here17:13
kenvandineUXA makes my box usable17:13
asackenvandine: its not usable with compiz ... slow17:13
kenvandinepitti: got mine :)17:13
rickspencer3meeting adjourned?17:13
bryce_a lot of X bugs we're stuck because we don't have good debug and/or testing info.  I've got some troubleshooting guides at http://wiki.ubuntu.com/X/Troubleshooting that can help guide you to get deeper info.17:13
kenvandineasac: fast as hell here17:13
kenvandinebryce_: thx17:13
bryce_rickspencer3: thanks17:13
asackenvandine: it worked all the time. bug upgrade from yesterday night killed it17:13
kenvandinerickspencer3: yeah17:13
asackenvandine: have you upgraded today?17:13
rickspencer3thanks all17:13
kenvandineasac: hummm17:13
* kenvandine checks17:14
asacthanks all17:14
ArneGoetjethanks17:14
pittithanks all17:14
rickspencer3seb128: talk to you in 16 minutes17:14
seb128rickspencer3: indeed17:14
kenvandineasac: no i haven't.... asac is it confirmed it is broken for everyone?17:14
rickspencer3g'night ArneGoetje, talk to you in the morning17:14
seb128thanks everybody17:14
* kenvandine is scared to break his desktop more :)17:14
asackenvandine: i dont think that many upgrade three times a day ;)17:14
calcpitti: updated the bug report17:14
kenvandineasac: got a bug number?17:14
kenvandinei can verify :)17:15
bryce_asac: I built a new -intel last night which purports to fix a lot of UXA bugs, but had to wait for the libdrm I did yesterday to get to the mirrors.  But now we're in freeze so need to check with steve before uploading it17:15
asackenvandine: no. i didnt want to bother bryce_ before asking if UXA is really something we want to work on this cycle17:15
bryce_asac: anyway, so I dunno if UXA is this is going to make UXA stable enough to consider, so your continued testing would be very appreciated17:15
kenvandineok, only breaks uxa17:15
asacbryce_: well. so you say the problem might be because its out of sycn?17:15
asacbryce_: if so we should open bug and mark it as release critical17:15
pitticalc: thanks17:15
kenvandinebryce_: got something I can install locally if it breaks for me?17:16
asacbryce_: which should give enough reason to bring stuff in sync again17:16
pittibryce_: I'm happy to test it, but I have some serious gripes about doing the switch in Jaunty..17:16
cjcompiz is enabled by default?  Does there exist a 'minimum requiement' specification for Jaunty?17:16
asackenvandine: does EXA not work for me?17:16
asackenvandine: for me it didnt work in the past, but today it worked (luckily)17:16
* calc bbl, lunch17:17
asackenvandine: s/for me/for you/17:17
kenvandineasac: it was slow for me17:17
asacdamn. you know what i mean17:17
asackenvandine:yeah. but its still usable so you shouldnt be scared to upgrade ;)17:17
kenvandinenot really usable :)17:17
kenvandinereally really slow17:17
asachmm .. probably it was just flipped then ;)17:17
bryce_pitti: yeah I don't really want to do the switch in jaunty either.  But upstream is putting 100% bug fixing attention into UXA, and round about 0% in EXA, so we're standing on a crumbling ledge and need to jump at some point...17:17
kenvandinelike over a minute to render the app switcher17:17
asacbryce_: so where can i get the package?17:18
asacbryce_: to test if it fixes UXA for me17:18
pittibryce_: I guess we can upload the bug fixes either way, it's just a question of the default, right?17:18
bryce_asac: I'll have it later today; I need to rebuild it with the libdrm dependency17:19
pittibryce_: since we are in a6 freeze, perhaps upload to your PPA and send out a CFT?17:19
bryce_pitti: that's was I was planning17:19
pitti\o/17:20
kenvandinebryce_: great17:20
* kenvandine updates/breaks his box :)17:20
pittibryce_: I guess the default is for the entire driver, it's not model or model range or chipset specific?17:21
pittibryce_: I. e. can we say "enable it on 945, but not on the 845"?17:21
asaci guess this would be a similar effort as deciding whether we want compositing in metacity or not17:21
pittiyeah, whitelisting based on testing17:22
bryce_pitti: well, the easiest change to make is all or nothing17:22
pittibryce_: right17:22
pittibryce_: so in intrepid it was XAA across the board, right?17:22
bryce_pitti: however of course you can always put in whatever you want int he code to whitelist/blacklist specific pci ids, chip families, etc.17:22
pittibryce_: oh, hang on, that's still per-driver, or for all drivers?17:23
asacpitti: EXA for intel i would think in intrepid17:23
bryce_however in the case of UXA we never saw good correlation of it works for 965 but not 915 for instance - there were failures being reported across the board on all chipsets17:23
pittididn't we have the "enable EXA" spec for jaunty?17:23
pittibryce_: ah, so e. g. the artifacts with compiz happened on all chipsets?17:23
bryce_pitti: UXA is specific to -intel; it is not appropriate for any other driver17:23
pittibryce_: any idea how that relates to bug 304871?17:24
ubottuLaunchpad bug 304871 in xserver-xorg-video-intel "[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)" [Unknown,Confirmed] https://launchpad.net/bugs/30487117:24
pittibryce_: i. e. will older chips be even worse off with UXA?17:24
bryce_pitti: one of the design assumptions for UXA is that the video memory and the system memory are physically shared - which is only true for on-board integrated video cards; so for video drivers that are used with discrete cards (nvidia, ati, etc.) that assumption doesn't hold, so UXA wouldn't be usable on them17:25
bryce_pitti: the enable EXA spec was for -ati17:25
bryce_pitti: purportedly the UXA changes would fix that BO front buffer bug17:25
pittioh!17:26
bryce_pitti: however in testing it was found it didn't solve the problem as upstream had said it would17:26
pittiun-oh!17:26
bryce_but there are tons of BO fixes in the 2.6.3 changelog, so maybe...17:26
bryce_I am coming not to trust the -intel upstream quite so readily though ;-)17:27
pittibryce_: would be curious if the crack-of-the-day UXA would fix chips that the more solid EXA obsoleted..17:27
bryce_you mean 8xx?  don't hold your breath17:28
cjbryce_: will a GM965/GL960 suffice as a repro card for bug 328035?17:29
ubottuLaunchpad bug 328035 in xserver-xorg-video-intel "*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call" [High,Triaged] https://launchpad.net/bugs/32803517:29
cjalso, I may not be able to get this laptop to sleep/wakeup...17:30
bryce_cj: maybe17:30
cjany way to fake a wakeup?17:30
bryce_cj: it may be particular to the lenovo's 965 specifically17:30
bryce_cj: that I don't know17:31
bryce_cj: but you should report suspend/resume troubles to the kernel team.  There's a test script out now for those kinds of issues.17:31
cjthis is a sony vgn cr520e.. I'll post a lspci dump in a moment...17:31
cjoh?  do they have a channel on freenode?17:31
bryce_cj: you mean like #ubuntu-kernel?17:32
cjyeah, something like that :)17:33
bryce_;-)17:33
=== jorge__ is now known as jcastro
pitticj: why fake a wakeup? neither suspend nor hibernate works for you?17:35
cjpitti: da17:36
cjpitti: it's been a while since I tried it... I'm dist-upgrading to jaunty as we type, so I'll give it a go when that finishes...17:37
bryce_I've just uploaded the new intel 2.6.3 to my ppa17:38
bryce_I'll put out an email to #ubuntu-x once it's finished building17:38
asacbryce_: what is your ppa? ~bryce?17:40
asacor with last name too?17:40
bryce_~bryceharrington17:40
asack17:40
asaci will check that tomorrow. today is almost done17:40
crevettedidrocks: https://bugs.edge.launchpad.net/bugs/337911 updated17:57
ubottuUbuntu bug 337911 in nautilus-sendto-universe "New upstream version (1.1.2)" [Wishlist,Incomplete]17:57
didrockscrevette: I finish a build on dapper first and I am up to you :)17:58
didrockscrevette: is it the file you uploaded http://launchpadlibrarian.net/23727032/nautilus-sendto_1.1.2-0ubuntu1.diff.gz ?18:03
seb128pitti: can you look at accept pidgin srus?18:04
didrocksseb128: I can upload gaim for hardy right now. Do you have something to test it?18:05
seb128didrocks: dapper you mean?18:05
crevettedidrocks: no18:05
didrocksseb128: oupsss, sorry, dapper yes18:05
seb128no18:05
crevettedidrocks: my changelog has just changelog related to nautilus-sendto-universe18:06
didrockscrevette: strange, I see that in your comment :/18:06
crevetteI admit I didn't check the file before uploading18:06
crevetteletme check18:06
didrocksseb128: I upload it in everycase and for someone to test it with an ICQ account?18:06
seb128didrocks: yes18:06
didrockscrevette: last time, it was the same: it seems you uploaded nautilus-sendto and not nautilus-sendto-universe18:08
didrocksseb128: isn't better that I add the gaim package to the bug, instead of pidgin one, for automatic closure?18:08
crevettedidrocks: okay, I uploaded the wrong one :)18:08
seb128didrocks: yes indeed18:08
didrockscrevette: twice :p not do a third one ;)18:09
crevetteokay done18:09
didrocksseb128: it recreates all candidates /o\ I have to invalidate some :)18:10
seb128yes18:11
crevettefor nemiver, is the changelog can be like http://dpaste.com/12031/ or should I remove reference of GNOME bugs18:12
didrockscrevette: fixe minute ;)18:12
didrocksfive*18:12
cjdidrocks: that's much better than "/me ducks"18:17
didrockscj: :)18:19
didrocksok, crevette let's have a look18:19
didrockscrevette: all depends fo the readibility, I usually remove them and nobody killed me (apparently ;))18:21
didrocksof*18:21
crevettedidrocks: yeah, I have mixed feelings, let's remove them18:22
didrockscrevette: the important thing is that you check there are not taken as launchpad bugs (so, listed in .changes file when building your source package)18:23
crevetteyeah :)18:23
chrisccoulsonhi seb128. i just saw someone reported a gnome-session bug describing what tedg was experiencing a few days ago (vino-server continually spawning). do you think that is actually a gnome-session bug?18:24
chrisccoulsonbug 340515 fyi18:24
ubottuLaunchpad bug 340515 in gnome-session "Consumes all CPU, logs a lot of output" [Undecided,New] https://launchpad.net/bugs/34051518:24
seb128chrisccoulson: is vino-server crashing?18:24
chrisccoulsonnot sure, i suppose i should find out. i wasn't sure if tedg had understood why it was happening18:24
crevettedidrocks: https://bugs.edge.launchpad.net/bugs/337914 is updated as well18:28
ubottuUbuntu bug 337914 in nemiver "Upgrade to version 0.6.5" [Wishlist,Incomplete]18:28
pittiseb128: sure18:37
seb128pitti: danke18:37
seb128chrisccoulson: did you send the gnome-desktop-edit-item bug upstream btw?18:44
chrisccoulsonits done18:44
seb128thanks18:44
chrisccoulsonii was confused at first as i wasn't sure what gnome-panel had to do with it. i worked it out in the end though ;)18:44
pittiseb128: hardy and intrepid accepted; I don't see a dapper and gutsy upload?18:45
seb128pitti: do we care about gutsy?18:45
seb128pitti: there is a debdiff for gaim dapper on the bug but nobody has a dapper install around to build and test it apparently18:46
pittiseb128: oh, I'll sponsor dapper then, I have a dapper chroot18:46
seb128ETOOMANYSUPPORTEDVERSIONS18:46
seb128pitti: danke18:47
pittiseb128: I think we should still update gutsy, it has another month to live, and the backport is probably trivial18:47
seb128right18:47
seb128I've no gutsy install either18:47
pittineither have I, I'm afraid, but I can bootstrap one18:49
seb128pitti: let's source build on an another and upload to proposed18:49
pitti"on an another"?18:50
seb128pitti: I doubt many users will complain about gutsy-proposed18:50
seb128+ubuntu version18:50
pittiah, right18:50
seb128if the patch apply cleanly no need to test build on gutsy18:50
pittiseb128: I'll test didrocks's gaim update on dapper, since it's untested18:50
seb128just do a source upload, let's the buildd do that18:50
seb128pitti: thanks18:50
pittiseb128: I agree, we can test the -propsoed .debs18:50
pittiseb128: they should work on hardy, too18:52
didrockspitti & seb128 : thanks a lot. If I can do anything (no, I won't search for my deprecated icq account :))18:52
pittiI actively use ICQ, so I can test dapper18:53
pittiseb128: do you have an icq account?18:53
pittior anyone else here?18:53
didrockspitti: great ;) I must advocate I dropped everything for jabber18:53
=== tonyyaru1so is now known as tonyyarusso
seb128pitti: yes18:55
seb128pitti: not on jabber?18:55
pittiseb128: well, we are testing ICQ here :)18:55
pittiseb128: I just stopped pidgin to start gaim18:55
* pitti currently configures his account18:55
pittihm, I can log into ICQ just fine with current dapper's gaim18:56
pittiseb128: I am 135336116, can you please ping me?18:56
crevetteis ICQ still one of the top IM protocol ? it was when I was young, let say 12 years ago18:57
* crevette did use ICQ for a while, and has not use it since few years18:58
pitticrevette: nowadays a lot of my friends are using skype (I don't), but it's still fairly popular here, yes18:58
pittiI'm mainly using it because they do :)18:58
crevetteXMPP for the win18:58
pittiworks fine for me18:58
pittijust talking to a friend18:58
pittitsk, how can a 3 year old client still work and a 0.5 year old not?18:59
didrockspitti: the parameters have changed19:00
pittididrocks: right, I know19:00
pittididrocks: but the current dapper version (not your patched one) works just fine19:00
didrockspitti: apparently old protocol continues working :)19:00
seb128pitti: I added you but you are not online? or didn't add me?19:00
pittiseb128: you don't appear in my list either19:00
pittiah, there you come19:01
seb128ok, that works!19:01
=== rickspencer3 is now known as rickspencer3-afk
seb128ok, I've to go for dinner, bbl19:02
didrocksseb128: have a nice dinner!19:02
seb128thanks, you too19:02
didrockscrevette: nautilus-sendto-universe seems good (build and install). I upload it right now19:02
cjeep.  ctrl-alt-backspace broke!19:03
pitticj: s/broke/was disabled/19:03
cjpitti: okay.  I can see the argument for that.  *sigh*19:03
cjhow do I toggle that?19:03
cjit probably breaks some apps, doesn't it?19:04
pitticj: install dontzap, it has a scrpit; or modify xorg.conf manually19:05
crevettedidrocks: danke19:06
cjis my proxy doing something weird?  I'm getting a bad sig for dists/jaunty/Release (40976eaf437d05b5)19:07
kenvandine_wkseb128: ekiga 3.2 is planned for next week19:11
pittiwe don't even have 3.1 yet..19:16
dobeydid icon-naming-utils 0.8.90 get pulled in yet?19:18
kenvandine_wkpitti:  i know, 3.1 is a devel release and seb128 was wanting to know if 3.2 would come out with gnome 2.2619:19
kenvandine_wkbefore we thought about updating it19:19
kenvandine_wkseb128: did we really want to update libgda from 3.0.2 to 3.99.13?19:20
kenvandine_wkthat is a major bump19:20
kenvandine_wk3755 lines in the Changelog19:20
cjoooh, hibernate seems to work...19:24
cjhowever, resume does not...19:25
kenvandine_wkcj: then hibernate doesn't sound so useful :)19:26
cjkenvandine_wk: I'll agree with you :)19:26
cjbut the little light on the bottom of my computer does its flashy thing during hibernate...19:26
cjwhich may be considered "useful" by some.  probably those in marketing...19:27
kenvandine_wkhehe19:27
crevettekenvandine: 3.99.13 is a pre-version for 4.0 so It's seems risky19:27
kenvandine_wkcrevette: exactly19:28
kenvandine_wkbut if 4.0 will be part of 2.26... maybe19:28
pittikenvandine_wk: if we want it, then we should package the devel release sooner rather than later19:28
pittikenvandine_wk: I still remember the pain we had with the upgrade to 3.019:29
pittiin one major step that took a lot of time, and broke a lot19:29
kenvandine_wkpitti: yeah, just want to check with seb128 before i spend a ton of time on it19:29
crevettehttp://mail.gnome.org/archives/devel-announce-list/2009-January/msg00006.html19:29
crevetteligda is in, but there is no decision on the version19:29
seb128kenvandine_wk:19:35
seb128$ apt-cache showsrc libgda4 | grep Version19:35
seb128Version: 3.99.11-0ubuntu119:35
kenvandine_wkoh19:35
kenvandine_wkdoh19:35
kenvandine_wki didn't see that :)19:35
seb128kenvandine_wk, pitti: before beta seems the right time to update ekiga if we want to do it19:35
pittiright19:36
pittiwe should track their dev releases as we track GNOME's19:36
seb128ETOOMUCHTODOANDNOINTEREST but right ;-)19:36
pittikenvandine_wk: ekiga is one of those unchartered^Wunmaintained corners of the GNOME desktop, that I was talking about19:36
seb128if somebody wants to do the updates that would be nice19:36
pittiseb128: if only we had another GNOME maintainer...19:36
pitti:)19:37
seb128pitti: ;-)19:37
pittiMarch 16!19:37
pittiseb128, didrocks: for the record, preparing pidgin/gutsy right now19:37
seb128pitti: thanks19:37
didrockspitti: ok, thanks :)19:37
kenvandine_wkseb128: want me to take ekiga and it's deps too?19:38
pittididrocks: I just apply your debdiff to the gutsy version19:38
pittikenvandine_wk: if you have time, and it interests you, sure19:38
pittikenvandine_wk: I'm happy to test it again with you :)19:38
didrockscrevette: uploaded, thanks, please, check my comments on minor issues on bug #33791419:38
ubottuLaunchpad bug 337914 in nemiver "Upgrade to version 0.6.5" [Wishlist,Fix committed] https://launchpad.net/bugs/33791419:38
pittikenvandine_wk: last time wasn't very successful :)19:38
didrockspitti: you cheated :p19:39
kenvandine_wkpitti: i have a few things in front of it in queue :)19:39
kenvandine_wkbut i can do it when i have time19:39
seb128kenvandine_wk: would be nice!19:39
seb128kenvandine_wk: opal and ptlib probably need to be update too right?19:40
kenvandine_wkseb128: also, what about libgdamm?  is there a 3.99 package for it?19:40
kenvandine_wkseb128: yes19:40
kenvandine_wkalways do19:40
kenvandine_wk:/19:40
* kenvandine_wk actually hates that stack... but knows it pretty well :)19:40
seb128hehe19:41
seb128kenvandine_wk: I don't think so for libgdamm and no hurry I don't think anything use it right now19:41
kenvandine_wkok19:41
* kenvandine_wk ditches that one for now :)19:41
seb128kenvandine_wk: do libgda and ekiga stack first we will see about that later19:41
crevettedidrocks: okay thanks a lot for the fixes19:42
didrocksI am going to have my lunch now, bbl19:42
didrockscrevette: you're welcome :)19:42
mvodidrocks: a late lunch :)19:43
mvobon appetite19:43
seb128didrocks: dinner you mean right?19:43
didrocksmvo: thanks19:44
didrocksseb128: hum, considering I didn't have the time at work to have my lunch, technically… :)19:45
seb128didrocks: enjoy anyway ;-)19:47
didrocksseb128: thanks ;)19:48
seb128bbl19:52
=== jorge__ is now known as jcastro
seb128pitti: still aorund?21:01
seb128around21:01
seb128pitti: do you know why bug #340508 has been cleaned?21:01
ubottuLaunchpad bug 340508 in gnome-control-center "gnome-appearance-properties crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()" [Undecided,New] https://launchpad.net/bugs/34050821:01
seb128pitti: I've seen several bugs that I know to be duplicated cleaned today21:02
seb128pitti: I'm wondering if there is an apport or retracer bug somewhere there21:02
seb128pitti: those have not been tagged as retracing failed and no comment has been added21:03
pochuseb128_: hi, do you have time for some sponsorship? I need a libproxy upload for bug 314945 :)21:45
ubottuLaunchpad bug 314945 in libproxy "MainInclusionReport for libproxy" [Undecided,In progress] https://launchpad.net/bugs/31494521:45
pochuthe package is at http://emilio.pozuelo.org/~deb/libproxy_0.2.3-2~jaunty1.dsc21:45
seb128_pochu: could you fix the version to be a normal one and not ~jaunty?21:46
pochuseb128_: sure thing21:48
seb128_thanks21:48
pochuseb128_: can I base it in the Debian package? It's basically a fake-sync21:48
pochui.e. just add a -0ubuntu2 entry21:49
seb128_pochu: why do you need to fake sync it rather than real sync?21:49
pochuseb128_: it's in NEW :(21:49
seb128_ah ok, yeah sure then21:49
pochuand I wouldn't hold my breath waiting for it to be processed...21:50
pochu:)21:50
pochuactually it has to be -0ubuntu4, since we have ubuntu3 in the archive ;)21:50
pochuseb128_: ok, this should be fine: http://emilio.pozuelo.org/~deb/libproxy_0.2.3-0ubuntu4.dsc21:52
pochuwho should I ask for a UI freeze exception? slangasek?21:55
pochu(it's about one of the "check for notification capabilities" patch)21:55
seb128_what UI do you want to change?21:55
seb128_which one?21:55
pochuliferea21:55
seb128_libproxy uploaded21:55
pochucool, thanks :-)21:56
pochuthat should make slangasek happy21:56
pochuI could ask for a freeze in exchange for that21:56
seb128_yeah, you can try asking steve, he will tell you what to do if that's not right ;-)21:56
rickspencer3kenvandine_wk: ping21:56
pochuseb128_: ok, thanks!21:56
=== seb128_ is now known as seb128
didrocksseb128: I almost forget gnome-netstatus :) it's ready when the soft freeze will be ended. bug #34077522:03
ubottuLaunchpad bug 340775 in gnome-netstatus "Please sponsor gnome-netstatus 2.26.0 to jaunty" [Undecided,Triaged] https://launchpad.net/bugs/34077522:03
seb128didrocks: thanks22:03
didrocksyou're welcome22:03
seb128didrocks: you still have pangomm on your todo right? ;-)22:04
didrocksseb128: when did you give me pangomm ? Looking at my backlog…22:05
seb128didrocks: I though I did this afternoon22:05
seb128didrocks: but maybe I meant to and I didn't22:05
didrocksseb128: not sure. Or maybe I was afk and working :)22:06
didrocksit happens sometimes ;)22:06
seb128didrocks: let's try again, do want to update pangomm tomorrow ? ;-)22:06
didrocksseb128: "Oh yeah, for sure ;)"22:07
seb128cool22:07
seb128no hurry with the freeze22:07
seb128and it's probably a good time to watch some TV or something before going to bed22:07
didrocksseb128: yes, just before GNOME release :)22:08
seb128indeed!22:08
didrockswhen exactly is it scheduled, btw?22:08
seb128be ready for 2.26 soon ;-)22:08
seb128tarballs due next monday for 2.2622:08
didrocksok, I will be available at the end of the day :)22:08
didrocksand then, everyday :D22:08
didrocks(on vacations)22:08
seb128didrocks: oh, cool ;-)22:09
seb128you took holidays to package GNOME 2.26? ;-)22:09
didrocksseb128: didn't know it? ;)22:09
didrocksmore seriously, some days away from my job will be great for my health :)22:09
seb128you should take some days away from the computer too22:10
seb128sometimes it's good to do a real break ;-)22:10
didrocksseb128: hum, yeah, but ubuntu-fr + gchildcare project + my book to update + ubuntu lessons to prepare for ORSYS…22:10
didrockswell, I plan more to take some break just after UDS ;)22:11
seb128utch22:11
seb128good luck then ;-)22:11
seb128yeah, good plan, it will be sunny there and almost summer22:11
seb128better plan for a break away from computers22:11
didrocksit's just a question of right scheduler algorithm :)22:11
didrocksseb128: yes, I will! You too, I imagine?22:12
seb128I didn't decide yet but I will for sure take some holidays during summer22:12
seb128after uds, after GUADEC ... not sure yet22:12
didrocksthat should be a good plan :)22:14
didrockshum, time to have some rest so ^^22:14
seb128'night didrocks22:14
didrocksthanks, have a good night too!22:14
seb128thanks!22:15
=== onestone_ is now known as onestone
=== asac_ is now known as asac

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