Bug 623949 - Pressing the edit button in the component line of some bug lets fedora loop
Summary: Pressing the edit button in the component line of some bug lets fedora loop
Alias: None
Product: Fedora
Classification: Fedora
Component: bugzilla   
(Show other bugs)
Version: 14
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Itamar Reis Peixoto
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-13 09:08 UTC by Joachim Backes
Modified: 2010-08-13 10:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-13 10:41:34 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Joachim Backes 2010-08-13 09:08:57 UTC
Description of problem:
I wanted to edit the component of some bug in the bugzilla db, so I pressed the edit button in the component line of that bug. I did this in firefox-3.6.4. Almost immediataly I did this, firefox began to loop. 

I tried this with several bugs, each time with the same result

Version-Release number of selected component (if applicable):
3.4.7+, not 3.6

How reproducible:

Steps to Reproduce:
1.Open some bug
2.Press "edit" in the component line
Actual results:
firefox loops

Expected results:

Additional info:

I did not test this with other browsers, and I don't know whether this is a firefox or a bugzilla issue.

Comment 1 Joachim Backes 2010-08-13 09:25:36 UTC
I tested with opera-10.61: same result.

Comment 2 Joachim Backes 2010-08-13 10:41:34 UTC
Seems my box is too slow (dual core Intel(R) Core(TM)2 CPU 6300  @ 1.86GHz) is too slow :-( : I have to wait for about 1 min until the edit dialog opens.

Comment 3 Joachim Backes 2010-08-13 10:52:16 UTC
Now I tested again: It had to wait more than 60 secs until I could open the component pulldown menue.

Is my CPU too slow? Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz :-(

Comment 4 Joachim Backes 2010-08-13 10:53:30 UTC
Please reopen the issue. I can't imagine that my procs are too slow.

Note You need to log in before you can comment on or make changes to this bug.