[00:31]  * cwillu can't remember whether he promised to huggle, or to stop huggling, so he huggles dtchen for a few moments and then stops 
[00:32] <dtchen> you promised both depending on my preference
[00:32]  * cwillu awaits dtchen's preference
[00:32] <dtchen> of course by the time you were moaning about it, i had already committed the fix to bzr, as i had typed here
[00:33] <cwillu> sorry, I got the impression you were talking about the race condition exclusively
[00:40] <franta> Hi every one! I don't know if this is the right place, but I'll ask anyway... I've found that Jaunty doesn't recognize my mp3 player, but I don't know where to report that...
[00:42] <maco> franta: what do you mean doesnt recognize? and what kind is it?
[00:44] <_VIM_> Hi, what file(S) do I need for guest Addtions in Virtualbox? I know it's some header dev package or something...I have the KDE jaunty.
[00:44] <franta> maco: it's sansa e270 and lsusb shows it , but it doesn't get an entry in /dev .. like /dev/sdx1 or something... wonder if it's because I'm running Jaunty on an external disk...
[00:46] <dtchen> franta: Sansas normally have a hardware toggle between MTP and UMS
[00:46] <franta> maco: I have kubuntu, but I don't think that matters...
[00:46] <dtchen> s/UMS/MSC/ depending on the context
[00:47] <franta> dtchen: yes, I know... there's MTP and MCU or something like that... I have it set so it acts as mass storage...
[00:47] <franta> I'm on Hardy now and it works..
[00:49] <dtchen> franta: that's odd; hal-info has a specific quirk for your Sansa e270
[00:49] <dtchen> (obviously, it *should* work0
[00:49] <dtchen> )
[00:49] <franta> dtchen: I think it's because I'm booting from usb hdd...
[00:49] <franta> but flash drive works...
[00:57] <_VIM_> Hi, what file(S) do I need for guest Addtions in Virtualbox? I know it's some header dev package or something...I have the KDE jaunty.
[01:05] <franta> _VIM_: isn't it included?
[01:05] <_VIM_> I guess not :(
[01:05] <_VIM_> cant get it to install
[01:06] <cwillu> _VIM_, you can use the download from virtualbox's site (afaict, virtualbox-ose-guest-utils doesn't include the windows guest utils).  It's just a matter of dumping the file in the location it's expecting, which is documented in the man pages
[01:06] <_VIM_> somthing bout "kernel config is invalid..."
[01:06] <_VIM_> no i'ts a not a windows guest
[01:07] <_VIM_> it's a KDE Jaunty guest
[01:08] <cwillu> !info linux-headers
[01:08] <cwillu> !info linux-headers-generic
[01:08] <_VIM_> i installed that
[01:09] <cwillu> no idea then, sorry
[01:09] <_VIM_> np thanks anyways :)
[01:34] <FFForever> dtchen, you around?
[01:36] <FFForever2> sorry my wifi died are u around?
[01:41] <cwillu> maco, sorry, just saw your pm now
[01:42] <FFForever2> can someone anyone help me get my mic working, i was talking with dtchen about a week and a half ago and he said something about alsa that ships with ubuntu 9.04 does not have the patch i need for my mic =\
[01:43] <FFForever> i have a hp 6810us
[01:46] <FFForever> please someone...
[02:04] <nblracer> what is cca?
[02:47] <FFForever> Anyone wanna help me fix meh mic?
[02:49] <charlie-tca> Probably many want to, but do not know how, FFForever
[02:49] <FFForever> i have searched but no one seems 2 know how =(
[02:50] <maco> FFForever: has it ever worked in ubuntu?
[02:50] <FFForever> maco, nope =(
[02:50] <maco> alsa-info.sh link?
[02:51] <maco> and have you filed a bug?
[02:51] <FFForever> maco, that url is invalid for me =(
[02:52] <FFForever> and i didn't file a bug because no one ever responds 2 them =(
[02:56] <blizzle> Hello. I'm trying to get a TNT2 working in Jaunty with Nvidia's drivers. Jockey doesn't appear to see anything available, I've epically failed at downloading nvidia's .run package.. any pointers?
[02:56] <RAOF> blizzle: Whee! Old-skool.
[02:56] <blizzle> RAOF: Yeah, it's a tad ancient!
[02:56] <RAOF> blizzle: You'll need to be using the nvidia-glx-96 series drivers.  I'm not sure if they actually work with Jaunty's Xserver yet, though.
[02:57] <blizzle> RAOF: From what I've read, I need the glx-71 series.
[02:57] <RAOF> That's entirely possible.  It's been some time since I had a TNT2 :)
[02:57] <maco> FFForever: haha sure we respond. dtchen goes through a *lot* of sound bugs
[02:58] <maco> FFForever: and i was asking you for the link supplied by downloading and running http://alsa-project.org/alsa-info.sh
[02:58] <blizzle> RAOF: So I should give up, then, and forget accelerated 3d for now? :/
[02:59] <FFForever> maco, ahhh whoops .sh is also a tld...
[02:59] <maco> for what country? O_o
[02:59] <RAOF> blizzle: It looks like the nvidia-glx-71 package should be installable, at least.
[03:00] <blizzle> RAOF: It is, and I have. Doesn't seem to help things much, though.. what am I missing?
[03:00] <FFForever> http://www.alsa-project.org/db/?f=7bee1d7350cbe77d1d1cb1a6fbe03e7c689e029c
[03:00] <blizzle> RAOF: I mean, Jockey should pick up the driver and offer to enable it, no?
[03:00] <RAOF> blizzle: Do you have it specified in xorg.conf?
[03:01] <maco> FFForever: looking
[03:01] <RAOF> blizzle: I would think so, yes.  Do you have the nvidia-71-modaliases package installed?  That's how jockey works out whether your card is supported.
[03:01] <FFForever> maco thanks
[03:02] <blizzle> RAOF: Nothing at all in xorg.conf, and yes, all -71 related packages are installed, including source.
[03:03] <RAOF> blizzle: running 'sudo nvidia-xconfig' should set your driver to the nvidia binary.  I'm not sure why jockey isn't seeing the driver (and suspect it means that the driver doesn't officially support our Xserver)
[03:04] <maco> FFForever: is the mic recognized as a capture device?
[03:05] <FFForever> maco how do i check?, i went though audacity (launched as root) and tried each "device" and none of them was picking up sound
[03:05] <blizzle> RAOF: Command not found on nvidia-xconfig
[03:06] <RAOF> Well, that's rather stupid.  That command was introduced in 96, it seems.
[03:06] <RAOF> blizzle: Basically you want to have Driver "nvidia" in you Device section.
[03:06] <blizzle> RAOF: I heard that support for legacy hardware was removed in Intrepid.. would that have any bearing on the issue.. and do I need to install -96?
[03:07] <crdlb> I believe there's a separate nvidia-xconfig package for -71
[03:07] <maco> FFForever: padsp audacity
[03:07] <blizzle> crdlb, Oh? Where would I find it.. it's not coming up.
[03:08] <RAOF> blizzle: Nvidia has been progressively stripping legacy support out of its new drivers, yes (to the point where we now have *four* nvidia drivers in the archive).  But the -71 driver will still drive your TNT2
[03:08] <maco> FFForever: that should route audacity through pulse. see what happens.
[03:08] <crdlb> I guess somebody removed it in jaunty
[03:09] <FFForever> maco uhhh =(
[03:09] <maco> FFForever: dtchen's got the same sound as you in his laptop and he says the mic is detected, but it's not getting recorded, so try that way
[03:09] <blizzle> RAOF: I'm pessimistically optimistic :)
[03:09] <crdlb> the intrepid package looks a bit broken (it conflicts against nvidia-glx and nvidia-glx-new instead of the new numbered pkgs)
[03:09] <maco> FFForever: what?
[03:09] <FFForever> maco now i have no devices listed
[03:09] <maco> FFForever: do you have pulseaudio running?
[03:09] <FFForever> i think?
[03:09] <FFForever> i hear sound?
[03:09] <maco> ps -ef | grep pulse
[03:10] <FFForever> yeah =)
[03:10] <maco> pasuspender -- audacity
[03:10] <maco> what then?
[03:11] <FFForever> maco should i relaunch audacity first?
[03:11] <maco> yes
[03:11] <maco> kill all running audacities
[03:11] <maco> then do that
[03:12] <FFForever> maco nope =(
[03:12] <maco> FFForever: test this: arecord -Dplughw:0
[03:13] <FFForever> ���������������������������������
[03:13] <maco> ...
[03:13] <maco> what?
[03:13] <FFForever> that is what it keeps outputting
[03:13] <FFForever> (into my terminal)
[03:13] <maco> oh
[03:13] <maco> wait are we talking about a mic jack or one that's on the screen?
[03:14] <FFForever> the one right above the screen =)
[03:14] <maco> since you have internal and external mic listed along with doc mic
[03:14] <FFForever> i want to use the one that is right above the screen (internal)
[03:14] <maco> if you tap the screen or speak loudly into the mic does the output change?
[03:14] <FFForever> well i think its listed as internal but i don't know =(
[03:15] <maco> yes, internal means the screen mic
[03:15] <FFForever> maco just lots of ?...
[03:15] <FFForever> i cant record from audacity =(
[03:15] <maco> the ?'s never change when you make loud noises?
[03:15] <FFForever> nope but they do come in blocks =\
[03:16] <maco> blocks?
[03:16] <FFForever> well yeah like sets of 5-10
[03:16] <maco> do they pause or come faster when you make noises?
[03:16] <FFForever> nope
[03:17] <FFForever> btw the mic works (i tested it in xp)
[03:17] <maco> :(
[03:18] <FFForever> i hate having 2 go into windows to talk on skype =(
[03:19] <maco> FFForever: have you updated in the last 2 hours or so?
[03:20] <FFForever> i think...
[03:20] <maco> can you please check for new updates?
[03:20] <maco> dtchen just put out a bunch of new sound stuff this afternoon
[03:20] <maco> s/put out/uploaded/
[03:21] <FFForever> (i am not using the main mirror but a closer one 2 me should i switch?)
[03:21] <maco> you've got him very confused by the way, since he's got a slightly newer version of the same sound card as you
[03:22] <FFForever> maco i talked 2 him about a week and a half ago and he said something about alsa not having a patch or something like that
[03:22] <maco> haha and now he's grumbling that it stopped working on his when it used to work, so there's a regression for him
[03:23] <FFForever> should i stop the upgrade?
[03:23] <maco> no install the updates anyway
[03:23] <FFForever> kk done
[03:24] <FFForever> do i need 2 reboot?
[03:24] <maco> testing against current usually is most reliable testing
[03:24] <maco> at least log out and back in for the new pulseaudio
[03:24] <maco> if there was a new kernel for you, then yes, reboot
[03:24] <FFForever> kk
[03:24] <FFForever> brb
[03:27] <FFForever> back
[03:29] <maco> FFForever: he just grabbed my 1/8" plug mic and tested, and he knows what's wrong. external mic works fine. internal is broken because 1 of the pins is reversed in the kernel.
[03:29] <maco> he said he'll fix it in a bit
[03:29] <maco> in the meantime he says if you have a plugin mic, that should work
[03:30] <FFForever> maco no external mic for me =(
[03:30] <FFForever> can you please ask him when i should be expecting a patch in the repo (tmw, a week, etc)
[03:30] <dtchen> (i'm right here, so you don't need to relay)
[03:31] <maco> oh youre online now
[03:31] <FFForever> ahhh cool
[03:31] <dtchen> FFForever: with the next kernel upload, hopefully, but no guarantees - really depends on free time
[03:32] <FFForever> dtchen, so in about a week?
[03:32] <dtchen> FFForever: perhaps, probably more likely to be a couple weeks
[03:33] <FFForever> cool ive waited since 8.04 so a little longer won't hurt
[03:34] <FFForever> dtchen, thanks for all of your help and time
[03:39] <JesperHansen> wth is wrong with the terminal in jaunty? I am having a hard time selecting any text and if I do it gets pasted automatically to the command line. What is this for a kind of behavior :O
[03:40] <maco> JesperHansen: only in the terminal?
[03:42]  * JesperHansen suspects this mousepad left click is bogus
[03:42] <maco> JesperHansen: right. what version of xserver-xorg-input-synaptics are you using?
[03:42] <maco> this sounds like 0.99.3-1ubuntu1
[03:43] <JesperHansen> 0.99.3-2ubuntu1
[03:44] <maco> update
[03:44] <maco> 2ubuntu2 is out
[03:44] <maco> brb.
[03:48] <JesperHansen> hmm, still doing it. cat /dev/input/mice makes only one backspace when I press the left click as only one click is detected, but gnome detects multiple
[03:50] <JesperHansen> umm.. ctrl+alt+backspace gone in jauntry?
[03:50] <JesperHansen> -r
[03:51] <maco> yes
[03:51] <maco> by default, disabled, jsut like in upstream Xorg
[03:51] <maco> 1) some people accidentally hit it when they switch workspaces
[03:51] <maco> 2) devs would rather people report bugs in graphics than hit c-a-b and ignore them
[03:52] <maco> you can re-enable it like this http://albertomilone.com/wordpress/?p=335
[03:53] <JesperHansen> Is there btw. some way to make the apport application suck less?
[03:53] <JesperHansen> ie. not requiring people to create an account
[03:53] <JesperHansen> on launchpad
[03:54] <maco> er...if you dont have an lp account, how do you intend to respond to developers' requests for more information?
[03:55] <JesperHansen> Consider comparing it with mozilla firefox's talkback when firefox crashes. The user provides an email if more information should be needed.
[03:55] <FFForever> maco any idea why i have 2 hold a key 2 boot my system when my power cable is not plugged in?
[03:56] <JesperHansen> All of my bug reporting for ubuntu stops when I see I need to login and create an account. Like "pfffft, don't have time to create an account.. Do it later or actually, never"
[03:56] <maco> FFForever: acpi
[03:57] <FFForever> any idea on fixing it?
[03:57] <maco> JesperHansen: or create 1 accout once and never again...
[03:57] <maco> JesperHansen: where does the boot stop?
[03:58] <JesperHansen> maco: did I mention a boot?
[03:58] <maco> JesperHansen: er...that was at FFForever
[03:58] <maco> remembering which person to answer is almost as hard as remembering what language to speak
[03:59] <FFForever> i am lost?
[03:59] <maco> (try studying 2 foreign languages at once. you'll answer people speaking $lang1 in $lang2 and those speaking $lang2 in $lang1, i guarantee it)
[03:59] <FFForever> maco u do it?
[03:59] <maco> FFForever: at what point does booting stop working if you dont hold those keys?
[04:00] <FFForever> i don't even see the loading bar =\
[04:00] <maco> FFForever: turn off usplash and tell me where it stops
[04:00] <maco> it gets past grub, right?
[04:02] <FFForever> maco i see the grub selection menu but after that i get a blank screen, then i hold a key till it finished loading and its all gold
[04:02] <scottywz> can someone help me with a problem opening terminal sessions?
[04:02] <FFForever> and everything is gold if my power is plugged in
[04:03] <maco> FFForever: in grub, edit the boot line to not say "quiet splash"
[04:03] <maco> then watch where it stops when you dont hold a key
[04:04] <maco> or see if maybe it works when you turn off usplash that way
[04:04] <FFForever> maco like this?, quiet           splash
[04:06] <maco> the boot line already says "quiet splash"
[04:06] <maco> delete that and then boot
[04:06] <FFForever> ohhh i added it i was just making sure it was right....
[04:06] <maco> if you dont know, you have to highlight the boot line in grub, hit "e" to edit, go down to the kernel line on that screen, hit "e" to edit that line, then delete those, hit enter, and then "b" to boot
[04:06] <FFForever> ohhh....
[04:06] <FFForever> i was adding it 2 menu.lst....
[04:07] <maco> no no those 2 options are auto-added in menu.lst
[04:07] <FFForever> ahhh
[04:07] <maco> you dont need to touch that file to do a one-time option-edit
[04:07] <maco> grub's interactive
[04:10] <FFForever> ill do it later i need 2 finish this project
[04:11] <maco> ok
[04:15] <scottywz> can somebody please help me with a problem opening terminal sessions?
[04:16] <scottywz> im getting "PTY allocation request failed on channel 0" when I try to ssh into my jaunty box
[04:22] <westyvw> problems with touchpad on asus n20a in jaunty. works with latest sidux. copy xorg.conf for synaptics pad?
[04:22] <westyvw> problem is an understatement, doesnt work at all
[04:25] <westyvw> tell
[04:25] <westyvw> :tell
[06:18] <pwnguin> RAOF: is it possible that nouveau is confusing the font engine somehow?
[06:18] <RAOF> What do you mean?
[06:19] <pwnguin> lemme bring up a screenshot
[06:19] <pwnguin> http://people.cis.ksu.edu/~jld5445/av-kerning.png
[06:19] <RAOF> Corruption, or large fonts?
[06:21] <pwnguin> see the av in the playlist (and elsewhere)?
[06:22] <pwnguin> last time i had bad font problems, it was a dpi thing
[06:23] <pwnguin> but nobody seems to be having this problem but me so perhaps im doing something wrong =/
[06:23] <mjc> pwnguin: xdpyinfo
[06:24] <pwnguin> mjc:
[06:24] <pwnguin> mjc: http://pastebin.com/f6641b62e
[06:24] <mjc> pwnguin: 381x238 millimeters the actual size of your display?
[06:25] <pwnguin> millimeters sound small
[06:25] <pwnguin> lemme translate that first =/
[06:25] <pwnguin> its 14.1 inch widescreen
[06:26] <pwnguin> those dimensions sound about right
[06:27] <pwnguin> actually no
[06:27] <pwnguin> 381 is 15 inches
[06:34] <pwnguin> well, bumping up the dpi does fix it, but kinda tweaks the fonts all over
[06:35] <pwnguin> with the exception of a few kernings, 96 dpi seemed fine
[06:36] <mjc> pwnguin: well your monitor might be misreporting size
[06:36] <mjc> or the ratio is wrong
[06:36] <mjc> can you measure it exactly and find out? use a milimeter ruler from inside edge to inside edge
[06:37] <maco> or do inches * 25.4
[06:37] <mjc> maco: milimeter ruler for accuracy
[06:37] <mjc> not for conversion
[06:37] <mjc> well sorry, s/accuracy/precision/
[06:37] <maco> mjc: might not own a millimeter ruler
[06:37] <mjc> maco: most rules have both on them
[06:38] <maco> then again there are pdf rulers out there
[06:38] <RAOF> pwnguin: It is possible that nouveau is corrupting that.
[06:38] <mjc> pwnguin: it's most likely the monitor misreporting size
[06:38] <mjc> but if not that, then nouveau
[06:43] <pwnguin> sadly, my rulers only go to 1 ft
[06:43] <pwnguin> if you want mm precision, i should just dig up the specs
[06:44] <yossarian> 'lo peeps
[06:45] <yossarian> so i shouldn't endeavour to install jaunty jackalope on ext4?
[06:45] <pwnguin> why not?
[06:47] <maco> might lose data
[06:47]  * pwnguin has been using ext4 for a few weeks now
[06:48] <yossarian> how safe is it?
[06:48] <yossarian> and how long 'til it's 'usable'?
[06:54] <crdlb> a filesystem is just not something you experiment with
[06:54] <pwnguin> sure it is
[06:54] <yossarian> :(
[06:54] <crdlb> I like to be in at least the bottom 90% on things like that
[06:54] <pwnguin> there's a tradeoff in filesystems
[06:55] <pwnguin> new features versus testing and bugs
[06:55] <maco> pwnguin: er...thats the tradeoff in everything
[06:56] <crdlb> and ext3 is "good enough"
[06:56] <yossarian> i have an unrelated question, though. i'm on 64bit intrepid and i'm having certain problems, like viewing flash videos in full screen. is there any point in using 64bit or should i revert to 32 for the time being?
[06:56] <pwnguin> maco: with the exception that filesystems generally make their way to bug free
[06:56] <yossarian> i'm not a complete n00b, though, just very close to one :)
[06:57] <pwnguin> and the worst they can deal out is bigger than a bluescreen
[06:57] <pwnguin> anyways
[06:57] <pwnguin> fedora 11's shipping ext4 by default i think
[06:57] <crdlb> fedora is fedora
[06:57] <pwnguin> which is probably a bit premature
[06:58] <crdlb> fedora is a permanent alpha ;P
[06:58] <pwnguin> kernel.org removed the EXPERIMENTAL tag back in december or so
[06:59] <pwnguin> if you don't make regular backups, its probably a good idea to stay away from ext4 just in case
[06:59] <pwnguin> its also a good idea to start making backups
[06:59] <crdlb> imho, if you have something on ext4 and on a backup, you only have one copy of it :)
[07:00] <pwnguin> my backups are on raid 0
[07:02] <SwedeMike> one should wait a couple of years before a filesystem goes out of experimental, unless there is a real good reason to start using it immediately.
[07:02] <SwedeMike> I would never do it just because it's fun (on a box where the information is important)
[07:03] <pwnguin> well
[07:03] <pwnguin> this is #ubuntu+1
[07:04] <pwnguin> anyone running jaunty has to deal with breaking in bad ways
[07:04] <pwnguin> you're probably not running your webserver or mysql DB on jaunty
[07:05] <pwnguin> anyways, online defrag's pretty nice if you care about boot speed
[07:06] <SwedeMike> pwnguin: well, I wouldn't run ext4 even when jaunty is properly released.
[07:07] <SwedeMike> at least not on a box which is important
[07:07] <ronny> hmm
[07:07] <pwnguin> again, it depends on your definition of important and tolerance for risk
[07:07] <ronny> pwnguin: major issues with sound here
[07:10] <pwnguin> it should come as no surprise that ted tso is using ext4 on his desktop now
[07:15] <dtchen> ronny: "major"?
[07:16] <ronny> dtchen: suddenly the pc-speaker beek works, and the rest is silent
[07:17] <ronny> the only sound config that seems to work is oss
[07:17] <ronny> but only for the tests from the sound preferences
[07:18] <dtchen> ronny: alsa-info.sh output?
[07:19] <ronny> dtchen: where do i get that one?
[07:22] <ronny> nm, should have googled (TM)
[07:30] <ronny> dtchen: http://dpaste.com/121136/
[07:31] <ronny> what i dont et is why the heck pulse is not actually running
[07:32] <dtchen> it probably is; what does pgrep -f pulseaudio return?
[07:32] <ronny> oh yikes
[07:32] <dtchen> sorry, you probably don't want -f
[07:33] <dtchen> anyhow, please unmute 'Surround', 'Center', and 'LFE'
[07:33] <ronny> i just figured one of the reason - it pumped all of my sound into a rtp thing
[07:33] <dtchen> ah
[07:33] <ronny> but why the heck?!
[07:33] <dtchen> did you configure it to do so using paman?
[07:34] <ronny> no
[07:34] <ronny> i wonder how that happended
[07:34] <ronny> i think i did set up in intrepid, but it worked there
[09:48] <yossarian> hum this is weird
[09:48] <yossarian> just updated to jaunty
[09:48] <yossarian> and it seems to work nicely
[09:48] <yossarian> except
[09:48] <maco> except its alpha software?
[09:48] <yossarian> when i try to enable compiz it says 'desktop effects could not be enabled'
[09:48] <TheInfinity> no 3d drivers? ;)
[09:49] <yossarian> i have nvidia 180
[09:49] <yossarian> enabled
[09:49] <fosco_> this is a common and well known jaunty problem
[09:49] <yossarian> any way to bypass it?
[09:49] <yossarian> i tried deleting /dev/nvidiactl
[09:49] <TheInfinity> wait until its fixed ;)
[09:50] <fosco_> http://ubuntuforums.org/showpost.php?p=6378516&postcount=25 <- the bug and how to solve it
[09:51] <yossarian> hmm i don't get it :-s
[09:51] <BUGabundo> guud morning!
[09:56] <yossarian> i can't find the solution there :\
[09:59] <BUGabundo> is gnome-do dependency broken?
[10:02] <maco> BUGabundo: probably since it's written in mono and mono is broken (i cant update f-spot because itll break tomboy)
[10:04] <BUGabundo> https://bugs.edge.launchpad.net/ubuntu/+source/f-spot/+bug/314516
[10:04] <BUGabundo> maco: I got it finally updated yesterday
[10:04] <BUGabundo> it was one queue for weeks
[10:04] <BUGabundo> but some how it got broken any way
[10:04] <BUGabundo> bad APT
[10:05] <BUGabundo> The following packages have unmet dependencies:
[10:05] <BUGabundo>   gnome-sharp2: Depends: libart2.0-cil but it is not going to be installed
[10:05] <BUGabundo>                 Depends: libgconf2.0-cil but it is not going to be installed
[10:05] <BUGabundo>                 Depends: libgnome2.0-cil but it is not going to be installed
[10:05] <BUGabundo>                 Depends: libgnome-vfs2.0-cil but it is not going to be installed
[10:05] <BUGabundo> E: Broken packages
[10:10] <maco> BUGabundo: here's a hint: aptitude why-not libgconf2.0-cil
[10:12] <BUGabundo> https://bugs.launchpad.net/do/+bug/330025
[10:12] <BUGabundo> in case anyone wants so sub to it
[10:13] <BUGabundo> maco: then the package should have that depency
[10:15] <BUGabundo> maco: that lib requires me to remove gnome-do, and not fix it
[10:16] <maco> BUGabundo: ugh you dont get it
[10:16] <maco> gnome-do NEEDS a different -cil package
[10:17] <maco> one of your other mono apps needs that -cil package
[10:17] <maco> those two -cil packages *cannot* peacefully coexist
[10:17] <maco> decide which app you want more, or don't update til whichever one wants the older package is updated to work with the newer one
[10:18] <BUGabundo> maco that's clear: I want DO
[10:18] <maco> ok so install whatever do needs and itll uninstall whatever needed that
[10:19] <maco> it's libgnome2.24-cil that you have to remove
[10:19] <BUGabundo> but that's the prob: with ALL installed it still fails to launch
[10:19] <BUGabundo> but DO 0.8 requites 2.24
[10:20] <maco> oh i thought that output above was for do
[10:20] <BUGabundo> and then it seems to need gnome-sharpe
[10:20] <BUGabundo> that also depends some other stuff that is not instalable
[10:20] <maco> gnome-sharp2 and gnome-do conflict with each other
[10:21] <BUGabundo> not here
[10:21] <maco> gnome-sharp2 needs 2.0-cil. gnome-do needs 2.24-cil. 2.0-cil and 2.4-cil cannot co-exist. gnome-do and gnome-sharp2 thus conflict as well
[10:21] <BUGabundo> as I said, yesterday it seemed to be fixed
[10:21] <maco> what do you mean "not here"?
[10:21] <BUGabundo> something is wrong with my PPA version then
[10:21] <BUGabundo> not here = not on my system
[10:22] <BUGabundo> I don't get any conflit
[10:22] <BUGabundo> it will install... but not start
[10:22] <maco> just because gnome-do doesnt say "no gnome-sharp2" allowed doesnt mean they dont conflict farther along the dependency chain, which is what's happening
[10:22] <maco> probably theyre *supposed* to work together
[10:22] <maco> since do is complaining that it cant find sharp
[10:22] <maco> since sharp isn installed
[10:22] <maco> because its dependencies conflict with do's dependencies
[10:23] <maco> so do conflicts with its own dependency, in effect. as weird as that sounds
[10:23] <BUGabundo> its bug on depencies then
[10:23] <BUGabundo> eheh
[10:23] <maco> when sharp is updated to work with 2.24, they can coexist
[10:23] <BUGabundo> I guess
[10:23] <maco> basically, gnome-do is not installable until sharp is updated to work with 2.24
[10:23] <BUGabundo> but then apt shouldn't have allowed the update to go in
[10:24] <BUGabundo> I never force, just in case
[10:24] <ziroday> BUGabundo: there is a PPA for do, it works for me on jaunty
[10:24] <maco> who says that's apt's fault?
[10:24] <maco> apt only knows what the package tells it. maybe the package is wrong.
[10:24] <BUGabundo> I know
[10:24] <BUGabundo> that's what I said
[10:24] <maco> do might not say "i need sharp"
[10:24] <BUGabundo> ziroday: I have both PPAs (do-core and testers) but it doesn't build for 64 bits
[10:25] <ziroday> BUGabundo: ah, can't help you on 64bit sorry
[10:25] <BUGabundo> maco that's why I filed that bug! cause it NEEDs it
[10:26] <maco> how about a title like "gnome-do's dependencies conflict with each other"
[10:26] <BUGabundo> feel free to improve the bug description
[10:26] <maco> and if that's from a ppa...whyd you file it in "gnome-do (ubuntu)"
[10:27] <BUGabundo> apport did it! (I have a bug on that too... apport should really link to other LP projects)
[10:27] <maco> BUGabundo: by the way, is kmail doing stupid stupid things for you?
[10:27] <BUGabundo> I also marked it to GO project
[10:27] <BUGabundo> like what?
[10:27] <maco> like saying that there are new mails but then not actually showing them in the inbox?
[10:27] <BUGabundo> kmail is working! that's all I need it to do
[10:27] <maco> i know i had 260 unread before
[10:28] <BUGabundo> not that!
[10:28] <maco> it says "263 unread" but there are no new ones highlighted anywhere
[10:28] <BUGabundo> but I have some cache prob: some folders have emails, it shows it as bold, but doesn't show the unread count
[10:28] <maco> restarting kmail sometimes fixes it
[10:28] <BUGabundo> only all emails number
[10:28] <BUGabundo> maco: that's the count of SUBfolders
[10:28] <BUGabundo> not that folder
[10:28] <maco> it also seems if kmail is running before i get online (such as after resuming from suspend) itll refuse to check for new mail til after i close it and reopen it. which is stupid.
[10:29] <maco> BUGabundo: im looking in the inbox folder.
[10:29] <BUGabundo> they seem to change the behaviour during 4.x
[10:29] <maco> there are no subfolders on my inbox
[10:29] <BUGabundo> maco: KIO probs... not kmail by it self
[10:29] <BUGabundo> those get jamed...
[10:29] <maco> kio?
[10:29] <BUGabundo> I always close kmail before hibernate just in case
[10:29] <maco> that shouldnt be necessary
[10:30] <BUGabundo> yeah, the connections it starts and then are managed by the system libs
[10:30] <BUGabundo> not kmail it self
[10:30] <BUGabundo> just pkill kio
[10:30] <BUGabundo> and you will be fine
[10:30] <maco> not that evolution always resumes properly either. but at least 3/4 of the time it resumes properly. kmail never does.
[10:30] <BUGabundo> kmail works IF it is not looking for mail
[10:30] <maco> but theyre not local files, so what's kio for?
[10:30] <BUGabundo> but if it is, KIOs will get locked
[10:30] <BUGabundo> no idea1
[10:30] <BUGabundo> I have a bunch
[10:30] <maco> i dont get it
[10:31] <BUGabundo> one for each smtp, imap, pop connection
[10:31] <maco> also, it keeps re-collapsing my threads after i close and open it. i dont want my threads collapsed!
[10:32] <BUGabundo> that's a setting!
[10:32] <maco> BUGabundo: but i set it to not-collapse. then i restart it and it re-collapses. i want it to store the setting across sessions
[10:32] <maco> also, the threading mode names are completely unintuitive. thank you.
[10:33] <BUGabundo> mine don't clopass
[10:33] <BUGabundo> AFAIK
[10:33]  * BUGabundo needs checking
[10:33] <BUGabundo> ehhe Works For ME (TM)
[10:34] <maco> trying "current activity, threaded" ...maybe that means "there's new stuff so move the thread to the top like gmail"
[10:35] <maco> but without putting the messages inside the thread in stack-order like evolution does
[10:35] <BUGabundo> maco: I can't find the collapse setting. where is it?
[10:35] <BUGabundo> I use mailinglist
[10:35] <maco> View menu
[10:35] <BUGabundo> for most of my folders
[10:36] <BUGabundo> some date asc, some desc
[10:36] <BUGabundo> activity SUCKs
[10:36] <BUGabundo> maco: the View menu is not a setting
[10:36] <maco> O_o....no option to select thread?
[10:36] <BUGabundo> its a state.... it won't be saved!
[10:36] <maco> BUGabundo: silly
[10:36] <BUGabundo> there's an option somewhere
[10:37] <maco> if you configure the threading mode its in there
[10:37] <BUGabundo> I have to track it down (or was it "accidently" removed ?)
[10:37] <maco> but if you toggle it in the View menu, i think that ought to be saved.
[10:37] <BUGabundo> saw it
[10:37] <maco> obviously if i toggled it, it means i liked it. keep it.
[10:37] <BUGabundo> file a bug.... eheh
[10:37] <BUGabundo> setting to ALWAYS EXPAND and testing
[10:38] <BUGabundo> works here!
[10:38] <maco> "you like to use this mode eh?  oh well. i'll just forget next restart"
[10:38] <BUGabundo> read threads are getting expanded
[10:38] <maco> right if you edit the view mode
[10:38] <maco> that seems like a silly way to do it
[10:38] <BUGabundo> when they were copplase
[10:38] <BUGabundo> at least using mailinglist view
[10:38] <maco> if you tell it "i want to work this way" by setting it to "this why" by using the View menu, it ought to just remember that
[10:39] <BUGabundo> file a bug!
[10:39] <BUGabundo> KDE has lots of them
[10:39] <BUGabundo> Kontact plenty more!
[10:39] <BUGabundo> eheh
[10:39] <BUGabundo> not enough devs
[10:39] <maco> *this* is what i dont like about kde apps. they dont pay any attention to how the user is working. they require that you find and navigate some over-complicated settings dialog, hunting for the checkbox that makes the checkbox in the menu permanent
[10:40] <BUGabundo> never bother me
[10:40] <maco> i hate their settings dialogs
[10:40] <maco> i avoid them
[10:40] <BUGabundo> I set it ONCE on the view, and it works as expected
[10:40] <maco> i avoid changing settings in kde specifically to avoid ever having to look at those dialogs
[10:40] <BUGabundo> if a folder has a diff way of working I just make a new view for it!
[10:40] <maco> kde 4.2 is pretty, but its apps are still annoying
[10:41] <maco> and WHY does kmail not have a "select the thread" keyboard shortcut or menu option or anything?
[10:41] <maco> hold down shift and click around a bunch is not efficient
[10:44] <BUGabundo> maco: collapse the thread and you can do what you want
[10:44] <BUGabundo> just hit '.' (dot)
[10:44] <BUGabundo> it should expand or collapse and then you can move/copy
[10:45] <maco> ok...
[10:46] <maco> i should map a delete-thread shortcut
[10:46] <maco> oh ther's one already. will have to learn that..
[10:47] <BUGabundo> maco maco : "CHEEEEEEEEEEEEEEESEE" eheheeheheh
[10:47] <maco> yes i saw
[10:47] <BUGabundo> I have it as ctrl+d
[10:47] <maco> like in evolution?
[10:48] <BUGabundo> cause its closer to use left hand
[10:48] <maco> i mentioned the existence of the driver we use to pete graner, so he added it to jaunty and intrepid
[10:48] <BUGabundo> and 'd' for single mail delete
[10:48] <maco> LD
[10:48] <maco> *:D
[10:48] <BUGabundo> you go girl!
[10:48] <BUGabundo> pushing it! hehe
[10:48] <BUGabundo> but FOR ME its not even close to 100% good
[10:48] <BUGabundo> sucks on 64 bits
[10:48] <maco> well its doesnt cause regressions
[10:48] <BUGabundo> I appreciate all GREAT work Nol has been doing
[10:48] <maco> which would be the *big* blocke
[10:49] <maco> *blocker
[10:49] <BUGabundo> video is gettting slower each version
[10:49] <maco> it adds *some* functionality at least
[10:49] <BUGabundo> if you get and older one from SF you will see what I mean
[10:49] <BUGabundo> since nol started to try to get v4l to work at the same time, it got way worse...
[10:49] <maco> i told him it works for photo, which is more than without the driver, but video is slow. orientation detection was being worked on and *installs new version* and oh hey it works now
[10:50] <BUGabundo> many apps fail to use it, unless I use PRELOAD
[10:50] <BUGabundo> yeah
[10:50] <BUGabundo> pics are good
[10:50] <BUGabundo> but my cam aint have all that good quality I see on some webcams
[10:50] <maco> pics are the only thing i used my usb webcam for
[10:50] <BUGabundo> those 1.3 MPx are fake
[10:50] <BUGabundo> I want to use video broadcast
[10:51] <BUGabundo> most of it via flash (bambuser and ustream.tv
[10:51] <maco> but im having an issue. i cant compare cheese w/ each cam on here because cheese goes "oh, which cam do you want to use?" and only lists /dev/video0 (builtin) and ignores my /dev/video1 (usb)
[10:51] <BUGabundo> and currenclty (and on 64 bits) that's a bit touch and go
[10:51] <BUGabundo> 30% of the time it works
[10:51] <BUGabundo> can't you provide it via conf or cli operand?
[10:51] <maco> camorama doesnt even offer to let you choose your input
[10:52]  * BUGabundo reads man
[10:52] <BUGabundo> seems not
[10:52] <maco> cheese has a gui way to pick which cam to use
[10:52] <maco> it just isnt iterating the list properly, i guess
[10:52] <BUGabundo> bug for that?
[10:52] <maco> and like i said, camorama doesnt even have the option
[10:52] <BUGabundo> you can always unload the driver
[10:52] <BUGabundo> eeh
[10:52] <maco> well im not sure yet if thats the exact problem
[10:53] <BUGabundo> and let the 2nd be the only cam
[10:53] <maco> it could be that something's wrong with my usb cam's detection
[10:53] <maco> though hal seems to do fine
[10:53] <BUGabundo> let me re-test the lattest version
[10:53] <BUGabundo> and start cam-server
[10:54] <maco> ah camorama takes an arg
[10:55] <maco> camorama says could not connect to video device /dev/video1
[10:55] <BUGabundo>   -d, --device=STRING                        v4l device to use
[10:55] <BUGabundo> it uses v4l so you need PRELOAD
[10:55] <maco> im trying a different camera
[10:56] <maco> i have 2 webcams
[10:56] <BUGabundo> I know
[10:56] <maco> i would like to compare performance
[10:56] <BUGabundo> you mentioned it
[10:56] <maco> ok so...do you mean my external might not be v4l?
[10:56] <BUGabundo> $ ./install
[10:57] <maco> huh?
[10:57] <BUGabundo> run caminfo on it
[10:57] <maco> gotta install that...
[10:58] <BUGabundo> duh
[10:58] <BUGabundo> $ v4l-info
[10:58] <BUGabundo> not caminfo
[10:58] <maco> oh
[10:59] <BUGabundo> btw I'm posting the resulst of that to the forum
[11:00] <BUGabundo> just in case some one needs to compare
[11:00] <BUGabundo> I see a really low video step
[11:00] <BUGabundo> maybe that's what's making it slow
[11:01] <maco> v4l-info doesnt show /dev/video1
[11:02] <BUGabundo> done
[11:02] <maco> oh wait
[11:02] <BUGabundo> I only have one so I can't say
[11:03] <maco> pgraner had me unload the module my external uses during debugging
[11:05] <maco> huh. it seems hal knows my webcam is a webcam but doesnt know that that makes it a video device.
[11:06] <BUGabundo> maco: mind testing http://blubug.bugabundo.net:65006/
[11:11] <maco> BUGabundo: your site crashed X
[11:12] <BUGabundo> ehehe
[11:13] <BUGabundo> really?
[11:13] <BUGabundo> its just a PIC!
[11:13] <BUGabundo> works here fine
[11:13] <maco> well i opened it and it was like "Loading..." and taking a while
[11:13] <BUGabundo> I don't even see your connection attenpt on my log
[11:13] <maco> so i went to switch back to here
[11:13] <maco> and then my cpu started spinning up all insane
[11:13] <BUGabundo> let me test from another computer
[11:14] <maco> my mouse still moved but nothing else worked. and allthough i have ctrl+alt+bksp re-enabled, it didnt work
[11:14] <maco> alt+sysrq+REI worked, but the SUB never went through
[11:15] <BUGabundo> works now
[11:15] <BUGabundo> wrong IP on port fw
[11:16] <BUGabundo> some how the router changed my IP
[11:16] <BUGabundo> lol
[11:16] <BUGabundo> didn't you try alt sysreq K
[11:16] <BUGabundo> eheheheheheehh
[11:16] <maco> well i no longer trust your networking
[11:16] <maco> you killed my laptop
[11:16] <BUGabundo> don't all those ppl ever heard about dontzap tool?
[11:16] <maco> or at least froze it
[11:16] <BUGabundo> used it the second it hit the repos
[11:17] <maco> theyre upset that they have to teach their tech-support-receivers to use the *command line* dontzap tool
[11:17] <BUGabundo> how can a simple adsl router with a block port KILL your laptop?
[11:17] <maco> kde has a gui way. kde is smart.
[11:17] <BUGabundo> doesn't make sense
[11:17] <maco> i dont know but the timing was impeccable
[11:17] <maco> i try to open your site, and BAM my computer freezes
[11:18] <maco> maybe firefox or my wireless driver reacted poorly?
[11:19] <BUGabundo> SERIOUS BUG then
[11:19] <BUGabundo> should file a SECURITY bug if you can reproduce
[11:19] <BUGabundo> would you mind accessing that page again? the port fw should be fixed
[11:20] <BUGabundo> ahh some users already using it
[11:20] <maco> i dont have the link
[11:20] <maco> i rebooted, remember?
[11:20]  * BUGabundo must not make stupid faces while on webcam
[11:20] <BUGabundo> http://blubug.bugabundo.net:65006/
[11:21] <maco> you're not a bot!
[11:21] <BUGabundo> apperently not!
[11:32] <joaopinto> BUGabundo, a lot of archives there :P
[11:35] <BUGabundo> ehehe
[11:35] <BUGabundo> ppl are pervets
[11:48] <Hirato> any comments on Jaunty's current stability?
[11:51] <Hirato> just curious if there's currently any issues that might hinder early adoption
[11:51] <BUGabundo> Hirato: every day we get new bugs/probs
[11:51] <BUGabundo> and every new day some get fixed
[11:52] <BUGabundo> if you need a stable system don't upgrade
[11:52] <BUGabundo> but feel free to get a daily and run it from a livepen setup
[11:53] <Hirato> I don't might instabilities, I'm just asking if it's unstable to the extent of critical components not working with proprietary drivers (nvidia specifically)
[11:53] <Hirato> at present :)
[11:55] <BUGabundo> nope. its working for me with Nvidia
[11:55] <BUGabundo> don't know the current state o ATI
[11:55] <Hirato> thanks mate, just what I wanted to hear
[14:56] <lidaobing> !schedule
[15:01] <maxb> Someone with power over the bot should fix its spelling of "Jackalope" :-)
[15:03] <Pici> !schedule-#ubuntu+1 =~ s/Jackelope/Jackalope/
[15:03] <Pici> maxb: fixed
[15:04] <maxb> thanks
[15:04] <lidaobing> !schedule
[15:28] <MarcoPau> hello, can jaunty work on a pendrive?
[15:28] <BUGabundo> yes
[15:29] <MarcoPau> BUGabundo: same procedure with casper-rw directory?
[15:31] <Hirato> I thought there was a utility that doing the majority of the grunt work for you
[15:32] <MarcoPau> I actually check pendrivelinux.com for the initrd.gz file, but I can't see anything related to jaunty at the moment
[15:32] <BUGabundo> usb-creator
[15:32] <MarcoPau> I just downloaded the iso file and created the two partitions as I've been doing with the previous releases
[15:33] <MarcoPau> BUGabundo: thanks, I'm checking that out
[15:34] <blizzle> Managed to finally get 3d acceleration and Nvidia's drivers installed on jaunty (for TNT2).. wanted to say thanks to those who helped yesterday.. RAOF not here it seems.
[15:34] <BUGabundo> no need for two partitios
[15:34] <BUGabundo> since ibex that the installer is able to DELETE everthing that its not userspace
[15:35] <MarcoPau> BUGabundo: great. fat or ext3?
[15:36] <BUGabundo> for what?
[15:38] <MarcoPau> BUGabundo: for usb-creator. I usually made two partitions, one as fat and casper-rw as ext3. set the boot flag on the fat and install-mbr on the pendrive
[15:38] <MarcoPau> no need for that anymore at all?
[15:39] <BUGabundo> MarcoPau: start usbcreator and let it did do everything!
[15:39] <BUGabundo> it will format the pen as needed!
[15:39] <BUGabundo> no need to mess around
[15:39] <MarcoPau> awesome. thanks BUGabundo
[15:40] <MarcoPau> obrigado
[15:40] <BUGabundo> de nada
[15:58] <nblrac> any reports on that intel bug?
[15:59] <BUGabundo> sure
[15:59] <BUGabundo> a bunch of them
[15:59] <BUGabundo> just have to find the one that suits you
[16:00] <nblrac> lol
[16:00] <nblrac> .
[16:01] <nblrac> i though i had this bug 304871
[16:01] <nblrac> but after looking though my logs, i see that i dont
[16:02] <nblrac> but the symptoms are the same
[16:09] <nblrac> the odd thing is, when i boot from the 8.04 (to edit xorg.conf and view logs) graphics are great compiz works at the higher level.
[16:10] <nblrac> in 8.10 compiz would not even work. and now in jaunty graphic acceleration has to be turned of for it to boot correctly.
[16:13] <nblrac> is there a way i can roll back the drivers?
[16:14] <nblrac> with out breaking any thing else
[16:17] <BUGabundo> nblrac: yes
[16:17] <BUGabundo> synaptic and FORCE older version
[16:17] <BUGabundo> if available on your local cache
[16:20] <nblrac> i just downloaded the old deb
[16:20] <nblrac> but im un sure how i can force it to be installed
[16:23] <BUGabundo> put it in the cache and choose it from synapic
[16:23] <BUGabundo> or use dpgk -I YOURDEB.deb
[16:24] <BUGabundo> typo: or use dpgk -i YOURDEB.deb
[16:56] <TuTUXG> is it just me or pulseaudio server in jaunty 64 bit is actually very unstable?
[16:56] <BUGabundo> no no!!! its just you /sarcasm
[16:57] <TuTUXG> BUGabundo, so u mean the opposite? lol
[16:57] <Pici> TuTUXG: There was just an update released for it, see
[16:58] <Pici> https://lists.ubuntu.com/archives/ubuntu-devel/2009-February/027375.html
[16:58] <TuTUXG> Pici, cool, thanks for the info
[17:00] <BUGabundo> TuTUXG: its higly experimental
[17:00] <BUGabundo> will not make into final release
[17:00] <BUGabundo> report EVERY bug you find
[17:04]  * SiDi hopes Xubuntu 9.04 will stay on alsa...
[17:06] <TuTUXG> SiDi, pulse is the future and is much nicer when works
[17:06] <BUGabundo> eheh "when it works"
[17:08] <SiDi> when it works  indeed :D
[17:08] <SiDi> wine and games still sux with pulse
[17:08] <SiDi> i cant leave exaile and etqw with pulse, while i can with alsa
[17:08] <SiDi> same for wine games
[17:08] <SiDi> and i play a lot.. :D
[17:11] <TuTUXG> i know this is bs, but if u can actually see the whole picture, u will understand y ubuntu chose pulse over alsa
[17:13] <TuTUXG> or u can stick with debian
[17:16] <BUGabundo> I just found out that wubi automagicly installs Ubuntu 64 bits if it can!
[17:21] <TuTUXG> the new wallpaper transition is sexy
[17:23] <quassel116__> Does anyone else always get the "Partial upgrade" message when running update-manager?
[17:23] <quassel116__> Mine wont upgrade f-spot
[17:23] <TuTUXG> mono problem
[17:24] <quassel116__> is there a fix?
[17:24] <TuTUXG> wait till they fully upgrade mono2
[17:24] <quassel116__> oh ok
[17:25] <TuTUXG> Voltron, picasa is much better imo
[17:26] <Voltron> yeah, i dont even use f-spot, i use picasa but it was still weird to me that it wouldnt update f-spot
[17:27] <TuTUXG> just remove it, upgrade everything else, reinstall it again
[17:27] <Voltron> i guess i should go through and clean out all the stuff i dont use because i have a replacement for it so that i don't have these problems again
[17:27] <Voltron> well, not problems, but annoyances
[17:28] <TuTUXG> well, that's what alpha means
[17:29] <Commie_Cary> dose ATI support juanty yet
[17:30] <Voltron> i thought it was alpha because it was the leader, like alpha male you know?
[17:30] <Tekno> :D
[17:30] <TuTUXG> lol
[17:39] <Commie_Cary> dose ATI support juanty yet
[17:39] <BUGabundo>  !ati
[17:39] <Voltron> !ati
[17:39] <Voltron>  !ati
[17:40] <Voltron> what does it respond to?
[17:40] <Commie_Cary> >_>
[17:40] <Commie_Cary> thats for 8.10
[17:40] <BUGabundo> its outdated
[17:40] <Pici> Voltron: It already responded, look up,.
[17:40] <Commie_Cary> im asking if they support 9.04
[17:41] <Voltron> but, it didnt respond to me
[17:41] <Voltron> !nvidia
[17:41] <Voltron> ah, i see
[17:41] <Pici> Voltron: Because someone had just requested it. It has built-in flood protection
[17:41] <Voltron> i see that now...
[17:41] <Voltron> thanks
[17:41] <BUGabundo> Voltron: I know nvidia is working
[17:41] <BUGabundo> not sure about ati
[17:42] <BUGabundo> you have to wait for a user that owns one
[17:42] <Commie_Cary> damn it
[17:42] <Commie_Cary> I want to use ext4 already
[17:42] <Commie_Cary> :<
[17:42] <BUGabundo> Pici: do you have any tips on how to debug
[17:42] <BUGabundo> a wired card?
[17:42] <Voltron> what is so good about ext4?
[17:42] <BUGabundo> guys at #ubuntu kernel are a sleep or on holiday
[17:43] <BUGabundo>  !ext4
[17:43] <Pici> BUGabundo: check lspci/lshw?
[17:44] <BUGabundo> let me get that on a paste bin
[17:44] <scizzo-> Voltron: google for ext4
[17:44] <Voltron> very difficult
[17:44] <scizzo-> why?
[17:44] <BUGabundo> too many hits
[17:45] <BUGabundo> Voltron: http://kernelnewbies.org/Ext4
[17:45] <Pici> http://en.wikipedia.org/wiki/Ext4
[17:45] <Voltron> thanks guys
[17:46] <Voltron> how much performace gain will i get though?
[17:47] <BUGabundo> Voltron: each case is diferent
[17:47] <BUGabundo> you have to test it your self
[17:48] <Voltron> hmmm, i think i will wait until jaunty get released to go ahead and go through all the trouble
[17:48] <Voltron> is anyone here using it though?
[17:49] <BUGabundo> I'm waiting to find a 200GiBs disk to backup my laptop data so I can format
[17:49] <Voltron> get a USB drive, theyre cheap now days
[17:49] <Voltron> 200 gig would be like 45$
[17:50] <Voltron> USB hard drive*
[17:50] <BUGabundo> 1TiBs for 90€, 45 for 500GiBs
[17:52] <TuTUXG> from ext3 to ext4 and 5400rpm to 7200rpm, my system's boot time is cut from 55s to 25s
[17:55] <Voltron> Can't
[17:55] <Voltron> I just run NTFS?
[18:03] <Voltron> !ntfs
[18:03] <Voltron> !FUSE
[18:04] <Voltron> !kernel
[18:04] <Voltron> !ntfs-3g
[18:05] <Voltron> !ntpd
[18:05] <Voltron> !jaunty
[18:06] <Voltron> go to #timmy
[18:06] <unixdawg> so did koffice get update dfor jaunty yet ?
[18:07] <Voltron> sorry, wrong channel
[18:07] <unixdawg> TIMMMYYYYY
[18:07] <unixdawg> lol
[18:11] <Ienorand> I sanyone else running jaunty in vmwarte here?
[18:12] <Ienorand> *Is; *Jaunty; *VMWare.
[18:38] <tawmas> Hi! I'm in the middle of my daily upgrades, and synaptic seems to be stuck while upgrading dovecot-common (the terminal says "Installing new version of config file /etc/init.d/dovecot").
[18:38] <tawmas> CPU activity is low (synaptic fluctuates between 0 and 2%).
[18:38] <tawmas> I don't know what's going on, and what I can do about that...
[18:41] <tawmas> Nevermind, it spawned a "Modified configuration file" window, on a different desktop and below a Firefox window :-(
[18:48] <Ienorand> Is f-spot being kept back in upgrades the norm for all at the moment?
[18:48] <BUGabundo1> @Ienorand yes! dependy
[18:48] <`Matir> Ienorand, yeah, it is for me
[18:49] <`Matir> Has anyone seen their touchpad switch from edge-scrolling to multitouch?  I'm trying to figure out how to revert to edge scrolling
[18:50] <BUGabundo1> `Matir: humm only kernel could do that
[18:50] <BUGabundo1> and only if your touchpad supports multitouth
[18:50] <BUGabundo1> file a bug....
[18:51] <BUGabundo1> it would seem that if MT is availble it will be used instead of ES
[18:53] <`Matir> BUGabundo1, there's a bug open on it (https://bugs.launchpad.net/bugs/320632), but no workaround for ES
[18:53] <FFForever> anyone know how i can watch netflix ondemand in linux?
[18:54] <BUGabundo1> FFForever: ask on #ubuntu or ubuntu-users ML
[18:55] <FFForever> ML?
[18:55] <maxb> mailing list
[18:55] <FFForever> where is the ml?
[18:56] <BUGabundo1> https://lists.ubuntu.com/archives/ubuntu-users
[18:57] <BUGabundo1> or on answers
[18:57] <BUGabundo1> https://answers.launchpad.net/ubuntu/
[19:01] <FFForever> maco, u around?
[19:03] <maco> FFForever: yes
[19:04] <FFForever> maco do u know how i can compile my own kernel with a temp fix to get my mic working?
[19:04] <maco> FFForever: you don't know how to compile a kernel?
[19:04] <maco> and you're running an alpha release?
[19:04] <maco> this sounds like a bad idea
[19:05] <FFForever> yes?
[19:05] <FFForever> i am on 9.04 because it has newer packages =)
[19:05] <maco> that's not a good reason
[19:06] <maco> you *really* ought to only run stable releases if you don't know how to mess with all the underlying stuff in case of breakage
[19:08] <nightrid3r> will jaunty support the SIS671/771 vga chip in 3D
[19:27] <nblrac> mm i just broke X even more by forcing old drivers at it :(
[19:28] <nblrac> but when i boot in recovery mode to root
[19:29] <nblrac> it ask for a root password for maintenance, is this new for jaunty?
[19:29] <SiDi> nblrac, it should be the password of your default user
[19:30] <nblrac> i have 2 users, and i tried both
[19:30] <BUGabundo1> maco: that DO bug, it was related to a bad behaving plugin
[19:30] <nblrac> they both did not work
[19:30] <BUGabundo1> nblrac: it only asks your pass if you set one for ROOT
[19:31] <BUGabundo1> its the root pass, not your users
[19:31] <Pici> Or its a bug.
[19:31] <_010100> BUGabundo1: so did the plugin want the package that couldnt be installed?
[19:32] <nblrac> i dont think i never set a root password, i always just used sudo and my password
[19:33] <SiDi> try to put nothing then ? :P
[19:36] <BUGabundo1> it would seem so maco
[19:36] <BUGabundo1> Pici: I remember a bug like that on feisty
[19:37] <maco> BUGabundo1: was the plugin included or 3rd party / part of another package?
[19:38] <BUGabundo1> not sure
[19:38] <BUGabundo1> I just removed all
[19:38] <BUGabundo1> and it worked
[19:38] <maco> disabled or uninstalled?
[19:38] <maco> figure out which plugin
[19:39] <maco> if it's one that's included, then gnome-do's package needs to depend on gnome-sharp2
[19:39] <BUGabundo1> I'm now re-instiling everything #DO
[19:39] <maco> ok
[19:39] <BUGabundo1> just finish reinstaling
[19:40] <BUGabundo1> its starting and all my plugins are still active
[19:40] <BUGabundo1> go figure!
[19:41] <nblrac> SIDi i dont think that can be the password; i thought that ubuntu install auto generated the password and kept it for it self
[19:44] <Pici> nblrac: no, it locks the root account. There is no password set, but its not blank either.
[19:45] <nblrac> so how to i boot in revovery mode with network so i can install the correct driv ers
[19:48] <BUGabundo1> guys trying to debug that sis laptop, and I'm testing a few acpi options
[19:48] <BUGabundo1> hpet=disable, acpi=noirq, pci=routeirq
[19:49] <BUGabundo1> one of them looked like it froze, but actually took more then 30 sec to show any output
[19:49] <nblrac> brb
[19:49] <BUGabundo1> does any one ever experience that?
[19:51] <Ienorand> Is sanyone else running jaunty in vmware here?
[21:30] <Oli```> anybody know about the clash between python2.6 and python-gdbm that's happened in the latest updates?
[21:45] <Ienorand> bernard__: same problem, you running vmware?
[21:45] <bernard__> No.
[21:46] <bernard__> I found this:
[21:46] <bernard__> https://bugs.launchpad.net/ubuntu/+bug/325973
[21:46] <bernard__> But it doesn't seem to match my situation exactly either.
[21:46] <bernard__> I don't think any of the instances are starting, so the system is usable.
[21:46] <bernard__> bernard@stickers:~$ nautilus
[21:46] <bernard__> (nautilus:7559): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
[21:47] <Ienorand> ah, unexpected logout...
[21:48] <Ienorand> bernard__: I've reported bug #329146 myself, does that match yours?
[21:49] <bernard__> Yes, it does.
[21:49] <bernard__> I'll try and remember my launchpad login. :p
[21:49] <Ienorand> Okay, good I'm not alone at least, it's completely possible to use ubuntu with this issue but it is somewhat annoying :/
[21:50] <bernard__> Yeah.
[21:50] <biouser> I'm sure that someday pulseaudio will be really good but for right now I think I would like to have sound
[21:50] <biouser> any ideas of a good way to remove
[21:50] <bernard__> pulseaudio -k; sudo apt-get purge pulseaudio?
[21:51] <bernard__> Works for me, for what it's worth.
[21:52] <biouser> removing ubuntu-desktop is not the problem it once was?
[21:53] <bernard__> Uhhhhhhhh... pass. Sorry. :p
[21:54] <bernard__> Okay, I added a comment and subscribed to your bug, Ienorand.
[21:56] <biouser> okay, I can listen to democracy now now
[21:57] <biouser> will there be a memo when pulseaudio works?
[21:57] <biouser> I kind of like the idea of it
[22:01] <Ienorand> biouser: You said you had flash issues? In that case https://wiki.ubuntu.com/PulseAudio has info...
[22:03] <SiDi> biouser, there should be a window popping up on system startup once it works properly and even linux software uses it ! \o/
[22:03] <bernard__> Ienorand: from dmesg: [   42.636631] nautilus[3660]: segfault at 98a0008 ip b5d9755d sp b5d85fc0 error 4 in libbrasero-media.so.0.1.1[b5d87000+1e000]
[22:04] <bernard__> Spammed a million times.
[22:04] <biouser> Ienorand I think I did most/all of that and have been using flash-10...
[22:05] <Ienorand> biouser: ah, ok
[22:06] <biouser> I am happy without pulse for now but eventually... I don't know, I really wish that everyone would just get on the JACK train....
[22:06] <Ienorand> bernard__: okay, that's at least something, add to bug?
[22:06] <bernard__> Ah.
[22:06] <bernard__> Removing libbrasero-media0 stopped it.
[22:07] <bernard__> And nautilus works.
[22:07] <bernard__> Woo!
[22:07] <bernard__> Will do.
[22:08] <Ienorand> bernard__: have you tried restarting after that as well, since I've had times when it stopped only to return after reset...
[22:08] <bernard__> Okay, I'll restart and report.
[22:10] <Ienorand> Going for a reboot myself...
[22:12] <bernard__> Ienorand: Yay! Still working!
[22:16] <Ienorand> bernard__: how did it go?
[22:16] <bernard__> Still working. Woo!
[22:16] <bernard__> Updated your bug's description.
[22:17] <Ienorand> so, what was that package name again?
[22:17] <bernard__> libbrasero-media0 I think.
[22:18] <bernard__> I removed brasero first, that didn't fix it, but it may be pulled in by the other.
[22:18] <Ienorand> cheers
[22:24] <Ienorand> bernard__: Works for me as well. I'll add brasero to the bug
[22:24] <bernard__> Cool.
[22:24] <bernard__> I'm just glad to get my window list back. :3
[22:25] <DanaG> grr, stupid nvidia 96... hangs on login.
[22:29] <DanaG> Gotta' love closed-source hardware.
[22:29] <DanaG> ANd nouveau devours 40% of the CPU.
[22:29] <DanaG> when I use it, that is.
[22:29] <DanaG> And even gnome-panel is devouring CPU on nvidia 96.
[22:30] <DanaG> ... and when I kill gnome-panel, Xorg crashes.
[22:31] <DanaG> backtrace is in /usr/lib/xorg/modules//libxaa.so
[22:31] <DanaG> xaa?  Doesn't nvidia use its own thing instead of XAA?
[22:31] <RAOF> Yes.
[22:32] <DanaG> I wonder why it's loading libxaa for nvidia.
[22:33] <DanaG> ALso backtraces in /usr/lib/xorg/modules/extensions//libextmod.so
[22:34] <DanaG> And nouveau DOES still devour CPU on that system.
[22:34] <DanaG> Then again, nvidia does now, too... when it's not crashing.
[22:39] <DanaG> I don't regret getting ATI on my new laptop, actually.\
[22:40]  * DanaG makes note to self: when talking to people, take note of the address -- it can indicate time zone.
[22:40] <DanaG> I don't happen to know what time zone Australia is in, though.
[22:41]  * DanaG is in GMT+8, if you ignore that hassle that is DST.
[22:47] <bernard__> DanaG: I'm in New Zealand, and it's 11:46 AM here, so it'll be a little earlier than that in Oz.
[22:48] <maco> bernard__: is it tomorrow there?
[22:48] <bernard__> It's Tuesday.
[22:48] <bernard__> :)
[22:48] <maco> so yes, tomorrow
[22:48] <bernard__> No, you're all in yesterday. :p
[22:49] <bernard__> It's okay, the world is still fine.
[22:49] <maco> or you're a time-traveler
[22:52] <DanaG> http://www.newegg.com/Special/ShellShocker.aspx
[22:52] <DanaG> er
[22:52] <DanaG> wrong tab
[22:52] <DanaG> still cool though.
[22:53] <DanaG> frankly, /me prefers firewire or eSATA.
[23:10] <thehook> whats the status of jaunty and nvidia drivers? :)
[23:11] <maxb> afaics, they work
[23:12] <maxb> except for occasional hilarious weirdness when windows spontaneously become transparent
[23:12] <maxb> :-)
[23:13] <thehook> hehe, so still not working 100% with the new xorg?
[23:14] <maxb> well, I got weirdness more often in intrepid, so I'd classify them as working
[23:20] <thehook> maxb: ok, thank you i will upgrade to jaunty then :)
[23:28] <Commie_Cary> when is ATI going to support 9.04
[23:34] <burner> anyone know how to configure dual screen in KDE with nouveau?
[23:35] <burner> I tried system settings -> display, but i can't turn off the mirroring
[23:38] <pwnguin> try the xrandr command line
[23:39] <burner> interesting... man page here i come
[23:45] <burner> doesn't seem to work, but it works in gnome.  I tried 'xrandr --output vGA 1440x900' and 'xrandr --output VGA --right-of DVI' to no avail
[23:46] <RAOF> burner: What's the output?
[23:46] <RAOF> (KDE's system settings does seem broken.  In fact, KDE seems broken with dual-head)
[23:48] <burner> RAOF: no output... just goes to the next line
[23:48] <burner> xrandr --output VGA --off doesn't do anything either
[23:48] <RAOF> Your VGA is still running after that?
[23:48] <RAOF> Oh.  Is VGA actually the right identifier?  I guess not.
[23:48] <RAOF> Not if this is nouveau
[23:49] <ripps> Can install a fresh ubuntu and use my seperate /home partition?
[23:49] <RAOF> ripps: Yes.
[23:49] <burner> oh, VGA-0 maybe?
[23:49] <burner> ah ha!
[23:49] <RAOF> burner: 'xrandr' will tell you.
[23:49] <RAOF> XRandR1.2 output naming is horribly inconsistent.  It sucks.
[23:49] <ripps> Last time I tried it with intrepid, I had to wipe it because it would fail with associating the user directory with my user.
[23:50] <burner> huzzah, i'm dual screening kde with nouveau!  too bad the gui doesn't work though
[23:59] <pwnguin> ripps: you just need to make sure that the user id numbers match up
[23:59] <pwnguin> i have a seperate /home and two ubuntu install
[23:59] <pwnguin> i have a seperate /home and two ubuntu install
[23:59] <pwnguin> s