We have a Ubuntu 10.04 LTS machine set up in vmware for serving a git
repository over ssh and our Hudson instance do several polls a minute.
This is how our /var/log/ConsoleKit looks:
root@Sandbox:/var/log/ConsoleKit# ls -l
total 457424
-rw-r--r-- 1 root root 228364612 2011-02-28 14:41 history
** Changed in: gdm
Importance: Unknown = Medium
--
ck-history can take a *long* time to run, during which gdm is unusable
https://bugs.launchpad.net/bugs/400863
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
** Changed in: gdm
Status: New = Fix Released
--
ck-history can take a *long* time to run, during which gdm is unusable
https://bugs.launchpad.net/bugs/400863
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
** Branch linked: lp:ubuntu/gdm
--
ck-history can take a *long* time to run, during which gdm is unusable
https://bugs.launchpad.net/bugs/400863
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing
Thanks guys, it's a very noticeable improvement!
--
ck-history can take a *long* time to run, during which gdm is unusable
https://bugs.launchpad.net/bugs/400863
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
** Branch linked: lp:~ubuntu-desktop/gdm/ubuntu
--
ck-history can take a *long* time to run, during which gdm is unusable
https://bugs.launchpad.net/bugs/400863
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
I've made a patch that caches the result of ck-history so there is no delay on
startup (patch also upstream):
lp:~ubuntu-desktop/gdm/ubuntu
The cached version is used on startup and then updated once ck-history
completes. The information is only used for ordering the user list so
out-of-date
** Changed in: gdm (Ubuntu Karmic)
Status: Confirmed = In Progress
--
ck-history can take a *long* time to run, during which gdm is unusable
https://bugs.launchpad.net/bugs/400863
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This should have gotten a lot better since ConsoleKit was fixed to not
create and log system sessions for cron, etc. But caching the result is
still nice, thanks Robert!
** Changed in: gdm (Ubuntu Karmic)
Status: In Progress = Fix Committed
--
ck-history can take a *long* time to run,
This bug was fixed in the package gdm - 2.27.90-0ubuntu2
---
gdm (2.27.90-0ubuntu2) karmic; urgency=low
[ Robert Ancell ]
* debian/patches/13_cache_ck_history.patch:
- Cache result of ck-history to make startup fast (LP: #400863)
[ Martin Pitt ]
* Add
** Bug watch added: GNOME Bug Tracker #594344
http://bugzilla.gnome.org/show_bug.cgi?id=594344
** Also affects: gdm via
http://bugzilla.gnome.org/show_bug.cgi?id=594344
Importance: Unknown
Status: Unknown
--
ck-history can take a *long* time to run, during which gdm is unusable
** Changed in: gdm
Status: Unknown = New
--
ck-history can take a *long* time to run, during which gdm is unusable
https://bugs.launchpad.net/bugs/400863
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
** Changed in: gdm (Ubuntu Karmic)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = Robert Ancell
(robert-ancell)
--
ck-history can take a *long* time to run, during which gdm is unusable
https://bugs.launchpad.net/bugs/400863
You received this bug notification because you are a member of
Bug 423450 is to have the user detection in the GDM server thus this
delay would only be caused once.
--
ck-history can take a *long* time to run, during which gdm is unusable
https://bugs.launchpad.net/bugs/400863
You received this bug notification because you are a member of Ubuntu
Desktop
Robert Ancell wrote:
Bug 423450 is to have the user detection in the GDM server thus this
delay would only be caused once.
Regardless, please could you provide a reference to the analysis of the
fastest we can get GDM up and running? I don't mind if remote user id's
are populated later
did that change recently in karmic? when we looked at it at the distro
sprint the rotation was not having any effect since the ck-history
command look at all the files in the directory including the ones
rotated and gziped
--
ck-history can take a *long* time to run, during which gdm is unusable
** Changed in: gdm (Ubuntu Karmic)
Milestone: None = karmic-alpha-6
--
ck-history can take a *long* time to run, during which gdm is unusable
https://bugs.launchpad.net/bugs/400863
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
This is a duplicate of bug #287715, whose root cause has been resolved;
ck-history will be much faster once the old, cluttered history logs have
rotated off.
There *should* be an option to disable the facebrowser - users are not
enumerable in all contexts - but that's a separate bug.
--
I'd like to reiterate that whilst waiting for ck-history, gdm does not
even allow you to log in with a typed-in username. Which is kind of a
separate bug, but not really entirely since if this delay wasn't there,
you'd never notice.
--
ck-history can take a *long* time to run, during which gdm
I finally tried to figure out why gdm took so long to present the users
names (30 seconds or more sometimes) and came across this bug. I'm going
to add the regression-potential tag, since this is clearly a regression
over Jaunty's login process.
$ ls -l /var/log/ConsoleKit/
total 6504
-rw-r--r--
$ dpkg -l|egrep '(consolekit|gdm)'
ii consolekit 0.3.1-0ubuntu1
framework for defining and tracking users, s
ii gdm2.27.4-0ubuntu11
GNOME Display Manager
--
I'm going to up the priority to Medium. While many average desktop users
may not have cron jobs that make consolekit's history large, I daresay
there is a significant percentage that do. This bug gets to be highly
annoying fast for those users. Feel free to adjust the priority as
necessary.
**
** Changed in: gdm (Ubuntu)
Importance: Undecided = Low
** Changed in: gdm (Ubuntu)
Status: New = Confirmed
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
** Also affects: gdm (Ubuntu Karmic)
Importance: Low
Assignee: Ubuntu
Reopening bug. Even with the logrotate file in place, and having verified that
log rotation *has* occurred
ck-history still takes a prohibitively long time to run.
Indeed, now that some of the history is gzipped, ck-history is now up
from taking 20 seconds to taking 40 seconds!
I have now
This was supposedly fixed by consolekit 0.3.0-2ubuntu7 by adding log
rotation to the ConsoleKit history file:
consolekit (0.3.0-2ubuntu7) karmic; urgency=low
* Install a logrotate configuration file for /var/log/ConsoleKit/history
so that it doesn't get huge and cause ck-history to take a
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/29203053/Dependencies.txt
--
ck-history can take a *long* time to run, during which gdm is unusable
https://bugs.launchpad.net/bugs/400863
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
26 matches
Mail list logo
