[00:27] <RiotingPacifist> is this the right place to come if im on crack?
[00:31] <verbalshadow> sure if you know how to help poor x users like me :P
[00:32] <RiotingPacifist> well i think ive found a bug while on xorg crack (xorg-edgers ppa), but it looks like a packaging mistake rather than a real bug
[00:33] <RiotingPacifist> i can try and help with your problem but beyond the relatively simple i don't know much about how xorg works
[01:03] <verbalshadow> I need help figuring out what is make x crash w/ corruption ( "white scanlines" ) in a hard lock ( key/mouse don't work including magic ones alt-sysRq-REISUB )on lucid
[01:24] <verbalshadow> I need help figuring out what is make x crash w/ corruption ( "white scanlines" ) in a hard lock ( key/mouse don't work including magic ones alt-sysRq-REISUB )on lucid
[13:57] <Q-FUNK> howdy!  in Lucid, restoring from hibernate on -intel takes more than a minute here.  is this a known issue?
[16:06] <Sarvatt> bryyce: just dropping patch 100 is enough to make guest sessions and such work and stops the segfaults, finally got around to rebuilding with only that patch disabled. can we move the xf86CloseLog() down under return(signo) in xf86Init() maybe?
[16:10] <Sarvatt> also xserver-xorg-input-wacom looks like it should be mergeable now unless we were waiting for it to be in squeeze? it doesn't work with serial tablets yet but its working fine with usb on both my graphire 3 4x6 and intuos2 4x5
[16:11] <Sarvatt> err xf86Init.c I meant
[16:27] <seb128> hey there
[16:28] <seb128> bryyce, guest session still crashes xorg with your update
[16:28] <seb128> so it seems to be a different issue
[16:29] <apw> bryyce, hey ... i am seeing i915 going to alll one color, typically black or white but i think i've seen a sort of blue.  and this is recoverable by a suspend/resume
[16:29] <apw> any suggestions as to whether this could be a mesa or kernel issue?
[16:29] <apw> tseliot, ^^
[16:30] <tseliot> apw: oh, do either dmesg or Xorg.0.log contain anything useful?
[16:31] <Sarvatt> apw: after suspend/resume?
[16:31] <Sarvatt> if so use powersave=0 module parameter for i915
[16:31] <tseliot> if that does it ^ then it must be some kms issue
[16:32] <seb128> what does powersave=0 tells us?
[16:32] <Sarvatt> i915.powersave=0 is needed on my machine and quite a few other peoples to fix the flickering and lockups on a solid color like that
[16:32] <apw> nothing in dmesg
[16:32] <seb128> the mini10v has screen flickering after suspend
[16:32] <seb128> the powersave option workaround it
[16:32] <seb128> is that a known issue?
[16:32]  * apw likes the sound of that
[16:33]  * apw goes apply it
[16:33] <Sarvatt> I *really* think it needs to be the default module option for lucid
[16:33] <apw> Sarvatt, if it fixes it for me and pgraner, it _will_ be the default in about 10s
[16:33]  * Sarvatt cheers
[16:33] <tseliot> :-D
[16:34] <pgraner> tseliot: why didn't you tell us this sooner we could have evaluated it for a default setting
[16:34] <Sarvatt> seen 2 problems from it, 915-945 having flickering and hangs after suspend/resume and 965 flickering straight away after boot constantly
[16:35] <Sarvatt> there is a commit queued up for 2.6.32.4 that fixes the latter
[16:35] <tseliot> pgraner: sorry, had I known that I would have told you. I wasn't aware of the problem as I have spent most of the time on proprietary drivers :-/
[16:36] <pgraner> tseliot: no worries, would have been helpful its killing apw and I we loose screen ever few mins
[16:36] <tseliot> ouch
[16:37] <seb128> Sarvatt, is there a reference bug for the flickering bug?
[16:37] <apw> i can say even with a 32.4 kernel the flickering is not fixed on dell 10v, its different looking but still there
[16:37] <Sarvatt> sure I can dig up lots for you, one minute
[16:37] <Sarvatt> http://bugzilla.kernel.org/show_bug.cgi?id=14781
[16:38] <Sarvatt> https://bugs.freedesktop.org/show_bug.cgi?id=25598
[16:38]  * apw is back from suspend with powersave=0 ... will let you know if its the killer setting
[16:38] <Sarvatt> sorry ignore that second one
[16:39] <Sarvatt> still digging, have a bunch bookmarked for these 2 major bugs i'm hitting
[16:39] <Sarvatt> https://bugs.launchpad.net/bugs/492392
[16:39] <apw> sounds like what i would have written if i'd filed a bug instead of whining :)
[16:40] <Sarvatt> guess those are the only two relevant ones to the flickering I was following, the other is alot more major and havent found a fix to it
[16:40] <seb128> Sarvatt, thanks
[16:43] <Sarvatt> apw: yeah the "remove render reclock support" commit only fixes some flickering people are getting after booting from what I can see (lots of newer thinkpads hitting this), powersave=0 is still needed on 945GSE here where i'm only getting the problem after resume
[16:44] <tseliot> jbarnes: any updates on this ^^ ?ù
[16:45] <Sarvatt> he sent out [PATCH] drm/i915: disable LVDS downclock by default so powersave=0 wouldnt be needed for some of the cases
[16:45] <apw> yeah the flickering is only after resume on my machine here, the hard locks to a single colour are possible without suspend but defiantly more prevalent afterwards
[16:45] <seb128> i915.powersave=0 seems to workaround it there too
[16:45] <seb128> the issue is only after resume
[16:46] <Sarvatt> i'm on as aspire one, pretty much the same machine you guys are using
[16:46] <Sarvatt> on an aspire one rather
[16:46]  * apw will let you know if this fixes me here, and i recon if so then its probabally prudent to turn it off by default and let people turn it on if they are brave
[16:48] <apw> so far ... so goof
[16:50] <Sarvatt> lucky we didn't go to intel 2.10 yet, all those mini's would be locking up every hour or so with batchbuffer I/O failures :D been broken in intel git for a month and a half now
[16:50] <Sarvatt> http://bugs.freedesktop.org/show_bug.cgi?id=25475
[20:54] <kamalmostafa> tseliot: Is libGL broken again perchance?  All of the 'octave-*' packages seem to be FTBFS because of
[20:54] <kamalmostafa>   octave-3.2.3: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory
[20:54] <kamalmostafa>   http://launchpadlibrarian.net/38045633/buildlog_ubuntu-lucid-i386.octave-image_1.0.10-2_FAILEDTOBUILD.txt.gz
[20:59] <superm1> kamalmostafa, he's not signed in right now
[21:00] <tjaalton> heh, that looks like fun to fix
[21:03] <superm1> kamalmostafa, is octave-3.2 missing a dependency on libgl1-mesa-glx though?
[21:04] <tjaalton> no
[21:04] <tjaalton> ldconfig is not run yet, so it can't find the lib
[21:08] <superm1> Oh, fun fun
[21:09] <superm1> the postinst for libgl1-mesa-glx didn't run it?
[21:14] <tjaalton> oh, it should have, but either it didn't or it doesn't work right
[21:20] <superm1> it looks like it tries pretty hard to do it.  it's in there twice
[21:29] <kamalmostafa> tjaalton, superm1: I see a couple of libgl1-mesa-glx "issues" in that build log which may relate:
[21:29] <kamalmostafa>    Setting up libgl1-mesa-glx (7.7-0ubuntu6) ...
[21:29] <kamalmostafa>    update-alternatives: using /usr/lib/mesa/ld.so.conf to provide /etc/ld.so.conf.d/GL.conf (gl_conf) in auto mode.
[21:29] <kamalmostafa> and
[21:29] <kamalmostafa>    dpkg: warning: while removing libgl1-mesa-glx, directory '/usr/lib/xorg' not empty so not removed.
[21:29] <tjaalton> those are only informational
[21:31] <kamalmostafa> ok.  do you suspect the problem to be in liblg1-mesa-glx or in octave-3.2?
[21:33] <kamalmostafa> should we expect to see a "Processing triggers for libgl1-mesa-glx ..." line in the build log?  There is none.
[21:40] <tjaalton> it's not a trigger
[21:41] <tjaalton> the postinst should run ldconfig and the build should then see libGL
[21:41] <tjaalton> certainly a problem in mesa, not octave
[21:41] <seb128> bug #506510 is still happening I reopened it
[21:48] <kamalmostafa> tjaalton: okay, thank you for the clarification.  I tried building a different package (which) needs needs libgl1-mesa-glx, and it builds fine.  Why would that be?
[21:48] <kamalmostafa> That package being "fraqtive"
[21:49] <tjaalton> kamalmostafa: no idea
[21:51] <kamalmostafa> tjaalton: okay, thanks again for the help.