[00:00]  * LimCore gives Hobbsee the correcting-trivial-typos-while-reading award
[00:02]  * Hobbsee gives LimCore the "12 errors in 2 screens of text" award back
[00:03] <Hobbsee> interesting.  there are later versions of tor, even packaged.
[00:04]  * LimCore wonders why Hobbsee picks on spelling mistakes, and hands a copy of netiquete, however is that spelled
[00:04] <LimCore> well I am on 8.04 (amd64) on this box
[00:04] <Hobbsee> not just spelling, grammar too.  and it makes it hard to read.
[00:04] <LimCore> Really?
[00:05]  * Hobbsee points out https://wiki.torproject.org/noreply/TheOnionRouter/TorOnDebian
[00:06] <Hobbsee> (found from the tor site)
[00:07] <LimCore> mhm, yet in ubuntu 8.04 amd64 this version is the newest available. What to do to have the newest debian one in ubuntu 8.04 also?
[00:07] <Hobbsee> !sru
[00:07] <Hobbsee> guess it could get backported too, if someone tested the jaunty version on 8.04
[00:49] <LimCore> Overall tor seems to be in havy development. Many bugfixes including security fixes. I guess it would be really good for secuirty to keep it up-to-date, same as I ssh is (I hope)
[01:07] <persia> LimCore, well, tor tends to mix bugfixes & security updates with new features still.  I don't yet have the impression that they are handling long-term support for any releases.
[01:08] <persia> To keep something up-to-date for a release post-release, it's typically expected that upstream is maintaining the versiown that was released separately from trunk (which many upstreams do).
[01:08] <persia> When this isn't the case, it needs lots of review and testing for each version to be considered.
[01:58] <Rocket2DMn> cprofitt, youre changing your name too?
[01:58] <cprofitt> yes
[01:58] <Rocket2DMn> and congrats on membership
[01:58] <Rocket2DMn> :)
[01:59] <cprofitt> thanks
[01:59] <cprofitt> the investigation is over...
[01:59] <cprofitt> so I can be me again...
[01:59] <Rocket2DMn> i still have your resume around somewhere, too...
[01:59] <cprofitt> though PrivateVoid has more zip than my real name
[02:00] <Rocket2DMn> do they let your LP name change, too?
[02:01] <cprofitt> yes
[02:01] <cprofitt> I have to wait for the forum staff to say ok to the name change though
[02:01] <Rocket2DMn> wait why are we talking in this channel, back to the BT
[02:01] <Rocket2DMn> my bad
[02:39] <anakron> HI all
[02:40] <anakron> i have some problems to reproduce a bug of qterm
[02:41] <anakron> i dont know how to compile it, because i get a problem when i tried to compile:   'Unknown CMake command "qt4_wrap_ui"
[02:42] <anakron> someone can help?
[02:42] <Hobbsee> have you installed cmake?
[02:42] <anakron> yes
[02:42] <Hobbsee> oh, make install cmake.  hrm.
[02:43] <anakron> where? anywhere?
[02:43] <anakron> ...im not compiling cmake
[02:44]  * Hobbsee suggests adapting http://www.nabble.com/newbie-compile-question-td14422765.html for your use
[02:44] <anakron> XD
[02:44] <anakron> ok thanks
[02:44]  * Hobbsee also suggests googling errors, as that was the first google result...
[02:47]  * Ryan52 thinks that Hobbsee must really like to talk in third person ;)
[02:48] <anakron> :)
[03:21] <Lupine> Please mark as WishList: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/305865
[04:23]  * hggdh thinks nobody talks in the third person -- it is just a figment of a deranged imagination
[04:28]  * Palintheus agrees
[05:02] <Rocket2DMn> Lupine, added that bug to wishlist
[09:35] <marmuta> hi, I'm trying to get a backtrace for gnome-system-monitor. are there dbg symbols in the repos? can't find them
[09:38] <persia> marmuta, Have you enabled the ddebs repo?
[09:38] <persia> !backtrace
[09:42] <marmuta> thanks, didn't know about ddebs. is that ddebs.ubuntu.com?
[09:42] <persia> Yep.
[09:43] <persia> Some packages provide a -dbg package, but just about everything has a -dbgsym.
[09:51] <marmuta> almost there, where do I get the public key for ddebs? can't find anything about it in the wiki
[09:51]  * persia digs at the wiki
[09:51] <persia> https://wiki.ubuntu.com/DebuggingProgramCrash
[10:08] <marmuta> thank you persia, symbols are installed, but now gdb doesn't stop anymore :/
[10:09] <persia> heh.  heisenbug.  Annoying those.  If you enable apport, does it trap it?
[10:10] <marmuta> does apport get better backtraces?
[10:10] <marmuta> i'll try
[10:10] <persia> apport doesn't get better backtraces, but sometimes it works when things don't run under gdb.
[10:11] <persia> apport traps the coredump into a .crash file in /var/crash, and you can use apport-retrace to dig out a stack trace, so the program isn't actually running under gdb.
[10:13] <marmuta> good, i'll see what i can do
[10:15] <marmuta> but wait, g-s-m still doesn't run, the bug is still there, just gdb doesn't stop
[10:15] <persia> Now I'm confused.  Is the bug not a crash?
[10:15] <marmuta> i tried handle SIGABORT stop nopass
[10:15] <persia> That ought to crash it.
[10:16] <marmuta> no, i believe its an uncaught exception
[10:16] <persia> How is the application failing?
[10:17] <marmuta> i just comes back in the terminal and gdb said before Program received signal SIGABRT, Aborted.
[10:18] <marmuta> now it says exited normally but nothing shows up
[10:18] <persia> Stepping back.  Before you did anything, how was the application failing?
[10:19] <marmuta> running it on the comand line just came back, no error
[10:19] <persia> And what did you expect it to do?
[10:20] <marmuta> in gdb i got sigabrt and a callstack in terminate, the clibs finall exception exit
[10:20] <marmuta> i expected it to open the window :) which it didnt
[10:21] <persia> And you installed the debugging symbols, and now what does it do?
[10:22] <marmuta> still the same, with the difference that gdb doen't show anything unusual...still no window
[10:22] <persia> And if you enable apport, does it trap a crash?
[10:24] <marmuta> i was about to do that, i'm currently figuring out how i disabled it :)
[10:25] <persia> It was probably disabled for you when the release happened :)  Look in /etc/default
[10:25] <persia> I don't advocate doing more than enabling apport, but https://wiki.ubuntu.com/Testing/EnableProposed provides instructions.
[10:26] <marmuta> ... it was already enabled=1
[10:26] <persia> And if you run a while true; echo hello and then kill it, does apport trigger?
[10:27] <persia> Sorry, that's `while true; do echo hello; done`
[10:27] <marmuta> i did the sh -c 'kill -SEGV $$' from the wiki, didnt trigger
[10:28] <persia> Have you restarted apport since you enabled it?
[10:29] <marmuta> yep i did what the wiki you gave me said: sudo /etc/init.d/apport start
[10:29] <persia> Odd.  Should have worked.  You have apport installed, I presume?
[10:30] <marmuta> lol, i'll check
[10:30] <marmuta> yes, but not apport-retrace
[10:34] <persia> Well, I'm confused how to suggest you proceed.
[10:35] <persia> Sounds like you've got a crash, but when you install the debugging symbols, you can't get the crash.
[10:35] <persia> Usually, the way around this is to use apport to catch the crash without gdb, and apport-retrace to get the trace.
[10:35] <persia> With apport not working, I've no idea how to get a useful trace.
[10:36] <persia> Or if the application just works normally with the debugging symbols, that means the strip caused an issue, but that doesn't sound like what you've found.
[10:36] <marmuta> i wouldnt call it a crash, it's more a forced exit, maybe that's why apport doenst pick it up
[10:37] <marmuta> an it doesnt work normally with the symbols, the window never shows up
[10:38] <persia> How is a "forced exit" different from a crash?  Is the application exiting normally, and just not doing what it's supposed to do?
[10:38] <marmuta> I'll go and file the report with what i have, some libs symbols show up already.
[10:38] <persia> What's the exit code from the application?
[10:38] <persia> Without a complete stack trace, it's extremely unlikely anyone will actually wade through it.
[10:39] <marmuta> mhmm, ok
[10:39] <marmuta> now it gets stuck, there is a zombie g-s-m, i'll restart and get back to you
[10:39] <persia> There's lots of complete traces in Malone, so those of us who like the investigation of tracking down that class of bugs have lots of good ones to choose from.
[10:40] <persia> Good luck.  It probably just needs some persistence to find the exact issue: if well described, with a clean trace or other pointer to the problem, it shouldn't be that hard to fix.
[10:40] <marmuta> yes, it just needs an exception handler i guess
[10:41] <marmuta> thank you for now
[10:41] <persia> Probably.  90% of crashes seem to be unintialised pointers, ignoring return codes, or unhandled exceptions.
[10:55] <marmuta> persia, I can't reproduce it anymore, installing the dbgsym must have fixed it and uninstalling them didn't break it
[10:56] <persia> Exceedingly odd.  I wonder what happened in the meantime.
[10:56] <persia> Your system now works as expected?
[10:56] <marmuta> yep, gsm comes up no problem, from terminal and panel
[10:58] <marmuta> i'll keep an I on it
[10:58] <marmuta> and thank you, you've been a great help
[10:58] <marmuta> s/I/eye/
[10:58] <persia> Well, you're welcome.  Sorry that we didn't actually find the problem.
[12:46] <orogor> hi here
[12:46] <orogor> i do have some problem with lvm2 on amd64 , lvm partitiosn arent  activated at boot
[12:46] <orogor> this  and at boot time i do have some strange error , "env 34 not found"  or something liek that
[13:06] <orogor> hi again
[13:06] <orogor> anyone around ?
[13:09] <orogor> lvm doesnt  get activated at boot time , saw this is suposzed to be done by an udev rule , unfortunatly i find it hard to read udev rules and woudl gladly accept some help
[13:26] <orogor> can anyone help me tracking a bug in startuip script/udev/lvm ?
[13:32] <albert23> orogor: you are using jaunty I suppose?
[13:33] <albert23> orogor: If you do, the fix is in bug 314879
[13:35] <orogor> albert23, using ubuntu amd64
[13:36] <orogor> ubuntu hardy
[13:39] <albert23> orogor: Then I don't know. You can try and see if vgscan finds the partition
[13:39] <orogor> it does
[13:39] <orogor> all works fine , just partitions fdont get activated at boot time
[13:39] <orogor> activation is done by an udev rule
[13:39] <orogor> restarting udev does activate the rule and the lvm
[13:39] <orogor> but at the system startup udev start doesn t seems to do that
[13:41] <albert23> orogor: then you will need to check your initrd. You may want to boot into busybox and do some testing there
[13:42] <albert23> I have lvm on hardy/amd64 as well, and it works for me
[13:46] <orogor> albert23, how do i do that ?
[13:47] <orogor> humm i think i rememebr
[13:48] <albert23> orogor: append break=bottom to your kernel line in grub. That will bring you in busybox
[13:48] <albert23> You can do that in /boot/grub/menu.lst or in the grub menu when you boot
[13:48] <albert23> Then in busybox try lvm vgscan
[13:49] <albert23> Also check if /etc/udev/rules./85-lvm2.rules exists
[13:49] <orogor> it does
[13:50] <albert23> I mean, in the busybox
[13:50] <orogor> thats  why when i restar udev , the lvm get activated
[13:50] <orogor> haa
[13:50] <orogor> whats the busybox fs ?
[13:50] <albert23> busybox is a small shell in the initrd
[13:51] <orogor> well i meant initrd
[13:51] <orogor> afair , gunziping initrd and loopback mounting it is ok
[13:52] <albert23> To prevent a lot of testing, just updating your initrd with update-initramfs -u and make sure grub/menu.lst points to the correct initrd may save you some time
[13:53] <orogor> i did that already
[13:53] <orogor> dpkg-reconfigure lvm2 make a new initrd
[13:53] <albert23> make sure it updates the right initrd
[13:54] <albert23> i.e. I have both -generic and -server, and sometimes only -server gets updated
[13:57] <albert23> So look in grub/menu.lst which initrd is used, and make sure that one gets a new timestamp if you update initramfs
[13:58] <orogor> haaaa
[13:58] <orogor> somethign around taht yes
[13:58] <orogor> oot@pascalou:/tmp# dpkg-reconfigure lvm2
[13:58] <orogor> Backing up any LVM2 metadata that may exist...done.
[13:58] <orogor> update-initramfs: Generating /boot/initrd.img-2.6.24-23-generic
[13:58] <orogor> root@pascalou:/tmp# uname -a
[13:58] <orogor> Linux pascalou 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 GNU/Linux
[13:59] <albert23> Ah, that may explain....
[14:02] <orogor> graa
[14:02] <orogor> which package hold the wizard for grub ?
[14:04] <albert23> it may be easier to just edit menu.lst manually
[14:08] <orogor> trying the reboot
[14:12] <orogor> works now , thanks a lot
[14:13] <albert23> orogor: no problem
[14:15] <orogor> there s  still the small error about exec 34 not found
[14:15] <orogor> no idea what it s related to
[14:16] <orogor> and i looked and apparently i ll have some issues to get booglogd working
[14:16] <orogor> bianry isn t installed only the init script
[14:17] <orogor> bootlogd binary belongs to sysvinit , which would replace a lot of low level script
[14:24] <albert23> orogor: you probably don't want sysvinit. It's replaced by upstart in Ubuntu...
[16:10] <CheesyMcPuffs> can someone help me?
[16:10] <CheesyMcPuffs> my cd drive is not being recognized
[16:11] <persia> CheesyMcPuffs, How is it connected?
[16:11] <ogra> in jaunty ?
[16:11] <CheesyMcPuffs> it is through a SATA
[16:11] <CheesyMcPuffs> in 8.10 intrepid
[16:11] <CheesyMcPuffs> and WinXP recogniyes it
[16:12]  * ogra just knows jaunty had a fix yesterday for cd drives
[16:12] <persia> If you run dmesg | less, do you see anything shown?
[16:12] <CheesyMcPuffs> wait, do dmesg | less
[16:13] <CheesyMcPuffs> yes, quite a bit is shown
[16:13] <persia> Run that in a terminal.  It should show *lots* of output.  Somewhere in there should be some information about a CD drive.
[16:13] <persia> If you don't see anything there, it's a bug in "linux".  If you see something there, and it's just not accessible, it's a bug somewhere else (and there are several candidates).
[16:14] <CheesyMcPuffs> no there is a lot, goign though it
[16:15] <CheesyMcPuffs> ok: this is all it says about my ata2, where the cd drive is located: [    4.580031] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[16:15] <CheesyMcPuffs> [    4.588028] ata2.00: NODEV after polling detection
[16:17] <persia> RIght.  Sounds like a kernel thing.  File a bug against the linux source package, including your dmesg output, the output of lscpi -vvnn, and describe the specific model of your drive, how it is connected, and that it doesn't work.
[16:17] <persia> You'll probably be asked to perform some testing after a while, and then someone ought be able to fix it.  No idea about scheduling or anything.
[16:18] <CheesyMcPuffs> oh
[16:18] <CheesyMcPuffs> is there any way to see if linux does recognize it but didnt mount
[16:18] <CheesyMcPuffs> like in /dev
[16:18] <CheesyMcPuffs> then try to add it to fstab?
[16:19] <persia> Yes.  You've just done that.  It said "NODEV after polling detection", which means it didn't find the device.
[16:19] <CheesyMcPuffs> oh
[16:19] <CheesyMcPuffs> nevermind then
[16:19] <CheesyMcPuffs> ty
[16:19] <persia> You could look around at your /dev/sd* files to see if there's something we missed, but I suspect it didn't get recognised.
[16:19] <ogra> well, should be /dev/scdX
[16:19] <ogra> *if* there is a cdrom
[16:20] <CheesyMcPuffs> oh idk, if this helps, on start up, i have the boot sequence going, and it hits a few errors along the way with i think it was device sr0
[16:20] <ogra> errors ?
[16:20] <CheesyMcPuffs> yea
[16:20] <ogra> (they should be in your dmesg output)
[16:21] <CheesyMcPuffs> it will say: I/O error sector: xxxxxxxxxx
[16:21] <CheesyMcPuffs> then the next line will list the block
[16:22] <CheesyMcPuffs> well ty for ur help, ill submit it, goes to launchpad right?
[16:22] <persia> RIght.  https://launchpad.net/ubuntu/+source/linux/+filebug
[16:24] <CheesyMcPuffs> any other info i should send beside the dmesg and lscpi -vvnn
[16:26] <persia> Make and model of your drive, and precise description of how it's connected.
[16:28] <CheesyMcPuffs> like, Sata, through ata2, molex power?
[16:28] <CheesyMcPuffs> oh, when it asks for package, what should i put?
[16:28] <persia> That sounds about right.  If ATA2 has multiple attachment points, then you'd want to specify which as well.
[16:28] <persia> linux
[16:28] <CheesyMcPuffs> oh
[16:28] <CheesyMcPuffs> lol
[16:29] <persia> It's a kernel issue, because it didn't recognise the device at all (I think).  If I'm wrong, the kernel devs will quickly kick it back into userspace.
[16:29] <CheesyMcPuffs> userspace?
[16:30] <persia> things not the kernel :)
[16:30] <CheesyMcPuffs> Windows XP is able to read and write from it, so.. i know its connected and functioning, just not being recognized, sry if this seems redundant
[16:30] <CheesyMcPuffs> ohh ok
[16:31] <persia> No, that's why I say file a bug.  If you hadn't said that, I'd ask you to check your cables first :)
[16:35] <CheesyMcPuffs> lol
[16:35] <CheesyMcPuffs> is this good, for the extra info? This is my second CD drive, it is plugged into the second Sata slot on the motherboard, it goes through the Sata interface and uses a Sata power cable.
[16:35] <CheesyMcPuffs> Info:
[16:35] <CheesyMcPuffs> Lite-on it corp.
[16:35] <CheesyMcPuffs> CD-RW/DVD-ROM DRIVE
[16:35] <CheesyMcPuffs> MODEL SHC-52S7K
[16:36] <persia> I think so, but I'm not great with kernel bug triage: if it's insufficient, someone will ask for more information.
[16:37] <CheesyMcPuffs> how can i get read out from terminal?
[16:37] <CheesyMcPuffs> is it saved to a file?
[16:37] <ogra> smells related to bug 267838
[16:37] <ogra> and cjwatson seems to seek for more info on that actually
[16:38] <CheesyMcPuffs> :O
[16:38] <ogra> you could mention there that you have an installed system and the kernel doesnt recognize the drive either
[16:38] <persia> CheesyMcPuffs, dmesg is in /var/log/dmesg.  For saving lspci -vvnn, you'll want to do something like `lspci -vvnn > lscpi-vvnn.out` froma terminal.
[16:38] <ogra> that would help him a lot since he doesnt need to seek the bug in cdrom-detect of the installer anymore :)
[16:39] <CheesyMcPuffs> want me to comment?
[16:39] <persia> Indeed.
[16:39] <CheesyMcPuffs> kk
[16:39] <CheesyMcPuffs> so just comment, but not send in bug
[16:40] <persia> If you could incude your lcpci -vvnn there, and report that the installed system also doesn't recognise the drive, it would certainly make cjwatson happier.
[16:43] <torkiano> hello, if a bug is about KDE3 it will be resolved or I tell buf reporter to try with the KDE4 version?
[16:44] <CheesyMcPuffs> persia, i did the lspci -vvnn > lscpi-vvnn.out, where does it save to?
[16:44] <torkiano> bug 47429
[16:46] <CheesyMcPuffs> oh nevermind, it was in my folder, lol
[16:46] <persia> CheesyMcPuffs, lspci-vvnn.out in whatever directory you ran the command.
[16:46] <CheesyMcPuffs> yea
[16:46] <CheesyMcPuffs> sry about that had a brain fart, i must sound pretty dumb, but im just kinda nervous, this is my first time really doing something like this with ubuntu
[16:50] <ogra> dont worry, we have all once started like that ;)
[16:50] <CheesyMcPuffs> wait, should i have done the command with sudo, or does it matter with permission
[16:51] <tawmas> Hello
[16:52] <persia> CheesyMcPuffs, For lspci, yes, please do with sudo.  Sorry.
[16:52] <persia> tawmas, Hello.
[16:52] <CheesyMcPuffs> oh... already posted.. does it really matter?
[16:53] <tawmas> I have a bug whereby all multimedia and otherwise extended keys on my keyboard log me out abruptly (a la CTRL-ALT-BACKSPACE). What would be a good package to file that against? Also, what kind of information do I need to provide? I've checked keyboard shortcuts and they seem ok
[16:53] <persia> CheesyMcPuffs, Do it again, into lspci2-vvnn.out, and see if there is a big difference.  It may not matter.
[16:54] <CheesyMcPuffs> kk
[16:54] <tawmas> persia, Hello to you!
[16:55] <CheesyMcPuffs> oh, yea, there is
[16:56] <persia> Then if it's a big difference, you'll want to repost.
[17:03] <CheesyMcPuffs> is there a way i can edit or delete my posts on launchpad?
[17:04] <ogra> nope
[17:04] <ogra> just add a new comment saying the former was incomplete
[17:05] <CheesyMcPuffs> i just said: Sry for the double post, forgot to run commands under sudo, and say that the drive is recognized while running windows XP.
[17:07] <tawmas> Sorry I got disconnected. If anybody replied, would you please repeat?
[17:08] <CheesyMcPuffs> nothing happened
[17:09] <CheesyMcPuffs> * tawmas (n=tawmas@adsl203-149-091.mclink.it) hat #ubuntu-bugs betreten
 Sorry I got disconnected. If anybody replied, would you please repeat?
