Advertisement
Guest User

0-greeter.log

a guest
Apr 21st, 2013
122
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.74 KB | None | 0 0
  1. ** (<unknown>:3114): DEBUG: Client registered with session manager: /org/gnome/SessionManager/Client1
  2. ПреЎупрежЎеМОе ЌеМеЎжера ПкПМ: Не уЎалПсь прПчОтать сПхраМёММый файл сеаМса «/var/lib/gdm3/.config/metacity/sessions/10b860d363b9417a96136652721154699100000031100006.ms»: Не уЎалПсь Пткрыть файл «/var/lib/gdm3/.config/metacity/sessions/10b860d363b9417a96136652721154699100000031100006.ms»: Нет такПгП файла ОлО каталПга
  3. ** (process:3127): DEBUG: Greeter session pid=3127 display=:0.0 xauthority=/var/run/gdm3/auth-for-Debian-gdm-8qmA8m/database
  4.  
  5. (polkit-gnome-authentication-agent-1:3128): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'
  6.  
  7. (polkit-gnome-authentication-agent-1:3128): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
  8. gdm-simple-greeter[3127]: Gtk-WARNING: /scratch/build-area/gtk+2.0-2.20.1/gtk/gtkwidget.c:5628: widget not within a GtkWindow
  9. ПреЎупрежЎеМОе ЌеМеЎжера ПкПМ: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x120002b (ОкМП Ð)
  10. ПреЎупрежЎеМОе ЌеМеЎжера ПкПМ: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
  11. ПреЎупрежЎеМОе ЌеМеЎжера ПкПМ: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x120002b (ОкМП Ð)
  12. ПреЎупрежЎеМОе ЌеМеЎжера ПкПМ: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
  13. ПреЎупрежЎеМОе ЌеМеЎжера ПкПМ: CurrentTime used to choose focus window; focus window may not be correct.
  14. ПреЎупрежЎеМОе ЌеМеЎжера ПкПМ: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
  15.  
  16. ** (gnome-power-manager:3126): WARNING **: Failed to send buffer
  17.  
  18. (gnome-settings-daemon:3117): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
  19.  
  20. (gnome-settings-daemon:3117): atk-bridge-WARNING **: IOR not set.
  21.  
  22. (gnome-power-manager:3126): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
  23.  
  24. (gnome-power-manager:3126): atk-bridge-WARNING **: IOR not set.
  25.  
  26. (gnome-settings-daemon:3117): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
  27.  
  28. (gnome-settings-daemon:3117): atk-bridge-WARNING **: IOR not set.
  29.  
  30. (gnome-power-manager:3126): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
  31.  
  32. (gnome-power-manager:3126): atk-bridge-WARNING **: IOR not set.
  33.  
  34. (gnome-settings-daemon:3117): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
  35.  
  36. (gnome-settings-daemon:3117): atk-bridge-WARNING **: IOR not set.
  37.  
  38. (gnome-settings-daemon:3117): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
  39.  
  40. (gnome-settings-daemon:3117): atk-bridge-WARNING **: IOR not set.
  41.  
  42. (gnome-settings-daemon:3117): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
  43.  
  44. (gnome-settings-daemon:3117): atk-bridge-WARNING **: IOR not set.
  45.  
  46. (gnome-settings-daemon:3117): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
  47.  
  48. (gnome-settings-daemon:3117): atk-bridge-WARNING **: IOR not set.
  49.  
  50. (gnome-settings-daemon:3117): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
  51.  
  52. (gnome-settings-daemon:3117): atk-bridge-WARNING **: IOR not set.
  53. gnome-settings-daemon: Fatal IO error 11 (Ресурс вреЌеММП МеЎПступеМ) on X server :0.0.
  54. gnome-settings-daemon: Fatal IO error 104 (СПеЎОМеМОе сбрПшеМП ЎругПй стПрПМПй) on X server :0.0.
  55. polkit-gnome-authentication-agent-1: Fatal IO error 11 (Ресурс вреЌеММП МеЎПступеМ) on X server :0.0.
  56. The application 'polkit-gnome-authentication-agent-1' lost its connection to the display :0.0;
  57. most likely the X server was shut down or you killed/destroyed
  58. the application.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement