Bug 120217 - Removing from cc doesn't mix with anything
Summary: Removing from cc doesn't mix with anything
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 2.8
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-06 21:14 UTC by Pete Zaitcev
Modified: 2007-04-18 17:05 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-07-15 22:40:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Pete Zaitcev 2004-04-06 21:14:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
When I mark something on cc list, them mark checkbox "remove
selected from cc list", and do anyting else with the bug,
for example change its status from NEW to ASSIGNED, Bugzilla
processes the request correctly, but then cannot refresh
the bug view. Instead it reports errors such as these:

Insecure dependency in exec while running with -T switch at
/var/www/bugzilla/bugzilla/process_bug.cgi line 1818.

SELECT profiles.userid, profiles.login_name,  profiles.disabledtext 
FROM profiles, logincookies WHERE logincookies.cookie = '76760' AND
profiles.userid = logincookies.userid AND profiles.login_name =
'zaitcev' AND (logincookies.ipaddr = '66.229.81.220' OR
logincookies.ipaddr = '66.229.81.220'): server closed the connection
unexpectedly at globals.pl line 337.


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


How reproducible:
Always

Steps to Reproduce:
0. Add something to cc list
1. mark something on cc list
2. mark checkbox "remove selected from cc list",
3. change its status from NEW to ASSIGNED
4. Commit


Actual Results:  "closed the connection unexpectedly at globals.pl
line 337."



Additional info:

Comment 1 David Lawrence 2004-07-15 22:40:02 UTC
Fixed.


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