[17:09] <CheesyMcPuffs> * bdrung (n=bdrung@p4FE21EBE.dip.t-dialin.net) hat #ubuntu-bugs betreten
 nothing happened* tawmas (n=tawmas@adsl203-149-091.mclink.it) hat #ubuntu-bugs betreten
 Sorry I got disconnected. If anybody replied, would you please repeat?
[17:09] <CheesyMcPuffs> * bdrung (n=bdrung@p4FE21EBE.dip.t-dialin.net) hat #ubuntu-bugs betreten
 nothing happened
[17:09] <CheesyMcPuffs> its in german
[17:10] <tawmas> thanks
[17:10] <CheesyMcPuffs> oops... copied wrong posts
[17:10] <CheesyMcPuffs> oh well
[17:10] <CheesyMcPuffs> yea
[17:10] <tawmas> :-)
[17:10] <CheesyMcPuffs> * tawmas hat die Verbindung getrennt (Remote closed the connection)
 i just said: Sry for the double post, forgot to run commands under sudo, and say that the drive is recognized while running windows XP.
[17:10] <CheesyMcPuffs> * tawmas (n=tawmas@adsl203-149-091.mclink.it) hat #ubuntu-bugs betreten
 Sorry I got disconnected. If anybody replied, would you please repeat?
