[01:00] <netstar> How does dapper play video DVDs?
[01:01] <Amaranth> it doesn't
[01:01] <Amaranth> without extra stuff not in ubuntu
[01:01] <netstar> What stuff?
[01:01] <netstar> :P
[01:01] <Amaranth> i can't remember, i watch DVDs on my DVD player :P
[01:01] <Amaranth> this is off-topic for #ubuntu-devel though
[01:02] <netstar> You're right, I'm being lazy
[01:04] <LaserJock> what you watch DVDs? your supposed to be working on Ubuntu ;-)
[01:10] <Amaranth> LaserJock: shh
[01:11] <LaserJock> Amaranth: don't worry I won't tell if you don't
[01:18] <Seveas> Does anyone know intersting upstream projects that use trac for project management?
[01:25] <_lemsx1_> i had to remove all the fglrx packages and force remove the libmesa1 one
[01:25] <_lemsx1_> now everything is fine
[01:26] <Amaranth> _lemsx1_: at least you could remove it, i just helped someone who couldn't remove, reinstall, or anything
[01:31] <_lemsx1_> Amaranth: ouch... well, mv -f always works ;-)
[01:32] <_lemsx1_> does anybody knows if there is any serious bug in mount?
[01:33] <_lemsx1_> i lost my /dev/hdb1 driver (xfs formated) for no particular reason... that's a spare drive, so, it doesn't bother me much
[01:33] <_lemsx1_> when i try to mount it i get a: mount: /dev/hdb1 already mounted or /mnt/shared busy
[01:33] <_lemsx1_> i'll ask in #ubuntu just to see if somebody knows
[01:35] <Fjodor> Anyone with glibc experience. Seems my patch wasn't ready afterall, as debian/rules build fails with an undefined reference
[01:37] <Seveas> Fjodor, I've had my fun with glibc hacking - how big is the patch?
[01:39] <Fjodor> Rather large. Basically, it's Suse's patches from AMD, but taken from a gentoo bug report about adding them to gentoo. I worked out the parts of the patch that didn't make it, made the patch, and now tried debian/rules build. It fails with ref. to __copysign, that I know is defined somewhere in fpu, but it seems that dir isn't touched yet when it fails
[01:40] <Fjodor> I'll be glad to send it to you, if you like
[01:40] <Fjodor> The gentoo page is http://bugs.gentoo.org/show_bug.cgi?id=100289
[01:43] <Fjodor> I've put the patch in http://daimi.au.dk/~u983179/glibc-2.3.6-amd-patches.patch.bz2
[01:45] <Fjodor> It is against the build_tree gotten from debian/rules unpack and debian/rules patch
[01:59] <Fjodor> Seveas: Any ideas?
[02:00] <Seveas> Fjodor, not yet 
[02:01] <Seveas> I'll poke some more at it tomorrow, but don't have an amd64 to test
[02:01] <Seveas> can you put your buildlog online?
[02:01] <Fjodor> Please excuse my impatience. It does not reflect ingratitude :-)
[02:01] <Fjodor> Sure, how?
[02:02] <Fjodor> And if you need a machine, I can give you an account on mine, though it is going offline soon for the night. It's 0202am here
[02:02] <Fjodor> As for how, I mean what file of course
[02:02] <_ion> seveas: Finnish .jp fans on IRC always get provoked when someone uses that as a smiley. 
[02:03] <Seveas> _ion, should I care?
[02:03] <Seveas> Fjodor, same TZ here - i'm off in less than 10 minutes
[02:03] <_ion> seveas: No.
[02:04] <Seveas> _ion, ok 
[02:04] <Fjodor> Fair enough then, but where is the build log saved?
[02:04] <Seveas> dpkg-buildpackge -rfakeroot | tee buildlog
[02:04] <Seveas> dpkg-buildpackge -rfakeroot 2>&1 | tee buildlog
[02:05] <Fjodor> I'll move the patch and upload the log to http://daimi.au.dk/~u983179/glibc
[02:05] <Seveas> noted - off to bed now
[02:05] <Seveas> bye
[02:05] <Fjodor> Bye, and thanks
[02:05] <_ion> Good night.
[02:10] <Fjodor> Hmmm, build-package removes the build-tree dir that I patched. How do I tell it to reapply my patch?
[02:10] <Fjodor> ls
[02:10] <_ion> Does the package use cdbs?
[02:11] <Fjodor> cdbs?
[02:13] <_ion> glibc doesn't seem to use it. (tarball.mk in cdbs uses a 'build-tree' directory, that's why i asked.)
[02:13] <_ion> You should save the diff to debian/patches/number-patchname.patch
[02:13] <_ion> Look at the other patches in that directory.
[02:14] <Fjodor> Only four are with numbers
[02:14] <_ion> The number in the beginning is just a convention. They are applied in an alphabetical order.
[02:15] <Fjodor> I shouldn't add it to 00list.amd64?
[02:17] <_ion> You should do what has been done with the other patches. I haven't looked at the glibc source package, and different packages might use different patch systems. Some use dpatch, etc.
[02:17] <Fjodor> Ok. But thanks
[02:43] <Jamal__> anyone see this? http://digg.com/linux_unix/Ubuntu_Center_Pre-Alpha_Released_-_Web_Based_Ubuntu_Control
[02:44] <_ion> Eww, PHP.
[02:45] <Jamal__> what do you like?
[02:45] <Jamal__> perl?
[02:45] <Jamal__> I gotta go eat
[02:45] <Jamal__> later
[02:47] <_ion> Perl definitely isn't as ugly as PHP, but i like Python and love Ruby.
[02:47] <na7e> he left
[02:48] <na7e> i like ruby myself, too bad it's not as good at being a glue language as python
[02:50] <rob> can someone tell me who maintains xorg currently?
[02:59] <Fjodor> If anyone other than Seveas wants to take alook at this amd64-optimized glibc, look in http://daimi.au.dk/~u983179/glibc
[05:20] <lamont2> "The system adiminstrator has disabled access to the system temporarily."
[05:20] <lamont2> I wouldn't mind that so much if it would turn off eventually
[06:02] <holy_cow> lamont, when does that show up?
[06:03] <lamont> it shows up when you have ldap passwd/shadow/group, and completely break it
[06:03] <holy_cow> aha!
[06:03] <holy_cow> i have yet to try that
[06:03] <lamont> breaking it?  I recommend against that...
[06:03] <holy_cow> naw, testing is good, i got lotsa boxes and vmware instances
[06:21] <lamont> holy_cow: this was my main desktop, you see....
[06:21] <holy_cow> :/ that sux indeed
[10:19] <lifeless> where has makeinfo gone ?
[10:19] <lifeless> oh, nm. my bad, somehow got texinfo uninstalled
[10:38] <desrt> The path 'file:///store_00010001/DCIM/100K7630' is not absolute.
[10:40] <infinity> Looks absolute to me.
[10:40] <desrt> when trying to download pics from the SD card i just bought for my camera
[10:40] <desrt> using the internal memory is quite fine
[10:41] <sivang> morning all
[10:41] <lifeless> desrt: url unaware program
[10:42] <desrt> lifeless; uhm?
[10:42] <lifeless> to a url unaware program file:/// is not absolute
[10:42] <desrt> lifeless; the program generated this url for itself
[10:42] <ajmitch> desrt: the bug is in malone
[10:42] <desrt> ajmitch; awesome.  got a # for me?
[10:43] <lifeless> desrt: score one for that program
[10:43] <ajmitch> desrt: you didn't search for it? :)
[10:43] <ajmitch> bug #34077
[10:43] <Ubugtu> Malone bug 34077 in gthumb "Can't import photos: The path is not absolute"" [Normal,Needs info]  http://launchpad.net/bugs/34077
[10:43] <ajmitch> I'm assuming that's what you're seeing?
[10:44] <desrt> i found it :p
[10:46] <desrt> ajmitch; i searched... but i'm quite ineffective when it comes to launchpad
[10:46] <desrt> i searched for 'path is not absolute' and libgnomeprint and subversion came up :p
[10:49] <desrt> sad but true
[10:49] <desrt> today was fun
[10:49] <desrt> i hacked up an ubuntu livecd for a group project
[11:00] <desrt> man
[11:01] <sivang> desrt: tired?
[11:01] <desrt> yes.
[11:01] <desrt> final presentation tomorrow :p
[11:01] <sivang> sleep tight!
[11:01] <desrt> nite.
[11:16] <holy_cow> goddamit, i'm starting to hate reading peoples opinions about linux/windows/mac/newbuser needs/poweruser needs
[11:17] <Burgundavia> holy_cow: hmm?
[11:17] <holy_cow> its like listening to chicks gossping, none of it makes any sense and none of it is even remotely well thought out, never mind researched
[11:18] <Burgundavia> it is important to respect peoples opinions, as they can tell you important things
[11:18] <holy_cow> Burgundavia, i have been a firm believer in that, my faith is starting to slip :/
[11:18] <Burgundavia> but sometimes people mixed up what they need with what they thyink they need
[11:18] <Burgundavia> and how they think they are going to get what they did
[11:19] <holy_cow> i think that fundamentally humans have processing units between their ears that are not designed for complex thought
[12:22] <Seveas> _ion, *hug*
[12:22] <Seveas> nm+wpa works
[12:22] <giftnudel> where?
[12:22] <Pygi> Seveas: great news ^^
[12:22] <giftnudel> how?
[12:22] <Pygi> Seveas: you could say that to me as well, you know ^^
[12:22] <Seveas> just a quick remark: in your postinst you should do a source /etc/default/wpasupplicant and warn if ENABLED=1
[12:23] <Pygi> giftnudel: wait a lill'...you'll hear all about it later ;)
[12:23] <Seveas> because that will mess up nm
[12:24] <Seveas> now to find the 802.1x patch and apply it
[12:24] <Seveas> because itherwise nm is still useless to me ^_^
[12:25] <Pygi> Seveas: if you find it, please send it to mario dot danic at gmail dot com
[12:25] <Pygi> ok?
[12:25] <Seveas> bien sr, mon ami
[12:26] <siretart> Seveas: is there a wiki dokumenting that?
[12:26] <Pygi> siretart: yup
[12:26] <siretart> Seveas: I'd like to try it out next week, after my test
[12:26] <siretart> where?
[12:26] <Seveas> Pygi, can tell more 
[12:27] <Seveas> ion_ made very nice packages
[12:27] <Pygi> siteart: https://wiki.ubuntu.com/DapperNetworkManager
[12:27] <siretart> thanks
[12:27] <Seveas> you need a new wpasupplicant, new NM/NM-applet and possible a new l-r-m (if you use atheros)
[12:27] <Pygi> siretart, Seveas: but we are still do do a lill' modifications, to the repos and the wiki
[12:28] <Pygi> siretart: the wiki will be updated today, same with repos
[12:28] <siretart> Pygi: I'll join your work on wednesday
[12:29] <Pygi> siretart: k, great...
[12:29] <Pygi> now only Seveas to find that 802.1x patch ;)
[12:30] <Seveas> Pygi, http://rlove.org/log/2006/Feb
[12:31] <Seveas> no, a screenshot 
[12:32] <Seveas> friggen hell
[12:32] <Seveas> it's already in ther
[12:32] <Pygi> Seveas: ah, I was testing new n-m as well ;)
[12:32] <Seveas> this is really, really cool
[12:33] <Pygi> Seveas: now all we have to do is get it into dapper ;)
[12:33] <Pygi> testing, a lot of testing first ofcourse
[12:33] <Seveas> Pygi, I'll be testing WPA and EAP/TTLS 
[12:33] <Pygi> Seveas: k, great ;) I am testing WPA as well ...
[12:34] <Seveas> urgh
[12:34] <Seveas> ok, this sucks: NM constantly scans
[12:34] <Seveas> which is bad in case of madwifi which can't do background scans
[12:34] <Pygi> hm 
[12:34] <Seveas> and thus my connection is gone for a second (kills no connections but is still annoying as hell)
[12:35] <Seveas> madwifi-ng can do background scans
[12:35] <Pygi> perhaps we could write a workaround for that? :-/
[12:35] <Seveas> dunno
[12:35] <Pygi> yup, but we can't use the -ng
[12:35] <Mithrandir> Seveas: you can ask NM to just scan when it doesn't have a connection.
[12:35] <Seveas> Mithrandir, cool - where?
[12:36] <Mithrandir> Seveas: unsure; my laptop is in my backpack and I'm too lazy to go fetch it. :-)
[12:37] <Mithrandir> Seveas: I just know you can make it.  Browse with gconf-editor, possibly?
[12:37] <Seveas> that option should definitely be on by default - more network cards break
[12:37] <Seveas> hmm, sounds like a plan
[12:37] <Seveas> hmm, no n-m in /apps
[12:37] <Mithrandir> maybe we could make it scan when you open the menu?
[12:38] <Mithrandir> (or when it loses the connection)
[12:38] <Seveas> that would be ideal
[12:38] <Seveas> (well, ideally drivers don't break during a scan)
[12:38] <Pygi> Seveas: yup, but we can't really influence the drivers, unless it is possible to write a workaround
[12:39] <siretart> Seveas: upstream still considers madwifi-old to be more stable than madiwifi-ng
[12:39] <Seveas> siretart, no surprise, madwifi-ng is buggy as hell
[12:40] <siretart> I see
[12:40] <Seveas> madwifi bug 444
[12:40] <Ubugtu> Madwifi bug 444 in madwifi: driver "Madwifi does not work with NetworkManager and WPA" [Enhancement,Assigned]  http://madwifi.org/ticket/444
[12:40] <Seveas> (I added trac support to Ubugtu)
[12:40] <siretart> nice
[12:40] <Seveas> and have been swearing for an hour at debbugs 
[12:41] <Mithrandir> why?
[12:41] <Seveas> it is NOT possible to de reliable machine reading
[12:41] <Mithrandir> use the LDAP interface.
[12:41] <Seveas> can't search on ID
[12:41] <Seveas> aba is planning to fix that $soon
[12:42] <Seveas> but in the mean time it's not possible to do reliable machine reading
[12:43] <Seveas> Pygi, hmm - riddle me this
[12:44] <Seveas> nm-applet says wireless strength 38%, netstatus-applet says 79%
[12:44] <tseng> i had to wait a few seconds for nm to catch up with reality
[12:44] <Seveas> or more exactly, always twice as much as nm-applet says
[12:45] <Seveas>           Link Quality=38/94  Signal level=-57 dBm  Noise level=-95 dBm
[12:45] <Seveas> ok, netstatus-applet is weird
[12:45] <Pygi> Seveas: definetly it is ;)
[12:45] <Pygi> netstatus-applet being weird, that is ;)
[12:45] <Seveas> ah well, good riddance
[12:45] <Seveas> with the new icon it's too big anyway
[12:45] <tseng> 0.6.1 from the wiki page works nicely for me, fwiw
[12:46] <Treenaks> Have they fixed the status reporting to be consistent then? (dB vs percentage)
[12:46] <Treenaks> (in-kernel)
[12:46] <Pygi> tseng: yup, great ;) but we need to update the page and repos today ;)
[12:47] <Pygi> once we call for a wider testing, please post all your experiences to the -devel list ^_^ || especially if it doesn't work, and what exactly doesn't work 
[12:48] <Seveas> will do
[12:49] <Pygi> Seveas: thx
[12:50] <infinity> Seveas: If you can backport the background scanning from -ng to -old, I'll (very) happily include it, but I've not had the time to even look at it (and would have no way to test it)
[12:51] <infinity> Seveas: We're also investigating some cleverly hackish ways to ship both -old and -ng (though -old would still be the default for everyone except a select few PCI IDs that just plain NEED -ng)
[12:51] <Pygi> infinity: what's your wiki page, so I could link to it as you are a contributor at dappernm wiki
[12:51] <infinity> Pygi: If I have one, it probably has very ltitle interesting info on it.
[12:51] <Pygi> infinity: ah, kk
[12:51] <siretart> Seveas: you're using madwifi?
[12:52] <infinity> Pygi: https://wiki.ubuntu.com/AdamConrad <-- Very obviously out of date and useless.
[12:52] <siretart> Seveas: then netstat-applet is right. on madwifi, the 38 is not to be read as percentage, but as RSSI. 
[12:53] <Pygi> infinity: hm... perhaps we could include part of -ng code inside the old one, and make an internal switch that we could pass, so it would use -old or -ng, depending on the switch? :-/
[12:54] <infinity> Pygi: Not really doable, no.
[12:54] <Pygi> infinity: yup, I thought so...
[12:56] <Seveas> siretart, ah ok
[12:56] <Seveas> so more is broken in madwifi 
[01:16] <Lathiat> http://lwn.net/Articles/175976/
[01:16] <Lathiat> interesting
[01:16] <Lathiat> combination live/install cd from mandriva
[01:19] <siretart> Seveas: well, it's not really broken, but a different semantic. To get the number 79%, divide the 56 (or something, this depends on your particular machine) by 38
[01:19] <siretart> Seveas: IOW, thats intended by madwifi upstream and not considered as a bug
[01:19] <Seveas> urgh
[01:22] <infinity> (Alternately, one could say it's a buggy driver for presenting data to userspace COMPLETELY DIFFERENTLY than the other drivers, but hey, just blame userspace, that's easier)
[01:22] <infinity> madwifi's "oh, standards aren't important, we'll just do whatever" stance can be annoying.
[01:26] <Seveas> infinity, exactly, they say WEXT 18/19 compliance is just an enhancement...
[01:27] <Pygi> Seveas: well, if it's really important, I guess it wouldn't be to hard to change that...
[01:28] <Seveas> Pygi, it's a cosmetic issue, presumably netstat-applet has fixed^Wworked around it and nm-applet not
[01:28] <Pygi> Seveas: hm, well..should we leave it that way or...?
[01:31] <Seveas> If i can cook up a patch really quickly I'll send it, otherwise I wouldn't bother
[01:31] <infinity> Pygi: Special-case it for madwifi (like to many other things in NM) so it's "correct".
[01:31] <infinity> It's not difficult to do, just a pain to have to do it.
[01:32] <Pygi> infinity: understandable...
[01:32] <Pygi> Seveas: k, great...you know the mail ^_^
[01:32] <Seveas> dennis@mirage:~/temp/gnome-netstatus-2.12.0$ grep -i madwifi -R .
[01:32] <Seveas> dennis@mirage:~/temp/gnome-netstatus-2.12.0$
[01:32] <Seveas> dennis@mirage:~/temp/gnome-netstatus-2.12.0$ grep -i madwifi -R .
[01:32] <Seveas> dennis@mirage:~/temp/gnome-netstatus-2.12.0$
[01:32] <Seveas> hmm...
[01:33] <Treenaks> duh
[01:33] <Treenaks> als het de 1e keer niet werkt werkt het de 2e keer ook niet ;)
[01:33] <Treenaks> misschien staat er 'atheros' ?
[01:33] <Seveas> Treenaks, EN
[01:33] <Seveas> not NL 
[01:33] <Treenaks> Oops
[01:34] <infinity> Seveas: ath_pci
[01:34] <Seveas> ah: ./netstatus-sysdeps.c:      g_strncasecmp (iface, "ath",  3) &&
[01:34] <Treenaks> so.. maybe you're looking for the wrong string :)
[01:39] <Seveas> hmm, I see no special casing for atheros/madwifi...
[02:04] <giftnudel> now that nm supports wpa, is there a chance that it will get vpn support?
[02:04] <Treenaks> giftnudel: once it stabilises upstream, sure
[02:04] <Treenaks> giftnudel: but not for dapper
[02:05] <giftnudel> is there an easy way to add that, or do you have to recompile everything
[02:08] <Pygi> giftnudel: it is not even sure that nm will get into dapper
[02:09] <infinity> s/nm/nm 0.6/
[02:09] <infinity> nm is already in dapper.
[02:09] <Pygi> yes, nm 0.6
[02:09] <Pygi> sorry infinity, by n-m I reffer to 0.6
[02:10] <infinity> Anyhow, the VPN issue has less to do with upstream stability and more to do with a complete lack of reasonable integration of the debian/ubuntu NM backend with the VPN stuff, I'd assume.
[02:11] <infinity> Oh, and the fact that much of its cleverness relies on having a loacl nameserver that supports views, like bind9.
[02:11] <infinity> (Well, exactly like bind9 right now, since the backend doesn't know how to drive others)
[02:12] <infinity> Hacking on NSS violently to get it to support local views natively, so you don't need a fullblown nameserver to do so would be a Very Good (and fun) project for someone.
[02:13] <Treenaks> 'hacking on NSS' scares people. 'violently' even more...
[02:13] <infinity> Well, yes, that had occurred to me.
[02:14] <infinity> NSS modules don't look that hard to write, though.
[02:14] <infinity> You shouldn't need to abuse the libc resolver directly to get the behaviour you want, I don't think..
[02:16] <Pygi> infinity: perhaps, but there is no way to do that for dapper ;)
[02:16] <tseng> guys, is autostart .desktop supported in gnome 2.12?
[02:17] <tseng> or new for 2.14
[02:17] <infinity> No, for dapper, if you want the VPN stuff you'd have to recompile the package and install bind9
[02:17] <Pygi> infinity: but perhaps, if situation fixes itself for dapper+1, we could do it for then
[02:18] <Pygi> perhaps -ng and new wpasupplicant will be way stable then ^_^
[02:18] <infinity> madwifi-ng is stabilising a bit, but it'll be a long, hard road.
[02:19] <Pygi> yup, understandable...and probably not ready for dapper+1
[02:19] <infinity> When I publihed packages for testing, I only got about a 50% success rate from testers, which wasn't promising.
[02:19] <infinity> That was 2 months ago now.
[02:20] <Pygi> we've got 90% success rate for this packages we've built. but not many people tried it...and that one that failed, done so by his own mistake
[02:20] <infinity> I can publish a new SVN snapshot and call for wider testing again, but I fear it wouldn't go terribly well.
[02:20] <Pygi> that's a good rate, I would say ;)
[02:21] <infinity> Besides, it's way too late in the release cycle to consider a switch anyway, I tihnk.
[02:21] <Pygi> infinity: hm, perhaps after dapper is published?
[02:21] <Pygi> infinity: yup, most probably
[02:21] <infinity> After dapper is published, I'll switch to -ng unconditionally anyway, and we'll see how many bug we can shake out during the dapper+1 cycle.
[02:21] <infinity> If I HAVE to switch back, I will, but I don't plan on it.
[02:22] <Pygi> infinity: if we are to consider switching to -ng, with our patches included, count me in to help writing patches
[02:22] <infinity> Well, on June 2nd, I'll switch to madwifi-ng. :)
[02:23] <infinity> So, if you want to contribute fixes at that point, feel free.
[02:23] <infinity> I don't currently own any atheros hardware, so I'm flying blind most of the time, and counting on user feedback.
[02:23] <Pygi> I had to get one few days back, just to test the packages we've built
[02:24] <Pygi> _ion: have you finally woke up? ^_^
[02:25] <Pygi> infinity: will the dapper+1 daily images be built since June 2nd, or are we going to wait *some time*?
[02:26] <Pygi> btw. we have 4 months or so for dapper+1 most probably?
[02:27] <Robot101> is dapper's Xorg patched somehow to make DRI work, that would make it stop working under Xorg-air?
[02:28] <infinity> Pygi: Not sure when we'll open the archive for dapper+1... Could be a 1-week "cooling off" period before we open the floodgates for syncs, merges, and new uploads.
[02:29] <Fjodor> Seveas: Are you awake?
[02:29] <Seveas> Fjodor, yeah
[02:30] <Fjodor> Did you want an account on my machine for hacking the glibc thing?
[02:30] <Seveas> may be useful
[02:30] <giftnudel> oh, and btw, nm 0.6 from the wiki works flawlessly  for me
[02:30] <Fjodor> 2 secs
[02:30] <Seveas> Fjodor, I think you need some makefile tweaking
[02:31] <Fjodor> Ok
[02:31] <Seveas> that symbol that is missing used to be defined in an S file and now is defined in a c file - no makefiles have been changed and I don't know if the glibc makefile trickery picks it up automatically
[02:32] <Fjodor> Ah. Seems reasonable
[02:32] <Seveas> it may very well do that automagically (glibc Makefile is really tricky)
[02:37] <Pygi> giftnudel: great, but the info is currently obsolete ;)
[03:11] <towolf_> salve, i've been running nm from cvs since ages but i'd like to help populating the v0.6 testing database with the pkgs Pygi announced on the forums
[03:12] <Pygi> towolf_: great, but please wait until me and _ion announce new packages, and update wiki
[03:12] <towolf_> fine
[03:12] <Pygi> we'll call for wider testing today, that
[03:12] <Pygi> towolf_: thanks ^^
[03:14] <zyga_> darn
[03:15] <zyga_> I've just realised that I cannot fix a bug without ngettext that takes two numeric arguments and is expanded to a [N] [N]  array of strings (where N is num-plurals)
[04:17] <mcquaid> hello, my gf4 burnt out and i've had to go back to my old voodoo3 
[04:17] <mcquaid> i can't get dri working with this card
[04:17] <mcquaid> i've since upgraded to dapper hoping it might resolve some issues
[04:18] <mcquaid> i'm still in the same boat and i notcied a new file available: libgl1-mesa-glide3
[04:18] <mcquaid> I'm trying to determine what that file is for exactly
[04:18] <mcquaid> is that for using dri via the tdfx driver or is it using the older (outdated?) glide driver which is not recommended
[04:19] <mcquaid> i was going to install it to try it but it flags a lot of seemingly unrelated  stuff for removal
[04:19] <mcquaid> stuff like kdebase-dev libkonq4-dev libsdl-dev etc
[04:20] <mcquaid> according to the xorg logs, dri is enabled 
[04:20] <mcquaid> but glxinfo states it's not
[04:21] <mcquaid> so from what i've read this is a userspace setup issue
[04:22] <mcquaid> i've googled and search the forums to no end but i just found other voodoo users with the same/similar problem
[04:37] <siretart> see topic
[04:39] <mcquaid> i realize this is normally not for end user support
[04:39] <Pygi> _ion: do not refuse to wake up... abrakadabra, wake up
[04:39] <mcquaid> but no other end users i've encountered have a clue about voodoo cards
[04:40] <siretart> mcquaid: file a support ticket in launchpad. this channel is not for support at all
[04:40] <mcquaid> ok
[04:40] <Pygi> mcquaid: you also have forums
[04:51] <bSON> hi
[04:51] <bSON> does the ubuntu x.org server have the aiglx extensions?
[04:51] <neuralis> bSON: no.
[04:51] <bSON> ok
[04:53] <Amaranth> xserver-xorg-air-core is in universe
[04:55] <bSON> Amaranth: but you can't make use of it without a composite-enabled metacity and stuff, can you?
[04:55] <Amaranth> bSON: spiftacity is in universe too
[04:55] <HiddenPuppy> spiftacity?
[04:55] <HiddenPuppy> the name alone. :S
[04:55] <mjg59> metacity with the compositor enabled
[04:55] <Amaranth> metacity with the compositor enabled
[04:55] <Amaranth> heh
[04:56] <bSON> cool
[04:56] <HiddenPuppy> mjg59: you where eager for some ehm, bling in dapper? ;)
[04:56] <HiddenPuppy> were
[04:57] <bSON> Amaranth: and xair will tell me that all renedering is disabled?
[04:57] <Amaranth> too bad neither one of them appears to work with ppc
[04:57] <Amaranth> bSON: sudo ln -sf /usr/bin/Xorg-air /usr/bin/X
[04:57] <Amaranth> bSON: then restart X
[04:57] <HiddenPuppy> Amaranth: nor most of the drivers, so the pain is everywhere
[04:58] <Amaranth> HiddenPuppy: I have a 9200, the one that's supposed to have the best support
[04:58] <Amaranth> radeon 9200, that is
[04:58] <HiddenPuppy> I should've never tossed that one out. =)
[04:58] <bSON> Amaranth: i guess i'll have to replace my gnome session's metacity with spiftacity
[04:58] <Amaranth> bSON: no
[04:58] <Amaranth> bSON: spiftacity --replace
[04:58] <bSON> ok, good
[04:58] <Amaranth> then you need to set a gconf key, but i don't remember what it is
[04:58] <bSON> that's what i meant...
[04:59] <HiddenPuppy> Is anyone here familiar with the innards of the networking system?
[04:59] <Amaranth> oh, i thought you meant permanently
[05:00] <bSON> Amaranth: i already tried xgl and compiz, now i want to give aiglx a chance :)
[05:00] <Amaranth> bSON: it's not as shiny but at least it doesn't run two xservers
[05:01] <Amaranth> and someone on the forums has some packages for compiz and aiglx with the changes needed to make them work together
[05:01] <bSON> Amaranth: well, wobbly windows will come back soon, then i don't care which of the two i use ;)
[05:01] <Amaranth> so then you get the shiny and the lower memory usage
[05:01] <bSON> yeah
[05:02] <bSON> lets do the X restart...
[05:03] <Amaranth> wtf
[05:03] <HiddenWolf> *chuckle*
[05:03] <Amaranth> X fails to access /dev/dri/card0 twice, then it suddenly works
[05:03] <HiddenWolf> Right, i'm going nuts here
[05:04] <HiddenWolf> I took my router out of the connection, fired up pppoeconf, get a perfectly working ppp0, but ubuntu insists on timing out on eth0
[05:05] <bSON> hi
[05:05] <Amaranth> (WW) RADEON(0): Video BIOS not detected, using default clock settings! <--annoying
[05:05] <bSON> Amaranth: Xorg-air can't find the drm module for fglrx...
[05:05] <Amaranth> bSON: err
[05:05] <Amaranth> aiglx only works with open-source drivers
[05:05] <bSON> oh...
[05:05] <HiddenWolf> open source radeon driver only, right?
[05:06] <Amaranth> until nvidia and ati add GLX_EXT_texture_from_pixmap to their drivers
[05:07] <bSON> it's shown in glxinfo on my Xgl
[05:07] <Amaranth> that's because Xgl provides it
[05:08] <Amaranth> which works with that because it's a seperate server
[05:08] <bSON> my radeon 9600 xt has no 3d acceletation with the radeon driver...
[05:08] <Amaranth> or some crap
[05:08] <bSON> Amaranth: oh
[05:08] <Amaranth> bSON: when did you try last?
[05:08] <Amaranth> there is support for r300 cards in the open-source driver
[05:08] <Amaranth> it's just not done
[05:08] <bSON> after installing dapper flight 4
[05:11] <bSON> Amaranth: at least option "RenderAccel" didn't work
[05:11] <Amaranth> but did you see if 3d worked?
[05:11] <Amaranth> doesn't matter though, i know the r300 driver doesn't work with aiglx
[05:13] <mcquaid> bSON, do you have the dri driver working for ati?
[05:13] <bSON> dunno, i'll have to try
[05:14] <mcquaid> do this: export LIBGL_DEBUG=verbose
[05:14] <mcquaid> then run glxinfo
[05:14] <bSON> should i maybe try to use "accelmethod" exa?
[05:16] <bSON> mcquaid: with the "ati" driver? or "radeon"?
[05:17] <mcquaid> i believe that's with the ati driver only
[05:19] <HiddenWolf> I wonder what the future of aiglx and xgl is. Something like "use aiglx if possible, fallback to xgl, then xorg"
[05:20] <bSON> probably
[05:20] <bSON> til xgl learns to run on its own
[05:32] <bSON> how can i choose the used dri driver?
[05:32] <bSON> is that done automatically?
[05:47] <bSON> bobbens: no success
[05:48] <bSON> oh, wrong channel...
[05:55] <_ion> pygi: The spell you cast worked with a slight delay.
[05:56] <Pygi> _ion: ion, great ;)
[05:56] <Pygi> we have so much to do now you know, 
[05:56] <Pygi> first of all, read your mails
[05:57] <Pygi> second of all, please add l-r-m packages to the repository, and edit the wiki to be valid (to instruct on installing l-r-m) packages
[05:57] <_ion> pygi: I read the mails and added the warning to postinst. I'm building the packages right now.
[05:57] <Pygi> _ion: k, and add lrm, and edit wiki pls
[05:58] <Pygi> I have more news for you as well  ^_^
[05:58] <_ion> Will do.
[06:06] <_ion> pygi: Hmm. It would be better if people used the networkmanager-lrm repo at people.ubuntu.com because the package is huge and my repository is behind my home ADSL. :-)
[06:07] <_ion> pygi: We might as well tell madwifi users to use that repository. Right?
[06:07] <Pygi> _ion: tonio_ said that we could use his 80Mbit repo if we want...
[06:08] <_ion> http://people.ubuntu.com/~adconrad/networkmanager-lrm/ is already there, and it's quite fast.
[06:08] <Pygi> _ion: let's rather keep all on one place...want me to ask tonio_ to host it for us?
[06:09] <_ion> pygi: Ok.
[06:10] <Pygi> _ion: k,just tell me when you uploaded the new n-m
[06:10] <_ion> The updated package (with the check) is available from my repository now.
[06:10] <Pygi> oh, ok, great
[06:11] <Pygi> now the wiki ^_^
[06:13] <_ion> *** Please set ENABLED=0 in /etc/default/wpasupplicant
[06:13] <_ion> *** if you want network-manager to manage wpasupplicant.
[06:13] <_ion> It worked. :-)
[06:16] <Pygi> _ion: o joy ^_ ^
[06:32] <HiddenWolf> Right, webcam support sucks.
[06:43] <_ion> pygi: There seems to be something wrong with the l-r-m patch: "With the patch, WPA works, but it's rather buggy. The connection doesn't last very long, and NM doesn't seem to be able to remember my WPA key. Plus, the system will randomly lock up when reconnecting (EDIT: This seems to happen if I choose to show my WPA key with nm-applet)" (from the forum)
[06:45] <Pygi> _ion: I saw that...
[06:45] <zyga> pitti: hi
[06:45] <Pygi> _ion: it was the first report of it's kind, and there is no some actuall info on what happened, and how...
[06:46] <_ion> pygi: True.
[06:46] <Pygi> _ion: so we'll have to wait until more people report/confirm somethin' like that
[06:46] <_ion> Yep.
[06:46] <zyga> pitti: do you have a moment?
[06:46] <Pygi> _ion: perhaps it's only a isolated incident cause by *somethin'*
[06:47] <Pygi> _ion: I'm just waiting until Tonio_ returns, so we can host all
[07:07] <_ion> infinity: Does this <https://lists.ubuntu.com/archives/dapper-changes/2006-March/007934.html> affect the patched l-r-m package?
[07:14] <Lure> _ion: that what concerns me too - there is new ipw2200 and I would not like to clash with NM-patches l-r-m
[07:15] <Lure> _ion: are l-r-m patches only for madwifi or also for ipw2200?
[07:15] <_ion> lure: The patch is only needed for madwifi.
[07:16] <Lure> _ion: ok, then concern is only if this new kernel release will not override NM-patched l-r-m
[07:16] <mjg59> The ABI name has changed. So it will.
[07:16] <Lure> and breaking madwifi NP support
[07:16] <Pygi> mjg59: huh, so it will break l-r-m packages we've built? :-
[07:16] <Pygi> :-/
[07:16] <Pygi> that is no good
[07:16] <Lure> mjg59: so we need to wait for release of kernel and rebuild then?
[07:21] <mjg59> Lure: Yes
[08:33] <sivang> doko__: ping
[10:57] <_ion> http://bash.org/?626249
[11:48] <Lure> _ion: is airo wireless supposed to work with NM (Riddell is testing it)
[11:49] <Lure> is http://mail.gnome.org/archives/networkmanager-list/2006-January/msg00204.html patch included?
[11:50] <_ion> Probably not, unless the kernel source maintainers have included it.
[11:50] <Lure> _ion: you patch to l-r-m (done by infinity) was then only for madwifi?
[11:51] <_ion> Yes.
[11:51] <Lure> ok
[11:51] <_ion> If that patch is needed, it should be probably filed as a bug report to the kernel package.
[11:54] <Lure> _ion: does it make sense to open bug report for NM-related fixes as we do not know yet if NM will be accepted?
[11:54] <_ion> That doesn't look like a network-manager related fix.
[11:55] <_ion> "This patch adds IWENCODEEXT and IWAUTH support to the airo driver for WEP and unencrypted operation.  No WPA though."
[11:56] <robertj> Lure: it's definately going into Universe right?
[11:57] <Pygi> Lure: nop
[11:57] <_ion> I've had the impression that it's definitely not going to main, and the one in universe *might* be upgraded to the 0.6 series if the package is good enough.
[11:57] <Lure> Pygi: what "nope"?
[11:58] <Pygi> It cannot go in main, that is not even an option
[11:58] <Pygi> Lure: sorry, wrong guy ^_^
[11:59] <Burgundavia> if you are talking about n-m, it pretty much to replace what is already there
[11:59] <_ion> Hm, /me just realized network-manager 0.5.1 _is_ in main.
[11:59] <Burgundavia> so we are talking into main
[11:59] <Burgundavia> n-m is already on the livecd
[11:59] <Pygi> Burgundavia: ah, yes, really ... haven't saw that ...
[11:59] <Pygi> _ion: so that's why packages have to be *so* good ^_^
[11:59] <_ion> pygi: Heh, yep.
[12:00] <Pygi> everything is working (packages I mean), only repos to fix
[12:00] <Pygi> but we are workin' on that
[12:00] <Pygi> _ion: please write info on DapperNetworkManager and DapperKNetworkManager on how to import key
[12:00] <Pygi> thanks
[12:01] <_ion> Ok.