Comment 13 for bug 1101395

Are you running packages that are after September 7th? (currently,
those only exist in the Mythbuntu repo). You'll see from this commit
that it's literally impossible for mythlogserver to crash anymore

https://github.com/MythTV/packaging/commit/b2571edc639c8d99262dfd4ea222ec920d8a2451
Thanks,

Thomas Mashos

On Sun, Sep 15, 2013 at 3:46 PM, Peter D. <email address hidden> wrote:
> Bug still exists 16th September.
>
> --
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to MythTV.
> https://bugs.launchpad.net/bugs/1101395
>
> Title:
> mythlogserver crashed with SIGSEGV in QObject::disconnect()
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
> Triaged
> Status in MythTV:
> Unknown
> Status in “mythtv” package in Ubuntu:
> Fix Released
>
> Bug description:
> crashed on remote frontend
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: mythtv-common 2:0.26.0+fixes.20130118.8f8274a-0ubuntu0mythbuntu2 [origin: LP-PPA-mythbuntu-0.26]
> ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
> Uname: Linux 3.2.0-35-generic x86_64
> NonfreeKernelModules: nvidia
> .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.0.1-0ubuntu17.1
> Architecture: amd64
> CrashDB: mythbuntu
> Date: Fri Jan 18 15:13:07 2013
> Disassembly: => 0x0: Cannot access memory at address 0x0
> DistributionChannelDescriptor:
> # This is a distribution channel descriptor
> # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
> canonical-oem-somerville-precise-amd64-20120703-2
> ExecutablePath: /usr/bin/mythlogserver
> InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08
> Installed_mythtv_dbg: 2:0.26.0+fixes.20130118.8f8274a-0ubuntu0mythbuntu2
> MarkForUpload: True
> MythTVDirectoryPermissions:
> total 4
> drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos
> ProcCmdline: /usr/bin/mythlogserver --daemon --verbose general --loglevel info --syslog local7
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x0: Cannot access memory at address 0x0
> PC (0x00000000) 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
> disconnect (member=0x0, receiver=0x7ff2d800b560, this=0x7ff2e000b4c0) at /usr/include/qt4/QtCore/qobject.h:252
> unregisterSocket (socket_=0x7ff2e000b4c0, this=0x7ff2d800b560) at ../include/nzmqt/nzmqt.hpp:703
> nzmqt::PollingZMQContext::qt_static_metacall (_o=0x7ff2d800b560, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at moc_nzmqt.cpp:401
> Title: mythlogserver crashed with SIGSEGV in QObject::disconnect()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mythbuntu/+bug/1101395/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mythbuntu-bugs
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~mythbuntu-bugs
> More help : https://help.launchpad.net/ListHelp