[02:49] <ophuk> Where can I find information on the automated tests Ubuntu runs on a kernel?
[02:51] <sarnold> ophuk: http://autopkgtest.ubuntu.com/packages/linux
[02:51] <sarnold> ophuk: https://git.launchpad.net/qa-regression-testing/tree/scripts  kernel*
[02:52] <ophuk> sarnold, thanks
[02:53] <ophuk> I might have a few more questions if you guys don't mind
[02:54] <ophuk> Is there a way to run these tests locally?
[02:54] <sarnold> ophuk: you're welcome :)
[02:55] <sarnold> ophuk: the kernel's special, so.. "maybe"? :) here's the wiki on how to use adt-run to run the autopkgtests by hand http://packaging.ubuntu.com/html/auto-pkg-test.html
[02:55] <sarnold> here's the description of how the automated thing is hooked up https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure (way more work)
[02:56] <ophuk> sarnold, lol. Yes it is. Unfortunately at work we have this old kernel with some third party thing and we had to manually patch for dirty cow:(
[02:57] <sarnold> the qa-regression-testing there is .. potentially entangled with a bunch of other things. _probably_ you can just run "cd scripts ; ./make-test-tarball kernel " then follow the directions... copy it to a vm, unpack, and probably ./install-packages ./script-kernel or something like that...
[02:57] <sarnold> ophuk: ouch
[02:58] <ophuk> hmmm, possibly
[02:58] <sarnold> ophuk: be sure to patch for this thing too, it's got a one-shot-run exploit as well https://www.ubuntu.com/usn/usn-3151-1/
[02:59] <ophuk> yeah. We're working on upgrading to a newer version but who knows when that will be
[03:03] <tsimonq2> Debian bug 791040
[03:03] <tsimonq2> Hmmmmmmmmm
[03:10] <tsimonq2> slangasek: Thanks many for feedback regarding freehdl, that's why I think it's a good idea to subscribe the last uploader in Ubuntu to these sort of bugs! :)
[04:26] <sarnold> xnox: does the archive re-org mean 'cppunit' (in universe in newer releases) can be run during the build for packages in main? :)
[04:42] <tsimonq2> pitti: Having problems with systemd-resolvd. I ended up having to manually change my DNS nameserver in /etc/resolv.conf to be able to access major things like Tweetdeck and the CSS for GitHub...
[04:43] <tsimonq2> pitti: Pinging because I *never* had this problem before, and it's a DNS one...
[04:44] <sarnold> note that systemd-resolved has an insanely confusing relationship with /etc/resolv.conf -- in one mode systemd-resolved is a consumer, and in the other mode, systemd-resolved populates it for other things with their own resolvers to consume
[04:46] <tsimonq2> ... /o\
[04:46] <tsimonq2> sarnold: Looks like the former of which Failed Miserably.
[04:46] <tsimonq2> sarnold: Because I had to do it's job... :P
[05:24] <tjaalton> sheesh, the tests can take an eternity to run.. or is there an issue with the CI?
[08:04] <pitti> tjaalton: the "issue" is that it's still catching up with glibc and there was a whole new KDE upload too
[08:04] <pitti> see the queues on /running
[08:04] <pitti> tsimonq2: mind filing a bug with the details? (server/NM, journal, contents of resolv.conf, your network config)
[08:05] <pitti> tsimonq2: with that level of detail I'm afraid I can't help
[08:05] <tjaalton> pitti: hah, ok.. i'll check again next week :P
[08:41] <xnox> sarnold, yes
[08:41] <xnox> sarnold, it also means that header only boost libraries leak into main abi =)
[08:43] <xnox> tedg, /usr/bin/ld: cannot find -lpthreads
[08:43] <xnox> fun
[08:46] <sarnold> xnox: I'm going to pretend I didn't hear that bit :) and leave it to do ko to cope...
[08:49] <Unit193> pull-lp-source is boarked.
[08:53] <infinity> Unit193: Works for me.
[08:54] <Unit193> infinity: Yes sorry, I did a thing that made it hit dde.debian. :3
[08:55] <Unit193> Basically, stupid user thought another service disappeared.
[08:56] <Unit193> (FWIW: pull-lp-source: Error: Unable to retrieve package information from DDE: http://dde.debian.net/dde/q/udd/dist/d:ubuntu/r:zesty/p:certbot/?t=json (<urlopen error [Errno -2] Name or service not known>)  )
[09:05] <nacc> any AA able to help process icingaweb2 and zendframework in the new queue? context is LP: #1593024
[09:29] <Saviq> pitti, hey, have you heard of issues with resolved and go programs? http://rclone.org/ errors out with http://pastebin.ubuntu.com/23602655/ when <IP_ADDRESS> is in resolv.conf - it's fine when I replace it with my real NS
[09:30] <pitti> Saviq: no, haven't heard; does dig @<IP_ADDRESS>:53 drive.amazonaws.com do the same?
[09:30] <pitti> err, without the :53 of course
[09:31] <Saviq> pitti, no, that works fine, I wonder if it's because how it was compiled (building my own now to see)
[09:33] <pitti> Saviq: AFAIK our go compiler uses NSS, but upstream's doesn't, so it should just use straight DNS on resolv.conf
[09:34] <pitti> i. e. dig @<IP_ADDRESS> should be pretty much equivalent
[09:34] <Saviq> pitti, FWIW, rebuilding my own made it work, I'll report the issue upstream
[09:41] <pitti> Saviq: so that might actually be Ubuntu vs. upstream Go compiler behaviour (NSS or not)?
[09:41] <Saviq> pitti, yeah sounds like it
[09:41] <Saviq> depends on what rclone uses to build their bins
[09:43] <pitti> Saviq: so it seems their way of a DNS query looks slightly different to glibc's or dig's, and that and resolved don't understand each other
[09:44] <Saviq> pitti, the error msg actually suggests it couldn't even find <IP_ADDRESS>
[09:44] <pitti> Saviq: hm, that's not how I interpret that error message
[09:45] <Saviq> pitti, yeah, could be interpreted both ways...
[09:46] <Saviq> should probably ask resolved to log requests to see if it even gets asked
[09:51] <pitti> Saviq: you can, start it in verbose mode
[09:51] <pitti> Saviq: this should then also tell you what it's trying to query/forward and where things go haywire
[09:51] <pitti> Saviq: sudo systemctl stop systemd-resolved
[09:51] <pitti> Saviq: sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-resolved
[09:51] <Saviq> pitti, yup, already looking at the log
[09:56] <Saviq> pitti, huh ¿? http://pastebin.ubuntu.com/23602749/
[09:58] <Saviq> so it says it replied, wonder if the CNAME/DNAME resolution makes the difference?
[11:08] <pitti> dannf: manual test run worked \o/
[11:09] <dannf> pitti:  :)
[11:09] <pitti> Laney: ^ arm64 autopkgtest run on bos01
[11:09] <dannf> pitti: shall i try one myself?
[11:09] <pitti> we don't have custom images yet, so test runs will be slow, but that's fine for testing and manual requests
[11:09] <pitti> dannf: not yet, setting up the worker now; this was just a manual "call autopkgtest on the infra" run
[11:10] <dannf> *nod*
[11:11] <pitti> dannf: (still having something else half-committed in the pipe, let me finish that first)
[11:15] <Laney> pitti: nice!
[11:15] <Laney> what changed?
[11:15] <pitti> Laney: nothing really -- the reboot problem already got fixed a while ago, and I just re-verified that everything is okay
[11:16] <pitti> Laney: dannf and I just had a quick meeting about the roadmap
[11:16] <pitti> Laney: so the idea was to start one arm64 worker now but not enable the arch in britney yet
[11:16] <pitti> Laney: so that we can issue manual test requests, but only enable it in p-m once we have the capacity
[11:17] <pitti> Laney: actuall, the existing bos01 workers will take care of it, just adding to "architectures ="
[11:18] <slangasek> rbasak: samba removed from xenial-proposed
[11:19] <Laney> pitti: right - is there more capacity planned?
[11:19] <smoser> pitti, https://blueprints.launchpad.net/ubuntu/+spec/boot-time-optimization
[11:19] <pitti> Laney: yes, it is (that was dannf's side)
[11:19] <smoser>  [pitti] Builds a cloud image and injects package: DONE
[11:19] <Laney> neat
[11:19] <smoser> ^ ? where can i learn more info on that ?
[11:19] <pitti> smoser: see the whiteboard, it points to the script
[11:21] <dannf> Laney: yeah - i think i know what hw to purchase, will try to get it approved. i'll keep you in the loop
[11:23] <Laney> okay!
[11:23] <smoser> pitti, so you "Determining which binaries of source %(src)s are installed and have a new version...'"
[11:23] <smoser> but then what do you do with that info ?
[11:24] <smoser> seems like you should exit if its empty ? ie, you're basically only updating the image if that is inside, right ?
[11:24] <pitti> smoser: see line 77, it then installs these binaries
[11:24] <smoser> but if its empty
[11:25] <pitti> smoser: right, good point; "apt-get install -y" succeeds and does nothing, I had expected it to error out with something like "missing package arg"
[11:25] <smoser> i guess apt does "right" thing
[11:25] <pitti> no, there's little point in succeeding then
[11:25] <smoser> well, it depends on what you want.
[11:25] <smoser> if its not already inside, then essentially you are just adding -proposed
[11:25] <smoser> which i thought maybe you were desiring
[11:26] <pitti> smoser: well, in theory this Should Not Happen™ as we would only practically call it for packages that actually are in -proposed
[11:26] <pitti> but there could be some corner cases
[11:26] <pitti> like, binaries are only available on one architecture
[11:26] <pitti> then the test would run in vain
[11:26] <pitti> it also should not fail as that update doesn't regress boot speed
[11:27] <pitti> but would be nice to succeed fast
[11:27] <smoser> right. yeah, maybe exit SOME_NON_ZERO if not present
[11:27] <smoser> and handle that
[11:27]  * smoser is happy you used mount-image-callback :)
[11:27] <pitti> smoser: handling exit code is not actually all that simple as this all just gets written into m-i-c's stdin
[11:28] <smoser> well, sure it is
[11:28] <smoser> it will exit with whever you told it to in the python popen
[11:28] <pitti> and I want its stdout to stay on the real stdout instead of capturing it
[11:28] <pitti> smoser: ah, good
[11:29] <pitti> smoser: so [ empty ] && exit 99 will reflect in img_shell.wait()
[11:29] <pitti> ?
[11:29] <smoser> i think so , yeah.
[11:29] <pitti> and I can then pass through m-i-c's exit code to the caller of that script
[11:29] <smoser> i mean popen stuff asside. moujnt-image-callaback will exit with the program's return code
[11:29] <pitti> nice
[11:29] <pitti> ok, I'll add that
[11:30] <pitti> smoser: so I'll define a "magic" exit code that means "nothing to do", like "10"
[11:30] <rbasak> slangasek: thank you!
[11:30] <pitti> smoser: and then it would not upload the image either
[12:37] <tsimonq2> pitti: Will do a bit later.
[12:43] <nacc> stgraber: do you mind approving the zendframework binaries now that they are built? it's showing in https://launchpad.net/ubuntu/zesty/+queue
[13:01] <nacc> tjaalton: is dogtag-pki's autopkgtest issues on your plate? it's holding tomcat8 in -proposed, afaict
[13:03] <tjaalton> nacc: tomcat 8.5 broke tomcatjss & dogtag
[13:04] <nacc> tjaalton: ok, it did start failing before 8.5
[13:04] <nacc> tjaalton<EMAIL_ADDRESS>[13:04] <nacc> taken from: http://autopkgtest.ubuntu.com/packages/d/dogtag-pki/zesty/s390x
[13:05] <pitti> dannf, Laney:
[13:05] <pitti> http://autopkgtest.ubuntu.com/packages/gzip/zesty/arm64
[13:05] <dannf> pitti: :)
[13:05] <pitti> dannf: 10min 9s overhead, 1s actual test
[13:06] <Laney> nice, but also eek
[13:06] <dannf> pitti: yeah - is that container creation / other I/O?
[13:07] <pitti> Laney: instances take a while to boot, but most of that overhead really is due to not having an autopkgtest specific iage
[13:07] <pitti> thus this needs to install the full -generic kernel, purge cruft, dist-upgrade and so on
[13:07] <pitti> actually no, I did't call this with setup-testbed
[13:08] <pitti> nevermind, I did
[13:08] <pitti> setup-testbed took 5 mins
[13:10] <pitti> dannf: no, this isn't container, it's full nova instance
[13:10] <dannf> ah, i see
[13:10] <tjaalton> nacc: can't check, but did amd64 pass before
[13:10] <tjaalton> ?
[13:10] <pitti> dannf: Laney is planning some optimization to run tests in lxd containers (on all arches) that don't need a full VM (i. e. 99% of our tests)
[13:10] <pitti> but that's independent
[13:15] <nacc> tjaalton: yes, also a regression there too, i think
[13:15] <nacc> tjaalton: http://autopkgtest.ubuntu.com/packages/d/dogtag-pki/zesty/amd64
[13:15] <Laney> pitti: you making an adt image?
[13:15] <pitti> Laney: not worth the trouble yet; hang on
[13:15] <nacc> passed with 10.3.5-5, started regressing with java-atk-wrapper/0.33.3-11 maybe?
[13:15] <tjaalton> nacc: hmm ok
[13:16] <tjaalton> my browser is frozen atm, I'll check later :)
[13:16] <nacc> tjaalton: thanks -- was just noticing the tomcat8 gating in z-p
[13:17] <tjaalton> anyway, dogtag upstream is finally looking into it, but most likely won't get it fixed before xmas which would be the deadline for stretch (plus 10day migration delay)
[13:18] <tjaalton> so apart from removing tomcatjss & dogtag I don't see a way to unblock tomcat8
[13:18] <tjaalton> oh and freeipa too
[13:19] <nacc> tjaalton: ok, i guess it's not a huge deal, as the SRUs i need to do are all fixed in the version in of tomcat8 that made it into the archive before the dogtag regression
[13:19] <nacc> tjaalton: just sort of odd to see :)
[13:19] <pitti> dannf, Laney: bug 1648810
[13:20] <tjaalton> nacc: yeah that was a bad timing to push 8.5 to debian without checking that rdeps would still build..
[13:21] <nacc> tjaalton: ack, np -- thanks for confirming!
[13:43] <shadeslayer> Hey, does anyone know how long it takes for the supported seed to get updated and where I can check the current list that launchpad knows ?
[13:52] <cjwatson> shadeslayer: the supported seed is in revision control and developer-managed, so I suspect you must be asking about something related but different
[13:53] <cjwatson> shadeslayer: but I don't know exactly what, so can you rephrase your question?
[14:04] <shadeslayer> cjwatson: is there a way to check if the changes we made were deployed ?
[14:05] <shadeslayer> cjwatson: would seeded-in-ubuntu work for the supported seed?
[14:08] <shadeslayer> cjwatson: oh ok it does work
[14:10] <shadeslayer> hm there was a thing to check if you had upload privs to a package too
[14:10] <shadeslayer> ubuntu-upload-permission!
[14:15] <shadeslayer> cjwatson: ref http://bazaar.launchpad.net/~kubuntu-dev/ubuntu-seeds/kubuntu.zesty/revision/1349 , ubuntu-upload-permission -t breeze-plymouth  does not list the kubuntu team
[14:15] <cjwatson> shadeslayer: OK, so you're asking about upload permissions
[14:15] <shadeslayer> yep
[14:15] <cjwatson> shadeslayer: I didn't know about ubuntu-upload-permission; edit-acl in lp:ubuntu-archive-tools is the thing I use, though they're probably equivalent for this purpose
[14:16] <shadeslayer> :D
[14:16] <cjwatson> shadeslayer: anyway, translating seeds into upload permissions is a manually-gated process controlled by ~developer-membership-board
[14:16] <shadeslayer> aha
[14:16] <shadeslayer> clivejo: ^^
[14:16] <cjwatson> I already told clivejo the same thing
[14:16] <shadeslayer> oh I wasn't aware
[14:17] <shadeslayer> well there you go, someone needs offer chocolates to the dmb
[14:17] <shadeslayer> ;)
[14:22] <shadeslayer> cjwatson: thanks for the clarification <3
[14:22]  * shadeslayer goes back into his hole to swear at binutils and dpkg-dev some more
[14:25] <acheronuk> shadeslayer: yes, we are still waiting for that seed change to get translated to our packageset by the DMB
[14:25] <shadeslayer> ack
[14:25] <acheronuk> + you won't see the source name in there, just the 1st listed binary that it produces
[14:26] <acheronuk> I had the SAME confusion very recently ;)
[14:59] <ricotz> pitti, hi, is there another network-manager upload planned?
[15:00] <ricotz> (it could use a rebuild against valac 0.34.4)
[15:08] <pitti> ricotz: not from my side; feel free to just do a no-change upload, although autopkgtest queues won't let this land anytime soon anyway
[15:09] <ricotz> pitti, I see, although I can't upload things ;)
[15:10] <pitti> Laney: I landed the "huge queues" britney part now; should be reasonably safe
[15:10] <pitti> Laney: I'll have a look at it this evening just in case, though
[15:10] <pitti> but I'm off for a bit, sprint just ended and socializing/fresh air and such
[15:11] <Laney> pitti: nice, happy airing
[15:12] <pitti> Laney: will cd ~ tomorrow, so still Sevilla tonight
[15:12] <pitti> it's not like I desperately crave to move from warm Sevilla to icy Augsburg :)
[16:03] <Laney> pitti: I just moved things to -huge
[16:03] <Laney> let's see if that works
[16:05] <Laney> they seem to be bytes instead of strings
[16:05] <Laney> hope that doesn't matter ¬_¬
[17:00] <Laney> it did matter, and I accidently broke huge/amd64 while trying to recover it :P
[17:00]  * Laney tries again to get those back
[17:03] <Laney> a protip is: don't put things in a queue while you're looping over it ...
[20:52] <Laney> should be recovering now
[21:12] <pitti> Laney: ah, nice -- how did you do this, delete all jobs and the britney pending cache?
[21:12] <pitti> Laney: or direct AMQP surgery?
[23:35] <wxl> um, anyone know where i can find the iconv library? we seem to have derivatives of it (e.g. libiconv-hook) but no iconv itself?
[23:35] <tsimonq2> pitti: I believe this is it: https://github.com/systemd/systemd/issues/3826
[23:36] <tsimonq2> !info libiconv
[23:36] <tsimonq2> !info libiconv-dev zesty
[23:36] <wxl> if you think i haven't searched you got another thing coming. i'm just surprised
[23:36] <wxl> https://www.gnu.org/software/libiconv/
[23:36] <tsimonq2> !info iconv wily
[23:36] <tsimonq2> O__o
[23:38] <wxl> oh heh maybe it's in gnulib


