Bug ID | 1126449 |
---|---|
Summary | php7: wrong time displayed |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Other |
Assignee | bnc-team-screening@forge.provo.novell.com |
Reporter | suse+build@de-korte.org |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
I run a Horde installation on a openSUSE Tumbleweed. Up to and including php-7.3.1 time was displayed properly in the calendar application (Kronolith) that comes with Horde. After the upgrade to php-7.3.2, existing events are shown with a 2 hour offset. After some experimentation I have come to the conclusion that this is caused by an openSUSE modification with the 'php7-systzdata-v17.patch'. With the patch applied the displayed time is wrong, without it the time is correct. Possibly related, with the patch applied I see frequent segfaults (several times per hour) in php-fpm like the following: [21-Feb-2019 23:02:04] WARNING: [pool www] child 33612 exited on signal 11 (SIGSEGV) after 4218.979829 seconds from start This is with timezone (in php.ini) set to 'Europe/Amsterdam' with a load of just a handful of users. Without the patch, no segfaults, which leads me to believe there might be a relation. There were no problems with php-7.3.1 (time was displayed correctly and no segfaults).