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.

Description of problem:
I played a bit with collections and I found one crash. After that I even cannot start g-d any more. see reproducer

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


How reproducible:
always

Steps to Reproduce:
1.have one document in g-d
2.place that document into two collections
3.right click select those two collections only
4.go into collection dialog via +
5.click several times the first and the second collection there 
  
Actual results:
crash,g-d doesn't start any more

Expected results:
normal sane behaviour

Additional info:

version:
gnome-documents-3.8.1-1

We should not allow collections to be added to or removed from themselves.

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

I was able to reproduce (kinda) on gnome-documents-3.14.3-1.el7.x86_64. Gnome-Documents didn't crash for me, but I was able to add a collection to itself and it created an infinite loop of those collections. Similar issue except no crash. But as comment #2 says, collections probably shouldn't be able to be added or removed from themselves.

I have built gnome-documents-3.14.3-3.el7:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=11181410

This prevents nested collections and ensures that they are always flat. This is in line with what we did upstream in more recent versions.

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://rhn.redhat.com/errata/RHBA-2016-2458.html