[07:21] <shenki> im the reporter of bug 200057, and was wondering who i needed to poke about it
[07:21] <ubotu> Launchpad bug 200057 in linux "HP / Compaq laptops crash with port 0x80 delay write" [Undecided,New] https://launchpad.net/bugs/200057
[07:24] <shenki> it's an issue that will occur with any kernel before 2.6.25, resulting in hard locks galore for owners of affected laptops
[07:26] <Lure> shenki: it might be harder to get kernel developer here over weekend
[07:26] <Lure> shenki: I would suggest to write to ubuntu-kernel mailing list, or try tommorow
[07:26] <shenki> Lure: yeah, i figured
[07:27] <shenki> i've put off doing something about this for long enough, i thought i'd atleast make a start this weekend
[07:29] <pwnguin> sadly, theres a bit of a mismatch between volunteering your weekend to test / fix ubuntu
[07:29] <pwnguin> and being paid to work weekdays fixing the kernel
[10:02] <maks__> ACPI: Remove ACPI_CUSTOM_DSDT_INITRD option
[10:05] <maks__> http://marc.info/?l=linux-kernel&m=120560901809175&w=2
[11:17] <alex_joni> are there any instructions on building custom kernels?
[11:17] <alex_joni> I just built a kernel based on the latest hardy one, but I'm not sure how to build the lum package
[14:05] <kraut> moin
[14:23] <eradicus> moin kraut
[18:58] <jdi9> Sup.  Can someone clue me in on why ALSA and OSS are still in the virtual kernel flavor (since removed from generic)?


[03:44] <HiMtNdRiFtEr> evening
[04:56] <harsha> hi
[15:28] <cmaloney> morning
[15:39] <flipsidecreation> good morning cmaloney
[15:46] <cmaloney> How's the morning so far?
[15:46] <flipsidecreation> good, just working on some making some YouTube videos
[15:48] <cmaloney> Cool deal
[15:49] <flipsidecreation> yeah, a few people have asked me about doing one on kdenlive, which is the software that I use to edit with
[15:52] <cmaloney> Ah, neat.
[15:53] <flipsidecreation> yeah, and you know me as Tom Lawrence, I will be presenting on pFsense at the MUG
[16:04] <cmaloney> God Damn, MySQL innodb is slow
[16:09] <_stink_> flipsidecreation: that's pretty meta
[16:09] <flipsidecreation> ^
[16:09] <_stink_> using kdelive to edit a video about kdenlive
[16:10] <flipsidecreation> yes
[16:10] <flipsidecreation> I could go deeper, make a video on kdenlive about making the kdenlive video
[16:10] <cmaloney> flipsidecreation: Oh, hi there!
[16:10] <cmaloney> Looking forward to the talk in April
[16:10] <flipsidecreation> also, I should change my IRC name to TomLawrence
[16:11] <flipsidecreation> the only real reference I have left to flipsidecreations.com is my mail server
[16:11] <cmaloney> Nah, keep 'em guessing. :)
[16:12] <cmaloney> I changed mine to cmaloney for work after a while
[16:12] <cmaloney> used to be snap-l until it got ridiculous
[16:13] <flipsidecreation> yeah, maybe that will be my weekend project, re-registering with IRC servers
[16:13] <flipsidecreation> I have to work on SEO for my name.  I am being out ranked by Sir Thomas Lawrence
[16:13] <flipsidecreation> and he is dead
[16:13] <cmaloney> heh
[16:14] <cmaloney> I have an engineering professor in my namespace
[16:14] <cmaloney> and some stoner idiot who keeps using my gmail account as his email dumping ground
[16:15] <cmaloney> Had one woman get really upset with me that I hadn't told her about my (thenm girlfriend, now wife) because she thought I was some young Irish Stepdancer.
[16:15] <flipsidecreation> haha
[16:16] <flipsidecreation> Sir Thomas Lawrence was a painter, so I am screwed in regards to doing image searches
[16:16] <cmaloney> Yeah, I'll bet
[16:17] <_stink_> my namesake is a British extreme rock climber
[16:17] <flipsidecreation> that is not a bad association
[16:17] <cmaloney> brb
[22:29] <cmaloney> Evening and all that (at least it will be in the next 30 minutes)
[22:30] <mrgoodcat> is 6:00 official evening?
[22:30] <cmaloney> 17:42 is after sunrise
[22:30] <cmaloney> but I've always heard 6pm was "Evening"
[22:31] <mrgoodcat> never really thought about the exact definition i suppose
[22:31] <mrgoodcat> the period of time at the end of the day, usually from about 6 p.m. to bedtime.
[22:31] <mrgoodcat> ty google
[22:58] <_stink_> so i was saying epiphany is nice the other day
[22:58] <_stink_> i was wrong
[23:00] <cmaloney> It's awesome, or it's not nice?
[23:03] <_stink_> memory use isn't much better than chrome (or might be worse after a few tabs are open)
[23:03] <_stink_> and it's buggier
[23:03] <_stink_> call me fickle :P
[23:03] <cmaloney> Ugh
[23:03] <cmaloney> Fickle. Happy? :)
[23:12] <_stink_> yes!
[23:23] <mrgoodcat> i'm not very surprised
[23:23] <mrgoodcat> browsers are just so complex now
[23:23] <mrgoodcat> it's hard to have one with a low memory footprint
[23:24] <mrgoodcat> especially if modern js/css/html5 standards compliance is a factor
[23:24] <mrgoodcat> and it doesn't hurt to have google backing you when you're trying to squash bugs in such a complex system


[03:16] <KombuchaKip> Anyone know how to get my music to resume playing instead of pausing when I lock my machine under Ubuntu Trusty? Rhythmbox just pauses for some reason.
[03:19] <sarnold> KombuchaKip: I think that's a logind byproduct; I think you can set permissions on audio devices in /dev/ to something your user account can write to..
[03:20] <KombuchaKip> sarnold: Thanks man.
[03:54] <maclin> pitti, hi，the language pack is still 0408 version. Will it be updated before released?
[05:16] <pitti> maclin: yes; the LP export finished yesterday evening; I kicked off the package build, and will test and upload it now
[05:16] <Mirv> maclin: I think the base packages will be updated (too) to the 0410 which is mentioned at https://translations.launchpad.net/ubuntu/trusty/+language-packs - which is needed because only the base packs apparently include help translations
[05:16] <Mirv> ah
[05:17] <Mirv> timing +1
[05:38] <maclin> pitti, thanks. we are waiting for that to test:)
[05:39] <pitti> maclin: would you be willing to test some locally built .debs, as a confirmation that they are good and what you expect?
[05:40] <pitti> I test the German and English ones
[05:41] <maclin> pitti, of course. Our QA team just want to confirm that. Where can we get the debs?
[05:41] <pitti> maclin: hang on (just scp'ing the built sources from the DC machine)
[05:43] <maclin> pitti, good, we are waiting for the Chinese ones:)
[05:49] <pitti> maclin: I put them on http://people.canonical.com/~pitti/tmp/langpack/
[05:51] <maclin> pitti, great, we will get and test, thanks:)
[06:37] <pitti> maclin: how does it look like?
[06:39] <pitti> maclin: they are waiting in https://launchpad.net/ubuntu/trusty/+queue?queue_state=1 now; I accepted all others, as they generally look fine
[06:45] <JackYu> pitti, great, it seems good. maclin is out for a meeting:)
[06:49] <pitti> JackYu: thanks
[07:17] <seb128> good morning desktoper
[07:17] <seb128> brrrr it's cold today
[07:17] <pitti> bonjour seb128
[07:17] <seb128> pitti, salut, ça va ?
[07:17] <pitti> seb128: but still sunny
[07:17] <pitti> seb128: ça va bien, merci ! j'attends avec impatience le releas
[07:17] <pitti> e
[07:18] <seb128> yeah
[07:18] <pitti> seb128: I uploaded fresh langpacks this morning, FYI
[07:18] <seb128> moi aussi, mais j'aurais bien aimé pouvoir mettre à jour quelques paquets tjs
[07:18] <seb128> pitti, nice!
[07:19] <pitti> gedit is back to German for me now
[07:22] <pitti> seb128: Je crois tu peux encore le faire -- parles à infinity ?
[07:22] <pitti> "crois que"
[07:22] <seb128> pitti, oui, je prépare quelques changements là
[07:23] <seb128> but I can see busy SRU time until .1
[07:23] <seb128> so many details/annoyances we didn't get to
[07:23] <seb128> like my ipod showing with an usb stick icon
[07:23] <seb128> dvds still being listed in the UI after being ejected
[07:24] <seb128> it feels like we have been fire fighting until freeze and didn't have time for polish :/
[07:26] <pitti> oh, right, DVDs -- what was that again?
[07:27] <didrocks> an hardware technology
[07:27] <pitti> oh right, these stone disks with enchiseled bits, right?
[07:27] <didrocks> with real objects
[07:27] <seb128> the thing that came after floppies
[07:27] <seb128> I'm pretty sure we still have bugs with those btw
[07:27] <pitti> you bet
[07:27] <seb128> ;-)
[07:27] <seb128> oh can we release with bugs in floppy handling!?
[07:28] <pitti> I'm fairly sure I've seen a bug report about udisks not handling 45 rpm records right
[07:28] <seb128> hehe
[07:28] <seb128> joke aside, lot of polish I want to do for .1
[07:28] <pitti> *nod*
[07:28] <andyrock> seb128, https://bugs.launchpad.net/unity/+bug/1281058
[07:28] <ubot2> Launchpad bug 1281058 in unity (Ubuntu) "The system shutdowns when multiple accounts are open" [High,In progress]
[07:29] <andyrock> it's an oem-priority
[07:29] <andyrock> do I need to open another bug for the UIFe
[07:29] <andyrock> ?
[07:29] <pitti> please, no
[07:29] <seb128> andyrock, no
[07:29] <pitti> it's utterly confusing to track an issue in two dfiferent places
[07:29] <seb128> just retitle the existing one
[07:29] <pitti> seems my right hand is lagging today
[07:30] <seb128> andyrock, Trevinho: btw is somebody investigating the lockscreen giving input to what is behind it sometimes?
[07:30] <seb128> that seems a release blocker/security issue
[07:31] <pitti> ah yeah, the new lock screen is still rather buggy, too -- .1 material for sure
[07:31] <pitti> especially with user switching
[07:31] <pitti> and it still reveals the actual desktop for about a second or so
[07:31] <seb128> right
[07:31] <seb128> though some fixes landed this night
[07:31] <andyrock> well g-s used to do the same
[07:31] <didrocks> yeah, it's like, "it's there. Ahaha! ah no it's not :p"
[07:31] <seb128> I need to upgrade/restart my session
[07:33] <andyrock> so it's not a regression... and using the system-indicator to switch user should call PromptLock that skips fading
[07:34] <seb128> andyrock, you are speaking about the "show for a second", not about the "sometime input is on the win behind the lock" (which can be IRC, annoying when you type your password)
[07:39] <andyrock> sure
[07:40] <andyrock> last time I checked the code there was code to avoid it...
[07:40] <seb128> andyrock, Trevinho: could be https://code.launchpad.net/~sjakthol/unity/fix-grab-after-blank/+merge/215360 ?
[07:41] <andyrock> yep
[08:04] <Laney> hey
[08:05] <seb128> Laney, happy friday! how are you?
[08:06] <Laney> good thanks! happy friday to you too ;-)
[08:06] <Laney> how are you?
[08:06] <seb128> good!
[08:07] <Laney> i see sun and blue sky
[08:09] <Laney> Launchpad (136)
[08:09] <Laney> wtf
[08:09] <seb128> is that the queue?
[08:09] <Laney> bug mail overnight
[08:09] <seb128> oh
[08:09] <seb128> fun
[08:10] <seb128> my inbox was rather quiet this nigh
[08:10] <seb128> t
[08:10] <Laney> erm, weird
[08:10] <Laney> it's mainly translation import errors for cinder
[08:10] <Laney> why in the world did i get those?
[08:10] <Laney> that's an openstack thing
[08:11] <seb128> the bottom of the emails should say?
[08:11] <Laney> not for those, but it does say in the body
[08:11] <Laney> On 2013-10-30 16:41z (162 days 7 hours 48 minutes ago), you uploaded
[08:11] <Laney> ...
[08:11] <seb128> haha
[08:12] <seb128> andyrock, Trevinho: is anyone reviewing https://code.launchpad.net/~sjakthol/unity/fix-grab-after-blank/+merge/215360 ?
[08:14] <seb128> Laney, we are likely going to need an unity upload today btw
[08:14] <seb128> Laney, I hope ^ fixes the "input goes under the lock" issue didrocks&I saw yesterday
[08:16] <Laney> if we can fix that and ideally the grab thing it should go in
[08:16] <seb128> cool
[08:17] <Laney> having a test user in lightdm offends my eyes
[08:17]  * Laney deletes with fire
[08:23] <didrocks> Laney: you reenabled that plugin? :p
[08:23] <Laney> I have a precision blowtorch next to my ssd for such events
[08:26] <didrocks> heh
[08:32] <seb128> Laney, I guess it's too late/not realistic to want to land indicator-keyboard change to use an upstart job? (knowing it would require a one liner change to ubiquity as well)
[08:32] <Laney> probably
[08:32] <Laney> what does it fix?
[08:33] <seb128> nothing reported
[08:33] <seb128> it's just that the indicator would have its own log and be respawned if it hit a segfault
[08:33] <seb128> would also be consistent with other indicators
[08:34] <Laney> I think best not, the time for that kind of stuff has been and gone
[08:34] <seb128> k
[08:34] <Laney> also considering there's been little errors in these things before
[08:34] <seb128> maybe as an SRU (without the path change since ubiquity hardcode directories)
[08:40] <seb128> mvo, hey
[08:40] <seb128> mvo, did we say we should land https://code.launchpad.net/~brian-murray/aptdaemon/bug-1266844/+merge/207276 ? even if it's not a proper solution that's better than no change?
[08:41] <seb128> mvo, that's currently the most reported trusty issue
[08:41] <andyrock> seb128, approved
[08:41] <seb128> andyrock, thanks
[08:41] <andyrock> np
[08:41] <mvo> seb128: didn't I upload this yesterday?
[08:41] <andyrock> seb128, now i've an exam
[08:41] <andyrock> i'll be online
[08:41] <seb128> andyrock, good luch!
[08:41] <seb128> luck even
[08:42] <seb128> mvo, oh
[08:42] <seb128> autopkgtest for aptdaemon 1.1.1-1ubuntu4: FAIL (Jenkins: public, private)
[08:42] <andyrock> this afternoon to fix other bugs ;)
[08:42] <seb128> mvo, it's blocked in proposed
[08:42] <seb128> andyrock, k!
[08:42] <mvo> seb128: meh, can this be overriden? afaik its failing since the begining of time
[08:42] <seb128> hum
[08:42] <seb128> https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job/trusty-adt-aptdaemon/
[08:42] <seb128> yeah
[08:42] <seb128> I wonder how the previous version went through
[08:42] <seb128> I guess somebody overwrote it
[08:42] <seb128> Laney, ^
[08:43] <Laney> I don't see evidence of that
[08:43] <Laney> probably one of the bugs let it in
[08:43] <Laney> It started failing with the ubuntu3 upload
[08:44] <Laney> hang on, might be being misled
[08:44] <Laney> I don't think we have enough history there
[08:45] <Laney> anyway, it didn't fail since the beginning of time but got broken some point this cycle
[08:46] <seb128> mvo, is the test looking like something that can be easily fixed?
[08:47] <mvo> seb128: I check it now
[08:48] <Laney> On ci.debian.net the output includes the diff of dependency and base system changes since the last run
[08:48] <Laney> pretty useful http://ci.debian.net/data/unstable-amd64/packages/p/pango1.0/2014-03-23.log
[08:48] <seb128> nice
[08:48] <Laney> we should get that ;-)
[08:48] <Laney> let me skip this test if mvo is going to look at fixing it
[08:48] <Laney> thanks mvo!
[08:49] <seb128> Laney, mvo: thanks
[08:51] <mvo> Laney: is it possible to (re)test  1.1.1-1ubuntu2 ? I would not be suprised if it actually fails now too
[08:51] <Laney> Dunno about on jenkins, but you should be able to fetch it and do that locally
[08:52] <Laney> Jenkins doesn't seem to keep the first test that failed and the last one that passed so it's not very easy to compare what changed
[08:54] <mvo_> re
[08:54] <seb128> mvo_, wb!
[08:54] <mvo_> silly network
[09:20] <seb128> Laney, not sure if you saw my telepathy-indicator mention on #u-release
[09:20] <seb128> quite busy discussion
[09:20] <Laney> yeah, will look shortly
[09:20] <seb128> thanks
[09:20] <Laney> scripting fun
[09:21]  * larsu hears something about telepathy-indicator
[09:22] <seb128> larsu, trying to land your fix from yesterday evening
[09:22] <larsu> ah cool, thanks
[09:22] <larsu> I wonder what's going on in bug #1259564
[09:22] <ubot2> Launchpad bug 1259564 in indicator-messages (Ubuntu) "GPG_AGENT_INFO not being passed to thunderbird" [Undecided,Confirmed] https://launchpad.net/bugs/1259564
[09:23] <larsu> I guess GPG_AGENT_INFO isn't set in dbus' environment?
[09:23] <larsu> for some reason, indicator-messages was not ported to upstart
[09:23] <larsu> maybe that would help? (or is that moot now anyway?)
[09:23] <seb128> it was not?
[09:23] <seb128> we should maybe have landed those branches from tedg earlier in the cycle :/
[09:24] <seb128> it is, /usr/share/upstart/sessions/indicator-messages.conf
[09:24] <seb128> $ status indicator-messages
[09:24] <seb128> indicator-messages start/running, process 2600
[09:24] <seb128> larsu, use upstart here?
[09:25] <larsu> oh, when did that land?
[09:25] <larsu> I tried a couple of days ago and was sure it wasn't ported
[09:25] <larsu> maybe I was just confused
[09:26] <seb128> larsu, oh, sorry, too much going on, we landed that earlier this week :p
[09:27] <seb128> larsu, ogra needed it for the touch image
[09:27] <seb128> larsu, https://launchpad.net/ubuntu/+source/indicator-messages/13.10.1+14.04.20140408-0ubuntu1
[09:27] <larsu> thanks :)
[09:27] <seb128> larsu,
[09:27] <seb128> $ strings /proc/`pidof indicator-messages-service`/environ | grep GPG
[09:27] <seb128> GPG_AGENT_INFO=/tmp/gpg-n3dktm/S.gpg-agent:2448:1
[09:27] <seb128> larsu, bug fixed? :-)
[09:28] <larsu> seb128: I guess?! I'll mark it as fixed an ask to reopen if it still happens to people. Thanks!
[09:28] <seb128> it's buggy though
[09:28] <larsu> oh it is?
[09:28] <seb128> $ strings /proc/`pidof compiz`/environ | grep GPGGPG_AGENT_INFO=/run/user/1000/keyring-H21sVl/gpg:0:1
[09:29] <seb128> bah, fighting agents
[09:29] <seb128> larsu, not an issue from the indicator though
[09:29] <larsu> seb128: I don't see the problem?
[09:30] <larsu> oh, different agents
[09:30] <larsu> should I reassign to another component?
[09:31] <seb128> larsu, close the indicator-messages bug, saying that specific issue
[09:31] <seb128> is fixed
[09:32] <larsu> ok
[09:32] <seb128> larsu, the other issue seems to be https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1257706
[09:32] <ubot2> Launchpad bug 1257706 in gnupg2 (Ubuntu) "gpg-agent environment variables not correctly exported" [Undecided,Confirmed]
[09:32] <seb128> or similar
[09:33] <seb128> we have a few bugs about fighting agents I think :/
[09:33] <seb128> it's another of those "we should fix that for .1" issues
[09:33] <seb128> https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1271591
[09:33] <ubot2> Launchpad bug 1271591 in gnome-keyring (Ubuntu) "upstart job race prevents gnome-keyring from being ssh agent" [High,Triaged]
[09:34] <seb128> larsu, ^ use that one as reference if you want to point to another bug in your comment
[09:34] <larsu> seb128: too late :)
[09:34] <seb128> k, no worry
[09:34] <larsu> seb128: it's already linked to in a previous comment in the bug
[09:35] <seb128> k
[09:57] <mvo_> pitti: what was the best way again to run a package against adt?
[09:59] <pitti> mvo_: the official docs are in /usr/share/doc/autopkgtest/README.running-tests.gz; which package do you want to test?
[09:59] <pitti> mvo_: i. e. for most packages schroot is enough (and I suppose you have them already)
[09:59] <pitti> mvo_: for some which need network or kernel bits you need to run in an LXC container or even Qemu
[10:01] <mvo_> pitti: as close as possible to what jenkins is doing if possible, I don't really understand the failure for aptdaemon currently
[10:02] <mvo_> pitti: but thanks, I will play with it and see if lxc gives me a similar failure first
[10:02] <pitti> mvo_: I get the failures with simply running the tests on my workstation in trunk
[10:03] <pitti> without any adt-run stuff at all
[10:03] <mvo_> pitti: oh, exactly the same failures?
[10:03] <pitti> mvo_: perhaps not exactly (haven't compared bit by bit), but enough of them
[10:03] <mvo_> ok
[10:04] <pitti> mvo_: as for "exactly what jenkins is doing" -> prepare-testbed and run-adt-test as per http://packaging.ubuntu.com/html/auto-pkg-test.html
[10:04] <mvo_> thanks again
[10:05] <pitti> mvo_: I run "adt-run -o /tmp/out aptdaemon --- schroot trusty" here to compare with jenkins output
[10:05] <mvo_> pitti: please update to the current ubuntu-trusty bzr, I fixes some failures already
[10:05] <mvo_> (I think :)
[10:05] <pitti> ah
[10:06] <pitti> mvo_: seems 1.1.1-1ubuntu4 is already released in the branch, but not in trusty?
[10:07] <mvo_> pitti: trusty-proposed maybe?
[10:07] <pitti> mvo_: ah yes, held back by test failures
[10:07] <mvo_> pitti: I was using the packaging branch - should I use the bzr+ssh://bazaar.launchpad.net/~aptdaemon-developers/aptdaemon/ubuntu-trusty/ ?
[10:07] <mvo_> one?
[10:07] <pitti> so, running
[10:07] <pitti> adt-run -o /tmp/out aptdaemon -U --apt-pocket=proposed --- schroot trusty
[10:08] <pitti> mvo_: yes, that's the one I usually use as well -- it's what Vcs-Bzr: says
[10:08] <pitti> mvo_: oh, you don't use UNRELEASED?
[10:09] <mvo_> pitti: ok, sorry, let me fix that
[10:09] <pitti> or tags?
[10:09] <mvo_> pitti: it should be on unreleased, let me double check
[10:09] <pitti> mvo_: so, I'm not 100% sure that lp:~aptdaemon-developers/aptdaemon/ubuntu-trusty/ matches exactly what's in trusty-proposed, I just hope it does
[10:10] <pitti> changelog-wise it fits
[10:11]  * darkxst really wonders how release week will go with moving and house and probably no internet for a bit ;(
[10:11] <Laney> hopefully you have some ISO testers
[10:11] <mvo_> pitti: I commited my changes now to lp:~aptdaemon-developers/aptdaemon/ubuntu-trusty/
[10:11] <Laney> also luckily with LTSes you have a .1 release
[10:12] <mvo_> pitti: i.e. the ubuntu5 fixes
[10:12] <pitti> mvo_: ah, splendid, thanks
[10:12] <darkxst> we have lots of testers!
[10:21] <pitti> mvo_: hmm, seems the trusty-proposed version hangs in schroot, re-trying in lxc
[10:22] <mvo_> pitti: I have two test failure currently, its slowly improving :) lxc seems to be working for me
[10:22]  * pitti runs both in parallel
[10:22] <pitti> $ adt-run -o /tmp/out-trunk -B .// --- lxc -es adt-trusty
[10:22] <pitti> for your trunk branch; that'll build the branch first and use the built .debs
[10:28] <mpt> Weird, Software Updater’s “Technical Description” pane anti-aliases its text in a different way from everything else on the system
[10:28] <pitti> mvo_: sorry, I need to leave for the afternoon
[10:29] <Laney> I really hate software updater's progress bar when it's checking for updates
[10:31] <pitti> mvo_: so, prepare-testbed and run-adt-test are the ultimate "production" verification
[10:31] <ogra_> Laney, image based upgrades will fix that :)
[10:31] <seb128> Laney, why?
[10:32] <mpt> Laney, that has three factors: (1) It spends a long time checking for updates <https://wiki.ubuntu.com/SoftwareUpdates#Ideas>, (2) recursive references mean it can’t predict ahead of time how many sources will need checking, and (3) the Ambiance/Radiance indeterminate progress bar is poorly designed (hi Cimi:-)
[10:32] <seb128> ogra_, image based upgrades also have a download bar ;-)
[10:32] <darkxst> r0
[10:32] <seb128> ogra_, though the "update" is a spinner for "checking for updates"
[10:32] <ogra_> seb128, yeah, but a predefined set of files
[10:32] <Cimi> ciao mpt :P
[10:33] <Laney> mpt: I think it's mainly (3) that I've got an issue with
[10:33] <Laney> It moves too fast and doesn't move smoothly
[10:34] <mpt> Yes indeed
[10:34] <Laney> Just looks like it's jerking around
[10:34] <seb128> Laney, didrocks: can you please test https://launchpad.net/~ci-train-ppa-service/+archive/landing-011/ (lock screen fixes)
[10:34] <mpt> And it bounces at all, like the Windows one does, which can be misleading if you glance at it at the wrong time
[10:34] <mpt> (specifically if you glance at it when it happens to be against the left edge)
[10:37] <mvo_> pitti: thanks, I'm on it now
[10:37] <Laney> Interesting; that's provided by aptdaemon
[10:39] <darkxst> speaking of aptdaemon (well nearly) what happens when we need an appstream to make gnome-software work?
[10:39] <seb128> what do you mean?
[10:40] <seb128> what appstream exactly?
[10:40] <darkxst> so now all gnome apps have an appdata file
[10:40] <darkxst> but for gnome-software to work, these need to hosted by some server
[10:41] <darkxst> fedora has it, and I think openSuse
[10:41] <seb128> is GNOME having one?
[10:41] <seb128> hum, why is that let down to distros?
[10:41] <darkxst> GNOME is not a distro!
[10:41] <Laney> So it can be used for all apps I guess
[10:42] <Laney> like app-install-data or something, but hosted remotely?
[10:42] <seb128> why does it need a server? can't we have a package containing the db?
[10:42] <darkxst> seb128, that is half-way hack I guess
[10:42] <seb128> "hack", I don't agree
[10:43] <seb128> but yeah, I don't see Canonical working on a such server in the near futur
[10:43] <seb128> not sure, you guys could perhaps have a people page/team/community maintained version
[10:45] <darkxst> seb128, apart from phillw (who has been somewhat ejected from the community), we have no infrastructure resources
[10:46] <darkxst> (outside of what Canonical provides)
[10:47] <seb128> brb, session restart to test unity lockscreen fixes
[10:49] <Laney> seb128: what's it meant to fix? your bug from yesterday?
[10:50] <seb128> Laney, https://code.launchpad.net/~sjakthol/unity/fix-grab-after-blank/+merge/215360
[10:50] <Laney> yeah
[10:50] <seb128> see the description
[10:50] <seb128> I couldn't reproduce that alt-tab problem
[10:50] <seb128> but I guessed the "type through lockscreen" didrocks and I saw could be the same issue
[10:51] <seb128> Laney, in any case just sanity check/test that you have no regression with lock screen
[10:51] <Laney> oh yeah I made that happen
[10:51] <seb128> the alt-tab thing?
[10:51] <Laney> yep
[10:51] <seb128> you saw the UI on top of lock?
[10:52] <Laney> just the alt tab switcher
[10:52] <seb128> k
[10:52] <Laney> now lock screen doesn't get input
[10:52] <seb128> be careful
[10:52] <seb128> the stuff behind might
[10:52] <Laney> and yep, input is going to windows underneath
[10:52] <seb128> like it could be IRC :p
[10:52] <Laney> laney@raleigh> more bar                                                                                ~
[10:52] <Laney> foo
[10:52] <Laney> nah, no IRC on that machine
[10:52] <seb128> workaround to unlock is to use the session indicator
[10:52] <seb128> switch user
[10:52] <seb128> log back from lightdm
[10:52] <seb128> that unlocks the session
[10:52] <Laney> adding the PPA and restarting session
[10:52] <seb128> you are testing without that ppa right?
[10:52] <seb128> cool
[10:56] <Laney> seb128: seems to fix that issue indeed
[10:56] <seb128> Laney, seems to fix the one we were having as well
[10:56] <seb128> let me land that
[10:56] <Laney> nice
[10:56] <seb128> Laney, thanks for testing
[10:56] <Laney> I never had that one so can't confirm
[10:58] <seb128> well, improvement in any case
[10:58] <seb128> let's get that in
[10:59]  * darkxst wonders.... how many servers does canonical have? surely hosting an appstream instance wouldn't even put a dent in it!
[10:59] <Laney> you'd have to talk to the sysadmins
[10:59] <Laney> #canonical-sysadmin @ freenode
[11:00] <Laney> I doubt it's very likely though, most people (LoCos etc) seem to arrange their own sponsorship
[11:00] <seb128> the issue is not bandwith
[11:01] <seb128> it's admin work/security of the machine
[11:01] <seb128> e.g not sure what sort of permissions appstream needs, what security record it has, etc
[11:03] <darkxst> from the public side it would be a read-only stream of data
[11:03] <seb128> how/who would update the content?
[11:04] <darkxst> appdata files come from upstream
[11:04] <seb128> how do they get on the server?
[11:04] <darkxst> a script I guess!
[11:04] <seb128> you need a mechanism/a way to tell it what to import
[11:04] <seb128> the script would list all the upstream in the world with their urls?
[11:04] <seb128> or have an Ubuntu archive to parse
[11:04] <seb128> or?
[11:05] <darkxst> hypothetically the script would parse ubuntu packages for appdata
[11:05] <seb128> k
[11:05] <seb128> well I guess somebody needs to come with a detailed plan first of what would happen on the server
[11:06] <seb128> what would need to be installed
[11:06] <seb128> who would have access, etc
[11:06] <seb128> then you can try asking IS for hosting
[11:08] <darkxst> seb128, ok, I seem to be lacking time these days, but I will get one of my drones onto it!
[11:08] <seb128> ;-)
[11:17] <seb128> nice, today iso is 50M smaller
[11:17] <seb128> seems like to be the langpacks base refresh
[11:17] <seb128> well I guess it is, the manifest doesn't point to actual package dropped from the image
[12:05] <desrt> good morning ubuntistoj
[12:46] <seb128> desrt, hey
[12:47] <desrt> hihi
[12:47] <ochosi> hey seb128
[12:47] <seb128> ochosi, hey
[12:47] <ochosi> seb128: do you think you could review a very simple patch for indicator-bluetooth?
[12:48] <ochosi> or would i better talk to someone else about that
[12:48] <seb128> ochosi, just give the url, I'm sure larsu or charles or cyphermox can do that ;-)
[12:48] <ochosi> ok, well it's not ready yet :D
[12:48] <ochosi> but i basically need to get an alternative depend in for indicator-bluetooth
[12:48] <mvo_> seb128: tests pass !
[12:48] <ochosi> oterwise we pull the unity-stack just for that indicator...
[12:48] <seb128> mvo_, wooot
[12:49] <seb128> ochosi, oh, that I can ack
[13:06] <Laney> hmm
[13:06] <Laney> did someone say there was a click updates bug in u-s-s?
[13:06] <seb128> Laney, https://launchpad.net/bugs/1306569
[13:06] <ubot2> Launchpad bug 1306569 in ubuntu-system-settings (Ubuntu) "Can't update clicks from store with u-s-s #287 on mako" [High,Confirmed]
[13:06] <Laney> I was just fixing the tests (hopefully correctly...) and I think I saw a bug there that might make all click updates be ignored
[13:10] <seb128> Laney, \o/
[13:10] <seb128> Laney, it's weird, the service doesn't even seem activated when I use the panel here
[13:11] <Laney> I don't know how it works really
[13:12] <Laney> so I could be wrong, but the test that checks new updates are shown was failing
[13:12] <Laney> will test it in a bit
[13:16] <seb128> Laney, thanks
[13:16] <seb128> Laney, do you still have an ubuntu codesearch somewhere?
[13:22] <Laney> seb128: same place it always was - http://ubuntu-codesearch.surgut.co.uk/search?weighted=1&q=seb128
[13:24] <charles> ochosi: if it's a packaging patch to indicator-bluetooth, cyphermox or seb128 would be the ones to look at it
[13:24] <charles> ochosi: if it's code, me or cyphermox
[13:25] <Laney> It'll need to call whatever xfce program instead of the control-center
[13:25] <seb128> Laney, weird
[13:25] <Laney> (I guess)
[13:25] <seb128> Laney, http://ubuntu-codesearch.surgut.co.uk/search?weighted=1&q=indicator-keyboard-service
[13:25] <seb128> Laney, doesn't list http://paste.ubuntu.com/7234846/
[13:25] <seb128> Laney, well, ubiquity include the string and is not listed?
[13:25] <Laney> odd
[13:26] <seb128> bregma, hey
[13:27] <bregma> uh-oh, now what?
[13:27] <Laney> ubuntu@codesearch:/srv/mirror-unpacked/ubiquity_2.18.1$ grep -r indicator-keyboard-service *
[13:27] <Laney> bin/ubiquity-dm:                            'indicator-keyboard-service',
[13:27] <Laney> hmm!
[13:27] <seb128> bregma, I did a landing of https://code.launchpad.net/~sjakthol/unity/fix-grab-after-blank/+merge/215360 while you were sleeping, hope it's ok
[13:27] <seb128> Laney, hmm indeed!
[13:27] <bregma> seb128, as long as you do the required paperwork
[13:27] <seb128> bregma, it looks like it fixes the "can type through lockscreen" issue didrocks&I we having
[13:28] <seb128> bregma, what paperwork?
[13:28] <bregma> after final freeze, don't you need to SRU the fix?
[13:28] <andyrock> seb128, https://bugs.launchpad.net/unity/+bug/1306211
[13:28] <ubot2> Launchpad bug 1306211 in unity (Ubuntu) "Trying to lock screen in a guest session leads to an unusable session" [Undecided,New]
[13:28] <seb128> bregma, well, release team judged it important enough to include it as a freeze exception
[13:28] <andyrock> can you still reproduce it?
[13:29] <seb128> bregma, they are still landing some rc fixes today
[13:29] <andyrock> seb128, it works fine here
[13:29] <andyrock> actually there should be no "lock" button in guest session
[13:29] <seb128> andyrock, it took me 10 tries to get it again, and the issue stops if I touch the keyboard
[13:29] <bregma> seb128, I have no problem with that
[13:29] <seb128> bregma, great, was more a fyi anyway ;-)
[13:30] <andyrock> but what you mean for unsable
[13:30] <andyrock> ?
[13:30] <andyrock> lockscreen shows up?
[13:30] <andyrock> or the screen fails to turn on?
[13:30] <seb128> andyrock, no, it dime and wake up the screen in loop, making the session impossible to use
[13:30] <seb128> like screen goes dooown up doooown up dooown up
[13:30] <andyrock> ok
[13:31] <seb128> andyrock, the "lock" is in the "logout" unity dialog
[13:31] <seb128> another unity bug
[13:32] <andyrock> yeah that's another story ;)
[13:32] <seb128> that option shouldn't be listed when lockscreen is locked down
[13:33] <ochosi> charles: ok thanks!
[13:41] <Trevinho> seb128: oh thanks for the landing... Last night just after the final freeze, the fever took me, si I passed a pretty bad night /morning... :(
[13:44] <seb128> Trevinho, :-(, get better!
[13:45] <seb128> Trevinho, https://code.launchpad.net/~sjakthol/unity/fix-grab-after-blank/+merge/215360 might be the issue we were having yesterday
[13:47] <Trevinho> seb128: seb yes very likely.... It's actually nux fault, since when you delete a view that is grabbing, then you should remove the grab also ;\
[13:47] <Trevinho> But this is fine, as we make sure the view is ungrabbed anyway.
[13:48] <seb128> right
[13:48] <seb128> Trevinho, see, it was a real bug, and not me or my box being crazy ;-)
[13:49] <seb128> charles, xnox: https://code.launchpad.net/~seb128/indicator-power/ubiquity/+merge/215424
[13:49] <Trevinho> seb128: yes, in fact I also said that all the ones you report are real bugs :), but just that for some reason you always it them all! :)
[13:50] <charles> seb128, acked
[13:50] <Trevinho> pitti: with last landing and last indicator session, the screen on tty switch is basically shown immediately...
[13:51] <Trevinho> As before we had not a concept of prompt or fading lock. Which now we have
[13:52] <seb128> right
[13:52] <seb128> Trevinho, andyrock: what's the deal with power off, when is it supposed to happen?
[13:52] <seb128> if you lock and don't touch anything it starts diming off after some seconds
[13:52] <seb128> I guess that's wanted
[13:53] <seb128> if you (or your cat) mouve the cursor though, it never goes off again then
[13:53] <seb128> that's a bug?
[13:53] <Trevinho> pitti: btw in some cases I see login1 not to emit the lock signal to us... For example call multiple time the display manager lock. We get that signal only If the greeter wasn't there before
[13:53] <Trevinho> It looks light dm does something strange
[13:54] <Trevinho> seb128: it must go off after the defined desktop idle time
[13:54] <Trevinho> seb128: we use a shorter delay only once
[13:55] <andyrock> Trevinho, i think it makes sense to use a shorter timeout also the second time
[13:55] <andyrock> etc. etc.
[13:55] <andyrock> that's what seb128 is saying
[13:55] <andyrock> right?
[13:55] <seb128> Trevinho, andyrock: doesn't seem to work, let us try
[13:55] <seb128> andyrock, no
[13:56] <seb128> didrocks did "lock, move mouse, walk away" and went away for some hours yesterday
[13:56] <andyrock> seb128, oh so your screen does not dim anymore?
[13:56] <seb128> he uses a timeout of 30 min
[13:56] <seb128> the screen never stopped
[13:56] <Trevinho>  andyrock Not to go against the user preferences (that also might about never use Screensaver)... And say you only locked to hear the music
[13:56] <seb128> Trevinho, andyrock: we just tried with 1 min, doesn't work
[13:57] <seb128> doh
[13:57] <seb128> it's working :p
[13:57] <Trevinho> seb128: it works with 1 sec
[13:57] <seb128> spoke too soon
[13:57] <seb128> ok, maybe a bug fixed in yesterday update
[13:57] <seb128> or maybe another corner case or something
[13:57] <Trevinho> seb128: this wasn't Murphy... :-D
[13:57] <seb128> lol
[13:58] <Trevinho> seb128: we always does it when we get the presence status dorm uss power
[14:02] <Trevinho> From*
[14:04] <seb128> Laney, let me know how the click upgrade stuff goes, I did some pinging of the u1 guys about the issue earlier, I want to unping them if we fix it
[14:12] <xnox> seb128: something weird happens to my sound indicator under ubiquity
[14:12] <seb128> xnox, oh, what?
[14:14] <xnox> seb128: https://plus.google.com/photos/109160032876474505377/albums/6001038263425551073/6001038268744851618?authkey=CKXGwua3-JS1HA&pid=6001038268744851618&oid=109160032876474505377
[14:14] <xnox> seb128: btw it's very painful to share a single photo from G+ without posting it on the feed!
[14:15] <xnox> seb128: i'm dist-upgrading now, and will try without power-indicator to see if there is some weird interaction between them / width limit
[14:15] <xnox> cause, well, Gtk+ =))))
[14:16] <seb128> xnox, urg, looks like a missing icon for mute in the theme? weird
[14:16] <seb128> cool phone case btw ;-)
[14:17] <seb128> xnox, indicator-power seems happy at least ;-)
[14:17] <Laney> are you in bed?
[14:21] <xnox> Laney: haha.
[14:21] <xnox> Laney: i was trying to get the lighting on the screen right for the picture. Got to figure out how to do screenshots properly from cmdline / externally triggered.
[14:22] <xnox> seb128: missing icon sounds interesting. I'll test in the VM properly in a sec.
[14:36] <seb128> Laney, your branch fixes the clicks
[14:37] <Laney> huh, how about that
[14:38]  * seb128 line up a landing
[14:38] <Laney> I'd like gatox to review the changes before they actually go in
[14:38] <Laney> but you can get it underway
[14:39] <gatox> Laney, ack
[14:39] <Laney> ty
[14:39] <seb128> Laney, ah, I was just querying him to ask for that, didn't notice he was there ;-)
[14:56] <xnox> seb128: it's all good, once i booted into proper live cd image, instead of trying to hack things up locally.
[14:56] <Laney> updates panel is buggy if you refuse the update then go back in
[14:56] <xnox> seb128: so go ahead with releasing indicator-power.
[14:56] <Laney> I have a blank panel now
[15:00] <seb128> xnox, great
[15:00] <seb128> Laney, yeah, saw that
[15:00] <seb128> Laney, there is one issue with your update, it restores the bug "tests fail if updates are available"
[15:02] <Laney> it didn't happen because updates were never available?
[15:04] <seb128> ?
[15:05] <seb128> oh, right
[15:05] <seb128> I think it might be the fix for that issue that causes the problem
[15:07] <seb128> Laney, the change was http://bazaar.launchpad.net/~diegosarmentero/ubuntu-system-settings/click-updates/revision/647
[15:07] <seb128> Laney, which was in reaction to https://code.launchpad.net/~diegosarmentero/ubuntu-system-settings/click-updates/+merge/208567/comments/499988
[15:08] <Laney> sec
[15:13] <Laney> seb128: ok, fixed
[15:13] <Laney> the issue is evident in that diff
[15:13] <Laney>         os.environ["IGNORE_UPDATES"] = "True"
[15:13] <Laney>     return value == "IGNORE_UPDATES";
[15:17] <Laney> This means it doesn't have any autopilot tests for when there are updates
[15:18] <Laney> the interaction of the different bugs here is quite funny
[15:26] <seb128> Laney, that IGNORE_UPDATES is a bit weird, wouldn't it make sense to have it a bool as well?
[15:27] <Laney> the other one isn't a bool
[15:27] <Laney> it's a string which says "True"
[15:27] <Laney> it is all weird, didn't want to get too deep
[15:27] <Laney> I'd have just done the normal check for it being set to anything nonempty
[15:27] <seb128> k, makes sense
[15:28] <seb128> well at least it fixes the case
[15:28] <seb128> I'm going to put a silo with the fixes lined up
[15:28] <seb128> gatox, can you review the change, it's small ;-)
[15:28] <seb128> gatox, I'm waiting on the review to land the fix
[15:28] <gatox> seb128, ok, on it now
[15:28] <seb128> gatox, thanks
[15:29] <Laney> the other env var is inverted with respect to this one as well
[15:29] <Laney> so double weird
[15:29] <seb128> yeah, let's clean that later
[15:29] <Laney> it could do with a round of fixes
[15:29] <seb128> indeed
[15:37] <gatox> seb128, Laney need info: https://code.launchpad.net/~laney/ubuntu-system-settings/fix-tests/+merge/215417
[15:38] <gatox> Laney, seb128 about those envs, it's that way because the api to read that, it only returns strings
[15:39] <seb128> is that a qt api?
[15:39] <gatox> seb128, yes, QProcessEnvironment
[15:39] <seb128> k
[15:40] <Laney> of course it does, that's what env vars are
[15:40] <gatox> right
[15:40] <seb128> you can use 0/1 strings though ;-)
[15:41] <seb128> or 0 !0
[15:42] <seb128> Laney, saw gatox's review comment?
[15:42] <Laney> yes
[15:42] <seb128> cool
[15:46] <andyrock> seb128, do you know where are located the xml files for the default rotating wallpapers?
[15:46] <seb128> andyrock, /usr/share/gnome-background-properties/
[15:47] <andyrock> thx
[15:47] <seb128> yw!
[15:48] <seb128> you are adding support for those to the lock screen?
[15:48] <gatox> Laney, ping me when you answer the question or if you do any change, so i review it right away
[15:48] <Laney> I did answer
[15:49] <Laney> basically to say that I don't understand it
[15:49] <Laney> so if you have a better fix then please do it :-)
[15:49] <andyrock> seb128, mmm we can but there was a bug I want try to reproduce
[15:49] <gatox> Laney, my suggestion is just to revert the changes in update_manager.cpp
[15:49] <andyrock> https://bugs.launchpad.net/unity/+bug/1301842
[15:49] <ubot2> Launchpad bug 1301842 in Unity "lockscreen re-locks after unlocking if wallpaper chaged in the backgroud" [Undecided,New]
[15:50] <Laney> gatox: not if you want the tests to work
[15:50] <Laney> try it
[15:50] <andyrock> seb128, i think it's just a duplicate
[15:50] <seb128> andyrock, k, I was going to say that it doesn't seem to highest priority thing to look at
[15:50] <seb128> andyrock,  please look at bugs before adding support for rotating images ;-)
[15:50] <andyrock> seb128, i was looking at bugs ;)
[15:50] <seb128> great
[15:50] <andyrock> just want to change the duration
[15:50] <seb128> cool
[15:50] <andyrock> so i'll not lose 5 minutes of my life
[15:50] <andyrock> :D
[15:51] <seb128> andyrock, you can also do a "sleep 5; gsettings set ...."
[15:51] <seb128> easier way to change the bg
[15:52] <seb128> andyrock, gsettings set org.gnome.desktop.background picture-uri 'file:///dir/image'
[15:53] <andyrock> cool
[15:56] <seb128> andyrock, can't confirm that one
[15:56] <seb128> gatox, so, do you have a suggested change or should we just land that version (we can tweak/improve later)
[15:56] <Laney> I bet the wallpaper is a red herring there
[15:56] <Laney> i.e. Trevinho is correct
[15:57] <gatox> seb128, running the tests here and checking the thing with update_manager.cpp, just a sec
[15:57] <seb128> k
[15:58] <seb128> Laney, andyrock: yeah, likely just the timeout thing
[16:04] <andyrock> seb128, yeah i marked it as a duplicate
[16:06] <gatox> seb128, Laney i just tested it here, reverting the changes in update_manager.cpp, and it works, and the tests are ok too... the other changes are correct
[16:07] <gatox> was that failing for you?
[16:07] <Trevinho> attente: unity side for https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1291461 is done, but is it missing indicator-keyboard?
[16:07] <ubot2> Launchpad bug 1291461 in Unity "Lockscreen: keyboard layout switching shortcuts not working" [Low,Triaged]
[16:08] <Trevinho> attente: as that guy complains something,,,
[16:09] <Laney> gatox: http://paste.ubuntu.com/7235553/
[16:10] <Laney> bzr merge . -r 679..678
[16:10] <Laney> to revert that change
[16:15] <gatox> Laney, i was running autopilot tests... i see, that's because the test is actually wrong, if you want i can fix that and propose a branch
[16:15] <Laney> gatox: yes, the c tests
[16:16] <Laney> please do fix it and push a branch, don't propose it
[16:16] <Laney> I'll pull it into that one
[16:16] <gatox> Laney, ack
[16:23] <Trevinho> Lol, this story is too nice https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303698 :)
[16:23] <ubot2> Launchpad bug 1303698 in unity (Ubuntu) "curiosity killed the trusty tahr" [Undecided,New]
[16:28] <gatox> Laney, there: lp:~diegosarmentero/ubuntu-system-settings/fix-update-not-required-test
[16:30] <Laney> ty
[16:33] <Laney> seb128: I pushed it again, gogogo
[16:33] <seb128> Laney, \o/
[16:34] <Laney> gatox: can you approve the mp?
[16:34] <gatox> Laney, sure
[16:34] <Laney> mergi
[16:34] <Laney> merci
[16:35] <gatox> Laney, seb128 approved
[16:35] <seb128> gatox, thanks
[16:36] <xnox> seb128: Laney: is there some sort of keyboard indicators fixes in the works?
[16:36] <xnox> i'm looking into https://bugs.launchpad.net/ubuntu/trusty/+source/ubiquity/+bug/1301720
[16:36] <ubot2> Launchpad bug 1301720 in ubiquity (Ubuntu Trusty) "[Text Entry] Missing English input in Simplified and Traditional Chinese default enviroment" [High,Triaged]
[16:37] <xnox> and i don't see how ubiquity did anything wrong, since e.g. lightdm login screen has "english" keyboard layout / indicator.
[16:37] <xnox> yet upon login, there is no keyboard indicator and in the keyboard layout panel in the control-center there is no layouts setup what's so ever.
[16:38] <xnox> this is with just ubuntu desktop, executed in chinese locale, not kylin.
[16:38] <seb128> xnox, not sure it's a bug?
[16:38] <seb128> the indicator mixes layout and input methods
[16:38] <xnox> but i will go and test kylin.
[16:39] <xnox> seb128: and in chinese i should have a way to switch to english input method, no?
[16:39] <seb128> so you might have a chinese pinyin input on an english layout regrouped under 1 icon
[16:39] <xnox> i'll test out precise, to see what hapens there.
[16:39] <seb128> check with attente next week
[16:39] <seb128> he's in eow at this time
[16:39] <seb128> xnox, not worth testing kylin, well at least they use a different stack (fcitx)
[16:40] <xnox> seb128: right, i get a weird mini-overlay-popup and i can switch between english and chinese thing. So i think it's not a bug.
[16:43] <seb128> Laney, u-s-s building in https://launchpad.net/~ci-train-ppa-service/+archive/landing-009/
[16:43] <Laney> cool
[16:53] <xnox> i shall not deal with fr locale bugs ever again, i have no idea how to type on the console in that locale
[16:54] <Laney> ZUT ALORS!
[16:56]  * xnox merde...
[16:58] <seb128> ok, have a good w.e everyone!
[16:58] <Laney> you too!
[17:03] <Laney> me too now, see you on monday
[22:02] <xclaesse> what was the trick again to see gnome-online-accounts in the control center?
[22:03] <darkxst> xclaesse, XDG_CURRENT_DESKTOP=GNOME gnome-control-center


[20:59] <MetalnaS> Hi everyone
[21:00] <MetalnaS> I have a java/Mysql/tomcat problem on ubuntu is this an appropriate channel to ask for help ?
[21:01] <nthykier> MetalnaS: Yeah, as long as it isn't programming related
 euuh what seriously ?
[21:03] <nthykier> MetalnaS: It is the right channel for java/Mysql/tomcat problems on Ubuntu. As long as the problem is not how to write java code using Mysql or tomcat
[21:06] <nthykier> MetalnaS: If you need help with coding you want to ask in ##java. They know more than we do
 hmm my web app is working fine on windows but on ubuntu i have an error when its trying to connect to Mysql so is this good ?
[21:07] <nthykier> MetalnaS: Sure, what error does it give you?
[21:09] <MetalnaS> okay great so here's the error http://pastebin.com/xvkcNd68
[21:11] <nthykier> NullPointer? and you are sure it is not just an unhandled case in your servlet?
[21:12] <MetalnaS> and here's the BD class where the problem seems to occur http://pastebin.com/GuQgwbdn
[21:12] <MetalnaS> I think so   i have no errors in my servlet
[21:13] <MetalnaS> and like i said the same code works fine on windows
[21:13] <nthykier> well, I guess DriverManager.getConnection(...) must be returning NULL in the constructor
[21:15] <nthykier> MetalnaS: Have you tried to use the Driver's connect?
[21:15] <MetalnaS> that's what i thought but i tried everything and i'm sure i'm using the right username and pass ..
[21:16] <nthykier> Store the return value of Class.forName(this.driver).newInstance(); + use the "connect" method listed here http://java.sun.com/j2se/1.4.2/docs/api/java/sql/Driver.html
[21:16] <nthykier> if that returns NULL, then the driver thinks it is the wrong kind of driver for the database
[21:16] <MetalnaS> okay i'll do this
[22:01] <MalditoFlanders> hello
[22:01] <nthykier> hello
[22:02] <MalditoFlanders> hi
[22:02] <MalditoFlanders>  anybody can help me to upload an applet into a SIM Card ?
[22:04] <nthykier> I have no clue how that works


