[00:00] <BUGabundo1> just to be sure : what gw do I see on the wifi card?
[00:03] <hggdh> the gw should be your local IP on the wifi
[00:03] <BUGabundo1> on both sides, correct?
[00:04] <hggdh> yes
[00:06] <BUGabundo1> not my day
[00:06] <BUGabundo1> 2nd laptop just kernel froze
[00:06] <BUGabundo1> HARD reboot
[00:07] <hggdh> yeeee! These are indeed interesting times ;-)
[00:14] <BUGabundo> bah
[00:14] <BUGabundo> NM also prefers wifi to 3G
[00:14] <BUGabundo> reading up man route
[00:14] <BUGabundo> to set a diff default route
[00:24] <Turl> can you help me debug why doesn't the screen lock on lid close?
[00:25] <BUGabundo> not tonigh
[00:25] <Turl> :(
[00:25] <BUGabundo> too tired and with an headhacke
[00:25] <Turl> anyone else?
[00:26] <BUGabundo> I set mine to not lock any way
[00:26] <BUGabundo> what does your gconf-editor keys for gnome-power-manager say?
[00:28] <Turl> in which part of the gnome-power-manager keys? it has loads of subkeys :p
[00:28]  * BUGabundo didn't I say I was tired?
[00:28]  * BUGabundo makes an effor and looks up
[00:28] <Turl> yeah you did
[00:29] <BUGabundo> apps/gnome-power-manager/lock
[00:30] <BUGabundo> but it seems this is done by screen saver
[00:30] <Turl> odd, if I set it up to suspend, it works beautifully
[00:30] <BUGabundo> /apps/gnome-screensaver/lock_enabled
[00:30] <Turl> I enabled "lock screen when screensaver is on" but nothing
[00:31] <Turl> just checked that key, it's on :S
[00:33] <maco> Turl: gnome hasnt offered to lock screen on lid close since feisty. i guess it was too many options confusing user
[00:33] <maco> kde still has it
[00:33] <Turl> maco: I used to have it enabled on Intrepid :/
[00:34] <Turl> and it worked
[00:34] <Turl> you just need to set up the "blacken screen" action on gnome-power-manager and then setup the screensaver to lock screen
[00:34] <Turl> but it doesn't seem to work in jaunty
[00:36] <maco> Turl: oh. it used to just plain have "on lid close: lock screen"
[00:36] <maco> if you enable the screensaver manually, then what happens?
[00:37] <Turl> how can you enable it manually? :p
[00:37] <Turl> I have set it up to activate in 1 min, lets see what happens
[00:37] <maco> ok
[00:38] <maco> you can right click the battery too i think...or maybe its the lock screen applet that has right-click -> enable screensaver
[00:39] <Turl> well, it appeared and well, locked the screen
[00:39] <maco> hm ok
[00:40] <maco> is thre a "screensaver" option for lid close?
[00:40] <Turl> sec, I think I know what's going on
[00:41] <Turl> no, it wasn't what I thought
[00:47] <BUGabundo> (12:44:25 AM) asac: BUGabundo: cant you set metric manually in connection editor?
[00:50] <RichW> I need to know if python 2.6 will make it to jaunty final?
[00:51] <RichW> I am a open source software developer.
[00:52] <BUGabundo> I don't think so RichW
[00:52] <BUGabundo> it aint even on universe
[00:53] <RichW> nice to see they put in python 3 though... good for developing software for ubuntu +2
[00:53] <BUGabundo> yes p3 is in
[00:54] <RichW> i dont see why they dont just keep 2.5 as default and then have 2.6 launch with the usual python2.6 command
[00:54] <RichW> if they want to play safe for now.
[00:56] <RichW> if they can manage 3 why not 2.6?
[00:56] <BUGabundo> you have to ask to who ever mantains it
[00:56] <BUGabundo> I don't have a clear reply
[00:57] <BUGabundo> I think there was some talk about it on ubuntu-devel-discuss ML
[00:57] <Turl> wii :D I made lock on lid close work :p
[00:57] <Turl> I had to enable "use_screensaver_settings"
[00:57] <Turl> and then it worked :D
[01:00] <BUGabundo> Turl: can you right about in on the wiki ?
[01:00] <BUGabundo> so future users find it ?
[01:00] <maco> s/right/write/
[01:00] <BUGabundo> thanks maco
[01:00] <BUGabundo> I should be in bed... I'm getting sicker by the minute
[01:01] <maco> so go to bed!
[01:01] <Turl> where should I write it maco?
[01:02] <maco> um....i dont know
[01:02] <maco> looking for a good page...
[01:02] <Turl> how was that syntax to do gconf editing fron the term?
[01:03] <maco> er i guess just make a page for it
[01:03] <maco> there's no page about screen lock right now
[01:04] <Turl> is there any section or something? I find the ubuntu wiki quite different :/
[01:04] <dtchen> gconftool-2 -s -t datatype /path val
[01:04] <BUGabundo> as I was saying before twitter plugin kill pidgin: I have this terrible headache! I usually don't suffer from this, so its quite annoying
[01:04] <dtchen> man gconftool-2
[01:05] <hggdh> welcome to migrane country...
[01:08] <maco> dtchen: when i wave my hand in front of your face, it means i want to talk to you
[01:10] <dtchen> maco: wait in line.
[01:11] <maco> dtchen: 1) i think this place is closing soon 2) dont you get hungry?
[01:16] <dtchen> maco: 1) not for another 44 minutes, 2) not currently
[01:23] <yesyes> is anyone having issues with firefox in jaunty? when i lauch firefox from the command line nothing happens, not even an error message and nothing appears in top/ps.
[01:24] <yesyes> the same thing happens when i run the file directly from /usr/share/firefox
[01:24] <maco> which firefox
[01:24] <maco> er
[01:24] <maco> run "which firefox"
[01:24] <yesyes> 3.0.6
[01:24] <maco> not a valid answer
[01:25] <yesyes> /usr/bin/firefox
[01:25] <maco> there we go
[01:25] <maco> ls -l /usr/bin/firefox
[01:25] <dtchen> make sure you don't have stale processes
[01:25] <maco> dtchen: firefox nowadays opens a new window in the original proc, doesnt it?
[01:26] <yesyes> that points to /usr/bin/firefox-3.0 which points to ../lib/firefox-3.0.6/firefox.sh
[01:26] <maco> ok and if you run *that*?
[01:26] <maco> maybe with -debug or whatever they offer?
[01:27] <maco> -safe-mode?
[01:27] <yesyes> one second i'm having issues with my wm...
[01:28] <yesyes> firefox.sh hangs...
[01:30] <maco> huh. you're right. even with -safe-mode
[01:30] <yesyes> weird
[01:32] <yesyes> i'm having to use epiphany now :/
[01:34] <bluefoxicy> if I upgrade what should break
[01:34] <yesyes> firefox apparently hah.
[01:35] <maco> bluefoxicy: random?
[01:35] <bluefoxicy> heh
[01:35] <bluefoxicy> 8.10 is buggy as shit anyway
[01:35] <bluefoxicy> 9.04 can't be that bad.
[01:36] <yesyes> i was having no problems with it until today
[01:37] <IdleOne> bluefoxicy, how can a "stable" release be buggy mean that the following Alpha is better?
[01:38] <bluefoxicy> IdleOne:  when the "Stable" release actively fails to recognize random hardware and breaks i.e. my iPod trying (failing) to properly encode MP3s, it's obvious somebody released an "Alpha" and forgot to actually fix the broken crap
[01:38] <bluefoxicy> this was a very sloppy release
[01:42] <yesyes> where are the 'valid language files'? opera is asking for one.
[01:44] <yesyes> nevermind; working now.
[02:21] <skyjumper> anyone able to use the android adb debugger in jaunty?
[02:39] <ali1234> skyjumper: with a real phone or the emulator?
[02:40] <skyjumper> real phone, but i got it working
[02:40] <ali1234> cool
[02:40] <skyjumper> https://bugs.launchpad.net/ubuntu/+source/udev/+bug/316215
[02:44] <unixdawg> wow jaunty works great on a p3 600 384 megs of ram
[03:49] <unixdawg> so has koffice been fixed so it does not deinstall kde4.2
[03:50] <unixdawg> last time I tried to install it i screwed up kde 4.2
[05:21] <DanaG> http://xkcd.com/543/
[05:24] <DanaG> Anything new with the jackalope today?
[05:53] <MrGoodkat_> how do i add all servers to jaunty mid?
[05:53] <MrGoodkat_> i just got the mainserver, but that one is pretty slow over here, usually i use the server for taiwan or china, but i cant choose them in jaunty
[06:25] <cwillu> oooo, uswsusp builds s2ram again
[06:26] <Tekno> btw
[06:26] <Tekno> is it possible to use uswsusp without initrd?
[06:26] <Tekno> somehow
[06:26] <cwillu> no idea, sorry
[06:28] <cwillu> why don't you have one though?  I always used them even when I built my own kernels (I've since recovered from that disorder :p)
[06:29] <Tekno> decreases boot time
[06:29] <Tekno> at least second lol :D
[06:29] <Tekno> I want under 20s ;)
[06:32] <DanaG> random: http://www.notebookreview.com/default.asp?newsID=4818&review=hp+mini+1000+mi
[06:33] <cwillu> Tekno, probably would have more luck switching the rc files over to native upstart
[06:34] <cwillu> Tekno, if you happen to be interested, I'm all for testing that :)
[06:35] <cwillu> Tekno, of course, s2both eliminates most of the remaining benefits to a quick bootup :p
[06:35] <DanaG> Good to see OEMs getting into Linux.
[06:36] <Tekno> cwillu: yea, but with slow hdd takes ages to shutdown with s2both/s2p
[06:36] <cwillu> Tekno, you're not supposed to care :p
[06:36] <Tekno> 2GB ram and SSD with 8MB/s writing speed
[06:37] <cwillu> ah, heh
[06:38] <cwillu> Tekno, although an aggressive pre-swap might mitigate that delay at the cost of most of the life of the ssd :p
[07:03] <chu_> hey, what is the general experience with SuSE here?
[07:04] <chu_> whoops
[07:12] <maco> haha
[07:12] <cwillu> E: core-utils.c: Home directory /root not ours
[07:13] <cwillu> output of /usr/lib/pm-utils/01PulseAudio
[07:13] <cwillu> and hence inhibiting
[07:13] <cwillu> but I don't see how it could work anywhere
[07:13] <maco> er...
[07:13] <cwillu> suspend from gpm is failing due to pulseaudio inhibiting it
[07:15] <maco> in jaunty right?
[07:16] <cwillu> yes
[07:16] <cwillu> maco, what parameters to sudo is your /usr/lib/pm-utils/01PulseAudio using?
[07:16] <maco> cwillu: dtchen is looking at the source code right now
[07:16] <maco> cwillu: pastebin output of: ls -l ~/.pulse*
[07:19] <DanaG> For me, PA dies every single time I resume from suspend.  Grr.
[07:19] <cwillu> maco, http://pastebin.com/f35fc1c90
[07:19] <cwillu> maco, if what I saw was actually what's in the package and not some modification I forgot about, it needs an -H
[07:20] <maco> cwillu: needs an -H?
[07:21] <cwillu> maco, sudo doesn't change $home, so pactl wouldn't be operating on the correct user
[07:21] <maco> cwillu: ok do it again -ld
[07:21] <cwillu> at least, in my case :p
[07:21] <maco> cwillu: he's trying to see ~/.pulse
[07:22] <maco> cwillu: woah i dont know what you're saying. what uses -H?
[07:22] <cwillu> maco, sorry, see the existence of it, or the contents?
[07:22] <cwillu> maco, that pastebin includes .pulse
[07:22] <maco> cwillu: the permissions on it
[07:22] <maco> cwillu: the permissions for .pulse arent there, just its contents' permissions
[07:22] <cwillu> oh, sorry :p
[07:23] <maco> cwillu: meh, he's the one that told me to tell you the wrong flag :P
[07:23] <cwillu> drwx------ 2 cwillu cwillu 4096 2009-02-14 23:21 .pulse/
[07:23] <cwillu> looks right to me
[07:23] <maco> you've puzzled him
[07:24] <cwillu> maco, the sudo lines in /usr/lib/pm-utils/01PulseAudio need to use -H to set the home directory, or they'll just read /root as cwillu (in my case), rather than /home/cwillu/...
[07:24] <cwillu> sudo doesn't change the home dir by default
[07:24] <maco> oh...
[07:25] <cwillu> and again, I don't know that this wasn't a previous screwup on my part causing me to have the wrong line in there in the first place :p
[07:25] <maco> are there multiple PA users logged in simultaneously?
[07:25] <cwillu> nope
[07:25] <maco> he says that'll only make a difference if multiple PA users are logged int
[07:25] <maco> *in
[07:25] <maco> he does agree that the -H should probably be there though
[07:26] <cwillu> maco, smack him for me :p
[07:26] <maco> my arms aren't 10 feet long, sorry
[07:26] <cwillu> it'll make a difference, it's trying to read /root as cwillu
[07:26] <cwillu> maco, that's why I keep a stick around :p
[07:26]  * cwillu smacks dtchen with a stick
[07:27] <cwillu> maco, tell him to _su_ to root, and then sudo -u <user> pactl
[07:27] <cwillu> that'll demonstrate what happens in the hook
[07:28] <maco> you mis-typed that path, right? should have a sleep.d in there? really confusing me when i try to look at the file and what you said is non-existent :P
[07:28] <cwillu> sudo -u root sudo -u <user> pactl... won't demo it, as the first sudo doesn't change the homedir away in the first place
[07:28] <cwillu> maco, ah, yes, sorry
[07:28] <cwillu> joys of typing from a stable workstation :p
[07:28] <maco> ah
[07:29] <cwillu> for my next trick:  /usr/lib/pm-utils/sleep.d/95hdparm-apm resume suspend: /usr/lib/pm-utils/sleep.d/95hdparm-apm: line 26: get_power_status: command not found
[07:29] <cwillu> and I know I didn't muck with that one :p
[07:30] <DanaG> wait, is pm-utils doing something with PulseAudio?
[07:31] <cwillu> DanaG, of course :p
[07:31] <maco> cwillu: he says theoretically the -H should only matter with multiple users, but you must be hitting a race condition. if it wasnt a race condition, we'd all hit it
[07:31] <cwillu> DanaG, check /var/log/pm-suspend.log
[07:31] <cwillu> maco, he's wrong, frankly :p
[07:31] <cwillu> afaik
[07:32] <DanaG> Lately, my system has failed to even try to suspend.
[07:32] <cwillu> unless pactl is inventing its own home dir string
[07:32] <DanaG> I hit sleep, and the screen locks... and that's it.
[07:32] <maco> cwillu: i think its something to do with the loops...
[07:32] <maco> oh brb. im going to try to induce a kernel panic now.
[07:32] <DanaG> Yet, sudo /etc/acpi/sleep.sh --force works fine.
[07:32] <cwillu> maco, ask him if pactl should _ever_ work with $home set to somebody elses homedir
[07:33] <DanaG> I am using the PA 0.9.15, though.
[07:35] <cwillu> maco, i.e., how is pactl supposed to find /home/cwillu/.pulse if the homedir is /root, as it will always be with an unadorned sudo -u?
[07:36] <ltsmooth42> i remember i used to be able to press alt-f2 to bring up a run window.  was this removed or was the key replaced?  i'm referring to gnome
[07:37] <cwillu> ltsmooth42, doesn't work here anymore either
[07:37] <cwillu> shortcut is still set correctly
[07:37] <cwillu> DanaG, can you pastebin /var/log/pm-suspend.log?
[07:37] <DanaG> Not in Linux right now, but I'll give it a try tomorrow.
[07:37] <maco> cwillu: only a couple people have hit this bug. it actually was in hardy
[07:39] <ltsmooth42> maco: it worked for me in hardy
[07:39] <ltsmooth42> i lvoe the run dialog
[07:39] <cwillu> maco, okay?  it's still wrong :p
[07:39] <maco> ltsmooth42: yeah me too
[07:39] <maco> cwillu: right, but depending on the race you may/may not hitit
[07:40] <cwillu> maco, uh?
[07:40] <cwillu> maco, which, pactl not finding my home dir?
[07:40] <maco> yeah
[07:40] <cwillu> maco, why is pactl doing anything beyond reading $home?
[07:41] <maco> cwillu: can be multiple instances of pulse running if multiple users use it
[07:41] <maco> so it tries to go through a list and kill it for all of them
[07:41] <cwillu> maco, yes, but _that_ list is right
[07:41] <ltsmooth42> but other than the missing run dialog i've been using 9.04 rather than 8.04
[07:41] <cwillu> it's returning cwillu
[07:41] <cwillu> maco, but sudo -u cwillu won't change $home, ever
[07:41] <maco> so for multiple users, hitting that bug should be *very* easy. for only one, it'd be uncommon, but possible
[07:41] <cwillu> su sudo -u cwillu will always have home set to /root, for instance
[07:42] <cwillu> maco, I only have one user logged in
[07:42] <maco> *shrug* there's some suid stuff happening in there too though. if you look at core-util.c you see that
[07:42] <dtchen> cwillu: it's libpulse0 via src/pulsecore/core-util.c, and it's a race between what getuid() returns and what sudo tells it
[07:43] <maco> yay youre here to explain what i cannot
[07:43] <cwillu> yay :)
[07:43] <dtchen> i've already fixed it in bzr
[07:43] <maco> cwillu: thats a hint to go test his branch
[07:43] <maco> and giv efeedback, of course
[07:45] <cwillu> I'm sorry :p
[07:45] <cwillu> dtchen, is there any reason why it should be reading anything but the ~/.pulse?
[07:45] <cwillu> beyond a system daemon
[07:47] <dtchen> cwillu: yes, the state needs to be stored
[07:47] <dtchen> (unless your question is cleverly asking something else)
[07:48] <cwillu> dtchen, why should ever try to read /root/.pulse if I'm not running as root?
[07:48] <cwillu> is what I'm asking :)
[07:48] <dtchen> it shouldn't
[07:49] <cwillu> it will, every time
[07:49] <cwillu> unless sudo -H is used
[07:49] <cwillu> you follow what I'm saying?
[07:49] <dtchen> no, it depends what $HOME is when sudo is invoked
[07:50] <cwillu> which will be /root
[07:50] <cwillu> in those hooks
[07:50] <dtchen> it didn't crop up in SRU testing
[07:51] <cwillu> dtchen, the pm-utils hooks will be run as root, $home won't be set to the user
[07:52] <dtchen> cwillu: i'm not contesting that
[07:52] <cwillu> so, when you sudo -u cwillu _in_ one of those hooks, it'll be reading /root/.pulse, right?
[07:52] <cwillu> (which it does)
[07:52] <cwillu> (on my systems at least)
[07:52] <dtchen> it doesn't here.
[07:53] <cwillu> how could it not?
[07:53] <dtchen> I don't even have /root/.pulse*
[07:53] <cwillu> trace it, I bet it's trying to read /root/.pulse, failing, and then falling back on whatever mechanism
[07:54] <pwnguin> anyone feel like playing a game (in the name of bug hunting)?
[07:54] <dtchen> perhaps, but i don't have the resources to do so ATM; there are a billion other bugs i need to fix
[07:54] <cwillu> dtchen, just put a -H in the sudo line, and I'll huggle you forever
[07:55] <cwillu> or I'll promise to stop huggling, if you would prefer
[07:55] <dtchen> 02:43 < dtchen> i've already fixed it in bzr
[07:55] <maco_> figures. i hibernate to induce a kernel panic so i can take a picture of it, but it's gone in -7-generic. then, while i'm running just fine, it panics as soon as i move the mouse.
[07:55] <pwnguin> bug #261189
[07:56] <pwnguin> it's probably closed but i dont have 3d to test with in jaunty =/
[08:01]  * DanaG is glad to have serial-over-LAN.
[08:01]  * DanaG has one major gripe about "radeon" over fglrx: it uses way too damn much power to not accelerate anything.
[08:01] <DanaG> I'm talking 30 watts on battery.
[08:01] <DanaG> fglrx+compiz == 19 watts for whole system....
[08:02] <DanaG> ... radeon + metacity == 30 watts!
[08:02] <DanaG> It's already aged my battery (that is, reduced actual max capacity!) by 10 minutes (judged in Windows).
[08:02] <pwnguin> but they have documentation!
[08:02] <DanaG> Yeah, I still don't regret ATI hardware...
[08:03] <pwnguin> i mean, ati released docs and now their video cards only render rainbows and cure cancer
[08:03] <DanaG> ... I just wish they'd implemented powerplay even bEFORE releasing 3D specs.
[08:03] <DanaG> To me, not KILLING my battery (30 watts!) is worth more to me than having 3D acceleration.
[08:04] <DanaG> It's like redlining your engine... while coasting downhill... in neutral.
[08:05] <SwedeMike> wow, I just checked powertop, pulseaudio is doing 600 wakeups per second total.
[08:05] <pwnguin> seriously though, if someone can test rrootage gigawing 9a for segfaults, that'd be good
[08:06] <pwnguin> SwedeMike: i always get rescheduling interrupts
[08:06] <SwedeMike> when I ran 8.10, I used to total around 100-150 per second total for the whole system
[08:06] <DanaG> I also have this other issue in Intrepid: can't use fglrx versions newer than 8.543.
[08:06] <SwedeMike>   24.7% (320.9)        pulseaudio : common_timer_set (posix_timer_fn)
[08:06] <SwedeMike>   24.4% (318.0)        pulseaudio : schedule_hrtimeout_range (hrtimer_wakeup)
[08:07] <dtchen> SwedeMike: it'll get better in the next upload [at the expense of disabling glitch-free globally]
[08:07] <maco_> SwedeMike: even in jaunty?
[08:07] <SwedeMike>   17.0% (221.4)       <interrupt> : extra timer interrupt
[08:07] <dtchen> maco_: yes, it's worse in jaunty
[08:07] <SwedeMike> maco_: my figures pasted here is fram jaunty, 8.10 had 100-150 /s, jaunty does 800/s
[08:07] <maco_> dtchen: when i made that complaint on hardy, you said new versions of pulse fix it...
[08:07] <maco_> or was it my sound driver that was waking up in hardy?
[08:08] <dtchen> maco_: glitch-free is way more expensive on BROKEN HDA codecs
[08:08] <maco_> oh right
[08:08] <dtchen> there are only a handful of GOOD HDA codecs
[08:08] <maco_> SwedeMike: so what he's saying, is your hardware sucks
[08:08] <maco_> he was saying this to me yesterday
[08:08] <maco> cant type
[08:09] <SwedeMike> maco_: mkay, but why did it get worse from 8.10 ?
[08:09] <maco> SwedeMike: 9.04 has glitch-free PulseAudio
[08:09] <maco> which is great when your hardware's not crappy
[08:09]  * DanaG happens to have a good HDA codec, it seems.
[08:09] <pwnguin> 5.5% ( 15.1)      <kernel IPI> : TLB shootdowns
[08:09] <maco> when your hardware *is* crappy, the driver and pulseaudio start freaking out
[08:09] <SwedeMike> oki, this is centrino2... so I guess a lot of people will be in trouble then
[08:09] <pwnguin> 24.6% (180.5)      <kernel IPI> : Rescheduling interrupts
[08:09] <DanaG> And at least fglrx doesn't make audio breakkkkkkkkkkkkkkkkkkkkkk up like that when closing the laptop lid, like nvidia did.
[08:09] <maco> centrino means your wireless card and cpu
[08:09] <maco> not your sound card
[08:09] <SwedeMike> 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
[08:10] <maco> yeah that doesnt mean anything either
[08:10] <DanaG> It used to get stuck in a loop likikikikikikikikikikikikike this.
[08:10] <maco> thats what a large portion of HDA say
[08:10] <maco> lspci -nv | grep -A 1 0403
[08:10] <maco> thatll tell you the specific HDA card you've got
[08:10] <maco> but its really the codec that matters
[08:10] <SwedeMike> :~$ lspci -nv | grep -A 1 0403
[08:10] <SwedeMike> 00:1b.0 0403: 8086:293e (rev 03)
[08:10] <SwedeMike> 	Subsystem: 17aa:20f2
[08:10] <maco> which is somewhere in /proc that i cant type from memory
[08:11] <SwedeMike> this is a thinkpad X200
[08:11] <maco> basically all the junk that alsa-info.sh matters
[08:11] <maco> and the way the sound chip is integrated into the motherboard can cause breakage too
[08:11] <pwnguin> probably /proc/asound/Intel
[08:11] <maco> dtchen: do i sound enough like you yet?
[08:12] <SwedeMike> ~$ cat /proc/asound/Intel/codec#0  | grep -i codec
[08:12] <SwedeMike> Codec: Conexant CX20561 (Hermosa)
[08:12] <SwedeMike> this one?
[08:13] <maco> uh huh
[08:13] <dtchen> it's preferable to use awk '/^Vendor/ {print $3}' /proc/asound/card*/codec*
[08:13] <SwedeMike> 0x14f15051
[08:13] <maco> you like the digits better than the words?
[08:14] <maco> well then again, i guess youve got those memorized
[08:20] <pwnguin> anyone else notice a goofy font kerning?
[08:20] <cwillu> pwnguin, screenshot?
[08:20] <pwnguin> gimme a sec
[08:20] <maco> in what? if firefox or OOo, they both do their own "special" things to fonts
[08:21] <cwillu> I'm just rebooting, so I may see it in a sec
[08:21] <pwnguin> anything with a v, in gnome
[08:21] <pwnguin> and firefox
[08:21] <maco> v?
[08:21] <pwnguin> the letter
[08:21] <cwillu> avythivg?
[08:22] <pwnguin> except for fixed width (duh)
[08:22] <cwillu> looks fine here
[08:22] <cwillu> I'm not in fixed width here :p
[08:23] <maco> all apps that have names that use the letter v have bad kerning? but apps like "nautilus" which lack a v are fine?
[08:25] <pwnguin> http://people.cis.ksu.edu/~jld5445/av-kerning.png
[08:26] <pwnguin> comprende?
[08:26] <cwillu> interesting
[08:26] <maco> oh
[08:26] <maco> the title font is fine...it looks like the letters are just being mashed against each other
[08:27] <pwnguin> ...
[08:27] <cwillu> DVD is fine
[08:27] <pwnguin> just lowercase v
[08:27] <maco> well the title font is bold
[08:27] <cwillu> Caravanacid is fine
[08:27] <maco> so not-bold lowercase v's?
[08:27] <cwillu> what font do you have it set to??
[08:27] <cwillu> (one ?, typo)
[08:27] <pwnguin> caravanacid is not fine in the playlist and window picker
[08:28] <pwnguin> "Sans"
[08:29] <pwnguin> i think capital J is also screwy
[08:37] <pwnguin> maybe it's just something to do with nouveau and dpi
[09:39] <ziroday> hmph why is apport not working
[09:52] <DanaG> Heh, gotta' love what Asus puts in their DMI strings:
[09:52] <DanaG> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/327267
[09:53] <DanaG>  Manufacturer: "System manufacturer"     Product Name: "System Product Name"     Version: "System Version"   Serial Number: "System Serial Number"
[09:53] <DanaG> Yes, their serial number is, quote, "System Serial Number".
[09:56] <Alexia_Death> Sombody failed to change manufacturers defaults
[09:59] <DanaG> =P
[11:01] <Alexia_Death> Anybody else have roblems with pulseaudio session not starting when they log into kde?
[11:02] <asraniel> anybody knows how to change the current time in kubuntu? i get an error about the timeserver when changing the time in system settings
[11:02] <Alexia_Death> asraniel: you need to correct the timezone?
[11:04] <asraniel> Alexia_Death: hm, i'll test. but the error is a bug anyway. i should be able to set the time manualy, without needing a timeserver (which i can't)
[11:06] <Alexia_Death> asraniel: you are right
[11:07] <Alexia_Death> theres more than one bug
[11:07] <Alexia_Death> if i set it to timeserver it still fails to contact it.
[11:07] <gnomefreak> Alexia_Death: did you set PA to be used by default?
[11:08] <Alexia_Death> gnomefreak: havent set it but It used to be. And it is my first option in audi pefs
[11:08] <gnomefreak> Alexia_Death: kde doesnt use PA by default
[11:08] <Alexia_Death> it used to at some point
[11:08] <gnomefreak> try https://wiki.ubuntu.com/PulseAudio
[11:09] <Alexia_Death> Ok thanks
[11:09] <gnomefreak> np
[11:09]  * gnomefreak gone again trying to finish this today
[11:09] <Alexia_Death> Ive made phonon use pulseaudio because I have BT headset and pulseaudio seems to be the only way to sanely manage it
[11:45] <Wicla> Are there any reasons why public keys get obsolete after each update?
[11:45] <Wicla> Agent admitted failure to sign using the key. when trying to connect to a host with public key auth
[12:30] <tretle> jaunty alpha 4's installer is crashing on the partitioning step, instead staying on the greyed out Keyboard setup stage. Is this a known issue with the live cd?
[13:39] <skyjumper> is openoffice freezing on startup for anyone else on jaunty amd64?
[13:44] <skyjumper> nevermind
[13:45] <ikonia> ok
[13:48] <Ienorand> If I have provided the information requested on a bug should I change status from incomplete to new, or should I leave that up to the triager?
[13:48] <ikonia> Ienorand: I'd leave it for the guy it's assigned to
[13:48] <ikonia> Ienorand: he'll be notified that you've applied an update
[13:49] <Ienorand> ikonia: okies
[14:55] <BUGabundo> is any one here able to run Guest Session WITHOUT compiz being on?
[15:44] <miik> Feb 15 16:37:24 darkstar pulseaudio[5955]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0.
[15:44] <miik> Feb 15 16:38:32 darkstar pulseaudio[5955]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0.
[15:44] <miik> Feb 15 16:38:50 darkstar pulseaudio[5955]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0.
[15:46] <BUGabundo> miik: what app is doing that?
[15:48] <miik> i dont know.. im listening to music in rhythmbox.. and i see this pulseaudio error messages in syslog
[15:50] <BUGabundo> ahh
[15:50] <BUGabundo> please report on LP
[15:51] <miik> ok
[15:51] <BUGabundo> use the alsa test script to collect extra details
[15:51] <BUGabundo> and use apport to gather pa info
[15:51] <BUGabundo> $ apport-cli -fp pulseaudio
[15:51] <BUGabundo> also mark RB as part of the bug
[15:57] <miik> what is RB ?
[15:59] <BUGabundo> rhythmbox
[16:00] <BUGabundo> miik: http://www.alsa-project.org/alsa-info.sh
[16:00] <BUGabundo> alsa script for data collention
[16:00] <BUGabundo> bbl
[16:11] <maxb> miik: you seem to have filed the bug twice
[16:13]  * maxb marks as duplicate
[16:40] <tretle>  Hey, seems something went horribly wrong during an installation, ubuntu has rewrote things it shouldnt have and now the hard drive in my laptop is unable to have the partitions removed or rewrote to. Does anyne know of a good disk scrubber on the live cd I can use?
[16:53] <miik> maxb, yeah, i did
[16:53] <miik> first normal, then i saw i could use apport, so i did that after
[17:18] <Ienorand> Hello, anyone else here running Jaunty in vmware?
[18:10] <Commie_Cary> dose ATI support 9.04 yet
[19:28] <Fly-Man-> Morning :)
[19:28] <BUGabundo> afternoon
[19:29] <Fly-Man-> How can I get Jaunty latest kernel ?
[19:29] <Fly-Man-> Installing Jaunty on VMware
[19:29] <Fly-Man-> and now the Vmware tools needs some additional stuff that's not in the kernel I have now
[19:30] <BUGabundo> what kernel do you have?
[19:30] <BUGabundo> Linux blubug 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:42:34 UTC 2009 x86_64 GNU/Linux
[19:30] <Fly-Man-> 2.6.28-3-server
[19:30] <BUGabundo> update-manager -d does anything?
[19:30] <fosco_> Fly-Man-: sudo aptitude update && sudo aptitude dist-upgrade
[19:30] <BUGabundo> or if no GUI do-release-upgrade
[19:30] <fosco_> as always
[19:31] <BUGabundo> fosco_: sure
[19:31] <BUGabundo> or sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade
[19:34] <Fly-Man-> fosco_, BUGabundo, thanks :)
[19:34] <Fly-Man-> That worked :)
[19:34] <BUGabundo> plain upgrade WILL NOT upgrade kernel
[19:34] <BUGabundo> you need dist-upgrade
[19:34] <Fly-Man-> Yeah, so I noticed :)
[19:34] <fosco_> development versions are not recommended for newbies
[19:34] <Fly-Man-> fosco_, trust me ;)
[19:34] <fosco_> make sure what you're doing
[19:34] <Fly-Man-> No newbie here :p
[19:34] <fosco_> ok
[19:35] <Fly-Man-> but VmWare newbie
[19:35] <Fly-Man-> and it asks for some stuff that for some reason aren't installed standard in this kernel
[19:36] <Fly-Man-> ANy news on the release of Jaunty for public ?
[19:36] <Fly-Man-> Still March ?
[19:36] <BUGabundo> april
[19:36] <BUGabundo> as always
[19:36] <BUGabundo> why would it change?
[19:36] <BUGabundo>  !release
[19:37] <Fly-Man-> Linux testgrid 2.6.28-7-server #20-Ubuntu SMP Mon Feb 9 16:33:23 UTC 2009 i686
[19:37] <Fly-Man-> And that's the one :)
[19:37] <Fly-Man-> Thanks for the help :)
[19:39] <IntuitiveNipple> Anyone else been seeing lock-ups requiring a power cycle after it has been left idle for several hours? I've just returned to the PC after 8 hours and within seconds of moving the mouse it 'froze' - initially responded to SyReq+K but VT7 didn't restart gdm as expected. Was able to SysReq+S to sync disks but then it wouldn't honour SysReq-O to turn off.
[19:39] <IntuitiveNipple> This is the 2nd or third time I've seen it happen
[19:41] <BUGabundo> IntuitiveNipple: GPM bug? ACPI? suspend/resume bug?
[19:41] <IntuitiveNipple> no way to tell, so far.
[19:41] <BUGabundo> do you have your PC to hibernate after 8h?
[19:41] <IntuitiveNipple> no, it just sits idle on the desk.
[19:41] <BUGabundo> try this https://wiki.ubuntu.com/KernelTeam/SuspendResume
[19:42] <BUGabundo> and https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting
[19:42] <IntuitiveNipple> BUGabundo: yes thanks, I know..... I'm on the ACPI kernel team  :)
[19:42] <BUGabundo> BTW EVERYONE here, please test this and report on the wiki (and LP if it fails)
[19:42] <IntuitiveNipple> I'm asking if anyone else is experiencing similar in case it is not just a local issue
[19:42] <BUGabundo> ehheh
[19:42] <BUGabundo> I did not know that
[19:43] <BUGabundo> just trying to help
[19:43] <IntuitiveNipple> Looking back through the logs, I have just found evidence of a gdm startup script error in .xsession-errors:
[19:43] <IntuitiveNipple> 4096): [: 402: 4096: unexpected operator
[19:43] <IntuitiveNipple> [: 402: 4096: unexpected operator
[19:43] <BUGabundo> I've seen boards that try to "save" energy
[19:43] <IntuitiveNipple> Looks like someone missed some spaces out of a test [ ... ] condition there
[19:43] <BUGabundo> but then software doesn't know about that and FAIL
[19:44] <ronny> IntuitiveNipple: nothing here, left for skying the whole day, worked fine when i got back
[19:44] <IntuitiveNipple> BUGabundo: Yeah, and it could be related to the nvidia 180.29 driver since it has a bunch of other issues right now.
[19:44] <ronny> hmm
[19:44] <ronny> i got 4gb of ram sitting around, anyone aware of a service that pre-caches apps like firefox, OOO and others
[19:44] <IntuitiveNipple> ronny: That's the thing, an issue like this, unless several people have it and you can determine a common scenario, there's no 'bug' as such that is defined enough to report :)
[19:45] <IntuitiveNipple> I tend to think it is an Xorg issue just from the 'feel' of it when it occurs.
[19:45] <IntuitiveNipple> I had it happen with the 'nv' driver too, I've just realised.
[19:45] <IntuitiveNipple> sreadahead should be helping with that kind of thing
[19:45] <BUGabundo> IntuitiveNipple: test table: recovery consolse: let it seat there all night
[19:45] <BUGabundo> that would eliminate HW
[19:46] <BUGabundo> or leave it running memtest
[19:46] <ronny> IntuitiveNipple: sreadahead?
[19:46] <BUGabundo> RightNow (TM) my laptop is doing a great job with hibernate and resume
[19:46] <BUGabundo> works great
[19:47] <BUGabundo> still I get a fail to poweroff one in 10
[19:47] <BUGabundo>  !info sreadahead
[19:47] <BUGabundo> !info sreadahead
[19:47] <IntuitiveNipple> http://code.google.com/p/sreadahead/
[19:48] <ronny> IntuitiveNipple: i dont have a solid state disk
[19:49] <BUGabundo> !info uswsusp
[19:49] <IntuitiveNipple> Doesn't have to be SSD
[19:49] <BUGabundo> any body here using uswsusp ?
[19:49] <BUGabundo> I really like the timed count down
[19:49] <IntuitiveNipple> nope
[19:49] <ronny> IntuitiveNipple: and it requires a kernel patch in order to work only with ext3?
[19:49] <BUGabundo> but many devs don't like it!
[19:49] <Tekno> im using uswsusp
[19:49] <siegie> BUGabundo: long time ago in gutsy, but at the moment default suspend is working fine for me
[19:50] <IntuitiveNipple> ronny: We've work underway to include it
[19:51] <ronny> IntuitiveNipple: anyway, i dont want to optimize boot itself, but application startup
[19:51] <BUGabundo> I use it' cause it used to help fix hibernate
[19:51] <BUGabundo> I'll have to try standard hibernate again
[19:51] <BUGabundo> but I'll miss the compress image!
[19:51] <BUGabundo> it makes a really big diff when resuming
[19:52] <RAOF> ronny: The "preload" daemon might be what you're after.
[19:53] <Tekno> preload is cool
[19:53] <Tekno> [Sun Feb 15 21:53:07 2009] readaheading 2306 files
[19:53] <Tekno> ;)
[19:53] <ronny> nice
[19:54] <Q-FUNK> howdy!  anybody using Skype on Jaunty?  was working fine on Intrepid with a couple of minor tweaks to the PA deamon.conf but not anymore.
[19:54] <ronny> yay, thats what i just need :)
[19:55] <BUGabundo> Q-FUNK: I have it working
[19:55] <BUGabundo> on 64 bits
[19:55] <BUGabundo> but not webcam
[19:55] <Q-FUNK> ok.  here, the sound skips horribly.  it was rock-solid on  intrepid.
[19:56] <BUGabundo> audio is a bit touch and go... either it works, either it doesn'tI'm using PA 9.15 test2 from themuso PPA
[19:56] <Q-FUNK> ah, ok
[19:56] <Q-FUNK> url?
[19:56] <BUGabundo> why don't you try it too?
[19:56] <Q-FUNK> or rather, deb and deb-src lines?
[19:56]  * BUGabundo does skype work ok with any verion of PA?
[19:56] <Q-FUNK> BUGabundo: it works fine with the one from intrepid
[19:57] <BUGabundo> https://launchpad.net/~themuso/+archive
[19:57] <BUGabundo> remember this is TEST!
[19:57] <BUGabundo> please report all bugs
[19:57] <BUGabundo> jaunty will not ship 9.15, only 9.14 plus a few patchs from upstream
[19:58] <Q-FUNK> ah.  the PA guys were under the impression that jaunty would ship with 0.9.15
[19:59] <BUGabundo> nope
[20:00] <ronny> hmm
[20:01] <ronny> i'll have to fix my sound
[20:01] <ronny> beeps on terminals suddenly work, but everything else doesnt
[20:01] <ronny> im completely puzzled
[20:13] <BUGabundo> ronny: try killing PA and restarting it
[20:13] <BUGabundo> pulseaudio -k ; start-pulseaudio-x11
[20:30] <DanaG> grr, keyboard stops working on resume from suspend.
[20:30] <DanaG> [37113.822205] (EE) device key_bitmask has changed
[20:30] <DanaG> [37113.822297] (EE) AT Translated Set 2 keyboard: Device has changed - disabling.
[20:31] <DanaG> Device has changed, so now I can't use it at all?  Where's the sense in that?
[20:31] <DanaG> If it's changed... then so what?
[20:31] <BUGabundo> anybody here using https://help.ubuntu.com/community/Medibuntu repos?
[20:31] <BUGabundo> they don't show up on synaptic
[20:32] <BUGabundo> and apt-cache policy of installed packages show them as LOCAL packages and not a repo
[20:32] <martijn81> when will ktorrent 3.2 come out for jaunty?
[20:33] <martijn81> it is just released
[20:33] <DanaG> !info gnump3d
[20:34] <andersk> BUGabundo: works for me.
[20:34] <DanaG> !info gnump3d intrepid
[20:34] <DanaG> !info gnump3d hardy
[20:35] <Commie_Cary> dose ATI support 9.04 yet
[20:37] <BUGabundo> andersk: http://paste.ubuntu.com/118583/
[20:39] <andersk> I see "500 http://packages.medibuntu.org jaunty/free Packages" on that.  Did you `aptitude update`?
[20:39] <Commie_Cary> dose ATI support 9.04 yet
[20:40] <DanaG> Nopez.
[20:41] <BUGabundo> of course
[20:41] <BUGabundo> it seems that it isn't feching some packages
[20:41] <BUGabundo> 'cause im on amd64
[20:41] <BUGabundo> discussing on #medibuntu
[20:42] <nsp_cli> hi all - i asked this question a day or two ago
[20:42] <nsp_cli> i'm having some trouble getting the latest (netinst) jaunty to install on my macbook
[20:42] <nsp_cli> it dies during "select and install packages"
[20:42] <nsp_cli> with this error:
[20:42] <nsp_cli> http://paste.ubuntu.com/117932/
[20:42] <nsp_cli> any thoughts?
[20:44] <nsp_cli> maco previously mentioned that "there was new mono stuff yesterday that hasnt been straightened out" ?
[20:46] <ronny> BUGabundo: didnt work
[20:47] <RAOF> nsp_cli: There's still some new mono stuff that hasn't been straightened out.  f-spot and tomboy are currently not simultaneously installable.
[20:47] <nsp_cli> raof: thanks - in the installer, can i specifically avoid those packages?
[20:48] <nsp_cli> using the netinst cd?
[20:48] <RAOF> I didn't know we _had_ a netinst CD :)
[20:48] <RAOF> And, no.  I don't think so.
[20:48] <nsp_cli> hahah
[20:48] <nsp_cli> hm ...
[20:48] <RAOF> You _could_ do a server install, which won't install X or any of that stuff, and then install ubuntu-desktop later.
[20:48] <nsp_cli> ah, ok
[20:49] <nsp_cli> i'll give that a shot
[20:49] <nsp_cli> if that fails, is there an alpha3 image floating around somewhere?
[20:49] <nsp_cli> [on an unrelated note, the alpha 4 installer hangs my macbook pro]
[20:51] <BUGabundo> nsp_cli: and a daily?
[20:51] <nsp_cli> BUGabundo: what?
[20:51] <nsp_cli> the dailys don't cause any problems ... just the alpha4 alternative amd-64 image hangs my machine
[20:52] <nsp_cli> and i'm 99.99% sure the media is fine
[20:52] <BUGabundo> then it is now fixed
[20:53] <BUGabundo> as just on A4
[20:53] <nsp_cli> k
[20:54] <DanaG> ftp://ftp.hp.com/pub/softlib/software10/COL25940/dennis-stable-install-usb-gm-1.img  -- that's the HP thingy.
[21:55] <DanaG> Anyone know how to make a fake USB storage device that exists on my host, so I can boot a VM from it?
[21:55] <DanaG> It's an image that refuses to boot from anything other than USB.
[22:00] <IntuitiveNipple> DanaG: You could use the USB gadget driver
[22:03] <DanaG> Hmm, how do you do that?
[22:04] <tretle> hi, I am having problems after installing on my laptop
[22:04] <tretle> I cant delete or repartition the drive from any ubuntu version now or even a windows cd
[22:04] <tretle>  unable to open /dev/scd0 - unrecognised disk label. Input/output error during write on /dev/sda
[22:11] <thomasdelbeke> Hi there
[22:11] <thomasdelbeke> http://paste.ubuntu.com/118604/
[22:12] <andersk> Does that UUID show up in the output of `ls -l /dev/disk/by-uuid`?
[22:13] <thomasdelbeke> no
[22:13] <thomasdelbeke> I am now in intrepid
[22:14] <thomasdelbeke> I can no longe access jaunty
[22:14] <thomasdelbeke> display problem
[22:14] <thomasdelbeke> I could install
[22:14] <thomasdelbeke> booted into it
[22:14] <thomasdelbeke> updated
[22:14] <thomasdelbeke> then got a display error
[22:15] <thomasdelbeke> http://paste.ubuntu.com/118607/
[22:16] <andersk> Sounds like you need to update your /etc/fstab.
[22:16] <thomasdelbeke> how?
[22:16] <thomasdelbeke> update-mod?
[22:16] <thomasdelbeke> I had errors previously
[22:16] <thomasdelbeke> with fsck
[22:16] <thomasdelbeke> in alfa 3
[22:17] <andersk> Do you know what caused this to start happening?  And can you pastebin your current /etc/fstab?
[22:17] <thomasdelbeke> I also installed 9.04 on ext4
[22:17] <andersk> That might be it.  Upgrading a filesystem to ext4 changes its UUID.
[22:18] <thomasdelbeke> http://paste.ubuntu.com/118611/
[22:18] <thomasdelbeke> no,
[22:19] <thomasdelbeke> i have jaunty on a seperate partition
[22:19] <andersk> Oh I see; you have two entries for /media/sda4 in your /etc/fstab.
[22:19] <thomasdelbeke> yes
[22:20] <andersk> You probably need to comment out the second one (7419...).
[22:21] <thomasdelbeke> and then I can access jaunty again?
[22:21] <thomasdelbeke> intrepid is the ext3
[22:22] <thomasdelbeke> I am running gpart /dev/sda
[22:22] <thomasdelbeke> it is ridiculously slow
[22:25] <thomasdelbeke> http://paste.ubuntu.com/118614/
[22:25] <thomasdelbeke> Sorry
[22:25] <thomasdelbeke> was a bit confused there
[22:25] <thomasdelbeke> anyway
[22:26] <thomasdelbeke> I have commented out the excess entry
[22:26] <thomasdelbeke> Is it normal that gpart won't work
[22:26] <thomasdelbeke> when having this problem
[22:27] <thomasdelbeke> I will try and reboot now
[22:36] <thomasdelbeke> Hi there
[22:36] <thomasdelbeke> Anyone still there?
[22:37] <Tekno> no
[22:37] <thomasdelbeke> Commenting out as prescribed worked
[22:37] <thomasdelbeke> ok
[22:37] <thomasdelbeke> You neither?
[22:37] <Tekno> me neither
[22:37] <thomasdelbeke> Come back tomorrow?
[22:38] <Tekno> maybe tomorrow
[22:38] <ikonia> ?
[22:38] <thomasdelbeke> hmm
[22:38] <thomasdelbeke> ??
[22:40] <thomasdelbeke> So anyway, just wanted to say there are serious display problems witcht acer aspire 9410 in jaunty
[22:41] <thomasdelbeke> I cannot log into it, after updating
[22:41] <thomasdelbeke> cheers, thomas
[23:06] <bazookatooth> i have one issue left w/ jaunty.... my login sound is god awful now. all other sound playback is flawless.. but the login sound is crackly and garbled.. sounds terrible. what gives?
[23:10] <IntuitiveNipple> there's some alsa reports in the logs I noticed