[00:00] <BUGabundo> ctp: please read the release notes, and install/upgrade a daily image of Karmic
[00:00] <Lounge> ctp: yes they can use all the help they can muster ^^
[00:01] <ctp> hexa--: hey, i've forgotten one fact. which city are you from. i have to travel around next weeks, so not sure, if i am in your region. but if ...
[00:01] <BUGabundo> ctp: https://wiki.ubuntu.com/KarmicKoala/TechnicalOverview and
[00:01] <BUGabundo> |daily | ctp
[00:01] <BUGabundo> !daily | ctp
[00:03] <ctp> i have to chose between squeeze and jaunty _today_ (no joke, it's sunday, but they expect a decision) for 30 workstations. not sure what to take. i must say. i love debian but ...
[00:04] <hexa--> ctp: mittelhessen
[00:05] <ctp> hexa--: ah, ok. btw you're at har2009?
[00:06] <hexa--> ctp: funny, i'm a student, no job at all... :)
[00:06] <hexa--> ctp: i'd like to, so much :]
[00:06] <BUGabundo> hexa--: ctp please that that to PVT. thank you
[00:07] <hexa--> ctp: jabber?
[00:07] <ctp> the reason for squeeze/karmic is: kernel 2.6.30 (the company i'm working for currently hacks kernel drivers, so they need bleeding edge stuff) and most recent libs. so no chance for lenny/jaunty installation with lot of upgrade hickhack
[00:08] <BUGabundo> ctp: you can get mailine kernel for jaunty too
[00:08] <BUGabundo> ctp: https://wiki.ubuntu.com/KernelMainlineBuilds
[00:09] <ctp> BUGabundo: right, but same with libs, gcc 4.4 etc
[00:09] <ctp> hexa--: ctp@jabber.ccc.de
[00:09] <BUGabundo> ahh
[00:09] <BUGabundo> then yes, you may need karmic
[00:10] <BUGabundo> but I would not place that onto 30 PRODUCTION workstations
[00:11] <ctp> BUGabundo: i think i'll package the stuff into a vmware instance for them. currently they're working with lenny pinning hundreds of packages ;-)
[00:12] <BUGabundo> ctp: you could do the same with jaunty plus packages from karmic
[00:12] <DanaG> Or have remote secondary machines?
[00:12] <BUGabundo> but it would be integrantion HELL
[00:13] <ctp> hexa--: see query. no  jabber client here. i need some web based client ;-)
[00:14] <BUGabundo> ctp hexa-- take it to IRC PVT ?
[00:14] <ctp> BUGabundo, DanaG et al.. thx for infos ;-)
[00:14] <BUGabundo> ctp: no prob
[00:14] <ctp> BUGabundo: we did ;-)
[00:14] <BUGabundo> I would love to see 30 more testers for karmic
[00:14] <BUGabundo> but I also know you need to get work done
[00:14] <BUGabundo> and can't depend on the breakage that is expected on a devel cycle
[00:18] <DanaG> s/depend/gamble/
[00:19] <BUGabundo> what gamble? it WILL happen! LOL
[00:20] <BUGabundo> its just a question of HOW serious it will be
[00:26] <BUGabundo> Sarvatt: ping .still around ?
[01:42] <yoasif> hey all
[01:43] <yoasif> anyone seeing gconfd-2 taking up 10-15% of cpu constantly?
[03:32] <felipe__> hi everyone, I am testing ubuntu karmic koala and I've some problems with the grub, and defenitely I can't fix it because I can't find the menu.list? someone can help me?
[03:34] <felipe__> the version of the grub is 1.9.4  so it is almost 2
[03:39] <BluesKaj> felipe__, alt+f2 ,  kdesudo kate /boot/grub/menu.lst
[03:40] <DanaG> yay, somebody who actually knows not to use bare sudo for X apps!
[03:40] <DanaG> That's one of my pet peeves: people saying "sudo <X application>"
[03:41] <felipe__> blueskaj: yeah but that is in the old grub , in grub 2 is different right?
[03:41] <yofel> felipe__: look into /etc/default/grub
[03:42] <BluesKaj> I'm using grub, dunno whether it's 2 or not
[03:42] <yofel> version 0.X is grub 1.X is grub2
[03:43] <felipe__> blueskaj: are you testing karmic koala? because, I can't find the file in this distribution ...
[03:43] <BluesKaj> yes i am , felipe__
[03:43] <felipe__> I tried with os-prover and then update-grub
[03:43] <yofel> DanaG: yeah, but I also met somebody who said: open a terminal and then start a bash shell with gksu xterm ...
[03:43] <felipe__> but , the system says: mapdevfs: error while loading shared libraries: libdebian-installer.so.4: cannot open shared object file: No such file or directory
[03:44] <yofel> *root shell
[03:44] <yofel> felipe__: yes, grub2 has no menu.lst anymore
[03:44] <DanaG> bah, just sudo -i!
[03:44] <DanaG> =þ
[03:45] <yofel> ;)
[03:45] <BluesKaj> felipe__, I see nothing in the menu.lst about grub2
[03:46] <DanaG> look in /etc/default/grub
[03:46] <DanaG> and /etc/grub.d
[03:46] <yofel> BluesKaj: menu.lst is grub, grub2 has no menu.lst
[03:46] <BluesKaj> then why use it?
[03:46] <felipe__> yofel: yeah I know, but how I can configure my system for having dual boot
[03:47] <yofel> no idea, I don't use grub2 on my dual boot machines since it's know to be buggy
[03:48] <felipe__> ahahah
[03:48] <felipe__> ok, but the thing is try to fix the bug :-)
[03:49] <BluesKaj> felipe__, I dual boot , would like to have a look ? http://www.pastebin.ca/1468346
[03:49] <felipe__> yofel: but do you have dual booting? where is the file of configuration?
[03:51] <felipe__> blueskaj : yeah this file looks like my old one with grub 1.X in jaunty but in koala I can't fine the file of configuration
[03:51] <yofel> felipe__: the only machine that I have dual boot on is still running jaunty with grub since I can't afford to break it and my karmic machines are ubuntu only
[03:53] <yofel> felipe__: if you want the grub2 'menu.lst' that woud be /boot/grub/grub.cfg but the 'DO NOT EDIT THIS FILE' should be taken seriously i think
[05:07] <coz_> hey guys how to flash in kde4?
[05:10] <woodbj> works fine for me in firefox and konqueror
[05:21] <coz_> mmm
[05:21] <coz_> I guess I could install firefox
[05:45] <ripps> It seems that python-gnome2-extras is broken. I think it's because of it's dependency python-gdl
[06:06] <Protector1981> -.- ecrypt dont works with karmic? oO
[08:51] <lynggaard> hi, planning on building a new comp, and with all the gfx sub system/driver changes I would like an advice. Planning on ubuntu 9.10 64bit, but should I go with ati based card (eg. 4770)now they have started to like OSS drivers, or should I stay with nvidia (like GTS 250) and their binary blob (is that available in 64bit?)
[08:51] <lynggaard> Can't seem to find any solid advice for the new stuff happening in 9.04/9.10
[08:52] <lynggaard> any advice or pointers to guides ?
[08:53] <RAOF> The nvidia binary blob works on x86-64; the OSS drivers for r700 cards (like the 4770) aren't quite done yet, although I think there'll be some support in Karmic (9.10)
[08:55] <lynggaard> RAOF, thanks do you know if the ATI support will include 3D effects? or are we talking something alike the Intel + 9.04 (unstable and very slow)?
[08:55] <lynggaard> RAOF, do you know of a link where i can read up on the state of the mentioned ATI drivers ?
[08:56] <RAOF> lynggaard: There's already 2D support for ATI; I was talking about the 3D support.  The annoying 9.04 Intel performance regressions should all be fixed in Karmic.
[08:57] <RAOF> The ATI drivers will be doing something like what happened in the Intel drivers soon, though (moving to a GPU memory manager & kernel modesetting, in their case TTM).  I'm not sure how that'll effect the performance & stability for Karmic, though.
[08:57] <lynggaard> RAOF, good to know about intel, my coworker will be very happy.
[08:57] <RAOF> They'll get faster suspend/resume & boot with kernel modesetting, too.
[08:58] <lynggaard> RAOF, do you know of a good place to follow the progress of the ATI driver. A quick google wasn't much help
[08:58] <Sarvatt> i would pick nvidia any day of the week, would be surprised if open source ati would be to your liking even in a year from now. the r6xx and newer support is very incomplete right now, they are mainly focusing on improving the situation for r5xx and older cards that arent supported by fglrx anymore
[09:00] <Sarvatt> the blob sucks, but you'd be stuck with the blob either way and at least the nvidia blob supports things like vdpau
[09:00] <lynggaard> RAOF, what would your recommendation ? which holds the better future/ will ati be able to catch-up...
[09:01] <lynggaard> Sarvatt, what is vdpau ?
[09:01] <lynggaard> Sarvatt, and what is "very incomplete"?
[09:01] <RAOF> Sarvatt: Yeah.  Unfortunately, nothing else supports vdpau :)
[09:01] <Sarvatt> http://en.wikipedia.org/wiki/VDPAU
[09:02] <RAOF> lynggaard: vdpau is nVidia's GPU video decoding extension.  Like XvMC, but supporting codecs that people actually care about.
[09:02] <lynggaard> thanks for the links
[09:04] <Sarvatt> very incomplete = i'd be surprised if it was even working and/or had half the features of the binary blob drivers in a year from now
[09:05] <RAOF> I'm not sure; the r700 stuff is using the new gallium framework.  How fast it gets working is going to depend heavily on how mature that gets.
[09:05] <lynggaard> how about sli support ? reason I am asking is because from a windows (gaming) perspective I really like the idea of starting with a single cheap ati 4770 and adding another later in case I run into performance issues.  but if it means basically no linux performance (just want fast 2D and some of the helpfull 3d desktop effects) then I might need to rethink that idea
[09:05] <lynggaard> gallium framework ?
[09:06] <RAOF> lynggaard: Dunno about SLI.  That's probably a low priority, though.
[09:06] <RAOF> lynggaard: http://www.tungstengraphics.com/wiki/index.php/Gallium3D
[09:07] <RAOF> The gallium framework is the new "let's make developing 3d drivers less of a pain" code that's recently been merged into MESA mainline.  It's essentially a way of getting (nearly) API-independent 3d drivers.
[09:07] <RAOF> You can also (and the nouveau drivers have) implement other interesting things, like GPU video decoding through it.
[09:08] <Sarvatt> http://www.x.org/wiki/radeon
[09:11] <RAOF> For a new ATI card you'll have the fglrx binary driver anyway; that should work, even if it's not as fun as the OSS drivers ;)
[09:11] <zniavre> hello / bonjour
[09:12] <zniavre> does nvidia 173.14.xx works yet ?
[09:13] <RAOF> Ah.  The joy of 4 separate nvidia blobs :(
[09:14] <zniavre> yep my graphic card is now officialy too old :o(
[09:15] <lynggaard> RAOF, agree it is not as fun... but I must admit I go by the following priorites "working (gets the job done) then OSS friendly company" sad but true.
[09:15] <RAOF> Certainly.
[09:15] <RAOF> Partially what I meant was, like the nvidia blob, fglrx does some things worse than the OSS drivers.
[09:17] <lynggaard> RAOF + Sarvatt, Do you want to pass judgement on my first one 4770 then later maybe another idea, or should i go for a GTS 250 or above nvidia right away ? what would you recommendation be (for a core i7, karmic 64bit)
[09:18] <lynggaard> RAOF: yeay I know the fglrx can be a lot of work to get working , my old (current) comp has a at x800
[09:18] <RAOF> lynggaard: Well, that'll be particularly difficult since fglrx no longer supports it :).  With a new card, it should be easy.
[09:19] <lynggaard> RAOF: i know, it went away when I did an upgrade to 9.04 :-(
[09:19] <RAOF> lynggaard: Last I checked, ATI cards had the best price/performance.  As you'll initially need a binary blob whichever way you go, I'd choose ATI - you'll get an OSS driver faster.
[09:21] <dupondje> nouveau driver works fine here
[09:21] <dupondje> but no 3D :(
[09:22] <RAOF> Right.  Nouveau driver is a much better 2d driver than the nvidia blob.  With the exception of suspend/resume.  Just no 3d
[09:22] <lynggaard> dupondje, my work-paid laptop has nvidia mobile something, works great but I am only running 32bit on that, hence my initial question about 64bit availability
[09:22] <dupondje> doesn't make a difference
[09:22] <dupondje> all drivers are 32 & 64bit
[09:23] <RAOF> dupondje: That's not strictly speaking true.  It happens to be the case that nvidia provides an x86-64 driver, though.
[09:24] <lynggaard> dupondje, maybe now... but it has certainly been an issue with all my older computers. 64bit is still a bit of a pain, if not the drivers then something else
[09:25] <dupondje> i'm running 64bit karmic, and have no issues
[09:25] <dupondje> 32bit is like prehistoric imo
[09:25] <dupondje> Do they sell any computer with less then 4GB ram now ?
[09:26] <lynggaard> dupondje, try to install lotus software on that ;-)
[09:27] <dupondje> blame the company
[09:28] <dupondje> its sad that still not all software is ported
[09:28] <dupondje> 64bit should be mainstream :s
[09:29] <lynggaard> dupondje, agree... just doesn't help me install the dam thing :-(
[09:29] <lynggaard> but at least I can run ubuntu fulltime at work :-)
[09:29] <syn-ack> I cant. :(
[09:30] <syn-ack> then again, we're a windows shop :D
[09:30] <syn-ack> heh
[09:31] <syn-ack> question
[09:31] <syn-ack> actually, nm
[09:31] <lynggaard> (must admit i have a virtual box, for the 2-3 apps that doesn't work on linux)
[09:32] <syn-ack> question probably isnt "supported" by ubuntu so I will roll my own solution
[10:22] <DanaG> I've been on 64-bit for a while, and haven't had too many issues.
[12:06] <bash> um...
[12:06] <bash> E: Malformed line 1 in source list /etc/apt/sources.list.d/pidgin-ppa.list (dist parse)
[12:06] <bash> :/
[12:08] <bash> fixed it..
[12:08] <bash> sudo rm /etc/apt/sources.list.d/pidgin-ppa.list
[12:12] <penguin42> anyone else seeing gnome app problems since a recent update? All seem to be dieing in libgail?
[13:36] <miik> in installer i picked location sweden, but then it recommended me US keyboard layout
[13:36] <miik> why??
[13:36] <miik> it must know if i pick sweden, it should recommend swedish by default
[13:38] <tgpraveen> miik: many people have the us keyboard layout in many countries
[13:38] <tgpraveen> I think it is most popular layout
[13:38] <tgpraveen> and only minority of people have a different one
[13:39] <miik> uh?? what??
[13:39] <miik> minority? dude
[13:39] <miik> everyone in sweden uses swedish layout
[13:39] <miik> everyone in norway uses norweigan layout
[13:39] <miik> usa uses usa layout
[13:39] <miik> russia uses russian layout
[13:40] <miik> china uses china layout, japan uses japan layout
[13:40] <miik> why it try use US layout if i pick other country than US?
[13:42] <penguin42> hmm I think I saw a similar bug for that
[13:43] <penguin42> milk: Maybe there is a list of rules with only a few in
[13:43] <penguin42> milk: Similar to this one? https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/389610
[13:45] <miik> oh
[13:57] <virtuald> even uk doesn't use us layout
[14:10] <miik> dude i get angry, try ubuntu 9.10 alpha2, in virtualbox, and i can only 800x600 and 640x480
[14:10] <miik> i need higher resolution!!
[14:13] <dupondje> install guest additions
[14:14] <miik> but in windows 7, i dont need isntall guest additions, i can still use 1024x768 and higher
[14:14] <cemunal> can i use alsa-base package for alsa-driver 1.0.20 in 9.04?
[14:15] <cemunal> from karmic repos
[14:16] <tgpraveen> hey I just upgraded and now my system menu
[14:16] <tgpraveen> has many divisions like
[14:16] <tgpraveen> personal,look and feel, internet etc.
[14:17] <tgpraveen> the old way of only two submenus of prefer and admin is gone
[14:17] <tgpraveen> anybody else see this?
[14:17] <penguin42> oh , mine doesn't
[14:17] <tgpraveen> hmm weird it might one of the many ppas that I have enabled
[14:18] <penguin42> but my gnome is not particularly happy after the last update - I've had a few crashes involving libgail
[14:30] <darthanubis> I think I solved a bug?
[14:30] <darthanubis> How can I get the status of it changed?
[14:32] <miik> launchpad maybe?
[14:32] <miik> bugs.launchpad.net
[14:32] <miik> idk
[14:33] <penguin42> darthanubis: Add your fix to the bug in launchpad and hopefully the maintainer of the package will see it, if they don't spot it you might give them a mail - you can also try on #ubuntu-qa
[14:33] <darthanubis> thx
[14:33] <darthanubis> https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/347487
[14:34] <darthanubis> The fix was a hack to my BIOS
[14:35] <penguin42> darthanubis: That's a bit worrying actually - I doubt all the people have a broken BIOS - it's likely that virtualbox needs to be more careful in what it's doing with the bios?
[14:36] <BUGabundo> boas tardes!
[14:36] <darthanubis> penguin42, It was not VB's fault, I believe it is XFX's fault. the MOBO maker.
[14:37] <penguin42> darthanubis: The other guys on there are using Toshiba machines
[14:37] <darthanubis> penguin42, Yeah for them, it was toshiba-acpi or some such
[14:38] <darthanubis> I was not loading that module
[14:38] <nperry`> darthanubis I'm pretty sure its how VB is accessing the mobo.
[14:38] <penguin42> darthanubis: So it looks like there are potentially multiple problems
[14:38] <darthanubis> true, it makes sense
[14:39] <penguin42> darthanubis: On your machine did toshiba-acpi get loaded anyway?
[14:41] <darthanubis> penguin42, never
[14:42] <darthanubis> I have a nforce 680i LT from XFX, with a E8400, no toshi nothing
[14:43] <penguin42> ok, so your case is probably just a screwed bios as you saw - and possibly that bug is just a toshiba one - there are probably multiple things that can kill virtualbox
[14:44] <penguin42> darthanubis: Also it's very very bad manners to tell people to disregard someone elses comment
[14:47] <BUGabundo> hey BluesKaj
[14:47] <BluesKaj> good day folks
[14:48] <BluesKaj> hi BUGabundo
[14:48] <darthanubis> penguin42, I don't need your admonishment. It was worst "manners" to post bogus information to a bug report.
[14:49] <darthanubis> penguin42, the most importatn thing should be the BUG, not someone's feelings.
[14:49] <darthanubis> I asked the guy NOT to do it before he did
[14:50] <darthanubis> I was alerting ppl not to be distracted. Too bad you can't see that. Maybe it would be best to know what your talking about first, so as not to appear to be uncouth?
[14:52] <penguin42> darthanubis: It wasn't false information - he was trying to help to say that virtualbox worked on some systems and thus the bug didn;t affect everyone
[14:52] <darthanubis> ok
[14:53] <darthanubis> I felt I had cause, but I did not like calling out someone like that. I get what your saying. But in the channel before he posted, he seemed flippant and eager to dismiss the bug. I did not feel that was helpful to the resolution of the issue.
[14:55] <darthanubis> I'm human and thanks for pointing out my poor etiquette.
[14:55] <darthanubis> seriously
[14:55] <penguin42> it just seemed a bit harsh
[14:56] <darthanubis> billybigrigger, hope you see where I was coming from? My bad
[14:56] <darthanubis> penguin42, I agree.
[14:56] <darthanubis> I was not personal. I was just really frustrated by the bug.
[14:56] <penguin42> but anyway, it looks like there is a tosh-acpi bug there, and a bios bug - or perhaps virtualbox is being sensitive to something boht are doing that it shouldn't be
[14:56] <darthanubis> It
[14:56] <BluesKaj> I always thought that it's understood that a bug isn't necessarily a bug for everyone. I've certainly encountered that issue many times.
[14:57] <darthanubis> Look at this
[14:58] <darthanubis> Virtualbox Freezes System Everytime (Ubuntu 9.04)
[14:58] <darthanubis> http://forums.virtualbox.org/viewtopic.php?f=7&t=17617&p=81786#p81786
[14:58] <darthanubis> penguin42, KVM locked my system before I hacked my BIOS. I have not tested it yet. But I really think the BIOS was 90% of my issue
[14:59] <penguin42> darthanubis: Yeh - it would get a bit more suspicious if it turns into just a bit more than your machine and all the tosh-acpi users
[15:01] <BluesKaj> hmm, not everyone is gonna hck their BIOS to fix something , especially with VB or VMWare or any other virtual OS . Besides it looks very machine specific.
[15:03] <peabody> yo
[15:04] <penguin42> hi
[15:04] <peabody> I'm trying to build a custom kernel, and let me premise this, I'm not retarded
[15:04] <BluesKaj> yo-yo
[15:05] <penguin42> peabody: From kernel.org or from deb source?
[15:05] <peabody> I'm using 9.04 and I'm following this guide https://help.ubuntu.com/community/CustomRestrictedModules to build my restricted modules
[15:05] <peabody> I'm using the 9.04 ubuntu package
[15:05] <peabody> not lenny
[15:05] <peabody> but yeah, deb source
[15:06] <BUGabundo> and peabody what's up? and why are you doing so ?
[15:06] <peabody> so the instructions say: Note: this will only work if you have created AND installed linux-image and linux-header or linux-source packages.
[15:06] <BUGabundo> sure
[15:06] <peabody> because I'm trying to enable a few optimizations for my cpu and enable 64-bit memory addressing
[15:07] <peabody> so I did my kernel config and built my header and image packages
[15:07] <peabody> then went into the instructions..gedit debian/rules  Now we need to set which flavours will be built, and to note the abi_version
[15:08] <peabody> but in my debian/rules I don't have that abi line
[15:08] <peabody> so I figured, well I will install the packages reboot, and start back from the top because it says they need to be installed
[15:09] <BUGabundo> peabody: wouldn't this be better on #ubuntu-kernel ?
[15:09]  * penguin42 hasn't tweaked a deb build of the kernel
[15:09] <peabody> but when I tried to install my image it executed /etc/kernel/postinst.d/nvidia-common
[15:09] <BUGabundo> after all this is #+1!
[15:09] <peabody> oh I didn't even know!
[15:09] <peabody> thanks
[15:09] <BUGabundo> np
[15:09] <BUGabundo> just trying to get you out of trouble, *before* it bytes you in the @rse
[15:14] <BUGabundo> why cwillu
[15:15] <BUGabundo> what is that channel and ML for the discussion of Design ?? #ux?
[15:15] <Wicla> hey. Are KMS actived per default in Karmic?
[15:15] <BUGabundo> think so
[15:16] <peabody> BUGabundo: It's a ghosttown in there, but I guess I have no choice but to wait them out
[15:16] <BUGabundo> peabody: trying to help a user who asked for that info
[15:17] <BUGabundo> but I can't recall what the ML was! a very strange nam
[15:17] <BUGabundo> *name
[15:17] <Wicla> I'm not sure. Followed "Configuring KMS on Karmic..." on https://wiki.ubuntu.com/X/KernelModeSetting. After reboot my computer wasn't able to restore completly restore itself after suspend.
[15:18] <Wicla> However under "More informaion" it says: "The kernel configuration used for karmic includes KMS by default .."
[15:18] <darthanubis> peabody, https://help.ubuntu.com/community/Kernel/Compile
[15:18] <darthanubis> That worked perfectly for me, now I just have to compile custom modules
[15:18] <darthanubis> peabody, http://kernel.ubuntu.com/~kernel-ppa/mainline/
[15:19] <darthanubis> That is a great resource there! i did not even know we had such a thing
[15:19] <peabody> darthanubis: I'm at the same spot as you
[15:19] <darthanubis> peabody, https://wiki.ubuntu.com/KernelMainlineBuilds
[15:19] <BUGabundo> darthanubis: what? the mainline kernels?
[15:19] <darthanubis> yeah
[15:20] <darthanubis> peabody, https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
[15:20] <peabody> I'm not building from the git, I'm using the stable package
[15:20] <BUGabundo> peabody: that's what the Mainline PPA is for
[15:21] <peabody> I see
[15:21] <peabody> :)
[15:21] <peabody> *starts over*
[15:21] <BUGabundo> ahaha
[15:22] <darthanubis> peabody, I took a break before I tackled the restricted modules
[15:22] <darthanubis> but gues i'll try it now
[15:22] <BluesKaj> peabody, I know that some brave souls over at #kubuntu have built their own kernels , but they're few and far between . It won't hurt to ask tho . There are some knowledgeable and ppl who may help.
[15:22] <darthanubis> need lirc to work
[15:22] <peabody> same for me, I did my compiles about 3 hours ago... then hit a brick wall on the custom modules
[15:22] <darthanubis> peabody, I'll let you know how mine goes
[15:22]  * cwillu poeks BUGabundo 
[15:23] <cwillu> thunderstorms make me bounce in and out of channels .;p
[15:23] <peabody> thanks, and take notes if you would ;)
[15:23] <peabody> I'm going to look at restarting with 2.6.30
[15:23] <cwillu> shouldn't need to compile the kernel just to compile a custom module
[15:23] <cwillu> that's what the kernel headers are fore
[15:24] <penguin42> If i understand peabody has the opposite problem; trying to build a custom kernel and trying just to get the non-free-modules/custom-modules to work with his new kernel build
[15:25]  * BUGabundo tickels cwillu back
[15:25] <cwillu> dkms should take care of that, as long as you build it in a debian way
[15:25] <darthanubis> penguin42, exactly
[15:25] <cwillu> presuming the module in question is actually buildable with any given kernele
[15:25] <peabody> yeah the post-install script is dying on the nvidia section unfortunately
[15:26] <peabody> I've got the kernel compiled and the package built, but the installer is flaking out
[15:26] <darthanubis> Linux core2duo 2.6.30-020630-generic #020630 SMP Wed Jun 10 09:04:38 UTC 2009 x86_64 GNU/Linux
[15:26] <darthanubis> That kernel is from mainline
[15:26] <cwillu> peabody, which version of nvidia?
[15:26] <cwillu> and where is the nvidia package from?
[15:27] <peabody> from the l-r-m
[15:27] <peabody> well no, I 'm not sure where it pulled it from actually
[15:27] <cwillu> earlier version (from before jaunty) may not build against 2.6.30
[15:27] <peabody> I just ended up with an nvidia_180 or something directory in /usr/src
[15:27] <peabody> but everything I'm using I pulled from repository
[15:29] <BUGabundo> cwillu: are you any good with compiz?
[15:29] <BUGabundo> kmail and gwibber start in full screen with compiz enabled
[15:29] <BUGabundo> it used to just be kmail, but now gwibber also does it
[15:29] <cwillu> rules enabled?
[15:29] <BUGabundo> very annoying!
[15:30] <BUGabundo> let me check
[15:30] <BUGabundo> cwillu: windows rules disabled
[15:31] <BUGabundo> I do have a few workarounds enables dough
[15:31] <cwillu> :/
[15:32] <peabody> he shoots he scores
[15:32] <peabody> 2.6.30 headers got the nvidia module installed correctly
[15:32] <cwillu> heh, yep
[15:32] <cwillu> things won't ever build without those :p
[15:32] <penguin42> peabody: Yeh you always need to match your headers with your kernel
[15:32] <peabody> well I did that before ;)
[15:33]  * peabody crosses his fingers
[15:33] <peabody> let's see if I can boot into 2.6.30
[15:33] <peabody> I'm doing all this with kdm shutdown, but does that make a difference?>
[15:34] <cwillu> shouldn't
[15:34] <cwillu> not going to say it won't though :p
[15:34] <cwillu> but it shouldn't
[15:35] <cwillu> BUGabundo, I'm curious, what do those apps do if you run metacity (from the kde session) instead of compiz or kwin?
[15:35] <peabody> well, rebooted into 2.6.30, but I think there's an issue with X, which means with nvidia
[15:36] <cwillu> doesn't start up?
[15:36] <cwillu> do you have an xorg.conf file that might be screwing things up?
[15:36] <cwillu> (you need one with nvidia)
[15:36] <peabody> Fatal sever error: No screens found
[15:36] <BUGabundo> cwillu: no idea! I don't have the full blown KDE wm here
[15:36] <BUGabundo> peabody: run XFIX on it
[15:37] <peabody> like kdm XFIX ?
[15:37] <cwillu> peabody, nvidia-xconfig should give you a mostly usable xorg.conf file
[15:38] <cwillu> alternatively, just make sure you have a device section, and the driver set to nvidia
[15:38] <peabody> hmm tty7 is just a black screen with a blinking cursor
[15:38] <peabody> I'm waiting for it to write out follow the white rabbit or something
[15:39] <cwillu> pastebin /etc/X11/xorg.conf and /var/log/Xorg.0.log
[15:40] <peabody> hrmm.. it's on a different computer without windowing, but let's see if pastebun is lynx compatible
[15:40] <peabody> err wait, I'll just setup ftpd and steal it off
[15:41] <penguin42> scp ftw
[15:41] <peabody> I don't have any ssl stuff setup yet
[15:41] <cwillu> peabody, apt-get install pastebinit
[15:41] <cwillu> and then pastebinit /etc/X11/xorg.conf
[15:42] <peabody> nice
[15:42] <BUGabundo> peabody: install pastebinit!
[15:42] <BUGabundo> !info pastebinit
[15:42] <peabody> yeah it's installed ;) thx
[15:42] <BUGabundo> darn cwillu beat me to it
[15:43] <cwillu> BUGabundo, and I'm in the middle of building the base in a tremulous game too :)
[15:43] <BUGabundo> ahah
[15:43] <peabody> http://pastebin.com/f5e29f4c1
[15:43] <cwillu> BUGabundo, I don't have a browser available, can you check that and make sure nvidia's configured? :)
[15:43] <peabody> http://pastebin.com/f65e0a7f9
[15:44] <BUGabundo> checking
[15:44] <BUGabundo> cwillu: never heard of elynks? LOL
[15:44] <peabody> (EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
[15:44] <BUGabundo> peabody: Unknown post id, it may have expired or been deleted
[15:45] <cwillu> peabody, okay, does dmesg show anything interesting?
[15:45] <cwillu> and try modprobing nvidia directly
[15:45] <BUGabundo> peabody: chose recovery mode on GRUB and run XFIX first
[15:45] <BUGabundo> so it reconfigures xorg
[15:45] <peabody> nvidia: no symbol version for module_layout
[15:45] <peabody> BUGabundo: rebooting
[15:46] <cwillu> BUGabundo, I have moral issues with terminal-mode browsers :p
[15:47] <BUGabundo> like what?
[15:47] <peabody> ok that got me back into X without the nvidia module
[15:48] <BUGabundo> no so bad
[15:48] <BUGabundo> at least you now have Xorg
[15:48] <peabody> so.. progress at least.. now I need to rebuild the kernel with customizations, then rebuild my restricted modules.... bbiab
[15:49] <Machtin> hm, i accidentaly removed that folder view.. in which you can enter folders.. i added another folder view via "add widgets".. but when i want to open a folder within it, it just opens the folder with dolphin..
[15:49] <Machtin> how can i get that standard-thing back?
[15:49] <peabody> too bad it's like 640-480 on a 24" widescreen ;)
[15:50] <BUGabundo> peabody: been there :))
[15:51] <penguin42> pixels the size of a golf ball
[15:56] <BUGabundo> lol
[16:03] <peabody> penguin42: pretty much, I've got one tab open and it takes up half the taskbar.. it's bigger than my hand!
[16:04] <penguin42> ouch
[16:04] <peabody> nw though, new kernel is compiling now
[16:05] <peabody> for all it's little hassles, kubuntu is such a better build than fedora kde
[16:06] <BUGabundo> peabody: why do you say so?
[16:07] <peabody> well there's some differences like I never had to fudge with the nvidia stuff, my graphics were right out of the box on fedora
[16:07] <peabody> but I think debians doing a better job at getting the hardware right.. even if they're all ass sore about the nvidia drivers
[16:08] <peabody> fedora blew a fucking wad on my disks and once I get all this straight, I've got to run testdisk on my home directory to get back BOTH mirrors of all my pictures and everything else
[16:09] <peabody> I went to reinstall fedora this morning, and the installer wouldn't even detect my primary disk.. even though I had it mounted and everything
[16:10] <peabody> it's probably not so much fedora's fault my home directory got hosed, as it would be ext4's fault but trying to restore and not even getting my disk in the installer was an unexpected nightmare
[16:11] <peabody> it's always hardest to troubleshoot something when there's no errors and everything seems to work except what you are trying to do!
[16:14] <peabody> oh and fedora does handle my bluetooth keyboard and mouse correctly where I have to edit my /etc/default/bluetooth and /etc/init.d/bluetooth to get it to stay connected in kubuntu
[16:14] <peabody> that's about it though
[16:15] <peabody> it's just not quite as pretty as fedora
[16:15] <peabody> :p
[16:16] <BUGabundo> peabody: keyb and mouse via BT been working for me since hardy with no major prob
[16:16] <BUGabundo> did you do the "correct" way ?
[16:17] <peabody> well when it tries to enable hci mode it disconnects them and they won't reconnect.. I've read that the problem is with my stupid logitech bluetooth dongle but I didn't have any problem in fedora using them
[16:17] <peabody> so I just disable hci mode and they work without issue.. I jsut can't connect like my cell phone
[16:30] <peabody> hmm.. this is perfect http://kcheck.sourceforge.net/
[16:33] <BUGabundo> what is it ?
[16:34] <peabody> it's a python script that pulls all the sources from kernel.org and you chose your optimizations and it builds and isntalls everything automatically
[16:35] <BUGabundo> really?
[16:35] <peabody> but it uses pygtk so I'd have to run it from livecd... but still nice tool
[16:35] <BUGabundo>  $ bzr branch lp:kernelcheck
[16:35] <BUGabundo> wait a minute!!!
[16:35] <BUGabundo> its uses LP ?
[16:36] <BUGabundo> "This automated process is a fork of AutoKernel"
[16:40] <tgpraveen> does anyone here know abt the progress of delta debs?
[16:40] <tgpraveen> iirc it was a high priority blueprint I think such a thing should be worked upon quickly and implemented say by alpha 4 or so
[16:40] <tgpraveen> as in the alpha cycles when we have a lot of updates it will be most useful
[16:40] <tgpraveen> any news anyione on this?
[16:41] <BUGabundo> was it really?
[16:41] <BUGabundo> I don't recall it being HIGH
[16:41] <BUGabundo> do you have a link for it ?
[17:03] <YDdraigGoch> BUGabundo, https://blueprints.launchpad.net/ubuntu/+spec/rsync-based-deb-downloads
[17:03] <BUGabundo> lets see
[17:05] <BUGabundo> thanks for the linki
[17:05] <BUGabundo> must have missed it
[17:05] <BUGabundo> subbing
[17:05] <YDdraigGoch> yw =)
[17:08] <BUGabundo> what's the name of debian unstable?
[17:08] <BUGabundo> its not sid anymore is it
[17:08] <BUGabundo> ?
[17:08] <penguin42> thought it still was
[17:08] <penguin42> it's always been sid
[17:09] <BUGabundo> $ cat /etc/debian_version
[17:09] <BUGabundo> squeeze/sid
[17:09] <BUGabundo> really?
[17:09]  * penguin42 wonders what squeeze is
[17:09] <BUGabundo> I though each of the 3 repos had a name, like we do
[17:09] <BUGabundo> so they have stable, experimental and unstable
[17:09] <BUGabundo> each gets a name per cycle
[17:10] <penguin42> no, I think unstable is always sid, and they just move the names through stable and testing
[17:10] <BUGabundo> *if* karmic is based on their unstable it shouldn't be sid
[17:10] <BUGabundo> *if* I'm correct
[17:10] <BUGabundo> ahhhh that explains it penguin42
[17:10] <BUGabundo> thanks
[17:10] <BUGabundo> so squeeze is the new testing ?
[17:10] <ziroday> mmhm
[17:11] <Tekno_> what o_O
[17:11] <Tekno_> this is ubuntu channel
[17:12] <penguin42> BUGabundo: sid was the unstable neighbour in the Toy Story film
[17:12] <BUGabundo> Tekno_: if you read it all, you will see its karmic related!
[17:13] <BUGabundo> could have been a bug on /etc/debian_version
[17:14] <BUGabundo> cwillu: here is a nice tool to debug nvidia: nvidia-bug-report.sh
[17:47] <coz_> hey guys  wanted to upgrade to 9.10  but its been stuck at the last downloadable file for 2 hours   what to do?
[17:47] <BUGabundo> coz_: stop it, change mirrors and try again ?
[17:47] <penguin42> I'd kill the download and kick it off again - what's the file?
[17:48] <coz_> BUGabundo,  change mirrors?  I was using   update-manager -d
[17:48] <BUGabundo> so what?
[17:48] <coz_> ok
[17:48] <BUGabundo> you can change it anyway
[17:48] <BUGabundo> there are several other servers that have karmic
[17:48] <BUGabundo> not all, it's a fact, but many
[17:48] <coz_> BUGabundo,  ok I am new to upgrading lol  I never upgrade
[17:48] <BUGabundo> of course you can retry with current server
[17:49] <coz_> it didnt download session -uitls
[17:49] <BUGabundo> coz_: did you read the release notes?
[17:49] <BUGabundo> better get that
[17:49] <BUGabundo> eheeh
[17:49] <coz_> BUGabundo,  ;)
[17:50] <coz_> ok retrying
[17:53] <coz_> ok got it :)  duh
[19:02] <DanaG> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/284319
[19:03] <BUGabundo> DanaG: humm aint that one of those
[19:03] <BUGabundo> that the change in devikit and hal?
[19:03] <DanaG> Nope, it's more of a progression -- started out with lots of broken things, and now has only one major one left.
[19:04] <DanaG> handy hint: read posts from bottom to top.  =þ
[19:05] <BUGabundo> LOL
[19:05] <BUGabundo> well my powerbutton stil doesn't work
[19:12] <DanaG> Does Launchpad have a way to automatically / programmatically forward bug reports upstream?
[19:13] <dupondje> don't think so
[19:13] <dupondje> else it would need an account upstream everywhere
[19:13] <dupondje> etc
[19:13] <dupondje> etc
[19:13] <dupondje> :)
[19:14] <BUGabundo> DanaG: no
[19:14] <DanaG> Bummer.
[19:14] <BUGabundo> it "helps" you, but you need to upstream it your self
[19:14] <DanaG> I wanted to forward the ALSA bug upstream.
[19:14] <DanaG> without making an account/
[19:14] <DanaG> .
[19:14] <dupondje> its lovely to have alot of accounts !:)
[19:14] <dupondje> spam +++ :)
[19:15] <BUGabundo> I have way to many already
[19:16] <dupondje> the One Hundred papercuts guy is never here anymore ? :p
[19:17] <BUGabundo> ah?
[19:18] <dupondje> killin bugs ! :)
[19:28] <peabody> blarg
[19:29] <peabody> same freaking problem compiling and installing this kernel package
[19:29] <peabody> once I build the image package when I try to install it, it errors out on nvidia crap again
[19:29]  * peabody hits head against wall repeatedly
[19:31] <peabody> hmm.. I think I might have figured out how to punch through it though
[19:31] <peabody> is there a way to reboot to grub short of shutdown -h?
[19:32] <peabody> reboot and shutdown -r both just reload the currently loaded kernel
[19:33] <peabody> ok now I wonder if I should download and compile the nvidia drivers or if I should try using the restricted drivers..
[19:33]  * BUGabundo is confused by peabody question
[19:33] <DanaG> ugh, top-posting: http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/archive/2009/03/msg00138.html
[19:33] <DanaG> this WHOLE mailing list is top-posted.
[19:34] <BUGabundo> LOLOLOL
[19:34] <BUGabundo> outlook?
[19:34] <peabody> I got it recompiled and installed with my custom kernel, but I glazed over the restricted drivers part... now I'm debating just runnning the current nvidia driver script or rebuilding the ubuntu restricted drivers .. and I've decided on the former
[19:36] <DanaG> And they also have endless quoting.
[19:36] <DanaG> =þ
[19:37] <peabody> BOOYAKA
[19:39] <BUGabundo> peabody: ahaah
[19:39] <BUGabundo> DanaG: and AV warning ?!
[19:40] <peabody> BUG now I jsut have to rebuild my raid, recover my lost files, and I'm back in business ;)
[19:40] <peabody> it's cakewalk from here though ;)
[19:42] <stormy2k> Is this also a channel for KDE problems in kubuntu 9.10 or is there another channel for that?
[19:42] <peabody> try #kde or #kubuntu
[19:43] <BUGabundo> stormy2k: user question yes
[19:43] <BUGabundo> devel questions try #kubuntu-devel
[19:43] <stormy2k> Ok, thanks
[19:44] <BUGabundo> np
[19:44] <stormy2k> Well, it's a simple one I guess. I just can't find the configuration for my touchpad. Under Gnome it works fine (scrolling and tapping), but under KDE it doesn't
[19:44] <BUGabundo> btw does grub2 handle LVM booting ?
[19:44] <BUGabundo> stormy2k: wrong
[19:44] <stormy2k> Okey, thx anyway :)
[19:44] <BUGabundo> tapping is not working
[19:44] <BUGabundo> known bug
[19:45] <BUGabundo> let me see if I can find it
[19:45] <stormy2k> Oh, okey, I can look it up myself on Launchpad
[19:45] <BUGabundo> thanks
[19:45] <BUGabundo> my FF awesome bar is missbeaving
[19:46] <BUGabundo> so autocomplete is not working as expected
[19:47] <stormy2k> You use 3.0 or 3.5 version?
[19:48] <BUGabundo> ff 3.6
[19:48] <BUGabundo> for a moment I though you were refering to KDE 3.5
[19:48] <BUGabundo> LOLOLOLOLOLOLOLOLOLOL
[19:48] <stormy2k> ^^
[19:48] <stormy2k> There's a 3.6 allready?
[19:53] <BUGabundo> of course
[19:53] <BUGabundo> alpha1
[19:54] <BUGabundo> stormy2k: https://launchpad.net/~ubuntu-mozilla-daily/+archive/ppa
[19:55] <stormy2k> So thats allready the built-version of the next firefox that comes after 3.5?
[19:56] <BUGabundo> yes
[19:57] <stormy2k> Well, that's bleeding edge
[19:57] <peabody> omg this is so much faster
[19:57] <stormy2k> But 9.10 will include 3.5 or even 3.6?
[19:58] <BUGabundo> 3.5
[19:58] <BUGabundo> and yes, its MUCH faster
[19:58] <BUGabundo> and 3.6 is even faster
[19:58] <hifi> 3.5 is in the karmis repos?
[19:59] <BUGabundo> hifi: y
[19:59] <hifi> nice, will try
[19:59] <stormy2k> Yes hifi
[19:59] <BUGabundo> *** 3.5~rc2+nobinonly-0ubuntu1 0
[19:59] <BUGabundo>         500 http://archive.ubuntu.com karmic/universe Packages
[19:59] <stormy2k> Even faster? Wow. I'm using 3.5 at karmic and I have to say I like it
[19:59] <hifi> yeah!
[19:59] <BUGabundo> stormy2k: try 3.6
[19:59] <BUGabundo> eheh
[20:00] <stormy2k> But 3.5 is also in the official repos
[20:00] <hifi> is there a backport for jaunty?
[20:01] <hifi> wait, never mind
[20:01] <hifi> of course there's in the ppa repo
[20:02] <BUGabundo> hifi: see the PPA I gave
[20:02] <stormy2k> Think he found it allready :)
[20:02] <BUGabundo> hifi: https://launchpad.net/~ubuntu-mozilla-daily/+archive/ppa
[20:03] <peabody> BUGabundo: I was talking about my new kernel.. way faster optimized ;)
[20:03] <hifi> though the current versions are in the build queue, waiting for them to finish
[20:03] <BUGabundo> peabody: are you sure?
[20:03] <hifi> my firefox extensions will most probably stop working
[20:03] <BUGabundo> our kernel team tries to make it AFAP
[20:03] <stormy2k> Most work with 3.5, don't know about 3.6
[20:03] <BUGabundo> hifi: they will
[20:04] <BUGabundo> stormy2k: you can't imagine! most of my 58 are dead
[20:04] <BUGabundo> now I have a subset of 30 something forced with nightly tools
[20:04] <stormy2k> Wow... 58, you really need this browser ;)
[20:05] <stormy2k> Well, noscript, addblock, cookie sage, that's pretty much it for me
[20:06] <BUGabundo> let me pastebin the list
[20:06] <peabody> absolutely, and I'm sure I made mods your kernel team would not.. though I don't know why they set the core freq to 300 mhz.. I bumped it to 1000 of course dropped support for ISA, MCA, PCMCIA, etc architectures not in my config, changed it from i586 arch to Athlon64, switched to sparce memory model, enabled the 64GB memory, and changed my prioritization to real-time instead of CFQ, switch compression to LZH.. a few other tweaks, but
[20:06] <peabody>  else really performance related
[20:06] <BUGabundo> stormy2k: http://paste.ubuntu.com/200986/
[20:07] <BUGabundo> peabody: whould you opening a thread on kernel ML with that?
[20:07] <BUGabundo> and let me know the results of the discussion
[20:07] <stormy2k> Wow, thats a lot, will have a look at some of them
[20:08] <BUGabundo> stormy2k: that's just a small set LOL
[20:08] <peabody> sure, I'll jsut toss up a copy of my .config and see what they say
[20:09] <peabody> a few parts are still experimental, but the difference I've got is dramatic
[20:10] <BUGabundo> remember they have to support OLD HW
[20:10] <BUGabundo> you don't!
[20:13] <peabody> yeah I know that's wishful thinking that they would remove support for MCA, despite a PS/2 not having been sold for 20 years ;)
[20:15] <peabody> I don't think there's a single 586 platform that supports it so I kinda don't get why they would include it when the arch is i586
[20:17] <peabody> anyways, I'm going to start disk analysis and play ps3, thanks for the help earlier :)
[20:18] <stormy2k> Yeah, thanks for your help from my side as well
[20:18] <BUGabundo> peabody: there's a blueprint and discussion of moving from 586 to 686
[20:18] <BUGabundo> so now it's the time
[20:42] <coz_> anyone here using easystroke on karmic?
[20:44] <coz_> I am getting no errors in the terminal for this but this is suppose to be a lower case "n"   http://picpaste.com/upload.php
[20:45] <Machtin> is there some program, with which i could create midi files? like a on-screen keyboard or something like that
[20:45] <coz_> but no big deal .. at least yet.. i just switched the gesture renderer to compiz/annotate
[21:09] <BUGabundo> Sarvatt: ping. after reboot I don't have composite working :((((
[21:30] <dupondje> anjunta package broken it seems
[21:33] <Tekno_> Really sure, are you.  Yeesssssss.
[22:47] <ripps> I see that pidgin can now be hidden using the indicator-applet, is there anyway to make it hidden by default?
[22:49] <BUGabundo> ripps: isn't it hiddin already?
[22:49] <BUGabundo> or was that on KDE ?
[22:50] <ripps> BUGabundo: when I start pidgin at boot, it's not minimized
[22:50] <BUGabundo> ahh the minimize
[22:50] <BUGabundo> that's done with a plugin
[22:50] <BUGabundo> mine starts minimized!
[22:54] <ripps> Okay, here's another one. Why doesn't evolution-indicator do anything anymore? I liked how it worked in Jaunty, now it does nothing. I filed a bug on this.
[22:59] <ripps> Okay, the extpref plugin for pidgin allows me to minimize it, but it's not really hidden. It's still sitting there in the toolbar.
[23:00] <EagleSn> I have installed Ubuntu Karmic Alpha 2
[23:00] <BUGabundo> woot EagleSn
[23:00] <EagleSn> installer crashed in the lastest steps
[23:00] <EagleSn> now ibuquity is isntalled in installed system
[23:01] <EagleSn> it becomes with GRUB 2, and detection of other OS is not still working
[23:02] <ripps> EagleSn: I had alot of issues installing Karmic from cd, I had to use the daily-live cd, and even then it took me several tries to install it all the way
[23:04] <EagleSn> it installed for me
[23:04] <EagleSn> how can I add a Window$ OS to GRUB 2?
[23:36] <_CommandeR_> Hi I get an error when i boot from USB = http://pastebin.com/m38bb2b5e
[23:38] <BUGabundo> _CommandeR_: that's not karmic!
[23:38] <_CommandeR_> BUGabundo, oh sorry this is only for karmic ?
[23:39] <_CommandeR_> my fault last time I was here it was for jaunty sorry guys :)
[23:39] <BUGabundo> _CommandeR_: yes
[23:39] <hexa> i wonder why nobody commented on my bug report
[23:39] <hexa> https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/390035
[23:39] <BUGabundo> eheh
[23:39] <BUGabundo> its always the devel branch
[23:51] <sahak> hello
[23:51] <sahak> is Ubuntu 9.10 going to use KMS by default?
[23:51] <BUGabundo> hey sahak
[23:51] <BUGabundo> ys
[23:51] <BUGabundo> already does
[23:51] <hexa> anybody know how i can reset the nautilus settings?
[23:52] <sahak> BUGabundo, do LiveCDs use it too?
[23:52] <hexa> or set every folder to Symbol View
[23:52] <sahak> if I install from http://cdimage.ubuntu.com/daily-live/ will I get it enabled by default?
[23:53] <hexa> got it
[23:53] <BUGabundo> hexa: no idea
[23:53] <hexa> that fixes the problem
[23:53] <hexa> at least for nautilus
[23:53] <hexa> so i suppose sarvatt was right about the sort columns problem
[23:53] <BUGabundo> sahak: should
[23:53] <RAOF> BUGabundo: It's _available_ by default, but I don't think it's enabled by default yet; certainly the -9 kernel defaults to no-KMS.
[23:53] <BUGabundo> ok
[23:53]  * BUGabundo gets an eraser 
[23:53] <sahak> RAOF, thanks
[23:54] <sahak> RAOF, and to enable it I have to rebuild initrams?
[23:54] <RAOF> sahak: Nah; you can just pass i915.modeset=1 to the kernel from GRUB if you like.
[23:55] <sahak> RAOF, thanks again. I am going to try it right now.
[23:55] <RAOF> Or add that to a file in /etc/modprobe.d.  But if you want the modeset as soon as possible in the boot, yes, you'll need it in the initrd.