/srv/irclogs.ubuntu.com/2013/02/18/#ubuntu-installer.txt

xnoxmpt: we have a keyboard bug for every step of the installer09:54
xnoxhttps://wiki.ubuntu.com/Ubiquity/KeyboardBug#preview09:54
xnoxhttps://wiki.ubuntu.com/Ubiquity/KeyboardBug09:54
mptjoy10:35
xnoxYeah, it's like christmas came early =)10:39
xnoxThe best bit is when people need/want to switch to English after booting in e.g. russian locale at every single step.10:40
mptxnox, do you happen to have a screenshot of the 12.10 installer with the wi-fi spinner at the bottom left?11:06
xnoxmpt: no, as I failed to type my 63 character long WiFi correctly to trigger the spinner.11:08
xnoxs/WiFi/WiFi password/11:08
* xnox can fake a screenshot for you though.11:08
xnoxmpt: https://picasaweb.google.com/105922848292507689403/February182013#584625579132723531411:42
xnoxnexus7 saves the world again11:42
ogra_xnox, erm, how did you get that working ?11:45
xnoxogra_: which part? =)11:45
ogra_the whole of it11:46
ogra_how did you work around my bug ?11:46
xnoxogra_: so my old nexus was already pre-flashed, I $ sudo apt-get install oem-config-gtk etc... & sudo touch /var/oem-config/run & reboot11:46
xnoxit just works.11:47
ogra_hmpf11:47
ogra_why doesnt it on fresh images then11:47
xnoxi may not be fully up to date then.11:47
xnoxdo you want me to dist-upgrade and see if it breaks? =)11:47
ogra_yes please :)11:47
* ogra_ is a little desparate to find *any* pointer to whats wrong11:50
mptxnox, excellent, thank you11:54
mptdiscussing this layout pattern right now11:54
xnoxogra_: dist-upgrade, reboot, had plymouth splash and now just black screen with nothin on it.12:06
xnoxhere is the dpkg view of my dist-upgrade: http://paste.ubuntu.com/1676722/12:06
ogra_YAY !!!!12:06
xnoxgrep for upgrade12:06
xnoxand install12:07
ogra_sigh, 164 packages12:07
* xnox was spending time fixing background which now works =) and not dist-upgrading12:07
xnoxogra_: how can I boot it now?12:09
ogra_remove the lock12:09
ogra_that sometimes works12:09
ogra_i havent found a reliable way yet, it seems to be very random12:10
ogra_do you have an ssh server installed ? probably the logs on an installed system are more verbose12:11
xnoxyeap ssh'ed in.12:11
xnoxFatal server error: Server is already active for display 012:11
ogra_yeah12:11
ogra_complaining about the lock, as well, right ?12:12
ogra_thats all i can get ... i wish there was an ~.xession-errors for u-dm12:12
xnoxright in syslog I see the same stuff as currently seen in the daily desktop images with "Failed to activate service 'org.freedesktop.ConsoleKit' timed out12:13
xnoxand consolekit failing to acquite the bus12:14
* xnox wonders if the first X is started ubiquity-dm, then ubiquity-dm fails, and respawns a new X without cleaning the lock.12:15
xnox(killing the first instance)12:15
ogra_yes, thats one of my three theories12:16
ogra_the most compelling one actually ... else it would be lightdm or upstart which is unlikely12:16
ogra_thats why i would like an .xsession-errors file12:16
ogra_since i guess one of the fired up apps u-dm uses is at fault here12:17
ogra_and oem-config-debug sadly only kicks in after oem-config is up12:17
xnoxit's weird because there is console-kit-daemon running with pid 965, yet the one that failed to activate has pid 126312:18
xnoxso it failed to talk to it.12:18
ogra_hmm12:18
ogra_i see qdbus in your upgrade list12:19
ogra_nothing about consolekit or polkit12:20
ogra_theoretically there is an Xsession.d script that firse up the appropriate ck session for you12:21
ogra_(unless you use lightdm)12:21
ogra_http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=68026412:22
ubot2Debian bug 680264 in nodm "nodm: ConsoleKit fails to recognize the current session as local" [Normal,Open]12:22
ogra_i wondefr if thats related12:22
ogra_it has a patch to try out12:23
xnoxthere were some pam changes12:23
ogra_also, slangasek seems to have moved soem pam stuff around in lightdm from "auth" to "session" that tries to read /etc/default/localer ... which doesnt exist in our installer env12:24
xnoxalso ubiquity launches X directly does that read / launch xsessions?12:24
ogra_though you should have it on an installed system indeed12:24
ogra_i think it does, not sure12:24
ogra_hmm, it doesnt launch xinit but plain X12:24
ogra_so Xsession might ot be processed12:25
ogra_once my nx7 is charged enough i'll try your method ... it didnt strike me to test on an installled system12:26
mptehhhh12:26
xnoxmpt: did you just read the backlog? =) or is that the comment on the font/spacing alignment of the connecting label?12:27
mptxnox, I'm in a meeting where we're talking about bug 732634 for the umpteenth time :-]12:28
mptas if it was ever a deliberate design choice12:28
ogra_or just a general statement to the evilness of the world ?12:28
ubot2Launchpad bug 732634 in ubiquity (Ubuntu) "Progress bar restarts from zero after copying files" [Medium,Confirmed] https://launchpad.net/bugs/73263412:28
xnoxmpt: refresh the bug report, does that help?12:29
mpt\o/12:31
cjwatsonThat bug is darkly amusing since it has comments like "The proper solution is apparently to teach debconf that its progress value is sometimes only for a subtask of a larger task" several years after such support was introduced12:32
cjwatsonIt's just broken, it's not fundamentally missing12:32
cjwatsonxnox: Do you know about and understand the PROGRESS REGION extension?12:33
xnoxcjwatson: know about - yes, understand - sort of.12:33
cjwatsonYour bug reference is incorrect - nested progress bar support was introduced long before that12:34
cjwatsonBefore espresso was renamed to ubiquity12:34
cjwatsonr799, originally12:34
ogra_geez, installing oem-config-gtk tries to pull in nearly all of kde here12:35
ogra_even with recommends disabled12:35
xnox=)))) well, ok that it even early, for me at that time it was good enought that _it exists today_12:35
xnoxogra_: install oem-config-gtk ubiquity-frontend-gtk12:35
xnoxand oem-config and ubiquity then it's a short list.12:35
ogra_yep, just did that :)12:35
xnoxit is trying to pull in the kde frontend for some reason, instead of the gtk one.12:36
cjwatsonxnox: The idea is that you say PROGRESS REGION <start> <end>, then PROGRESS START <start> <end> <title> ... (more progress commands) ... PROGRESS STOP, and the progress commands within the start/stop pair are scaled to the region you provided12:36
cjwatsonIIRC12:37
cjwatsonSo have a look at the protocol stream and see what's doing it wrong12:38
xnoxok. thanks. debug mode logs again =))))12:39
cjwatsonThat's what they're for :)12:39
xnoxcjwatson: i think we are missing some progress regions then, as if one does progress start 0 without starting a new progress region you see the jump to zero effect.12:40
ogra_1405 ?        S      0:00 /usr/bin/python3 /usr/bin/ubiquity-dm vt7 :0 oem /usr/sbin/oem-config-wrapper --only12:40
ogra_ 1431 ?        S      0:00 sleep 112:40
ogra_ 1432 ?        Z      0:00 [Xorg] <defunct>12:40
cjwatsonYep, very likely12:40
ogra_aha12:40
ogra_i wonder wheer that zombie comes from12:40
cjwatsonShould be a pretty trivial fix once identified12:40
xnoxogra_: in ubiquity-dm we have a loop of trying to start X server and if it fails so many times, we try fail-safe config.12:41
ogra_yeah, i had that at some point during my tests12:41
ogra_i wish there would be any indicator in any log though ...12:41
xnoxogra_: it's python - so just type in more logging =)12:42
* ogra_ digs into the dm and scatters soem prints over it12:42
xnoxogra_: anything in /var/crash/ ?12:50
ogra_wait, just rebooting12:50
ogra_http://paste.ubuntu.com/1676848/12:54
ogra_definitely CK12:54
xnoxogra_: can you grep if there are any console-kit daemons running any way?12:55
xnoxin ps.12:55
ogra_i wonder if we should just switch to process Xsession12:55
xnoxcjwatson: why ubiquity-dm has never been a proper Xsession?12:55
ogra_ogra@nexus7:~$ ps ax|grep console12:55
ogra_  956 ?        Sl     0:00 /usr/sbin/console-kit-daemon --no-daemon12:55
xnoxso it's failing to talk to it.12:56
* xnox ponders to try that debian patch or see/revert recent slangaseks pam changes.12:56
ogra_well, i think it is started in the wrong order12:56
xnoxogra_: the first thing ubiquity-dm does is ask for a console-kit session, which should dbus activate it.12:57
ogra_yes, but it doesnt take care for starting it12:57
ogra_which usually Xsession woudl do12:57
xnoxso who started the one that is running?!12:57
cjwatsonxnox: Too much effort to excise all the bits we wanted to avoid12:57
cjwatsonThere were memory constraints and the like - I explicitly didn't want to run a full session12:58
cjwatsonOr a full DM12:58
xnoxok.12:58
cjwatsonI mean I guess you could split ubiquity-dm into a DM part and a session part.  It just never seemed worth the effort really12:58
ogra_well, with the recent diet lightdm might serve out purpose12:59
cjwatsonubiquity-dm can't rely on lightdm12:59
ogra_hmm, indeed flavours ...12:59
cjwatson'cos it needs to be workable in lots of different flavours, yeah12:59
ogra_oh13:00
ogra_erm13:00
ogra_seems teher is no session dbus at all running here13:01
ogra_i would assume thats needed for ck to talk to the system bus through it13:01
xnoxbut we are starting on lightdm, which in turn starts on dbus.13:03
ogra_system13:04
ogra_not session13:04
ogra_the session bus is started by gnome-session or alternatively by Xsession13:04
xnoxupstart jobs that is.13:04
xnoxah, wait.13:04
ogra_it runs as the session user usually13:04
ogra_so after auth13:04
* xnox thought ck runs on system bus, not session.13:05
* ogra_ tries to mimic the Xsession behavior in the oem-config.conf exec line 13:05
xnoxcause ck is opened before ubiquity-dm starts a session bus13:05
ogra_the point is that to talk to system services the session bus is used i think13:06
ogra_with ck inbetween for policy checks13:06
* ogra_ reboots with the hack in place13:08
ogra_bah, patched the wrong codepath13:11
ogra_hmm, so i have it starting with a session bus but it doesnt change anything :(13:18
ogra_oh, lovely ... at least i can count how often it respawned now13:19
* ogra_ moves the code around a bit13:22
ogra_GOT IT !!!13:34
ogra_bah, only partially13:34
ogra_changing the exec line in oem-config.conf to:13:35
ogra_exec /usr/bin/ck-launch-session oem-config-firstboot $debug $automatic13:35
ogra_gets me running X and a popup that the installer encountered an error on the desktop13:35
ogra_aha13:36
ogra_dbus.exceptions.DBusException: org.freedesktop.NetworkManager.Settings.NotPrivileged: Insufficient privileges.13:36
ogra_thats funny ...13:36
ogra_since i have NM in the panel13:36
* xnox reverted lightdm, consolekit and it boots now13:37
* xnox ponders if consolekit's memory leak wasn't actually a memory leak.13:37
ogra_oh, i created an oem user for testing ... i guess i should swithc that back to root as we use it on the image13:39
ogra_yipiie13:42
xnoxyou fixed it? =)13:42
ogra_ogra@nexus7:~$ grep exec /etc/init/oem-config.conf13:42
ogra_    exec /usr/bin/dbus-launch --exit-with-session /usr/bin/ck-launch-session oem-config-firstboot $debug $automatic13:42
ogra_with that it works for me13:43
xnoxit also needs to go into ubiquity normal as it also fails with ~ similar symtoms.13:43
xnoxand this also means we can drop dbus-launch code from ubiquity-dm13:43
ogra_well, i still think it would be better to just process Xsession.s13:43
ogra_Xsession.d13:43
xnoxmy boot was a fluke as it is back to booting black.13:46
ogra_hmm13:48
ogra_none of the indicators work ... i can select reboot but never get the popup for it13:48
ogra_so i would guess its not 100% yet13:48
ogra_btw, the panel doesnt expand in landscape13:52
xnoxogra_: so poking indicator-session-service it's sitting on the dbus that lightdm has, instead of ours.13:53
ogra_ah13:53
ogra_thats a mess13:53
* ogra_ is so happe we found the cause and at least a workaround ... i wated my whle weekend on this (including my birthday on sat.)13:54
ogra_*happy13:54
ogra_*wasted13:55
xnoxogra_: looking at all the Xsession.d scripts some of them are definately what we do not want.14:23
ogra_hmm, yeah14:24
=== zequence_ is now known as zequence

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!