Me TV

Unable to scan for channels, crashes on error "Cannot scan"

Bug #229896 reported by Timothy Denholm
2
Affects Status Importance Assigned to Milestone
Me TV
Fix Released
High
Unassigned

Bug Description

Application gets as far as opening a dialog that says starting to scan for channels, then errors appears saying "*** FIX ME: Cannot scan".

Additional info:
- Ubuntu 8.04 x86_64
- AVerMedia 777 DVB-T
- Terminal Output:
tim@visceroid:~$ me-tv
Me TV-Message: 13/05/08 21:08:58 - Me TV Version: 0.5.29
Me TV-Message: 13/05/08 21:08:58 - Loading glade file '/usr/share/me-tv/glade/me-tv.glade'
Me TV-Message: 13/05/08 21:08:58 - Creating EPG file at '/home/tim/.me-tv/epg.xml'
Me TV-Message: 13/05/08 21:08:58 - EPG file loaded
Me TV-Message: Exception message: '*** FIX ME: Cannot scan'
Me TV-Message: 13/05/08 21:09:03 - Exception in void ScanDialog::scan(): *** FIX ME: Cannot scan
Me TV-Message: 13/05/08 21:09:03 - Pushing error message onto queue: *** FIX ME: Cannot scan
Me TV-Message: Exception message: 'There's no channels.conf file at '/home/tim/.me-tv/channels.conf'. Me TV cannot continue.'
Me TV-Message: 13/05/08 21:09:07 - Exception in void Application::init(): There's no channels.conf file at '/home/tim/.me-tv/channels.conf'. Me TV cannot continue.
Me TV-Message: 13/05/08 21:09:09 - Terminating application normally

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

iiNet hey, another Aussie!

Thanks for raising this, it lets me know that people are actually using this. We know about this issue and it has already been fixed in the source repository. That will be 0.5.30 which is due for release shortly. I've been holding onto the release because this issue is the only thing that has changed. Do you need it to continue or do you know how to work around it?

Join us #me-tv on FreeNode if you've got time to chat.

Changed in me-tv:
assignee: nobody → lamothe
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Committed in revision 365.

Changed in me-tv:
status: Confirmed → Fix Committed
Revision history for this message
Scott Evans (vk7hse) wrote :

I too had this issue...

I managed to resole it by deleting all files in your .me-tv folder in your home directory!

Then the scan functioned as it should!

Scott

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

Thanks. I'll release it this weekend.

Revision history for this message
Timothy Denholm (tim-denholm) wrote :

I tried Scott's solution, but I still get the same error.

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

Hi Tim,

Scott forgot to mention that he also upgraded to the latest version in the source repository. ;) I see you're on IRC so we can continue there.

Thanks,

Michael

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

Released in 0.5.30

Changed in me-tv:
status: Fix Committed → Fix Released
Revision history for this message
Timothy Denholm (tim-denholm) wrote :

Yup, everything is working for me perfectly since upgrading to 0.5.30. Great work Michael, thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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