[00:49] <bazhang> MINT users casting themselves as victims. I can see it.
[00:50] <bazhang> at one point MINT was using automatix or its descendant as the official codec getter
[00:51] <bazhang> perhaps spawn rather than descendant
[00:58] <bazhang> * [vibhav] (~vibhav___@<IP_ADDRESS>): Vibhav Pant aka "Infinitybot"
[00:58] <bazhang> same user?
 can i have a split screen in gnome terminal
[01:30] <bazhang> possible?
[01:32] <IdleOne> don't think so
[01:32] <bazhang> I better take this to -meta
[02:04] <bazhang> only ops allowed in meta?
[02:04] <bazhang> err -meta
[02:07] <IdleOne> I don't think anybody really knows about that channel
[02:08] <bazhang> augh
[02:08] <bazhang> using ancient hardware and expecting miracles
[05:30] <bazhang> how can one *not * see a huge factoid like gnome3 three consecutive times
[05:31] <rww> because they're being stupid deliberately
[05:32] <bazhang> and a PM in french. quelle surprise
[05:38] <rww> I'm getting kinda tired of how often "pr0n" comes up in #ubuntu-offtopic.
[05:39] <bazhang> I find #defocus to be less troll infested than there
[05:39] <rww> Less troll-infested, but less moderated. So the smaller number of trolls make more noise :|
[05:49] <bazhang> get ryanxb on that one
[05:57] <bazhang> thought the mac makeover was fairly invasive
[07:31] <trijntje_oneiric> Got spam from<EMAIL_ADDRESS>while joining
[07:31] <rww> I'm looking into it, thanks.
[07:32] <trijntje_oneiric> cool, thanks
[07:36] <ikonia> Newss = onjoin spam
[07:37] <ikonia> doing the same in #debian
[07:37] <ikonia> newss was using 08:22 -!- Newss<EMAIL_ADDRESS>has joined #ubuntu
[07:38] <rww> As I mentioned elsewhere, they weren't doing it for me. Perhaps I am special.
[07:38] <ikonia> I got it
[07:38] <rww> fun
[07:38] <rww> before or after people started complaining about it?
[07:39] <ikonia> now, I just did a test
[07:39] <ikonia> 08:36 -!- Irssi: Starting query in freenode with Newss
[07:39] <ikonia> 08:36 <Newss> hi 13 year asia girls sexy camshow http://to.ly/aMjP
[07:39] <ikonia> 08:36 <Newss> hi 13 year asia girls sexy camshow http://to.ly/aMjP
[07:39] <ikonia> 08:38 -!- Newss<EMAIL_ADDRESS>[07:39] <ikonia> 08:38 -!-  ircname  : %lili
[07:39] <rww> ah, just got it in #debian
[07:39] <ikonia> my current timestamps is 8:39
[07:40] <ikonia> and gone from debian too
[07:40] <ikonia> trijntje_oneiric: thanks for the info
[07:48] <ikonia> hello lotuspsychje
[07:48] <ikonia> trijntje_oneiric: we ask that you leave the channel now that your business is done so we can assist other people
[07:48] <lotuspsychje> was just checking out, im already leaving
[07:49] <ikonia> lotuspsychje: checking out ?
[07:49] <ikonia> lotuspsychje: do you need something ?
[07:49] <lotuspsychje> reported spam to an op
[07:49] <ikonia> lotuspsychje: ahh, the user newss ?
[07:49] <lotuspsychje> yeah
[07:49] <ikonia> he's been delt with, thank you
[07:49] <trijntje_oneiric> ikonia, sure, didnt see that in the topic. Thanks for your help!
[07:49] <ikonia> trijntje_oneiric: thanks for yours
[07:49] <lotuspsychje> ok tnx good day
[08:03] <ikonia> has anyone read this
[08:03] <ikonia> http://www.ubuntu.com/certification/hardware/201104-7945
[08:03] <ikonia> what an utter joke - Canonical are listing hardware as certified
[08:03] <ikonia> but then making the point that "standard ubuntu installs may not work"
[08:10] <ikonia> @mark #ubuntu Pwnna complaining about bugs - but won't report them himself
[08:54] <ikonia> bazhang: as a suggestion, I've found asking to pastebin the output of sudo apt-get update works better, as that captures what repos are active, which includes repos which may not be  in sources.list
[08:54] <bazhang> ikonia, nice one, will do
[08:55] <ikonia> bazhang: it's only a thought, but I've been caught out with sources.list that are fine, but repos are configured elsewhere
[09:00] <ikonia> lots of bad repos there
[09:01] <bazhang> but the ubuntu one is one where its choking, ie the gpg
[09:02] <ikonia> looks like dns
[09:27] <elky> ask for the hosts file?
[09:27] <ikonia> long resolved I believe
[09:29] <elky> yeah i noted the timestamp after i said that
[09:30] <ikonia> time to go for me, laters
[09:30] <elky> ciao
[09:52] <Myrtti> nnnngggh
[09:53] <Myrtti> anyone else looking at -ot?
[10:13] <elky> will look now
[10:13] <elky> oh, already dealt with
[11:10] <IdleOne> jrib: bluegoon asking about ATI in -ot and aspect ratio in #u
[11:10] <IdleOne> confuzzled me. didn't mean to toss them back into your lap :)
[11:10] <elky> IdleOne, <bluegoon> Er, hey chaps, I have a giant red "1" in the top left of my screen, its in a red box.
[11:11] <elky> that's the kind of comments he was making in #u, i interpreted them as g+ trolling as well.
[11:11] <IdleOne> hmm
[11:11] <jrib> ah
[11:11] <IdleOne> ok so it isn't me :)
[11:11] <Myrtti> top left != top right
[11:13] <elky> Myrtti, yeah, but that takes looking twice
[11:13] <elky> when all he was crapping on about was a red box with a 1 in it.
[11:13] <Myrtti> and I'm the best person to remind about the difference
[11:13] <elky> hehe
[11:13] <Myrtti> Vasen means left and Oikea means right in Finnish
[11:13] <Myrtti> the old joke is that I'm one of those persons who should allowed to drive Volvos only
[11:14] <elky> hehehe
[11:14] <Myrtti> as they've got the reminder of which is left and right on the steering wheel
[11:28] <popey> hah
[12:40] <bazhang> * [Johny_Mnemonic] (~john@<IP_ADDRESS>): John   was +q earlier, changed IP and rejoined
[12:45] <IdleOne> bazhang: ^ is back
[12:46] <IdleOne> * Johny_Mn1monic<EMAIL_ADDRESS>has joined #ubuntu
[12:47] <bazhang> IdleOne, yep, got him in PM now. hopefully he responds this time.
[12:59] <oCean> do you think this is a common problem? https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469
[12:59] <oCean> the list with duplicates is the longest I've seen :(
 .  ..  Mac OS X Snow Leopard.vmdk
