[07:54] <mrooney> would anyone mind looking at bug #235600 and seeing if I properly triaged it (it is pretty short). I am not sure what else I can do, just wait?
[07:55] <mrooney> I don't know if the package is correct, that's one thing, that is just how it was filed
[08:04] <Rocket2DMn> mrooney, im not pro but I dont think those belong triaged under compiz stuff
[08:05] <mrooney> Rocket2DMn: oh okay, why do you say that
[08:06] <Rocket2DMn> if the bug occurs only under compiz, then it should be a problem relating to compiz
[08:06] <Rocket2DMn> otherwise, those menus are all related to gnome preferences (i dont know what the exact package is)
[08:10] <mrooney> well Expo view only exists in compiz certainly
[08:10] <mrooney> so the bug inherently can only exist in compiz
[08:11] <Rocket2DMn> ah Expo is a compiz plugin, duh.  sorry
[08:11] <Rocket2DMn> its been awhile since i used compiz
[08:12] <Rocket2DMn> in which case it seems right to me :)
[08:19] <mrooney> Rocket2DMn: okay great, thanks, I wasn't sure about compiz vs the plugins-main but I think you have affirmed that it is right
[08:19] <mrooney> it is a plugin after all
[08:20] <Rocket2DMn> yes
[08:20] <mrooney> I just wish someone from compiz would say something
[08:20] <mrooney> launchpad needs a 'poke' feature :)
[08:20] <Rocket2DMn> if for some reason it is wrong, im sure they will understand upstream
[08:28] <Hobbsee> mrooney: expose would be a plugin, not core compiz, so i'm guessing it's in hte right place.  that being said, the same team of people tend to look at all compiz packages
[09:28] <Iulian> Heya
[11:59] <techno_freak> i donno how to figure what's the bug, but suddenly all my media players have muted out and they play in uber slow motion. but youtube within FF plays normally. :S
[12:03] <techno_freak> ok, it can't play system sounds even, might be an alsa issue
[14:39] <qense> hello
[14:40] <techno_freak> hello
[15:41] <qense> Is this a bug at all: bug 229477 ? Or is this just an hardware error?
[16:09]  * DOOM_NX mpainw windows
[16:53] <jcastro> bdmurray: the freshubuntu podcast guys are looking for a bug person for an audio interview.
[16:53] <jcastro> ogasawara: You should do it too!
[17:02] <bdmurray> mvo: bug 40058 has a milestone for 6.06
[17:03] <bdmurray> mvo: should it be rolled forward?
[17:05] <bdmurray> hmm, it looks like it has been fixed before
[17:26]  * persia makes a scary face
[17:26]  * bddebian runs
[17:26] <persia> bdmurray: Re: 40058: it's essentialy unsoluable.  There is a fixed update interval for changelogs.ubuntu.com, and anyone pulling an update before the next refresh gets hit by that bug.
[17:27] <bddebian> Boo
[17:27] <persia> It's currently always sorted for a given package within 4 hours, but...
[17:27]  * persia supposes one might create some sort of push-based feed into changelogs.ubuntu.com, but that's a deep infrastructural change
[17:28] <bdmurray> persia: okay, I'd saw one suggestion about pulling the changelog out of the downloaded package but I guess the package isn't downloaded to your local system when you see that message
[17:29] <persia> bdmurray: Right.  If you have apt-listchanges installed, it shows the changelogs for the affected packages, as this is post-download.
[17:29] <persia> Note that the original cause of the bug (main/universe changes) has been solved, but users may still encounter nearly identical symptoms.
[17:33] <persia> bdmurray: Checking the SRU status in Dapper, Dapper users can still encounter the original bug for packages that were moved between main and universe, but it's unlikely that we'll be doing any more moves anytime soon.
[17:59] <rubikcube> hi, any idea with respect to which point I wasn't detailed enough here in the OP? https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/238634
[17:59] <persia> rubikcube: I'm not sure you were too vague, but it's not easy to identify the cause.
[18:00] <persia> As it stands, there's no good way to solve the bug, as setting the extra dependency at install-time is not easy with the way apt works.
[18:00] <rubikcube> "cause" as in what was done to reproduce this or as in what went wrong (or not) in the package management?
[18:00] <persia> Further, what do you do for users who have multiple language packs?
[18:00] <persia> "cause" as in what went wrong.
[18:01] <persia> I'm not sure what is required for triage, although the response you got wasn't helpful.
[18:02] <rubikcube> I don't know enough about the whole apt/deb system :-)  If it had the possibility of dynamic dependencies, that might be not too difficult
[18:02] <rubikcube> well, it's just the canned auto-repsonse, afaict
[18:04] <persia> Yeah, I think you hit a canned autoresponse.  Your Description lays out the steps to reproduce fairly well.  I'll set back to "New", to avoid expiry, but can't test directly (I don't have a Kubuntu installation) to confirm.
[18:04] <jjesse> what is the bug#
[18:04] <rubikcube> sadly I don't even know if that behaviour is fixed in hardy already, I could reproduce it in gutsy kubuntu, but we get people with that problem from times to times in #gimp
[18:04] <rubikcube> 238634
[18:05] <persia> jjesse: bug #238634
[18:05] <persia> rubikcube: I doubt it's fixed, and suspect it will be around for quite a long while.  It's not an easy bug to solve.
[18:06] <rubikcube> I suppose you opt against installing the respective language packs for all of gnome/kde/xfce/whatever by default?
[18:07] <persia> rubikcube: That would likely prevent the creation of a Kubuntu CD (which I believe will be again a goal soon).
[18:08] <rubikcube> it would only have to be the language packs...  Or don't separate the language from programs.  But that would really increase the download/cd size even more
[18:09] <persia> rubikcube: Right.  It's hard.  IIf you come up with a solution that doesn't break anything, and does the right thing, please follow up in the bug report.
[18:10] <rubikcube> do you know if deb dependencies are scriptable?
[18:10] <persia> They are, but only at package build time.
[18:10] <rubikcube> that's the way I'd do it on gentoo
[18:12] <rubikcube> something like having one language meta pack per language, and all i18n'ed packages would check which lang-meta-* packages are installed and as a result depend on the respective individual/specific language package
[18:12] <rubikcube> dunno if this is doable :-)
[18:22] <rubikcube> I'll ask the debian people for a proposed solution :-) :-)
[18:55] <jayson_> Hello people, i'm trying to debug firefox and receive a lot of no debugging symbols. I have followed the informations on wiki. How can I debug this ?
[20:48] <Awsoonn> https://bugs.edge.launchpad.net/ubuntu/+source/meta-gnome2/+bug/237803
[20:49] <Awsoonn> should this be under 'gnome-applets'?
[20:53] <pedro_> Awsoonn: that might be gnome-panel
[20:54] <pedro_> btw i cannot reproduce that here either
[20:54] <Awsoonn> nor can I
[21:04] <Awsoonn> hmm
[21:04] <Awsoonn> ...
[21:06] <Awsoonn> anyone alive?
[21:08] <Awsoonn> the internet took a well deserved crap?
[21:25] <jaysonsantos> https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/239206
[21:25] <jaysonsantos> Can I continue runing a process when i receive a seg fault like that link ?
[21:37] <Awsoonn> jaysonsantos: not that I know of
[21:38] <jaysonsantos> Awsoonn> I don't remember all commands in gdb, but it have a "pass", that can jump the error ?
[21:42] <Awsoonn> jaysonsantos: not that I am aware of
[21:46] <Old_Soldier> jaysonsantos: the only thing you can do in grub is go into the edit mode and edit your options in menu list preboot. if grub cant find menu.lst then you need to do some grub magic :) google "grub hermanzone" for some very good grub info
[21:56] <Awsoonn> https://bugs.edge.launchpad.net/ubuntu/+source/meta-gnome2/+bug/238622
[21:57] <Awsoonn> what should that go under?
[21:59] <Awsoonn> appears that the next gnome has it taken care of in any case
[22:00] <Awsoonn> maybe language-pack-gnome-uz ?
[22:06] <siretart> Awsoonn: the bug is not clear at all what the actual problem is. so it is hard to say what package this is about
[22:07] <siretart> Awsoonn: my guess would be glibc, set the bug to 'incomplete' and ask for clarification what the reporter actually expects to be done. currently the bug is causing only confusion
[22:07]  * Awsoonn thumbs up
[23:05]  * siretart is (again) on an ffmpeg bug triaging rampage...
[23:15] <siretart> yay! https://bugs.edge.launchpad.net/ubuntu/+source/ffmpeg/+bugs?field.status%3Alist=NEW is zero now! :)
[23:17] <james_w> go siretart! :-)
[23:18] <greg-g> wow, look at all of those incomplete
[23:18] <greg-g> well done
[23:21] <siretart> greg-g: yes. I cannot do much with them if they don't provide enough information to reproduce it. that particularily includes a testfile
[23:22]  * siretart iieks at the list of bugs in https://bugs.edge.launchpad.net/ubuntu/+source/xine-lib
[23:24] <m-c> Hello - I am trying to file a bug against the Thoggen package, but Launchpad says it might be maintained upstream.  How do I determine what organization maintains a package?  How do I determine who is the upstream provider?
[23:25]  * siretart needs sleep. good night!
[23:25] <netzmeister> n8
[23:26] <james_w> m-c: where does launchpad say that?
[23:26] <m-c> https://bugs.launchpad.net/thoggen/+filebug  james_w
[23:27] <james_w> m-c: ah, you want https://bugs.launchpad.net/ubuntu/+source/thoggen/+filebug
[23:27] <james_w> so that it files it against the ubuntu package.
[23:27] <m-c> Okay, thank you
[23:27] <james_w> if it is an upstream bug you can file it in the upstream bug tracker
[23:29] <james_w> http://sourceforge.net/tracker/?group_id=124800 it looks like
[23:29] <m-c> Yes, but is that the upstream source, or just the project homepage?
[23:30] <m-c> As far as I know, upstream implied the organization is creating the .DEB package, which is used to create the Ubuntu-specific package.  But, I am no expert!  :-D
[23:30] <james_w> that was where the upstream homepage sent me for filing bugs
[23:31] <m-c> Okay, well, the bug is already in that tracking database.  I was going to post it to the Launchpad, to get it more visibility, but if it is not necessary, then I will leave well enough alone.
[23:32] <m-c> *the bug is already in that sourceforge tracking database
[23:33] <james_w> m-c: ah, in that case you can file it and then link the two in launchpad so that we can track the fix.
[23:33] <m-c> Okay, thanks for your advice.
[23:34] <greg-g> if you need any help with linking the two bug reports, let us know
[23:34] <james_w> if you're not sure how to link them I'd be happy to talk you through it.
[23:34]  * james_w high-fives greg-g 
[23:34] <greg-g> go teamwork! :)
[23:35] <m-c> I was just going to put a link to the web page in the Further Information... is there more?  :)
[23:36] <greg-g> m-c: go ahead and do that and we can do it for you.  Or tell you how to make it so Launchpad actually checks that link every day to see if the status of that bug (in sourceforge) has changed
[23:37] <m-c> greg-g: Sure, I am always open to learning something new.
[23:37] <greg-g> awesome
[23:38] <greg-g> m-c: well, a good way to start is to just report the issue, with a good title and description, then at the bottom of the description put the link to the Sourceforge bug
[23:38] <greg-g> then I can walk you through from there
[23:39] <greg-g> so, after you have submitted the bug, paste the url here
[23:48] <m-c> The link to the new Launchpad bug report is here  >> https://bugs.launchpad.net/ubuntu/+source/thoggen/+bug/239317
[23:48]  * greg-g looks
[23:49] <greg-g> m-c: the link you gave is to a svn log, not a bug report
[23:49] <greg-g> do you have the link to the bug report?
[23:50] <m-c> I was only given that link from Tim
[23:50] <m-c> I looked in the bug list on Sourceforge and did not see this issue listed
[23:50] <greg-g> ahh, ok
[23:50] <m-c> http://sourceforge.net/tracker/?atid=700637&group_id=124800&func=browse
[23:50] <greg-g> then yeah, that is fine as is
[23:50] <greg-g> the linking is for bug reports
[23:51] <m-c> All looks okay, then?
[23:52] <greg-g> I would point sebastian droge to the bug report, so he can confirm it and mark himself as working on it (don't assign it to him youself though)
[23:53] <m-c> It is a nice application - putting DVD files into a free-er format, but I am concerned it will never work in Hardy, since the bug is not critical.
[23:53] <greg-g> slomo_: new bug 239317 mentions you are working on it.  Feel free to update it's status and assignment if that is correct.
[23:53] <m-c> Don't subscribe him?  Okay, that's new to me.  I will send him an email.
[23:54] <greg-g> I just pinged him
[23:54] <m-c> oops, did not think tolook for him online with the "_"  :-)  Thanks for your help, greg-g !!
[23:54] <m-c> Have a great day.
[23:55] <greg-g> uh, tah
[23:56] <Awsoonn> what package might this be best suited? LP238733
[23:57] <Awsoonn> https://bugs.edge.launchpad.net/ubuntu/+bug/238733