[07:42] <tjaalton> superm1: ping? is the latest fglrx known to be buggy with compiz & video?
[07:47] <tjaalton> superm1: apparently bug 179042
[07:47] <wgrant> tjaalton: Doesn't the EPR # mean it has been forwarded to AMD already?
[07:48] <tjaalton> wgrant: probably so
[07:49] <tjaalton> there should be a wikipage with the forwarded bugs
[07:49] <tjaalton> on it
[07:59] <tjaalton> sigh, looks like wacom upstream is just ignorant
[08:14] <wgrant> I noticed...
[08:14] <tjaalton> http://sourceforge.net/mailarchive/forum.php?thread_name=20081009171824.GV5387%40cathedrallabs.org&forum_name=linuxwacom-devel
[08:14] <wgrant> I thought either I was completely misunderstanding it, or they were ignorant.
[08:14] <wgrant> And I suspected the latter.
[08:15] <wgrant> Oh.
[08:15] <wgrant> More traffic.
[08:16] <tjaalton> seems like Ping doesn't follow the -devel list
[08:16] <wgrant> How related to linuxwacom is Ping?
[08:16] <tjaalton> the main author
[08:17] <tjaalton> or developer
[08:17] <wgrant> Oh.
[09:33] <wgrant> Who is this Vincenzo character?
[10:05] <tjaalton> wgrant: where?
[10:05] <wgrant> -devel-discuss.
[10:05] <wgrant> See #-devel
[10:06] <tjaalton> ah, reading
[10:06] <wgrant> He's just insane.
[10:06] <tjaalton> ok, I won't bother then :)
[10:06] <wgrant> Heh.
[10:06] <tjaalton> loads of stuff to do
[10:07] <tjaalton> starting from getting nvidia 173 in hardy-proposed
[10:07] <tjaalton> with cuda
[10:07] <wgrant> Aha.
[10:07] <wgrant> Shiny.
[10:07] <tjaalton> well, the library at least
[10:25] <Ng> wgrant: a frustrated user, by the looks of it
[10:25] <Ng> it's a tad harsh to call him insane, I would say
[10:25] <Ng> it's not that he's especially wrong either (assuming you mean the thread about hardware support regressions), he's just not addressing the issue in a way that will have any positive outcome
[10:32] <tjaalton> maybe his vga-problems are related to the latest upload to hardy-proposed, where every chip inluding 855 and earlier have to be quirked
[11:08] <tjaalton> oh, it's only about vga-out
[11:12] <wgrant> Bug #295990. Fsck. FOrgot about that.
[11:13] <wgrant> I didn't bother with the keyboard stuff in g-s-d, because most of the settings are either really global or don't work with evdev...
[11:14] <wgrant> But of course layout needs setting per-device.
[11:22] <tseliot> tjaalton: nvidia-173 in hardy proposed???
[11:23] <tseliot> tjaalton: that will break things for a few users, please don't do it
[11:25] <tseliot> the reason why I didn't touch the lrm in hardy (instead of using the lrm-envy) is also that the current nvidia-glx-new works when 173, etc. doesn't with certain hardware configurations
[11:25] <tseliot> s/when/while/
[11:27] <tseliot> I think that backporting driver 173 and 178 to hardy through lrm-envy would be less risky
[11:30] <tjaalton> tseliot: it's not my idea
[11:30] <tjaalton> tseliot: what would break?
[11:30] <tjaalton> 173 didn't drop any hw support AIUI
[11:31] <tseliot> tjaalton: there are some cards (I don't remember which ones) for which the driver won't work
[11:31] <tseliot> and I'm not talking about cards being dropped by a driver
[11:31] <tseliot> the driver won't work at all
[11:32] <tseliot> tjaalton: who asked you to do this? (not to blame it on him but only to talk to him about this)
[11:32] <tjaalton> stefan bader
[11:32] <tseliot> username?
[11:32] <tjaalton> not on irc atm
[11:32] <tjaalton> dunno
[11:33] <tseliot> anyway rtg asked me to backport 178 to hardy and I will do it in the lrm-envy packages
[11:34] <tseliot> but we have to be careful not to break the packages in main
[11:35] <tseliot> tjaalton: BTW did you tell him about the linux-restricted-modules-envy?
[11:35] <tjaalton> tseliot: no, I bet he knows already
[11:36] <tseliot> ok, if you see him (metaphorically speaking), please ask him to talk to me
[11:36] <tjaalton> I'll reply to his email
[11:36] <tseliot> ok
[11:42] <tseliot> tjaalton: oh and I know that you maintain the lrm in hardy but in the future please notify me when you decide to modify them (as regards fglrx and nvidia) so that we can discuss the changes, etc.
[11:52] <tjaalton> tseliot: I don't really maintain it anymore, not since it was frozen :)
[11:53] <tseliot> hehe right ;)
[14:10] <pwnguin> Vicenzo is insane?
[14:19] <pwnguin> interesting
[14:40] <superm1> tjaalton, the fact that is has an EPR means AMD has an internal bug filed about it
[14:40] <superm1> we'll be closing out bugs per their announce/release notes based on those EPR's
[14:47] <tjaalton> superm1: yeah, a friend of mine suffers from it, that's why I was asking
[17:24] <bryce> heya
[17:25] <bryce> tjaalton: no need for wiki page, I got this set up for us to keep track:  https://bugs.edge.launchpad.net/fglrx/+bugs
[17:27] <bryce> tjaalton: also, when you run across bugs that need upstreaming to AMD, we now have a way to mark them - click the "Affects project..." and then tick the third bullet "just mark as needs upstream for now"
[17:27] <bryce> (full process documented at https://wiki.ubuntu.com/X/Upstreaming)
[17:39] <tjaalton> bryce: ok, thanks
[17:48] <bryce> how's thing tjaalton?
[17:50] <tjaalton> got my plane tickets today
[17:51] <bryce> :-)
[17:52] <tjaalton> trying to decide what souvenirs to buy ;)
[17:53] <bryce> have you been to san francisco before?
[17:56] <tjaalton> nope, there are too many places to see when I have only the sunday off
[17:57] <bryce> I used to live in san francisco, I can give tips if you need suggestions
[17:57] <tjaalton> sure thanks
[18:02] <bryce> I would suggest catching the BART from San Jose and get off downtown, then do one of the walking tours down through china town to fisherman's warf.  That should give maximum SF-ishness in the least amount of time.
[18:03] <superm1> bryce, i'm  gonna be in SF for a few days before UDS starts too.  i'll have to get some ideas from you  then too :)
[18:03] <bryce> sure
[18:03] <bryce> if you like musicals/plays/concerts, it is a great place to catch one of those
[18:03] <bryce> here's a link showing the neighborhoods:  http://www.sfcityguides.org/descriptions.html
[18:04] <superm1> would you recommend a car for those few days?
[18:04] <tjaalton> ok that should be a start :)
[18:04] <bryce> the top NE corner is where the biggest concentration of "things to see" is, and if you have limited time, is where I'd suggest focusing
[18:04] <bryce> superm1: well, downtown SF is *impossible* to get around in by car
[18:05] <superm1> okay then for sure no car
[18:05] <bryce> but the good news is it's totally walkable/public-transitable.  In fact the whole time I lived there I kept my car in storage
[18:05] <bryce> so you just need to sort out getting around in San Jose
[18:05] <bryce> San Jose is standard U.S. can't-get-around-without-a-car
[18:06] <superm1> right, about what i'm used to :)
[18:06] <bryce> although if the hotel is within walking distance of the lightrail, it might be ok
[18:06] <superm1> havent picked one out yet (but that reminds me i need to! :)
[18:07] <bryce> the weather in downtown SF is likely to be pretty cold and rainy, so plan accordingly
[18:07] <bryce> in San Jose it will be a bit better.
[18:08] <superm1> anything that's north of texas is cold to me now :)
[18:09] <superm1> but you'd recommend a hotel in San Jose over finding one in SF though provided i can find one close to a light rail?  assuming due to cost?
[18:10] <bryce> oh definitely
[18:10] <bryce> right, hotels in downtown SF are damn expensive
[18:11] <superm1> okay that's good to know
[18:11] <bryce> superm1: is the one that UDS is held in booked up yet?  
[18:12] <superm1> bryce, not sure.  i'd imagine so?
[18:12] <superm1> but also given it's in mountain view - i'd expect pricey...
[18:12] <bryce> oh duh, UDS is at google
[18:13] <superm1> that'll be the other challenge to figure out; getting from SF to MTV cost effectively
[18:14] <bryce> well, when I went to the X conference at google earlier this year, I got a hotel in San Jose and a car, and drove in each day.  Traffic wasn't too bad (the conference started fairly late though).  Walking would have been impossible.
[18:14] <bryce> UDS is at a different google location than that, but might be the same situation.  not sure
[18:14] <bryce> a lot of the X guys shared cars
[18:14] <superm1> well i heard there is a free shuttle if you talk to the right people 
[18:15] <bryce> cool, that could work
[18:15] <superm1> i just dont know who those people are, and if i dont find them, it will probably just end up being a taxi or one day car rental
[18:16] <bryce> anyway, even if you do rent a car, my recommendation for exploring SF would be the same - park it at a BART terminal and take BART in
[18:16] <superm1> okay, will definitely keep that in mind.  would probably leave the car rental for sunday then to use in exploring San Jose and for driving down
[18:17] <superm1> (if anything)
[18:27] <tjaalton> so are sunnyvale, mtv etc part of san jose?
[18:28] <superm1> tjaalton, http://maps.google.com/maps?f=q&hl=en&geocode=&q=san+jose+ca&sll=37.0625,-95.677068&sspn=42.224734,93.164063&ie=UTF8&ll=37.51844,-121.92215&spn=0.663338,1.455688&z=10
[18:28] <superm1> you can see the breakdown there a bit
[18:29] <bryce> superm1: yeah all three sort of run together in a big sprawl
[18:29] <tjaalton> yeah i've used gmaps quite a bit :)
[18:34] <tjaalton> my brother-in-law has been there many times
[18:36] <tjaalton> and asked me to bring some parts for his '65 grand prix ;)
[18:40] <bryce> hehe
[19:05] <bryce> tjaalton: hey, given that Intel is no longer supporting i815/i825 chips (maybe more pre-855?) on -intel, I'm wondering about if we could/should put -i810 back in the archive
[19:05] <superm1> bryce, hdmi audio on intel, any ideas what intel driver release it ends up falling into?  (i thought there was a video driver piece to it too)
[19:06] <bryce> superm1: hmm no idea; I've never needed to touch video stuff before and would assume the kernel would split that out, but I've not done very much with hdmi so far
[19:07] <superm1> bryce, well the video driver needs to let the audio driver know how much bandwidth it can have i believe. i thought there was an interaction there
[19:09] <superm1> bryce, ah http://www.phoronix.com/scan.php?page=news_item&px=NjgzNg  there's some patches to both.  i'm assuming there will be more chatter on it in the coming months then
[19:36] <bryce> superm1: ah cool
[19:54] <tjaalton> bryce: but they don't support it either :)
[19:55] <tjaalton> hm, still no internet.. at least my phone works
[19:56] <tjaalton> s/internet/adsl/
[19:57] <bryce> tjaalton: sure but at least (assuming it works at all), it'd give users the option.
[20:20] <bryce> erf, already back up to 2000 bugs in ubuntu-x.  
[20:43] <tjaalton> bryce: well, I don't know.. vincenzo's problem seems more like a hotkey-issue than a bug in -intel
[20:44] <tjaalton> besides, -i810does not support xserver 1.5
[20:44] <tjaalton> aiui it's not pcitoolized
[20:45] <bryce> ahh
[20:45] <bryce> good point.  So if community folks want -i810 back, they'll need to first get it up to date for 1.5.
[20:50] <tjaalton> or better, help intel testing the new releases for regressions
[20:51] <tjaalton> of -intel
[21:19] <bryce> no, I'm thinking of the cases where the testing has already done, I've upstreamed the issue to Intel, and they've said they won't be supporting it in -intel.
[21:19] <bryce> +been
[21:56] <tjaalton> meaning that they refuse to include fixes or that they wont be doing the work themselves?
[22:04] <bryce> the latter
[22:11] <tjaalton> right, so the community might be able to fix them. i don't know which is more work, porting the driver (with other bugs) or fixing the bugs
[22:25] <tjaalton> night
[22:35] <bryce> night tjaalton
[22:50] <tormod> hi there, I get some bad, spurious Xorg hangs on Intrepid. In order to investigate, I built xserver 1.5.3 to get the automatic backtracing. now it locks up at startup... I suspect the "RAW mode" commit. Any experiences among you?
[22:54] <tormod> or do I miss some crucial ubuntu patches? (I built it from fdo+debian git)
[23:15] <tormod> or do I need to recompile the DDX?
[23:21] <tormod_> for once, my ssh session stayed alive/recovered. Actually Xorg is not hung, but died and I don't get my console back. just the gray X screen and the cursor (from running startx).
[23:23] <tormod_> gdb is my friend: evdev_drv.so: undefined symbol: XIRegisterPropertyHandler
[23:23] <tormod_> gotta love these xserver point releases....
[23:26] <wgrant> tormod_: We carry property patches separately.
[23:27] <tormod_> wgrant, thanks! I will take a look
[23:31] <tormod_> I guess all those patches are in the ubuntu branch on git.debian.org and I just have to pull from there, d'oh.
[23:45] <tormod_> hmm why is patch 138 not in git, but listed in "series" ?