[01:19] bryce: pingety ping [01:19] bryce: sorry if I sound like a broken record... do you remember that bug in the intel driver where it said that VGA was connected when it actually isn't? [01:23] hi federico1 [01:23] uhh, vaguely [01:24] I thought you had a patch? [01:24] s/you/ubuntu [01:25] lemme check [01:25] 108_dont_disable_vga_centering_bit.patch ? [01:26] hmm [01:26] commit 3aa8591abfbe8db0f13912910c850fdd748808df [01:26] one sec, let me check [01:26] not sure that's it, that's for bug #17235 [01:26] Launchpad bug 17235 in ubuntu "CXX transition : rudiments" [Medium,Fix released] https://launchpad.net/bugs/17235 [01:26] silly ubottu [01:27] for ubottu, bug #324913 [01:27] Launchpad bug 324913 in xserver-xorg-video-intel "With my Sony Vaio (i945) I can swith to have my internal screen also on the projector with "xrandr --auto" but when unplugging the projector the internal screen image disappears" [High,Fix released] https://launchpad.net/bugs/324913 [01:28] the b.f.o doesn't look like it [01:28] I remember that patch being way bigger [01:29] hmm, don't see any other patches relevant to that, can you give me some more context to jog my memory? [01:29] I have this url in my journal - http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/tree/src/i830_quirks.c [01:29] or maybe the patch was a quirk for a certain model? [01:30] oh that could be [01:30] we had a problem where you boot with no external displays connected, and gnome-panel appears at 1024x768 while your LCD is in fact much bigger [01:30] it happened because the driver lied about VGA being connected, and defaulted to 1024x768 --- then, the panel was stupid and assummed that the first output was the primary display [01:30] did xrandr show a phantom output in that case? [01:31] yep, that's not an uncommon issue [01:31] https://wiki.ubuntu.com/X/Quirks [01:31] bryce: yeah, it showed an output that wasn't in fact there [01:32] that's usually more common with phantom s-video or lvds outputs [01:33] federico1: generally the procedure is to have the user verify that by setting Option "Ignore" on the output, that it makes the issue go away [01:33] if it does, then upstream can (usually) quirk it [01:33] it's probably quirkable for some cards [01:33] although I remember keithp or anholt saying that this was a race condition when initializing the driver [01:34] mm, there is a quirk_ignore_crt() available [01:34] maybe I should ask them :) [01:34] Sony VGC-LT71DB has no VGA output (bug #17395) [01:34] Launchpad bug 17395 in kbd-chooser "kbd-chooser: new changes from Debian require merging" [Medium,Fix released] https://launchpad.net/bugs/17395 [01:34] that's the only hw with that quirk currently [01:35] yep, best to ask one of them, or jesse [01:35] which jesse? [01:36] yeah, it looks a lot like that bug [01:37] barnes [01:37] bryce: thanks [01:37] sure thing [01:37] oh, I don't know him :) [01:37] so [01:37] I'm talking to the fedora guys, trying coordinate some RANDR love [01:37] I've been doing a lot of randr stuff for opensuse [01:37] the gnome stack is pretty much okay except for some panel problems, and probably some gdm ones [01:38] I have three or four main areas of bugs: [01:38] - panel [01:38] - intel driver [01:38] - hooking to signals from gnome-power-manager (re-detect displays on unsuspend) and something about docking stations (re-detect on dock/undock, figure out what people actually do there) [01:38] so if we could split up the work... [01:41] there's also a set of bugs that seem to be particular to randrwrap in gnome-display-properties, i.e. that can't be reproduced using just the xrandr cmdline tool [01:42] I find those frustrating, because they're ambiguous who to upstream them to [01:42] do you know if the fedora guys had special plans for working on these bugs? [01:44] the randrwrap ones? [01:44] well, any of the above, but yeah the randrwrap ones in particular [01:44] I've been hacking on randrwrap - don't really know what soeren is doing these days [01:45] so ping me about those [01:45] ok [01:45] lately esp. this week I've been focusing mostly on -ati bugs [01:45] about the other bugs, I'm discussing things with mclasen in #fedora-desktop [01:45] ooh [01:45] the next couple weeks I've planned to focus on xserver crash bugs, since we now have some good crash capturing tools in place with apport so are getting better auto-collected backtraces [01:46] bryce: my fucking ATI driver will sometimes do a RANDR change, and freeze the displays. I have to switch to a text VT and then back, and then it will be correct [01:46] mm, which version of -ati? [01:47] but a weird kind of freeze - you don't see the mouse pointer move, but if you move it, you see that some widgets highlight/spin/whatever [01:47] hmm, Xorg.0.log says: [01:47] Module radeon blah blah, module version = 4.3.0 - is that what you need? [01:48] hmm, I'd expect 6.9.xxx [01:48] one sec, I'll tell you the real version [01:49] anyway, I've not run across a bug report similar to that so far [01:51] 6.9.0 plus a few patches which are probably backports [01:51] * bryce nods [01:51] bryce: ok [01:51] hmm [01:51] what chip class? lspci | grep VGA [01:51] what info would you need to diagnose this? [01:52] RV280 [Radeon 9200 SE] [01:52] ahh [01:52] lots of bugs on that one [01:52] so [01:52] normally I have VGA connected [01:52] when I plug a second monitor in the DVI and configure it to the *left* of the VGA one, and make it use a smaller resolution, I get that kind of freeze [01:53] there is a tool called radeontool you can get from git.freedesktop.org in airlied's stuff, which provides register dumps [01:53] I'm not yet sure if it's 100% reproducible, but happens often enough for me :) [01:53] with bugs like these, I would collect register dumps once from when you see the problem and once when you are nto seeing the problem, and then file a bug at freedesktop.org with that info, plus Xorg.0.log and lspci info [01:54] sweet [01:54] thanks, I'll do that [01:55] here's some rv280 / xrandr bugs we have: [01:55] https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video- [01:55] https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/205085 [01:55] Ubuntu bug 205085 in xserver-xorg-video-ati "[RV280 9250] Graphical glitches after resolution change with compiz enabled" [High,Incomplete] [01:55] https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/291715 [01:55] Ubuntu bug 291715 in xserver-xorg-video-ati "[RV280 9200] ati driver with xrandr borked in intrepid" [High,Incomplete] [01:55] oh, yeah, compiz seems full of epic fail [01:56] yeah none of those seems an exact match, but seems there is something screwy with the xrandr behavior on rv280 [01:56] yeah [01:57] oh, I remembered - I also get funny output when rotating 90 degrees [01:57] anyway [01:57] hmm [01:57] I'll write a mail to you and interested people [01:57] what's your email again? [01:57] bryce@canonical.com [01:58] thanks [01:58] federico1: btw is your card AGP? If it is, there's some quirking which sometimes helps [01:58] yeah [01:58] Option "AGPMode" "2" [01:58] try 1, 2, 4, 8 [01:58] _sometimes_ there is one that works better than others [01:58] will do [01:59] * federico1 sees todo.txt grow uncontrollably [01:59] if so, quirks can be added - see http://wiki.ubuntu.com/X/Quirks [01:59] heh, sorry :-) [02:00] getting back to the panel bugs, I don't have the todo.txt space to work on them myself, but they seem to be the most commonly reported problem so far. [02:01] federico1: oh also at the last ubuntu developer sprint I collected a "projector sh!t list" of issues people were running into [02:01] cross driver, xserver, gnome panel, and capplet [02:01] url me :) [02:01] * bryce eyeballs the ratty sheet of paper in his briefcase [02:02] I'll have to type it up first. I'll ping ya when I get that in [02:02] hehe, I have a similar list here - http://en.opensuse.org/GNOME/Multiscreen [02:02] nice [02:03] yeah I'll review that and my list, maybe in sharing notes we can squish a few of the bugs [02:03] oh, duh, I had a link to the intel bug I was asking you about right in that page - https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/152416 [02:03] Ubuntu bug 152416 in xserver-xorg-video-intel "GNOME panels are smaller than detected and set resolution" [Low,Fix released] [02:03] aha [02:04] ok yeah that quirk patch went upstream already [02:04] bryce: make sure you have a b.n.c account, or our @#$% bugzilla won't show you bug dependencies. Also, if you find a bug for which you don't have permission, it's probably a SLED bug - tell me and I'll make it visible (we have an annoyingly paranoid bugzilla team...) [02:04] ok cool [02:04] anyway [02:04] my clearinghouse is https://bugzilla.novell.com/show_bug.cgi?id=multiscreen-tracker [08:44] hiya [08:44] I have an interesting case of something weird in X going on :) [08:45] in dmesg: [08:45] [15560.738232] [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 [08:45] in /var/log/Xorg.0.log.old (had to restart X over SSH to un-black it) [08:45] http://paste.ubuntu.com/120487/ [08:45] any idea? [10:09] dholbach: EXA or UXA? and what chipset? [10:29] VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) [10:30] dholbach: what issue do you have? [10:30] yes, EXA (didn't change from the default and it says something about it in the log [10:30] seb128: [10:30] I have an interesting case of something weird in X going on :) [10:30] in dmesg: [10:30] [15560.738232] [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 [10:30] in /var/log/Xorg.0.log.old (had to restart X over SSH to un-black it) [10:30] http://paste.ubuntu.com/120487/ [10:30] any idea? [10:31] hum, no, no idea [10:31] I've the same card on my laptop but no such issue [10:31] it was the first time it happened to me [10:32] * dholbach tries pulling the plug again :) [10:32] ok, worked this time :) [10:33] dholbach: check the backtrace in xorg... if it's like an ioctl then probably the chip or hung... if it's a segv or something the stacktrace alone might be actionable for upstream [10:34] i've seen the "vblank on disabled pipe" message before but on a machined that "worked" [10:34] so I think you might have both the vblank warning and then some other thing as well that causes the crash [10:34] mnemo: there was no backtrace - no segfault [10:35] so xorg is inside the WaitForSomething() function?? [10:36] i mean check the backtrace in gdb (dont look for a stacktrace in xorg.log) [10:37] ok [15:01] hmm, should I be using EXA or UXA on jaunty atm? (965) [15:02] I seem to be using the former and switching desktops isn't the fastest thing ever, it has to be said [15:10] exa works fine for me [15:10] uxa makes xorg crash on resume [15:11] well it feels a lot snappier now I don't have sunbird eating my CPU like there's no tomorrow [15:12] different to intrepid, but not really slow [15:13] Ng: bug 320813 [15:13] Launchpad bug 320813 in linux "[drm] compiz animations cause temporary freezes with vblank" [High,In progress] https://launchpad.net/bugs/320813 [15:13] I'll disable vblank again once I get home [15:14] aha [15:15] with uxa you get dri2 and hence no vblank [15:15] and mine crashes on resume also with exa [15:15] interesting. I've not yet done a suspend/resume cycle [15:15] bah why is ssh-agent running [15:17] vte feels a bunch faster, which rocks [15:19] so yeah, I have x-session-manager spawning ssh-agent and seahorse-agent - isn't seahorse supposed to be at the top? [15:30] Ng: echo $SSH_AUTH_SOCK [15:39] seb128: that's pointing at /tmp/keyring-blah/socket.ssh, but nothing appears to be connected to it [15:39] I did get a gnome style ssh password prompt the first time, but since then ssh has been prompting me in terminals [15:40] (this was all working with auto-unlocked keyrings in intrepid, but I've hit problems before when ssh-agent and seahorse-agent were both running, afair) [18:53] karmic koala [18:54] seb128: "uxa makes xorg crash on resume" has it crashed more than the one time? [18:54] bryce: I tried several times during the sprint each time, I switched back to exa since but I can try again if you think that's fixed now [18:55] ok. no, no reason to think it's fixed yet [18:55] what is this speed issue on intel every speaks about? [18:55] xorg doesn't feel slow on jaunty for me on my laptop which has an intel card [18:56] ie compiz animations are smooth, video plays correctly [18:56] yeah, performance has been ok for me as well, even just with EXA [18:56] but several people showed me their intel systems which were slow for desktop switching in compiz (which may be fixed now) [18:57] you mean some seconds hangs and high cpu usage? [18:57] some seconds or 1 second which seems long enough to watch [18:57] iirc some people were having performance problems even with compiz off. don't remember if anyone showed me that specific case [18:58] not fixed yet, at least for me [18:58] what is the issue? [18:58] I had heard people were seeing on the order of seconds. However all the examples I saw it was <1 sec between switches, but noticeably laggy [18:58] I had a very slow animation and high cpu usage issue [18:58] which I workarounded using [18:58] [18:58] [18:58] [18:58] [18:58] [18:58] [18:58] drirc [18:58] tjaalton gave me that workaround I think [18:59] he said that was a patch dropped which will be added back no? [18:59] yep, that was the issue that I am wondering if it may be fixed now. it required a kernel change, which timg had on his todo list [18:59] I'm uncertain if that patch will fix all the performance issues, or just this specific one [18:59] well, once that fixed speed is as good as intrepid for me [18:59] I'm wondering what are the other concerns [18:59] ok, good to know [19:00] I don't think we should switch to uxa if it's not tested for jaunty [19:00] we are trying to get some credibility back from users who think we are breaking too much between ubuntu version and quality is going down this cycle [19:00] er, who said we were considering uxa? [19:00] so better to stay on what is proved to be stable if we can [19:01] I was reading the mailing lists discussions [19:01] which list? [19:01] and it was not clear from me if we were considering exa performances as a blocker or not [19:01] "let's going back to intel driver 2.2.x" [19:02] :) [19:02] well, getting the exa performance issues solved is a high priority. I think the testing done so far shows uxa is not ready for prime time. I talked with upstream about this choice (jesse) and he agreed sticking to exa probably makes the most sense so far [19:03] "video card (intel) problems in jaunty" on ubuntu-devel-discuss [19:03] oh heh, I unsubbed from that list a while ago. Too much angst ;-) [19:04] I tend to go through the title quickly and read some of the discussions just to know what the issues raised by users [19:05] anyway, I told everyone to help test uxa and report bugs upstream. If the issues everyone reports get all solved, then I guess we can consider uxa, but it's too unstable so far [19:06] I think it's too late in a cycle we want to be stable do consider a such change now [19:06] better to stay on exa and try fix performances issues [19:06] heh, I see there's also a long thread on ctrl-alt-backspace [19:06] that's noise [19:06] I didn't read this one ;-) [19:08] yep, looks like a tedious discussion [19:32] bryce: hey, I'll disable intel-vblank again in mesa, once I get back home :) [19:33] I don't think there's enough time to get it stable for jaunty [19:33] ok [19:33] seb128: btw I could only find one post there on "video card (intel) problems in jaunty" [19:34] and it sounded mis-informed [20:30] bryce: right, there is only one question and one reply, I was just not sure how informed the discussion was about the plans for jaunty [22:07] what package is X a member of? running ubuntu-minimal 8.10, installed xserver-xorg-core, xinit, and xauth but there is still no /usr/bin/X. any help? [22:10] he he, installing 'xorg'. i'll see if that fixes it till somebody responds [22:17] adelie42: xserver-xorg [22:18] sweet, thanks