Rudinei Dias
2013-Jan-08 16:41 UTC
[CentOS] After performing a reboot in VM (Virtualbox), log user on gnome not display the desktop.
After performing a reboot in VM (Virtualbox) which had been stopped, the User logs in but does not display the desktop leaving only the background image. The services are all active, can access and use the VM via ssh, but the Desktop died. I do not know where to begin to solve this problem. Any idea? Thanks ------------------------------------------------------------- Rudinei Dias
Rudinei Dias
2013-Jan-09 11:43 UTC
[CentOS] After performing a reboot in VM (Virtualbox), log user on gnome not display the desktop.
Jan 8 16:02:38 oracletest gnome-session[1854]: WARNING: Failed to send buffer Jan 8 16:02:38 oracletest gnome-session[1854]: WARNING: Failed to send buffer These errors was found in messages when i try to log. ------------------------------------------------------------- Rudinei Dias ---------- Forwarded message ---------- From: Rudinei Dias <rudinei.dias at gmail.com> Date: 2013/1/8 Subject: After performing a reboot in VM (Virtualbox), log user on gnome not display the desktop. To: centos at centos.org After performing a reboot in VM (Virtualbox) which had been stopped, the User logs in but does not display the desktop leaving only the background image. The services are all active, can access and use the VM via ssh, but the Desktop died. I do not know where to begin to solve this problem. Any idea? Thanks ------------------------------------------------------------- Rudinei Dias
Liam O'Toole
2013-Jan-09 11:51 UTC
[CentOS] After performing a reboot in VM (Virtualbox), log user on gnome not display the desktop.
On 2013-01-08, Rudinei Dias <rudinei.dias at gmail.com> wrote:> After performing a reboot in VM (Virtualbox) which had been stopped, the > User logs in but does not display the desktop leaving only the background > image. > The services are all active, can access and use the VM via ssh, but the > Desktop died. > I do not know where to begin to solve this problem. > Any idea? >The file .xsession-errors in the user's home directory is a good place to start. -- Liam