Ubuntu
mythtv package

Mythtv frontend stuck in restart loop (code 139) after update to Ubuntu 16.10

Bug #1633871 reported by Simon Lambourn on 2016-10-16

30

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	mythtv (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

After updating to Ubuntu 16.10, Mythtv frontend will not shut down - it appears to function normally but on exit (normal exit at my request), there is an onscreen notification "the frontend has crashed unexpectedly (exit code 139). Restarting, please wait ..." and the frontend restarts.

This was working without problems on 16.04. I read that this is due to timezone problems?? The backend is on the same PC as the frontend so should see the same timezone. I can't see any error messages in the log (frontend or backend) either.

Any advice or help welcomed...

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: mythtv 2:0.28.0+fixes.20160413.15cf421-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 16 15:48:45 2016
Installed_mythtv_dbg: 2:0.28.0+fixes.20160413.15cf421-0ubuntu2
PackageArchitecture: all
SourcePackage: mythtv
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (1 days ago)

Tags:

Revision history for this message

Simon Lambourn (simon-lambourn-o) wrote on 2016-10-16:

#1

Frontend log Edit (5.8 MiB, application/octet-stream)
.var.log.mythtv.hwclock-rebootTime.log.txt Edit (179.4 KiB, text/plain; charset="utf-8")
.var.log.mythtv.mythbackend.log.txt Edit (4.4 MiB, text/plain; charset="utf-8")
.var.log.mythtv.mythcommflag.log.txt Edit (677.1 KiB, text/plain; charset="utf-8")
.var.log.mythtv.mythfilldatabase.log.txt Edit (10.6 KiB, text/plain; charset="utf-8")
.var.log.mythtv.mythfrontend.log.txt Edit (5.8 MiB, text/plain; charset="utf-8")
.var.log.mythtv.mythmetadatalookup.log.txt Edit (760.5 KiB, text/plain; charset="utf-8")
.var.log.mythtv.mythpreviewgen.log.txt Edit (1.6 MiB, text/plain; charset="utf-8")
.var.log.mythtv.mythtv-setup.log.txt Edit (434.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (20.8 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (82.4 KiB, text/plain; charset="utf-8")
MythTVDirectoryPermissions.txt Edit (549 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (115 bytes, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-10-17:

#2

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mythtv (Ubuntu):
status:	New → Confirmed

Revision history for this message

chicobiker (chicobiker) wrote on 2016-10-17:

#3

I have exactly the same problem. Just upgraded to 16.10 and running latest .28 fixes. Like the OP, it worked perfect prior to upgrading to 16.10.

Revision history for this message

heynnema (heynnema) wrote on 2016-11-04:

#4

Same problem here. If you start mythfrontend in terminal, you'll probably see a stack smashing error.

Revision history for this message

ed mcguirk (emcguirk) wrote on 2017-01-17:

#5

Has this been fixed or is there any activity on this problem? I just upgraded to 16.10 today and after running into the usual mysql password problem, I gave up and purged mysql and mythtv, deleted all mythtv files and directories, rebooted, and reinstalled mythtv from scratch.

I have the same continuously restarting frontend with exit code 139.

As an aside, I have been running mythtv on ubuntu for over 5 years and an ubuntu upgrade rarely manages to complete without killing mythtv. It doesn't break every time but most times it does which usually burns a whole day since I can't remember if this fix will be the same as last version fix or the same as last year's fix. I'm not a linux pro so I have to relearn all those terminal commands I haven't touched in 6 months. Plus little things like mysql commands on the mythtv troubleshooting page that no longer work unless you add the -p parameter which current versions of mysql now require and mysql does not say -p is missing, it just fails leaving you wondering why.

Revision history for this message

Thomas Mashos (tgm4883) wrote on 2017-01-17:

#6

I would recommend everyone try the updated packages from

https://launchpad.net/~mythbuntu/+archive/ubuntu/0.28

Revision history for this message

Simon Lambourn (simon-lambourn-o) wrote on 2017-01-17:

#7

Thankyou Thomas. It appears to work for me (one test only). I'll report back if I have any problems.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.