[00:44] <goddard> hello?
[02:28] <TheMuso> ;/c
[04:31] <robertzaccour> The only DE that recordmydesktop outputs 1920x1080 in is Gnome Shell. The others I tried recently (Unity, Xfce, KDE, LXDE) recordmydesktop outputs 1920x1072. Any suggestions?
[05:06] <pitti> Good morning
[07:19] <dholbach> good morning
[07:22] <obounaim> Good morning everybody
[07:49] <tkamppeter> Any thundderbird/email expert around here? How can my gmail account, 6 years of e-mail, 180000 mails take only 3.2 GB whereas my canonical accoung, 10 months, 2800 mails tages 27 GB?
[07:49] <pitti> big attachments?
[07:50] <tkamppeter> pitti, do your Canonical mails also occupy such a lot of space?
[07:50] <tkamppeter> pitti, biggest attachment on a Canonical mail in my box is around 10 MB.
[07:50] <pitti> tkamppeter: not more than usual, but I keep all in maildirs, and delete mail from lists
[07:51] <tkamppeter> pitti, in maildirs they would continue occupying disk space.
[07:52] <tkamppeter> pitti, I use the Canonical account via IMAP, should the inbox then not take space at all?
[07:52] <pitti> I really don't know how Tbird keeps its mail
[07:52] <pitti> but I would think that it does download it
[07:53] <pitti> it would be a ridiculously bad user experience otherwise
[07:57] <tkamppeter> I would like to have locally only some kind of cache, with mails longer not looked at only kept on the IMAP server.
[07:57] <pitti> I use archivemail for that on my mail server, but that's not quite what you want
[07:58] <pitti> $ du -hs ~/.mail
[07:58] <pitti> 31M/home/martin/.mail
[07:58] <pitti> :)
[07:58] <jibel> tkamppeter, you can try to compact your mail boxes if TB is not setup to do it automatically.
[07:58] <vibhav> Will it make sense to open merge requests now?
[07:58] <vibhav> s/open/file/
[07:58] <pitti> vibhav: for raring? sure
[07:58] <vibhav> pitti: What about submitting debdiff's for them?
[07:58] <pitti> https://launchpad.net/ubuntu/raring/+queue?queue_state=1
[07:59] <pitti> raring uploads work, but they are held in unapproved until bootstrapping finished
[07:59] <pitti> vibhav: same answer
[07:59] <vibhav> yes!
[08:04] <tkamppeter> pitti, I have found the problem: Until recently Thunderbird was managinmg IMAP accounts completely onm the remote server, now a recent update introduced taking local copies and so suddenly I had more 27 GB of old mails on my SSD. I have turned off the local copies now and deleted the huge INBOX file. Perhaps Thunderbird is sponsored by HDD/SSD manufacturers now?
[08:05] <pitti> tkamppeter: I think something like "locally cache the last 4 weeks of mail" or so would be a sensible default indeed
[08:05] <pitti> searching through older ones is okay to take some time, while looking at recent ones should be fast
[08:06] <vibhav> pitti: You touched anthy last, could I preapre a merge for it?
[08:06] <vibhav> prepare*
[08:06] <pitti> vibhav: please do
[08:06] <vibhav> thanks
[08:07] <pitti> vibhav: thanks to you!
[08:11] <tkamppeter> pitti, this is really missing, and there is also no function to delete old or otherwise unwished mails only in the local cache and not on the server.
[08:12] <tkamppeter> pitti, so I could only manually remove the cache, by turning off caching, closing Thunderbird, deleting the INBOX file and starting Thunder bird again.
[08:12] <pitti> tkamppeter: FYI, chrisccoulson is our TB maintainer, he might know how to do that in a better way
[08:13] <pitti> tkamppeter: I have never used TB, so I have NFC about this, I'm afraid
[08:27] <tkamppeter> chrisccoulson, I have some problem with Thunderbird. Most recently it seems to have changed defaults and it cloned the whole inbox of an IMAP account to the local disk, being 27 GB in my Canonical Inbox of 10 months. Now is there a way of something like keeping cache of the last 4 weeks? Or removing mails only from the local cache and not from the server?
[08:38] <ev> mpt: I may have been wrong about this after all - still looking into it. But I've definitely fixed those three days.
[08:39] <mpt> ev, have you seen bug 927386? It looks right up your alley -- the error tracker apparently being unusable in Ubiquity :-)
[08:40] <ev> on it
[08:48] <ev> mpt: I've followed up on the bug
[08:50] <tkamppeter> pitti, I have a problem with apport. In Quantal I get a crash window from time to time. When I agree with sending a bug report by simply leaving the default settings of the dialog the report never gets sent. Now progress bar window and and now call of the browser. I have observed that on four different computers.
[08:51] <pitti> tkamppeter: it's sending errors to http://errors.ubuntu.com, not to LP; it's working as intended
[08:52] <tkamppeter> pitti, this is the configuration made for end users, as they probably will no know how to write a bug report?
[08:52] <pitti> right
[08:52] <pitti> and we don't want to flood LP with bugs/crashes from stable releases
[08:52] <tkamppeter> pitti, who gets access to this data? Can I go to ttp://errors.ubuntu.com/ find my data and get it into a bug report?
[08:53] <pitti> ev: ^ I think that's possible for an user, if you figure out your hash, right?
[09:01] <ev> pitti: correct - though currently only people in bugcontrol can access their own reports. We're fixing this.
[09:01] <pitti> ev: tkamppeter should be able to as a developer
[09:04] <ev> pitti, tkamppeter: printf $(sudo cat /sys/class/dmi/id/product_uuid) | sha512sum
[09:04] <ev> pitti, tkamppeter: tack that on the end of http://errors.ubuntu.com/user/
[09:05] <ev> (this is supposed to be in the preferences dialog, but for some reason a new version of activity-log-manager wasn't released in 12.10
[09:05] <tkamppeter> ev, and how do I proceed?
[09:06] <ev> tkamppeter: what do you mean?
[09:08] <tkamppeter> ev, how do I access my data on errors.ubuntu.com.
[09:08] <pitti> open above URL, there you see all reports that you sent
[09:08] <ev> tkamppeter: I just explained. You run the first command that I pasted. That gives you a sha 512 hash. Then put it on the end of http://errors.ubuntu.com/user/ in your browser
[09:09] <ev> so http://errors.ubuntu.com/user/deadbeefdeadbeefdeadbeef
[09:09] <pitti> firefox http://errors.ubuntu.com/user/`printf $(sudo cat /sys/class/dmi/id/product_uuid)|sha512sum`
[09:09] <ev> pitti: cheers :)
[09:09] <pitti> tkamppeter: ^ this is a copy&paste command
[09:10] <pitti> tkamppeter: you can bookmark this, it's a stable URL for each computer
[09:10] <pitti> (NB "computer", not "user")
[09:10] <ev> yeah, I should really change that
[09:11] <vibhav> Is there a way to submit bugs for a ppa via apport?
[09:11] <vibhav> a package in a ppa*
[09:11] <vibhav> Only onnly blueprint\bug report on it?
[09:12] <vibhav> s/only/or/
[09:12] <pitti> vibhav: a PPA package can ship a package hook which sends bugs to the upstream project, if desired
[09:14] <vibhav> pitti: Is that documented anywhere?
[09:15] <pitti> vibhav: in /usr/share/doc/apport/package-hooks.txt.gz
[09:20] <vibhav> thanks pitti
[09:39] <mpt> ev, how much work will it be to add the 13.04 line?
[09:40] <ev> very little. Just waiting for some reports to actually come through :)
[09:43] <mpt> ev, and change the X axis I guess
[09:43] <ev> mpt: to expand to 13.04 release?
[09:44] <mpt> ev, either hard-coded to 2012-04-25, or soft-coded to the latest milestone registered for any release
[09:44] <mpt> er, 2013-04-25
[09:44] <ev> it already does the latter for 12.10 :)
[09:44] <ev> but yeah, definitely need to make this automatic
[09:44] <ev> fetching from Launchpad as you suggest
[09:44] <ev> I get chills every time I hardcode the release numbers somewhere
[09:45] <mpt> Chills are usually for good things...
[09:53] <tkamppeter> ev, sorry, I overlooked your first pastes.
[09:54] <ev> no worries
[09:56] <tkamppeter> ev, pitti, now I can display my data in the browser, but how do I make use of this data set for a bug report, especially if I want to get the core dump into the retracer?
[09:56] <pitti> tkamppeter: errors.u.c. does retracing on its own
[09:58] <tkamppeter> pitti, so I only add a link to the appropriate OOPS to the bug report?
[09:59] <pitti> tkamppeter: we don't usually file bugs for the stable release; but at this particular point in time I guess you can do that
[09:59] <pitti> (raring not open yet)
[10:00] <tkamppeter> pitti, I will use it only in certain selected cases where an SRU would be appropriate.
[10:17] <tkamppeter> ev, pitti, I have found a small usability problem in the web interface of https://errors.ubuntu.com/: OOPSes are sorted alphabetically by their UUID, which is absolutely useless, as UUIDs are more or less random numbers. It would be much better to sort them by date and perhaps also tell in the overview list in which package the problem occurred.
[10:17] <ev> tkamppeter: I'm already aware of it. It's on my todo list.
[10:17] <ev> thanks all the same though
[10:21] <tkamppeter> ev, pitti, thank you very much.
[10:23] <ev> sure thing
[10:25] <ev> tkamppeter: in the interest of transparency, I've moved it into a bug report: https://bugs.launchpad.net/errors/+bug/1069743
[10:49] <vila> hi all
[10:49] <vila> I'm upgrading to quantal and noticed that computer-janitor has been removed. How are the corresponding features handled now ?
[11:09] <vibhav> Would it make sense to merge apt-cacher-ng 0.7.7-2 from sid? The changes in this version are a bit insignificant ( http://packages.debian.org/changelogs/pool/main/a/apt-cacher-ng/apt-cacher-ng_0.7.7-2/changelog )
[11:16] <Laney> no, leave a comment on m.u.c saying so
[11:19] <vibhav> done
[11:46] <infinity> jamespage: Regarding your openattestation upload in the precise queue.  Can you use release versions in  your version numbers instead of codenames?
[11:46] <jamespage> infinity, I can yes
[11:46] <infinity> jamespage: So, 1.5-0.12.04.0 instead of 1.5-0precise1, or something along those lines.
[11:47] <infinity> jamespage: Thanks.  We're trying to break people of the codename habit, since the end of the alphabet's coming up, and it'll sort rather poorly. :P
[11:47] <jamespage> infinity, OK
[11:48] <seb128> infinity, easy solution, don't wrap, just append
[11:48] <seb128> z -> za -> zb, etc :p
[11:48] <infinity> seb128: *grin*
[11:51] <infinity> jamespage: Oh, same complaint in the quantal queue, now that I look over there.
[11:51] <cjwatson> * seb128 is now known as Excel
[11:51] <cjwatson> (though not quite, it did Z AA AB IIRC)
[11:52] <infinity> jamespage: For reference, I'm using versions like "1.6.0-0ubuntu0.12.10" for vmware-view-client.  Might want to use something along those lines.
[11:52] <jamespage> infinity, ack
[11:52] <infinity> cjwatson: Wasn't DOS drive lettering the same?
[11:56] <cjwatson> infinity: I recycled those neurons years ago.
[11:57] <cjwatson> infinity: https://en.wikipedia.org/wiki/Drive_letter_assignment suggests it was a bit more complicated than that.
[12:00] <infinity> cjwatson: I wish I hadn't read that.
[12:01] <infinity> cjwatson: Only Novell would have considered `: a reasonable drive designation.
[12:05] <mlankhorst> infinity: of course! Lets use unicode designations
[12:05] <mlankhorst> 家:
[12:06] <Laney> Ubuntu ☭
[12:25] <vibhav> Laney: Ubuntu Community?
[15:17] <bdmurray> seb128: is there a bug regarding .xsession-errors filing your disk? bug 1069402
[15:23] <seb128> bdmurray, there is bug #1000775
[15:24] <seb128> bdmurray, that's the bug that lightdm doesn't limit the log or truncate it, that doesn't cover whatever buggy app is spamming the log which is an issue by itself as well
[15:25] <bdmurray> seb128: right, okay thanks!
[15:25] <seb128> bdmurray, yw!
[15:37] <doko> mvo, python-apt ftbfs for python3.3
[15:51] <mvo> doko: can you link to the ftbfs
[15:51] <jamespage_> hallyn, around?
[15:51] <doko> mvo, no, local build, deprecated function
[15:51] <mvo> doko: on the product sprint right now, could you mail me the build link?
[15:52] <mvo> doko: eh, sorry
[15:52] <mvo> doko: build log I mean? or past the failure message please?
[15:52] <doko> mvo, will do
[15:52] <mvo> thanks
[15:53] <mvo> doko: hints on how to reproduce also welcome, unless its very difficult
[15:53] <doko> mvo: just build in a raring chroot
[15:56] <hallyn> jamesh: what's up?
[15:56] <hallyn> uh
[15:57] <hallyn> jamespage: what's up?
[15:57] <hallyn> jamesh: sorry, nm
[15:59] <bdmurray> pitti: doe bug 1053749 belong somewhere else?
[16:29] <mitya57> doko: can you please sponsor my fix for sphinx ftbfs (bug 1069894)?
[16:36] <jacobw> hi, is this the right place to seek information on packaging? i'm looking for information about packaging xul extensions
[16:37] <mitya57> jacobw: maybe #ubuntu-mozillateam will be a better place...
[16:45] <jacobw> mitya57: thanks
[18:22] <jbicha> slangasek: so now we have 2 bugs for the efi boot issue, bug 1069475 & bug 1069908
[18:48] <barry> cjwatson: i'd like to avoid having to always say 'raring-proposed' during normal development, and i'd like for only 'raring' to show up in apt-get sources and udd branches
[18:50] <stgraber> barry: changelog and .changes file will just say raring and LP will then redirect to raring-proposed where it'll finally be copied to raring once it's all built and tested
[18:50] <barry> stgraber: perfect :)
[18:50] <stgraber> so for apt-get sources, it'll be raring, not sure how UDD will handle that stuff though
[18:56] <barry> stgraber: that will be fun to see ;)
[19:24] <ptomblin> Hi.  I just discovered (because one of my users knows how to contact me outside of email) that when I upgraded from 12.04 to 12.10 yesterday, it installed this package "mail-stack-delivery", which a) changed mail delivery from MBOX to MailDir b) removed half of my spam tests in postfix/main.cf
[19:25] <ptomblin> The former is pretty important, because it didn't change dovecot imap to show maildir mail, so the users couldn't see any new mail - but that's probably a good thing because if it had changed, they wouldn't have been able to see their old mail.
[19:28] <slangasek> ptomblin: according to the changelog, the mail-stack-delivery package has been present since oneiric; the precise version of the package definitely depended on it; so I don't think you've gotten to the root issue yet
[19:28] <slangasek> ptomblin: in any case, you should probably file a bug on dovecot about the issue, and if you need further help debugging, #ubuntu-server is a good place to find experts
[19:29] <ptomblin> Well, all I know is that I have a spent half the afternoon trying to undo the damage, and now my users are asking how I can get them all the mail they got in the last two days that's stuck in maildirs.
[19:37] <ceolin> hey guys, is there a channel for appmenu or this one can be used ?
[19:38] <jcastro_> #ubuntu-unity probably
[19:39] <ceolin> jcastro_: thanks, i'll try there
[20:25] <gruebert> Greetings.
[20:26] <gruebert> Regarding UDC. . .
[20:32] <gruebert> nexus 7.
[20:32]  * gruebert hangs his head.
[20:34] <gruebert> re: nijaba
[20:40] <gruebert> oh, the silence.
[20:41] <slangasek> gruebert: we could put on some background music
[20:42] <gruebert> oerm.  Some requiem, perhpa.
[20:42] <gruebert> perhaps.
[20:43] <gruebert> So...  how mny babies do I have to eat to get a nexus7 howto?  cause, I might as well kill two birds with one stone.
[20:44] <gruebert> I'm raring to go.
[20:53] <gruebert> Is it possible to stream UDC?
[20:56] <dobey> gruebert: you mean UDS? there will be audio streams available for it next week, when it starts, yes
[20:56] <gruebert> sorry, yes.
[20:56] <gruebert> I'm chomping at the bit to throw 13.04on my nexus7.
[20:57] <gruebert> vnc is meh.
[20:58] <dobey> barry: ping
[21:32] <barry> dobey: pong
[21:34] <jcastro_> We don't call them derivatives anymore do we, we call kubuntu, xubuntu, and lubuntu ... ?
[21:34] <Laney> flavours
[21:34] <jcastro_> ta
[21:34]  * jcastro_ fixes the spelling and moves on
[21:34] <Laney> you'd probably omit the u though
[21:35] <Laney> pip pip
[21:42] <dobey> barry: hey, so i tried to build dirspec nightlies on raring; but it seems py3versions -vr returns python3.3, which isn't getting installed. is py3versions -vr perhaps the wrong way to use it, and one should just use "python3" always in the packaging? or do I need to wait for python3.3 to get in as the default python3?
[21:45] <darkxst> slangasek, can you confirm what changes were made to images for secure boot? it looks like the release cd always boots signed image? which was missing on ubuntu-gnome image
[21:46] <barry> dobey: python3.3 should be a supported version in raring right now, with 3.2 still the default.  i think we're going to need an updated python3-defaults package, probably with the latest experimental version though
[21:46] <barry> or unstable
[21:49] <darkxst> slangasek, are there any other changes we need to make other than including signed kernel?
[21:57] <dobey> barry: is there a way to Build-Depends on "all versions of python3" that isn't "python3.2, python3.3, python3.etc"?
[21:58] <barry> dobey: "X-Python3-Version: >= 3.2" and BD on python3-all|dev *should* do it, and it is a bug if that doesn't work ;)
[21:59] <dobey> ah ok. i just have python3, not python3-all
[22:01] <dobey> will see if that fixes it; thanks
[22:01] <dobey> barry: btw, are you in .dk already?
[22:02] <barry> dobey: not yet.  i'm also distracted today and tomorrow finishing up work on a talk i give on wednesday ;)
[22:02] <dobey> ah no worries. just wanted to make sure i wasn't bugging you too late in the day :)
[22:04] <barry> nope :)
[22:04] <xnox> barry: stgraber: well UDD will do what it does with current SRUs it will update both the -proposed & release branches. And hopefully it will be identical commits....
[22:05] <xnox> as in shared history, but who knows.
[22:05] <dobey> but time for me to head off anyway. later :)
[22:06] <xnox> I had a quick chat but for example if you are working on a transition you may need dependencies from -proposed or test build against proposed if something did not cause the scales tip enough to copy the packages over.
[22:54] <cjwatson> barry: everything should ultimately show up in lp:ubuntu/raring/blah, although possibly with "branch nick: raring-proposed" in some commits - I forget.  If something causes uploads to back up in -proposed it's possible that you may occasionally need to check out from -proposed to get the newest source.  otherwise it shouldn't be a major imposition
[22:55] <barry> cjwatson: that sounds great, thanks.
[23:37] <darkxst> cjwatson, can you confirm what changes were made to images for secure boot? it looks like the release cd always boots signed image? which was missing on ubuntu-gnome image
[23:38] <darkxst> cjwatson,  are there any other changes we need to make other than including signed kernel?
[23:38] <cjwatson> darkxst: make sure you have grub-efi-amd64-signed and shim-signed as well
[23:39] <darkxst> cjwatson, ok will check, thanks
[23:40] <cjwatson> I don't know how you construct your top-level ISO9660 image; live-build / ubuntu-defaults-image won't do the right thing yet, I'm afraid
[23:41] <darkxst> cjwatson, we use the ubuntu image and rebuild the squashfs
[23:41] <cjwatson> our debian-cd instance unpacks the debian-cd_info tarball from d-i and extracts /EFI/BOOT/{BOOTx64,grubx64}.efi from the grub/efi.img therein
[23:41] <cjwatson> OK, that will save effort
[23:41] <darkxst> but efi booting completely broke with the final release :(
[23:41] <cjwatson> we ship grub-efi-amd64-signed and shim-signed as .debs outside the squashfs
[23:42] <cjwatson> darkxst: I expect that it's only on some hardware
[23:42] <cjwatson> unless you're saying that non-SB machines broke too, in which case it's not just about linux-signed
[23:42] <darkxst> well it appears to be trying to boot the signed kernel on non-secureboot
[23:42] <cjwatson> that's permissible
[23:43] <darkxst> cjwatson, not when our image was missing the signed kernel
[23:43] <cjwatson> sure, but in that case it's frankly bizarre that it would be trying to boot it ...
[23:43] <cjwatson> so, sure, shove linux-signed in and see if it helps, but it smells of some other problem
[23:44] <darkxst> cjwatson, grub config points to signed kernel?
[23:44] <cjwatson> you mean when booting the CD itself or after installation?
[23:44] <darkxst> yeh booting the CD
[23:44] <cjwatson> oh, well, that's right there on the top-level iso9660 fs, you could just edit it!
[23:45] <cjwatson> although probably better to include the signed kernel for the sake of the SB machines that get confused without it
[23:45] <cjwatson> (it's not meant to be strictly required, but we haven't tracked down the bug that causes some firmware to throw a wobbly without it yet)
[23:46] <darkxst> cjwatson, yes we have fixed that issue, anyway just wanted to check we arent missing other bits as well
[23:46] <cjwatson> sure
[23:46] <cjwatson> I don't think so
[23:47] <darkxst> cjwatson, I meant the missing kernel is fixed (once we rebuild image)
[23:47] <cjwatson> aye
[23:51] <darkxst> cjwatson, do we need to include the ubiquity update also?
[23:51] <xnox> darkxst: there was one ubiquity update to stop it from removing signed kernels at post-install cleanup. You _do_ want that update ;-)
[23:52] <everaldo> cjwatson, so, we need also to ship grub-efi-amd64-signed and shim-signed as .deb ?
[23:52] <everaldo> xnox, when we rebuild the iso it alerady includes ubiquity updates
[23:53] <darkxst> everaldo, no it pulls ubiuquity from main
[23:53] <everaldo> darkxst, oh :(
[23:54] <everaldo> darkxst, can we build images with updates repo or just wget ubiquity ?
[23:54] <xnox> You do want 2.12.15, and 2.12.16 is a nice to have.
[23:55] <cjwatson> everaldo: darkxst said you were only rebuilding the squashfs, so you should already have that
[23:56] <cjwatson> yeah, you need >= 2.12.15 if you're for some reason not building with -updates enabled
[23:56] <cjwatson> it was all a bit of a mad rush towards the end
[23:57] <cjwatson> everaldo: I wouldn't recommend just wgetting ubiquity; you'd need to get various associated packages as well
[23:57] <cjwatson> copy it into a dedicated PPA if you have some reason not to just build with all of -updates
[23:57] <everaldo> I don't see any problem to include updates
[23:57] <everaldo> darkxst, do you see?
[23:58] <darkxst> yes I think we can enable updates for the rebuild
[23:58] <everaldo> ok, going to do it
[23:59] <darkxst> it would be nice to get the e-d-s fix also, but that is still in proposed I think
[23:59] <everaldo> darkxst, e-d-s ?
[23:59] <darkxst> evolution-data-server (gmail fix)