[00:00] <_jz> 12 hours with xserver-xorg-core and xserver-xorg-video-ati from feisty under gutsy and no freeze using compiz !!
[00:01] <_jz> i think that's the way ! tomorrow i'll test using only the previous xserver-xorg-video-ati, and current gutsy xorg-core and will keep you informed :)
[00:01] <ubotu> New bug: #64811 in linux-source-2.6.22 (main) "PCI cannot allocate resource for region 7 8 and 9 on Acer Aspire 5601AWLMi Laptop (dup-of: 54294)" [Undecided,New] https://launchpad.net/bugs/64811
[00:03] <bryce> ye gods the influx of me-toos on 156325 ;-)
[00:20] <ubotu> New bug: #156467 in xserver-xorg-video-intel (main) "No direct rendering on 855GM chip in Gutsy" [Undecided,New] https://launchpad.net/bugs/156467
[00:30] <ubotu> New bug: #156470 in linux-restricted-modules-2.6.22 (restricted) "Random desktop freeze with nvidia-glx-new 100.14.19" [Undecided,New] https://launchpad.net/bugs/156470
[00:49] <tepsipakki> for the record, I can't change the keymap with 1.4 for some strange reason
[00:49] <tepsipakki> so I'll continue tomorrow trying to figure out why
[00:53]  * bryce nods
[00:53] <bryce> I'm working on fglrx.  It's strange, there's a link to the file, but it doesn't seem to be mentioned anywhere on ati/amd's site that I can find
[00:53] <bryce> so no release notes
[01:48] <arsham> hi bryce
[01:48] <arsham> hi all
[01:49] <bryce> heya arsham
[01:49] <arsham> I am one of those who has problems with intel graphic card , in gutsy
[01:49]  * bryce nods
[01:49] <arsham> I just red your article in lunch pad
[01:50] <arsham> I have something to say
[01:50] <arsham> most of time , exactly when a pm comes from pidgin , the lockup happens
[01:50] <arsham> for me
[01:51] <bryce> which bug id number?
[01:51] <arsham> w8
[01:51] <arsham> 127101
[01:51] <bryce> ahh
[01:51] <arsham> I closed every application , that uses libnotify
[01:52] <arsham> nothing happened yet
[01:52] <arsham> but I have to read whole of the bug reports in that area
[01:52] <bryce> ok well it's likely you're experiencing some new bug
[01:52] <arsham> maybe
[01:53] <arsham> have you had any chance to fix that?
[01:53] <bryce> even if it demonstrates symptoms that are just like in 127101, it's probably caused by something different
[01:53] <arsham> maybe
[01:53] <bryce> in any case, 127101 is closed as fixed and verified by its reporters, so you'll want to post a new bug report
[01:53] <arsham> aw , I am not familiar with bug reporting
[01:54] <arsham> just googling for my problem
[01:54] <bryce> here's some info on bug reporting:  https://wiki.ubuntu.com/X/Debugging/
[01:54] <arsham> why the graphic card hangs with compiz in gutsy? 
[01:54] <bryce> you probably only need to read section 2
[01:54] <arsham> thank you
[01:55] <arsham> what was the difference between faisty and gutsy in these kind of case?
[01:56] <bryce> feisty used the -i810 driver, whereas gutsy used a newer -intel driver
[01:56] <arsham> aw
[01:56] <bryce> also feisty did not have compiz enabled by default
[01:56] <arsham> is there any chance for me to use i810 driver?
[01:57] <arsham> I am confused 
[01:57] <arsham> another thing , maybe helps :
[01:57] <bryce> there is a chance
[01:58] <arsham> while locking up , amarok plays the whole song till the end , and doesn't play the next one , maybe related to OSD or notify 
[01:58] <arsham> and I can ssh and remote control my computer 
[01:58] <arsham> but keyboard and screen is locked
[01:58] <arsham> and mouse is active , you know that already
[01:59] <arsham> how can I use that driver?
[01:59] <arsham> is it stable?
[01:59] <ubotu> New bug: #156456 in compiz (restricted) "mplayer can't display Videos " [Undecided,Invalid] https://launchpad.net/bugs/156456
[02:02] <arsham> another thing that I saw was :
[02:02] <arsham> during reboot : I got the splash screen of ubuntu's shutting down , seems that the control got back to the GC
[02:09] <arsham> bryce, would you please guide me to fix my problem?
[02:11] <bryce> sorry, I'm a bit busy, but here's some docs that should help for installing i810: https://help.ubuntu.com/community/i915Driver
[02:11] <arsham> thank you
[02:12] <arsham> and good luck
[02:13] <bryce> there is also a place for asking for tech support on ubuntu here:  https://answers.launchpad.net/ubuntu/+addquestion
[02:13] <arsham> thanks man
[02:16] <bryce> np
[02:18] <arsham> X crash
[02:31] <arsham> which graphic card do u advise me for my next laptop?
[02:32] <bryce> all graphics cards have some bugs, none is perfect
[02:33] <bryce> i945 seems to be fairly well supported
[02:33] <arsham> and about performance?
[02:34] <bryce> best performance are with binary drivers, which are not well supported 
[02:34] <arsham> thank you , your gr8
[02:58] <arsham> bye all
[02:58] <arsham> bye bryce  , thank you helping me
[04:55] <bryce> heh, some of the fglrx commentary at phoronix is humorous.  "AIGLX is a TOTAL DELUSION. The fps is less than XGL. Firefox scrolling seems like a 286 dir command (on dos).
[04:55] <bryce> Radeon open source driver is better!"
[06:37] <tepsipakki> bryce: made some small adjustments to the Projects-page
[06:42] <tepsipakki> the x11proto's are good to go before the server, since it build-depends on them
[06:50] <ubotu> New bug: #156550 in xserver-xorg-driver-ati (main) "[gutsy] ati open source driver issues with external monitor" [Undecided,New] https://launchpad.net/bugs/156550
[07:14] <bryce> ok cool
[07:15] <bryce> btw, I've also now started a page for patches:  https://wiki.ubuntu.com/X/Patches
[07:15] <bryce> mostly focused on -intel
[07:16] <bryce> so far haven't run across anything too exciting
[07:47] <tepsipakki> btw, dropping patch 120 means that users need to put XAANoOffscreenPixmaps in the config, or use EXA
[07:48] <tepsipakki> otherwise the performance is horrible
[08:37] <bryce> what about modifying dexconf to put one or the other of those in?
[08:40] <tepsipakki> well, perhaps we could evaluate EXA
[08:40] <tepsipakki> for intel&ati at least
[08:51] <tepsipakki> hey seb128 
[08:51] <seb128> hi tepsipakki
[08:51] <tepsipakki> seb128: do you remember why xvfb depends on xfonts-base & xauth? Debian has those in Recommends
[08:52] <seb128> xvfb doesn't work without xauth
[08:52] <tepsipakki> the changelog of xorg-server mentions that fabbione pointed that out (haven't asked him yet)
[08:52] <seb128> xvfb-run
[08:52] <seb128> if ! which xauth >/dev/null; then
[08:52] <seb128>     error "xauth command not found"
[08:52] <tepsipakki> hmm, maybe it should be a Depends on debian as well
[08:52] <seb128> right
[08:53] <bryce> heya seb128
[08:53] <tepsipakki> actually, it's xbase-clients now, but could be changed since it's split now
[08:53] <seb128> or they don't consider xvfb-run as important enough to add a Depends
[08:53] <seb128> hello bryce
[08:54] <seb128> I think we dropped the xauth Depends by mistake during a merge and that was creating ftbfs
[08:54] <tepsipakki> right
[08:54] <seb128> because packages using xvfb-run needs to Build-Depends on xauth also then
[08:54] <seb128> I think it makes sense to have the Depends
[08:54] <tepsipakki> jcristau: ^^
[08:54] <tepsipakki> seems like it yes
[08:56] <jcristau> you need xauth if you want to use xvfb-run, not necessarily for Xvfb
[08:57] <jcristau> so yeah, if you use xvfb-run at build time, then you need a build-dep on xauth and xfonts-base
[09:03]  * _jz two hours with feisty's xorg-video-ati (and gutsy's core) and still no freeze using compiz !
[09:04] <bryce> :-)
[09:07] <tepsipakki> duh, tried the debian version of hal and still can't change the kblayout
[09:08] <tepsipakki> even if I remove the fdi it still uses hal-rules
[09:43] <tepsipakki> finally got the local fdi file to work
[09:45] <tepsipakki> yeah, I had a broken fdi file, it didn't have a "match" entry for input.keys :P
[09:46] <tepsipakki> bryce: so, what do we do with the server?-)
[09:47] <bryce> how do you mean?
[09:48] <tepsipakki> upload now or keep it on hold
[09:48] <tepsipakki> besides, until xorg is uploaded people shouldn't be able to upgrade to it without force
[09:49] <bryce> what's the status with that hal bug you were worried about?
[09:49] <tepsipakki> it is easily worked around
[09:49] <tepsipakki> but has to be done by the user for now
[09:49] <bryce> how serious of an issue is it if not worked around?  does it only affect non-US kbds?
[09:50] <tepsipakki> only !us yes
[09:50] <bryce> what's the workaround?
[09:50] <tepsipakki> and, if the DE forces pc105 layout
[09:50] <tepsipakki> put a fdi-file in /etc/hal/fdi/policy that changes it
[09:51] <bryce> where does the fdi-file come from?
[09:51] <tepsipakki> http://pastebin.com/m51eeabc5
[09:51] <tepsipakki> nowhere, needs to be made
[09:52] <bryce> hmm
[09:52] <tepsipakki> it was discussed last night on #debian-x
[09:52] <bryce> but people won't be able to upload to xserver 1.4 until the new xorg is there?
[09:53] <jcristau> you might want to wait until we agree on the transition plan
[09:53] <jcristau> or, just don't build-dep on libhal-dev
[09:53] <jcristau> for now
[09:53] <tepsipakki> hmm, that would work too
[09:54] <bryce> well, I'd say as long as there's a way we can get xserver into the repo so we can start building against it, but without inflicting the kbd issue on people in general, I'd favor uploading it
[09:54] <tepsipakki> bryce: yes, as long as there are drivers that have an older ABIVER
[10:01] <ubotu> New bug: #130837 in linux-restricted-modules-2.6.22 (restricted) ""Non-free Linux 2.6.22 modules on Realtime kernel" is missing components" [Undecided,Fix released] https://launchpad.net/bugs/130837
[10:04] <bryce> ahh, got lrm with latest fglrx built
[10:04] <tepsipakki> bryce: is it for gutsy or hardy?
[10:04] <bryce> gutsy
[10:04] <tepsipakki> ok
[10:04] <bryce> I've not set up a Hardy environment for building yet
[10:05] <tepsipakki> I did, and now some dialogs doesn't have any visible text anymore (in X, before upgrading to 1.4)
[10:06] <tepsipakki> :)
[10:06] <bryce> oh lovely
[10:06] <bryce> it's so good to know we'll have things to keep us busy for Hardy ;-)
[10:07] <bryce> btw, I've also dug through the -intel git log and identified changes that look interesting from a backporting standpoint:  https://wiki.ubuntu.com/X/Patches
[10:07] <bryce> I don't know if the quirks are worth backporting or not, but if so, there's a slew of them
[10:08] <bryce> I think tomorrow I'm going to make another pass through the intel bugs and see if any match up to these patches
[10:08] <tepsipakki> http://users.tkk.fi/~tjaalton/dpkg/xserver.debdiff
[10:21] <tepsipakki> bryce: so, I'll upload xorg-server and post a notice on u-d about the issues it has?
[10:21] <bryce> yup, sounds good
[10:22] <tepsipakki> right, I'll get on it
[10:25] <tepsipakki> +with
[10:26] <tepsipakki> 4h of sleep does take its toll :P
[10:28] <bryce> heh
[10:30] <bryce> wow, the new xserver has a surprisingly short changelog
[10:30] <bryce> +entry
[10:30] <tepsipakki> could be shorter :)
[10:33] <bryce> anyway, debdiff looks good
[10:34] <tepsipakki> 107 is a controversial patch, apparently the toolkits should be fixed not to use background none windows, but..
[10:41] <tepsipakki> hmm, I was wrong about putting the drivers on hold, since they now depends on xserver >=1.4 so they won't get built before it is uploaded
[10:41] <tepsipakki> -s
[10:42] <tepsipakki> um, I _might_ want to change the release name from xorg-server
[10:43] <bryce> uh?  really?
[10:43] <tepsipakki> it was gutsy
[10:45] <tepsipakki> so dput would have uploaded it for gutsy :)
[10:46] <bryce> ah
[10:46] <bryce> yeah I do that all the time :-)
[10:47] <bryce> but I have a plan for preventing it for hardy
[10:47] <bryce> however right now I need to go to bed.  Meeting time in +5 hrs.
[10:47] <bryce> bug 156325 is debbed.  'night.
[10:47] <ubotu> Launchpad bug 156325 in linux-restricted-modules-2.6.22 "New fglrx 8.42.3 to Gutsy" [Wishlist,Fix committed] https://launchpad.net/bugs/156325
[10:47] <tepsipakki> good night
[11:49] <seb128> bryce: +5h-49min?
[11:50] <seb128> doh, that was one hour ago ;-)
[11:50] <seb128> bryce: ignore my comment ;-)
[13:31] <pcjc2> Bryce?
[13:32] <pcjc2> I know this bug #93832 is closed, but should we add to the debug pages somewhere that this melting / fading symptom is a _VERY_ bad sign, and one which means you should power off the computer ASAP to avoid potential LCD damage?
[13:32] <ubotu> Launchpad bug 93832 in xserver-xorg-video-intel "screen "melts", no output displayed" [Undecided,Fix released] https://launchpad.net/bugs/93832
[13:32] <pcjc2> Or do we want to avoid letting people think it might be Ubuntu's fault if their LCD breaks for any reason later in its life?
[13:41] <ubotu> New bug: #156658 in xserver-xorg-video-intel (main) "Console incorrectly programmed if leaving X with no outputs (945GM)" [Undecided,New] https://launchpad.net/bugs/156658
[14:05] <baggins> hum
[14:05] <baggins> i've lost DRI on ubuntu 7.10 when i log in. it seems to spawn a new X server when i log in and can't get a lock on the hardware because the login screen still has it.
[14:05] <baggins> i am logged in on the terminal with startx at the moment.
[14:26] <tepsipakki> baggins: filed a bug yet?
[14:27] <baggins> no
[14:27] <tepsipakki> please do
[14:28] <tepsipakki> attach xorg.conf and /var/log/Xorg.0.log
[14:30] <baggins> ok, i'll do it when i have to reboot and i get annoyed about it again
[14:30] <baggins> i guess i have the question of: is that normal? does GDM now spawn a new X server when a user logs in?
[14:30] <tepsipakki> no
[14:30] <tepsipakki> and no
[14:31] <tepsipakki> create another user and then login as that user
[14:33] <ubotu> New bug: #155531 in xserver-xorg-video-ati (main) "totem don't display video on Ubuntu 7.10" [Low,New] https://launchpad.net/bugs/155531
[14:49] <_jz> that new  xserver-xorg-video-ati is pure crap !! i hope there will be a fix soon ! :/
[14:49] <baggins> do you have DRI?
[15:34] <tepsipakki> bryce: awake already? I thought about the colors in Projects
[15:34] <tepsipakki> bryce: could green be for done items, yellow pending, and red (?) for open
[15:38] <ubotu> New bug: #156666 in xorg (main) "Xorg restarts randomly while typing" [Undecided,New] https://launchpad.net/bugs/156666
[15:57] <tepsipakki> bbl ->
[19:06] <ubotu> New bug: #46463 in language-support-th (main) "Western keyboard layouts don't work after thai language login" [Medium,New] https://launchpad.net/bugs/46463
[19:24] <ubotu> New bug: #156573 in xorg (main) "xserver bug needs resolved" [Undecided,Incomplete] https://launchpad.net/bugs/156573
[19:25] <ubotu> New bug: #156341 in xorg (main) "ubuntu 7.10 and ATI = black screen?" [Undecided,New] https://launchpad.net/bugs/156341
[20:10] <ubotu> New bug: #154210 in compiz (main) "Massive memory leak in compiz (dup-of: 151168)" [Undecided,New] https://launchpad.net/bugs/154210
[20:11] <baggins> hum
[20:11] <baggins> lots of ATI issues, it seems with 7.10
[20:16] <tepsipakki> black screen issues are known
[20:47] <ubotu> New bug: #156801 in xserver-xorg-video-ati (main) "totem display`s vertical lines no movie Gutsy 7.10" [Undecided,New] https://launchpad.net/bugs/156801
[20:58] <baggins> heh
[20:58] <baggins> wow you can just see the dups rolling in. :)
[21:20] <ubotu> New bug: #156824 in xorg (main) "Xorg freaks out, hogs CPU, and possesses my laptop" [Undecided,New] https://launchpad.net/bugs/156824
[21:33] <bryce> heya tepsipakki
[21:33] <bryce> tepsipakki: I got a weird issue I'm trying to sort out with a user on i810
[21:34] <bryce> they've got a bunch of large LCD panels mounted that display info in kiosk mode, with Feisty installed
[21:34] <bryce> some of the LCD panels are mounted in landscape mode, others in portrait mode and rotated 90 deg with xrandr
[21:35] <bryce> oddly, a lot of the landscape (unrotated) displays are having failures where they lock up
[21:35] <bryce> the lock ups occur after several day's uptime (typically about 6 days, but as little as 40 min in some cases)
[21:36] <bryce> initially we suspected memory leaks, and in fact there were some memory leaks
[21:37] <bryce> but in tracking memory usage, it seems that in many cases there is no memory growth prior to the failure
[21:38] <bryce> do you know of any issues with i810 that could result in a lockup after an arbitrary amount of time, or have any ideas on why a i810 system would fail *unless* it were rotated with xrandr?
[21:42] <tepsipakki> so they are identical otherwise?
[21:44] <bryce> yes
[21:44] <tepsipakki> indeed sounds strange.. what bug is it?
[21:44] <bryce> exactly the same hardware and software.  They're mounted different, and one set is rotated
[21:45] <bryce> mark tardiff reported it to me, but apparently he hasn't put in a bug report on it for some reason
[21:46] <bryce> we've not been able to find an error message or backtrace
[21:47] <bryce> (honestly I'm still not convinced that it's an Xorg issue)
[21:47] <tepsipakki> I'm afraid I don't have any ideas either
[21:47] <bryce> ok thanks
[22:05] <ubotu> New bug: #156839 in linux-restricted-modules-2.6.22 (restricted) "nvidia graphics cat not detected" [Undecided,New] https://launchpad.net/bugs/156839
[22:30] <ubotu> New bug: #154818 in xorg (main) "X broken by upgrade to Gutsy" [Undecided,Incomplete] https://launchpad.net/bugs/154818
[22:46] <ubotu> New bug: #82577 in xfce4-terminal (main) "Terminal does not work on Xubuntu feisty (dup-of: 91849)" [Low,Invalid] https://launchpad.net/bugs/82577
[22:46] <ubotu> New bug: #133088 in xfce4-terminal "xubuntu terminal (xfterm4) dies, kills X (dup-of: 91849)" [Undecided,New] https://launchpad.net/bugs/133088
[23:38] <ubotu> New bug: #149864 in xorg (main) "Problems with x.org after update." [Undecided,Incomplete] https://launchpad.net/bugs/149864
[23:45] <pcjc2> hi
[23:45] <pcjc2> lots of flux on bugs today
[23:46] <pcjc2> bryce: (or anyone) is there any way we can get launchpad to fix the mime type of Xorg.0.log and Xorg.0.log.old etc..?
[23:46] <bryce> heya pcjc2
[23:46] <bryce> hmm, good thought
[23:47] <bryce> I'm not really sure, but maybe you could ask on #ubuntu-devel?
[23:47] <pcjc2> ok, I'm subscribed to the launchpad beta list, might be worth asking there
[23:47] <pcjc2> Xorg*log* -> text/plain
[23:48] <bryce> yeah
[23:48] <pcjc2> Not a lot of response from the Intel guys...
[23:48] <bryce> nope :-(
[23:48] <pcjc2> what are they up to (coding driver support for their latest unreleased chipset in secret?)
[23:48] <bryce> I see they're listed as attending Barcamp, so if that's true, I'll be seeing them this weekend
[23:49] <bryce> no idea
[23:49] <pcjc2> aha, say hello for me!
[23:49] <bryce> will do; I also plan to query them about -intel bugs
[23:49] <bryce> oh hey btw, I was a busy bee last night...
[23:49] <bryce> https://wiki.ubuntu.com/X/Patches
[23:50] <pcjc2> We've done the hard parts... just need them to review the patches, or investigate the _why_ now we know the workarounds / fixes
[23:50] <bryce> I gathered a listing of -intel (and other) patches for reviewing
[23:50] <bryce> most of those are probably crap patches, or ones we already have, but probably worth a look
[23:50] <pcjc2> wow... thats a lot of patches
[23:51] <bryce> if you could review them, and mark ones that look irrelevant to help narrow the list, it'd be a big help
[23:51] <bryce> I'm looking from the direction of going through our bug reports and see if any match with these patches
[23:52] <bryce> in which case I'll build one or two -intel rollups with some patches for folks to test with
[23:52] <pcjc2> some of those are backports from git
[23:52] <pcjc2> I was meaning to email you
[23:52] <bryce> right, all the ones marked origin 'xorg git'
[23:52] <pcjc2> (but haven't fixed my laptop install yet.. am on a different machine now0
[23:52] <pcjc2> )
[23:53] <pcjc2> hah... didn't spot that!
[23:53] <pcjc2> no.. some of the Fedora ones I recognise form git too
[23:53] <bryce> yeah, so those will come automatically if/when we get a new -intel release
[23:53] <pcjc2> I think we need to put together a patch with the 855 fixes, and push into Hardy
[23:53] <bryce> but if we can key up some of these to high priority issues in the intel tracker, we could sru them into Gutsy
[23:54]  * bryce nods
[23:54] <pcjc2> (We might consider my startup without blinking lots patch for a future push to Hardy)
[23:54] <pcjc2> Sounds like pushing those fixes closes a few bugs, and we can see what is left
[23:54] <pcjc2> I might not be able to look at these tonight (want to fix my laptop install, and its already 12PM)
[23:55] <pcjc2> will try to do so in a day or so..
[23:55] <bryce> no prob
[23:55] <bryce> yeah just wanted to mention it since I'm off tomorrow, traveling friday, and then in conference mode for the next 2 weeks 
[23:56] <bryce> I should still be around online but intermittently, and my productivity is probably not going to be as high; I figure I'll mostly focus on bug triaging and other random bits and pieces
[23:56] <pcjc2> The intel git tree has changed loads since 2.1.1
[23:57] <bryce> yup
[23:57] <pcjc2> Do you know if they planned to do a bugfix release in the 2.1 series, or just finish what they've got in HEAD now?
[23:57] <bryce> I went through the full changelog in git to identify this shortlist of "interesting" changes
[23:57] <bryce> I've no idea
[23:57] <pcjc2> (might be worth asking them that)
[23:57] <bryce> I've been speculating about a 2.1.2 but that's just me
[23:57] <bryce> yup definitely
[23:58] <bryce> oh also, if there are patches you have or know of, that we should definitely include either in Hardy or as a backport or update to Gutsy, can you add them to that X/Patches page?  I can then roll them up and take care of processing them through from there.
[23:58] <jcristau> kyle was supposed to do 2.1.2 a while ago, but...
[23:59] <bryce> jcristau: do you know if anyone is planning on picking that up?
[23:59] <jcristau> i don't