Bug 922313
| Summary: | [abrt] systemd-analyze-197-1.fc18.2: systemd-analyze:23:<module>:ImportError: No module named gi.repository | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew <travneff> | ||||||
| Component: | systemd | Assignee: | systemd-maint | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 18 | CC: | johannbg, lnykryn, metherid, msekleta, notting, plautrba, systemd-maint, travneff, uckelman, vpavlin, zbyszek | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:ae9ec77b1e4fa66c4f54ce917a56d72f2345b802 | ||||||||
| Fixed In Version: | systemd-201-2.fc18.6 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-05-16 02:58:02 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 710996 [details]
File: backtrace
Created attachment 710997 [details]
File: environ
May be related to recent yum update which installed systemd-python-197-1.fc18.2.x86_64 Solved after installing pygobject3 (and pygobject3-base as dependency). pygobject2 was already installed. I'm not familiar with python, but seems like either pygobject3 should be a dep for systemd-python or systemd-python should use pygobject2. Similar issues for Arch linux: https://bugs.archlinux.org/task/32822 https://bugs.archlinux.org/task/32969 For Fedora for now, it should definitely be using pygobject2 until the system as a whole moves to python3. I can confirm that the problem goes away after installing pygobject3. This is fixed in a way in F19, btw, since systemd-analyze is now a C tool. systemd-201-2.fc18.1 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/systemd-201-2.fc18.1 Package systemd-201-2.fc18.2: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.2' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.2 then log in and leave karma (feedback). Package systemd-201-2.fc18.4: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.4' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.3 then log in and leave karma (feedback). Package systemd-201-2.fc18.5: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.5 then log in and leave karma (feedback). systemd-201-2.fc18.6 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6 Package systemd-201-2.fc18.6: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6 then log in and leave karma (feedback). systemd-201-2.fc18.6 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: Happens always after launching systemd-analyze, parameters don't matter. Version-Release number of selected component: systemd-analyze-197-1.fc18.2 Additional info: cmdline: /usr/bin/python /bin/systemd-analyze blame core_backtrace: 88e14038cc215ec67a5d143047e34b99a98262ed 0x17 <module> /bin/systemd-analyze - executable: /bin/systemd-analyze kernel: 3.8.2-206.fc18.x86_64 uid: 1000 Truncated backtrace: systemd-analyze:23:<module>:ImportError: No module named gi.repository Traceback (most recent call last): File "/bin/systemd-analyze", line 23, in <module> from gi.repository import Gio ImportError: No module named gi.repository Local variables in innermost frame: argparse: <module 'argparse' from '/usr/lib64/python2.7/argparse.pyc'> __builtins__: <module '__builtin__' (built-in)> __file__: '/bin/systemd-analyze' __package__: None sys: <module 'sys' (built-in)> __name__: '__main__' os: <module 'os' from '/usr/lib64/python2.7/os.pyc'> __doc__: None