mythlogserver crashed with SIGSEGV in QObject::disconnect()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MythTV |
Unknown
|
Unknown
|
|||
Mythbuntu |
Expired
|
Medium
|
Unassigned | ||
mythtv (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
crashed on remote frontend
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-common 2:0.26.
ProcVersionSign
Uname: Linux 3.2.0-35-generic x86_64
NonfreeKernelMo
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.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
DistributionCha
# This is a distribution channel descriptor
# For more information see http://
canonical-
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08
Installed_
MarkForUpload: True
MythTVDirectory
total 4
drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos
ProcCmdline: /usr/bin/
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 (member=0x0, receiver=
unregisterSocket (socket_
nzmqt:
Title: mythlogserver crashed with SIGSEGV in QObject:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Related branches
Mario Limonciello (superm1) wrote : | #1 |
- .var.log.mythtv.mythfrontend.log.txt Edit (217.1 KiB, text/plain; charset="utf-8")
- CoreDump.gz Edit (3.1 MiB, application/x-gzip)
- Dependencies.txt Edit (5.7 KiB, text/plain; charset="utf-8")
- ProcMaps.txt Edit (49.3 KiB, text/plain; charset="utf-8")
- ProcStatus.txt Edit (828 bytes, text/plain; charset="utf-8")
- Registers.txt Edit (843 bytes, text/plain; charset="utf-8")
- Stacktrace.txt Edit (3.5 KiB, text/plain; charset="utf-8")
- ThreadStacktrace.txt Edit (78.4 KiB, text/plain; charset="utf-8")
- XsessionErrors.txt Edit (13.2 KiB, text/plain; charset="utf-8")
information type: | Private → Public |
Changed in mythbuntu: | |
status: | New → Triaged |
Changed in mythtv (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in mythbuntu: | |
importance: | Undecided → Medium |
tags: | removed: need-amd64-retrace |
H Buus (mythtv-0) wrote : | #2 |
H Buus (mythtv-0) wrote : | #3 |
See http://
Mario Limonciello (superm1) wrote : Re: [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect() | #4 |
Thanks for the patch. Once upstream applies it it will land in our auto
builds.
On Feb 5, 2013 1:01 AM, "H Buus" <email address hidden> wrote:
> See http://
> segv.patch) that I believe will fix this problem.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> mythlogserver crashed with SIGSEGV in QObject:
>
> To manage notifications about this bug go to:
> https:/
>
Mark Preston (emarkpreston) wrote : | #5 |
Without MythTV's frontend running, the Launchpad Bug reporter came up on screen today. I had to twice enter my Linux Admin password, and then and only then would this bug be reported. While this bug has been triaged as being of medium importance, I suggest it is worse (higher importance). Ever since MythTV has become part of my auto-downloads through the Ubuntu Update Manager, my hard drive spins furiously and the CPU had insane load averages of 15 : 12 : 8. I have a quad core cpu. This conflict even causes the mouse cursor to disappear from the screen and no amount of mouse movement "finds" it. What is even more confusing is that I am taken to a Launchpad page to select from several bugs and I have NO WAY of knowing which to select. So, even though I'm in ignorance, I have selected this one. By the bye: the Launchpad bug report took several minutes to populate it's report and send it along here. As my upload speed is 76K, that's a lot of upload. In the megabytes.
Mark Preston (emarkpreston) wrote : | #6 |
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".
Thomas Mashos (tgm4883) wrote : Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect() | #7 |
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 <email address hidden> 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:/
>
> Title:
> mythlogserver crashed with SIGSEGV in QObject:
>
> 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.
> LP-PPA-
> ProcVersionSign
> Uname: Linux 3.2.0-35-generic x86_64
> NonfreeKernelMo
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.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
> DistributionCha
> # This is a distribution channel descriptor
> # For more information see
> http://
> canonical-
> ExecutablePath: /usr/bin/
> InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary
> 20120703-15:08
> Installed_
> MarkForUpload: True
> MythTVDirectory
> total 4
> drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos
> ProcCmdline: /usr/bin/
> --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:
Mark Preston (emarkpreston) wrote : | #8 |
Today, I turned the 'puter on. A few moments after the desktop finished loading, I noticed both tuner lights on my SiliconDust tuner are active. No reason for that no scheduled work for Myth. I sudo the backend to stop and noticed a significant drop in CPU usage. And the tuner LEDs are out.
Per Mr. Mashos request re: top & cpu from a few days ago. With no other software app running, other than the terminal, so that I might observe the TOP results, stopping the backend restored some sanity to the OS. Part of Apache2 was mis-configged and aptitude figured that out and re-installed it, so that's at an 'end' for now.
keepitsimpleengr (keepitsimpleengineer) wrote : | #9 |
This happens almost every start up.
Stefan Pappalardo (sjuk) wrote : | #10 |
- mythfrontend.log Edit (3.0 MiB, text/plain)
mythlogserver crashes on on frontend-
Launchpad Janitor (janitor) wrote : | #11 |
This bug was fixed in the package mythtv - 2:0.27.
---------------
mythtv (2:0.27.
* Add a patch to readjust the inclusion order to fix FTBFS on PPC.
- Submitted upstream at http://
-- Mario Limonciello <email address hidden> Tue, 10 Sep 2013 12:29:00 -0500
Changed in mythtv (Ubuntu): | |
status: | Triaged → Fix Released |
Peter D. (0123peter) wrote : | #12 |
Bug still exists 16th September.
Thomas Mashos (tgm4883) wrote : | #13 |
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:/
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:/
>
> Title:
> mythlogserver crashed with SIGSEGV in QObject:
>
> 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.
> ProcVersionSign
> Uname: Linux 3.2.0-35-generic x86_64
> NonfreeKernelMo
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.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
> DistributionCha
> # This is a distribution channel descriptor
> # For more information see http://
> canonical-
> ExecutablePath: /usr/bin/
> InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08
> Installed_
> MarkForUpload: True
> MythTVDirectory
> total 4
> drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos
> ProcCmdline: /usr/bin/
> 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:
> ...
nik [tm] (tmcruisin) wrote : | #14 |
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 <email address hidden> 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:/
> 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:/
>>
>> Title:
>> mythlogserver crashed with SIGSEGV in QObject:
>>
>> 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.
>> ProcVersionSign
>> Uname: Linux 3.2.0-35-generic x86_64
>> NonfreeKernelMo
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.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
>> DistributionCha
>> # This is a distribution channel descriptor
>> # For more information see http://
>> canonical-
>> ExecutablePath: /usr/bin/
>> InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08
>> Installed_
>> MarkForUpload: True
>> MythTVDirectory
>> total 4
>> drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos
>> ProcCmdline: /usr/bin/
>> 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 exhaust...
kmitche (kmitche) wrote : | #15 |
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 <email address hidden> 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:/
> 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:/
>>
>> Title:
>> mythlogserver crashed with SIGSEGV in QObject:
>>
>> 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.
>> ProcVersionSign
>> Uname: Linux 3.2.0-35-generic x86_64
>> NonfreeKernelMo
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.log.
>>
>> .var.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
>> DistributionCha
>> # This is a distribution channel descriptor
>> # For more information see http://
>> canonical-
>> ExecutablePath: /usr/bin/
>> InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08
>> Installed_
>> MarkForUpload: True
>> MythTVDirectory
>> total 4
>> drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos
>> ProcCmdline: /usr/bin/
>> 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...
Thomas Mashos (tgm4883) wrote : | #16 |
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] <email address hidden> 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 <email address hidden>
> 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:/
>> 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:/
>>>
>>> Title:
>>> mythlogserver crashed with SIGSEGV in QObject:
>>>
>>> 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.
>>> ProcVersionSign
>>> Uname: Linux 3.2.0-35-generic x86_64
>>> NonfreeKernelMo
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.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
>>> DistributionCha
>>> # This is a distribution channel descriptor
>>> # For more information see http://
>>> canonical-
>>> ExecutablePath: /usr/bin/
>>> InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08
>>> Installed_
>>> MarkForUpload: True
>>> MythTVDirectory
>>> total 4
>>> drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos
>>> ProcC...
Thomas Mashos (tgm4883) wrote : | #17 |
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 <email address hidden> 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 <email address hidden> 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:/
>> 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:/
>>>
>>> Title:
>>> mythlogserver crashed with SIGSEGV in QObject:
>>>
>>> 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.
>>> ProcVersionSign
>>> Uname: Linux 3.2.0-35-generic x86_64
>>> NonfreeKernelMo
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.log.
>>>
>>> .var.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
>>> DistributionCha
>>> # This is a distribution channel descriptor
>>> # For more information see http://
>>> canonical-
>>> ExecutablePath: /usr/bin/
>>> InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08
>>> Installed_
>>> MarkForUpload: True
>>> MythTVDirectory
>>> total 4
>>> drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos
>>> ProcCmdline: /usr/bin/
Mario Limonciello (superm1) wrote : | #18 |
also make sure you are running a 0.27 based build not earlier.
On Sep 15, 2013 6:41 PM, "Thomas Mashos" <email address hidden> 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 <email address hidden>
> 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 <email address hidden>
> 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:/
> >> 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:/
> >>>
> >>> Title:
> >>> mythlogserver crashed with SIGSEGV in QObject:
> >>>
> >>> 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.
> LP-PPA-
> >>> ProcVersionSign
> >>> Uname: Linux 3.2.0-35-generic x86_64
> >>> NonfreeKernelMo
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.log.
> >>>
> >>> .var.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
> >>> DistributionCha
> >>> # This is a distribution channel descriptor
> >>> # For more information see
> http://
> >>> canonical-
> >>> ExecutablePath: /usr/bin/
> >>> Installa...
doylecentral (doyle) wrote : | #19 |
I upgraded on 9/13/13 from whatever repo came with mythbuntu.
On Sun, Sep 15, 2013 at 7:02 PM, Thomas Mashos
<email address hidden>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:/
> 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:/
> >
> > Title:
> > mythlogserver crashed with SIGSEGV in QObject:
> >
> > 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.
> LP-PPA-
> > ProcVersionSign
> > Uname: Linux 3.2.0-35-generic x86_64
> > NonfreeKernelMo
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.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
> > DistributionCha
> > # This is a distribution channel descriptor
> > # For more information see
> http://
> > canonical-
> > ExecutablePath: /usr/bin/
> > InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary
> 20120703-15:08
> > Installed_
> 2:0.26.
> > MarkForUpload: True
> > MythTVDirectory
> > total 4
> > drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos
> > ProcCmdline: /usr/bin/
> --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...
Thomas Mashos (tgm4883) wrote : | #20 |
0.26 or 0.27?
Thanks,
Thomas Mashos
On Sun, Sep 15, 2013 at 5:32 PM, doylecentral
<email address hidden> wrote:
> I upgraded on 9/13/13 from whatever repo came with mythbuntu.
>
>
> On Sun, Sep 15, 2013 at 7:02 PM, Thomas Mashos
> <email address hidden>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:/
>> 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:/
>> >
>> > Title:
>> > mythlogserver crashed with SIGSEGV in QObject:
>> >
>> > 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.
>> LP-PPA-
>> > ProcVersionSign
>> > Uname: Linux 3.2.0-35-generic x86_64
>> > NonfreeKernelMo
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.log.
>> >
>> > .var.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
>> > DistributionCha
>> > # This is a distribution channel descriptor
>> > # For more information see
>> http://
>> > canonical-
>> > ExecutablePath: /usr/bin/
>> > InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary
>> 20120703-15:08
>> > Installed_
>> 2:0.26.
>> > MarkForUpload: True
>> > MythTVDirectory
>> > total 4
>> > drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos
>> > ProcCmdline: /usr/bin/
>> --loglevel info --syslog local7
>> > ProcEnviron:
>...
doylecentral (doyle) wrote : | #21 |
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.
Candidate: 2:0.26.
Version table:
2:
500 http://
amd64 Packages
*** 2:0.26.
100 /var/lib/
2:
500 http://
amd64 Packages
2:
500 http://
Packages
dc@mythbackend:~$
On Sun, Sep 15, 2013 at 8:44 PM, Thomas Mashos
<email address hidden>wrote:
> 0.26 or 0.27?
> Thanks,
>
> Thomas Mashos
>
>
> On Sun, Sep 15, 2013 at 5:32 PM, doylecentral
> <email address hidden> wrote:
> > I upgraded on 9/13/13 from whatever repo came with mythbuntu.
> >
> >
> > On Sun, Sep 15, 2013 at 7:02 PM, Thomas Mashos
> > <email address hidden>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:/
> >> 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:/
> >> >
> >> > Title:
> >> > mythlogserver crashed with SIGSEGV in QObject:
> >> >
> >> > 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.
> >> LP-PPA-
> >> > ProcVersionSign
> >> > Uname: Linux 3.2.0-35-generic x86_64
> >> > NonfreeKernelMo
> >> > .var.log.
> >> >
> >> > .var.log.
> >> >
> >> > .var.log.
> >> >
> >> > .var.log.
> >> >
> >> > .var.log.
> >> >
> >> > .var.log.
> >> >
> >> > .var.log.
> >> >
> >> > .var.log.
> >> >
> >> > .var.log.
> >> >
> >> > .var.log.my...
doylecentral (doyle) wrote : | #22 |
Sorry didn't see your mail.
c@mythbackend:~$ dpkg -l | grep -i myth
rc libmyth-0.25-0
2:0.25.
MythTV and add-on modules (runtime)
ii libmyth-0.26-0
2:0.26.
MythTV and add-on modules (runtime)
ii libmyth-python
2:0.26.
access some MytTV features
ii libmythtv-perl
2:0.26.
some MythTV features
ii mythbuntu-
2.2 Mythbuntu Bare Client
ii mythbuntu-common
0.67 Mythbuntu application
support functions
ii mythbuntu-
0.63-0ubuntu2 Mythbuntu Configuration
Application
ii mythbuntu-
1.08 default settings for
Mythbuntu
ii mythbuntu-desktop
0.77 The Mythbuntu standalone
system
ii mythbuntu-
1.01 Mythbuntu LightDM setup
ii mythbuntu-
0.10-0ubuntu1 Mythbuntu diagnostic
utility
ii mythgallery
2:0.26.
add-on module for MythTV
ii mythmusic
2:0.26.
MythTV
ii mythtv
2:0.26.
application (client and server)
ii mythtv-backend
2:0.26.
application (server)
ii mythtv-
2:0.26.
configure a "Master Backend" profile of MythTV.
ii mythtv-common
2:0.26.
application (common data)
ii mythtv-database
2:0.26.
application (database)
ii mythtv-frontend
2:0.26.
application (client)
ii mythtv-
2:0.26.
Theme
ii mythtv-
2:0.26.
transcoding MythTV tasks
ii mythweb
2:0.26.
module for MytTV
ii php-mythtv
2:0.26.
On Sun, Sep 15, 2013 at 7:41 PM, Thomas Mashos
<email address hidden>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 <email address hidden>
> 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
> > ...
Thomas Mashos (tgm4883) wrote : | #23 |
This is only fixed in 0.27
Thanks,
Thomas Mashos
On Sep 15, 2013 6:35 PM, "doylecentral" <email address hidden> wrote:
> Sorry didn't see your mail.
>
> c@mythbackend:~$ dpkg -l | grep -i myth
> rc libmyth-0.25-0
> 2:0.25.
> MythTV and add-on modules (runtime)
> ii libmyth-0.26-0
> 2:0.26.
> MythTV and add-on modules (runtime)
> ii libmyth-python
> 2:0.26.
> access some MytTV features
> ii libmythtv-perl
> 2:0.26.
> some MythTV features
> ii mythbuntu-
> 2.2 Mythbuntu Bare Client
> ii mythbuntu-common
> 0.67 Mythbuntu application
> support functions
> ii mythbuntu-
> 0.63-0ubuntu2 Mythbuntu Configuration
> Application
> ii mythbuntu-
> 1.08 default settings for
> Mythbuntu
> ii mythbuntu-desktop
> 0.77 The Mythbuntu standalone
> system
> ii mythbuntu-
> 1.01 Mythbuntu LightDM setup
> ii mythbuntu-
> 0.10-0ubuntu1 Mythbuntu diagnostic
> utility
> ii mythgallery
> 2:0.26.
> add-on module for MythTV
> ii mythmusic
> 2:0.26.
> MythTV
> ii mythtv
> 2:0.26.
> application (client and server)
> ii mythtv-backend
> 2:0.26.
> application (server)
> ii mythtv-
> 2:0.26.
> configure a "Master Backend" profile of MythTV.
> ii mythtv-common
> 2:0.26.
> application (common data)
> ii mythtv-database
> 2:0.26.
> application (database)
> ii mythtv-frontend
> 2:0.26.
> application (client)
> ii mythtv-
> 2:0.26.
> Theme
> ii mythtv-
> 2:0.26.
> transcoding MythTV tasks
> ii mythweb
> 2:0.26.
> module for MytTV
> ii php-mythtv
> 2:0.26.
>
>
> On Sun, Sep 15, 2013 at 7:41 PM, Thomas Mashos
> <email address hidden>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
...
Peter D. (0123peter) wrote : | #24 |
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-
or
mythtv-
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 -0000
Thomas Mashos <email address hidden> 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:/
> 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:/
> >
> > Title:
> > mythlogserver crashed with SIGSEGV in QObject:
> >
> > 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.
> > LP-PPA-
> > 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64
> > NonfreeKernelMo
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.log.
> >
> > .var.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
> > DistributionCha
> > # This is a distribution channel descriptor
> > # For more information see
> > http://
> > canonical-
> > ExecutablePath: /usr/bin/
> > 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08
> > Installed_
> > 2:0.26.
> > True MythTVDirectory
> > drwxr-xr-x 2 root root 4096 Nov 2...
keepitsimpleengr (keepitsimpleengineer) wrote : | #25 |
Not fixed.
doylecentral (doyle) wrote : Re: [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect() | #26 |
Have no idea why i'm getting this
On Sun, Sep 21, 2014 at 7:54 PM, keepitsimpleengr <
<email address hidden>> wrote:
> Not fixed.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> mythlogserver crashed with SIGSEGV in QObject:
>
> To manage notifications about this bug go to:
> https:/
>
Michael Duffy (michael-duffy-1987) wrote : | #27 |
Nor I
On Sep 22, 2014 7:01 PM, "doylecentral" <email address hidden> wrote:
> Have no idea why i'm getting this
>
> On Sun, Sep 21, 2014 at 7:54 PM, keepitsimpleengr <
> <email address hidden>> wrote:
>
> > Not fixed.
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https:/
> >
> > Title:
> > mythlogserver crashed with SIGSEGV in QObject:
> >
> > To manage notifications about this bug go to:
> > https:/
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> mythlogserver crashed with SIGSEGV in QObject:
>
> 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.
> LP-PPA-
> ProcVersionSign
> Uname: Linux 3.2.0-35-generic x86_64
> NonfreeKernelMo
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.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
> DistributionCha
> # This is a distribution channel descriptor
> # For more information see
> http://
> canonical-
> ExecutablePath: /usr/bin/
> InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary
> 20120703-15:08
> Installed_
> MarkForUpload: True
> MythTVDirectory
> total 4
> drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos
> ProcCmdline: /usr/bin/
> --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:
> ?? ()
>...
Thomas Mashos (tgm4883) wrote : | #28 |
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: | Triaged → Expired |
I believe this is caused by a bug in nzmqt. It has been reported here: /github. com/jonnydee/ nzmqt/issues/ 8 code.mythtv. org/trac/ ticket/ 10924 code.mythtv. org/trac/ ticket/ 11043 code.mythtv. org/trac/ ticket/ 11360 code.mythtv. org/trac/ ticket/ 11378
https:/
Several tickets have been filed against mythtv that appear to have this same root cause:
http://
http://
http://
as well as the mythtv ticket that links to this launchpad bug:
http://