mythlogserver crashed with SIGSEGV in QObject::disconnect()

[gilson585]

not sure what happened, this occurred following a reboot after updates

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-common 2:0.26.0~master.20120726.83e227a-0ubuntu0mythbuntu2 [origin: LP-PPA-mythbuntu-0.26]
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
NonfreeKernelModules: wl
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythlcdserver.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythmessage.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythtranscode.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
CrashDB: mythbuntu
Date: Thu Jul 26 21:47:20 2012
ExecutablePath: /usr/bin/mythlogserver
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Installed_mythtv_dbg: 0.0
ProcCmdline: /usr/bin/mythlogserver --daemon --verbose general --loglevel info --syslog local7
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f92d459abda: mov 0x48(%rax),%rax
 PC (0x7f92d459abda) ok
 source "0x48(%rax)" (0x00000048) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/libmythnzmqt.so.0
 QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
Title: mythlogserver crashed with SIGSEGV in QObject::disconnect()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: audio cdrom dialout video

[Scott Johnson (scopeuk)]

I experienced this issue, it was resolved by updating my config.xml file with additional details for my database, hostname/username etc.
for whatever reason these were blank after the update on my system

[gilson585 (gilson585)]

I concur with Scott, the issue is resolved by using a correctly filled out config.xml

[Todd Bradshaw (snooptodd)]

The database fields were correct in my config.xml and I got this crash.

[Bob Havlin (bob-havlin)]

My config.xml is correct and I get this crash too.

[Grizzly (sven-witterstein)]

Still in 12.10

[Tony Stanley (tony-j-stanley)]

This error only occurs on my remote frontend. The local frontend is fine.

The files below are configured for local host:
/usr/share/doc/mythtv-backend/contrib/config_files/config.xml
/usr/share/mythtv/config.xml

while the following files reference the backend server
/etc/mythtv/config.xml
/home/mythtv/.mythtv/config.xml
/home/<myusername>/.mythtv/config.xml

I assume this is correct because I have not tried to make any adjustments.

[Jacob (jeisinge)]

I think this type of crash occurs for me when I shutdown mythtv's backend: https://bugs.launchpad.net/mythbuntu/+bug/1082425

[paul summers (paulsum)]

i shut down the mythbackend, by running the mythbackend setup, clicking "exit" on the "backend still running box" and then not entering the password/clicking exit.

[paul summers (paulsum)]

this crash happened because i ran mythbackend setup, then exited via esc key. setup hung, so I alt-tab'ed to the terminal window and cntrl-c'ed to closed it.
the crash happen when i was copying files to equalize the free space over 3 drives... (had a problem with permissions on one drive and it was not being used)

[Mario Limonciello (superm1)]

I got it to happen on a remote frontend as well.

[keepitsimpleengr (keepitsimpleengineer)]

This is happening regularly for me on both local and remote front-ends. Happened today on remote.

[Launchpad Janitor (janitor)]

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