=== Ubugtu [n=bugbot@ubuntu/member/seveas] has joined #kubuntu-devel === jjesse_ [n=jjesse@mail.ftpb.com] has joined #kubuntu-devel === kmon [n=javier@217.Red-80-25-51.staticIP.rima-tde.net] has left #kubuntu-devel ["Kopete] === mario_ [n=mario@83-131-250-18.adsl.net.t-com.hr] has joined #kubuntu-devel === mario_ is now known as Pygi === LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #kubuntu-devel === enfact [n=enfact@c-24-63-70-248.hsd1.ma.comcast.net] has joined #kubuntu-devel === seth [n=seth@ubuntu/member/seth] has joined #kubuntu-devel === LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #kubuntu-devel === hendry [n=hendry@222.106.128.34] has joined #kubuntu-devel === Parkotron [n=parker@fctnnbsc16w-156034209164.nb.aliant.net] has joined #kubuntu-devel === LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #kubuntu-devel === LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #kubuntu-devel [05:11] where do we comment on https://wiki.ubuntu.com/DapperKNetworkmanager [05:44] not so good, knetworkmanager hangs my system on a zydas driver. === LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #kubuntu-devel === LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #kubuntu-devel === hendry [n=hendry@222.106.128.34] has joined #kubuntu-devel === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #kubuntu-devel === Lure [n=admin@clj46-234.dial-up.arnes.si] has joined #kubuntu-devel [06:20] hi Lure - knetworkmanager decided to stop working [06:24] morning Hobbsee [06:24] hey seaLne [06:24] Hobbsee: for me too. it doesn't work on wireless. it also crashed my system twice :) [06:24] robotgeek: ouch. i had it working last night [06:25] wired is so much less hassell :) [06:25] Hobbsee: it works great while switching networks, i think it's a problem with my broadcom [06:25] ah ok [06:25] Hobbsee: really? tried removing knetwrokmanagerrc - it helped me once... === LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #kubuntu-devel [06:26] Lure: yeah, tried that, no fix [06:26] Hobbsee: so what is happening? [06:29] Lure: it says activation [06:29] and the window stayed? [06:29] yes [06:30] I had this once - I have removed kNM from wallet (was not enough) and removing knetworkapplet worked === Hobbsee doenst even use kwallet [06:30] Hobbsee: but where is then your password stored? [06:31] Lure: i have no idea [06:31] I have also seen on my system that selection of network to connect is strange [06:32] it does not select last one, but tries with random (or less secure?) in case that you hve tried to connect to multiple [06:32] I have connected once to unsecure AP of my neighbour ;-), and now kNM does always this one first [06:33] I had to remove kNMrc to get back to normal [06:33] hehe [06:33] I need to discuss these issues with author - maybe fixes are already there in latest sources [06:34] has it maybe set a default wireless network? [06:35] seaLne: problem was also that it could not switch back to my primary one anymore... [06:36] Hobbsee, seaLne: can you collect messages from NM and kNM and send with details to my e-mail? [06:37] sorry i don't use wireless otherwise i'd try it [06:37] Lure: i will also do so :) [06:37] seaLne: OK, I though you had problems too and switched back to wired [06:37] Lure: it crashed with zydas driver (froze my system) [06:37] sorry for the confusion [06:38] robotgeek: thanks - we need feedback [06:38] zydas - first time I heard of this... [06:38] Lure: yes, i might be unique. i am on powerpc [06:38] Lure: i will recompile their latest drivers, and see if it happens again [06:38] even better! === Hobbsee_ [n=Hobbsee@CPE-144-136-113-76.nsw.bigpond.net.au] has joined #kubuntu-devel [06:42] Lure: :( [06:43] Lure: it no workie... [06:43] cant find a network device [06:44] Hobbsee: again... [06:44] is it possible that something is taking your device over? [06:44] have you checked NM messages? what they say? [06:44] Lure: um, like wpasupplicant? [06:44] yes, or dhclient [06:47] Lure: here is the output with broadcom http://kubuntu.pastebin.com/613768 [06:49] robotgeek: to which network are you connecting and which security [06:50] Lure: to wireless "PMLAN" and wep hex key with open mode [06:51] robotgeek: activation timeouts (20s) [06:51] is it normal for your AP that it takes longer to connect? [06:52] Lure: i think it is a problem with the broadcom device [06:52] but does it work w/o NM? [06:53] yes [06:53] i use a script to connect, plus wlassistant also works [06:53] it for sure is not kNM specific - it is either driver (missing support for wpasupplicant) or NM/wpasuplicant (less likely from current experience) [06:54] but i dont use wpa [06:54] robotgeek: then this is probably it (driver/wpas interaction), however I do not have much experience with WEP anyhow [06:54] I think wpasupplicant takes over all security in NM (I need to verify this) [06:55] Lure: thanks for your help, i will try with zydas tommorow and verify if it is problem with card/nm [06:56] robotgeek: that would be great [06:56] cool, i want knm working for my cards :) [06:59] robotgeek: maybe wpasupplicant should not get involved with WEP, but it does in your case as the card may not report proper security mode back [06:59] is iwlist scan reporting appropriate info for your AP? [07:00] lemme check, it used to. [07:02] except for signal quality, everything else seems to be fine === Lure will reboot to try new kernel w/ ipw2200 1.1.1 === Lure [n=admin@clj46-234.dial-up.arnes.si] has joined #kubuntu-devel === Lure survived WPA wireless connect with latest kernel [07:21] yay! === Sime [n=konversa@ip54579d1b.direct-adsl.nl] has joined #kubuntu-devel === Lure [n=luka@external-7.hermes.si] has joined #kubuntu-devel === ubuntulog [i=ubuntulo@trider-g7.fabbione.net] has joined #kubuntu-devel === Topic for #kubuntu-devel: Dapper delayed || https://wiki.kubuntu.org/KubuntuEspresso || https://wiki.ubuntu.com/KubuntuDapperGoals || http://wiki.ubuntu.com/Kubuntu || Join: http://www.last.fm/group/Kubuntu+Developers/ || Kubuntu meeting on #ubuntu-meeting on Thurs, 16th March - 20:00 UTC -- https://wiki.ubuntu.com/Kubuntu/Meetings === Topic (#kubuntu-devel): set by Tonio_ at Sun Mar 19 14:49:31 2006 === faked [n=faked@83-65-238-134.dynamic.xdsl-line.inode.at] has joined #kubuntu-devel === _Sime [n=konversa@ip54579d1b.direct-adsl.nl] has joined #kubuntu-devel === tvo [n=tobi@5354EA9B.cable.casema.nl] has joined #kubuntu-devel === Lure [n=admin@clj46-234.dial-up.arnes.si] has joined #kubuntu-devel === superstoned [n=supersto@168-234.surfsnel.dsl.internl.net] has joined #kubuntu-devel [04:51] hey ppl, i have 2 weird problems: [04:52] - /dev/null is every time i boot unreachable, so i can't login to KDE (have to chmod 777 it) [04:52] and second, my resolution switches back to 1024x768 after i login in KDE [04:53] (while i don't even have that as an option in /etc/X11/xorg.conf under modes) [04:53] any idea where i could look for the /dev/null prob, and where the resolution settings are kept? i was unable to find them in the user directorie (~/.kde/??? nowhere to be found) [04:54] should i ask in #kubuntu? === allee [n=ach@allee.exgal.mpe.mpg.de] has joined #kubuntu-devel === robotgee1 [n=robotgee@host-24-225-190-218.patmedia.net] has joined #kubuntu-devel === LeeJunFan [n=junfan@s64-186-37-84.skycon.net] has joined #kubuntu-devel === apokryphos [i=[U2FsdGV@server2.polaristar.com] has joined #kubuntu-devel === nlindblad [n=nlindbla@user179.217-10-120.netatonce.net] has joined #kubuntu-devel === nlindblad [n=nlindbla@user179.217-10-120.netatonce.net] has left #kubuntu-devel ["Konversation] === Pygi [n=mario@195.29.212.226] has joined #kubuntu-devel [06:10] Tonio_: you here? [06:16] someone with a ipod and dapper around? [06:26] Pygi: ping [06:27] Lure: pong [06:27] have you seen report on madwifi working with new kernel? [06:27] yup [06:27] I thought that patch is needed for WPA support... [06:27] that is great ^_^ [06:27] but that's only one patch ^_^ [06:28] report* [06:29] BTW, are madwifi disconnects (scan) supposed to hapen to everybody? [06:29] there is one guy in forums with own version of madwifi which claims everything works with his NM [06:31] kinda useless to everyone else if he doesn't make it public [06:32] hm, it needs to be fixed [06:32] crimsun: I have asked him what patches he applied - he was wondering if test NM would still work as good [06:32] crimsun: we need to look at porting -ng background scanning feature to -old [06:33] Pygi: but I am sensing mixed reports with madwifi - is it possible that it is related to specific chipsets of madwifi [06:38] uniq: i have a ipod nano and i run dapper [06:39] superstoned: could you please test ipodslave from http://ubuntu.lnix.net/dapper/ ? [06:40] trying to close https://launchpad.net/distros/ubuntu/+source/ipodslave/+bug/3303 [06:40] Malone bug 3303 in ipodslave "ipod:/ does not work" [Normal,Needs info] === superstoned [n=supersto@168-234.surfsnel.dsl.internl.net] has joined #kubuntu-devel [06:47] hi again [06:47] hi. [06:48] sorry, i tried a new login, to test some things which didnt work [06:48] but unlocking my own session doesn't work. [06:48] moin [06:48] any idea whazzup? can you lock and unlock a session? [06:48] and what did u want with a ipod? [06:48] Lure: hm ... not sure ... [06:49] crimsun: where is that guy that claims he has it's own version of madwifi? [06:49] s/crimsun/Lure [06:49] Pygi: just a second... [06:51] Pygi: http://www.ubuntuforums.org/showpost.php?p=845589&postcount=57 [06:51] I have asked him not to upgrade and to post patches used [06:51] hm, can you please send the url to the mail? [06:52] I am not able to see now :-/ [06:52] Pygi: email address? [06:55] mario dot danic at gmail dot com [06:56] Pygi: sent [06:57] THANKS [06:57] i'll look into it === Tonio_ [n=tonio@tonio.planetemu.net] has joined #kubuntu-devel [07:04] hello ;) [07:09] Tonio_: hi [07:09] Lure: hehe, good news for networkmanager :) [07:10] seems there are chances we get it in [07:10] Tonio_: yes, from whom? [07:11] http://fridge.ubuntu.com/node/298 [07:11] Lure: read this [07:12] nice - have not seen that ... [07:12] also reports are improving., still a bit too-fuzzy for my opinion, but mostly driver issues/differences [07:13] Lure: the only *real* problem I've seen is Riddell's [07:13] Tonio_: _ion was asking in morning for you - he has some patches (including name change), he would like to get in [07:13] driver working but not with networkmanager [07:13] Lure: ah ? [07:13] great ;) [07:13] Tonio_: PPC is also still unknown (robotgeek will test) [07:14] ppc unknown you mean ? [07:14] you patch works, so what the point is ? [07:14] ho !!! ppc <> ppp ;) [07:14] hehe [07:14] Tonio_: I am not sure if NM and drivers on PPC are ready for NM [07:14] raphink as ppc but couldn't test, cause no wireless [07:15] Lure: well, to be honnest, actually, my preference for the default dapper tool would go to wlassistant [07:15] not knetworkmanager [07:15] really? [07:15] I need WPA ;-) [07:15] because wlassistant is based on command line actions, uses iwlist, iwconfig === claydoh [n=clay@65.99.186.76] has joined #kubuntu-devel [07:16] Lure: yes, but we may not have as much problems with wlassistant [07:16] my opinion is : have kubuntu with wlassistant installed by default [07:16] and have knetworkmanager available in main, but not installed [07:16] I would first like to get latest sources of kNM [07:16] although knetwork brings lots of gnome dependancies, because of networkmanager itself.... [07:17] do you see NM to be worse than wlassitant for WEP? [07:17] that's the reason I think it is nicer to have wlassistant in dapper and investigate and work strong for knetworkmanager in dapper+1 [07:17] most of issues are WPA related (wpasupplicant requirements for drivers) [07:17] raphink, Riddell: core-dev's opinion ? [07:17] on? [07:17] I am fine if we get NM just in universe [07:18] Lure: I'm seeing wlassistant working as long as iwlist and iwconfig are working :) [07:18] knetworkmanager doesn't work that way [07:18] Lure: look at Riddell's problem... [07:18] Lure: that doesn't happen with wlassistant [07:18] Lure: NM cannot go in universe [07:18] it is already in main ;) [07:19] and latest version will go in main or die :) [07:19] Tonio_: most of the problems I have seen in forums/irc were releated to config issues [07:19] Lure: yes, wireless drivers is a pain [07:19] and config stuff was caused by different manual hacks people did to make wifi at all work in the first place [07:19] Riddell's problem is the only real problem I've seen [07:19] like ndiswrapper, fwcutter,,, [07:20] anyway, wlassistant, although not that advanced, allows to use dhcp, fixed IP address etc..... [07:20] the only missing thing is wpa [07:20] as I said, I am fine with getting wlassitant as default and kNM in universe [07:20] Lure: on my laptop, I hae to use fwcutter, but some strange reason it doesn't work [07:20] I am just concerned if nm-applet will get in for Ubuntu, we will have to have kNM in Kubuntu! [07:21] so I had to switch to ndiswrapper, and write a script that each boot rmmods bcm43xx and modprobe ndiswrapper [07:21] standard users are not able to do this...... [07:21] wireless is and will always be a pain with linux [07:22] because linux is not as good as because reagarding to drivers and generally hardware management [07:22] not as good as windows ;) === incinerator [n=incinera@82-41-24-164.cable.ubr04.edin.blueyonder.co.uk] has joined #kubuntu-devel [07:23] Tonio_: personally, I have switched to Linux because I hate hunting drivers around (but true out-of-the-box is slightly better) [07:23] getting drivers from vendors is pain - one-sto-shop of ubuntu is great. ;-) [07:28] Lure: maybe, but when you have a driver to manually install, windows is way better.... [07:29] right click on the INF file, and choose install..... [07:29] Tonio_: this is why you installed ndiswrapper ;-) [07:29] once lure will be able to do this, I will applause :) [07:29] Lure: nope, I installed ndiswrapper because linux driver isn't working at all, even with firmwares extracted with fwcutter [07:29] ;) [07:29] I just apt-get dist-upgrade and done (my notebook works out of the box) [07:30] have you seen that it was updated in latest kernel? [07:30] Lure: when a driver is available, wich is rare....... === LeeJunFan_ [n=junfan@s64-186-37-84.skycon.net] has joined #kubuntu-devel [07:42] Riddell: what does Mepis announcement really mean for Kubuntu? Are you already working with them? === Tonio_ [n=tonio@tonio.planetemu.net] has joined #kubuntu-devel === superstoned [n=supersto@168-234.surfsnel.dsl.internl.net] has joined #kubuntu-devel === superstoned [n=supersto@168-234.surfsnel.dsl.internl.net] has joined #kubuntu-devel === nlindblad [n=nlindbla@user179.217-10-120.netatonce.net] has joined #kubuntu-devel === nlindblad [n=nlindbla@user179.217-10-120.netatonce.net] has left #kubuntu-devel ["Konversation] === Lure [n=admin@clj46-234.dial-up.arnes.si] has joined #kubuntu-devel === superstoned [n=supersto@168-234.surfsnel.dsl.internl.net] has joined #kubuntu-devel [08:23] is guidance supposed to remember the resolution i set? [08:23] (it doesn't, that's why i ask) [08:23] <_Sime> superstoned: yes, (fixed in 0.6.3) [08:23] so i should upgrade? [08:23] is it already in repository? [08:24] i upgraded less than an hour ago, and just logged in (and had to re-adjust the res) [08:24] btw randr is not enabled by default, is it? could it? [08:24] (just found out how to enable it, after a long search - its nowhere to be found). and how do i get the nvidia driver instead of nv with guidance? [08:25] did it by hand, works, yeah. but a noob can't do it... [08:26] _Sime? 0.6.3 is not yet in kubuntu i guess??? [08:26] <_Sime> superstoned: not yet. RSN. [08:27] ok === Pygi [n=mario@83-131-240-108.adsl.net.t-com.hr] has joined #kubuntu-devel [08:28] Tonio_: ping [08:28] Lure: ping [08:29] Pygi: pong [08:29] Lure: you got that post wrongly ;) [08:29] he doesn't currently have NM installed [08:29] if he would install it, it would stop workin' properly [08:29] Pygi: [08:29] Tonio_: does the new package in repo contain the patch I sent you? [08:29] Pygi: hi :) [08:30] Hi Tonio_ ^_^ [08:30] Pygi: I used latest .tar.Gz version from johan, which apparently contains the patch :) [08:30] I'm just updating the wikipages [08:30] hm, ok then ^_^ [08:30] Pygi: you are right ;-) I think I have read too many posts/irc today... [08:30] but version stays to 0ubuntu1 and changelog only has one global entry [08:30] that's the rule as long as the packages don't go to main [08:31] Tonio_: yes, I am aware of that ^_^ Not my changes ^_^ [08:31] Pygi: I know ;) [08:31] that's why I emails both of you :) [08:31] yup, agreed ;) [08:31] also, I will need your help ^_^ [08:32] yep ? [08:32] Tonio_: is rename of packages also in? [08:32] Two of us should look into porting background scanning from -ng to -old [08:32] Lure: yes [08:32] nm-applet isn't a convenient name for a package [08:32] otherwise it's not usable enough, and is full of flaws [08:32] johan's idea was nice on that point [08:32] Lure: please do answer that guy on forum [08:33] Pygi: which background scanning ? [08:33] in knetworkmanager ? [08:33] Tonio_: naming was proposed by debian (mbiebl) [08:33] Tonio_: In network manager [08:33] Lure: okay ;) [08:33] Pygi: I will [08:33] Lure: k, thanks [08:33] Tonio_: the n-m core is constantly scanning, and -old doesn't support it [08:33] so problems arise [08:33] Pygi: talkin' about the knetworkmanager scanning ? [08:33] ah okay..... known solution to that issue ? [08:34] Tonio_: no, talking about the madwifi drivers ;) [08:34] yup, there is solution [08:34] it's located in -ng [08:34] which is ? [08:34] what -ng ? [08:34] more details please ;) [08:34] we should port that part from madwifi-ng to madwifi-old, to support background scanning [08:34] ah okay ;) [08:34] bah ;) === Tonio_ doesn't understand with only 20% required informations provided :) [08:35] Pygi: why not simply upgrading madwifi globally ? [08:35] Tonio_: we can't do that .... -ng is higly unstable, and cannot get into dapper [08:36] hum k [08:36] so we need to extract a diff and apply it as a patch......... [08:36] huh, no [08:36] sounds complicated job for a non coder like me ;) [08:36] we can't extract entire diff [08:36] so what's needed exactly ? [08:36] we need just the part of background scanning support [08:37] hum, that's what I'm saying ;) [08:37] I'm not a coder, so that's not an easy trick [08:37] aha, ok ^__^ [08:37] I'm not able to do that really.... [08:37] I am coder, so we'll work together on that ^_^ === faked [n=faked@85-124-45-10.dynamic.xdsl-line.inode.at] has joined #kubuntu-devel [08:39] Pygi: I can also look into that (did quite some kernel coding, but more in FS space) === toma_ is now known as toma [08:39] Lure: sure ^_^ [08:40] I think _ion asked for me about a patch [08:40] maybe it is this :) [08:40] I need to ask him when he's available [08:40] Pygi: I am only concerned that such patch will be hard to get through... [08:40] Lure: nah, it'll get throught [08:42] otherwise, if we don't get the patch, all of our packages are usseles [08:43] have you responded to the guy on forums? [08:43] I have edited my initial post - noting that he may want to wait for updated l-r-m packages [08:45] I just asked infinity to build updated l-r-m packages [08:45] but that won't help [08:45] we need to make that patch for -olf [08:45] *old [08:45] but there are many users with madwifi that do not complain about disconnects... [08:46] still, there are many from opposite side as well [08:46] so what is really the cause of disconnects? [08:46] do you have madwifi (I have ipw2200 - lucky me)? [08:47] I told you several times already ;) [08:48] the cause is that n-m scans all the time, but -old doesn't support it [08:49] I know - but whay does it work for some madwifi users, and it does not for others - they all have same driver! [08:49] s/whay/why/ [08:49] magic perhaps? ^_^ [08:50] I do not belive in magic - I need facts... ;-) [08:50] Pygi: so you have madwifi and you have that problem? [08:50] I've tested madwifi on another computer (borrowed athereos card) and the problem is there, that is a fact [08:51] seveas has the problem as well === mvo [n=egon@p54A66471.dip.t-dialin.net] has joined #kubuntu-devel [08:52] it would help having HW, but I am suprised as most of madwifi users in forums report success [08:52] maybe we need to ask for specific info (which driver version, chipset...) to nail down problem scope [08:52] then please do so ^_ [08:52] ^_^ [08:52] will try... === Tonio_ [n=tonio@tonio.planetemu.net] has joined #kubuntu-devel [08:57] re [08:57] grmpf.... dsl connection problems those days.... [08:58] Tonio_: we should get new kNM sources by end-of-week from SuSE guy - he is busy getting RC out [08:58] Lure: nice :) did you contact him ? [08:59] or do they plan to officially release them on svn ? [08:59] Yes, I am also discussing strange thing observed on my and Hobsee system [08:59] (key issues with wallet/rc file [08:59] yes [08:59] same here [08:59] they don't get in [08:59] Tonio_: I just asked infinity to build new l-r-m for us [08:59] btw. about the patch _ion needed you for ... [08:59] but I was prompted to let knetworkmanager enter the wallet [08:59] it was the one I sent you... [09:00] Pygi: ah ok ;) [09:00] no SVN yet, but at least another snapshot [09:00] Tonio_: you mean you need to enter WEP/WPA keys for each connect? [09:02] Lure: no, that works for me [09:02] but I can't find the wep key in kwallet ;) [09:03] Lure: are they supposed to be visible ? or are they stored as binary ? [09:04] I think they are binary... [09:05] Lure: that explains this ;) [09:05] anyway, I don't have your problem :) [09:05] Tonio_: I have seen n-m-gnome, is n-m-kde in the works too? [09:06] currently I get apt-get upgrade reporting that is keeping n-m back. [09:06] riddell: i have updated packages for ipodslave, kio-apt and krusader at http://ubuntu.lnix.net/dapper/ - I would say kio-apt is pretty important for dapper, if not updated the breezy kio-apt will only users search for breezy, hoary and warty stuff at packages.ubuntu.com via apt:/. Krusader is just a update to 1.70.0, ipodslave is a update to fix (not tested, no ipod here) for #3303 (malone). [09:08] Lure: n-m-kde is knetworkmanager :) [09:08] why should we change the name ? [09:08] hum..... [09:08] you may answer "why not ?" ^_^ [09:09] this is what debian have done and Riddell said that we need to follow [09:09] okay, doing it right now [09:09] see https://lists.ubuntu.com/archives/ubuntu-devel/2006-March/016646.html [09:09] Lure: may I wait for new upstream version to come out maybe ? [09:09] Tonio_: we can wait for now ^_^ [09:10] there is upstream SVN only - no packages yet [09:10] Pygi: I will do that for both libnl and knetworkmanager once we get the new sourcecode [09:11] Tonio_: agreed ^_^ [09:11] Lure: when can we start lookin' at porting that code for -ng? [09:11] Pygi: did you already located the scan code in -ng? [09:11] Lure: nop ^_^ [09:12] I first need to get both old and ng code on my system [09:13] Pygi: where is the madwifi-ng source repository? [09:14] Lure: what package ? [09:14] Tonio_: ? [09:14] Lure: isn't the code in lrm ? [09:14] Tonio_: the non-alt version (ie: no hardcoded values) of this patch should be merged into n-m [09:14] yes, madwifi, but I need madwifi-ng [09:14] http://mail.gnome.org/archives/networkmanager-list/2006-January/msg00141.html [09:16] Tonio_: can you please do it? [09:17] Lure: to get you going, scanning is located here [09:17] ieee80211_wireless.c [09:17] Pygi: ues, working on it === faked [n=faked@83-65-238-183.dynamic.xdsl-line.inode.at] has joined #kubuntu-devel [09:17] Tonio_: k, thanks [09:18] Pygi: you have to hate these wifi drivers - each one implementing own 802.11 stack.... [09:18] ;-) [09:18] Lure: ;) [09:20] Lure: -old interrupts connection to do the scan (as told by seveas) [09:22] and gee, what should we answer on this one? [09:22] "The sources.list information is wrong, I get a 404." [09:22] there is no answer to this one [09:22] lol ;) [09:23] Pygi: maybe the server was down? [09:23] Lure: nop, higly unlikely === Parkotron [n=parker@fctnnbsc16w-156034226132.nb.aliant.net] has joined #kubuntu-devel [09:29] Lure: new l-r-m have to be built [09:29] the old one's doesn't work on fresh install [09:29] otherwise, it works [09:30] I know [10:03] Pygi: the patch doesn't work [10:04] Tonio_: huh ??' [10:04] you can't patch or? [10:04] no, but once applyed, doesn't build [10:05] Tonio_: not sure if you have seen - _ion is looking for you in ubuntu-devel... [10:06] Lure: thanks :) [10:08] Tonio_: ah, k, then just drop the patch [10:19] Pygi: nope, patch still fails.... [10:19] and this time it is good, I check every letter, and the patch is the same than given on the website :) [10:19] oh, try to fix it? [10:20] I'm looking at this, but I don't much understand I must say === faked [n=faked@85-124-43-201.dynamic.xdsl-line.inode.at] has joined #kubuntu-devel [10:25] mvo: kdm doesn't actually handle languages [10:26] Lure: where is this mepis announcement? [10:26] mepis [10:26] it's mepis day? [10:26] i just got mail that adept crashes on simplymepis [10:26] i politely sent the guy to burning hell :] [10:27] Riddell: http://www.mepis.org/node/9454 with quote from Mark [10:27] uniq: you need to ask for upstream version freeze exceptions for kio-apt and krusader [10:29] oh well [10:29] kio-apt [10:29] ? [10:31] mornfall: an ioslave to givean html frontend to apt-cache queries [10:31] Lure: groovy. I've only exchanged one e-mail with warren about CUPS not working, I don't expect him to show up on #kubuntu-devel any time soon [10:31] is that in main? it could possibly benefit from adept_batch methinks [10:32] Riddell: it can be only good - more effort on KDE [10:32] Lure: i wish [10:33] mornfall: apt:/ to try it out, using adept_batch is certainly an interesting idea [10:34] Riddell: i think i had a discussion about kio-apt with its author (very long time ago) [10:35] Lure: I'm skepical that we'll get much back from them, but we will see. it's still good news of course [10:36] Riddell: I just thinking that they will have same Ubuntu problems like you do (your cups example is good) and may get addressed faster [10:36] ;-) [10:37] no mention of Kubuntu in that announcement I note :( [10:38] Yes, that is bad... [10:52] Riddell: can I ask your opinion on wlassistant vs knetworkmanager by default in dapper ? [10:52] Riddell: I think networkmanager is not mature enough to go actually.... [10:53] having knetworkmanager in main, yes, but not by default to me [10:56] Riddell: another reason is that knetworkmanager isn't of any use for non-wifi users and it autostarts... while wlassistant needs to be launched manually [10:57] Tonio_: make it not autostart? [10:57] Pygi: hum...... that's not it's purpose I think.... [10:57] Tonio_: we should follow ubuntu in use of network-manager === claydoh [n=clay@65.99.186.76] has joined #kubuntu-devel [10:57]