[00:41] <terli> *coughs silently*
[00:41] <terli> I just upgraded to kernel ~9 on a whim.
[00:42] <terli> My sound is shot.
[00:42] <crimsun> ~9?
[00:43] <terli> the latest revision.
[00:43] <crimsun> 2.6.28-4.9?
[00:43] <terli> I erm, ran 'pulseaudio in a terminal and it says I'm not in pulse-rt, whatever that means
[00:43] <crimsun> irrelevant
[00:44] <terli> yes, 2.6~~9
[00:44] <crimsun> first, you need to be running *current* jaunty
[00:44] <terli> I am.
[00:44] <terli> everything updated.
[00:44] <terli> two reboots.
[00:44] <crimsun> as of 5 minutes ago?
[00:44] <terli> as of 20.
[00:44] <crimsun> ok, good. now run http://www.alsa-project.org/alsa-info.sh (bash)
[00:44] <terli> thx.
[00:46] <terli> http://www.alsa-project.org/db/?f=a18500574c8afce9076ca7a491668feb7c5b1e81
[00:46] <terli> um, pulsaudio...
[00:47] <terli> care to give me a very very short technical rundown on how alsa fits into the new pulseaudio thingy?
[00:47] <crimsun> sound hardware -> kernel (alsa-kernel/driver) -> alsa-lib -> pulseaudio
[00:48] <crimsun> see my presentation if you want more detail
[00:48] <terli> that's detailed enough
[00:48] <crimsun> anyhow, so your volume settings look, unsurprisingly, like they're muted and/or zeroed
[00:49] <crimsun> take a look at 'PCM', mainly
[00:49] <terli> I'm on a laptop
[00:50] <terli> I am pressing the "mute" multimedia key and it's not toggling
[00:50] <crimsun> depending on your vendor, you may need also to unmute and increase 'Headphone' and 'Master Mono'
[00:50] <terli> I mean, it is, but it's doing it twice.
[00:50] <crimsun> that's a completely different problem. one problem at a time, please.
[00:50] <crimsun> right now, your sound is inaudible because the volumes are muted and zeroed. you should fix that.
[00:51] <terli> *looks*
[00:51] <crimsun> i.e., amixer -Dhw:0 set 'PCM' 80% && amixer -Dhw:0 set 'PCM' unmute
[00:51] <terli> did there used to be a way to get at it on the menu?
[00:52] <terli> ran it anyway.
[00:52] <crimsun> yes, use the speaker icon (mixer_applet) in the notification area
[00:52] <terli> not really having any affect. output and "applications I'm afraid.
[00:52] <terli> Mono:
[00:52] <terli>   Front Left: Playback 25 [81%] [3.00dB] [off]
[00:52] <terli>   Front Right: Playback 25 [81%] [3.00dB] [off]
[00:53] <terli> and then...
[00:53] <terli> it puts out the exact same thing
[00:53] <terli> only it says on.
[00:53] <terli> but, I still can't hear anything, just so you know.
[00:54] <crimsun> did you also set 'Headphone' and 'Master Mono'?
[00:55] <terli> I don't have those.
[00:55] <crimsun> i assure you that you do. the volume applet may not expose them by default, but you definitely have them.
[00:55] <terli> that is probably the case.
[00:56] <terli> found it
[00:57] <terli> well, I think I found it. I'm selecting master mono but...it's not having any effect.
[00:58] <terli> I mean, I'm selecting it, pressing close, opening volume control and it's not doing anything different.
[00:58] <crimsun> pastebin your `amixer -Dhw:0'
[00:59] <terli> http://pastebin.com/m10fd451a
[01:00] <crimsun> 'Master Mono' and 'Headphone' are still muted
[01:00] <terli> right.
[01:00] <crimsun> please unmute those first, then try muting 'External Amplifier'
[01:00] <terli> by?
[01:01] <crimsun> you can use gnome-alsamixer, alsamixer -Dhw:0, amixer -Dhw:0 set ..., ...
[01:01] <crimsun> e.g., amixer -Dhw:0 set 'Master Mono' unmute && amixer -Dhw:0 set 'Headphone' unmute && amixer -Dhw:0 set 'External Amplifier' mute
[01:01] <terli> its ok
[01:02] <terli> getting alsamixer now
[01:02] <crimsun> alsamixer or gnome-alsamixer?
[01:02] <terli> gnome-
[01:02] <crimsun> the former is already installed; it's part of the alsa-utils package.
[01:04] <terli> changed mute/unmute in gnome-alsamixer.
[01:05] <terli>  WARNING **: gam_toggle_get_state (). No idea what to do for mixer element "Mono Output Select"! << whatever that means, I'm sure someone knows
[01:05] <terli> amixer still thinks that everything is off
[01:05] <crimsun> amixer won't lie to you
[01:06] <terli> amixer now thinks that master and master-mono are on.
[01:06] <terli> but not mono-mix
[01:06] <terli> er, mix mono
[01:06] <terli> which is probably input-related
[01:06] <crimsun> and that g-a message is displayed because it doesn't know how to properly handle elements with no range or mute control
[01:06] <crimsun> bug in g-a, of course.
[01:07] <terli> never shows.
[01:07] <crimsun> 'Mix Mono' is capture-related, yes
[01:07] <terli> until you use it to send a rocket to the moon.
[01:08] <crimsun> anyhow, once you have all those ('PCM', 'Headphone', 'Master Mono', and 'External Amplifier') set, try: pasuspender -- speaker-test -Dplughw:0 -c2
[01:08] <terli> *presses a key experimentally*
[01:08] <terli> uhuh, I thought that might have tipped the scales.
[01:08] <terli> this ibm has...
[01:08] <terli> hardware audio in addition to software.
[01:09] <terli> so even now that I've *corrected* alsa's heresy, it was still sorta muted.
[01:09] <crimsun> it wasn't alsa's fault at all
[01:09] <crimsun> some other application told alsa to do something, and alsa did the right thing
[01:09] <terli> I think it could have been exaile.
[01:10] <terli> I got this brief popup...
[01:10] <terli> muting something..
[01:10] <terli> damm pythonites.
[01:11] <terli> now I've got to remove it, no telling what it will do next, sure thing in the morning I'm running mac os x inside of gedit and random bits of the universe are coming out of my powerport...
[01:11] <terli> thanks.
[02:16] <BotLobsta> anyone know why my 2.6.28 kernels will not boot after I resized my root, home, and swap partitions but my 2.6.24 kernel will?
[02:26] <spitfire> BotLobsta: nfc.
[02:26] <spitfire> is it still based on 2.6.28-rc?
[02:27] <BotLobsta> the 2.6.28 kernel in jaunty?
[02:27] <BotLobsta> i would think not but i dont know
[02:27] <spitfire> yeah
[02:27] <spitfire> in previous alpa it was still rc
[02:28] <spitfire> BotLobsta: what did chnage since last alpha?
[02:28] <BotLobsta> i have seen a few new kernel packages in the past few days
[02:28] <BotLobsta> when was the last alpha?
[02:28] <spitfire> 17 dec
[02:29] <spitfire> And the only highlights since inrepid were new kernel and xorg.
[02:29] <spitfire> any new thingies?
[02:29] <BotLobsta> ummm
[02:30] <BotLobsta> it seems like almost everything has been updated since then
[02:30] <BotLobsta> i get like 60 updates a day so its tough for me to remember what big things are new
[02:31] <spitfire> Here is what I know: http://www.ubuntu.com/testing/jaunty/alpha2
[02:31] <spitfire> noticed ay other difference from intrepid (not mentioning just updates)
[02:32] <BotLobsta> not really
[02:32] <BotLobsta> i run xubuntu so there arent as many big changes for me
[02:33] <BotLobsta> the latest kernel is 2.6.28-4 so i believe its based on the final release of 2.6.28
[02:59]  * x1250 likes firefox-3.1b2, is a lot faster :)
[02:59] <BotLobsta> much faster than what?
[03:00] <x1250> BotLobsta, faster than 3.0 ofcourse
[03:01] <BotLobsta> ah
[03:01] <BotLobsta> i dont remember that much of an improvement
[03:02] <BotLobsta> but last time i ran 3.1 was a few months ago
[03:03] <x1250> BotLobsta, beta 2 uses the new javascript engine by default :)
[03:03] <BotLobsta> x1250, ah. i do remember that big improvement
[03:04] <x1250> yeah, that was really needed
[03:04] <BotLobsta> it was
[03:47] <x1250> BotLobsta, what is the error you get at boot?
[03:48] <BotLobsta> it just beeps at me until i turn it off
[03:48] <BotLobsta> x1250, nothing shows up on the screen after the first message
[03:50] <x1250> maybe you should report a bug on launchpad
[03:50] <BotLobsta> i just dont have the faintest idea as to what it could be
[03:52] <x1250> BotLobsta, did that kernel ever worked for you?
[03:52] <BotLobsta> x1250, yea it worked perfectly until I resized/moved my partitions earlier today
[03:55] <x1250> I guess the best you can do is file a bug report, if you haven't
[03:55] <BotLobsta> i havent yet
[03:55] <BotLobsta> ill try that and see how it goes
[03:57] <x1250> BotLobsta, file a bug report in launchpad, and one in http://bugzilla.kernel.org/, and link them
[03:57] <x1250> in that way it will get fixed fast, and the patch will be applied fast, if someone fixes it
[03:58] <BotLobsta> im wondering if its more of a configuration error on my side or an actual bug
[04:04] <x1250> do you have something in mind?
[04:05] <BotLobsta> I was thinking some of my UUIDs got messed up (especially my swap one) and the new ones werent put in all the spots they need to be
[04:06] <DanaG> yo, anyone know how to make Gnome do this: pop up a notification upon pressing a certain key?
[04:06] <BotLobsta> i put my new swap partition's uuid in /etc/fstab but thats the only place i changed it
[04:07] <DanaG> I have a key $KEY_LIGHT that's the ambient-light-sensor toggle thing; I want it to notify-send the status of the ambient light sensor.
[04:18] <x1250> DanaG, use gconf-editor to set a key combination in /apps/metacity/global_keybindings/run_command_1, and put your script in /apps/metacity/keybinding_commands/command_1. I guess that should work.
[04:21] <DanaG> hmm, key is 0xc5.
[04:26] <Andre_Gondim> I am using Intrepid, always when I try to upgrade to jaunty with update-manage -d I receve this message "http://sft.if.usp.br/ubuntu/dists/jaunty-updates/Release  Unable to find expected entry  partner/binary-i386/Packages in Meta-index file (malformed Release file?)" does not matter what mirror I am using, what am I do?
[04:26] <DanaG> jaunty-updates does not exist, I'd imagine.  =þ
[04:27] <DanaG> Oh yeah, the script worked.  Now I can tell whether my Ambient Light Sensor is on or off -- I scripted notify-send.
[04:27] <DanaG> ... but compiz doesn't run it!
[04:27] <DanaG> Only metacity runs the thing on demand.
[04:28] <DanaG> Stupid compiz.
[04:29] <DanaG> https://bugs.launchpad.net/compiz/+bug/158855
[04:31] <x1250> DanaG, tried some other key combination?
[04:32] <DanaG> I also  have things bound to XF86Launch1 and XF86Launch2... but they don't work with compiz, either.
[04:34] <x1250> try asking on #compiz, maybe its already fixed (and you can get a patch).
[04:42] <x1250> booh, today I realized the fan for my video card is not working (dell inspiron 9400, ati x1400). I wonder if its jaunty's fault. Is there any way to get some info about the fan, somewhere?
[04:43] <x1250> maybe it died :(
[05:21] <DanaG> Oh hey, is there any way to get PulseAudio to run a specific command when I insert a specific device?
[05:56] <pradeep> does today's daily have ext4 enabled?
[07:36] <lucent> I'm trying to find out why initramfs and LVM broke recently
[07:36] <crimsun> how recently?
[07:36] <crimsun> 6 hours ago? 2 days ago? 1 week ago?
[07:37] <lucent> crimsun: between Jaunty Alpha 2 and now
[07:37] <crimsun> oh geez
[07:37] <crimsun> well, that's a cracktonne of changes, yanno
[07:38] <crimsun> linux, lvm2, udev/watershed
[07:38] <lucent> huh, watershed? that is a new one for me
[07:38] <lucent> what is that /where is documentation
[07:39] <crimsun> /usr/share/doc/watershed
[07:39] <lucent> that only lists the changelog and copyright
[07:39] <lucent> do I need to install the documentation?
[07:40] <crimsun> well, i figured that you could read the changelog.gz for udev/watershed
[07:41] <crimsun> hint: watershed itself isn't all that immediately important here in terms of your breakage
[07:41] <lucent> oh
[07:41] <lucent> well you could just say that
[07:41] <crimsun> dude, i have no idea what your config is
[07:41] <lucent> watershed documentation doesn't exist where you say it is
[07:41] <crimsun> watershed could be important, but i don't know
[07:41] <crimsun> "my arm hurts!" "uh, ok..."
[07:42] <lucent> if you don't know what it is then why are you telling me to read the /usr/share/doc/watershed/  files? or the changelog which only says one entry "initial release"
[07:42] <lucent> don't waste my time please
[07:42] <lucent> I don't mind if you don't know
[07:42] <crimsun> dude, _i_ know what watershed is. i'm asking you what your config is.
[07:42] <lucent> but don't waste my time on documentation that doesn't exists
[07:42] <lucent> oh
[07:43] <lucent> root on ext4 on LVM with grub2 bootloader
[07:43] <lucent> right now the Grub2 part works great and initramfs loads, but doesn't find the device nodes for /dev/mapper/volzontar-root (an LVM volume)
[07:43] <crimsun> then i'm guessing your brekage lies in linux, lvm2, and udev
[07:44] <crimsun> breakage*
[07:44] <lucent> to get it booting I type "lvm vgscan --mknodes; lvm vgchange -ay" and exit
[07:44] <lucent> the system boots
[07:44] <lucent> how do I find out which package update has the regression though?
[07:44] <lucent> I need to know which version of lvm2 and initramfs-tools was in jaunty alpha 2
[07:44] <lucent> how do I find out that info?
[07:44] <crimsun> check the manifest for the isos.
[07:45] <lucent> hm, manifest, okay
[07:45] <lucent> the weird part is that those commands haven't changed
[07:45] <lucent> everything should work but initramfs does not run the scripts
[07:46] <lucent> what does watershed do? You said you know about it
[07:46] <lucent> the documentation is not where you say it is
[07:46] <lucent> so what does watershed do?
[07:46] <crimsun> it handles idempotency, but as i suspected, it's not relevant for you
[07:47] <crimsun> your breakage is linux+lvm+udev
[07:47] <crimsun> although now that i look at it closer, it's more than likely just lvm+udev
[07:48] <crimsun> the first thing i would do is revert to the last udev 124
[07:48] <lucent> I think that initramfs-tools is failing to run a script or something
[07:48] <lucent> or udev doesn't make the nodes
[07:49] <crimsun> note that udev did undergo a massive upgrade (124->136) entailing multiple significant changes
[07:49] <crimsun> the only changes i see in initramfs-tools were to add watershed (not important) and ext4 if not available in the kernel
[07:50] <lucent> the ext4 part works okay, I have tested this
[07:50] <crimsun> where in the initramfs is the lvm breakage?
[07:50] <lucent> before then I must pass rootfstype=ext4 to the kernel
[07:50] <crimsun> i.e., are you waiting for busybox to show up?
[07:50] <crimsun> or are you passing something explicitly, like break=mount ?
[07:51] <lucent> well, when initramfs gives up trying to find the root device, and shows me busybox... there's no lvm nodes in /dev/mapper
[07:51] <lucent> initramfs is timing out because it can't find the device (/dev/mapper/volzontar-root)
[07:52] <lucent> there exists an lvm-related script in the busybox / initramfs environment then which should have activated my lvm volumes
[07:53] <lucent> brb I'm going to reboot and test if the volumes are activated but not having nodes (which would indicate an udev issue)
[08:07] <lucent> crimsun: something is messed up I'm guessing, because "mdadm" doesn't exist as a script in initramfs scripts
[08:07] <lucent> crimsun: please have a look at /usr/share/initramfs-tools/scripts/init-premount/lvm2 and tell me what you think, won't that fail because of a missing mdadm script?
[08:10] <crimsun> lucent: is mdadm even installed? (it isn't locally)
[08:11] <lucent> un  mdadm          <none>         (no description available)
[08:11] <lucent> nopers.
[08:11] <lucent> that's super wierd
[08:11] <lucent> weird*...   should that be removed from the lvm2 hook, does it matter?
[08:12] <lucent> I could try removing 'mdadm' text from the script and observe
[08:12] <crimsun> it likely was deinstalled due to udev->* scheduling
[08:13] <crimsun> i.e., migration to udev 136, its corresponding deprecation of /etc/udev/rules.d, and its versioned rdepends
[08:14] <crimsun> note that scott has been handling the migration largely himself; jaunty-changes has a bunch of his uploads migrating to the new udev world order
[08:23] <lucent> crimsun: ah okay.  Well, all I can figure out is that the presence of "mdadm" does not seem to make a difference in the lvm2 script
[08:23] <lucent> crimsun: also, I narrowed it down to the execution of "lvm vgchange" command;  running lvm vgchange does create the needed nodes
[08:24] <lucent> so I see "lvm vgchange" exists in a script on the initramfs when I am kicked out into busybox, but why ... is it not running? does it run and gets ignored or overwritten somehow... I don't know the order of execution for that
[08:26] <crimsun> to troubleshoot that, you'd need to step through the initramfs sequence; use break=mount
[08:26] <crimsun> i think there's an irclog of that somewhere
[08:28] <lucent> alright
[08:28] <lucent> that's further than I got yesterday anyways, thanks
[08:28] <lucent> oh about rules.d, it's depreciated... does anything replace its function?
[08:29] <crimsun> it's not deprecated; the location changed
[08:29] <crimsun> -> /lib/udev/rules.d
[08:30] <lucent> ah, okay
[08:31] <lucent> one more question, how to revert the behavior of the system bell that just started again in Jaunty Alpha 2?
[08:32] <lucent> it's not pcspkr... I've rmmod'ed that
[08:32] <lucent> on my laptop computer it emits this decidedly irritating noise at maximum volume through the audio device
[08:32] <lucent> making me crazy here :P
[08:34] <crimsun> depends on your hardware
[08:36] <crimsun> hda-intel now handles it on some platforms; on others, it can be at the hardware level (e.g., thinkpads)
[08:36] <lucent> agh, must be hda-intel as a rough guess
[08:36] <lucent> I want to stabbity kill kill x stab stab that changeset
[08:37] <crimsun> hopefully you don't have snd_pcsp loaded
[08:37] <lucent> wait
[08:37] <lucent> I just muted it with alsamixer?  is that right?
[08:37]  * lucent smiles :)
[08:37] <crimsun> yes
[08:37] <crimsun> again, it's exposed through hda-intel on certain platforms
[08:38] <lucent> I'm really glad that you mentioned hda-intel as a possible
[08:38] <lucent> thanks
[08:42]  * tritium waves at crimsun
[08:42] <crimsun> lucent: yw
[08:42] <crimsun> heya tritium
[08:42] <tritium> How are you, crimsun?
[08:43] <crimsun> exhausted, you? (have to get to work in some hours)
[08:44] <tritium> Doing ok, thanks.  Let's chat another time.  Go get some rest!
[08:45]  * lucent hovers over the "submit bug report" option
[08:49] <lucent> crimsun: the error is caused by watershed, indirectly
[08:49] <lucent> I'm surprised though
[08:49] <lucent> https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/315580
[08:50] <lucent> well that's one possibility, I have not confirmed here
[11:17] <x1250> whats the matter with apport-gtk? it can't send reports. Error is: <urlopen error The read operation timed out>
[11:19] <Alexia_Death> Morning.
[11:19] <Alexia_Death> Last nights updates killed sound for me...
[11:19] <Alexia_Death> Anybody else with same issue?
[11:20] <Alexia_Death> It seems pulseaudio is used for everything but nothing gets out...
[11:23] <lemonade> i have same issue
[11:23] <Alexia_Death> aaaan... output module list only lists my modem...
[11:24] <Alexia_Death> in normal setup Id get two devices
[11:24] <x1250> Alexia_Death, did you check your sound preferences? Inside "volume control" there's another volume slider. Check that.
[11:24] <Alexia_Death> x1250: I did
[11:24] <Alexia_Death> All of them are on
[11:25] <x1250> Alexia_Death, try $ pulseaudio -k, and open totem or anything and check if it works.
[11:25] <x1250> you'll be using alsa, so it if don't work, pulseaudio is not guilty.
[11:27] <Alexia_Death> hmm
[11:27] <Alexia_Death> I tried to tell amarok to use alsa plugin
[11:27] <Alexia_Death> Killed amarok
[11:28] <Alexia_Death> and no, still does not work
[11:28] <Alexia_Death> so its alsa that is broke.
[11:28] <Alexia_Death> I remeber seeing something about alsa in the updates list.
[11:33] <x1250> alsa-utils was updated yesterday. It works here though.
[11:37] <x1250> lemonade, what happens if you run: $ pulseaudio -k, and check if sound works?
[11:37] <x1250> you need to restart the sound program you use ofcourse
[11:39] <Alexia_Death> hmm
[11:39] <Alexia_Death> I dont even know how to figure it out...
[11:40] <Alexia_Death> Is there an alsa test routine somewhere I could run?
[11:41] <x1250> check /var/log for anything
[11:49] <lemonade> x1250: ok, just a moment i'll try
[11:52] <Alexia_Death> x1250: neither dmesg, messages nor kernlog has anything of interest
[11:57] <afflux> x1250: for the apport thing, someone told me that this would be related to LP being too slow
[11:59] <x1250> afflux, it makes sense, LP _is_ slow, lately.
[12:00] <afflux> not sure how to workaround it, I think I wasn't even able to submit any crash report for the jaunty cycle
[12:44]  * Alexia_Death grumbles
[12:44] <Alexia_Death> no audio
[13:02] <Alexia_Death> Any ideas what to look at about my sound issue.
[13:02] <Alexia_Death> Its clear now that its an alsa issue
[13:03] <Alexia_Death> For aplications theres no issue. everyting is playing and nothing is muted
[13:03] <Alexia_Death> but no beep comes out since updates last night,
[13:04] <Alexia_Death> O_O
[13:04] <Alexia_Death> Aaah.
[13:04] <Alexia_Death> Okay. Front speakers were muted in alsamixer O_O
[13:05] <Alexia_Death> For the device
[13:05] <Alexia_Death> That I could not get that easy if I didnt kill of pulseaudio first.
[13:06] <Alexia_Death> get to*
[13:13] <Alexia_Death> Okay
[13:13] <Alexia_Death> Nature of the bug established
[13:14] <Alexia_Death> Alsa device is always started with muted front speakers
[13:14] <Alexia_Death> After reboot unmute is gone.
[13:14] <spitfire> Alexia_Death: I think it sometimes also happened on intrepid
[13:15] <Alexia_Death> spitfire: never to me on my hardwarw
[13:15] <spitfire> according to pulseaudio thread i read
[13:15] <Alexia_Death> headset too.
[13:15] <Alexia_Death> Oh, pulseaudio
[13:15] <spitfire> but didn't see it happening
[13:15] <Alexia_Death> Inever used pulseaudio in intrepid
[13:15] <spitfire> Alexia_Death: I'm on my way to pulse ;)
[13:15] <Alexia_Death> Its not easy to fix either:(
[13:16] <spitfire> I'm on intrepid, just backporting alsa bluez pulse and rhythmbox/
[13:16] <spitfire> Alexia_Death: It works locally.
[13:16] <Alexia_Death> the bulez thing crashes pulseaudi for me.
[13:16] <Alexia_Death> pulseaudio*
[13:16] <spitfire> But I want to get sound played across network;)
[13:16] <Alexia_Death> I have bt headset
[13:16] <Alexia_Death> :D
[13:16] <spitfire> Alexia_Death: I don't
[13:17] <spitfire> It's not what I want to use it for.
[13:17]  * Alexia_Death contemplates adding this channel to her auto join list.
[13:17] <Alexia_Death> who was it who had the same problem I did with sound?
[13:18] <Alexia_Death> alsamixer -Dhw:0 to get to the device alsamixer.
[13:18] <Alexia_Death> Unmute anything there.
[13:19]  * Alexia_Death contemplates failing a bug about this.
[13:19] <Alexia_Death> I consder myself an advanced user and this took me over an hour to figure out... Most will be lost..
[13:54] <c_korn> hello
[13:55] <c_korn> someone
[13:55] <c_korn> argh
[13:56] <c_korn> I have an entry in /etc/crypttab for sda4_crypt. can I add another entry with sda4_crypt that uses a keyfile instead of a passphrase?
[13:59] <tim_sharitt> I lost my sound settings in System > Preferences after an update (thursday?), Is that the norm, or did I screw something up?
[14:06] <x1250> tim_sharitt, thats ok, change intended. Double click de volume applet to get the sounds preferences now. There is no much there though :P
[14:08] <tim_sharitt> x1250, Thanks, I figured something was changed. Just wanted to make sure something wasn't broke.
[14:18] <tux91> Hello everybody. Does anyone have their sound broken after recent updates
[14:18] <tux91> ?
[14:21] <Alexia_Death> tux91: I did
[14:22] <Alexia_Death> tux91: lsamixer -Dhw:0  and see if unmuting stuf helps
[14:22] <Alexia_Death> alsamixer*
[14:22] <Alexia_Death> My front and headphones start up unmuted after restart
[14:22] <c_korn> does anyone know how to setup a keyfile for the encrypted swap? this guide worked for the /home partition but when I try it with swap I am still asked for the passphrase at boot: http://www.howtoforge.com/automatically-unlock-luks-encrypted-drives-with-a-keyfile
[14:23] <tux91> Alexia_Death: it worked! thanks so much
[14:23] <Alexia_Death> welcome. Spent hours earlyer trying to figure it out;)
[14:23] <Alexia_Death> start up muted*
[14:24]  * Alexia_Death grumbles.
[14:24] <Alexia_Death> Filing a bug about this. Seems like a common issue by now.
[14:24] <x1250> Alexia_Death, you finally fixed it, great :)       ..... lemonade, does Alexia_Death fix helps you too?
[14:25] <Alexia_Death> x1250: yes :)
[14:25] <Alexia_Death> x1250: main trick was getting arount to the hw alsacontrols without killing pulseaudio first.
[14:32] <Alexia_Death> https://bugs.launchpad.net/ubuntu/+bug/315809 <- bug filed
[14:34] <Alexia_Death> Anybody else but me have serious problems with stability of 1.6 X?
[14:35] <Alexia_Death> I dont mind quircks but frequent crashes are no fun:P
[14:35] <x1250> Alexia_Death, anything on the logs?
[14:36] <x1250> or post a crashed log to pastebin, and xorg.conf
[14:36] <x1250> what video card, driver?
[14:36] <Alexia_Death> x1250: most traces start with graphics. Those that are left that is. Input is totally broken too, but I have several patches applied that fix most of those from upstream
[14:36] <Alexia_Death> nvidia, both unsupported wrong abi binary driver and nv are unstable.
[14:37] <Alexia_Death> Unpatched plugging in a wacom kills X dead
[14:37] <x1250> aah, you'll have to wait, unsupported means "they" don't care about your problems, yet
[14:37] <Alexia_Death> yeah, but nv is just as broken
[14:37] <Alexia_Death> And slow as hell:P
[14:38] <x1250> post Xorg.0.log from nv then
[14:38] <Alexia_Death> Will, once i generate one.
[14:38] <Alexia_Death> Running with nvidia now.
[14:39] <charlie-tca> Anybody having issues with Xubuntu not giving the desktop?
[14:44] <c_korn> hello
[14:44] <c_korn> someone knows how to setup a keyfile for an encrypted swap partition?
[14:45] <c_korn> so that I only need to enter the passphrase of the root partition at boot
[14:45] <c_korn> and not the passphrase for root+swap
[14:49] <c_korn> this guide has worked for my home partition
[14:50] <c_korn> http://www.howtoforge.com/automatically-unlock-luks-encrypted-drives-with-a-keyfile
[14:50] <c_korn> but it cannot be used for swap because I am still asked for thr swap partition passphrase at startup
[15:22] <Splex_> anyone suddenly have sound stop working on a recent update?
[15:25] <homy> Splex_: with me, sound works fine (I updated everything about an hour ago)
[15:26] <x1250> Splex, ...
 tux91: lsamixer -Dhw:0  and see if unmuting stuf helps
 alsamixer*
[15:26] <Splex_> x1250: thanks, im trying that through alsamixer now
[15:27] <Splex_> x1250:  im also wondering why there is no gui access via volume control... or am i missing something?
[15:27] <Splex_> is the gnome volume control now a frontend for pulseaudio?
[15:31] <x1250> Splex, I guess calling it a frontend is too much for the poor thing, at least for now. It only controls volumes, but can do so per application, which is good, if you feel like it.
[15:31] <Splex_> basically what pulseaudio volume control does...
[15:33] <homy> Hi! I have problems with an nvidia card. In intrepid I use restricted drivers in order to get a higher resolution, here jockey doesn't show me any available drivers.
[15:34] <legodude> homy: I was told that you can't get them working with jaunty :(
[15:34] <legodude> the drivers are not compatibile with jaunty (X? kernel?)
[15:34] <homy> Will this problem be solved until jaunty is final/beta ?
[15:36] <x1250> homy, try "nv" drivers
[15:37] <homy> x1250: it is installed, but my xorg doesn't list any driver, so isn't it used then?
[15:38] <homy> ok, so I'll do a xserver restart now. I'll come back when x is back up.
[15:39] <legodude> nv didn't seem to work for me
[15:43] <homy> Hi. I tried the "nv" driver, but it is even worse than the default (vesa? ). I only get the "bulletproof X".
[15:47] <legodude> I get a mouse cursor atop garbage
[16:16] <Alexia_Death> lemonade: Was your sound issue the same as mine?
[16:43] <x1250> Alexia_Death, did you report a bug? if so, then close it please :)
[16:43] <Alexia_Death> why?
[16:43] <Alexia_Death> it is a bug.
[16:44] <Alexia_Death> a pressistent one
[16:44] <Alexia_Death> It resets to muted at every reboot.
[16:45] <Alexia_Death> x1250: why do you think its not a bug?
[16:45] <x1250> aahh, yes, I thought your bug report was not about that, but what you first thought, just no sound.
[16:49]  * Alexia_Death makes it a habbit not to file bug reports untill sure what it is that is actually wrong ;)
[17:42] <Alexia_Death> err---
[17:42] <Alexia_Death> Feedback time.
[17:43] <Alexia_Death> the latest kernel, 2.6.28-4, anybody else having problems with it not turning ont the wireless radio?
[17:43] <Alexia_Death> 2.6.28 does.
[17:43] <Alexia_Death> Both kernels break my touchpad.
[17:43] <Alexia_Death> no more taps.
[17:44] <Alexia_Death> they get handled by a wrong (non-synaptic) module...
[17:44] <Alexia_Death> that would be 2.6.28-3
[17:45] <Alexia_Death> 2.6.17, the intrepid kernel has neither of the problems. but it wrote my drive full using nv driver with kernel traces...
[17:45] <Alexia_Death> And I was wondering why it became slow as hel when I used nv...
[17:47] <Alexia_Death> thats the touchpad issue: "ETPS/2 Elantech Touchpad"      id=5    [XExtensionPointer]
[17:48] <Alexia_Death> What of these should become bugreports and does anybody have solutions at least for the touchpad problem?
[17:58] <spitfire> Alexia_Death: you're sure it's not hal's fault?
[17:59] <Alexia_Death> spitfire: no. but it does not happen for the older kernel and same hal
[17:59] <spitfire> ok
[17:59] <spitfire> Alexia_Death: Try vanilla then ;)
[18:00] <Alexia_Death> spitfire: could, wont. done building kernels:P did it too mutch for gento:P
[18:00] <Alexia_Death> Jaunty has to get it right too:P
[18:00] <Alexia_Death> For everybody:P
[18:01] <spitfire> Alexia_Death: I just switched back from gentoo 2 days ago
[18:01] <spitfire> Kernel building was ok
[18:01] <Alexia_Death> I switched from gentoo about... hmm... year and half ago
[18:01] <spitfire> kenrnel-package in ubuntu sucks
[18:02] <spitfire> I started using ubuntu in dec '07 switched to gentoo in jul '08
[18:02] <spitfire> and back two days ago
[18:02] <Alexia_Death> well, ubuntu is supposed to be user friendly, so when this stops being alpha this shit should not happen
[18:02] <Alexia_Death> I was gentoo user for over 2 years
[18:02] <Alexia_Death> Started with gentoo:P
[18:02] <spitfire> Alexia_Death: Most likely it won't ;)
[18:02] <Alexia_Death> :P yeah
[18:02] <spitfire> Alexia_Death: people shouldn't start with it
[18:03] <spitfire> but I learnt a lot from it.
[18:03] <Alexia_Death> yes they shoudl if they want to learn:P
[18:03] <spitfire> Like I said "but I learnt a lot from it."
[18:03] <Alexia_Death> ok, gentoo was my first desktop install
[18:03] <spitfire> But they can get frustrated before seeing anything
[18:03] <Alexia_Death> Had slackware for router before that
[18:04] <Alexia_Death> Well, I would know nothing about configuring kernels if I hadnt done gentoo...
[18:04] <Alexia_Death> And Id know nothing about init if I hadnt done slackware:P
[18:05] <Alexia_Death> And debugging of all sorts if I dint have a bad habbit to perpetually run Ubuntu alpha:P
[18:06] <spitfire> Alexia_Death: I still haven't used gdb :P
[18:08] <Alexia_Death> spitfire: I have, but I havent mastered it fully:P Strace is often enough:P
[18:08] <spitfire> I have really done no real debugging.
[18:11] <Alexia_Death> (II) Synaptics touchpad driver version 0.15.2
[18:11] <Alexia_Death> Synaptics Touchpad no synaptics event device found
[18:11] <Alexia_Death> X is convinced theres no synaptics device
[18:44] <Alexia_Death> spitfire: you were right.
[18:44] <spitfire> about?
[18:44] <Alexia_Death> It is hal.
[18:44] <Alexia_Death> Or rather
[18:44] <spitfire> hla-info?
[18:45] <Alexia_Death> Kernel now names my touchpad differently
[18:45] <spitfire> *hal-info?
[18:45] <Alexia_Death> yes
[18:45] <Alexia_Death> and the fdi file does not therefore grab it.
[18:45] <Alexia_Death> Synaptic fdi is part of synaptic package so thats what the bug should be filed with.
[18:46] <spitfire> Alexia_Death: why wait?
[18:46] <spitfire> You have done you investigation ;)
[18:46] <Alexia_Death> ?
[18:46] <spitfire> Why wait to fill a bug?
[18:46] <Alexia_Death> Starting browswer now to do just that;)
[18:47] <Alexia_Death> Never had the habbit of sitting on a perfectly good bug:P
[18:47] <spitfire> Alexia_Death: I'm trying to get pulse working, so I'm backporting half-a-jaunty:P
[18:47] <spitfire> So I broke my alsa.
[18:47] <spitfire> But I think it's my fault.
[18:48] <Alexia_Death> heh.
[18:48] <spitfire> Not really half
[18:49] <spitfire> Just bluez pulse pulse gui tools and alsa
[18:49] <spitfire> pulse needed also libspeex
[18:49] <spitfire> and that's all
[18:49] <spitfire> ant a bunch of packages needed to be rebuild
[18:49] <spitfire> but I rebuild stable ones;)
[18:55] <pwnguin> Alexia_Death: you might check out #ubuntu-x
[18:56] <pwnguin> your level of participation in wacomtools upstream might justify idling in #ubuntu-x, if you care about ubuntu ;)
[18:58] <Alexia_Death> :D
[18:59]  * Alexia_Death joins another channel...
[19:01] <Alexia_Death> pwnguin: I rather care about getting stuff working and remaining working ;)
[19:01] <pwnguin> even better
[19:02]  * Alexia_Death thinks about going to #ubuntu to fish for hotplug testers for wacom but decides against it. the daemon needs more licking over.
[19:03] <pwnguin> unfortunately, i cant unplug my wacom
[19:03] <Alexia_Death> why?
[19:04] <pwnguin> its built into the laptop
[19:04] <Alexia_Death> can I edit the name of the bug :(
[19:04] <pwnguin> in lp?
[19:04] <Alexia_Death> pwnguin: serial
[19:04] <Alexia_Death> pwnguin: yes.
[19:04] <Alexia_Death> Ive made a wee bit but significant error in the title
[19:04] <pwnguin> what's the url?
[19:04] <Alexia_Death> it has to be 2.6.28 not 2.6.18
[19:05] <Alexia_Death> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/315882
[19:05] <Alexia_Death> Damn.
[19:05] <pwnguin> heh
[19:05]  * Alexia_Death slaps herself for not checking before OK :S
[19:05] <pwnguin> do you see a yellow circle with a pencil near the title at that url?
[19:06] <Alexia_Death> Err... Well... Ive always thought that was some sort of an ! mark
[19:07] <Alexia_Death> But indeed! it is a pencil and indeed, it is fixed...
[19:07] <pwnguin> well, if you click it, i think you can correct the title
[19:07] <Alexia_Death> ;)
[19:07] <Alexia_Death> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/315882
[19:07] <Alexia_Death> YAY!
[19:07]  * Alexia_Death is going to pretend dot being stupid and blame the designer:P
[19:10] <bluevapour> anyone able to help me with firehol
[19:11] <m0RrE> any qualified guesses when intel i7 t will be in the kernel?
[19:12] <x1250> bluevapour, how should anyone know that if you don't ask?
[19:14] <bluevapour> because basically my server is working fine, on lan
[19:14] <bluevapour> firehol has server all accept so it shouldnt block anything
[19:14] <bluevapour> yet global cant access http but they can access ssh
[19:16] <FireFox||> m0RrE: What are your problems with the i7 core i720 ?
[19:20] <FireFox||> m0RrE: you bought a dell studio XPS desktop I assume?
[19:33] <legodude> I'm having problems with nv... I get a mouse cursor on top of a garbage background
[19:33] <legodude> and that's it
[19:33] <legodude> even if I try to kill the X server or switch to a console login tty I get garbage
[19:36] <Alexia_Death> legodude: whats your kernel?
[19:41] <legodude> 2.6.28-3-generic
[19:43] <legodude> Alexia_Death: I had it working perfectly in 8.10 with nvidia drivers
[19:43] <legodude> but have never gotten it working in jaunty
[19:44] <Alexia_Death> legodude: interesting. works for me.
[19:44] <legodude> grr
[19:44] <legodude> what card?
[19:44] <Alexia_Death> legodude: Hmm, dont even know exactly. laptop...
[19:45] <Alexia_Death> 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GT (rev a1)
[19:45] <legodude> I have a 7200gs which is fairly standard
[19:46] <Alexia_Death> legodude: with a hack you can get nvidia
[19:46] <legodude> even if I kill the x server I get garbage so it seems to be somewhere in kernel land for me
[19:46] <Alexia_Death> but it will be prone to crashing
[19:46] <legodude> what's the hack?
[19:46] <legodude> I've not heard about that
[19:46] <legodude> ugh
[19:47] <Alexia_Death> legodude: IgnoreABI "true"
[19:47] <legodude> ahhh
[19:47] <Alexia_Death> legodude: but you should really tell your grub to not bother with splash
[19:47] <Alexia_Death> then you see whats going on.
[19:47] <legodude> how do I do that?
[19:47] <legodude> nosplash option?
[19:47] <Alexia_Death> yes
[19:48] <legodude> lemme see here
[19:52] <legodude> Alexia_Death: I just want to add it as a command line option?
[19:52] <Alexia_Death> legodude: ?
[19:53] <Alexia_Death> in /boot/grub/menu.lst and just change your kernel parameters
[20:02] <legodude> (EE) open /dev/fb0: No such file or directory
[20:02] <legodude> could this be it?
[20:03] <Alexia_Death> could
[20:03] <Alexia_Death> Google it?
[20:03] <legodude> I am
[20:04] <legodude> I saw it before and ignored it, because everything else in Xorg.log looks normal
[20:44] <LLStarks> yo
[20:44] <LLStarks> my jaunty pals
[20:52] <c_korn> hello I have set up an encrypted swap partition.
[20:52] <c_korn> I also set up a keyfile in the also encrypted root partition
[20:52] <c_korn> but I am still asked for the swap passphrase at boot
[21:08] <c_korn> is there a log of the root partition decryption at boot time?
[21:10] <spitfire> c_korn: man you're still encrypting it :P
[21:11] <c_korn> spitfire: it seemed to be a problem with the daily iso yesterday today the bug from yesterday is gone
[21:11] <c_korn> now I have a different one
[21:11] <spitfire> oh:P
[21:12] <LLStarks> yo
[21:12] <LLStarks> will jaunty be released with firefox upstream builds still broken?
[21:12] <c_korn> I only want to type in the passphrase of the root partition at boot. so I added a keyfile in root for my swap and my home directory. the keyfile for the home partition works but I am still asked for the passphrase of the swap partition
[21:13] <c_korn> LLStarks: firefox works for me
[21:13] <c_korn> I already opened a bug report: https://bugs.launchpad.net/ubuntu/+bug/315854
[21:14] <LLStarks> is ext4 safe yet?
[21:14] <c_korn> but I think it is wrong because I have to enter the root passphrase before the swap passphrase
[21:14] <c_korn> so the root partition is already mounted before the swap partition I presume
[21:15] <c_korn> LLStarks: I did not encounter any issues since yesterday :P
[21:15] <LLStarks> pure ext4 or mounted as ext4?
[21:16] <c_korn> LLStarks: pure
[21:17] <LLStarks> how do i mount and/or convert an ext3?
[21:26] <c_korn> can't anyone help me?
[21:29] <LLStarks> ?
[21:29] <LLStarks> with what?
[21:31] <c_korn> LLStarks: scroll up
[22:00] <c_korn> yeah, now I cannot decrypt swap because I deleted the passphrase
[22:09] <archivator> I was wondering, is anyone working actively on reducing boot time?
[22:10] <archivator> I was recently examining my boot process and everything seemed quite tight. Just wondered where we could squeeze some extra juice from..
[22:23] <c_korn> archivator: I only noticed there is a brainstorm idea about it: http://brainstorm.ubuntu.com/idea/42/
[22:23] <c_korn> but I wonder that jaunty still does not use upstart 0.5
[22:54] <shadowkanji> hey anyone tested kubuntu 9.04 alpha 2?
[22:57] <shadowkanji> ......want to know how stable it is
[22:57] <DanaG> !nvidia
[23:03] <RAOF> shadowkanji: Works (mostly) for me.
[23:04] <RAOF> Don't expect any proprietary drivers to be installable.
[23:05] <shadowkanji> I can live without proprietary drivers. mostly?
[23:05] <RAOF> And it might require some assistance to boot if you've got a slightly interesting lvm/crypt/whatever setup
[23:05] <RAOF> Yeah, you can live without proprietary (graphics) drivers.
[23:07] <shadowkanji> yea. all that matters is that its stable and works with my wireless :P although I may just stick with 8.10 and install kde 4.2 on tuesday when RC1 is out. I find the current kde4 horribly unstable
[23:10] <Melik> ive always hated KDE
[23:12] <shadowkanji> I'm always going between gnome and kde. I find gnome lacks new features, it's always been the same whereas kde4 was nice but unstable :/