Ed Greshko ha scrito il 10/09/2014 alle 16:01:
On 09/10/14 19:17, antonio wrote:
Gdm Gnome: it is a pretty standard installation....how do I kill X when ssh-ing??
Tnx again (I have to wait until problem is out again)
Well, assuming you can ssh into that system, when you do the "ps -eaf | grep X" and the X server is running you will get a line similar to
root 1365 1320 1 Sep03 tty1 03:11:27 /usr/bin/X :0 vt1 -background none -nolisten tcp -seat seat0 -auth /var/run/kdm/A:0-xBMk9b
you can then just do a "sudo kill -9 1365" replacing the 1365 with the number you get.
Now with all that said.....
I just noticed the following in you failed.boot file....
set 10 06:00:51 Fujiantonio gdm[741]: GdmLocalDisplayFactory: Failed to issue method call: È stato raggiunto il timeout
This then led me to find.....
https://bugzilla.redhat.com/show_bug.cgi?id=1018902
Which sounds very similar to what you're reporting.
I joined that bug, as I have same problems of comment #12.
In particular I get:
systemd[1] bus_get_selinux_context failed: resource temporarily unavailable
systemd: Failed to get caller's security context on: resource
temporarily unavailable.
Now I switched Selinux to permissive to see if it is connected
--
Antonio M
Skype: amontag52
Linux Fedora F20 (Heisenbug)
on Fujitsu Lifebook A512
http://lugsaronno.altervista.org
http://www.campingmonterosa.com
--
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
