Bug 152590

Summary:	mid-air collision submit my changes anyway does nothing
Product:	[Community] Bugzilla	Reporter:	Alasdair Kergon <agk>
Component:	Bugzilla General	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-11-07 16:20:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alasdair Kergon 2005-03-30 15:47:26 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Description of problem:
Added text to a bug while someone else had also.
Got mid-air collision page.
'Submit my changes anyway' button has no effect - blank page (View Source is completely empty).

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=152162

Bug number is missing from first message of the page and page title:


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 #22 From Chris Adams (cmadams) 	on 2005-03-30 10:34 EST 	  	  	 
[snip]


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 152162


Client is Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
.

Additional info:

Comment 2 David Lawrence 2008-09-16 16:52:20 UTC

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.