[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] you promised both depending on my preference [00:32] * cwillu awaits dtchen's preference [00:32] 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] sorry, I got the impression you were talking about the race condition exclusively [00:40] 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] 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] 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] franta: Sansas normally have a hardware toggle between MTP and UMS [00:46] maco: I have kubuntu, but I don't think that matters... [00:46] s/UMS/MSC/ depending on the context [00:47] 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] I'm on Hardy now and it works.. [00:49] franta: that's odd; hal-info has a specific quirk for your Sansa e270 [00:49] (obviously, it *should* work0 [00:49] ) [00:49] dtchen: I think it's because I'm booting from usb hdd... [00:49] 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] _VIM_: isn't it included? [01:05] <_VIM_> I guess not :( [01:05] <_VIM_> cant get it to install [01:06] _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] !info linux-headers [01:08] Package linux-headers does not exist in jaunty [01:08] !info linux-headers-generic [01:08] linux-headers-generic (source: linux-meta): Generic Linux kernel headers. In component main, is optional. Version 2.6.28.7.7 (jaunty), package size 2 kB, installed size 32 kB [01:08] <_VIM_> i installed that [01:09] no idea then, sorry [01:09] <_VIM_> np thanks anyways :) [01:34] dtchen, you around? [01:36] sorry my wifi died are u around? === Daviey_ is now known as Daviey [01:41] maco, sorry, just saw your pm now [01:42] 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 =\ === FFForever2 is now known as FFForever [01:43] i have a hp 6810us [01:46] please someone... [02:04] what is cca? [02:47] Anyone wanna help me fix meh mic? [02:49] Probably many want to, but do not know how, FFForever [02:49] i have searched but no one seems 2 know how =( [02:50] FFForever: has it ever worked in ubuntu? [02:50] maco, nope =( [02:50] alsa-info.sh link? [02:51] and have you filed a bug? [02:51] maco, that url is invalid for me =( [02:52] and i didn't file a bug because no one ever responds 2 them =( [02:56] 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] blizzle: Whee! Old-skool. [02:56] RAOF: Yeah, it's a tad ancient! [02:56] 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] RAOF: From what I've read, I need the glx-71 series. [02:57] That's entirely possible. It's been some time since I had a TNT2 :) [02:57] FFForever: haha sure we respond. dtchen goes through a *lot* of sound bugs [02:58] FFForever: and i was asking you for the link supplied by downloading and running http://alsa-project.org/alsa-info.sh [02:58] RAOF: So I should give up, then, and forget accelerated 3d for now? :/ [02:59] maco, ahhh whoops .sh is also a tld... [02:59] for what country? O_o [02:59] blizzle: It looks like the nvidia-glx-71 package should be installable, at least. [03:00] RAOF: It is, and I have. Doesn't seem to help things much, though.. what am I missing? [03:00] http://www.alsa-project.org/db/?f=7bee1d7350cbe77d1d1cb1a6fbe03e7c689e029c [03:00] RAOF: I mean, Jockey should pick up the driver and offer to enable it, no? [03:00] blizzle: Do you have it specified in xorg.conf? [03:01] FFForever: looking [03:01] 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] maco thanks [03:02] RAOF: Nothing at all in xorg.conf, and yes, all -71 related packages are installed, including source. [03:03] 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] FFForever: is the mic recognized as a capture device? [03:05] 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] RAOF: Command not found on nvidia-xconfig [03:06] Well, that's rather stupid. That command was introduced in 96, it seems. [03:06] blizzle: Basically you want to have Driver "nvidia" in you Device section. [03:06] 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] I believe there's a separate nvidia-xconfig package for -71 [03:07] FFForever: padsp audacity [03:07] crdlb, Oh? Where would I find it.. it's not coming up. [03:08] 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] FFForever: that should route audacity through pulse. see what happens. [03:08] I guess somebody removed it in jaunty [03:09] maco uhhh =( [03:09] 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] RAOF: I'm pessimistically optimistic :) [03:09] the intrepid package looks a bit broken (it conflicts against nvidia-glx and nvidia-glx-new instead of the new numbered pkgs) [03:09] FFForever: what? [03:09] maco now i have no devices listed [03:09] FFForever: do you have pulseaudio running? [03:09] i think? [03:09] i hear sound? [03:09] ps -ef | grep pulse [03:10] yeah =) [03:10] pasuspender -- audacity [03:10] what then? [03:11] maco should i relaunch audacity first? [03:11] yes [03:11] kill all running audacities [03:11] then do that [03:12] maco nope =( [03:12] FFForever: test this: arecord -Dplughw:0 [03:13] �� [03:13] ... [03:13] what? [03:13] that is what it keeps outputting [03:13] (into my terminal) [03:13] oh [03:13] wait are we talking about a mic jack or one that's on the screen? [03:14] the one right above the screen =) [03:14] since you have internal and external mic listed along with doc mic [03:14] i want to use the one that is right above the screen (internal) [03:14] if you tap the screen or speak loudly into the mic does the output change? [03:14] well i think its listed as internal but i don't know =( [03:15] yes, internal means the screen mic [03:15] maco just lots of ?... [03:15] i cant record from audacity =( [03:15] the ?'s never change when you make loud noises? [03:15] nope but they do come in blocks =\ [03:16] blocks? [03:16] well yeah like sets of 5-10 [03:16] do they pause or come faster when you make noises? [03:16] nope [03:17] btw the mic works (i tested it in xp) [03:17] :( [03:18] i hate having 2 go into windows to talk on skype =( [03:19] FFForever: have you updated in the last 2 hours or so? [03:20] i think... [03:20] can you please check for new updates? [03:20] dtchen just put out a bunch of new sound stuff this afternoon [03:20] s/put out/uploaded/ [03:21] (i am not using the main mirror but a closer one 2 me should i switch?) [03:21] 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] 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] 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] should i stop the upgrade? [03:23] no install the updates anyway [03:23] kk done [03:24] do i need 2 reboot? [03:24] testing against current usually is most reliable testing [03:24] at least log out and back in for the new pulseaudio [03:24] if there was a new kernel for you, then yes, reboot [03:24] kk [03:24] brb [03:27] back [03:29] 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] he said he'll fix it in a bit [03:29] in the meantime he says if you have a plugin mic, that should work [03:30] maco no external mic for me =( [03:30] can you please ask him when i should be expecting a patch in the repo (tmw, a week, etc) [03:30] (i'm right here, so you don't need to relay) [03:31] oh youre online now [03:31] ahhh cool [03:31] FFForever: with the next kernel upload, hopefully, but no guarantees - really depends on free time [03:32] dtchen, so in about a week? [03:32] FFForever: perhaps, probably more likely to be a couple weeks [03:33] cool ive waited since 8.04 so a little longer won't hurt [03:34] dtchen, thanks for all of your help and time [03:39] 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] JesperHansen: only in the terminal? [03:42] * JesperHansen suspects this mousepad left click is bogus [03:42] JesperHansen: right. what version of xserver-xorg-input-synaptics are you using? [03:42] this sounds like 0.99.3-1ubuntu1 [03:43] 0.99.3-2ubuntu1 [03:44] update [03:44] 2ubuntu2 is out [03:44] brb. [03:48] 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] umm.. ctrl+alt+backspace gone in jauntry? [03:50] -r [03:51] yes [03:51] by default, disabled, jsut like in upstream Xorg [03:51] 1) some people accidentally hit it when they switch workspaces [03:51] 2) devs would rather people report bugs in graphics than hit c-a-b and ignore them [03:52] you can re-enable it like this http://albertomilone.com/wordpress/?p=335 [03:53] Is there btw. some way to make the apport application suck less? [03:53] ie. not requiring people to create an account [03:53] on launchpad [03:54] er...if you dont have an lp account, how do you intend to respond to developers' requests for more information? [03:55] Consider comparing it with mozilla firefox's talkback when firefox crashes. The user provides an email if more information should be needed. [03:55] maco any idea why i have 2 hold a key 2 boot my system when my power cable is not plugged in? [03:56] 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] FFForever: acpi [03:57] any idea on fixing it? [03:57] JesperHansen: or create 1 accout once and never again... [03:57] JesperHansen: where does the boot stop? [03:58] maco: did I mention a boot? [03:58] JesperHansen: er...that was at FFForever [03:58] remembering which person to answer is almost as hard as remembering what language to speak [03:59] i am lost? [03:59] (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] maco u do it? [03:59] FFForever: at what point does booting stop working if you dont hold those keys? [04:00] i don't even see the loading bar =\ [04:00] FFForever: turn off usplash and tell me where it stops [04:00] it gets past grub, right? [04:02] 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] can someone help me with a problem opening terminal sessions? [04:02] and everything is gold if my power is plugged in [04:03] FFForever: in grub, edit the boot line to not say "quiet splash" [04:03] then watch where it stops when you dont hold a key [04:04] or see if maybe it works when you turn off usplash that way [04:04] maco like this?, quiet splash [04:06] the boot line already says "quiet splash" [04:06] delete that and then boot [04:06] ohhh i added it i was just making sure it was right.... [04:06] 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] ohhh.... [04:06] i was adding it 2 menu.lst.... [04:07] no no those 2 options are auto-added in menu.lst [04:07] ahhh [04:07] you dont need to touch that file to do a one-time option-edit [04:07] grub's interactive [04:10] ill do it later i need 2 finish this project [04:11] ok [04:15] can somebody please help me with a problem opening terminal sessions? [04:16] im getting "PTY allocation request failed on channel 0" when I try to ssh into my jaunty box [04:22] problems with touchpad on asus n20a in jaunty. works with latest sidux. copy xorg.conf for synaptics pad? [04:22] problem is an understatement, doesnt work at all [04:25] tell [04:25] :tell === bluesmoke is now known as Amaranth [06:18] RAOF: is it possible that nouveau is confusing the font engine somehow? [06:18] What do you mean? [06:19] lemme bring up a screenshot [06:19] http://people.cis.ksu.edu/~jld5445/av-kerning.png [06:19] Corruption, or large fonts? [06:21] see the av in the playlist (and elsewhere)? [06:22] last time i had bad font problems, it was a dpi thing [06:23] but nobody seems to be having this problem but me so perhaps im doing something wrong =/ [06:23] pwnguin: xdpyinfo [06:24] mjc: [06:24] mjc: http://pastebin.com/f6641b62e [06:24] pwnguin: 381x238 millimeters the actual size of your display? [06:25] millimeters sound small [06:25] lemme translate that first =/ [06:25] its 14.1 inch widescreen [06:26] those dimensions sound about right [06:27] actually no [06:27] 381 is 15 inches [06:34] well, bumping up the dpi does fix it, but kinda tweaks the fonts all over [06:35] with the exception of a few kernings, 96 dpi seemed fine [06:36] pwnguin: well your monitor might be misreporting size [06:36] or the ratio is wrong [06:36] can you measure it exactly and find out? use a milimeter ruler from inside edge to inside edge [06:37] or do inches * 25.4 [06:37] maco: milimeter ruler for accuracy [06:37] not for conversion [06:37] well sorry, s/accuracy/precision/ [06:37] mjc: might not own a millimeter ruler [06:37] maco: most rules have both on them [06:38] then again there are pdf rulers out there [06:38] pwnguin: It is possible that nouveau is corrupting that. [06:38] pwnguin: it's most likely the monitor misreporting size [06:38] but if not that, then nouveau [06:43] sadly, my rulers only go to 1 ft [06:43] if you want mm precision, i should just dig up the specs [06:44] 'lo peeps [06:45] so i shouldn't endeavour to install jaunty jackalope on ext4? [06:45] why not? [06:47] might lose data [06:47] * pwnguin has been using ext4 for a few weeks now [06:48] how safe is it? [06:48] and how long 'til it's 'usable'? [06:54] a filesystem is just not something you experiment with [06:54] sure it is [06:54] :( [06:54] I like to be in at least the bottom 90% on things like that [06:54] there's a tradeoff in filesystems [06:55] new features versus testing and bugs [06:55] pwnguin: er...thats the tradeoff in everything [06:56] and ext3 is "good enough" [06:56] 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] maco: with the exception that filesystems generally make their way to bug free [06:56] i'm not a complete n00b, though, just very close to one :) [06:57] and the worst they can deal out is bigger than a bluescreen [06:57] anyways [06:57] fedora 11's shipping ext4 by default i think [06:57] fedora is fedora [06:57] which is probably a bit premature [06:58] fedora is a permanent alpha ;P [06:58] kernel.org removed the EXPERIMENTAL tag back in december or so [06:59] if you don't make regular backups, its probably a good idea to stay away from ext4 just in case [06:59] its also a good idea to start making backups [06:59] imho, if you have something on ext4 and on a backup, you only have one copy of it :) [07:00] my backups are on raid 0 [07:02] 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] I would never do it just because it's fun (on a box where the information is important) [07:03] well [07:03] this is #ubuntu+1 [07:04] anyone running jaunty has to deal with breaking in bad ways [07:04] you're probably not running your webserver or mysql DB on jaunty [07:05] anyways, online defrag's pretty nice if you care about boot speed [07:06] pwnguin: well, I wouldn't run ext4 even when jaunty is properly released. [07:07] at least not on a box which is important [07:07] hmm [07:07] again, it depends on your definition of important and tolerance for risk [07:07] pwnguin: major issues with sound here [07:10] it should come as no surprise that ted tso is using ext4 on his desktop now [07:15] ronny: "major"? [07:16] dtchen: suddenly the pc-speaker beek works, and the rest is silent [07:17] the only sound config that seems to work is oss [07:17] but only for the tests from the sound preferences [07:18] ronny: alsa-info.sh output? [07:19] dtchen: where do i get that one? [07:22] nm, should have googled (TM) [07:30] dtchen: http://dpaste.com/121136/ [07:31] what i dont et is why the heck pulse is not actually running [07:32] it probably is; what does pgrep -f pulseaudio return? [07:32] oh yikes [07:32] sorry, you probably don't want -f [07:33] anyhow, please unmute 'Surround', 'Center', and 'LFE' [07:33] i just figured one of the reason - it pumped all of my sound into a rtp thing [07:33] ah [07:33] but why the heck?! [07:33] did you configure it to do so using paman? [07:34] no [07:34] i wonder how that happended [07:34] i think i did set up in intrepid, but it worked there === dns is now known as dns53 === dns is now known as dns53 [09:48] hum this is weird [09:48] just updated to jaunty [09:48] and it seems to work nicely [09:48] except [09:48] except its alpha software? [09:48] when i try to enable compiz it says 'desktop effects could not be enabled' [09:48] no 3d drivers? ;) [09:49] i have nvidia 180 [09:49] enabled [09:49] this is a common and well known jaunty problem [09:49] any way to bypass it? [09:49] i tried deleting /dev/nvidiactl [09:49] wait until its fixed ;) [09:50] http://ubuntuforums.org/showpost.php?p=6378516&postcount=25 <- the bug and how to solve it [09:51] hmm i don't get it :-s [09:51] guud morning! [09:56] i can't find the solution there :\ [09:59] is gnome-do dependency broken? [10:02] BUGabundo: probably since it's written in mono and mono is broken (i cant update f-spot because itll break tomboy) [10:04] https://bugs.edge.launchpad.net/ubuntu/+source/f-spot/+bug/314516 [10:04] Ubuntu bug 314516 in drapes "gnome-sharp2 transition" [Medium,Confirmed] [10:04] maco: I got it finally updated yesterday [10:04] it was one queue for weeks [10:04] but some how it got broken any way [10:04] bad APT [10:05] The following packages have unmet dependencies: [10:05] gnome-sharp2: Depends: libart2.0-cil but it is not going to be installed [10:05] Depends: libgconf2.0-cil but it is not going to be installed [10:05] Depends: libgnome2.0-cil but it is not going to be installed [10:05] Depends: libgnome-vfs2.0-cil but it is not going to be installed [10:05] E: Broken packages [10:10] BUGabundo: here's a hint: aptitude why-not libgconf2.0-cil [10:12] https://bugs.launchpad.net/do/+bug/330025 [10:12] Ubuntu bug 330025 in gnome-do "Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'gconf-sharp, Version=2.20.0.0, Culture=neutral, PublicKeyToken=35e10195dab3c99f' or one of its dependencies." [Undecided,New] [10:12] in case anyone wants so sub to it [10:13] maco: then the package should have that depency [10:15] maco: that lib requires me to remove gnome-do, and not fix it [10:16] BUGabundo: ugh you dont get it [10:16] gnome-do NEEDS a different -cil package [10:17] one of your other mono apps needs that -cil package [10:17] those two -cil packages *cannot* peacefully coexist [10:17] 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] maco that's clear: I want DO [10:18] ok so install whatever do needs and itll uninstall whatever needed that [10:19] it's libgnome2.24-cil that you have to remove [10:19] but that's the prob: with ALL installed it still fails to launch [10:19] but DO 0.8 requites 2.24 [10:20] oh i thought that output above was for do [10:20] and then it seems to need gnome-sharpe [10:20] that also depends some other stuff that is not instalable [10:20] gnome-sharp2 and gnome-do conflict with each other [10:21] not here [10:21] 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] as I said, yesterday it seemed to be fixed [10:21] what do you mean "not here"? [10:21] something is wrong with my PPA version then [10:21] not here = not on my system [10:22] I don't get any conflit [10:22] it will install... but not start [10:22] 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] probably theyre *supposed* to work together [10:22] since do is complaining that it cant find sharp [10:22] since sharp isn installed [10:22] because its dependencies conflict with do's dependencies [10:23] so do conflicts with its own dependency, in effect. as weird as that sounds [10:23] its bug on depencies then [10:23] eheh [10:23] when sharp is updated to work with 2.24, they can coexist [10:23] I guess [10:23] basically, gnome-do is not installable until sharp is updated to work with 2.24 [10:23] but then apt shouldn't have allowed the update to go in [10:24] I never force, just in case [10:24] BUGabundo: there is a PPA for do, it works for me on jaunty [10:24] who says that's apt's fault? [10:24] apt only knows what the package tells it. maybe the package is wrong. [10:24] I know [10:24] that's what I said [10:24] do might not say "i need sharp" [10:24] ziroday: I have both PPAs (do-core and testers) but it doesn't build for 64 bits [10:25] BUGabundo: ah, can't help you on 64bit sorry [10:25] maco that's why I filed that bug! cause it NEEDs it [10:26] how about a title like "gnome-do's dependencies conflict with each other" [10:26] feel free to improve the bug description [10:26] and if that's from a ppa...whyd you file it in "gnome-do (ubuntu)" [10:27] apport did it! (I have a bug on that too... apport should really link to other LP projects) [10:27] BUGabundo: by the way, is kmail doing stupid stupid things for you? [10:27] I also marked it to GO project [10:27] like what? [10:27] like saying that there are new mails but then not actually showing them in the inbox? [10:27] kmail is working! that's all I need it to do [10:27] i know i had 260 unread before [10:28] not that! [10:28] it says "263 unread" but there are no new ones highlighted anywhere [10:28] but I have some cache prob: some folders have emails, it shows it as bold, but doesn't show the unread count [10:28] restarting kmail sometimes fixes it [10:28]