[03:59] <BenC> infinity, Mithrandir: ping, lrm needs NEW love
[04:00] <infinity> BenC: Will do.
[04:00] <BenC> infinity: Thanks
[04:00] <infinity> But only because I want it, not because I'm working, you understand.
[04:00] <BenC> once that's done I can do linux-meta
[04:01] <infinity> Do -meta now, if LRM is built everywhere.
[04:01] <BenC> infinity: Sure, and I appreciate your off-the-clock assistance :)
[04:01] <infinity> Get it in the next 2 minutes, and you win!
[04:01] <BenC> LRM isn't even building yet
[04:01] <infinity> Oh.  Source NEW, right. :)
[04:02] <infinity> There, accepted under the wire, I think.
[04:02] <infinity> Should publish in abot 55 seconds.
[04:03] <BenC> thanks
[04:45] <infinity> BenC: http://librarian.launchpad.net/5426144/buildlog_ubuntu-feisty-amd64.linux-restricted-modules-2.6.20_<IP_ADDRESS>-1_FAILEDTOBUILD.txt.gz
[04:46] <infinity> BenC: Your vmware-tools stuff appears to be i386-only...
[04:46] <BenC> hmm
[04:46] <BenC> I was sure I did x86/x86_64 builds
[04:47] <infinity> Alternately, if that's a generated file, you could just have an unclean tarball...
[04:47] <infinity> I dunno.
[04:47] <infinity> You decide. :)
[04:48] <infinity> BenC: Looks like lrm was successful on the other 4 arches, though.
[05:20] <okaratas> good bye..
[05:51] <BenC> infinity: Ah, desched is object only...it is i386 only
[05:51] <BenC> I'll do another upload in the morning...heading to bed
[07:39] <infinity> BenC: The stuff you were "going to upload in the morning" worked fine, I'm pushing them through binary NEW now.
[10:21] <gnomefreak> is there no linux-image-2.6.20-2-generic yet?
[10:43] <infinity> gnomefreak: Given that I have it installed, I'd say it exists.
[10:46] <gnomefreak> infinity: why didnt it update but the .20-2-386 installed
[10:47] <gnomefreak> infinity: im on 19-generic so i figured -generic would have been updated
[10:47] <infinity> There's not been a linux-meta upload for 2.6.20 yet.
[10:47] <infinity> Will be soonish.
[10:48] <gnomefreak> ah ok that could explain it ty
[10:48] <gnomefreak> i will try the 386 for now. brb reboot
[10:48] <infinity> Just install -generic explicitely.. *shrug*
[10:51] <gnomefreak> infinity: sorry what was that last thing you said?
[11:19] <infinity> 20:48 < infinity> Just install -generic explicitely.. *shrug*
[11:20] <gnomefreak> ah i will look to see if l-r-m is ther for -generic first
[03:57] <BenC> infinity: ping
[06:54] <derekS> is there a problem with 2.6.20-2.2 and mice drivers?
[06:57] <crimsun_> specifically?
[06:57] <crimsun_> input seems to work fine for both ps/2 and usb
[06:57] <derekS> ps/2
[06:58] <derekS> there are no errors in xorg, it seems that there is no /dev/input/mouse0 (dunno if there should be)
[06:58] <crimsun_> mouse[01]  exist here.
[06:59] <derekS> 2.6.20-2?
[06:59] <crimsun_> /proc/version_signature => Ubuntu 2.6.20-2.2-generic
[06:59] <derekS> yeah, same here
[06:59] <derekS> maybe its because hal is going wild then?
[06:59] <crimsun_> hmm, that's interesting.
[07:00] <derekS> load average 5.6
[07:00] <derekS> (and i am not doing anything on it
[07:00] <derekS> )
[07:00] <crimsun_> BenC: should /proc/version_signature match $(uname -r)?
[07:00] <crimsun_> meaning the second field in /proc/version_signature
[07:00] <derekS> oh, my 2 don't match
[07:01] <derekS> weird i was using uname -r
[07:03] <derekS> also, generic no longer does smp?
[07:03] <crimsun_> err, it does
[07:03] <crimsun_> CONFIG_SMP=y ... CONFIG_X86_SMP=y
[07:04] <derekS> it also isn't finding my second processor
[07:04] <derekS> well, when i do uname -r, i have *-generic, but when i do /proc/version_signature i have *-386
[07:04] <derekS> does that mean i am actually running 386?
[07:06] <crimsun_> it -should- mean the -generic. What do dmesg and /boot/config-$(uname -r) corroborate?
[07:06] <derekS> dmsg says 386
[07:06] <derekS> lemme check /boot
[07:08] <derekS> ahh it gives me 386 for the config-$(uname -r)
[07:08] <derekS> lemme restart
[07:08] <derekS> and play around with some stuff
[07:09] <derekS> could it be the 386 driver has mouse probs?
[07:09] <crimsun_> I can't test/verify atm
[07:10] <derekS> ok
[07:10] <derekS> lemme play
[07:13] <derekS> ahh, i just reinstalled generic, and i get the same things now
[07:14] <derekS> however i figured out that i am etting an error msg about mice on bood
[07:14] <derekS> *boot
[07:14] <derekS> something about udev not finding it.... lemme look through the logs
[07:15] <derekS> hmm, can't find which log it was in
[08:33] <darwish> Hi all. On LDD3 Chapter 6, authors wrote an ioctl method for a global and persistent driver. This ioctl method modifies a *global* variable without locking. Won't this make problems on SMP systems if two processes execute the ioctl command at the same time ?.
[08:35] <kylem> ioctls are under the big kernel lock
[08:36] <darwish> kylem, aha .. this wasn't mentioned in the book .. Big thanks :)
[11:17] <derekS> in this screenshot, you can actually see the problem with my mouse (http://www.slovin.info/image6.jpg)...any suggestions?
[11:22] <darwish> derekS, better ask the support channel .. this is for developemtn discussion only :) ..
[11:22] <derekS> darwish: heh ok
[11:22] <darwish> development*
[12:02] <zul> gah..
[12:03] <zul> whoever changed the CHECKSUM_HW can die
[12:05] <infinity> BenC: Unlikely pong...


