[00:01] cjwatson, cody-somerville right. well at least in the context that cody-somerville was referring to, it's more relevant that it is a bootable live disk [00:04] pochu: .31-2.16 doesn't seem to have an gspca fixes either [00:05] slangasek: hey. Is there any way for cron to use common-session in PAM, but not the pam_ck_connector that is declared within? [00:05] or is that question too crazy to even contemplate? [00:06] james_w: yeah, that's too crazy; the mechanism for selecting different modules based on service is to configure /etc/pam.d/$service :) [00:06] yeah :-) [00:06] but, but... https://bugs.edge.launchpad.net/ubuntu/+source/consolekit/+bug/287715/comments/5 [00:06] Ubuntu bug 287715 in consolekit "Trying to shut down or restart falsely suggests others are logged in" [Medium,Triaged] [00:07] "This PAM module should be used with caution; only local login managers such as login should use this." [00:07] (the new GDM has further increased the priority of this somewhat) [00:07] hrm? how would that be an issue for GDM? [00:08] it's a bit baroque [00:08] this is basically a manifestation of the "we need to distinguish between interactive and noninteractive sessions in PAM" bug [00:08] GDM now tries to be clever with the user selector by showing users in frequency order [00:08] to do this it calls ck-history --frequent [00:08] ah, so it sees cronjobs, haha [00:08] that in turn parses /var/log/ConsoleKit/history [00:09] we've fixed it so that it only shows non-system users [00:09] but if you have a */10 cronjob say, you appear to log in a lot [00:09] right; so the right thing is that we need to *split* /etc/pam.d/common-session, for this reason and others [00:09] the more sever issue is that with cron running so often /var/log/ConsoleKit/history is huge, and --frequent requires parsing the whole thing [00:10] so it takes a few seconds after getting to GDM to actually get any users listed [00:10] billybigrig: I have no clue about that, sorry [00:11] I'm adding logrotate to consolekit to keep the size limited, and considering a new mode for ck-history that is a frequency/recency measure, but fixing this would still be good [00:11] is the split something that is planned, or just needed? [00:12] james_w: Debian bug #169930, fwiw; I don't have anything more than the roughest notion of what the split needs to look like, at this point [00:12] Debian bug 169930 in pam "pam: Default usage of pam.d-include-files" [Wishlist,Closed] http://bugs.debian.org/169930 [00:12] ok, thanks [00:12] I guess it's unlikely to be done this cycle? [00:13] in that case, is just waiting for the correct fix the right thing to do, and just work on the other fixes to the symptoms? [00:15] cjwatson, looks like the TB can see into the future [00:15] james_w: if this log scales poorly, presumably terminal servers are going to have the same problem, right? So the symptom should still be addressed, one way or another [00:16] yeah, that should still be fixed [00:16] I don't see another fix for that original bug though [00:16] huh, where did ubottu get that wrong description and bug state? [00:17] I'm thinking of using logrotate's behaviour to involve recency in the frequency calculation [00:17] yeah, I can't offer much for that bug right now; any workarounds would be fussy and make the path to a correct fix longer [00:18] parse the first file, emit the frequency-based user list from that, then parse the first rotated file, and emit any further users from that in frequency order, etc. [00:18] so that the GDM list can fill asynchronously in still a useful order [00:18] ok, thanks, I await a true fix [01:01] So 2.6.31-rc2 fixes one thing for me, but breaks another. :) [01:01] Hurray! [01:02] yeah, but I've just found that what seems to be broken as a user, seems to work as root./ [01:02] Seems some ioctls for talking to DVD/CD drives only work as root. [01:02] i.e the eject command as a user doesn't work, but as root works fine. [01:03] Seems to work for me. [01:04] ion: You on 2.6.31-2-generic? [01:04] And what arch? [01:04] Linux hapatus 2.6.31-2-generic-pae #15-Ubuntu SMP Mon Jul 6 02:33:43 UTC 2009 i686 GNU/Linux [01:05] ok I am on amd64. [01:06] If the multiarch thing were already in place, i could simply switch this system to amd64 and give results soonish. :-P [01:06] heh [01:13] doko: do you know why build-essential no longer has a direct dependency on gcc? The most recent changelog entry still talks about it [01:21] doko: looks like a bug in the patch for build-essential 11.4, which doesn't match the changelog entry [01:47] persia: They still have not backported our project :\ [01:48] persia: https://bugs.launchpad.net/ubuntu/+source/tmw/+bug/393724 [01:48] Ubuntu bug 393724 in tmw "Please Backport tmw 0.0.24.1-1 in Hardy with tmw 0.0.29.1-1 in karmic" [Undecided,New] [01:49] see this is they type of unresponsiveness we have to deal with [01:51] Kage_Jittai: that's not the correct procedure for requesting backports. https://help.ubuntu.com/community/UbuntuBackports#How%20to%20request%20new%20packages [01:53] slangasek: I was told it would work [01:53] you were told incorrectly, then; the page I've linked you to documents how to request backports [01:53] slangasek: I don't have time to read that page [01:54] filing a bug on the package isn't going to be noticed by the backports team [01:58] https://bugs.launchpad.net/dapper-backports/+bug/396317 [01:58] Ubuntu bug 396317 in dapper-backports "Please Backport tmw 0.0.24.1-1 in Hardy with tmw 0.0.29.1-1 in karmic" [Undecided,New] [01:58] will that work? [01:59] should have been filed against the hardy-backports project rather than dapper-backports, but that should show up on the backport team's radar anyway, yes [02:00] slangasek: *sigh* Dapper needs to be backport too prolly [02:00] but Hardy is the most used out of date [02:00] doubtful, given that dapper desktop support expires in a few short days [02:00] ok [02:01] I remember when dapper was new :P [02:01] slangasek: ok, well, I hope this doesn't vanish with it [02:01] slangasek: well see if the backport team picks up on it this time [02:02] *sigh* [02:02] some people have no patience [02:02] Indeed. [02:02] 220 open hardy-backports bugs, I doubt they'll find time to backport some game client in the next couple of hours [02:04] good to see backport requests open for stuff that hasn't even landed in karmic yet [02:06] I see tmw 0.0.29.1-1 in karmic [02:07] slangasek: sorry, I was referring to a bug for php 5.3 [02:08] it seems that a few people want that version [02:11] ah [02:11] * slangasek uploads php 5.3 as a dummy package depending on python [02:12] heh [02:12] * wgrant likes that idea. [02:12] you'd probably make a lot of sysadmins very happy [02:14] ...or mad. [02:14] No, you'd make developers mad. [02:15] Well, and those few sysadmins that already got bullied into isntalling some unofficial php5.3 package. [02:16] because their developers needed goto? [02:16] well, because their developers are mad and interrupting their sleep [03:12] pitti: Ok, I have found which event device is for my touchpad using lsinput and input-events, so its fine at the kernel level. Seems hal is not picking it up properly, here is the lshal block for the touchpad. http://paste.ubuntu.com/211657/ [03:21] does it work when you rmmod psmouse && modprobe psmouse? [03:22] i've been having to boot with i8042.reset=1 since around 2.6.30-git13 for mine to get detected as a touchpad instead of a generic mouse every other boot [03:23] they added a quirk to always do that for my machine in dtor's input tree but it hasnt hit linus' yet [03:24] * ScottK opines we could use some new developer with the energy for reviewing backports requests ... [03:24] http://git.kernel.org/?p=linux/kernel/git/dtor/input.git;a=commit;h=9230ccb1071d2d7e4ecb6314e67203b9f7f08140 [03:25] Sarvatt: Its USB. [03:25] psmouse is PS/2 only. [03:26] Sarvatt: And, I wouldn't even get feedback from my finger on the touchpad using input-events if the driver weren't loaded or loaded properly. [03:29] Wow. [03:30] Whoever sponsored network-manager-openvpn did not test it at all. [03:30] cody-somerville: does it take out NM? [03:31] ajmitch, The binary is almost empty [03:31] ajmitch, Just has the /usr/share/doc/ stuff [03:31] that's a bit odd [03:31] though the problem with sponsoring is usually how much you can test things are sane [03:32] They should have atleast done dpkg-deb -c on the deb [03:32] Although, when I sponsor I will at least check things built correctly [03:36] pitti: Seems I can't use suspend/hibernate from the logout menu, or run the gpm preferences as well. Not sure what I am looking for in lshal's output unfortunately, so more guidence will be needed. :) [03:39] * cody-somerville fixes network-manager-openvpn. [03:41] cody-somerville: looks like it may be something as simple as debhelper compat level [03:42] ajmitch, That was my first thought [03:42] Its actually DEB_DESTDIR in rules [03:42] at least the build log shows files going into debian/tmp, so it's just not picking them out of there [03:42] ok [03:42] ajmitch, There is no $package.install file [03:42] a minor omission [03:42] so DEB_DESTDIR needs to be $(CURDIR)/debian/network-manager-openvpn/ and not DEB_DESTDIR = $(CURDIR)/debian/tmp/ [03:52] debian/tmp is debhelper compat level 1 and 2! [03:53] Hrm? I get stuff in debian/tmp with debhelper 7, if I do it right. [03:53] StevenK: it's come back to haunt you [03:54] StevenK: the debhelper manpage lists it as a new fallback in 7 [03:56] Argh! [03:56] Noooooo! [03:56] StevenK: embrace the evil [03:56] Noooooo! [03:57] If I don't have commit access to a universe package that is managed in bzr, does that mean I'm not allowed to upload? [03:57] I've created a branch merge proposal [03:57] you're technically allowed to, I suppose, but it'd be polite to at least do a merge proposal [03:57] which you've done [03:57] cody-somerville, Rather it means you should complain to whoever controls the bzr resource. I'd suggest uploading, and submitting a merge request [03:58] * cody-somerville nods. [03:59] No point trying to fix access rights now, as everything will change with package branches. [03:59] What? Why? [04:00] Package branches are meant to get a flag to grant write access to uploaders. [06:05] Good morning [06:07] Morning pitti. [06:07] lool: thanks, no prob [06:08] ion: see /topic and u-d-a@; gdm upgrade is known to fail, unfortunately there's nothing to fix :( [06:09] does that include losing the app bubbles on lower gnome pane by chance pitti [06:09] gnomefreak: it breaks gdm pretty much completely [06:10] s/pane/panel [06:10] you _need_ to install it in screen, or a VT [06:10] oh [06:10] pitti: thanks [06:11] but it's only breakage for those of us silly enough to run karmic on our desktops already :) [06:11] TheMuso: can you please ubuntu-bug hal and add lsinput output? I'll take a look then and fix it upstream (please assign the bug to me) [06:12] TheMuso: no suspend/hibernate is a separate problem; sounds like gnome-power-manager isn't running; I uploaded a new one last night, does that work? [06:12] pitti: Probably haven't got it yet, due to keeping local mirror whic updates daily. I'll refresh it and try again. [06:13] TheMuso: is gnome-power-manager running? (pidof) [06:13] pitti: ok will file a bug ASAP. [06:13] pitti: Machine is currently not runing, just a sec. [06:13] *running [06:13] ah [06:13] its my notebok [06:14] gah bad typing this afternoon. [06:15] pitti: no its not running. [06:15] * TheMuso refreshes his local mirror. [06:15] TheMuso: if you start it from a shell with --verbose, what does it say? [06:15] pitti: I was commenting about the link in the topic. It says “Press Ctrl+Alt+F7 to get back to the graphical login manager” where it should say “Run sudo /etc/init.d/gdm start to get back to the graphical login manager”. :-) [06:15] TheMuso: do you have devicekit-power 009? [06:15] ion, Ctrl+Alt+F7 also works... [06:15] ion: oh, ok; thanks [06:16] but it should start automatically (did for me) [06:16] persia: Not very well if gdm isn’t running. [06:16] pitti: yes I have that version of devicekit-power [06:16] just a sec I'll pastebin the gnome-power-manager output. [06:16] TheMuso: and gnome-power-manager 2.27.1-0ubuntu4? [06:16] Ah. I have an issue with gdm running too much, rather than not enough, Perhaps slightly different. [06:16] pitti: gpm is ubuntu3, I'll refresh and try again. [06:16] s/refresh/update/ [06:17] pitti: 2.26.1-0ubuntu2 prerm ran gdm stop, 2.26.1-0ubuntu3 postinst ran gdm reload. gdm reload doesn’t seem to start gdm if it’s not running in the first place. [06:17] persia: after an upgrade from 2.20? should also be fixed now [06:17] TheMuso: right, known; 0ubuntu4 should fix it [06:17] pitti, Hrm. Wasn't fixed about 5 hours ago, but I'll admit not to having logged in again since then. [06:18] pitti: ok thanks. [06:18] persia: I only fixed 2.20 (jaunty) -> 2.26 upgrade [06:18] persia: if you have a different problem about "running too much", we need a new bug report, I think [06:18] Right. I'll upgrade, and try a new login test in an hour or so. [06:21] Gdm for me dies a random time after I log in, based on the amount of activity. Once I log in for a second time, things don't die till I reboot. [06:22] That's close to my bug, but my death was always within a second or two. [06:22] (or at least a fresh invocation occurred within that time) [06:23] persia: Right. [06:28] pitti: So, this UNR MIR bug is getting confusing. I'd like to set the packages to a status when I've commented with a MIR, but it hasn't been checked yet -- what Status do you suggest? (And could you check one or two of the simple ones, like go-home-applet) ? [06:40] StevenK: I'd use "incomplete" for the ones which still need an MIR [06:41] StevenK: yes, we discussed how to handle the backlog and assign it to MIR folks, I'll do that today [06:41] pitti: So, Incomplete if they need one written, and New if they're good? [06:42] pitti: Do I need an MIR for unr-meta itself? :-) [06:42] StevenK: unr-meta> nope, just add a task [06:42] StevenK: right (states) [06:43] * pitti -> i915 debugging, brb [06:43] Hrm. I think update-grub needs to be made a dpkg trigger. [06:45] pitti: What about ubuntu-netbook-remix-default-settings? It's trivial, effectively a bunch of gconf defaults [06:46] * TheMuso files a bug [06:46] TheMuso, There's some trickiness in handling update-grub and/or update-initramfs singly and in combination: it may be a bit before anyone can fix it (it's not as simple as one might think) [06:47] persia: Right, but I'll file the bug anyway. [06:47] So its on the radar. [06:49] pitti: Yep, latest gpm works fine. [06:51] TheMuso: gpm, or gdm? [06:51] They are two different things :-) [06:52] StevenK: gnome-power-manager to be precise. [06:54] TheMuso: Ahhh. I was thinking the console mouse thingy [06:55] StevenK: for stuff like this, just add a task and set it to "new" [06:57] StevenK: ah ok. [06:59] pitti: Already done. [07:51] good morning [07:52] StevenK: do you guys still need bug 219087 (moblin-applets)? [07:52] Launchpad bug 219087 in libmokoui2 "MIR for moblin-applets" [Undecided,Fix released] https://launchpad.net/bugs/219087 [07:52] hey dholbach [07:52] hiya pitti [08:09] pitti: Nope. [08:09] pitti: Kill it. [08:09] StevenK: done (timed out) [08:10] pitti: Hehe, answer quickly or your MIR gets it? [08:10] StevenK: where "quickly" is "within half a year", yes :) [08:10] and you can always reopen if you still want/need it === azeem_ is now known as azeem [08:21] is there a reason turnkey linux and ubuntu/canonical websites look nearly identical in theme / layout? === tkamppeter_ is now known as tkamppeter [08:31] pitti: Fix Commited for unr-meta makes it nervous, it means component-overrides will explode. [08:31] s/it/me/ === Tonio__ is now known as Tonio_ [08:32] StevenK: c-mismatches doesn't look at MIR bug states [08:32] StevenK: it means "approved, but not promoted yet" [08:32] pitti: Oh, right. I'm happy to go through and promote things in one huge lump after it's all done [08:32] StevenK: I think we should move them over in one batch, with unr-meta [08:33] pitti: Works for me. [08:33] pitti, My apologies. While I could reproduce the gdm-appears-twice issue, I've just had a disk failure on the affected machine, and can't file the bug with ubuntu-bug. GIven the other issues, it may be that the problem is not software-specific. [08:34] persia: good to hear from a gdm perspective, but I'm sorry for your broken hw; good luck with getting it fixed! [09:22] slangasek: depends on g++, and g++ depends on gcc [09:27] directhex: can you tell me where in http://www.microsoft.com/interop/cp/default.mspx is ECMA 334 listed please ? Cant find it [09:30] pitti: re the jinja2 mir: sorry that I missed the pybabel reverse-recommends. should it be dropped from jinja2 as jinja2 is mostly used as a build-dependency and recommends don't get installed during build or should I add a mir for pybabel? [09:31] I did a quick try to use jinja2 in pygments but failed at first, perhaps I should try a little bit harder [09:31] mvo: I have a question about the DH_PYCENTRAL=include-links change in the xapian-bindings package [09:32] mvo: I was going to slot it into the Debian packaging, to avoid having an Ubuntu diff, but I'm unsure exactly what it does, and so what it should be conditional on, if anything... [09:39] geser: pybabel> not sure what it is used for, does python-ninja2 import it? [09:47] pitti: skimming through the source jinja2 has an i18n extension which can use gettext or pybabel for translating a webpage [09:47] geser: ah, the pygment Debian maintainer replied, he'll do the transition [09:48] geser: sounds like it could become a suggests then [09:52] pitti: should I do an upload with this change? recommends -> suggests [09:53] geser: please do [09:53] geser: closed python-babel task [09:57] % tail -n 1 data/desktop-switcher.desktop.in [09:57] X-Ubuntu-Gettext-Domain=desktop-switcher [09:57] pitti: ^ [09:58] \o/ [09:58] StevenK: that's hardcoded upstream? (eww) [09:58] pitti: Therefore, I have nothing to do. [09:58] StevenK: ok, please set back to new then [09:58] pitti: Upstream is effectively njpatel. :-) [09:58] it should at least be X-GNOME-* [09:58] anyway, good enough [09:59] pitti: I can get s/Ubuntu/GNOME/ to happen upstream, easy enough [09:59] pitti: desktop-switcher task thrown back to New [09:59] thanks === asac_ is now known as asac [10:10] StevenK: webfav. who will take care that this will work with ffox 3.5? [10:12] asac: I'll talk to Bill Filler about that. [10:12] StevenK: ok so he is the primary contact? [10:12] ojwb: hi! the include-links means that python-central does less magic in its maintainer scripts by doing all the symlinking at build time instead of install time [10:13] asac: Yes, he's who I would talk to about it. [10:13] StevenK: ill open a bug and assign it to him [10:13] ojwb: so it adds robustness and it also means that the package is immediately useful when installed/upgraded (as opposed to the default behavior where the .py files are only available after --configure and not in --unpack) [10:14] mvo: OK, but should that only happen for Ubuntu? and if so, should it only be for Ubuntu karmic and newer or what? [10:14] ojwb: I think it would be a good addition in debian too, personally I think include-links should the default [10:14] * ojwb saw something about it requiring rebuilds for newer python versions [10:14] for all of python-central [10:14] though that's clearly not a frequent issue [10:14] yeah, that is the drawback [10:15] but for me (robustness + available on unpack) > a rebuild every ~18 months :) [10:15] seems reasonable to me [10:17] ojwb: thanks! (and thanks for the backport of the set_data() change from 1.1 to 1.0 for enrico) [10:17] cjwatson: FYI, the other day you asked me about disabling automount of internal disks; I located the problem now (bug 396448), working on it now [10:17] Launchpad bug 396448 in devicekit-disks "internal partitions get automounted on startup" [High,Triaged] https://launchpad.net/bugs/396448 [10:19] mvo: no problem - let me know if it throws up any issues [10:19] asac: Oh, subscibe me to the bug? [10:19] if not, it should be in 1.0.14 [10:20] mvo: hmm, presumably that wants to go in karmic... [10:20] pitti: could you please sponsor http://www.bienia.de/tmp/jinja2.debdiff ? I wasn't fast enough to upload it before it got promoted. [10:21] oh, sorry [10:21] ah, feature freeze is aug 27th, so that's ok [10:21] ojwb: when is 1.0.14 scheduled? [10:21] this month [10:21] for what date I mean [10:21] great [10:21] that should work then :) [10:21] yeah [10:21] it could slip to august, but not by all of august [10:22] geser: done, thanks [10:22] ojwb: is the patch isolated enough to put it into the ubuntu 1.0.13 so that we can give it some early testing ? would that help you guys? [10:23] it's isolated enough, and probably would [10:23] esp if you're happy to nursemaid 1.0.14 in, since it would then have an ubuntu diff to resolve [10:25] Keybuk, Hobbsee: what did you do to get gdm started on vt1? [10:26] ojwb: ok, that should be fine, I have a look at the upstream svn log [10:26] pitti: i turned on the machine, selected the kenel in gdm, and waited for it to boot. ie, nothing different. [10:26] pitti: when I did the demo hack? a cross hack? [10:26] but that was old gdm code [10:27] Keybuk: in the context of bug 396226 [10:27] Launchpad bug 396226 in gdm "GDM logs out after some minutes of typing on the keyboard" [Medium,Incomplete] https://launchpad.net/bugs/396226 [10:27] seems everyone there has gdm start on vt1 initially, and on vt7 the second time [10:27] ojwb: its r12994? [10:28] * ojwb looks [10:29] no, that's the trunk version, which won't apply to 1.0.x [10:29] http://oligarchy.co.uk/xapian/patches/xapian-flint-lazy-update-backport-for-1.0.patch [10:29] I haven't commited that to the 1.0 branch yet [10:30] that's the patch Enrico tested [10:30] ojwb: ok, thanks! [10:30] pitti: oh, it just does that by default [10:30] hmm [10:31] we want it on tty1 by default though, don't we? :) [10:31] well, sure, but we didn't do that switch yet, anywhere I could see? [10:31] I suspect new gdm simply behaves that way out of the box [10:31] anyway, I bet I can guess what causes the crash now [10:31] FirstVT=7 [10:31] StevenK: filed, assigned upstream to bfifller and packaging task to you. 396453 [10:31] ^ in /etc/gdm/gdm.conf for me [10:32] Keybuk: do you have "1" there? [10:32] Hobbsee: ^ [10:32] pitti: no, 7 - but that's the old gdm configuration file, no? [10:32] mvo: comments on my reply? [10:32] enrico: I'm just in the middle of writing it :) [10:32] Keybuk: current gdm still ships it, and settings like autologin still work [10:33] mvo: \o/ [10:33] pitti: it doesn't mean it supports vt allocation, etc. === pbn_ is now known as pbn [10:34] I expect what's causing that bug is [10:34] gdm is on tty1 [10:34] so it could be the missing ConsoleKit patch in bug 375877 [10:34] getty is on tty1 [10:34] Launchpad bug 375877 in consolekit "Move *dm to VT1" [Undecided,In progress] https://launchpad.net/bugs/375877 [10:34] pitti: 7 here too [10:34] Keybuk: so getty and gdm collide? [10:34] so getty will get random raw input as you type [10:34] which getty will interpret as a klingon trying to login [10:34] right, that'd explain the weird characters people saw [10:34] after a few minutes, it'll timeout that login and exit() [10:34] upstart will respawn getty on tty1 [10:34] Ahaha. That explains everything. [10:35] that would do it [10:35] at which point getty will call TIOCSCTTY to claim ownership of the tty [10:35] and X will lose control of the tty [10:35] Keybuk: so we just need to drop the getty on vt1? [10:35] and shamelessly exit [10:35] pitti: my hunch is that if you reboot, and quickly "sudo stop tty1" - you won't get auto-logged out [10:35] enrico: be patient with me :) I want to try some of the code (like the different scan-the-database code) in order to figure out what performance charackteristis to expect [10:36] so I still wonder why gdm starts on vt7 for me right away [10:36] I'm using xorg-edgers, but this hardly sounds like something that X itself would do? [10:36] pitti: interestingly, AutoLogin is broken for me [10:36] I had auto-login enabled [10:36] but after upgrading to new gdm, it doesn't work anymore [10:36] enrico: but I really hope we can get something like "--quick-update" method that takes around the order of ~4s (on my system) so that ideally we could just run it after every apt-get update [10:36] (or at least daily) [10:36] Keybuk: try moving /etc/gdm/gdm.conf-custom to /etc/gdm/custom.conf ? [10:37] pitti, how do you see where gdm is starting with autologin? [10:37] Keybuk: current package does that automatically, but if you had ubuntu[23] installed that migration was broken [10:37] pitti: how will that help? [10:37] the AutomaticLogin=scott is in /etc/gdm.conf for me [10:37] Keybuk: gdm reads custom.conf now, not gdm.conf-custom [10:37] Keybuk, the autologin option is set there [10:37] seb128_: well, I do ctrl+alt+f1 -> VT with getty, ctrl+alt+f7 -> gdm [10:38] Keybuk: auto-login still works for me with the new gdm [10:38] geser: how/where is it configured? [10:38] my /etc/gdm.conf has AutomaticLoginEnable=true \n AutomaticLogin=scott [10:38] and it doesn't [10:39] oh, it could be a race condition [10:39] pitti, I've gdm on no vt with autologin it doesn't seem to keep a greeter after login [10:39] both gdm and getty are started on boot, and whichever gets there first gets it, I suppose [10:39] Keybuk: ^ would that work? [10:39] weirdly, I have TimedLoginEnable=true as well [10:39] Keybuk: http://pastebin.ubuntu.com/211805/ that's my /etc/gdm/custom.conf [10:39] my session is on vt7 [10:39] geser: why is it in custom.conf not gdm.conf? [10:39] seb128_: right, but if nobody is logged in [10:40] Keybuk: because the new gdm sucks wrt. backwards compatibility :( [10:40] Keybuk: I put it there (had it in gdm.conf-custom till now) [10:40] pitti: right, but I'm confused [10:41] there are THREE configuration files [10:41] as I didn't want to change the gdm.conf [10:41] you're tell me to move it from config file A to B [10:41] and I'm saying my config is in config file C [10:41] not A or B :) [10:41] Keybuk, we used to use gdm.conf-custom and pitti renamed to custom.conf now [10:41] which are both identically empty [10:41] which is the upstream naming [10:41] Keybuk: gdm should really also read gdm.conf indeed [10:41] mvo: ok, I like that. Forcing it to be fast, and if anything would hint at too much work to do, just do nothing [10:41] seb128_: again, you're not listening [10:41] Keybuk, gdm.conf is upstream default, custom.conf your user changes [10:41] my AutomaticLoginEnable=true is not in gdm.conf-custom *OR* custom.conf [10:41] it's in gdm.conf [10:41] I'm wondering why it's there [10:42] because you did edit it at some point§? [10:42] Keybuk: you selected that in the installer? [10:42] pitti: yes [10:42] ubiquity used to set it in gdm.conf directly [10:42] iz ubiquity bog [10:42] this was installed with "Automatic Login" checked in the installer [10:42] ah [10:42] now [10:42] could *this* be causing the problem? [10:42] has the config migration ended up with a mangled config file that gdm isn't reading anymore? [10:42] Keybuk: I suppose that's it; gdm is not reading these settings from gdm.conf [10:42] it could [10:42] right, what I said above [10:42] and thus gdm isn't reading VTallocation=true [10:43] so this would explain both why autologin doesn't work [10:43] and why gdm is on tty1 ? [10:43] gdm.conf:FirstVT=7 [10:43] gdm.conf:VTAllocation=true [10:43] but I have exactly the same here [10:43] pitti: yes, I have that [10:43] what I'm suggesting is that the gdm.conf changes have been mangled in such a way that gdm is refusing to read *the entire file* [10:44] d6e74831651b44a9fee800f3af7e2093 gdm.conf [10:44]