[11:11] <knome> ochosi, you probably knew, but abiword loooks a bit weird. the ruler is white on gray
[12:15] <astraljava> knome: Interesting, the Terminal help bug. Anyone on to that yet, or want me to?
[12:42] <knome> astraljava, if you wish to, free to take it
[12:50] <knome> btw, i didn't see any scrollbars-on-slideshow issues
[12:56] <astraljava> I think Len also reported them having vanished by now.
[13:08] <pleia2> knome: have a draft for the testing blog post in wordpress now, just working to add Charlie's notes
[13:08] <knome> pleia2, great :)
[13:08] <knome> pleia2, i tweeted about testing yday
[13:24] <pleia2> knome: ok, blog post is ready for review
[14:09] <pleia2> knome: heading out for the day for more venue visiting, feel free to publish if you think it looks good, otherwise we can talk about it later (tomorrow?)
[15:57] <knome> pleia2, published, and tweeted
[16:00] <knome> pleia2, we definitely need to review the wiki, and docs
[16:00] <knome> pleia2, i did some wiki cleanup yesterday, but there's a lot more to do
[16:01] <knome> pleia2, also, i've tweeted three times in the last 20h
[16:14] <astraljava> knome: That's a weird one, the terminal F1 bug. If you use the string it wants to use in exo-open directly, it works. I'm building a debug build now to investigate further.
[16:14] <knome> astraljava, have you tried to just remove the # ?
[16:15] <knome> astraljava, i mean, if it has something to do with parsing the url, that # is not needed anyway...
[16:15] <knome> astraljava, and parsing it what i think it very well might have to do about, looking at the error
[16:15] <knome> astraljava, btw, what's your schedule tomorrow/tue?
[16:15] <astraljava> knome: No, like I said, it works in exo-open _with_ the hash char.
[16:17] <astraljava> I'm coming to town late tomorrow, but then the interview is at 9 am. on Tuesday, no idea about the plans for the rest of the day before the flight, yet.
[16:17] <knome> astraljava, yes, i understand, but the terminal help is clearly having problems with the # :)
[16:17] <knome> i don't know why i'm highlighting, though
[16:17] <knome> maybe we should meet somewhere?
[16:18] <knome> it would do me good to get out, and wife would like me to get out too. :)
[16:18] <astraljava> knome: Hmm... that'd be strange if it did.
[16:18] <astraljava> Yeah sure, we can have lunch, maybe?
[16:18] <knome> astraljava, did you read the error?
[16:18] <knome> sure! where are you having the interview?
[16:18] <astraljava> Downtown.
[16:18] <knome> :| i know
[16:19] <knome> but more exactly where?
[16:19] <astraljava> Heheh. :) Annankatu something, next to Funky Burger.
[16:19] <knome> heh, right, you are thinking of grabbing something there? :P
[16:19] <astraljava> Not this time, we went there when I was in Helsinki the last time.
[16:19] <knome> ok
[16:20] <knome> haven't been there, so was it any good?
[16:20] <astraljava> It was alright. But quite expensive for my current situation.
[16:20] <knome> i see
[16:22] <knome> ah, so it's really close to the kamppi center
[16:22] <astraljava> Yeah.
[16:22] <knome> eerikin pippuri has some good kebab :)
[16:22] <astraljava> Yes it does.
[16:23] <astraljava> Lemme check the menu.
[16:23] <knome> well, it's just the normal stuff :)
[16:23] <knome> and sub-10€ too :)
[16:23] <knome> (which is the only way to go with kebab...)
[16:25]  * knome is not acting wisely
[16:25] <knome> the coffee doesn't really help with the headache
[16:26] <astraljava> Right, yeah that'll work.
[16:26] <astraljava> What time do you expect you'll be able to start digesting food?
[16:27] <knome> uah :)
[16:27] <knome> noon
[16:27] <knome> what time will you be free?
[16:28] <astraljava> I don't suppose it'll last longer than 1.5h or so.
[16:28] <astraljava> So noon will be fine.
[16:28] <knome> right, i missed the iv time
[16:29] <knome> well, i can get downtown earlier
[16:31] <astraljava> Sure. But then there's the thing which might emerge later, the place where I went to an interview on Friday might recall me back, she sounded really convinced.
[16:31] <astraljava> So let me get back to the schedule closer.
[16:31] <knome> aha
[16:31] <knome> okay
[17:41] <knome> astraljava, heh no, that list is just list for all pages we have. but look, how clean!
[17:43] <astraljava> gah! There's hundreds of 'em!!1one
[17:43] <knome> yeah.
[18:25] <astraljava> argh... frustrating. mr_pouit, micahg, madnick, somebody: How can I get debug information logged somewhere, _anywhere_, from an Xfce4 application? I have compiled with --enable-debug=yes, I use g_debug() to print out stuff, I pipe stdout and stderr into a file, and nothing appears.
[18:25] <knome> astraljava, have you asked #xfce-dev? ;]
[18:25] <astraljava> My google-fu fails me for a better process, so I'm stumped.
[18:26] <astraljava> knome: I haven't, so far.
[18:26] <knome> that's a good channel
[18:26] <knome> sometimes it's quiet, but not always ;)
[18:26] <astraljava> Alright, I'll try it next. Thanks!
[19:39] <ochosi> mr_pouit: had you noticed that xfburn is in accessories as well as multimedia? (shouldn't we remove it from the former?)
[19:39] <ochosi> hi everyone
[19:39] <astraljava> Hi Simon.
[19:40] <ochosi> hey astraljava
[19:40] <ochosi> astraljava: what up? (you calling me by my RN added so much gravitas to your greeting that i'm expecting something huge now :) )
[19:41] <ochosi> reboot, brb
[19:44] <astraljava> Hahaha. He fled! I WIN!! *evil cackle*
[19:47] <astraljava> *ahem*
[19:48] <astraljava> No, Simon. I do not intend you any harm. I'm just one of those who like to have a more personal "grasp" on people who I interact with on a regular basis. :)
[19:48] <astraljava> To me, there is no separation between IRL and IRC.
[19:58] <ochosi> :)
[19:59] <ochosi> yeah, well i guess people are different in that respect, but i don't mind if you don't make that separation
[20:00] <knome> ochosi, i just understood it yesterday we need to update our logo in the doc package.
[20:01] <knome> ochosi, it has the logo from over 2 years ago. to be exact, it has the old version of the old logo, which probably dates more than three years
[20:01] <ochosi> knome: ah :)
[20:01] <ochosi> where does that show up?
[20:01] <knome> ochosi, applications -> help
[20:02] <GridCube> file:///usr/share/xubuntu-docs/common/images/headerlogo.png
[20:02] <knome> i also understood we really need to update the docs as soon as possible, and get them uploaded to precise with SRU next july, if possible
[20:02] <GridCube> that link shoudl actually work :P
[20:02] <ochosi> uargh, true, we need to replace that logo
[20:03] <knome> and also, i understood that we should take many short sprints to do that - and i know how - etherpad
[20:03] <knome> paste a part of the documentation in a pad, get 5+ people to work on it and it's ready really soon.
[20:03] <knome> when it's done, paste another part
[20:04] <GridCube> >Copyright © 2009 Canonical Ltd.
[20:05] <ochosi> knome: this will be a busy week for me, not really sure i'll have time for docs
[20:05] <knome> GridCube, there is most probably parts that are more current, but yes, i think that's when most of the documentation is written
[20:05] <knome> ochosi, we can't do this for precise
[20:05] <knome> ochosi, we probably could squeeze in the english docs, but there would be absolutely no chance of getting the translations in
[20:05] <knome> ochosi, that's why i said "SRU in july"
[20:06] <ochosi> mhm, right, i'm a bit tired atm and not reading very closely ;)
[20:06] <knome> no problem
[20:06] <GridCube> knome, there are traduction engines for colaborative traductions
[20:06] <knome> traduction??
[20:07] <knome> right, translation
[20:07] <GridCube> oh
[20:07] <knome> no, that's not the issue
[20:07] <knome> time is
[20:07] <GridCube> mmm yes
[20:07] <knome> i know there are good tools, but that's not realistic
[20:07] <ochosi> i think for p+1 we should consider shipping the xfce docs
[20:07] <ochosi> they have greatly improved
[20:08] <knome> can't be realistic to get docs + translations done in one month, if the old docs date to more than 3 years.
[20:08] <ochosi> e.g. in form of a wiki-snapshot
[20:08] <knome> ochosi, sure, sounds good
[20:08] <ochosi> we could even do that now
[20:08] <knome> i suppose that's part of the work to be done
[20:08] <knome> ochosi, do they come with translations?
[20:08] <knome> anyway, i need to go for a while now
[20:09] <knome> see you soonish again if you're still up
[20:09] <knome> if not, good night
[20:09] <ochosi> mhm, see ya
[21:01] <knome> i'm back soon


[10:14] <mup> Issue operator#796 closed: Temper the chattiness of DEBUG logs <Created by marcoppenheimer> <Closed by PietroPasotti> <https://github.com/canonical/operator/issues/796>
[10:14] <mup> PR operator#797 closed: cleaned up logging output <Created by PietroPasotti> <Merged by PietroPasotti> <https://github.com/canonical/operator/pull/797>
[21:55] <mup> PR operator#800 opened: Added a very basic smoke test. Run it with `tox -e smoke` <Created by pengale> <https://github.com/canonical/operator/pull/800>


