LLStarksif i'm having vsync issues, do i file against ddx?00:10
RAOFFiling against the DDX isn't a terrible idea, but more information might help.00:11
LLStarksi've been having x session-wide tearing for about a week00:11
LLStarksrather, almost a week00:12
LLStarksno edgers drivers or anything00:12
RAOFAnd you're running... nouveau?00:13
RAOFOdd.  The DDX will do; they all collect roughly the same logs, anyway.00:14
LLStarksthere was a recent vblank patch, wasn't there?00:14
LLStarksthat was i830...00:15
RAOFI don't recall a recent vblank patch that we've picked up.  Possibly in the kernel, though.00:15
LLStarksprobably doesn't apply here00:17
RAOFYeah.  That's just not printing out error messages.00:18
RAOFOr, rather, printing only the first 5 and discarding the rest.00:18
LLStarksugh. time to bisect.00:19
RAOFWant to throw up an Xorg.0.log just to check?00:20
LLStarksi didn't see anything suspicious00:20
RAOFIs it only with the spanned monitors?00:23
LLStarksraof, eh? single lvds.00:50
RAOFLLStarks: That xorg log shows i915 allocating a 2880x900 framebuffer at one point.00:50
LLStarksi had my laptop vga'd to my tv00:51
LLStarksbut that was yesterday.00:51
LLStarksdid i not power cycle <__<00:51
RAOFAnd vsync woes aren't only when that's happening, I take it :)00:52
LLStarkslemme double check00:52
LLStarksyeah, spanned too.00:52
LLStarksand using tv as single-monitor00:53
LLStarksthe tearing is quite visible on screenshots.00:56
RAOFVisible on *screenshots*?  That's odd.00:57
LLStarksflash, xv, gl, it doesn't matter01:00
LLStarksi'll file a bug01:03
ubot4Launchpad bug 726902 in xserver-xorg-video-intel (Ubuntu) "Tearing on i945. Loss of vsync? (affects: 1) (heat: 6)" [Undecided,New]01:09
LLStarksraof, can i force vsync on intel?01:09
LLStarkslet's see if that compiz trick still works01:10
RAOFvsync is already enabled by default.  Try glxgears for example; it should be limited to (almost) exactly 60FPS01:12
LLStarksyeah, compiz fixes it.01:13
LLStarkscan't use metacity anymore i guess01:13
LLStarksand i'm on classic01:18
LLStarkshmmm. i see now.01:20
LLStarkswhenever metacity/compiz crashes when hooking vga or just in general, i usually reactivate metacity with just plain "metacity"01:21
LLStarksinstead of --replace01:21
LLStarksugh, maybe idon't get it01:22
bryce_cnd, heya sorry the dmb didn't give you more concrete advice, although I do remember when I mentored kirkland it was exactly the same sort of situation; he wanted to know more specifics and just got told "it's obvious when it's obvious" or similar02:07
bryce_cnd, and yeah stgraber's advice regarding doing merges is good; when I went for MOTU I devoted half a day a week to doing merges via MOM, until I felt ready (I wanted to make sure I had touched each of the different patching systems, and had done a variety of different types of packaging work)02:12
RAOFLLStarks: Oh!  You're using Metacity?  With compositing?  Don't do that :)02:16
LLStarksnot with compositing02:16
LLStarksyou can't turn that on unless you explicitly set gconf, right?02:16
RAOFLLStarks: Yeah, pretty much.02:17
RAOFgconftool-2 --get /apps/metacity/general/compositing_manager will tell you.02:18
LLStarksit was only relevant for like a month after beryl fell apart02:18
RAOFNo, it's still useful; I use it :)02:18
RAOFWhen I'm not using a GL compositor.02:18
LLStarksraof, is vga_switcheroo needed at a kernel level?05:43
RAOFLLStarks: What do you mean?  It's implemented at the kernel level.05:43
LLStarksas of which kernel?05:43
RAOF.35?  From memory?05:44
LLStarksi'm thinking of grabbing a few optimus notebooks lying around and bruteforcing them acpi calls05:44
RAOFFrom my understanding of optimus, that's not going to be terribly useful, except to possibly turn off the nvidia card.05:45
LLStarksdell vostros with optimus don't have a physical connection and bruteforcing worked.05:46
RAOFBecause, IIUC, optimus is basically the nvidia card rendering to specific piece of vram, and then copying that vram somewhere special, and then having that scanned out.05:46
LLStarksassuming that acpi_call generates calls that "work", i see little reason why it wouldn't be sufficient.05:48
LLStarksyet devs are convinced that acpi is not the solution05:50
LLStarksthey're looking elsewhere now05:51
RAOFIt looks like that dell has an ACPI mux, which suggests that the nvidia card *is* connected to the outputs, so it's not quite optimus.05:51
RAOFFeel free to try; it's not like we've got specs saying it's impossible :)05:52
LLStarkswell, the whole point of acpi_call is discover acpi mux methods. most optimus notebooks that i've examined have at least one working method.05:53
LLStarkssome don't05:54
LLStarksmost do05:54
RAOFMy understanding of Optimus is that it didn't use ACPI muxs.  It's entirely possibly my understanding is wrong :)05:54
RAOFAlthough you won't be able to do shared rendering stuff with an acpi mux; you'll have to either use the nvidia card for everything or the intel gpu for everything, which isn't optimal.05:55
LLStarksi'd rather lose shared rendering if a simple SB.PCI0.PEG1.GFX0._OFF call can enable the discrete gpu05:59
RAOFWell, I meant that systems which use a mux instead of a more funky approach *can't* support shared rendering.06:00
RAOFOr, at least, if you've got shared rendering support then there's no reason for you to include a mux as well.06:01
RAOFSo they're less likely to actually have one :)06:01
LLStarkswell, a couple of asus notebooks can do cuda and intel simultaneously06:01
LLStarkswhich is confusing to say the least06:02
LLStarks*simultaneously on linux06:02
RAOFNot tremendously confusing.  The nvidia card doesn't have to be hooked up to any outputs to make that work :)06:02
LLStarksbtw, if not acpi, what approaches are left? nvidia coding an intel driver?06:06
RAOFLLStarks: The intel and nvidia drivers cooperating, yes.08:42
RAOFLLStarks: That's how it'll (eventually!) work in Linux-land :)08:42
tjaaltonsigh, this nvidia blob is slow09:22
RAOFAt 2D?09:24
RAOFSilly blob09:24
tjaaltonlike scrolling in chromium or nautilus09:24
tjaaltonnouveau was really fast09:24
tjaaltonhuh, classic desktop opens unity now?10:24
tjaaltonhad to disable the compiz plugin manually10:26
seb128seems a bug, you are the second to mention it10:38
tjaaltonok, good10:40
seb128tjaalton, bug #72686210:41
ubot4Launchpad bug 726862 in unity (Ubuntu) (and 1 other project) "unity launchs itself on the classic desktop (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/72686210:41
tjaaltonseb128: thanks10:41
knittl"Due to hardware capability constraints, disabling display"11:12
knittli think this is related to my "blank screen when using nvidia-current and both screens run at full resolution"11:13
knittl[ 89311.337] (WW) NVIDIA(0): Due to hardware capability constraints, disabling display11:14
knittl[ 89311.346] (WW) NVIDIA(0):     device Seiko/Epson (DFP-0) in MetaMode11:14
knittl[ 89311.346] (WW) NVIDIA(0):     "CRT-0:1920x1080@1920x1080+1920+0,DFP-0:1920x1200@1920x1200+0+0".11:14
knittlin my xorg.0.log11:14
knittli think nvidia-current might be detecting hardware limits not correctly11:15
knittlnvidia-173 has no problems with 2 screens11:15
knittltseliot: friendly ping :)11:15
tseliotknittl: what's up?11:28
knittli was told to talk to you regarding jockey not recognizing the installad driver11:28
tseliotthat's correct11:29
knittland i wanted to ask if you have a clue about my issue above11:29
knittlone monitor blank when using nvidia-current and both on full resolution11:29
knittlit works with -173 though11:29
knittlso i think -current is somewhat borked in that regard11:29
knittldo you have a secret wire to nvidia? :]11:30
tseliotknittl: I do but you'll have to file a bug report about it and attach your nvidia-bug-report.log11:31
knittlbugreport on launchpad?11:32
knittlok, on it11:34
tseliotalso what's up with jockey?11:34
knittlnvidia bug report is generated already11:34
knittltseliot: i install nvidia-current, and jockey tells me 'another version of this driver is in use'11:34
knittlafter reboot that is11:34
tseliotwhat version of ubuntu/jockey is that?11:34
knittli'm on 32 bit11:34
knittlbut also happened in maverick11:35
tseliotwhat's the output of jockey-text -l ?11:35
knittltseliot: http://www.thehappy.de/neo/jockey-nvidia-current.png11:35
knittla screenshot, coz a picture says more than thousand words ;)11:35
knittl$ jockey-text -l11:36
knittlxorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Disabled, In use)11:36
tseliotI don't see how it can be disabled and in use at the same time. Did you install nvidia-current from Jockey?11:37
knittldisabled & in use … funny :D11:37
knittltseliot: yes, i did11:37
tseliotcan I see 1) your xorg.conf 2) the output of sudo update-alternatives --display gl_conf , please?11:38
knittland u-a: http://paste2.org/p/127556411:39
tseliotthey look good to me. Can you file a bug report about it, please? (with "ubuntu-bug jockey-gtk")11:43
knittlyup, currently filing one on nvidia-current11:43
tseliotand include the information that you've just shown me in the bug report11:44
knittltseliot: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/72711211:44
ubot4Launchpad bug 727112 in nvidia-graphics-drivers (Ubuntu) "nvdia-current does not detect hardware capabilities (affects: 1) (heat: 6)" [Undecided,New]11:44
knittlhm, there's a 'correctly' missing …11:45
tseliotif you can't add it, I will11:46
knittlno, i've added it11:46
knittltseliot: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/72711711:53
ubot4Launchpad bug 727117 in jockey (Ubuntu) "jockey-gtk shows nvidia-current as disabled although it's installed and active (affects: 1) (heat: 6)" [Undecided,New]11:53
knittlthanks in advance, i really appreciate your support11:54
tseliotknittl: does nvidia-173 still show up in Jockey? Even after an apt-get update?11:54
tseliotthe log shows that it shouldn't11:55
knittltseliot: currently i only see nvidia-current (not even nouveau)11:55
tseliotok, that makes sense (I don't know about nouveau though)11:56
knittlbefore installing nvidia-current i could see all three: nvidia-173, nvidia-current and "experimental 3d support for nvidia cards"11:56
knittlthat was libgl-dri-mesa-experimental or something like that11:57
tseliotyes, a few things changed in jockey and in the drivers11:57
tseliotcan you also put the output of jockey-text -l in the bug report, please?11:58
knittloh yeah. of course11:58
knittljust a sec11:58
bjsnidertseliot, to avoid the error message that happens on i386 systems when installing nvidia-current, couldn't the script test for build-arch and then only install the 32-bit vdpau links on amd64?14:03
tseliotbjsnider: I'd rather not have the same command twice (one without the 32bit stuff) in the postinst just for that warning14:05
bjsnidertseliot, that was the only error or indication of failure in the jockey log from knittl14:06
bjsniderhis jockey log actually said "error", not "warning"14:07
tseliotright, I don't think that's what's causing the problem though14:08
bjsniderwell, jockey installs the module, sets up the alternatives and then errors out before xorg.conf is created, right at the end14:09
tseliotit says error only because it was printed to stderr, not because it was an error14:09
knittlyeah, jockey aborts before creating xorg.conf14:10
knittland the error message is confusing14:10
tseliotfurthermore the error is printed only when installing the driver. The driver is not shown as enabled after a reboot14:11
tjaaltondoes jockey still create the xorg.conf even though xserver autoloads nvidia?14:11
bjsnideri guess jockey isn't logging the problem14:11
tseliottjaalton: yep14:13
tseliotI don't think we want the Nvidia logo to show up every time, do we?14:13
bjsnideryeah, "ubuntu, by nvidia"14:13
tseliotthe autoloading stuff is supposed to make things work when you install the package manually14:14
bjsniderif he tries that, everything works. there's no error14:15
tjaaltonright, forgot about the logo14:15
knittldriver installs fine with apt-get14:15
bjsniderknittl, right, but if you use jockey, it errors out, says "check the jockey log" which doesn't include anything helpful14:16
knittlbjsnider: yup, exactly14:17
tseliotah, so you got an error too14:17
knittlyeah, but bjsnider (i think) told me, it was a false positive14:18
tseliotknittl: right but was your xorg.conf written when that happened?14:18
bjsniderthe jockey log contains an error that everyone on i386 gets14:18
knittlxorg.conf had to be generated with nvidia-xconfig (or manually)14:19
bjsniderknittl, why are you on i386?14:20
knittli installed ubuntu back in the time when rumor had it, that not all apps would work with 64 bit OS14:21
knittland since there is no easy way to upgrade 32->64 bit, i'm still with i36814:21
tseliotknittl: can I see the original log, please?14:22
knittltseliot: jockey.log?14:22
tseliotthe one with the error14:22
knittli cleared the file before starting jockey and copied right after the error popped up and i had closed jockey14:23
bjsniderthe line 4 from the bottom doesn't contain an explanation14:24
tseliotI guess KernelModuleHandler.enabled() failed somehow14:27
bjsnideris 2.6.38-5-generic-pae the kernel in natty right now?14:28
tseliotknittl: please attach that log to the bug report14:32
knittlhm. i thought i had14:32
knittlwill do14:32
bjsnidermaybe the pae kernel is somehow the problem14:33
tseliotI think I've found the problem. I need confirmation from pitti though14:35
tselioteven though I find it a bit weird14:35
knittljockey.log attached14:36
bjsnidertseliot, is this exclusively a jockey problem?14:41
tseliotI think so14:42
bjsniderin that case, his external monitor issue is exclusively an nvidia problem14:42
knittlbjsnider: yeah, monitor being blank is a driver issue14:46
knittli guess14:46
knittlmost of the time, my internal monitor is blank though ;)14:46
bjsnideractually, it could be a hardware problem, but not something we can fix anyway14:47
knittlhardware problem would not explain, why it works with nvidia-17314:48
knittlminus the comma14:48
tseliotit definitely is s different problem14:49
bjsniderin that case it's a regression in the driver14:49
cndbryce_, is it still possible to get a fix in for evdev?15:17
cnddue to the alpha 3 release freeze15:18
tseliotcnd: maybe we should ask an archive admin? What fix are you referring to?15:35
cndtseliot: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/72520215:35
ubot4Launchpad bug 725202 in xserver-xorg-input-evdev (Ubuntu) "X crashes on startup in evdev_drv (affects: 5) (dups: 1) (heat: 32)" [Medium,In progress]15:35
cndsome MS dongles are wreaking havoc in the kernal15:35
cndand that's havoc is propagating up to evdev :)15:35
tseliotnasty bug, I think we should include it15:37
tseliottjaalton: ^^15:37
tseliotcnd: where's the source?15:37
cndtseliot, I just pushed it to git.debian.org15:37
tseliotor the patch15:37
tseliotcnd: here? http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-input-evdev.git;a=shortlog;h=refs/heads/ubuntu15:39
cndtseliot, yep15:39
cndwait, it's not there...15:39
tseliotwhich is why I asked ;)15:39
cndahh, pushed to the wrong tree15:40
cndsorry bout that15:40
cndone sec15:40
cndis git.debian.org hard to reach for anyone else?15:40
cndit doesn't resolve to an ip address half the time for me15:40
cndand then it's slow to connect15:40
cndtseliot, it's updated now15:41
tseliotI can reach that address without problems here15:42
cndtseliot, it happens intermittently15:43
tseliotlet me review your changes15:44
cndtseliot, thanks15:44
tseliotcnd: any reason why you changed the source instead of adding a patch?15:45
cndtseliot, I didn't change the source15:46
cndI changed one of the patches15:46
cndthe patch is my xi 2.1 work15:47
tseliotcnd: ok, I guess my eyes are a little tired then ;)15:47
cndtseliot, np :)15:47
cndit's really hard to read15:47
cndI know :(15:47
tseliotcnd: I'm asking an admin. If he says it's ok, I'll upload the package16:00
cndtseliot, sounds good to me16:00
cndtseliot, where are you asking?16:00
tseliotcnd: private message16:01
tseliotwe're good to go16:03
tseliotcnd: uploaded and pushed16:05
cndtseliot, great!16:05
LLStarksdoes xvmc still need to be manually configured in xvmconfig or should it work out of the box?16:54
alexmayorgagot a hung laptop with bug 553789 Anything to gather or do I just restart?17:56
ubot4Launchpad bug 553789 in xserver-xorg-video-nouveau (Ubuntu) (and 2 other projects) "X freeze/crash with nouveau driver (affects: 26) (dups: 5) (heat: 132)" [High,Confirmed] https://launchpad.net/bugs/55378917:56
alexmayorgaRAOF: ping17:56
alexmayorgabryce_: ping18:17
mdeslaurDoes anyone here have a Lenovo T510 with nvidia optimus in it? is it possible to force usage of the Intel graphics in it?18:32
Sarvattmdeslaur: yep it is luckily18:34
Sarvattyou can pick between the 2 GPU's or optimus mode in bios on that18:34
mdeslaurSarvatt: oh sweet...and the Intel card supports the 1920x1080 screens?18:35
Sarvattone of the few optimus laptops that actually work18:35
mdeslaurSarvatt: that's good news...I was thinking of replacing my T61, but didn't want an nvidia card this time, but that,s all that is listed on the Lenovo site for the high-res screens18:36
mdeslaurSarvatt: so, thanks!18:36
Sarvattmdeslaur: how long can ya wait? :)18:36
mdeslaurSarvatt: why?18:36
bjsniderSarvatt, how's ath9k doing in natty? is it unusable still?18:58
Sarvattbjsnider: I ditched my ath9k for intel a looong time ago, had all kinds of problems on .37 with it18:59
Sarvatthad to rmmod/modprobe it every 10gb transferred or so (very rough estimate)19:00
Sarvattmainly ditched it because it didn't work on the 5ghz band19:01
knittlnamnö,bauern sind die sicher nicht19:12
knittlmcnö, sind eher unbekannt19:12
knittlwoops. sorry19:13
bjsniderSarvatt, the hardware didn't work on 5gz or the driver?19:24
bjsniderwhat was it?19:24
bjsnideri think that means it was only draft n19:26
Sarvattalmost all non intel mini pcie cards are only 2.4ghz band :(19:41
Sarvattcard says ar5b9519:42
Amaranthso, it seems fullscreen flash locks the GPU (or kernel panics in the i915 module) with a macbook pro with intel HD3000 :/20:37
AmaranthI don't even know how to get debug info about that since the system seems to entirely die20:38
SarvattAmaranth: try the drm-intel-next mainline kernel20:40
Sarvattall kinds of sandybridge problems with fixes still not merged in .38 at the moment20:41
AzelphurHi, my X keeps freezing and using 100% CPU, I'd like to take a crack at debugging it, anyone care to help?20:56
AzelphurIt's frozen and 100%ing now and I'm ssh'd in from my netbook20:56
Sarvattbryce_, RAOF: think I should put a newer mesa 7.10 branch checkout in x-updates/natty? so many juicy sandybridge fixes in the past few days and we're in bad shape in that regard in the archive mesa21:00
bryce_Sarvatt, if you have time, that'd be great21:02
Sarvattwont even take 5 minutes to do that, okie21:03
Azelphurguess I'll just keep killing and restarting X like I usually do until it works \o/21:03
Azelphurlooks like it'e the nvidia driver anyway, I managed to attach gdb to it21:04
SarvattAzelphur: ya read my mind, was just going to ask that.. might want to check http://www.nvnews.net/vbulletin/forumdisplay.php?f=1421:05
Azelphurfun, lots of people with problems :p21:06
Sarvattwhat driver version/desktop environment are you using? watching videos using vdpau and using kwin seem to be common themes with that problem there with the current releases21:09
bryce_ugh kwin21:10
Sarvattif you've got flash 10.2 on 32 bit it's using vdpau so might be triggering that just having ads open on web sites21:12
cndRAOF, the libavg guys have a minimal test case for that mesa glx tls issue21:17
cndbug 25921921:17
ubot4Launchpad bug 259219 in mesa (Ubuntu) "Broken TLS support in libGL.so (affects: 1) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/25921921:17
Sarvattgo figure, new batch of commits to 7.10 branch right as I was going to upload :)21:28
bryce_oh oops was thinking 1.1021:29
bryce_and went, "Didn't they *just* release it?"21:30
bryce_hmm, bug #720468 seems our most popular gpu lockup today21:32
ubot4Launchpad bug 720468 in xserver-xorg-video-intel (Ubuntu) "[i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x7f9c002d) (affects: 16) (dups: 13) (heat: 124)" [High,Triaged] https://launchpad.net/bugs/72046821:32
RAOFcnd: Ah, sweet.  Test case!21:45
jcristauSarvatt: idr says he wants to do 7.10.1 tomorrow21:45
Sarvattno wonder all the intel fixes are getting cherry picked all the sudden :)21:45
RAOFYeah.  I was expecting that soon and was planning to update to 7.10.1 when it was releaesed.21:47
* Sarvatt has been REALLY out of the loop21:48
bryce_RAOF, are you on x86_65?22:01
RAOF(Well, this box is; I've got an i386 965 box too)22:01
bryce_would you mind grabbing the CoreDump.gz files off bugs 724187 and 723319 and doing gdb /usr/bin/Xorg ; core /tmp/CoreFile ; bt full ?22:02
ubot4bryce_: Bug 724187 on http://launchpad.net/bugs/724187 is private22:02
bryce_I suspect one of the bugs is just a dupe of the livecd OOM bug, and the other maybe is something to do with vbox22:03
bryce_but the retracers couldn't grok them22:03
cndbryce_, lsinput works again!22:14
cndand should forever more!22:14
RAOFbryce_: The coredump contained a single resolvable symbol; OsLookupColor at #38 in the stack.  Sorry, no joy.22:15
Sarvattwonderful, it looks like fglrx requires the horizontal resolution to be a multiple of 64 (or else it reports screwed up info to xrandr) to work around a driver bug that was causing corruption in 3D apps when it wasn't22:15
RAOFThat's totally awesome!22:16
SarvattRAOF: did ya load the symbols manually? gotta do that for core dumps22:16
ubot4Launchpad bug 659205 in fglrx-installer (Ubuntu) "[fglrx] fails to detect correct resolution with non-multiple of 64 virtual desktop area (affects: 3) (heat: 29)" [Undecided,New]22:16
bryce_cnd, awesome!22:16
bryce_RAOF, ok thanks for checking22:17
RAOFSarvatt: I did not know that :).  How does one load symbols manually? :)22:17
Sarvattsymbol <path to debug lib> for each lib22:18
SarvattI think..22:19
Sarvattbeen awhile, let me check22:19
RAOFOh, and it'll probably work better if I don't have a locally built, patched Xserver, too.22:20
Sarvattsharedlibrary <path to debug lib>?22:21
Sarvattcould have sworn it was symbol22:21
RAOFI think symbol works.22:22
RAOFBut, again, symbol resolution will likely work better if I actually have the same symbols :)22:23
RAOFHm.  Now with symbols it seems to be dying in dl-fini, which may be fallout of the gallium fallback patch which I already fixed.22:30
bryce_is that bug 724187?  yeah it smells a lot like that other vbox/gallium/x64 bug22:34
ubot4bryce_: Bug 724187 on http://launchpad.net/bugs/724187 is private22:34
RAOFYeah, that's the core file I was looking at.22:36
Sarvattbtw, nvidia-current works with the 1.10 release as long as IgnoreABI is set, we could just add that via jockey the way we have many times in the past22:40
bryce_RAOF, does bug 723319's core give anything beyond ShouldSkipDevice()?22:41
ubot4bryce_: Bug 723319 on http://launchpad.net/bugs/723319 is private22:41
bryce_I'm 90% sure that's just the OOM bug already fixed now22:43
Sarvattbryce_: fixed? ahh I was sick all weekend and didn't check up on it, was it just reverted or actually fixed?22:44
Sarvattthe ubiquity one?22:44
* Sarvatt digs22:44
bryce_Sarvatt, oh sorry you were sick!22:44
bryce_Sarvatt, yep, it happened I caught colin just in time as he was prepping a new ubiquity update, and he accepted the patch to revert22:45
bryce_mario gave another similar patch which purportedly also helped, and he took that as well22:45
bryce_the original cosmetic bug is re-opened, colin agreed it was better to have the OOM solved22:46
RAOF723319 goes up ot ProcXGetDeviceFocus, will an null client.22:48
bryce_RAOF, mind pasting the bt onto the bug?  I'll follow up on it from there.22:52
bryce_looking at the XorgLogOld.txt I can see it definitely is the same bug22:52
bryce_RAOF, thanks that's perfect23:07
bryce_bug 718620 appears to be a hybrid-graphics specific issue 23:37
ubot4Launchpad bug 718620 in xserver-xorg-video-intel (Ubuntu) "With HybridGraphics Xorg assert failure: X: ../../dix/pixmap.c:118: AllocatePixmap: Assertion `pScreen->totalPixmapSize > 0' failed. (affects: 19) (dups: 25) (heat: 200)" [High,Triaged] https://launchpad.net/bugs/71862023:37

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!