Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#17069 - [seamonkey] forgets passwords
Attached to Project:
Arch Linux
Opened by Aleksey Kazantsev (ioctl) - Sunday, 08 November 2009, 21:05 GMT
Last edited by Paul Mattal (paul) - Sunday, 06 December 2009, 18:27 GMT
Opened by Aleksey Kazantsev (ioctl) - Sunday, 08 November 2009, 21:05 GMT
Last edited by Paul Mattal (paul) - Sunday, 06 December 2009, 18:27 GMT
|
DetailsDescription:
Seamonkey mail client likes to forget mail server password. Seamonkey web browser sometimes do the same with the proxy-server password. Additional info: * package version(s) 2.0-2 Steps to reproduce: Run seamonkey and mail client with a configured mail account, wait for a few hours. At first, seamonkey will show a box "Mail Server Password Required" with asterisk instead of password. So, you can press "Ok" button, but this box will appear again for 2-3 times, and then it will appear without password at all. So, you need to enter password by yourself. It is very irksomely, especially when password is long, and seamonkey forgets it every day. I suppose, that this problem can be caused by specific server response. But any way, mail client does not show any boxes like "wrong password", or "server is busy", it simply forgets my correct password. It is the same situation with the http proxy-server password. |
This task depends upon
Closed by Paul Mattal (paul)
Sunday, 06 December 2009, 18:27 GMT
Reason for closing: Upstream
Additional comments about closing: No response for a month, an upstream issue. It's also not clear whether this is a design choice upstream, or a bug.
Sunday, 06 December 2009, 18:27 GMT
Reason for closing: Upstream
Additional comments about closing: No response for a month, an upstream issue. It's also not clear whether this is a design choice upstream, or a bug.
Comment by Gerardo Exequiel Pozzi (djgera) -
Sunday, 08 November 2009, 22:22 GMT
- Field changed: Status (Unconfirmed → Waiting on Response)
Looks like an upstream issue rather than a packaging issue. Please report to upstream if not already reported. Thanks
Comment by Laszlo Papp (djszapi) -
Sunday, 06 December 2009, 18:25 GMT
No response from the reporter, is it worth to close, mainly if it's upstream ?