[00:05] <seb128> robert_ancell, hey
[00:08] <robert_ancell> seb128, hey
[00:09] <seb128> robert_ancell, how are you?
[00:09] <seb128> robert_ancell, thanks for the gdm email, I didn't have time to look at that today though :-(
[00:10] <seb128> robert_ancell, pitti said that setuid not working on script is by design
[00:10] <seb128> robert_ancell, and asked if we could make the server do the calls rather than adding a wrapper
[00:10] <robert_ancell> seb128, yeah, I know the feeling!
[00:10] <seb128> robert_ancell, since we already have the communication with the server and it has the priviledge required to change user
[00:10] <seb128> what do you think?
[00:11] <robert_ancell> seb128, the problem is the server is running as root, and we need to run as gdm.  We could get the server to run setuid gdm
[00:11] <robert_ancell> I mean we get the server to run that program I showed you basically
[00:11] <seb128> robert_ancell, well pitti said "seteuid(gdm); g_spawn_async(); seteuid(0)"
[00:12] <robert_ancell> seb128, sure.
[00:12] <robert_ancell> btw, I never knew a process had so many uids...
[00:12] <seb128> what do you mean?
[00:13] <robert_ancell> seb128, uid, effective uid, saved uid
[00:14] <seb128> ah, I didn't know that either
[00:15] <seb128> robert_ancell, anyway same as yesterday, if you do any work on that today drop me an email otherwise I will try to block some time for it again tomorrow
[00:15] <seb128> ;-)
[00:16] <robert_ancell> sure
[00:17] <seb128> thanks
[01:17] <RAOF> Oh, this is going to be a 64bitness issue, isn't it. :(
[01:18] <lifeless> isn't it always?
[01:19] <RAOF> No, not recently :)
[01:34] <chrisccoulson> kenvandine - how is bindwood meant to work? is it just meant to sync my bookmarks to couchdb automatically, or do i have to set something up? (i can't see any extra options in the firefox UI, and I don't see any bookmarks in couchdb either)
[01:45] <bryceh> heh, just finished going through all the bugs I have reported that are still open.  I found a quarter of them I could close as fixed but see I never got a response from anyone.  Dunno to be happy or sad.
[01:47] <RAOF> Ok.  Why is this perfectly valid pointer getting nulled before it hits the signal handler?
[01:51] <kenvandine> chrisccoulson, it just syncs
[01:51] <kenvandine> you should be able to enable/disable it in the ubuntuone-preferences
[01:51] <kenvandine> i think
[01:52] <chrisccoulson> ah, the checkbox in the preference is inactive and insensitive too
[01:52] <chrisccoulson> that's probably why it doesn't do anything
[01:53] <kenvandine> it is for me too
[01:53] <kenvandine> not sure what's up with that
[02:25] <Nafai> rickspencer3: Sorry I missed you earlier
[02:29] <rickspencer3> Nafai np
[02:29] <rickspencer3> turns out my issue was with my own stupidity
[02:29] <rickspencer3> which is what normally is the course of things around here ;)
[02:30] <Nafai> Know the feeling :)
[06:45] <pitti> Good morning
[06:45] <pitti> bryceh: intel 2.10> thanks, so it doesn't look overly important then? And I guess you want to keep UMS?
[06:46] <pitti> robert_ancell: uids> don't forget the fs uid :)
[06:47] <robert_ancell> pitti, I didn't dig deep enough to see that one! :)
[06:48] <pitti> robert_ancell: real and effective uid are the most interesting ones, usually; fs uid (file system access) is usually the same as euid
[06:49] <pitti> robert_ancell: and "saved" just means the one you can get back to
[06:49] <robert_ancell> pitti, what is the reason for all of them?  Why not just one UID?
[06:49] <pitti> robert_ancell: e. g. a root process can do setreuid(1000, 1000)
[06:49] <pitti> robert_ancell: but keeps '0' as saved uid, so that the process can do setreuid(0,0) later on
[06:49] <pitti> i. e. just as a flag that _this_ process can become root again, while a 'normal' uid 1000 process can't
[06:50] <robert_ancell> pitti, complex
[06:50] <pitti> robert_ancell: I don't know -- two would certainly be enough (the saved one is really just an implementation detail, you can't manipulate it directly)
[07:32] <RAOF> Ok, that's enough f-spot for the afternoon.
[07:36] <RAOF> pitti: Can I have a bit of an induction talk about bug flow in an hour or two?  I need to do the washing up now, but after that... :)
[07:36] <pitti> RAOF: yes, we can do that
[07:37] <RAOF> Thanks.
[07:37]  * RAOF -> washing up
[08:03] <didrocks> good morning
[08:39] <will__> anyone can help with my desktop
[08:42] <seb128> #ubuntu might
[08:42] <will__> seb can u help with nautilus
[08:43] <will__> and my desktop
[08:47] <seb128> no
[08:47] <seb128> try #ubuntu
[08:47] <seb128> this channel is not an user question one
[08:47] <will__> tried
[08:47] <will__> no luck
[08:48] <will__> dont suppose you know about nautilus scripts do you
[08:49] <seb128> no
[08:49] <seb128> again you are on the wrong channel
[08:49] <will__> ok well thanks
[08:54] <didrocks> seb128: hey, how are you?
[08:57] <seb128> didrocks, hey, just getting some coffeee
[08:57] <seb128> I will tell you afterward
[08:57] <seb128> but apparently good ;-)
[08:57] <seb128> you?
[08:57] <pitti> bonjour seb128
[08:57] <didrocks> coffee? good idea, doing same :)
[08:57] <seb128> hey pitti, how are you?
[08:57] <didrocks> seb128: yeah, I'm fine, thanks :)
[08:57] <pitti> seb128: I'm great! nothing lifts the mood like fixing a bug :)
[08:58] <seb128> pitti, fixing 2 bugs do! ;-)
[08:58] <didrocks> seb128: when you will get back from you coffee, you can sync gst-plugins-bad0.10 from debian unstable :)
[08:58] <seb128> didrocks, weird
[08:58] <pitti> seb128: I'm at it :) the next fix is already committed, working on bug #3 and #4 now :)
[08:58] <seb128> lol
[08:58] <didrocks> seb128: there was an added plugin which has been reverted, and the only -dev diff remaining (arch specific) has been removed in the new version
[08:59]  * pitti hugs ubottu
[08:59] <seb128> didrocks, don't we have changes because we move the farsight code to good for empathy?
[08:59] <seb128> didrocks, ie .install hacked to not installed those since they are in good now?
[08:59] <didrocks> seb128: oh, let me have a double check so, I should be wrong
[09:00] <seb128> didrocks, thanks
[09:01] <seb128> didrocks,
[09:01] <seb128> +debian/tmp/usr/lib/gstreamer-<EMAIL_ADDRESS>[09:01] <seb128> +debian/tmp/usr/lib/gstreamer-<EMAIL_ADDRESS>[09:01] <seb128> +debian/tmp/usr/lib/gstreamer-<EMAIL_ADDRESS>[09:01] <seb128> +debian/tmp/usr/lib/gstreamer-<EMAIL_ADDRESS>[09:01] <seb128> +debian/tmp/usr/lib/gstreamer-<EMAIL_ADDRESS>[09:01] <seb128> didrocks, that's the .good diff we have
[09:02] <didrocks> seb128: ok, my bad so, sorry. I tried with branches but I didn't saw the diff in .install files, only the dep things. Fixing it now
[09:05] <seb128> didrocks, np, thanks ;-)
[09:08] <seb128> pitti, btw we didn't really discuss the gst-ffmpeg issue the other day
[09:09] <seb128> pitti, you replied that you would prefer not having a copy but I'm not sure it was a real reply to the question considering the issue and options or just a "copying code sucks"
[09:09] <pitti> seb128: hm, I'm afraid I don't remember that at all -- what's the problem?
[09:10] <seb128> ok, so summary
[09:10] <seb128> gst-ffmpeg upstream says their code is neither tested nor meant to work with ffmpeg 0.5
[09:10] <seb128> which is the system version we have
[09:10] <seb128> so we are in a situation or we either
[09:11] <seb128> - use the system ffmpeg 0.5 for gst-ffmpeg , which will lead to quite some crashing situations
[09:11] <seb128> - switch gst-ffmpeg to use it's ffmpeg copy which is known to work
[09:12] <pitti> hm, I don't think we ever discussed that
[09:12] <pitti> seb128: which version does gst-ffmpeg work with?
[09:12] <pitti> this code is quite security sensitive, so code copies here would suck indeed
[09:12] <seb128> pitti, I pinged you but that's the day you were having for the morning
[09:12] <seb128> pitti, you did a quick "copies suck" reply when coming back
[09:12] <seb128> I was not sure if you read the discussion with siretart I had or not
[09:13] <pitti> seb128: do we need a newer ffmpeg for this or an older one?
[09:13] <pitti> I didn't, no
[09:13] <seb128> ok
[09:13] <seb128> newer or older I don't know
[09:13] <seb128> my guess would be older
[09:13] <seb128> they tend to play slow catching up on ffmpeg
[09:13] <pitti> so perhaps we should downgrade ffmpeg then?
[09:13] <pitti> or has this already been discussed?
[09:14] <seb128> that's not like gst-ffmpeg was the only ffmpeg user
[09:14] <seb128> no, I didn't think siretart would consider that a valid option
[09:14] <seb128> ffmpeg 0.5 is probably better and they just backported required changes for kde and other things I think
[09:15] <seb128> maybe we should move that to #ubuntu-devel and discuss it with siretart
[09:30] <pitti> seb128: ok, seems lucid is good wrt to that then?
[09:30] <seb128> pitti, as said on the other channel I'm confused
[09:31] <seb128> pitti, the discussion shifted to that security in ffmpeg one
[09:31] <pitti> right, but I thought we settled that lucid's gst-ffmpeg was patched to work with 0.5?
[09:31] <seb128> pitti, but what I understood the other day is that what we have for gst-ffmpeg is neither tested nor meant to work with the ffmpeg we have
[09:31] <seb128> and that upstream commends against using it
[09:32] <seb128> pitti, sirestart said he would come back to that after the security discussion, let's wait
[09:32] <istaz> seb128: I don't know if you have seen but new telepathy-butterfly has A/V disabled http://blog.staz.be/index.php?post/2010/03/10/Telepathy-butterrfly-0.5.5-released
[09:32] <seb128> istaz, no, I didn't, thanks, reading
[09:34] <seb128> istaz, ok, good to know, I will get those updates in lucid, thanks for the notice and the bug fixing work ;-)
[09:38] <istaz> np
[10:16] <chrisccoulson> hey RAOF - are you having any luck getting gjs built?
[10:21] <chrisccoulson> hey pitti - do you know whats going on with http://launchpadlibrarian.net/40773332/buildlog_ubuntu-lucid-armel.openjdk-6_6b18~pre2-1ubuntu1_FAILEDTOBUILD.txt.gz
[10:21] <chrisccoulson> all the armel builds in main pulling in xulrunner-1.9.2 are failing, like it's not been promoted to main yet
[10:21] <asac> chrisccoulson: xulrunner-1.9.2-dev is in universe
[10:21] <asac> ;)
[10:21] <asac> ah right
[10:21] <asac> its not promoted
[10:22] <asac> 11:18 < asac>  Filename: pool/universe/x/xulrunner-1.9.2/xulrunner-1.9.2-dev_1.9.2+nobinonly-0ubuntu1_armel.deb
[10:22] <pitti> chrisccoulson: hm, it is in main
[10:22] <chrisccoulson> asac - that only applies to armel does it?
[10:22] <asac> not sure. all i see its in universe pool here on armel ;)
[10:22] <asac> and it finished 2 days ago
[10:23] <asac> Binary only demotions to universe
[10:23] <asac>  ---------------------------------
[10:23] <asac> o xulrunner-1.9.2-gnome-support xulrunner-1.9.2-testsuite   {xulrunner-1.9.2}
[10:23] <asac> not sure if that has something to do with it
[10:29] <pitti> oh, indeed
[10:29] <pitti> xulrunner-1.9.2-dev | 1.9.2+nobinonly-0ubuntu1 |         lucid | amd64, i386, powerpc, sparc
[10:29] <pitti> xulrunner-1.9.2-dev | 1.9.2+nobinonly-0ubuntu1 | lucid/universe | armel
[10:29]  * pitti promotes
[10:29] <asac> \o/
[10:30] <pitti> asac, chrisccoulson: so, these can be retried in 90 mins
[10:30] <asac> does that take some time before we can retry failed builds?
[10:30] <asac> ah ok ;)
[10:30] <chrisccoulson> pitti - thanks
[10:30] <chrisccoulson> asac - will you be able to retry those? i can't retry builds in main, even for packages i can upload ;)
[10:31] <asac> heh
[10:31] <asac> chrisccoulson: you can upload packages to main?
[10:31] <chrisccoulson> asac - i can upload anything in the ubuntu-desktop package set
[10:31] <asac> ah
[10:31] <chrisccoulson> which includes some components in main
[10:32] <asac> yeah. so doko will retry. if you dont see that happening just ping me
[10:32] <asac> do you have more build failures spotted?
[10:34] <chrisccoulson> asac - it was only the armel ones so far
[10:36] <asac> chrisccoulson: yes, but which?
[10:36] <asac> all?
[10:36] <asac> i guess all in main ;)
[10:36] <chrisccoulson> asac - yelp, gnome-python-extras and couchdb
[10:37] <asac> right
[10:37] <asac> will retry those
[10:38] <chrisccoulson> thanks
[11:03] <asac> hmmm ... libindicate ftbfs across the board
[11:05] <seb128> asac, known issue with gir, should be fixed for today's weekly dx updates
[11:05] <RAOF> chrisccoulson: No luck so far.
[11:05] <RAOF> pitti: Is now a good time?
[11:05] <asac> super
[11:06] <chrisccoulson> RAOF - don't worry about it too much if it's getting late for you now
[11:06] <chrisccoulson> i'll probably set aside some time this afternoon to look at that if you like
[11:07] <RAOF> I'm happy to do it tomorrow, but I won't get to it tonight.
[11:11] <chrisccoulson> RAOF - no worries, thanks
[11:22] <pitti> RAOF: hi! yes, can do
[11:22] <pitti> RAOF: sorry for the lag, too much IRC this morning
[11:25] <seb128> pitti, same here
[11:25] <seb128> speaking of which lunch time
[11:25] <seb128> I've some shopping to do and grabbing something to eat on the way there
[11:26] <seb128> I'm away for a good hour at least
[11:26] <seb128> bbl
[11:26] <pitti> seb128: enjoy!
[11:26] <seb128> pitti, thanks, you too ;-)
[11:31] <didrocks> enjoy seb128 :)
[12:13] <sabdfl> who's the best person to talk with about adding http://www.ubuntugeek.com/ambiance-theme-for-google-chromechromium.html to the chromium package?
[12:16] <hyperair> what's the correct package for filing bugs about default keyboard shortcuts?
[12:20] <chrisccoulson> hyperair - it depends on which shortcut it is
[12:23] <hyperair> chrisccoulson: someone was complaining about control+alt+del
[12:23] <chrisccoulson> yeah, i just noticed
[12:23] <chrisccoulson> that currently reboots the machine doesn't it?
[12:23] <hyperair> i'm not sure what that does
[12:24] <hyperair> i think in X it doesn't do anything
[12:26] <framli> In Gnome, it opens a window for shutdown, reboot, logout.
[12:26] <chrisccoulson> right, and that makes more sense
[12:27] <hyperair> well i'll let you explain that then =p
[12:28] <chrisccoulson> hyperair, i just closed it with a comment
[12:28]  * hyperair claps
[12:31] <framli> I think that the recent complaint is about it being incoherent for users that are used to windows ctrl alt del. BTW, what does apple alt del does in OsX ?
[12:32]  * hyperair wonders
[13:15]  * Keybuk presses the Enter key happily
[13:16] <ogra> upload !
[13:16] <didrocks> +1 :)
[13:19] <Keybuk> I haven't even committed the changes yet
[13:19] <Keybuk> let alone sent them upstream
[13:19] <Keybuk> or merged them into our package
[13:19] <Keybuk> or fixed the packaging
[13:21] <Keybuk> and I actually need to check a patch that slangasek added too
[13:26] <asac> seb128: could you poke someone from evolution upstream to look at patch in gnome bug 585577 ?
[13:30] <asac> bryceh: i plan to upload something like: http://pastebin.com/M5i4tAGH ... so you are prepared
[13:30] <asac> if you prefer me to give you a debdiff or commit somewhere let me know
[13:32] <baptistemm> asac, hi, if you still look at bluez, I did 4.61 --> bug 534702
[13:33] <asac> baptistemm: can you attach a full upstream diff please?
[13:33] <asac> need to check fi we need a FFe
[13:35] <seb128> asac, ok
[13:35] <asac> gratias
[13:35] <seb128> np
[13:35] <asac> if they stay unresponsive we should include the patch i think to make fta a bit happier
[13:35] <asac> s/stay/are/
[13:38] <baptistemm> asac, full upstream diff ? you want a dediff ?
[13:38] <baptistemm> debdiff
[13:39] <asac> well. either full debdiff or upstream diff
[13:39] <baptistemm> k
[13:39] <asac> i want to check what upstream changes were done to figure if we need FFe
[13:39] <asac> i read the changelog
[13:39] <asac> want to check what that involves
[13:39] <asac> if its a one liner to "support X" then its fine
[13:39] <asac> if it adds considerable stuff we should check with release
[13:41] <baptistemm> too lame we had to defer 4.60
[13:41] <asac> yeah
[13:42] <asac> but lets first look ;)
[13:44] <pedro_> chrisccoulson, hello there, are you taking care of yelp ?
[13:44] <seb128> hey pedro_
[13:44] <pedro_> bonjour seb128!
[13:44] <seb128> pedro_, nobody is really on charge of that one, why?
[13:45] <baptistemm> hi pedro_
[13:45] <baptistemm> pedro_, what wh/j #ubuntu-bugs
[13:45] <pedro_> seb128, we're having a crash on exit , bug 535168
[13:45] <baptistemm> wooosp
[13:45] <pedro_> hello baptistemm!
[13:45] <seb128> pedro_, bug #528169
[13:45] <chrisccoulson> hi pedro_, i'm not really taking care of yelp
[13:45] <chrisccoulson> how come?
[13:45] <seb128> pedro_, reopen this one and dup, it was assigned to the canonical team
[13:45] <chrisccoulson> oh
[13:46] <seb128> pedro_, or if there is too many dups just assign the new one to canonical-desktop-team
[13:46] <seb128> with a comment saying it's the same issue
[13:46] <pedro_> seb128, sounds better i don't want to spam too many people, will do the last
[13:46] <pedro_> thanks folks
[13:46] <seb128> thanks
[13:46] <seb128> pedro_, how are you otherwise?
[13:47] <pedro_> seb128, good good , trying to catching up with everything post holidays/earthquake , thanks for asking
[13:47] <pedro_> seb128, how's everything there ? are you still having snow?
[13:48] <seb128> things are good there
[13:48] <seb128> no snow anymore no
[13:48] <seb128> at least not in this part of the country
[13:48] <seb128> the south had some still some days ago
[13:48] <seb128> not sure if they are done with it now
[13:48] <didrocks> seb128: not yet from last news
[13:48] <didrocks> hey pedro_ o/
[13:49] <seb128> it's quite sunny there in fact
[13:49] <seb128> but still cold, and windy
[13:49] <pedro_> bonjour didrocks!
[13:49] <didrocks> same in Paris, some sun for once \o/
[13:49] <chrisccoulson> we've got some sun here too, which is quite unusual!
[13:49] <pedro_> sunny and cold hehe that's weird ;-)
[13:50] <chrisccoulson> pedro_ - can you recreate the yelp crash easily?
[13:51] <pedro_> chrisccoulson, yup, i'm able to reproduce it every time
[13:51] <chrisccoulson> pedro_ - before anybody gets a change to look at it, it might be worth getting a xtrace log
[13:51] <chrisccoulson> have you used xtrace before?
[13:53] <pedro_> chrisccoulson, yeah for getting other logs, is something like xtrace -D:9 -d:0 -k 2>&1 | tee ~/xtrace.log  ; enough for the crash there?
[13:53] <chrisccoulson> pedro_ - yeah, that's fine. it might be helpful when somebody comes to look at the bug
[13:53] <seb128> chrisccoulson, don't bother too much about this one right now, it's on the canonical list we will pick on it later
[13:53] <pedro_> chrisccoulson, ok , i'll attach the log shortly
[13:54] <chrisccoulson> thanks
[13:54] <chrisccoulson> seb128 - yeah, i wasn't intending to spend any time looking at that today
[13:54] <seb128> ok, good
[13:55] <pedro_> chrisccoulson, xtrace log added
[13:56] <chrisccoulson> pedro_, thanks
[13:56] <pedro_> thank you ;-)
[14:14] <chrisccoulson> wow, xorg locked up quite hard there
[14:23] <pitti> does anyone use anjuta here?
[14:24] <seb128> pitti, I try it every now and then but not regularly, why?
[14:24] <pitti> we need somebody to test it with gdb 7.1
[14:24] <tedg> pitti: I think that MacSlow does.
[14:24] <pitti> just to see whether it generally still works
[14:24] <pitti> tedg: thanks
[14:25] <pitti> MacSlow: do you fancy trying anjuta with a new gdb version? we need to know if it still generally works (there's a PPA for it)
[14:29] <MacSlow> pitti, yeah I do
[14:30] <MacSlow> pitti, I can do it... but I have to do a test/branch upload first... and a phone-conf in about 30 min.
[14:30] <pitti> MacSlow: not that urgent; the PPA is described in bug 535179, it would be great if you could just followup there?
[14:30] <MacSlow> pitti, but if you hand me the link to the PPA I can give anjuta/gdb 7.1 a try later this afternoon... if that good enough for you
[14:30] <MacSlow> pitti, ok
[14:31] <pitti> MacSlow: *hug*, thanks
[14:31] <MacSlow> pitti, is' doch klar :)
[14:31] <LaserJock> didrocks: beta1 freeze is today?
[14:33] <didrocks> LaserJock: right, I was preparing the new releases of each components
[14:34] <LaserJock> didrocks: how close are you for netbook-launcer?
[14:35] <ogra> pitti, hey ho
[14:35]  * pitti waves to ogra
[14:35] <ogra> pitti, there is bug 517300 i'D like to talk to you about based on https://blueprints.launchpad.net/ubuntu/+spec/desktop-lucid-likewise-open-migration this seems to be desktop land now
[14:36] <ogra> pitti, so it seems the desktop team is responsible for it now, we have a patch but there is copyright assignment etc involved that should be handled centrally by the team/person who is responsible
[14:37] <pitti> ogra: hm, that doesn't sound like something that we can do for lucid, though
[14:37] <didrocks> LaserJock: I'm merging and testing right to left support and then, I'll release in something like 2 hours, I guess, why?
[14:37] <pitti> ogra: oh, you mean to get it upstream?
[14:38] <LaserJock> didrocks: I was going to sit down to work on bug #455143
[14:38] <ogra> pitti, hmm ? its fixed and all, its just upstream conversation thats missing ... we're even happy to help testing in the mobile team (since nobody else has HW) we just want to ghave the right people as drivers on it
[14:38] <pitti> ogra: ah, I'm happy to ping upstream about that one
[14:38] <didrocks> LaserJock: I've targetted it for beta1 as an opportunity, if you have something working, we can merge it until Monday I would say
[14:38] <ogra> pitti, so can i move it from server team to desktop team ? (the bug i mean)
[14:39] <ogra> pitti, if testing is required, Gruemaster has an AD setup and ARM boards to help testing
[14:39] <pitti> ogra: okay (but might get moved to b2)
[14:39] <NCommander> pitti: upstream been pinged and we even got the copyright assignment stuff done. what we lack is someone who knows how to properly use it :-)
[14:39] <LaserJock> didrocks: ok, I just didn't want to mess you up by not having it ready
[14:39] <pitti> NCommander: use what? likewise-open?
[14:39] <LaserJock> didrocks: but I had a lot of work and real life stuff come up
[14:40] <ogra> pitti, not urgent, but the mobile team has a commitment that we clear mian FTBFS until release for ARM
[14:40] <pitti> no idea about how to set it up, etc., I'm afraid; nobody in the desktop team has ever touched it
[14:40] <ogra> *main
[14:40] <didrocks> LaserJock: no, even if it doesn't make it for beta 1, it's not a big deal, I would say. It's just a nice to have feature. No pb, daily work first :-)
[14:40] <didrocks> LaserJock: thanks for working on that ;)
[14:41] <LaserJock> didrocks: it's fine as long as I'm not blocking you or making you miss targets
[14:41] <LaserJock> so I'll keep plugging away
[14:41] <didrocks> LaserJock: sure, thanks ;)
[14:42] <pitti> ogra, NCommander: so, to understand the status of this, what's blocking the upload?
[14:42] <ogra> pitti, upstream approval and testing
[14:42] <pitti> ogra: ok, I see
[14:43] <pitti> looks harmless enough, anyway
[14:44] <ogra> pitti, but i wonder if we can even keep it in main if nobody ever tested it through lucid
[14:44] <ogra> how are we supporting that for 3 years ?
[14:44] <pitti> ogra: upstream tested it
[14:44] <pitti> (isntalls, upgrades, etc.)
[14:46] <pitti> ogra: I'm not sure; it got MIRed by the server team, and then abandoned
[14:46] <pitti> (bug 201537 )
[14:46] <ogra> hmm
[14:46] <pitti> so we might eventually demote it back, yes
[14:47] <ogra> ++
[14:47] <ogra> that doesnt sound like a good package for an LTS
[14:47] <pitti> rickspencer3: ^ do you know whether we have any commercial commitment to likewise-open to keep it in main?
[14:48] <rickspencer3> pitti, I'm not sure
[14:48] <rickspencer3> what is the problem?
[14:48]  * rickspencer3 reads up
[14:48] <pitti> rickspencer3: it was originally MIRed by server team, then abandoned, and now nobody is responsible for it any more
[14:48] <rickspencer3> oh
[14:48] <pitti> but still in main
[14:48] <rickspencer3> can we "be responsible" for it?
[14:48] <ogra> https://blueprints.launchpad.net/ubuntu/+spec/desktop-lucid-likewise-open-migration
[14:49] <LaserJock> didrocks: I need like a UML or mindmap of netbook-launcer, it's really not clear where things are sometimes
[14:49] <ogra> rickspencer3, ^^^ according to that you are :)
[14:49] <rickspencer3> ogra, ack
[14:49] <ogra> rickspencer3, but it doesnt really feel like a package for an LTS if nobody in the teams tests or uses it
[14:49] <pitti> rickspencer3: if we get someone who has time and hard/software to deal with it, sure :)
[14:49] <rickspencer3> pitti, oh fudge
[14:49] <pitti> rickspencer3: I just know that nobody in the desktop team ever touched it so far
[14:49] <rickspencer3> I was really expecting the Likewise guys to be more involved
[14:50] <rickspencer3> let me jiggle the handle on it
[14:50] <pitti> rickspencer3: well, we don't have an immediate problem with it
[14:50] <pitti> rickspencer3: we have that arm patch, which looks very reasonable; I can ping Garry to review/apply it
[14:50] <pitti> and I'm sure that will go well
[14:50]  * ogra would like to get bug 517300 off the mobile team sholders though
[14:50] <pitti> rickspencer3: I was just interested in a more long-term setup
[14:50] <didrocks> LaserJock: right, and there is none TBH :) I'm mostly grepping the code to find where to put things. From what I saw, favorite view is not the same than other apps views (and folder view is separated as well)
[14:50] <rickspencer3> pitti, right
[14:51] <rickspencer3> my expectation was that the LW team would be a bit more involved
[14:51] <rickspencer3> I am following up now
[14:51] <seb128> hey ric
[14:51] <seb128> hey rickspencer3
[14:51] <rickspencer3> hi seb128
[14:51] <pitti> rickspencer3: ok, so the expectation is that they'll support it themselves; that's fair enough
[14:52] <pitti> rickspencer3: I just wondered about the current state/arrangement
[14:52] <rickspencer3> pitti,  me too
[14:52] <LaserJock> didrocks: yeah, I'm confused about how each of the non-standard categories are treated seperately
[14:52] <rickspencer3> I totally forgot about it after you guys got it into main
[14:52] <LaserJock> didrocks: I wonder if it would be worth some time post-Lucid to do some documentation work (at least comments in the code) for it
[14:52] <LaserJock> just to make contribution easier in the future
[14:53] <didrocks> LaserJock: let's wait lucid to be out first, and we can see that together after if you want :-)
[14:54] <seb128> kenvandine, hey
[14:55] <kenvandine> hey seb128
[14:55] <seb128> kenvandine, how are you?
[14:56] <kenvandine> tired :) and you?
[14:56] <seb128> a bit tried but good otherwise ;-)
[14:56] <seb128> kenvandine, how busy are you today?
[14:56] <kenvandine> very this morning... but then i should be ok
[14:56] <seb128> kenvandine, can we default back to you for dx updates?
[14:56] <kenvandine> i am finishing up the exception handling stuff in gwibber
[14:56] <kenvandine> sure
[14:56] <kenvandine> i can handle it
[14:57] <seb128> kenvandine, ok, let's see I will handle some of those on the way if that's just "merge and upload" for ted and let you the other one for later?
[14:57] <seb128> for -> from
[14:57] <kenvandine> sure
[14:57] <seb128> good, thanks
[14:57] <kenvandine> thx
[14:57] <seb128> let me know if it turns out you are too busy or if you need sponsoring
[14:58] <kenvandine> i know i will need some sponsoring
[14:58] <kenvandine> about half of the DX packages don't have perms for ~ubuntu-desktop
[14:58] <kenvandine> we'll let cjwatson worry about fixing that for next cycle :)
[15:00] <seb128> kenvandine, ok, so let's say I will do updates which are just merges from ted, since that's about as much work to do sponsoring for him or you ;-)
[15:00] <kenvandine> ok :)
[15:01] <seb128> kenvandine, I will ping you to let if there is some you should look at
[15:01] <kenvandine> thx
[15:50] <seb128> bryceh, rickspencer3: do you have any way to build a list of bugs with a lucid task for a group of packages or for members of a team in launchpad?
[15:51] <rickspencer3> seb128, kind of
[15:51] <rickspencer3> in bughugger there is a "bugs for packages query"
[15:51] <rickspencer3> and then you can filter by "release contains lucid"
[15:52] <chrisccoulson> seb128 - the old keyboard applet was provided by libgnomekbd wasn't it?
[15:52] <rickspencer3> unfortunately, it's all a bit fubar right now because the query calculates gravity, which takes forever, so the queries are a bit useless atm
[15:52] <rickspencer3> however, I could tinker with it later today if that could help you
[15:52] <rickspencer3> seb128, ^
[15:53] <rickspencer3> so you want to pick a package, and get all bug tasks that are on Lucid?
[15:53] <seb128> chrisccoulson, yes
[15:54] <chrisccoulson> seb128 - i wonder if we should create a null keyboard applet in gnome-applets, like we do with the mixer-applet etc
[15:54] <chrisccoulson> as gnome-panel shows an error after upgrading now we removed it
[15:54] <seb128> chrisccoulson, we should, I think that was the case
[15:54] <seb128> rickspencer3, so, not really
[15:55] <seb128> rickspencer3, I went through all dx indicators sources buglists in launchpad yesterday and cleaned things and added lucid tasks
[15:55] <rickspencer3> seb128, I'm saying I could make that query work for you pretty easily
[15:55] <rickspencer3> just need to comment out some code and test it out
[15:55] <seb128> rickspencer3, now I've a group of some sources packages I care a bugs, with lucid tasks assigned to canonical-dx-team, ted, bratsche, ronoc and dbart
[15:56] <seb128> rickspencer3, and I would like a way to say "give me all lucid ask on indicator-*" on a page
[15:56] <rickspencer3> seb128, yes, I can do that with bughugger
[15:56] <seb128> lucid *t*asks
[15:56] <rickspencer3> I've been meaning to fix this, but haven't had the motivation since bdmurray came out with bryce's json searches
[15:56] <seb128> rickspencer3, ok, I will try a bit later and see if I can get it working or ping you if I don't
[15:56] <rickspencer3> seb128, and if you want, you can ask bdmurray to run that as a chron job every 24 hours too
[15:56] <seb128> rickspencer3, well I'm fine setting a json search too if that's the way to go
[15:57] <seb128> so let's say I've this indicator group I care about
[15:57] <rickspencer3> the nice thing about a json search is it is at your fingertips
[15:57] <seb128> ie "libdbusmenu indicator-applet indicator-session"
[15:57] <rickspencer3> the bad thing is that it only runs once per day
[15:57] <rickspencer3> ah
[15:57] <seb128> and I want daily bug counts and lucid tasks
[15:57] <rickspencer3> that you have to hack around a tiny bit
[15:57] <seb128> can we track those in some clever way?
[15:57]  * LaserJock corsses fingers and hits killall netbook-launcher
[15:58] <rickspencer3> create a lp user, subscribe that user to each package you care about, and then do a "bugs on packages this user is subscribed to" search
[15:58] <rickspencer3> seb128, but we could hard code something up for you if you need to do it several times a day
[15:58] <seb128> doing that was next on my list on how to get that working
[15:58] <rickspencer3> if only once per day, ask bdmurray to make a json search for you
[15:58] <seb128> but I don't like much adding random lp users
[15:58] <seb128> rickspencer3, well what you recommend doing?
[15:59] <rickspencer3> seb128, ask bdmurray to make a json search for you
[16:03] <seb128> rickspencer3, ok, will do that
[16:03] <rickspencer3> thanks seb128
[16:03] <seb128> np
[16:31] <LaserJock> didrocks: should this work for testing: LD_PRELOAD=/usr/local/lib/libnetbook-launcher.so.0 /usr/local/bin/netbook-launcher
[16:33] <didrocks> LaserJock: seems correct to me
[16:37] <NCommander> ccheney: ping. I need you to throw an OOo patch into ooo-build, can you help me so we can close the bug on OOo being broken on ARM?
[16:40]  * pitti says good night for today, I'll go out tonight for a magic show
[16:41] <pitti> just finishing the day with a 3-bug-fix jockey upload
[16:41] <Nafai> good night pitti
[16:42] <ccheney> NCommander: if you just need to test a build you can stick the patch into the hotfixes directory
[16:42] <NCommander> ccheney: no, ready for merging to close a bug in LP :-)
[16:42] <NCommander> I already built it :-)
[16:43] <ccheney> ok where is the patch i can add it to ooo-build upstream
[16:43] <seb128> 'night pitti
[16:44] <didrocks> good evening pitti
[16:44] <NCommander> ccheney: http://pastebin.ubuntu.com/393376/
[16:44] <NCommander> ccheney: the filename is off, it has to edit bridges/sources/cpp_uno/gcc3_linux_arm
[16:46] <ccheney> NCommander: will that apply as is (no whitespace corruption)?
[16:46] <ccheney> may be better to email the patch :)
[16:46] <ccheney> also should this be part of another larger patch or by itself?
[16:46] <NCommander> just this
[16:47] <ccheney> wow looks like it preserved tabs :)
[16:50] <didrocks> LaserJock: hum, I don't see the fullname for empathy with your liblauncher patch
[16:50] <NCommander> ccheney: heh :-)
[16:50] <asac> the patch itself has some indentation issues looking at the paste ;)
[16:51] <didrocks> LaserJock: oh my bad, it's only on the favorites view
[16:52] <LaserJock> didrocks: phew
[16:52] <didrocks> (that we don't get it)
[16:52] <didrocks> hum, another thing to fix, we'll see later :)
[16:53] <didrocks> LaserJock: yeah, I was really surprised ;)
[16:54] <rickspencer3> pitti, ogra fyi, I pinged likewise team, will let you know what happens
[16:54] <ogra> thanks
[16:55] <ogra> rickspencer3, can you probably point them to bug 517300 too ?
[16:55] <rickspencer3> ogra, will do
[16:55] <ogra> thanks a lot !
[16:55] <ogra> :)
[16:55]  * rickspencer3 subscribes coffeedude
[16:56] <rickspencer3> actually, I assigned him ;)
[16:59] <NCommander> ccheney: once you commit it to ooo-build, I'd be glad to look at it and make sure everything is right before the next OOo upload
[17:01] <LaserJock> didrocks: grr, I just can't seem to figure out what draws the tile container
[17:01] <LaserJock> didrocks: I tried netbook-launcer/nl-content-view.c but that didn't seem to work
[17:02] <didrocks> LaserJock: yes, it's not really obvious (that's why I only had a 5 minutes look yesterday morning), njpatel, can you guide us for that ? ^
[17:02] <njpatel> LaserJock, didrocks: what draws each icon + label?
[17:03] <didrocks> njpatel: the idea is to find where to plug the "right click event"
[17:03] <njpatel> didrocks, sure, but you mean the application icon and the application label right? Or the category icon and label?
[17:03] <didrocks> njpatel: it's more the container that is interesting
[17:03] <njpatel> didrocks, what do you want to do?
[17:04] <LaserJock> we want to extend the "Change Desktop" menu seen in Favorites to the rest of the menu
[17:04] <njpatel> ah
[17:04] <didrocks> njpatel: showing the "change background" menu option when you don't click on an icon, but on the underlaying container
[17:04] <LaserJock> s/menu/right-click menu/
[17:05] <njpatel> one sec
[17:08] <didrocks> njpatel: the code to add is quite obvious as it's already on the favorite panel. The issue is just "on what object do we plug the signal" :)
[17:08] <njpatel> LaserJock, I'd have a look to see if netbook-launcher/nl-content-view is eating the right-click event or netbook-launcher/nl-scroll-view
[17:08] <njpatel> LaserJock, otherwise adding the right-click code to nl-content-view should make it work across the board
[17:09] <LaserJock> njpatel: ok, I tried adding a button_press_event to nl-content-view and it never made it
[17:09] <njpatel> LaserJock, you'd have to make sure the content view is set to be "reactive" (clutter_actor_set_reactive), otherwise it won't receive events
[17:10] <didrocks> oh, clutter_actor_set_reactive, didn't know that one ^^
[17:10] <LaserJock> ah, ok, that's good to know :-) let me check
[17:10] <didrocks> I tried already, but without that :)
[17:11] <LaserJock> njpatel: ok, I see that nl-content-view doesn't have that, I'll add it
[17:13] <LaserJock> njpatel: \o/
[17:14] <LaserJock> didrocks: ok, that seems to work just fine in all menus
[17:15] <didrocks> LaserJock: sweet! :)
[17:15] <njpatel> sweet
[17:15] <LaserJock> njpatel: I was digging through code most of the morning trying to figure that out, thanks
[17:16] <didrocks> njpatel: thanks dude for the hint, won't have find it without you :)
[17:16] <njpatel> yeah, it's an odd properly of the way clutter works, though it speeds up the event propagation
[17:16] <njpatel> didrocks,  :0
[17:16] <njpatel> er, :), even!
[17:19] <didrocks> 15 UNE related bug closed in 4 uploads, /me feels way better on UNE state now :-)
[17:20] <kwwii> anyone seen bug #537374 ?
[17:21] <seb128> kwwii, not me
[17:22] <seb128> kwwii, oh, reading the description, wait I try
[17:22] <kwwii> seb128: I can confirm that it causes problems, I wonder if this is reason enough to turn it off
[17:22] <kwwii> essentially, you can arrow down beyond the visible menu
[17:23] <seb128> kwwii, right I confirm
[17:23] <seb128> kwwii, check with bratsche if he thinks that's fixable for lucid or if he can bring it upstream, look at it
[17:24] <seb128> kwwii, if he's too busy let's turn it off
[17:24] <kwwii> seb128: right, will do...thanks
[17:25] <seb128> kwwii, np
[17:25] <ccheney> NCommander: ok will get it committed now, any preference for name of the patch?
[17:26] <ccheney> NCommander: i'm not completely sure what the change in asm does :)
[17:27] <ogra> ccheney, it saves our butts ... so call it saves_our_butts.patch
[17:29] <ccheney> lol, usually something relating to what the patch does is good, not sure what that patch does myself :)
[17:30] <ccheney> finally-works-this-time.patch ;-)
[17:31] <ogra> ccheney,  branch_directly_to_cpp_vtable_call_on_arm.patch might work
[17:32] <ccheney> ogra: ok thanks that sounds helpful to someone who knows arm :)
[17:32] <NCommander> ccheney: <dmart> NCommander: How about "privateSnippetExtractor simplification to avoid exception unwind failures and stack corruption risk" ?
[17:32] <ogra> right, that would be a proper description
[17:32] <ccheney> NCommander: yes that is useful too since i have to add a description for my git commit :)
[17:33] <ccheney> thanks guys!
[17:33] <chrisccoulson> seb128 - bug 537286 is because there is the panel doesn't tell xsplash it is loaded, giving the perception that the login time is really long
[17:33] <chrisccoulson> we can probably close that for lucid
[17:34] <chrisccoulson> sorry, i meant to say "there is no panel"
[17:34] <chrisccoulson> that makes more sense ;)
[17:34] <seb128> chrisccoulson, oh, I didn't even got that it was not a bug about lucid ;-)
[17:34] <chrisccoulson> yeah, that's karmic
[17:34] <seb128> chrisccoulson, thanks for noticing, please close it
[17:34] <chrisccoulson> anyway, i will close that as fixed
[17:34] <chrisccoulson> thanks
[17:49] <bryceh> seb128, I did start making a query a couple weekends ago for getting bugs with lucid tasks for packages belonging to a team but haven't quite finished it yet.  It's high on my todo list though.
[17:50] <seb128> bryceh, ok, let me know if you get it working, thanks ;-)
[17:51] <njpatel> bryceh, a quick question, is there any plans to re-sync with xorg again before lucid release? The reason I ask is that there seems to be an issue in libdrm2, causing crashes when closing OpenGL windows (which I've seen more of with the latest stable Clutter)
[17:52] <njpatel> basically this crash: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567677
[17:53] <bryceh> njpatel, we have plans to merge xserver 1.7.6 when it's released
[17:54] <bryceh> njpatel, do you know for certain this bug is fixed in 1.7.6?
[17:55] <njpatel> bryceh, not for certain, but it seems like there was a commit that made the freeing of the resources in the dri2.c (which is where this happens), cleaner
[17:56] <njpatel> bryceh, are there any packages available that I can test, which would have git Xorg? Otherwise I'll try and compile xorg git over the weekend
[17:56] <bryceh> check xorg-edgers, it usually has git snapshots
[17:56] <bryceh> beyond that if there is a specific patch you would like to test let me know, I can roll a ppa for you
[17:57] <njpatel> bryceh, okay, will do again (it seemed to have a older version than lucid a couple of days ago)
[17:57] <bryceh> in any case, please file a bug in launchpad against xorg-server for this and subscribe me, so we can track the issue through solution
[17:57] <njpatel> sure, will do -- thanks bryceh
[17:58] <tjaalton> we'll also get mesa 7.7.1
[17:58] <tjaalton> well, if it's accepted
[18:06] <LaserJock> didrocks: sorry for taking so long (work break ;-) ), I put up a proposed merge
[18:07] <didrocks> LaserJock: sweet! I'll either make a release for beta1, or just land it afterwards
[18:07] <didrocks> LaserJock: work break :-) I had that with my previous employer too. I can happen at any time :p
[18:10] <LaserJock> didrocks: so I managed to fix 4 bugs, I'm impressed. I'm generally a packager and not a coder
[18:10] <didrocks> LaserJock: heh, congrats!
[18:11] <didrocks> LaserJock: and thanks again for your work on UNE, it helps a lot :-)
[18:12] <LaserJock> didrocks: so wow, it looks like we got all but 1 of the beta-1 targets done
[18:13] <didrocks> LaserJock: right. I was afraid to have been to optimistic when doing the list, but apparently, it was ok :-)
[18:14] <didrocks> LaserJock: the favorite view is quite special as it's not the same than the others one. That's why I didn't have the time to investigate to see why keys aren't handled
[18:14] <LaserJock> so what happens between beta1 and beta2 bug-wise
[18:16] <didrocks> LaserJock: I would say we should just fix all remaining ones :-)
[18:17] <didrocks> LaserJock: if we find some too difficult, it's no so important and we can discare as the "first to fix" list was for beta1 IMHO
[18:17] <seb128> time for sport and dinner
[18:17] <seb128> bbl
[18:18] <didrocks> see you seb128
[18:19] <seb128> didrocks, see you didrocks
[21:10] <ccheney> NCommander: got it committed to ooo-build git
[21:14] <didrocks> going to bed, have a good night everyone :)
[21:14] <ogra> ccheney, do you plan an upload before beta1 ?
[21:14] <seb128> "night didrocks
[21:15] <ccheney> ogra: i'm still working on the epiphany stuff and b1 freeze is today (aiui) so probably not
[21:15] <ogra> ok
[21:15] <didrocks> good night seb128!
[21:16] <ccheney> ogra: the next upload i was planning was a 3.2.0 upstream one but that also changes over to the new deb format v3 so i have to determine what that does to my packaging work, probably will take a day to get it merged up and building properly
[21:16] <ccheney> i was hoping to be done with this epiphany stuff by now but it keeps pulling in more and more functions, ugh
[21:16] <ccheney> probably 10x more symbols than initially showed up to be able to actually build it on hardy :-\
[21:32] <RAOF> Morning all.
[21:32] <RAOF> Good evening didrocks :)
[21:34] <RAOF> didrocks: Re: bug #514083 - thanks for the pointer to trunk.  My next step there is to fix it in bzr and submit a merge request against upstream, which we'll pull in to the distro packages, right?
[21:43] <LaserJock> RAOF: I think so yes, at least that's the way he seems to be going with it and that's what I've done.
[21:43] <bryceh> heya RAOF
[21:43] <RAOF> bryceh: Good morning.
[21:43] <RAOF> LaserJock: Thanks.
[21:45] <NCommander> ccheney: is ther esomething I can to do to help make an upload happen sooner rather than later? We *really* need this fixed in archive
[21:57] <seb128> hey robert_ancell
[21:57] <robert_ancell> seb128, hey hey
[21:58] <seb128> robert_ancell, thanks for the gdm work
[21:58] <seb128> robert_ancell, I'm a bit ashamed to say I didn't do anything with it yet though, but I will in a bit or tomorrow for sure
[21:59] <robert_ancell> seb128, no problem. I didn't do the gdmserver bit because I'm still not 100% sure what the right way of doing it is...
[22:00] <ccheney> NCommander: if you want to just fix it for the current version in the archive adding it to the hotfixes directory and uploading will probably work as is
[22:00] <ccheney> i'll either be doing an upload this weekend (if i finish my epiphany work) or after beta release next thursday, due to the time it takes to build i am generally requested to not upload past monday of a release week
[22:01] <ccheney> and with the freeze today its up to slangasek if he would even accept it anyway
[22:01] <seb128> robert_ancell, did you have a look to what those guys who contacted you some time ago are doing?
[22:03] <robert_ancell> seb128, the gdmsetup2 guys? they just run gconftool-2 as root
[22:03] <seb128> robert_ancell, bah, they just basically call gconftool --set
[22:03] <seb128> robert_ancell, sudo -u gdm gconftool in fact
[22:04] <seb128> robert_ancell, I can't see a clean way to do that
[22:05] <seb128> robert_ancell, calling dbus-launch gconftool-2 --set after changing uid to the gdm user?
[22:05] <seb128> I really hate suggesting that :p
[22:06] <ccheney> ugh another class needs copying in (/me hates backporting glib/gtk crap)
[22:06] <robert_ancell> seb128, that's what I was thinking... (note you also have the clear the environment otherwise it might contact the wrong gconf)
[22:06] <ccheney> every class relies on more classes that aren't in the old version, etc :-\
[22:07] <seb128> robert_ancell, want to hack that today if you have a chance?
[22:07] <robert_ancell> seb128, I'll have a look if I have time.  You can review and sponsor it tomorrow then :)
[22:07] <seb128> robert_ancell, I still have gtk, telepathy-butterfly and some dx updates to look at tonight
[22:07] <chrisccoulson> what sections do i need to put in xorg.conf to create a minimal configuration to force my laptop to use the vesa driver?
[22:07] <seb128> robert_ancell, yeah, I will do that without fault
[22:08] <chrisccoulson> there's no xorg.conf at all now, and i don't have a template
[22:08] <seb128> robert_ancell, I'm trying to get updates cleaned today before beta freeze, will be easier to get bug fixes than updates after that
[22:08] <robert_ancell> seb128, sure, this is a UI change though, don't know if that means we should rush it
[22:09] <seb128> we will rush it tomorrow
[22:09] <seb128> ;-)
[22:09] <NCommander> ccheney: well, it can wait for beta 2 if need be, but if you can kick me a source package, I'd love to shove it in a PPA for testing purposes
[22:09] <seb128> well it's after freeze but I think we will find people understanding the need so it should be alright tomorrow
[22:10] <seb128> robert_ancell, I was pondering pushing the UI without the server code today, so we just could claim the remaining work as bug fix :p
[22:10] <ccheney> NCommander: all you would need to do to make it work would be to add the patch you sent me to ooo-build/patches/hotfixes and rebuild with a new version number
[22:10] <robert_ancell> seb128, LOL
[22:10] <ccheney> NCommander: my internet access is pretty slow so it takes quite a while for me to upload anything
[22:10] <NCommander> ccheney: petal faster? :-)
[22:10] <ccheney> NCommander: anything being multi hundred mb openoffice.org files anyway :)
[22:11] <NCommander> ccheney: heh. I don't envy your job
[22:12] <ccheney> the best i can get currently is 1mbps up, used to be on 384kbps up
[22:13]  * ccheney applied to the google fiber in your community thing, would be nice to get real broadband
[22:17]  * bryceh gives ccheney a box of pigeons
[22:18] <NCommander> ccheney: where yo ulive?
[22:18] <ccheney> NCommander: near houston
[22:18] <NCommander> ccheney: ah
[22:19] <ccheney> at my old house i was about 800ft from being close enough for att uverse, heh
[22:19]  * NCommander starts the Better Upload Speeds for OOo Devs Fund
[22:19] <ccheney> the new place has comcast but they don't even have docsis 3 yet
[22:19] <NCommander> ccheney: actually, I have faster upstreams on my cell phone ;.;
[22:19] <ccheney> att 3g here is about 1000/128
[22:19] <ccheney> so even slower :)
[22:20] <ccheney> up near boston their 3g is actually decent
[22:21] <ccheney> hmm the phone company here seems to be rolling out 20/? for $85/mo
[22:21] <ccheney> not sure what the upstream speed is
[22:23] <ccheney> comcast has 20mbps burst not sure what the real speed is though, 20mbps burst isn't that useful for Ooo
[22:28] <chrisccoulson> seb128 - do you have the same firefox slowness issue as didrocks?
[22:29] <seb128> chrisccoulson, not really
[22:29] <seb128> or not right now
[22:29] <chrisccoulson> oh, he mentioned that you were seeing the issue too
[22:29] <seb128> I had firefox hanging for some seconds on tabs switches being launchpad pages yesterday
[22:29] <seb128> but it's not doing it today
[22:29] <chrisccoulson> so, it's just didrocks then ;)
[22:34] <seb128> seems so
[22:34] <seb128> or at least today :p
[22:37] <LaserJock> I don't know how you can deal with super-long words in grids other than to widen the grid, any ideas?
[22:53] <chrisccoulson> grrrrr, my filesystem has gone read only again :-/
[22:53] <seb128> chrisccoulson, disks issues?
[22:54] <chrisccoulson> seb128 - it does it every couple of days, and then i have to manually run fsck from a live CD
[22:54] <seb128> not nice
[22:55] <chrisccoulson> yeah, it's a bit of a pain
[22:55] <chrisccoulson> right, bbiab, i'd better restart and recover it again
[23:10] <ccheney> i had that happen to me also yesterday, my wife shut down my system and it came up needing to be manually fsck'd, it was shut down properly though so it seemed a bit odd
[23:10] <ccheney> it didn't go read only while running though
[23:11] <ccheney> at least not to my knowledge
[23:11] <chrisccoulson> ccheney, you're having issues too?
[23:12] <chrisccoulson> my kern.log is full of sata errors
[23:12] <ccheney> chrisccoulson: i'm not sure what happened
[23:13] <ccheney> chrisccoulson: i don't show any sata errors and it didn't seem to go read only while running, but required manual fsck on reboot
[23:13] <ccheney> if it happens again i'll have to look into it closer
[23:15] <ccheney> i thought she had just hit the power switch but she actually shut my system down properly but it the fs wasn't cleanly unmounted for some reason
[23:15] <ccheney> s/it//
[23:16] <chrisccoulson> i get lots of errors leading to things like this:
[23:16] <chrisccoulson> ata2: hard resetting link
[23:16] <chrisccoulson> and it seems to mess up the filesystem if it happens at the wrong time
[23:19] <RAOF> chrisccoulson: I think I see something like that coming out of suspend sometimes.
[23:20] <chrisccoulson> RAOF - yeah, this is much worse after suspend too
[23:21] <RAOF> Argh.  Bzr, just fix the rich-root mess, please!
[23:22] <Nafai> RAOF: I ran into that this morning too
[23:33] <ccheney> down to 6 undefined symbols now :)
[23:33] <ccheney> hopefully 2 of those (new class) don't pull in a bucketload more
[23:47] <ccheney> looks like those two pull in quite a bit of other stuff in the same class, but hopefully no other classes :)