[02:28] <elky> i kind of recommend not doing !cloak in it though, or it'll have people asking in #f
[02:32] <IdleOne> agreed, could cause some confusion and they have enough to deal with without having to redirect to #ubuntu-irc
[09:30] <topyli> popped into a pm window
[09:31] <ikonia> ?
[09:32] <topyli> ikonia: alabd. ^
[09:32] <ikonia> oh
[09:33] <topyli> decided not to join the channel after all but fill my query window with the same stuff instead
[09:33] <ikonia> same old same old
[09:34] <topyli> i'm having a good day, so i explained everything again, twice
[09:34] <ikonia> prepare for another 2 times
[09:34] <elky> At least.
[09:35] <topyli> heh
[09:35] <topyli> maybe i'll repeat the same thing 30 times
[09:43] <elky> xchat is scriptable.
[09:43] <elky> if PM from alabd, then
[10:45] <ikonia> vortech ?
[10:54] <jpds> His humble thing freaks me out.
[10:54] <ikonia> a few people have comment on that, language is a tough one to crack if it's not your first langauge though
[11:01]  * gnomefreak gets a bad feeling about this
[11:02] <gnomefreak> junni seems to ask random users to join that channel (#ggz) its a gaming channel
[11:03] <jpds> gnomefreak: Then, tell him not to/
[11:04] <gnomefreak> jpds: waiting to make sure and i would like to see him do it to someone other than me in #ubuntu
[11:08] <gnomefreak> i think i handled it as nice as i could be
[11:08] <gnomefreak> now one more thing to work on than i can relax
[11:32] <elky> I'm pretty sure that's a repeat offender.
[11:32] <elky> (fwiw)
[12:12] <asac> hi .. .how can i get the ubot thing in new channels?
[12:14] <ikonia> asac: depends on the channel
[12:14] <ikonia> different bots (clones) run in different channels
[12:14] <ikonia> !bots
[12:15] <ikonia> I'm surer there is a wiki page that tells you how to request
[12:15] <jpds> asac: Which channel would you like to have it in?
[12:15] <ikonia> just the man
[12:16] <asac> jpds: i want ubottu (or a clone with same db and features in #linaro)
[12:16] <asac> or if you have a bot that just does "bugs" then that
[12:16] <jpds> asac: Done.
[12:16] <asac> thanks!!
[12:17]  * asac waves and leaves channel
[12:18] <bazhang> may want to keep an eye on flames; using bt4 and wanting support (he has been told the proper channel for that) have to go out for a few
[12:41] <bazhang> jungli had his ban lifted?
[12:42] <funkyHat> bazhang: no
[12:43] <bazhang> funkyHat, got him in PM, thanks
[13:01] <funkyHat> He's just arrived in -ot
[13:03] <bazhang> yep, after the chat via PM ( he says he is a nice guy, only ban-evaded to harass another user kaushal) and that he has changed now.
[13:05]  * gnomefreak gets the feeling Kaushal has had problems before in #ubuntu
[13:05] <gnomefreak> with another user
[13:06] <bazhang> jungli and indian_munnda (same person btw as blockcold)
[13:06] <gnomefreak> yeah jungli
[13:06] <bazhang> he's in -ot now as blockold
[13:07] <gnomefreak> wait you mean that kaushli is blockcold?
[13:07] <gnomefreak> yeah he said hi jto me and i cant figure out who it was until now
[13:07] <bazhang> nope, jungli is blockold/indian_munnda
[13:13] <elky> bazhang, lawl @ post-chat line.
[13:14] <bazhang> elky, :)
[15:41] <gnomefreak> hey ubot4 doesnt know mozilla bugs, they are kind of important for us in #ubuntu-mozillateam
[15:42] <Pici> pfft
[15:44] <jpds> gnomefreak: Action has been taken.
[15:44] <gnomefreak> jpds: thanks
[15:56] <h00k> morning all
[16:57] <bazhang> #ubuntu-hk has a bot and nothing else (locobot_3) not even a topic
[16:58] <h00k> what is hk?
[16:58] <bazhang> hong kong
[16:59] <topyli> now that's the kind of channel i want to be an op in
[16:59] <bazhang> wonder if still belongs in the !cn factoid
[17:00]  * jpds wonders if the HK mirror is still active.
[17:01] <h00k> topyli: its stressful I bet!
[17:01] <jpds> It's still UP! \o/
[17:07] <bazhang> that came out of nowhere
[17:47] <h00k> ubuntu tweak wouldn't be something that is supported, I'm going to guess, 'eh?
[17:48] <bazhang> !find tweak
[17:49] <h00k> !tweak
[17:49] <h00k> lag here :(
[17:49] <h00k> tweak is unknown
[17:50] <bazhang> !info tweak
[17:55] <h00k> er, a factoid for ubuntutweak, anyway. it's some script somebody wrote :(
[17:55] <h00k> like Automatix
[18:13] <tsimpson> every couple of years, someone thing "oh, I think I'll write a script to automate the install of restricted stuff"
[18:13] <tsimpson> and they always do it WRONG
[18:14] <tsimpson> mostly because there is no right way to automate such a thing, automation like that is not good
[18:19] <jussi> or they create a distro with it alll in, a la mint...
[18:20] <bazhang> ugh mint
[19:23] <bazhang> whoa quick seeker
[19:23] <Seeker`> slow bazhang is slow :P
[19:24] <Pici> 14:24:16 <?faggot3> I'm testing something.
[19:24] <Pici> (in pm)
[19:25] <Seeker`> hmm
[19:26] <bazhang> banning reaction time?
[19:27] <funkyHat> tsimpson: i really don't know what's wrong with just installing -restricted-extras ⢁( ... it's not very hard
[19:27] <funkyHat> I guess you still have to do the dvd css stuff manually, or do you?
[19:27] <Seeker`> I'm off out, have fun in faggot3 reappears
[19:27] <bazhang> klined
[19:28] <Seeker`> nice
[19:28] <tsimpson> funkyHat: you need to do it manually because it's technically illegal to automatically install it
[19:28] <h00k> surprise!
[19:28] <funkyHat> I thought it was just illegal to install it altogether? ;D
[19:29] <funkyHat> *in certain countries
[19:29] <tsimpson> yes, that too
[19:30] <tsimpson> but automatically installing it gives no chance to read the licenses/legal conditions
[19:30] <funkyHat> ah yeah
[20:24] <jussi> right, who wants to be a guinea pig?
[20:24] <jussi> (I need to test my forward alias)
[20:26] <jussi> nobody? meh... Ill ask our lovely oftopicers...
[20:26] <Pici> jussi: sure
[23:52] <IdleOne> @btlogin
[23:53] <IdleOne> @login
[23:53] <IdleOne> @btlogin


[00:06] <slickymaster> ok knome, I'm about again
[00:07] <knome> slickymaster, for starters, take a look at what i and pleia2 just discussed
[00:07] <slickymaster> doing it
[00:09] <slickymaster> yeah, the StartUbuntu flyers section should be dropped
[00:09] <Unit193> knome, pleia2: What were your thoughts on the aforementioned idea of translations on docs.x.o?
[00:09] <knome> Unit193, i'm happy with it
[00:09] <slickymaster> it's way long gone that XP transition
[00:10] <slickymaster> which idea is that Unit193 ?
[00:10] <slickymaster> having the translations also linked fron the site?
[00:10] <knome> slickymaster, yes
[00:10] <slickymaster> ok
[00:10] <slickymaster> +1 to it
[00:11] <slickymaster> I agree that the FAQs section ought to be updated but there hasn't been much written to update it
[00:12] <pleia2> Unit193: should be fine, but we should create a wiki page with "update the docs" instructions, right now it's simple so I just remember it every time I update the site, but if we're building translations each time too, it starts getting more complicated
[00:12] <Unit193> I have `./update` for my daily build. :P
[00:14] <slickymaster> knome, what type of widgets are you talking about?
[00:14] <pleia2> Unit193: great, sharing the contents of ./update should be much of the docs we need
[00:14] <knome> pleia2, we can probably drop a script in the branch
[00:14] <pleia2> knome: or that
[00:14] <slickymaster> I mean the ones you mentioned that could be added to the front page
[00:15] <knome> slickymaster, see the staging site for the visual look potential
[00:15] <pleia2> the server our docs live on doesn't always like to talk to the bzr server, so it's still all handled by hand
[00:15]  * slickymaster sees
[00:15] <Unit193> pleia2: I could, it's a little geared towards my setup, but it's pretty generic.
[00:15] <pleia2> I should look into that again, maybe open a ticket
[00:15] <knome> pleia2, could probably do a script that exports everything into a tar.gz you only have to unpack on the server
[00:16] <pleia2> knome: any of the above is fine :) I just don't want to add this to my workload without a plan
[00:16] <Unit193> knome: Mine uses rsync...
[00:16] <knome> i understand, which is why i'm proposing clear actionable items for Unit193 to take :P
[00:16] <Unit193> Whaaaat?  Nooo, this needs to be done by knome!
[00:18] <knome> pleia2, did you have a photo of the xubuntu t-shirt or want to come up with more text on the products page for that? :P
[00:18] <slickymaster> knome: "This is dynamically created content."
[00:18] <pleia2> knome: no photo
[00:18] <slickymaster> can you clarify that for me a bit more
[00:18] <knome> slickymaster, meaning it's not hardcoded to the website, we can control that without RT tickets to IS
[00:18] <knome> slickymaster, the column count too.
[00:18] <slickymaster> right
[00:19]  * knome drops web banners for now
[00:19] <knome> slickymaster, anything in the discussion you saw you'd like to work on now?
[00:20] <slickymaster> take a pick knome, I'll be about for a hour more
[00:20] <slickymaster> so
[00:20] <knome> well i'm working on this and that already
[00:21] <knome> *you* take a pick that scratches your itch :P
[00:21] <slickymaster> the docs item
[00:22] <knome> on it right now
[00:22] <slickymaster> on text review?
[00:22] <knome> done
[00:22] <knome> refresh the page
[00:23] <Unit193> pleia2: Want to look at it perhaps?
[00:23] <slickymaster> needs a hard refresh
[00:24] <knome> slickymaster, as anything with canonical cache
[00:24] <pleia2> Unit193: not today, probably not this week, I'm really buried at $day_job
[00:24] <knome> ok, updated a bit more
[00:28] <slickymaster> I'm ok with that
[00:28] <knome> slickymaster, well if you aren't, feel free to edit it
[00:28] <slickymaster> no, I am
[00:29] <slickymaster> but were'nt you and pleia2 also talking about bumping up the position of the docs links on that page?
[00:29] <knome> i did that.
[00:29] <slickymaster> weren't even
[00:30] <slickymaster> I see it now, it's visible in the page load, without the need of scrolling the page down
[00:31] <slickymaster> knome: the StartUbuntu section is going to be replaced by anything?
[00:31] <knome> slickymaster, not at the moment, until we have the xubuntu flyers ready
[00:31] <knome> well, there's the note about the development of those
[00:32] <knome> GridCube, ping
[00:32] <GridCube> YES
[00:32] <GridCube> caplocks
[00:32] <knome> haha :)
[00:32] <GridCube> yes?
[00:33] <knome> re: https://wiki.ubuntu.com/Xubuntu/Marketing/Projects/DesktopOfTheWeek
[00:33] <knome> did we know the wallpaper licenses for the first two?
[00:34] <knome> #3 link is not working
[00:36] <GridCube> yes, probably taken down, i have no clue about first two
[00:36] <knome> so we should start with your wallpaper
[00:36] <knome> or Unit?
[00:38] <Unit193> Nope.
[00:38] <knome> gridders then
[00:38] <GridCube> :) its fine
[00:38] <GridCube> i dont mind either way
[00:39] <Unit193> You can use that, I can re-shoot, or something I don't actually care, just got to scrollback and saw my non-ping name. :P
[00:39] <GridCube> P: we can get a prettier one from Unit193
[00:43] <knome> http://xubuntu.org/screenshots/dotw/
[00:44] <knome> pleia2, if around, see ^that and comment
[00:45] <slickymaster> GridCube, is that library you work at?
[00:46] <GridCube> lol, no, not even
[00:46] <GridCube> my library is like a shoebox with books in it
[00:46] <slickymaster> knome: "This desktop is Bruno", shouldn't it be "This desktop is Bruno's"?
[00:47] <GridCube> or is from P:
[00:47] <slickymaster> or that
[00:47] <knome> slickymaster, nooo :P
[00:47] <bluesabre> Unit193: going to add xfce components to https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1424887
[00:47] <slickymaster> ahah
[00:47] <knome> do you know how small the caption textarea in wp is? :(
[00:47]  * slickymaster caught the grammar police
[00:47] <bluesabre> and then I'll poke -release folks about it tomorrow
[00:47] <knome> i can see like 9 words at a time
[00:47]  * slickymaster hides
[00:48] <GridCube> wow thats froma august 2013
[00:48] <GridCube> how fast time goes on
[00:49] <Unit193> bluesabre: Ah, nice.  Have fun then, I'll try to keep an eye on it too.
[00:53] <knome> looks like color scheme day tomorrow
[00:54] <bluesabre> ochosi: see the above link as you (you're now subscribed)
[00:57] <bluesabre> knome: think I need to add any more words to https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1424887 ?
[00:59] <knome> "each component since 14.04" ?
[01:00] <knome> or even
[01:00] <knome> "each component since 14.04 LTS"
[01:00] <knome> i think that might tickle the approve-nerve
[01:01] <bluesabre> heh
[01:01] <knome> well that says "we've used this devel stuff for LTS, now we'd like the final stuff in"
[01:01] <knome> maybe say something about affected flavors
[01:01] <knome> studio
[01:01] <knome> and how they are fine with this
[01:02]  * bluesabre hasn't spoken with myth and studio
[01:02] <knome> Unit193, didn't you?
[01:02] <knome> or who was it
[01:02] <bluesabre> probably xubuntuw38
[01:02] <knome> i remotely remember seeing some comment on their development channel that they are fine with it
[01:03] <Unit193> Likely Studio.
[01:03] <knome> but... don't put that in the bug because i said it.
[01:03] <knome> studio tries to go DE-agnostic anyway
[01:04] <Unit193> And I don't think zequence would object though, but lets ping him.
[01:04] <knome> yes
[01:04] <knome> myth people too
[01:05] <Unit193> They only do LTS releases.
[01:05] <knome> oh.
[01:05] <knome> then let's not
[01:05] <knome> they are probably just happy that we got a non-dev release in before the next LTS :P
[01:17] <slickymaster> damn, coorecting the translated tags in the po files is making me sleepy
[01:17] <bluesabre> :)
[01:17] <knome> slickymaster, hah.
[01:17] <knome> slickymaster, no whining!
[01:18] <slickymaster> not whining, yawning :P
[01:20]  * slickymaster would love to catch one in the fi.po file
[01:20] <knome> unlikely ;)
[01:20] <slickymaster> lol
[01:20] <slickymaster> there's none, already check that one
[01:20] <knome> yep
[01:57] <bluesabre> this bug confuses me https://bugzilla.xfce.org/show_bug.cgi?id=11583
[01:57] <bluesabre> ~"this pdf won't open in thunar or nautilus, nautilus opens up at the location of the file"
[01:58] <bluesabre> maybe I misunderstand, but I wouldn't read a document with my filing cabinet
[02:00] <bluesabre> oh wait... well that is odd
[02:00] <brainvvash> why even pass "--launch FileManager" ?
[02:00] <bluesabre> maybe thunar intelligently opens the file in the correct app
[02:00]  * bluesabre shrugs
[02:00] <bluesabre> I'll comment on that one later
[02:00] <brainvvash> comment what?
[02:01] <bluesabre> dunno yet
[02:01] <bluesabre> :D
[02:01] <bluesabre> whats up brainvvash ?
[02:02] <brainvvash> exo-open --launch FileManager  is meant to launch the default file manager, no additional arguments
[02:02] <brainvvash> not much.. just waiting for Xfce 4.12 to be released :D
[02:04] <Unit193> --launch TYPE [PARAMETERs...]       Launch the preferred application of TYPE with the optional PARAMETERs, where TYPE is one of the following values.
[02:25]  * bluesabre packages new light-locker patch
[02:25] <Unit193> bluesabre: Pssst, I already did that, pinged you, linked you, and pushed to staging. :P
[02:25] <Unit193> Or is this a newer-new? :P
[02:26] <bluesabre> newer-new
[02:26] <bluesabre> 6 hours ago?
[02:26] <Unit193> Nope, same.
[02:26] <bluesabre> D:
[02:26] <Unit193> But, uhh.  If you're already nearly done...
[02:27] <bluesabre> oh, I see
[02:27] <bluesabre> light-locker (1.6.0-0ubuntu1~ppa15.04.2) vivid; urgency=medium
[02:27] <bluesabre> confused me since there was not a 15.04.1 there
[02:27] <Unit193> That's not mine.
[02:28] <Unit193> :D
[02:29] <Unit193> ...Did I push it to staging?  I meant to, and did in my head...
[02:29] <bluesabre> now I'm confused
[02:29] <bluesabre> 2015-02-16
[02:29] <bluesabre> last vivid build
[02:29] <Unit193> https://sigma.unit193.net/source/light-locker_1.6.0-0ubuntu2.dsc
[02:30] <bluesabre> oh goodie
[02:31] <Unit193> That's partially why I asked about LL, since we're shipping each commit basically. :P
[02:32] <bluesabre> heh
[02:32] <knome> i wonder how many apps would work if you only shipped either the odd or even numbered commits.
[02:32] <bluesabre> I saw cavalier's ping before your ping
[02:32] <Unit193> Oooh.
[02:32] <Unit193> brainvvash pinged me.
[02:33]  * bluesabre can now easily retrieve pings, nice weechat script for that
[02:35] <Unit193> That'll be handy.
[02:35]  * knome notes to ping bluesabre more often
[02:35]  * bluesabre gets excited
[02:35] <knome> you get excited of work? :P
[02:36] <bluesabre> I get excited at the prospect of possibly not losing work
[02:36] <knome> wow, that's a long shot
[02:36] <knome> but okay.
[02:40] <bluesabre> :D
[02:42] <knome> and also, i'm off to bed
[02:42] <knome> nighty and ttyl
[02:42] <bluesabre> nighty knome
[02:42] <bluesabre> lock-on-lid seems to work, so thats exciting
[02:45] <Unit193> Yey!
[02:45]  * bluesabre can't upload light-locker either
[02:46] <Unit193> Hah. :D
[02:46] <bluesabre> I think our packageset is temporarily broken :P
[02:46] <Unit193> That's alright, I can't upload anything. :D
[02:46] <bluesabre> Unit193: want to upload that to -staging so we can get more testing?
[02:46] <Unit193> There was a packageset change earlier, I believe.
[02:46] <Unit193> Sure.
[02:46] <bluesabre> Thanks
[02:47] <bluesabre> Unit193: where was the packageset change... not sure I'm subscribed to that notification
[02:47] <Unit193> [15:43:15] queuebot:#ubuntu-release: Packageset: 52 entries have been added or removed
[02:48]  * bluesabre thinks the release team wants me him to focus on the xfce release
[02:48] <bluesabre> dang, didn't erase one of those words
[02:48] <bluesabre> ah, indeed
[05:11] <Unit193> bluesabre: Why is 60-xubuntu.conf in debian/ rather than usr/share/lightdm/lightdm.conf.d/ ?
[07:18] <elfy> can someone with the knowledges do social thing for beta 1 tests please - ty :)
[11:27] <bluesabre> Unit193: beats me
[11:48] <bluesabre> We've got the go-ahead for xfce-4.12 https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1424887
[11:49] <brainvvash> does the task manager crash the notification area?
[11:49] <bluesabre> (not that I expected otherwise)
[11:50] <bluesabre> brainvvash: works for me
[11:50] <bluesabre> (doesn't crash the notification area)
[11:50] <brainvvash> ok
[12:01] <knome> elfy, tweeted
[12:04] <Akusari> sounds great :-) So i guess for trusty i can use xfce-412 ppa to get the same like planed for vivid?
[12:19] <bluesabre> Akusari: yeah, once the release lands we'll update the xfce-412 ppa with the latest and greatest
[12:22] <knome> though it's not exactly the same as the polished experience in vivid
[12:22] <knome> and using the PPA is at your own risk, on vivid you get the support
[12:37] <Akusari> yes, yes, i know....
[12:38] <knome> just want to avoid misconceptions since many more people read this channel
[12:39] <Akusari> yeah and i think a lot of people will ask for backports XD
[12:41] <knome> you can always ask...
[12:42] <Akusari> hehe - right :-)
[12:44] <Akusari> if i would be the head, i wouldn't offer any kind of backports fot trusty or older xubuntu versions. :)
[12:44] <Akusari> sounds hard but it's the best i think
[12:46] <Akusari> i would offer that you can use our xfce-4.12 ppa, but its your own risk of course (So, at least, we agree :-))
[12:47] <knome> well, 14.04 is supported until 2017, so it's a balance between backporting 4.12 and supporting a development version for two more years
[12:47] <knome> so a backport isn't completely out of question
[12:47] <knome> but probably still unlikely, since it's a lot of work
[12:48] <Akusari> yes, you need to analyze how many ressources (men-power) might be used for a backport and much mnore importend "support" of those packages
[12:49] <knome> it's mostly different people taking the burden though
[12:49] <Akusari> we,, i know such problems, because i'm a developer in a software house ;-)
[12:49] <Akusari> well
[13:06] <elfy> knome: thanks :)
[13:09] <knome> eh. the "bridge linux xfce edition" menu icon looks suspiciously close to the old xubuntu logo
[13:09] <knome> http://i1-news.softpedia-static.com/images/news2/Bridge-Linux-Xfce-2015-02-Released-a-Fast-and-User-Friendly-Arch-Linux-Distro-473288-3.jpg
[13:10] <knome> or is the "arch xfce" icon
[13:10] <knome> http://i1-news.softpedia-static.com/images/news2/Bridge-Linux-Xfce-2015-02-Released-a-Fast-and-User-Friendly-Arch-Linux-Distro-473288-11.jpg
[13:44] <jjfrv8> elfy, I can't do any hardware test with the 32-bit beta. Fails to create a bootable flash drive with UNetbootin.
[13:49] <knome> !team | next community meeting announced; tomorrow (feb 25) at 17utc
[13:50] <knome> and sorry for the short notice...
[14:18] <knome> pleia2, ygm
[14:24] <knome> bbl
[16:09] <elfy> jjfrv8: ack - I gave up using unetbootin ftr
[16:12]  * pleia2 social medias about b1 testing
[16:14] <elfy> pleia2: awesome sauce - thanks :)
[16:41]  * dkessel needs a search engine for this channel's irc logs
[16:41] <elfy> oh ... hang on dkessel
[16:41] <dkessel> i just encountered that bug where while watching a video, the mouse cursor won't come back when moving a mouse. i believe someone reported it for parole the other day
[16:43] <elfy> check what rww was saying in #ubuntu+1 yesterday http://irclogs.ubuntu.com/2015/02/23/%23ubuntu+1.html
[16:43] <elfy> at the end of those really long logs - that might help you
[16:44] <dkessel> oh, nice! thanks elfy :)
[16:44] <elfy> not tried it myself though
[16:45] <dkessel> let's see
[16:46] <dkessel> nah. i guess i'll check the past few days' logs manually
[16:47] <knome> dkessel, it was me, changing the video sink fixed the issue
[16:47] <dkessel> knome: just found out about that. i see the same thing happening in chrome while watching html5 video...
[16:48] <slickymasterWork> elfy bug 1425047
[16:48] <slickymasterWork> hey knome, dkessel
[16:48] <knome> hello slickymasterWork
[16:48] <dkessel> hey slickymasterWork
[16:48] <elfy> slickymasterWork: yes - now you are back - have you tried again?
[16:48] <elfy> I've just run that test - passed here
[16:49] <dkessel> i get this while watching video in fullscreen. after going back to windowed mode, controls and mouse cursor return
[16:49] <slickymasterWork> well since it's the same image, I'd expect to achieve the same result elfy
[16:50] <elfy> I'm beginning to think that any bugs from vbox shouldn't cause a fail unless replicated on something else
[16:50] <elfy> slickymasterWork: well yea - but theoretically I've got the same image here :)
[16:50] <slickymasterWork> I'm assuming you're referring to the b1 image elfy
[16:50] <elfy> yes
[16:50] <slickymasterWork> that's odd
[16:50] <elfy> not really - vbox
[16:51] <elfy> possibly different vbox version 4.3.22-dfsg-1 here
[16:51] <slickymasterWork> but what is even odder is the fact that it installs if not partitioning, i.e, entire disk
[16:52] <slickymasterWork> the axact same here elfy
[16:52] <slickymasterWork> exact also
[16:52] <elfy> right
[16:52] <Akusari> hello people :-)
[16:53] <elfy> well I did exactly the same test, manual partition and it passes
[16:53] <elfy> as I said I'm getting to think that vbox fails shouldn't be
[16:55] <elfy> slickymasterWork: and you run that from try or install?
[16:56] <knome> pleia2, sent the mail, thanks
[16:57] <slickymasterWork> from what I could gather and figured out the system just couldn't mount /dev/sda2 and that's why whining about not finding a HFS filesystem on dev sda2
[16:57] <pleia2> knome: thanks :)
[16:57] <knome> pleia2, and sorry for not CC'ing, i'm sure you wouldn't have understood most of the message anyway ;)
[16:58] <pleia2> bork bork
[17:01] <slickymasterWork> elfy partitioning was run from install
[17:02] <elfy> ok - so not livesession? just want to see if I can replicate this in vbox
[17:02] <slickymasterWork> entire disk was run from within live session
[17:03] <slickymasterWork> going to try to run partitioning also from within live session to see if it acts the same wasy
[17:03] <slickymasterWork> * way
[17:24] <elfy> slickymasterWork: ok - seeing it
[17:25] <slickymasterWork> did you run it from install?
[17:25] <slickymasterWork> I'm running it now from within live session to see if it acts the same way elfy
[17:26] <elfy> I bet you'll see a pass
[17:27] <slickymasterWork> pass?! elfy
[17:27] <elfy> running both arch's again
[17:27] <elfy> then I'll check kvm
[17:27] <elfy> then I'll check hardware
[17:28] <slickymasterWork> no procrastination for elfy ;)
[17:28] <elfy> :)
[17:28] <knome> elfy's shoothing for the free stickers
[17:28] <elfy> well ...
[17:28] <elfy> I didn't say then I'll check kvm straight after that
[17:29] <elfy> knome: well ... if I actually always put my results on the tracker - I'd be miles ahead :p
[17:29]  * slickymasterWork is shooting for the t-shirts :P
[17:29] <knome> elfy, j/k :P
[17:29] <elfy> knome: :)
[17:30] <elfy> slickymasterWork: when it crashed - did you get any notification?
[17:31] <slickymasterWork> nopes, nothing at all
[17:31] <elfy> just end up at a dead wallpaper?
[17:31] <slickymasterWork> the slideshow simply disappears
[17:31] <slickymasterWork> yeaps
[17:31] <elfy> k
[17:32] <slickymasterWork> I had to drop to TTY1 and go through the logs to find out what happened
[17:33] <elfy> ok - assuming that this is in fact a bug
[17:33] <slickymasterWork> the way I see it it is, even more if you're able to reproduce it in hardware
[17:34] <elfy> few things we need to make sure of - 1st it's not just vbox, 2nd - would we expect people to Install or to wander about the livesession and do their installing, 3rd we accept the issues if it is just either only vbox or works everywhere from live
[17:35] <elfy> I'll boot vbox to get ubiquity debug logs as well
[17:35] <slickymasterWork> I'm finish the install from within the live session and at least that will provide us some more info
[17:35] <slickymasterWork> s/finish/finishing
[17:35] <elfy> I've got a pass from within livesession - didn't actually twig the test was for install ... oops
[17:36] <slickymasterWork> it works from within the live session elfy
[17:36] <elfy> 32bit crashed again :D
[17:36] <slickymasterWork> ^^
[17:36] <elfy> slickymasterWork: yea - though it would
[17:37] <elfy> hopefully this is just 32bit
[17:37] <elfy> then I can say - get 64bit :D
[17:37] <slickymasterWork> thing is, most people will install directly from the 'Install' option, so I'm leaning to consider it as a bug in ubiquity
[17:37] <elfy> okey doke - both crashes
[17:38] <slickymasterWork> elfy, no escape, hit the 'This bug affects you' link :P
[17:38] <elfy> I already have :)
[17:38] <slickymasterWork> lol
[17:39] <slickymasterWork> elfy amd64 tag added to the bug report
[17:40] <slickymasterWork> elfy, you sure you hit the correct bug? bug 1425047
[17:41] <elfy> I'm positive
[17:42] <slickymasterWork> it's odd, it's still with the 'New' status and it ought to be 'Confirmed' then
[17:43] <elfy> yea it is now
[17:43] <slickymasterWork> right, it is now
[17:47] <slickymasterWork> btw elfy, b1 images are also hitting bug 1424561
[17:47] <elfy> yes
[17:49] <elfy> slickymasterWork: ok - so talking to people about the install crash now, grabbing some other logs for the bug
[17:50] <slickymasterWork> I don't have that box anymore elfy :P
[17:51] <elfy> ?
[17:51] <slickymasterWork> aren't you asking me for some other logs?
[17:51] <elfy> no - I'm doing it :)
[17:53] <slickymasterWork> :)
[18:10] <slickymasterWork> bbl ->
[18:10] <elfy> sigh - all a bit poorly this is :D
[18:51] <elfy> mmm
[18:52] <elfy> ochosi: so currently - using manual partitioning - installs appear to crash - but are actually complete if you reboot
[18:52] <elfy> all work properly from live session
[18:53] <elfy> that's vbox and unfortunatel also hardware
[19:10] <Akusari> Vivid iso beta testing: Is this really the current used default wallpaper or  a graphic error ? http://www.zimagez.com/zimage/screenshot-24022015-200653.php
[19:11] <Unit193> Akusari: That's the development wallpaper. :D
[19:11] <Akusari> it looks soooo, well,...not my taste :-P
[19:14] <knome> fortunately you can change the wallpaper in a modern desktop environment like xfce
[19:18] <brainvvash> that screenshot reminds me that I wanted to ask if we could add a label to the whiskermenu icon. something like " Menu " (spaces for additional padding)
[19:20] <brainvvash> the app menu is an important component and the visual representation in the panel is somewhat subtle currently
[19:21] <brainvvash> adding the label makes it also easier to click
[19:22] <elfy> adding a label makes something easier to click - I'd love to see that
[19:23] <brainvvash> easier to target?
[19:23] <elfy> well for you you could just set it to icon and text - that should be a big enough target
[19:24] <brainvvash> I can do that, but I feel like it should be the default
[19:25] <elfy> and I feel it shouldn't
[19:25] <elfy> there we go - 2 different people - 2 opinions :)
[19:25] <brainvvash> that's ok
[19:25] <elfy> meanwhile - in real problems - the installer fails without the live session :)
[19:26] <brainvvash> it's the first thing I notice when looking at the default xubuntu desktop
[19:27] <brainvvash> so, maybe it could be discussed
[19:28] <knome> i wonder why these discussions always so up at the last minute
[19:28] <knome> any ideas why that might be so?
[19:28] <elfy> nope
[19:29] <elfy> but no reason why not to start it in early May I guess
[19:29] <knome> me neither
[19:29] <Frostsongr> I like just the icon too
[19:29] <knome> must be bad luck :P
[19:29] <brainvvash> late? still plenty of time until 16.04
[19:33] <brainvvash> not enough supporters, so I'll drop this topic :)
[19:33] <knome> in a random 15-minute period on a single IRC channel?
[19:36] <Unit193> We "could" add an icon, and think Xfce does by default, but it end up just taking up space and you'll see other distributions/OSes/etc also don't do this.
[19:36] <elfy> label
[19:36] <elfy> there's already an icon :)
[19:36] <brainvvash> elfy said NO, so I'm not motivated enough to discuss this :D
[19:37] <knome> if we decide not to add the label, we can voluntell brainvvash to write a FAQ article on enabling the label
[19:38] <brainvvash> "how to open the properties window?"
[19:38] <elfy> mmm
[19:48] <knome> brainvvash, that's exactly the wording we are after
[20:06] <elfy> anyone in here know if "cyphermox> elfy: do you know if _NET_NUMBER_OF_DESKTOPS gets used for something special in xfce?"
[20:06] <elfy> maybe Unit193 or bluesabre :)
[20:06]  * Unit193 ducks.
[20:06] <cyphermox> heheh ;)
[20:06] <cyphermox> I'm trying to find some reason for windows to show up outside the screen
[20:06] <Unit193> Can't remember if it is xfsettingsd, xfwm4, or xfdesktop that uses it.  WHy do you ask?
[20:06] <cyphermox> so far, not much to go on
[20:07] <cyphermox> either _NET_NUMBER_OF_DESKTOPS, and/or _NET_DESKTOP_NAMES
[20:07] <elfy> that said - probably just about anyone but me :)
[20:08] <elfy> cyphermox: lol - forgot you were in here :)
[20:08] <Unit193> http://paste.openstack.org/show/4YdQrp9eHW3Z7qi31HGU
[20:08] <elfy> cyphermox: tbh - any question like that - better to try in here than me I'm afraid
[20:08] <cyphermox> elfy: ok
[20:28]  * ranu is wondering why Thunderbird is too slow to load the inbox and the selected messages :(
[20:28] <ranu> but that's off topic, so >.>
[20:33] <Akusari> vivid beta1 iso testing: manual partition has some trouble... i'm collecting data...
[20:39] <elfy> Akusari: yes - we know - bug 1425047
[20:39] <Akusari> more or les the same i'm adding data
[20:40] <elfy> as long as it's to that bug :)
[20:40] <elfy> you'll find that on reboot it's worked I suspect
[20:40] <elfy> with entire disc you'll find it's not there to work with - but you can find it and move it onto desktop
[20:41] <elfy> you'll find also it's hardware as well as vm's :)
[20:45] <Unit193> Well that's a simple answer, don't use ubiquity to install!
[20:45]  * Unit193 ducks.
[20:45] <Akusari> ok. data added to your bug :-)
[20:46] <elfy> Unit193: actually - don't not use the live-session :p
[20:46] <Akusari> let me check a "forced" reboot
[20:46] <knome> actually, just don't do installs, always upgrade:P
[20:46] <Unit193> elfy: Oh so this is more 'install only' issues?  Well that's simple.
[20:46]  * elfy has almost rewritten xubuntu image tests to only use livesession :D
[20:47] <elfy> Unit193: yea - currently 4/5ths of tests will be a mash of fails and passes and confusion :)
[20:48] <Akusari> well, i noticed a download tio
[20:48] <Akusari> timeout
[20:49] <Akusari> during the installtion. that's why i shipped the installer archiv :-)
[20:55] <sidi> guiding my little brother in his first xub install
[20:55] <sidi> he needs to build his wifi driver manually
[20:55] <sidi> over google hangout, very fun :-)
[20:55] <elfy> :)
[20:56] <Akusari> The timout happend here: (was killed later on and run again) http://www.zimagez.com/zimage/screenshot-24022015-212516.php
[21:02] <Unit193> elfy: Not sure if you test ll from staging, but re-upped (well, give it a minute to build.)
[21:04] <elfy> Unit193: I don't *test* but I do use it and staging
[21:06] <Unit193> Ah, well this is more suspend stuff.
[21:07] <elfy> ok - well I can use that too if it needs some testing
[21:07] <elfy> not something I use often - but can do :)
[21:07] <Unit193> bluesabre: Re: new ll (as of a few minutes ago.)
[21:24] <elfy> Unit193: what was this update to ll for re suspend ?
[21:25] <Unit193> Better integration with systemd/upower and such.
[21:25] <Unit193> Think might be laptop related.
[21:25] <elfy> aah - not going to see that then ;)
[21:44] <slickymaster> elfy, in ny installs it didn't worked on reboot
[21:45] <slickymaster> in fact it always went to the installer slideshow again
[21:45] <slickymaster> s/ny/my
[21:45] <elfy> and if you unmounted the image?
[21:46] <slickymaster> didn't try that :P
[21:46] <elfy> :)
[21:47] <elfy> it IS obviously all a bit on the fubar side for sure
[21:48] <elfy> but if nothing changes between now and Thursday - we've choice of not releasing or releasing and making it a Big Red Known Notice :p
[21:48] <slickymaster> yeaps
[21:48] <elfy> I'm assuming that those who can are looking at what's up with that
[21:49] <slickymaster> you and I
[21:50] <elfy> I could look at the code if you thought I'd not just go an put the kettle on :D
[21:50] <slickymaster> lol
[21:54] <Unit193> elfy: I take it using the "old" menu doesn't help?
[21:54] <elfy> the boot one?
[21:55] <Unit193> syslinux, right.
[21:55] <elfy> ie the one behind the language?
[21:55] <Unit193> Yep.
[21:55] <elfy> if so - no - same issue if you choose Install
[21:57] <slickymaster> yeah, eventualy we'll end up in the same place
[21:58] <elfy> trying to remember which different options I've tried today
[22:02] <slickymaster> irc you went through tem all elfy
[22:02] <slickymaster> * them
[22:03] <Akusari> good night :-)
[22:03] <Akusari> my holly bed is waiting ^^
[22:15] <elfy> slickymaster: I thought so ... just lost count :p
[22:42] <elfy> night all
[22:42] <elfy> I'll look for pings for this issue in the morning
[22:45] <knome> nighty elfy


