Pete Travis wrote:
--===8084609375064345886==
Content-Type: multipart/alternative; boundary=001a11c36c50d0f15c04ee3edcaa
--001a11c36c50d0f15c04ee3edcaa
Content-Type: text/plain; charset=ISO-8859-1
On Dec 23, 2013 4:47 PM, David Highley dhigh...@highley-recommended.com
On Dec 24, 2013 1:34 PM, David Highley dhigh...@highley-recommended.com
wrote:
( I wrote )
And with the new user account? This is a crucial test, because tweaking
your config files and troubleshooting the display stack are very
different.
(Reply)
Bingo, seems to be old scruff somewhere in
On Dec 22, 2013 2:49 PM, David Highley dhigh...@highley-recommended.com
wrote:
user for login.
We see by using journalctl -f | less
That the shell fails to register before a timeout occurs and that there
is a kernal pool segfault and a core dump. We have not been able to
determine if they
Pete Travis wrote:
--===6465155735344206330==
Content-Type: multipart/alternative; boundary=001a11c38892b4deff04ee38beb6
--001a11c38892b4deff04ee38beb6
Content-Type: text/plain; charset=ISO-8859-1
On Dec 22, 2013 2:49 PM, David Highley dhigh...@highley-recommended.com
On Dec 23, 2013 1:22 PM, David Highley dhigh...@highley-recommended.com
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
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 dhigh...@highley-recommended.com
On Dec 23, 2013 4:47 PM, David Highley dhigh...@highley-recommended.com
wrote:
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.
And with the new user account? This is a
David Highley wrote:
Mateusz Marzantowicz wrote:
On 21.12.2013 20:40, David Highley wrote:
We upgraded a test system to Fedora 20 using the fedup process. There
were 60 packages that were left from Fedora 19 after the upgrade that
were subsequently fixed by doing a yum
On 22.12.2013 22:49, David Highley wrote:
David Highley wrote:
Mateusz Marzantowicz wrote:
On 21.12.2013 20:40, David Highley wrote:
We upgraded a test system to Fedora 20 using the fedup process. There
were 60 packages that were left from Fedora 19 after the upgrade that
were subsequently
We upgraded a test system to Fedora 20 using the fedup process. There
were 60 packages that were left from Fedora 19 after the upgrade that
were subsequently fixed by doing a yum distro-sync. Since the upgrade we
are not able to login into a Gnome session. We select the user in the
greater and it
On 21.12.2013 20:40, David Highley wrote:
We upgraded a test system to Fedora 20 using the fedup process. There
were 60 packages that were left from Fedora 19 after the upgrade that
were subsequently fixed by doing a yum distro-sync. Since the upgrade we
are not able to login into a Gnome
Mateusz Marzantowicz wrote:
On 21.12.2013 20:40, David Highley wrote:
We upgraded a test system to Fedora 20 using the fedup process. There
were 60 packages that were left from Fedora 19 after the upgrade that
were subsequently fixed by doing a yum distro-sync. Since the upgrade we
are
On 21.12.2013 22:50, David Highley wrote:
Mateusz Marzantowicz wrote:
On 21.12.2013 20:40, David Highley wrote:
We upgraded a test system to Fedora 20 using the fedup process. There
were 60 packages that were left from Fedora 19 after the upgrade that
were subsequently fixed by doing a yum
13 matches
Mail list logo