[08:37] <tjaalton> got green light to update llvm-3.2 for mesa, so I'll upload it in a bit
[11:00] <ogra_> tjaalton, https://bugs.launchpad.net/ubuntu-nexus7/+bug/1068994/comments/24
[11:00] <tjaalton> ogra_: ooh, excellent
[11:01] <ogra_> yeah, raster did some debugging :)
[11:05] <tjaalton> I'll add some of it to the upstream bug and ping whot
[11:05] <ogra_> great
[11:49] <mlankhorst> morning
[12:03] <tjaalton> mlankhorst: push your changes to xorg-server, infinity added some which I'd like to commit there
[12:04] <tjaalton> audit is now in main \o/
[12:47] <mlankhorst>   ah
[12:48] <mlankhorst> tjaalton: I have none to xorg-server atm?
[12:48] <tjaalton> who released 1.13.2?
[12:48] <mlankhorst> oh I did, but I think it's on the ubuntu branch already
[12:48] <jcristau> marcoz is supposed to handle 1.13.x
[12:49] <jcristau> ah.  in ubuntu, not upstream.  oops :)
[12:49] <tjaalton> yeah :)
[12:49] <mlankhorst> hm I don't know if I committed the release to raring changelog though *checks*
[12:49] <tjaalton> mlankhorst: still unreleased
[12:49] <tjaalton> ah
[12:49] <tjaalton> that would explain it then
[12:49] <mlankhorst> I guess I never did
[12:50] <mlankhorst> ah well I'll do so now
[12:50] <tjaalton> cool
[12:51] <mlankhorst> and seems adconrad did a -0ubuntu2 on top of it
[12:52] <tjaalton> right,
[12:52] <tjaalton> -,
[12:53] <tjaalton> I was merging that when I noticed -0u1 wasn't committed
[12:55] <mlankhorst> ok pushed
[12:55] <tjaalton> thx
[12:56] <tjaalton> oh you pushed infinity's change too, nice
[12:56] <mlankhorst> did you test the mesa 9.1 package? :)
[12:58] <tjaalton> I didn't but Sarvatt did
[12:58] <tjaalton> on some hw
[12:58] <tjaalton> hum, might give it a go now
[12:58] <mlankhorst> it should work probably
[13:10] <mlankhorst> ah well, piglit try #2 on i915
[13:30] <mlankhorst> looks like the varying packing causes it to hang hard :(
[13:47] <jcristau> anybody knows what CVE-2013-1591 is about?
[13:47] <jcristau> also wtf is pale moon?
[13:50] <tjaalton> "A custom-built and optimized Firefox-based browser for Windows." *shudder*
[14:31] <mdeslaur> jcristau: this seems to be the only difference in pale moon: http://cgit.freedesktop.org/pixman/commit/?id=de60e2e0e3eb6084f8f14b63f25b3cbfb012943f
[14:33] <jcristau> thanks
[15:10] <mlankhorst> oh finally
[15:10] <mlankhorst> mesa 9.0.2 on my intel mbp has 11 tests fixed, no regressions
[15:11] <tjaalton> cool
[15:11] <tjaalton> updating -intel again
[15:15] <mlankhorst> so I guess it's time to upload
[15:56] <mlankhorst> tjaalton: hey can you sponsor mesa for me? seems i cant upload to quantal
[16:20] <tjaalton> mlankhorst: sure, later :)
[16:42] <mlankhorst> oh seems i should be able to upload now
[16:45] <bjsnider> tjaalton, any issues with intl on raring right now?
[16:45] <bjsnider> had a snb user last night in the other channel who couldn't load it after doing a clean install of the latest image
[17:05] <mlankhorst> tjaalton: nm quantal has xorg package set now :)
[17:17] <tjaalton> bjsnider: it has worked very well for me on snb, make sure to file a bug and ickle will react :)
[17:18] <tjaalton> upgraded my ivb desktop today, blissful there too
[17:19] <tjaalton> i965 with mesa 9.1 seems oddly sluggish with the dash though
[17:35] <Sarvatt> ricotz: doing mesa as soon as this llvm builds
[17:36] <ricotz> Sarvatt, oh, i just pushed llvm
[17:36] <Sarvatt> lol
[17:37] <Sarvatt> https://launchpad.net/~xorg-edgers/+archive/ppa/+builds?build_text=&build_state=all
[17:37] <ricotz> Sarvatt, why are you pushing it to raring?
[17:37] <ricotz> and an older version too
[17:37] <Sarvatt> r600 backend isn't in raring's llvm-3.2
[17:38] <ricotz> Sarvatt, ok, but the raring build will make no difference
[17:38] <ricotz>  llvm-3.2 - 3.2-2ubuntu2.1~edgers1 (Newer version available)
[17:38] <Sarvatt> oh argghhh
[17:38] <Sarvatt> https://lists.ubuntu.com/archives/raring-changes/2013-January/date.html
[17:38] <Sarvatt> spot the problem? i was looking on that :)
[17:38]  * Sarvatt forgot to update the bookmark this month
[17:39] <ricotz> Sarvatt, i see either way i pushed 3.2-2ubuntu3~
[17:39] <ricotz> will cancel the other builds then
[17:40] <Sarvatt> https://launchpad.net/~canonical-x/+archive/x-staging wasn't saying llvm-3.2 in raring was newer when i started the source download an hour ago (10kbps from the ppa ftw..)
[17:40] <ricotz> lol ;)
[17:41] <ricotz> i guess we had the same idea then
[17:41] <ricotz> wanted to look at mesa too
[17:41] <ricotz> Sarvatt, a drm update would be nice
[17:41] <ricotz> first
[17:42] <Sarvatt> sure thing, doing that now
[17:43] <ricotz> Sarvatt, thanks
[17:43] <ricotz> Sarvatt, feel free to push xserver 1.14 to raring too
[17:44] <ricotz> ;)
[17:44] <tjaalton> Sarvatt: llvm in raring has it now
[17:45] <tjaalton> maybe not made it out of proposed yet
[17:45] <Sarvatt> tjaalton: yeah pushed an hour ago and i started looking at updating it in the ppa earlier :)
[18:18] <fm> how can i get further with https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1116587 ?
[18:25] <bryce> fm, you're right - nothing in your Xorg.0.log or dmesg.  And if there's no i915_error_state file then it's sounding like it's not "just" a GPU lockup or xserver crash
[18:25] <bryce> even possible it's not X locking up
[18:26] <fm> bryce, so what could i do to narrow that down?
[18:26] <bryce> fm, check .xsession-errors, /var/crash for any .crash files, and /var/log/syslog
[18:26] <fm> quite annoying to have a system crash every 10 minutes
[18:26] <bryce> fm, is it exactly regular 10 min, or just more or less?
[18:27] <fm> no apport popping up at reboot so no .crash, and syslog empty as well
[18:27] <fm> bryce, no just more or less
[18:27] <bryce> fm, can you trace to when that first started and what you did leading up to it?  or has it been like that since install?
[18:27] <fm> i think it does not happen when idle ;)
[18:28] <fm> bryce, happens since running 13.04, was not there with 12.10
[18:28] <fm> right now i am on 2.21.2 or so
[18:28] <bryce> fm, and it started right after upgrading?
[18:28] <fm> there was an xorg-intel-drv update just today
[18:28] <fm> bryce, yes happend right after upgrading
[18:31] <bryce> fm, hmm well no idea what's wrong, but can throw out some advice for tracking it down more
[18:31] <bryce> fm, I haven't run across reports quite like this, that sound like a GPU lockup but don't have evidence in the logs
[18:32] <bryce> fm, so something must be a bit unique about your system.  So you might doubly think about anything you've installed  or done that other people wouldn't have done.  or anything unusual about the hardware that others might not have.
[18:33] <bryce> fm, fwiw, until just recently, this cycle for 13.04 we haven't changed much on X compared with 12.10, aside from targeted bug fixes.  Same xserver, drivers, etc.
[18:34] <bryce> fm, so issues that crop up on upgrade to 13.04 that didn't happen in 12.10, we often suggest looking first at the kernel or other things, before X, which did receive big bumps.
[18:34] <bryce> so, like try installing and booting the quantal kernel, and see if you can rule that out
[18:34] <fm> will look at .xsession-errors next time, haven't looked there
[18:35] <bryce> fm, or try turning off splash in the kernel config to rule in/out plymouth
[18:35] <bryce> yeah anything unusual in .xsession-errors would be interesting
[18:35] <fm> ok, will try an old kernel
[18:35] <bryce> and ssh in while it's frozen and look for any files changed in /var/log/*
[18:35] <fm> what is the best way to get it?
[18:36] <fm> bryce, yeah, can just go to ctrl-alt-1
[18:36] <bryce> fm, think you can download the .deb off launchpad.  kernel has no dependencies so pretty much grab from whereever's convenient.
[18:37] <bryce> oho, if you can vt switch, that suggests not a gpu lockup
[18:37] <bryce> fm, have you been able to just `sudo service lightdm restart` to get it working again?  Or does it require a full reboot?
[18:38] <bryce> fm, ok gotta go work on some other stuff, but good luck.  If you can copy some of the stuff we discussed onto the bug, it'll help fill in whomever looks at it next.
[18:39] <fm> bryce, will try lightdm restart
[19:06] <mlankhorst> hey
[19:15] <bryce> mlankhorst, hi
[19:56] <mlankhorst> ok seems mesa 9.0.2 works for me
[20:01] <mlankhorst> so I uploaded mesa-lts-quantal 9.0.2 too now :)


