Ubuntu
mythtv package

mythfrontend.real crashed with SIGSEGV in reloadTheme()

Bug #939191 reported by Kim Tyler on 2012-02-23

This bug report is a duplicate of: Bug #962981: mythfrontend.real crashed with SIGSEGV in QMutex::lock(). Edit Remove

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	mythtv (Ubuntu)	New	Medium	Unassigned

Bug Description

can't configure mythtv backend because of this fault

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-frontend 2:0.25.0~master.20120216.769dfae-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Thu Feb 23 10:39:32 2012
ExecutablePath: /usr/bin/mythfrontend.real
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
Installed_mythtv_dbg: 0.0
ProcCmdline: /usr/bin/mythfrontend.real --syslog local7
ProcEnviron:
LANGUAGE=en_AU:en
TERM=xterm
PATH=(custom, no user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x439520: mov (%rdi),%rax
PC (0x00439520) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
?? ()
?? ()
__libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
?? ()
?? ()
Title: mythfrontend.real crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to precise on 2012-02-16 (6 days ago)
UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo

Tags:

Revision history for this message

Kim Tyler (ktyler) wrote on 2012-02-23:

#1

.var.log.mythtv.mythbackend.log.txt Edit (28.2 KiB, text/plain; charset="utf-8")
.var.log.mythtv.mythfrontend.log.txt Edit (13.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (9.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (691 bytes, text/plain; charset="utf-8")
MythTVDirectoryPermissions.txt Edit (549 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (85.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (825 bytes, text/plain; charset="utf-8")
Registers.txt Edit (765 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-23:

#2

StacktraceTop:
reloadTheme () at main.cpp:1250
main (argc=3, argv=<optimized out>) at main.cpp:1635

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-23: Stacktrace.txt

#3

Stacktrace.txt Edit (4.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-23: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (23.4 KiB, text/plain)

Changed in mythtv (Ubuntu):
importance:	Undecided → Medium
summary:	- mythfrontend.real crashed with SIGSEGV in __libc_start_main() + mythfrontend.real crashed with SIGSEGV in reloadTheme()
tags:	removed: need-amd64-retrace

Revision history for this message

MarcRandolph (mrand) wrote on 2012-04-07:

#5

Kim Tyler, can you describe what you might have been doing when this crash was generated? Was it when the frontend first fired up? Were you moving around the menus? Opening a screen (recordings? videos? schedules?)? Or maybe starting up a video or recording for playback? The log doesn't seem to indicate anything. I see you mention setup - were you going through the setup screens?

Thank you!

visibility:

private → public

Revision history for this message

Kim Tyler (ktyler) wrote on 2012-04-07:

#6

This is not occuring anymore. I was trying to configure mythtv backend, and it kept on crashing. By hand configuration of text files, it was enogh to get most of it going and bypass the above problem.

This problem is not occurring anymore - fixed? Please close if appropriate

Revision history for this message

MarcRandolph (mrand) wrote on 2012-04-08:

#7

I suspect it a duplicate of bug #962981, and since you can't reproduce it currently, we'll just go with that assumption. Thanks for the reply!

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #962981 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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