[00:00] <maxb> albert23: Hmm. mesa 7.7-0ubuntu4 breaks my system here
[00:02] <albert23> maxb: did you reinstall xserver-xorg-core after the upgrade? (bug 506247)
[00:13] <maxb> I'm seeing a somewhat different failure mode: total lockup on a black screen when X starts
[00:19] <DanaG> argh, something annoying about apt-listchanges:
[00:20] <DanaG> In gnome changelogs... it has Fixes: (#xxxxxx) -- that links to debian bug tracker, not Gnome bug tracker as it should.
[03:03] <agroker> just upgraded, and had a problem with gdm vs gdm 2.0 - none of them working
[03:21] <HulkHogan> !ops
[03:41] <NoelJB> Amaranth, you around?
[04:00] <Altusanew> Hey is there anyone using TestDrive to test Lucid? https://launchpad.net/testdrive
[04:05] <DanaG> ooh, new nvidia 96 driver.  Time to see if it's any less broken than the last 5 releases have been for me.
[04:05] <DanaG> Well, no time to test right now; will do it later.
[04:07] <NoelJB> Altusanew, no, I use VMware (and also have a separate partition).
[04:10] <Altusanew> NoelJB: Oh well, thanks anyhow.  I was just trying to get into doing some testing and thought that TestDrive would help but it seams it is not designed to support 64 bit guests on 32 bit hosts.
[04:14] <NoelJB> Altusanew, not testdrive's problem.  I'm not aware of anything that will efficiently host a 64 bit guest on a 32 bit host.  No point, really.
[04:14] <NoelJB> Can't you tell test drive to run a 32bit version of lucid?
[04:15] <NoelJB> Personally, except for my build systems, which are VMs specifically created for building packages for my 64 bit host, I tend to use 32 bit guests.  There are some performance benefits.
[04:16] <Altusanew> NoelJB: Well Virtualbox supports it and I currently do it with VMs that I have set up myself but TestDrive is checking against the kernal version not against the CPU type.
[04:16] <Altusanew> I can but I wanted to test some 64 bit specific this so that maybe I could use 64 bit in 10.04
[04:17] <Altusanew> I am mostly using VMs to test out different distros and Ubuntu variants. Like server, Ubuntu (currently running Kubuntu) and netbook remixes
[04:18] <bjsnider> DanaG, let me save you the trouble. it is as broken. there will be no difference
[04:18] <bjsnider> if anything, the situation could be worse
[04:20] <DanaG> The *segfault* situation I've griped about?
[04:20] <DanaG> *segfault*
[04:23] <bjsnider> nvidia has not released a new driver
[04:24] <bjsnider> i'm sure alberto has
[04:24] <bjsnider> but the contents of the driver package being prebuilt binaries the actual install scripts are all that changed
[04:24] <bjsnider> prebuilt libraries i should say
[04:27] <bjsnider> let's do a reality check here. nvidia does not have the manpower to create a really good driver for old hardware. that is not going to change. all they can afford to do is update the drivers so they'll run on the latest kernels/xorg releases. they cannot addd new features or fix bugs beyond that
[04:27] <bjsnider> and that will not change
[04:30] <bjsnider> nvidia's workstation customers are *not* using riva tnt2 cards
[04:43] <RAOF> nvidia *totally* has the manpower to create a really good driver for old hardware.  However, there's no *business reason* why they'd bother, so they don't.
[04:43] <RAOF> There's nothing particularly wrong with that.
[04:43] <bjsnider> not the linux manpower they don't
[04:44] <vish> !schedule
[04:45] <RAOF> So, perhaps I could be plainer: nvidia could easily spend money to create a really good driver for old hardware, but chooses not to because there's no good business reason for them to.
[04:45] <bjsnider> right
[04:45] <RAOF> They might not *currently* have the manpower to create a really good driver for old hardware *and* a really good driver for new hardware, but that's entirely under their control.
[04:46] <bjsnider> the point i was making is, don't expect that situation to change
[04:46] <RAOF> Oh, absolutely.
[05:00] <DanaG> I don't need "really good" for old hardware.
[05:00] <DanaG> I just need either, A, specs, or B, not SEGFAULT!
[05:00] <DanaG> That nvidia-96 driver has been broken the same exact way for, oh, 2 years.
[05:01] <bjsnider> the nouveau guys do not need the specs anymore
[05:01] <bjsnider> they've already reverse-engineered everything
[05:01] <DanaG> Oh yeah, fixed-function hardware... easier to reverse-engineer.
[05:02]  * DanaG wonders which will end up being more powerful: P4-Celeron 1.6GHz and geforce "four" (HAH!) MX... or Atom 1.6GHz +HT, and Intel something-or-other IGP.
[05:02] <bjsnider> nvidia would have to hire people to go through documentation and release it, and we're currently in a depression
[05:03] <DanaG> The least nvidia could do, would be to offer to lend nouveau devs the hardware to test.
[05:03] <DanaG> That way the nouveau people could at least spare that expense.
[05:04] <bjsnider> i seriously doubt that nvidia has a bunch of old hardware lying around to give to the nouveau guys
[05:04] <bjsnider> however...
[05:04] <bjsnider> DanaG has such hardware apparently
[05:04] <DanaG> Oh yeah, one of my friends has a Dell XPS M1330, where the GPU has died twice.
[05:05] <bjsnider> probably a bumpgate chip
[05:05] <DanaG> Yup.
[05:06] <crimsun> I have a diamond monster 3d and a 3d II
[05:06] <bjsnider> i have a bumpgate chip here but it hasn't blown up yet in 2 years of constant use
[05:06] <DanaG> crimsun: do you know the difference between the alsa-drivers package and alsa-drivers-alsa package?
[05:07] <crimsun> ...the what?
[05:07] <DanaG> linux-alsa-driver-modules-2.6.32-9-generic       linux-alsa-driver-modules-alsa-2.6.32-9-generic
[05:07] <DanaG> linux-alsa-driver-modules-2.6.32-9-server        linux-alsa-driver-modules-alsa-2.6.32-9-server
[05:07] <crimsun> from the ppa?
[05:07] <DanaG> yeah.
[05:07] <crimsun> the description should say
[05:07] <DanaG> there's linux-alsa-driver-modules and linux-alsa-driver-modules-alsa.
[05:08] <crimsun> if it doesn't, that's a boog
[05:08] <DanaG> One's from Ubuntu, one's from upstream... but what are the significant differences?
[05:08] <crimsun> what's the source ppa?
[05:10] <DanaG> both are same version, both "500 http://ppa.launchpad.net lucid/main Packages"
[05:10] <DanaG> grr, apt-cache policy REALLY should show PPA name.
[05:10] <DanaG> ppa.launchpad.net <YOINK> lucid/main Packages
[05:10] <DanaG> that's all it gives.  Bleh.
[05:10] <bjsnider> yoink?
[05:11] <crimsun> that's lucid's, I guess
[05:13] <DanaG> "yoink" as in it doesn't have that bit of information.
[05:13] <DanaG> =þ
[05:14] <bjsnider> i'm tempted to create a ppa called yoink
[05:14] <DanaG> -Description: Ubuntu supplied Linux modules for version 2.6.32 on x86/x86_64 This package contains modules supplied by Ubuntu for Linux kernel 2.6.32 on x86/x86_64.
[05:14] <DanaG> +Description: Ubuntu supplied Linux modules for version 2.6.32 ALSA snapshots. This package contains modules supplied by Ubuntu for Linux 2.6.32 ALSA snapshots from http://www.alsa-project.org/main/index.php/Main_Page
[05:14] <DanaG> that's the diff between descriptions.
[05:14] <DanaG> Looks like perhaps one is a metapackage?
[05:15] <DanaG> yup.  the modules-VER one is a metapackage, the modules-alsa-VER is not.
[05:15] <DanaG> But, one does not depend on the other.
[05:21] <crimsun> yeah, that's a bug
[05:21] <crimsun> I'll ping bjf about it
[05:22] <crimsun> anyhow, they're drawn from http://www.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.bz2 daily
[05:23] <crimsun> so essentially you're getting either git master HEAD of sound-2.6.git or whenever t pushes a new tarball, whichever is newer
[05:24] <crimsun> I don't commit my work in Ubuntu's kernel these days; it's all upstream directly
[05:24] <crimsun> the side effect is that Ubuntu tends to get the fixes a couple releases (kernel-wise) afterward unless I Cc: <stable@kernel.org>
[05:26] <DanaG> That's good for upstream, though.
[05:26] <DanaG> I'd agree with that policy.
[05:26] <crimsun> it's good for everyone, actually
[05:27] <crimsun> the uninvasive stuff ends up in Ubuntu thanks to upstream point releases (via the Cc:)
[05:27]  * DanaG saw that as C   (smiley of person with helmet)
[05:27] <DanaG> C:)
[05:57] <^arky^> This morning I am facing X freezes on intel
[05:57] <yofel> meh, kde 215400 is still  there...
[05:59] <yofel> ^arky^: really? I booted an hour ago and my 945GME works fine so far, had a weired reboot on first try though
[05:59] <yofel> suspenc fsck
[05:59] <yofel> *suspect
[06:00] <yofel> good morning folks btw ^^
[06:00] <^arky^> yofel, the X just freezes think its that fancy splash
[06:00] <^arky^> with the progess bar that might be the issue
[06:00] <yofel> ^arky^: tried to disable splash in grub? Plymouth still needs some work I guess (I personally have splash always disabled)
[06:00] <^arky^> it freeze when it says 'battery fully charged'
[06:01] <^arky^> yes, I am trying to get newest packages and debug the issue
[06:01] <^arky^> I am using old jaunty  machine get my morning work done  meanwhile
[06:14] <iflema> ar0nic: sudo apt-get update && sudo apt-get install bcmwl-kernel-source
[06:14] <iflema> ar0nic: in a terminal
[06:16] <yofel> iflema: wrong channel? ^^
[06:44] <iflema> hmmm
[06:59] <wolter> hi, is synaptic package manager going to be present in lucid?
[07:10] <yofel> wolter: I'm pretty sure it will (it's present now at least)
[07:10] <wolter> oh ok
[07:11] <wolter> is that i am writing the ubuntu manual and we need to know in order to keep/exclude the synaptic package manager subsection
[07:12] <yofel> well I keep more track of the Kubuntu development than the Ubuntu one so I can't guarantee it
[07:13] <yofel> maybe asking in #ubuntu-devel would be better in this case
[09:38] <BUGabundo_work> morning
[09:48] <yofel> moin BUGabundo_work
[09:49] <knittl> https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/506357
[09:49] <knittl> i still get the same error after upgrading
[09:49] <knittl> i fixed it manually yesterday which worked fine
[09:52] <knittl> how is >=python2.5 required? i don't see it in the code
[09:53] <yofel> hm, lemme install 2.4 again and try it
[09:54] <yofel> but who uses that anyway?
[09:55] <knittl> i don't, but i still have it installed
[09:55] <knittl> /usr/bin/python points to python2.6
[10:00] <yofel> hm, running 'python2.4 __init__.py' indeed gives that syntax error
[10:02] <yofel> well, the bug is fixed anyway...
[10:02] <knittl> what is the bug?
[10:02] <knittl> i still get the error, so i don't see it fixed
[10:02] <yofel> s/bug/bug report/
[10:02] <yofel> knittl: remove 2.4
[10:02] <knittl> why?
[10:02] <knittl> :D
[10:02] <knittl> what if i still need it? ^^
[10:02] <knittl> i mean, i don't ... but what about others?
[10:04] <yofel> knittl: then just wait for the fix, the new package won't attempt to build the 2.4 .pyc anymore as it now depends on python (>=2.5)
[10:08] <knittl> yofel: the bug was fixed in the package at-spi 1.29.5
[10:08] <dupondje> I tought of something, why do we do a fsck @ boot ?
[10:08] <knittl> that is the package version i recieved today
[10:08] <dupondje> why not @ shutdown ?
[10:08] <knittl> Setting up python-pyatspi (1.29.5-0ubuntu2) ...
[10:09] <yofel> dupondje: please not, if I press shutdown I want it to shutdown, fsck at boot is ok
[10:09] <dupondje> yofel: you can see it the other way, if I press shutdown, I go to sleep, I don't care if it keeps running for 10 more minutes ?
[10:10] <yofel> dupondje: and if it finds an error it can't correct by itself and waits hours for user input? (and the battery dies in the meantime)
[10:10] <knittl> yofel: so this is supposed to be the fixed version. but it still has the same code. i could apply my fix again, that works. but i wonder why it says "bug fixed" when it's still the same code and still syntax-erroring
[10:11] <yofel> knittl: as I understand the bug it's the python2.4 execption handling that doesn't work as expected here, and just bumping the python depends is the smaller fix here
[10:12] <knittl> yofel: yes, but if the dependency were bumped i wouldn't get an error, would i?
[10:12] <knittl> and it's still in /usr/lib/python2.4 ... so what's wrong there?
[10:13] <yofel> knittl: ... now that you mention it...
[10:13] <yofel> argh...
[10:14] <knittl> :D
[10:14] <eagles0513875> hey guys where can i download the latest version of lucid
[10:14] <eagles0513875> the one i have was pre alpha one and its not working right on a vm for me
[10:14] <yofel> !daily
[10:14] <eagles0513875> ty yofel
[10:14] <knittl> ok, i gotta go. cu yofel, i will fix it again myself *g*
[10:15] <yofel> knittl: have fun :/
[10:17] <BUGabundo_work> 0/ yofel
[10:17] <yofel> ?
[10:22] <riphost> Hi, ive installed the commandline system, how do I make it startx on boot as my user?
[10:25] <yofel> riphost: any reason you want 'just X' ?
[10:25] <yofel> since you usually would use gdm/kdm to start X
[10:25] <BUGabundo_work> riphost: in lucid?
[10:26] <BUGabundo_work> service gdm start
[10:26] <BUGabundo_work> or gdm start
[10:26] <BUGabundo_work> what ever startup now uses
[10:27] <yofel> BUGabundo_work: if he installed the server edition then he has no gdm
[10:27] <yofel> afaik at least
[10:28] <BUGabundo_work> ok
[10:28] <BUGabundo_work> then
[10:28] <yofel> riphost: ping?
[10:29] <BUGabundo_work> sudo aptitude update ; sudo aptitude install ubuntu-desktop
[10:30] <yofel> [11:29] <riphost> nevermind think i got it
[10:30] <yofel> from #ubuntu
[10:30] <yofel> well then...
[10:43] <eagles0513875> hey guys how is it that the ubuntu installer is more responsive and quicker then the kubuntu one
[11:02] <eagles0513875> hey guys would installing a system on an lvm improve performance over all?
[11:16] <CosmiChaos> (metacity:4142): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
[11:17] <CosmiChaos> (metacity:4142): atk-bridge-WARNING **: IOR not set.
[11:17] <CosmiChaos> (metacity:4142): atk-bridge-WARNING **: Could not locate registry
[11:17] <CosmiChaos> Compiz refused to work, Cairo-dock does to
[11:17] <CosmiChaos> any solution?
[11:41] <CosmiChaos> Anyone familiar with that: https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/506919
[11:42] <yofel> CosmiChaos: dup, give me a moment
[11:43] <yofel> we talked about that a while ago
[11:44] <CosmiChaos> well the problem is not really the errorless isntalaltion of that package
[11:45] <CosmiChaos> but that at-spi service is dead since 1.29.5-0ubuntu1 for me
[11:45] <yofel> CosmiChaos: bug 506357
[11:45] <CosmiChaos> (metacity:13261): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.(metacity:13261): atk-bridge-WARNING **: IOR not set.(metacity:13261): atk-bridge-WARNING **: Could not locate registry
[11:45] <CosmiChaos> its not a fix
[11:46] <yofel> well, I'm no expert on this
[11:46] <CosmiChaos> I im with 1.29.5-0ubuntu2, that is newer
[11:46] <CosmiChaos> it is not fixed
[11:46] <CosmiChaos> and at-spi registry still not running
[11:46] <CosmiChaos> and i have no idea to make my desktop work again :(
[12:11] <edgy> Hi, zsync http://cdimage.ubuntu.com/kubuntu/dvd/current/lucid-dvd-amd64.iso.zsync doens't complete the download, any hint?
[12:14] <edgy> failed to retrieve from lucid-dvd-amd64.iso
[12:14] <edgy> Aborting, download available in lucid-dvd-amd64.iso.part
[12:15] <Ian_Corne> there's dvd's now?
[12:16] <edgy> Ian_Corne: sure
[12:16] <Ian_Corne> what do they offer extra?
[12:19] <edgy> Ian_Corne: more packages
[12:48] <BUGabundo_work> Ian_Corne: live and alternate into one, lang packs, etc
[12:48] <BUGabundo_work> edgy: worked for me sunday. maybe the build failed?
[12:48] <BUGabundo_work> edgy: try rsync instead, but do use zsync when it works
[12:51] <gnomefreak> BUGabundo_work: you had said nvidia was incompatible with xorg-7.5 yesterday right?
[12:52] <BUGabundo_work> gnomefreak: i read your line
[12:53] <BUGabundo_work> it was still broken to me last night
[12:53] <BUGabundo_work> not sure how it is today
[12:54] <gnomefreak> BUGabundo_work: no updates today for it
[13:02] <eagles0513875> hey gnomefreak
[13:05] <BUGabundo_work> gnomefreak: ask in #ubuntu-x
[13:05] <gnomefreak> hi eagles0513875 thanks BUGabundo_work i will
[13:06] <eagles0513875> can i ask you guys a question
[13:06] <eagles0513875> why on earth is the kubuntu install so much slower then the gnome installer
[13:06] <BUGabundo_work> eagles0513875: dont ask to ask, just ask
[13:06] <eagles0513875> performance wise when using the installer on gnome it seems so much faster
[13:07] <eagles0513875> i must be goign nuts to think that wya
[13:36] <gnomefreak> BUGabundo_work: nvidia works for me know. i installed plymouth and it upgraded gdm and installed libdri-nouveau but i had nouveau left over from a while ago
[13:37] <gnomefreak> i think that is the name of the package its right or at least close to the name
[13:41] <BUGabundo_work> gnomefreak: CLOOOOWWWW
[13:42] <gnomefreak> plymouth should be replacing usplash in Lucid
[13:45] <BUGabundo_work> i know
[13:45] <BUGabundo_work> but it never installs :(
[13:47] <gnomefreak> bug 506547
[13:50] <yofel> BUGabundo_work: "never installs"?
[13:51] <BUGabundo_work> well, refrasing: is never pulled by updates
[13:51] <BUGabundo_work> sounds better yofel ?
[13:51] <yofel> odd, ubuntu-standard recommends it
[13:55] <gnomefreak> BUGabundo_work: it hasnt replaced it yet so you have to install it
[13:55] <gnomefreak> at least on apt/dpkg end
[13:55] <BUGabundo_work> ha
[13:56] <BUGabundo_work> yofel: are u sure? standard?? not desktop ?
[13:56] <yofel> I thought the same, but apt-cache depends only shows plymouth in -standard
[13:57] <gnomefreak> its standard
[13:57] <BUGabundo_work> weird
[13:57] <BUGabundo_work> so minimal systems will have it
[13:57] <gnomefreak> show ubuntu-standard and look at recommends
[13:57] <BUGabundo_work> very weird
[15:53] <BluesKaj> howdy
[16:18] <BUGabundo_work> hey blackxored
[16:18] <BUGabundo_work> bhaafvpsdfjghs
[16:18] <douglasawh-work> had anyone had problems with luksAddKey in lucid?
[16:18] <blackxored> hey
[16:18] <douglasawh-work> has*
[16:19] <BUGabundo_work> sorry blackxored . was meant to BluesKaj
[16:20] <blackxored> ok hi anyways
[16:53] <DanaG> hmm, nvidia-96 won't even install.
[16:53] <DanaG> http://pastebin.com/f5f2af40d
[16:54] <BUGabundo_work> ehe
[16:54] <BUGabundo_work> no comments
[16:55] <DanaG> And before I set it to "-x", it just did this:
[16:55] <DanaG> setting up nvidia-96...
[16:55] <DanaG> dpkg: error processing nvidia-96; postinst failed.
[16:55] <DanaG> Absolutely no error message in between.
[17:01] <vish> hmm,,...
[17:01] <vish> what do they call it when both the router and the modem are set to pppoe configuration...?
[17:02] <vish> double routing or something?
[17:02] <vish> , i forgot what the term was :/
[17:05] <yofel_> that's odd, I tried to install 96 just for fun 2 days ago and it worked
[17:06] <yofel_> there was an update since then but nvidia-96 is still installed fine
[17:06] <yofel> DanaG: that's odd, I tried to install nvidia-96 just for fun 2 days ago and it worked
[17:08] <DanaG> Weird.
[17:08] <DanaG> Anyway,  that system hasn't been booted in a while, so it has a bunch of other packages to update; I'm doing that bit right now.
[17:09] <alex_mayorga> I'm getting "Network error" from ICQ in Empathy, anyone else?
[17:10] <sammm> When is Empathy going to get MSN webcam support then?
[17:11] <sammm> It's really annoying how lots of fit girls want to go on webcam for me but Empathy won't let me. :(
[17:11] <sammm> Fit young schoolgirls. :)
[17:11] <alex_mayorga> Odd, supposedly Empathy closed unexpectedly
[17:12] <alex_mayorga> but I'm still here :S
[17:12] <alex_mayorga> I guess clicking "Report Problem..." would shut me down
[17:12] <alex_mayorga> let's see...
[17:12]  * Pici waves preemtively
[17:13] <alex_mayorga> "The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes." What's this?
[17:13] <yofel> o.O
[17:15] <alex_mayorga> The contact list is unresponsive, though
[17:15]  * BUGabundo_work waves back at Pici , while laughing
[17:16] <alex_mayorga> anything that I should capture?
[17:23] <bjsnider> Pici, i think he was just kidding around
[17:24] <bjsnider> that guy you banned
[17:27] <IdleOne> kidding around does not make it right
[17:28] <IdleOne> besides he was banned from #ubuntu for ban evading
[17:28] <bjsnider> banned for ban evading?
[17:28] <IdleOne> yes
[17:28] <IdleOne> he got banned
[17:29] <bjsnider> what if he evades that ban? will he be banned for ban evading that ban for ban evading?
[17:29] <IdleOne> lol probably
[17:29] <IdleOne> point is that he is known by the ops
[17:30] <bjsnider> i c
[17:47] <BUGabundo_work> i'm always impressed how Pici reads every single line in quasi realtime of this #
[17:48] <BUGabundo_work> him and ikonia :|
[17:48] <Pici> We see all
[17:48] <BUGabundo_work> ahah
[18:11] <sivang> hey all
[18:11] <sivang> Is Lucid usable on the desktop already?
[18:11] <sivang> are there any show stoppers I should be wary if I Want to use it as a development platform?
[18:11] <sivang> (9.10 slowness is KILLING Me)
[18:17] <bjsnider> karmic isn't slow
[18:18] <bjsnider> so the premise of your question is incorrect
[18:18] <fejes> hi.
[18:18] <fejes> Is this an appropriate forum for asking for insight into Lucid problems?
[18:20] <fejes> aka, why 2.6.32 kernels cause a corrupt video within seconds of getting past grub.
[18:21] <yofel> fejes: that sounds plymouth related...
[18:21] <robin0800> fejes: upstart perhaps
[18:21] <yofel> if you have it installed at least
[18:21] <fejes> I'm not sure -
[18:21] <yofel> fejes: what graphics card do you have?
[18:21] <fejes> I can't really see anything, it shows "starting up", then instantly turns into vertical stripes.
[18:22] <fejes> This is a dell vostro 1000, with an ATI 200M
[18:22] <fejes> booting to 2.6.31 from karmic works.
[18:22] <yofel> hm... ati, KMS maybe
[18:22] <fejes> 01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200M]
[18:23] <fejes> yeah, I thought it might be KMS, so I've tried several radeon.modeset={0,1} variations,
[18:23] <fejes> but nothing I do seems to change it.  Although, the pattern of stripes changes, which is pretty.
[18:23] <fejes> (=
[18:23] <yofel> fejes: you're not using fglrx or someting like that?
[18:23] <yofel> *something
[18:23] <fejes> nope...
[18:24] <yofel> ok, as I'm really no ati expert: I'm out of ideas
[18:24] <fejes> Section "Device"
[18:24] <fejes>         Identifier      "Configured Video Device"
[18:24] <fejes>         Driver          "radeon"
[18:24] <fejes>         BusID           "PCI:1:5:0"
[18:24] <fejes>         Option          "DRI"   "true"
[18:24] <fejes> Yeah, I'm rather stumped.
[18:24] <yofel> I do remember the other ati folks talking about ati being pretty broken
[18:24] <yofel> hm
[18:24] <fejes> I also have other issues, such as dri/glx completely borking on yesterday's updates.
[18:24] <yofel> Sarvatt: do you know more mabe?
[18:25] <fejes> but I'd just like to know why the 2.6.32 kernels are crapping out so badly for me.
[18:25] <fejes> the rest, I can probably deal with, or wait for more upgrades.
[18:25] <yofel> DanaG: do you know what could cause vertical stripes on boot with 2.6.32 with an ati radeon xpress?
[18:26] <DanaG> hmm, not sure... #radeon would be better able to help.
[18:26] <fejes> ok, I can try that.
[18:26] <fejes> thanks for your help.
[18:30] <fejes> #radeon seems to be quiet.
[18:30] <fejes> any other resource suggestions that might be useful?
[18:30] <yofel> fejes: it's pretty normal to get an answer after a few hours here
[18:30] <fejes> *nods*
[18:31] <fejes> I know... I'll keep monitoring.
[19:26] <pasjr> is Alpha still being released 01-14-10
[19:26] <pasjr> alphla 2
[19:27] <pasjr> just wondering, I have not had any updates for two days
[19:27] <yofel> pasjr: why shouldn't it? the release dates are  fixed
[19:28] <yofel> pasjr: soft freeze, only bugfixes
[19:28] <pasjr> o that explains it
[19:47] <sivang> okay, so I have to suffer until april then.
[19:47] <sivang> that is the slowlest ubuntu ever.
[19:47] <sivang> cheers all
[19:48] <bjsnider> karmic is the slowest ubuntu ever?
[19:50] <DanaG> hmm, fun way to tie up notify-osd for 500 seconds:
[19:50] <DanaG> while (true); do notify-send this sucks; done;
[19:50] <DanaG> but run in console to be able to ctrl-c it.
[19:51] <genii> 6.06 was (the slowest release)
[20:55] <kombucha> trying to install openssh-server in Lucid, but it's not working.... also tried just 'openssh'
[20:55] <kombucha> how do I install this in Lucid?  it's working fine in Karma
[20:57] <Ian_Corne> apt-get install ssh
[21:10] <kombucha> thanks Ian
[21:40] <knittl> any solutions to the locales-problem?
[21:50] <ripps> knittl: sudo locale-gen --purge; sudo reboot
[21:51] <knittl> ripps: did that, didn't help
[21:51] <ripps> knittl: what's the exact problem? you getting perl erros?
[21:51] <knittl> i can't type non-ascii chars in gnome-terminal
[21:52] <ripps> *shrugs*
[21:52] <knittl> and if i change GTK_IM_MODULE to xim i can't enter any non-ascii chars in any app
[21:52] <knittl> ??? <- supposed to be umlauts
[21:54] <CosmiChaos> how to configure gdm?
[21:55] <CosmiChaos> login screen, auto login, gdm-themes?
[21:55] <CosmiChaos> where is the configuration tab
[22:09] <ripps> Geez, CosmicChaos didn't stick around long enough for anybody to answer
[22:49] <DanaG> http://pastebin.com/f6c666560
[22:49] <DanaG> that's nvidia.
[22:51] <knittl> DanaG: how did you install nvidia drivers?
[22:53] <DanaG> nvidia 96 from the repos.
[22:53] <DanaG> http://pastebin.com/f2560a8ea
[22:54] <knittl> can you do a grep nvidia /etc/modprobe.d/*
[22:55] <knittl> that's what helped me today :D
[22:55] <DanaG> http://pastebin.com/fcc56129
[22:55] <knittl> looks better than mine
[22:56] <knittl> what's the actual problem?
[22:56] <DanaG> Xorg seems not to be starting... judging from the log.
[22:56] <DanaG> I'm setting it up remotely, at the moment.
[22:56] <knittl> 96 is the right driver? old video card?
[22:57] <DanaG> yup.
[22:57] <knittl> try recreating initramdisk
[22:57] <knittl> sudo update-initramfs -u
[22:58] <knittl> does it help to exit to a console and then start gdm with sudo service gdm start?
[22:58] <DanaG> nope, I've restarted gdm... same behavior.
[22:58] <DanaG> .: 6: Can't open /scripts/casper-functions
[22:59] <knittl> then i don't have any ideas, sorry :-/
[23:27] <arand> Is the communication status indicator supposed to be to the right of the shutdown?
[23:31] <sebsebseb> Hi
[23:33] <DanaG> weird broken nvidia 96.
[23:47] <arand> Is the communication status indicator supposed to be to the right of the shutdown? Anyone seeing the same/diff?