[13:19] <bazhang> thought that was illegal
[13:20] <oCean> I've heard/read so before
 käften  <-- shut up
[13:22] <oCean> oh nice
[13:22] <elky> its only illegal if it's not on apple hardware.
[13:22] <elky> iirc, ianal.
[13:23] <oCean> so, on vbox on ubuntu is nog legal?
[13:23] <oCean> *not
[13:23] <elky> not unless it's on non-apple hardware. we need not ask that.
[13:23] <oCean> right
[13:24] <elky> licencing is hard ;)
[13:24] <bazhang> http://stackoverflow.com/questions/39159/is-it-possible-to-run-osx-in-a-virtual-machine
[13:25] <bazhang> its vmware, and server is legal, but desktop is not
[13:25] <elky> Note: Virtualization is legal only on Apple hardware. – Eonil Jun 24 at 16:46
[13:26] <elky> we also tolerate discussion of virtualised microsoft environments, which is not explicitly legal in all circumstances either.
[13:29] <elky> I think it's one of those areas where unless it's immediately obvious there's illegal activity, we have to assume best of the situation.
[13:30] <bazhang> he showed us the vmdk as being snow leopard desktop
 .  ..  Mac OS X Snow Leopard.vmdk
[13:33] <elky> And had you not explicitly decided to investigate, we, as non-lawyers, would not have known. Do we now ban every mention of desktop osx in #u?
[13:33] <bazhang> there was no investigation. I knew it was illegal, and he posted it there in the channel.
[13:34] <elky> Do we now ban every mention of desktop osx in #u?
[13:34] <elky> Because I've certainly over the past 5 years seen many mentions.
[13:35] <bazhang> being lawyers is beside the point. discussing warez, etc is offtopic on freenode
[13:36] <bazhang> there's even a factoid for illegal.
[13:36] <elky> was he advertising a service of distributing that vmdk?
[13:36] <bazhang> but if hackintosh is now a-okay, then we need to change the factoids
[13:37] <elky> discussing warez != "i have an osx vm"
[13:37] <bazhang> "some illegal activity we'll turn a blind eye to"
[13:37] <ikonia> hackintosh is not ok
[13:37] <oCean> I agree, I don't like to give opportunity to discuss warez etc
[13:37]  * elky gives up trying to get a straight answer and tries to match timestamps.
[13:38] <bazhang> not apple hardware = illegal for desktop. simple.
[13:39] <elky> what. was. the context. that. you are getting riled up over?
[13:40] <elky> because outlawing mentioning a mere mention of vms that are not linux is going to be very very tedious.
[13:41] <oCean> the context is "help me conver Mac OS X Snow Leopard.vmdk to .vdi, so I can run it on my ubuntu
[13:41] <oCean> *convert
[13:42] <elky> oCean, thanks.
[13:42] <bazhang> elky, is this your personal view, or a judgment as a member of the IRCC
[13:42] <elky> That's what I was after. That is clearly out of bounds.
[13:43] <bazhang> ok
[13:43] <elky> bazhang, you seem to think those two categories of view are mutually exclusive.
[13:45] <elky> so what you were actually wanting to say was "that was a discussion of piracy". Because it was a discussion of piracy.
[13:49] <oCean> it's very common that he will change his question to,  Oh but I meant how to convert SomeRandomAppliance.vmdk to vdi
[13:50] <elky> and if he does, we just need to remind him that it's illegal to do it for mac/win when we give the information.
[13:51] <elky> and that the channel is logged if need be.
 15:53 <suzy_> hi girls sexy show cam? http://webcams.de.nu   <-- onjoin spam he reported
