Does anybody know who the official maintainer of this package is? I am
willing to work on getting the patch included in the kernel if this
approach is acceptable to the ConsoleKit team, but I don't want to
bother with the kernel side of things unless ConsoleKit will incorporate
the changes also.
On Mon, 2009-04-06 at 13:50 +, micah4 wrote:
Does anybody know who the official maintainer of this package is? I am
willing to work on getting the patch included in the kernel if this
approach is acceptable to the ConsoleKit team, but I don't want to
bother with the kernel side of things
Thanks very much micah4. Both for broadening my view on what is a bug and for
your analysis and patch. I would be very much pleased if you push your patch
either directly to the kernel developers or through the ConsoleKit maintainer.
Hope you have the time.
(PS: I believe a lot more people
Hi micah,
Thanks for working on this. I would recommend that you first try
and get your kernel patch included in Linus' tree. Once that is available
we can work on including your patch in to consolekit.
I'm not at all well placed to review the kernel patch, so taking it to
the kernel developers
A quick look at the code shows that the threads are created so that they
can sleep on an ioctl to the virtual consoles, with one thread for each
(possible) virtual console which waits for the VC to become active. The
threads were probably created so that the application could be released
without
@micah4:
This is also what the Red Hat bugtracker (
https://bugzilla.redhat.com/show_bug.cgi?id=457845 ) says:
Comment #1 From Matthias Clasen 2008-08-05 18:28:43 EDT ---
This is not a bug, it is working around the limitiations of the linux vt
system.
These are threads, one for each vt,
Here is a patch, one for ConsoleKit and one for the kernel that will get
rid of the numerous threads. Adds a new ioctl to the VT system. It's
kludgy, but it is a straightforward solution which works AFAICT (though
I don't really know how to test whether console-kit-daemon is working
properly).
Here is the patch for the kernel.
** Attachment added: Kernel patch to make ConsoleKit nicer.
http://launchpadlibrarian.net/24316072/kernel.patch
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member
Sorry, last kernel patch missed an include file. Use this patch instead.
** Attachment added: kernel.patch
http://launchpadlibrarian.net/24316171/kernel.patch
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you
60 useless threads may not use much more memory or consume much more cpu
on a modern machine. They do, however, use a significant portion of my
resources.
They consume almost 30% of my listing when I run ps -eLf and nearly 50%
of my listing when I run pstree -p. They consume keystrokes when I
On an Xubuntu Intrepid server, just found console-kit-daemon taking
96-100% of CPU. Yes, this is not the same bug as this report is. But it
does seem like including this package in a default install is bad
engineering.
--
console-kit-deamon spawns too many threads
Rock on, Vlad!
I'd like to take a look at your utility. It may be of use in other cases.
Would you post the source code, or a link to where the code may be found?
Thanks.
Loye Young
On Tue, Feb 24, 2009 at 3:47 PM, Vladimir wrote:
After seeing that the discussion goes nowhere and nobody in
@Vladimir:
Now what? Is your system more responsive? Do you have significantly more free
RAM? Do you get 2FPS more in some benchmark?
What is the BENEFIT?
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a
2 mehthurt
Yes, even better. :-)
2 Loye Young (source enclosed)
The source:
/* console-kit-daemon */
int main() {
return 0;
}
/* console-kit-daemon END*/
Cut and paste into file console-kit-daemon.c and do the following:
gcc -Wall -o console-kit-daemon console-kit-daemon.c
Vladamir is exactly right. Kruft needs to stay off our systems.
Besides, Microsoft and Macrovision have patents on bloatware, and they would
be pissed if we infringed on their intellectual property.
Happy Trails,
Loye Young
Isaac Young Computer Company
Laredo, Texas
http://archive.iycc.net
On
After seeing that the discussion goes nowhere and nobody in charge is
willing to do anything about this problem, I chose my own solution. It
is ugly, dirty, but it works for now.
I wrote in C program with only one instruction: exit. I have replaced
the huge console-kit-daemon in /usr/sbin with
Why not using:
#!/bin/sh
exit 0
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: consolekit
Status: Confirmed = Invalid
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: Red Hat Bugzilla #457845
https://bugzilla.redhat.com/show_bug.cgi?id=457845
** Also affects: consolekit (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=457845
Importance: Unknown
Status: Unknown
--
console-kit-deamon spawns too many threads
** Changed in: consolekit (Fedora)
Status: Unknown = Invalid
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
If it can't get its thread count under control I'd just as soon uninstall it,
it seems however just about everything on the desktop depends on it for
something though.
On my system, console-kit-daemon with all its threads takes about 2MB of
RAM (RSS in ps aux).
This has near *zero* impact on
@IronStorm
everything on the desktop
depends on it for something
off-topic rant
Yet another example of rampant dependency inflation. I've complained
about this before in a variety of contexts. Somehow, the entire open
source developer community needs to get a handle on it. It's a big
problem for
WTF is this consoleKit thing for, why the heck does it need 60 dormant
threads, and why do 50 odd packages depend on it?
http://people.freedesktop.org/~mccann/doc/ConsoleKit/ConsoleKit.html#id2565344
-- that's helpful!
Seriously, I've been using RedHat 5.2 and have never had need of
whatever
Seriously, I've been using RedHat 5.2 and have never had need of
whatever fast-user-switching or seat counting this thing provides...
clearly I'm up way past my bed time too... that should read using Linux
since RH5.2... haha
--
console-kit-deamon spawns too many threads
** Changed in: consolekit (Ubuntu)
Status: New = Triaged
** Also affects: consolekit via
https://bugs.freedesktop.org/show_bug.cgi?id=17720
Importance: Unknown
Status: Unknown
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received
** Changed in: consolekit
Status: Unknown = Confirmed
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Right.
https://bugs.freedesktop.org/show_bug.cgi?id=17720
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
By now, everybody should have come to the conclusion that there is in
fact nobody here who actually has the required know-how CKD to figure
out of what's going on here; all we have are 2 possibly broken patches
and plenty of vague assumptions.
I still say: if you're really that concerned, you
Sadly, the patch blocks shutdown and restart through hal (at least that's how I
interpreted the errors).
So DON'T USE IT.
Actually, that's kind of mistery to me: how can it block the shutdown?
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received
Alex, thanks for your patch. But how do we implement it? A little
description would certainly help.
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
How does who implement what? Inotify? Detection of sysfs mounted? BSD?
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It still reserves some stack (65k?), causes unnecessary context switches and
takes some attention of the scheduler.
It's still bloat to request a resource which is NEVER used (a thread to monitor
console 58? What for?!).
And BTW, why is FreeBSD configured to the number of active consoles?
Could
Mr. Demou, I don't have any more knowledge on this than any other
reporter, or you. I don't mind at all if the report gets closed with an
explanation on why this is a feature, not a bug. Actually that would be
a great thing as it would leave a findable explanation for people who in
the future
Lynoure, I understand your questions and desire for explanations and
that's why I've created a question from this bug
regarding:
If a bug report does not define what the problem is with enough clarity, they
are normally just plain incomplete.
...from my point of view and after reading
Nick,
if you don't understand what is the problem, maybe you should go work
for Microsoft. They have same philosophy: Wasted resources? So what? Go
buy better machine. We don't care.
So this the problem. Linux used to be synonym for small, efficient.
Thanks to people like yourself it is no
Vladimir, our difference is not whether I care about wasted resources (I
do) but whether I see any worthy evidence of wasted resources (I don't).
But I'm afraid that at this point of time you probably wouldn't believe
me if I told you that the sky is blue so I had to google for a few
minutes in
Lynoure Stefan, please take the time to explain to us what the problem
with console-kit-deamon is, because until now everybody else HAS NOT
(and it doesn't help that originally some of the posters were chasing a
completely different problem that wasn't even there). That's the reason
I've marked
Mr. Demou, if you are, as you said, not an expert and not sure if
spawning 60 threads is normal and correct for console-kit-daemon in
Ubuntu or not, please don't mark the bug invalid but consider Incomplete
as a better choice. Maybe even consider finding out these things from
the developers or
Spawning 60 threads when no more than 5 will be used shoud be considered
a bug. Plain and simple.
** Changed in: consolekit (Ubuntu)
Status: Invalid = New
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you
** Changed in: consolekit (Ubuntu)
Importance: Undecided = Low
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Description changed:
since upgrading to gutsy beta htop shows about fifty processes like the
following
pid user pri ni virt res shr s cpu% mem% time+ command
7582 root 23 0 7456 2016 1336 s 0.0 0.2 0:00.00 /usr/sbin/console-kit-deamon
- that do not show up in top or ps. it also
This bug report seems more like asking:
1) Is it normal for Console-Kit-Daemon to spawn ~60 threads
2) If htop reports 0.2% usage per thread does this mean that those 60
threads eat-up 0.2%*60=12% of RAM?
I've tried to convert it to a Question but launchpad returned an error
--
nobody has shed some light as to what is wrong with console-kit-deamon
spawning 60 threads. Until we can't define what's wrong with it this
can't be considered a bug.
Of course there were some statements regarding system resources that get
eaten up by those threads but except from memory they
You should file a bug on the ConsoleKit bugtracker and post your patch
there: https://bugs.freedesktop.org/enter_bug.cgi?product=ConsoleKit
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
I have prepared a simple patch (only basic functionality, no integration
in g_object style programming, parameter passing with a global variable)
to limit the number for MAX_CONSOLE consolekit can use. It is more a
feature request than a solution.
You can pass a parameter --limit-vts N or -l N to
Martin, could you please proof that the 60 console-kit-threads don't
slow down a computer? Please consider slower computers with low
ressources as well.
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a
I have no idea why you are all so agitated by this. If the console-kit-
daemon developers think that it makes sense for it to spawn ~60 threads,
then so be it! It may be alright to ask for the reason behind this and
to suggest to reduce the thread count, but _please_ don't snivel such
nonsense as
(i am the original reporter) original bug report was, that i thought
htop shows incorrect data (as ps and top did not show the processes). it
became clear, that this is not the case, as the processes ARE running.
htop is (at least a little bit) unusable showing that many spam threads.
but one can
I've written an email to the author of ConsoleKit inquiring about the
issue. What follows is the text of my correspondence:
quote
Mr. McCann,
Users on Ubuntu systems (myself included) are finding that ConsoleKit
generates several dozen processes and doesn't seem to release them.
Although no
@ Jonathan Rogers
However, currently it says nothing about what the threads are used for
or what would be an appropriate number of threads.
Of course, it's not documented, so no one knows, which is why the bug
report exists in the first place. Experienced users and system engineers
know that
I have the same problem. I was trying to uninstal consolekit, but it is
bindet to hundreds other apps. Impossible to remove. If I kill it, it
restarts automatically.
This bug is very annoying. I never need to switch user, I am the only
one here and yet I need to run this absurd application. I
@Jonathan Rogers --
There are at least two major flaws in your analysis. First, your
analysis presumes to know ex ante the configuration of the computer and
the use to which the package will be put. Second, it does not take into
account the need for simultaneously managing multiple users and
Sounds great, Loye. I look forward to your memory footprint reduced
console-kit-daemon. I too am interested in multiseat configurations.
I've experimented with a configuration that uses Xorg to create a
separate screen on each of two ports of my video card and an instance of
Xephyr running on top
i have checked Hide userland threads and it solve the issue,
Hiding the threads doesn't solve the issue; it merely hides the problem.
The problem is that the threads are running, not that the list of running
threads is too long.
On Mon, Apr 28, 2008 at 4:58 PM, Aeffenwell [EMAIL PROTECTED]
Ok, i understand, sorry
so, for the bug tracking, I have this issue since feisty fawn.
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
While it may be technically correct that spawning a thread for each
potential virtual console wastes resources, does anyone have an estimate
of how much? On my system, console-kit daemon (the entire process with
all umpteen threads) is using about 2.5MiB of resident memory, of which
about 1.7MiB
Hi,
I've noted that i had this problem for other programs like skype, firefox (and
npviewer)
in the setup, i have checked Hide userland threads and it solve the issue,
and for console-kit-daemon too.
I don't know if it can help.
Bye
--
console-kit-deamon spawns too many threads
This looks like an upstream bug: console-kit starts a thread for each
console that can theoretically exist. On Linux
(/usr/include/linux/vt.h) MAX_NR_CONSOLE is defined to be 63. console-
kit apparently wants to monitor each of the consoles to see if anyone
ever logs in on these consoles or
The problem, methinks, is a memory leak in the code, not too many
spawns.
If so, it may explain Bug 132029.
Happy Trails,
Loye Young
Isaac Young Computer Company
Laredo, Texas
http://www.iycc.biz
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You
pstree on my system shows about 60 console-kit-daemon threads on my up-
to-date Hardy as well. All except couple of the last ones have pids in
perfect sequence. Does console-kit-daemon start a fixed number of them
when starting up, whether so many are needed or not?
--
console-kit-deamon spawns
Crashing is a completely different symptom from anything described in
the bug description or discussion so far, so that really needs a new bug
report.
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member
Console kit crashes on hardy beta4 amd64. Causing all shift/ctrl key
sequences to be unavailable.
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have the same! Why it need so much?
--
console-kit-deamon spawns too many threads
https://bugs.launchpad.net/bugs/148454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've changed the header of this bug to be more concise about the actual
problem.
The question is, as Evan said before: Why does console-kit need so many
threads.
** Summary changed:
- htop shows about 50 console-kit-deamon processes that top and ps dont show
+ console-kit-deamon spawns too
64 matches
Mail list logo