[17:10] <CheesyMcPuffs> there we go, that correct
[17:11] <tawmas> K, thnx
[17:11] <CheesyMcPuffs> daß ist gut? jk
[18:02] <torkiano> Hello, Can someone mark bug 296814 as triagued?
[18:13] <ToHellWithGA> 304969
[18:14] <andresmujica> bug 304969
[18:14] <ToHellWithGA> do y'all know roughly how long it takes canonical and adobe to figure out how to get old versions working?
[18:14] <ToHellWithGA> thanks andresmujica
[18:14] <andresmujica> np
[18:14] <ToHellWithGA> i just installed 8.04 because of its long-term-edness but can't put flash on, kind of a bummer
[18:15] <andresmujica> hmm.. that issue is a recurrent topic....
[18:15] <ToHellWithGA> it seems like the kind of thing that would be an excellent candidate for a backport
[18:15] <ToHellWithGA> then again, i can understand that changing from version 9 to 10 could introduce other issues
[18:18] <andresmujica> this is probably the bug you're looking for
[18:18] <andresmujica> bug 235135
[19:30] <ToHellWithGA> andresmujica: 235135 seems much more complex than 304969
[19:31] <ToHellWithGA> if backporting could be avoided by updating a single broken link i'd settle for 9 rather than 10
[19:36] <andresmujica> yeap.. you're right
[19:37] <andresmujica> the problem is that flash has an ecosystem around it.. that involves pulseaudio and alsa...
[19:38] <andresmujica> why don't you check the adobe-plugin at the canonical partner repo
[19:38] <Bit_Breaker> hello. does anyone have any trouble with banshee?
[19:40] <andresmujica> do you have a specific bug?
[19:41] <Bit_Breaker> yes
[19:41] <Bit_Breaker> i will pastbin it
[19:42] <Bit_Breaker> here you go http://pastebin.com/m44eeb5d1
[19:43] <Bit_Breaker> also i am using the PPA instructions here https://edge.launchpad.net/~banshee-team/+archive
[19:44] <Bit_Breaker> i get the same error from synaptic as well
[19:46] <Bit_Breaker>  andresmujica: are you still there?
[19:52] <andresmujica> yeap
[19:53] <andresmujica> bit_breaker: i was referring to an already reported bug, maybe you can ask for some support at #ubuntu.
[19:53] <Bit_Breaker> has this bug been reported already?
[19:54] <andresmujica> hmm don't know really, take into account that you're using the banshee-team PPA , so the support probably goes for them.  let me check a sec...
[19:55] <andresmujica> take a look in here https://bugs.edge.launchpad.net/banshee  maybe you'll find the bug, if not don't hesitate on report it there
[19:56] <andresmujica> https://bugs.edge.launchpad.net/banshee/+filebug
[20:02] <torkiano> hello, i'd like to participate in 5-a-day iniciative but when i should upload my bug numbers? ( 5-a-day --add 296853
[20:03] <torkiano> When the bug is confirmed? triaged? when the bug has the correct package assigned?...
[20:06] <greg-g> torkiano: when you have done some kind of postive work on the bug.  There isn't a hard and fast rule.  But, the more work you put into a triaging a bug the better.
[20:06] <torkiano> ok, thank you greg-g
[20:07] <greg-g> np, thanks for participating!
[20:07] <torkiano> is there a plan to integrate 5-a-day on launchpad?
[20:10] <andresmujica> torkiano, you can use the applet... about the launchpad what do you mean?
[20:10] <andresmujica> something like autoreporting?
[20:11] <torkiano> andresmujica: more integrated, with statistics in your launchpad / team account, not only in daniel.holba.ch
[20:12] <torkiano> people like the statistics ;-)
[20:18] <andresmujica> ohh yeap.. :)
[20:18] <andresmujica> ask daniel, maybe it's on the path
[20:19] <andresmujica> roadmap i mean..
[20:19] <greg-g> andresmujica: there is talk of that, not sure who is working on it now or what the progress is.
[20:20] <greg-g> I'm sure if someone wants to help out we can find the right person to talk to.
[20:25] <andresmujica> yeap, i've been thinking about auto reporting, something like every time you touch a bug the 5-a-day stats would be updated, but i came to the conclusion that it would be against the spirit of 5-a-day
[20:26] <andresmujica> but the statistics into launchpad itself would be nice..
[21:30] <andresmujica> someone recalls the url for making a stacktrace search in gnome's bugzilla?
[21:35] <tawmas> Hi! What is the best package for filing a bug about multimedia keys and all other "special" keys on extended keyboards causing X to crash?