[05:15] <bryce> ok, revert dialog seems to work, although my devel box for some reason borks up when setting to a lower resolution.  Only piece of hw I have that does that though.  Odd.
[05:27] <bryce> http://people.ubuntu.com/~bryce/Testing/XrandrGui/xrandrgui-04.png
[08:10] <bryce> tjaalton: I see you've already been active on bug 184651, so probably already know about the patch attached to it, but in case not, I wanted to make mention of it
[08:10] <ubotu> Launchpad bug 184651 in xorg-server "Crash when starting gnome-settings-daemon" [High,In progress] https://launchpad.net/bugs/184651
[08:10] <tjaalton> it's fixed upstream, and the patch is in debian too and was on my local tree
[08:10] <bryce> that bug got mentioned at the distro team meeting as high priority by evand and cjwatson (who are on one of the dupes of that bug )
[08:10] <bryce> awesome
[08:10] <tjaalton> shouldn't it have been milestoned then?-)
[08:11] <bryce> hmm, seems to be milestoned
[08:14] <tjaalton> ah, right
[08:14] <tjaalton> duh
[08:16] <bryce> seb128: http://people.ubuntu.com/~bryce/Testing/XrandrGui/xrandrgui-04.png
[08:16] <seb128> hey bryce
[08:16] <seb128> ah, nice!
=== seb128_ is now known as seb128
=== seb128_ is now known as seb128
=== seb128 is now known as seb128_
=== seb128_ is now known as seb128
[10:48] <bryce> seb128: patches, packages, and debs posted to bug #197673
[10:48] <ubotu> Launchpad bug 197673 in gnome-control-center "gnome-display-properties should revert change automatically if not acknowledged" [High,In progress] https://launchpad.net/bugs/197673
[10:48] <seb128> bryce: excellent
[10:48] <bryce> needs testing next
[10:50] <bryce> it would be nice to get the gnome-desktop patch uploaded, because it's a dependency for the other two.
[10:51] <bryce> also, don't forget the three updated patches at http://people.ubuntu.com/~bryce/Testing/XrandrGui/
[10:51] <bryce> these also need integrated/tested.
[10:51] <bryce> night.
[10:53] <seb128> bryce: well, you have upload rights now ;-)
[10:53] <seb128> bryce: do you want me to test those and upload if that works correctly on my hardy?
[10:54] <seb128> bryce: 'night
[11:16] <ubotu> New bug: #210646 in xorg-server "After xorg and gtk updates many programs run extremely slow" [Undecided,New] https://launchpad.net/bugs/210646
[11:16] <ubotu> New bug: #210652 in linux-restricted-modules-2.6.24 (restricted) "[Hardy] ltmodem driver missing" [Undecided,New] https://launchpad.net/bugs/210652
[11:18] <ubotu> New bug: #210660 in compiz (main) "compiz.real crashed with SIGSEGV when attempting to switch users (dup-of: 160264)" [Undecided,New] https://launchpad.net/bugs/210660
[11:19] <ubotu> New bug: #210390 in xserver-xorg-video-radeonhd (universe) "unable to rotate screen using gnome-display-properties" [Wishlist,Confirmed] https://launchpad.net/bugs/210390
[11:46] <dennda> bryce: I am sorry for not being very responsive. I am still a bit busy but I hope we can start working on debugging tomorrow
=== seb128_ is now known as seb128
[12:31] <ubotu> New bug: #210740 in xserver-xorg-video-intel (main) "gnome-display-properties: resolution change does not do anything for internal notebook display" [Undecided,New] https://launchpad.net/bugs/210740
[13:36] <ubotu> New bug: #210780 in xserver-xorg-video-intel (main) "X slower after upgrade to 4GB RAM" [Undecided,New] https://launchpad.net/bugs/210780
[15:21] <ubotu> New bug: #208428 in ubiquity (main) "Ubuntu does not install (dup-of: 184651)" [Undecided,New] https://launchpad.net/bugs/208428
[15:41] <ubotu> New bug: #210830 in xdm (universe) "[hardy] XDM: huge font size" [Undecided,New] https://launchpad.net/bugs/210830
[16:15] <bryce> seb128_: with the three updated patches, what needs to happen is to replace the corresponding patches in the three packages, and then update all the other patches as needed since some of the code changes may cause minor breakage.
[16:15] <seb128_> bryce: ok
[16:15] <bryce> dennda: ok no prob, yeah I know how it goes re:busy.  
[16:16] <seb128_> bryce: could you try to remove debug g_print calls in those patches? I would like to not have .xsession-errors flooded with non issues in hardy
[16:17] <bryce> seb128_: by "the three updated patches" I mean the redhat patches I posted at http://people.ubuntu.com/~bryce/Testing/XrandrGui/, not the revert dialog patches
[16:17] <seb128_> ok
[16:17] <seb128_> let's go by steps and get the revert changes in first
[16:18] <bryce> the revert dialog patches aren't ready for upload yet - in addition to the g_print() calls there's at least one situation I know of that will cause it to not work right
[16:18] <seb128_> ok
[16:18] <seb128_> also I commented on the bug, I just had a quick look to the gnome-desktop one
[16:19] <bryce> well, if you can work on the new redhat patches, I can continue work on the revert dialog to get that done in the meantime, and then help in with what remains for the redhat patches
[16:19] <seb128_> you like file in the return false cases
[16:19] <seb128_> s/like/leak
[16:19] <seb128_> in what order do you want to do things?
[16:19] <seb128_> update to current redhat versions first
[16:19] <seb128_> and then do the undo?
[16:20] <bryce> I think the revert dialog should get uploaded first; it's almost done.  I expect once the new redhat stuff is packaged we'll need to test it a day or so
[16:23] <seb128__> re
[16:23] <seb128__> sorry sucking dsl line today
[16:24] <seb128__> <seb128_> ok
[16:24] <seb128__>  btw you need to rebase your gnome-desktop changes on the current hardy version
[16:24] <seb128__>  the upload was only a shlibs update
[16:24] <seb128__>  so no conflict there, just the changelog and the .shlibs which changed
[16:24] <seb128__> bryce: ^ dunno if you got that before the disconnect
[16:24] <bryce> oh ok, I'd checked the base before I started but it must have been updated in the meantime
[16:25] <seb128__> yes, I did update yesterday to fix a bug
[16:35] <ubotu> New bug: #210861 in xserver-xorg-video-intel (main) "X server crashes when compiz is enabled and I try to use -vo xv in MPlayer" [Undecided,New] https://launchpad.net/bugs/210861
[17:40] <dennda> bryce: In which language is the new gnome-display-properties written?
[17:41] <dennda> I can't seem to find the source
[17:41] <dennda> (I am experiencing quite a few bugs and I'd love to help fixing all of them)
[17:43] <seb128> dennda: C
[17:43] <seb128> dennda: apt-get source gnome-control-center
[17:44] <dennda> gna
[17:44] <dennda> don't know C yet, unfortunately
[17:44] <dennda> was hoping it was python
[17:46] <bryce> most of the meat of the code is actually in gnome-desktop
[17:46] <bryce> dennda: well if you care to learn C, I'm available to answer questions
[17:47] <dennda> bryce: I do, but that'll be some point in the future. Many things to do at the moment
[17:47] <dennda> but thanks
[17:54] <dennda> Hm are there patches for X3100 still in the queue? (Video has some bugs with compiz enabled)
=== seb128_ is now known as seb128
[21:35] <bryce> phoronix test suite released (GPLv3)
[21:53] <tormod> hi there! I find it alarming how many GL screensavers are crashing nowadays, see https://bugs.edge.launchpad.net/ubuntu/+source/xscreensaver/ Of course most of them are nvidia and fglrx...
[21:54] <tjaalton> hey, I've witnessed matrixview hanging my coworkers desktop :)
[21:54] <tjaalton> on nvidia
[21:56] <bryce> yeah I've just triaged all the -fglrx bugs, and it seems there are a lot of DRI/DRM/GLX type of issues
[21:56] <bryce> from the limited amount I've dug into them, I wonder if a kernel module is missing or something
[21:57] <bryce> I cut the number of -fglrx bugs in l-r-m by half :-)
[21:57] <tormod> wouldn't a missing module just disable DRI and actually avoid the crashes?
[21:57] <bryce> well you'd think so
[21:58] <bryce> I'm not really sure though - like I said I didn't dig into any of the bugs very far
[21:58] <bryce> tormod: btw ati has been bugging me for our "top 5 bugs", so if you have some to suggest, I can pass them up the chain
[21:58] <tormod> (wildly guessing) could it be a compiler issue, some new defaults, broken optimizations etc?
[21:58] <bryce> I'm guessing they'll just say it's not their problem (kernel issue) or some such, but maybe then we'd have more info
[21:59] <bryce> an ABI issue would be more likely I'd guess
[21:59] <tormod> ati? as in Alex and Dave?
[21:59] <bryce> I don't really know enough about how the fglrx<->kernel integration is set up to say
[21:59] <tormod> or AMD?
[22:00] <bryce> ah, I mean the ATI engineers inside AMD who develop fglrx
[22:01] <tormod> hard to pick the "top 5" since no reports have a useful backtrace
[22:02] <tormod> they could have a look at my xscreensaver link above
[22:03] <bryce> yeah that's my thought too
[22:03] <jcristau> of course they don't have a useful backtrace, it's proprietary crap
[22:03] <bryce> jcristau: well sometimes the surrounding X calls have some clues
[22:04] <bryce> but unfortunately most of the auto-gathered ones in launchpad don't even have that, so they're even more useless than usual ;-)
[22:04] <Ng> tjaalton: do you ever see a green console before/after suspend?
[22:04] <tjaalton> Ng: I've seen that yes
[22:05] <Ng> it started happening on mine a couple of days ago and has done on every subsequent suspend/resume (I've not rebooted yet)
[22:05] <tjaalton> I'll check again after -13 is usable
[22:06] <bryce> tormod: heh, can you see all the private crash bugs in xscreensaver?
[22:06] <bryce> you're not kidding about there being a ton of crash bugs
[22:06] <tormod> bryce: no, ah don't tell me I just see the top of the iceberg
[22:07] <Ng> tjaalton: don't spose there's anything I can do while it's like this, is there? I really need to reboot to get an unoopsed kernel so I can get some debugging info for another bug ;/
[22:07] <Ng> tjaalton: s/do/do to debug this/, that is
[22:08] <bryce> tormod: there's another 9 marked private.  I'll unprivate them
[22:10] <tjaalton> Ng: I'm not sure.. maybe -13 is better since there were some changes related to drm
[22:10] <bryce> there we go
[22:10] <tormod> there are also some r300 and radeon crashes. Is apport working better than before?
[22:11] <bryce> I'd talked with pitti about it a couple weeks ago; apparently it had broken and stopped doing it's work correctly, but he kicked it and said it should work properly now
[22:12] <tormod> bryce: that might explain why these crashes started to flood a few days ago
[22:13] <tormod> btw why is "cdrom" listed in NonfreeKernelModules?
[22:13] <Ng> tjaalton: ok
[22:13] <bryce> tormod: heh I noticed that too.  nfi
[22:15] <bryce> maybe this has to do with it?  http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg32430.html
[22:15] <ubotu> New bug: #209414 in ubuntu "Atheros 5007 reported incorrectly as "Atheros Communications, Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01) " on Amilo 1718li Laptop in Hardy Heron Beta (dup-of: 182489)" [Undecided,New] https://launchpad.net/bugs/209414
[22:16] <bryce> oooh, that could explain the performance bugs we got too
[22:17] <ubotu> New bug: #210749 in xorg (main) "Openoffice spreadsheet crashes x" [Undecided,New] https://launchpad.net/bugs/210749
=== seb128_ is now known as seb128
[22:21] <tormod> amd64 seems to be overrepresented.
[22:22] <bryce> interesting
[22:22] <bryce> I've noticed a surprising number of amd64 bugs in general
[22:27] <tormod> This gives a good overview: https://bugs.edge.launchpad.net/ubuntu/+source/xscreensaver/?field.searchtext=crashed+with&orderby=title
[22:33] <bryce> are you able to reproduce the problem?  I'd be interested to hear if setting Option "AIGLX" "off"  has any effect
[22:33] <bryce> it's weird, when I search on "[fglrx]" in xscreensaver, only 3 bugs come up
[22:34] <tormod> bryce: search and sort in LP has been broken for ages
[22:34] <bryce> bleah
[22:34] <tormod> you have to make the URL yourself, like I did above.
[22:35] <bryce> ahh
[22:35] <bryce> 12 bugs - https://bugs.edge.launchpad.net/ubuntu/+source/xscreensaver/?field.searchtext=fglrx&orderby=title
[22:36] <ubotu> New bug: #211043 in linux-restricted-modules-2.6.24 (restricted) "could not find module b43" [Undecided,New] https://launchpad.net/bugs/211043
[22:38] <bryce> hrmph, these backtraces are less than useful.  All I can tell is it has something to do with GL in fglrx
[22:39] <bryce> and you're right; amd64 is overrepresented
[22:40] <tormod> yes there are also some [r300 amd64] crashes
[22:40] <bryce> hm, bug 179042 maybe?
[22:40] <ubotu> Launchpad bug 179042 in linux-restricted-modules-2.6.24 "[fglrx] fglrx, compiz and opengl conflict" [Medium,Triaged] https://launchpad.net/bugs/179042
[22:40] <tormod> anyone here having that combination?
[22:42] <bryce> here's another, that got put into l-r-m already - 181121
[22:42] <bryce> probably all those xscreensaver bugs could be duped onto that one
[22:43] <tormod> bug #181121
[22:43] <ubotu> Launchpad bug 181121 in linux-restricted-modules-2.6.24 "[fglrx] glplanet crashed with SIGSEGV" [Undecided,Incomplete] https://launchpad.net/bugs/181121
[22:44] <tormod> what do you mean it got put into l-r-m?
[22:45] <tormod> oh I got it
[22:46] <tormod> do you have a bughelper script to do mass-reassigning?
[22:46] <bryce> sorry, that was a GL game not a screensaver, but it looks like the same issue
[22:46] <bryce> no, but bdmurray does
[22:46] <tormod> glplanet is also a screensaver
[22:46] <tjaalton> tormod: no I mean that according to the changelog the driver manager doesn't recommend installing fglrx anymore, if the user is running r300 or whatever the fglrx supports but also has good support in -ati&mesa
[22:47] <bryce> ahhh
[22:47] <bryce> ok even better.  I assumed it was some sort of game
[22:48] <tormod> tjaalton: re what?
[22:49] <tjaalton> tormod: re: "what do you mean it got put into l-r-m?" (or was that not for me :)
[22:49] <tormod> bryce 181121 is a poor dup, since it should already have been closed for no response.
[22:49] <tormod> tjaalton: not for you :)
[22:49] <tjaalton> tormod: awww :)
[22:50] <bryce> tormod: ahh, but it's reported by bdmurray who is the Canonical Bugmeister
[22:51] <tormod> bryce: right! So if he doesn't follow up, who will? :)
[22:51] <bryce> precisely
[22:52] <bryce> also I subbed ted gould who maintains xscreensaver; he should also be eyeballing this one
[22:52] <tormod> would you like to have 181121 assigned to you? otherwise I close it.
[22:53] <bryce> I'd already asked brian about this bug this morning, but said he could look at it when he has time (I think he has bug hug day events going on presently)
[22:53] <tormod> ok here you are.
[23:30] <bryce> tormod, I gather fglrx just gained AIGLX support in the latest version.  Maybe it's buggy?
[23:30] <bryce> I've encouraged a bunch of the -fglrx bug reporters to test turning it off.
[23:31] <tormod> would make a lot of sense. when did the latest fglrx get in?
[23:32] <tormod> off-topic: is the data I submit thru hwtest available on LP?
[23:33] <bryce> afaik the data is not available :-/
[23:33] <bryce> last fglrx update was January I think
[23:34] <tjaalton> no, early March
[23:34] <tjaalton> Tue 11th
[23:34] <bryce> hmm, my l-r-m checkout must be old
[23:35] <bryce> oh I see what I did.  duh
[23:35] <tjaalton> I'm about to upload a new one
[23:36] <tormod> early March, then apport came back and crash bugs started to flood? could make sense.
[23:36] <tormod> what about all the nvidia bugs?
[23:40] <ubotu> New bug: #211066 in linux-restricted-modules-2.6.24 (restricted) "Cannot upgrade linux-restricted-modules-generic" [Undecided,Confirmed] https://launchpad.net/bugs/211066
[23:40] <tjaalton> here we go, the first bug about no lrm available for -14
[23:43] <Ng> tjaalton: brightness works for me in -14 \o/
[23:43] <Ng> although gdm is being very very strange
[23:44] <Ng> I had to comment out GtkTheme=Human in gdm.conf to get the greeter to not consume a whole core in a gtkrc loading loop
[23:46] <ubotu> New bug: #211074 in linux (main) "[hardy] no nvidia module FATAL with linux-image-2.6.24-14-generic (dup-of: 211066)" [Undecided,Incomplete] https://launchpad.net/bugs/211074
[23:46] <ubotu> New bug: #211076 in linux-meta (main) "Hardy, linux-restricted-modules broken (dup-of: 211066)" [Undecided,New] https://launchpad.net/bugs/211076
[23:47] <bryce> I do have to say that the fglrx bug reporters are surprisingly responsive compared with the -intel reporters
[23:47] <bryce> but maybe that's just because the reports are all much more recent
[23:51] <ubotu> New bug: #210905 in mumble (main) "not push-to-talk - xevie problem" [Undecided,Confirmed] https://launchpad.net/bugs/210905
[23:55] <ubotu> New bug: #211089 in ubuntu "kernel update left Ubuntu without restricted drivers (dup-of: 211066)" [Undecided,New] https://launchpad.net/bugs/211089
[23:56] <tjaalton> Ng: yeah brightness works, tried it with -13