| Summary: | [abrt] Zim: ipc.py:277:start_server_if_not_running:AssertionError: Failed to start server (spawning) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Brad Hubbard <bhubbard> | ||||||
| Component: | Zim | Assignee: | Robin Lee <robinlee.sysu> | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 20 | CC: | bhubbard, byujiang, fabian, KoVadim, robinlee.sysu | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/c1c0a212e79c2680b7870ecdec0083d8c4fc4989 | ||||||||
| Whiteboard: | abrt_hash:503abf9d2eb1f413b3d1f2b6bca0594f7a26d893 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-06-29 13:44:05 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 840460 [details]
File: backtrace
Created attachment 840461 [details]
File: environ
*** Bug 917320 has been marked as a duplicate of this bug. *** Is this issue reproducible? I believe I only saw it once so, no. Another user experienced a similar problem: it happened after xfce session was restored. reporter: libreport-2.2.2 cmdline: /usr/bin/python /usr/bin/zim executable: /usr/bin/zim kernel: 3.14.8-200.fc20.x86_64 package: Zim-0.60-2.fc20 reason: ipc.py:277:start_server_if_not_running:AssertionError: Failed to start server (spawning) runlevel: N 5 type: Python uid: 1000 This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: When logging in Zim crashed as the session was being restored. Version-Release number of selected component: Zim-0.60-2.fc20 Additional info: reporter: libreport-2.1.10 cmdline: /usr/bin/python /usr/bin/zim executable: /usr/bin/zim kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: ipc.py:277:start_server_if_not_running:AssertionError: Failed to start server (spawning) Traceback (most recent call last): File "/usr/bin/zim", line 74, in <module> zim.main(argv) File "/usr/lib/python2.7/site-packages/zim/__init__.py", line 443, in main start_server_if_not_running() File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 277, in start_server_if_not_running raise AssertionError, 'Failed to start server (spawning)' AssertionError: Failed to start server (spawning) Local variables in innermost frame: trace: 'Traceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 267, in start_server_if_not_running\n s.ping()\n File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 750, in call\n conn = Client(SERVER_ADDRESS, SERVER_ADDRESS_FAMILY)\n File "/usr/lib64/python2.7/multiprocessing/connection.py", line 173, in Client\n c = SocketClient(address)\n File "/usr/lib64/python2.7/multiprocessing/connection.py", line 301, in SocketClient\n s.connect(address)\n File "/usr/lib64/python2.7/socket.py", line 224, in meth\n return getattr(self._sock,name)(*args)\nerror: [Errno 2] No such file or directory\n' ZimCmd: <function ZimCmd at 0x7f5aa1ce1b18> i: 9 app: <Application: ('/usr/bin/python', u'/usr/bin/zim')> loglevel: 30 s: <zim.ipc.ServerProxyClass object at 0x7f5a9ff8cad0> time: <module 'time' from '/usr/lib64/python2.7/lib-dynload/timemodule.so'>