[12:51] <Wamty> how can i check if my vga is installed properly on ubuntu?
[12:53] <ToHellWithGA> Wamty: in gutsy or feisty?
[12:53] <ToHellWithGA> and by vga, do you mean video card driver or framebuffer mode?
[12:53] <crimsun> easy.  Can you see anything via the video output? :)
[01:47] <ToHellWithGA> .me doesn't think Wamty wanted to be helped
[03:04] <err_> hi
[03:04] <err_> anyone around?
[03:08] <DanaG> My onboard audio device still doesn't have working input, but at least my offboard sound card DOES have working input.
[03:10] <DanaG> Oh, and PulseAudio insists on using Mic, not Line as I have set it.
[03:11] <DanaG> How I'm testing it:  parec -r -d alsa_input.pci_1102_8_alsa_capture_0 | parec -p
[03:42] <DanaG> I wonder why it still doesn't work.... (not complaining, just curious how it got marked as fixed.)
[03:45] <DanaG> Odd, on my laptop, fn-super is ctrl-alt-del.
[03:47] <DanaG> Argh, why does the SSH client just LOCK UP when the connection dies?
[03:47] <DanaG> The SSH client should EXIT, or at least, unblock ctrl-c.
[04:22] <DanaG> (snd_pcm_open_conf) type is not defined
[04:23] <DanaG> with aplay -v (due to my .asoundrc.)
[04:23] <DanaG> But I can't figure out what line is causing the error.
[04:26] <DanaG> ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'defaults.pcm.dmix.device'
[04:29] <DanaG> aah:  Unknown PCM default
[04:30] <DanaG> Looks like perhaps the !defaults needs to be changed to !default
[04:35] <DanaG> aah, fixed it.
[04:35] <RAOF> Yay!
[04:38] <Pumpernickel> props
[04:38] <DanaG> pulseaudio: modules/module-alsa-sink.c:193: do_write: Assertion `(memchunk->length % u->frame_size) == 0' failed.
[04:38] <DanaG> Also, I had to remove my overriding default to my dmix96 thingy.
[04:38] <DanaG> But now I get this message, trying to use my 'route'-type virtual device.
[04:41] <DanaG> AAh, I just removed the custom dmix96.
[04:41] <DanaG> Sweet, now I have pulseaudio AND upmixing with offboard audio!
[04:43] <DanaG> Now I just need a feature: load custom sink X when device Y appears.  Oh, and I need a "let go of this device when it's inactive, so I can modprobe -r it."
[04:45] <RAOF> That'd be nice.
[04:45] <RAOF> But doesn't gnome-volume-applet actually hang on to the device indefinately?
[04:46] <DanaG> I have the applet set to use my onboard sound card, which is always present.
[04:46] <DanaG> It's wonderful having pulseaudio --- I put system audio to the onboard speakers, and music to the offboard if it is present.
[04:47] <DanaG> Then, if something decides to be annoying on onboard, I just hit mute.
[04:47] <RAOF> Oooh, that's cool.
[04:48] <DanaG> I also manually set /etc/modprobe.d/alsa-base to always give hda-intel index 0 and emu10k1 index 1.
[07:20] <DanaG> bye.
[07:33] <LordLimecat> gutsy is/will be LTS, right
[07:33] <crimsun> no, gutsy+1.
[07:34] <LordLimecat> oh
[07:34] <LordLimecat> .....no name yet?
[07:34] <crimsun> ...that's why it's known as gutsy+1.
[07:35] <crimsun> (the name of the proceeding devel branch isn't known until the week of the current devel release, normally)
[07:35] <LordLimecat> 2 more questions
[07:35] <LordLimecat> 1) what letter will it be?  isnt H taken by 5.10?
[07:35] <LordLimecat> or no clue yet?
[07:35] <crimsun> 1) see above, 2) does it matter? (no)
[07:35] <LordLimecat> lol
[07:36] <LordLimecat> just curious, i was always curious as to why they used H for 5.10
[07:36] <LordLimecat> also, more seriously, is there, aside from launchpad, somewhere that lists the major goals for gutsy?
[07:36] <crimsun> no.
[07:36] <LordLimecat> alright, thanks :)
[07:40] <LordLimecat> *drools* bulletproof x :D
[09:29] <Quinn_Storm> I830WaitLpRing is to me like 'pc load letter' was to the Office Space crew
[09:35] <Quinn_Storm> I'm running away for now...maybe in a few months I'll play more with gutsy, but this hardware is just too unreliable with it
[09:39] <dawn_chorus> eh?
[09:41] <dawn_chorus> so there'll be a fluxbuntu flavor of Gutsy?
[10:59] <johnnybuoy> hi all!
[11:00] <johnnybuoy> what is default infrastructure for laptops in gutsy?
[11:00] <crimsun> would you rephrase, please?
[11:00] <johnnybuoy> I have been using powersaved since I installed feisty when it was still in developement, but it seems it is not maintained anymore
[11:00] <johnnybuoy> ??
[11:00] <johnnybuoy> well, okay
[11:01] <johnnybuoy> so, i am interested in knowing what the default set of tools and packages is in gutsy because it seems to me that powersaved is not being maintained
[11:02] <crimsun> powermanagement-interface, powermgmt-base, powernowd
[11:02] <RAOF> Gnome-power-manager, laptop-mode, powernowd?
[11:02] <crimsun> this is all via ubuntu-desktop and acpi-support
[11:02] <johnnybuoy> okay
[11:02] <crimsun> the former should cover everything
[11:02] <johnnybuoy> so I just uninstall powersaved and if I have ubuntu-desktop installed it should work?
[11:03] <crimsun> if you install ubuntu-desktop, it will remove powersaved.
[11:03] <johnnybuoy> no it won't
[11:03] <crimsun> since powersaved Conflicts powernowd
[11:04] <johnnybuoy> I know for a fact it won't as I have both powersaved and ubuntu-desktop installed here
[11:04] <johnnybuoy> powersaved:
[11:04] <johnnybuoy>   Installed: 0.14.0-7ubuntu1
[11:04] <crimsun> that's because powernowd is a Recommends.
[11:04] <johnnybuoy> ubuntu-desktop:
[11:04] <johnnybuoy>   Installed: 1.44
[11:04] <johnnybuoy> I don't want powernowd actually
[11:05] <crimsun> ...
[11:05] <RAOF> Why not?
[11:05] <johnnybuoy> I don't need it, I use conservative, whics does the same in kernel mode
[11:05] <johnnybuoy> which
[11:05] <crimsun> then why does it even matter?  why did you ask?
[11:06] <johnnybuoy> well, except for powernowd I could use the default utils in ubuntu
[11:06] <crimsun> ok, then do so
[11:06] <johnnybuoy> I was just wondering if something new emerged
[11:07] <crimsun> if something drastic appears, you should read about it on -devel{,-announce} or -changes
[11:07] <johnnybuoy> okay, I need to subscribe to one of those
[11:07] <johnnybuoy> oki doc'
[11:07] <johnnybuoy> thx
[11:08] <crimsun> ...you run gutsy without reading any of the three?
[11:08] <johnnybuoy> yes
[11:08] <crimsun> you don't even have to sub, just read consistently
[11:08] <johnnybuoy> ?-)
[11:10] <johnnybuoy> I don't know why, but my battery is being detected as doing only 2:30 hours, and that doesn't change one bit. it's as if it were a countdown timer while my battery has 6 hours in it
[11:12] <johnnybuoy> I have no idea where the bug could be, which is why I want to try to uninstall powersaved
[11:12] <johnnybuoy> the /proc/acpi interface shows the rate and the capacity right
[11:13] <RAOF> johnnybuoy: Anything like http://ubuntuforums.org/showpost.php?p=2796459&postcount=3
[11:14] <johnnybuoy> well, does it matter if I answer?
[11:14] <johnnybuoy> yes, it definitely is that problem
[11:17] <Enverex> lol, not a good start for Tribe 1. If you select Log Off from the Gnome menu now X freezes
[11:18] <johnnybuoy> it doesn't freeze
[11:18] <johnnybuoy> wait a few minutes and the logout dialog will appear
[11:18] <johnnybuoy> ( at least that's what happens here )
[11:18] <johnnybuoy> and it definitely does look as if X was frozen
[11:22] <crimsun> that was fixed in gnome-session_2.19.2-0ubuntu2
[11:22] <johnnybuoy> ah
[11:22] <crimsun>   * debian/patches/11_session_dialog.patch:
[11:22] <crimsun>     - updated GPM_DBUS_SERVICE, GPM_DBUS_PATH and GPM_DBUS_INTERFACE. That
[11:22] <crimsun>       fixes the 30 seconds wait for the gnome session logout dialog.
[11:25] <Enverex> johnnybuoy, Ah, never thought about waiting a few minutes (normally in a hurry)
[11:26] <johnnybuoy> but if you update your system it will go away
[11:41] <Enverex> My laptop is up to date, just rebooted and the only updates available are for OpenOffice
[11:42] <johnnybuoy> hmm
[11:42] <johnnybuoy> and do you still get the same behaviour?
[11:50] <Enverex> Yup
[11:52] <johnnybuoy> well, that's strange
[11:52] <johnnybuoy> and does the dialog appear after a while?
[11:53] <johnnybuoy> Enverex: ^^
[11:53] <Enverex> johnnybuoy, Lets see
[11:55] <Enverex> Yeah, eventually
[11:56] <johnnybuoy> hm
[11:56] <johnnybuoy> then it prolly is the same bug
[11:56] <johnnybuoy> that should've been fixed
[11:56] <johnnybuoy> (it's fixed here)
[11:57] <johnnybuoy> what mirror you using?
[11:59] <johnnybuoy> Enverex:
[12:33] <mikkael> i see people talking about a live cd, is it released yet ?
[12:35] <gnomefreak> mikkael: no they are testing the ISO's atm
[12:36] <mikkael> so no public access to a iso ?
[12:36] <mikkael> i would like to test it on 2 machines
[12:36] <gnomefreak> mikkael: wait a few hours a day tops if no issues are found to stop it
[12:37] <mikkael> ok
[12:37] <gnomefreak> https://isotesting.stgraber.org/  but dont be suprised if they dont work
[12:37] <mikkael> that bad ?
[12:38] <gnomefreak> mikkael: they are testing before they release the images
[12:38] <gnomefreak> mikkael: so yes it can be that bad
[12:39] <mikkael> yes in know the process, i participated in feisty final release iso testing
[12:39] <mikkael> (a bit) ;)
[12:40] <gnomefreak> final release ISOs are nothing like what you will find now
[12:41] <mikkael> i can imagine
[01:39] <DexterF> hi
[01:40] <DexterF> .bash_aliases in konsole is not parsed here. are functions allowed in there?
[04:46] <mikkael> did you recently change the "to test" iso ?
[04:47] <mikkael> because every status is at 0 again..
[04:48] <mikkael> i need to know if i should report my results now, but not sure if i tested the correct iso
[04:48] <Hobbsee> mikkael: report any bugs you have with it, it's released now
[04:49] <mikkael> is it the same as 0606 daily ?
[04:49] <Hobbsee> .1, i think
[04:49] <Hobbsee> depending on which flavour
[04:49] <mikkael> i will compare md5 sum of the iso i used to the one thats available to download..
[04:50] <Hobbsee> that's a smart idea
[04:50] <gnomefreak> https://wiki.ubuntu.com/GutsyGibbon/Tribe1?highlight=%281%29%7C%28tribe%29%7C%28gutsy%29
[04:50] <mikkael> what was the shell command to get the md5 sum of a file again ;) ?
[04:50] <gnomefreak> http://cdimage.ubuntu.com/releases/gutsy/tribe-1/
[04:50] <gnomefreak> mikkael: md5sum
[04:51] <mikkael> that easy!
[04:51] <gnomefreak> the last link is the download link
[04:51] <gnomefreak> mikkael: md5sum file.iso
[04:51] <gnomefreak> replace file with the name
[04:52] <mikkael> yeah its the same
[04:52] <mikkael> thank you
[04:54] <gnomefreak> mikkael: the isos for daily on wed. should have been same (or whenever we froze give or take a day
[04:58] <Hobbsee> gnomefreak: really, it's "whenever it's done, there are no tribe# milestoned bugs outstanding, and we've got the tests done to release"
[04:58] <mikkael> would be cool if someone could check if i reported properly :)
[04:58] <mikkael> https://isotesting.stgraber.org/isotesting/test/59
[05:01] <Hobbsee> mikkael: you might want to file a bug on https://isotesting.stgraber.org/isotesting/result/59/3 stuff, if you can get relevant logs
[05:01] <Hobbsee> as in, people will only look at the attached bugs, and the numbers of "done"'s
[05:02] <mikkael> is there a chance that there are logs saved somewhere at the moment or is it needed to reproduce it ?
[05:02] <Toma-> <3 displayconfig
[05:03] <mikkael> talking about logs of the not-successfull live sessions ?
[05:13] <Enverex> Ok, amazed that ia32-libs STILL hasn't been fixed...
[05:16] <bipolar> I guess since the first alpha CD is out, I should upgrade from feisty :)
[05:16] <bipolar> like I did from edgy
[05:17] <bipolar> and dapper, come to think of it....
[05:17] <mikkael> well i cant find any logs of those failed live session boot ups, and i have no idea how i could my hands on those logs when im reproducing
[05:18] <mikkael> i mean it doesnt touch the disk, so how can i post a log :) ?
[05:18] <mikkael> ill move on to another image
[05:24] <bipolar> mikkael: serial port to another box. redirect the console to that :)
[05:24] <Hobbsee> he's gone
[05:26] <DanaG> Argh, every time Nautilus starts the desktop, it also opens my home dir in a window.
[05:28] <DanaG> Oh, and also, my snd-hda-intel master mixer often goes to highest volume.
[05:28] <DanaG> At boot, I mean.
[05:30] <bipolar> 921 packages upgraded, 100 newly installed, 11 to remove and 9 not upgraded.
[05:30] <bipolar> Need to get 912MB of archives. After unpacking 374MB will be used
[05:31] <bipolar> wow.... :)
[05:33] <bipolar> libqt3-mt 3:3.3.8really3.3.7-0ubuntu7  < heheh....
[05:34] <DanaG> Perhaps that's so they can upgrade later to really lower version numbers.
[05:34] <bipolar> strange :)
[05:34] <bipolar> development repos are always fun like that
[05:36] <Hobbsee> teh later libqt3-mt was really stuffed
[05:36] <Hobbsee> bipolar: DanaG so we reverted
[05:38] <DanaG> Oh, I see, I thought it said 3.3.3.8 really 3.3.7
[05:38] <bipolar> Hobbsee: ahh... cool
[05:39] <andi5> hi... Can't exec "xdvi.bin": No such file or directory at /usr/bin/xdvi line 90. ... may someone tell me whether i am missing something, given that such a dramatic bug would have been reported already, i guess ... thanks for any hint!
[05:56] <DanaG> woah: http://www.theinquirer.net/default.aspx?article=40135
[05:57] <DanaG> http://www.theinquirer.net/default.aspx?article=40132
[05:59] <bipolar> DanaG: indeed. I want one :)
[06:00] <bipolar> although it would have been nice to have a tablet style screen that flips around, since it's a touchscreen.
[06:00] <bipolar> and it's running the wrong OS
[06:05] <bipolar> Fetched 912MB in 26m0s (584kB/s) < not to shabby
[06:08] <DanaG> When I'm on [gigabit]  ethernet in one of the labs at Cal Poly, I can get 7000 kiloBYTES per second from mirrors.kernel.org.
[06:11] <bipolar> DanaG: sweeeet
[07:09] <Hobbsee> hehe
[07:11] <bipolar> lolz
[07:12] <geser> Is it safe to upgrade to gutsy?
[07:12] <Hobbsee> geser: define safe.
[07:12] <Hobbsee> geser: you can upload to over half of it, so that's your call.
[07:12] <Hobbsee> if i'ts broken, you fix it.
[07:13] <Hobbsee> :P
[07:14] <geser> I changed to feisty around herd-1. So I'm asking myself if it's time to switch to gutsy.
[07:15] <Hobbsee> yeah, why not.  it mostly works
[07:15] <geser> So there isn't currently something totally broken?
[07:15] <Hobbsee> and where it doesnt, then you have more incentive to fix it :P
[07:15] <Hobbsee> not to my knowledge.  not that badly
[07:16] <geser> I don't mind the occasional breakage, but I try to avoid them.
[07:17] <geser> so I'll probably upgrade to gutsy at the weekend (if nobody breaks it till then)
[07:17] <bipolar> geser: I just upgraded from feisty 10 min ago
[07:18] <bipolar> geser: there were some minor issues on my box caused by 3rd party apps.
[07:18] <bipolar> nothing someone with dpkg experiance can't fix
[07:19] <geser> sounds good
[07:21] <Hobbsee> geser: during freezes should be the most stable
[07:21] <Hobbsee> obviously
[07:22] <geser> perhaps I should upgrade before everyone starts uploading again
[07:23] <Hobbsee> could be smart
[07:23] <Hobbsee> actually, what worries me is a grub transititon
[07:23] <Hobbsee> but i guess a live cd will fix that, as will not upgrading grub
[07:23] <Hobbsee> and i'd imagine that'll be tested outside of the repos first.
[07:35] <geser> are there no lowlatency kernels in gutsy anymore?
[08:10] <dm> http://armory.worldofwarcraft.com/#character-sheet.xml?r=Dalvengyr&n=Suralus
[08:28] <mikkael> should i file a bug on this appearance of the kubuntu installer ? it works, but that progress window is "damaged" http://www.divshare.com/download/868002-55d
[08:29] <mikkael> hmm it gets fixed if i resize it :)
[08:50] <The-Compiler> Hi there
[08:51] <The-Compiler> I try to use the Kubuntu Gutsy live-cd in a VM. The CD boots, then I get the error "process for the file transfer broken" (or so). Any ideas? (PS: Sorry for my bad english, I'm swiss)
[08:51] <DexterF> hi
[08:52] <DexterF> something set an NFS mount point here to mode 660 root:messagebus, I have no idea what. who makes a good suspect?
[08:53] <DexterF> wow, nvm
[08:53] <DexterF> the shares aren't mounted
[09:04] <akrus`Away> The-Compiler: Gutsy LiveCD???
[09:04] <akrus`Away> ah
[09:04] <akrus`Away> i missed news :)
[09:40] <pvandewyngaerde> how do i upgrade to gutsy gibbon ?
[09:41] <pvandewyngaerde> from kubuntu feisty
[10:18] <SlimG> My wireless nic isn't recognized in gutsy, where do I start when trying to figure out what/where the problem is?