On Mon, May 31, 2010 at 10:37 PM, Michal Schmidt <mschmidt@xxxxxxxxxx> wrote: > On Mon, 31 May 2010 14:42:21 +0800 Luming Yu wrote: >> Hmm, I must have filed the bug into wrong category since nothing >> happened with the problem.. > > It's been 5 days since you filed the bug, 2 of them weekend. > Surely you must realize that Fedora is not RHEL and that there's not > guaranteed upper bound on the response time. > > Also from your description I get the feeling that the bug is not that > severe, or is it? Did it crash only once, or is it reliably > reproducible? If you can reproduce it, please tell so in the bugreport. I heard the bug from one of my friends, and reproduced and confirmed it happened to me too. So I'm pretty sure it's reproducible. I have left the hung banshee there and suspend the system, and waiting on expert's input to proceed forward.. i.e. I'm ready to provide info from an already-hang banshee.. > >> Took a deeper look at the back trace, now >> it looks more like a gstreamer problem... any suggestion on that? (I >> can't move https://bugzilla.redhat.com/show_bug.cgi?id=595997 to >> right place) > > Don't you have an "edit" link shown next to "Component: banshee"? > I think the reporter of a bug can always edit the component but maybe > I'm wrong about that. > You are right, I must have used IE , I'm sorry about that. /l -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
