Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1436566

Summary: Invoking the application when a primary instance is present leads to CRITICALs
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Pelka <tpelka>
Component: gnome-documentsAssignee: Debarshi Ray <debarshir>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: jkoten, mkrajnak
Target Milestone: rcKeywords: Regression, Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnome-documents-3.22.2-5.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 10:01:37 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 Tomas Pelka 2017-03-28 08:22:36 UTC
Description of problem:
Can't start gnome-documents due to 

Version-Release number of selected component (if applicable):
gnome-documents-3.22.2-1.el7.x86_64
glib2-2.50.3-2.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. G_MESSAGES_DEBUG=all G_MESSAGES_PREFIXED=all gnome-documents
2.
3.

Actual results:
(org.gnome.Documents:32032): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport_from_connection: assertion 'interface_->priv->connections != NULL' failed
You have new mail.

Expected results:
no error and gnome-documents should start

Additional info:
Please advice any logs or debug I could provide.

Comment 1 Martin Krajnak 2017-04-06 14:51:51 UTC
This is not an issue in gnome-documents-3.22.2-2.el7.x86_64

Comment 2 Martin Krajnak 2017-04-20 12:12:38 UTC
Once again I encountered this issue with following reproducer:

From terminal:
1. pkill gnome-documents
2. Run gnome-documents via Gnome shell and close it
3. run gnome-documents via terminal again

Result:
$ gnome-documents 

(org.gnome.Documents:30176): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport_from_connection: assertion 'interface_->priv->connections != NULL' failed

Comment 3 Debarshi Ray 2017-06-09 14:20:56 UTC
I have built gnome-documents-3.22.2-5.el7:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13392324

Comment 5 Martin Krajnak 2017-06-14 13:56:02 UTC
The issue is resolved in gnome-documents-3.22.2-5.el7.

Comment 6 errata-xmlrpc 2017-08-01 10:01:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2312