After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 676581 - errors reported in .xsession-errors
errors reported in .xsession-errors
Status: RESOLVED DUPLICATE of bug 676578
Product: gnome-settings-daemon
Classification: Core
Component: updates
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: Richard Hughes
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2012-05-22 16:51 UTC by darren
Modified: 2012-05-22 17:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description darren 2012-05-22 16:51:16 UTC 
I'm not accustomed to reporting errors, so my apologies for probably not getting this right....

I have been trying to keep my .xsession-errors file because it grew to be several gigabytes recently.  While watching it with tail -f, I noticed an error that requested that I report it.  So, here's a few lines from the .xsession-errors:

(nautilus:3274): GVFS-RemoteVolumeMonitor-WARNING **: g_proxy_mount_operation_handle_show_processes: No GMountOperation for id `3274:9'

(gnome-settings-daemon:3198): PackageKit-WARNING **: couldn't parse execption 'GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_5ftransaction_5ferror.Code4: GetDistroUpgrades not supported by backend', please report

(gnome-settings-daemon:3198): updates-plugin-WARNING **: failed to get upgrades: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_5ftransaction_5ferror.Code4: GetDistroUpgrades not supported by backend

(nautilus:3274): GVFS-RemoteVolumeMonitor-WARNING **: g_proxy_mount_operation_handle_show_processes: No GMountOperation for id `3274:9'
Comment 1 darren 2012-05-22 16:53:37 UTC 
I meant to say, "keeping my eye on my .xsession-errors....".
Comment 2 Bastien Nocera 2012-05-22 17:03:51 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 676578 ***