Bug 1079752

Summary: (xfdesktop:1224): GLib-GIO-CRITICAL **: g_file_get_path: assertion 'G_IS_FILE (file)' failed" in ~/.xsession-errirs
Product: [Fedora] Fedora Reporter: Peter H. Jones <jones.peter.busi>
Component: xfdesktopAssignee: Kevin Fenzi <kevin>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: kevin, nonamedotc
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: 2014-03-28 16:57:57 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:
Attachments:
Description Flags
.xsession-errors none

Description Peter H. Jones 2014-03-23 17:37:28 UTC
Created attachment 877899 [details]
.xsession-errors

Description of problem:
Messages in ~/.xsession-errors

Version-Release number of selected component (if applicable):
xfdesktop-4.10.2-2.fc20.x86_64

How reproducible:
Discovered during normal running

Actual results:
.xsession-error messages

Expected results:
No error messages

Additional info:
I noticed serveral different types of error messages in ~/.xsession-errors. Does this indicate several bugs, or just one underlying problem?

Comment 1 Kevin Fenzi 2014-03-24 17:46:43 UTC
So, ~/.xsession-errors is simply the stdout/stderr from your lightdm session. 

I don't think either of these are a problem aside from being messy.

I suppose we could report them upstream to see if they could get cleaned up... would you like to do that? Or would you like me to do so?

Comment 2 Peter H. Jones 2014-03-24 21:14:37 UTC
I would prefer you to report this problem upstream, 1) because you probably do that more often than I, and would have an account set up, and 2) you are in a better position to look through other bug reports and tests and see if the messages are ocurring there. Thanks for asking.