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
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1177385
Title:
mythlogserver crashed with SIGSEGV in QObject::disconnect()
Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
Expired
Bug description:
I exited mythfrontend on a remote machine after watching a few
television shows that I had recorded. A few minutes later, this error
popped up on my screen.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: mythtv-common 2:0.26.0+fixes.20130506.ac5525d-0ubuntu0mythbuntu3
[origin: LP-PPA-mythbuntu-0.26]
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
.var.log.mythtv.mythavtest.log:
.var.log.mythtv.mythbackend.log:
.var.log.mythtv.mythccextractor.log:
.var.log.mythtv.mythcommflag.log:
.var.log.mythtv.mythfilldatabase.log:
.var.log.mythtv.mythjobqueue.log:
.var.log.mythtv.mythlcdserver.log:
.var.log.mythtv.mythmediaserver.log:
.var.log.mythtv.mythmetadatalookup.log:
.var.log.mythtv.mythpreviewgen.log:
.var.log.mythtv.mythshutdown.log:
.var.log.mythtv.mythtranscode.log:
.var.log.mythtv.mythtv.setup.log:
.var.log.mythtv.mythutil.log:
.var.log.mythtv.mythwelcome.log:
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CrashDB: mythbuntu
Date: Tue May 7 08:21:55 2013
Disassembly: => 0x20: Cannot access memory at address 0x20
ExecutablePath: /usr/bin/mythlogserver
InstallationDate: Installed on 2013-01-20 (107 days ago)
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64
(20121017.1)
Installed_mythtv_dbg: 0.0
MarkForUpload: True
MythTVDirectoryPermissions:
total 8
drwxrwsr-x 2 mythtv mythtv 4096 Jan 22 16:42 bare-client
drwxr-xr-x 2 root root 4096 Mar 4 01:06 videos
ProcCmdline: /usr/bin/mythlogserver --daemon --verbose general --loglevel
info --syslog local7
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x20: Cannot access memory at address 0x20
PC (0x00000020) not located in a known VMA region (needed executable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
?? ()
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: Upgraded to raring on 2013-04-27 (9 days ago)
UserGroups: adm cdrom dip lp lpadmin mythtv plugdev sambashare sudo vboxusers
To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1177385/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~mythbuntu-bugs
Post to : mythbuntu-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mythbuntu-bugs
More help : https://help.launchpad.net/ListHelp
