[02:16] <cellofellow> how do I see the futon interface for my instance of desktop-couch? There used to be a ~/.local/share/desktop-couch/couchdb.html file but that's gone.
[02:59] <cody-somerville> Is it possible to create lucid chroots yet? I'm getting: diff: PreDepends: diffutils but it is not installed
[03:03] <gnomefreak> cody-somerville: diff was held back because it needed to add packages (if that is what the above means)
[03:04] <gnomefreak> install it directly and it installs
[03:08] <gnomefreak> trying now
[03:13] <lamont> Nov  7 18:02:11 rover3 avahi-daemon[1069]: Invalid query packet.
[03:13] <lamont> Can I have a little more detail please, avahi?
[03:29] <gnomefreak> cody-somerville: i ran into it just run apt-get -f install and it fixes it
[04:45] <jdong> is there a decent way for per-user upstart jobs
[04:45] <jdong> like what OS X / launchd allows?
[04:45] <jdong> I'd like a per-user service to respawn when it crashes, and figured while I could write a script to do that, it'd be cooler if the user had control over it
[04:49] <ion> It’s in TODO. :-P
[05:06] <jdong> ion: yay? ;-)
[05:08] <ion> Dunno wherher Keybuk’s planning to implement that for 0.10 or after.
[05:09] <maco> planning for 2100 already? O_O
[06:13] <JanC> it shouldn't be too difficult to add that
[15:30] <ramblagir> Is there a development tools CD image somewhere? I want to install some development tools on my Ubuntu computer but it's not connected to the internet.
[16:49] <salty-horse> after upgrading to 9.10, wireshark no longer has a "run as root" desktop file. is this on purpose? (I think ScottK is the packager)
[16:50] <ScottK> salty-horse: It was an intentional change by Debian or upstream, I don't recall.
[16:51] <salty-horse> what am I supposed to do with wireshark without root? should I give my desktop user the necessary  permissions?
[16:52] <ScottK> I guess open a shell and gksudo or kdesudo wireshark.
[16:53] <Laney>    * removed wireshark-root.desktop to discourage running Wireshark as root
[16:53] <salty-horse> Laney, thanks. I didn't find it while looking through https://launchpad.net/ubuntu/+source/wireshark/+changelog
[16:56] <superm1> it doesn't help though that significant parts of the tool need root
[17:21] <dtchen> superm1: right, different distros have taken approaches like giving users the necessary caps and restricting them via selinux, smack, etc.
[17:22] <dtchen> hyperair: WRT cracking and ppc, yes, it's a known issue, and it doesn't just affect ppc. However, it's unclear whether it's a driver issue, a library issue, or a PA issue
[17:23] <dtchen> crackling*
[17:23] <hyperair> dtchen: er what?
[17:23] <dtchen> hyperair: please file a bug (affecting linux -- ubuntu-bug alsa-base and then retriage it to affect linux)
[17:23] <dtchen> hyperair: sorry
[17:24] <hyperair> wait, what's this about cracking?
[17:24] <hyperair> and ppc?
[17:24]  * hyperair attempts to understand
[17:24] <dtchen> hyperair: finger-rot. It was supposed to be addressed to slytherin.
[17:24] <hyperair> aah
[17:24] <hyperair> okay
[18:15] <MattJ_> Is there a way to see a human-readable list of patches that have been applied to a package in Ubuntu, specifically libssl in my case
[18:15] <MattJ_> ?
[18:17] <ion> http://patches.ubuntu.com/o/openssl/
[19:26] <djsiegel1> pitti: hello
[19:27] <djsiegel1> pitti: was beeping improved in karmic? it seems to be, and I'd like to mark bug #77010 fixed
[19:29] <maco> possibly the hardware beep was disabled?
[19:30] <MattJ_> Thanks ion :)
[19:39] <dtchen> maco: / djsiegel1: no, and no.
[19:39] <dtchen> there was a rather hackish workaround applied
[19:39] <djsiegel1> dtchen: but is there improvement for users?
[19:39] <djsiegel1> I have heard fewer beeps
[19:39] <dtchen> but, if you ... well, you've already marked it Fix Released, so I won't comment further
[19:39] <djsiegel1> or is it my imagination
[19:39] <djsiegel1> no, please comment further
[19:40] <maco> hahaha
[19:40] <djsiegel1> If we've significantly curbed occurrences of the hardware beep, and a stronger fix is on track for Lucid, I would consider it fixed
[19:41] <djsiegel1> but if we didn't cut down on the beeps, I will revert to unfixed, dtchen
[19:42] <dtchen> you've papered over the symptom, yes. You haven't fixed the cause.
[19:42] <djsiegel1> ok, "papered over" sounds great for a paper cut :)
[19:42] <dtchen> the fix for the cause won't land until 2.6.33 at the earliest.
[19:43] <dtchen> really, you're a better judge of whether the paper cut was resolved
[19:43] <djsiegel1> As far as status in hundredpapercuts is concerned, if the users feel less pain and discomfort, it's a win.
[19:43] <dtchen> sure
[19:44] <dtchen> I just want to warn you that there are changes on the horizon that will break this workaround further
[19:44] <djsiegel1> I know it feels dirty to celebrate a dirty hack job...
[19:44] <dtchen> again, you're the better job of paper cuts
[19:45] <dtchen> s/job/judge/
[19:45] <sladen> djsiegel1: yeah, but instead of a low latency, short hardware beep there is a now a high-latency, 800 msecond software beep with longer (150 msec) before it starts playing than the total length of the hwardware beep
[19:45] <djsiegel1> sladen, then that's a new paper cut. As long as the beep is played at the user-controllable volume label, that is great
[19:46] <djsiegel1> this particular paper cut is just aimed at the heinously lound hardware beep, but I agree there is more work to be done on beeps in general :)
[19:51] <osiris> any chances the 70ba2a374704e00df8868a7ac3d7350329d28924 (32bit ioctl compat fix for radeon drm) will get into the ubuntu kernel?
[19:53] <dtchen> osiris: file a bug affecting linux
[21:42] <dmb> is there daily builds for the next version of ubuntu yet?
[21:44] <chrisccoulson> dmb - not yet. checking http://cdimage.ubuntu.com/daily/ would tell you this though ;)
[21:45] <dmb> chrisccoulson, have uploads started (i don't know if the topic is old or not)
[21:46] <chrisccoulson> dmb - yes. the title says "Archive: lucid open for uploads"
[21:46] <chrisccoulson> and if you're interested, you should be subscribed to the lucid-changes list
[21:46] <dmb> oh, so thats the new name!
[21:47] <dmb> ok, i'm done :)
[21:48] <ryanakca> What importance would bug 264313 be?
[21:49] <ryanakca> Medium or High?
[22:00] <dmb> i would say high, but thats just me
[23:30] <ryanakca> dmb: OK