|
Bugzilla – Full Text Bug Listing |
| Summary: | roundcubemail-1.6.5 always dies with PHP errors | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | James Carter <jimc> |
| Component: | Other | Assignee: | Aeneas Jaißle <aj> |
| Status: | NEW --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Apache error_log showing complaints when opening roundcubemail-1.6.5 | ||
Today I did dist-upgrade (I do it weekly) and zypper correctly upgraded again to roundcubemail-1.6.5-1.1.noarch. But now it runs with no errors. The browser is the same MozillaFirefox-119.0-1.1.x86_64 that was installed last week. Very mysterious; I didn't do anything on the web/mail server. While there are errors in /var/log/apache2/error_log involving Nextcloud, reported in the midst of the dist-upgrade, there is nothing about Roundcube; the last such errors are the ones that I attached here last week. I think we could close this bug; if anything turns up that seems related, I'll reopen it. |
Created attachment 870688 [details] Apache error_log showing complaints when opening roundcubemail-1.6.5 I upgraded to roundcubemail-1.6.5-1.1.noarch , hosted on apache2-prefork-2.4.58-1.1.x86_64 . Formerly it was running with no problems, but now MozillaFirefox-119.0-1.1.x86_64 complains "Something Went Wrong" on initial connection, with no further information. I reverted to roundcubemail-1.6.4-1.1.noarch and normal operation was restored. I've attached /var/log/apache2/error_log showing complaints from 1.6.5 about nonexistent array keys (looks like it's trying to fix the charset of the names of standard folders such as "trash_mbox"), followed by no reportable errors after I reverted to 1.6.4. I'm not sure what you guys could do beyond a quick reversion, but a fix would be appreciated.