[11:26] <schopin> When downgrading a Recommends to a Suggests, will the suggested package be removed on upgrades?
[11:32] <schopin> Do we have a way to mark a LP bug as something that needs Release Notes mention?
[12:30] <adrien> hey, is there anyone moderating ubuntu-devel-discuss@ ? it would be great to validate my mails :)   (I sent one and I'll send another one in a couple minutes)
[12:34] <adrien> (now :) )
[12:35] <adrien> also, would an @canonical.com mail address help? migrating away from gmail and switching back to @canonical.com once I have sieve set up is one of my new year's resolution
[12:42] <tsimonq2> schopin: Recommends to Suggests> Not explicitly removed, no. Might be marked for autoremoval. juliank would know for sure.
[12:43] <tsimonq2> schopin: I believe there is an LP project for Ubuntu release notes; let me double check that and grab you a linl.
[12:43] <tsimonq2> https://bugs.launchpad.net/ubuntu-release-notes
[12:43] <tsimonq2> I've seen that used recently.
[12:44] <juliank> schopin: downgrades to Suggests are removed by ubuntu-release-upgrader; but not by the normal apt policy (u-r-u overrides the policy to not consider suggests important)
[12:44] <tsimonq2> adrien: You'd have to look at the list administrator page to see. ;) I would imagine @canonical.com would help
[12:44] <juliank> schopin: I picked this as a compromise, because suggested packages enhance software you have installed, hence you may have gotten used to them being around and removing them in the release would break your workflow
[12:45] <jbicha> juliank: is that the same behavior on Debian?
[12:45] <jbicha> (except for the lack of a release upgrader)
[12:46] <juliank> yeah, so Debian never gets suggests removed :D
[12:51] <schopin> juliank: tsimonq2: thanks for the info.
[17:41] <bdmurray> schopin: there is an ubuntu-release-notes project so you can add a bug task for that.
[17:42] <bdmurray> ah tsimonq2 mentioned it also


