[03:58] james_w: btw I've finished the gnome-desktop update, I just need to test it and then will upload it, perhaps tonight [05:58] tests ok; gnome-desktop uploaded [06:16] hmm, looks like seb128 already did gnome-settings-daemon [06:46] bryce: great, I'll test them in a little while. [07:11] New bug: #214439 in xserver-xorg-video-tdfx (main) "Quake engine games freeze if video settings changed" [Undecided,New] https://launchpad.net/bugs/214439 [07:16] tdfx wtf? [07:18] 3dfx Banshee... interesting [07:20] New bug: #214442 in xserver-xorg-video-ati (main) "Time out error with r128 and some games" [Undecided,New] https://launchpad.net/bugs/214442 [07:21] bryce: what would you like me to work on today? [07:22] I can test the uploads, and also seb uploaded g-c-c, so I think the patches need updating there again. [07:22] james_w: how far along are you with the gnome-control-center patches? Getting that uploaded is probably the next priority [07:23] they were pretty good I think, I'll update them and do some more testing, and then talk to seb about them. [07:23] presently, I'm working on a new patch to g-d to add a mess of null pointer checks. Seems like many of our bugs have been due to null pointers from g-d [07:25] so yeah, getting all the patches in g-c-c building properly, and getting that package would be the main goal today. [07:25] ok, sure [07:26] Looking over our bugs and that people are reporting problems still even after seb's last set of uploads (which I thought would fix those bugs), the new g-c-c changes unfortunately aren't going to solve that [07:26] so priority #2 after that is sorting out why 199960 and 210226 are still happening [07:27] the patch I'm doing may help with 210226 but it may just expose the null pointer at a higher level (which would be a good thing, but just one step) [07:29] in 199960, the reporters are getting pretty ornery and fussy, but I'm hopeful the g-s-d upload sorted it out - but not much word since the 3rd [07:30] 199960 is nice and easy to reproduce, which helps. [07:30] any idea how to reproduce 210226? [07:31] are you able to reproduce 199960? I've not been able to [07:31] I haven't reproduced 210226, but the backtraces are pretty clear [07:33] there were a bunch of unrelated issues lumped into 199960; I think the only remaining active was when running with Xgl, however I *think* the Apr 6th g-d/g-s-d uploads might have addressed that [07:33] I did "aptitude install xserver-xgl" and gnome-settings-daemon didn't start on the next login, so I assumed it was the bug, maybe it wasn't [07:33] if not, then maybe we need an explicit check for Xgl in g-s-d (and probably g-c-c) like the code I posted in comment 57 [07:34] I tested on Monday [07:35] I'll test again today. [07:53] bryce: have you sent any of the other patches that we are carrying upstream? [07:56] my plan has been to send them once we verified they built against the latest code [07:56] on my list so far are these three for gnome-desktop: [07:56] 102_gd-xrandr-null-pointer-check.patch [07:56] 103_gd-xrandr-xerror-check.patch [07:56] 104_gd-randr-revert-support.patch [07:58] I'm not sure if I should send in the g-s-d patch; I'm not sure checking for xrandr versions is really that necessary. ubuntu and fedora are both running xrandr 1.2 servers, so... might be useful in general, but I don't know [07:58] I want to go through the g-c-c patches once your work's uploaded, and send in a few of those. I think half or so will be relevant for them [07:59] yeah, that's what it looks like to me. [08:00] the revert dialog requires 104_gd-randr-revert-support.patch? [08:00] yes [08:00] ok, thanks. [08:01] I'd asked ssp previously about that but never got a response, and am guessing he won't be so interested, but who knows. [08:01] I'm going back to bed for a short nap, but I'll start with g-c-c after that. [08:01] ok cool [08:06] james_w: I'll be cc'ing the gnomecc list (it's pretty low traffic if you want to subscribe during this project) [08:12] hello [08:12] hi [08:12] bryce: hey [08:13] bryce: they changed all that in gnome-desktop since my patch update on monday or did you list changes which we already had in your changelog? [08:14] I listed changes we already had [08:14] ah ok, that was confusing [08:14] I think you didn't see my update and redid the work or something [08:14] s/think/though [08:15] actually that's the case :-/ [08:15] :-( [08:15] but we dicussed it on IRC some days ago? [08:15] but I noticed right after uploading and see that we had almost exactly the same patch [08:15] I thought you had said you didn't have time to work on it, so I had it on my todo list [08:15] hum [08:15] then I sent this mail to colin and you [08:16] james_w joined the chan [08:16] and we discussed the changes [08:16] you even asked me when I did take the snapshot [08:16] I copied the redhat viewcvs from saturday and you said that was newer than your snapshot [08:16] no? [08:16] I assumed you took the snapshot and handed it over to james_w [08:17] so I asked james_w before I started if he'd had a chance to work on it, and he said no, so I said I had some time and would help by doing that bit [08:17] ok, I though I had been clear when I asked you guys to test the new hardy versions [08:17] I thought you meant the gnome changes in general [08:17] hum, k [08:17] so to be clear I updated this one [08:17] and the gnome-settings-daemon one too [08:18] there was just the gnome-control-center one to update, that's what I explain on the chan to james_w [08:18] I though you read that too, sorry about the confusion [08:19] no prob, actually the patches for gnome-desktop applied cleanly without issue, so the time was mostly just reviewing all the changes, which I planned to do regardless [08:19] alright [08:19] btw they broke the ABI, dunno if you noticed [08:20] I had to add a breaks in the package on monday due to that [08:20] yeah I ran into that; confused me a bit [08:20] can you tell me more about it? [08:20] ok, so the only change in your update is the unstable define renamed apparently [08:21] so no breakage in this one [08:21] good ;-) [08:22] right; in fact my change just adds another define test we can opt to start using if we wish [08:22] since "ONLY_IN_FEDORA" clearly is not 100% true ;-) [08:22] right ;-) [08:22] but in general it probably doesn't matter to anyone, unless they're browsing code [08:23] btw why did you change the configure.in? [08:23] I didn't change that, but I wonder if it's a difference between the fedora rpm patch, and what I took from ssp? [08:23] -#GNOME_COMMON_INIT [08:24] +GNOME_COMMON_INIT [08:24] etc [08:24] they likely have extra debug macros used in git [08:24] that they don't use for the packaging [08:24] you reenabled those [08:24] yeah, I noticed that too but don't know what it does. I can revert that part if you'd like [08:24] if that builds that's alright [08:24] it builds and I tested it and seems to work properly [08:25] alright, good [08:25] let's wait for james_w gnome-control-center patch update now [08:25] I'm wondering if somebody tried the current version using xgl [08:25] users tend to complain loud when things are broken [08:26] yeah I'm wondering that too [08:26] but they don't bother adding a comment when things are fixed usually [08:26] james_w said he can recreate the xgl issue fairly easy and will test it [08:26] you know I get that with most X bugs too ;-) [08:26] :-) [08:40] New bug: #214470 in xorg (main) "gdm screen uses virtual screen size instead of actual" [Undecided,New] https://launchpad.net/bugs/214470 [08:51] bryce: isn't bug 205979 a dupe of 184651? [08:51] Launchpad bug 205979 in xorg-server "xserver crash on exit in CloseDownDevices and SrvXkbFreeGeomRows" [Unknown,Confirmed] https://launchpad.net/bugs/205979 [08:57] tjaalton: hmm let me look [08:59] darn, I nearly figured that one out myself. guess I'm duplicating a lot of work lately! ;-) [08:59] heh :) [09:00] I've now got six patches for xorg-server, mostly from upstream and one that defaults to intel instead of i810 [09:01] hmm, their patch doesn't match the direction I was going, but I bet it just solves it from a different (likely better) direction [09:03] hmm, and looking at the backtraces and steps to reproduce, they're *slightly* different [09:04] I'm not 100% sure that the patch for 184651 will also solve 205979, but I think it's possible and it wouldn't surprise me at all [09:05] maybe ask again after this has been uploaded and then mark as dupe if it's fixed (and close the upstream report) [09:26] New bug: #214484 in xorg (main) "Standard NV driver doesn't work with G70 cards at 2560x1600" [Undecided,New] https://launchpad.net/bugs/214484 [09:29] hmmh, I had some mesa patches to add, but now I can't find any.. "assigned to" ftw [09:30] lunch -> [09:30] bryce: if you have anything you want me to look at, just ask [09:31] I don't have any patches for the xserver at the moment; I've been uploading other things directly as I run across them [09:32] bugwise, the top priorities right now are the 4 x-related bugs at https://bugs.launchpad.net/ubuntu/+bugs?field.milestone%3Alist=829 [09:32] did you guys made some video driver changes which could have broken the dpi values detected on some cards? [09:34] I uploaded some patches for -intel the past few days, including one that updates a bunch of quirks, a few of which could correct some dpi issues [09:34] other than -intel, I've not updated any other drivers [09:34] ok [09:35] https://bugs.launchpad.net/ubuntu/+source/evince/+bug/213745 [09:35] Launchpad bug 213745 in evince "PDF pages appear extremely small in evince" [Medium,Incomplete] [09:35] upstream thinks it could be a dpi detection issue, I've asked for xdpyinfo logs and what card those users are using [09:36] * bryce nods [09:37] for font dpi issues we also need to see their EDID, so it would be good to have their Xorg.0.log's [09:37] ok [09:38] asked that on the b ug [09:38] bug [09:38] one thing to look for in EDID is the monitor's physical dimensions, which is the thing that messes up dpi calculations [09:38] anyway, off to bed for me. night [09:38] 'night bryce [09:59] bryce: ok, those guys seem to all have intel cards [09:59] bryce: so I would say you broke the intel driver :-) [10:11] New bug: #213745 in xserver-xorg-video-intel (main) "PDF pages appear extremely small in evince" [High,Confirmed] https://launchpad.net/bugs/213745 [10:11] New bug: #214499 in linux-restricted-modules-2.6.24 (restricted) "Recompiled Ubuntu kernel - nvidia driver does not load (comm: modprobe Not tainted)" [Undecided,New] https://launchpad.net/bugs/214499 [10:16] New bug: #214501 in xkeyboard-config (main) "no dead keys in hardy" [Undecided,New] https://launchpad.net/bugs/214501 [10:19] on bug #214119 I heard that before and this was already before the libpciaccess merge. [10:19] Launchpad bug 214119 in xserver-xorg-video-amd "[HARDY] Koolu W.E. (ION A603) does not detect higher resolution than 800x600" [High,Triaged] https://launchpad.net/bugs/214119 [10:20] as far as I can tell, this is yet another case of a buggy BIOS that will require workarounds in x86emu. The same driver works fine if compiled against an older X and using an xorg.conf [10:32] New bug: #209759 in firefox (universe) "firefox does not display scaled jpegs (dup-of: 182038)" [Undecided,Confirmed] https://launchpad.net/bugs/209759 [10:56] New bug: #214513 in xserver-xorg-driver-i810 "mouse i810" [Undecided,New] https://launchpad.net/bugs/214513 [11:06] New bug: #214517 in xserver-xorg-video-intel (main) "supend/resume broken with latest intel driver & kernel 2.6.24-15 " [Undecided,New] https://launchpad.net/bugs/214517 [12:10] New bug: #214527 in evince (main) "Evince rendering very small text (dup-of: 213745)" [Low,Invalid] https://launchpad.net/bugs/214527 [12:16] New bug: #208483 in ubiquity (main) "installer crashes in keyboard layout selection (dup-of: 184651)" [Undecided,New] https://launchpad.net/bugs/208483 [12:19] seb128: hi. I've updated the g-c-c patch: http://jameswestby.net/scratch/g-c-c.diff [12:19] james_w: excellent! [12:20] it's now not showing any name for my monitor, I'll look in to why. [12:21] I also didn't change the #define to be the new one bryce added support for, so it still says FEDORA. [12:22] New bug: #212373 in firefox-3.0 (main) "PNG error (dup-of: 182038)" [Undecided,Incomplete] https://launchpad.net/bugs/212373 [12:42] james_w: ok, the applet runs, that broken the "cancel the changes" action though, and I've no monitor description written either [12:42] s/broken/broke [12:43] the cancel button in the timer window? [12:43] james_w: should I upload or do you want to give a try at fixing at least the cancellation thing before? [12:43] yes [12:43] or using esc [12:43] it worked here. [12:43] do you get any output on the terminal? [12:46] james_w: that's working now, go figure [12:46] xrand1.2 is still quite broken though [12:46] I thought it would work alright on intel, but it doesn't :-( [12:47] when switching to a lower resolution and back the screen has the small resolution area displayed correctly and the borders corrupted [12:48] mvo: ^ compiz issue? [12:49] compiz seems to thing the corrupted border is the limit of the workspace too [12:49] I can move the xorg cursor there and use things under it correctly [12:49] but when doing a dialog dnd for example it stops and switch workspaces [12:51] seb128: I have a look once I finished debugging this bug #213566 issue [12:52] Launchpad bug 213566 in xkeyboard-config "dapper->hardy missing files on upgrade" [High,In progress] https://launchpad.net/bugs/213566 [12:52] ok [12:52] its a nasty one [12:52] james_w: ok, that seems already to me, thanks a lot for the work on it, I'll upload [12:52] james_w: btw do you have an opinion on whether we should use "Refresh Rate" or "Refresh rate"? [12:53] if you want to hang on a minute I think I might have fixed the name thing. [12:53] the upstream capplet is using "Refresh rate" [12:53] james_w: sure [12:53] I though upstream was using "Rate", and we patched it to use "rate", which I just reverted [12:54] bryce said that the usability guy (is that mpt?) said that we should use capital letters for labels, and all of the rest do. [12:54] james_w: if you do patch edition could ou remove the extra g_print? I don't think we make any use of those informations anyway and we should have only errors printing in .xsession-errors [12:54] sure, you want me to remove them all? [12:54] just the non error ones [12:54] we should still display failures [12:54] should I move them to something that would show up in .xsession-errors for debugging? [12:55] they do show up there already [12:55] that's why I want to clean those ;-) [12:55] at the moment it prints thing like [12:55] CRTC 49 Timestamp: 3792732 [12:55] Output 4e Timestamp: 3792732 [12:55] applying configuration. Clone: yes [12:55] etc [12:56] those should not be printed I think [12:56] that's just a detail though [12:56] yeah, I agree. [12:56] I want to clean .xsession-errors for hardy but too much to do [12:56] I'll do a mini goal and try to get that for 8.04.1 [12:57] do a mini goal = write a wiki page or something or tag bugs and try to get contributors helping to clean those [12:57] I've got it showing "Cloned Output" again, so it's wrong, but less wrong. [12:57] did you had this label already using the hardy version? [12:57] there's something wrong with the clone checkbox, so I'll have a quick look to see if I can debug that. [12:58] ok [12:58] yes, it was wrong in the previous versions as well. [12:58] ok, so at least that's not a regression [12:58] brb, need to restart xorg to get an usuable workspace again [12:58] I think it's a problem with gnome-desktop patch though, so it shouldn't stop us uploading this. [13:00] re [13:03] Is there something better to use than g_print for real error messages? [13:03] aside from a popup of course? [13:04] g_warning and g_error [13:05] g_error call abort though so it's only to use on real errors [13:05] and g_warning is for error worth reporting but which should stop the program [13:06] thanks [13:08] and also g_messages for normal messages [13:08] what is nice is that you can change the log handler so make those go in a debug log rather than on std* [13:29] oh, that is not a cool bug [13:30] using xrand1.2 breaks the dpi informations on intel [13:30] which means once you have used the new capplet you will have broken dpis and the evince issue we got several bugs about [13:30] ouch [13:35] that breaks the web browse fonts too [13:36] and that was due to the latest change? [13:39] I've no idea, I didn't notice the issue before [13:39] no, seems to be an upstream issue [13:39] I'm going to downgrade the intel driver now [13:40] ok, the changes seem to have added only some quirks [13:40] and people started reporting that some days ago [13:40] right [13:40] https://launchpad.net/bugs/178558 suggests the issue is not new [13:40] Launchpad bug 178558 in xulrunner-1.9 "Firefox 3.0 makes everything annoyingly huge" [High,Fix released] [13:40] see https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/178558/comments/50 [13:41] yeah [13:41] I think evince was not sensible to wrong dpi before or something [13:41] so we didn't get lot of bugs about the issue [13:42] or we got firefox font issues bugs which are not easy to track [13:43] maybe with X log, output of xrandr and xdpyinfo it would be possible to do something. random screenshots, not so much [13:43] jcristau: I can give you any information you need [13:43] jcristau: starting xorg xpydinfo shows a correct 120 dpi number [13:44] using xrand1.2 to set the same screen resolution I'm already using the xdpyinfo number goes to 1x1 [13:44] that's a dell D630 laptop using a intel 965 video card [13:44] using the current intel driver [13:45] heh, mine dropped from 106x105 to 87x85 [13:45] do you X log, preferrably with the ModeDebug option turned on? [13:45] meh [13:46] s/do you/& have an/ [13:46] jcristau: easy enough to get, where do I turn this option? [13:46] in the Device section [13:46] jcristau: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/213745 has several Xorg.0.log [13:46] Launchpad bug 213745 in xserver-xorg-video-intel "PDF pages appear extremely small in evince" [High,Confirmed] [13:46] jcristau: but I don't think they are using the debug mode [13:47] I'll try in a bit, I've things open that I don't want to close right now ;-) [13:47] (might be a good idea to set ModeDebug by default) [13:47] ok [13:47] let me know if those logs are useful already [13:48] eww [13:48] dimensions: 1280x800 pixels (40959x50175 millimeters) [13:48] resolution: 1x0 dots per inch [13:49] yeah, that's what you get after using xrandr1.2 [13:49] dimensions: 1440x900 pixels (37887x31871 millimeters) [13:49] resolution: 1x1 dots per inch [13:49] that's the value on my laptop [13:49] (II) intel(0): Printing DDC gathered Modelines: [13:49] (II) intel(0): Modeline "1280x800"x0.0 65.31 1280 1296 1328 1344 800 801 804 810 -hsync -vsync (48.6 kHz) [13:50] it was 120x120 before using xrandr [13:50] that 0.0 is broken [13:50] (II) intel(0): Printing DDC gathered Modelines: [13:50] (II) intel(0): Modeline "1440x900"x0.0 108.50 1440 1520 1600 1952 900 903 909 926 -hsync -vsync (55.6 kHz) [13:50] (II) intel(0): Modeline "1440x900"x0.0 108.50 1440 1520 1600 1952 900 903 909 926 -hsync -vsync (55.6 kHz) [13:50] I've those [13:50] seb128: what exact command? xrandr --output 'foo' --mode 1440x900? [13:51] jcristau: I'm using this new xrandr1.2 capplet from redhat that bryce backported [13:51] is the xrandr command line using 1.2 too? [13:51] hrm, actually it's "1024x768"x0.0 here too [13:51] same here [13:51] yes [13:51] so that's not it [13:51] modedebug would probably help [13:53] ok, sec, editing xorg.conf and restarting [13:54] was it a boolean? [13:54] do you have an url to the capplet source? [13:54] tjaalton: yes [13:55] jcristau: the patches are on http://people.ubuntu.com/~bryce/Testing/XrandrGui/ [13:56] jcristau: http://www.gnome.org/~ssp/randr/ is the upstream thing, I think that's using git [13:57] http://www.gnome.org/~ssp/randr/.git [13:57] New bug: #214561 in evince (main) "Evince shows pdfs file with a very small size (dup-of: 213745)" [Low,Invalid] https://launchpad.net/bugs/214561 [14:00] New bug: #214581 in nvidia-settings (universe) "[hardy] nvidia-settings window is displayed way too small" [Undecided,New] https://launchpad.net/bugs/214581 [14:02] jcristau: http://people.ubuntu.com/~seb128/Xorg.0.log [14:06] so at startup X sets your screen size to 304 x 190 [14:06] (mm) [14:06] as reported by your monitor [14:07] and then something goes crazy [14:07] as said if I don't use this capplet the xdpyinfo settings are correct [14:07] so it goes wrong when using the xrandr calls [14:08] the code which applies the settings seems to be in the gnome-desktop changes [14:08] randrwrap.c [14:08] it calls XRRSetScreenSize() [14:09] tjaalton: if you maintain xkeyboard-config in git for ubuntu you may want to sync with my latest uplaod [14:09] mvo: so what was the bug? [14:09] mvo: I noticed your latest comment.. maybe this bug went "unnoticed" when people upgraded to edgy.. [14:10] seb128: multiple ones, but the killer was wrong order of unpack and replacing files in /etc with symlinks that confused dpkg [14:10] mvo: and it's not maintained in git, unfortunately [14:10] ok [14:10] it's not maintained by XSF in Debian :) [14:10] tjaalton: it pretty servere, if it went unoticed than our QA back then was pretty bad [14:11] tjaalton: it kills the keyboard for anyone using the gnome-keyboard preferences [14:11] ugh [14:11] it depends on the unpack ordering for it to trigger, maybe we were just luck on dapper->edgy [14:12] the issue that xkeyboard-config is in universe (and should be in main) is still open though [14:12] could be yes [14:12] * mvo goes to the seeds [14:13] that was a bugger of a bug, happy to have nailed it down (works in my upgrade test environement, lts see if it works in the wild as well :) [14:15] width_mm = (width * 96.0) * 25.4; [14:15] height_mm = (height * 96.0) * 25.4; [14:15] [14:15] rw_screen_set_size (assign->screen, width, height, width_mm, height_mm); [14:15] so it's supposed to set dpi to 96 [14:15] except, maybe not [14:17] gotta run, bbl -> [14:17] hmm, shouldn't that be (width / 96.0) * 25.4? [14:18] hum, yeah [14:19] trying [14:21] seems likely to fuck things up, setting dpi to 1/96 instead of 96 :) [14:23] brbr [14:23] trying that change [14:27] jcristau: ok, nice catch, much better now ;-) [14:27] note for next time, don't blame xorg too quickly ;-) [14:27] cool [14:28] blaming red hat is a much better strategy! ;) [14:28] yeah ;-) [14:31] New bug: #214592 in xserver-xorg-video-intel (main) "[Hardy] OpenGL renders Wrong " [Undecided,New] https://launchpad.net/bugs/214592 [14:34] seb128: the clone checkbox isn't showing up as 'glade_xml_get_widget (xml, "clone_checkbox");' is returning NULL [14:34] there is '' in the glade file. [14:34] do you know enough about glade to offer any suggestions? [14:39] james_w: hum, looking [14:40] james_w: was glade_xml_new run with a different root widget? [14:41] james_w: so that clone_checkbox is not a child of whatever root was set to? (that might be a possible explaination for this behavior) [14:42] glade_xml_new (GLADE_FILE, NULL, NULL); [14:43] james_w: where is this clone widget? [14:44] james_w: is that the Mirror Screen one? [14:44] I'm seeing it at line 100 of "capplets/display/display-capplet.glade" [14:44] seb128: yes [14:44] it's displayed correctly for me [14:45] hmm, odd. [14:45] Do you have multiple screens? [14:46] no [14:46] I'm using a laptop right now [14:46] and it's not pluged to any monitor or dock [14:46] and this is with the latest changes I made? [14:47] using the debdiff you sent me some hours ago [14:47] odd. [14:47] james_w: http://people.ubuntu.com/~seb128/xrandr.png [14:48] I'll fix up what I have currently and pass that to you. [14:48] ok, thanks [14:48] I don't have the checkbox, or the "Detect displays" button. [14:50] did you install the glade? [14:50] or do you run from your source? [14:50] yeah, I'm just wondering whether it's not getting installed. [14:50] try to strace -e open gnome-display-properties 2>&1 | grep glade [14:50] then glade this one [14:50] and see if it's correct [14:52] yeah, it's not in the .deb and the one on my system is old. [14:52] thanks! [14:52] you are welcome [14:53] weird though [14:53] the debdiff you sent me works correctly and the glade is installed there [14:55] ah, it's in capplets-data [14:57] yes [14:57] I usually sudo dpkg -i *.deb ;-) [14:58] yeah, I'm using two machines, and I was too lazy to copy them all across. [14:58] It all seems to work nicely though. [14:59] cool [15:15] seb128: http://jameswestby.net/scratch/g-c-c.diff updated if you want to grab it again and do your thing [15:16] james_w: my thing being debuild? ;-) [15:16] oh, I thought you used sticky tape to make the .debs [15:18] my debian applicant manager made me rewrite my a rules without using debhelper or cdbs [15:19] I really appreciate the packaging tools since ;-) [15:33] james_w: good work, thanks [15:34] james_w: new revision uploaded to hardy [15:34] james_w: I get the issue you described I think though, I've only one screen and the clone options is checked by default so the monitor label is wrong [15:41] yeah, I think that's a problem in the -desktop patch, I asked bryce about it as I am not sure what the correct logic should be. [15:43] that's a minor point [15:43] and it's likely that redhat will fix it [15:43] next issue should be to look if it still bug under xgl [15:46] yep, I'm going to try that now. [15:55] xgl kills g-s-d, with a backtrace very similar to https://bugs.edge.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/210226 [15:55] Launchpad bug 210226 in gnome-settings-daemon "gnome-settings-daemon crashed with SIGSEGV in rw_screen_list_outputs()" [Medium,Confirmed] [16:31] New bug: #178274 in xulrunner-1.9 (main) "[hardy] firefox breaks on some pages with an X error (dup-of: 205599)" [Medium,Incomplete] https://launchpad.net/bugs/178274 [16:31] New bug: #184076 in midbrowser "gecko received an X Window System error (dup-of: 205599)" [Undecided,New] https://launchpad.net/bugs/184076 [16:31] New bug: #194782 in firefox-3.0 (main) "[hardy] firefox breaks on some pages with an X error (dup-of: 205599)" [Undecided,New] https://launchpad.net/bugs/194782 [17:01] New bug: #214652 in xorg (main) "Xorg freezes on logout in hardy" [Undecided,New] https://launchpad.net/bugs/214652 [17:34] seb128: how would you feel about http://jameswestby.net/scratch/g-s-d.diff [17:34] is there a preferred way to add the linker options? [17:34] I wasn't sure whether autoconf would be appreciated. [17:35] It's taking bryce's code for detecting Xgl and just disabling the xrandr plugin if it is detected. [17:35] morning [17:35] hi bryce, sleep well? [17:37] james_w: that seems the wrong approch to me, do you know why it breaks exactly? [17:37] nope, afraid not. [17:38] james_w: well enough [17:40]