/srv/irclogs.ubuntu.com/2009/05/05/#ubuntu-desktop.txt

rickspencer3why does two weeks of writers block melt away right when I have to take care of my kids02:44
rickspencer3curse you muse!02:44
=== rickspencer3 is now known as rickspencer3-afk
MayureshGood day fellas....04:36
MayureshI need help with connecting my 1 TB hdd with my laptop using ubuntu.04:36
MayureshIts failing after sometime, after writing around 58 M04:37
MayureshI have the dmesg output with me and have already searched the net for any useful information, but didn't get any.04:37
Mayureshany help is much appreciated.04:37
mpontilloMayuresh: you might have better luck in #ubuntu; this channel is a much more limited audience. I would suggest that you pastebin any relevant dmesg output first. see http://paste.ubuntu.com04:41
Seven-7Arrrrgh. Does anyone know how to get help support for Evolution?04:44
Seven-7It's freezing on opening.04:44
Mayureshmpontillo: Thanks. I'll also place this question at #ubuntu. In the mean time, I have pasted the output: http://paste.ubuntu.com/164643/04:48
pittiGood morning07:33
pitticalc: pong07:34
pittibryce: thanks, I processed it last night07:34
robert_ancellpitti: hello07:38
=== tkamppeter__ is now known as tkamppeter
pittirobert_ancell: good morning, how are you?07:48
robert_ancellpitti: good, trying to get the hang of karmic packaging.  Is there anything different to do than a normal package update?07:49
pittirobert_ancell: not really, in what way?07:54
pittikarmic right now is in the "anything goes, break it" stage07:54
robert_ancellpitti: In that I open a bug with the debdiff and subscribe the main sponsors?07:55
pittirobert_ancell: for a new upstream version it's better to attach the source package's diff.gz07:58
pittirobert_ancell: so that we don't have to wade through the upstream diff07:58
robert_ancellpitti: do you need the orig.gz then?07:58
pittirobert_ancell: if a package is in bzr, just commit to the branch and ask us to upload it07:59
pittirobert_ancell: for GNOME packages we know where to get them from; for other packages, an URL to the orig.tar.gz is fine07:59
robert_ancellpitti: and if it needed modification due to directory naming?07:59
pittirobert_ancell: a repacked orig? then please put it on your people.u.c. page or attach it08:00
=== eeejay_givingup is now known as eeejay
robert_ancellpitti: when you merge a debian changelog with an ubuntu one do you keep all the entries?08:06
pittirobert_ancell: we usually do, although admittedly I "flush" them from time to time08:06
pittisince a merge requirement is to give a detailled list of remaining ubuntu changes08:06
pittirobert_ancell: oh, you are merging from Debian?08:07
pittirobert_ancell: wrt. orig.tar.gz, when Debian has it, we can get it from there08:07
robert_ancellyes, ok08:07
robert_ancellI'm working on avahi - I noticed you'd done that one previously08:07
pittiright08:08
pittiin my times I didn't need to repack the orig, though08:08
robert_ancellWhen you say remaining ubuntu changes do you mean "any change from upstream" - as you listed the patches as provided by debian08:08
robert_ancelland the patches that are obsolete - should I list them in the changelog?08:08
pittirobert_ancell: no, "ubuntu changes" are relative only to Debian for merging08:09
robert_ancellok, easy (in this case we have none)08:09
pittirobert_ancell: the patches shoudl usually document themselves, with https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines08:09
pittirobert_ancell: if we have zero changes, we can sync08:09
robert_ancellpitti: most aren't. I have been tagging mine08:10
pittirobert_ancell: if our only remaining delta is the changelog, or some obsolete cruft, we sync08:10
pittithat's in fact the ideal case08:10
robert_ancellok, how do we trigger that then? avahi failed the automerge08:10
pittionce we have done our homework and pushed patches to upstream and packaging fixes to Debian, we are in sync and can stop maintaining a delta08:10
pittirobert_ancell: if you are sure that the remaining delta is zero, request a sync with https://wiki.ubuntu.com/SyncRequestProcess08:11
pittiin short, "requestsync avahi karmic" should do08:12
robert_ancellpitti: ok, once the sync is complete and there are other changes should I push those to Debian so we keep the sync?08:12
pittirobert_ancell: "other changes" -> "future changes"?08:13
robert_ancellyes (I don't want to sync then immediately fix a bug)08:13
pittirobert_ancell: yes, we should, if it's packaging related08:13
pitticode changes should better go into the upstream bug tracker08:13
pittirobert_ancell: well, syncing in between has the advantage to have a really clean slate again08:13
robert_ancellsure08:13
=== celthunds is now known as celthunder
robert_ancellpitti: again, when I look at glade it appears that should by synced too - is there anything special I should be looking out for in the debian/ directory?08:30
seb128hey robert_ancell08:30
seb128robert_ancell: did you get my email?08:30
robert_ancellseb128: hey seb - you're giving me easy packages to merge again08:30
seb128is that ironic? ;-)08:31
robert_ancellyes, as far as I can see both avahi and glade can be synced with debian08:31
seb128I didn't look at the diff but basically at the list of things not merged yet and picked some of your packages there08:32
seb128oh, that would be good ;-)08:32
seb128    - debian/rules: Create an up to date PO template during build.08:32
seb128  * Python 2.6 transition (fixes FTBFS)08:33
seb128those are in debian now?08:33
robert_ancellthe PO template thing is.08:33
seb128I'm a bit surprised since the po thing is specific to ubuntu for language packs and python2.6 is not used in debian yet that I know about08:33
robert_ancellok, no then I'm confused08:33
seb128ah good, somebody must have sent the change to lower the delta and they took it08:33
seb128robert_ancell: ok, you are right, pitti sent them the change and they applied it08:35
seb128robert_ancell: tomorrow you can do gdm which is a non trivial one ;-)08:35
robert_ancellseb128: so what was the python 2.6 fix, I'm looking at the bug and the source but I can't see what it is.  And if we merge do we use the builds from Debian or build them locally?08:37
seb128we grab the source from debian and upload that08:38
seb128it's built on ubuntu08:38
seb128robert_ancell: https://launchpad.net/ubuntu/+source/avahi08:38
seb128robert_ancell: you have the diff for each upload there08:38
seb128the change is basically site-packages -> *-packages08:39
seb128the python directory used in 2.6 changed08:39
robert_ancellok, I see now.  So we can't sync because we need that change08:39
seb128right08:40
seb128but you can send the patch to debian08:40
seb128there is no reason they couldn't do that, that still work for site-package and they will get 2.6 too08:40
seb128so we can sync with there next upload08:40
seb128if you didn't oversight other changes too ;-)08:40
seb128robert_ancell: they don't have Keybuk's change either08:42
seb1280.6.23-4ubuntu308:43
seb128robert_ancell: and they still enable ipv6 apparently that we don't08:45
pittiseb128: no, I've been sending POT creation patches to Debian for years08:46
robert_ancellPOT?08:46
seb128pitti: right, but they didn't take it until recently08:46
seb128robert_ancell: intltool-update call08:46
seb128pitti: it was still listed in the summary of changes when we rebased previous on debian08:47
pittiright08:47
seb128anyway there are the 3 others changes08:47
seb128python2.6 site-packages -> *-packages08:47
seb128runlevel08:47
seb128ipv608:47
seb128which still need to be applied08:47
pittirobert_ancell: you are looking at the current ubuntu patch that MoM creates?08:48
seb128I found those patches not practical when you have different versions08:48
pittiI love them08:48
seb128I usually diff the debian directories between current debian and ubuntu08:48
pittiI usually grab the Debian version and the current ubuntu patch, and then walk through teh Ubuntu patch and throw out the obsolete stuff08:49
pittiand then apply the rest08:49
robert_ancellI'm not sure how to use MoM08:49
seb128I will let pitti explain since I don't use it08:49
pittirobert_ancell: I almost never take the automatic merge, since it's often unclean, and it can't check which changes aren't really required any more08:50
robert_ancellpitti: where are the files that MoM generates?08:50
pittirobert_ancell: the only things I use from MoM are the current Ubuntu diff and the fact that a package needs merging (and by whom)08:50
pittirobert_ancell: https://merges.ubuntu.com/main.html -> click on package -> remove '/REPORT' from URL08:50
robert_ancelloh08:51
pittii. e. https://merges.ubuntu.com/a/avahi/avahi_0.6.23-4ubuntu4.patch is the current Ubuntu patch08:51
seb128the package names should rather point to the directory than to REPORT08:52
seb128I find myself removing the REPORT every time and wondering why it's the default08:52
* pitti too08:52
seb128you can easily click on it and back to go back to the directory08:52
robert_ancellanother question: debian bumped the soname from 5 to 6 when they went from 0.6.23 to 0.6.24, any idea why?08:53
pittiugh08:53
seb128because the library soname changed?08:53
seb128that's an upstream thing usually08:54
seb128libraries are name libname.no.SONAME08:54
seb128where SONAME is a number08:54
pittionly two packages depend on libavahi-core5, so that transition is easy08:54
seb128when they break the compatibility in the abi they bump this number08:54
seb128so that doesn't break applications using the old abi08:54
seb128and you install the new abi next to it and start rebuilding things using this one08:55
seb128the package renaming is to allow installing both versions08:55
seb128and have a smooth transition08:55
mvoI personally use grab-merge and work based on this because it often has quite good results for me (checking the debdiff afterwards carefully of course)08:56
seb128I fail to see how that's better than a diff -Nru of the debian directories usually08:57
seb128you just lot of extra noises when the versions are not the same08:57
pittimvo: it discourages you from actually checking which of our delta can be dropped, though08:57
pittiseb128: you don't get a three-way diff that way, though08:57
robert_ancelli see.  The avahi guys aren't keen on keeping ABI within minor releases.08:58
mvopitti: not really, the debdiff of the merge (against the debian version) needs to be checked afterwards for this as well. but I guess the workflow is pretty equivalent in the end, just approaching it from different directions08:58
* robert_ancell thinks the avahi package will take some more time08:58
seb128pitti: I find that not required in most cases, especially if your changelog has an accurate summary of changes from the previous merge already08:58
seb128anyway everybody has his own workflow ;-)08:59
pittiI'm just eager to drop delta08:59
pittisure08:59
seb128one other thing I don't bother doing that quite some people do is to copy over old ubuntu changelog entries08:59
pittisame for me09:00
pittiif we have a good merge summary, it's just redundant09:00
seb128robert_ancell: see that was good that you had an easy one to start ;-)09:00
mvoI think old changelogs are often useful (and one of the things that you get with the merge from mom)09:00
seb128mvo: I summarize all those in the current entry09:00
seb128quicker to read than trying to go over all the old uploads09:00
seb128and that wins some CD space ;-)09:01
seb128especially for GNOME where we copy the NEWS each time09:01
mvoseb128: fair enough in case of NEWS I guess09:01
pittiseb128: you should *really* use Seb Bacher to save 6 bytes for each changelog record :-P09:01
mvohaha09:01
* seb128 hugs pitti09:01
Nafallolol09:02
robert_ancellgood day all!09:29
robert_ancell(that was an inverted good night)09:29
pittirobert_ancell: enjoy the evening!09:29
seb128robert_ancell: good evening!09:29
* crevette shouldn't do uplaod with its long name09:29
robert_ancell:)09:29
pittirobert_ancell: or, rather: ʇɥƃıu pooƃ09:29
huatsmorning everyone !09:50
seb128lut huats09:51
huatshello seb12809:51
seb128huats: how are you? how is your business going?09:52
huatsseb128: I am fine09:52
huatsand I try to start the business09:52
huatsit is not that easy but I have some possibilities :)09:52
huatsI think I'll know more by the end of the month :)09:53
huatswell for the moment I am mainly focussing on putting together all the pieces09:53
huats:)09:53
seb128ok, good luck09:55
seb128still as busy?09:55
seb128but still going to uds?09:55
huatsstill going to th uds :of course seb12809:56
huatsI am still busy09:56
seb128I'm wondering since you seem to not be around a lot recently09:56
seb128so I was wondering if you would still manage to get time for uds09:56
huatsIn fact I am around but not chatting09:56
huats:)09:56
huatsit is weird for someone as talkative than I am :)09:57
seb128lol09:57
huatsNeed to logout09:59
pittiseb128: your X-GIO-NoFuse=true patch in f-spot, do you know whether that's reported upstream?09:59
* pitti is tagging our patches09:59
pittibug 33846610:00
ubottuLaunchpad bug 338466 in f-spot "Fspot doesn't load pictures from my digital camera" [Low,Fix released] https://launchpad.net/bugs/33846610:00
seb128pitti: I don't think I sent that upstream no because I was not sure that was the right way10:00
seb128ideally it could be using the fuse mount but for some reason that sloooow10:01
pittiprobably because it generates thumbnails from the real pictures isntead of using the camera's thumbnails?10:01
pitti(that's what we had in gthumb)10:01
seb128could be10:02
pittiall our other patches are reported upstream now10:03
pitti(if only they'd apply them)10:03
seb128I hate the bugzilla.gnome.org slowness10:11
pochuthe good thing is that it makes launchpad feel fast ;)10:13
seb128yeah10:14
seb128mvo: you are a vm user right? what do you recommend on jaunty to have something usable? ;-)10:32
seb128I use kvm -cdrom iso to boot live cds10:32
seb128and virt-manager for installs but virt-manager is the suck, mouse location keeps being wrong, it it doesn't go in some screen corners10:32
huatsseb128: if you move the mouse quite fast you can reach that corners10:34
huatsseb128: i am doing that all the time :)10:34
seb128huats: it's not fast, you need to go against the opposite border rather10:34
seb128yeah, me too, but that's annoying so I'm looking for better suggestions10:34
huatsyeah opposite AND going fast to the corner you want to reach :)10:35
seb128and something I could switch full screen too would be nice10:35
* pitti just uses kvm in CLI mode10:35
huatsok10:35
pittikvm -m 512 -cdrom ubuntu.iso -hda testubuntu.img -boot d10:35
seb128pitti: is there some magic command to get an hdd in kvm so you can install something? ;-)10:35
seb128oh10:35
seb128easy enough10:35
seb128and testubuntu.img need to be created using some other tool?10:36
pittiseb128: -hda, -hdb, etc. -boot c -> boot from hd; -boot d -> boot from cdrom10:36
pittiseb128: you can use existing ones, or just dd if=/dev/zero one yourself10:36
seb128ok thanks10:36
seb128I'm pondering upgrading my laptop to karmic yet10:36
pittiI have a dd'ed 6 GB testubuntu.img which works just fine10:36
seb128or using a kvm install for now10:36
seb128I would like to get working beamer, suspend, etc for uds10:37
pittiseb128: with some tool you can even mount these images in your host system, for nice and easy file exchange10:37
mvoseb128: I just use plain kvm10:39
seb128pitti, mvo: ok thanks10:39
seb128I will use the office bandwith tomorrow to do karmic and debian unstable kvm images10:39
pittiseb128: hah, yay phat pipes10:40
mvoseb128: there is also ctrl-alt-f2 with kvm that gives you a useful console to do stuff10:40
mvoseb128: like sendkey ctrl-alt-f110:40
seb128ok thanks10:40
pittiseb128: if all else fails, I still have a jaunty install on my USB stick which I can boot, so I'm just using karmic10:40
seb128is there a way to put kvm in full screen? ;-)10:40
mvoseb128: or inject NMI (not that fullful ;)10:40
seb128pitti: I've upgraded my desktop but I tend to be a bit conservative with my laptop until uds10:41
pittisounds fine10:41
pittiespecially if you are still working on some SRUs10:41
mvoseb128: -full-screen10:41
seb128and usually it's useful for srus too10:41
seb128right10:41
seb128though I'm mostly done with srus for jaunty I think10:41
pittiseb128: I just have one computer, so I need to get along with chroots10:41
seb128mvo: kvm for the win apparently ;-)10:41
pittiwell, I have the G1 for ssh etc., but that doesn't run ubuntu yet10:41
seb128"yet" ;-)10:42
pittithere was a post on planet recently about wiping android and installing ubuntu :)10:42
pittibut how would I do phone calls then?10:42
seb128who need to do phone calls on a phone anyway10:43
seb128install ekiga and use that? ;-)10:43
pittiI'd love to, if only T-Online wouldn't block voip10:43
mvoseb128: I like it a lot10:44
=== dpm_ is now known as dpm
Ampelbeinseb128: hi. i'm currently working on the gnome-media merge/update. scrollkeeper has been deactivated to fix FTBFS, see bug 243573. I tried a build with scrollkeeper enabled and it worked. So do we again use scrollkeeper?11:13
ubottuLaunchpad bug 243573 in gnome-media "Please sponsor gnome-media 2.23.3-0ubuntu2 (main) into Intrepid" [Wishlist,Fix released] https://launchpad.net/bugs/24357311:13
seb128Ampelbein: no11:18
seb128Ampelbein: scrollkeeper should be run on the client side not on the buildd11:18
Ampelbeinseb128: ok, so i drop the build-dep, too?11:19
seb128if it's not required11:20
seb128I'm not sure how smart the configure is, ie try to pbuilder it without the build-depends11:20
asacpitti: so the sudo su -> root @console caused kind of colleteral damage to network manager ...11:47
asacpitti: walters said its unfortunate, but he thinks that root shouldnt be @console unless you login at gdm or a real console11:47
asacbug 360818 bug 37129111:49
ubottuLaunchpad bug 360818 in network-manager-vpnc "NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets " [Medium,In progress] https://launchpad.net/bugs/36081811:49
ubottuLaunchpad bug 371291 in network-manager "MASTER PPP connect fails if root is @console with pppd_timed_out() - (NetworkManager does not connect to Mobile Broadband anymore in Jaunty (Sierra AC880))" [Undecided,Triaged] https://launchpad.net/bugs/37129111:49
asacpitti: in particular this means that using "deny" in @console rules is not practical as it will remove permissions from root11:50
asacno action needed for jaunty ... we will change the network manager rules to not use any deny in @console ... but i guess we should consider to not make root @console for simple sudo su's11:51
Ampelbeinseb128: bug 371952 ready for review, see the linked branch.11:57
ubottuLaunchpad bug 371952 in gnome-media "Please sponsor version 2.27.1 in karmic" [Wishlist,Confirmed] https://launchpad.net/bugs/37195211:57
seb128Ampelbein: ok thanks12:03
seb128Ampelbein: you can do the same for gnome-utils next if you want ;-)12:04
pittiasac: oh, do you really rely on d-bus ACLs in network-manager?12:05
Ampelbeinseb128: will have a look after lunch12:05
seb128Ampelbein: no hurry, enjoy your lunch12:05
pittiasac: I had hoped that at_console will go away at some time, and we can remove that hack from d-bus (with the /var/run/console/ stamps)12:05
pittiPolkit already knows that stuff, after all12:05
asacpitti: we rely on dbus acls for some parts ...  look at /etc/dbus-1/system.d/NetworkManager.conf for instance12:06
asacpitti: @console going away is probably the right long term thing12:07
asaci agree12:07
asaci will check with dan how much work is to use polkit everywhere12:07
pittiah, I see12:07
pittiasac: so the problem is that if you do sudo -i, that terminal gets a CK session for root, and thus is able to access NM, although it shouldn't be?12:08
asacpitti: no. the problem is more devastating :)12:08
asacpitti: nm consists of multiple parts that communicate through dbus12:09
asac... all running as root12:09
asacnow you do sudo su12:09
asacand booooom. those parts cannot communicate anymore because the @console "deny" prevents it12:09
asac;)12:09
asacso the problem is that @console leads to less permissions for root12:10
asacthan without @console12:10
asacpitti: shouldnt the at_console check actually check whether the process is a child of the console?12:13
asaci think i can answer that by myself12:13
asacproblem is obviously the /var/run/console/ thing ;)12:13
pittiasac: I wonder why you need that deny rule in the first place12:14
asacis there a different approach for that?12:14
asacpitti: without that deny all @console can access that interface12:14
asacpitti: we will now use explicit interface allows12:14
asace.g. listing all interfaces that are allowed explicitly rather than adding a generic destination allow with a interface deny12:15
pittiasac: that's strange; d-bus should deny access to methods by default12:15
pittiit didn't in the past, but that was fixed in jaunty12:15
asacpitti: well. there is is a generic allow destination12:15
pittioh, I see12:15
pittiasac: right, ignore me12:15
asacallow send_destination="org.freedesktop.NetworkManager"/>12:15
asacyeah12:15
asacso that will be replaced by all interfaces named explicitly ... which is a bit hard to maintain but also makes some sense12:16
asachopefully that works ;)12:16
asacseems more users than expected have root shells open while doing networking12:16
pittiinteresting bug, though12:18
asacyeah12:18
asacarguably dbus shouldnt deny anything for root user imo ;)12:18
asacthat would at least reflect the unix best practices12:19
asacwell old-best-practices. i think with selinux and stuff thats not always true anymore12:19
* pitti -> lunch and some errands12:34
Ampelbeinseb128: doing gnome-utils now12:52
seb128good12:52
seb128pedro_: holla!13:29
seb128or "olla"?13:29
pedro_seb128: salut my friend!13:29
seb128pedro_: how are you?13:29
pedro_seb128: hola with just one l ;-)13:29
seb128hola then ;-)13:29
pedro_seb128: good good looking at some evo bugs, how about you?13:29
seb128good13:29
seb128pedro_: do you still run jaunty?13:30
seb128pedro_: could you help to confirm some of my desktop srus so they can be moved to updates13:30
seb128pedro_: some are trivial to test on any config13:30
pedro_seb128: yeap, at least for a couple of more weeks for doing SRU verifications13:30
seb128pedro_: ok, so could you do some of those on desktop components? ;-)13:30
pedro_seb128: sure ;-)13:31
pedro_count with that13:31
seb128the gnome-settings-daemon ones should be easy (out of the lid close crasher)13:31
* pedro_ looking at the pending list13:31
seb128same about gnome-applets, at least confirming that the update works correctly13:32
seb128nautilus too13:32
* seb128 kicks launchpad13:33
seb128now it's playing bugzilla and timeout!13:33
pedro_seb128: ok will do those today13:33
seb128thanks13:33
pedro_yeah it's working freaking slow for me too :-/13:33
=== rickspencer3-afk is now known as rickspencer3
=== proppy1 is now known as proppy
pedro_seb128: bug 360084 ; it's still an issue with the proposed version of g-s-d and seems to depend on a change to gnome-control-center as stated on the upstream report15:11
ubottuLaunchpad bug 360084 in gnome-settings-daemon "confirm dialog below main window" [Low,Fix committed] https://launchpad.net/bugs/36008415:11
pedro_commit is at http://git.gnome.org/cgit/gnome-control-center/commit/?id=6ea3c02290362ae3e9b4e9259bc72fc0b4ac45d215:11
seb128pedro_: ok, fine, write that on the bug saying that it's still working the same way but not broken in new ways15:12
pedro_seb128: ok will do it15:12
seb128ie we can move that to updates it doesn't fix everybody but doesn't break either15:12
seb128thanks15:12
pedro_you're welcome15:13
seb128the sru was not especially for this bug but I listed everything fixed in the new version ;-)15:13
seb128ok, time to go to catch my plane for the dxteam sprint15:20
seb128see you later15:20
=== al-maisan_ is now known as al-maisan
rickspencer3awe: fyi, our team meeting is in 8 mins17:22
pittiuh, https://blueprints.edge.launchpad.net/sprints/uds-karmic?searchtext=desktop-karmic- is quite well filled17:26
awerickspencer3: thanks!   you might want to update the wiki page, it says 14:00 UTC17:27
aweoops, i meant 16:00 UTC17:27
rickspencer3pitti: with two rooms, I think we have room for like 36 total or something17:27
rickspencer3awe: thanks17:27
rickspencer3could you please adjust it (being a wiki and all ;) )17:27
rickspencer3I think the fridge is correct17:28
rickspencer35 days x 5 Sessions per day X 1.5 rooms = 3717:29
rickspencer3pitti: sound about right ^^^ ?17:29
pittiwhy 1.5 rooms?17:29
pittithat's for desktop + DX + OLS, right?17:29
asacmeeting?17:29
rickspencer3we have two rooms, but should save some space for impromptu meetings17:29
pittior does OLS have their own?17:29
pittirickspencer3: right17:30
rickspencer3design and dx17:30
rickspencer3I kept OLS in desktop track for now17:30
rickspencer3so there are some design-karmic-*17:30
rickspencer3and dx-karmic-* sessions as well17:30
calcwhat is OLS?17:30
rickspencer3calc: Online Services17:30
calcah ok17:30
rickspencer3we should be saying Ubuntu1 now17:31
rickspencer3sorry17:31
kenvandine_wkyo17:31
asacso is this meeting ;)?17:31
calcno going to start any second now though17:31
bryceheya asac17:31
rickspencer3hehe17:31
asachi bryce17:31
calchi17:31
rickspencer3meeting time17:31
rickspencer3tkamppeter: welcome, are you there?17:31
kenvandine_wki am laggy from the u1 upload that is happening here :)17:31
rickspencer3https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-05-0517:32
rickspencer3I believe seb128 is traveling to the Dx sprint in London17:32
rickspencer3everyone ready to go?17:32
kenvandine_wkyup17:32
rickspencer3Riddell: ready?17:32
* rickspencer3 poke poke17:32
Riddellhi17:33
rickspencer3Let's go a little out of order, start with introducing awe17:33
rickspencer3awe = Tony Espy, and he'll be an honorary desktopper for Karmic!17:33
asac \o/17:34
pittihey awe, welcome to the team!17:34
kenvandine_wkwelcome awe!17:34
* awe hey guys, nice to be part of a the new gang!17:34
* asac waves @ awe 17:34
rickspencer3welcome awe!17:34
bryceheya awe17:34
pittifinally we have our own guitar rock star17:34
awe;/17:34
rickspencer3awe: do you want to introduce yourself briefly?17:34
awesure17:34
awei've spent the last 9 months or so as tech lead on the hp mini17:35
awefor oem services17:35
awemy background is networking plus desktop audio playback17:35
tkamppeterhi, I am17:35
awei've also spent a lot of time working with the kernel team and defining how oem plays with the kernel17:35
awelook forward to working with you all on karmic17:36
* awe done w/intro17:36
rickspencer3sweet17:36
rickspencer3awe: you were a pepper, right?17:36
rickspencer3(pepper = worked on Pepper Pad)17:37
aweyes.  i build an equiv of network-mgr in java for pepper, plus the audio playback subsys based on helix17:37
awes/build/built/17:37
* rickspencer3 <3 pepper pad17:37
asacawe-some ;)17:37
kenvandine_wkhaha17:37
aweplus i play back up guitar for pitti on "wish you were here"  ;)17:38
rickspencer3I know that I speak for everyone when I say that we are really glad to have you on the team, and we're looking forward to seeing what you do in Karmic17:38
awethanks17:39
rickspencer3moving on17:39
rickspencer3actions from last meeting:17:39
rickspencer3ACTION: rickspencer3 to get definitive list of who has talks at all hands to double check that everyone who has one is prepared17:39
rickspencer3I totally FAILed at this, but I'm still trying17:39
rickspencer3there must be a list somewhere :)17:39
pittithe track leads certainly have themm17:39
rickspencer3pitti: good idea17:39
rickspencer3I was looking for the one list to rule them all, but just pinging track leads should work17:40
asacso can we assume that we dont have a talk if we didnt hear anything yet?17:40
pittirickspencer3: or ask cvd, when I talked to her on the phone last week she had the schedule17:40
rickspencer3asac: I think that we *shouldn't* assume that yet, as I am concerned that perhaps some emails were filtered out in spam filters17:40
asacrickspencer3: who would have sent such a mail?17:41
rickspencer3some people got emails saying their talks *weren't* accepted, but it's not clear if this was consistent across tracks17:41
asaccvd?17:41
asachmm.17:41
asacok i will check with brian who submitted the talk17:41
rickspencer3asac: I'll take care of finding out asap and let you know17:41
asacthanks a lot17:41
rickspencer3next topic: UDS17:42
rickspencer3did everyone get their blueprints in?17:42
kenvandine_wkyup17:42
bryceasac, the email started with, "ENLARGE your member ship for your talk like you were on v1agr4!!!1!" you didn't get that one?17:42
asacbryce: oh ... i have more than 100 matches;)17:42
bryceasac: bingo17:43
rickspencer3hehe17:43
pittiI just have two, but they are both quite big, so I don't think I'd like to pile up more for karmic17:43
pittisince I also want to work on the devkit migration17:43
brycerickspencer3: I've gone mine in, but there's too many; probably should trim them down a bit17:43
rickspencer3Riddell: I didn't see Kubuntu blueprints in pitti's link17:43
asacrickspencer3: blueprints without sessions dont need to be in yet?17:43
rickspencer3asac: I suppose so17:43
mihahello guys, 1. ubuntu with desktop effects likes to hang when you press notebook keys such as volume up when playing movies/down, 2. network manager fails to reconnect (you must enter password again and press connect)17:43
pittihttps://blueprints.edge.launchpad.net/sprints/uds-karmic?searchtext=kubuntu17:44
asacrickspencer3: ok. thanks.17:44
pittirickspencer3: they are prefixed kubuntu-17:44
rickspencer3miha: hi, we're in a meeting right now17:44
mihaok17:44
mihasorry17:44
rickspencer3you might want to ask in #ubuntu17:44
rickspencer3no problems, you're welcome to hang out17:44
pittihttps://blueprints.edge.launchpad.net/sprints/uds-karmic?searchtext=kubuntu-karmic- is better17:44
rickspencer3pitti: thanks!17:44
rickspencer3Riddell rocks, as usual17:44
rickspencer3so essentially, pitti and rickspencer3 will sort, prioritize and such by eod Thursday17:45
asacrickspencer3: i will setup a blueprint about NM UI topics (first start, wizard, etc.) in karmic ... thats the only one left i want broader discussion on.17:45
asacdoing that right after meeting17:45
rickspencer3asac: thanks17:45
rickspencer3anyone else have blueprints that need to be submitted?17:45
rickspencer3note that we have two rooms, but are covering Dx, Design, and Ubuntu1 in our track17:46
asacthe prefix is ubuntu-desktop-... ?17:46
asacah ubuntu-karmic17:46
rickspencer3none the less, I'd like to keep a lot of time unscheduled for impromptu sessions17:46
rickspencer3asac: right, the naming convention is ubuntu-karmic-*17:46
pittiasac: desktop-karmic-*17:46
rickspencer3heh17:46
* asac confused ;)17:46
rickspencer3right desktop-karmic-*17:46
rickspencer3(my bad)17:47
rickspencer3Riddell confused me :)17:47
rickspencer3so is everyone good to go with blueprints?17:47
rickspencer3moving on: Desktop Summit17:48
rickspencer3if you are going, please add yourself to the meeting page17:49
rickspencer3I created a little table there17:49
Riddellwhich meeting page?17:49
rickspencer3https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-05-0517:49
rickspencer3Riddell: ^^^17:49
rickspencer3next topic: Triaging versus Bug Fixing/Closing in Karmic17:50
rickspencer3I just wanted to briefly bring this up as pitti and I have both been talking to desktop engineers, and it seems pretty universal that the current mix is not right17:50
rickspencer3I don't want to brainstorm about it here, but ...17:50
pittiit's not so much of a mix, as of a "when to stop?" and "what to look at" questions17:51
rickspencer3I think we should have a UDS talk about how to handle bug inflow17:51
rickspencer3pitti: sure17:51
rickspencer3that's a good way to put it17:51
rickspencer3I wanted to make two points now:17:52
pedro_count me in for that session, I'd love to help with that17:52
rickspencer31. We should tackle this problem as a team, but the implementation of any solutions may look different for each product area, as the problems manifest differently17:52
rickspencer32. We should consider *bold* action in Karmic17:53
rickspencer3pedro_: absolutely!17:53
brycebold action?17:53
rickspencer3bryce: yes17:54
mihaComrades, we stand at edge of cliff. We must make a bold step forwards. (old Yugoslavian joke) :)17:54
rickspencer3like don't think in terms of a 10% increase in throughput17:54
rickspencer3think about a 10 fold increase17:55
rickspencer3stretch your comfort zone17:55
pittibefore we can determine/measure this, we first need to define "throughput"17:55
pittiin terms of "what do we want to achieve"17:55
rickspencer3pitti: hehe17:55
asaci think the ideal goal would be that developers can filter everything not triaged or so to /dev/null and spend all their time on real bug-fix work17:56
asacisntead of bugmail work17:56
rickspencer3asac: that's a great example17:56
pittiI liked the bug gravity idea17:56
asacbug-fix work == fix on own AND work with upstream17:56
asacpitti: what definition of gravity do you like?17:57
pittito make us focus on what's most important, to maximize the usefulness17:57
rickspencer3bryce: make sense? It would be ideal if you felt that you could suggest radical approaches17:57
calcdisable all desktop bug reporting without using apport would help get to the 10x throughput17:57
rickspencer3calc: yes!17:57
asacpitti: for the triaging or the bug-fixing?17:57
pittiasac: number of affected people, type of attached debugging information, number of dups, reported by core-dev member, etc.17:57
asacyeah17:58
pittiasac: triaging17:58
pittiI think once we got a bug to triaged/assigned, we are doing pretty good17:58
rickspencer3I think asac is suggesting "no triaging" for engineers!17:58
pittithe challenge is to pick the "right" ones17:58
asacpitti: i agree, but still developers would get rid of the triaging stage at all if possible17:58
brycerickspencer3: it's still seeming rather ambiguous how to apply to X, but I'm listening17:58
pittiasac: unfortuantely their special knowledge is required very often17:58
asacpitti: thats true, but also depends on the area you look at17:59
pittibryce: I think the point is that everyone shouldl think about the problem from his perspective17:59
rickspencer3bryce: here's a thought exercise, if you only had 1 hour a week to triage bugs, what would yo do with that time?17:59
asacpitti: for mozilla its 99.0% of bugmail that i doesnt require special skills17:59
calcfor eg OOo there is very little if any triaging being done besides me currently, so i think getting the community to do more towards triaging would be needed before having engineers no longer do it17:59
asacjust a guidance and man power17:59
pittiand thus at UDS we can share our thoughts17:59
rickspencer3anywho ... let's bring these ideas to UDS17:59
calcok17:59
asacpitti: well it definitly requires special skills, but not at the early stages18:00
pittiasac: for triaging as in the medical sense ("set priority and look how many are affected"), that's probably very true18:00
rickspencer3I just wanted to plant the seed of thinking bold and trying something new and perhaps even agressive18:00
rickspencer3as pitti put it early "turn the problem upside down"18:00
asacpitti: yeah. for me it would be a huge improvement if my incoming queue would be just bugs that are properly prepared (thats what i refer to for triaging)18:00
pitti"Enter an 11-digit prime number to file this bug"18:01
pitti*cough*18:01
rickspencer3!18:01
asacthe evaluation part of triaging needs to be done by developer. if we are also overloaded on that side we need gravity18:01
asacfor that or more engineers ;)18:01
pittiso, some questions to think about:18:01
pitti - Which kind of your typical bugs would you classify as "something I want to work on", and "something I want to look at", and "something I shouldn't look at"18:02
brycerickspencer3: I guess if I had only an hour to triage, I'd use 45 min to write a launchpadlib script to automate the triaging, and then run that for the last 15 min ;-)18:02
pitti - "how can I organize my bug queues in a way that I can process something to zero without getting overloaded"18:02
kenvandine_wkbryce: good answer :)18:02
pittibryce++18:03
rickspencer3kewl18:03
pitti - "which of my current work can be documented and automated"18:03
rickspencer3any other business?18:03
=== bratsche_ is now known as bratsche
pittio/18:04
pittiI had a topic for -intel18:04
pittiso, we have our first alpha-1 next Thursday18:04
pittiI think it would be nice if we could upload -intel 2.7.0 and turn on UXA by default18:04
pittiso that we can run our karmic "target" architecture for as long as possible, and collect feedback early18:04
pittigiven how long it takes to fix some of those bugs, we can't start early enough I think18:05
pittibryce: do you think that's reasonable?18:06
pittior is there something blocking that?18:06
brycewell18:06
bryceright now we have a lot of UXA bugs, and in talking with Intel I see we have some leverage to get attention on these18:07
bryceif we move ahead and enable UXA I sort of worry Intel may conclude that we no longer consider them blocking issues, and give them less priority18:07
pittibryce: so you want them to fix the first wave of then first?18:07
pittis/then/them/18:07
bryceideally, yes, if it doesn't impact our schedule for KMS enablement18:08
pitti(btw, I enabled that here, but no noticeable difference, even with usplash disabled)18:08
brycewhat I am doing these days is basically 75% triaging/upstreaming UXA bugs and 25% KMS preparations18:08
bryceI've written a script to generate reports on current state of UXA bugs, that I send to Intel18:09
pittiokay, I see18:09
bryceI'll send a copy of the next one to ubuntu-devel@ for transparency18:09
pittibryce: so perhaps 2.7.0 with exa, as in the xorg-edgers PPA?18:09
brycefor KMS, I'm working on putting together a wiki page to howto and capture testing results... link in a sec18:09
brycehttps://wiki.ubuntu.com/X/KernelModeSetting <-- still a WIP18:10
brycepitti: yes 2.7.0/exa is available now from https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/18:10
bryceI can also upload that for karmic... I started doing that but got distracted for some reason.  Should be up this week at the latest.18:11
pittiI just wondered whether there are specific reasons to hold it back18:11
bryceoh yeah I remember - the package in x-updates doesn't have the patches included in our 2.6.3 version, so I need to take time to do the merging18:11
pittibryce: if you say that not enabling it by default yet will increase pressure to fix uxa bugs, so much the better :)18:11
brycethat's the plan :-)18:12
pittiok, thanks for the heads-up18:12
bryceso far there are >20 bugs which will be regressions once we enable UXA18:12
brycethose are freshly tested; and that seems like a lot to me given that people are having to manually enable it at this point, I'd like to cut that down a lot before switching over18:13
rickspencer3bryce: Yingying_Zhao will be hosting weekly calls starting next week, so I'll be able to cover your bug list for you there18:13
brycegreat18:13
rickspencer3any other business?18:14
kenvandine_wkone thing18:14
brycecalc, how's your son doing?18:14
kenvandine_wki will be emailing everyone soon to test an update to u1 :)18:14
rickspencer3meeting adjourned?18:15
brycethanks!18:15
pittithanks everyone18:15
rickspencer3kenvandine_wk: right. What was the uptake on U1?18:15
rickspencer3did everyone on the desktop team install it?18:15
rickspencer3(hint hint)18:15
awe+118:15
kenvandine_wkrickspencer3: i don't have reports from everyone18:15
kenvandine_wkyou, pitti and Riddell for sure18:16
rickspencer3okay, we'll look for your email, and set something up so we can get everyone on it18:16
awekenvandine_wk: what kind of report do you need?18:16
kenvandine_wkwell, bug reports18:16
calcbryce: doing ok now18:16
kenvandine_wkdoes it work for you18:16
kenvandine_wketc18:16
calcbryce: he was sick about a week18:16
kenvandine_wkawe:  basically we want as many people to really use it as possible18:16
kenvandine_wkthere are lots of bugs fixed since last week, so there should be a new package soon18:17
awekenvandine_wk: cool.  i had problems with it a few weeks back, but it's been solid ever since.  nice work18:17
kenvandine_wki will mail the group when it is ready18:17
brycecalc: good to hear18:17
kenvandine_wkit won't sync my data yet :/18:18
rickspencer3thanks kenvandine_wk18:18
rickspencer3calc: glad your son is on the mend!18:18
* rickspencer3 wishes he had a gavel18:18
rickspencer3thanks all!18:18
asacthanks18:18
rickspencer3mdz: hi!18:18
mdzhowdy, desktop folk18:19
kenvandine_wkhey mdz18:19
asacwelcome ;)18:19
brycehi mdz18:19
pittihey mdz18:21
calchi18:22
mihai disabled all gnome effects..this ubuntu cute volume thing doesnt work with dekstop things18:40
mihaand especially not with any movie player18:40
mihacan i complain about that? :)18:40
hyperairwhat if i said no?18:41
mihai already said it :)18:41
hyperairoh whoops18:41
mihahehe18:41
mihais it known bug? does it matter i use ATI and the just support this effects? :)18:42
hyperair?18:42
hyperairi don't understand you18:42
chrisccoulsonhey pitti - i'm looking at getting tracker 0.7.0 ready for karmic. it has a new build-dependency on a package currently in universe though18:42
chrisccoulsonnot sure what to do :/18:42
pittichrisccoulson: disable it, or file a MIR if it isn't crackful18:43
mihahyperair if i have gnome effects enabled,play divx in full screen.. and i either swith program or press volume up, Xorg crashes and then everything hangs18:43
mihaswitch18:43
chrisccoulsoni had a look at disabling it, and it doesn't look possible. the dependency is valac, which i think is only needed at build-time18:43
chrisccoulsoni can file a MIR for that18:44
* hyperair washes his hands off this issue and goes to sleep18:44
mihahyperair sweet tight!:)18:44
mihasleep18:44
hyperaircan't help you there. i'm using intel and got my own share of rubbish18:44
mihahehe18:44
* hyperair glares in the general direction of the intel gpu driver devels18:44
mihahyperair well i disabled effects, again those nvidia kids will brag :(18:44
mihahyperair take care18:45
hyperairthanks18:46
hyperairyou too18:46
pochumiha: you could try nouveau, not sure it will help though :-)18:46
pochumiha: #ubuntu-x sounds more appropriate though18:47
mihapochu i think problem is that these effects dont work with xv on ati drivers18:49
mihai might be wrong18:49
mihai had problems only with moview18:49
mihamovies18:49
pochuoh, you have ati not nvidia18:50
pochuI misread then, sorry18:50
mihayeah, only in newest drivers they even support composite + direct rendering :)18:50
mihai guess it will get better?! :)18:50
pochuanyway it sounds offtopic here, this is not a support channel :-)18:50
mihaokey sorry18:51
mihajust i think such questions are ignored on the help channel :)18:51
mihatake care18:51
rickspencer3bryce: any chance you could weed your blueprints today?18:51
bryceum, yeah...18:52
brycerickspencer3: can we merge desktop-karmic-intel-video-retrospective into one of the others?18:56
rickspencer3bryce: sure, whatever you want18:56
rickspencer3I have to take a call now, can you send mail or ping me this afternoon?18:57
rickspencer3oh wait18:57
rickspencer3actually, we should probably keep that one on it's own18:57
rickspencer3(or cut it)18:57
james_wbryce: there's a jaunty retrospective on the foundations track that it could perhaps be merged in to?19:02
brycejames_w: mm possibly, esp. since we found that the core issues for the -intel driver issues was actually kernel changes needed, not localized to X/userspace19:04
james_wyou could chat to robbie, as it sounds like you would like a couple of kernel people there as well19:05
brycejames_w: you mean pete?19:10
james_wyeah, I guess him too19:10
james_wI meant ask Robbie what he was planning to use the session for, and whether he could pull in a couple of people from each team for it19:10
bryceoh gotcha19:10
brycewell, rick had asked for this session specifically, so I'll leave it to his judgment19:11
bryceI suppose people will appreciate having a dedicated session to complain about all the problems that resulted from updating -intel past 2.419:12
james_wheh :-)19:12
* awe goes offline for awhile... back online @ 4 EDT19:27
artirthe meeting is over?19:28
=== ember_ is now known as ember
=== rickspencer3 is now known as rickspencer3-afk
crevettehello20:03
calcwow that was nice of xorg... it crashed in the middle of me using it20:28
calcnot even on a sleep/resume change or something more obvious like that20:29
chrisccoulsonYou need to add `Option "NoCrashyForCalc" 1` or something to your xorg.conf ;)20:30
calchehe20:32
calcit went to a bright green screen with bits of it blinking then back to gdm login20:32
calcits the first time i've seen it crash in probably a month20:32
chrisccoulsonyeah, i haven't actually seen it crash for many months. although i have had a garbled screen occasionally20:33
chrisccoulsondoes any compiler like gcc display visible strings with proper internationalization?20:40
pittigood night everyone21:18

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