[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Weird warning from console-kit-daemon



Hi,

2012/5/8 Camaleón <noelamac@gmail.com>:
> On Mon, 07 May 2012 20:49:32 +0200, Sébastien Kalt wrote:
>> Is cgroup memory really disabled ?
>
> I can't tell, it doesn't seem to be so (I would have expected a
> message saying it has been disabled) though it should, or at least
> that's what the docs say :-?
cat /proc/cgroup will tell you which cgroup is enabled.

> 1/ Cgroup is still enabled for memory handling.
> 2/ The printed mesages have no relation with this cgroup thingy :-)
>
> Are the above errors coming up when you are locally logged or when
> running from a remote system or when some specific configuration is
> in place (e.g., it happens when running an X session or launching a
> GUI application but does not when no X server is in place)?
It happens when I log in an X session, and then a console, and/or
launch an application as another user with gksu, or su to another user
in an urxvt console.

But, weirdly, the messages stopped at 14h41 today, just after my last
synaptic update !

Here are the updated packages :

coreutils:amd64 (8.13-3.1, 8.13-3.2),
python-qt4:amd64 (4.9.1-1, 4.9.1-3),
ufraw-batch:amd64 (0.18-1.1+b1, 0.18-1.1+b2),
cpp:amd64 (4.6.3-5, 4.7.0-6),
gcc:amd64 (4.6.3-5, 4.7.0-6),
python-pyexiv2:amd64 (0.3.2-1+b1, 0.3.2-1+b2),
pciutils:amd64 (3.1.9-2, 3.1.9-3),
gdal-bin:amd64 (1.7.3-6+b4, 1.9.0-1),
libdbd-mysql-perl:amd64 (4.020-1+b1, 4.021-1),
libvorbisfile3:amd64 (1.3.2-1.2, 1.3.2-1.3),
lsb-base:amd64 (4.1+Debian2, 4.1+Debian3),
libvorbisenc2:amd64 (1.3.2-1.2, 1.3.2-1.3),
sox:amd64 (14.4.0-2, 14.4.0-3),
mysql-client:amd64 (5.1.62-1, 5.5.23-2),
libperl5.14:amd64 (5.14.2-9, 5.14.2-10),
python-gdal:amd64 (1.7.3-6+b4, 1.9.0-1),
grep:amd64 (2.11-3, 2.12-1),
libevent-2.0-5:amd64 (2.0.18-stable-1, 2.0.19-stable-1),
libvorbis0a:amd64 (1.3.2-1.2, 1.3.2-1.3),
libfolks-telepathy25:amd64 (0.6.8-2, 0.6.9-1),
perl-doc:amd64 (5.14.2-9, 5.14.2-10),
libio-socket-ssl-perl:amd64 (1.66-1, 1.67-1),
mysql-common:amd64 (5.1.62-1, 5.5.23-2),
lsb-release:amd64 (4.1+Debian2, 4.1+Debian3),
libogg0:amd64 (1.2.2~dfsg-1, 1.2.2~dfsg-1.1)
Remove: mysql-server-core-5.1:amd64 (5.1.62-1),
mysql-server-5.1:amd64 (5.1.62-1),
mysql-client-5.1:amd64 (5.1.62-1)

I'll confirm tomorrow that the messages have definitely disappeared ;)

Sebastien


Reply to: