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?
Have no idea why i'm getting this
On Sun, Sep 21, 2014 at 7:54 PM, keepitsimpleengr
1101...@bugs.launchpad.net wrote:
Not fixed.
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1101395
Title:
mythlogserver crashed
Nor I
On Sep 22, 2014 7:01 PM, doylecentral 1101...@bugs.launchpad.net wrote:
Have no idea why i'm getting this
On Sun, Sep 21, 2014 at 7:54 PM, keepitsimpleengr
1101...@bugs.launchpad.net wrote:
Not fixed.
--
You received this bug notification because you are subscribed to the bug
Not fixed.
--
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:
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
Bug still exists 16th September.
--
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
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,
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
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
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]
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
also make sure you are running a 0.27 based build not earlier.
On Sep 15, 2013 6:41 PM, Thomas Mashos tho...@mashos.com 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
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.netwrote:
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
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.netwrote:
Are you running packages that
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:
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
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
This bug was fixed in the package mythtv -
2:0.27.0+fixes.20130907.ac841f0-0ubuntu3
---
mythtv (2:0.27.0+fixes.20130907.ac841f0-0ubuntu3) saucy; urgency=low
* Add a patch to readjust the inclusion order to fix FTBFS on PPC.
- Submitted upstream at
** Branch linked: lp:ubuntu/saucy-proposed/mythtv
--
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
** Changed in: mythtv
Remote watch: code.mythtv.org/trac/ #11360 = code.mythtv.org/trac/ #10924
--
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
mythlogserver crashes on on frontend-mythbuntobox and on front-/backend-
mythbuntubox, and it does unpredictable. Perhaps there is some hint in
the mythfrontend.log (see attachment).
** Attachment added: mythfrontend.log
This happens almost every start up.
--
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
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
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
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 emp2...@att.net 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
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
Thanks for the patch. Once upstream applies it it will land in our auto
builds.
On Feb 5, 2013 1:01 AM, H Buus myt...@hbuus.com wrote:
See http://code.mythtv.org/trac/ticket/10924 for a patch (mythlogserver-
segv.patch) that I believe will fix this problem.
--
You received this bug
See http://code.mythtv.org/trac/ticket/10924 for a patch (mythlogserver-
segv.patch​) that I believe will fix this problem.
--
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:
I believe this is caused by a bug in nzmqt. It has been reported here:
https://github.com/jonnydee/nzmqt/issues/8
Several tickets have been filed against mythtv that appear to have this same
root cause:
http://code.mythtv.org/trac/ticket/10924
http://code.mythtv.org/trac/ticket/11043
** Bug watch added: code.mythtv.org/trac/ #11360
http://code.mythtv.org/trac/ticket/11360
** Also affects: mythtv via
http://code.mythtv.org/trac/ticket/11360
Importance: Unknown
Status: Unknown
** Also affects: mythtv (Ubuntu)
Importance: Undecided
Status: New
**
** Tags removed: need-amd64-retrace
--
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
31 matches
Mail list logo