cannot report error

JD jd1008 at gmail.com
Mon Dec 31 05:56:43 UTC 2012


On 12/30/2012 08:08 PM, Thufir Hawat wrote:
> On Sun, 30 Dec 2012 18:24:40 -0800, JD wrote:
>
>> Also look in ~/.xsession-errors  file
> aha!
>
> thufir at dur:~$
> thufir at dur:~$ cat .xsession-errors
> xfce4-session-Message: ssh-agent is already running
>
> (xfdesktop:28250): GLib-GIO-CRITICAL **: g_file_get_path: assertion
> `G_IS_FILE (file)' failed
>
> (polkit-gnome-authentication-agent-1:28300): GLib-CRITICAL **:
> g_variant_new_string: assertion `string != NULL' failed
>
> (polkit-gnome-authentication-agent-1:28300): polkit-gnome-1-WARNING **:
> Failed to register client:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
> ** Message: applet now removed from the notification area
> ** Message: using fallback from indicator to GtkStatusIcon
> WARNING: gnome-keyring:: couldn't connect to: /run/user/thufir/keyring-
> Vy5eBl/pkcs11: No such file or directory
>
> (Pidgin:28256): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child
> that doesn't believe we're it's parent.
>
> (Pidgin:28256): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child
> that doesn't believe we're it's parent.
>
> (Pidgin:28256): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child
> that doesn't believe we're it's parent.
>
> (Pidgin:28256): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child
> that doesn't believe we're it's parent.
> WARNING: gnome-keyring:: couldn't connect to: /run/user/thufir/keyring-
> Vy5eBl/pkcs11: No such file or directory
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> news.pan.NZB was not provided by any .service files
> thufir at dur:~$
>
>
> I'm not sure what the original error is, but that warning about the
> keyring seems crucial, because that might be why I can't report the
> error.  The password doesn't match because it couldn't connect to the
> keyring?
>
> googling this keyring thing.
>
> thanks,
>
> Thufir
>
>
I believe it would be sufficient to send those contents of .xsession-error
to the ubuntu dev team mailing list (which you might have already 
subscribed to).

Cheers,

JD





More information about the ubuntu-users mailing list