[12:04] <Milos_SD> Hello
[12:04] <Milos_SD> is there any news about fglrx in xorg-edgers ppa? :)
[12:21] <ricotz> tseliot, ^ ;)
[12:22] <tseliot> ricotz: I know...
[12:23] <ricotz> tseliot, sorry for bugging you again
[12:24] <tseliot> ricotz: I need to deal with broadcom first, as users with 3.2 are left with broken wireless...
[12:24] <tseliot> but I'll try to do everthing today
[12:27] <ricotz> tseliot, ok :)
[12:29] <Milos_SD> I have one more question :)
[12:30] <Milos_SD> on that laptop with Sandy Bridge graphics and ATI (disabled right now from BIOS), there is some bug that just restarts Xserver (trow me back to log in screen) when using xorg-edgers (and there is no way to get back to ubuntu's default because ppa-purge is not working with multiarch...
[12:31] <Milos_SD> is there some workaround for this bug?
[12:32] <Milos_SD> I noticed that almost every laptop with intel graphics, old or new does this with xorg-edgers... and there is no problems with ATI OSS and nvidia binary using xorg-edgers.
[12:48] <Milos_SD> doesn anyone else has this problem?
[14:47] <bjsnider> ricotz, http://www.nvnews.net/vbulletin/showthread.php?t=168940
[14:48] <ricotz> bjsnider, i know ;)
[15:19] <ricotz> bjsnider, should be available soon in edgers
[15:19] <bjsnider> yeah, i just wanted to update you because i was putting it into x-updates
[15:20] <ricotz> bjsnider, alright
[15:21] <ricotz> bjsnider, please make it so that the edgers version is higher
[16:30] <bjsnider> ricotz, i think edgers should be higher because they're both tagged ~distro~ppa, and i use ~xup, where you probably use ~edgers, although there's no excude for using both ppas at the same time. that's nuts
[16:37] <Sarvatt> ricotz: ~zedgers it is? :P
[16:39] <Sarvatt> Milos_SD: remove the :i386 packages first
[16:39] <Sarvatt> its a pain in the butt because you'll have to reinstall things but thats the only way at the moment
[16:44] <Sarvatt> Milos_SD: dpkg -l | grep sarvatt | grep :i386 ; dpkg -l | grep ricotz | grep :i386
[16:44] <Sarvatt> purge all those, keep track of whats uninstalled (most likely ia32-libs-multiarch and wine), then you can ppa-purge and reinstall those
[16:46] <ricotz> bjsnider, right, the xorg-server dep should manage this two perhaps
[16:47] <ricotz> Sarvatt, hmm, purging "| grep ricotz |", hopefully it doesnt use a ppa of mine!
[16:47] <ricotz> better "dpkg -l | grep 0sarvatt | grep :i386 ; dpkg -l | grep 0ricotz | grep :i386"
[19:17] <bjsnider> cool, we now have a "cancel build" option for ppas
[19:17] <bjsnider> first i've noticed it anyway
[19:46] <bryceh> bjsnider, yep they added it a week or two ago
[20:19] <ricotz> bjsnider, could you update nvidia-settings in x-updates too? for 290.x there are some needed changes
[20:20] <bjsnider> yeah, i was going to, but there's such a huge build queue right now that i wasn't worried about it
[20:20] <bjsnider> good thing there are 20 idle armel builders though
[20:20] <bjsnider> we've on top of the armel issue for sure
[20:21] <ricotz> bjsnider, yeah, but they will takes long time too
[20:25] <dzan> hi, I added the repo ( linux mint 11 ) and did an update, then tried: apt-get install nvidia-graphics-drivers but that came up empty, ideas?
[20:30] <ricotz> dzan, as i wrote "apt-get install nvidia-current" ;)
[20:31] <Sarvatt> don't know what ppa you added or what ubuntu release linux mint maps to (hope you added the right one..) but its nvidia-current
[20:32] <dzan> Sarvatt, thx I got it, ricotz helped me :)
[20:43] <bryceh> i've run into that bug where you upgrade oneiric -> precise with nvidia installed and then X doesn't start due to nvidia failing
[20:47] <ricotz> bryceh, a dkms problem?
[20:47] <bryceh> ricotz, yeah nvidia kernel module missing (apparently didn't build?)
[20:47] <ricotz> Sarvatt, you probably noticed 1.11.99.1 ;)
[20:47] <ricotz> bryceh, i read about it, but havent ran into myself
[20:47] <bryceh> oh wait, I said this was an upgraded machine, actually it was a fresh install
[20:48] <bryceh> I wasn't expecting nvidia to get installed; I guess it did due to having 'third party sources' checkmarked or some such
[20:48] <bryceh> aha, bug #876499
[20:49] <ubot4> Launchpad bug 876499 in ubiquity (Ubuntu) (and 1 other project) "Incorrect Nvidia driver installed by checking 3rd party box (affects: 4) (heat: 18)" [Undecided,Confirmed] https://launchpad.net/bugs/876499
[20:49] <Sarvatt> bryceh: file bug fast against nvidia-graphics-drivers, move to ubiquity?
[20:49] <Sarvatt> oh
[20:49] <bryceh> wait, no not that bug
[20:49] <Sarvatt> was saying fast because logs might get overwritten, not sure :) ubiquity would probably have good logs from the start
[20:49] <Sarvatt> you already know the kernel module didnt get built
[20:50] <Sarvatt> ricotz: you upload it to edgers or something?
[20:50] <bryceh> good idea; filing bug
[20:50] <bryceh> ooh, my apport hook prompts are kinda fun from the console
[20:50] <ricotz> Sarvatt, no, just saying there is finally a first 1.12 pre-release
[20:53] <Sarvatt> bryceh: /var/lib/dkms/whatever have a build recorded for your current kernel?
[20:54] <Sarvatt> modinfo nvidia (or is it nvidia-current) say anything?
[20:55] <ricotz> "modinfo nvidia_current" ;)
[20:56] <Sarvatt> can tell i haven't used the blob in almost a year :)
[20:57] <bryceh> sorry had to type the ridiculously long bug filing url into firefox on another computer
[20:57] <bryceh> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/893760
[20:57] <ubot4> Launchpad bug 893760 in nvidia-graphics-drivers (Ubuntu) "Could not start graphical session by checking 3rd party box; nvidia kernel driver failed to build (affects: 1) (heat: 6)" [Undecided,New]
[20:57] <bryceh> *** Unable to determine the target kernel version. ***
[20:57] <bryceh> hunh
[20:58] <bryceh> modinfo nvidia_current just says can't find it
[20:58] <Sarvatt> yeah it never got built
[20:59] <bryceh> what else would be worth testing?
[20:59] <Sarvatt> it did install nvidia-173 too
[20:59] <Sarvatt> 2011-11-21 19:42:40 configure nvidia-173 173.14.30-0ubuntu8 <none>
[21:00] <bryceh> lsmod is showing no nv*
[21:00] <bryceh> but you're right, -173 is installed
[21:01] <bryceh> so, guess it is a dupe of 876499 after all
[21:01] <Sarvatt> yuck this is a problem in 11.10 too??
[21:02] <bryceh> hmm, possibly although I don't recall seeing it myself or running across bug reports other than this one
[21:03] <bryceh> although I was only looking at nvidia bug reports superficially last release
[21:03] <bryceh> Sarvatt, you thinking it's ubiquity rather than dkms?
[21:04] <Sarvatt> i'm looking at https://launchpadlibrarian.net/83010560/UbiquitySyslog.txt from the other bug now, all kinds of weird
[21:04] <Sarvatt> can you get that same log from your system?
[21:04] <Sarvatt> ubiquity is loading the nvidia driver right after the build for some strange reason, of course that doesnt work
[21:07] <bryceh> where can I find this UbiquitySyslog?  no 'ubiquity' in syslog, and no *ubiquity* in /var/log either
[21:07] <bryceh> ah /var/log/installer/syslog maybe?
[21:07] <Sarvatt> darn, i have absolutely no idea
[21:07] <Sarvatt> oh that sounds right
[21:08] <bryceh> wow it's humongous
[21:09] <Sarvatt> i'd just save all those logs for later and fix it up yourself, purge nvidia-173 see if nvidia-current is offered in jockey (might be a missing pci id from -current?)
[21:11] <bryceh> well, the entire purpose of setting up this system is to find bugs, so given that it's at 'mission accomplished' at the moment, no need to work around the problem ;-)
[21:11] <Sarvatt> that was freaking fast :)
[21:12] <bryceh> I know, I'm pleased in fact
[21:12] <bryceh> this is one of the three bugs we have open right now against precise - http://www.bryceharrington.org/Arsenal/Reports/ubuntu-x-swat/totals-precise-workqueue.svg
[21:12] <Sarvatt> wonder if nvidia-current nvidia-current-updates being the same thing is throwing off ubiquity, no nvidia-173-updates
[21:12] <Sarvatt> then again why isn't this more common..
[21:13] <Sarvatt> wow
[21:13]  * Sarvatt has been living off in kernel land, 3 more oneiric SRUs today :(
[21:15] <Sarvatt> yeah not seeing any other related bugs so far
[21:16] <bryceh> The bug report says '11-10' in the description but the apport spew says 12.04, so maybe the bug was described incorrectly.  At this point evidence only supports this being a precise-only bug.