[00:00] fta: i think its our problem [00:00] cdbs orders might be difference [00:00] ? [02:22] <[reed]> asac: ping [02:36] hello [02:38] 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] asac: you around or is it still too early? [06:07] NCommander: you have email ;) [06:09] our link is fixed as well [06:10] s/our/your [07:25] !info sunbird hardy [07:25] sunbird (source: lightning-sunbird): Sunbird stand-alone Calendar. In component universe, is optional. Version 0.7+nobinonly-0ubuntu2 (hardy), package size 7792 kB, installed size 23212 kB [07:26] !info sunbird intrepid [07:26] sunbird (source: lightning-sunbird): Sunbird stand-alone Calendar. In component universe, is optional. Version 0.8+nobinonly-0ubuntu1 (intrepid), package size 7917 kB, installed size 23908 kB [07:51] its almost 3am :( [08:01] @time new_york [08:01] Current time in America/New_York: October 21 2008, 03:01:25 - Next meeting: Community Council in 3 hours 58 minutes [08:01] Current time in America/New_York: October 21 2008, 03:01:25 - Next meeting: Community Council in 3 hours 58 minutes [08:02] ok im gone maybe ill be back for meeting but i really need sleep === asac__ is now known as asac [11:36] Hello? [11:37] anybody there? [11:43] Does anyone can help handle bug #286906? [11:43] Launchpad bug 286906 in xulrunner-1.9 "Unable to use libmozjs.so in an application, because of library path problem." [Undecided,New] https://launchpad.net/bugs/286906 [13:28] asac: hi :) [13:30] asac: I'm here to know which features are new and documentation ready on https://help.ubuntu.com/community/NetworkManager [13:30] asac: which ones still hold good in ubuntu 8.04 and ubuntu 8.10 and which things are new. [13:42] 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 === shirish1 is now known as shirish [13:53] shirish: wait for a few minutes pleaes ;) [13:54] asac: sure, will do [13:56] 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] :/ [13:57] 1gig of resident memory used on a session that usually only uses 600mb [13:58] it's bouncing around though, up to 1g, down to 948m slowly back up to a gig, down to 946m [13:59] (2.5gb in this machine, there's 100mb not even used yet, so it's not thrashing that I can see) [13:59] I can get 1 click every 3 minutes through [14:00] if I middle click a tab, the windows will go grey, and 3 minutes later (or so) it'll close it [14:00] cwillu: try to disble all your extensions is the first advice i ususally give [14:01] cwillu: if that doesnt help try to disble your adobe flashplugin [14:03] asac: is the practise of adding $USER to netdev still desired or is that deprecated? [14:04] asac: that should have been is the practise of adding $USER to the netdev group still desired or is that deprecated practise? [14:13] shirish: huh? [14:13] shirish: oh because of dhcp? i dont think so. no [14:13] dhcp is run as root now [14:14] shirish: let me check that page now [14:14] 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] shirish: Installation -> maybe we should make it obvious that its installed by default in hardy, intrepid [14:14] right [14:15] asac: hi [14:15] shirish: untick the "Enable this connection" .... thats all outdated, but even before it was called "enable roaming mode" [14:15] asac: did you get change to check my package? [14:15] nxvl: no i didnt get any coins ;) [14:15] :-P [14:16] nxvl: i have two things on my list. then i will do that [14:16] asac: hang there a minute, brother, writing the first thing about hardy and Intrepid. [14:16] shirish: well. so gutsy + hardy the checkbox is called "enable roaming" or something [14:16] asac: ok, did you have the link to the package? [14:16] in intrepid that administration menu doesnt exist anymore [14:16] by default [14:17] you need to install the network-admin thing from gnome to get that gui back [14:17] (usually NM should be able to deal with that now) [14:22] asac: in this version of nm-applet it says "enable networking" [14:22] shirish: sorry. there is confusion [14:22] shirish: previously that dialog in system was the gnome dialog [14:22] thats gone now and replaced with nm connection editor [14:23] shirish: the "configuring section is mostly about the /etc/network/interfaces " section [14:24] asac: can you please first check the installation section, do you think that is correct or incorrect? [14:24] shirish: i really think we cannot keep the documentation for all (dapper - intrepid) on the same page [14:24] asac: the part of ubuntu 8.04 and ubuntu 8.10 installation [14:24] shirish: ok let me lok there [14:25] but note that we should certainly do someting about the configuring section [14:25] especially what to do for old setups [14:25] shirish: i think NM is installed by default since feisty [14:25] 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] asac: ok, what about the bit about the applet, you think that is wrong as well ? [14:26] 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] Preferences -> Sessions [14:27] but i don tihnk we should mention that [14:27] nobody wants to disable it [14:27] asac: right [14:27] shirish: imo. we should state that its installed by default. then we should just document the features [14:27] and add a FAQ or Troubleshooting section [14:27] asac: right [14:27] with the most common pitfalls [14:28] shirish: so the main elements (which would deserve a short intro) are: [14:29] 1. the applet [14:29] 2. the connection editor (which is what you find in System now) [14:29] not sure how to document the applet. usually thats self explaining. to connect to a network, just click on it [14:30] 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] for the connection editor we should do multiple paragraphs: [14:30] asac: right hang on, putting up things as you speak. [14:31] 1. introduce the available connection types (wired/wireless/mobile broadband/VPN) [14:31] 2. document how to create/modify a user connection [14:32] (here we might need a hint that auto created connections are _not_ editable. and modifying them withouth changing names wont be saved) [14:32] 2a. introduce wired/wireless/mobile broadband/ppp tabs [14:33] 2b. introduce ip4settings tab in connection editor (e.g. which type - aka static dhcp, dhcp addresses only, etc.; how to edit routes) [14:34] 3. document how to install vpn support [14:34] 3a. give a quiick overview of the vpn wizards you get in connection editor when the vpn packages are installed [14:34] (not sure if this really needs to be detailed) [14:41] nxvl: do you have test packages in a PPA ? [14:42] 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] asac: yes, in my ppa [14:43] asac: nvalcarcel [14:44] nxvl: so i can take that orig and do a test build and get the exact same result ;) [14:44] ok getting the branch here too [14:45] yes [14:45] 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] shirish: yeah. please save what i wrote though ;) [14:46] asac: write, its there in my logs :) [14:46] shirish: the endable sentence can be dropped. the applet is there to manage your networking from the desktop ;) [14:48] asac: did that [14:48] shirish: configuring is completely outdated. needs to be dropped [14:49] 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] oh sorry [14:49] didnt see that you still split dapper et al [14:49] asac: right, for the moment shall I put it as configuring for old versions? [14:50] asac: I dunno, there may be users who may be using and may need this documentation. [14:50] shirish: hardy + intrepid + _gutsy_ [14:50] shirish: its unfortunate that that documentation still exists [14:50] it made lots of users most likely revert our transition where we removed everything from interfaces automatically [14:50] asac: shouldn't that be gutsy+hardy+intrepid in that order or the reverse ;) [14:51] sure [14:52] 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] asac: by et al you mean Hardy and after that right? [14:54] nxvl: you didnt add the .desktop file to the branch [14:54] please do that ;) [14:54] shirish: yes [14:57] 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] asac: mm i forgot tu push that change [14:57] asac: one second [14:58] shirish: you still have "ts used to enable or disable the nm-applet for that session. " [14:58] thats just not th epurpose of the applet [14:58] the purose is to "manage and activate/deactive your network connections" [14:58] asac: k, pushed [14:59] asac: right [14:59] asac: what it should be saying, its used to disable or enable networking for the session? [14:59] asac: ah, ok didn't see that last sentence, doing it [15:01] shirish: ok and "Specifically for Hardy and latter," would be "For intrepid or later, ..." [15:02] shirish: TBD means ... to be defined. we should replace that with the link to the troubleshooting section when we have that ;) [15:02] asac: ok cool. [15:03] shirish: imo we shouldnt really make a single document out of it for NM 0.7 [15:03] i mean everything below is completely outdated too [15:03] i mean everything below is completely outdated t [15:03] oops [15:03] ;) [15:03] no issues. [15:06] asac: corrected the former, now what about suspend support, that's also outdated/deprecated as far as Hardy, Intrepid is concerned? [15:07] shirish: i am not even sure how this applies anywhere [15:07] most likely its just dapper and feisty [15:07] but cant tell for sure [15:07] asac: so will put it like that, dapper and feisty (atleast the headings) [15:07] 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] shirish: then we can keep the document in the state as it was before [15:08] (even though its inaccurate for a bunch of things for a bunch of things) [15:08] ;) [15:08] 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] asac: how do I do that? Do you want me to create a new page or how? [15:09] shirish: yes. i think we should make one main document that just states: [15:09] documetnation for network manager before 0.7 (dapper,feisty, gutsy, hardy) can be found here: ... [15:09] and for network manager 0.7 (intrepid, and later) can be found here: [15:09] asac: ah ok, that is cool. [15:10] shirish: at least i think that makes sense [15:10] asac: but then this page also needs to be renamed, ok making a new page. [15:15] nxvl: looks good. a final release commit would have helped to identify what was released later though [15:16] nxvl: you can still do that by just running dch -r -Dhardy-security [15:16] or something [15:16] and commit with "RELEASE x.y.z-0ubuntuY to WHATEVERYOURDISTROISCALLED/hardy-security" [15:16] nxvl: ^^ [15:16] nxvl: when that is done i am happy ;) [15:17] our distro is always called hardy [15:17] no -security or -updates [15:17] is always hardy [15:17] asac: have made a page called it networkmanager options https://help.ubuntu.com/community/NetworkManagerOptions is that good enough ? [15:18] asac: but got your point on the release commit [15:18] shirish: err. most likely nobody will look for that [15:18] shirish: imo the top most page should refer to NetworkManager0.6 and NetworkManager0.7 [15:18] nxvl: yeah ... then use "hardy" ;) [15:19] asac: i'm unsure about the versioning schema [15:19] nxvl: i usually say: to ubuntu/intrepid .... you could say to "oem/hardy" [15:19] ;) [15:19] asac: so you want me to integrate this at the NetworkManager doc itself. [15:19] nxvl: just the complete version from the changelog imo [15:19] asac: since i'm having a different base version, but the ubuntu part should stay the same, or change? [15:19] nxvl: you can also move the +nb1 before the +nobinonly [15:19] nxvl: the netbook thin at the end is not needed [15:19] just 8.04.1 should be enough [15:19] asac: is nxvl your new padawan? ^^ [15:20] sebner: intermediate ;) [15:20] kk ^^ [15:20] sebner: kind of, i still don't understand asac'c packaging methods [15:20] :P [15:20] nxvl: who does that .... :P [15:20] right [15:20] asac: oh! ok then [15:21] asac: can you re-check the NetworkManager top-post section, is that good ? [15:23] yeah let me install abrowser agin ;) [15:23] dont have a browser right now [15:24] asac: "abrowser" or "a browser" ^^ [15:25] its abrowser [15:25] hihi [15:31] sebner: hi :) [15:32] 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] asac: using the documentation template, so would have to excuse the stuff not written yet :) [15:35] 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] asac: scratch that last line. [15:36] 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] p [15:37] asac: right, that I should have thought of before. [15:37] asac: I know you care for the baby but when does NM 0.7 gets officially matura? ca? [15:38] 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] maybe its ok for now to link to it from the "main" networkmanager page and keep that at 0.6 [15:39] sebner: never. dcbw said he would hang himself if not released by end of this month [15:39] but given that they now started to do refactoring i doubt that it will happen [15:39] hehe [15:39] kk thx [15:43] asac: https://help.ubuntu.com/community/NetworkManager0.7 that good, the top-most thing? [15:45] shirish: you should say "ATTENTION: if you are use dapper, feisty, gutsy or hardy, read the documentatoin for networkmanager 0.6 [15:45] btw, either NetworkManager (upstream name) or network-manager (package name) please [15:45] shirish: ^^ [15:45] asac: that's what you meant by FAT ;) [15:47] yeah ;) [15:47] shirish: also put the same on the other page for intrepid [15:48] shirish: people will most likely find one of these through google [15:48] so we cannot rely on them reading the url ;) [15:48] asac: right, updated the same. [15:51] asac: did that as well. [15:52] asac: ok now for some info. or introduction of the nm-applet and then nm-connection editor [15:52] asac: know any good content for ^^^ [15:54] what about lightning/iceowl-extension 0.9? [15:56] shirish: i wrote my ideas above ;) [15:56] is there anything that isnt clear :-P [15:56] ? [15:56] MechtiIde: didnt make the train for intrepid. jaunty will get it [15:58] jdstrand: it completely missed that we had a reason to celebrate two days ago ;) [15:58] asac: I know! I'm updating CVEs for feisty now :) [15:58] jdstrand: so here my cheers and hugs for succeeding in providing full security support coverage for feisty ;) [15:59] mission accomplished [15:59] now please let go dapper away :/ [15:59] * jdstrand hugs asac [15:59] re dapper> 8 months for you, 32 for me [16:00] jdstrand: yeah. most likely it doesnt make such a big difference for you ;) [16:00] but it certainly is much appreciated here :) [16:00] heh [16:00] jdstrand: you still will receive a bunch of tarballs on every release [16:00] oh yes, I'm well aware ;) [16:00] the same amount actually ;) [16:03] jdstrand: will 8.04.1 be supported till june or end of april? [16:05] asac: I thought april [16:06] jdstrand: wasnt sure, i rememberd that some said that 8.04 isnt LTS, only 8.04.1 [16:07] asac: I'd like to see that quoted-- I certainly never heard that === fta_ is now known as fta [16:14] mozilla bug 435088 [16:14] Mozilla bug 435088 in XPCOM "Check .autoreg in the GRE directory, too" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=435088 [16:18] good [16:21] asac, i guess we can drop our bzXXX_gre_autoreg.patch [16:22] yeah [16:22] since its similar ;) [16:22] err identical i mean [16:22] not identical at all. but the goal is the same [16:24] fta: ok then i mixed that up. we should verify that then after dropping [16:25] mozilla bug 412610 [16:26] Mozilla bug 412610 in Startup and Profile System "MAXPATHLEN too small for glibc's realpath()" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=412610 [16:27] Hi, is there anyone around to review my intrepid-nomination of bug 286688? [16:27] Launchpad bug 286688 in ubufox "restart notification erroneously keeps appearing after restart" [Undecided,New] https://launchpad.net/bugs/286688 [16:29] maxb: any idea how i can shutdown withput that being rewritten? [16:30] maxb: are you having extensoins installed (besides ubufox obviously) [16:31] 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] 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] 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] and only then discuss what happens on right click [16:34] (e.g. left-click is the main use case) [16:34] 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] 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] shirish: we should later look how we can fix the 0.6 document for gutsy/hardy [16:43] 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] k [16:44] shirish: for now lets focus solely on 0.7 [16:44] let me know ;) [16:51] asac, could you push your ff3 branches ? 3.0.3+nobinonly-0ubuntu2 is not on lp [17:07] suzhe: hi [17:07] hello [17:07] fta: oh yeah. we have a .intrepid branch now ... will push from there to head too [17:07] asac: what's your opinion about bug #286906? [17:07] Launchpad bug 286906 in xulrunner-1.9 "Unable to use libmozjs.so in an application, because of library path problem." [Undecided,Incomplete] https://launchpad.net/bugs/286906 [17:08] asac, at least, update .head, that's what i merge from for 3.1 [17:08] fta: done [17:08] sorry that i forgot [17:08] hmm still pushing up ;) [17:09] seems ftbfs-with-branding-dir is no longer needed, i can't find the root of this patch... [17:09] mozilla Bug 460915 [17:09] Mozilla bug 460915 in General "Build problem when using --with-branding-dir" [Normal,Assigned] http://bugzilla.mozilla.org/show_bug.cgi?id=460915 [17:11] 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] suzhe: well mozjs.so doesnt really have any abi guarantees i think [17:11] which is why we dont provide it in libdir, but in pkglibdir [17:12] fta: yeah [17:12] fta: it was a bug [17:12] (not sure when) [17:12] (not sure if still a problem) [17:12] 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] fta: did i do a lousy comment in commit? [17:13] i don't have enough history on that particular patch [17:14] asac: AFAIK, libmozjs.so keeps backward compatibility since version 160 quite well. [17:15] asac, ok, it appeared in rev2 [17:15] shirish: those nm applet lines should be accompanied by screenshots i guess [17:16] 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] asac: you mean the one where I give the link to the D-Link stuff? [17:16] shirish: no. every line ;) [17:16] asac: damn, ok cool. will try [17:16] asac: And I don't think the abi will be changed in xulrunner 1.9 series [17:17] 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] 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] asac: I'm not sure if there is any policy on that. [17:18] asac: let me have a check. [17:20] 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] niki: if nm-applet is running and NetworkManager you need to restart NetworkManager ... yes. [17:22] s/and NetworkManager/and NetworkManager not/ [17:22] asac: this in on a fresh boot up, so, shouldn't it be started automatically ? [17:23] niki: it should [17:23] niki: so please check if its not running [17:23] if so, post your complete syslog somewhere [17:24] I will [17:26] 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] asac: you just want the systray or the whole desktop there? [17:26] niki: interestee in interfaces are always not-managed by default (same as in gutsy) [17:27] niki: should be "unmanaged" in applet [17:27] 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] 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] 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] suzhe: well. believing is good [17:28] we need a policy or upstream needs to use SONAMEs to express how they change abi/api [17:28] asac: right, ok will work on that. [17:30] 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] niki: try hal-find-by-capability --capability net.80211 [17:31] asac: can you help ask upstream developer about this issue? [17:32] root@niki-laptop:/etc/default# hal-find-by-capability --capability net.80211 [17:32] /org/freedesktop/Hal/devices/net_00_16_ea_7a_d2_8a [17:32] ^ asac [17:32] asac, where did you handle firefox-trunk before you created the bzr branch? [17:32] branch nick: firefox-trunk [17:32] timestamp: Wed 2007-03-21 18:21:52 +0100 [17:32] message: [17:32] initial firefox-trunk debian/ package [17:32] seems to find it fine [17:32] niki: do you see "wirless networks" in the applet at all? have you checked with right clicking that wireless isnt disabled? [17:33] "wirless networks" -> thats a grey text in the applet drop down [17:33] yep, but in the list it just says "device is unmanaged" [17:34] niki: then you have a configuration for that in /etc/network/interfaces [17:34] ok, so I my not have that then anymore ? [17:34] niki: NM _never_ managed devices in /etc/network/interfaces for you [17:35] niki: or maybe ... can you post your interfaces please? [17:35] well sometime ago it kinda ignored the entry in interfaces, so that I could managed it both places [17:35] asac: I think the solution used by opensuse is good enough. [17:35] fta: isnt there a branch for that in firefox project? [17:36] 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] had to have the entry because nm didn't manage to associate with my ad-hoc network [17:36] asac, that's rev2 of all ff3 branches, rev1 being the tarball [17:36] sec, i'll paste it in a sec [17:37] 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] 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] asac: many ubuntu users reported similar issues. [17:38] suzhe: many? ididnt get to know about that yet. [17:38] do you have references? [17:38] fta: maybye https://code.edge.launchpad.net/~mozillateam/firefox/trunk.dev [17:39] fta: i think that "restart" was done because you wanted to get rid of the tarball cruft in the branch [17:39] might be wrong of course [17:39] asac: http://pastebin.com/d5fcc918c [17:39] fta: hmm. thats that branch [17:39] asac, no, we never restarted, this branch starts like all the others [17:40] yeah [17:40] asac: you can search ubuntu libmozjs.so on google. [17:40] asac, i wasn't there yet at that time so i don't know [17:40] suzhe: only see old noise on the first page [17:40] about firefox broken etc. [17:41] fta: most likely i did all at once and imported that [17:42] fta: the firefox-trunk branch nick was just the name of that branch for me locally at that time [17:42] asac: BTW, any progress with your google chrome/chromium import to LP? [17:42] sebner: jcastro would know more ;) [17:43] asac: for example: http://itsiriuscn.yo2.cn/articles/ubuntu%E4%B8%AD%E5%AE%89%E8%A3%85chmsee.html [17:43] jcastro: pingeling :) [17:43] last i know is that we had a pending request to create a "super" project on launchpad [17:43] lol [17:43] damm, your quite busy asac ;-) [17:44] niki: he is always busy so just ignore it ^^ [17:44] niki: so ... you sure you could use wireless in the NM menu? [17:44] in hardy? [17:44] intrepid [17:45] niki: err. i mean if you could use the exact same config and still select your access points in the NM menu [17:45] on hardy [17:45] 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] I bougth this lappy some months ago, and went strait to intrepid, so actually don't know [17:47] niki: ok. then thats a problem of you ;) [17:47] niki: currently every device configured in interfaces is unmanaged in nm [17:47] niki: you can do adhoc stuff in NM directly [17:47] sebner: it's been imported [17:47] not sure why you use interfaces [17:47] jcastro: everything? [17:47] sebner: it needs to be shuffled around namespace wise [17:47] jcastro: is the "master" project set up? [17:47] oh [17:47] no, I never got a response about that [17:48] "chromium" is importing though [17:48] 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] jcastro: jcastro you mean "chrome"? [17:48] ^ asac [17:48]