Didn't work. Installed thunar and i can mount filesystems as a normal
user using thunar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/544139
Title:
Active VT tracking can fail at startup
To manage
Upstream requests updating this patch:
Hmm, so I have discussed this with some folks, and it seems we do need
something like this as the kernel will not help us here.
However, I don't think the patch is acceptable: there are other reasons why EIO
might be returned. Since we
** Changed in: consolekit
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/544139
Title:
Active VT tracking can fail at startup
--
ubuntu-bugs mailing list
Verification for Lucid.
I've verified that the package upgrades correctly from a default Lucid
installation and that after the installation the system reboots, that X
and the network are working. If there are specific verifications to do,
let me known.
Marking as verification-done.
** Tags
This bug was fixed in the package consolekit - 0.4.1-3ubuntu2
---
consolekit (0.4.1-3ubuntu2) lucid-proposed; urgency=low
* 10-retry_console_open_eio.patch: Retry console opens if they return EIO,
since this may happen while a tty is closing (see LP #554172, and thanks
to
** Changed in: consolekit
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/544139
Title:
Active VT tracking can fail at startup
--
ubuntu-bugs mailing list
Any testers for the lucid update? At least to verify that it still
works?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/544139
Title:
Active VT tracking can fail at startup
--
ubuntu-bugs mailing
** Branch linked: lp:ubuntu/consolekit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/544139
Title:
Active VT tracking can fail at startup
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Branch linked: lp:ubuntu/lucid-proposed/consolekit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/544139
Title:
Active VT tracking can fail at startup
--
ubuntu-bugs mailing list
It seems nobody forwarded this upstream? *sigh*, I'll clean up after
this and do that, so that we can get rid of that delta.
--
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
** Project changed: gdm = consolekit
** Bug watch added: freedesktop.org Bugzilla #31790
http://bugs.freedesktop.org/show_bug.cgi?id=31790
** Changed in: consolekit
Importance: Undecided = Unknown
** Changed in: consolekit
Status: New = Unknown
** Changed in: consolekit
Remote
Accepted consolekit into lucid-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: consolekit (Ubuntu
** Patch added: lucid-proposed patch
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139/+attachment/1728928/+files/consolekit_0.4.1-3ubuntu2.debdiff
** Description changed:
+ Impact: ConsoleKit sometimes fails to determine which VT is active, breaking
many parts of the
This bug was fixed in the package consolekit - 0.4.1-4ubuntu1
---
consolekit (0.4.1-4ubuntu1) maverick; urgency=low
* 10-retry_console_open_eio.patch: Retry console opens if they return EIO,
since this may happen while a tty is closing (see LP #554172, and thanks
to Lennie
Thanks a lot, Lennie!
--
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
OK, I'll go ahead then, and we can revisit if further problems arise.
Thanks, and particular thanks to Lennie for tireless debugging.
--
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
I'll backport this to Lucid after it's spent some time being tested in
Maverick.
** Changed in: consolekit (Ubuntu Maverick)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Changed in: consolekit (Ubuntu Maverick)
Milestone: None = ubuntu-10.10
** Changed in: consolekit (Ubuntu
Thanks Colin.
I had some time and access to the laptop again.
So I created a small patch on top of your patch to prove it what
happends.
I did 10 boots and 4 times the code was triggered, 6 times it did not trigger,
but it seems those were the times it did not need to be triggered.
So I think
I rebooted my box (Lucid) 10 times.
Good, I cannot reproduce the symptoms described in #9 or #109.
zero errors. all okay. no fail or error in syslog.
The Lucid consolekit package 0.4.1-3ubuntu2~ppa1 from cjwatson (#124 and #128)
works for me.
--
Active VT tracking can fail at startup
Colin, sorry. At the moment I can test for Lucid only. Anyone else?
--
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
Ohh, hi Colin, sorry I missed your first 2 messages.
I have a few remarks:
1. won't the timing be different on Maverick ? You still need to be able
to reproduce the problem first.
2. Would it not be a good idea to build a ppa for Lucid so people can
test that ?
3. I've been really busy with
I've uploaded a matching Lucid version.
--
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
Lennie, I suspect that if you read through bug 554172 it will be
enlightening. It explains why opening /dev/console (/dev/tty0 will be
the same) can sometimes fail with EIO.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification
It was quiet a long bug report, but it made sense to me.
I wasn't able to test, the laptop I use for testing was in use this
evening.
--
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,
Could anyone please test the packages in that PPA? If it works and I
get positive feedback, I can probably still just about squeeze it into
10.10.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a member of
With reference to comment 110 in particular, I wonder if this is a
consequence of bug 554172.
--
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.
--
How about version 0.4.1-4ubuntu1~ppa2 in
https://launchpad.net/~cjwatson/+archive/ppa? It should build soon.
This retries the open() of console fds on EIO.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a
Thanks Lennie! (^-^)v
I just understood why the console #3 was popping up all the time. That
brings two newbie questions:
- why is nothing done if all no console could be obtained? IMHO the
first warning should be printed from ck_get_a_console_fd. In fact,
shouldn't the retry loop be in
Damien, all good questions, but I got a better response from upstream:
Atleast /dev/tty0 should work, find out why it isn't.
--
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
Well, I just answered my second question by trying it. It doesn't work.
But I still think that ck_get_a_console_fd should return ERROR and not a bogus
fd.
This is fine tuning though...
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug
Concerning your last question, I think a default kernel might have
something like 65536 possible values for that and you don't want to
check them all. Probably it can even be raised with a kernel-compile.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You
Your 3rd question:
No1 likes that part of the code, I've got the feeling that part will go
away.
--
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.
--
Lennie, I made 10 reboot tests. Looks good to me:
8x:
Sep 2 09:16:04 st-002 kernel: [0.00] console [tty0] enabled
Sep 2 09:16:04 st-002 init: Failed to open system console: Input/output error
Sep 2 09:16:05 st-002 console-kit-daemon[1085]: WARNING: tried but failed
Sep 2 09:16:05
Good very good, so now I can get back to talking to upstream about this.
How they want to put in a real fix.
--
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.
Damien I think the text was actually tried but failed, but I doubt
moojix has that text as it will not be reached if moojix didn't see:
trying again
Anyhow, I made some more changes and a new ppa.
The ppa is building at this moment.
--
Active VT tracking can fail at startup
I downloaded the ppa on my laptop and it didn't break it.
But I wasn't able to reproduce the problem which we are trying to fix.
So I wasn't able to test the fix/workaround.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification
Thanks Lennie, I'll try it tomorrow.
I am now doing quite a few reboot cycles to see how the retry delay
varies. Early results show large differences: between 20ms and almost
two seconds.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug
Damien,
Let me know what you'll find, because then we'll get a good idea of how
bad it really is.
The new ppa has a loop which has 30 times 0.2 seconds (I changed the
usleep also this time).
So that's 6 seconds, that ought to be enough ?
If you have any other code/suggestions let me know.
--
Lennie,
I finished rebooting a few times and here's a histogram of what I've
got.
It basically falls into 3 categories: less than 100ms (majority of
cases), about 600~1000ms and close to 2000ms. I could not get anything
2 seconds, which is a good sign.
Given the wide range I would suggest
just FYI:
the latest ppa (0.4.1-3ubuntu1-lbesselink7) works for me.
grep but failed /var/log/syslog | wc -l
0
grep console-kit /var/log/syslog | grep -v VT_WAITACTIVE
Sep 1 11:49:26 st-002 console-kit-daemon[1368]: WARNING: did not fail
Sep 1 11:49:26 st-002 console-kit-daemon[1368]: WARNING:
moojix,
How often did the bug appeared with the stock ubuntu packages? If it was
not systematic you'll need to reboot a few (or a lot) of times to
trigger the bug and see how it's handled by Lennie's PPA.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You
Damien,
i had the symptoms (no automount of external drives and shutdown/restart not
working as user) described above in this bug at
99% of my reboots (On my new box since 4 weeks nearly with every daily boot -
it's a workstation, not a server). As I had other priorities on this new box
(i870
okay, I've used the original Lucid consolekit package (0.4.1-3ubuntu1) for some
reboot tests.
I can reproduce the symptoms: 1. reboot: okay - 2. .. 5. reboot failed with the
symptoms.
1. reboot syslog (ok)
egrep console /var/log/syslog_20100901_2 | grep -v activation
Sep 1 18:16:04 st-002
I've repeated the tests with Lennies ppa (0.4.1-3ubuntu1-lbesselink7)
In 9/10 reboots this is my syslog:
grep console /var/log/syslog | grep -v VT_WAITACTIVE
Sep 1 19:00:26 st-002 rsyslogd-2039: Could no open output file '/dev/xconsole'
[try http://www.rsyslog.com/e/2039 ]
Sep 1 19:00:26
moojix do you have one that does not say the following ?: did not fail
--
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
Lennie,
no, unfortunately zero. all say with your ppa did not fail.
--
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
Then I don't think I actually solved it, just slowed it down enough so
it didn't fail.
I'm already looking at a diff between 0.4.1-3ubuntu1 and
0.4.1-3ubuntu1-lbesselink7
This morning the strace I tried also looked good. I don't think it's the
debug/warning logging to syslog.
Maybe it is the
After a whole evening running tests and no failures (and thus no way to
test the fix), the new ppa gave this result after less then 10 reboots:
Sep 2 00:21:06 laptop console-kit-daemon[]: WARNING: tried but failed
Sep 2 00:21:06 laptop console-kit-daemon[]: WARNING: eventually choose to
That sounds very promissing.
But I've been pondering, maybe it needs more work to be sure.
--
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
Yes, knowing why the console FD is wrong would be very nice... Then upstream
could fix the bug in a more appropriate fashion.
But in the meantime it will at least make Ubuntu usable for some of us.
Also, the original sources had this FIXME warning where you added the
retry loop, showing that
Lennie, Damien,
trying again is not written on my box
zgrep trying again /var/log/* | wc -l
0
grep console-kit /var/log/syslog.1 | grep Aug 31 | grep -v VT_WAITACTIVE
Aug 31 07:51:10 st-002 console-kit-daemon[1369]: WARNING: ck_get_a_console_fd,
choose: /dev/tty0
Aug 31 07:51:10 st-002
moojix,
look for try but failed, this is the actual string.
--
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
I had the same symptoms as Damien desribed in #9
(no automount of external drives, shutdown or restart was not possible as user).
I used a similar workaround as Sepero pointed out in #10 (ubuntuforum link).
My workaround were the following 2 steps:
edit /etc/init/rc-sysinit.conf
old: start on
sorry for my last comment #91. This workaround did not work for me.
Same symptoms (no automount external drives, no shutdown etc.) after reboot.
@Lennie I tested now your quick hack ppa from #66.
I have not tested as intensive as Damien, but it works well after 10 reboots on
my box.
--
Active
The work around in Lennie's PPA seems to be working here. Haven't
experienced the problem since using it.
--
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.
Hi,
moojix and cmat could you post the debug from your logs ?
You possible don't want to post all of it, just the stuff that seems to
be different between boots.
I'm especially interrested to know if it says trying again. You can see it
with:
grep trying again /var/log/syslog
In that case
Lennie,
I tired to build the debs before, but I haven't been very successful. I
now have a very good reason to try again though :-) Stay tuned...
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because you are a member of
moojix, cmat,
To isolate the interesting parts of the log, you can also try this
(rather awful) command:
cat /var/log/daemon.log | egrep console-kit-
daemon\[[0-9]{3-4}\]\:.WARNING:.[^V]
(it finds the console kit messages in the logs, but removes the 64
VT_WAITACTIVE messages from the threads)
I think I have some good news...
I first tried Lennie's PPA, but without patches #5, #6 and #7 (IOW, only
patch #8). I'm actually not exactly sure what patches were applied,
because the skipping :%d messages were still there. But the message of
patch #7 was not there any more, which is the
I have performed 222 reboots with the latest PPA from Lennie, and not a single
time did the bug happen. \( ^^)/
(However, this bug is far from being closed since we don't know exactly WHY
it's working.)
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You
The most logical explanation is, you had the same 'problem' I had when I
turned on --debug for the console-kit-daemon.
It would start logging messages to rsyslogd (which saves it in syslog,
daemon, etc.) early and the timing would be off and you would not be
able to reproduce it.
--
Active VT
But I haven't turned on --debug when starting the daemon. Or is it a
compilation option?
If so, did you turn it on in your latest PPA (lbesselink4)?
Also, I don't see how this would explain the lack of messages in the
daemon log. From the code I saw even in case of an immediate success,
the
The debug that I added which says:
Aug 26 17:44:51 tacto-ppp-01 console-kit-daemon[927]: WARNING:
ck_get_a_console_fd, choose: /dev/tty0
Is earlier in the startup of console-kit-daemon then the previous
versions.
The previous version had the first debug at:
Aug 26 17:44:51 tacto-ppp-01
Ok, it makes sense now, thanks. I was only looking at the patch 08-
and thought that the 07- was already used in your previous PPA, so I
missed those debug statements.
So if we want to see if the retry loop is effective then we should
remove patch 07?
--
Active VT tracking can fail at startup
Yes seems like it, I hope to have time for it this evening otherwise
it's probably something for tomorrow.
If you know how to build it, you could try it out yourself. :-)
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received this bug notification because
I have updated the libs too, just in case. But the logs are expectedly
the same.
( Small thing: you used usleep(200) which is not a pause of 0.2 sec but
0.0002 sec. )
Could it be that there's a problem in the packaging? Do you see the new
debug warnings on your machine if you install your newest
Using an hex editor, the new error strings (such as did not fail ?
after %d attempts) show up in the binary of console-kit-daemon.
which console-kit-daemon returns the proper location (/usr/sbin), so
there should not be any conflict (like multiple binaries, who knows!)
Probably not a packaging
Thanks, I'm testing your PPA. I have about 60 consecutive successful
boots so things look good (I will continue to 200 to be sure).
However, there is nothing suspicious appearing in the logs (ie. no more
got an error: ioctl VT_GETSTATE). Does it mean that bad FDs are not
returned any more?
Also,
120 reboots and not a miss!
Attached is the log of all reboots (minus the VT_WAITACTIVE message from
the 64 threads)
** Attachment added: good-log-120.txt
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139/+attachment/1519982/+files/good-log-120.txt
--
Active VT tracking can
Also, this is the last consolekit log in full
** Attachment added: last-good-full.txt
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139/+attachment/1519983/+files/last-good-full.txt
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You received
So that could mean that when we keep trying to grab the console_fd it
seems to work.
But I'm missing some debug-information, that is a bit strange.
It was a bit late last night so that might be why it is missing. :-)
I hope that is the reason, because otherwise I can't quiet explain it.
--
Yeah, can't explain that either. If we ask for an FD more than once
there should be something mentioned in the logs.
It could also be that I've just been lucky with the reboots. I've had
about 100 successive boots before (without any patch) so it's worth
trying more tomorrow...
--
Active VT
Damien, I do have a question.
Just to make sure, you did use the same hardware/machine to test ?
I think I read you had several of these machines ? Did you maybe do a
restore from an image or something like that ? Did you use the same
method to do so ?
There was no extra USB-device plugged in
Lennie,
Exactly the same machine. I just did apt-get update;apt-get install
consolekit. That's all. Not a single hardware change.
Mmmm... But I remember that it only upgraded the consolekit package, not
the associated libraries. Could that explain something?
--
Active VT tracking can fail at
no, I don't think that matters.
I'll have a look at what else I did, maybe I did something wrong and the
debug isn't displayed.
--
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
Lennie,
Maybe we could try a couple of times (20x?) to get a proper console_fd, with a
small pause in the loop (0.5s ?)
That way we would know if there is some delay between the fd becoming useless
and a new fd being reported.
--
Active VT tracking can fail at startup
I'll see if I can create some code that does that.
But I hope to get an answer from upstream how they would like it to be
solved.
That way I don't have to create any code which we'll gonna throw away
later. :-)
But more importantly they can incorporate it in the upstream version, so
others
I did what you asked and added a loop, 0.2 seconds 40 times.
I uploaded a new ppa, it will need some time to compile. It says 26
minutes to wait till it will compile amd64 and 8 hours before i386 will
build.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You
BTW, Lennie, does your PPA includes Colin's patch?
--
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
Damein,
That's annoying. But atleast now we know, we can ask the kernel for
something, which it will give us, but what it gives us is useless.
Interresting.
No, it does not include that patch.
I was trying to find out what is going on and fixed my problem with a
workaround along the way.
OK, I created a ppa with my quick hack so people can test it.
deb http://ppa.launchpad.net/lbesselink/consolekit/ubuntu lucid main
But it will take a couple of hours before it has been compiled by
launchpad.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You
Well, the ppa is doing compiling. I hope someone, anyone.
Maybe Damien has time to test this ?
It solves this specific problem of the VT_WAITACTIVE.
__
Looking at some of the logging, the most likely candidate for which is changing
the console_fd from under consolekit is this:
kernel: [
Just a small lesson, don't change text at the last moment :-)
Instead of:
Well, the ppa is doing compiling. I hope someone, anyone.
I meant to say:
Well, the ppa is done compiling. I hope someone, anyone can test it.
--
Active VT tracking can fail at startup
Hi Lennie,
Just tried your PPA but it still fails, after just 6 boots.
Log is attached.
** Attachment added: cc.log
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139/+attachment/1514607/+files/cc.log
--
Active VT tracking can fail at startup
I changed the original package (not ppa) to have g_warning instead of
g_debug for VT_WAIT..
let's see what happends.
--
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
Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Could not determine
active console
Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 2
Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt
2 returned -1
Aug 22 13:31:14 laptop
Yes, it's this one that failed:
res = ioctl (console_fd, VT_GETSTATE, stat);
Interresting, it would have done:
kb_ok = (ioctl (fd, VT_GETSTATE, vts) == 0);
just moments before that in ck_fd_is_a_console
I wonder...
--
Active VT tracking can fail at startup
So I checked, when it fails:
Aug 22 14:32:46 laptop console-kit-daemon[1119]: WARNING: input of
ck_get_active_console_num: 3
Aug 22 14:32:46 laptop console-kit-daemon[1119]: WARNING: Could not determine
active console
That doesn't make a lot of sense to me, it seems to have called
Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: input of
ck_get_active_console_num: 3
Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: got an error: ioctl
VT_GETSTATE
Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Could not determine
active console
When I have and
The theory in the description of this bug is that something is starting
X at the time, and that ConsoleKit is racing with it. As such, you will
see different results from the same ioctl from moment to moment.
It's not obviously that GDM is calling ConsoleKit too early - ConsoleKit
is started by
On Sun, Aug 22, 2010 at 11:57:38AM -, Lennie wrote:
Eventually they all return -1 and say error waiting for native console.
Could you please attach the full unedited log? I'd like to go through
the whole thing myself. Thanks.
--
Active VT tracking can fail at startup
Here is the whole part of the log when it fails:
Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: input of
ck_get_active_console_num: 3
Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: got an error: ioctl
VT_GETSTATE
Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING:
A small test-program to query dbus would be enough. That way I could run
it without gdm (and thus X) and see if it can cope with that.
And seems to work just fine if I run it on the console without gdm, etc.
--
Active VT tracking can fail at startup
https://bugs.launchpad.net/bugs/544139
You
Is that first part really threaded though ? Isn't it just failing
because X starts up at the same time or something like that ?
--
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
What I mean is, it starts up tried to find the active vt, when that
succeeds it continues to the next step, it tried to get it again but
fails. Then starts the threads, but not for the active console:
/* don't wait on the active vc */
if (i == current_num) {
I hacked in some code in ck_vt_monitor_init to try again and I think I
got it.
The console_fd was just a bad one so the threads couldn't use it to
VT_WAITACTIVE.
Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: console_fd: 3
Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING:
Colin,
Regarding lsof, here's the output I have when the bug occurs.
(I am running Lucid so I can't test your PPA)
** Attachment added: lsof-broken.txt
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139/+attachment/1511936/+files/lsof-broken.txt
--
Active VT tracking can
** Tags added: patch
--
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
Hi Colin and all the others,
I recently upgraded a laptop and I also sometimes had the 'can not
shutdown/reboot' probleem.
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 ?
Which can be
Forget what I mentioned, it doesn't work. I was doing reboot-cycles to try and
produce the error and I got the same problem again:
WARNING: Could not determine active console
WARNING: Error waiting for native console 10 activation: Invalid argument
...
--
Active VT tracking can fail at startup
1 - 100 of 152 matches
Mail list logo
