Mythbuntu Control Centre error in compareState after upgrade to Trusty

[Richard Kershenbaum]

After upgrading to Trusty, I get "Exception in compareState of plugin Repositories" when using the MySQL or Backup tabs, after hitting "apply". Upgrading to mythbuntu-common 0.74 did not fix the problem.

The CLI reports errors as follows:

$ mythbuntu-control-centre
WARNING: Error importing plugin bare_console
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/MythbuntuControlCentre/plugin.py", line 56, in reload_plugins
    __import__(plugin, None, None, [''])
  File "/usr/share/mythbuntu/plugins/python/bare_console.py", line 29, in <module>
    import gobject
ImportError: No module named 'gobject'
Reading package lists... Done
Building dependency tree
Reading state information... Done
Traceback (most recent call last):
  File "/usr/bin/mythbuntu-control-centre", line 360, in compareState
    plugin.compareState()
  File "/usr/share/mythbuntu/plugins/python/mythbuntu_repos.py", line 193, in compareState
    SELVER = self.convertVersion(self.repobox.get_active_text())
  File "/usr/share/mythbuntu/plugins/python/mythbuntu_repos.py", line 185, in convertVersion
    if VERSION.endswith(".x"):
AttributeError: 'NoneType' object has no attribute 'endswith'

[Thomas Mashos (tgm4883)]

For the first error, remove the mythbuntu-bare-console package. It was something I was testing and doesn't work right.

For the second error, I cannot reproduce this. Do you see a "Repositories" tab on the right side of MCC?

[Thomas Mashos (tgm4883)]

Hmm, can you also check to see if you have the 'mythbuntu-repos' package installed?

[Richard Kershenbaum (richard-dblhouse)]

Thomas, thanks for looking at this! Based on your replies, I have resolved the errors.

First, I removed mythbuntu-bare-console in Synaptic. That didn't (by itself) eliminate the error in MythBuntu backup, when invoked from MCC.

Next, I opened MCC and navigated to "repositories". The menu under "Select which version..." was blank, so apparently no version was selected. (Should I have needed to do this manually?) I selected 0.27, and clicked "Refresh available repositories", and replied to the subsequent messages. Then I ran "Software Updater", and some MythBuntu and MythTV updates were installed.

After that completed, I ran both a backup and a MySQL optimize within MCC without encountering the prior errors.

Thanks again!

[Thomas Mashos (tgm4883)]

Hmm.

What version did you upgrade from, and what mythtv version were you on?

[Richard Kershenbaum (richard-dblhouse)]

I had been running for some time on 12.10 with MythTV 0.26. I upgraded to 13.10 and then immediately to 14.04 with MythTV 0.27.

I know this is an unsupported upgrade path. I had a problem on MythBuntu 12.04 that was solved by upgrading to 12.10. So I was not running an LTS release before I moved to Trusty.

[Thomas Mashos (tgm4883)]

Did you have the mythbuntu-repos activated so you could get 0.26
updates on 12.10?
Thanks,

Thomas Mashos

On Thu, May 29, 2014 at 12:52 PM, Richard Kershenbaum
<email address hidden> wrote:
> I had been running for some time on 12.10 with MythTV 0.26. I upgraded
> to 13.10 and then immediately to 14.04 with MythTV 0.27.
>
> I know this is an unsupported upgrade path. I had a problem on
> MythBuntu 12.04 that was solved by upgrading to 12.10. So I was not
> running an LTS release before I moved to Trusty.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1322746
>
> Title:
> Mythbuntu Control Centre error in compareState after upgrade to Trusty
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mythbuntu/+bug/1322746/+subscriptions

[Richard Kershenbaum (richard-dblhouse)]

Yes. I probably activated them when I upgraded from MythTV 0.25. I do know that I was getting MythTV updates on 12.10.

[Thomas Mashos (tgm4883)]

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.

[Richard Kershenbaum (richard-dblhouse)]

Since this apparently only occurs after an upgrade, and I've long-ago completed the upgrade, I no longer have a way to replicate the problem.

I concur with closing the bug report.

Thanks to everyone for all the great work on MythTV and for looking at this specific problem!