[03:25] <mako> greetings
[03:25] <Treenaks> hi mako
[03:26] <ogra> hey mako
[03:34] <mako> there is a non-zero chance i might miss the meeting tonight
[03:34] <mako> i'm at LSM.. it's unclear what if the place where i can get net will be open
[04:00] <Seveas> too bad
[04:00] <Seveas> If you know the time you'll be there, we could change them meeting time I suppose...
[06:20] <JanC> changing meeting time less than 24h before is a problem for many people...
[06:24] <ogra> TB does that all the time though ;)
[06:27] <Kamion> I'm likely to be out of touch from about half an hour from now until the time of the meeting
[06:27] <Kamion> so I'll need to know soon
[10:15] <Mez> evening seth
[10:17] <mdke> /j #get-e
[10:17] <mdke> pah
[10:18] <mdke> weird there isn't even a space there
 perhaps?
[10:27] <seth_k> afternoon Mez
[10:27] <Mez> evening Seth
[11:50] <Seveas> 10 minutes to liftoff
[11:51] <Seveas> Let's get the pre-party started
[11:51] <mako> looks like i'll make it after all
[11:51] <seth_k> so we're having a pre-pre-party?
[11:51] <tseng> mako++
[11:51] <mako> there is a cool hacker squat in dijon that is open
[11:51] <Seveas> welcome mako :)
[11:52] <mako> they have "apt-get install anarchism" painted on the top of the building
[11:52] <Seveas> lol :)
[11:52] <ogra> mako, so how is france ? you just left germany before the wather got really odd
[11:53] <Seveas> Here's for all cell phine addicts: http://www.firebox.com/index.html?dir=firebox&action=product&pid=1044
[11:53] <mako> http://garlicviolence.org/irl/drkvg-tanneries-aptget_install_anarchism.jpg
[11:53] <Seveas> phone*
[11:54] <bddebian> Hey no URLs, I'm on my Hurd box.. :-(
[11:54] <mako> they have a box of ubuntu CDs up :)
[11:54] <Seveas> :)
[11:54] <mako> of course! :)
[11:54] <Seveas> nice picture
[11:55] <ogra> mako, cool
[11:55] <\sh> g'evening gentlemen
[11:55] <bddebian> Heya \sh
[11:55] <Seveas> g'evening \sh
[11:55] <Seveas> :)
[11:55] <Seveas> about talks: Ubuntu-nl has been invited to talk at software freedom day NL
[11:56] <mako> Kamion: around?
[11:56] <\sh> mako: your proposal for your clubclothes :) ++10 from me ;)
[11:56] <Seveas> mako, is it possible to get an extra box of ubuntu cd's for that day?
[11:56] <silbs> mako: Kamion might be on a train. He was in London today.
[11:56] <Seveas> \sh, clubclothes as in Ubuntu t-shirts?
[11:56] <ogra> hey silbs
[11:57] <Seveas> +10 from me too then :)
[11:57] <\sh> seveas: read makos proposal :)
[11:57] <silbs> hi ogra
[11:57] <mdke> hi guys
[11:57] <ogra> :)
[11:57] <Seveas> \sh, where?
[11:57] <\sh> planet
[11:57] <Seveas> ah
[11:57] <mako> does anyone know where elmo is?
[11:57] <mdke> he hasn't been in #ubuntu-devel for a while
[11:57] <sabdfl> hi guys
[11:58] <tseng> hi mark.
[11:58] <Seveas> hi sabdfl
[11:58] <Mez> mdke: Kamion = on train :D
[11:58] <\sh> hey mark
[11:58] <Mez> mako = @ conference
[11:58] <mdke> Mez, i didn't ask, but ok
[11:58] <sabdfl> mako's made it
[11:58] <mdke> hopefully they'll get here :)
[11:58] <Mez> mdke, again - I confused you and mako ;)
[11:58] <mdke> ahh
 I'm likely to be out of touch from about half an hour from now until the time of the meeting
[11:58] <mdke> thought so
[11:59] <ogra> that was 16:26 UTC
[11:59] <mdke> hey sabdfl
[11:59] <kinjoo> hi guys
[11:59] <Seveas> hi kinjoo
[12:00] <mdke>  /nick mdke_not_to_be_confused_with_mako_or_mdz
[12:00] <Seveas> :D
[12:00] <Mez> no I just confuse you with mako :D
[12:00] <Mez> I see the m and the k in the same place ;)
[12:00] <sabdfl> i'll sms elmo quickly
[12:00] <Seveas> m[^a] k[^o]
[12:00] <Seveas> or md[^z]
[12:01] <mako> (and beer)
[12:01] <Seveas> good thinking, beer
[12:01] <ogra> :)
[12:01] <ogra> hey hno73 :)
[12:01] <Mez> ooh beer :D
[12:01] <hno73> ogra: hey :)
[12:01] <mdke> hey hno73!
[12:01] <mako> so, we still waiting for kamion or elmo?
[12:01] <hno73> hello mdke!
[12:02] <ogra> mako, yeps
[12:02] <Mez> lol- I think I may go my own fridge :D
[12:02] <sabdfl> just sms'd elmo, let's get cracking
[12:02] <sabdfl> mako: do you want to handle the member candidates first?
[12:03] <ogra> call up their names to make sure they are here ?
[12:03] <Mez> dont we usually give names firsT?


[00:29] <hajour> hi all
[00:43] <erkan^> Good night hajour (-:
[00:43] <hajour> goodnight erkan^ :)
[00:44] <erkan^> how are you?
[00:48] <hajour> still recovering
[00:48] <hajour> and how are you erkan^
[00:48] <hajour> ?
[00:50] <erkan^> I am good, i am being with Google Picasa
[00:50] <erkan^> are you ill, hajour ?
[00:50] <hajour> i had a big epileptic attack in night i think
[00:51] <hajour> i got muscle pain everywhere and i was really tired
[00:51] <erkan^> ow
[00:51] <erkan^> doe aan rusten, aub
[00:52] <hajour> yes i will do easy
[00:52] <hajour> i will not be long here now.
[00:52] <erkan^> I understand it
[00:52] <hajour> tomorrow i come longer again
[00:53] <erkan^> i don't care, it is importnat when you feel very good than we can chat, hajour
[00:53] <hajour> i just missed ubuntu
[00:54] <erkan^> ja, maar ga je toch niet bij ubuntu weg, hajour ? of begreep ik verkeerd?
[00:54] <hajour> no i don't leave ubuntu .we have talked it out well sort off
[00:55] <hajour> ubt is not ubuntu
[00:55] <hajour> ubt=ubuntu-beginners-team
[00:55] <erkan^> ok
[01:02] <erkan^> I go sleep now. veel sterkte en hugs, erkan^ :)
[01:03] <erkan^> I go sleep now. veel sterkte en hugs, hajour :)
[01:03] <hajour> o to late
[03:26] <hajour> jledbetter, are you around?
[03:27] <jledbetter> hajour, Yes. How are you?
[03:27] <hajour> recovering
[03:27] <hajour> and how are you jledbetter ?
[03:28] <jledbetter> hajour, Recovering? I'm fine. Almost bed time here. :)
[03:28] <hajour> i had a epileptic attack a couple of days ago
[03:29] <hajour> http://www.youtube.com/watch?v=2eU56nAV284   <<< like this
[03:29] <jledbetter> hajour, Oh no :( I'm glad to hear that you're recovering
[03:29] <hajour> muscles are still stiff and still fast tired
[03:30] <jledbetter> hajour, Are there things to help with the soreness?
[03:30] <hajour> but i not have yet make a mail together with maco for asking sponsoring
[03:30] <hajour> no just have to go true it
[03:30] <jledbetter> hajour, When is it due? I really hope you apply.
[03:31] <hajour> am i now to late for ask sponsering ?
[03:31] <Pendulum> hajour: nope. sponsorship applications are due by March 29th
[03:31] <hajour> UndiFineD,  have put me on the list for uds
[03:31] <jledbetter> Pendulum, Thank you :)
[03:32] <hajour> thank you Pendulum
[03:32] <Pendulum> jledbetter: for?
[03:32] <hajour> but if i get sponsering and i can come.
[03:33] <jledbetter> Pendulum, The date. I couldn't remember.
[03:33] <hajour> i would like someone is informed about some things
[03:34] <hajour> if i get a attack medic people moslty give depakine injection. because its fluid .
[03:34] <hajour> but i am very alergic for depakine
[03:34] <hajour> if i get a attack i cant say it myself
[03:34] <hajour> someone else need to say it then
[03:35] <Cheri703> hajour: you might carry a card or something with instructions like that. just in general, not UDS specifically
[03:35]  * hajour remembers now again why she was not be away 21 years vacation ect.
[03:36] <hajour> yes but still not all medic look or you have a card
[03:37] <hajour> they just response fast as possible
[03:38] <hajour> also i hope if that happens .what i hope not.people nnot go be afraid for me or something
[03:39] <Cheri703> if you wear a medic alert bracelet or necklace, then it alerts them that there is more going on
[03:40] <hajour> i had a neckllace when i was child and still a medic gave me depakine
[03:41] <hajour> so thats why i am more reassured if some people know that
[03:42] <Cheri703> well, yeah, but there's no guarantee that any of the people you have told in advance are going to be with you at all times
[03:42] <hajour> still it make change smaller it will happen
[03:42] <hajour> will not happen i mean
[03:43] <hajour> i not know  or i can go or i get sponsering and i now already am nerves
[03:45] <hajour> o btw i walk on high heals.because if i wear flat shoes i fall.my muscles arewrong grown in my childhood because of have wear a iron hip mmm bricket? not know the good word for it
[03:47] <hajour> i have wear that 3 years from half year till 3 and half year
[03:48] <hajour> mm i think i need to buy more duck tape
[03:49] <hajour> then i can tape my bodyparts better to each other
[03:49] <hajour> XD i see it all for me .silver woman
[03:49] <hajour> all taped in
[03:50] <hajour> it will be cheap not cost on cloths :))
[03:52] <hajour> ye well better see things with a little humor
[03:52] <hajour> btw who is already been on a UDS? Pendulum  i know
[03:55] <hajour> i am trying to get a idea what i can expect on a UDS
[03:57] <hajour> mmm i just discovered my kids have played last week on my games on facebook .they do better then me :D
[03:58] <hajour> my oldest almost not sleep whole here live
[03:58] <hajour> i think she was bored.
[03:59] <hajour> well enough talked against myself by
[03:59] <hajour> till later maybe
[05:51] <hajour> http://www.guardian.co.uk/world/2011/mar/15/japan-nuclear-crisis-tsunami-live
[05:53] <hajour> persia and rx007 live in japan .i not know who more from ubuntu
[05:56] <hajour> jledbetter nobody knows yet from japanese ubuntu or they are alive ect
[05:57] <pleia2> persia has checked in, he's ok
[05:58] <hajour> btw it makes me mad to see after all what is happened the many victums .to see that piece between about a kill bank black day.what is money compared to humans
[05:58] <hajour> glad to hear persia is ok pleia2
[05:58] <hajour> his family to pleia2 ?
[05:59] <pleia2> hajour: I haven't heard any bad news
[05:59] <hajour> have they food and shelther?
[05:59] <pleia2> I don't know anything behind him saying that he's ok :)
[06:00] <hajour> if you speak him will you ask him then pleia2 ?
[06:00] <pleia2> of course
[06:01] <hajour> if he need help i thought on organize some here from ubuntu for to help ubuntu teammembers when needed pleia2
[06:02] <hajour> many small things together can make a big difference
[06:03] <hajour> japanese ubuntu team members
[06:03] <hajour> i meant
[06:04] <hajour> if it is not a good idea just say
[06:05] <pleia2> it's certainly something we should keep in mind if they need the help
[06:05] <hajour> pleia2,  if you speak persia will you want ask then or he know or rx007 is ok?
[06:05] <hajour> we could ask on uds then
[06:07] <hajour> the danger is still not gone btw.because of the nuclear reactor
[06:07] <hajour> and after shocks
[06:08] <pleia2> yeah
[06:09] <hajour> cant help it .in this kind things my brains is going on max by thinking of possibly solutions
[06:09] <hajour> for to help
[06:09] <hajour> i cant sleep
[06:10] <hajour> rx007 is team member of speechcontrol
[06:10] <hajour> not heard from him
[06:10] <pleia2> I have a cousin in tokyo, she said there are still outages for power and internet
[06:10] <pleia2> so hopefully it's just that he hasn't been able to get to a stable internet connection
[06:11] <hajour> yes i hope so
[06:13] <hajour> good friend of my brother who is married to japanese woman live also in japan with there son
[06:13] <hajour> not heard of them to
[06:15] <pleia2> hope everyone is ok
[06:15] <pleia2> bedtime for me, take care hajour
[06:16] <hajour> good night pleia2
[06:16] <hajour> and you to take care pleia2
[14:05] <erkan^> AlanBell, i have a probleem with a magnifier (i had typing on a terminal --> magnifier)
[14:05] <erkan^> (magnifier:5832): Bonobo-WARNING **: Assigning a default value to a non readable property 'source-display-screen'
[14:05] <erkan^> (magnifier:5832): Bonobo-WARNING **: Assigning a default value to a non readable property 'target-display-screen'
[14:05] <erkan^> An instance of magnifier is already active. Exiting Program.
[22:39] <erkan^> hello