[09:18] <tintou_> I've filled an issue in Launchpad itself a few weeks ago, but would it be possible to reassign all the signon-* and libaccounts* projects from https://launchpad.net/online-accounts to https://launchpad.net/~accounts-sso-devs which contains the team from https://gitlab.com/accounts-sso
[10:07] <cjwatson> tintou_: Could you point me to the issue you filed?
[10:20] <tintou_> cjwatson: arf, sorry for the noise, I've probably used the "contact this team admins" here instead https://launchpad.net/~pspmteam
[10:22] <cjwatson> That is ... probably not very useful
[10:23] <rbasak> Launchpad is building git-ubuntu snaps broken currently (we embed tests and they fail). I haven't been able to reproduce locally - my snap builds from the same source tree seem to reliably work.
[10:23] <cjwatson> tintou_: Could you file a ticket on https://answers.launchpad.net/launchpad/+addquestion ?  We may need to consult a bit.
[10:23] <rbasak> Do you have any details on how I could reproduce Launchpad's builds exactly please?
[10:23] <rbasak> Separately I'm trying to follow up by investigating exactly how the Launchpad built snap is broken.
[10:24] <cjwatson> rbasak: I guess it would be necessary to set up launchpad-buildd in a VM.  It's a bit of a long tail to get to "exactly".
[10:25] <rbasak> I'm using "snapcraft cleanbuild" locally
[10:25] <wgrant> rbasak: Have you tried building it in a buildd chroot?
[10:25] <wgrant> cleanbuild does not currently use a properly clean chroot AFAIK
[10:25] <rbasak> wgrant: no. That sounds like a good idea.
[10:26] <wgrant> It probably uses something big based on a cloud-image.
[10:26] <rbasak> I'm seeing this, which I suppose is expected:
[10:26] <rbasak> -prefix=/root/build_git-ubuntu/stage/usr
[10:26] <rbasak> +prefix=/build/git-ubuntu/stage/usr
[10:26] <rbasak> But also this, which I'm more surprised to see
[10:26] <rbasak> -CPPFLAGS=      -I. -IInclude -I$(srcdir)/Include  -I/root/build_git-ubuntu/stage/usr/include -I/root/build_git-ubuntu/stage/usr/include/x86_64-linux-gnu
[10:26] <rbasak> +CPPFLAGS=      -I. -IInclude -I$(srcdir)/Include  -I/build/git-ubuntu/stage/usr/include
[10:27] <rbasak> LDFLAGS not affected though
[10:28] <tintou_> cjwatson: question opened https://answers.launchpad.net/launchpad/+question/670044 thanks :)
[10:28] <wgrant> rbasak: I'd suggest building in a chroot that contains a sane set of packages (eg. chroot_url from https://api.launchpad.net/devel/ubuntu/xenial/amd64)
[10:28] <wgrant> It will probably tell you which dep you're missing
[10:29] <rbasak> wgrant: so put that in schroot or a container or similiar, apt install snapcraft and run that inside it?
[10:30] <cjwatson> LP converts it to a container, but that's probably only necessary if you build-depend on snaps.
[10:31] <wgrant> Indeed.
[10:31] <rbasak> OK I'll try that thanks
[10:31] <rbasak> (using schroot)
[10:31] <wgrant> tintou_: Can you explain the justification and history in the ticket?
[10:32] <wgrant> It's very exceptional for us to reassign ownership of projects like this.
[10:32] <wgrant> We'll need to do some research.
[10:39] <rbasak> Is it the buildd user I should run snapcraft against?
[10:39] <tintou_> I just added more information, but yeah I understand that it might require to ask people for the feasibility :)
[10:56] <rbasak> Hmm. snapcraft seems to want sudo.
[10:56] <cjwatson> rbasak: We currently run snapcraft as root.
[10:57] <cjwatson> https://bugs.launchpad.net/launchpad-buildd/+bug/1702656
[10:57] <rbasak> Ah OK. Easier for me to replicate then, thanks :)
[10:58] <rbasak> Running snapcraft now. I did it in a plain chroot as I realised I'm doing this all in a test VM anyway
[11:00] <cjwatson> Yeah, that's basically what Launchpad did until we switched to a container.
[13:22] <rizzitello> Hi all im working on a project and we are in current discussion to add submodules to our project. How is this going to affect ubuntu builds? last I tried launchpad didn't work right with git repos with submodules . Is there a workaround or has this been fixed ?
[13:25] <cjwatson> rizzitello: What sort of builds?  Source package recipes, snaps, ...?
[13:25] <rizzitello> packages
[13:26] <cjwatson> Sounds like https://bugs.launchpad.net/git-build-recipe/+bug/1733603, which we haven't got round to fixing yet
[13:26] <cjwatson> git-build-recipe is open source, like the rest of Launchpad; I'd be happy to review a tested patch to it
[13:27] <rizzitello> source repo?
[13:27] <rizzitello> and how best for me to test my patch?
[13:27] <cjwatson> https://git.launchpad.net/git-build-recipe
[13:28] <cjwatson> "python3 setup.py test" should work
[13:29] <rizzitello> any pointers on where to squash this bug?
[13:30] <cjwatson> That's most of the work; if I had an immediate answer to that I'd already have fixed the bug :)
[13:30] <rizzitello> lol ok just trying to save anytime on the search :P
[13:31] <cjwatson> But it's quite a small project, only a couple of thousand lines of code outside tests
[13:32] <cjwatson> Maybe pull_or_clone, or somewhere near there
[13:32] <rizzitello> ok thanks cjwatson ill see what i can do ..
[13:32] <cjwatson> Cheers
[13:52] <rbasak> I've not been successful at reproducing the problem.
[13:52] <rbasak> Now that I've got things close, I'll see if a diff against the Launchpad build log gives me anything.
[14:03] <rbasak> Could there be some different in network environment perhaps? Eg. pip falling back to something if it can't fetch from pypi?
[14:05] <rbasak> That kind of thing anyway - LP's build log shows pip working normally AFAICT
[15:01] <cjwatson> rbasak: There is certainly such a difference - LP builders run with very constrained network access and have an authenticated outbound proxy
[15:02] <cjwatson> rbasak: This is regrettably quite hard to reproduce exactly locally
[15:13] <rbasak> Thanks. I'm trying to pin it down from the other direction.
[15:13] <rbasak> ImportError: /snap/git-ubuntu/x8/lib/python3.6/site-packages/../../../usr/lib/x86_64-linux-gnu/../libgcrypt.so.20: symbol gpgrt_get_syscall_clamp, version GPG_ERROR_1.0 not defined in file libgpg-error.so.0 with link time reference
[15:13] <rbasak> That's the actual specific problem.
[15:13] <rbasak> I'm building both libgcrypt.so.20 and libgpg-error.so.0 as part of the snap build, from upstream source
[15:13] <rbasak> I don't see that it has appeared in my local chroot via snapcraft installing deps before it begins
[15:14] <rbasak> Any chance it could arrive in the chroot on Launchpad in some other way?
[15:14] <rbasak> Another difference is that on Launchpad snapcraft is using make -j4
[15:15]  * rbasak looks up objdump syntax
[15:28] <cjwatson> rbasak: launchpad-buildd also installs   snapd fuse squashfuse udev (you may have difficulty installing these ones in a chroot, but check their deps) python3 socat snapcraft, and either bzr or git depending on what sort of source for the snap you gave it
[15:29] <cjwatson> reasonably believable that something there could pull in gpg-error
[15:32] <rbasak> Hmm.
[15:32] <rbasak> On the Launchpad build, that symbol is missing. On my working build, the symbol is presne.t
[15:32] <rbasak> That narrows it down at least.
[15:33] <cjwatson> You should be able to see what packages are being installed in the build log on each side
[15:33] <rbasak> ack
[15:34] <cjwatson> Also make sure sources.list is the same (you can see that near the top of the LP build log, in one of its initialisation commands)
[15:34] <cjwatson> override-sources-list
[15:34] <cjwatson> You'll have to replace "ftpmaster.internal" with "archive.ubuntu.com" but otherwise should be able to use it intact
[15:43] <cjwatson> (It is just about technically possible to set this all up locally, aside maybe from the strange DNS view hacks that I've never seen directly.  But having been beating my head against it for the last two days I can't yet say I'd recommend trying it.)
[15:44] <rbasak> I'm starting to suspect that libgpg-error has a bug related to concurrent builds
[15:44] <rbasak> The configure output is identical
[16:00] <nacc> rbasak: but the issue we're seeing is unrelated to the symbol being present or not, it's the rpath thing snapcraft does
[16:01] <nacc> rbasak: that is, check if the libgpg-error.so has the symbol in the snap (not the one used by _pygit2). if it does, the build of libgpg-error isn't the problem.
[16:02] <nacc> rbasak: if it does, check the `ldd` output for _pygit2, you'll see in the working cases it uses our snap's build. In the failing cases it uses the core snap's. I pinged kyrofa on this, and he said they are working on making the build/stage order determinate
[16:02] <nacc> not sure if that will just break us everywhere or fix us everywhere, tbh
[16:03] <rbasak> nacc: inside snap run, if I run python3, then "import pygit2" fails
[16:03] <rbasak> With ImportError: /snap/git-ubuntu/x8/lib/python3.6/site-packages/../../../usr/lib/x86_64-linux-gnu/../libgcrypt.so.20: symbol gpgrt_get_syscall_clamp, version GPG_ERROR_1.0 not defined in file libgpg-error.so.0 with link time reference
[16:04] <rbasak> /snap/git-ubuntu/x8/lib/python3.6/site-packages/../../../usr/lib/x86_64-linux-gnu/../libgcrypt.so.20 is inside the snap
[16:04] <rbasak> ldd gives me ldd /snap/git-ubuntu/x8/lib/python3.6/site-packages/../../../usr/lib/x86_64-linux-gnu/../libgcrypt.so.20
[16:04] <rbasak> 	libgpg-error.so.0 => /snap/core/current/lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f348d9e3000)
[16:05] <nacc> right the last bit is the bug
[16:05] <rbasak> And libgpg-error.so.0 doesn't have that symbol in a broken snap
[16:05] <rbasak> But in my local build, it does
[16:05] <nacc> it's the *wrong* libgpg-error
[16:05] <rbasak> Oh.
[16:05] <rbasak> Staging order?
[16:05] <nacc> not libgcrypt, libgpg-error
[16:05] <nacc> yeah, i *think* so, but that's what my commit was supposed to fix
[16:05] <nacc> so it's somethign else, but heck if i know wht
[16:06] <nacc> i did see this from the launchpad build logs:
[16:06] <nacc> Copying needed target link from the system
[16:06] <nacc>              /lib/x86_64-linux-gnu/libgpg-error.so.0.17.0
[16:06] <nacc> i think "system" here is the core snap, but i'm not sure
[16:07] <nacc> snapcraft does some weird stuff about library resolution, and that was something we had to fix when we reverted snapcraft before
[16:07] <nacc> because it did it "wrong" :)
[16:08] <nacc> rbasak: can you confirm in the broken snap, the libgpg-error.so *in* the git-ubuntu snap does have the symbol?
[16:08] <rbasak> So in the "good" build tree, I don't see the missing symbol in ./parts/git-ubuntu/install/lib/x86_64-linux-gnu/libgpg-error.so.0, but I do see it in ./parts/libgpg-error/install/usr/lib/libgpg-error.so.0.22.0
[16:09] <rbasak> And it's also in ./prime/usr/lib/libgpg-error.so.0.22.0 in the good snap
[16:09] <nacc> hrm, yeah, the 'lib/x86_64-linux-gnu bit should get pruned by our yaml
[16:09] <rbasak> In the bad snap, the final thing doesn't have the symbol, which is presumably equivalent to what was in prime in the build tree
[16:10] <rbasak> So that's the difference I think. Same snapcraft.yaml, same version of snapcraft.
[16:10] <nacc> rbasak: line 395 of the yaml, iirc
[16:12] <rbasak> OK. So if I can get that line working, the problem should be solved
[16:12] <rbasak> lib/x86_64-linux-gnu/libgpg-error.so.0 vs. usr/lib/*/*gpg-error*
[16:12] <rbasak> Perhaps the globbing doesn't catch the multiarch directory
[16:14] <nacc> line 395 should be          - -lib/*/*gpg-error*
[16:15] <nacc> i think it does, because we don't end up with two libgpg-error in the snap
[16:15] <nacc> the problem is that possibly the timing is off as to when snapcraft does it's rpath search
[16:15] <nacc> i think we'd need kyrofa to help with that, he figured this out last time :)
[16:17] <rbasak> If it is ignoring it, then how is it that the "bad" libgpg-error.so.0* ends up in the snap?
[16:18] <rbasak> Or are you saying that it ignores the ignore for the purposes of this rpath search?
[16:18] <nacc> rbasak: afaik, the bad libgpg-error never ends up in the snap
[16:19] <nacc> it's the linktime reference that is bad
[16:19] <nacc> which i believe snapcraft influences by editing the rpath in the library itself, but i'm not sure (they do soe patchelf voodoo)
[16:19] <rbasak> I can tell whether a snap is good or bad by examining the symbols in libgpg-error.so.*. Would you expect that?
[16:19] <nacc> rbasak: *which* libgpg-error.so ?
[16:20] <rbasak> The one in usr/lib in the snap squashfs
[16:21] <rbasak> Perhaps we should move to #snappy
[16:21] <nacc> yeah we can


