Ubuntu GNOME desktop disappearing on keyboard input

Discussions about using Linux guests in VirtualBox.
Post Reply
mjf
Posts: 25
Joined: 7. Aug 2014, 14:36

Ubuntu GNOME desktop disappearing on keyboard input

Post by mjf »

Hello,

I'm running Ubuntu GNOME 16.10 in VirtualBox 5.1.26 on a Windows 7 64-bit host.

If I don't use the guest for a while, any keyboard input will cause the desktop to disappear and tty1 text console to show up. I then have to enter Ctrl-Alt-F2 and Ctrl-Alt-F1 to make the desktop reappear.

How can I avoid this behavior?

Thanks, mjf
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Ubuntu GNOME desktop disappearing on keyboard input

Post by socratis »

Stop any screen savers (disable them) and make sure that the power settings never allow the VM to go to power savings mode. See if that helps...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
mjf
Posts: 25
Joined: 7. Aug 2014, 14:36

Re: Ubuntu GNOME desktop disappearing on keyboard input

Post by mjf »

Thanks for your advice.

I disabled all screen savers, but the problem still occurs. When I have not used the keyboard for a while, the first keystroke will take me from the desktop to a text console. Whether I have been using the mouse before does not matter.

Here are the entries to /var/log/syslog

Code: Select all

Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (**) Option "fd" "43"
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (**) Option "fd" "41"
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (**) Option "fd" "44"
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (**) Option "fd" "42"
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (**) Option "fd" "45"
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (**) Option "fd" "50"
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (**) Option "fd" "49"
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got pause for 13:65
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got pause for 13:70
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got pause for 13:64
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got pause for 13:67
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got pause for 13:69
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got pause for 13:68
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got pause for 226:0
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got pause for 13:66
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got resume for 13:65
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got resume for 13:70
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got resume for 13:64
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got resume for 13:67
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got resume for 13:69
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got resume for 13:68
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got resume for 226:0
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): EDID vendor "VBX", prod id 0
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): DDCModeFromDetailedTiming: 1920x1136 Warning: We only handle separate sync.
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): Using hsync ranges from config file
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): Using vrefresh ranges from config file
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'Power Button', /dev/input/event0 is tagged by udev as: Keyboard
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'Power Button', /dev/input/event0 is a keyboard
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'Sleep Button', /dev/input/event1 is tagged by udev as: Keyboard
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'Sleep Button', /dev/input/event1 is a keyboard
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'Video Bus', /dev/input/event3 is tagged by udev as: Keyboard
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'Video Bus', /dev/input/event3 is a keyboard
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'VirtualBox mouse integration', /dev/input/event6 is tagged by udev as: Mouse
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'VirtualBox mouse integration', /dev/input/event6 is a pointer caps
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'VirtualBox USB Tablet', /dev/input/event5 is tagged by udev as: Mouse
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'VirtualBox USB Tablet', /dev/input/event5 is a pointer caps
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'ImExPS/2 Generic Explorer Mouse', /dev/input/event4 is tagged by udev as: Mouse
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'ImExPS/2 Generic Explorer Mouse', /dev/input/event4 is a pointer caps
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): EDID vendor "VBX", prod id 0
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): DDCModeFromDetailedTiming: 1920x1136 Warning: We only handle separate sync.
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): Using hsync ranges from config file
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): Using vrefresh ranges from config file
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) systemd-logind: got resume for 13:66
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'AT Translated Set 2 keyboard', /dev/input/event2 is tagged by udev as: Keyboard
Oct  9 22:03:03 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) input device 'AT Translated Set 2 keyboard', /dev/input/event2 is a keyboard
Oct  9 22:03:04 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): EDID vendor "VBX", prod id 0
Oct  9 22:03:04 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): DDCModeFromDetailedTiming: 1920x1136 Warning: We only handle separate sync.
Oct  9 22:03:04 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): Using hsync ranges from config file
Oct  9 22:03:04 Yakkety64 /usr/lib/gdm3/gdm-x-session[1543]: (II) modeset(0): Using vrefresh ranges from config file
Oct  9 22:03:08 Yakkety64 gnome-terminal-[3963]: Allocating size to GtkBox 0x5599f9a357b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Ubuntu GNOME desktop disappearing on keyboard input

Post by socratis »

I really have no clue, but I have the feeling that this thread belongs to the "Linux Guests" as opposed to "Windows Hosts". Maybe someone in there will have a better understanding of the messages...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply