Version-Release number of selected component: jpackage-utils-1.7.5-18.1.fc17 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 cmdline: /usr/bin/python /usr/lib/rpm/osgi.prov kernel: 3.5.2-3.fc17.x86_64
Created attachment 609141 [details] File: backtrace
Created attachment 609142 [details] File: core_backtrace
rebooted after update, logged into standard Gnome session, got black background error announcement Package: jpackage-utils-1.7.5-18.1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
For me this looks like a bug in python - _RealGetContents from zipfile.py is calling seek() with invalid argument. Reassigning to python package.
Notes: - Although the error is raised in _RealGetContents, the actual problem seems to be in zipfile.is_zipfile, which wrongly returns True for /usr/bin/fastjar (normal binary). - Reproduce: -- yum install libgcj, that provides /usr/bin/fastjar -- # the following line should print False, but prints True -- python -c "import zipfile; print zipfile.is_zipfile('/usr/bin/fastjar')" - The core of the problem seems to be in fact, that stringEndArchive ("PK\005\006") is found in the file. Reported upstream as http://bugs.python.org/issue16735
Part of the problem is that osgi.prov should have never been called on that binary because it doesn't end with ".jar". Quick look doesn't tell me why it was called because we have this in osgi.attr (rpm auto-requires/provides generator): %__osgi_provides %{_rpmconfigdir}/osgi.prov #%__osgi_requires %{_rpmconfigdir}/osgi.req %__osgi_path ^(.*\.jar|((%{_libdir}|%{_datadir}).*/MANIFEST.MF)) Note that third line has correctly escaped dot before jar
(In reply to comment #7) > Note that third line has correctly escaped dot before jar I think there needs to be double escaping - one for rpm and one for glibc.
Created attachment 666574 [details] Reproducer Reproduce with: rpmbuild -ba foo.spec
Fixed upstream: http://git.fedorahosted.org/cgit/javapackages.git/commit/?id=5a855c8b189a46919de1f769ae57d9e21384d55a
This bug is fixed in Fedora 18 and later. For now there are no plans to make this fix in Fedora 17.