Mythtv Crashes after upgrade to 24.04

[johnlatz]

Linux mythbox 6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC x86_64 x86_64 x86_64 GNU/Linux v34.0+fixes.20240210.e3e165a1-0ubuntu6 Ubuntu package mythfrontend

mythfrontend will not start. If started as /usr/bin/mythfrontend --service, will continually crash

I wish I could tell you more. I have a dump from "mythfrontend -v all > mythdumpfile.txt

I have a crash file from /var/crash/_usr_bin_mythfrontend.real.1000.crash

I have removed (via "apt") and reinstalled (via "apt") the mythfrontend executable

mythbackend seems to run fine....

Would anyone be able to inspect my dump // crash logs and help me?

[johnlatz]

Some additional information - I spent this morning fighting to load Nvidia proprietary drivers. What I've discovered.

1) If the computer defaults ot the open source driver, the maximum resolution I seem to be able to output to my 4k screen is 1280x720. MythFrontend will run 2) Neither nvidia-470 nor nvidia-535 will drive my panel 3) Nvidia-535-open will drive my panel, but MythFrontend will not run 4) Nvidia-550 will drive my panel, but MythFrontend will not run

I moved ~/.mythtv to ~/.mythtv_old and attempted to restart MythFrontend. What follows is the result of grep "mythfrontend.real\[" _usr_bin_mythfrontend.real.1000.crash

Aug 31 12:18:50 localhost mythfrontend.real[40398]: mythfrontend[40398]: E CoreContext soapclient.cpp:265 (SendSOAPRequest) SOAPClient::SendSOAPRequest: request failed: http://192.168.0.16:6550/Myth Aug 31 12:18:50 localhost mythfrontend.real[40398]: mythfrontend[40398]: E CoreContext mythxmlclient.cpp:103 (GetConnectionInfo) MythXMLClient::GetConnectionInfo Failed - (32002) unexpected end of file Aug 31 12:18:50 localhost mythfrontend.real[40398]: mythfrontend[40398]: E CoreContext backendselect.cpp:225 (ConnectBackend) Access denied for mythbox: MythTV AV Media Server. Wrong PIN? Aug 31 12:18:59 localhost mythfrontend.real[40398]: mythfrontend[40398]: W CoreContext mythuithemehelper.cpp:65 (FindThemeDir) ThemeHelper: No theme dir: '/usr/share/mythtv/themes/Steppes-large' Aug 31 12:18:59 localhost mythfrontend.real[40398]: mythfrontend[40398]: E CoreContext mythuithemehelper.cpp:75 (FindThemeDir) ThemeHelper: Could not find theme: Steppes-large - Switching to Mythbuntu Aug 31 12:18:59 localhost mythfrontend.real[40398]: mythfrontend[40398]: W CoreContext mythpainter.cpp:36 (Teardown) MythPainter: 107 images not yet de-allocated. Aug 31 12:18:59 localhost mythfrontend.real[40398]: mythfrontend[40398]: W CoreContext mythuithemehelper.cpp:65 (FindThemeDir) ThemeHelper: No theme dir: '/usr/share/mythtv/themes/Steppes-large' Aug 31 12:18:59 localhost mythfrontend.real[40398]: mythfrontend[40398]: E CoreContext mythuithemehelper.cpp:75 (FindThemeDir) ThemeHelper: Could not find theme: Steppes-large - Switching to Mythbuntu Aug 31 12:18:59 localhost mythfrontend.real[40398]: mythfrontend[40398]: E CoreContext lirc.cpp:207 (Init) LIRC: Failed to connect to Unix socket '/dev/lircd' Aug 31 12:18:59 localhost mythfrontend.real[40398]: mythfrontend[40398]: E CoreContext mythudplistener.cpp:181 (EnableUDPListener) UDPListener: EnableUDPListener called after MythUDPListener instance is deleted Aug 31 12:18:59 localhost mythfrontend.real[40398]: mythfrontend[40398]: E CoreContext mythcecadapter.cpp:200 (Open) CECAdapter: Failed to find any CEC devices.

[bennettpeter]

I cannot understand why it is using port 6550 . Have you switched ports in your setup? Port 6550 was never used pre V34 but it now hosts the old deprecated API. I do not know why the frontend would be using it. The Myth Port should be 6543 and the status port 6544 Can you connect to http://backend:6544 ? The new setup is there and you can check the port assignment

[johnlatz]

Frontends Frontend: localhost, IP-Port: 192.168.0.16:6547, Online: false

MySQL Server Port 3306

Database schema version is 1379 Test Database Connection Connection to database was successful

General Backend Settings Backend Port: 6543 Frontend Port: 6544

I can't find SOAP or port 6550 anywhere on those screens.

Oh - attempting to reach http://192.168.0.16:6550/Myth via a browser results in a "404 Not Found."

[johnlatz]

Pouring through the crash logs more:

2024-09-01T10:45:20.253391-07:00 localhost kernel: mythfrontend.re[358415]: segfault at d8 ip 000078a64d541364 sp 00007ffe5db8c058 error 4 in libX11.so.6.4.0[78a64d530000+90000] likely on CPU 1 (core 1, socket 0) 2024-09-01T10:45:31.226548-07:00 localhost kernel: mythfrontend.re[358573]: segfault at d8 ip 000071cdcdced364 sp 00007ffcc6c412a8 error 4 in libX11.so.6.4.0[71cdcdcdc000+90000] likely on CPU 5 (core 6, socket 0) 2024-09-01T10:47:42.926391-07:00 localhost kernel: mythfrontend.re[360844]: segfault at d8 ip 00007546d8f41364 sp 00007ffcbf3f90a8 error 4 in libX11.so.6.4.0[7546d8f30000+90000] likely on CPU 8 (core 2, socket 0) 2024-09-01T12:10:48.925668-07:00 localhost kernel: mythfrontend.re[5320]: segfault at d8 ip 00007c26994ed364 sp 00007ffde3fc8ca8 error 4 in libX11.so.6.4.0[7c26994dc000+90000] likely on CPU 7 (core 1, socket 0) 2024-09-01T12:57:33.697672-07:00 localhost kernel: mythfrontend.re[34594]: segfault at d8 ip 000074577d541364 sp 00007ffe3a70bb58 error 4 in libX11.so.6.4.0[74577d530000+90000] likely on CPU 10 (core 5, socket 0) 2024-09-01T12:59:14.889664-07:00 localhost kernel: mythfrontend.re[36812]: segfault at d8 ip 000074c978b41364 sp 00007fff4cfa37b8 error 4 in libX11.so.6.4.0[74c978b30000+90000] likely on CPU 10 (core 5, socket 0)

At which point, I'm flummoxed - is that an issue in the kernel, the library, or the code? I have attempted to reinstall the X11-6 package again, to no avail

[johnlatz]

mythfrontend_verbose.txt

Output from "/usr/bin/mythfrontend.real --syslog local7 -v all --loglevel debug"

What is "DescURL=http://192.168.0.10:8200/rootDesc.xml", and why is this pointing to an IP on which I have no devices?

[johnlatz]

mythtv_settings.sql.txt