mythfrontend.real crashed with SIGSEGV in mpegts_push_section() - remote frontend

Bug #1041788 reported by Douglas Mackay
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MythTV
Fix Released
Unknown
Mythbuntu
Expired
Undecided
Unassigned

Bug Description

Frontend crashes when starting playback. This is from a remote frontend

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-frontend 2:0.26.0~master.20120823.6566c3c-0ubuntu0mythbuntu2 [modified: usr/share/mythtv/mythfrontend.sh] [origin: LP-PPA-mythbuntu-0.26]
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
CrashDB: mythbuntu
Date: Sun Aug 26 09:15:40 2012
ExecutablePath: /usr/bin/mythfrontend.real
InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Installed_mythtv_dbg: 2:0.26.0~master.20120823.6566c3c-0ubuntu0mythbuntu2
MythTVDirectoryPermissions:
 total 0
 drwxr-xr-x 1 root root 0 Aug 26 05:14 recordings
 drwxr-xr-x 1 root root 0 Aug 25 22:56 videos
ProcCmdline: /usr/bin/mythfrontend.real --syslog local7
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6335c81a57 <mpegts_push_section+103>: movzbl 0x1(%rdi),%eax
 PC (0x7f6335c81a57) ok
 source "0x1(%rdi)" (0x7f633545b000) in non-readable VMA region: 0x7f633545b000-0x7f633565b000 ---p /usr/lib/libmythavcodec.so.54.23.100
 destination "%eax" ok
SegvReason: reading VMA /usr/lib/libmythavcodec.so.54.23.100
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 mpegts_push_section (filter=<optimized out>, section=0x475a1e0 "<\264\201", section_len=1156) at libavformat/mpegts-mythtv.c:689
 write_section_data (s=0x471b320, tss1=0x475a160, buf=<optimized out>, buf_size=<optimized out>, is_start=<optimized out>) at libavformat/mpegts-mythtv.c:401
 handle_packet (ts=0x4727700, packet=0x7fff40c8d790 "G\\!\021\250;\212O1\005Z\341\252fG\251I\270\332F\375m\310U!9Q(\006\325\314UA\205\203\215ᴮr\025A\256\"O\271\212\354\310U[ع\335xFy\203\236o\245\307\326\357'=oNz\376\234>\244\024_\374\020T\352c}3\200\005e\351\021\300\202'\240\232\001,(\005\245\241\354\177\222\354\b`[\350\205\351O\327\305\023\274h\301\223\260\304IUtے\352\352\374VZ{a\305\067\247\275") at libavformat/mpegts-mythtv.c:2527
 handle_packets (ts=0x4727700, nb_packets=0) at libavformat/mpegts-mythtv.c:2643
 mpegts_read_packet (s=<optimized out>, pkt=0x7fff40c8d960) at libavformat/mpegts-mythtv.c:2951
Title: mythfrontend.real crashed with SIGSEGV in mpegts_push_section()
UpgradeStatus: Upgraded to precise on 2012-04-15 (132 days ago)
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video
XsessionErrors:
 (xfwm4:1514): xfwm4-WARNING **: The display does not support the XComposite extension.
 (xfwm4:1514): xfwm4-WARNING **: Compositing manager disabled.
 (polkit-gnome-authentication-agent-1:1543): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed
 (polkit-gnome-authentication-agent-1:1543): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
modified.conffile..etc.mythtv.session.settings: [modified]
mtime.conffile..etc.mythtv.session.settings: 2012-08-25T18:52:19.505465

Revision history for this message
Douglas Mackay (o-launchpad-mackayd-co-uk) wrote :
description: updated
summary: - mythfrontend.real crashed with SIGSEGV in mpegts_push_section()
+ mythfrontend.real crashed with SIGSEGV in mpegts_push_section() - remote
+ frontend
visibility: private → public
Changed in mythtv:
status: Unknown → New
Changed in mythtv:
status: New → Confirmed
Changed in mythtv:
status: Confirmed → Fix Released
Revision history for this message
Thomas Mashos (tgm4883) wrote :

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream has moved on to a new version and believes this to be fixed. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.

Changed in mythbuntu:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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