Description of problem: No EPG information in VDR frontend. Maybe caused by this error in the log: vdr[30484]: [30484] loading plugin: /usr/lib64/vdr/libvdr-epg2vdr.so.2.4.7 vdr[30484]: [30484] ERROR: /usr/lib64/vdr/libvdr-epg2vdr.so.2.4.7: undefined symbol: PyObject_Repr runvdr[30484]: vdr: /usr/lib64/vdr/libvdr-epg2vdr.so.2.4.7: undefined symbol: PyObject_Repr Version-Release number of selected component (if applicable): vdr-epg2vdr-1.2.5-1.fc35.x86_64 How reproducible: Always Steps to Reproduce: 1. Configure and start VDR, EPGD, MARIADB 2. journalctl will show the above error message 3. Actual results: Error message / no EPG data in VDR GUI Expected results: No Error message / EPG data in VDR GUI Additional info: Discussion (german) and possible solution here: https://www.vdr-portal.de/forum/index.php?thread/133185-vdr4arch-epg2vdr-scraper2vdr/
I have not used the plugin for a while and am now a bit confused about the error message. The plugin is up to date with the python3 version. I currently do not know how to solve this :-(
The issue is that the plugin is not linked against python: $ ldd /usr/lib64/vdr/libvdr-epg2vdr.so.2.4.7 linux-vdso.so.1 (0x00007fff69734000) /usr/lib64/gtk3-nocsd.so (0x00007feb8ce5a000) libm.so.6 => /lib64/libm.so.6 (0x00007feb8cd61000) libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007feb8ca73000) libuuid.so.1 => /lib64/libuuid.so.1 (0x00007feb8ca6a000) libtinyxml2.so.7 => /lib64/libtinyxml2.so.7 (0x00007feb8ca52000) libmariadb.so.3 => /lib64/libmariadb.so.3 (0x00007feb8c9fc000) libjansson.so.4 => /lib64/libjansson.so.4 (0x00007feb8c9ea000) libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007feb8c7cb000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007feb8c7b0000) libc.so.6 => /lib64/libc.so.6 (0x00007feb8c5a6000) /lib64/ld-linux-x86-64.so.2 (0x00007feb8cf01000) libz.so.1 => /lib64/libz.so.1 (0x00007feb8c58c000) libssl.so.1.1 => /lib64/libssl.so.1.1 (0x00007feb8c4ef000) The build process must ensure to specify the required python libs when linking the plugin.
FEDORA-2022-4a7bfc854f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4a7bfc854f
Great, it works! Thanks! 🐝🐝🐝
FEDORA-2022-4a7bfc854f has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-4a7bfc854f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4a7bfc854f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-be1a98d775 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-be1a98d775` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-be1a98d775 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-be1a98d775 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.