[06:21] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Kinetic Final] has been disabled
[07:25] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Kinetic Final] has been updated (20221020)
[11:45] <mparillo> Looks like KK will be re-spun. My reading makes it sound as if you have a DKMS module and Secure Boot, you would make a great tester for the re-spin. Off-topic: RMS's and Linus's original instincts on Secure Boot sound more and more correct to me.
[11:46] <arraybolt3> Can confirm, people with a DKMS module and Secure Boot would be great for testing here.
 I see no changes regarding dkms and secure boot
[12:27] <RikMills> might have regressed in a previous release and escaped notice
[12:28]  * RikMills shrugs
[13:16] <BluesKaj> Hi all
 Backport? (re @RikMills: building 5.26.1 :))
 Yes (re @myfenris: Backport?)
 👌🏻👍
 It is now in backports PPA for kinetic
[14:22] <fenris[m]> In progress...
 so far so good ... nothing broke
[15:21] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Kinetic Final] has been marked as ready
[17:10] <sgmoore[m]> https://www.scarlettgatelymoore.dev/kde-gear-snaps-round-2/
[18:55] <mparillo> https://ubuntu.com/blog/canonical-releases-ubuntu-22-10-kinetic-kudu
[18:56] <mparillo> http://cdimage.ubuntu.com/kubuntu/releases/22.10/release/
[18:57] <RikMills> yeah, the blog post went too early apparently
[18:58] <RikMills> but we must be good to go
[19:00] <mparillo> Thanks for your edits on the News Post. I clicked Publish, so, depending on WordPress, the News article will be live in seconds, minutes, or hours.
[19:01] <RikMills> I have updated the download/alternate pages. same wait
[19:17] <RikMills> posted on Reddit
[19:19] <clivejo> ^^Jammy
[19:20] <RikMills> clivejo: no, kinetic
[19:20] <clivejo> topic says jammy :P
[19:21] <RikMills> https://i.imgur.com/0Nyz4Be.png
[19:21] <RikMills> ohhhh
 https://irc-attachments.kde.org/efca04f2/file_60835_tgs.webp