[14:19] <gsedej> xnox, thanks for clarifying
[14:28] <gsedej> also on 2 older laptops (intel i7 4000 series ) that i tried ubuntu, it was always trying to boot windows, no metter bootorder. I had to use some custom boot and enable/disable fastboot to go automatically to grub and not windows
[14:29] <gsedej> in one case fastboot needs to be enabled to use custom boot
[14:30] <xnox> gsedej:  that is highly dependant on a given laptop. We have experienced many laptop firmwares which are not UEFI spec compliant, and e.g. force boot windows bootmgr, or inverse ubuntu's shim/grub, instead of the default bootorder entry.
[14:31] <xnox> gsedej:  e.g. on some windows 10S laptops i had to use from windows uefi variable editor to set "windows" bootmgr path to Ubuntu's shim to get the machine boot into grub.
[16:10] <gsedej> i think this is also the case with at least one of laptops (force windows boot)
[22:44] <xnox> gsedej:  =( it is very sad


[02:47] <lobaman> i need to press double ~ to show that character.
[02:48] <lobaman> i mean to show ¨~¨  i need to press double.
[02:48] <lobaman> and also double quote.
[02:48] <lobaman> and i cant type apostrophe.
[02:49] <lobaman> edubuntu does it. is there a way to make this disable.
[02:49] <crusader_> hello can someone please help me with LTSP installation on edubuntu 7.10?
[03:13] <lobaman> how to make my keyboard normal as before?
[03:13] <lobaman> cause i need to press ¨ twice. to show ¨ character.
[03:13] <lobaman> and also i can do this. ä <== double quote + a  and i dont like it.
[03:14] <lobaman> and these ë <== double quote + e ... i want to disable it.
[05:24] <lobaman> anyone alive?
[05:36] <lobaman> ok i have problem in keyboard.
[05:37] <lobaman> i have to press twice ` to show the character.
[05:37] <lobaman> also the double quote ¨
[05:37] <lobaman> i dont want this feature
[05:38] <lobaman> i can do this ä .... <== doublequote + a
[05:38] <lobaman> i dont want this. it slow me to type.
[05:57] <Amaranth> compose key stuck on?
[05:57] <Amaranth> oops, too late
[06:00] <johnny_> uggh..
[06:01] <johnny_> so.. what to do about moving ubuntu to another drive..
[06:01] <johnny_> trying to figure out the whole uuid thing
[06:01] <johnny_> used to normal designators
[06:01] <johnny_> i'm trying to use blkid but it doesn't to work
[06:43] <kgoetz> johnny_: replace the uuid with a proper identifyer
[07:36] <johnny> kgoetz, found it.. vol_id
[08:39] <vi390> where can I disable XDMCP
[10:19] <Kamping_Kaiser> vi390, its disabled by default
[15:30] <MegaIRC> hi everybody
[15:31] <MegaIRC> is there somebody than can help me in a project
[15:31] <MegaIRC> ?
[17:49] <LaserJock> ogra_cmpc: did you get my email to pitti regarding squeak?
[18:23] <foefieslide> small issue
[18:23] <foefieslide> installed edubuntu 7.10 - works great
[18:24] <foefieslide> hooked up via terminal no problemo
[18:25] <foefieslide> but i have 40 amd terminals that pxe boot, run through initial stuff, shows the edubuntu screen and then just before log in
[18:25] <foefieslide> it gets stuck...so the cursor simply flicker all the time
[18:26] <foefieslide> i checked the chipset is GeodeLX
[18:27] <foefieslide> i added XSERVEr = VESA to the /opt/ltsp/i386/etc/lts.conf
[18:27] <foefieslide> ran ltsp-update-image
[18:27] <foefieslide> but the problem persist
[18:27] <foefieslide> any advise
[18:33] <johnny> there have been various video problems with thos geodes.. i don't know what what the ultimately issue is tho
[18:34] <johnny> try asking in #ltsp
[19:50] <foefieslide> johnny tx Qfunk's patches worked very well
[19:57] <nhaines> Hi everyone!  I'm curious about the best way to try out Edubuntu Hardy Alpha 5.  Is it to install Ubuntu Hardy and use the Edubuntu add-on CD?
[20:00] <johnny> nhaines, i don't know the mechanics for sure, but that sounds right
[20:01] <nhaines> Oh well, it's not a Desktop CD, but adding the CD as a repo source and doing 'sudo apt-get install edubuntu-desktop' can't be too hard.  ;)
[20:01] <nhaines> Thanks!
[21:31] <nixternal> ogra: you around?
[22:25] <subsume> I am attempting to follow https://help.ubuntu.com/community/UbuntuLTSP/LTSPFatClients
[22:25] <subsume> but I am not understanding how to make the client machines link up to this


[18:21] <wxl> i can't imagine libreoffice-math gets used by nearly anyone
 I actually thought we excluded it. Shows how much I pay attention.
[18:22] <wxl> nope but we should
 I agree
[18:23] <wxl> i really need to get a dev environment set up
 I need to do "Something" too.
[18:27] <wxl> i'm surprised we don't have something readily available a la altispeed
 I have a VM all set to go, I just don't find myself in front of it enough.
[18:34] <wxl> thus why i mention altispeed… it could be accessible anywhere
 do we know if or when lxqt 1.3 will be in the development version ?
[19:21] <wxl> i suspect unless @tsimonq2 has given a particular timeline that there are no certain plans
[19:22] <wxl> it does seem to be in experimental though
 Probably the Matrix bridge. Anyway, I'm starting LXQt 1.3
 @tsimonq2 in May 10
 But it will be working on lxde-gtk3
 XD
[22:15] <wxl> ew


[00:01] <flocculant> sigh - no - I'd take this, but not for *all* button
[00:01] <flocculant> or
[00:01] <flocculant> neutral :p
[00:01] <knome> hmm?
[00:07] <flocculant> there's more than 1 for sure
[00:07] <knome> than one what? :)
[00:20] <pleia2> been socialmediaed
[00:20] <knome> pleia2, ta
[00:26] <bluesabre> flocculant: woot!
[00:28] <flocculant> bluesabre: yea - pleased there :)
[00:29] <flocculant> looking pretty good now :)
[00:32] <flocculant> bluesabre: so just some 'really small subsubsubscript' menulibre things I think
[00:33] <flocculant> one at least I think can be 'opinion' d :)
[00:33] <flocculant> bug 1513590 - pretty sure we said that wasn't a bug ?
[00:34] <flocculant> bug 1515184 - can't confirm now - perhaps close it
[00:35] <flocculant> then thunar
[00:35] <flocculant> if we still get all these bugs there - should we start looking elsewhere when we move to 16.10?
[00:36] <flocculant> and how many are really thunar and not elsewhere like gvfs etc?
[00:36] <flocculant> stuff to think about
[00:41] <flocculant> if xubuntu is about giving people xfce and tools - when is one as broken as thunar is off and on - perhaps we should think outside the box here
[00:42] <flocculant> until somethinks about nautilus ofc ...
[00:42] <flocculant> then thunar \o/
[00:43]  * knome thinks outside the box and goes to bed
[00:43] <knome> good night everybody and catch you later :)
[00:44] <bluesabre> flocculant: yeah, thunar has been not so great for a while now... not sure if the same issues are seen in pcmanfm, and probably not in caj
[00:44] <bluesabre> a
[00:45] <flocculant> well
[00:46] <flocculant> with pcmanfam I don't get the usb3issue iirc
[00:46] <flocculant> I shouldn't have to really quickly yank the cable :)
[00:47] <bluesabre> :D
[00:48] <bluesabre> it would be really swell if we could get more code contributors to xfce to fix these things :)
[00:48] <flocculant> well
[00:49] <flocculant> bluesabre: sigh .... I know ;)
[00:49] <bluesabre> but yes, we are getting to the point that we should consider alternatives
[00:50] <flocculant> asmuch as I would love to be able to say "omg I CAN fix this' I can't ...
[00:50] <bluesabre> same here
[00:50] <bluesabre> unfortunately
[00:50] <flocculant> so if xfce  can't - we are xubuntu not xfce
[00:51] <flocculant> and do that whole - this is Xubuntu - thing
[00:51] <bluesabre> yup, agreed
[00:51] <flocculant> a whole cycle to think those things :)
[00:52] <bluesabre> there's lots of options out there now, so this is something we should look into for 16.10
[00:52] <flocculant> for sure
[00:53] <flocculant> I'd really like for team to look outside now - I'd rather test foo now :p
[00:53] <flocculant> !team | up dudes
[00:54] <bluesabre> do we need a meeting soon so we can decide how to vote?
[00:54] <bluesabre> it's been... a contentious topic
[00:55]  * Unit193 looked outside, too dark to see things.
[00:55] <Unit193> I have pcmanfm installed, but as I don't use the filemanager all that much thunar does pretty well for me.
[00:56] <bluesabre> I use thunar, it crashes, I restart and remember to rename things from a terminal
[01:00] <Unit193> Just played around with it for a bit, finally got one.
[01:01] <Unit193> I'm guessing we already had a good stacktrace though?
[01:02] <bluesabre> good stacktrace probably, but no good debuggers to figure out how to fix it
[01:02] <bluesabre> I'm ok at coding, terrible at debug
[01:03] <Unit193> thunar crashed with SIGSEGV in __GI___libc_free()
[01:05] <Unit193> https://paste.unit193.net/?ecacb0305f88cf72#vK6jNpzOl7F3I16cDi7luRjyZ7E/EV1mhnVCpShQwp8= ? :D
[01:06] <flocculant> night peeps
[01:06] <bluesabre> https://img.buzzfeed.com/buzzfeed-static/static/2014-10/26/6/enhanced/webdr08/enhanced-14836-1414320930-8.jpg
[01:06] <bluesabre> night flocculant
[01:07] <Unit193> Mhmmmm! :D
[01:07] <Unit193> Soo, do we have anyone on thunar over in Xfceland?
[01:09] <bluesabre> nope, not really
[01:10] <bluesabre> for me, it'd probably be easier to port caja/nemo to xfce than fix thunar
[01:10] <Unit193> ...ali?
[01:10] <bluesabre> could be a good person to hand it to
[01:10] <Unit193> sidi?! ;P
[01:11] <bluesabre> he can sandbox it, but that would make it less valuable
[01:11] <bluesabre> >.>
[01:14] <Unit193> And http://git.xfce.org/xfce/thunar/commit/?id=029012f4c39d9d3d9ae617491a69f76f54a4192f didn't even help (or all cases?)
[01:15] <Unit193> Think it's worth it to at least push that?
[01:17] <bluesabre> could add a daily thunar to https://launchpad.net/~xubuntu-dev/+archive/ubuntu/ppa and run with it
[01:18] <Unit193> Meh.
[01:18] <Unit193> Also, this does fix some bugs. :3
[01:19] <Unit193> bluesabre: Select a couple files → Ctrl+x → navigate to somewhere → ctrl+v  thunar should crash.  Update from PPA, repeat.
[01:22] <bluesabre> it's always hit and miss for me... I can usually go a few copy+pastes/renames before it dies on me
[01:24] <Unit193> Using the method I outlined seemed to hit it more.  Do you have the PPA one?
[01:25] <Unit193> Should we push that, and hope it makes some of them go away (like it seems to)?
[01:25] <bluesabre> Unit193: I'll check it out, but yeah, I think it'd be good to include
[01:41] <Unit193> OK, I'll wait your order.
[03:11] <bluesabre> :)
[03:12] <bluesabre> now I have to actually do it in reasonable time
[03:12] <bluesabre> I'll do that in the morning
[03:12] <Unit193> This way flocculant can NACK it too.
[03:13] <bluesabre> :)
[03:13] <bluesabre> nighty all
[03:14] <Unit193> G'nighty.
[09:48] <knome> added featherlight popups for the submissions in the admin, so it's now easier and faster to get to see a preview
[09:53] <Unit193> That's actually a lot of submissions...
[09:57] <knome> quite, yeah
[09:58] <knome> get voting :)
[09:58] <knome> at the least, we need to make sure the team actually votes before the end of week
[09:59] <knome> if we want to involve the community in a way or another, then we should get that done even faster
[10:02] <Unit193> "Untitled"?  And, on it then.
[10:02] <knome> yeah, there are many untitled submissions
[10:04] <knome> it all actually goes relatively smoowth with this interface
[10:04] <knome> -w
[10:04] <knome> i didn't time my voting, but it definitely didn't feel like too long
[10:05] <knome> and now it should be even faster since you have the featherlight popups :)
[10:05] <knome> (i used some time to check if photos were blurry)
[10:06] <Unit193> So, this voting to let them in or chose winners?
[10:06] <knome> i don't know; either way, i think the team needs to pick a shortlist
[10:06] <knome> eg. if the community votes, it can't be 50 options
[10:07] <knome> so, either voting for things people can vote on, or if we don't end up with community voting, then it's for inclusion
[10:07] <knome> i voted up anything i would be okay being included
[10:07] <knome> eg. more than 6
[10:09] <knome> that'd make it 11
[10:12] <Unit193> Why are there planes strafing?
[10:13] <knome> how would i know? :)
[10:13] <knome> !team | wallpaper contest voting is open; get your votes in now!
[10:14] <Unit193> I have come to the conclusion I don't use normal wallpapers.  Also, I like that I can review and change my choices later, and really should.
[10:14] <knome> what is "normal" anyway...
[10:16] <knome> from what i've seen, many people like to use a photo they are emotionally connecting with, or some kind of mountainy view, or then just some solid color
[10:16] <knome> mountainy view being something to dream of
[10:16] <knome> could be a photo of a quiet beach somewhere too
[10:17] <knome> you get the gist
[11:31] <knome> ok, bbl
[13:31] <Unit193> flocculant: If I ping you, you won't get it will you?
[14:39] <bluesabre> Unit193: we could make an offline forwarding bot
[14:39] <bluesabre> every time there is a ping to an offline person, they get an email :D
[14:39] <Unit193> Howdy, bluesabre.
[14:40] <bluesabre> hi Unit193
[15:23] <petrovich> Hi there
[15:23] <petrovich> Is it only me, or no one cannot upgrade his 16.04 ubuntu?
[18:21] <KenstaFoo> Hello
[18:21] <knome> hello


[03:23] <devilhorns> grrr
[06:08] <ajay> hi all, i was going through igep forum , isaw Remove from IDC cable the pin 6 or remove all cables except pin 2,3 and 5, that's all.
[06:08] <ajay> Don't remove the protection resistors if you don't know what are you doing, if you remove the resistors and connect directly a full RS232 to J960 you can damage the board.  is the solution for grounding issue
[06:08] <ajay> so should i remove DB9 connectors all pin other than 2 3 5
[06:09] <ajay> where this resistor resides in IDC10 to DB9 cable
[06:09] <ajay> which absence can cause damage of board
[13:04] <dcordes> I am wondering if this a netbooklauncher or an onboard bug: onboard and onboard floating maximize button are both hidden when the 'go home' gnome-panel-applet button is pressed
[13:04] <dcordes> Any advise welcome.
[13:31] <persia> dcordes, Might try asking in #ubuntu-bugs: the folk there tend to be very good at hunting down the appropriate package.
[15:12] <dcordes> Few weeks ago I came here pestering everybody about folowing problem:
[15:12] <dcordes> In any ubuntu arm rootfs networking would only work as root
[15:12] <dcordes> non privileged users were unable to ping or use network in any other way
[15:13] <dcordes> solution is fairly easy
[15:13] <dcordes> # CONFIG_ANDROID_PARANOID_NETWORK is not set
[15:18] <ynezz> lol?
[15:32] <dcordes> ynezz: it is for potential log readers.
[15:32] <dcordes> If you put question somewhere and find solution it is good to put it in the same place
[15:40] <ynezz> ok, I just don't get that config directive, that's all
[15:41]  * persia thinks the easier way is not to start from an Android kernel :)
[16:08] <dcordes> persia: There are no options
[16:08] <dcordes> persia: I had to patch many drivers in order for stuff to work
[16:09] <dcordes> ynezz: if you set that config only root will be able to use network. I think the android javablob is executed as root .. and some strange abstraction on top of that
[16:09] <dcordes> for permissions
[16:12] <ynezz> dcordes: and you're porting android kernel to ubuntu, or what's the use case?
[16:16] <dcordes> ynezz: I am patching the android kernel so it will work with any GNU/Linux userspace
[16:20] <ynezz> ah
[16:25] <dcordes> Hm would this be a good idea to inquire about Xorg input device problem in maverick RC ?


[00:00] <asac> fta: i think its our problem
[00:00] <asac> cdbs orders might be difference
[00:00] <fta> ?
[02:22] <[reed]> asac: ping
[02:36] <suzhe> hello
[02:38] <suzhe> anybody there?
[04:43] <[reed]> asac / fta: committed like 7 of glandium's patches... wonder if any of them obsolete some of your patches ;)
[06:06] <gnomefreak> asac: you around or is it still too early?
[06:07] <gnomefreak> NCommander: you have email ;)
[06:09] <gnomefreak> our link is fixed as well
[06:10] <gnomefreak> s/our/your
[07:25] <gnomefreak> !info sunbird hardy
[07:26] <gnomefreak> !info sunbird intrepid
[07:51] <gnomefreak> its almost 3am :(
[08:01] <gnomefreak> @time new_york
[08:02] <gnomefreak> ok im gone maybe ill be back for meeting but i really need sleep
[11:36] <suzhe> Hello?
[11:37] <suzhe> anybody there?
[11:43] <suzhe> Does anyone can help handle bug #286906?
[13:28] <shirish> asac: hi :)
[13:30] <shirish> asac: I'm here to know which features are new and documentation ready on https://help.ubuntu.com/community/NetworkManager
[13:30] <shirish> asac: which ones still hold good in ubuntu 8.04 and ubuntu 8.10 and which things are new.
[13:42] <cwillu> firefox is routinely getting stuck for several minutes when I come back to it.  It's not paging in (it's already in memory according to top), and strace shows it calling getTimeOfDay 4 times, then write, and so forth over and over again
[13:53] <asac> shirish: wait for a few minutes pleaes ;)
[13:54] <shirish> asac: sure, will do
[13:56] <shirish> asac: please lemme know when you are free so we can start atleast knowing what spaces needed to be started to do stuff.
[13:57] <cwillu> :/
[13:57] <cwillu> 1gig of resident memory used on a session that usually only uses 600mb
[13:58] <cwillu> it's bouncing around though, up to 1g, down to 948m slowly back up to a gig, down to 946m
[13:59] <cwillu> (2.5gb in this machine, there's 100mb not even used yet, so it's not thrashing that I can see)
[13:59] <cwillu> I can get 1 click every 3 minutes through
[14:00] <cwillu> if I middle click a tab, the windows will go grey, and 3 minutes later (or so) it'll close it
[14:00] <asac> cwillu: try to disble all your extensions is the first advice i ususally give
[14:01] <asac> cwillu: if that doesnt help try to disble your adobe flashplugin
[14:03] <shirish> asac: is the practise of adding $USER to netdev still desired or is that deprecated?
[14:04] <shirish> asac: that should have been is the practise of adding $USER to the netdev group still desired or is that deprecated practise?
[14:13] <asac> shirish: huh?
[14:13] <asac> shirish: oh because of dhcp? i dont think so. no
[14:13] <asac> dhcp is run as root now
[14:14] <asac> shirish: let me check that page now
[14:14] <shirish> asac:  I have been having issues as to which is the correct way to configure stuff for having things managed by network-manager
[14:14] <asac> shirish: Installation -> maybe we should make it obvious that its installed by default in hardy, intrepid
[14:14] <shirish> right
[14:15] <nxvl> asac: hi
[14:15] <asac> shirish: untick the "Enable this connection"  .... thats all outdated, but even before it was called "enable roaming mode"
[14:15] <nxvl> asac: did you get change to check my package?
[14:15] <asac> nxvl: no i didnt get any coins ;)
[14:15] <asac> :-P
[14:16] <asac> nxvl: i have two things on my list. then i will do that
[14:16] <shirish> asac: hang there a minute, brother, writing the first thing about hardy and Intrepid.
[14:16] <asac> shirish: well. so gutsy + hardy the checkbox is called "enable roaming" or something
[14:16] <nxvl> asac: ok, did you have the link to the package?
[14:16] <asac> in intrepid that administration menu doesnt exist anymore
[14:16] <asac> by default
[14:17] <asac> you need to install the network-admin thing from gnome to get that gui back
[14:17] <asac> (usually NM should be able to deal with that now)
[14:22] <shirish> asac: in this version of nm-applet it says "enable networking"
[14:22] <asac> shirish: sorry. there is confusion
[14:22] <asac> shirish: previously that dialog in system was the gnome dialog
[14:22] <asac> thats gone now and replaced with nm connection editor
[14:23] <asac> shirish: the "configuring section is mostly about the /etc/network/interfaces " section
[14:24] <shirish> asac: can you please first check the installation section, do you think that is correct or incorrect?
[14:24] <asac> shirish: i really think we cannot keep the documentation for all (dapper - intrepid) on the same page
[14:24] <shirish> asac: the part of ubuntu 8.04 and ubuntu 8.10 installation
[14:24] <asac> shirish: ok let me lok there
[14:25] <asac> but note that we should certainly do someting about the configuring section
[14:25] <asac> especially what to do for old setups
[14:25] <asac> shirish: i think NM is installed by default since feisty
[14:25] <shirish> asac: think the same but then how we do that, I'm not a good shot at doing stuff from scratch, but that could be taken up at the ubuntu-doc mailing list
[14:26] <shirish> asac: ok, what about the bit about the applet, you think that is wrong as well ?
[14:26] <asac> shirish: the nm-applet doc isnt right. its a tray thing. the only thing the user can do is enable/disable it in the gnome session
[14:26] <asac> Preferences -> Sessions
[14:27] <asac> but i don tihnk we should mention that
[14:27] <asac> nobody wants to disable it
[14:27] <shirish> asac:  right
[14:27] <asac> shirish: imo. we should state that its installed by default. then we should just document the features
[14:27] <asac> and add a FAQ or Troubleshooting section
[14:27] <shirish> asac: right
[14:27] <asac> with the most common pitfalls
[14:28] <asac> shirish: so the main elements (which would deserve a short intro) are:
[14:29] <asac> 1. the applet
[14:29] <asac> 2. the connection editor (which is what you find in System now)
[14:29] <asac> not sure how to document the applet. usually thats self explaining. to connect to a network, just click on it
[14:30] <asac> also might be important to mention that NM auto creates connections on a best effort base, but if those connections dont match your need (e.g. no dhcp), then you need to use the connection editor to configure things
[14:30] <asac> for the connection editor we should do multiple paragraphs:
[14:30] <shirish> asac: right hang on, putting up things as you speak.
[14:31] <asac> 1. introduce the available connection types (wired/wireless/mobile broadband/VPN)
[14:31] <asac> 2. document how to create/modify a user connection
[14:32] <asac>   (here we might need a hint that auto created connections are _not_ editable. and modifying them withouth changing names wont be saved)
[14:32] <asac>    2a. introduce wired/wireless/mobile broadband/ppp tabs
[14:33] <asac>   2b. introduce ip4settings tab in connection editor (e.g. which type - aka static dhcp, dhcp addresses only, etc.; how to edit routes)
[14:34] <asac> 3. document how to install vpn support
[14:34] <asac>   3a. give a quiick overview of the vpn wizards you get in connection editor when the vpn packages are installed
[14:34] <asac>  (not sure if this really needs to be detailed)
[14:41] <asac> nxvl: do you have test packages in a PPA ?
[14:42] <asac> nxvl: security updates are kind of critical and since there is no official way to stage them for broad-testing we usually put them in a PPA so w can at least verify the bits that will be released before pushing them
[14:43] <nxvl> asac: yes, in my ppa
[14:43] <nxvl> asac: nvalcarcel
[14:44] <asac> nxvl: so i can take that orig and do a test build and get the exact same result ;)
[14:44] <asac> ok getting the branch here too
[14:45] <nxvl> yes
[14:45] <shirish> asac: going slow, can you re-check the Installation part once again and then the configuring part which I have put up atm.
[14:45] <asac> shirish: yeah. please save what i wrote though ;)
[14:46] <shirish> asac: write, its there in my logs :)
[14:46] <asac> shirish: the endable sentence can be dropped. the applet is there to manage your networking from the desktop ;)
[14:48] <shirish> asac: did that
[14:48] <asac> shirish: configuring is completely outdated. needs to be dropped
[14:49] <asac> shirish: the bits about the interfaces do not apply to most users. so we should add how to deal with interfaces in the troubleshooting section
[14:49] <asac> oh sorry
[14:49] <asac> didnt see that you still split dapper et al
[14:49] <shirish> asac: right, for the moment shall I put it as configuring for old versions?
[14:50] <shirish> asac: I dunno, there may be users who may be using and may need this documentation.
[14:50] <asac> shirish: hardy + intrepid + _gutsy_
[14:50] <asac> shirish:  its unfortunate that that documentation still exists
[14:50] <asac> it made lots of users most likely revert our transition where we removed everything from interfaces automatically
[14:50] <shirish> asac: shouldn't that be gutsy+hardy+intrepid in that order or the reverse ;)
[14:51] <asac> sure
[14:52] <asac> shirish: add to hardy et al: "if your interfaces are shown as "unmanaged" in network manager applet, please read the troubleshooting section about "TBD"
[14:54] <shirish> asac: by et al you mean Hardy and after that right?
[14:54] <asac> nxvl: you didnt add the .desktop file to the branch
[14:54] <asac> please do that ;)
[14:54] <asac> shirish: yes
[14:57] <shirish> asac: ok please refresh or recheck the page, the first two sections, Installations and the new one which I made about configuration, are you happy with that?
[14:57] <nxvl> asac: mm i forgot tu push that change
[14:57] <nxvl> asac: one second
[14:58] <asac> shirish: you still have "ts used to enable or disable the nm-applet for that session. "
[14:58] <asac> thats just not th epurpose of the applet
[14:58] <asac> the purose is to "manage and activate/deactive your network connections"
[14:58] <nxvl> asac: k, pushed
[14:59] <shirish> asac: right
[14:59] <shirish> asac: what it should be saying, its used to disable or enable networking for the session?
[14:59] <shirish> asac: ah, ok didn't see that last sentence, doing it
[15:01] <asac> shirish: ok and "Specifically for Hardy and latter," would be "For intrepid or later, ..."
[15:02] <asac> shirish: TBD means ... to be defined. we should replace that with the link to the troubleshooting section when we have that ;)
[15:02] <shirish> asac: ok cool.
[15:03] <asac> shirish: imo we shouldnt really make a single document out of it for NM 0.7
[15:03] <asac> i mean everything below is completely outdated too
[15:03] <asac> i mean everything below is completely outdated t
[15:03] <asac>  oops
[15:03] <asac> ;)
[15:03] <shirish> no issues.
[15:06] <shirish> asac: corrected the former, now what about suspend support, that's also outdated/deprecated as far as  Hardy, Intrepid is concerned?
[15:07] <asac> shirish: i am not even sure how this applies anywhere
[15:07] <asac> most likely its just dapper and feisty
[15:07] <asac> but cant tell for sure
[15:07] <shirish> asac: so will put it like that, dapper and feisty (atleast the headings)
[15:07] <asac> shirish: really. lets split this up in a) documetnation of networkmanager 0.6 (e.g. dapper, feisty, gutsy, hardy) and networkmanager 0.7 (intrepid and later)
[15:08] <asac> shirish: then we can keep the document in the state as it was before
[15:08] <asac> (even though its inaccurate for a bunch of things for a bunch of things)
[15:08] <asac> ;)
[15:08] <asac> we just run into in accuracies all over the place and fixing everything just because we want to document intrepid is too hard
[15:08] <shirish> asac: how do I do that? Do you want me to create a new page or how?
[15:09] <asac> shirish: yes. i think we should make one main document that just states:
[15:09] <asac> documetnation for network manager before 0.7 (dapper,feisty, gutsy, hardy) can be found here: ...
[15:09] <asac> and for network manager 0.7 (intrepid, and later) can be found here:
[15:09] <shirish> asac: ah ok, that is cool.
[15:10] <asac> shirish: at least i think that makes sense
[15:10] <shirish> asac: but then this page also needs to be renamed, ok making a new page.
[15:15] <asac> nxvl: looks good. a final release commit would have helped to identify what was released later though
[15:16] <asac> nxvl: you can still do that by just running dch -r -Dhardy-security
[15:16] <asac> or something
[15:16] <asac> and commit with "RELEASE x.y.z-0ubuntuY to WHATEVERYOURDISTROISCALLED/hardy-security"
[15:16] <asac> nxvl: ^^
[15:16] <asac> nxvl: when that is done i am happy ;)
[15:17] <nxvl> our distro is always called hardy
[15:17] <nxvl> no -security or -updates
[15:17] <nxvl> is always hardy
[15:17] <shirish> asac: have made a page called it networkmanager options https://help.ubuntu.com/community/NetworkManagerOptions is that good enough ?
[15:18] <nxvl> asac: but got your point on the release commit
[15:18] <asac> shirish: err. most likely nobody will look for that
[15:18] <asac> shirish: imo the top most page should refer to NetworkManager0.6 and NetworkManager0.7
[15:18] <asac> nxvl: yeah ... then use "hardy" ;)
[15:19] <nxvl> asac: i'm unsure about the versioning schema
[15:19] <asac> nxvl: i usually say: to ubuntu/intrepid .... you could say to "oem/hardy"
[15:19] <asac> ;)
[15:19] <shirish> asac: so you want me to integrate this at the NetworkManager doc itself.
[15:19] <asac> nxvl: just the complete version from the changelog imo
[15:19] <nxvl> asac: since i'm having a different base version, but the ubuntu part should stay the same, or change?
[15:19] <asac> nxvl: you can also move the +nb1 before the +nobinonly
[15:19] <asac> nxvl: the netbook thin at the end is not needed
[15:19] <asac> just 8.04.1 should be enough
[15:19] <sebner> asac: is nxvl your new padawan? ^^
[15:20] <asac> sebner: intermediate ;)
[15:20] <sebner> kk ^^
[15:20] <nxvl> sebner: kind of, i still don't understand asac'c packaging methods
[15:20] <nxvl> :P
[15:20] <sebner> nxvl: who does that .... :P
[15:20] <nxvl> right
[15:20] <nxvl> asac: oh! ok then
[15:21] <shirish> asac: can you re-check the NetworkManager top-post section, is that good ?
[15:23] <asac> yeah let me install abrowser agin ;)
[15:23] <asac> dont have a browser right now
[15:24] <sebner> asac: "abrowser" or "a browser" ^^
[15:25] <shirish> its abrowser
[15:25] <sebner> hihi
[15:31] <shirish> sebner: hi :)
[15:32] <shirish> asac: have put up a new page where I have ported stuff from what we discussed so far, https://help.ubuntu.com/community/NetworkManager0.7
[15:32] <shirish> asac: using the documentation template, so would have to excuse the stuff not written yet :)
[15:35] <shirish> asac: then how do you want to do it? I thought you wanted to have a new page, altogether, what should be ideal IMHO should be https://help.ubuntu.com/community/NetworkManager has stuff only for NM 0.7 while the rest should be another page altogether, all stuff on the same page doesn't work (becomes too confusing)
[15:36] <shirish> asac: scratch that last line.
[15:36] <asac> shirish: yes. it would be ok to make NetworkManager 0.7 and give a fat reference to the 0.6 page right on to
[15:36] <asac> p
[15:37] <shirish> asac: right, that I should have thought of before.
[15:37] <sebner> asac: I know you care for the baby but when does NM 0.7 gets officially matura? ca?
[15:38] <asac> shirish: well. its ok as its now i think. its just that we want to make 0.7 the default at some point
[15:39] <asac> maybe its ok for now to link to it from the "main" networkmanager page and keep that at 0.6
[15:39] <asac> sebner: never. dcbw said he would hang himself if not released by end of this month
[15:39] <asac> but given that they now started to do refactoring i doubt that it will happen
[15:39] <sebner> hehe
[15:39] <sebner> kk thx
[15:43] <shirish> asac: https://help.ubuntu.com/community/NetworkManager0.7 that good, the top-most thing?
[15:45] <asac> shirish: you should say "ATTENTION: if you are use dapper, feisty, gutsy or hardy, read the documentatoin for networkmanager 0.6
[15:45] <asac> btw, either NetworkManager (upstream name) or network-manager (package name) please
[15:45] <asac> shirish: ^^
[15:45] <shirish> asac: that's what you meant by FAT ;)
[15:47] <asac> yeah ;)
[15:47] <asac> shirish: also put the same on the other page for intrepid
[15:48] <asac> shirish: people will most likely find one of these through google
[15:48] <asac> so we cannot rely on them reading the url ;)
[15:48] <shirish> asac: right, updated the same.
[15:51] <shirish> asac: did that as well.
[15:52] <shirish> asac: ok now for some info. or introduction of the nm-applet and then nm-connection editor
[15:52] <shirish> asac: know any good content for ^^^
[15:54] <MechtiIde> what about lightning/iceowl-extension 0.9?
[15:56] <asac> shirish: i wrote my ideas above ;)
[15:56] <asac> is there anything that isnt clear :-P
[15:56] <asac> ?
[15:56] <asac> MechtiIde: didnt make the train for intrepid. jaunty will get it
[15:58] <asac> jdstrand: it completely missed that we had a reason to celebrate two days ago ;)
[15:58] <jdstrand> asac: I know! I'm updating CVEs for feisty now :)
[15:58] <asac> jdstrand: so here my cheers and hugs for succeeding in providing full security support coverage for feisty ;)
[15:59] <asac> mission accomplished
[15:59] <asac> now please let go dapper away :/
[15:59]  * jdstrand hugs asac
[15:59] <jdstrand> re dapper> 8 months for you, 32 for me
[16:00] <asac> jdstrand: yeah. most likely it doesnt make such a big difference for you ;)
[16:00] <asac> but it certainly is much appreciated here :)
[16:00] <jdstrand> heh
[16:00] <asac> jdstrand: you still will receive a bunch of tarballs on every release
[16:00] <jdstrand> oh yes, I'm well aware ;)
[16:00] <asac> the same amount actually ;)
[16:03] <asac> jdstrand: will 8.04.1 be supported till june or end of april?
[16:05] <jdstrand> asac: I thought april
[16:06] <asac> jdstrand: wasnt sure, i rememberd that some said that 8.04 isnt LTS, only 8.04.1
[16:07] <jdstrand> asac: I'd like to see that quoted-- I certainly never heard that
[16:14] <fta> mozilla bug 435088
[16:18] <asac> good
[16:21] <fta> asac, i guess we can drop our bzXXX_gre_autoreg.patch
[16:22] <asac> yeah
[16:22] <asac> since its similar ;)
[16:22] <asac> err identical i mean
[16:22] <fta> not identical at all. but the goal is the same
[16:24] <asac> fta: ok then i mixed that up. we should verify that then after dropping
[16:25] <fta> mozilla bug 412610
[16:27] <maxb> Hi, is there anyone around to review my intrepid-nomination of bug 286688?
[16:29] <asac> maxb: any idea how i can shutdown withput that being rewritten?
[16:30] <asac> maxb: are you having extensoins installed (besides ubufox obviously)
[16:31] <maxb> No other extensions. I'm away from the computer on which I initially observed it right now, but let me just check if I can reproduce here.
[16:32] <shirish> asac: can you take a look at https://help.ubuntu.com/community/NetworkManager0.7 and see if things are write, specificially the part about nm-applet, nm-connections editor as well as the introduction to the various technologies
[16:34] <asac> shirish: NM-Applet (a) .... imo the main focus should be on teaching users how to connect to networks and what those entries mean
[16:34] <asac> and only then discuss what happens on right click
[16:34] <asac> (e.g. left-click is the main use case)
[16:34] <maxb> How annoying, what was trivially reproducable there does not reproduce here. I shall investigate further tonight when I'm back at the problem machine and update the bug.
[16:35] <asac> shirish: i think the title "Configuring Devices for Ubuntu 7.10 (Gutsy), Ubuntu 8.04 (Hardy), Ubuntu 8.10 (Intrepid)" is now obsolete and can be removed from the 0.7 document
[16:35] <asac> shirish: we should later look how we can fix the 0.6 document for gutsy/hardy
[16:43] <shirish> asac: I dunno much about doing stuff for 0.6 simply because I don't have that any of those configurations, also going for dinner so bbiaw :)
[16:44] <asac> k
[16:44] <asac> shirish: for now lets focus solely on 0.7
[16:44] <asac> let me know ;)
[16:51] <fta> asac, could you push your ff3 branches ? 3.0.3+nobinonly-0ubuntu2 is not on lp
[17:07] <asac> suzhe: hi
[17:07] <suzhe> hello
[17:07] <asac> fta: oh yeah. we have a .intrepid branch now ... will push from there to head too
[17:07] <suzhe> asac: what's your opinion about bug #286906?
[17:08] <fta> asac, at least, update .head, that's what i merge from for 3.1
[17:08] <asac> fta: done
[17:08] <asac> sorry that i forgot
[17:08] <asac> hmm still pushing up ;)
[17:09] <fta> seems ftbfs-with-branding-dir is no longer needed, i can't find the root of this patch...
[17:09] <fta> mozilla Bug 460915
[17:11] <fta> asac, in rev6, i see   + renamed debian/patches/brandir-dir-depth-fix to debian/patches/ftbfs-with-branding-dir, do you know anything about brandir-dir-depth-fix ?
[17:11] <asac> suzhe: well mozjs.so doesnt really have any abi guarantees i think
[17:11] <asac> which is why we dont provide it in libdir, but in pkglibdir
[17:12] <asac> fta: yeah
[17:12] <asac> fta: it was  a bug
[17:12] <asac> (not sure when)
[17:12] <asac> (not sure if still a problem)
[17:12] <shirish> asac: back, put up some more info. in the nm-applet please re-check in the nm 0.7 page https://help.ubuntu.com/community/NetworkManager0.7 and lemme know what you think.
[17:13] <asac> fta: did i do a lousy comment in commit?
[17:13] <fta> i don't have enough history on that particular patch
[17:14] <suzhe> asac: AFAIK, libmozjs.so keeps backward compatibility since version 160 quite well.
[17:15] <fta> asac, ok, it appeared in rev2
[17:15] <asac> shirish: those  nm applet lines should be accompanied by screenshots i guess
[17:16] <asac> suzhe: yes. but is there any policy on that? if there is we can make a proper first tier lib out of it
[17:16] <shirish> asac: you mean the one where I give the link to the D-Link stuff?
[17:16] <asac> shirish: no. every line ;)
[17:16] <shirish> asac: damn, ok cool. will try
[17:16] <suzhe> asac: And I don't think the abi will be changed in xulrunner 1.9 series
[17:17] <asac> shirish: e.g. "he network-manager or the nm-applet is the one which is found in the systray. The icon of two computers, one below to the other on the left-side." -> screen snippet shich shows the tray with NM
[17:18] <niki> asac: now that your talking about nm, has there been any changes to it so that I have to do some manual configuration lately ?
[17:18] <suzhe> asac: I'm not sure if there is any policy on that.
[17:18] <suzhe> asac: let me have a check.
[17:20] <niki> asac: because, nm doesn't show up in systray when I login any more, have to do a /etc/init.d/NetworkManager restart to get it to show up
[17:21] <asac> niki: if nm-applet is running and NetworkManager you need to restart NetworkManager ... yes.
[17:22] <asac> s/and NetworkManager/and NetworkManager not/
[17:22] <niki> asac: this in on a fresh boot up, so, shouldn't it be started automatically ?
[17:23] <asac> niki: it should
[17:23] <asac> niki: so please check if its not running
[17:23] <asac> if so, post your complete syslog somewhere
[17:24] <niki> I will
[17:26] <niki> asac: another issues with nm is that it seems to have "lost" all the interfaces, no wired interfaces (only an usb0 which is defined in /etc/network/interfaces which is greyed out), and no wireless interface, is that a known issue ?
[17:26] <shirish> asac: you just want the systray or the whole desktop there?
[17:26] <asac> niki: interestee in interfaces are always not-managed by default (same as in gutsy)
[17:27] <asac> niki: should be "unmanaged" in applet
[17:27] <asac> niki: if wireless isnt seen, then that device isnt known to hal ... not a NM issue. you might have disabled wireless in nm right-click menu though
[17:27] <suzhe> asac: though there is no explicit policy about abi compatibility issue of libmozjs.so, I believe that the abi won't be changed during xulrunner 1.9 lifetime.
[17:28] <asac> shirish: well. given that each line gets a snapshot the shown section should be as small as possible - while still giving user enough context to spot that
[17:28] <asac> suzhe: well. believing is good
[17:28] <asac> we need a policy or upstream needs to use SONAMEs to express how they change abi/api
[17:28] <shirish> asac: right, ok will work on that.
[17:30] <niki> asac: wireless is enabled, just wonder why hal had dropped "support" for my "Intel Corporation PRO/Wireless 5100 AGN [Shiloh]" as it has been working, but i'll investigate that
[17:31] <asac> niki: try hal-find-by-capability --capability net.80211
[17:31] <suzhe> asac: can you help ask upstream developer about this issue?
[17:32] <niki> root@niki-laptop:/etc/default# hal-find-by-capability --capability net.80211
[17:32] <niki>  /org/freedesktop/Hal/devices/net_00_16_ea_7a_d2_8a
[17:32] <niki> ^ asac
[17:32] <fta> asac, where did you handle firefox-trunk before you created the bzr branch?
[17:32] <fta> branch nick: firefox-trunk
[17:32] <fta> timestamp: Wed 2007-03-21 18:21:52 +0100
[17:32] <fta> message:
[17:32] <fta>   initial firefox-trunk debian/ package
[17:32] <niki> seems to find it fine
[17:32] <asac> niki: do you see "wirless networks" in the applet at all? have you checked with right clicking that wireless isnt disabled?
[17:33] <asac> "wirless networks" -> thats a grey text in the applet drop down
[17:33] <niki> yep, but in the list it just says "device is unmanaged"
[17:34] <asac> niki: then you have a configuration for that in /etc/network/interfaces
[17:34] <niki> ok, so I my not have that then anymore ?
[17:34] <asac> niki: NM _never_ managed devices in /etc/network/interfaces for you
[17:35] <asac> niki: or maybe ... can you post your interfaces please?
[17:35] <niki> well sometime ago it kinda ignored the entry in interfaces, so that I could managed it both places
[17:35] <suzhe> asac: I think the solution used by opensuse is good enough.
[17:35] <asac> fta: isnt there a branch for that in firefox project?
[17:36] <asac> suzhe: no. people will create packages that link against the libs directly which we do not want unless we know that we can track abi
[17:36] <niki> had to have the entry because nm didn't manage to associate with my ad-hoc network
[17:36] <fta> asac, that's rev2 of all ff3 branches, rev1 being the tarball
[17:36] <niki> sec, i'll paste it in a sec
[17:37] <asac> suzhe: i men what does it help if it works, but you cannot really maintain this stuff in a distro ... we need a real solution
[17:37] <suzhe> asac: then do you have a good solution for this problem? I searched on google and found that there are some other applications that require libmozjs.so
[17:37] <suzhe> asac: many ubuntu users reported similar issues.
[17:38] <asac> suzhe: many? ididnt get to know about that yet.
[17:38] <asac> do you have references?
[17:38] <asac> fta: maybye https://code.edge.launchpad.net/~mozillateam/firefox/trunk.dev
[17:39] <asac> fta: i think that "restart" was done because you wanted to get rid of the tarball cruft in the branch
[17:39] <asac> might be wrong of course
[17:39] <niki> asac: http://pastebin.com/d5fcc918c
[17:39] <asac> fta: hmm. thats that branch
[17:39] <fta> asac, no, we never restarted, this branch starts like all the others
[17:40] <asac> yeah
[17:40] <suzhe> asac: you can search ubuntu libmozjs.so on google.
[17:40] <fta> asac, i wasn't there yet at that time so i don't know
[17:40] <asac> suzhe: only see old noise on the first page
[17:40] <asac> about firefox broken etc.
[17:41] <asac> fta: most likely i did all at once and imported that
[17:42] <asac> fta: the firefox-trunk branch nick was just the name of that branch for me locally at that time
[17:42] <sebner> asac: BTW, any progress with your google chrome/chromium import to LP?
[17:42] <asac> sebner: jcastro would know more ;)
[17:43] <suzhe> asac: for example: http://itsiriuscn.yo2.cn/articles/ubuntu%E4%B8%AD%E5%AE%89%E8%A3%85chmsee.html
[17:43] <sebner> jcastro: pingeling :)
[17:43] <asac> last i know is that we had a pending request to create a "super" project on launchpad
[17:43] <sebner> lol
[17:43] <niki> damm, your quite busy asac ;-)
[17:44] <sebner> niki: he is always busy so just ignore it ^^
[17:44] <asac> niki: so ... you sure you could use wireless in the NM menu?
[17:44] <asac> in hardy?
[17:44] <niki> intrepid
[17:45] <asac> niki: err. i mean if you could use the exact same config and still select your access points in the NM menu
[17:45] <asac> on hardy
[17:45] <niki> asac: well I haven't been able to get it to associate with an ad-hoc network yet, that is why I have the entry in interfaces.
[17:46] <niki> I bougth this lappy some months ago, and went strait to intrepid, so actually don't know
[17:47] <asac> niki: ok. then thats a problem of you ;)
[17:47] <asac> niki: currently every device configured in interfaces is unmanaged in nm
[17:47] <asac> niki: you can do adhoc stuff in NM directly
[17:47] <jcastro> sebner: it's been imported
[17:47] <asac> not sure why you use interfaces
[17:47] <asac> jcastro: everything?
[17:47] <jcastro> sebner: it needs to be shuffled around namespace wise
[17:47] <asac> jcastro: is the "master" project set up?
[17:47] <asac> oh
[17:47] <jcastro> no, I never got a response about that
[17:48] <jcastro> "chromium" is importing though
[17:48] <niki> hehe, yeah, I know, had to "skip" hardy because the wireless card wasn't supported, support was first added in 2.6.27
[17:48] <asac> jcastro: jcastro you mean "chrome"?
[17:48] <niki> ^ asac
[17:48] <asac> jcastro: we really need all parts. otherwise that single import isnt worth much ;)
[17:48] <jcastro> yeah it needs to be renamed
[17:48] <asac> jcastro: could you ping lp folks again?
[17:48] <jcastro> asac: yeah
[17:49] <fta> sebner, i follow chromium quite closely
[17:49] <asac> jcastro: please dont rename it to chromium ;) ... chromium-project is the "main" project.
[17:49] <asac> and chrome/ was a subtree
[17:50] <niki> asac: I'll comment out wlan0, and reboot to see what happens, i'll be back in about 10 15 min.
[17:50] <sebner> jcastro: fta : already building on linux?
[17:50] <fta> sebner, but there's not much activity for linux, just 1 or 2 commits a week to build various small things already in the tree for linux
[17:50] <jcastro> sebner: hahahaha not even close.
[17:50] <sebner> rofl
[17:50] <sebner> jcastro: it'S opensource. fix it :P
[17:50] <fta> not, most of the code remains to be written/ported
[17:51] <fta> -not+no
[17:51] <sebner> and now .. who kicks google's ass to do that?
[17:51] <niki> brb...
[17:52] <fta> i think they are working on it internally, it's just not public yet
[17:52] <asac> yeah ... most likely throwing stuff over the wall ;)
[17:53] <shirish> asac: are you guys talking about google chrome or something else altogether?
[17:53] <fta> chromium
[17:54] <Jazzva> asac, ping
[17:54] <shirish> fta: what is chromium?
[17:54] <asac> shirish: chromium ... yes
[17:54] <asac> Jazzva: ?
[17:54] <fta> chromium =  google chrome minus branding and some features
[17:55] <asac> Jazzva: i think MOTU freeze will start on 23rd ;) ... whatever we want to get in extension wise should be done soonish ;)
[17:55] <shirish> fta: ah, ok cool.
[17:55] <asac> Jazzva: also a review of the app-install-data ;) do you know how many changes we have in there?
[17:55] <fta> http://blog.chromium.org/2008/10/google-chrome-chromium-and-google.html
[17:56] <Jazzva> asac, is this procedure still right for getting Profile dir? http://developer.mozilla.org/En/Code_snippets/File_I%2F%2FO , section "Getting special files"? I tried it two nights ago in order to fix foxyproxy, but it didn't work, I tested with file.path, but it didn't write anything
[17:56] <Jazzva> asac, 23rd? Oh... that soon. I'll be quick :)
[17:56] <asac> Jazzva: yes thats correct
[17:56] <asac> Jazzva: you have the diff you tried?
[17:57] <Jazzva> asac, app-install-data will have removal of mime-type for firefox-2 extensions. And there should be few files added for new extensions
[17:57] <Jazzva> asac, no. It's a one line change, I'll paste it now
[17:58] <suzhe> hello jorendorff
[17:58] <jorendorff> hi
[17:58] <jorendorff> So, we were discussing https://bugs.launchpad.net/ubuntu/+source/xulrunner-1.9/+bug/286906
[17:58] <jorendorff> And I think a big part of the question is whether the ubuntu moz team *wants* to provide a binary ABI that's stable over time
[17:59] <suzhe> asac: jorendorff is a developer from spidermonkey team.
[17:59] <jorendorff> a policy question I know nothing about, hoping the folks here can help
[17:59] <jorendorff> (just a developer, but hoping I can help)
[18:01] <asac> jorendorff: well. the ubuntu moz team doesnt have a will on its own. its just that when developers want to develop against mozjs.so they want that lib to be available in the distro
[18:01] <asac> but unless there are no ABI/API guarantees/policies/procedures, we cannot ship libraries in decent fashion
[18:01] <jorendorff> asac: Sorry if I don't understand the issues properly -- I really know next to nothing about packaging
[18:02] <Jazzva> asac, http://paste.ubuntu.com/60599/
[18:02] <asac> jorendorff: for instance. we currently build libmozjs.so as part of the xulrunner
[18:02] <asac> jorendorff: there libmozjs.so is shipped in pkglibdir ...
[18:02] <Jazzva> I think that's the place where it gets the settings dir, and then it checks it for foxyproxy.xml. If it doesn't exist, it creates new file, if it exists it reads from it.
[18:02] <asac> this means de-facto that those libs are not available for public consumption ... just for internal use (e.g. xulrunner itself)
[18:03] <asac> jorendorff: when it comes to decide whether we can make a lib available in libdir /(e.g. /usr/lib) we usually need the lib to use -version-info (or something similar if your lib doesnt use libtool)
[18:04] <asac> which properly indicates abi/api compatibility
[18:04] <asac> OR we need a guarantee that there will be no abi/api breakage as long as libmozjs.so is shipped under that name
[18:04] <asac> the latter is what nspr and nss are doing
[18:04] <jorendorff> ok, I'll paste this into a bug on our end.
[18:05] <jorendorff> It looks like we are at least weeks away from providing either of those.
[18:05] <suzhe> asac: In this case, can pkglibdir act as the version info?
[18:06] <jorendorff> suzhe: Right now, my guess is, nobody currently wants to guarantee that there will even be a libmozjs.so file there
[18:06] <jorendorff> much less anything about its remaining stable in any way over time
[18:07] <jorendorff> nobody meaning neither the Ubuntu moz team nor the moz xulrunner team nor the moz spidermonkey team
[18:07] <suzhe> jorendorff: it's guaranteed by pkg-config file mozilla-js.pc
[18:07] <jorendorff> Well, that is interesting
[18:07] <jorendorff> where does that file come from?
[18:07] <suzhe> xulrunner-1.9-dev package.
[18:08] <suzhe> and I believe it comes from upstream.
[18:08] <jorendorff> ah, looks like that's coming from xulrunner
[18:08] <suzhe> content of mozilla-js.pc is pasted in that bug report.
[18:09] <jorendorff> I saw it; it's coming from here http://mxr.mozilla.org/mozilla-central/source/xulrunner/installer/mozilla-js.pc.in
[18:10] <jorendorff> But it looks suspicious to me.  I'm pretty sure xulrunner just takes whatever version of SpiderMonkey is in the tree, so it seems wrong to slap %MOZILLA_VERSION% on that (since the two are ostensibly independently versioned)
[18:11] <suzhe> jorendorff: will xulrunner 1.9 sticks to a specific version of spidermonkey?
[18:13] <jorendorff> No, they take whatever version of SpiderMonkey is in the tree -- i.e. the latest
[18:14] <jorendorff> For all I know the ABI may remain compatible from 1.7 to trunk, for features exposed in jsapi.h
[18:14] <jorendorff> but if so, as much by coincidence as anything else
[18:15] <jorendorff> I know that other functions, the ones not exposed in jsapi.h, tend to come and go.
[18:15] <suzhe> jorendorff: do you have any policy to maintain ABI compatibility for features exposed in jsapi.h?
[18:16] <jorendorff> no
[18:16] <asac> suzhe: at this point the pkglibdir acts as version info
[18:16] <asac> suzhe: just that it doesnt help for you as it changes on each and every upstream release
[18:16] <jorendorff> recently we considered changing jsval from pointer-sized to a 64-bit type, for example.
[18:16] <asac> (which is intended just for things like this)
[18:16] <jcastro> asac: now is the time to sign up! https://wiki.ubuntu.com/UbuntuOpenWeek/Prep
[18:16] <niki> asac: no luck, but I did get a segmentation fault from nm
[18:16] <asac> niki: no luck with what?
[18:16] <asac> adhoc?
[18:17] <asac> adhoc doesnt work for most modern chipsets i think
[18:17] <asac> (funnily)
[18:17] <niki> asac: the interface didn't show up
[18:17] <asac> niki: remove everything from interfaces
[18:17] <niki> asac: well i'm running adhoc atm
[18:17] <asac> niki: it will show up for sure after reboot
[18:17] <asac> niki: good to know ;) .... wlang?
[18:17] <asac> iwlang ;)
[18:18] <niki> yep
[18:18] <asac> thats good news
[18:18] <asac> didnt work for me on my plain 4965 here
[18:18] <suzhe> asac: then, my question is: in which xulunner version range the ABI will keep stable? 1.9.x.x or 1.9.0.x?
[18:18] <asac> suzhe: we dont know anything. and there are no upstream guarantees. which means we only guarnatee that its stable for each upstream release
[18:18] <niki> see my paste bin from before, that sets my wlan up for adhoc
[18:18] <asac> suzhe: which is what we reflect by shipping stuff that way
[18:19] <asac> (which actually is the official upstream way to ship it ... e.g. run make install on unpatched sources)
[18:19] <asac> everyone who patches that out of the build system hides the problem and will make it less likely to be fixed
[18:19] <niki> asac: especially, see the pre-up command i have, I need that else adhoc won't work
[18:19] <asac> becaues everybody just accepts that people will "just" linke -rpath and then prey ;)
[18:20] <asac> niki: you can configure in NM that adhoc should share the NM
[18:20] <suzhe> asac: Hmm, then my package must be rebuilt every time when xulrunner upgrades. It's really bad.
[18:20] <asac> niki: NM should support it out of box
[18:20] <asac> niki: its just that it doesnt even work manually here
[18:20] <asac> e.g. with iwconfig only for instance
[18:21] <niki> I did the setup in iwconfig before doing it in ifupdown
[18:21] <asac> suzhe: right. but thats what upstream suggests. we need to convince spidermonkey developers to take over responsibility and make a properly versioned library out of it
[18:21] <suzhe> jorendorff: Can you help fix this issue from upstream, by adding version info to libmozjs.so?
[18:21] <asac> or release a policy ... or what ever
[18:21] <niki> but ifupdown needs pre-up iwconfig wlan0 mode ad-hoc
[18:22] <asac> suzhe: most likely thats not feasible for them they rather want to go the "strict" policy road and dont break abi/api until they go for libmozjs2.so
[18:22] <jorendorff> asac: OK, I am convinced you guys are doing the right thing.  I'm going to ask the xulrunner guys; surely someone has given this some thought
[18:22] <asac> etc.
[18:22] <jorendorff> we need a policy
[18:22] <asac> jorendorff: well. this has been long discussed i think. but you can try
[18:22] <asac> jorendorff: the xulrunner position is that caring about abi/api isnt necessary as xpcom will properly protect stuff
[18:23] <asac> jorendorff: but you never know ;)
[18:23] <jorendorff> yeah, I think the tendency is away from binary compatibility altogether and toward JS-only components and stuff, but I don't know how that fits in with SpiderMonkey
[18:23] <jorendorff> libmozjs that is
[18:23] <asac> only thing i can say is that without any of these mechanisms its really hard to ship libmozjs.so ... which would be a shame imo
[18:24] <jorendorff> Well -- we have some nuts and bolts we have to take care of, and believe it or not we are working on it...
[18:24] <jorendorff> but boy has it been a long haul  https://bugzilla.mozilla.org/show_bug.cgi?id=97954
[18:24] <asac> jorendorff: at best try to listen to what bsmedberg thinks. and also how he thinks libmozjs.so can be properly shipped in such a way that it can become a proper top-level lib on linux systems
[18:24] <niki> asac: the other end of the adhoc network is my firewall, which too is configured with ifupdown, but watch out, i had been trying to configure the interface on the firwall for weeks, with no luck, then one day I had to reboot the machine, and by magick adhoc worked on it, so my guess is that when you configure/deconfigure it leaves some garbage in the interface config or something like that.
[18:24] <suzhe> in my opinion libmozjs.so is really important for 3rd applications who wants to interpret and run javascript.
[18:24] <asac> jorendorff: i would be happy to get more ideas from him ;)
[18:25] <jorendorff> excellent -- I will do that
[18:25] <asac> niki: yeah. thats what i ment. for ages adhoc didnt work on modern intel
[18:25] <jorendorff> keep in mind that libmozjs as a library for applications that want a scripting engine
[18:25] <niki> asac: I'll try to empty the interfaces file, after filing the nm crash
[18:25] <asac> if it works now fine.
[18:25] <asac> niki: but then NM should work ttoo
[18:25] <asac> niki: give it a try
[18:25] <jorendorff> is an extremely different thing from libmozjs for things that want to hook into mozilla
[18:25] <asac> niki: thanks
[18:25] <niki> asac: both ends is intel fyi.
[18:26] <asac> niki: after empying you just need to restart ... or sudo killall nm-system-settings
[18:26] <niki> ok, ahould I also remove the lo interface ?
[18:26] <asac> jorendorff: right. i am all with you. imo mozjs should become a real project with its own build system and a decent library versioning policy
[18:27] <asac> jorendorff: and then xulrunner/firefox should be able to use mozjs from system-library
[18:27] <asac> just as it uses gtk now (e.g. with proper minimal versoin requirements and such)
[18:27] <jorendorff> the latter will take some selling :)  but I'm all with you on the former.
[18:27] <asac> of course upstream firefox builds could still use their own in-binary-blob libmozjs if they dont want to rely on that
[18:28] <asac> jorendorff: well. do the former and i am sure we can get the latter supported in the build-system
[18:28] <asac> thats the easier task ;)
[18:28] <asac> (e.g. making xulrunner use system-mozjs)
[18:33] <niki> asac: regarding this bug https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/269474 , I now have one more crash (exactly the same)
[18:35] <suzhe> asac: do you have a workable solution for this issue at current stage?
[18:36] <asac> niki: do you have the the syslog for this crash too?
[18:36] <asac> suzhe: i will think about it ... have to run now ... will be back in a few hours
[18:36] <niki> sec
[18:36] <asac> ok have to run ... culater
[18:36] <suzhe> asac: thanks a lot.
[18:37] <asac> suzhe: dont hope too much for now
[18:38] <niki> asac: http://pastebin.com/d3afb58e9
[18:39] <niki> in the first section marked ### NM Restart ###
[18:39] <niki> that is with everything exceplt lo commented out
[18:39] <niki> in interfaces file that is
[18:46] <niki> asac: gonna reboot, with an empty interfaces file, except lo is still defined.
[18:46] <niki> be back shortly
[18:56] <newz2000> hi, are there known probs with todays ff update?
[18:56] <newz2000> i.e. ff crashing every time you try to open it?
[19:00] <niki> asac: success, nm connected to adhoc here now, with empty interfaces file both wlan0 and eth0 is seen in nm applet, although eth0 wasn't specified in the interfaces file.
[19:01] <niki> but to get nm to connect to my adhoc network I had to run "iwconfig wlan0 mode ad-hoc" in a term, after that it connected on first try
[19:01] <niki> ^ asc
[19:01] <niki> ^ asac
[19:05] <newz2000> my prob seems to be related to firebug. :-( Will investigate further.
[19:26] <fta> asac, why are we dropping other-licenses/7zstub in nobinonly?
[19:31] <asac> fta: because its binonly?
[19:31] <fta> removed `other-licenses/7zstub/src/Windows/Control/Dialog.cpp'
[19:31] <fta> removed `other-licenses/7zstub/src/Windows/Control/Dialog.h'
[19:31] <fta> removed `other-licenses/7zstub/src/Windows/Control/ProgressBar.h'
[19:31] <asac> niki: hmm
[19:31] <fta> removed `other-licenses/7zstub/src/Common/ComTry.h'
[19:31] <fta> removed `other-licenses/7zstub/src/Common/CRC.cpp'
[19:31] <fta> removed `other-licenses/7zstub/src/Common/CRC.h'
[19:31] <fta> removed `other-licenses/7zstub/src/Common/Defs.h'
[19:32] <asac> niki: sounds like a bug in wpasupplicant then
[19:32] <asac> niki: would be interesting to get a syslog after reproducing
[19:32] <fta> we drop the whole thing, not just binaries
[19:32] <niki> asac: reproducing what ?
[19:33] <fta> asac, removed `./js/src/liveconnect/jsj_nodl.c'
[19:35] <fta> [reed], what is other-licenses/7zstub/ used for?
[19:35] <asac> niki: conneting to adhoc without running iwconfig first
[19:35] <asac> fta: i can tell you that
[19:36] <asac> fta: its the stub used to pack the iwndows installer
[19:36] <[reed]> fta: NSIS Installer
[19:36] <[reed]> yeah
[19:36] <[reed]> what asac said
[19:36] <asac> fta: previously there was only a binary ... now there appears to be sources (which is good)
[19:36] <niki> I didn't run iwconfig first, ran it after trying to use default nm
[19:36] <asac> fta: if the binary stuff isnt in there then i dont mind if we ship it in the nobinonly sources.
[19:36] <asac> fta: but we dont need it as we have 7z in the archive anyway
[19:37] <asac> and linux builds dont use it
[19:37] <fta> i would love to see that +nobinonly sig disappear for good
[19:39] <fta> is that a fake ? http://www.engadget.com/2008/10/20/apples-new-macbook-is-mm-mm-goo/
[19:39] <asac> fta: i dont see any benefit from making the version better readable
[19:39] <asac> ;)
[19:39] <niki> asac: do you want a copy of my log ?
[19:39] <asac> niki: i want that as a bug ... attached
[19:39] <niki> sure
[19:40] <asac> niki: 1. reproduce 2. attach complete log of failed attempt
[19:40] <asac> niki: 3. workaround 2. attach complete log after the success
[19:41] <niki> I have that in my current log, tried to associate 2 times before using iwconfig, so I should have what you want ;-)
[19:42] <niki> I'll finish what i'm doing right now, and then clean the log a little, and the upload it
[20:25] <shirish> asac: you still up buddy?
[20:51] <niki> asac: Ok, this is weired, I just rebooted to catch some logs and such for you, but this time it associated the wlan connection automatically without me doing anything
[22:44] <asac> niki: thats expected. once you connect for first time NM will auto connect there when it sees the same AP next time
[23:24] <Jazzva> asac, fta: willing to do a quick and easy upload :)? bug 287253
[23:24] <Jazzva> thanks
[23:27] <Jazzva> noticed that I haven't set deb mail... stupid
[23:28] <Jazzva> everything good now
[23:28] <fta> is it stil open?
[23:28] <fta> still
[23:41] <asac> fta: yes
[23:42] <asac> fta: universe still has normal FFe rules
[23:46] <fta> asac, bug fix doesn't need permission, right?
[23:48] <asac> fta: clearly mark it as such in the changelog and keep changes minimal
[23:49] <asac> i think you have to ping RMs to get it approved, but they wont do a thorough review
[23:49] <asac> there was an announcement mail about this on -devel-announce recently i think
[23:50] <fta> reading https://wiki.ubuntu.com/FreezeExceptionProcess is not clear for bug fix only
[23:51] <asac> fta: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2008-October/000502.html
[23:51] <asac> thtas the announcement of how universe/multiverse are handled during main hard freeze
[23:52] <asac> fta: if in doubt bug sispoty
[23:52] <fta> ok, so 23rd will be the date, i'm still fine without approval
[23:52] <fta> Jazzva, i'll push it
[23:53] <asac> fta: i think just uploading and seeing if archive admins auto approve it within 15 hours or so ...otherwise pinging them
[23:53] <asac> archive adminst -> Release Managers
[23:54] <NCommander> fta, during hard freeze they do
[23:55] <NCommander> BUt you upload normally, and it enters the unapproved queue, someone from motu-release has to kick it into the archive
[23:55] <Jazzva> fta, thanks :)
[23:55] <Jazzva> asac, I'm done with extensions list...
[23:55] <Jazzva> There wasn't much to update...
[23:55] <Jazzva> you can see in the changelog
[23:55] <Jazzva> https://code.edge.launchpad.net/~jazzva/app-install-data-ubuntu/ubuntu.mozilla-extensions
[23:55] <fta> Jazzva, any reason to not add abrowser ?
[23:55] <Jazzva> abrowser?
[23:55] <Jazzva> in MimeType?
[23:55] <asac>   in depends i guess
[23:56] <Jazzva> for diggler?
[23:56] <fta> diggler
[23:56] <asac> or recomends (but then both)
[23:56] <fta> -Depends: firefox-3 | seamonkey-browser
[23:56] <fta> +Depends: firefox | seamonkey-browser
[23:56] <Jazzva> I forgot to do that... I'll upload a new diff
[23:56] <fta> no need, i can add it
[23:58] <asac> i think its depated that extensions must depend on the browser
[23:58] <asac> most likely a recommends is better now tha tthose get auto installed by default
[23:59] <Jazzva> fta, ok. thanks
[23:59] <asac> but i guess we have those depends everwhere and shouldnt start to do something righ tnow


[12:04] <wonko> Not having to unlock my screen twice is definitely worth the trouble I've gone through. :)
[12:55] <wonko> Eickmeyer: https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1845952
[12:55] <wonko> too soon for the bot?
[16:52] <wonko> jackd restarts aren't gone. :(
[19:12] <sirriffsalothp> Hi guys, I'm running on a rog strix motherboard and I'm struggling to fix the boot menu as boot-repair can't work at it due to the legacy/efi/uefi differences... The boot menu comes up fine if I prompt it by pressing F8 on startup, and all seems to work fine, but how can I get the bios to automatically prompt me to the boot menu without having to
[19:12] <sirriffsalothp> press F8 every time I bootup?
[19:26] <M_aD> not a ubuntu studio specific question imho... best to ask in #ubuntu
[19:27] <M_aD> sirriffsalothp: ^
[19:30] <sirriffsalothp> M_aD okay thanks