Bug 54629
| Summary: | I have hadq to login 7 (SEVEN) times to load a uery, modify it, save it, and run it | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | j. alan eldridge <alane> |
| Component: | Bugzilla General | Assignee: | David Lawrence <dkl> |
| Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.8 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-09-07 16:59:39 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
j. alan eldridge
2001-10-14 09:21:28 UTC
Does this continue to happen if you delete any old bugzilla.redhat.com cookies and start over from scratch? Click on Settings->Configure Konqueror->Cookies->Management->Delete cookies with bugzilla.redhat.com domain->Apply. FWIW, I made this report change using Konqueror 2.2.1 with no problems. I've done that drill N times. It seems to be a short help. If I have to manually go and whack bugzilla cookies before I use it each time, that's not much of a fix, really. It seems to be, among other things, the query page that fscks things up. Passing through there seems to leave a stain on the session. Another thing that happens is, update a bug you just entered, to add an attachment, and whoops! hit the attach button, gotta login, and then, oh, your attachment failed, do it over again. There's just something fundamentally wrong with the way the session management is done in bugzilla. I have neither the experience with web apps nor the time needed to learn that to audit the thing myself. But that's what I'd suggest at this point: a complete code audit for session management errors. The fact that these things always come down to 'did you whack the cookies first?' indicates that it must not be getting handled correctly. I'm using Konquerer 2.2.1 from CVS 20011011 and ALWAYS have problems. ALWAYS. Have since sometime in the Konquere 2.2alpha1 stages. Consistently. This problem has been consistently happening in all versions of Konq since July. And I've done clean KDE installs, removing my .kde dir, too. My RPMs are built with Bero's spec files modulo removing patches that are in the tree now. It's not Konq. It happens, though not a badly it seems, with Mozilla, from 0.9.1 on through 0.9.5. I won't accept that every KDE installation I've done in the last 4 months is bolloxed up, and I won't accept that both my KDE and Mozilla installations are bolloxed up. I've been experiencing this problem on and off for ages. Just now I had a look at the cookies and noticed that there were two copies of several of them. I removed them all and for the moment it's behaving itself. Interestingly one set used <login>@cl.cam.ac.uk and the other <login>%40cl.cam.ac.uk. Could that be a source of trouble? (aside: it's bollocks or bollixed, rather than bollox according to the OED) Fixed? Dupe of bug 151237? I haven't encountered this problem for some time, so probably yes. |