[19:22] <RikMills> clivejo: done]
[19:22] <clivejo> better :P


[10:13] <Jordan_U> cjae_, So just to make sure, the computer doesn't boot right now, correct?
[10:14] <Jordan_U> Or rather Ubuntu doesn't boot correctly
[10:14] <cjae_> Jordan_U, no boots fine
[10:14] <cjae_> just seeing fail messges during reboot that want to clear up
[10:15] <cjae_> want to know the differences between the two quiets in menu.lst
[10:16] <cjae_> I see I failed during reboot and tried to see what it is in line with and think it was firestarter
[10:16] <Jordan_U> cjae_, Oh, you can ignore my comment on chrooting then, what two quiets?
[10:17] <cjae_> there is a quiet in kernel boot options by splash
[10:17] <cjae_> and there is a quiet under or above initrd
[10:18] <cjae_> the fail messages is why I wanted rid of the dumb splash screens
[10:19] <cjae_> does removing splash also remove the reboot splash screen?
[10:19] <Jordan_U> Yes
[10:19] <Jordan_U> I don't have any quiet option for my initrd line and I have never seen one before
[10:19] <cjae_> I am using xubuntu
[10:20] <cjae_> sorry might be specific to that
[10:20] <cjae_> that channel is basically dead
[10:20] <Jordan_U> I can't see how it would be
[10:20] <cjae_> while quiet at least
[10:21] <Jordan_U> cjae_, removing splash should let you see any errors at boot, does it?
[10:22] <cjae_> my menu.lst goes downward title, root, kernel, quiet, initrd
[10:23] <cjae_> like column direction
[10:23] <cjae_> yes was just wondering if it is true for term/rebooting
[10:24] <Jordan_U> I am not sure what you are asking
[10:25] <cjae_> You know how there is splash at boot and one at shutdown?
[10:25] <cjae_> I want to know if removing splash removes one at shutdown
[10:26] <Jordan_U> Yes, it does
[10:26] <cjae_> ok maybe then I may see the fail messages properly is there a way to find this out without rebooting?
[10:27] <cjae_> I tried dmesg|tail
[10:28] <Jordan_U> cjae_, I am not sure
[10:29] <cjae_> hey you know where I can find help about QoS
[10:31] <cjae_> on a router with ddwrt
[10:34] <Jordan_U> Not off hand


