Bug 1023985

Summary: Raising exceptions results in garbage objects
Product: [Fedora] Fedora Reporter: Thomas Woerner <twoerner>
Component: dbus-pythonAssignee: Dan Mashal <dan.mashal>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, nphilipp, rdieter, samuel-rhbugs, stefano
Target Milestone: ---Keywords: MoveUpstream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:50:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1014209, 1014548    
Attachments:
Description Flags
example tar archive with mechanism.py and test.py none

Description Thomas Woerner 2013-10-28 13:58:35 UTC
Created attachment 816812 [details]
example tar archive with mechanism.py and test.py

Description of problem:
python3 gc finds garbage objects if Exceptions are used in the mechanism.

Version-Release number of selected component (if applicable):
python3-dbus-1.1.1-5.fc19.x86_64

How reproducible:
Always

Steps to Reproduce:
1. yum install python3-dbus
2. Extract example tar archive as root
3. cd example
4. make install
5. python3 mechanism.py
6. Open another root-shell, got to the example directory: python3 test.py

Actual results:
Garbage objects

Expected results:
No garbage objects

Additional info:
This is not a problem if using python2.

Comment 1 Thomas Woerner 2013-10-28 14:02:46 UTC
There seems to be a race condition somewhere. The test.py script just calls the raise_exception method in ExampleObject several times.

Comment 2 Thomas Woerner 2013-10-28 14:20:39 UTC
The example bases on the examples from python-slip, but without polkit and python-slip support.

Comment 3 Thomas Woerner 2013-10-28 14:45:11 UTC
This is also a problem in Fedora 20.

Comment 4 Rex Dieter 2013-10-28 15:50:22 UTC
Mind testing
https://admin.fedoraproject.org/updates/dbus-python-1.2.0-1.fc20
?

If that helps here, can consider doing a f19 update too.

Comment 5 Thomas Woerner 2013-10-28 16:25:40 UTC
I updated to this version in my Fedora-19 installation and the problem is still there.

Comment 6 Rex Dieter 2013-10-28 17:26:28 UTC
OK, thanks. :(

Mind poking upstream?

https://bugs.freedesktop.org/enter_bug.cgi?product=dbus

against 'python' component.

Comment 7 Thomas Woerner 2013-10-29 17:40:47 UTC
Opened upstream bugzilla https://bugs.freedesktop.org/show_bug.cgi?id=71013

Comment 8 Fedora End Of Life 2015-01-09 20:23:27 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 9 Fedora End Of Life 2015-02-17 17:50:22 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.