From: kalinin <kalinin@icv.org.ru> To: ALT Linux Community general discussions <community@lists.altlinux.org> Subject: [Comm] lxdm-binary поглощает 100% CPU, p6, LXDEsktop Date: Tue, 02 Apr 2013 11:25:47 +0400 Message-ID: <515A87FB.6030002@icv.org.ru> (raw) Приветствую уважаемое сообщество! После очередного обновления имеет место 100%-ая загрузка CPU процессом lxdm-binary. И так продолжается уже не один час... top - 11:03:38 up 18:23, 1 user, load average: 1.43, 1.80, 1.60 Tasks: 200 total, 2 running, 198 sleeping, 0 stopped, 0 zombie CPU: 58.1%us, 41.9%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 2054656K total, 433464K used, 1621192K free, 10100K buffers Swap: 4088504K total, 0K used, 4088504K free, 333412K cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5521 root 20 0 4360 2044 1668 R 95.4 0.1 1090:54 lxdm-binary 5611 root 20 0 37840 9480 4992 S 2.6 0.5 2:50.48 X 9715 mk 20 0 98.5M 10M 8516 S 1.0 0.5 0:00.33 lxpanel 9716 mk 20 0 115M 10M 8392 S 0.3 0.5 0:00.27 pcmanfm 9805 mk 20 0 9920 5104 2396 S 0.3 0.2 0:00.16 xterm 9816 mk 20 0 2340 1004 724 R 0.3 0.0 0:00.25 top 9858 mk 20 0 99804 9892 8020 S 0.3 0.5 0:00.21 leafpad 1 root 20 0 2004 652 564 S 0.0 0.0 0:00.76 init [mk@alt ~]$ uname -a Linux alt.localdomain 3.0.69-std-def-alt0.M60P.1 #1 SMP Thu Mar 14 23:57:55 UTC 2013 i686 GNU/Linux /var/log/messages: Apr 2 11:01:38 alt lxdm: Requested session: LXDE Apr 2 11:01:42 alt dbus[3814]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper) Apr 2 11:01:42 alt dbus[3814]: [system] Successfully activated service 'org.freedesktop.UDisks' Apr 2 11:01:43 alt gnome-keyring-daemon[9725]: couldn't communicate with already running daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Apr 2 11:01:43 alt gnome-keyring-daemon[9738]: couldn't communicate with already running daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Apr 2 11:01:43 alt gnome-keyring-daemon[9740]: couldn't communicate with already running daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Apr 2 11:01:44 alt gnome-keyring-daemon[9758]: GLib-GIO: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. Apr 2 11:01:44 alt gnome-keyring-daemon[9735]: GLib-GIO: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. Apr 2 11:01:45 alt gnome-keyring-daemon[9758]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files Apr 2 11:01:45 alt gnome-keyring-daemon[9758]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files Apr 2 11:01:45 alt gnome-keyring-daemon[9735]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files Apr 2 11:01:45 alt gnome-keyring-daemon[9761]: GLib-GIO: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. Apr 2 11:01:45 alt gnome-keyring-daemon[9761]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files Apr 2 11:01:45 alt gnome-keyring-daemon[9761]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files Apr 2 11:01:45 alt gnome-keyring-daemon[9764]: GLib-GIO: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. Apr 2 11:01:45 alt gnome-keyring-daemon[9764]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files Прошу помочь разобраться, в чем тут дело! -- С уважением, Калинин Максим
next reply other threads:[~2013-04-02 7:25 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-02 7:25 kalinin [this message] 2013-04-02 8:18 ` Alex Moskalenko 2013-04-02 10:26 ` Alex Moskalenko
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=515A87FB.6030002@icv.org.ru \ --to=kalinin@icv.org.ru \ --cc=community@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Community general discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 community community/ http://lore.altlinux.org/community \ mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com public-inbox-index community Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.community AGPL code for this site: git clone https://public-inbox.org/public-inbox.git