[13:59] <bazhang> nothing when I /cycle
[14:01] <oCean> what can we do? We need multiple reports?
[14:01] <bazhang> I suppose. I PM'd them and no answer yet
[14:03] <elky> sometimes they have cycling prevention built in.
[14:04] <elky> nothing for a new connection
[14:20] <bazhang> 2nd complaint about suzy_
[14:21] <oCean> I saw
[14:21] <ikonia> same ip range as the other guy I banned
[14:21] <ikonia> same ip range, same channels
[14:21] <ikonia> I'd take that as the same issue
[14:30] <bazhang> ikonia, what test? to ID backtrack users, that is
[14:30] <bazhang> hang in the backtrack channel?
[14:30] <ikonia> bazhang: nothing concreate, just a message on the other channel,
[14:30] <bazhang> aha
[14:30] <ikonia> there we go
[14:33] <bazhang> does backtrack have some identifiers in their sources.list? or the kernel?
[14:34] <ikonia> yeah, some really annoying stuff too, things like xchat responds with ubuntu
[14:34] <ikonia> although the repos should point at the backtrack ones
[14:34] <ikonia> maybe worth a look at apt-get updae
[14:34] <ikonia> update
[14:39] <bazhang> pm from skaperen
[14:40] <ikonia> oh ?
[14:40] <oCean> me too
[14:43] <bazhang> claiming victimhood
[14:44] <bazhang> cybervolfe looks like running ubuntu, unless I am missing something from that pastebin
[14:45] <ikonia> agreed
[14:45] <oCean> it's not his first entry in BT (skaperen I mean) 40756 kicked by Ikonia for same kind of discussion
[14:46] <bazhang> says he is banned here, cannot join
[14:46] <ikonia> I don't thats actually his apt-get update
[14:46] <ikonia> he's in India yet his fastest mirror is USA ?
[14:48] <bazhang> nope not banned here. skaperen that is
 I went to #ubuntuanswers
