Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
Hi, I've forgotten whether this is a top post list or a bottom post list. Sorry. Somebody posted that the fix is only in 0.27, I was running either mythtv-backend_2%3a0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1_amd64.deb or mythtv-backend_2%3a0.26.1+fixes.20130914.bd7198b-0ubuntu0mythbuntu1_amd64.deb when the error popped up. I'm surprised that that information was not captured automatically, there was a very large data transfer. bP On Sun, 15 Sep 2013 23:02:14 - Thomas Mashos <1101...@bugs.launchpad.net> wrote: > 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. > <1101...@bugs.launchpad.net> 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 (0x) 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=, _id=, _a=) 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 : mythbuntu-b...@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~mythbuntu-bugs > > More help : https://help.launchpad.net/ListHelp > -- testing bP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpa
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
This is only fixed in 0.27 Thanks, Thomas Mashos On Sep 15, 2013 6:35 PM, "doylecentral" <1101...@bugs.launchpad.net> wrote: > Sorry didn't see your mail. > > c@mythbackend:~$ dpkg -l | grep -i myth > rc libmyth-0.25-0 > 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 Common library code for > MythTV and add-on modules (runtime) > ii libmyth-0.26-0 > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Common library code for > MythTV and add-on modules (runtime) > ii libmyth-python > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 A python library to > access some MytTV features > ii libmythtv-perl > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 A PERL library to access > some MythTV features > ii mythbuntu-bare-client > 2.2Mythbuntu Bare Client > ii mythbuntu-common > 0.67 Mythbuntu application > support functions > ii mythbuntu-control-centre > 0.63-0ubuntu2 Mythbuntu Configuration > Application > ii mythbuntu-default-settings > 1.08 default settings for > Mythbuntu > ii mythbuntu-desktop > 0.77 The Mythbuntu standalone > system > ii mythbuntu-lightdm-theme > 1.01 Mythbuntu LightDM setup > ii mythbuntu-log-grabber > 0.10-0ubuntu1 Mythbuntu diagnostic > utility > ii mythgallery > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Image gallery/slideshow > add-on module for MythTV > ii mythmusic > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Music add-on module for > MythTV > ii mythtv > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder > application (client and server) > ii mythtv-backend > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder > application (server) > ii mythtv-backend-master > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Metapackage to setup and > configure a "Master Backend" profile of MythTV. > ii mythtv-common > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder > application (common data) > ii mythtv-database > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder > application (database) > ii mythtv-frontend > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder > application (client) > ii mythtv-theme-mythbuntu > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 The mythbuntu MythTV > Theme > ii mythtv-transcode-utils > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Utilities used for > transcoding MythTV tasks > ii mythweb > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Web interface add-on > module for MytTV > ii php-mythtv > 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 PHP Bindings for MythTV > > > On Sun, Sep 15, 2013 at 7:41 PM, Thomas Mashos > <1101...@bugs.launchpad.net>wrote: > > > No, dropping the repo would not fix the issue. Can you post what the > > output of this is > > > > "dpkg -l | grep -i myth" > > Thanks, > > > > Thomas Mashos > > > > > > On Sun, Sep 15, 2013 at 4:24 PM, kmitche <1101...@bugs.launchpad.net> > > wrote: > > > Thomas, > > > I am running the mythbuntu repo. Mythlogserver appears to be active as > a > > result. Dropping the repo would fix this issue, correct? Thanks for > > following up with this. > > > Kent > > > On Sep 15, 2013, at 4:02 PM, Thomas Mashos <1101...@bugs.launchpad.net > > > > wrote: > > > > > >> 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. <1101...@bugs.launchpad.net > > > > 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 > > >>> No
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
I'm running .26 see below. I thought .27 was not out yet? I'm also running on a hypervisor xcp with xen monitoring tools installed. I have my system snapshots so if you want me to try something just let me know. dc@mythbackend:~$ sudo apt-cache policy mythtv mythtv: Installed: 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Candidate: 2:0.26.1+fixes.20130914.bd7198b-0ubuntu0mythbuntu1 Version table: 2:0.26.1+fixes.20130914.bd7198b-0ubuntu0mythbuntu1 0 500 http://ppa.launchpad.net/mythbuntu/0.26/ubuntu/ precise/main amd64 Packages *** 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 0 100 /var/lib/dpkg/status 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/multiverse amd64 Packages 2:0.25.0+fixes.20120410.1f5962a-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/multiverse amd64 Packages dc@mythbackend:~$ On Sun, Sep 15, 2013 at 8:44 PM, Thomas Mashos <1101...@bugs.launchpad.net>wrote: > 0.26 or 0.27? > Thanks, > > Thomas Mashos > > > On Sun, Sep 15, 2013 at 5:32 PM, doylecentral > <1101...@bugs.launchpad.net> wrote: > > I upgraded on 9/13/13 from whatever repo came with mythbuntu. > > > > > > On Sun, Sep 15, 2013 at 7:02 PM, Thomas Mashos > > <1101...@bugs.launchpad.net>wrote: > > > >> 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. <1101...@bugs.launchpad.net> > >> 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 (0x) 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
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
Sorry didn't see your mail. c@mythbackend:~$ dpkg -l | grep -i myth rc libmyth-0.25-0 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 Common library code for MythTV and add-on modules (runtime) ii libmyth-0.26-0 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Common library code for MythTV and add-on modules (runtime) ii libmyth-python 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 A python library to access some MytTV features ii libmythtv-perl 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 A PERL library to access some MythTV features ii mythbuntu-bare-client 2.2Mythbuntu Bare Client ii mythbuntu-common 0.67 Mythbuntu application support functions ii mythbuntu-control-centre 0.63-0ubuntu2 Mythbuntu Configuration Application ii mythbuntu-default-settings 1.08 default settings for Mythbuntu ii mythbuntu-desktop 0.77 The Mythbuntu standalone system ii mythbuntu-lightdm-theme 1.01 Mythbuntu LightDM setup ii mythbuntu-log-grabber 0.10-0ubuntu1 Mythbuntu diagnostic utility ii mythgallery 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Image gallery/slideshow add-on module for MythTV ii mythmusic 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Music add-on module for MythTV ii mythtv 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder application (client and server) ii mythtv-backend 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder application (server) ii mythtv-backend-master 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Metapackage to setup and configure a "Master Backend" profile of MythTV. ii mythtv-common 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder application (common data) ii mythtv-database 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder application (database) ii mythtv-frontend 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder application (client) ii mythtv-theme-mythbuntu 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 The mythbuntu MythTV Theme ii mythtv-transcode-utils 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Utilities used for transcoding MythTV tasks ii mythweb 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Web interface add-on module for MytTV ii php-mythtv 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 PHP Bindings for MythTV On Sun, Sep 15, 2013 at 7:41 PM, Thomas Mashos <1101...@bugs.launchpad.net>wrote: > No, dropping the repo would not fix the issue. Can you post what the > output of this is > > "dpkg -l | grep -i myth" > Thanks, > > Thomas Mashos > > > On Sun, Sep 15, 2013 at 4:24 PM, kmitche <1101...@bugs.launchpad.net> > wrote: > > Thomas, > > I am running the mythbuntu repo. Mythlogserver appears to be active as a > result. Dropping the repo would fix this issue, correct? Thanks for > following up with this. > > Kent > > On Sep 15, 2013, at 4:02 PM, Thomas Mashos <1101...@bugs.launchpad.net> > wrote: > > > >> 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. <1101...@bugs.launchpad.net> > 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
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
0.26 or 0.27? Thanks, Thomas Mashos On Sun, Sep 15, 2013 at 5:32 PM, doylecentral <1101...@bugs.launchpad.net> wrote: > I upgraded on 9/13/13 from whatever repo came with mythbuntu. > > > On Sun, Sep 15, 2013 at 7:02 PM, Thomas Mashos > <1101...@bugs.launchpad.net>wrote: > >> 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. <1101...@bugs.launchpad.net> >> 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 (0x) 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=, _id=, _a=) 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 : mythbuntu-b...@lists.launchpad.net >> > Unsubscribe : https://launchpad.net/~mythbuntu-bugs >> > More help : https://help.launchpad.net/ListHelp >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1101395 >> >> Title: >> mythlogserver crashed with SIGSEGV in QObject::disconnect() >> >> To manage notifica
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
I upgraded on 9/13/13 from whatever repo came with mythbuntu. On Sun, Sep 15, 2013 at 7:02 PM, Thomas Mashos <1101...@bugs.launchpad.net>wrote: > 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. <1101...@bugs.launchpad.net> > 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 (0x) 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=, _id=, _a=) 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 : mythbuntu-b...@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~mythbuntu-bugs > > More help : https://help.launchpad.net/ListHelp > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1101395 > > Title: > mythlogserver crashed with SIGSEGV in QObject::disconnect() > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mythbuntu/+bug/1101395/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101395 Title: mythlogse
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
also make sure you are running a 0.27 based build not earlier. On Sep 15, 2013 6:41 PM, "Thomas Mashos" wrote: > No, dropping the repo would not fix the issue. Can you post what the > output of this is > > "dpkg -l | grep -i myth" > Thanks, > > Thomas Mashos > > > On Sun, Sep 15, 2013 at 4:24 PM, kmitche <1101...@bugs.launchpad.net> > wrote: > > Thomas, > > I am running the mythbuntu repo. Mythlogserver appears to be active as a > result. Dropping the repo would fix this issue, correct? Thanks for > following up with this. > > Kent > > On Sep 15, 2013, at 4:02 PM, Thomas Mashos <1101...@bugs.launchpad.net> > wrote: > > > >> 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. <1101...@bugs.launchpad.net> > 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 (0x) 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=, _id=, _a=) 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 > >>> Po
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
No, dropping the repo would not fix the issue. Can you post what the output of this is "dpkg -l | grep -i myth" Thanks, Thomas Mashos On Sun, Sep 15, 2013 at 4:24 PM, kmitche <1101...@bugs.launchpad.net> wrote: > Thomas, > I am running the mythbuntu repo. Mythlogserver appears to be active as a > result. Dropping the repo would fix this issue, correct? Thanks for > following up with this. > Kent > On Sep 15, 2013, at 4:02 PM, Thomas Mashos <1101...@bugs.launchpad.net> wrote: > >> 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. <1101...@bugs.launchpad.net> 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 (0x) 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=, _id=, _a=) 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 : mythbuntu-b...@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~mythbuntu-bugs >>> More help : https://help.launchpad.net/ListHelp >> >> -- >> You received this bug notification because you are subscribed to a >> duplicate bug report (1029723). >> https://bugs.launchpad.net/bugs/1101395 >> >> Title: >> mythlogserver
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
Let me know. What I'm getting at is that with current packages it should be impossible for mythlogserver to crash because we aren't installing mythlogserver because we've disabled mythlogserver from compiling. Thanks, Thomas Mashos On Sun, Sep 15, 2013 at 4:16 PM, nik [tm] <1101...@bugs.launchpad.net> wrote: > Hi Thomas, > > I'm pretty sure it completely up to date, but will check when home > tonight an confirm. > > Regards > Nick Sharp > > > On 16/09/2013, at 8:32, Thomas Mashos <1101...@bugs.launchpad.net> > wrote: > >> 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. <1101...@bugs.launchpad.net> 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 (0x) 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=, _id=, _a=) 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 : mythbuntu-b...@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~mythbuntu-bugs >>> More help : https://help.launchpad.net/ListHelp >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1101395 >> >> Titl
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
Thomas, I am running the mythbuntu repo. Mythlogserver appears to be active as a result. Dropping the repo would fix this issue, correct? Thanks for following up with this. Kent On Sep 15, 2013, at 4:02 PM, Thomas Mashos <1101...@bugs.launchpad.net> wrote: > 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. <1101...@bugs.launchpad.net> 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 (0x) 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=, _id=, _a=) 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 : mythbuntu-b...@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~mythbuntu-bugs >> More help : https://help.launchpad.net/ListHelp > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1029723). > 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: my
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
Hi Thomas, I'm pretty sure it completely up to date, but will check when home tonight an confirm. Regards Nick Sharp On 16/09/2013, at 8:32, Thomas Mashos <1101...@bugs.launchpad.net> wrote: > 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. <1101...@bugs.launchpad.net> 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 (0x) 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=, _id=, _a=) 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 : mythbuntu-b...@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~mythbuntu-bugs >> More help : https://help.launchpad.net/ListHelp > > -- > You received this bug notification because you are subscribed to the bug > report. > 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-m
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
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. <1101...@bugs.launchpad.net> 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 (0x) 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=, _id=, _a=) 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 : mythbuntu-b...@lists.launchpad.net > Unsubscribe : https://launchpad.net/~mythbuntu-bugs > More help : https://help.launchpad.net/ListHelp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101395 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1101395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
Are you sure that mythtv is the culprit? What does 'top' say? Thanks, Thomas Mashos On Mon, Feb 25, 2013 at 10:39 AM, Mark Preston wrote: > After running sudo service mythtv-backend stop, the OS cannot get back > control. My mouse is weak to dead at times. Typing into a form took 10 > minutes because of this. > > What part of mythtv can I stop besides backend? I tried to stop > mythlogserver, mythlcdserver and another myth, but the terminal said > "unrecognized service". > > -- > 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: > Triaged > > 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 (0x) 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=, _id=, _a=) 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 : mythbuntu-b...@lists.launchpad.net > Unsubscribe : https://launchpad.net/~mythbuntu-bugs > More help : https://help.launchpad.net/ListHelp > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101395 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1101395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
