Description of problem: After updating to selinux-policy-3.9.16-30.fc15 from update testing sealert does not work, and it show the following error: Opps, sealert hit an error! Traceback (most recent call last): File "/usr/bin/sealert", line 692, in <module> run_as_dbus_service(username) File "/usr/bin/sealert", line 112, in run_as_dbus_service app = SEAlert(user, dbus_service.presentation_manager, watch_setroubleshootd=True) File "/usr/bin/sealert", line 326, in __init__ from setroubleshoot.browser import BrowserApplet File "/usr/lib/python2.7/site-packages/setroubleshoot/browser.py", line 46, in <module> import report.io.GTKIO ImportError: No module named GTKIO Version-Release number of selected component (if applicable): setroubleshoot-3.0.35-1.fc15.i686 setroubleshoot-server-3.0.35-1.fc15.i686 setroubleshoot-plugins-3.0.14-2.fc15.noarch selinux-policy-3.9.16-30.fc15.noarch selinux-policy-targeted-3.9.16-30.fc15.noarch How reproducible: 100% Steps to Reproduce: 1. Start sealert 2. 3. Actual results: Expected results: Additional info:
Sorry does not seems related to selinux-policy-3.9.16-30.fc15
Seems to be related to report-0.20-2.fc15.i686
libreport-gtk obsoletes report-gtk, which uninstalls the Python code needed by e.g. setroubleshoot.
Seems fixed with the last updates : libreport-gtk-2.0.4-2.fc15.i686 libreport-2.0.4-2.fc15.i686 # python Python 2.7.1 (r271:86832, Apr 12 2011, 16:16:18) [GCC 4.6.0 20110331 (Red Hat 4.6.0-2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import report.io.GTKIO >>> dir(report.io.GTKIO) ['ButtonBoxDialog', 'FailDialog', 'FieldDialog', 'GTKIO', 'LoginDialog', 'MessageDialog', 'SuccessDialog', '_', '__builtins__', '__doc__', '__file__', '__name__', '__package__', 'gio', 'os', 'report'] >>>
That one has been pulled already, because it doesn't fix the bad Provides/Obsoletes added in the previous -1.fc15 release: https://admin.fedoraproject.org/updates/libreport-2.0.4-2.fc15 It could be that two updates will be needed: * a libreport-gtk update with a self-Obsoletes, i.e. <= %version-%release * a report-gtk update with a Version bump (or Epoch bump as a last resort). The problem is that libreport-2.0.4-1.fc15 has erased report-gtk, libreport-2.0.4-2.fc15 doesn't add it back (Prov/Obs got removed from the pkg), and report-gtk will need to become > 0.20 to be pulled back in again.
And that works actually. An upgrade of "report" to 0.21 from Rawhide plus a self-Obsoletes in libreport-gtk: $ diff -u libreport.spec~ libreport.spec --- libreport.spec~ 2011-06-28 17:31:59.000000000 +0200 +++ libreport.spec 2011-06-28 17:33:00.562496706 +0200 @@ -5,7 +5,7 @@ Summary: Generic library for reporting various problems Name: libreport Version: 2.0.4 -Release: 2%{?dist} +Release: 3%{?dist} License: GPLv2+ Group: System Environment/Libraries URL: https://fedorahosted.org/abrt/ @@ -63,6 +63,7 @@ Summary: GTK front-end for libreport Group: User Interface/Desktops Requires: libreport = %{version}-%{release} +Obsoletes: libreport-gtk < %{version}-%{release} %description gtk Applications for reporting bugs using libreport backend [...] Loaded plugins: langpacks, presto, refresh-packagekit Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package libreport.x86_64 0:2.0.4-1.fc15 will be updated ---> Package libreport.x86_64 0:2.0.4-3.fc15 will be an update ---> Package libreport-gtk.x86_64 0:2.0.4-1.fc15 will be updated --> Processing Dependency: report-gtk for package: setroubleshoot-3.0.37-1.fc15.x86_64 --> Processing Dependency: report-gtk for package: python-meh-0.11-2.fc15.noarch ---> Package libreport-gtk.x86_64 0:2.0.4-1.fc15 will be obsoleted ---> Package libreport-gtk.x86_64 0:2.0.4-3.fc15 will be obsoleting --> Running transaction check ---> Package report-gtk.x86_64 0:0.21-0.fc15 will be installed --> Processing Dependency: report(x86-64) = 0.21-0.fc15 for package: report-gtk-0.21-0.fc15.x86_64 --> Running transaction check ---> Package report.x86_64 0:0.20-2.fc15 will be updated --> Processing Dependency: report = 0.20-2.fc15 for package: report-newt-0.20-2.fc15.x86_64 --> Processing Dependency: report = 0.20-2.fc15 for package: report-plugin-bugzilla-0.20-2.fc15.x86_64 --> Processing Dependency: report = 0.20-2.fc15 for package: report-plugin-localsave-0.20-2.fc15.x86_64 --> Processing Dependency: report = 0.20-2.fc15 for package: report-plugin-scp-0.20-2.fc15.x86_64 --> Processing Dependency: report = 0.20-2.fc15 for package: report-plugin-ftp-0.20-2.fc15.x86_64 ---> Package report.x86_64 0:0.21-0.fc15 will be an update --> Running transaction check ---> Package report-newt.x86_64 0:0.20-2.fc15 will be updated ---> Package report-newt.x86_64 0:0.21-0.fc15 will be an update ---> Package report-plugin-bugzilla.x86_64 0:0.20-2.fc15 will be updated --> Processing Dependency: report-plugin-bugzilla = 0.20-2.fc15 for package: report-config-bugzilla-redhat-com-0.20-2.fc15.x86_64 ---> Package report-plugin-bugzilla.x86_64 0:0.21-0.fc15 will be an update ---> Package report-plugin-ftp.x86_64 0:0.20-2.fc15 will be updated --> Processing Dependency: report-plugin-ftp = 0.20-2.fc15 for package: report-config-ftp-0.20-2.fc15.x86_64 ---> Package report-plugin-ftp.x86_64 0:0.21-0.fc15 will be an update ---> Package report-plugin-localsave.x86_64 0:0.20-2.fc15 will be updated --> Processing Dependency: report-plugin-localsave = 0.20-2.fc15 for package: report-config-localsave-0.20-2.fc15.x86_64 ---> Package report-plugin-localsave.x86_64 0:0.21-0.fc15 will be an update ---> Package report-plugin-scp.x86_64 0:0.20-2.fc15 will be updated --> Processing Dependency: report-plugin-scp = 0.20-2.fc15 for package: report-c onfig-scp-0.20-2.fc15.x86_64 ---> Package report-plugin-scp.x86_64 0:0.21-0.fc15 will be an update --> Running transaction check ---> Package report-config-bugzilla-redhat-com.x86_64 0:0.20-2.fc15 will be updated ---> Package report-config-bugzilla-redhat-com.x86_64 0:0.21-0.fc15 will be an update ---> Package report-config-ftp.x86_64 0:0.20-2.fc15 will be updated ---> Package report-config-ftp.x86_64 0:0.21-0.fc15 will be an update ---> Package report-config-localsave.x86_64 0:0.20-2.fc15 will be updated ---> Package report-config-localsave.x86_64 0:0.21-0.fc15 will be an update ---> Package report-config-scp.x86_64 0:0.20-2.fc15 will be updated ---> Package report-config-scp.x86_64 0:0.21-0.fc15 will be an update --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: libreport-gtk x86_64 2.0.4-3.fc15 localrepo 27 k replacing libreport-gtk.x86_64 2.0.4-1.fc15 Updating: libreport x86_64 2.0.4-3.fc15 localrepo 103 k Installing for dependencies: report-gtk x86_64 0.21-0.fc15 localrepo 18 k Updating for dependencies: report x86_64 0.21-0.fc15 localrepo 73 k report-config-bugzilla-redhat-com x86_64 0.21-0.fc15 localrepo 14 k report-config-ftp x86_64 0.21-0.fc15 localrepo 14 k report-config-localsave x86_64 0.21-0.fc15 localrepo 13 k report-config-scp x86_64 0.21-0.fc15 localrepo 14 k report-newt x86_64 0.21-0.fc15 localrepo 17 k report-plugin-bugzilla x86_64 0.21-0.fc15 localrepo 29 k report-plugin-ftp x86_64 0.21-0.fc15 localrepo 16 k report-plugin-localsave x86_64 0.21-0.fc15 localrepo 16 k report-plugin-scp x86_64 0.21-0.fc15 localrepo 18 k Transaction Summary ================================================================================ Install 2 Package(s) Upgrade 11 Package(s) Total download size: 371 k Is this ok [y/N]: Exiting on user Command Complete!
And while a self-Obsoletes can be helpful with multiarch dependency troubles, it isn't needed here. An upgrade of report to >= 0.21 plus a sane libreport update would suffice.
*** This bug has been marked as a duplicate of bug 715373 ***