Mybuntu Log Grabber does not open until pressing the close button on an error dialog box.

[warren]

1) Mybuntu 12.10 i386 Live USB daily build 10-6-2012
2) mythbuntu-log-grabber 0.10-0ubuntu1
3) I expected to open the Mythbuntu Log Grabber from the menu without an error dialog box in the process.
4) Applications/Accessories/Mythbuntu Log Grabber then the error dialog box containing 'Exception in captureState of plugin Repositories Disabling Plugin.' then the close button which get one to the Mythbuntu log grabber.
Two images have been attached to the bug report showing what occurred.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: mythbuntu-log-grabber 0.10-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
CasperVersion: 1.327
Date: Sun Oct 7 02:36:40 2012
LiveMediaBuild: Mythbuntu 12.10 "Quantal Quetzal" - Beta i386 (20121006)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: mythbuntu-log-grabber
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1063089

[warren (wkclemmons)]

Please provide more info.
So this a duplicate because I get same error message from two different
applications.

[Thomas Mashos (tgm4883)]

No, this is a duplicate because you get the same error in the same application. Mythbuntu Log Grabber is a plugin for the Mythbuntu Control Centre. It launches MCC with flags to only show the Log Grabber, which is why you see only the Log Grabber and not the rest of the plugins.

You did everything correct. We want separate bugs for errors with different plugins. In this odd case, the error was caused by the Mythbuntu-repos plugin and shows up whenever Mythbuntu Control Centre is launched. Only after investigation was I able to determine the two bugs were caused by the same plugin.