| bryce | tjaalton: do you want to revert the patch until there is a bug id we can reference? | 00:16 |
|---|---|---|
| bryce | tjaalton: I've asked stevenk for a bug id or commit id but he doesn't have one | 00:16 |
| bryce | I'll make sure in the future that patches the mobile team uploads come sourced with bug id's, etc. | 00:18 |
| bryce | here we go: http://lists.freedesktop.org/archives/xorg-commit/2008-February/014648.html | 00:34 |
| bryce | I've added a note about that in the changelog, and checked all steven's stuff into git | 00:48 |
| * jcristau can't see a patch by mjg59 there | 00:50 | |
| bryce | jcristau: <tjaalton> bryce: mjg59 said that it was from upstream | 00:51 |
| jcristau | ah ok | 00:51 |
| bryce | jcristau: it appears mjg59 modified the patch to apply against xserver 1.4 | 00:51 |
| jcristau | only saw the changelog on hardy-changes, so i was confused | 00:56 |
| ubotu | New bug: #190347 in linux-restricted-modules-2.6.24 (restricted) "Bad entry in menu" [Undecided,New] https://launchpad.net/bugs/190347 | 01:10 |
| bryce | I fixed up the changelog and stuff in git, but didn't push out a new release | 01:24 |
| ubotu | New bug: #188512 in ubuntu "Hardy Alpha 4 600x800 only in VMware (dup-of: 172821)" [Undecided,New] https://launchpad.net/bugs/188512 | 02:10 |
| ubotu | New bug: #190378 in xorg (main) "Kubuntu Hardy Alpha 4: xserver-xorg loads Type1 fonts" [Undecided,New] https://launchpad.net/bugs/190378 | 05:40 |
| ubotu | New bug: #190381 in xorg (main) "edidfail for widescreen lcd (Dell 2405 FPW) causes incorrect resolution and refresh rates" [Undecided,New] https://launchpad.net/bugs/190381 | 06:10 |
| tjaalton | bryce: no the patch is ok, I'd just wish they would end up in git as well :) | 07:03 |
| tjaalton | oh cool, you did that | 07:03 |
| bryce | yeah | 07:03 |
| bryce | I'm kinda bummed about my libxrandr changes | 07:04 |
| tjaalton | there are a couple of patches (by Hong Liu) that are probably worth having if they don't end up in the stable branch.. | 07:04 |
| bryce | ok | 07:05 |
| tjaalton | changes to libxrandr? | 07:05 |
| bryce | carl worth had game night, with me and keith and some other folk, and I told keith that I'd have a patch for him soon for it | 07:06 |
| tjaalton | ok, cool | 07:06 |
| bryce | but he said since libxrandr is a protocol library, it can't take additional logic code, so it'd have to be done as a separate library | 07:06 |
| bryce | which is disappointing since I'm already about 80% done with it this way, and it's only a week until FF. | 07:08 |
| bryce | unfortunately if Xorg can't take the libxrandr patch, then gnome certainly won't take the gnome-control-center patch, so all of this will have to be ubuntu-specific :-/ | 07:08 |
| bryce | bleah | 07:09 |
| bryce | it's particularly a shame because I could have saved a lot of time just copying the xrandr code in directly to gnome-control-center, but I figured this way others (like KDE) would be able to benefit from the library as well | 07:10 |
| bryce | hmm | 07:11 |
| tjaalton | would upstream take a separate library then? | 07:11 |
| bryce | well yeah, that's what he was saying I should do | 07:11 |
| bryce | but one of the objectives was to end up with no code I had to be the maintainer of ;-) | 07:12 |
| tjaalton | hehe, right | 07:13 |
| bryce | ah well, at least ubuntu will have a cool xrandr gui | 07:14 |
| tjaalton | too bad that there has to be two separate apps for the configuration (user-settings and system-wide), but there's no easy solution to that I guess | 07:19 |
| bryce | it sort of makes sense though, since conceptually we have two distinct workflows | 07:20 |
| tjaalton | but two entries on the menu | 07:20 |
| bryce | and also, the way things are going we'll have less and less system-wide configuration to do | 07:20 |
| tjaalton | true, maybe dc-gtk could be dropped from the menu? | 07:21 |
| bryce | that's sort of what I've been thinking | 07:21 |
| bryce | it's mostly broken at this point for most people. It may still make sense for the failsafe situation but in general it's mostly vestigial | 07:22 |
| tjaalton | speaking of which, I think we should streamline the failsafeDexconf even more. What worries me is that when people end up in it and change their configuration, the resulting xorg.conf looks a lot different to the one they had after installation | 07:22 |
| * bryce nods | 07:23 | |
| tjaalton | because I think that with the current xserver the only thing that would have to be changed with the failsafe-mode was the driver. rest is autoconfigured reliably anyway | 07:23 |
| bryce | do you feel like working on cleaning that up? It's been on my todo list to regen it based on the current dexconf, but I may not have time to get it done before FF | 07:23 |
| tjaalton | so, maybe just feed the real dexconf with the failsafe driver? | 07:23 |
| bryce | right | 07:23 |
| tjaalton | that would cut duplication a lot | 07:24 |
| bryce | that might work; I'm trying to remember what else drove me to having a separate copy | 07:24 |
| bryce | oh, I also wanted to make it write to xorg.conf.failsafe instead of xorg.conf | 07:25 |
| bryce | ah, and I put in code to disable dri, etc. etc. but that may not be necessary (probably those don't get enabled with vesa anyway) | 07:26 |
| tjaalton | right | 07:26 |
| bryce | I'd also forced it to 800x600 and 16 bit. Dunno if it's better or worse to let xserver autodetect vesa's max | 07:27 |
| tjaalton | hmm, I'm not sure what the server would do if it can't get the mode from the monitor | 07:29 |
| bryce | I believe it defaults to 1024x768 | 07:29 |
| bryce | at least, I've noticed in bug reports that it seems to be doing that when failing to detect the monitor | 07:29 |
| bryce | like for instance, I think that's what was screwing things up when it was thinking something was connected to s-video but couldn't get edid out of it | 07:30 |
| tjaalton | hmm, vesa shouldn't care about s-video | 07:33 |
| tjaalton | anyway, I'll take a look at it and see what can be safely dropped | 07:48 |
| bryce | cool thanks | 07:48 |
| bryce | I think the week after FF I'll devote to sorting out the displayconfig-gtk bugs, and fixing bulletproof-x stuff | 07:49 |
| tjaalton | hmm, failsafeDexconf still uses discover :) | 08:18 |
| tjaalton | if installed | 08:18 |
| tjaalton | sorry, make that failsafeXServer | 08:19 |
| tjaalton | gotta run -> | 08:23 |
| ubotu | New bug: #190410 in linux-restricted-modules-2.6.24 (restricted) "[hardy] avm-fritz-firmware-2.6.24-7 is referenced, but package repositories include only avm-fritz-firmware-2.6.17-6" [Undecided,New] https://launchpad.net/bugs/190410 | 10:00 |
| ubotu | New bug: #190418 in xorg (main) "Server crash when starting totem-xine to play a DVD" [Undecided,New] https://launchpad.net/bugs/190418 | 11:16 |
| ubotu | New bug: #139582 in xorg (main) "volume knob on dell multimedia keyboard doesn't work out of the box, cannot be configured in gnome keyboard applet" [Wishlist,New] https://launchpad.net/bugs/139582 | 13:41 |
| ubotu | New bug: #190506 in xrandr "[Hardy] GNOME and GDM are starting up with wrong display resolution" [Undecided,New] https://launchpad.net/bugs/190506 | 17:30 |
| ubotu | New bug: #154937 in linux-restricted-modules-2.6.24 (restricted) "nvidia-settings defaults to "no" on 3 button mouse emulation" [Undecided,New] https://launchpad.net/bugs/154937 | 18:44 |
| ubotu | New bug: #190526 in linux-restricted-modules-2.6.24 (restricted) "laptop monitor does not turn on after inactivity when using nvidia-glx-new" [Undecided,New] https://launchpad.net/bugs/190526 | 18:45 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!