Bug 1274205

Summary:	gnome-session falls down - Glibc critical error
Product:	[Fedora] Fedora	Reporter:	Robert Balejik <r.balejik1>
Component:	gnome-session	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	22	CC:	jmccann, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 19:20: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 Robert Balejik 2015-10-22 09:05:42 UTC

my gnome-session is falling - restarting after this error (happened ~10 times over last 2-3 days

GLib-CRITICAL: g_child_watch_add_full: assertion 'pid > 0' failed

my is HW Lenovo G 500s - fedora workstation 22 gnome.

error reproduction - have this version of glibc installed:
glibc-2.21-8.fc22.x86_64

Comment 1 Robert Balejik 2015-10-23 12:52:23 UTC

I reinstalled glibc but happende again and i noticed this error before the glibc error everytime: Re: 
[pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory.

Comment 2 Fedora End Of Life 2016-07-19 19:20:33 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.