288277 - Change Columns prevents use until COLUMNLIST cookie deleted

Status: RESOLVED WORKSFORME

(Bugzilla :: Query/Bug List, defect)

Description

[Simon Steele]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050228 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050228 Firefox/1.0+

Having visited the change columns page from the bug list, clicking either
"Change Columns" or "Reset to Bugzilla default" results in bugzilla not working
any more from this PC. This occurs with both Mozilla and IE as browser. 

Reproducible: Always

Steps to Reproduce:
1. Search for bugs with "UI" in them from the front page
2. Click "Change Columns"
3. Select a column like "votes"
4. Click "Change Columns" button
Actual Results:  
In IE I see an error page, in firefox nothing happens - you are stuck on the
change columns page. Deleting the COLUMNLIST cookie allows access again.

Expected Results:  
Add the votes column and re-display the list.

I am accessing the bugzilla over a VPN. Users on the local network do not
experience this problem, all users at this remote location do experience the
problem.

The apache error.log shows:

[Wed Mar 30 09:44:50 2005] query.cgi: Use of uninitialized value in string eq at
Bugzilla/Search.pm line 1281.
[Wed Mar 30 09:44:50 2005] query.cgi: Use of uninitialized value in string eq at
Bugzilla/Search.pm line 1281.
[Wed Mar 30 09:46:04 2005] query.cgi: Use of uninitialized value in string eq at
Bugzilla/Search.pm line 1281.
[Wed Mar 30 09:46:04 2005] query.cgi: Use of uninitialized value in string eq at
Bugzilla/Search.pm line 1281.

from these requests:

xx.173.70.58 - - [30/Mar/2005:09:43:59 +0100] "GET /bugs/query.cgi HTTP/1.1" 200
5439 "http://my.server/bugs/" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
rv:1.7.6) Gecko/20050321 Firefox/1.0.2"
xx.173.70.58 - - [30/Mar/2005:09:44:05 +0100] "GET
/bugs/query.cgi?format=advanced HTTP/1.1" 200 32822
"http://my.server/bugs/query.cgi" "Mozilla/5.0 (Windows; U; Windows NT 5.1;
en-GB; rv:1.7.6) Gecko/20050321 Firefox/1.0.2"

IE's cookie for COLUMNLIST looks like this:

COLUMNLIST
bug_severity%20priority%20rep_platform%20assigned_to%20bug_status%20resolution%20votes%20short_short_desc
my.server/bugs/
1536
3138338816
32108254
1905210448
29701387
*

Comment 1

[Joel Peshkin]

this works4me both on the tip and on 2.18

Are you saying that your COLUMNLIST cookie contains all the stuff you show in
comment 0 ??  Does firefox's cookie use that as well?

Please specify the exact version you are running and identify any patches or
modifications you have made.

Comment 2

[Simon Steele]

(In reply to comment #1)
> this works4me both on the tip and on 2.18

Yes, in-site and on b.m.o it works fine for me as well, it's only on the VPN
link that we are having problems.

> Are you saying that your COLUMNLIST cookie contains all the stuff you show in
> comment 0 ??  Does firefox's cookie use that as well?

That's the IE file format for cookies. Here are the details from firefox's
cookie as displayed when the COLUMNLIST cookie is selected:

Name: COLUMNLIST
Content:
bug_severity%20priority%20rep_platform%20assigned_to%20bug_status%20resolution%20votes%20short_short_desc
Host: my.server
Path: /bugs/
Send For: Any type of connection
Expires: 31 December 2037 23:57:39

> Please specify the exact version you are running and identify any patches or
> modifications you have made.

We are running version 2.18 with no patches. The only thing that could be even
slightly unusual is that we have changed the name "Bugzilla" to "Interactive"
using the templates.

Thanks.

Comment 3

[Frédéric Buclin]

This bug seems to appear only under some special circumstances, per reporter's
description; and joel cannot reproduce. Decreasing the severity to 'normal'.

Comment 4

[Frédéric Buclin]

Simon, can you still reproduce this bug on a more recent version of Bugzilla? Using VPN of course.

Comment 5

[Simon Steele]

Unfortunately I no longer have access to that bugzilla instance over the VPN so I can't tell you if this is still a problem or not!

Comment 6

[Frédéric Buclin]

There have been numerous changes since 2.18 and the reporter couldn't give us more feedback for the reason given in comment 5. Marking as WFM.