bryceI've uploaded new xdiagnose.  All tests pass and scripts work and bug filing appears to work, to the limit I can test it locally, so I don't expect any problems, but ping me if you spot anything weird this weekend.02:54
mlankhorstbryce: wont do anything this weekend, had to spend today dealing with lts stack, looks like I might need to re-enable the shared libgallium patch for mesa due to disk space on iso03:24
brycemlankhorst, good plan taking the weekend off03:33
mlankhorstfor now plan is to unrename libdrm (uploaded/accepted, rebuilds are pending), fix up plymouth to no longer require intel on arm (sponsored), and maybe re-enable the gallium patch, pending testing :)03:36
jibel_bryce, xdiagnose 3.4 is broken on raring bug 110168809:10
ubottubug 1101688 in xdiagnose (Ubuntu) "xdiagnose 3.4 installation failed with syntax errors" [Critical,Triaged] https://launchpad.net/bugs/110168809:10
brycejibel_, thanks09:21
=== jono is now known as Guest30234
* mlankhorst pokes Sarvatt 22:06
AzelphurHi folks, trying to get Steam running on Ubuntu 12.10, problem is when I install fglrx-updates, or install the latest version of fglrx from the website, Unity doesn't start at all. Ideas?22:55
mlankhorstdoes glxinfo work?23:13
brycemlankhorst, thought you weren't working this weekend?  ;-)23:20
mlankhorstblegh I keep irc open for other channels23:21
brycemlankhorst, I'm just teasing ;-)23:21
bryceAzelphur, see the topic23:22
Azelphurbryce: https://bugs.launchpad.net/fglrx/+bug/1068661 seems there is already an active topic on the subject, https://bugs.launchpad.net/fglrx/+bug/106866123:22
ubottuUbuntu bug 1068404 in xserver-xorg-video-intel (openSUSE) "duplicate for #1068661 Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade" [Critical,In progress]23:22
AzelphurUnless you want me to go break it again and file a new bug?23:22
AzelphurAlthough, I'm not on a hybrid, this is just a standard desktop with a 7770 in it23:23
bryceAzelphur, filing a bug also copies up your log files, which people generally need if you're going to ask them for help23:24
Azelphurrighto, I'll go do that, just get it into the broken state and run ubuntu-bug xorg?23:24
bryceAzelphur, besides, it's possible you *don't* have the same bug.  And if you do, having a new set of logs can help confirm that.  Setting two bugs as dupes is cheap and easy for us.23:25
Azelphuryea I agree, will get that done for you now :)23:25
bryceAzelphur, that's right.23:25
bryceupdate to latest before you do that; I stuck in some bugfixes today for the apport hook.23:26
Azelphurok, just standard Ubuntu 12.10 update?23:26
bryceoh, thought you were on raring; nevermind23:27
Azelphurnope, pretty normal 12.10 install :)23:27
Azelphurbryce: there we go, #1101948 :)23:48
bryce[    16.313] (EE) fglrx(0): Fail to init MGPU configuration:0x0!23:52
bryce[    16.456] (EE) fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or incompatible. 23:52
Azelphurinteresting, that means the problem is in fglrx?23:53
bryceyeah kernel module probably failed to build23:53
brycecheck your dkms and make.log files for errors23:53
Azelphurwhere are they at?23:54
bryceand probably you fscked your system by also installing the drivers from AMD's site.23:56
Azelphurwell, I only did that after experiencing the issue in the first place, and I built the .deb packages and installed them as instructed on the Ubuntu help pages :)23:56
Azelphurso baring in mind I only ever installed / removed the built packages, should be fine?23:57
brycedunno, sometimes packages leave cruft config files and stuff around23:58
* Azelphur shrugs23:58
Azelphurbut yea, how do I check dkms and where is make.log? :)23:59

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