mythbuntu-bugs team mailing list archive

Thread
Date
Re: [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()

To: mythbuntu-bugs@xxxxxxxxxxxxxxxxxxx
From: doylecentral <1101395@xxxxxxxxxxxxxxxxxx>
Date: Mon, 16 Sep 2013 01:25:34 -0000
Reply-to: Bug 1101395 <1101395@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
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
<1101395@xxxxxxxxxxxxxxxxxx>wrote:

> 0.26 or 0.27?
> Thanks,
>
> Thomas Mashos
>
>
> On Sun, Sep 15, 2013 at 5:32 PM, doylecentral
> <1101395@xxxxxxxxxxxxxxxxxx> wrote:
> > I upgraded on 9/13/13 from whatever repo came with mythbuntu.
> >
> >
> > On Sun, Sep 15, 2013 at 7:02 PM, Thomas Mashos
> > <1101395@xxxxxxxxxxxxxxxxxx>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. <1101395@xxxxxxxxxxxxxxxxxx>
> >> 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     : mythbuntu-bugs@xxxxxxxxxxxxxxxxxxx
> >> > 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 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     : mythbuntu-bugs@xxxxxxxxxxxxxxxxxxx
> > 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 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
References

[Bug 1101395] [NEW] mythlogserver crashed with SIGSEGV in QObject::disconnect()
From: Mario Limonciello, 2013-01-18
[Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
From: Peter D., 2013-09-15
Re: [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
From: Thomas Mashos, 2013-09-15
Re: [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
From: doylecentral, 2013-09-16
Re: [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
From: Thomas Mashos, 2013-09-16