I wonder what would happen if we enabled the last part again in
/etc/X11/Xsession.d again, instead of the what it says now:
# gdm already creates a CK session for us, so do not run the expensive D-Bus
# calls if we have $GDMSESSION
if [ -z $GDMSESSION ] [ -x $CK_LAUNCH_SESSION ] \
( [ -z
That did not help, maybe if I enable --debug in /usr/share/dbus-1
/system-services/org.freedesktop.ConsoleKit.service it might give us
more information.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a member of
On Sat, Aug 21, 2010 at 07:40:37PM -, Lennie wrote:
If what Colin mentions is true, then would it not help to just disable
the getting the recently-logged-in-user-list from consolekit as a
test/workaround ?
Could you try the package from my PPA?
The UserManager stuff in gdm is one likely
At the moment I'm doing reboots so I could get a some debug from
consolekit, but so far it hasn't happend.
As I don't know consolekit or gdm very well but I can program, I hope it
would give me some idea of where to start to look.
I think maybe the debug I enabled made startup of consolekit slow
On Sat, Aug 21, 2010 at 10:26:26PM -, Lennie wrote:
I think maybe the debug I enabled made startup of consolekit slow enough
that it doesn't happen for me anymore. Because I can't reproduce. :-)
Can I suggest adding some debug to consolekit in the if if (errno ==
EINVAL data-retries++
Yeah, just noticed that, because your change did not help. :-(
With the debug on, I've not been able to reproduce the problem yet, so I
don't yet have a debug with the error-situation.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug
Can people affected by this bug have a go at the version of consolekit
in this PPA?
https://launchpad.net/~cjwatson/+archive/ppa
Beware: I really haven't tested this *at all* beyond building it, and
can't reproduce the error condition myself anyway. Make sure you have a
way to roll back to
(I only have this built for Maverick right now.)
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
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
One other thing, just following up a hunch: on a broken system, could
you find the process ID of console-kit-daemon ('ps acx | grep console-
kit'), then attach the output of 'lsof -p THAT_PROCESS_ID' run as root?
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
Regarding gdm: I think why this is happening despite the fact that
ConsoleKit upstream says that gdm shouldn't be starting CK until X has
started is probably that we're carrying the patch in
https://bugzilla.gnome.org/show_bug.cgi?id=593996. This queries CK for
users before X starts.
However,
** Also affects: consolekit (Ubuntu Maverick)
Importance: High
Status: Triaged
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Sorry, this seems to have dropped off the radar a bit. I will take a
look at this when I get some time, but I'm busy with other things at the
moment. Somebody else feel free to take it if they get an opportunity to
work on it before I do
** Changed in: consolekit (Ubuntu Lucid)
Assignee:
Hi Chris,
Nice to see you're back! :-)
I have tried a few things in the sources of consolekit but unfortunately
installing my new deb can make things worse sometimes (i.e. X refuses
to start every other time or so, even if I make no changes in the
sources). Maybe some config files are not
well, unfortunately the bug reappears after ~20 reboots, even with the new
upstart patch...
regards
f
** Attachment added: 20100817_fail_13_upstart-proposed.tar.gz
Thanks Skorka, now we are sure it's not a duplicate :)
The good thing about this bug is that I'm now testing many other distros
(Debian, CentOS, Fedora...) for our multitouch system and I'm seeing
lots of good things there... ♪♪ Always look on the bright side of
life... ♪♪
--
Active VT tracking
Hi all,
I'm also affected by this bug, or at least encounter the exact same symptoms as
Damien described in #9
The machine is a laptop Acer Aspire 1692 and the kernel is 2.6.32.24-generic-pae
The distrib is an up to date Lucid 10.04, ( fresh install + updates)
I did not perform enough boots to
** Attachment added: 20100816_fail_02.tar.gz
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139/+attachment/1492942/+files/20100816_fail_02.tar.gz
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you
** Attachment added: 20100816_ok_08.tar.gz
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139/+attachment/1492943/+files/20100816_ok_08.tar.gz
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a
** Attachment added: 20100816_ok_09.tar.gz
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139/+attachment/1492944/+files/20100816_ok_09.tar.gz
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a
** Attachment added: 20100816_ok_11_upstart-proposed.tar.gz
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139/+attachment/1492947/+files/20100816_ok_11_upstart-proposed.tar.gz
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this
Tried Mike Bianchi's proposed solution in comment 81 of Bug #543506.
As a result, 2 bad boots in a series of 20. This is five times less than before.
Also, marking the present bug as duplicate of Bug #554172, please
correct me if mistaken.
--
Active VT tracking can fail at startup
OC,
These bugs look different: they seem to have runlevel problems. Some
comments point to this bug though, like #15 of Bug #543506.
There certainly is quite a lot of confusion with all these boot bugs.
This guy nailed exactly how messy all this is:
I confirm this on an HP Compaq nc6000 laptop, Ubuntu 10.04 i386, fresh install,
both as installed and after updates.
My rate of bad boots is roughly 50% (based on roughly 20 restarts).
I installed Maverick alpha3 as a dual-boot. After 20 restarts I cannot
reproduce the problem under Maverick.
(Chris Coulson, are you there? Is there anyone knowledgeable listening
to this thread anymore?)
Some more investigations today: if I build consolekit from the latest source
and install that, then the error is SYSTEMATIC.
Reinstalling the ubuntu package (--reinstall) does not change a thing, the
I reinstalled ubuntu on a computer. Before I had this issue maybee 1/5
startupps. But now (even with the workarounds) i would say its more 7/10
times.. I just started to use linux 2 month ago but Im starting to
wonder if switching was a good idea.
--
Active VT tracking can fail at startup
Tobias,
If you have a spare partition, could you try Debian testing? Since you
experience this bug almost systematically, it would be interesting to see if
Debian solves your problem like it did for me.
http://www.debian.org/devel/debian-installer/
Also, which video drivers do you use? If you
Ubuntu being based on Debian, I've tried testing (aka squeeze). The
good news is that it works without a glitch, the bad one is that I am
switching all our production systems to Debian.
FYI, here's a comparison of relevant packages versions on Squeeze and
Lucid:
Debian Squeeze:
I have no better news at this point so I contacted the consolekit guys
to see what they think.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
According to an answer on the consolekit list, GDM shouldn't be activating
ConsoleKit until after the X server is up.
This may thus be a GDM bug (not waiting for X ready state before launching
consolekit)
I have thus added GDM as affected package.
** Also affects: gdm
Importance: Undecided
No it's not the only problem, I can't power-off or restart, sound does
not work, cups is not started and some other services like apache2 are
not started either. I haven't tried to perform admin tasks yet so I
don't know about that. How can I edit my linux boot line? Using grub2,
so there is no
Hi all,
Here are some preliminary results...
1) After setting Mike's verbose option the errors came back on 11
reboots out of 51 (~20%)
2) So I removed the verbose option, updated and installed grub and
rebooted a few times. Errors were still there (7/42=16%), although I got
more at the
Hendrik,
For admin tasks, try to add a user through the GUI users-admin. I don't
know about apache or cups, but I'm not surprised they fail too.
Before editing your bootloader, first try without that hack (e.g. only Sepero's
3 hacks). Then if it doesn't work for you this is the way to edit
The results are in for today: a standard linux distro has this problem
7% os the time (7 bad boots, 93 good boots)
This is not so far from the 2/100 obtained before. I'm not so sure the
hacking does any effect after all...
I'll try the hacks tomorrow, but I don't have much time to get this bug
Sepero,
Thanks a lot for your input. I'm testing your solution right now.
Currently I have 30 reboots with no problems, which is a good sign.
I first tried 2) and 3) only, but it failed after 10 reboots (no power
button etc...) Trying with all 3 now and it seems to work.
However, I can now see
Two remarks:
1) you will have to reactivate your network connection(s) the first time
you login after doing the 3 changes proposed by Sepero. Obviously
purging ifupdown has something to do with that... ;-)
2) the ureadahead errors that I mentioned previously seem to happen just
after X starts
After 106 reboots the bug appeared twice! I really thought it was
gone for good 'cause nothing happened until the 90th reboot. But
apparently something is still lurking out there...
In any case it's a nice improvement, thanks for the hack!! ( ^^)/ At least now
we have a usable system.
For
Damien, Sepero, and all ...
If you look at
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/comments/83 you
will see
that I also recommend
Add init='/sbin/init --verbose' to the linux boot line in grub.
I believe this helps by forcing /sbin/init to serialize starting up
Ok, I'm gonna try the work-around suggested in the forum. bug 554172
does not look like it's the same I'm seeing though because restart
doesn't fix the problem only a total shutdown and then start again
sometimes fixes the problem temporarily.
@DD: I can see the power off and suspend buttons but
Mike,
I don't have the runlevel-unknown issue, at least not that I think of.
But anyway, I'll try your extra hack today and see if it helps. Problem is I
may have to do a good 200 reboots to be sure it helps so it's going to take
some time. Stay tuned...
--
Active VT tracking can fail at
Hendrik, all,
('DD' and 'Damien' are the same person ;-)
Is the power-off behaviour your only problem? Can you still perform
admin tasks and have sound when your problem occurs? If the answer is
yes then it is likely a different issue, at least partly. But I think
there's quite a few bugs
Happens to me every single boot on Acer Aspire One (110, ZG5, 1GB RAM) since
the last time I ran update manager (e.g. most recent updates right now 10 July
2010). I assume this did a kernel upgrade. I never experienced this problem
before. I am unsure how to try an earlier kernel without the
A Possible Solution
This bug seems very related to these two:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/554172
This solution here is what worked for me. If it works for you, please help
spread it to others.
Same problem here, on all our production machines. Like Chris I have the
following messages in daemon.log:
WARNING: Error waiting for native console X activation: Invalid argument
Only for me X grows from 1 to 62, so I have 62 messages there. (Oddly,
the two last ones are 62 *then* 61)
Symptoms
FYI: My computer hasn't suffered the symptoms described in this bug
report for over 2 months, so for my part this bug is fixed.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@ Anthony Long: I have an ATI Radeon X1250 (RS690M chipset), so I don't
have the nvidia driver installed.
This bug still exists on my computer and appears almost every time since
the last kernel update! Only workaround right now is to completely
shutdown, start again and hope that it works this
Are you using the current nvidia driver, by any chance? This sounds
exactly like the problem that I had with the 'current' version. I
downgraded to v. 173 and the problems went away. My symptoms were not
being able to mount drives, power management problems, shutting down
issues, no sound (that I
Also I have this bug in my Ubuntu 10.04 update 32 bit, but only
sometimes this occursAny workarounds???
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hey guys!
I'm also having this problem but it didn't appear for a long time. Now, after
the recent kernel update, it happens almost every time I start my laptop and it
won't go away even if I completely shut down. Before, I was able to get it to
work if I shut down and restarted. Can anyone
Isn't there any workaround for this bug? Is there a way to downgrade the
kernel to the previous version? There is nothing working anymore: no
sound, no power management, no screensaver, I can't plug in any USB
devices because it cannot be mounted and I can only shutdown using the
terminal.
--
I can't.
I noticed, that Login screen configuration can't be unlocked simultaneously.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Given that I'm still seeing these symptoms on an up-to-date Lucid
installation, I'm assuming there's been no movement on this.
Can anyone suggest a more elegant work-around than 'log in and out a few
times until things work again'?
--
Active VT tracking can fail at startup
** Also affects: consolekit (Ubuntu Lucid)
Importance: High
Status: Triaged
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
101 - 152 of 152 matches
Mail list logo
