[Bug 544139] Re: Active VT tracking can fail at startup
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 notifications about this bug go to: https://bugs.launchpad.net/consolekit/+bug/544139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 cannot distuingish the error causes we need at least a safe way out. My suggestion would be to retry opening 20 times and then give up. In systemd I have settled to use 20 times with 50ms in between, totalling to 1s in total. Could you please update the patch? I'll then merge it. --- -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 added: verification-done ** Tags removed: verification-needed -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 Lennie and others for extensive debugging work; LP: #544139). -- Colin Watson cjwat...@ubuntu.com Wed, 10 Nov 2010 12:18:29 + ** Changed in: consolekit (Ubuntu Lucid) Status: Fix Committed = Fix Released -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
** 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
** 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 watch: None = freedesktop.org Bugzilla #31790 -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 Lucid) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
** 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 system. For example, any dialog that requires PolicyKit authentication cannot be unlocked. + Development branch: Fixed in https://launchpad.net/ubuntu/+source/consolekit/0.4.1-4ubuntu1 by retrying console opens if they return EIO. + Patch: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139/+attachment/1728928/+files/consolekit_0.4.1-3ubuntu2.debdiff + TEST CASE: Unfortunately, this bug is not uniformly reproducible, and may take many reboot attempts or even not be reproducible at all on any given system. If it is reproducible, then you can either try unlocking an administration dialog such as System - Administration - Time and Date (which will fail with a broken version), or (quicker) check for the string Error waiting for native console in /var/log/daemon.log. A successful fix will always permit a user with administrative privileges to unlock administrative dialogs. + Regression potential: When it breaks (not necessarily every time), consolekit is effectively completely broken. The test case should be sufficient to ensure that it is working properly. + + Original description follows (note that the discussion about why EINVAL + was being returned does not correspond to the end result of + investigating this bug, but is preserved here for the record): + Binary package hint: consolekit A few times over the last couple of days, I've noticed some weird consolekit issues where it doesn't correctly determine which VT is active, causing a lot of things to break (eg, disk mounting, rebooting, suspending etc). The issue is solved by rebooting. When it fails, I get a lot of messages in my daemon.log when consolekit starts: WARNING: Error waiting for native console 5 activation: Invalid argument This occurs because the following call fails with EINVAL: ioctl (console_fd, VT_WAITACTIVE, num); I discussed this with Scott on #ubuntu-desktop. To summarize, there is a window between GDM starting and the X server coming up where the ioctl that consolekit does on the VT's will fail. Unfortunately, consolekit starts around the time of this window. Here is the log: chrisccoulson Keybuk - i mentioned a consolekit issue last week, and your name was mentioned there chrisccoulson that might have been what you remember Keybuk can you remember more about what you mentioned? chrisccoulson Keybuk - a couple of times when I booted last week, consolekit was unable to determine what the active VT was chrisccoulson and it was throwing out errors like this: chrisccoulson WARNING: Error waiting for native console 5 activation: Invalid argument Keybuk right Keybuk but why is consolekit using that ioctl? Keybuk that's only used when you switch VT chrisccoulson Keybuk - it spawns a thread for each VT, which waits for it to become active chrisccoulson so it can track where the active one is Keybuk ok Keybuk it'll fail with -EINVAL for a short period during boot Keybuk does it correctly back-off from that, and restart the thread again later? Keybuk (if it goes into an infinite loop, that's not good either) chrisccoulson Keybuk - no, that's probably the issue really. once it has failed, it just gives up chrisccoulson so, we probably need to fix consolekit then? Keybuk yeah Keybuk we caused X to have the same bug chrisccoulson ah, ok. that makes sense. and that explains why i can't recreate it all the time Keybuk you get -EINVAL from VT_WAITACTIVE in a very specific condition Keybuk the current foreground VT is in KD_GRAPHICS mode, but also VT_AUTO Keybuk ie. it's been left with painted graphics ... but no process running on it Keybuk since it's in graphics mode, the kernel prohibits VT switches Keybuk can you guess when that condition is true? chrisccoulson do you know how long it's in that condition for? Keybuk chrisccoulson: however long the X server takes to start ;-) Keybuk couple of seconds usually chrisccoulson oh, right. that seems obvious now :) chrisccoulson Keybuk - so the window is quite large then (and I think consolekit is activated after GDM starts isn't it?) chrisccoulson i think gdm is the first thing to use it anyway Keybuk chrisccoulson: gdm activates it chrisccoulson yeah, i thought so chrisccoulson thanks Keybuk which means it's activated before X starts or while X is starting Keybuk ie. exactly in that window Keybuk chrisccoulson: so, on the VT_WAITACTIVE+VT_AUTO thing ... you could kinda argue it's a kernel bug Keybuk because the kernel bug should deal with that case on its own Keybuk but the kernel guys will tell you that the whole VT_* stuff is a mess, and they'd
[Bug 544139] Re: Active VT tracking can fail at startup
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 and others for extensive debugging work; LP: #544139). -- Colin Watson cjwat...@ubuntu.com Thu, 30 Sep 2010 14:49:11 +0100 ** Changed in: consolekit (Ubuntu Maverick) Status: In Progress = Fix Released -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 544139] Re: Active VT tracking can fail at startup
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 Lucid) Assignee: Chris Coulson (chrisccoulson) = Colin Watson (cjwatson) ** Changed in: consolekit (Ubuntu Maverick) Status: Triaged = In Progress -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 that proves this works. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 other things. I'm sad to say. I have some code I wanted to test to find out what the cause of the problem is and get a fix upstream. 4. Maybe I should schedule some time for that tonight or tomorrow night. As it's only 12 days left. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 ck_get_a_console_fd? - why is the console fd search stopped at 3? We often have values above that (11, 12...) so would it work if we just extended the search to 12 (or whatever the limit is)? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 st-002 console-kit-daemon[1085]: WARNING: eventually choose to use 12 Sep 2 09:16:05 st-002 console-kit-daemon[1085]: WARNING: first fd was 3 Sep 2 09:16:05 st-002 console-kit-daemon[1085]: WARNING: retried 1 times Sep 2 09:16:05 st-002 console-kit-daemon[1085]: WARNING: skipping: 7 2x Sep 2 09:17:40 st-002 kernel: [0.00] console [tty0] enabled Sep 2 09:17:41 st-002 console-kit-daemon[1161]: WARNING: did not fail Sep 2 09:17:41 st-002 console-kit-daemon[1161]: WARNING: skipping: 1 Sep 2 09:17:41 st-002 console-kit-daemon[1161]: WARNING: skipping: 7 0.4.1-3ubuntu1-lbesselink9 works for me, too. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: 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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 starting the usleep value at 20ms and multiplying it by 2 every time it fails, with the max delay of 1 sec (what do you mean I'm going to 11? ;) ). That way we keep a good reaction time without polling hundreds of times. So we would check at the following accumulated times: 0 (first retry), 20, 60, 140, 300, 620, 1260, 2260, 3260,..., 10260. If it fails after those 10 seconds then we should have a phatt warning in the logs. A debug message telling the total time of the waiting loop would be nice too (if the loop is triggered, of course) ** Attachment added: ck_vt_delay.png https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/544139/+attachment/1534027/+files/ck_vt_delay.png -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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: skipping: 7 -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 with ssd) I had just ignored this UI shutdown-problem ( sudo shutdown -h 0 works well :) ). As i am not familiar with consolekit and boot process, I have no clue for which string or which startup sequence I need to look with the stock ubuntu consolekit package. I have not systematic tested with the stock Ubuntu package, what's the difference in the error-case and the good-case was. If Lennie is interested in, he can build a ppa with debug logging, but without the re-try fix, so I can try to reproduce the bug on my box with a nearly original Lucid-consolekit package, but with more logging. Additionally what could be helpful: I will reboot several times with the original stock Ubuntu consolekit package to be sure, that I can reproduce the bug on this box (to validate my 99% failure rate without any 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ] Sep 1 18:16:04 st-002 kernel: [0.00] console [tty0] enabled 2. reboot syslog (failed) egrep console /var/log/syslog_20100901_3 | grep -v activation Sep 1 18:20:03 st-002 rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ] Sep 1 18:20:03 st-002 kernel: [0.00] console [tty0] enabled Sep 1 18:20:03 st-002 init: Failed to open system console: Input/output error Sep 1 18:20:04 st-002 console-kit-daemon[1050]: WARNING: Could not determine active console Good. Now I'll try to reproduce this timing problem with Lennies PPA. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 st-002 kernel: [0.00] console [tty0] enabled Sep 1 19:00:26 st-002 init: Failed to open system console: Input/output error Sep 1 19:00:30 st-002 console-kit-daemon[1364]: WARNING: did not fail Sep 1 19:00:30 st-002 console-kit-daemon[1364]: WARNING: skipping: 7 in 1/10 reboot this is my syslog: grep console /var/log/syslog_20100901_9 | grep -v VT_WAITACTIVE Sep 1 18:58:08 st-002 rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ] Sep 1 18:58:08 st-002 kernel: [0.00] console [tty0] enabled Sep 1 18:58:09 st-002 console-kit-daemon[1147]: WARNING: did not fail Sep 1 18:58:09 st-002 console-kit-daemon[1147]: WARNING: skipping: 1 Sep 1 18:58:09 st-002 console-kit-daemon[1147]: WARNING: skipping: 7 In all 10/10 reboots I have no symptoms as I've got with the original stock Lucid package (missing external drives etc.). I do not understand how init: Failed to open system console: Input/output error is related. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 calls to the debug-functions ? I did already change them from warning to debug, so it would not try to log anything through syslog. An other day, an other ppa. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 use 12 Sep 2 00:21:06 laptop console-kit-daemon[]: WARNING: first fd was 3 Sep 2 00:21:06 laptop console-kit-daemon[]: WARNING: retried 1 times So the workaround/test works for me. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 something had to be done there. So even if the root of the problem is fixed upstream, keeping the retry loop in the code would still be a plus, IMHO. Just out of curiosity, I will also try with a shorter sleep time to determine the race time more accurately. ** Changed in: consolekit (Ubuntu Lucid) Status: Triaged = In Progress -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 console-kit-daemon[1369]: WARNING: console_fd: 11 Aug 31 07:51:10 st-002 console-kit-daemon[1369]: WARNING: input of ck_get_active_console_num: 11 Aug 31 07:51:10 st-002 console-kit-daemon[1369]: WARNING: Current VT: tty7 Aug 31 07:51:10 st-002 console-kit-daemon[1369]: WARNING: skipping: 7 -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 filesystem and net-device-up IFACE=lo new: start on filesystem and started rsyslog and net-device-up IFACE=lo apt-get install ifupdown --reinstall --purge Environment: - Lucid 2.6.32-24-generic #41-Ubuntu SMP Thu Aug 19 01:38:40 UTC 2010 x86_64 GNU/Linux - NVIDIA UNIX x86_64 Kernel Module 195.36.24 -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 please include the whole debug of one of those times you did get it at boot (replace the date and time with the right one :-) ): grep console-kit-daemon /var/log/syslog | grep 'Aug 30 23:02' -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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)
--
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 important thing (see #88). Without that message, the bug reappeared after about 20 reboots and consolekit went through the retry-loop. However, the delay in the retry loop being very small (200usec), the loop did not have any effect: all 30 retries failed. After much messing with the patches, I restarted with a clean source tgz and applied the patch 08 ONLY. I'm sure this time, 'cause I applied the patch manually on the sources (!). I also changed the usleep time to 20 (0.2sec). After a few reboots the bug did not reappear, so I checked the log... only to see that the loop was working! In fact, the bug was triggered more often now that no extra debug messages were printed. But every time the loop fixed the problem. Banzai! Interestingly, only 2 retries were necessary (which means a 0.2 second delay). Hence the characteristic time on which the bug occurs is [ 6ms t 200ms ]. Here's the log, which is now very compact: Aug 31 12:52:48 tacto-ppp-01 console-kit-daemon[954]: WARNING: Could not determine active console Aug 31 12:52:48 tacto-ppp-01 console-kit-daemon[954]: WARNING: console_fd: 3 Aug 31 12:52:48 tacto-ppp-01 console-kit-daemon[954]: WARNING: tried but failed Aug 31 12:52:49 tacto-ppp-01 console-kit-daemon[954]: WARNING: console_fd: 12 Aug 31 12:52:49 tacto-ppp-01 console-kit-daemon[954]: WARNING: did not fail ? after 2 attempts Aug 31 13:01:49 tacto-ppp-01 console-kit-daemon[864]: WARNING: Could not determine active console Aug 31 13:01:49 tacto-ppp-01 console-kit-daemon[864]: WARNING: console_fd: 3 Aug 31 13:01:49 tacto-ppp-01 console-kit-daemon[864]: WARNING: tried but failed Aug 31 13:01:50 tacto-ppp-01 console-kit-daemon[864]: WARNING: console_fd: 12 Aug 31 13:01:50 tacto-ppp-01 console-kit-daemon[864]: WARNING: did not fail ? after 2 attempts If I'm not mistaken no warnings are printed at all when consolekit works well, and only a few lines are printed when the retry loop saves the day. Lennie, could you make a niceclean PPA with your patch #08 only (and change the usleep delay to 0.2sec)? I'm afraid my packaging skills are not exactly good enough for everyone to play with my debs. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 message did not fail ? after 1 attempts should be spotted in the logs. Clearly I'm missing something ;-) -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 console-kit-daemon[927]: WARNING: console_fd: 11 What I had with the --debug option on was that it also started sending debug to syslog a lot earlier like my change now. Any debug that early seems to prevent it failing at all the first time. The 'did not ? after 1 attempts' is in the loop when it would try again which is after the first try. Does that make it clear for you ? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: 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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 PPA? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 issue then. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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, you said that the FD 3 was coming from another error (cfr the consolekit mailing list). Well, I don't see this #3 anymore: only FD 11 is used for all boots. Could this spurious FD be the real problem? The six good boots I had before the last bad boot (see message #69) were also using FD 11. Looks like going to 11 is the solution :-) -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 or something like that ? Or an external display if this is a laptop. Because timing seems to be very important to cause the error this bug is about. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: 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 don't encounter the same problems and have to go looking for solutions as well. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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. I've contacted upstream to see if we can figure out the right way to fix it, so they can include a patch. But if the kernel gives us something we can't use then it will probably limit the possibilities. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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: [ 14.439499] Console: switching to colour frame buffer device 160x50 And that is not X itself, it's the loading of the radeon driver. So it's the kernel-mode-setting. Because with gdm-debug on it much later says: Starting X server process: -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: 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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: 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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 console-kit-daemon[1108]: WARNING: Error waiting for native console 2 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 6 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 6 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 6 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 3 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 15 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 8 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 19 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 12 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 12 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 12 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 14 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 14 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 14 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 16 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 16 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 16 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 18 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 18 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 18 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 20 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 20 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 20 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 3 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 3 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 7 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 7 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 7 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 4 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 4 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 9 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 9 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 26 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 29 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 30 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 30 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 19 returned -1 Eventually they all return -1 and say error waiting for native console. Luckily I still had the GDM debug on, so it logged this a second later: Aug 22 13:31:15 laptop gdm-simple-slave[1210]: DEBUG(+): GdmServer: Starting X server process: /usr/bin/X :0 -nr -verbose -auth /var/run/gdm /auth-for-gdm-f4pe6Q/database -nolisten tcp vt7 Seems quiet clear to me. When things do not fail, one thread may eventually say: Aug 22 13:29:45 laptop console-kit-daemon[1088]: WARNING: VT_WAITACTIVE for vt 7 returned 0 I don't understand why it would say vt 1 after that: Aug 22 13:30:28 laptop console-kit-daemon[1133]: WARNING: VT_WAITACTIVE for vt 1 But that is just because I'm new to this I guess. :-) The real question is, thus again, is gdm the one initiating the start of consolekit. If so, then gdm is to early to talk to consolekit. Doing some more testing to see where the error in consolekit happends, just for reference. Because I'm still thinking how can I check what initiates the start of consolekit. -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 You received this bug notification because you are a member of
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: 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 ck_get_a_console_fd from ck_vt_monitor_init and it does: kb_ok = (ioctl (fd, VT_GETSTATE, vts) == 0); fd is 3 and just a moment later it does: res = ioctl (console_fd, VT_GETSTATE, stat); in ck_get_active_console_num and fails. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 it fails:
g_warning (input of ck_get_active_console_num: %d,
console_fd);
res = ioctl (console_fd, VT_GETSTATE, stat);
if (res == ERROR) {
g_warning (got an error: ioctl VT_GETSTATE);
perror (ioctl VT_GETSTATE);
goto out;
}
{
int i;
g_warning (Current VT: tty%d, stat.v_active);
--
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 544139] Re: Active VT tracking can fail at startup
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 D-Bus activation when GDM asks for it, no matter what stage it asks for it, and I assert that ConsoleKit ought to be able to back off for a while and cope even if X is starting at the time. I'll construct a simpler test program and see what I got wrong in my patch. The reason you're seeing odd sequences of messages is that there are multiple threads running in parallel. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: 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: Could not determine active console Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 4 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 4 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 4 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 7 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 7 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 7 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 9 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 9 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 9 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 11 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 11 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 11 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 13 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 13 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 13 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 15 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 15 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 15 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 17 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 17 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 17 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 19 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 19 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 19 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 3 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 3 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 3 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 21 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 21 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 21 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 23 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 23 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 23 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 25 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 25 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 25 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 27 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 27 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 27 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 29 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 29 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 29 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 31 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 31 returned -1 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: Error waiting for native console 31 activation: Invalid argument Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING: VT_WAITACTIVE for vt 33 Aug 22 15:19:19 laptop console-kit-daemon[1110]: WARNING:
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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) {
continue;
}
--
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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: input of ck_get_active_console_num: 3 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: got an error: ioctl VT_GETSTATE Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: Could not determine active console, trying again Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: console_fd: 12 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: input of ck_get_active_console_num: 12 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: Current VT: tty1 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: skipping: 1 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 13 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 2 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 6 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 8 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 10 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 5 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 3 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 14 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 55 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 59 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 11 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 16 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 18 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 20 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 62 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 60 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 41 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 46 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 49 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 56 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 53 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 54 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 21 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 12 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 9 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 45 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 17 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 39 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 22 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 19 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 23 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 26 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 28 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 29 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 31 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 30 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 32 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 27 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 25 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 33 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 36 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 34 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 35 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 37 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 40 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 38 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 4 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 7 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 42 Aug 23 02:32:07 laptop console-kit-daemon[1131]: WARNING: VT_WAITACTIVE for vt 44 Aug 23 02:32:07
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
** 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 achieved with the following command. sudo -u gdm -- gconftool -s /apps/gdm/simple-greeter/disable_user_list true --type bool which changes the file: /var/lib/gdm/.gconf/apps/gdm/simple- greeter/%gconf.xml I enabled the debug in /etc/gdm/gdm.schemas before hand by setting the 'debug/Enable' to true and judging by the /var/log/gdm/:0-greeter.log file it seems it doesn't talk to consolekit anymore at startup. Normally it would say something like this: GdmUserManager: Found current seat: /org/freedesktop/ConsoleKit/Seat1 But not with the recent-user-list-disabled. Maybe someone like Damien can test this ? Because I can't really reproduce the problem very well. Possible you could also post (part of) a logfile of when it fails to work, maybe there is an other hint in there as well. I hope this helps, because this is a pretty annoying problem. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544139] Re: Active VT tracking can fail at startup
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
