[00:25] <funkyHat> yofel: thanks. knittl - I'm having the same issue with mysql, and the dbs are in the standard place, no separate partition
[01:12] <IdleOne> I just had a very weird thing happen. I rebooted and was not able to get a GUI so went into grub and removed quiet splash and added text to boot options. When I did ctrl-x to boot up the GUI loaded and I was able to login normally
[01:39] <ZykoticK9> IdleOne, "ghost in the machine" ;)
[02:03] <kklimonda> seriously, I shouldn't install windows on my laptop and then install 10.10 - now I can see how slow it is :/
[02:04] <kklimonda> (by it I mean 10.10 )
[02:11] <BUGabundo> what?
[02:11] <BUGabundo> the GTK ?
[02:12] <kklimonda> everything
[02:13] <kklimonda> switching desktops is painfully slow, gtk apps are slow
[02:15] <kklimonda> oh, and firefox + flash is slow but that's nothing new
[02:17] <kklimonda> btw, what is up with the Ambiance theme? are the new buttons here to stay?
[02:18] <kklimonda> I actually like the new version of Ambiance more - buttons in 10.04 felt way yo heavy, especially in nautilus' breadcrumbs
[02:18] <kklimonda> but those new buttons look out of place
[02:19] <kklimonda> I wonder how does opera look like
[02:21] <BUGabundo> yep, that's the GTK bug
[02:21] <BUGabundo> just switch themes
[02:22] <BUGabundo> run gtkpref
[02:22] <BUGabundo> till you findout the one faster for you
[02:23] <kklimonda> heh
[02:24] <kklimonda> Total time: 20.23 is pretty bad, right? ;)
[02:25] <kklimonda> yeah, 8 times slower than clearlooks
[02:25] <kklimonda> seriously, wtf?
[02:27] <Daekdroom> 16,42 here with non default theme
[02:27] <Daekdroom> and it feels kinda smooth
[02:28] <Daekdroom> 16,44 with ambience
[02:28] <kklimonda> clearlooks is almost as fast as the default gtk+ theme and ambiance is .. slow is a wrong word here :/
[02:29] <Daekdroom> Human-Clearlooks is 13,30
[02:29] <kklimonda> check Redmond or Raleigh
[02:36] <BUGabundo> told you
[02:36] <BUGabundo> gtk bug
[02:37] <BUGabundo> im on 7sec or something
[02:37] <BUGabundo> Total time:  6.71
[02:37] <BUGabundo> AH AH
[02:37]  * BUGabundo points finger
[02:38] <kklimonda> but that's not ambiance, right? ;)
[02:40] <BUGabundo> no no
[02:40] <BUGabundo> its the fastest theme I could build
[02:40] <BUGabundo> one of the dark kind
[02:41] <Daekdroom> I'm completely satisfied with 16secs here :|
[02:42] <BUGabundo> I'm not
[02:42] <BUGabundo> I use FreeNX a lot
[02:42] <Daekdroom> FreeNX?
[02:42] <BUGabundo> that would timeout and kill my link
[02:42] <BUGabundo> !freenx > Daekdroom
[03:39] <KukuNut> why push xchat-common when xchat isn't ready? been days now but now updated xchat???
[03:40] <KukuNut> no*
[03:47] <kklimonda> well, that's called development for a reason - various things are in the flux
[03:48] <kklimonda> both xchat and xchat-common are built from the same source package so the fact that there is a newer version of xchat-common means that the i386 build has failed or is still in the queue.
[03:48] <kklimonda> may also be a problem with your mirror
[03:50] <kklimonda> s/i386/amd64
[04:34] <KukuNut> kklimonda: this is 64-bit
[05:51] <litropy> Upon bootup, I get the error: "fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver"
[05:52] <litropy> the error is reported already: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/609044
[05:52] <litropy> but I'm offering my system for diagnosis, since this is so new
[06:54] <DanaG> request_module: runaway loop modprobe binfmt-464c
[06:54] <DanaG> Can't boot Maverick because of that.
[07:44] <knittl> funkyHat: ok, good to know
[08:06] <bdunnaway> question for the sages:   I wish to move my root fs (btrfs) onto my LVM2 Volume Group.  I want grub2 to look for my / by uuid instead of /dev/sda3 or whatever
[08:07] <bdunnaway> running maverick, with ext2 /boot on sda1 and btrfs / on sda3 currently.  my lvm is on /sdc & sdd
[08:08] <bdunnaway> grub2 line reads:  linux	/vmlinuz-2.6.35-8-generic root=/dev/sda3 ro   quiet splash
[08:10] <Jordan_U> bdunnaway: Grub should be using UUIDs by default. If it's not for a btrfs root then please file a bug report.
[08:13] <bdunnaway>  it is.  Essentially an experimental system, but I'm running mostly a fresh install.  I had some issues earlier with grub2 & btrfs, but I've sorted them.  That's a update-grub generated line I posted
[08:14] <bdunnaway> now grub itself is referring to it's own /boot uuid:   search --no-floppy --fs-uuid --set 0130ab6d-ba48-4c29-xxxx--xxxxx
[08:15] <bdunnaway> but not root.  This is more of a search for knowledge than a support request, tbph
[08:18] <Jordan_U> bdunnaway: My guess is that grub-probe doesn't support grabbing the UUID of a btrfs filesystem yet. When the legal issues are sorted out and complete btrfs support is added to grub2 this problem will also be solved. But it could also be solved separately before then.
[08:20] <bdunnaway> sweet.  Well I can always manually set the /dev/mapper/vg-root  if needed I suppose
[08:30] <DanaG> https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/565002
[08:30] <DanaG> ARGH
[08:30] <DanaG> methinks they mean dlopen?
[12:11] <penguin42> forrestv: Good spot on unclutter
[12:18] <penguin42> it's also the cause of my most annoying bug (605829)
[14:51] <alkisg> !info freerdp maverick
[14:51] <alkisg> Hello, I'm looking for a new package called freerdp which supposedly landed in Ubuntu 4 days ago (https://bugs.launchpad.net/ubuntu/+bug/606601 - fix released) but I don't see it in the repositories - is more time needed until it's there?
[14:56] <Daekdroom> alkisg, you have to check if it's built
[14:57] <alkisg> Daekdroom: any hints where to check? Where's the build queue?
[14:57] <Daekdroom> alkisg, package page under ubuntu project in Launchpad
[14:58] <alkisg> Ah, thanks, got it
[14:58] <Daekdroom> alkisg, https://launchpad.net/ubuntu/+source/freerdp/0.7.2-1
[14:58] <Daekdroom> Should be in the repos already.
[14:58] <alkisg> I didn't realize it first shows in +source and then on the repos...
[15:34] <dieki> Anybody else had trouble with slow window redraws in Unity\Mutter on NVidia cards?
[16:19] <Daekdroom> Good lord. Pulseaudio is failing me =/
[16:19] <Daekdroom> They should seriously switch to OSSv4 someday.
[16:21] <penguin42> Daekdroom: What's it doing to you?
[16:21] <Daekdroom> penguin42, randomly stopping to work at all.
[16:21] <Daekdroom> Right now, for example, I have no sound no matter what.
[16:22] <Daekdroom> Althought I learned it can be fixed by restarting my session.
[16:22] <Daekdroom> Going to do that and gonna dig related bugs on launchpad.
[16:22] <penguin42> oh, he's gone
[16:23] <Daekdroom> hm.. seems relogging didn't work..
[16:23] <penguin42> Daekdroom: Some things to try
[16:24] <penguin42> Daekdroom: Check /var/log/user.log for errors (I always see some), try pasuspender /bin/true  and also do an lsof /dev/snd/*
[16:25] <Daekdroom> and there we go..
[16:25] <Daekdroom> http://pastebin.com/VcURLtCC
[16:26] <Daekdroom> http://pastebin.com/JyWd9HCh
[16:27] <penguin42> Daekdroom: Well there's your error - interestingly I did have a single sink is suspended message in my logs but it seems to work
[16:28] <penguin42> Daekdroom: Ah, figure out what that plugin-co thing is - that's your problem
[16:28] <Daekdroom> Probably firefox's plugin-container
[16:28] <penguin42> it's odd, because most firefox stuff does manage to route itself down pa
[16:30] <Daekdroom> A killall plugin-container did it.
[16:30] <Daekdroom> Curse you, flash!
[16:30] <penguin42> Daekdroom: Hmm I'm using flash from chrom and it's not having a problem with pa (via nspluginwrapper admittedly)
[16:32] <Daekdroom> Looks like Flash can't output sound if there's something else already doing it through PA.,
[16:34] <crimsun_> then your pluginwrapper is broken; is ia32-libs synced?
[16:34] <crimsun_> (presuming you're using a 64-bit host)
[16:35] <Daekdroom> Not using 64 bit :|
[16:36] <crimsun_> Daekdroom: did you do anything specifically like rip out bits of the pulseaudio infrastructure?
[16:36] <Daekdroom> I don't think so.
[16:36] <crimsun_> sorry, but "don't think so" isn't quite precise enough here ;)
[16:37] <Daekdroom> Let me rephrase..
[16:37] <Daekdroom> I didn't do anything with it intentionally, and probably unintentionally as well.
[16:37] <Daekdroom> I don't recall any package installed/upgraded messing with pulseaudio stuff either.
[16:41] <crimsun_> Daekdroom: ok, let's back up. Is this a standard maverick install?
[16:42] <Daekdroom> crimsun_, huh.. I have xorg-edgers PPA and mozilla-daily
[16:43] <crimsun_> err, ok. So you have firefox 3.6.9~hg20100722r34448.. installed?
[16:43] <crimsun_> Daekdroom: which page are you navigating to that causes this symptom?
[16:44] <crimsun_> s/causes/also triggers/
[16:44] <Daekdroom> crimsun_, apparently, any.
[16:44] <Daekdroom> Either I have sound output on the rest of the system or in the flash plugin.
[16:44] <Daekdroom> Can't have both :O
[16:45] <Daekdroom> As soon as I close the page, rhythmbox/totem/whatever starts playing sound
[16:46]  * penguin42 wonders why his kernel build has hung
[16:46] <symptom> crimsun_, MINE!
[16:47] <crimsun_> symptom: can't help if your nick collides with a common bug work use ;)
[16:48] <crimsun_> Daekdroom: k, i'll try to reproduce locally
[16:48] <Daekdroom> crimsun_, huh oh..
[16:48] <Daekdroom> Apparently, it was ~/.asoundrc or something like that :Z
[16:48] <crimsun_> hah
[16:48] <symptom> crimsun_, ya know it is surprising, it really doesnt happen that often
[16:48] <crimsun_> Daekdroom: yeah, that's a thorny one
[16:49] <Daekdroom> I better reinstall my system, incluiding but not limited to cleaning every hidden folder in my home. :|
[17:02] <penguin42> anyone having fakeroot problems?
[17:04] <crimsun_> may be tangentially related to debian 525144
[17:06] <penguin42> crimsun_: Hmm, I'm not getting a seg, I'm getting a hang in a semop, and if I kill it and start again I get an error about semop(1) failure
[17:06] <crimsun_> this is with 2.6.35-12.17?
[17:07] <crimsun_> I'm cheating a bit (2.6.35-12-generic #17~lucid1-Ubuntu)
[17:07] <penguin42> no, -10.15
[17:07] <penguin42> (current maverick)
[17:07] <crimsun_> I'll zsync a daily and see if I can reproduce
[17:07] <crimsun_> ..it
[17:07] <penguin42> I'm not sure if it's reproducable - I got it on the kernel build I was doing
[17:08] <crimsun_> 64-bit host compiling a 64-bit kernel?
[17:08] <penguin42> yes
[17:08] <penguin42> reported it as bug 609513
[17:20] <penguin42> crimsun_: Anyway, where did you get the -12 ?
[17:26] <crimsun_> penguin42: http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu/pool/main/l/linux-maverick/
[17:27] <penguin42> ah
[17:39] <crimsun_> oh you. silly cpu causes virtualbox-ose not to support 64-bit guests.
[17:39] <penguin42> which CPU?
[17:41] <crimsun_> well, to be fair, it's this bios coupled with this cpu
[17:41] <crimsun_> U4100
[17:45] <penguin42> it's interesting the only refence to the U4100 on intel.com is someone saying it's actually an Su4100
[17:46] <penguin42> http://ark.intel.com/Product.aspx?id=43568 shows it as not having VT
[17:49] <crimsun_> that's what I get for trying to go inexpensive
[17:49] <penguin42> yeh, this laptop has the same problem; it's got a T5500, bottom end early Core2 - about the only one without VT
[18:00]  * penguin42 wonders if anyone has checked Maverick on a 2.5T disk
[18:17] <gubu> latest xchat asking what channel to join and telling me no channel joined when by def #ubuntu is
[18:30] <yoasif> im using pidgin and the notification plugin seems to stop working after a while
[18:30] <yoasif> anyone else seeing this?
[18:30]  * penguin42 hasn't moved over to using pidgin on his maverick box yet, hmm maybe I should upgrade this box
[18:31] <Daekdroom> yoasif, I haven't noticed that.
[18:31] <yoasif> Daekdroom, bah
[18:32] <Daekdroom> Speaking of pidgin.. Random crash right now :|
[18:33] <yoasif> woo
[18:33] <yoasif> is there a bug open for volume resetting to mute on reboot? crimsun_
[18:33] <Daekdroom> yoasif, afaik, yes.
[18:35] <penguin42> oh, wth I'll take this one upto maverick, now that I've been able to work around most of the bugs on my other machine
[18:49] <penguin42> the download is nice and fast (coming off a squid on the machine I've already upgraded), but the dpkg will be SLOW on this laptop
[18:58] <kklimonda> is there a good explanation why is lapotp getting hotter under linux than under windows?
[18:58] <penguin42> kklimonda: I think that can be quite hard to analyse; you could try using powertop
[18:58] <Volkodav> or get the higher rpms on the fans
[18:59] <kklimonda> well, my fan is running as fast as on windows so that's not it
[19:00] <kklimonda> and it's running constantly :/
[19:39] <ikonia> aloon: telling you the correct channel, is nothing to do with maverick users "not being part of the channel" it's actually helping users to the correct channel
[19:41] <aloon> I had everything working perfect , not easy on a sony vaio F111. Anyhow after getting Nvidia and all sound , brightness issues dealt with the update manager had a bunch of stuff and I let it do its thing. Now when I go to install any software it gives errors when it comes to the kernel.
[19:41] <aloon> ikonia thanks I understand
[19:41] <ikonia> what is the error
[19:42] <aloon> ive tried to get rid of any pending failed updates or installs , but even then it gives the kernel errors
[19:42] <ikonia> what is the error
[19:42] <aloon> I can get some , one sec , and thank you
[19:42] <ikonia> please use a pastebin to show us the error
[19:44] <aloon> linux-generic depends on linux-image-generic (=2.6.35.10.11) however package linux-image-generic is not confirmed yet
[19:44] <aloon> thats one of the main ones
[19:45] <ikonia> first thing to do is make sure your cache files are up to date in case the repo has changed, (apt-get update) second thing is to check the other repos to see if that package is released in any of the others et
[19:46] <aloon> it was a two part screw up ... I also installed and used ubuntu tweak to clear my unused kernels , that was after I rebooted after the update and I could see that there was the weird error every time I went to install a program (the program installs , just gives kernel errors at the end)
[19:47] <aloon> I didnt install tweak just to that , but after I had problems I went in there and looked at the kernel and cache section
[19:47] <ikonia> it looks like it's the way tweak clears down the kernels
[19:48] <ikonia> reading a few similar bugs on launchpad
[19:48] <penguin42> forrestv: Prod
[19:49] <aloon> heres what i'm wondering , A: if I can fix the kernel as is in maverick , B: if i should reinstall maverick , get everything back but then not update headers and kernel (wait and research how to do it) , C: go back to Lucid
[19:49] <daedalus96> hey
[19:49] <daedalus96> i am trying to boot the live dvd for 10.10, but it won't load, i can get into the grub command line, does anyone now how i can get from there?
[19:49] <penguin42> daedalus96: There are a few known problems
[19:50] <daedalus96> i am trying to boot the live dvd for 10.10, but it won't load, i can get into the grub command line, does anyone now how i can get from there?
[19:50] <daedalus96> mhm
[19:50] <aloon> did you go into bios and enable boot from cd/dvd ?
[19:50] <penguin42> daedalus96: There are a couple of lines in the grub line like load_video and set gfx something, try editing those out
[19:50] <daedalus96> yes
[19:50] <daedalus96> w8
[19:50] <daedalus96> let me explain better
[19:50] <daedalus96> when i turn on my computer
[19:51] <ikonia> I thought the livecd was built on lilo, not grub
[19:51] <daedalus96> it skips the optical boot, and trys to load ubuntu (which is broken), and i press escape
[19:51] <ikonia> daedalus96: ok, so the cd is probably not bootable
[19:52] <daedalus96> taking me to a screen to choose which kernel to load
[19:52] <daedalus96> i can i change it to be?
[19:52] <penguin42> oh, if it's skipping the optical boot - hmm, I'd try and mount the CD on another system and see if it's ok
[19:52] <ikonia> daedalus96: if it's skipping the boot, then the CD is probably broke
[19:52] <daedalus96> it is
[19:52] <daedalus96> i tried it
[19:52] <aloon> ikonia , sorry to bug , which would you personally do ? fix kernel problem , reinstall maverick or go back to Lucid..
[19:52] <daedalus96> you mean to boot it from another comp, or is the files are there?
[19:52] <penguin42> daedalus96: Does it boot on other systems ?
[19:52] <penguin42> daedalus96: Both questions
[19:53] <daedalus96> give me a sec
[19:53] <daedalus96> i will join after i try it
[19:53] <daedalus96> it has files, but idk if it boots
[19:53] <ikonia> aloon: if your not confident with running a development version that changes and break, use lucid, if you are, search launchpad for bugs similar, there are quite a few with different fixes
[19:53] <daedalus96> cya soon
[19:53] <ikonia> ironic part message
[19:53] <ikonia> it skips the DVD boot and he's wondering why it's not booting
[19:55] <aloon> ikonia heres a very typical error that i've been getting:  http://paste.ubuntu.com/468561/
[19:56] <ikonia> aloon: yes, and I've offered you suggestions/info
[19:56] <aloon> ive been reading/writing
[19:56] <ikonia> http://paste.ubuntu.com/468561/
[19:56] <aloon> following
[19:56] <ikonia> oops
[19:56] <ikonia> run-parts: failed to exec /etc/kernel/postinst.d/update-nvidia: Exec format error
[19:56] <ikonia> seems to be a key issue
[19:56] <aloon> sorry having keyboard issues to
[19:56] <aloon> as you can see
[19:57] <ikonia> how did you install the nvidia drivers ?
[19:58] <litropy> peeps, there's something going on with plymouth
[19:58] <aloon> One sec I have to recheck , because the normal ways didnt work , obviously jockey etc didnt , but even the driver off of nvidia didnt work as it had in lucid.
[19:59] <ikonia> aloon: you should not get drivers from nvidia.com
[19:59] <aloon> nvidia-current is what ended up working
[19:59] <litropy> I boot up ... sometimes it just takes forever to switch to the window manager and everything is fine after, but most of the time, I just get a perpetual black screen. Sometimes, I see a garbled version of my splash screen, and that stays there perpetually. Sometimes, I get a notification that VESA is switching to Intel
[19:59] <aloon> http://www.sucka.net/2010/04/how-to-install-nvidia-video-driver-in-10-04-lucid-lynx/
[19:59] <litropy> 's graphics driver (which is a good thing)
[20:00] <aloon> I did those easy steps , under Lucid it was much harder for my 310M nvidia
[20:00] <aloon> but I was just learning about installing drivers in command line init3 etc
[20:01] <yofel> init 3 does nothing special since karmic
[20:01] <aloon> and like you said , not drivers drirect from nvidia site
[20:01] <ikonia> aloon: you're not using lucid though
[20:01] <yofel> actually init 3 didn't do anything special in ubuntu for a long time
[20:01]  * penguin42 reboots
[20:01] <litropy> any ideas would be greatly appreciated. If I can just bypass plymouth for now and be okay, that's fine, too
[20:02] <ikonia> aloon: why are you using a development version that changes if you are not confortable with running the OS at the moment ?
[20:02] <aloon> okay cool , was just covering bases , closing GDM was a breaktrhough when I realized jockey was not going to work with any driver
[20:02] <yofel> litropy: did you try to change the gfxpayload setting already? (first check dmesg for errors though)
[20:02] <daedalus96> hey
[20:02] <daedalus96> the live  dvd booted on this system
[20:02] <ikonia> daedalus96: you have a problem drive then
[20:03] <yofel> aloon: and how did jockey fail?
[20:03] <daedalus96> and an older live cd boots on the target system
[20:03] <aloon> sony vaio f111 , its i7 core laptop thats really nice , many things were not working under Lucid , keyboard backlight , hdmi sound , wireless had bugs , plymouth was ugly and low res ,
[20:03] <aloon> many of those things worked off the batt under maverick
[20:03] <ikonia> daedalus96: your using a DVD, has the system got a DVD drive ?
[20:03] <litropy> yofel, I like the sound of what you're saying, but I'm not educated enough to understand it fully. No, I haven't changed a gfxpayload setting, and where do I find dmesg log entries?
[20:03] <daedalus96> i believe it does
[20:04] <yofel> litropy: for dmesg, open a terminal and run 'dmesg' you'll get the current kernel log
[20:04] <aloon> jockey would always install the driver but then when you go to use desktop effects it would search for the driver and say no
[20:05] <yofel> odd
[20:05] <aloon> since lucid kockey has not worked for me on ATI or NVidia. I have to install with gdm stopped in command-line
[20:05] <litropy> yofel, what am I looking for in dmesg's output?
[20:05] <aloon> maybe its just the machines ive been running
[20:06] <aloon> but i read lots and lots of similar stories
[20:06] <yofel> litropy: can you pastebin it? pastebinit would be easiest if you could install it, after that, just run 'dmesg | pastebinit' and give me the link
[20:07] <litropy> yofel, now installing pbinit
[20:07] <forrestv> penguin42, hi
[20:08] <penguin42> forrestv: Thanks for the tip about unclutter
[20:08] <litropy> yofel, http://pastebin.com/SpHPdHM0
[20:08] <daedalus96> i am just going to reinstall teh system
[20:09] <litropy> yofel, keep in mind this has been run after a _successful_ bootup, not during the problem. In which I can't run anything.
[20:10] <yofel> well, seems like it successfully switched framebuffers here '[   24.464347] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver'
[20:12] <yofel> litropy: well, debugging boot if you can't do anything can be hard, so for now add 'GRUB_GFXPAYLOAD_LINUX=text' in a new line in /etc/default/grub, run 'sudo update-grub' and see if it helps
[20:14] <litropy> yofel, yes -- that's precisely the message. If I don't see that, _usually_ it doesn't work. But I have to hold [enter] to see it usually. Now adding/updating grub
[20:14] <penguin42> ok, quick survey - who has got the 'unclutter' package installed (but didn't manually do it)
[20:18] <penguin42> it doesn't seem to have got installed on this upgrade but has on my other box
[20:18]  * charlie-tca don't have it in xubuntu
[20:19]  * penguin42 wonders if it was a dependency in an earlier Alpha and has now gone
[20:21] <litropy> yofel, thank you -- that worked like a charm. Now, I'm curious -- what did that do? switch to text mode, which doesn't require a gfx driver?
[20:21] <vish> penguin42: it was installed since sabdfl requested it
[20:21] <vish> penguin42: it should be removed now , it was unseeded
[20:22] <penguin42> vish: Ah good; it was causing chaos
[20:22] <yofel> litropy: no, until now, the kernel always started in text mode, which had the problem that pylmouth looks horrible with ati/nvidia and some other drivers as they don't provide a drm framebuffer
[20:23] <yofel> litropy: we now try to fix that and cjwatson changed grub so the kernel starts in graphics mode, but some (or all) of the drm framebuffer don't like it and the driver crashes
[20:23] <yofel> litropy: the line I gave you makes the kernel start in text mode again
[20:23] <vish> penguin42: it was for a bug to solve the "hide pointer when user is typing" but it had more problems and didnt really solve anything..
[20:24] <penguin42> vish: Yeh 605829 and 61105 in my case
[20:25] <penguin42> hmm bug-buddy complaining it can't trace a stack - I guess with the ptrace stuff that's expected?
[20:26] <litropy> yofel, thank you for such a verbose description!Sounds like I'm getting my info straight from the source.
[20:27] <penguin42> mango-lassi seems to die at startup, pity I was hoping to replace synergy
[20:29] <yofel> litropy: maybe you're interested in the original notification about this https://lists.ubuntu.com/archives/ubuntu-devel/2010-July/030995.html
[20:32] <forrestv> penguin42, you're welcome ... i'm much happier now that it's fixed for me
[20:32] <penguin42> forrestv: Mine is happier; but I'm getting wildly flickering graphics
[20:34] <litropy> Thank you, yofel -- I truly appreciate it; I now know what to follow. Peeps, I have another one for ya: basically, I can't install libvirtodbc0: http://pastebin.com/Rtn1Ars0
[20:34] <penguin42> forrestv: It was ok on lucid but I was running xorg-edgers on there, I'm running a straight maverick on it now; I might try edgers I guess
[20:34] <litropy> whoops wrong link
[20:36] <litropy> her we go: http://pastebin.com/Rtn1ArS0
[20:37] <yofel> litropy: remove virtuoso-nepomuk first
[20:37] <yofel> libvirtodbc0 is missing a conflict on virtuoso-nepomuk
[20:38] <yofel> litropy: if apt refuses to do so, try 'sudo dpkg --force-depends --remove virtuoso-nepomuk' (which will ignore dependencies)
[20:39] <litropy> yofel, the former line ran successfully; now trying again.
[20:41] <litropy> yofel, success; thanks again! you guys are doing great work over there.
[20:47] <litropy> yofel, might the drm framebuffer error be graphics card specific? I'm running a dual core Intel Atom N280 (graphics card included with CPU)
[20:48] <yofel> not sure, I have an eeePC 1000H with intel graphics and that didn't work really well in graphics mode either
[20:48] <yofel> it's more the graphics driver
[20:49] <litropy> Yep, eeepc 1005ha pux
[20:49] <yofel> (or probably the kernel drm code I think)
[20:49] <litropy> what does drm stand for here?
[20:50] <yofel> no idea actually, didn't look into this too much until it broke ^^
[20:50] <litropy> direct rendering manager, yofel
[20:50] <yofel> ah, thanks :D
[20:53] <litropy> yofel, "The Direct Rendering Manager (DRM) is a component of the Direct Rendering Infrastructure, a system to provide efficient video acceleration (especially 3D rendering) on Unix-like operating systems ... It consists of two in-kernel drivers (realized as kernel modules on Linux), a generic drm  driver, and another which has specific support for the video hardware. This pair of drivers...
[20:53] <litropy> ...allows a userspace client direct access to the video hardware."
[20:53] <litropy> http://en.wikipedia.org/wiki/Direct_Rendering_Manager
[20:58] <litropy> If the drm successfully switches from VESA to Intel's, everyhting is fine. But if the framebuffer problem happens before the switch, the system hangs. So it sounds like if it's the driver that causes the problem, it's VESA's. Yet, on my other partition, I use a VESA driver just fine.
[20:58] <litropy> that is, even past bootup, I'm using a VESA driver.
[21:00] <litropy> but what do I know :P
[21:07] <litropy> Do I really need all these kernels? I know how to remove them from Grub's menu, but with every grub update, they of course come back. And they're taking up space on my hd
[21:08] <kklimonda> you can uninstall all but the most recent
[21:09] <Melodist> with synaptic
[21:10] <litropy> ty
[21:33] <aloon> For a bunch of reasons I installed maverick , I have a new sony vaio i7 core with 310M nividia and under Lucid there was a dozen things to fix like fn keys , VT , brightness etc etc , under Maverick most of the problems are solved (hdmi sound included) ... but last install I got Nvidia working perfect and then right away there was a linux headers and kernel update , after the update I started getting compiling errors ever time I installed a program
[21:34] <kklimonda> what compilation errors, what program?
[21:34] <penguin42> aloon: I'm not an nvidia user, but often driver stuff comes along later in the beta cycle
[21:35] <aloon> So now I reinstalled maverick and update manager wants to update headers & kernels in the first update , this time I havent installed nvidia yet , should I update kernel and headers ?
[21:35] <aloon> and then install nvidia ?
[21:36] <penguin42> worth keeping the kernel up to date
[21:36] <kklimonda> I use nvidia just fine with the most recent kernel
[21:36] <aloon> I think the problem was putting in the driver and then updating kernel right after
[21:37] <aloon> i'll try it kernel first this time
[21:39] <aloon> I alwyas struggled with ATI but always got it working , then I switched to nvidia which always was easy , but lately the newest laptop nvidia cards are not well supported and its a hairpulling experience getting everything setup
[21:40] <aloon> it's updating linux-image-generic
[21:41] <aloon> no errors
[21:42] <aloon> for some reason it seems that you have to put a script in usr to have the nvidia driver recompile the kernel properly when it gets updated. I wish it was easy like the old days
[21:45] <kklimonda> you don't have to - all you have to do is install nvidia from package
[21:47] <aloon> from synaptic ?
[21:47] <kklimonda> yeah
[21:48] <aloon> this is how I did it the last time and it worked , on Lucid I could not install nvidia via synaptic , the driver would be activated , but not work
[21:49] <aloon> on maverick nouveau driver actually looked decent on my laptop , but i wanted the features of my nvidia card , it seems nvidia-current does work for me under maverick
[21:49] <aloon> if the nvidia driver is installed through repositories , are you saying that it will update fine even if the kernel and headers are updated ?
[21:50] <aloon> if so , thats great news , i've spent weeks trying to get things going under Lucid
[22:48] <Daekdroom> I didn't know it was so *easy* to help translate ubuntu D:
[22:50] <penguin42> well, as someone who knows one language (and not particularly well) that's easy for you to say!
[22:51] <Daekdroom> penguin42, >.>