Ubuntu
mythtv package

mythtv-setup.real crashed with SIGSEGV in QVariant::QVariant()

Bug #905886 reported by Fabián Rodríguez on 2011-12-18

20

This bug affects 4 people

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

Bug Description

When trying to setup MythTV, after starting theMythTV Backend configuration utility, it crashes after country selection (language choice is never displayed).

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-backend 2:0.24.0+fixes.20111207.40f3bae-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-5.11-generic 3.2.0-rc5
Uname: Linux 3.2.0-5-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Dec 18 02:10:37 2011
ExecutablePath: /usr/bin/mythtv-setup.real
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111217)
Installed_mythtv_dbg: 0.0
ProcCmdline: /usr/bin/mythtv-setup.real
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f48dd8fb0f6 <_ZN8QVariantC2ERKS_+22>: mov (%rsi),%rcx
PC (0x7f48dd8fb0f6) ok
source "(%rsi)" (0x00000038) not located in a known VMA region (needed readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
QVariant::QVariant(QVariant const&) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
MythUIButtonListItem::GetData() () from /usr/lib/libmythui-0.24.so.0
LanguageSelection::Save() () from /usr/lib/libmyth-0.24.so.0
LanguageSelection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libmyth-0.24.so.0
QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
Title: mythtv-setup.real crashed with SIGSEGV in QVariant::QVariant()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo

Tags:

Revision history for this message

Fabián Rodríguez (magicfab) wrote on 2011-12-18:

#1

.var.log.mythtv.mythbackend.log.txt Edit (11.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (7.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.0 KiB, text/plain; charset="utf-8")
MythTVDirectoryPermissions.txt Edit (494 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (78.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (821 bytes, text/plain; charset="utf-8")
Registers.txt Edit (792 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (4.9 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (10.7 KiB, text/plain; charset="utf-8")

Revision history for this message

MarcRandolph (mrand) wrote on 2012-01-03:

#2

Howdy, and thank you for helping to improve Mythbuntu by opening this ticket. Was this crash reproducible for you, or did you try again and get past that point? Unfortunately, through no fault of your own, it appears that the debugging information that was captured is invalid, so we will likely have to close this ticket.

Changed in mythtv (Ubuntu):
importance:	Undecided → High
status:	New → Incomplete

Revision history for this message

Mario Limonciello (superm1) wrote on 2012-01-04:

#3

specifically if it is reproducible it would be quite helpful to install mythtv-dbg before reproducing it and filing another apport bug.

Revision history for this message

B.B. Lauret (bblauret) wrote on 2012-01-06:

#4

Same here in up-to-date precise:
Program received signal SIGSEGV, Segmentation fault.
0x02020d9b in QVariant::QVariant(QVariant const&) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
quit

Also the same segfault with the mythbuntu 0.24 ppa.

Revision history for this message

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

#5

Marking as confirmed since there is a second report - but we really need a backtrace for this ticket to go anywhere.

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

Revision history for this message

B.B. Lauret (bblauret) wrote on 2012-01-09:

#6

mythtv_setup_backtrace.txt Edit (7.4 KiB, text/plain)

Is this backtrace any help? If not, please point me to the right way, as I do not have any prior experience creating backtraces.

I should add I have not found a way to use apport, as I am running this on a headless server using X-redirection over ssh. I do not have X on the server. Mythtv is installed using the mythtv-backend-master meta-package. Should I use `ubuntu-bug -c /var/crash/_usr_bin_mythtv-setup.real.1000.crash -u 905886` ?

Revision history for this message

pdf (pdffs) wrote on 2012-01-29:

#7

mythtv-setup.real_thread_apply_all_bt_full Edit (28.3 KiB, text/plain)

libmyth-0.24-0-2:0.24.2+fixes.20120127.10d5624-0ubuntu0mythbuntu2
mythtv-backend-2:0.24.2+fixes.20120127.10d5624-0ubuntu0mythbuntu2
mythtv-backend-master-2:0.24.2+fixes.20120127.10d5624-0ubuntu0mythbuntu2

Full backtrace with relevant symbols.

Revision history for this message

pdf (pdffs) wrote on 2012-01-29:

#8

Okay, this is a packaging problem - /usr/share/mythtv/i18n/mythfrontend* needs to be split out from mythfrontend, put into a separate package, and both mythtv-backend and mythtv-frontend then need to depend on it. In the short term, installing mythtv-frontend allows mythtv-setup to work.

Revision history for this message

pdf (pdffs) wrote on 2012-01-29:

#9

Sorry for the message flood, scratch my last - having the i18n files allows the language list to be populated, but segfault still evident. Cancel language selection is the current workaround.

Revision history for this message

B.B. Lauret (bblauret) wrote on 2012-02-03:

#10

I can confirm that choosing cancel is a working workaround (altough with the setup in English).

Revision history for this message

pdf (pdffs) wrote on 2012-02-03:

#11

mythtv-setup will still segfault pretty frequently (quickly scrolling lists for example seems to trigger it). Can provide additional backtraces if useful.

Revision history for this message

Fabián Rodríguez (magicfab) wrote on 2015-03-11:

#12

I no longer use or have access to the initial setup I had when I reported this, so I can't provide further feedback.. I am removing myself from this bug's notifications.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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