Bug 1064367

Summary: [abrt] Zim: ipc.py:753:call:IOError: [Errno 104] Connection reset by peer
Product: [Fedora] Fedora Reporter: Pierguido Lambri <plambri>
Component: ZimAssignee: Robin Lee <robinlee.sysu>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fabian, robinlee.sysu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d302c155867d9a760fa8eee5044e84bb2fa20615
Whiteboard: abrt_hash:95b4001b076809cafc9078478518dea57cbe07b0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 15:09:48 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:
Description Flags
File: backtrace
none
File: environ none

Description Pierguido Lambri 2014-02-12 13:39:35 UTC
Version-Release number of selected component:
Zim-0.60-2.fc20

Additional info:
reporter:       libreport-2.1.12
cmdline:        /usr/bin/python /usr/bin/zim
executable:     /usr/bin/zim
kernel:         3.13.0-1.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
ipc.py:753:call:IOError: [Errno 104] Connection reset by peer

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 445, in main
    gui = server.get_notebook(notebook)
  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 805, in get_notebook
    return self.get_proxy(RemoteObject(self._notebookklass, uri), open)
  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 785, in get_proxy
    if not self.has_object(remoteobject):
  File "/usr/lib/python2.7/site-packages/zim/ipc.py", line 753, in call
    re = conn.recv()
IOError: [Errno 104] Connection reset by peer

Local variables in innermost frame:
name: 'has_object'
self: <zim.ipc.ServerProxyClass object at 0x7fc4a1b3b090>
args: (<RemoteObject: zim.gui.GtkInterface(file:///home/plambri/Notes)>,)
kwargs: {}
msg: <RemoteMethodCall: 4492: zim.ipc.Server(None).has_object((<RemoteObject: zim.gui.GtkInterface(file:///home/plambri/Notes)>,), {})>
conn: <read-write Connection, handle 4>

Comment 1 Pierguido Lambri 2014-02-12 13:39:47 UTC
Created attachment 862299 [details]
File: backtrace

Comment 2 Pierguido Lambri 2014-02-12 13:39:51 UTC
Created attachment 862300 [details]
File: environ

Comment 3 Robin Lee 2014-02-14 06:54:30 UTC
Is this issue reproducible?

Comment 4 Fedora End Of Life 2015-05-29 10:53:52 UTC
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.

Comment 5 Fedora End Of Life 2015-06-29 15:09:48 UTC
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.