[04:24] <Unit193> ochosi: http://paste.openstack.org/show/f7S8clgYUjwHPrancERu That doesn't look right at all.
[04:59] <Noskcaj> micahg, thanks for the sponsoring
[05:01] <micahg> Noskcaj: sure, I'll try to get to more tomorrow (I know I have some merges to look at as well0
[05:05] <Noskcaj> :)
[05:06] <Noskcaj> Just please look a bit more favorably on this month's MOTU application
[05:06] <Noskcaj> I'd wait longer to re-apply, but daylight savings running out means i can't apply till the end of the year if not this month
[05:13] <Unit193> forestpiskie: Uhh, I should have a result in http://iso.qa.ubuntu.com/qatracker/milestones/308/builds/57248/testcases/1310/results but it's not there...
[06:01] <Noskcaj> bug 1290691
[06:16] <Unit193> bluesabre: Know what http://paste.openstack.org/show/2X4hkEWDZcpvJywTCRgD/ means?
[06:20] <Noskcaj> Unit193, i'm going to guess it's from icu52, not much else i can think of
[06:20] <Noskcaj> or is the error in saucy too?
[06:21] <Unit193> Noskcaj: I don't see why downgrading python-datetimeparser (whatever, close enough) would help there then.
[06:22] <Noskcaj> um...
[06:22] <Unit193> I'm more wondering if something in the python module is wrong, or if gcalcli uses a deprecated function or something and it was finally removed.
[06:22] <Unit193> (Had the second before.)
[06:23] <Unit193> Or, if the module pulled a gnome and just dropped something.
[06:26] <Noskcaj> well i'll have to update datetime in debian now
[06:28] <Noskcaj> "Bumped version to 1.0.0 to reflect the major refactoring"
[06:29] <Noskcaj> from upstream changelog
[06:31] <forestpiskie> Unit193: you told me you were doing lts upgrades
[06:31] <Noskcaj> But pyicu and datetime have unpackaged new versions, so maybe trying with those could be a start
[06:32] <Noskcaj> 1.6 and 1.2 respectively
[06:34] <Noskcaj> and the pyicu changelog includes "added support for ICU 52.1"
[06:34] <Noskcaj> which is what ubuntu has
[06:36]  * Noskcaj nominates Unit193 to investigate further and file various FFes as punishment for finding a bug
[06:36] <Noskcaj> now i need to stop being useless and get some dinner
[06:55] <Unit193> forestpiskie: ...No, I don't have any LTS compys.
[06:56] <elfy> mmm
[06:56] <Unit193> Noskcaj: If it's not working now, then it's broken and a bug.
[06:56] <elfy> I'll osrt it out at some point then
[06:57] <Unit193> elfy: Cool, I was going back to edit and mark it as failed, so can you ping me when you do?
[06:59] <elfy> there you go :)
[06:59] <Noskcaj> Unit193, The pyicu changelog also mentions now supporting python2.7 and 3.3, so i'll prepare an upload.
[07:00] <Noskcaj> but i need to go to cadets now
[07:01] <Unit193> Well holding the old one now, may check half way through unicorn. :P
[07:06] <Unit193> elfy: Thing is, I didn't see it anywhere. :/
[07:08] <elfy> you're going to have to be a little bit more specific here ;)
[07:08] <elfy> the unicorn is camouflaged
[07:13] <Unit193> Right, changed to failed (decided it was technically failed and actually had a bug too.)
[07:14] <elfy> so you could see it - you were just mystified by the camouflage for a while then :p
[07:15] <Unit193> Eh?
[07:16] <elfy> Unit193: what did you mean by I didn't see it anywhere?
[07:16] <elfy> it was there all the time just struck through - all the deleted results are there
[07:16] <elfy> or is it because I'm an admin for the trackers
[07:19] <Unit193> Admin.
[07:21] <elfy> ok - I guess that makes sense :)
[07:25] <elfy> Unit193: calendar is still wrong - you went the wrong way ... should be 19:00 not 17:00
[08:57] <ochosi> Unit193: what about the light-locker desktop-file doesn't look right exactly?
[08:58] <Unit193> That last line.
[08:59] <Unit193> Exec=NoDisplay=true
[08:59] <ochosi> oh
[08:59] <ochosi> that's weird
[08:59] <Unit193> (Also don't need to copy the entire file, just what's different.)
[08:59] <ochosi> don't know where that's from, upstream it looks like this: https://github.com/the-cavalry/light-locker/blob/master/src/light-locker.desktop.in.in
[08:59] <Unit193> This renders the entire thing moot, right?  I don't see why that'd stop it from running.
[08:59] <Unit193> ochosi: -settings?
[09:00] <ochosi> oh
[09:00] <ochosi> :)
[09:00]  * ochosi hasn't had his morning coffee yet
[09:00] <Unit193> Coffee. \o/
[09:02] <ochosi> Unit193: so, until i get my coffee, where is this desktop file from again?
[09:03] <Unit193> ~/.config/autostart/ IIRC.
[09:07] <ochosi> ah ok, now i get the context
[09:07] <ochosi> this is the light-locker desktop file as created by -settings
[09:07] <ochosi> why didn't you just say so
[09:07] <ochosi> this is when light-locker is set to disabled?
[09:08] <ochosi> (i presume there's a \n missing somewhere in the code :))
[09:10] <bluesabre> Unit193: my guess is the same as yours, different api
[09:11] <Unit193> ochosi: That's what I thought.  Well, figured maybe you'd know, or something.
[09:12] <Unit193> bluesabre: Looks more like datetime icu mismatch.
[09:18] <ochosi> whoa, early morning to you, bluesabre :)
[09:19] <bluesabre> don't remind me >.<
[09:20] <ochosi> bluesabre: have you seen the nasty new greeter-bug yet? it's really the one i was describing earlier :/
[09:20] <bluesabre> oh no
[09:20] <bluesabre> link?
[09:23] <ochosi> https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1290575
[09:24] <ochosi> bluesabre: actually i just read some backlog between ali and xno on #ubuntu-devel and it seems this is not (only) our fault
[09:24] <ochosi> wondering though why the same thing works for unity-greeter but doesnt for us
[09:33] <bluesabre> that doesn't sound fun
[09:33] <bluesabre> but maybe somebody will create a patch quickly
[09:34] <bluesabre> menulibre 2.0.3: https://launchpad.net/menulibre/2.0/2.0.3
[09:34] <bluesabre> suppose its time to poke Noskcaj for some uploads since I've not been able to be around much lately
[09:35] <bluesabre> good news is that I've been looking for a reason to do a new greeter release, that seems like a pretty valid one
[09:39] <ochosi> yeah, i've also not been around too much
[09:39] <ochosi> will try to finish some theme stuff today and get releases ready
[09:59] <bluesabre> ok, emailed jackson
[09:59] <bluesabre> (possibly) bbl today
[09:59] <bluesabre> have fun folks :)
[10:00] <ochosi> righty, seeya bluesabre :)
[10:00] <ochosi> Unit193: mind to report a bug about l-l-settings?
[11:31] <starrats> good morning and hope good news for me, I was able to get thru update/upgrade/dist-upgrade without an error message.
[11:32] <starrats> need to restart bbl
[11:32] <starrats> exit
[11:39] <starrats> even made it thru restart without the cursor 'freezing/locking up' on me, I can only hope my bug reports were fixed, even the 'usb-modeswitch-data' wasn't an error message on terminal, 
[13:06] <brainwash> starrats: that's really good news
[13:07] <brainwash> was/is the freezing cursor problem a random one?
[13:07] <brainwash> maybe you are just lucky today :)
[13:27] <elfy> https://bugs.launchpad.net/ubuntu/+source/xfce4-indicator-plugin/+bug/1290803
[13:28] <elfy> that's odd - I can see the same behaviour here
[13:29] <brainwash> bug :(
[13:30] <elfy> yea
[13:30] <elfy> I can tell :p
[13:30] <brainwash> never noticed it
[13:32] <brainwash> please run "xfce4-panel -q; xfce4-panel"
[13:33] <brainwash> and try to reproduce the problem
[13:33] <brainwash> any terminal output could be helpful
[13:33] <elfy> I guess I'd need to actually get the damn thing back before trying that 
[13:33] <elfy> not doing that now - only got 10 minutes lunch left
[13:34] <elfy> I'll try and remember to do it later
[13:34] <brainwash> ok, but what do you mean with back?
[13:34] <elfy> so I can read it :p
[13:34] <elfy> anyway - not now ... 
[13:34] <brainwash> k
[13:35] <brainwash> I'll try to trigger the faulty behavior later
[13:36] <elfy> ok - well try and explain what you mean by terminal output and I'll see the ping when I get back
[13:39] <brainwash> elfy: if you start the panel from the terminal and do the steps to reproduce the issue, it will print some (more or less) helpful debug messages :)
[14:06] <schproodle> brainwash, FWIW 13.10 also has a blank properties panel 
[14:11] <schproodle> brainwash, 14.04 indicator properties seems to work here
[14:12] <brainwash> strange, the launchpad report targets the 14.04 package
[14:13] <brainwash> so it works fine after closing the window once?
[14:13] <brainwash> maybe you have to close and reopen it twice
[14:15] <wickz> Description:	Ubuntu Trusty Tahr (development branch)
[14:15] <wickz> Release:	14.04
[14:15] <wickz> xfce4-indicator-plugin:
[14:15] <wickz>   Installed: 2.3.0-0ubuntu1
[14:15] <wickz>   Candidate: 2.3.0-0ubuntu1
[14:15] <wickz>   Version table:
[14:15] <wickz>  *** 2.3.0-0ubuntu1 0
[14:15] <wickz>         500 http://ca.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
[14:15] <wickz>         100 /var/lib/dpkg/status
[14:15] <brainwash> ok, please add a comment to the bug report
[14:16] <brainwash> bug 1290803
[14:16] <brainwash> and say that you cannot reproduce it in 14.04
[14:16] <wickz> brainwash, me to comment?
[14:16] <brainwash> yes
[14:17] <brainwash> adding (helpful) comments is a great way to get the problem fixed faster
[14:18] <brainwash> not everyone reads this irc channel :P
[14:21] <wickz> ok, how's that look?
[14:23] <wickz> 1290803 
[14:23] <wickz> bug #1290803 
[14:45] <starrats> brainwash:  sorry I missed your earlier comments but thank you and the frozen/locked cursor issue could be random, not sure at the moment, afraid to restart for the hell of it and get frozen out again, lol
[16:36] <ali1234> tumblerd stopped generating thumbnails again
[16:36] <ali1234> stopped on 27th feb
[16:44] <elfy> brainwash: all I got in terminal was http://pastebin.com/4Y3piRx0
[16:45] <elfy> when I got back short while ago - I had no panel at all
[16:45] <brainwash> restart it then
[16:46] <brainwash> and add the wrapper error message to the report
[16:46] <elfy> what report?
[16:46] <elfy> oh nvm
[16:47] <elfy> no need to add it - ochosi did 
[16:47] <brainwash> oh
[16:47] <brainwash> he also fixed the typo :)
[16:49] <brainwash> ali1234: did you check the folder permissions?
[16:49] <brainwash> ~/.thumbnails
[16:49] <ali1234> yes
[16:50] <brainwash> :/
[16:50] <brainwash> works fine here (test system)
[16:50] <ali1234> i deleted the thumbnails and now it works again
[16:50] <brainwash> even for videos
[16:50] <ali1234> same as before
[16:52] <brainwash> bug 1290575 is caused by gtk-greeter
[16:55] <brainwash> I didn't notice this after the missing gtk_main_quit() call has been added, because I've replaced signal() with sigaction() + different handler function in my local branch
[18:57] <ochosi> brainwash: oh, fun. so you've tested this and it resolves the issue? (somewhat makes sense anyhow...)
[18:59] <ochosi> ali1234: so with compositing, couldn't the shadow-area be used for resizing?
[18:59] <ali1234> they could be yes
[19:00] <ali1234> but it will be a big change to the code
[19:00] <ali1234> the shadows aren't X11 windows
[19:00] <ali1234> they are just compositor surfaces
[19:00] <ali1234> so they can't get input
[19:00] <ochosi> oh
[19:00] <ochosi> so they'd have to be drawn in a different manner? (i'm guessing cairo?)
[19:01] <ali1234> yes
[19:02] <ochosi> i was wondering about this before, but would the shadow have to be a separate window then?
[19:02] <ali1234> everything is a separate window
[19:02] <ali1234> the decoration frame is 10 windows
[19:03] <ali1234> that doesn't include the actual client window
[19:03] <ochosi> Noskcaj: hey, can you take a look at what went wrong with xubuntu-artwork 14.04.0? somehow some folders of the icon-theme are missing in the package (they're in trunk though)
[19:03] <ochosi> oh wow
[19:03] <Noskcaj> ?
[19:03] <ochosi> i thought those were all packed into neat boxes
[19:03] <ali1234> they are, each box is a window
[19:03] <ochosi> Noskcaj: https://bugs.launchpad.net/bugs/1290390
[19:03] <Noskcaj> ok, i'll have a look
[19:04] <ochosi> thanks
[19:04] <ochosi> ali1234: right, so i guess that should/could be discussed with nick before even commencing work on it
[19:05] <ochosi> and after all, there are still quite a few xfwm4 patches that haven't been merged
[19:06] <ochosi> i mostly started thinking about this again after reading that ubuntu disabled window-borders in 14.04
[19:06] <ali1234> lol
[19:10] <ochosi> Noskcaj: would be nice if we could do one more upload before UIF and fix that packaging glitch in the same go
[19:10] <Noskcaj> ok
[19:21] <ali1234> Noskcaj: the thunar bookmarks patch needs a fix too... i haven't coded it yet though
[19:22] <Noskcaj> ali1234, ok. Just link me to anything as soon as it's became my job.
[19:22] <Noskcaj> I think we might need to revert gthumb to 3.2.6 for release
[19:23] <ochosi> why that?
[19:23] <ali1234> i thought we used tumbler?
[19:23] <ochosi> (not that it's all-too-important as we don't seed it by default)
[19:23] <ali1234> thumbnails broke again for me
[19:23] <ochosi> ali1234: you mean ristretto=
[19:23] <ochosi> maybe?
[19:23] <ali1234> ristretto is the viewer isn't it?
[19:23] <ochosi> tumbler is only for thumbnails
[19:23] <ochosi> yeah
[19:24] <ali1234> i thought gthumb was gnome-thumbnailer...
[19:24] <ochosi> ah, no, it isnt
[19:24] <ochosi> it's an image-collection viewer
[19:24] <ali1234> oh, i see
[19:24] <ali1234> poor naming choice... :)
[19:24] <ochosi> which uses headerbars now by default
[19:24] <ali1234> oh, that one...
[19:24] <ochosi> which was one reason why we yanked it out of the default seed for 14.04
[19:25] <ali1234> what's wrong with ristretto?
[19:26] <Noskcaj> ochosi, Those folders are missing from the actual tarball.
[19:27] <ochosi> ali1234: nothing, which is why we're using it. before both were seeded (i think gthumb was originally installed because thunar didn't handle digital cameras well, i.e. before the port to gio)
[19:27] <ochosi> gio/gvfs
[19:27] <ochosi> Noskcaj: yes, i saw that
[19:27] <ali1234> ah, i see
[19:28] <Noskcaj> ochosi, lol@gthum's reason. It doesn
[19:28] <Noskcaj> 't even use cameras anymore
[19:28] <ali1234> that thunar crash seems to be the biggest crasher on the error tracker now btw
[19:28] <ochosi> yeah, our default app set hasn't received too many updates/reviews
[19:28] <ali1234> for core components anyway
[19:29] <ochosi> yeah, it's a rather frequently occuring (and annoying) bug
[19:29] <ali1234> i still can't reproduce it
[19:31] <ochosi> hmm
[19:31] <ochosi> can you give me that commandline again so i can start thunar like that every time now
[19:32] <ochosi> maybe i can get you some output
[19:32] <ochosi> or have you already gotten some debug stuff from someone else?
[19:33] <Noskcaj> ochosi, Is there anything else to sync from the artwork git before i attach this to a bug?
[19:34] <ochosi> yeah, i'll quickly pull in another update from github, one sec..
[19:36] <Noskcaj> ok. Do you want to make the  changelog entry or do you need me to?
[19:37] <ochosi> depends, do you want to add the packaging fix as well?
[19:37] <ochosi> for me the changelog only says "update icons" :)
[19:38] <ochosi> the complete changelog is only on github for the icons anyway, and there changelog=commitlog
[19:38] <ochosi> ok, just pushed rev260
[19:38] <Noskcaj> i mean d/changelog, and maybe just add "Repack tarball. LP: XXXXXX"
[19:40] <ochosi> ok, one sec
[19:41] <Noskcaj> ty
[19:41] <ochosi> ok, please check rev261
[19:42] <brainwash> ochosi: yes, my local branch and unity-greeter don't call exit()
[19:52] <ochosi> brainwash: ok, i'll push this as a patch then. thanks
[19:55] <ochosi> wonder whether the return false; is important
[19:57] <brainwash> void?
[19:58] <ochosi> brainwash: that's exactly what i'm wondering about :)
[19:58] <ochosi> should it be void
[20:00] <brainwash> I guess so
[20:02] <ali1234> the gtk_main_exit() patch?
[20:02] <ali1234> i would have thought that function was synchronous
[20:02] <ali1234> but maybe not
[20:05] <brainwash> test it
[20:07] <starrats> brainwash:  I got an answer back from the ubuntu-bug people and they said my problems were not a ubuntu bug report and I should have sent it to launchpad.
[20:08] <starrats> but I didn't have any problems as I mentioned earlier in the day, other than I have not restarted my laptop yet
[20:09] <starrats> other than to comp;lete the update/upgrade/dist-upgrade
[20:20] <ali1234> test it how?
[20:37] <Noskcaj> catfish, menulibre, and mugshot are all upload ready in debian now
[20:41] <starrats> brainwash:  just did a restart and all went fine but will have to do more of them before I know that all is good
[20:43] <brainwash> starrats: thanks for testing everything :)
[20:56] <starrats> you are welcome brainwash
[20:57] <starrats> and that includes my daily update/upgrade/dist-upgrade in the morning
[21:59] <ochosi> hey sergio-br2 
[22:00] <sergio-br2> hey ochosi, fine?
[22:00] <ochosi> yup, and you?
[22:01] <ochosi> just prepared another upload for the icon-theme today with Noskcaj, also to fix that bug you reported (thanks for catching that btw)
[22:02] <sergio-br2> fine thk
[22:04] <sergio-br2> it's a thing that made i think... how can it possible to do the package, missing some folders from git?
[22:05] <ochosi> no idea, you gotta ask Noskcaj :)
[22:05] <ochosi> but he fixed it i hope
[22:08] <sergio-br2> is there any hope to update from git again? before beta 2 or rc?
[22:08] <ochosi> depends on what we update
[22:09] <ochosi> the main problem is UI freeze
[22:11] <ochosi> what would you like to update?
[22:22] <sergio-br2> i think it is possible to complete the apps
[22:22] <sergio-br2> maybe
[22:22] <sergio-br2> and categories too. So if anyone change de sizes, it will not get ugly
[22:25] <ochosi> i think we might be able to sell those as bugfix
[22:26] <ochosi> just need to report a bug that they're displayed fuzzy
[22:26] <ochosi> but apps are a lot of work in all sizes
[22:26] <sergio-br2> ahh, i saw a problem today: xfce4-notes-plugin has icons in all apps folders, but it seems xfce is not using them. Whisker menu and desktop shorcuts get the old icon, without the pencil
[22:26] <ochosi> aha
[22:26] <ochosi> lemme take a quick look
[22:27] <sergio-br2> so, even if i resize in whisker to 128 px, it still uses the old
[22:28] <ochosi> yeah, that is odd
[22:28] <ochosi> the icon-name is correct though
[22:28] <ochosi> (in the desktop file)
[22:28] <sergio-br2> yeah
[22:29] <sergio-br2> i forgot where there is other icon like it, the older...
[22:29] <knome> ochosi, dashitis again? icon-name, really?
[22:29] <ochosi> knome: what's the problem with a bit of dash-itis, really?
[22:29] <knome> :P
[22:30] <knome> "a bit"
[22:30]  * knome goes looking at open merge proposals
[22:37] <brainwash> is the xflock4 part of bug 1291019 an issue?
[22:38] <brainwash> currently xflock4 prefers calling xscreensaver over light-locker, if both locker programs are installed
[22:47] <ochosi> well the upgrade from 13.10 or 12.04 should definitely remove xscreensaver
[22:47] <ochosi> so it shouldn't be a problem
[22:49] <ochosi> if the upgrade path can't be fixed i guess xflock should call light-locker first
[22:50] <brainwash> but calling -command also starts light-locker
[22:51] <brainwash> mmh, bug 1286954
[22:51] <brainwash> but xscreensaver is still present on the daily image
[22:51] <bluesabre> weird
[22:51] <bluesabre> is there anything else that depends on it?
[22:53] <brainwash> what about recommendations?
[22:53] <brainwash> do they get pulled in too?
[22:54] <Unit193> xfce4-session?
[22:54] <brainwash> maybe
[22:54] <Unit193> Yep.
[22:55] <brainwash> bluesabre: we ship gstreamer0.10-tools, should we also add the 1.0 version for mugshot webcam support?
[22:56] <bluesabre> brainwash: it may be listed as a depends in the new mugshot upload
[22:56] <bluesabre> I'll double-check
[22:56] <brainwash> oh, I didn't check yet
[22:57] <bluesabre> Unit193: so, patch time for xfce4-session
[22:57] <bluesabre> brainwash: the new mugshot hasn't been synced yet
[22:57] <Unit193> bluesabre: Could just lower it to Suggests.
[22:57] <brainwash> ok
[22:57] <bluesabre> it may not have hit debian exp yet
[22:57] <bluesabre> Unit193: which ones get pulled by default with the iso?
[22:57] <Unit193> Dep, rec.
[22:58] <bluesabre> ok
[22:58] <bluesabre> its already in suggests
[22:59] <bluesabre> brainwash: so removing exit() from the greeter resolves the issue?
[22:59] <brainwash> yes
[22:59] <bluesabre> great
[22:59] <bluesabre> I'll try to get a new release out tonight
[23:00] <brainwash> my local greeter branch is a bit different, so I did not notice this issue :/
[23:00] <ochosi> well at least it supposedly fixes the issue
[23:01] <ochosi> there hasn't been too much testing yet
[23:01] <ochosi> but it's certainly worth a shot
[23:03] <knome> anybody has anything i've promised to look at but haven't?
[23:03] <knome> i've merged the docs MP's and the slideshow MP
[23:04] <bluesabre> knome: nice :)
[23:05] <bluesabre> er... knice
[23:05] <knome> hah
[23:07] <knome> ochosi, did you have a clear image of which GTK3 indicators you wanted to seed/use by default?
[23:08] <Unit193> knome: Already added them. :/
[23:08] <knome> Unit193, oki, then we're good.
[23:08] <ochosi> yup, -power, -messages, -sound, -application
[23:09] <knome> ochosi, anything else to mention, or would that be okay for documentation on the blueprint whiteboard?
[23:09] <ochosi> i think it's oi
[23:09] <ochosi> ok
[23:09] <knome> bluesabre, you still targeting for packageset uploader rights this cycle?
[23:09] <ochosi> or what would you have in mind?
[23:09] <knome> just document what we are doing.
[23:10] <bluesabre> knome: this cycle is getting away from me quickly. I will make an attempt to get some progress on that soon
[23:10] <bluesabre> but pre-14.04 seems unlikely
[23:10] <knome> okay
[23:10] <knome> if you don't mind, i'll postpone that item then
[23:10] <knome> if it seems to progress a lot, feel free to change it back to something more appropriate.
[23:11] <bluesabre> sure thing
[23:11] <bluesabre> thanks knome
[23:11] <knome> ochosi, did we seed the community wallpapers already?
[23:11] <ochosi> yup
[23:11] <knome> marking as done
[23:11] <ochosi> at least i'm pretty sure they got pulled in yesterday
[23:11] <knome> okay
[23:12] <knome> note: seed vs. upload :)
[23:12] <knome> anything else than the wallpaper we need to be worrying about for UIF?
[23:12] <ochosi> well, they were uploaded ages ago
[23:12] <knome> sure sure
[23:12] <bluesabre> yeah, but are they listed in the xubuntu.trusty seed?
[23:12] <ochosi> well you know the -themes status quo
[23:13] <ochosi> other than that, i dunno
[23:13] <knome> pleia2, wiki.ubuntu.com/BuildingCommunity/SocialMedia
[23:13] <knome> pleia2, is that stuff done on your part?
[23:13] <pleia2> knome: still chatting with the lubuntu guy over email
[23:14] <knome> pleia2, okay
[23:14] <knome> pleia2, since you popped up, do you have 5-15 mins?
[23:14] <pleia2> no, I r teh busy
[23:14] <knome> boo
[23:14] <knome> well, just to point out what i wanted to get done:
[23:14] <knome>  [xubuntu-team] Extend website with "recommended system resources" -specs: INPROGRESS
[23:15] <knome> it's a semi-easy task
[23:15] <knome> except maybe discussing the actual recommendations, but other than that
[23:15] <knome> and i think it would be nice to get it up as a separate page so it could be shown on the frontpage
[23:15] <knome> also:
[23:15] <knome>  [lyz] Finish flyer development: INPROGRESS
[23:16] <knome> what do you consider that includes at this point?
[23:16] <pleia2> we tried to get people to help with system requirements, but it turned into a mess
[23:16] <pleia2> and I'll have a look at the flyer google doc soon, it's on my list
[23:17] <knome> sys.req: you should look at xubuntu.org drafted pages. there you see what i've been planning. whether the numbers were final or not, we should get that page up and remove the stuff from the download page
[23:17] <pleia2> ok
[23:18] <knome> flyer: i acknowledge that there are some "open" issues in the flyer content, but is there something *else* than the content and getting it squeezed in the template (and then creating a US letter sized too) that you think that work item includes?
[23:18] <knome> or maybe i should'be said "open" "issues
[23:18] <knome> "
[23:21] <pleia2> unable to parse
[23:23] <knome> haha
[23:23] <knome> okay:
[23:23] <knome> do we need to do something else than
[23:23] <knome> 1) finish the content
[23:24] <knome> 2) squeeze the content into A4 and US letter size PDF's?
[23:24] <pleia2> single sided?
[23:25] <pleia2> or does 2) just mean reformat existing proposal for both sizes?
[23:25] <knome> i would consider the other (single-sided, 4/page) formats as a stage 2 thing, which looks like it'll happen after T
[23:25] <pleia2> yeah
[23:25] <knome> well the proposal is for the three-fold version
[23:25]  * pleia2 nods
[23:25] <pleia2> so no, that's it
[23:25] <knome> okat
[23:25] <knome> *okay.
[23:25] <pleia2> and content is mostly good, just a little nitpicking, should be done soon
[23:25] <knome> yep..
[23:25] <pleia2> I'll try to do it on the train if gdocs cooperates
[23:26] <knome> wise words, nitpicking
[23:28] <pleia2> haha
[23:30] <knome> bluesabre, please assign bug 1284720 for yourself
[23:30] <bluesabre> good job ubottu!
[23:31] <knome> launchpad is slow too.
[23:33] <knome> ochosi, bluesabre, brainwash, ali1234, Noskcaj... please assign any of the bugs in https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-t-bugs to yourself if you are going to work on them
[23:35] <brainwash> change to "in progress" required too?
[23:35] <knome> brainwash, any bug status that's appropriate
[23:36] <brainwash> ok
[23:36] <knome> just want the assignees set to be able to track who did what on the work items tracker
[23:36] <knome> currently they are almost all assigned to xubuntu-team
[23:36] <knome> which is obviously wrong...
[23:36] <knome> but the best we can do for now
[23:36] <knome> this also let's us track how many bugs need assignees
[23:38] <ali1234> on of the bugs is a duplicate
[23:38] <ali1234> bug 1273687 should be bug 1203296
[23:39] <knome> fixed.
[23:39] <knome> no assignee, aww
[23:39] <knome> ;)
[23:39] <ali1234> just assigned myself
[23:39] <knome> thanks :)
[23:39]  * knome is happy
[23:39] <ali1234> the bookmarks one too
[23:39] <knome> waiting for the status site to update itself
[23:40] <knome> should see a better view of the actual process
[23:40] <knome> err, prgoress
[23:40] <knome> progress
[23:40] <ali1234> i have no idea how to fix the g_slice bug
[23:40] <knome> i see to be failing at typing today :)
[23:40] <ali1234> other than auditing every line of code
[23:40] <knome> *seem...
[23:40] <ali1234> i know how to fix the bookmarks though. just need to create the directory before creating the file inside it
[23:41] <knome> yep
[23:41] <knome> that's good
[23:41] <knome> fortunately we still have time
[23:42] <brainwash> ali1234: thunar segfault already reported upstream?
[23:42] <ali1234> yes, a couple of times
[23:42] <knome> jjfrv8, what's the status of the menulibre docs stuff?
[23:43] <brainwash> ali1234: a fix would be awesome, so we can stop the flood of lp reports :)
[23:44] <brainwash> speaking of flood.. the original report points to a torrent directory
[23:45] <brainwash> + dvdrip file