[09:07] <XioNoX> hi !
[09:21] <asac> hi XioNoX
[09:21] <XioNoX> hi asac ;)
[09:22] <gnomefreak> morning
[09:22] <asac> morning gnomefreak
[09:23] <XioNoX> asac, new MDC... All my bookmarks are useless now :(
[09:23] <asac> http://developer.mozilla.org/en/Code_snippets still exists ;)
[09:23] <asac> http://developer.mozilla.org/en/How_to_Build_an_XPCOM_Component_in_Javascript
[09:23] <asac> exists too
[09:24] <asac> http://developer.mozilla.org/en/Adding_preferences_to_an_extension too
[09:24] <asac> hmm ... everything i have in my awesome bar still exists ;)
[09:25] <gnomefreak> is n-m Intrepid meant to have a "device: etho state: activated" normally its just the 2 computer icon
[09:25] <asac> gnomefreak: ?
[09:25] <asac> dont understand what you mean
[09:25] <XioNoX> nothink i have in my firefox bookmark folder exist :(
[09:25] <asac> nm is supposed to list all devices that are detected
[09:25] <asac> XioNoX: switch to english
[09:25] <gnomefreak> there is a green icon next to the normal 2PC icon
[09:25] <asac> i always told you
[09:25] <asac> XioNoX: this is the right time to admit that not using the world-language causes pain :)
[09:26] <XioNoX> asac, 3/4 of my booksmarks are in english :)
[09:26] <asac> make that 4/4 ;)
[09:26] <gnomefreak> that tells me im connected for most part. the exact text is in my last post inside the "
[09:27] <gnomefreak> screenshot coming
[09:28] <asac> gnomefreak: you have a screenshot? i havent seen anything green
[09:28] <asac> good
[09:28] <asac> XioNoX: i think URLs that are invalid are a bug
[09:28] <asac> if they were in "en" language
[09:29] <XioNoX> ok, but it is not really important, I've memorise all my MDC bookmarks :o
[09:29] <XioNoX> :)
[09:29] <saivann> asac : I just subscribed you to bug 236964, the sunbird-locales and lightning-extension-locales are ready for your review
[09:31] <gnomefreak> asac: the icon in upper right between the updte icon and the 2 pcs icon (the green one) http://www.flickr.com/photos/26378196@N05/2780972730/sizes/l/
[09:31] <gnomefreak> saivann: thanks
[09:31] <asac> jtv: we
[09:31] <asac> jtv: when is the comment change to land?
[09:31] <jtv> asac: we to you too
[09:31] <asac> ;)
[09:31] <jtv> asac: landed some time ago!
[09:31]  * gnomefreak has to look at mine to find out what i did
[09:31] <jtv> asac: still problem!?
[09:32] <asac> jtv: land == production deployment
[09:32] <asac> jtv: so maybe i should ask "when will it get rolled out" ;)
[09:32] <saivann> asac : There is a lot of changes in this new release and it's 4:31 am here, I suggest that you take a look at it, and that you tell me if there is things to fix in the afternoon (I would go to bed now :P )
[09:32] <saivann> gnomefreak : Also thanks for taking the initial steps!
[09:32] <jtv> asac: So much happened since then I can't even remember...  If it went "fix committed" after 2.0, it rolls out tonight.  Otherwise, it should already be there.
[09:33] <asac> saivann: good idea. get some rest
[09:33] <saivann> asac : See you later then ;)
[09:33] <jtv> asac: but I was pretty sure it rolled out 4 weeks ago... no?
[09:33] <gnomefreak> they are important since sunbird doesnt work for a lot of people without them
[09:33] <asac> jtv: you said that it was committed and that it would get rolled to production in a few weeks back ten
[09:33] <asac> back then
[09:33] <gnomefreak> same with lightning
[09:33] <jtv> asac: that seems like a year ago now :-)
[09:34] <saivann> gnomefreak : Yes, I fixed both package so that situation won't happen in the future
[09:34] <asac> jtv: ok. i then have to embargo auto updates of langpacks .... until i fixed the po2xpi transformer
[09:34] <jtv> asac: remember, it's improper syntax so it could be going wrong somewhere else
[09:34] <asac> jtv: so starting tomorrow the exports will have the new .po format?
[09:34] <jtv> asac: yes
[09:35] <jtv> asac: ohhhh, you're talking about the comments *in the PO files*?
[09:35] <gnomefreak> saivann: cool thanks, i still think they should be 1 locale package for sunbird and lightning. Im sure we are gonna still build both or we remove lightning from it since lighting is gonna be in tbird3
[09:35] <gnomefreak> s/they/there
[09:35] <asac> jtv: right ;)
[09:35] <jtv> asac: I thought you were talking about the "end-of-line comments" in properties files that turned out to be the double-slashes in URLs.  Sorry.
[09:35] <asac> jtv: no :) ... that fix was already rolled out
[09:36] <jtv> asac: right, I thought so, so I was confused and concerned.  :)
[09:36]  * asac nods
[09:36] <saivann> gnomefreak : I also think that we should wait to see Tb3 before, because the way lightning-extension-locales and sunbird-locales package builds is pretty different
[09:37] <jtv> asac: so in that case yes, it happens tomorrow
[09:37] <asac> jtv: so will that "po-file-format-change" get rolled tomorrow?
[09:37] <asac> ok.
[09:37] <asac> i told arne to stop auto updates until i fixed the po2xpi transformer
[09:37] <gnomefreak> saivann: true, i have it built but as of this point it hasnt been included, i will be building snapshot sometime this week
[09:40] <saivann> gnomefreak : Great. If Tb3 don't ship with lightning included, then we can consider making only one package for sunbird-lightning locales. With 0.8, I also worked to make lightning-extension-locales and sunbird-locales working the same way, so it's one of the first step before having only one source package :)
[09:42]  * saivann is now sleeping for ~7 hours
[09:50]  * gnomefreak nods
[09:50] <gnomefreak> asac: mozilla-devscripts is broken?
[09:50] <gnomefreak> version 0.09
[09:51]  * gnomefreak tried make -f command as well as debian/rules get-orig-source DEBIAN_DATE=20080819
[09:52] <gnomefreak> both (fail)
[09:53] <gnomefreak> make -f /usr/share/mozilla-devscripts/thunderbird-3.0.mk DEBIAN_DATE=20080819  is the make -f command i ran
[09:53] <gnomefreak> morning Volans
[09:53] <Volans> Hi gnomefreak
[09:54] <gnomefreak> fta or asac see commands above and let me know what is wrong with them please. i would like to get tbird built and finish chatzilla today
[10:06] <gnomefreak> anyone using firefox 3.1?
[10:06] <Volans> gnomefreak:  I have it installed but from mozilla tarball
[10:07] <gnomefreak> you can see me?
[10:07] <gnomefreak> wtf is going on
[10:08] <gnomefreak> i cant open webpages and now i see i cant run apt-get update all repos fail
[10:08] <Volans> gnomefreak: yes I read you
[10:12] <gnomefreak> be back try reboot
[10:16] <gnomefreak> ok updates should really tell you to restart
[10:19] <gnomefreak> ok seems firefox update broke firefox
[10:19] <gnomefreak> nope just very slow
[10:21] <Volans> better than all broken
[10:23] <gnomefreak> here are errors i get using mozilla-devscripts fta or asac
[10:43] <gnomefreak> anyone know why im getting bzr: ERROR: Path(s) are not versioned: debian/changelog while trying to commit?
[10:44] <gnomefreak> have to assume its from chatzilla (0.9.83-0ubuntu1) intrepid; urgency=low but that looks right to me
[10:44] <gandi> heya!
[10:44] <gandi> asac: let me know when you have a free second ;)
[10:44] <gnomefreak> hi gandi
[10:46] <Volans> gnomefreak: have you already try with `bzr status` to see what happen?
[10:46] <gnomefreak> bzr status
[10:46] <gnomefreak> unknown: debian/
[10:46] <Volans> is not under version control
[10:47] <Volans> you can run:
[10:47] <Volans> bzr add debian/
[10:47] <gnomefreak> i must have missed that
[10:47] <gnomefreak> thanks
[11:11] <asac> gnomefreak: ask fta for mozilla-devscripts
[11:11] <asac> gandi: ill ping you after lunch (where i am heading now)
[11:11] <gnomefreak> asac: ok
[11:11]  * gnomefreak has an issue with chatzilla bzr-builddeb wont build it without a source tarball
[11:12] <gnomefreak> guess i use dpkg
[11:13] <gandi> asac: that's ok :)
[11:14] <asac> gnomefreak: if upstream is still rev 1, you can use: bzr bd --export-upstream=- --export-upstream-revision=1 -e
[11:14] <asac> and the get the orig.tar.gz from the build-area directlry
[11:14] <asac> gnomefreak: otherwise look with bzr log  what the upstream revision is and replace it in that command properly
[11:23] <gnomefreak> ahthanks ill try that when i get done at drs. is there a general dir/file in upstream files that holds build-depends
[11:23] <gnomefreak> asac: ^^ sorry forgot your nick
[11:24] <gnomefreak> ah lunchtime
[11:26] <gnomefreak> i figured chrome/chatzilla.jar but its not
[11:33] <gnomefreak> Jazzva: if your around where should i look in .xpi source for build-deps
[11:34] <gnomefreak> nevermind Jazzva and asac it was caused by the first error it seems
[11:37] <gnomefreak> Jazzva: http://pastebin.mozilla.org/520767  i added zip to build-deps to try and fix that but it still fails with same error (i have all depends installed AFAIK. if im not here please ping me and ill read logs when i get home
[11:38] <gnomefreak> looks like a file is missing in .xpi and maybe we should wait for CVS to update to latest version
[11:59] <asac> gnomefreak: you dont have a build command specified? your build does nothing :) ... check that the build command is good
[11:59]  * asac  now really going for lunch ;)
[12:23]  * Volans going for lunch too
[12:43] <asac> back
[12:43] <asac> gandi: ^^
[13:07] <XioNoX> asac, I have some question about the application window
[13:13] <gandi> asac: back
[13:15] <XioNoX> asac, the easier way to add alternatives in the application tab, is to modify the firefox code :)
[13:16] <asac> XioNoX: yes. however, my main concern right now is not the application tab, but to get something _similar_ UI-wise in a ubufox dialog that pops up when you click on "Get alternatives"
[13:16] <asac> XioNoX: application tab would be nice to have.
[13:16] <asac> not required though
[13:17] <asac> XioNoX: point is that not even all mime-types are listed in application tab iirc
[13:17] <asac> so we need to do something anyway
[13:17] <XioNoX> ha, I though you wanted to modify it
[13:17] <XioNoX> directly
[13:17] <asac> XioNoX: i want at some point in the future ... but if overlaying is too hard, we dont need that
[13:18] <asac> XioNoX: if you can do a similar dialog that just has the mime-types on the left and on the right a drop down with the alternatives and an entry to "search for alternatives ..."
[13:18] <asac> that would be perfect
[13:18] <asac> XioNoX: shouldnt be that hard. you just iterate over the navigator.plugins array
[13:19] <XioNoX> yes, we can overlay the richlistbox, and use some getElementByAtribute, when the list is loaded totally, and then modify the others atributes of the item
[13:21] <XioNoX> ok, and when we will select an item in the list, it will change the key you have definied yesterday ?
[13:22] <asac> yes
[13:24] <XioNoX> and the list will be all the diffetents installed plugins for the mimetypes, or all the plugins installed or not ?
[13:25] <fta> hi
[13:32] <asac> XioNoX: the left hand side would have the mime-types currently used
[13:32] <asac> XioNoX: the right hand side would allow users to switch to all plugins that match the mime-type
[13:32] <XioNoX> used=installed ?
[13:33] <asac> ... and to install more (e.g. the plugin finder wizard)
[13:33] <asac> XioNoX: no ... used == .pluginsUsed
[13:33] <asac> e.g. what we just developed
[13:33] <asac> hi fta
[13:33] <XioNoX> on the current page
[13:33] <XioNoX> ok
[13:34] <asac> yep
[13:34] <asac> e.g.
[13:34] <asac> | left  | right |
[13:35] <asac> | application/x-shockwave-flash | ( Adobe Flash , { Adobe Flash | Gnash | Install ... }) |
[13:35] <asac> e.g. Adobe Flash is the currently used one
[13:36] <XioNoX> ok, ok
[13:53] <fta> asac, satisfied by my answer for liferea ?
[13:57] <asac> fta: didnt get it yet ;)
[13:57] <asac> fta: whats the bug id?
[13:57] <fta> bug 259578
[13:59] <asac> fta: okay
[13:59] <fta> good
[13:59] <asac> fta: and setting -DXULRUNNER_HOME=<empty> unconditionally in Makefile isnt fix-worthy?
[14:00] <fta> doesn't matter, it's not used
[14:00] <fta> the only location is now protected by the patch
[14:02] <asac> fta: true. still upstream should fix it imo to prevent future confusion ;)
[14:02] <asac> anyway
[14:02] <asac> fta: confirmed bug and asked for other pieces
[14:05] <fta> but i wonder why his pkg-config reports libdir and not ours
[14:06] <asac> fta: it doesnt. it did for the old xulrunner. if it does he has a patched xulrunner, but even debian doesnt patch it that way afaict
[14:06] <asac> maybe fedora has such a patch? (though they said they have only 2 or 3 patches in total)
[14:06] <fta> this test appeared in the last version only
[14:10] <fta> lol  https://bugzilla.redhat.com/show_bug.cgi?id=399541#c14
[14:12] <asac> not sure what that means ;)
[14:12] <fta> redhat bug 458295
[14:12] <fta> fedora bug 458295
[14:13] <asac> https://bugzilla.redhat.com/show_bug.cgi?id=458295
[14:16] <fta> i can't see their patches
[14:17] <fta> they are not browsable
[14:17] <fta> http://koji.fedoraproject.org/koji/rpminfo?rpmID=701657
[14:20] <asac> fta: they should have everything in CVS
[14:25] <asac> fta: http://cvs.fedora.redhat.com/viewvc/devel/xulrunner/
[14:25] <asac> http://cvs.fedora.redhat.com/viewvc/devel/liferea/
[14:27] <fta> done
[14:28] <fta> gasp, i posted the files without the LP:# for the sponsor bug. damn, i always forgot, it's unnatural
[14:28] <asac> fta: its good to have an entry:
[14:29] <asac>  * fix LP: #XXXX - "title is here"; fixed by new upstream release.
[14:29] <fta> i usually try to follow the syntax used by the previous uploaders
[14:30] <asac> fta: ah ok
[14:34] <fta> lp should add a table with the attachments at the top, like bugzilla
[14:35] <fta> and a way to make attachments obsolete
[14:35] <asac> fta:  you can remove attachments ;)
[14:36] <asac> fta: there is a table with all attachments on the side
[14:36] <fta> oh
[14:37] <fta> then if you want, i can updated them to include the missing LP:#
[14:37] <asac> if you have that change, pleaes do
[14:37] <asac> i am waiting for your go
[14:37] <fta> ok, hold on
[14:40] <fta> done
[14:40] <fta> it's ugly, you can't replace, just delete. then the comments are weird now
[14:40] <asac> hehe
[14:40] <fta> and it's only 1 file at a time
[14:41] <fta> ui limitation obviously, as apport could do better
[14:42] <asac> fta: it doesnt close the crash and cpu spikes bugs?
[14:42] <fta> read my comment on bug 203157, it's not the same bug
[14:43] <fta> people are reporting indefinite freezes, i just complained about spikes
[14:43] <fta> comment 30
[14:44] <asac> fta: i'd say that you can high-jack that bug and ask others to report new bugs when they still see the performance issues
[14:44] <asac> most bugs get poluted by comments from users that have different bugs
[14:45] <asac> so we have no choice but to claim bugs and hope that users dont file new ones
[14:45] <asac> ;)
[14:46] <fta> the initial bug as been confirmed by several users, I jumped in based on #26
[14:46] <asac> fta: i can add the LP: #203157 to changelog if you want
[14:46] <asac> (behind the spikes entry)
[14:46] <fta> imho, it's different
[14:47] <asac> ok. then ... anything else? like a crash bug?
[14:47] <fta> don't bother, i will comment on the bug and ask for testers
[14:47] <asac> sure
[14:48]  * asac does binary test build and if that starts pushes the sources
[14:48] <asac> fta: 28th aug is feature freeze ... so better get new upstream versions in until then ;)
[14:49] <asac> fta: if there is anything you really want to see upgraded ;) ... we can still bump afterwards if there are important bugs.
[14:49] <fta> so soon ?
[14:49] <fta> so exit ff3.1, songbird, flock ?
[14:50] <asac> we can do ffox3.1 and xul 1.9.1 in universe
[14:50] <fta> i wanted prism in too, but i can't sort out the webapps mess. i'm stuck
[14:50] <asac> fta: whats the problem? the backend still?
[14:51] <fta> they changed the format so all webapps already installed are no longer working
[14:51] <fta> but as it's unpacked in the user profile, it's a mess
[14:51] <fta> i tried to magically fix it at runtime, it's not perfect
[14:53] <XioNoX> asac, can I use the same .js file for the new window and the "old overlay" ?
[14:53] <fta> http://bazaar.launchpad.net/~mozillateam/prism/prism/annotate/head:/debian/rules  from 65 to the end
[14:54] <fta> and http://bazaar.launchpad.net/~mozillateam/prism/prism/annotate/head:/debian/prism.sh from 67 to the end
[14:56] <fta> basically, if the syntax is not recognized or if some fields are missing, a UI pops up, then you fix the fields and save, but it's only saved as a desktop file on the desktop, not in the webapp file (not possible as it's system wide) and not the unpacked version in the user profile
[14:56] <asac> fta: uploaded
[14:56] <fta> asac, thanks
[14:56] <asac> XioNoX: better use a new .js
[14:57] <XioNoX> ok
[14:57] <asac> XioNoX: i dont want to make overlay.js more interwoven with things than it already is
[14:57] <asac> I need to clean it up anyway
[14:59] <XioNoX> you have made the whole ubufox by yourself ??
[15:02] <asac> XioNoX: no. jazzva wrote some code. translations were contributed and so on
[15:03] <XioNoX> ok
[15:20] <fta> yep, they added libdir: http://cvs.fedora.redhat.com/viewvc/devel/xulrunner/mozilla-pkgconfig.patch?revision=1.11&view=markup
[15:25] <asac> too bad.
[15:25] <asac> so much about "we are upstream compatible" claim ;)
[15:27] <XioNoX> asac, what mean the let in "let item = document.createElement("richlistitem");"
[15:27] <XioNoX> or
[15:27] <XioNoX> for each (let visibleType in visibleTypes) {
[15:29] <asac> XioNoX: google?
[15:31] <asac> XioNoX: http://developer.mozilla.org/en/New_in_JavaScript_1.7#Block_scope_with_let
[15:31] <XioNoX> yeah, i'm reading that, thanks
[15:31] <XioNoX> and there are a french version :D
[15:34]  * rbu
[15:35]  * asac gets coffee
[16:17] <XioNoX> asac, can you just look at this loop : http://mxr.mozilla.org/mozilla/source/browser/components/preferences/applications.js#1193
[16:17] <XioNoX> I can't find how it works
[16:17] <XioNoX> specially with the setAttribute,
[16:17] <asac> XioNoX: what is it that you dont understand?
[16:18] <asac> XioNoX: setAttribute sets an xml attribute
[16:18] <XioNoX> how does this display something ?
[16:18] <asac> e.g. and element=<test> .... with element.setAttribute("name", "Alexander"); would become <test name="Alexander"/>
[16:18] <XioNoX> and in 2 colums
[16:19] <XioNoX> ok, but <test name="Alexander"/> will show nothing on screen
[16:19] <XioNoX> and there are nothing to separe the 2 parts
[16:19] <asac> XioNoX: maybe its a feature if richlistitem? .... or maybe the richlist is not the complete element, but just the drop down menu?
[16:20] <asac> XioNoX: look at the implementation of richlistitem
[16:20] <XioNoX> in my mind the richlist is the complete line, acording to vars names
[16:20] <asac> should be a xbl implementation
[16:21] <asac> e.g. richlistitem.xml
[16:22] <XioNoX> I haven't find any xml files and no links in the xul file...
[16:24] <asac> XioNoX: its in toolkit
[16:24] <asac> richlistbox.xml
[16:24] <asac> ther eis the binding for richlistbox and richlistitem ... which extends another widgets and so on
[16:26] <asac> i nthink all is based on the handlers in ./browser/components/preferences/handlers.xml
[16:26] <asac> but try to read through it ;)
[16:26] <asac> starting from richlistbox ;)
[16:26] <XioNoX> you think that I can just use the same attribute names ? :D
[16:40] <asac> XioNoX: try?
[16:40] <asac> you will figure ;)
[16:40] <XioNoX> it is what i'm doing :)
[16:40] <XioNoX> i'm talking too fast :)
[17:16] <saivann> asac : I'm back, if you have some time for the locales
[17:17] <saivann> asac : bug 230209 and bug 236964
[17:36] <fta> asac, if you care to have a look at prism...
[17:54] <XioNoX> back!
[18:23] <asac> Jazzva: you think you have time to test something before i upload nspluginwrapper?
[18:23] <asac> and probably fix it ;)
[18:25] <asac> fta: are the old webapps incompatible ... or just the config/desktop file?
[18:25] <asac> i assume system-wide installed webapps should work as we can upgrade them through our packages
[18:25] <asac> so what is left are user webapps that were installed/setup per-profile
[18:26] <fta> they don't if you already used them at least once
[18:26] <asac> fta: ok. because the global config file is copied to users profile?
[18:26] <fta> try it, use any of them with the version in hardy or intrepid, then try my ppa
[18:27] <Jazzva> asac, not at the moment :(. I think I have to finish this project till midnight (or at least to make something buggy and then fix it in the next few days)
[18:27] <fta> in addition to that, in 0.8+ it was unpacked in ~/.prism/something, now in 0.9+ it's in ~/Webapps
[18:27] <Jazzva> asac, actually... how long is the test?
[18:27] <asac> fta: ok. we can migrate the profile thing. whats the problem?
[18:27] <fta> WebApps
[18:27] <asac> Jazzva: ok. lets look at that tomorrow then
[18:27] <Jazzva> asac, great :). Thanks
[18:28] <fta> asac, that's what i've tried, but it doesn't work well
[18:29] <asac> fta: did you identify what the problem is?
[18:31] <fta> any webapp not patched by my script will not work
[18:31] <asac> fta: and what webapps will not get patched? is that a matter of locating them?
[18:31] <fta> but it's been a while since i last touched prism, so i don't remember all the details
[18:32] <asac> you said that in .8 they were installed in  ~/.prism/something ... how comes that i cant find any ".prism" in that script?
[18:33] <asac> ok i have:
[18:33] <asac> ls .prism/0m3mar0y.default/webapps/
[18:33] <asac><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>[18:33] <asac> so 0.9 needs them to be copied to ~/Webapps ?
[18:34] <fta> hm, don't you have a ~/.webapps ?
[18:34] <fta> see, i don't remember
[18:35] <fta> i'm still in my svg merge context
[18:35] <asac> .webrunner/u5618co2.default/
[18:36] <asac> thats the old dir i have
[18:38] <asac> fta: your prism build doesnt work with my xulrunner build because of jemalloc
[18:38] <asac> why do you have jemalloc as shared lib again?
[18:39] <fta> yep, i know, you remove the ld.config stuff in july
[18:39] <fta> no rebuild since
[18:39] <asac> fta: i changed xulrunner to static jemalloc
[18:40] <asac> is prism-bin just a xulrunner-stub?
[18:40] <fta> yes
[18:40] <fta> it's using my new xulapp build system
[18:40] <fta> you just need to rebuild it
[18:41] <fta> or add /etc/ld.so.conf.d/xulrunner-1.9.conf for the time being
[18:42] <asac> fta: nope ... there is no libjemalloc.so anymore
[18:42] <fta> so ? a rebuild should do it
[18:42] <asac> fta: yes. that should be enough
[18:43] <fta> i still have libjemalloc.so btw
[18:44] <asac> oh right
[18:44] <asac> i have to check the state then
[18:44] <asac> i think there was a regression intrepid with static linkage
[18:44] <asac> guess i disabled it again
[18:45] <asac> ah right ... the jemalloc patches are commented atm
[18:45] <asac> anyway
[18:45] <asac> not sure how to reproduce the prism issue. for me moving the webapps dir from the profile to .webapps works
[18:45] <asac> at least for google-mail
[18:46] <asac> if i dont do that i get a broken update.xul dialog ... closing that will open google-mail again
[18:47] <fta> take a .webapp file not from this package (ie, not fixed), and click on it
[18:47] <fta> http://www.sofaraway.org/ubuntu/tmp/google-maps-fr.webapp
[18:54] <fta> well, i probably need one more hack into the launcher
[18:55] <fta> lunch time. cu
[18:55] <asac> fta: enjoy ;)
[18:55] <asac> fta: ill try to reproduce with the webapp above
[18:59] <Ampelbein> hi there! am i right that bug #258642 should be set to invalid because retracing failed?
[19:32] <asac> Ampelbein: looking
[19:33] <asac> Ampelbein: download the CoreDump ... install all -dbgsym packages and try to get a backtrace using gdb
[19:33] <asac> Ampelbein: if that fails, close the report
[19:33] <Ampelbein> ok, thanks for the info.
[19:34] <asac> np
[19:34] <asac> Ampelbein: if you want to help wading through crashes, I can subscribe you to a bunch more (e.g. most are private by default)
[19:36] <Ampelbein> asac: if that would help you, that's ok. currently i'm going through the list of "new" and public bugs to find some where i can work on. it's plenty of work to do... ;-)
[19:38] <asac> Ampelbein: are you looking at firefox bugs?
[19:38] <Ampelbein> not specific.
[19:39] <asac> Ampelbein: please read https://wiki.ubuntu.com/MozillaTeam/Bugs/TriagersHandbook and help on firefox bugs. you can learn a lot and earn a lot of karma ;)
[19:39] <asac> the triagers handbook should give easy guidelines what to do with new and incomplete ones ;)
[19:39] <asac> if it lacks information let me know so i can improve that ;)
[19:40] <Ampelbein> ok, thanks. i'll read it and start working.
[19:40] <asac> Ampelbein: cool. concentrate on New and Incomplete bugs ... once you have some experience with that we can look at confirmed bugs and then how to forward upstream ;)
[19:41] <asac> Ampelbein: https://bugs.edge.launchpad.net/ubuntu/+source/firefox-3.0/+bugs?search=Search&field.status=New
[19:41] <asac> ^^ New firefox-3.0 bugs
[19:41] <asac> > 600 bugs :)
[19:41] <gnomefreak> asac: you were part right other part is due to debian/rules and ill look more at it in morning see you tonight or tomorrow
[19:41] <asac> gnomefreak: sure
[19:41] <Ampelbein> woohoo.
[19:41] <Ampelbein> me thinks i have to make some more coffee ;-)
[19:42] <asac> Ampelbein: we could make a standard response. the idea is to get bugs in the https://wiki.ubuntu.com/MozillaTeam/NormalizedBugFormat
[19:42] <fta>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
[19:42] <fta> 10343 root      20   0  125m  84m  14m R   56  4.2 484:10.29 Xorg
[19:42] <fta> 16083 fta       20   0  228m 110m  23m S   37  5.5   3:12.81 prism-bin
[19:42] <asac> thats the main requirement for "confirmed"
[19:42] <fta> a flash inside prism causes Xorg & prism to suck the cpu
[19:43] <asac> Ampelbein: if you have two or three standard responses i can write you a python script that sends the response and changes the bug state accordingly
[19:43] <asac> Ampelbein: just do a few and let me know once you know what text you always have to type ;)
[19:44] <asac> fta: yeah. always the same. flash sucks ;)
[19:44] <asac> (not only cpu)
[19:44] <fta> it used to work fine
[19:44] <knusper> hi
[19:44] <asac> hi knusper ;) ... what flavour do you have ;)
[19:44] <fta> in fact, it works fine, except it sucks cpu while doing so
[19:44] <knusper> asac: crunchy
[19:44] <Ampelbein> asac: i'll try something with thunderbird and mailing the commands. that way i can keep more easily track of what i did.
[19:44] <Ampelbein> but thanks anyway.
[19:45] <asac> knusper: hope you are not burned ;)
[19:45] <knusper> asac: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479854 <<-- i just read thisone
[19:45] <knusper> ;)
[19:45] <asac> Ampelbein: sure :) ... mail interface is efficient too
[19:45] <asac> knusper: yeah. no time :(
[19:45] <knusper> :(
[19:47] <knusper> so i have to switch to icedove?
[19:47] <asac> if you need enigmail now, then yes.
[19:48] <asac> knusper: problem is that iceape has no extension manager ... so installing it by hand is painful
[19:49] <knusper> so, do you also think it is difficult to figure out, what changes must be applied to the enigmail package to get it working with iceape
[19:49] <knusper> i have some time
[19:49] <knusper> but never contributed to debian
[19:50] <asac> knusper: point is the enigmail package needs a severe cleanup
[19:50] <knusper> so its not a minor change
[19:50] <asac> fta: how would i use the build-system.tgz we ship in xulrunner-1.9 to build an extensions?
[19:50] <asac> is there a way to hook in new "makefiles")
[19:50] <asac> hmm
[19:51] <asac> bye fta ;)
[19:51] <knusper> lol
[19:53] <knusper> asac: are you the only person responsible for the enigmail package in debian...?
[19:53] <asac> knusper: only thing that i can offer you is to bug me daily. i'll try to look next time i have a free minute ;)
[19:53] <asac> i cannot give instructions since its long time since i touched that package
[19:53] <asac> knusper: yes. and its unlikely that anyone else gets this package built without a huge ramp-up time ;)
[19:53] <asac> fta might be able to do that ;)
[19:54] <asac> knusper: enigmail isnt ment to be built outside the mozilla tree ... which makes this so hard to do.
[19:54] <knusper> a... I see
[19:55] <knusper> are you a debian guy or ubuntu developer
[19:55] <asac> both :)
[19:55] <knusper> :)
[19:55] <asac> ubuntu eats more time though
[19:55] <knusper> i am new to the *.deb world
[19:55] <asac> knusper: what are your experiences?
[19:55] <knusper> i have lenny running
[19:55] <asac> fta: you think we can use build-system.tgz to build enigmail?
[19:55] <knusper> i like it
[19:55] <knusper> really
[19:56] <asac> sure ... lenny is probably great. i like the pure-gnome feeling of debian desktop ;)
[19:56] <knusper> maybe...
[19:56] <knusper> i use fluxbox
[19:56] <asac> hehe
[19:57] <knusper> i have used openSUSE a very long time
[19:57] <asac> fluxbox is great too ;) ... but there is probabyl no difference desktop wise to the ubuntu package
[19:57] <fta> "pure-gnome feeling" ? screenshot ?
[19:57] <knusper> I use the devel version
[19:57] <asac> knusper: i hope you already feel the relief ;)
[19:57] <knusper> yeah
[19:57] <knusper> sure
[19:57] <asac> whenever i saw anyone using SUSE they never ran security updates ... and of course never upgraded to the next major version
[19:57] <asac> -> crap ;)
[19:58] <fta> btw, strace X is not a good idea
[19:58] <asac> you cant believe that this is still the truth for so many users.
[19:58] <asac> fta: yeah ;) ... you should at least look for use -eopen or something
[19:58] <knusper> cause at suse sometimes a system upgrade will upgrade your system to a unusable state
[19:58] <asac> fta: too bad. i still cant start virtualbox here in intrepid :(
[19:58] <asac> thus no screenshot from pure debian desktop
[19:59] <Ampelbein> hmpf. now i have a (stupid?) question. I installed all dbgsym packages and tried running 'gdb -c CoreDump'. But it just says "File format not recognized". Does this mean the CoreDump is invalid?
[19:59] <asac> fta: but its almost what upstream ships: it even has the  gnome food in the menu ;)
[19:59] <knusper> unusable = not fixable for a user with small linux experience
[19:59] <fta> asac, it's not because of the fool, it simply froze.
[19:59] <asac> knusper: yeah. i dont know why its that way, but it appears to be that way.
[20:00] <asac> knusper: good for the debian based distros ;)
[20:00] <asac> knusper: good for the suse users that get tempted by a good installer ;)
[20:00] <knusper> and hell.... aptitude is kinda fast
[20:01] <asac> fta: you sure its not because of the disk IO that the process slows down like hell?
[20:01] <knusper> if you install something on opensuse you can get your self a cup of coffe, including brewing it
[20:01] <asac> Ampelbein: hmm ... you probably also need to specify the binary?
[20:01] <knusper> but enough suse bashing
[20:01] <asac> hehe
[20:02] <asac> Ampelbein: what does "file CoreDump" give you?
[20:02] <fta> nope, it stopped on a select() then whole desktop turned dead, no mouse, no keyboard, no clock moving, nothing. the box was still alive though, i sshed in but decided to reboot, i had to anyway.
[20:02] <Ampelbein> CoreDump: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/lib/firefox-3.0.1/firefox'
[20:03] <knusper> asac: just for the record, I install icedove now, but I plan to bug you every now and then
[20:03]  * asac builds virtualbox-ose-sourc e
[20:03] <asac> knusper: thanks
[20:04] <asac> Ampelbein: so gdb -c CoreDump /usr/lib/firefox-3.0.1/firefox
[20:04] <knusper> where are you from, anyway?
[20:04] <asac> doesnt work?
[20:04] <knusper> <-- german
[20:04] <asac> knusper: same same here
[20:04] <knusper> thats why you understand my nick
[20:04] <asac> knusper: since you are using alice-dsl chances are high that you are from the hamburg area?
[20:04] <knusper> acutally berlin
[20:04] <Ampelbein> same error: bug258642/CoreDump" is not a core dump: File format not recognized
[20:04] <asac> hmm
[20:04] <asac> ok i am from hamburg ;)
[20:05] <Ampelbein> woohoo, deutsche! ;-)
[20:05] <asac> Ampelbein: are you on i386?
[20:05] <knusper> when I was a child I was in Hamburg for a chess tournament
[20:05] <Ampelbein> y
[20:05] <asac> the core is amd64 ... which explains why it doesent work
[20:05] <asac> Ampelbein: better focus on i386 crashes then ;)
[20:05] <Ampelbein> ah. now i see.
[20:05] <knusper> so long time ago..... ok.... cu soon
[20:05] <Ampelbein> my error.
[20:05] <asac> knusper: cu
[20:06] <Ampelbein> sorry for bothering you, still learning.
[20:06] <asac> welcome
[20:06] <asac> its not really obvious ;)
[20:06] <asac> gdb should complain that its wrong arch ;)
[20:07] <asac> yay ... virtual box sid is booting ;)
[20:10] <Wulfie> hey folks, I am trying to get lightning going on hardy.  If I use the 0.7 version that is available through synaptic things are working but the google calendar provider does not. If I use the one from the website the left pane gets filled with the calendar bar and I can't make it go away.
[20:10] <Wulfie> any suggestions?
[20:11] <asac> Wulfie: if you use what from the website?
[20:11] <asac> mixing the extensions is probably a bad idea
[20:11] <asac> at least uninstall lignthing package first ;)
[20:11] <Wulfie> asac: if I get the lightning from the mozilla site
[20:11] <Wulfie> I did that
[20:11] <Wulfie> I only had one installed at a time
[20:11] <asac> Wulfie: well. most likely its not compatible ... better use the built we have
[20:12] <asac> the provider is probably broken in 0.7
[20:12] <Wulfie> is the the 0.7?
[20:12] <Wulfie> is there a 0.8?  This was working for me until I reinstalled due to a hard drive crash
[20:12] <fta> [reed], how can i specify a relative date in the "advanced search" on bugzilla ? something like yesterday or 1 week ago..
[20:13] <asac> fta: i think its -1w
[20:14] <asac> Wulfie: what was working for you until you reinstalled?
[20:14] <Wulfie> what is your repo?
[20:14] <Wulfie> asac: hardy+thunderbird+lightning+google provider
[20:14] <asac> Wulfie: hmm
[20:14] <asac> Wulfie: maybe its a profile issue then
[20:14] <asac> Wulfie: uninstall the extension you got from mozilla ... that probably calls for trouble
[20:14] <Wulfie> tried with a clean profile as well
[20:15] <asac> then move the .mozilla-thunderbird directory to a different place
[20:15] <asac> and try again
[20:15] <asac> Wulfie: when it worked, did you start with 0.7 or with a version before that?
[20:15] <Wulfie> I am not entirely sure
[20:15] <Wulfie> is there an updated/testing build of the lightning extension at all?
[20:15] <asac> Wulfie: i'd say try to move the directory above to a safe location
[20:16] <fta> asac, thx, it wored
[20:16] <fta> k
[20:16] <asac> cool ;) ... not sure why i knew that ;)
[20:17] <Wulfie> asac: makes no difference - the problem is that Thunderbird itself has the google provider disabled as it depends on a version of lightning that's not installed
[20:17] <asac> Wulfie: https://edge.launchpad.net/~mozillateam/+archive
[20:17] <asac> there is lightning-sunbird - 0.8+nobinonly-0ubuntu0mt804  for hardy
[20:18] <asac> Wulfie: if that helps, we could think about doing a more official backport in ubuntu-backports
[20:20] <Wulfie> testing now
[20:21] <Wulfie> asac: that's go it
[20:21] <Wulfie> thanks much
[20:21] <asac> Wulfie: so it works?
[20:21] <Wulfie> it does
[20:21] <Wulfie> I now have my google calendar back
[20:22] <asac> Wulfie: good
[20:22] <Wulfie> thanks very much for your assistance
[20:22] <Wulfie> that was bugging me
[20:22] <asac> np
[20:22] <asac> lucky that it helps
[20:23] <Wulfie> I think that the google provider requires a 0.8 version there
[21:03] <[reed]> fta: yeah, -1d or -1w
[21:04] <fta> k
[23:13] <saivann> asac : Busy?
[23:13] <asac> yes, meeting
[23:13] <saivann> asac : ok