"Pete Travis wrote:" > > --===============3837768215548578561== > Content-Type: multipart/alternative; boundary=001a1135e9d6f7fc3604ee3ba4d1 > > --001a1135e9d6f7fc3604ee3ba4d1 > Content-Type: text/plain; charset=ISO-8859-1 > > On Dec 23, 2013 1:22 PM, "David Highley" <dhighley@xxxxxxxxxxxxxxxxxxxxxxx> > wrote: > > > > "Pete Travis wrote:" > ... > > > `journalctl _UID=<user's uid>` might be a helpful filter here - similar > to > > > the now obsolete ~/.xsession-errors. > > > > OK, we have done this and included the output for a login attempt. The > > abrt tracker is indicating that this has been previously reported so > > maybe with some luck it will get corrected. In the mean time Cinnamon > > seems to work for an alternative. > > Dec 23 12:08:25 redwood gnome-session[3721]: OK > > Dec 23 12:09:03 redwood systemd[4669]: Failed to open private bus > connection: Failed to connect to socket > /run/user/1000/dbus/user_bus_socket: No such file or directory > > Dec 23 12:09:03 redwood systemd[4669]: Starting Default. > > Dec 23 12:09:03 redwood systemd[4669]: Reached target Default. > > Dec 23 12:09:03 redwood systemd[4669]: Startup finished in 6ms. > > Dec 23 12:09:05 redwood gnome-session[4676]: gnome-session[4676]: > WARNING: Could not parse desktop file gnome-do.desktop or it references a > not found TryExec binary > > Dec 23 12:09:05 redwood gnome-session[4676]: WARNING: Could not parse > desktop file gnome-do.desktop or it references a not found TryExec binary > > Dec 23 12:09:05 redwood gnome-session[4676]: gnome-session[4676]: > WARNING: Could not parse desktop file remmina-applet.desktop or it > references a not found TryExec binary > > Dec 23 12:09:05 redwood gnome-session[4676]: WARNING: Could not parse > desktop file remmina-applet.desktop or it references a not found TryExec > binary > > This bit looks ripe for investigation. Do you have these .desktop files, > and do they contain correct references to present and functional binaries? > > > > > Dec 23 12:09:06 redwood gnome-session[4676]: (gnome-shell:4986): > Gjs-WARNING **: JS ERROR: Exception in callback for signal: > sessions-loaded: Error: Argument 'text' (type utf8) may not be null > > ...snip apparent traceback > > This is suspicious as well. Incompatible extension, perhaps? > > > snip remainder, gnome-shell didn't open so dependents fail too. > > Have you tried with a new user? If that works, move around your .files to > isolate the culprit. OK, I did find those and some old gnome2 stuff. So I went the drastic route and wiped out all files and directories with gnome in the name. Still get the same results. > > --Pete > > --001a1135e9d6f7fc3604ee3ba4d1 > Content-Type: text/html; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > > <p dir=3D"ltr"><br> > On Dec 23, 2013 1:22 PM, "David Highley" <<a href=3D"mailto:dh= > ighley@xxxxxxxxxxxxxxxxxxxxxxx">dhighley@xxxxxxxxxxxxxxxxxxxxxxx</a>> wr= > ote:<br> > ><br> > > "Pete Travis wrote:"<br> > ...<br> > > > `journalctl _UID=3D<user's uid>` might be a helpful fil= > ter here - similar to<br> > > > the now obsolete ~/.xsession-errors.<br> > ><br> > > OK, we have done this and included the output for a login attempt. The= > <br> > > abrt tracker is indicating that this has been previously reported so<b= > r> > > maybe with some luck it will get corrected. In the mean time Cinnamon<= > br> > > seems to work for an alternative.<br> > > Dec 23 12:08:25 redwood gnome-session[3721]: OK<br> > > Dec 23 12:09:03 redwood systemd[4669]: Failed to open private bus conn= > ection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No= > such file or directory<br> > > Dec 23 12:09:03 redwood systemd[4669]: Starting Default.<br> > > Dec 23 12:09:03 redwood systemd[4669]: Reached target Default.<br> > > Dec 23 12:09:03 redwood systemd[4669]: Startup finished in 6ms.<br> > > Dec 23 12:09:05 redwood gnome-session[4676]: gnome-session[4676]: WARN= > ING: Could not parse desktop file gnome-do.desktop or it references a not f= > ound TryExec binary<br> > > Dec 23 12:09:05 redwood gnome-session[4676]: WARNING: Could not parse = > desktop file gnome-do.desktop or it references a not found TryExec binary<b= > r> > > Dec 23 12:09:05 redwood gnome-session[4676]: gnome-session[4676]: WARN= > ING: Could not parse desktop file remmina-applet.desktop or it references a= > not found TryExec binary<br> > > Dec 23 12:09:05 redwood gnome-session[4676]: WARNING: Could not parse = > desktop file remmina-applet.desktop or it references a not found TryExec bi= > nary</p> > <p dir=3D"ltr">This bit looks ripe for investigation.=A0 Do you have these = > .desktop files, and do they contain correct references to present and funct= > ional binaries?</p> > <p dir=3D"ltr">> <br> > > Dec 23 12:09:06 redwood gnome-session[4676]: (gnome-shell:4986): Gjs-W= > ARNING **: JS ERROR: Exception in callback for signal: sessions-loaded: Err= > or: Argument 'text' (type utf8) may not be null<br> > > ...snip apparent traceback</p> > <p dir=3D"ltr">This is suspicious as well. Incompatible extension, perhaps?= > </p> > <p dir=3D"ltr">> snip remainder, gnome-shell didn't open so dependen= > ts fail too.<br></p> > <p dir=3D"ltr">Have you tried with a new user? If that works, move around y= > our .files to isolate the culprit.</p> > <p dir=3D"ltr">--Pete</p> > > --001a1135e9d6f7fc3604ee3ba4d1-- > > --===============3837768215548578561== > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: base64 > Content-Disposition: inline > > LS0gCnVzZXJzIG1haWxpbmcgbGlzdAp1c2Vyc0BsaXN0cy5mZWRvcmFwcm9qZWN0Lm9yZwpUbyB1 > bnN1YnNjcmliZSBvciBjaGFuZ2Ugc3Vic2NyaXB0aW9uIG9wdGlvbnM6Cmh0dHBzOi8vYWRtaW4u > ZmVkb3JhcHJvamVjdC5vcmcvbWFpbG1hbi9saXN0aW5mby91c2VycwpGZWRvcmEgQ29kZSBvZiBD > b25kdWN0OiBodHRwOi8vZmVkb3JhcHJvamVjdC5vcmcvY29kZS1vZi1jb25kdWN0Ckd1aWRlbGlu > ZXM6IGh0dHA6Ly9mZWRvcmFwcm9qZWN0Lm9yZy93aWtpL01haWxpbmdfbGlzdF9ndWlkZWxpbmVz > CkhhdmUgYSBxdWVzdGlvbj8gQXNrIGF3YXk6IGh0dHA6Ly9hc2suZmVkb3JhcHJvamVjdC5vcmcK > > --===============3837768215548578561==-- > -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