[00:23] <rharper> smoser: s/ENI/etc\/network\/interfaces (ENI)
[00:26] <smoser> rharper, ?
[00:27] <rharper> smoser: re your network config writeup
[00:27] <smoser> just shorten you mean ?
[00:27] <rharper> I mean expand it first
[00:27] <rharper> and indicate in parens you are shortening
[00:27] <rharper> cloud-init writes out /etc/network/interfaces (ENI) ...
[00:27] <rharper> I assume this is for documentation or for our consumption only (review) ?
[00:28] <smoser> http://paste.ubuntu.com/15420393/
[00:28] <smoser> i might throw it itno a google doc for easier comment
[00:28] <rharper> yeah
[00:28] <rharper> please
[00:28] <smoser> much of it is description that was in my head and as i worked through things.
[00:28] <rharper> yep
[00:28] <smoser> i think its actually reasonably stable at this point.
[00:31] <smoser> rharper, i'll do that before end of weekend.
[00:31] <smoser> and will schedule  something early monday to hangout
[00:31] <smoser> magicalChicken, leave your availability here.
[00:32] <smoser> others here playing along, i'll go ahead and make it public google doc so that you could read and comment if interested.
[00:32] <smoser> as i know harlowja_at_home in his PTL billiance almost has my converter done
[00:32] <rharper> smoser: I'll miss monday morning, I've a 9AM dr. appt, but after lunch Monday would be fine
[00:33] <rharper> smoser: PTL, what's PTL? =)
[00:36] <smoser> project technical lead.
[00:36] <smoser> rharper, ok. tell me when you can. i want as early as i can
[00:37] <rharper> smoser: I _know_ what PTL is, just like you did  earlier with harlowja_at_home
[00:37] <rharper> smoser: ok, I'll ping you  as soon as I'm back, I could probably make 10 AM central, 10:15 if I'm late.
[00:41] <smoser> k. gracias
[00:49] <smoser> magicalChicken, send me email if you dont want to leave that at home.
[00:49] <smoser> rharper, ah. saw your joke
[00:49]  * smoser turns to pumpkin. good night all
[01:13] <harlowja_at_home> lol
[18:27] <magicalChicken> smoser: Hey, sorry I saw this pretty late, I'm available anytime monday morning