[05:11] <robotgeek> where do we comment on https://wiki.ubuntu.com/DapperKNetworkmanager
[05:44] <robotgeek> not so good, knetworkmanager hangs my system on a zydas driver. 
[06:20] <Hobbsee> hi Lure - knetworkmanager decided to stop working
[06:24] <seaLne> morning Hobbsee 
[06:24] <Hobbsee> hey seaLne 
[06:24] <robotgeek> Hobbsee: for me too. it doesn't work on wireless. it also crashed my system twice :)
[06:24] <Hobbsee> robotgeek: ouch.  i had it working last night
[06:25] <seaLne> wired is so much less hassell :)
[06:25] <robotgeek> Hobbsee: it works great while switching networks, i think it's a problem with my broadcom
[06:25] <Hobbsee> ah ok
[06:25] <Lure> Hobbsee: really? tried removing knetwrokmanagerrc - it helped me once...
[06:26] <Hobbsee> Lure: yeah, tried that, no fix
[06:26] <Lure> Hobbsee: so what is happening?
[06:29] <Hobbsee> Lure: it says activation
[06:29] <Lure> and the window stayed?
[06:29] <Hobbsee> yes
[06:30] <Lure> I had this once - I have removed kNM from wallet (was not enough) and removing knetworkapplet worked
[06:30] <Lure> Hobbsee: but where is then your password stored?
[06:31] <Hobbsee> Lure: i have no idea
[06:31] <Lure> I have also seen on my system that selection of network to connect is strange
[06:32] <Lure> 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] <Lure> I have connected once to unsecure AP of my neighbour ;-), and now kNM does always this one first
[06:33] <Lure> I had to remove kNMrc to get back to normal
[06:33] <Hobbsee> hehe
[06:33] <Lure> I need to discuss these issues with author - maybe fixes are already there in latest sources
[06:34] <seaLne> has it maybe set a default wireless network?
[06:35] <Lure> seaLne: problem was also that it could not switch back to my primary one anymore...
[06:36] <Lure> Hobbsee, seaLne: can you collect messages from NM and kNM and send with details to my e-mail?
[06:37] <seaLne> sorry i don't use wireless otherwise i'd try it
[06:37] <robotgeek> Lure: i will also do so :)
[06:37] <Lure> seaLne: OK, I though you had problems too and switched back to wired
[06:37] <robotgeek> Lure: it crashed with zydas driver (froze my system)
[06:37] <seaLne> sorry for the confusion
[06:38] <Lure> robotgeek: thanks - we need feedback
[06:38] <Lure> zydas - first time I heard of this...
[06:38] <robotgeek> Lure: yes, i might be unique. i am on powerpc
[06:38] <robotgeek> Lure: i will recompile their latest drivers, and see if it happens again
[06:38] <Lure> even better!
[06:42] <Hobbsee> Lure: :(
[06:43] <Hobbsee> Lure: it no workie...
[06:43] <Hobbsee> cant find a network device
[06:44] <Lure> Hobbsee: again...
[06:44] <Lure> is it possible that something is taking your device over?
[06:44] <Lure> have you checked NM messages? what they say?
[06:44] <Hobbsee> Lure: um, like wpasupplicant?
[06:44] <Lure> yes, or dhclient
[06:47] <robotgeek> Lure: here is the output with broadcom http://kubuntu.pastebin.com/613768
[06:49] <Lure> robotgeek: to which network are you connecting and which security
[06:50] <robotgeek> Lure: to wireless "PMLAN" and wep hex key with open mode
[06:51] <Lure> robotgeek: activation timeouts (20s)
[06:51] <Lure> is it normal for your AP that it takes longer to connect?
[06:52] <robotgeek> Lure: i think it is a problem with the broadcom device
[06:52] <Lure> but does it work w/o NM?
[06:53] <robotgeek> yes
[06:53] <robotgeek> i use a script to connect, plus wlassistant also works
[06:53] <Lure> 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] <robotgeek> but i dont use wpa
[06:54] <Lure> robotgeek: then this is probably it (driver/wpas interaction), however I do not have much experience with WEP anyhow
[06:54] <Lure> I think wpasupplicant takes over all security in NM (I need to verify this)
[06:55] <robotgeek> Lure: thanks for your help, i will try with zydas tommorow and verify if it is problem with card/nm
[06:56] <Lure> robotgeek: that would be great 
[06:56] <robotgeek> cool, i want knm working for my cards :)
[06:59] <Lure> 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] <Lure> is iwlist scan reporting appropriate info for your AP?
[07:00] <robotgeek> lemme check, it used to. 
[07:02] <robotgeek> except for signal quality, everything else seems to be fine
[07:21] <Hobbsee> yay!
[04:51] <superstoned> hey ppl, i have 2 weird problems:
[04:52] <superstoned> - /dev/null is every time i boot unreachable, so i can't login to KDE (have to chmod 777 it)
[04:52] <superstoned> and second, my resolution switches back to 1024x768 after i login in KDE
[04:53] <superstoned> (while i don't even have that as an option in /etc/X11/xorg.conf  under modes)
[04:53] <superstoned> 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] <superstoned> should i ask in #kubuntu?
[06:10] <Pygi> Tonio_: you here?
[06:16] <uniq> someone with a ipod and dapper around? 
[06:26] <Lure> Pygi: ping
[06:27] <Pygi> Lure: pong
[06:27] <Lure> have you seen report on madwifi working with new kernel?
[06:27] <Pygi> yup
[06:27] <Lure> I thought that patch is needed for WPA support...
[06:27] <Pygi> that is great ^_^
[06:27] <Pygi> but that's only one patch ^_^
[06:28] <Pygi> report*
[06:29] <Lure> BTW, are madwifi disconnects (scan) supposed to hapen to everybody?
[06:29] <Lure> there is one guy in forums with own version of madwifi which claims everything works with his NM
[06:31] <crimsun> kinda useless to everyone else if he doesn't make it public
[06:32] <Pygi> hm, it needs to be fixed
[06:32] <Lure> crimsun: I have asked him what patches he applied - he was wondering if test NM would still work as good
[06:32] <Pygi> crimsun: we need to look at porting -ng background scanning feature to -old
[06:33] <Lure> Pygi: but I am sensing mixed reports with madwifi - is it possible that it is related to specific chipsets of madwifi
[06:38] <superstoned> uniq: i have a ipod nano and i run dapper
[06:39] <uniq> superstoned: could you please test ipodslave from http://ubuntu.lnix.net/dapper/ ? 
[06:40] <uniq> trying to close https://launchpad.net/distros/ubuntu/+source/ipodslave/+bug/3303
[06:40] <Ubugtu> Malone bug 3303 in ipodslave "ipod:/ does not work" [Normal,Needs info]  
[06:47] <superstoned> hi again
[06:47] <uniq> hi.
[06:48] <superstoned> sorry, i tried a new login, to test some things which didnt work
[06:48] <superstoned> but unlocking my own session doesn't work.
[06:48] <Tm_T> moin
[06:48] <superstoned> any idea whazzup? can you lock and unlock a session?
[06:48] <superstoned> and what did u want with a ipod?
[06:48] <Pygi> Lure: hm ... not sure ...
[06:49] <Pygi> crimsun: where is that guy that claims he has it's own version of madwifi?
[06:49] <Pygi> s/crimsun/Lure
[06:49] <Lure> Pygi: just a second...
[06:51] <Lure> Pygi: http://www.ubuntuforums.org/showpost.php?p=845589&postcount=57
[06:51] <Lure> I have asked him not to upgrade and to post patches used
[06:51] <Pygi> hm, can you please send the url to the mail?
[06:52] <Pygi> I am not able to see now :-/
[06:52] <Lure> Pygi: email address?
[06:55] <Pygi> mario dot danic at gmail dot com
[06:56] <Lure> Pygi: sent
[06:57] <Pygi> THANKS
[06:57] <Pygi> i'll look into it
[07:04] <Tonio_> hello ;)
[07:09] <Lure> Tonio_: hi
[07:09] <Tonio_> Lure: hehe, good news for networkmanager :)
[07:10] <Tonio_> seems there are chances we get it in
[07:10] <Lure> Tonio_: yes, from whom?
[07:11] <Tonio_> http://fridge.ubuntu.com/node/298
[07:11] <Tonio_> Lure: read this
[07:12] <Lure> nice - have not seen that ...
[07:12] <Lure> also reports are improving., still a bit too-fuzzy for my opinion, but mostly driver issues/differences
[07:13] <Tonio_> Lure: the only *real* problem I've seen is Riddell's
[07:13] <Lure> Tonio_: _ion was asking in morning for you - he has some patches (including name change), he would like to get in
[07:13] <Tonio_> driver working but not with networkmanager
[07:13] <Tonio_> Lure: ah ?
[07:13] <Tonio_> great ;)
[07:13] <Lure> Tonio_: PPC is also still unknown (robotgeek will test)
[07:14] <Tonio_> ppc unknown you mean ?
[07:14] <Tonio_> you patch works, so what the point is ?
[07:14] <Tonio_> ho !!! ppc <> ppp ;)
[07:14] <Tonio_> hehe
[07:14] <Lure> Tonio_: I am not sure if NM and drivers on PPC are ready for NM
[07:14] <Tonio_> raphink as ppc but couldn't test, cause no wireless
[07:15] <Tonio_> Lure: well, to be honnest, actually, my preference for the default dapper tool would go to wlassistant
[07:15] <Tonio_> not knetworkmanager
[07:15] <Lure> really?
[07:15] <Lure> I need WPA ;-)
[07:15] <Tonio_> because wlassistant is based on command line actions, uses iwlist, iwconfig
[07:16] <Tonio_> Lure: yes, but we may not have as much problems with wlassistant
[07:16] <Tonio_> my opinion is : have kubuntu with wlassistant installed by default
[07:16] <Tonio_> and have knetworkmanager available in main, but not installed
[07:16] <Lure> I would first like to get latest sources of kNM
[07:16] <Tonio_> although knetwork brings lots of gnome dependancies, because of networkmanager itself....
[07:17] <Lure> do you see NM to be worse than wlassitant for WEP? 
[07:17] <Tonio_> 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] <Lure> most of issues are WPA related (wpasupplicant requirements for drivers)
[07:17] <Tonio_> raphink, Riddell: core-dev's opinion ?
[07:17] <raphink> on?
[07:17] <Lure> I am fine if we get NM just in universe
[07:18] <Tonio_> Lure: I'm seeing wlassistant working as long as iwlist and iwconfig are working :)
[07:18] <Tonio_> knetworkmanager doesn't work that way
[07:18] <Tonio_> Lure: look at Riddell's problem...
[07:18] <Tonio_> Lure: that doesn't happen with wlassistant
[07:18] <Tonio_> Lure: NM cannot go in universe
[07:18] <Tonio_> it is already in main ;)
[07:19] <Tonio_> and latest version will go in main or die :)
[07:19] <Lure> Tonio_: most of the problems I have seen in forums/irc were releated to config issues 
[07:19] <Tonio_> Lure: yes, wireless drivers is a pain
[07:19] <Lure> and config stuff was caused by different manual hacks people did to make wifi at all work in the first place
[07:19] <Tonio_> Riddell's problem is the only real problem I've seen
[07:19] <Lure> like ndiswrapper, fwcutter,,,
[07:20] <Tonio_> anyway, wlassistant, although not that advanced, allows to use dhcp, fixed IP address etc.....
[07:20] <Tonio_> the only missing thing is wpa
[07:20] <Lure> as I said, I am fine with getting wlassitant as default and kNM in universe
[07:20] <Tonio_> Lure: on my laptop, I hae to use fwcutter, but some strange reason it doesn't work
[07:20] <Lure> I am just concerned if nm-applet will get in for Ubuntu, we will have to have kNM in Kubuntu!
[07:21] <Tonio_> so I had to switch to ndiswrapper, and write a script that each boot rmmods bcm43xx and modprobe ndiswrapper
[07:21] <Tonio_> standard users are not able to do this......
[07:21] <Tonio_> wireless is and will always be a pain with linux
[07:22] <Tonio_> because linux is not as good as because reagarding to drivers and generally hardware management
[07:22] <Tonio_> not as good as windows ;)
[07:23] <Lure> Tonio_: personally, I have switched to Linux because I hate hunting drivers around (but true out-of-the-box is slightly better)
[07:23] <Lure> getting drivers from vendors is pain - one-sto-shop of ubuntu is great. ;-)
[07:28] <Tonio_> Lure: maybe, but when you have a driver to manually install, windows is way better....
[07:29] <Tonio_> right click on the INF file, and choose install.....
[07:29] <Lure> Tonio_: this is why you installed ndiswrapper ;-)
[07:29] <Tonio_> once lure will be able to do this, I will applause :)
[07:29] <Tonio_> Lure: nope, I installed ndiswrapper because linux driver isn't working at all, even with firmwares extracted with fwcutter
[07:29] <Tonio_> ;)
[07:29] <Lure> I just apt-get dist-upgrade and done (my notebook works out of the box)
[07:30] <Lure> have you seen that it was updated in latest kernel?
[07:30] <Tonio_> Lure: when a driver is available, wich is rare.......
[07:42] <Lure> Riddell: what does Mepis announcement really mean for Kubuntu? Are you already working with them?
[08:23] <superstoned> is guidance supposed to remember the resolution i set?
[08:23] <superstoned> (it doesn't, that's why i ask)
[08:23] <_Sime> superstoned: yes, (fixed in 0.6.3)
[08:23] <superstoned> so i should upgrade?
[08:23] <superstoned> is it already in repository?
[08:24] <superstoned> i upgraded less than an hour ago, and just logged in (and had to re-adjust the res)
[08:24] <superstoned> btw randr is not enabled by default, is it? could it?
[08:24] <superstoned> (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] <superstoned> did it by hand, works, yeah. but a noob can't do it...
[08:26] <superstoned> _Sime? 0.6.3 is not yet in kubuntu i guess???
[08:26] <_Sime> superstoned: not yet. RSN.
[08:27] <superstoned> ok
[08:28] <Pygi> Tonio_: ping
[08:28] <Pygi> Lure: ping
[08:29] <Lure> Pygi: pong
[08:29] <Pygi> Lure: you got that post wrongly ;)
[08:29] <Pygi> he doesn't currently have NM installed
[08:29] <Pygi> if he would install it, it would stop workin' properly
[08:29] <Tonio_> Pygi: 
[08:29] <Pygi> Tonio_: does the new package in repo contain the patch I sent you?
[08:29] <Tonio_> Pygi: hi :)
[08:30] <Pygi> Hi Tonio_  ^_^
[08:30] <Tonio_> Pygi: I used latest .tar.Gz version from johan, which apparently contains the patch :)
[08:30] <Tonio_> I'm just updating the wikipages
[08:30] <Pygi> hm, ok then ^_^
[08:30] <Lure> Pygi: you are right ;-) I think I have read too many posts/irc today...
[08:30] <Tonio_> but version stays to 0ubuntu1 and changelog only has one global entry
[08:30] <Tonio_> that's the rule as long as the packages don't go to main
[08:31] <Pygi> Tonio_: yes, I am aware of that ^_^ Not my changes ^_^
[08:31] <Tonio_> Pygi: I know ;)
[08:31] <Tonio_> that's why I emails both of you :)
[08:31] <Pygi> yup, agreed ;)
[08:31] <Pygi> also, I will need your help ^_^
[08:32] <Tonio_> yep ?
[08:32] <Lure> Tonio_: is rename of packages also in?
[08:32] <Pygi> Two of us should look into porting background scanning from -ng to -old
[08:32] <Tonio_> Lure: yes
[08:32] <Tonio_> nm-applet isn't a convenient name for a package
[08:32] <Pygi> otherwise it's not usable enough, and is full of flaws
[08:32] <Tonio_> johan's idea was nice on that point
[08:32] <Pygi> Lure: please do answer that guy on forum
[08:33] <Tonio_> Pygi: which background scanning ?
[08:33] <Tonio_> in knetworkmanager ?
[08:33] <Lure> Tonio_: naming was proposed by debian (mbiebl)
[08:33] <Pygi> Tonio_: In network manager
[08:33] <Tonio_> Lure: okay ;)
[08:33] <Lure> Pygi: I will
[08:33] <Pygi> Lure: k, thanks
[08:33] <Pygi> Tonio_: the n-m core is constantly scanning, and -old doesn't support it
[08:33] <Pygi> so problems arise
[08:33] <Tonio_> Pygi: talkin' about the knetworkmanager scanning ?
[08:33] <Tonio_> ah okay..... known solution to that issue ?
[08:34] <Pygi> Tonio_: no, talking about the madwifi drivers ;)
[08:34] <Pygi> yup, there is solution
[08:34] <Pygi> it's located in -ng 
[08:34] <Tonio_> which is ?
[08:34] <Tonio_> what -ng ?
[08:34] <Tonio_> more details please ;)
[08:34] <Pygi> we should port that part from madwifi-ng to madwifi-old, to support background scanning
[08:34] <Tonio_> ah okay ;)
[08:34] <Pygi> bah ;)
[08:35] <Tonio_> Pygi: why not simply upgrading madwifi globally ?
[08:35] <Pygi> Tonio_: we can't do that .... -ng is higly unstable, and cannot get into dapper
[08:36] <Tonio_> hum k
[08:36] <Tonio_> so we need to extract a diff and apply it as a patch.........
[08:36] <Pygi> huh, no
[08:36] <Tonio_> sounds complicated job for a non coder like me ;)
[08:36] <Pygi> we can't extract entire diff
[08:36] <Tonio_> so what's needed exactly ?
[08:36] <Pygi> we need just the part of background scanning support
[08:37] <Tonio_> hum, that's what I'm saying ;)
[08:37] <Tonio_> I'm not a coder, so that's not an easy trick
[08:37] <Pygi> aha, ok ^__^
[08:37] <Tonio_> I'm not able to do that really....
[08:37] <Pygi> I am coder, so we'll work together on that ^_^
[08:39] <Lure> Pygi: I can also look into that (did quite some kernel coding, but more in FS space)
[08:39] <Pygi> Lure: sure ^_^
[08:40] <Tonio_> I think _ion asked for me about a patch
[08:40] <Tonio_> maybe it is this :)
[08:40] <Tonio_> I need to ask him when he's available
[08:40] <Lure> Pygi: I am only concerned that such patch will be hard to get through...
[08:40] <Pygi> Lure: nah, it'll get throught
[08:42] <Pygi> otherwise, if we don't get the patch, all of our packages are usseles
[08:43] <Pygi> have you responded to the guy on forums?
[08:43] <Lure> I have edited my initial post - noting that he may want to wait for updated l-r-m packages
[08:45] <Pygi> I just asked infinity to build updated l-r-m packages
[08:45] <Pygi> but that won't help
[08:45] <Pygi> we need to make that patch for -olf
[08:45] <Pygi> *old
[08:45] <Lure> but there are many users with madwifi that do not complain about disconnects...
[08:46] <Pygi> still, there are many from opposite side as well
[08:46] <Lure> so what is really the cause of disconnects?
[08:46] <Lure> do you have madwifi (I have ipw2200 - lucky me)?
[08:47] <Pygi> I told you several times already ;)
[08:48] <Pygi> the cause is that n-m scans all the time, but -old doesn't support it
[08:49] <Lure> I know - but whay does it work for some madwifi users, and it does not for others - they all have same driver!
[08:49] <Lure> s/whay/why/
[08:49] <Pygi> magic perhaps? ^_^
[08:50] <Lure> I do not belive in magic - I need facts... ;-)
[08:50] <Lure> Pygi: so you have madwifi and you have that problem?
[08:50] <Pygi> I've tested madwifi on another computer (borrowed athereos card) and the problem is there, that is a fact
[08:51] <Pygi> seveas has the problem as well
[08:52] <Lure> it would help having HW, but I am suprised as most of madwifi users in forums report success
[08:52] <Lure> maybe we need to ask for specific info (which driver version, chipset...) to nail down problem scope
[08:52] <Pygi> then please do so ^_
[08:52] <Pygi> ^_^
[08:52] <Lure> will try...
[08:57] <Tonio_> re
[08:57] <Tonio_> grmpf.... dsl connection problems those days....
[08:58] <Lure> Tonio_: we should get new kNM sources by end-of-week from SuSE guy - he is busy getting RC out
[08:58] <Tonio_> Lure: nice :) did you contact him ?
[08:59] <Tonio_> or do they plan to officially release them on svn ?
[08:59] <Lure> Yes, I am also discussing strange thing observed on my and Hobsee system
[08:59] <Lure> (key issues with wallet/rc file
[08:59] <Tonio_> yes
[08:59] <Tonio_> same here
[08:59] <Tonio_> they don't get in
[08:59] <Pygi> Tonio_: I just asked infinity to build new l-r-m for us
[08:59] <Pygi> btw. about the patch _ion needed you for ...
[08:59] <Tonio_> but I was prompted to let knetworkmanager enter the wallet
[08:59] <Pygi> it was the one I sent you...
[09:00] <Tonio_> Pygi: ah ok ;)
[09:00] <Lure> no SVN yet, but at least another snapshot
[09:00] <Lure> Tonio_: you mean you need to enter WEP/WPA keys for each connect?
[09:02] <Tonio_> Lure: no, that works for me
[09:02] <Tonio_> but I can't find the wep key in kwallet ;)
[09:03] <Tonio_> Lure: are they supposed to be visible ? or are they stored as binary ?
[09:04] <Lure> I think they are binary...
[09:05] <Tonio_> Lure: that explains this ;)
[09:05] <Tonio_> anyway, I don't have your problem :)
[09:05] <Lure> Tonio_: I have seen n-m-gnome, is n-m-kde in the works too?
[09:06] <Lure> currently I get apt-get upgrade reporting that is keeping n-m back.
[09:06] <uniq> 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] <Tonio_> Lure: n-m-kde is knetworkmanager :)
[09:08] <Tonio_> why should we change the name ?
[09:08] <Tonio_> hum.....
[09:08] <Tonio_> you may answer "why not ?" ^_^
[09:09] <Lure> this is what debian have done and Riddell said that we need to follow
[09:09] <Tonio_> okay, doing it right now
[09:09] <Lure> see https://lists.ubuntu.com/archives/ubuntu-devel/2006-March/016646.html
[09:09] <Tonio_> Lure: may I wait for new upstream version to come out maybe ?
[09:09] <Pygi> Tonio_: we can wait for now ^_^
[09:10] <Lure> there is upstream SVN only - no packages yet 
[09:10] <Tonio_> Pygi: I will do that for both libnl and knetworkmanager once we get the new sourcecode
[09:11] <Pygi> Tonio_: agreed ^_^
[09:11] <Pygi> Lure: when can we start lookin' at porting that code for -ng?
[09:11] <Lure> Pygi: did you already located the scan code in -ng? 
[09:11] <Pygi> Lure: nop ^_^
[09:12] <Lure> I first need to get both old and ng code on my system
[09:13] <Lure> Pygi: where is the madwifi-ng source repository?
[09:14] <Tonio_> Lure: what package ?
[09:14] <Lure> Tonio_: ?
[09:14] <Tonio_> Lure: isn't the code in lrm ?
[09:14] <Pygi> Tonio_: the non-alt version (ie: no hardcoded values) of this patch should be merged into n-m
[09:14] <Lure> yes, madwifi, but I need madwifi-ng
[09:14] <Pygi> http://mail.gnome.org/archives/networkmanager-list/2006-January/msg00141.html
[09:16] <Pygi> Tonio_: can you please do it?
[09:17] <Pygi> Lure: to get you going, scanning is located here
[09:17] <Pygi> ieee80211_wireless.c
[09:17] <Tonio_> Pygi: ues, working on it
[09:17] <Pygi> Tonio_: k, thanks
[09:18] <Lure> Pygi: you have to hate these wifi drivers - each one implementing own 802.11 stack....
[09:18] <Lure> ;-)
[09:18] <Pygi> Lure: ;)
[09:20] <Pygi> Lure: -old interrupts connection to do the scan (as told by seveas)
[09:22] <Pygi> and gee, what should we answer on this one?
[09:22] <Pygi> "The sources.list information is wrong, I get a 404."
[09:22] <Pygi> there is no answer to this one
[09:22] <Pygi> lol ;)
[09:23] <Lure> Pygi: maybe the server was down?
[09:23] <Pygi> Lure: nop, higly unlikely
[09:29] <Pygi> Lure: new l-r-m have to be built
[09:29] <Pygi> the old one's doesn't work on fresh install
[09:29] <Pygi> otherwise, it works
[09:30] <Lure> I know
[10:03] <Tonio_> Pygi: the patch doesn't work
[10:04] <Pygi> Tonio_: huh ??'
[10:04] <Pygi> you can't patch or?
[10:04] <Tonio_> no, but once applyed, doesn't build
[10:05] <Lure> Tonio_: not sure if you have seen - _ion is looking for you in ubuntu-devel...
[10:06] <Tonio_> Lure: thanks :)
[10:08] <Pygi> Tonio_: ah, k, then just drop the patch
[10:19] <Tonio_> Pygi: nope, patch still fails....
[10:19] <Tonio_> and this time it is good, I check every letter, and the patch is the same than given on the website :)
[10:19] <Pygi> oh, try to fix it?
[10:20] <Tonio_> I'm looking at this, but I don't much understand I must say
[10:25] <Riddell> mvo: kdm doesn't actually handle languages
[10:26] <Riddell> Lure: where is this mepis announcement?
[10:26] <mornfall> mepis
[10:26] <mornfall> it's mepis day?
[10:26] <mornfall> i just got mail that adept crashes on simplymepis <someversion>
[10:26] <mornfall> i politely sent the guy to burning hell :] 
[10:27] <Lure> Riddell: http://www.mepis.org/node/9454 with quote from Mark
[10:27] <Riddell> uniq: you need to ask for upstream version freeze exceptions for kio-apt and krusader
[10:29] <mornfall> oh well
[10:29] <mornfall> kio-apt
[10:29] <mornfall> ?
[10:31] <Riddell> mornfall: an ioslave to givean html frontend to apt-cache queries
[10:31] <Riddell> 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] <mornfall> is that in main? it could possibly benefit from adept_batch methinks
[10:32] <Lure> Riddell: it can be only good - more effort on KDE
[10:32] <mornfall> Lure: i wish
[10:33] <Riddell> mornfall: apt:/ to try it out, using adept_batch is certainly an interesting idea
[10:34] <mornfall> Riddell: i think i had a discussion about kio-apt with its author (very long time ago)
[10:35] <Riddell> 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] <Lure> 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] <Lure> ;-)
[10:37] <Riddell> no mention of Kubuntu in that announcement I note :(
[10:38] <Lure> Yes, that is bad...
[10:52] <Tonio_> Riddell: can I ask your opinion on wlassistant vs knetworkmanager by default in dapper ?
[10:52] <Tonio_> Riddell: I think networkmanager is not mature enough to go actually....
[10:53] <Tonio_> having knetworkmanager in main, yes, but not by default to me
[10:56] <Tonio_> 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] <Pygi> Tonio_: make it not autostart?
[10:57] <Tonio_> Pygi: hum...... that's not it's purpose I think....
[10:57] <Riddell> Tonio_: we should follow ubuntu in use of network-manager
[10:57] <Pygi> Riddel: ah
[10:57] <Riddell> Tonio_: wlassistant can only do wifi, knetworkmanager can do wired as well
[10:58] <Tonio_> Riddell: hum, sounds logic ;)
[10:58] <Tonio_> Riddell: is ubuntu thinking of using it by default if our current stuff is approved ?
[10:58] <Pygi> Tonio_: most likely...
[10:59] <Tonio_> Riddell: yes, right, but knetworkmanager cannot let you choose your ip parameters
[10:59] <Tonio_> when wlassistant let you do that ;)
[10:59] <Tonio_> Riddell: but I agree we have to follow ubuntu on that point
[10:59] <Riddell> Tonio_: you mean static IP?
[10:59] <Pygi> Tonio_: hack in that functionality
[10:59] <Tonio_> Riddell: yes
[10:59] <Tonio_> Riddell: only dhcp
[10:59] <Riddell> Pygi: adding functionality to network-manager isn't the easiest of things :)
[10:59] <Tonio_> Riddell: hehe
[10:59] <Riddell> suse spent a week just drawing charts of how the thing worked
[10:59] <Pygi> Riddell: yes ...
[11:00] <Tonio_> Riddell: so if ubuntu doesn't use networkmanager by default, then we'll replace kwifimanager by wlassistant, right ?
[11:00] <Pygi> ...but it can still be done...
[11:00] <Tonio_> Pygi: I think it is annoucned for a later version
[11:01] <Riddell> Tonio_: I haven't tested wlassistant yet, but I suspect it's the best option
[11:01] <Pygi> Tonio_: yes, 0.7
[11:01] <Tonio_> Riddell: "just works", yes :)
[11:01] <Lure> Riddell: wlassitant just works - plain simple
[11:01] <Lure> Tonio_: ;-
[11:02] <Lure> Tonio_: ;-)
[11:02] <Tonio_> Lure: hehe
[11:02] <Lure> It just do not have WPA (and WPA is primary reason why NM has problems) ;-)
[11:02] <Tonio_> Lure: it doesn't work as a daemon too, so need to make connection for each boot
[11:02] <Lure> as drivers (like you airo) seems to have problem with it 
[11:02] <Pygi> WPA is not reason why NM have problems
[11:03] <Pygi> the problem is madwifi -old
[11:03] <Tonio_> that means, we would eventually have wlassistant for manual connection and knetworkconf for default boot config
[11:03] <Tonio_> not very convenient, but better than what we had with breezy ;)
[11:03] <Lure> Pygi: yes, scan issue, but modes of operation NM causes several drivers not to respond properly
[11:04] <Lure> for example, Riddell airo does not report any network, even though it works w/o NM
[11:04] <Lure> Tonio_: way better than kwifimanager
[11:05] <Tonio_> Lure: wlassistant ? of course it si better :) kwifimanager is a pain
[11:05] <Tonio_> Lure: I never met someone who succeed in connecting on a network with it, without going in shell dhcping or something
[11:05] <uniq> riddell: ok, i'll drop krusader then. how do i ask for exception for kio-apt ? 
[11:06] <Tonio_> uniq: make a launchpad bug like this one :https://launchpad.net/distros/ubuntu/+source/kdbus/+bug/34341
[11:06] <Ubugtu> Malone bug 34341 in kdbus "UVF Exception 0.8.2 -> 0.8.6" [Normal,Confirmed]  
[11:07] <Tonio_> need a few files too (buildlog etc....)
[11:07] <Lure> Tonio_: what is still to be done on repository of NM in order to all upgrade (and not keep back n-m package)
[11:08] <Riddell> uniq: don't drop krusader, it would be good to get the new vesion in if we can
[11:08] <uniq> riddell: ok, i agree.
[11:08] <uniq> tonio_: buildlog and? 
[11:08] <Riddell> wlassistant has an unintuitive user interface, single click on it to disconnect or connect
[11:09] <uniq> lure: you can test it if you want. http://ubuntu.lnix.net/dapper/krusader/
[11:09] <Riddell> hmm, and Configure dialogue isn't a dialogue
[11:09] <Riddell> and the systray icon doesn't work
[11:10] <Tonio_> uniq: look at the bug I posted, needed files are in
[11:10] <Tonio_> Riddell: configure dialog isn't a dialog ?
[11:10] <Tonio_> don't understand this
[11:11] <Lure> uniq: 1.70 starts faster, or I have wrong feeling?
[11:11] <Riddell> Tonio_: click Options button, it replaces the user interface rather than having a dialogue.  not a big problem just against normal user interface design
[11:11] <Riddell> ksystraycmd doesn't work with kdesu
[11:12] <Tonio_> Riddell: right
[11:12] <Tm_T> ugh
[11:12] <Tonio_> Riddell: I will remove the systray, no pb
[11:13] <Riddell> Tonio_: .desktop file should have  kdesu ksystraycmd  wlassistant   not  ksystraycmd kdesu wlassistant
[11:13] <Tonio_> Riddell: why not kdesu wlassistant ?
[11:13] <Tonio_> did I do that error ?
[11:13] <uniq> lure: I don't know. Haven't used it much lately.
[11:14] <Riddell> Tonio_: yeah, just get rid of the systray stuff, it doesn't do any good
[11:14] <Tonio_> yep
[11:15] <Tonio_> I'm looking at the package, cause I think the .desktop patch wasn't provided by me.... I should have looked at that
[11:15] <Tonio_> aprt from that Riddell, works nice for you ?
[11:29] <_Sime> mornfall: about adept in svn. Is tags.h checked in?
[11:30] <Tonio_> Riddell: if you're using my repo, you can update for corrected wlassistant package
[11:36] <Riddell> _Sime: did you get my notice about guidance yesterday?
[11:36] <_Sime> maybe
[11:37] <_Sime> what was it?
[11:37] <Tm_T> bah, wordpress blahblah
[11:37] <Tm_T> now I have to make my own theme to wordpress too, it seems
[11:38] <Riddell> _Sime: if you open serviceconfig in system settings then click back and open userconfig or the like it crashes, serviceconfig is still making its cache
[11:41] <Lure> Tonio_: [23:07]  <Lure> Tonio_: what is still to be done on repository of NM in order to all upgrade (and not keep back n-m package)
[11:42] <kmon> Tonio_: Hi. I was wondering if you have any plans on including binary packages for amd64 arch on your kubuntu repo *the one with kpowersave, knetworkmanager, etc(
[11:47] <_Sime> Riddell: I see.
[11:47] <_Sime> it crashed here too
[11:49] <uniq> riddell & tonio_ https://launchpad.net/distros/ubuntu/+source/kio-apt/+bug/35921 Any obvious mistakes?
[11:49] <Ubugtu> Malone bug 35921 in kio-apt "UVF Exception 0.11 -> 0.13" [Normal,Unconfirmed]  
[11:51] <Riddell> uniq: you should probably upload the new package to revu
[11:51] <uniq> revu.tauware.de as pre breezy?
[11:54] <Riddell> uniq: it changed at some point, use dput's default
[11:55] <uniq> fqdn = revu.tauware.de
[11:55] <uniq> as in that? 
[11:57] <Riddell> if that's what dput says then yes
[11:58] <uniq> i doubt upload.ubuntu.com will accept me, if by default you refer to the default dput.cf settings.
[11:58] <Riddell> dput.cf has a revu option too
[11:59] <uniq> hmm.. the only revu option i can find in my dput.cf's is the one i've modified myself.
[11:59] <uniq> But i can try to upload.
[12:00] <Riddell> use whatever the wiki page says then
[12:00] <uniq> I will.
[12:02] <uniq> uploaded.