[14:53] <bazhang> claims he is forwarded there
[14:53] <oCean> huh
[14:54] <bazhang> and surprise; that is not a registered channel
 in the mean time you or someone (but not oCean) might want to revise or append the guidelines to handle things like this
[15:05] <oCean> append what?
[15:05] <ikonia> or he may want to ammend his attitude
[15:05] <ikonia> I suggest that's more realistic
[15:06] <bazhang> append his special situation so he's right and we're wrong, I guess
[15:06] <bazhang> now he claims his server is out of sync, so cannot join here
[15:07] <oCean> out of sync!
[15:08] <ikonia> close the window and have a drink,
[15:08] <ikonia> this sort of nonsense will waste the day
[15:10] <oCean> I closed the pm long ago. He can report here, and we can discuss his "special situation"
[16:08] <rww> ikonia: apparently, it's enough for Canonical that customized images with additional drivers work. As someone who dislikes proprietary hardware drivers, I will be skipping anything that says "(Pre-installed only)" on the side ;)
[16:18] <ikonia> rww: I actually think it's really really poor
[16:18] <ikonia> that's like me cerifying my mac for Sega Master system OS as long as you install all the extra bits to make it work
[17:05] <gord> well no its not
[17:05] <gord> if someone sold a mac that had the master system OS on it with all the bits you needed, then it is
[17:05] <ikonia> expand ?
[17:06] <ikonia> ok, I still feel it's very poor that caonical are certifying hardware for...."special" ubuntu,
[17:06] <ikonia> gord: a valid point
[17:07] <gord> if its stuff you just can't get your hands on, that sucks, that shouldn't be certified, but i'm guessing its restricted drivers and such you can download
[17:07] <gord> i mean if we restricted it to the base system then most nvidia machines couldn't be certified
[17:07] <ikonia> gord: it has no notes on it, it bascially says stock ubuntu may not work
[17:07] <ikonia> which for me is nuts to certify for ubuntu...but it doesn't work
[17:07] <ikonia> thats just me, I think the whole project is getting sloppy
[17:58] <ikonia> I don't think nvidia or ati should be certified unless there is a supported package in the main repo
[18:43] <io> is this the place to report inconsistencies with ubottu?
[18:44] <oCean> hi io
[18:44] <oCean> what is the actual issue?
[18:44] <io> hi :-)
[18:44] <io> 19:42 <io> tor
[18:44] <io> 19:42 <ubottu> Tor is a program to route connections through several servers for anonymity. It is not in Ubuntu's repositories. For setup info, see option (2)  of https://www.torproject.org/docs/debian.html.en | To use Tor on freenode, see !tor-sasl
[18:44] <io> 19:42 <io> info tor
[18:44] <io> 19:42 <ubottu> tor (source: tor): anonymizing overlay network for TCP. In component universe, is optional. Version <IP_ADDRESS>-1 (natty), package size 1016 kB,  installed size 2104 kB
[18:44] <io> it's clearly in the repositories
[18:45] <oCean> right
[18:45] <io> so I think the factoid needs to be fixed?
[18:45] <oCean> probably an old factoid still
[18:45] <oCean> yes, we'll fix it
[18:45] <oCean> thanks for the input
[18:46] <io> nothing major, I just noticed - thank you
[18:46] <io> o/
[18:57] <oCean> Unfortunately https://help.ubuntu.com/community/Tor is outdated, and even for 11.04 still pointing to the deb.torproject.org repository
[18:57] <oCean> but since natty it's back in universe
[19:02] <oCean> os2mac: ping
[19:03] <oCean> os2mac: may I remind you of your previous visit? You left us with "sorry... I need to delete this room from my auto start menu... I don't have an issue"
[19:05] <rww> !-tor
[19:06] <oCean> suggested rewording:
[19:06] <oCean> Tor is a program to route connections through several servers for anonymity. Since 11.04 it's back in the repositories (Universe). For previous versions see https://help.ubuntu.com/community/Tor | To use Tor on freenode, see !tor-sasl
[19:06] <oCean> ok?
[19:06] <rww> !tor =~ s/not in Ubuntu's repositories/in Ubuntu's repositories, but the Tor Project recommends against using distribution packages for security reasons/
[19:06] <oCean> the community/Tor link is a bit poor though
[19:06] <oCean> ?
[19:06] <oCean> is that the case?
[19:07] <rww> Yes. See the URL linked in the factoid.
[19:08] <rww> hrm, not that factoid.
[19:08] <oCean> but it's back in universe
[19:08] <rww> oh, yes that factoid. you removed it when you reworded
[19:08] <oCean>  https://www.torproject.org/docs/debian.html.en
[19:09] <oCean> I read that
[19:09] <rww> "Do not use the packages in Ubuntu's universe."
[19:09] <rww> it's in bold ;)
[19:09] <oCean> yes but is it true
[19:09] <oCean> I mean, isn't that an outdated statement?
[19:09] <oCean> after hardy it was not in the repositories
[19:09] <rww> In my opinion as a Tor user, Tor users should be using the Tor repositories for Tor.
[19:09] <oCean> but it returned in natty
[19:10] <rww> This conflicts with my opinion as a channel op, which is that we shouldn't recommend non-Ubuntu repositories, but the first ended up overriding the latter.
[19:11] <oCean> hmm.. in that case "unmaintained and out of date" I don't like it being available through universe anyway
[19:11] <rww> Neither do I or the Tor devs ;)
[19:12] <rww> and Tor is not as... forceful... as Mozilla, and thus doesn't get its packages upgraded to new major versions in SRUs :|
[19:14] <rww> (incidentally, I believe that Tor appearing and disappearing from Ubuntu is a direct result of it appearing and disappearing from Debian, which tends to get even more out of date than Ubuntu)
[19:15] <rww> (also incidentally, this is one of the very few pieces of software that I don't feel !latest reasonably applies to, because I am skeptical of our distros' tendency to keep up to date with security vulnerabilities, and the stakes are very high for something like Tor)
[19:19] <oCean> ok, I understand. Good enough reason to have the factoid mention this
[19:19]  * rww ponders tracking down some tor devs and having a chat about the current state of Tor things on Ubuntu
[19:20] <rww> because we /could/ be backporting this stuff in security updates, and I'm wondering whether anyone's trying to do this.
[19:23] <oCean> both provide <IP_ADDRESS>-1 atm
[19:25] <rww> oCean: I'm going to grab the relevant packages when I get home and see who the points of contact are for this.
[19:25] <oCean> great!
[19:26] <rww> because if Debian's Tor packages are acceptable now, then this really shouldn't be too difficult to hash out. I suspect someone just needs to grease wheels a bit.
[19:27] <oCean> sounds cool, would be nice if it only needs a little grease :)
[19:37] <rww> ubottu: bug 697407
[19:37] <rww> oCean ^^
[19:38] <rww> so apparently I'm wrong again: there allegedly is an SRU exception already
[19:40] <oCean> aha
[19:42] <rww> although now that I think about it... there's Tor packaging for 6.06, 8.04, 11.04, and 11.10. 11.04 and 11.10 are up-to-date with Debian and the Tor project repository. 6.06 and 8.04 are EOL on non-servers, and I doubt that Tor's on the supported packages list for server 5-year support.
[19:43] <oCean> So, we're already in sync, and nothing need be done for those older releases?
[19:44] <rww> 6.06 and 8.04 are probably screwed as far as support goes (I'm trying to find the list of packages we'
[19:44] <rww> re still doing updates to for them)
[19:45] <rww> so torproject.org is probably better than nothing (assuming it's been keeping them up to date). 10.04 and 10.10 don't have Tor packaging in our repositories, so those users have to use torproject.org.
[19:46] <rww> 11.04 and onwards may be okay to just use our repositories, and from the look of the version numbers, even if you do add torproject.org's repositories it'll use Ubuntu's package, because the torproject.org package has a ~natty+1 attached to the version number
[19:47] <rww> one question though is what Ubuntu (and Debian, for that matter) are doing as far as security updates for Tor packages in our repositories. If we're not updating them and torproject.org is...
[19:47] <rww> yup, torproject.org's staying up to date for 6.06 and 8.04.
[19:49] <oCean> what's the ~natty+1 ?
[19:49] <oCean> in the version nr
[19:50] <rww> oCean: effectively, 1.2.3~something is a lower version number than 1.2.3 as far as apt-get's concerned. It looks like the packages were backported to older releases and that tag added so the package would be replaced by a newer version from Ubuntu's repositories when the user upgrades.
[19:50] <rww> well, "newer"
[19:51] <rww> "same actual version or newer", I guess
[19:51] <rww> oh, duh, 6.06 is EOL completely now. so we can cross that off the list.
[19:52] <oCean> right, so there might not even be any grease required?
[19:52] <oCean> wheels are turning already :)
[19:53] <rww> on Ubuntu's side of things, we might be covered if Tor's getting updated appropriately already. I need to check that. On Tor's side of things, if we're doing things right, we need to tell Tor that so the page can be changed.
[19:53] <rww> anyways, back to my day job. ttyl.
[19:53] <oCean> rww: thanks man
[20:01] <Daviey> rww: ~ means less.  1~foo < 1
[20:02] <oCean> less is more!
[20:02] <oCean> more or less
[20:03] <oCean> Daviey: so what does ~natty+1 mean?
[20:06] <Daviey> oCean: For an SRU, a package cannot be higher than the version in the next release.  You can't add a binary which is already released in a newer release.
[20:07] <Daviey> (the convention is growing to use the release version number)
[20:08] <Daviey> Example, https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
[20:08] <Daviey> backports follow the ~distro1 convention.
[20:09] <oCean> ahh, thanks
[21:13] <oCean> bazhang / elky pooltable returned with his vmdk/vdi question I've send him a link after telling him: we cannot help you with illegal activities such as trying to run mac images on other than mac hardware.
[21:13] <oCean> all I've heard from him since, was "i understand"
[22:30] <topyli> i hope this is not too wrong
[22:31] <rww> if +qing trolls in #ubuntu-offtopic is wrong, I don't want to be right
[22:31] <topyli> heh
[22:31] <Myrtti> word
[22:31] <topyli> i have to go to bed. could someone remove the quiet in good time? (no hurry)
[22:32] <topyli> meh, i can do it tomorrow myself
[22:32] <topyli> ah, he left
[22:34] <rww> and came back
[22:34] <rww> and I think that's an attempt at quiet evasion.
[22:35] <topyli> dunno, didn't change anything, just returned
 the people on ubuntu-offtopic are bad like all others.
[22:36] <topyli> not banned after all
[22:36] <bazhang> let me guess who got +q
[22:36] <topyli> i will leave this to you now and go to bed. i'm in sleep already anyway
[22:37] <topyli> night
[22:37] <bazhang> oCean, thanks!
[22:39] <rww> topyli: they changed IP addresses
[22:40] <rww> bazhang: if memory serves, mernilio was ban evading.
[22:40] <bazhang> rww, mernilio is always an issue, ban evading or not.
[22:42] <rww> and indeed they are, so they're gone.
[22:42] <bazhang> wfm
[22:43] <rww> oCean: https://lists.torproject.org/pipermail/tor-commits/2011-July/033754.html
[22:44] <rww> oCean: On Tor's side of things, that notice is staying there until "there is some kind of track record indicating [Ubuntu] have learned sanity". On Ubuntu's side of things, I'm going to go look at how we can start that track record ;)
[22:48] <rww> !away > lemons
[22:54] <rww> ah, looks like happyaron's way ahead of me. bug 413657. I'll give this a rest, then :)
[22:55] <rww> (and someone named ioerror that hasn't been on freenode in months :|)
[23:02] <rww> (oh, they're on OFTC. yay)
[23:48] <tonyyarusso> rww: ioerror used to always be in the WordPress channel.