Summary: | squirrelmail-1.4.3-r1 generates duplicated quoted in reply-compose area | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tuan Van (RETIRED) <langthang> |
Component: | Current packages | Assignee: | Jeremy Huddleston (RETIRED) <eradicator> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | inaba, net-mail+disabled, sloan |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | compose.php-1.319.2.34 vs compose.php-1.319.2.35 diff |
Description
Tuan Van (RETIRED)
![]() Created attachment 32467 [details]
compose.php-1.319.2.34 vs compose.php-1.319.2.35 diff
attached is the diff between compose.php-1.319.2.34 and compose.php-1.319.2.35.
After applied this patch, "reply" works as normal.
hi, please apply patch ASAP - current stable version of squirrelmail is almost unusable this way... greetz rootshell I change this to blocker because if someone using this package with a large user base will: 1. crash their server. 2. Get a ton of complain from users because the browser/system lockup. in portage. thanks. in the future, please don't mark something a blocker unless it is a major problem. thanks. hi jeremy, in my opinion, lang did the right thing... I DO have a large user base. my users _did_ complain within 10 minutes after updating... was really no fun... this really _was_ a blocker greetz rootshell this has a trivial workaround. select the second duplicate text and delete it... am i not seeing something here? The real blocker is the memory usage bug #52787... unless they are related... --Jeremy It is indeed the same bug. Quoted from squirrelmail.org: [quote] UPDATE: The SquirrelMail 1.4.3 Release contains a serious memory exhausting bug. Please be patient and wait until we released version 1.4.3a (To be expected soon) or download a fixed version of compose.php Rev 1.319.2.35 from CVS and replace the compose.php file in the src directory [/quote] *** Bug 52787 has been marked as a duplicate of this bug. *** Jeremy, Lang, FYI - this bug with squirrelmail certainly sounds serious enough to have been marked as 'critical'. 'Serious memory leak' is definitely mentioned in the description of 'critical' ;-) We try to reserve 'blocker' for bugs that are preventing Gentoo developers from doing things. Hope that helps, Stu |