Failed to lock to channel

Bug #371165 reported by FrenchNux
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Me TV
Fix Released
Medium
Unassigned
me-tv (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: me-tv

I m using jaunty 64bits and Me-tv 0.8.9

i haven't got this issue with me-tv 0.8.7
Sometimes i have got "Exception: Failed to lock to channel"

03/05/2009 11:42:47: Setting display channel to 'NANTES' (21)
03/05/2009 11:42:47: Thread 'Stream' created
03/05/2009 11:42:47: Creating StreamThread
03/05/2009 11:42:47: StreamThread created
03/05/2009 11:42:47: Removing demuxers
03/05/2009 11:42:47: Waiting for signal lock ...
03/05/2009 11:42:49: status: 13
03/05/2009 11:42:49: currently tuned to freq 530166000, symbol rate 0, inner fec 2
03/05/2009 11:42:49: Exception: Failed to lock to channel
03/05/2009 11:42:49: Destroying StreamThread
03/05/2009 11:42:49: Removing demuxers
03/05/2009 11:42:49: StreamThread destroyed

Related branches

Revision history for this message
FrenchNux (christophe-pauc) wrote :
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

I get these too but it's due to poor reception. Is this the same with you? What would you expect it to say?

Changed in me-tv (Ubuntu):
status: New → Incomplete
Revision history for this message
FrenchNux (christophe-pauc) wrote :

with same reception i don't have this issue with me-tv 0.8.7

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

I'm setting the Ubuntu bug to invalid. This is not the version of Me TV that is in Ubuntu.

Changed in me-tv (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Now, I did change a timeout value recently but I thought that there was a separate one for DVB-S, you are DVB-S, right?

I might have to revert that change.

Changed in me-tv:
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
FrenchNux (christophe-pauc) wrote :

strength signal >60%

i am not sure but i think i am DVB-t (Digital Video Broadcasting – Terrestrial)

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Do you have an antenna? I think that you might be DVB-T, assuming that you are French.

I put that setting back to 5 seconds instead of 2 seconds. Hope that helps in the next release. There's still a major issue with data storage. New added scheduled recordings seem to clobber old ones, same with channels. When I sort that out, I'll release the next version. 0.8.7 is really stable, 0.8.8-0.8.9 are really only trying to resolve that performance issue in Jaunty's sqlite version.

If you're having issues, go back to 0.8.7, I know that it can lock up for 2 minutes at a time but it really should be an initial thing as it saves the EPG events. Once all the EPG events are in the database everything should run smoothly.

Revision history for this message
FrenchNux (christophe-pauc) wrote :

I chose to help by testing me-tv versions and reporting issues.

with > 80% reception, issue will appear again?

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Indeed, I just assume that everyone is trying to use the application rather than help make it better. That is my failing, but I'm very happy that you're here to help.

Really, it's just a word of warning for 0.8.8-0.8.9 users that the application is somewhat unstable after the performance fix for Jaunty. I've been running 0.8.7 for weeks without issue (or complaint from my wife).

Do you know how to build from bzr? I have a fix for this specific issue in revision 423 but I can't release it until I get the other stuff working. You could confirm this for me.

Revision history for this message
FrenchNux (christophe-pauc) wrote :

sorry i don't know ... But if you explain to me i probably build from bzr

Revision history for this message
FrenchNux (christophe-pauc) wrote :

i build package with revision 423...

in a first time, it seems better.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Good for you.

Changed in me-tv:
status: In Progress → Fix Committed
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Released in 0.8.10

Changed in me-tv:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package me-tv - 0.9.4-0ubuntu1

---------------
me-tv (0.9.4-0ubuntu1) karmic; urgency=low

  * New upstream release (LP: #379706)
    - Fix to stop EPG update crashing the application
      after faulty save (LP: #72872)
    - Fixed spin buttons from GtkBuilder conversion (LP: #382197)
    - Fixed icon on application popup menu (LP: #379685)
    - Fixed compiling of me-tv-0.8.12 fails on Fedora 11 (LP: #377020)
    - Fixed Failed to lock to channel at boot (LP: #377050)
    - Increased timeout to 5 seconds again (LP: #371165)
    - Fixed me-tv unusually slow, often freezes (LP: #351510)
    - Fixed channel persistence (LP: #361514)
    - Fix for forward slashes in description (LP: #359710)
    - Fixed Must create .me-tv directory manually (LP: #353796)
    - Fixed audio stream can't be changed (LP: #350402)
  * debian/control:
    - Removed dependency libxine1-ffmpeg, libxine1-x
    - Removed libglademm-2.4-dev Build-Depends.

 -- Scott Evans <email address hidden> Sat, 27 Jun 2009 00:46:22 +1000

Changed in me-tv (Ubuntu):
status: Invalid → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.