On Wed, 22 Sep 2004, Paul Nasrat wrote:
On Wed, 2004-09-22 at 07:43 -0400, Robert P. J. Day wrote:
i realized shortly after i posted this to the FC test list that it
really deserved to go here instead. thoughts?
Bugzilla is the appropriate place for installation bugs. Email is good
for increasing awareness - but it needs to be in bugzilla.
so i double clicked on the "tmp" entry in the "Disk Setup" window ... and got
a python exception traceback. just copying from the display manually, the
traceback routine list is:
self.editCb()
self.editLVMVolumeGroup(vgrequest)
...
Without the full trace it's hard to tell what's going on - are you
experiencing this error:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132217
If so add more details to that bug, else create a new bug ensuring you
get an anaconda dump.
can i ask how i should have queried bugzilla for this bug? i've
perpetually had problems with bugzilla, making queries as general as
possible and still managing to miss filed bugs.
for instance, what search criteria should i have used for this error?
normally, since it occurred during an install of FC3t2, i would have
selected "Fedora Core"/"fc3test2"/"anaconda". but even with a
wide-open status field, that bug would not have shown up, since that
bug is filed under "Fedora Core"/"devel".
is there some method to the madness of how bugs are categorized?
rday
