[11:31] <Laney> Greetings!
[11:31] <Laney> Who is to blame if g-a-p says that I can't have compiz but I actually can?
[11:35] <hyperair> Laney: afaik g-a-p tries to run the compiz script, and if it doesn't work, it says you can't have it =\
[11:36] <hyperair> try running the compiz script? maybe you got a blacklisted pci-id or something
[11:36] <Laney> I see jockey, and then compiz attempts to start and then dies
[11:36] <Laney> but compiz --replace works fine
[11:36] <hyperair> eh?
[11:36] <hyperair> did you manually install compiz or anything?
[11:37] <hyperair> in all the ubuntu packages, compiz is a script that calls compiz.real --replace
[11:37] <hyperair> plus a few other options
[11:37] <Laney> no
[11:37] <hyperair> try checking
[11:37] <hyperair> otherwise debug the script, if it's crashing halfway
[11:40] <Laney> metacity 4eva
[11:49] <hyperair> lol
[12:54] <Cyberkilla> Hello, is anybody there?
[12:56] <Cyberkilla> Hello, does anyone here know anything about the nvidia drivers in  karmic a4?
[12:57] <Cyberkilla> For some reason, 185.18.31, 185.18.36 and 190.x.x give me  artifacts, then system crashes (laptop resets itself).
[12:57] <Cyberkilla> I had to revert to 185.18.14.
[12:57] <Cyberkilla> It is an NVidia GeForce 8400M GT, inside of a Sony Vaio VGN-AR41E  laptop
=== ripps_ is now known as ripps
[13:15] <Cyberkilla>  Hello, is anybody there?
[13:15] <Cyberkilla> 12:56 < Cyberkilla> Hello, does anyone here know anything about the nvidia drivers in   karmic a4?
[13:15] <Cyberkilla> For some reason, 185.18.31, 185.18.36 and 190.x.x give me   artifacts, then system crashes (laptop resets itself).
[13:16] <jcristau> you said that already.
[13:16] <Cyberkilla> I had to revert to 185.18.14.
[13:16] <Cyberkilla> It is an NVidia GeForce 8400M GT, inside of a Sony Vaio VGN-AR41E   laptop
[13:16] <Cyberkilla> I know
[13:16] <Cyberkilla> I didn't think anyone was listening
[13:16] <jcristau> repeating the same thing 15 minutes later won't make people listen
[13:17] <Cyberkilla> Aww
[13:17] <Cyberkilla> I can't find anybody who knows about it. I was referred to this room, on the off-chance.
[13:45] <Q-FUNK> https://bugs.launchpad.net/bugs/417518
[13:45] <ubottu> Launchpad bug 417518 in xserver-xorg-video-geode "Sync xserver-xorg-video-geode 2.11.3-2 (main) from Debian unstable (main)." [Wishlist,Confirmed]
[13:58] <Cyberkilla> hmm
[14:12] <mac_v> hi... could someone instruct me how to set the kernel setting mentioned in comment #7 https://bugs.freedesktop.org/show_bug.cgi?id=23386 ? do i just have to add> radeon.modeset=1 at the end of the line or do i have to also add the i915.modeset=1 mentioned in the X wiki?
[14:12] <ubottu> Freedesktop bug 23386 in Driver/Radeon "Artifacts with cairo dock 2.0 [openGL]" [Normal,New]
[14:13] <mac_v> i tried with just radeon.modeset=1 and noticed that my system became very , i mean horribly sluggish
[14:14] <Q-FUNK> could someone ACK this sync?
[14:17] <tjaalton> mac_v: no, i915 refers to the intel driver. modesetting makes radeon slow, it's being worked on upstream
[14:17] <mac_v> tjaalton: ah , ok... thanx :)
[14:18] <tjaalton> Q-FUNK: just subscribe ubuntu-archive to the bug
[14:18] <Q-FUNK> ok
[14:19] <tjaalton> Cyberkilla: use nvidia-bug-report.sh to file it upstream, not much we can do about it
[14:22] <Cyberkilla> hmm
[14:22] <Cyberkilla> When would I do this? Presumably whilst in the midst of the chaos.
[14:22] <Cyberkilla> I'd have to install the crazy drivers again.
[14:22] <Cyberkilla> I'll see what I can do.
[14:22] <tjaalton> or use the nvidia forums
[14:22] <Cyberkilla> So, nobody has complained of this yet?
[14:23] <tjaalton> not here anyway
[14:23] <Cyberkilla> Someone said it might be a missing dependency in the package.
[14:23] <tjaalton> check if you have nvidia-glx-185 installed
[14:23] <Cyberkilla> Not a missing on on my system, but something odd with the way they made the packages. But, I don't see why it would only affect me in that case.
[14:24] <Cyberkilla> I do. Or rather, I did have everything installed.
[14:24] <tjaalton> regressions in that driver are not unheard of...
[14:24] <Cyberkilla> I've had to go back to 185.18.14
[14:24] <Cyberkilla> The sad thing is, it affects me in every new driver I've tested: 185.18.31, 185.18.36 ("stable") and one of the 190.x.x packages.
[14:42] <mac_v> tjaalton: do you happen to have the bug# for the upstream radeon issue?
[14:44] <tjaalton> no
[14:46] <mac_v> tjaalton: thanx :)
[18:21] <mac_v> after installing from xorg-edgers ppa , do i have to run "dpkg-reconfigure" ?
[18:22] <jcristau> no
[18:28] <mac_v> jcristau: thanx :)
[18:36] <tjaalton> that command is irrelevant in karmic
[22:46] <MTeck> How can I see what display driver I'm using?
[22:47] <mzz> MTeck: I'd normally look at /var/log/Xorg.0.log, but it might depend on why you want to know
[22:48] <MTeck> mzz: just what package is being used
[22:49] <mzz> MTeck: I'd look at /var/log/Xorg.0.log to find the file name of the driver used, then use dlocate or something to find the corresponding package name
[22:49] <mzz> I'm an ubuntu newbie, the dlocate half of this may be suboptimal
[22:49] <jcristau> should be pretty much xserver-xorg-video-${name_of_driver}
[22:51] <mzz> and yes, I'd expect that to be true, but I didn't want to say so in case there's some exception.
[22:51] <MTeck> jcristau: that's why I was trying to figure out what driver(s) I'm using
[22:52] <jcristau> easiest is probably 'grep _drv /var/log/Xorg.0.log'
[22:53] <MTeck> hrm - I'm not even using -fbdev - I thought that was pretty mcuh always needed
[22:53] <MTeck> thanks
[22:54] <MTeck> http://pastebin.ubuntu.com/258950/
[22:55] <jcristau> right, so intel.
[22:57] <MTeck> little grep line was nice and easy :)