FS#49863 - [mythtv] backend now crashing after recent pacman -Suy
Attached to Project:
Community Packages
Opened by loris caren (loris) - Monday, 27 June 2016, 07:14 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 23 July 2016, 12:40 GMT
Opened by loris caren (loris) - Monday, 27 June 2016, 07:14 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 23 July 2016, 12:40 GMT
|
Details
Description:
mythtv 1:0.28-3 was running perfectly on my i64 arch system until a couple of days ago when I did a pacman -Suy. The mythbackend now core dumps as soon as the frontend or the mythweb tries to do anything. Additional info: I've run it using gdb and get the following:- Thread 21 "PT1" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff137fe700 (LWP 7653)] 0x00007fffeab038c0 in QMetaObject::indexOfClassInfo(char const*) const () from /usr/lib/libQt5Core.so.5 I note that one of the (many) packages that got updated was qt5-base (now 5.6.1-2) but reverting (just) qt5-base to 5.6.0.4 simply resulted in a new core dump that also seemed to be within qt5 but at a different point. Steps to reproduce: 1. pacman -Suy 2. start mythbackend and then connect to it via mythfrontend or new mythweb. |
This task depends upon
Closed by Antonio Rojas (arojas)
Saturday, 23 July 2016, 12:40 GMT
Reason for closing: Fixed
Additional comments about closing: mythtv 0.28-4
Saturday, 23 July 2016, 12:40 GMT
Reason for closing: Fixed
Additional comments about closing: mythtv 0.28-4
Thread 23 "PT4" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff197fa700 (LWP 26995)]
0x00007fffea711840 in QMetaObject::indexOfClassInfo(char const*) const ()
from /usr/lib/libQt5Core.so.5
(gdb)
I'm still crashing the backend by trying to use the WebFrontend interface (port 6544). Yesterdays gdb trace
produced by this method.
https://bbs.archlinux.org/viewtopic.php?pid=1631996#p1631996