On Mon, Mar 07, 2005 at 07:30:12PM -0800 or thereabouts, ofey aikon wrote: > I am facing the same issue as described in > http://bugzilla.gnome.org/show_bug.cgi?id=144269 and was wondering > about the solution to the issue. Bugzilla says status=UNCONFIRMED. >[...] > I am a newbie and was wondering what this means in regard to the fix > for the bug.
I think that this is an oversight. A slightly misleading one, too. Bugs sent in to Bugzilla mostly begin as Unconfirmed, and when someone else is able to reproduce it, they move from Unconfirmed to New or to Assigned. So it's referring to whether the bug itself is confirmed to exist or not; and not to anything to do with any fixes. And since there is lots of discussion and several patches, it probably should have been updated. But hasn't been. Sorry :) (Since it is a gtk bug, I am reluctant to mess with the status field: I don't think I have ever touched a gtk bug in my life and I don't know how the gtk gang do things.) There is a list of "What do all these fields mean, anyway?" at http://bugzilla.gnome.org/bug_status.html If you're not one of the people in that discussion and this bug affects you, it is probably worth creating a bugzilla account and adding yourself to the Cc list of that bug. Adding a comment about "This affects me on (anything relevant about your platform)" can't hurt either, and might get it out of unconfirmed-ness. Telsa _______________________________________________ Gnome-bugsquad mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-bugsquad
