Description of problem: I have gotten 3 mid-air collisions in the last few days. Version-Release number of selected component (if applicable): Bugzilla 2.18 (according to note somewhere on this page - there does not seem to be an 'about' in the menu). How reproducible: Too often Steps to Reproduce: I don't know for sure, but this is what I think I did. The two different machines seem to be an essential part. 1. Log on to bugzilla from machine #1 and look at a bug 2. Log on to bugzilla from machine #2 and look at same bug 3. Submit a change to bug from either machine. 4. Refresh bug page on 2nd machine. 5. Maybe this provokes a Mid-air collision 6. Wait half a day 7. Again refresh bug page on 2nd machine. 8. Maybe this provokes a Mid-air collision Actual results: This is the text from the mid-air collision page - copied from Firefox ------------------------------------------ Mid-air collision for ! Mid-air collision detected! Someone else has made changes to this bug at the same time you were trying to. The changes made were: Added comments: Comment #25 From Bob Gustafson (bobgus) on 2006-04-30 15:43 EST I'm done. I have a good FC5 install and am now downloading updates and then will download additional software and then will configure some of the things that don't get configured (vncserver, ..) I will also write up a suggestion for a better way to install Fedora (minium software on install, then add additional software from CD's and/or web after the basic Fedora is installed). This scheme would make it easier for you to debug, because there is only one minimum system being installed.. See you.. You have the following choices: * This will cause all of the above changes to be overwritten, except for the added comment(s). * Throw away my changes, and revisit bug 189971 Preset Queries My Bugs | install on RAID ---------------------------------------------------------- Expected results: Just a refresh of current state of bug Additional info: Two machines are more or less software identical - both FC5 with reasonably fresh updated software.
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code. Updating bug version to 3.2.
Please reopen this issue if it is still occurring with the latest version of Bugzilla.