Bug 1073345

Summary: Search for Open Files produce Glib-CRITICAL asserts only sometimes
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Pelka <tpelka>
Component: gnome-system-monitorAssignee: David King <dking>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: low    
Version: 7.0CC: vhumpa
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnome-system-monitor-3.14.1-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 07:23:33 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 2014-03-06 09:02:43 UTC
Description of problem:
Search for Open Files producing Glib-CRITICAL asserts: g_regex_match_full: assertion `regex != NULL' failed

This is expected since I'm searching for empty string/regexp, but it is happening just sometimes

Version-Release number of selected component (if applicable):
gnome-system-monitor-3.8.2.1-5.el7

How reproducible:
100%

Steps to Reproduce:
1. open g-s-m from cmd line, open Search for Open Files dialog
2. leave the search filed empty and hit Find
3. watch cmd line - there are lot of Glib-CRITICAL asserts dealing with regex
4. close Search for Open Files dialog
5. open it again
6. repeat step 2.

Actual results:
No more asserts full list of opened files displayed in Search results.

Expected results:
I would expect coherent behaviour

Additional info:

Comment 3 David King 2015-05-15 12:34:34 UTC
This does not seem to be a problem in the version included in the desktop rebase.

Comment 6 errata-xmlrpc 2015-11-19 07:23:33 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://rhn.redhat.com/errata/RHBA-2015-2215.html