Bug 1408969

Summary:	Dbus-sharp needs an update or at least a couple of patches from 0.8.0 included
Product:	[Fedora] Fedora	Reporter:	Alex Tereschenko <frozen.and.blue>
Component:	dbus-sharp	Assignee:	Christian Krause <chkr>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	chkr, pokorra.mailinglists
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	dbus-sharp-0.8.1-3.fc26	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-02 16:48:59 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:

Description Alex Tereschenko 2016-12-28 15:40:46 UTC

Description of problem:
Fedora's dbus-sharp version is very old and contains a bug, which causes some DBus signals to not be delivered to clients. That causes, among other things, "application not responding" warning window upon logout for a properly written application. I've got this for Tomboy I'm maintaining (https://github.com/tomboy-notes/tomboy/issues/32), but after an investigation it turned out the reason is the lack of these two patches in Fedora's dbus-sharp, which are not present in 0.7.0 and went in with 0.8.0:

1) https://github.com/mono/dbus-sharp/commit/608328ba1e0ccc8d0387c244793b229bcc184648

2) https://github.com/mono/dbus-sharp/commit/76f43e6cc25eae25b658831111b37b10376311d2

They were backported to e.g. Debian and reused in Ubuntu, so there's no such problem there.

In general, while these two patches would be sufficient to fix the specific problem at hand, it would be nice to have Fedora package updated to the latest release, which contains several other fixes, could be useful for other people.

Version-Release number of selected component (if applicable):
0.7.0-15

How reproducible:
always

Steps to Reproduce:
1. Install Tomboy
2. Run Tomboy as "DBUS_DEBUG=1 tomboy --debug"
3. Try to logout from the session

Actual results:
"Program not responding" window appears with Tomboy listed

Expected results:
Logoff happens right away as Tomboy is properly implementing the necessary DBus signal handling for session termination.

Additional info:

Comment 1 Fedora Update System 2017-07-12 17:22:52 UTC

mono-zeroconf-0.9.0-19.fc26 dbus-sharp-0.15-2.hg2030296.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cc40ade2bd

Comment 2 Fedora Update System 2017-07-13 23:51:15 UTC

dbus-sharp-0.15-2.hg2030296.fc26, mono-zeroconf-0.9.0-19.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cc40ade2bd

Comment 3 Alex Tereschenko 2017-07-16 11:48:04 UTC

Checked on fedora 26 with all updates as of today - with current dbus-sharp version 0.8.1 this problem no longer occurs, so I think this is fixed.

On a side note, I see that dbus-sharp-glib is still at 0.6.0, whereas I'd expect it to be the same as dbus-sharp itself, however as this doesn't seem to cause any problems with Tomboy, I'd leave it up to you to decide what to do with that.

Thanks for fixing this on behalf of all Tomboy users! :)

Comment 4 Fedora Update System 2017-07-18 19:36:30 UTC

banshee-2.6.2-21.fc26 dbus-sharp-0.8.1-2.fc26 mono-zeroconf-0.9.0-19.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cc40ade2bd

Comment 5 Fedora Update System 2017-07-20 00:24:41 UTC

banshee-2.6.2-21.fc26, dbus-sharp-0.8.1-2.fc26, mono-zeroconf-0.9.0-19.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cc40ade2bd

Comment 6 Fedora Update System 2017-07-23 16:20:40 UTC

banshee-2.6.2-22.fc26 dbus-sharp-0.8.1-3.fc26 mono-zeroconf-0.9.0-20.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cc40ade2bd

Comment 7 Fedora Update System 2017-07-25 04:24:04 UTC

banshee-2.6.2-22.fc26, dbus-sharp-0.8.1-3.fc26, mono-zeroconf-0.9.0-20.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cc40ade2bd

Comment 8 Fedora Update System 2017-08-02 16:48:59 UTC

banshee-2.6.2-22.fc26, dbus-sharp-0.8.1-3.fc26, mono-zeroconf-0.9.0-20.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.