I configured XRDP in Ubuntu 14. For the user who was created during the installation of the OS, everything works well. But if you create a new user, and try to connect through it, then - a gray screen. Tell me, what could be the reason? Which way to dig?

ps I'm new to Linux, I’ve already rummaged a lot of things, .xsession with the parameters for the created user created it didn’t give results. Log

Сценарий для ibus запущен из run_im. Сценарий для auto запущен из run_im. Сценарий для default запущен из run_im. init: Процесс at-spi2-registryd main завершен, повторный запуск init: Процесс at-spi2-registryd main завершен, повторный запуск init: Процесс at-spi2-registryd main завершен, повторный запуск init: Процесс at-spi2-registryd main завершен, повторный запуск init: Процесс at-spi2-registryd main завершен, повторный запуск init: Процесс at-spi2-registryd main завершен, повторный запуск init: Процесс at-spi2-registryd main завершен, повторный запуск init: Процесс at-spi2-registryd main завершен, повторный запуск init: Процесс at-spi2-registryd main завершен, повторный запуск init: Процесс at-spi2-registryd main завершен, повторный запуск init: at-spi2-registryd возрождается слишком быстро, остановлен init: Процесс unity-panel-service main (27894) завершен с кодом 1 init: Процесс indicator-printers main (27970) завершен с кодом 1 init: Процесс unity-settings-daemon main (27883) завершен с кодом 1 init: Процесс hud main (27887) завершен с кодом 1 init: Процесс gnome-session (Unity) main (27891) завершен с кодом 1 init: Процесс indicator-bluetooth main (27953) завершен с помощью сигнала TERM init: Процесс indicator-power main (27958) завершен с помощью сигнала TERM init: Процесс indicator-datetime main (27959) завершен с помощью сигнала TERM init: Процесс indicator-session main (27974) завершен с помощью сигнала TERM init: Процесс indicator-application main (27989) завершен с помощью сигнала TERM init: Disconnected from notified D-Bus bus Xsession: X session started for at Вс. июня 14 11:00:42 MSK 2015 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:narvel being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 Сценарий для ibus запущен из run_im. Сценарий для auto запущен из run_im. Сценарий для default запущен из run_im. Сценарий для ibus запущен из run_im. Сценарий для auto запущен из run_im. Сценарий для default запущен из run_im. gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 gnome-session[2640]: WARNING: software acceleration check failed: Дочерний процесс завершился с кодом 1 gnome-session[2640]: CRITICAL: We failed, but the fail whale is dead. Sorry.... Xsession: X session started for at Вс. июня 14 11:05:22 MSK 2015 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:narvel being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 Сценарий для ibus запущен из run_im. Сценарий для auto запущен из run_im. Сценарий для default запущен из run_im. Сценарий для ibus запущен из run_im. Сценарий для auto запущен из run_im. Сценарий для default запущен из run_im. gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 gnome-session[2847]: WARNING: software acceleration check failed: Дочерний процесс завершился с кодом 1 gnome-session[2847]: CRITICAL: We failed, but the fail whale is dead. Sorry.... 

 Xsession: X session started for at Вс. июня 14 10:57:17 MSK 2015 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:narvel being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 Сценарий для ibus запущен из run_im. Сценарий для auto запущен из run_im. Сценарий для default запущен из run_im. Сценарий для ibus запущен из run_im. Сценарий для auto запущен из run_im. Сценарий для default запущен из run_im. gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 gnome-session[26970]: WARNING: software acceleration check failed: Дочерний процесс завершился с кодом 1 gnome-session[26970]: CRITICAL: We failed, but the fail whale is dead. Sorry....

  • judging by the logs, you are trying to start a graphics session that is too demanding of video equipment. try something less expensive. for example, by default gnome uses compiz as a window manager , and it’s worth trying instead, for example, metacity . To do this, install the gnome-session-flashback package and select a session without compiz when logging in: screenshot - aleksandr barakin am

1 answer 1

only group membership comes to mind.

Try to add a new user to the same groups as the first one (except, of course, the sudo groups and the “personal” group whose name matches the user name).

you can find out which groups the user is in with

 $ groups имя_пользователя

add to group:

 $ sudo adduser имя_пользователя имя_группы

after adding a user to the group (s), the effect will not come immediately, but only after the completion of all processes running on behalf of this user.

  • Did as you wrote - it did not help, it still remained. Logi screwed - sanu0074