[00:07] does anyone know when a good time to catch macslow might be? [00:07] when he's awake & on irc. that's a good start [00:08] thanks [00:08] DBO, he's in germany [00:08] mmmm, probably sleeping... [00:08] so mon-fri 9-17hs UTC aprox [01:32] asac: I've just run across bug #331849; you were the last commenter on it. It's the reason people are still hitting bug #331311. Basically, notify-osd should be installing those icons in the hicolor theme, rather than them being shipped in Human. [01:32] Launchpad bug 331849 in notify-osd "Notify-osd icons should be installed for hicolor" [Undecided,New] https://launchpad.net/bugs/331849 [01:32] Launchpad bug 331311 in gnome-settings-daemon "volume notifications are all black" [High,Fix released] https://launchpad.net/bugs/331311 [03:00] how to join the team? [03:00] What team? [03:01] i mean the developers [03:01] By doing packaging work. [03:01] !motu [03:01] motu is short for Masters of the Universe. The brave souls who maintain the packages in the Universe section of Ubuntu. See http://wiki.ubuntu.com/MOTU [03:01] Is what you want to see. [03:01] Also... [03:01] !gettingstarted [03:01] A great place to start your MOTU adventure is https://wiki.ubuntu.com/MOTU/GettingStarted [03:02] thanks :D === abc2xyz is now known as a2z === pgraner__ is now known as pgraner === jldugger_ is now known as jldugger === maco_ is now known as maco [06:08] good morning [07:43] Good morning [07:44] calc: 332578> good idea, will look at it [07:44] morning pitti [07:45] slangasek: could you please ack/nack bug 326989 ? [07:45] Launchpad bug 326989 in libopenobex "FFE: Please update to 1.5 in Jaunty" [High,In progress] https://launchpad.net/bugs/326989 [08:19] kirkland: oh, I just saw screen-profiles the first time, nice! however, is it really intended to always show that menu when you run "screen"? [08:19] kirkland: I'd expect it to come up only the first time [08:20] kirkland: also, F3/F4 don't work for me, do they for you? [08:20] kirkland: nicely done! [08:21] pitti: last time I checked, the menu came only once and F3/F4 were working properly [08:22] kirkland, Koon: hm, I have [08:22] -rw-r--r-- 1 martin martin 0 2009-02-23 09:18 .screenrc [08:23] maybe it isn't supposed to be empty? I'm fairly sure it only got created this morning [08:23] yes, confirmed, it's not in yesterday evening's backup [08:28] pitti: ah, *that* menu [08:29] pitti: it's a new one, and I agree it's a little painful [08:29] pitti: F3/F4 work here though, once you created a new tab with F2 [08:31] Koon: hm, I only tried it under X, and still doesn't work for me [08:31] pitti: the 0-sized .screenrc is apparently normal [08:37] pitti, kirkland: I experience the same. https://bugs.launchpad.net/ubuntu/+source/screen-profiles/+bug/333180 [08:37] Ubuntu bug 333180 in screen-profiles "screen-profiles menu appears always I run screen" [Undecided,New] === hunger_t is now known as hunger [08:56] didrocks: you uploaded a totem that build-depends on a gtk-doc-tools newer than what's in the archive; any plans to upload that too? [08:57] slangasek: I requested a sync request and FFe [08:57] let me find it [08:58] slangasek: bug #331201 [08:58] Launchpad bug 331201 in gtk-doc "Please sync gtk-doc 1.11-3 (main) from debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/331201 [08:59] didrocks: ah didn't notice that you needed sponsorship, ok [08:59] thanks, I'll have a look at that [09:01] * slangasek reads the very bottom of the bug description and coughs, realizing he should have already known about this ;) [09:02] slangasek: thanks a lot :) [09:02] slangasek: yeah, I am just a MOTU, not a core-dev :) [09:08] kirkland: another one on screen-profiles: https://bugs.launchpad.net/ubuntu/+source/screen-profiles/+bug/333180 [09:08] Ubuntu bug 333180 in screen-profiles "screen-profiles menu appears always I run screen" [Undecided,New] [09:08] kirkland: I meant https://bugs.launchpad.net/ubuntu/+source/screen-profiles/+bug/333189 [09:08] Ubuntu bug 333189 in screen-profiles "Selecting the plain profile might confuse the user when trying to change the configuration" [Undecided,New] [09:20] a|wen: why is kile building a -dbg package in Ubuntu? Is this a change pulled from the Debian svn tree? [09:21] slangasek: we've upgraded to an svn snapshot of the kde4 version ... so right now we are ahead of debian in that sense [09:22] a|wen: so why are we building a -dbg package? [09:23] slangasek: for the same reason we are building kde*-dbg packages... is there any good reason not to build it? [09:25] a|wen: because it should be redundant relative to our automatically-generated -dbgsym packages [09:25] a|wen: which are stored in a dedicated archive, where they don't take up space on the mirrors [09:26] a|wen: -dbg packages are tolerable as a lesser evil when they're synced from Debian; but I don't see any reason we should be creating new ones in Ubuntu [09:27] so I'm inclined to reject these packages out of binary NEW [09:27] slangasek: i see; as it is a kde4 app, i was mostly just looking at how the other kde4 applications was made [09:28] slangasek: i think the package is already in the archive (the 0ubuntu1 version is there) [09:28] the binaries aren't [09:28] can you upload a -0ubuntu3 version dropping the -dbg package? [09:29] slangasek: yeah, no problem [09:29] ok, thanks :) [09:30] i can't upload myself, but maybe you'll be keen on the debdiff? [09:30] a|wen: sure [09:38] slangasek: http://awen.dk/packages/kile/kile_2.1~svn20090217-0ubuntu3.debdiff [09:39] a|wen: :) [09:41] a|wen: uploaded, thanks! [09:42] slangasek: no problem; thx for spotting it and correcting me === glatzor_ is now known as glatzor [09:47] Keybuk: I'm here if you need me for some udev testing/debugging [09:48] * Ng is curious if there are any arguments against bug #157345 - and more importantly, who would be worth advocating it to [09:48] Launchpad bug 157345 in cupsys ""show printers shared by other systems" should be on by default" [Medium,Triaged] https://launchpad.net/bugs/157345 [09:51] Ng: tkamppeter? [09:52] dholbach: yeah I added a comment last night asking if he had any objections. It seems like it probably ought to have some input from team securitah [09:53] maybe pitti knows about it too? [09:53] Ng: in fact I'd like to do that as well, but IMHO bug 314408 should be solved first [09:53] Launchpad bug 314408 in qt4-x11 "Please separate autodetected from locally configured printers" [Wishlist,Triaged] https://launchpad.net/bugs/314408 [09:54] Ng: this would then comply to https://wiki.ubuntu.com/DefaultNetworkServices [09:55] that is exactly the kind of argument I was looking for :) [09:55] Ng: there's no principal blocker, other than finding the time to do it for GTK and Qt [09:56] pitti: I'll add appropriate commentary, thanks :) [09:59] slangasek: thanks [10:00] Ng: cool, Qt upstream scheduled fixing for 4.6.0 [10:01] pitti: given that we're post-FF, assuming a patch existed, would this be likely to make it for jaunty? [10:01] Ng: the gtk/qt patches fall under UIF [10:02] Ng: but the cups change itself is FF, of course; it'll probably be accepted if it lands by UIF, but not later [10:02] hmm, just over a week [10:07] http://launchpadlibrarian.net/22770218/buildlog_ubuntu-jaunty-i386.openerp-server_5.0.0-3-1_FAILEDTOBUILD.txt.gz << does anybody know where this FTBFS comes from? [10:07] pitti: darn. why does that immutable page have to have a typo on it? [10:07] DefaultNetworkServices? doesn't seem immutable - are you logged in/ [10:07] ? [10:07] er, apparently not [10:08] hrm. perhaps it isn't a typo either, but something i've never heard of [10:08] bigon: appears to be an objection from pkgstriptranslations? [10:08] if you mean "DCHP", I've just corrected that [10:08] cjwatson: yeah, that's hte one ;) [10:09] bigon: which is pkgbinarymangler [10:09] pitti: perhaps at some point you could propose a diff to ubuntu-policy encompassing that specification? [10:10] cjwatson: added to my todo list [10:12] no rush, thanks [10:18] hi there [10:19] i have created a bootsplash with gimp, 16 indexed colors, and compiled into a shared object, but it wouldnt be loaded, the bootscreen is just black with a blinking cursor while booting... [10:19] Keybuk: wrt. https://bugs.edge.launchpad.net/ubuntu/+source/elisa/+bug/315704/comments/23, I tend to agree (both that it's better suited in universe, support-wise, and that the user experience would be better); do you still remember why you wanted it in main in the first place? [10:19] Ubuntu bug 315704 in elisa-plugins-ugly "FFe and merge for Elisa 0.5.28-1 / sync request for elisa-plugins-{good,bad,ugly} 0.5.28-1 from Debian experimental" [Wishlist,Confirmed] [10:19] pitti: ask lool I think that was a mobile thing? [10:20] pitti: lool has been working on it previous cycle for sure [10:20] seb128: request came from Keybuk, lool helped a lot to implement it, though [10:20] ok [10:20] ignore me I was just mentionning it in case that was useful ;-) [10:22] seb128: merci [10:22] pitti: de rien ;-) [10:23] cjwatson, partman complains, but you can go on iirc [10:23] which means you die with oom on the slug [10:24] ogra: sure, I regard that as the user's fault :) [10:24] ok [10:24] it warned you; if you ignore it you get to keep both pieces [10:24] * ogra will do so too then, i'll m,ake sure its in the docs [10:24] -, [10:31] Keybuk, any idea about the weird behavior udev shows on my slug install ? http://paste.ubuntu.com/121199/ [10:33] Keybuk, the uuid's that end up in /target/etc/fstab dont match anything in the system until i call udevadm trigger which then changes the complete set of uuids for the target partitions [10:34] beyond that the first uuid in the mkinitramfs error doesnt exist at all === azeem_ is now known as azeem [10:44] join #ubuntu-offtopic [11:11] Keybuk: davmor2 has a problem with a fresh LVM installation that I speculate might be bug 332270. What's the easiest way for him to confirm that it's the same bug? [11:11] Launchpad bug 332270 in udev "udev repeatedly generates "change" events for the same block device(s)" [High,Triaged] https://launchpad.net/bugs/332270 [11:21] cjwatson, Keybuk: Does this only effect certain disks or does it only effect certain type of partitioning? Also removing quite and splash from the kernel line might give me more info wouldn't it? [11:21] davmor2: absolutely no idea [11:21] I still can't replicate it [11:22] pitti: -mobile wanted it in main [11:22] Keybuk: ah, thanks [11:22] lool: does that still hold? (elisa in main for mobile) [11:23] Keybuk: I got it doing a LVM install test that I used the new d-i lvm resize feature on, at 20% of a 250gig hd [11:24] davmor2: got what? [11:24] Keybuk: bug 332270 if it is that bug [11:24] Launchpad bug 332270 in udev "udev repeatedly generates "change" events for the same block device(s)" [High,Triaged] https://launchpad.net/bugs/332270 [11:25] davmor2: no, I mean what _happened_ when you got to 20%? [11:25] Keybuk: no I used the resize feature and set it to use 20% of my 250g hd [11:25] and then what happened? [11:26] it's not *re*size, BTW, it's setting the initial size [11:26] cjwatson: sorry :) [11:26] Keybuk: it wouldn't reboot [11:26] davmor2: why not? [11:27] did you see an error message? [11:27] were there messages on another console? [11:29] Keybuk: two ticks I'm just removing quite and usplash from kernel line as it doesn't provide me with any other consoles [11:32] davmor2: which architecture are you using? i386 or amd64 or something else? [11:34] Keybuk: Disk activity is constant it seems to of detected most of my hardware and now lists /sys/devices/pci0000:00/0000:00:1f.2/host2/target2:0:0/2:0:0:0/block/sda new line /sys/devices/pci0000:00/0000:00:1f.2/host2/target2:0:0/2:0:0:0/block/sda/sda1 and repeats === evand_ is now known as evand [11:35] That's the one. [11:35] davmor2: great! [11:35] geser: I386 [11:35] can you explain the steps you went through to do this? [11:36] I'll try and replicate in vmware [11:38] Keybuk: i386 alternat install. Select guided - lvm whole drive for partitioning. hit enter on the next screen and then on the next screen change -12-1 to 20% and hit enter complete the install [11:38] err, can you explain the -12-1 to 20% thing? [11:38] pretend that I've never seen the alternate installer before [11:38] was the disk blank when you did this? [11:38] or was there an existing operating system there? [11:38] did you remove the existing operating system? [11:38] or did you select resize? [11:40] Keybuk: I can help here [11:40] Keybuk: http://testcases.qa.ubuntu.com/Install/AlternateLvm after the guided - use entire disk and set up LVM you now get the option to not use the entire disk for more flexibility (new feature) [11:41] Keybuk: the installer recently gained a feature whereby, if you choose guided LVM partitioning (i.e. erase whole disk, stick LVM on it), then rather than just munching the entire volume group for logical volumes, it asks you how much of the volume group you want to use [11:41] I told it to use 20% of the 250GB drive rather than -12-1 (the whole drive) [11:41] Keybuk: the structure of the resulting volume group should be the same [11:41] ok, so whole-disk LVM [11:41] no MD? [11:41] davmor2: "-12-1"? that makes no sense to me [11:41] no encryption? [11:41] davmor2: is that literally what you saw? [11:42] cjwatson: I think that is what it said I can re-run it to check for you [11:42] it was something weird like that [11:42] davmor2: if you do see that, it's a bug, and I'd like syslog and partman; it should be more like "250 GB" [11:42] Keybuk: no not encrypted [11:42] it could be some kind of overflow bug [11:43] I think I got the logs from installer hang on [11:44] hmm, the partman test suite probably ought to test some bigger numbers [11:44] though it does test 4.3GB [11:44] $ longint2human 2500000000000 [11:44] 2.5 TB [11:44] *seems* fine ... [11:46] my only guess is that vgs is outputting garbage [11:47] davmor2: I'd like the output of 'vgs -o vg_free --units K --noheading --nosuffix' [11:49] * Keybuk sees "8.3 GB" [11:49] I selected 50% [11:50] now it's installing the base system [11:51] cjwatson: logs for partman and syslog should be http://www.davmor2.co.uk/syslog http://www.davmor2.co.uk/partman [11:51] davmor2: are you doing this in vmware or on a real machine? [11:51] Keybuk: really hw [11:51] real even [11:52] are you able to do it again? [11:52] Keybuk: Restarting now [11:52] davmor2: when partman is up, can you switch to Alt+F2 [11:52] then run [11:53] # killall udevd [11:53] # udevd --debug --resolve-names=never > /var/log/udev 2>&1 [11:53] then continue with your test [11:53] if it hangs, let it for 15-30 seconds or so [11:53] then ^C udev [11:53] and give me that log file ;) [11:54] cjwatson: from where would you like the vgs -o .... line typing ? [11:57] Keybuk: problem kicks in upon restart the install works fine [11:57] Keybuk, ny< idea for my uuid prob ? [11:57] *any [11:57] davmor2: oh, you're saying that the install worked fine before? [11:58] ogra: what uuid problem? [11:58] ogra: I can suggest some cream? [11:58] Keybuk, http://paste.ubuntu.com/121199/ [11:58] cream is always good [11:58] Keybuk: yes it's at the end of the install it reboots only then nothing happens [11:59] ogra: *shrug* your UUIDs in your fstab are wrong [11:59] davmor2: this is what happened last time too? [11:59] davmor2: the install absolutely definitely worked, and it was after the reboot you had the problem? [11:59] Keybuk, so you say thats a d-i failure ? even if the uuids change to the proper ones after running udevadm trigger manually ? [12:00] ogra: I'm not saying anything [12:00] Keybuk: yeap the install log is the one I posted for cjwatson [12:00] I'm just saying that all your pastebin shows is that your fstab is clearly wrong [12:00] i would expect them to be exactly whats in fstab on forst boot [12:00] *first [12:00] davmor2: ok, interesting [12:00] davmor2: so you can boot that system now, and it hangs on boot? [12:01] Keybuk, well, the fstab matches what i see after the uuids change when i call udevadm trigger, my question rather would be why are they different at all ? [12:01] ogra: no idea, why is the sky blue? [12:01] Keybuk: grub works then detect hw works then you get the never ending stream of /sys/devices [12:01] ogra: please find out :) [12:01] Keybuk: Would it help if you can watch it happening? [12:01] davmor2: ok [12:01] davmor2: could you boot, get to grub, replace "splash" with "init=/bin/bash" [12:02] and then run the following [12:02] mount -o rw,remount / [12:02] Keybuk, because the pink paint was out [12:02] edit /etc/init.d/udev [12:02] actually [12:02] rewind that [12:02] Keybuk: hang on mid install to confirm I can reproduce it [12:02] just boot with init=/bin/bash [12:02] and see if you get to a root prompt first [12:03] IntuitiveNipple: unless you have a serial console, I'm not sure how you could set that up ;) [12:03] Keybuk: I do, and I can give you shared SSH/screen access to view as it happens [12:03] IntuitiveNipple: that would be helpful [12:04] davmor2: tty2 [12:05] cjwatson: there isn't one on the installed system [12:05] davmor2: no, I mean during install, at the point where it gives you the LVM size prompt [12:05] cjwatson: np's [12:06] although there most certainly is a tty2 on the installed system :-0 [12:06] Keybuk: OK. I'll set it up. Just so you know what you'll be seeing: It's a lab PC with a clean install on Sunday. I've just downgraded udev/dmsetup to the pre-issue versions so it is possible to get control. [12:06] :-) [12:06] IntuitiveNipple: I assume it's ok for me to upgrade them again while the system is running? [12:06] * cjwatson peers at davmor2's syslog [12:06] Feb 23 10:09:31 main-menu[1756]: (process:11141): . [12:06] Feb 23 10:09:31 main-menu[1756]: (process:11141): TB [12:06] that's ... odd [12:07] Keybuk: Yes, it's a lab PC. I downgraded it specifically so we can see the initial reaction. You can also kick into the initrd by using kernel command-line "break" to stop before premount kicks off [12:08] cjwatson: by the way I think it is wrong to now call guided - use entire disk and setup lvm if you can set it to not use the entire disk :) [12:08] IntuitiveNipple: and how do I install a package? ;o) [12:09] They are in the /root/ directory of the installation, for use with dpkg. I'll show you once you're attached [12:09] davmor2: maybe, though I'm reluctant to change the translated string [12:10] davmor2: it does use the entire disk in the sense that it erases everything there before and puts an LVM volume group over the entire disk [12:10] davmor2: one thing that may address your problem is that I've changed the text in the size question to talk about the amount of the volume group you want to allocate, rather than the amount of disk [12:11] cjwatson: Right still listed as -12-1 and vgs line reads 159782010.88 [12:11] Keybuk: OK... this will get you onto my laptop, from where you can attach to the screen multiuser session where the serial console is running: ssh -p 2222 remoteop@alexandros.tjworld.net [12:11] Keybuk: The remoteop password is: letmein [12:12] Keybuk: Once logged in, attach to my screen session using: screen -x tj/Multiuser [12:12] * davmor2 right Keybuk s line next [12:12] (you realise this is a publicly logged channel?) [12:12] cjwatson: I should hope so :) [12:13] weird, X-Chat just decided to crash there [12:13] Keybuk: Did you miss my connection instructions? [12:13] I've connected, and I can see the root@jaunty:~# prompt [12:13] this is the lab machine? [12:14] Keybuk: I can confirm the last comment on that udev bug: when I disable one core, restart udev then the udevadm trigger doesn't cause any loop [12:14] Keybuk: That is the console to the lab machine... I'll send some commands [12:14] cjwatson: was that directed at me? [12:14] davmor2: no, IntuitiveNipple (which I can only assume is intended to mean "completely unintuitive" ...) [12:15] Keybuk: You have control... snoop around... do you want to see it reboot with 137-1 so when we install 138-1 you can see the difference? [12:15] no, I know what a booting Ubuntu machine looks like ;)P [12:16] :) [12:16] Do you want to update dmsetup? [12:16] davmor2: hmm, when you have a chance, it would be good if you could run through the installer, stop at the hostname prompt, 'nano /bin/perform_recipe_by_lvm' and stick 'set -x' at the top - then I need the resulting syslog after the rest of the installation [12:16] davmor2: sorry, I know each iteration takes a while [12:16] IntuitiveNipple: no, just going to take this one step at a time [12:16] cjwatson: np's it's better to get it fixed now :) [12:16] Keybuk: ok... just there was a package dependency issue [12:17] davmor2: there's clearly an arithmetic bug somewhere but I can't reproduce it at an ordinary shell [12:19] * Keybuk hates screen [12:19] it's like it *tries* to get being a terminal completely wrong [12:19] on purpose [12:19] IntuitiveNipple: no swap? on purpose? [12:20] Keybuk: correct [12:20] what's /dev/sda2 and /dev/sda4 ? [12:20] Keybuk: sda2 is formatted for swap but not in fstab [12:20] sda2 is not properly formatted for swap ;) [12:20] someone didn't use parted for it [12:20] sda3 is / sda4 is the demo LVM area, but nothing in it gets mounted. [12:20] ogra: I'm surprised that not more people agree with you on the long-term-reminder thing [12:20] "demo LVM area" ? [12:21] Keybuk: I had to build it using deboostrap - Sunday's live-CD ubiquity failed on starting [12:21] highvoltage, well, cjwatson's mail showed me that i probably didnt formulate it right [12:21] Keybuk: demo as in, it's not used but is 'there' to demo the bug. [12:21] so people might not have understodd what i meant [12:21] IntuitiveNipple: if you don't have that, do you not see the bug? [12:22] yes, ubiquity has a missing dependency at the moment (which probably needs to be fixed by removing the dependency, otherwise I'd have fixed it already) [12:22] Keybuk: how does sda2 manage to be improperly formatted for swap? [12:22] Keybuk: I'm not sure tbh... don't think I did that test. I know without the lvm2 package installed the bug doesn't show, but thats different. Do you want to delete sda4 ? [12:22] cjwatson: not wiped first, so looks like it has swap and ext3 metadata [12:22] IntuitiveNipple: can we rewind this conversation please [12:22] Keybuk: sure [12:22] IntuitiveNipple: your system is not set up "normally" [12:22] how you've set this up could be VERY important [12:23] does parted actually get that right, I wonder? [12:23] so, please explain your system's setup - and why it is the way it is [12:23] cjwatson: yes [12:23] note also that d-i sometimes falls back from libparted to mkswap when formatting swap partitions [12:24] ah yes, libparted memsets the header [12:24] Keybuk: It had to created using deboostrap, since Ubiquity failed. So, from the live-CD I fdisk-ed the 4 primary partitions and set their types, then used mkfs.ext3 /dev/sda1 and /dev/sda3, mkswap /dev/sda2, and pvcreate/lvcreate for sda4 [12:24] so what is sda4 for? [12:24] why did you do that? [12:24] Keybuk: Then used debootstrap to install Ubuntu into it [12:25] Keybuk: sda4 was there to test that LVM would trigger the bug [12:25] ok [12:25] as, I think, does busybox mkswap (not explicitly but effectively) [12:25] so sda4 is an LVM with a bunch of logical volumes in it [12:25] do you mount those volumes? [12:26] util-linux mkswap also does a memset, so if ext3 metadata is left around, it must be outside the swap header region? [12:26] Keybuk: No. I was about to create an alternative boot option using them a few minutes ago (which is why it is mounted on /target/) but its totally unused [12:26] no you don't mount those volumes? [12:26] or no I'm wrong? [12:26] Keybuk: It's a sacrificial system set up just for testing this bug scenario [12:26] Keybuk: nothing in LVM is mounted [12:26] (unless I am playing about) [12:27] cjwatson: we should start a campaign to import "doch" into the English language [12:28] absolutely [12:28] very annoying omission from English [12:29] lrwxrwxrwx 1 root root 10 Feb 23 11:54 0c3390a5-9d90-460d-bc8d-10ff5d02a6f4 -> ../../dm-0 [12:29] that's odd [12:30] Keybuk: The disk is 'thrashing' at this point [12:30] well, that definitely loops ;) [12:30] That's the same as happens at boot-time in initrd as soon as udev starts [12:31] and it never seems to stop... at least after leaving it 15 minutes it hasn't [12:32] * Keybuk hates screen [12:33] Well, while you hate it, I'll go grab a cuppa [12:33] IntuitiveNipple: how many cpus/cores does this lab PC has? [12:33] single [12:35] IntuitiveNipple: this computer has no internet access? [12:35] * Keybuk needs to get that log file off [12:38] There you go [12:38] Remember I've also attached some full debug LOG_DEBUG logs to the bug report [12:39] yeah, but you cut the important bit off ;) [12:39] The gzip logs are the full capture from start... nothing was edited [12:41] Keybuk: init=/bin/bash doesn't work :( [12:41] cjwatson, Keybuk: I can confirm though that it is reproducible [12:41] davmor2: good to know, thanks [12:42] davmor2: No, it won't, since the issue starts in initrd... you need to do "rdinit=/bin/busybox" or just add "break" to stop initrd at the premount point [12:42] rdinit? [12:42] $ wcgrep rdinit /usr/share/initramfs-tools/ [12:42] $ [12:43] cjwatson: which init inside the initramfs to run [12:43] besides surely /bin/busybox will just print a message about how you should have nominated an applet to run [12:43] break=top would have been just as good [12:43] invoking /bin/sh would be more normal [12:45] cjwatson: sorry, yes, I was thinking and typing at the same time... always a dangerous thing to do (sh is provided by busybox was in my mind) [12:47] cjwatson, Keybuk: I'm off for lunch in a second so cjwatson I'll try your other request when I get back. Keybuk is there anything else you'd like me to try? [12:47] not at this time [12:48] IntuitiveNipple's machine is proving a useful study so far [12:48] Cool :) [12:48] First time it's been useful in 5 years :) [12:48] It's damned noisy! How do fans get noisy when they're never used!? [12:50] ok [12:51] so in your case, it's lvm [12:51] lvm scans all the drives [12:51] and that is causing inotify events on them [12:51] quite why lvm is opening them writable is anyone's guess ;) [12:58] Keybuk: I did wonder, with the vscan && vgchange [12:58] s/vscan/vgscan/ [12:59] The timing issue is interesting too... as I said before. With debug logging there seems to be sufficient delay between actions to avoid the inotify trigger [12:59] sure [13:00] lvm vgscan beats inotify watch [13:00] it's only the inotify watch on the block device that has the LVM PV that really matters [13:01] see [13:02] making it not watch the LVM PV fixes the problem ;) [13:05] IntuitiveNipple: I think I broke it - it's not responding? [13:05] let me check [13:05] I think you did :) [13:06] No response on the physical console [13:06] I'll try to force a restart [13:07] Booting with "break" to stop at pre-mount else we'll be stuffed [13:07] no we won't [13:07] Yes were are... disk is thrashing madly [13:07] s/were/we/ [13:07] ah, it's thrashing inside the initramfs [13:07] I must hav mistyped the kernel command line [13:07] ok, can you reboot it again ;) [13:07] Yes, as always [13:09] This break-top [13:09] * IntuitiveNipple bites fingers [13:09] This *is* break=top [13:11] thrashing again or not? [13:11] OK you broke it again :)...I have noticed that when the udev issue occurs, the next warm-boot locks the PC at this point. I'll have to do a cold restart [13:11] No, it's froze up... give me amo [13:11] pitti: No, we didn't really use elisa in main after all; I was interested in doing the work back then because there was a chance of including it in the seeds and it was used by OEM [13:11] pitti: Nowadays, I think it's a blocker to have elisa* in main; so please demote if you feel like it [13:11] weird === mvo_ is now known as mvo [13:14]