[00:12] <Jordan_____> I'm trying to install a minimal install of ubuntu with wubi using the instructions here: http://ubuntuforums.org/showpost.php?p=3274621&postcount=2 but I get a full install with gnome, unity, etc. instead of a tty login
[11:51] <njin> bug 959251 noone experirncing it in real hardware ?
[11:51] <ubot2`> Launchpad bug 959251 in ubiquity "** CRITICAL **: unable to create '/root/.cache/dconf'" [Undecided,New] https://launchpad.net/bugs/959251
[12:04] <tokarbol> Is there a preseed option so that d-i would not use swap if it found a swap partition?
[12:53]  * cjwatson starts writing a test for bug 960047
[12:53] <ubot2`> Launchpad bug 960047 in ubiquity "ubiquity crashed with UnboundLocalError in set_indicator_keymaps(): local variable 'engine' referenced before assignment" [High,Triaged] https://launchpad.net/bugs/960047
[12:54] <ev> glad you noted that - I was just about to pounce on it :)
[12:54] <ev> tests for the win
[12:54]  * ev grabs a tea
[12:55] <cjwatson> test_set_indicator_keymaps_english (test_misc.MiscTests) ... Segmentation fault (core dumped)
[12:56] <cjwatson> wtf.  maybe I need to upgrade first
[13:03] <bdmurray> bug 960039 might be worth a look
[13:03] <ubot2`> Launchpad bug 960039 in ubiquity "ubiquity greeter : Label of the network indicator changes to the keyboard layout code" [Undecided,New] https://launchpad.net/bugs/960039
[13:04] <infinity> o/
[13:08] <cjwatson> OK, does this segfault for anyone else?  python -c 'from gi.repository import GdkX11; display = GdkX11.x11_get_default_xdisplay()'
[13:08] <cjwatson> still upgrading stuff, but I've upgraded most of the libraries ...
[13:09] <jibel> cjwatson, i does on an up to date precise amd64
[13:09] <cjwatson> jibel: it segfaults?
[13:09] <jibel> cjwatson, yes
[13:09] <ev> yay PyGI
[13:09] <cjwatson> bah, so how come the tests passed in stgraber's upload?
[13:10] <cjwatson> yay constructive ;-)
[13:10] <ev> :)
[13:10] <ev> segfaults for me as well, and I'm not nearly up to date
[13:11] <cjwatson> worked fine in the 2.9.30/i386 build
[13:11] <infinity> segv here too, you're not alone.
[13:13]  * infinity goes to hunt some caffeine before diving into things.
[13:14]  * ogra_ twiddles thumbs in front of the obligatory "waiting 60 seconds for network devices" message
[13:14] <stgraber> cjwatson: that should segfault when you're not in a gtk mainloop (from previous tests)
[13:15] <cjwatson> oh.  (FSVO "should")
[13:15] <cjwatson> I encountered this in the middle of the test suite, though
[13:16] <stgraber> well, apparently there are cases in gi world where stuff are kind of expected to segfault ;) "like from gi.repository import Xkl; test = Xkl.Engine()" because you should instead us Xkl.Engine.get_instance() :)
[13:19] <cjwatson> 'tests/run test_misc' -> test_set_indicator_keymaps_english (test_misc.MiscTests) ... Segmentation fault (core dumped)
[13:20] <slangasek> ogra_: it's not obligatory at all, you should only see that message if you have a broken network config?
[13:20] <cjwatson> ah, yes, it's a test isolation bug - it works if you run the whole test suite
[13:20] <cjwatson> (that's at least enough for me to get past this and fix what I actually wanted to work on)
[13:21] <ogra_> slangasek, well, its obligatory if oem-config didnt run yet :) but i also end up with no /e/n/i after a successfull non networked install (not even loopback in there) ... the latter is on my list for things to look at after (if i ever *sigh*) found out whats wrong with automatic preseeding installs in oem-config
[13:23] <slangasek> hmm, let me look at that ifupdown hook - is it possible we don't properly handle the case that there are *no* networks configured in /e/n/i?
[13:23] <ogra_> intrestingly the log doesnt reveal much exciting stuff even if i run oem-config --automatic --debug
[13:24] <ogra_> slangasek, i would rather blame oem-config to not run all modules ubiquity would usually
[13:24] <slangasek> ogra_: no, just reviewed /etc/network/if-up.d/upstart, and it was written to handle the case when there are no interfaces configured in /e/n/i - as long as 'ifup lo' succeeds
[13:25] <slangasek> ogra_: there *was* a problem with this error message showing up on first boot, which was tracked down to a resolvconf bug; but that should be fixed now
[13:25] <ogra_> hmm, but then i shouldnt get the message
[13:25] <slangasek> i.e., the resolvconf hook was exiting non-zero and preventing the upstart hook from ever firing
[13:25] <ogra_> also shouldnt we drop lo from /e/n/i for completeness ?
[13:26] <slangasek> no
[13:26] <slangasek> that's where it's supposed to be configured :)
[13:26] <ogra_> but upstart already handles it
[13:26] <slangasek> after getting this message, can you grab me the output of 'sudo ifquery --list' and 'ls -l /run/network'?
[13:26] <slangasek> upstart handles it to protect you from a misconfigured /e/n/i
[13:27] <slangasek> it's actually possible that you might want to have additional configuration of lo, beyond the default
[13:27] <ogra_> well, thats fine to add to /e/n/i then :)
[13:28] <barry> slangasek: okay, net's back up, but mumble is still ill ;)
[13:28] <ogra_> i just think (since years already) that its superfluous to have it there for the default
[13:28] <stgraber> slangasek: resolvconf hook preventing the upstart hook was a while ago right? (want to make sure my revert of ifupdown's run-parts arguments didn't fail for some reason without me knowing ;))
[13:28]  * ogra_ curses the HUD getting in his way all the time
[13:29] <njin> bug 959251 not reproducible in vm, only in real hardware
[13:29] <ubot2`> Launchpad bug 959251 in ubiquity "** CRITICAL **: unable to create '/root/.cache/dconf'" [Undecided,New] https://launchpad.net/bugs/959251
[13:29] <barry> ogra_: sigh
[13:29] <ogra_> feels like someone wants to teach me to take my hands off the kbd if i dont type
[13:29] <slangasek> stgraber: yes, that was supposed to be fixed in 1.63ubuntu8
[13:31] <cjwatson> could somebody look at 959251, please?
[13:31] <cjwatson> https://code.launchpad.net/~cjwatson/ubiquity/indicator-keymaps-960047/+merge/98407
[13:32] <stgraber> cjwatson: I'm currently working on bug 960096 but I'm happy to help someone with 959251 (as I'm the author of the gsettings code) or will have a look at it myself later today
[13:32] <ubot2`> Launchpad bug 960096 in ubiquity "Live session started with wrong layout" [Undecided,In progress] https://launchpad.net/bugs/960096
[13:34] <cjwatson> bug 960036 and bug 960039 are new keyboard indicator bugs, although I don't know if they're regressions or just things that never worked
[13:34] <ubot2`> Launchpad bug 960036 in ubiquity "ubiquity greeter : changing language changes order of the indicators" [Undecided,New] https://launchpad.net/bugs/960036
[13:34] <ubot2`> Launchpad bug 960039 in ubiquity "ubiquity greeter : Label of the network indicator changes to the keyboard layout code" [Undecided,New] https://launchpad.net/bugs/960039
[13:36] <stgraber> cjwatson: engine.lock_group(0) is meant to be called in all cases, not only when we reset the gsettings key
[13:36] <barry> ogra_: are you using unity 2d or 3d?
[13:36] <stgraber> cjwatson: engine.lock_group(0) is supposed to tell the indicator to select the first entry in the list
[13:36] <cjwatson> stgraber: hm, ok, so we should actually assign something to engine even if not nodes, then?
[13:37] <ogra_> barry, usually 3d, for the hangout stuff i switched to an x86 machine though and that runs 3d ... its all massively confusing (cant  find my terminals with alt-tab, hud gets in my way etc)
[13:37] <stgraber> cjwatson: doh, should have seen that one... yes, that bit of code should be moved out of the if
[13:38] <infinity> ogra_: s/usually 3d/usually 2d/ ?
[13:38] <ogra_> heh
[13:38] <ogra_> usually 2d indeed
[13:39] <barry> ogra_: maybe you could add a comment to bug 947468.  i seem to be unconvincing
[13:39] <ubot2`> Launchpad bug 947468 in unity-2d "Alt summoning of heads-up-display interferes with Emacs" [Undecided,Confirmed] https://launchpad.net/bugs/947468
[13:39] <ogra_> barry, will do
[13:39] <barry> thanks!  trying to rally the troops :)
[13:41] <Teduardo> Any chance of getting support for the Broadcom 5720 QP NIC in the 10.04 LTS pxeboot images?
[13:41] <Teduardo> a flood of servers are coming to market bearing these
[13:42] <stgraber> cjwatson: if you can move the display and engine lines from within the "if nodes" to just before it and then move back lock_group to outside the else, the MP looks good for merging
[13:42] <ogra_> Teduardo, before or after april ?
[13:42] <Teduardo> Do you mean are the servers coming before or after april, or do you mean that the version of Ubuntu?
[13:43] <ogra_> the servers indeed
[13:43] <Teduardo> I have some from Dell already
[13:43] <Teduardo> sitting here
[13:43] <ogra_> 12.04 LTS releases in april
[13:43] <Teduardo> oh, I was referring to the 10.04
[13:43] <ogra_> and i dont think there were any new spins of 10.04 planned
[13:44] <cjwatson> Teduardo: #ubuntu-kernel would be better, in any event - the installer mostly isn't directly responsible for hardware support
[13:44] <cjwatson> stgraber: right - reload the MP?
[13:44] <Teduardo> Sorry, I meant the kernel in the installer... splitting hairs now =)
[13:44] <cjwatson> Teduardo: same kernel
[13:45]  * barry -> reboot
[13:45] <cjwatson> Teduardo: and the kernel packaging is responsible for selecting which modules to deliver to the installer, as well
[13:45] <stgraber> cjwatson: looks good. Marked as approved on LP
[13:45] <Teduardo> right but if they update the kernel in the distribution, someone would then have to go back and port the new one to the installer images
[13:45] <cjwatson> Teduardo: which is a trivial thing to do, but the kernel would have to be sorted out first
[13:45] <cjwatson> honestly, not much point asking us before the kernel is changed
[13:46] <ogra_> grrr, why do i get a completely corrupted syslog from time to time in my installer tests
[13:46] <CIA-32> ubiquity: cjwatson * r5280 trunk/ (debian/changelog tests/test_misc.py ubiquity/misc.py):
[13:46] <CIA-32> ubiquity: Fix misc.set_indicator_keymaps to handle ll_CC forms of lang, and also
[13:46] <CIA-32> ubiquity: to avoid crashing on unknown languages in general (LP: #960047).
[13:47] <CIA-32> ubiquity: cjwatson * r5281 trunk/ubiquity/misc.py: call engine.lock_group(0) in all cases, per stgraber
[13:50] <infinity> cjwatson: Did you have any changes staged/shelved for powerpc->powerpc-smp?  If not, I'll do that all today.
[14:02] <ogra_> 23699 Jan  1 00:24:53 localhost localechooser: info: debian-installer/language preseeded to 'en' (seen: true)
[14:02] <ogra_> 23702 Jan  1 00:24:53 localhost localechooser: info: Preseeded language ignored: unknown language code
[14:02] <ogra_> cjwatson, ^^^ whats a proper preseed value for that ?
[14:03] <infinity> ogra_: 'en'?
[14:03] <cjwatson> infinity: I do, but just http://paste.ubuntu.com/892213/, feel free to fiddle from there
[14:03] <ogra_> (sees that actually nothing is wrong with oem-config --automatic if i get the "seen: true" in teh log the question is actually not asked
[14:04] <ogra_> infinity, but thats what the pressed file has :P
[14:04] <infinity> cjwatson: Alright, so still need to touch lots of other bits.  I'll get on that.
[14:04] <ogra_> d-i debian-installer/language string en
[14:04] <cjwatson> maybe 'd-i debian-installer/locale string en_US.UTF-8' or something instead
[14:05] <cjwatson> not sure offhand why en would be failing, would require some digging and I ought to look at this grub2 regression
[14:05] <ogra_> yeah, i didnt mean to pull you into my problems :)
[14:05] <stgraber> njin: ok, reproduced your bug, trying to figure out what's happening there exactly...
[14:05] <njin> great stgraber !
[14:06] <infinity> ogra_: /usr/share/localechooser/SUPPORTED might be a good place to start.
[14:06] <cjwatson> 'en' really ought to work - it's the default for that template
[14:06] <ogra_> awesome, thanks !
[14:07] <ogra_> cjwatson, well, i'm starting from a seemingly broken preseed file there might be something else intervening, i will start from scratch
[14:07] <infinity> ogra_: (or so the code implies)
[14:07] <infinity> But yeah, anything from languagelist should work too, which includes all the 2-char codes.
[14:20] <stgraber> ev: http://paste.ubuntu.com/892235/ + mkdir /tmp/my-bus + dbus-daemon --config-file=system.conf --nofork
[14:20] <stgraber> ev: that seems to work here
[14:20] <ev> stgraber: cheers!
[14:21] <stgraber> ev: that pastebin is just /etc/dbus-1/system.conf with the bus address changed and changed to run as you instead of messsagebus
[14:33] <stgraber> njin: I "think" I have a fix. Hopefully this one will be the right one... this function is getting really big for something supposedly simple
[14:35] <njin> do you need me to test something ?
[14:36] <njin> stgraber:^^
[14:36]  * bdmurray gets some more coffee
[14:43] <stgraber> njin: not just yet, I'm fixing some tests, building a new usb stick with the fix and if it all works here, I'll push it to trunk, release a new ubiquity and we'll have a respin in a few hours for you to test
[14:54] <njin> great
[14:57] <ogra_> screen -r
[14:58] <ogra_> DAMN !
[14:58]  * ogra_ really starts to dislike unity 3D
[14:58] <GrueMaster> this is not the screen you are looking for.
[15:02] <barry> cjwatson: could you perhaps sanity check this comment: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/933433/comments/8
[15:02] <ubot2`> Launchpad bug 933433 in ubiquity "Kubuntu manual install crashed during bootloader configuration on an XFS partition" [Medium,Triaged]
[15:05] <cjwatson> barry: it would be worth comparing your syslog with the reporter's
[15:06] <barry> cjwatson: it's exactly the same until you get to the traceback
[15:06] <barry> cjwatson: i.e. there is no traceback any more
[15:06] <cjwatson> barry: ok, good
[15:06] <cjwatson> barry: sounds sane then; the reporter's on 10.04, after all
[15:06] <barry> cjwatson: yep.  cool, i'll move on to bug 959724.  thanks
[15:06] <ubot2`> Launchpad bug 959724 in ubiquity "Limit boot loader installation target" [Medium,Triaged] https://launchpad.net/bugs/959724
[15:09]  * barry -> tea
[15:12] <bdmurray> speaking of compcache - perhaps someone could look at bug 933712
[15:12] <ubot2`> Launchpad bug 933712 in casper "casper configures system to use 50% ram for compressed swap post installation" [Low,New] https://launchpad.net/bugs/933712
[15:13] <cjwatson> ogra_: want to take a look?
[15:13] <ogra_> cjwatson, at ? (zram?)
[15:13] <cjwatson> 933712
[15:14] <ogra_> ah, sure
[15:14] <jodh> https://code.launchpad.net/~jamesodhunt/ubuntu/precise/ubiquity/bug-944191/+merge/98430
[15:14]  * jodh reboots (USB woes...)
[15:17] <infinity> I'm not sure precisely what compcache-enable does, but if you just have zram swap(s) setup, it doesn't "steal" your RAM in any negative sense.
[15:18] <infinity> Although, now that I realise that's there in initramfs-tools, maybe I should fold zram-config into it. :P
[15:21] <cjwatson> jodh: could you push that to lp:~jamesodhunt/ubiquity/bug-944191 instead, and propose it for merging into lp:ubiquity rather than lp:ubuntu/ubiquity?  we don't use lp:ubuntu/ubiquity
[15:22] <cjwatson> lp:ubuntu/ubiquity is an auto-import so attempts to merge actual branches into it tend to produce giant diffs :)
[15:24] <slangasek> stgraber: still hating gtk today?  I think bdmurray could use some help with bug #959486; my guess based on what he says he's seen is that the code is only setting the gtk labels after the window has already been displayed, so you only see them on a full window refresh, but I'm not sure where in the code that's happening
[15:24] <ubot2`> Launchpad bug 959486 in ubiquity "install alongside doesn't show which partition is which" [Medium,Triaged] https://launchpad.net/bugs/959486
[15:24] <bdmurray> I think its in gtkwidgets.py
[15:25] <bdmurray> and I also noticed that the icons aren't appearing.  There are supposed to be icons for the operating systems right?
[15:25] <stgraber> slangasek: I'm currently hating gnome, trying to figure out why the keyboard layout stuff still doesn't work when going from greeter => live session...
[15:25] <slangasek> icons> dunno
[15:26] <slangasek> ev: ^^ this is your code for the partition widget, right?
[15:26] <stgraber> bdmurray: I'm not too familiar with that part of the code so I'd have to poke at it for a moment, maybe ev knows though
[15:26] <ev> likely my code
[15:26]  * ev digs
[15:27] <bdmurray> there is a FIXME line regarding rendering dots over the frame but I tried not painting the background and that didn't seem to help
[15:28] <ev> eah, that's my code
[15:28] <ev> so I'd suggest looking at the draw function (do_draw in PyGI-land)
[15:28] <ev> see if that's firing
[15:29] <ev> err actually
[15:29] <ev> brb
[15:32] <ev> sorry, elmo grabbed me
[15:33] <ev> bdmurray: so I'd try to narrow this down by stubbing out the paint_background functions and see if that brings back the text at least
[15:33] <ev> if that doesn't help, see if commenting out our custom draw function helps
[15:33] <jodh> ahem, with corrected merge branch - https://code.launchpad.net/~jamesodhunt/ubuntu/precise/ubiquity/bug-944191/+merge/98434
[15:34] <ogra_> infinity, i was thinking about that
[15:34] <ev> jodh: uhm, shouldn't that be against lp:ubiquity?
[15:34] <bdmurray> ev: okay thanks
[15:35] <jodh> ev: yes, something odd happened there: https://code.launchpad.net/~jamesodhunt/ubiquity/bug-944191/+merge/98435
[15:35] <infinity> ogra_: The (slightly better) logic in zram-config could certainly be rolled into compcache-enable.
[15:35] <ogra_> infinity, yeah
[15:35] <infinity> ogra_: And then we just need to turn it on in places where we want it.
[15:36] <ogra_> well, the prob with the bug seems to be that we need to parse the cmdline to make it only run in casper envs
[15:36] <ogra_> i.e. only if boot=casper
[15:37] <ogra_> but then we break it for everyone who *wants* to use it
[15:37] <ogra_> (like ac100 users)
[15:38] <ogra_> i dont really see any solution to the bug apart from "dont install casper on normal systems"
[15:38] <ogra_> (which was the answer to the last iteration of the same bug we had years ago iirc)
[15:40] <infinity> ogra_: Well, we can enable it conditionally based on a kernel cmdline, and add that to the ac100 cmdline.
[15:40] <infinity> compcache=noreallyimeanit
[15:40] <ogra_> infinity, thats what happens already ... well, the COMPCACHE:SIZE var is shipped in casper and only if thats present compcache is actually used ...
[15:41] <ogra_> and we have a kernel cmdline var to *dis* able it
[15:41] <infinity> Yeah.
[15:42] <ogra_> i dont really like to fiddle around with kernel cmdlines more than we need
[15:42] <infinity> Dirty hack, check for [ -d casper-bottom ] && ! boot=casper?
[15:42] <infinity> ie: if casper is installed, but not in use?
[15:44] <infinity> Still, seems like it's just breaking one weird corner case (you have casper locally for some odd reason, *and* want compcache) to prevent another (you have casper installed locally when you shouldn't).
[15:45] <ogra_> yeah, that sounds pretty sane
[15:46] <ogra_> otoh i would just close the bug :P
[15:46] <ogra_> its not a bad thing to have 50% zram
[15:46] <ev> yay, I've got NetworkManager running on a different system bus (provided I stop the existing one first)
[15:46] <ev> cheers stgraber
[15:46] <ogra_> and i dont see why it would be a bad user experience to suddenly have more ram :)
[15:47] <cjwatson> infinity: if you want compcache explicitly, though, you can always configure it in initramfs.size
[15:47] <cjwatson> initramfs.conf
[15:47] <cjwatson> or another conf.d script
[15:51] <ogra_> cjwatson, still, i would just close that bug, a) using zram has no actual drawbacks, b) casper is usually not installed ... if infinity wants to fold his zram handling into the casper scripts i think thats fine but independent
[15:54] <bdmurray> [50786.728259] init: whoopsie main process (1783) killed by ABRT signal
[15:54] <bdmurray> I see that in dmesg and not in syslog fwiw
[15:56] <jodh> ev: https://bugs.launchpad.net/ubuntu/+source/whoopsie-daisy/+bug/960326
[15:56] <ubot2`> Launchpad bug 960326 in whoopsie-daisy "whoopsie-daisy SIGSEGV but no crash file generated" [Undecided,New]
[15:57]  * cjwatson posts hopefully enough analysis to bug 855871 to deconfuse the reporter
[15:57] <ubot2`> Launchpad bug 855871 in partman-partitioning "Grub install fails after manual xfs partitioning" [Medium,Triaged] https://launchpad.net/bugs/855871
[15:57] <cjwatson> I'm about to have a go at testing http://paste.ubuntu.com/892356/ for that
[15:59] <cjwatson> but first, COFFEE
[16:02] <ogra_> cjwatson, i would appreciate a look at bug 924018 i added a syslog and debconf seems to even though it marks questions as "seen" still ask them
[16:02] <ubot2`> Launchpad bug 924018 in ubiquity "Preseeding doesn't work with oem-config" [Medium,Confirmed] https://launchpad.net/bugs/924018
[16:02] <ogra_> and i dont see anything in the ubiquity code that would prevent the automatic mode
[16:09] <cjwatson> ack, will require some meditation
[16:10] <cjwatson> hm, 'debug-oem-config' would've been useful
[16:10] <ogra_> i just added --debug to the oem-config-wrapper cmdline
[16:10] <cjwatson> can you get that?  (I realise it takes a while, sorry ...)
[16:10] <ogra_> since i hacked it anyway
[16:10] <cjwatson> oh, but there's no debconf debug output in your log
[16:10] <cjwatson> maybe it's in /var/log/oem-config.log?
[16:10] <ogra_> oh, one sec
[16:11] <ogra_> LOL
[16:11] <ogra_> yeah, and i was looking at the wrong log all the time
[16:11] <ogra_> sorry, let me try myself first then before i waste your time
[16:12] <ogra_> (thopugh i can attach it anyway)
[16:12] <cjwatson> sure
[16:12] <ogra_> done
[16:14] <cjwatson> ogra_: is this the debconf frontend?
[16:14] <cjwatson> yeah, it is
[16:15] <ogra_> yep
[16:15] <ogra_> ARGH !
[16:15] <ogra_> the HUD just started lobO while i typed yep
[16:15] <ogra_> *libO
[16:15] <cjwatson> --automatic has little effect on the debconf frontend - it only does anything much useful with frontends that filter the debconf protocol
[16:16] <ogra_> apprently the p from yep got typed into the HUD window
[16:16] <cjwatson> so that is, I think, a red herring
[16:16] <ogra_> hmm
[16:16] <ogra_> but why is it asking the preseeded questions then
[16:16] <cjwatson> are they actually getting preseeded by anything?
[16:17] <ogra_> there is a preseed.cfg that gets applied by jasper on first boot, yes
[16:17] <cjwatson> for example, there's no sign that clock-setup/utc is preseeded here, but that's in the preseed file
[16:17] <ogra_> and i also applied it manually inveween to make it pick up changes
[16:17] <ogra_> (using debconf-set-selections /presseed.cfg)
[16:18] <ogra_> *preseed.cfg
[16:18] <ogra_> it definitely is preseeded, i can see it with debconf-get-selections
[16:18] <cjwatson> oh, wait, clock-setup/utc is preseeded, you're right, odd
[16:18]  * cjwatson goes and peers at debconf
[16:19] <ogra_> looking at the ubiquity plugins i see a lot of hardcoded places where "seen" is set to false ... not sure that relates anyhow if the debconf frontend is used
[16:20]  * ogra_ quickly picks up some fresh coffee
[16:20] <cjwatson> the reason the seen flag has no effect is that we explicitly set "Reshow: true" in the debconf configuration file
[16:20] <cjwatson> bin/ubiquity:start_debconf
[16:20] <cjwatson> now there was a reason I did that :-)  let me do some archaeology
[16:21] <cjwatson> dates back to before the oem-config mrge
[16:23] <ogra_> well, it doesnt seem to affect ubiquity --automatic
[16:24] <ogra_> and i guess using oem-config that way is a very special usecase
[16:24] <ogra_> (though important for QA to do automated install tests)
[16:25] <cjwatson> not saying it shouldn't be fixed somehow, I just want to remember the exact reason so as not to break other things
[16:26] <ogra_> right, i was meaning to say, i wouldnt mid if it was special cased even with a special switch :)
[16:26] <ogra_> *mind
[16:26] <cjwatson> that's one plausible option, yes
[16:26] <cjwatson> heh, original commit that added Reshow was "Add a debconf_ui frontend which can be used in text mode on a server."
[16:26] <ogra_> LOL !
[16:27] <cjwatson> anyway, I think it was basically because those questions had already been shown by d-i so if we wanted them to be actually asked then we needed to tell debconf to reshow
[16:27] <cjwatson> obviously doesn't make sense in automatic mode
[16:27] <ogra_> right
[16:27] <cjwatson> so, let's see
[16:28] <infinity> cjwatson: So, platform seeds, live-build, find-live-filesystem, and debian-installer.  Can you think of where else the powerpc-smp change needs to happen?
[16:29] <cjwatson> infinity: live-build or livecd-rootfs depending on where you want to do it
[16:29] <infinity> cjwatson: live-build was in the list already and done. :)
[16:29] <cjwatson> infinity: debian-cd/tools/boot/precise/boot-powerpc and possibly elsewhere
[16:29] <infinity> Oh, debian-cd, right.  I only touched cdimage.
[16:29]  * infinity looks.
[16:30] <cjwatson> maybe data/precise/yaboot/
[16:30] <cjwatson> or maybe not, it just has "powerpc64"
[16:30] <infinity> Yeah, that's subarch, not kernel flavour.
[16:30] <infinity> Cause we're wildly inconsistent there.
[16:31] <ogra_> traditionally
[16:31] <cjwatson> yeah
[16:31] <cjwatson> and there's casper_subarch=powerpc
[16:31] <cjwatson> so ok, change casper_subarch, and leave the d-i subarch as powerpc
[16:31] <cjwatson> then debian-cd should cope from there
[16:32] <infinity> Yeah, that's what I'm getting from my grep too.  Cheers.
[16:33] <cjwatson> ogra_: try http://paste.ubuntu.com/892423/ ?
[16:33] <cjwatson> something along those lines anyway ...
[16:33]  * ogra_ hacks that in
[16:34]  * infinity can't help but think he's missing something...
[16:34] <infinity> cjwatson: What's the name of the d-i component with all the kernel lookup tables?
[16:34] <cjwatson> infinity: base-installer
[16:35]  * infinity recalls having to touch that for some ARM kernels recently...
[16:35] <infinity> Right.
[16:35] <cjwatson> yeah, you probably need to fix that
[16:40] <bdmurray> ev: well I've managed to narrow it down to something in do_draw of StylizedFrame
[16:43] <ogra_> cjwatson, still getting questions for user-setup and tasksel but it improved a lot and it could well be my tinkering over the whole day that messed up the debconf db
[16:43] <ev> okay
[16:43] <ogra_> i'll try with a clean image but that will take a while
[16:44] <stgraber> I think I can blame bug 960096 on lightdm
[16:44] <ubot2`> Launchpad bug 960096 in ubiquity "Live session started with wrong layout" [Undecided,In progress] https://launchpad.net/bugs/960096
[16:44] <stgraber> (yeah, took me 3 hours to get to that conclusion)
[16:44] <infinity> cjwatson: What would you prefer for base-installer?  Minimal 1-line diff ( http://paste.ubuntu.com/892440/ ), or simplyfying that section to remove all the SMP business?
[16:44] <stgraber> now poking mterry to confirm and hopefully fix it
[16:45] <cjwatson> infinity: something that won't make me go insane when merging in future - I don't mind too much
[16:45] <cjwatson> infinity: remember to update the tests thouogh
[16:46] <infinity> cjwatson: Yeah, I think the tests may alread pass with powerpc-smp, but double-checking.
[16:46] <cjwatson> ogra_: OK - and that could even just be an inadequate preseed file
[16:46] <cjwatson> ogra_: sounds like a good improvement anyway
[16:46] <ogra_> right
[16:46] <ogra_> it definitely is !
[16:46] <ogra_> thanks so much ... i thought i would go insane here :)
[16:47] <ogra_> GrueMaster, ^^^ so we got a huge step forward
[16:47] <cjwatson> ogra_: happy to look at a debconf log from a fresh image if it's not fixed / immediately obvious
[16:47] <ogra_> ok
[16:48] <GrueMaster> Awesome!
[16:48] <GrueMaster> do you have a new preseed for me to try or does this require code changes?
[16:48] <infinity> cjwatson: Looks like the SMP magic comes from Debian, so I'll just go with the 1-line diff, much easier to merge.
[16:48] <ogra_> GrueMaster, we need to add automatic-ubioquity to the cmdline and yes, there are some minor code changes
[16:48] <cjwatson> infinity: OK
[16:49] <GrueMaster> ogra_: ok.  Will wait for your signal to give it a whirl.
[16:49] <ogra_> GrueMaster, i want to let the running install finish and will then start over with a clean image to see if we can get rid of the last bits
[16:49] <ogra_> YAY !
[16:49]  * ogra_ just logged in with ubuntu/ubuntu
[16:50] <ogra_> so even though it asked me the user-sertup question about fullname and login, it applied the preseeded passwd (which it didnt ask for)
[16:51] <cjwatson> blast, I need an amd64 sbuild instance
[16:51] <cjwatson> hooray for mk-sbuild
[17:08] <barry> mk-sbuild is awesome
[17:08]  * barry -> lunch
[17:09] <stgraber> out for lunch too, hopefully this afternoon will be more productive for ubiquity ;) at least I'm pretty familiar with gnome and lightdm's keyboard handling...
[17:09] <cjwatson> https://code.launchpad.net/~cjwatson/partman-partitioning/gpt-boot-partition-855871/+merge/98460 - review/thoughts welcome
[17:10] <cjwatson> dinner
[17:20] <CIA-32> base-installer: adconrad * r971 ubuntu/ (4 files in 3 dirs): Switch to powerpc-smp kernels
[17:41]  * infinity notices that he's hungry, and goes to do something about that.
[17:44] <ogra_> ARGH !
[17:44] <infinity> ogra_: ?
[17:44]  * ogra_ curses unity once more ... so it popped up the SD card nautilus window but the globalmenu still had the close buttons for the terminal i was working in
[17:45] <ogra_> which made me close my work window with all its history
[17:45] <infinity> Global menu follows focus.
[17:45] <infinity> Isn't it a feature that autofs-windows don't steal focus?
[17:45] <ogra_> focus follows mouse here :P
[17:45] <ogra_> and it seems thats still buggy
[17:45] <infinity> You use ffm with global menus?
[17:46] <infinity> That sounds horrifying.
[17:46] <ogra_> (though i heard a lot promises it would be fixed in 12.04)
[17:46] <ogra_> i use FFM since warty
[17:46] <infinity> Sure, I always used to use FFM.
[17:46] <infinity> But I can't see how it would ever play nicely with global menus.
[17:46] <ogra_> and this install is from hoary ... just updated every release
[17:46] <infinity> Unless you have it on a really long delay, and move FAST. :P
[17:47] <ogra_> which got me unity 3D ... but since i havent used any x86 desktop in over a year i never noticed how bad it is
[17:48] <ogra_> anyway, to move to the close button i had to move across the desktop and thus across the fullscreen nautilus window
[17:48] <ogra_> which i would have expected to switch the menu and window buttons to nautilus indeed
[17:49] <ogra_> anyway, thanks god at least the terminal preserved its history
[17:49] <slangasek> with ffm and compiz+unity, I would expect that mousing up to the top bar would cause compiz to recursively generate menus for the bar itself ;)
[17:49] <slangasek> but I guess unity is smarter than that, at least
[17:50] <cjwatson> I used ffm with global menus for a while and it didn't bother me desperately because (a) I tend to use the keyboard to get at menus and (b) if I have multiple windows on the screen then they tend to be terminals and I don't care about their menus anyway
[17:50] <ogra_> well, i'm using unity 3D for the first time in my life this week .... i must admit i'm shocked
[17:50] <cjwatson> but these days I have the global menu turned off
[17:50] <ogra_> i mean, i played with it before ... but never actually used it
[17:50] <ogra_> 2D doesnt have all these issues
[17:50] <cjwatson> 2D just steals your keybindings every other week
[17:51] <infinity> Heh.
[17:51] <ogra_> well, i rarely use much more than alt-tab
[17:51] <cjwatson> not that I'm bitter
[17:51] <ogra_> which doesnt seem to work as i need it at all here atm
[17:51] <ogra_> i never end up in the window i expect to end up in
[17:51] <infinity> Well, to be fair, 2D's keybindings just mimick the 3D defaults.  The problem is that they're all hardcoded. :/
[17:52] <infinity> Sure would love it if some of these Linux programmers remembered what config files were for.
[17:52] <ogra_> bah, and there is another prob with oem-config --automatic ...
[17:52] <ogra_> the upstart job somehow should respect the kernel cmdline setting :P
[17:53] <cjwatson> infinity: yes, on 3D they're configurable and 2D they're hardcoded, as a rule ...
[17:53]  * ogra_ has wonderful debug output from two runs now .... but nothing automatic at all :P
[17:53] <cjwatson> it does, but doesn't have any automatic handling
[17:54] <cjwatson> I suggest you call it automatic-oem-config rather than automatic-ubiquity, in line with debug-oem-config
[17:54] <cjwatson> (might not necessarily want the same for both)
[17:54] <infinity> cjwatson: They're only configurable in 3D because unity happens to be an enormous compiz plugin.  I doubt it was a conscious decision to make them configurable, but rather just how you work in that framework.
[17:54] <cjwatson> infinity: true
[17:55] <cjwatson> ogra_: so http://paste.ubuntu.com/892536/ say?
[17:56] <cjwatson> anyone had a chance to look at my partman-partitioning change?
[17:57] <infinity> I think I missed the call for review.
[17:57] <infinity> 48 minutes ago?
[17:57]  * infinity looks.
[17:57] <cjwatson> 17:09 <cjwatson> https://code.launchpad.net/~cjwatson/partman-partitioning/gpt-boot-partition-855871/+merge/98460 - review/thoughts welcome
[17:58] <infinity> I wonder how much "efi" code in Linux is actually just workaround for Intel Macs above and beyond normal efi handling.
[17:58] <ogra_> cjwatson, heh, thats exactly what i have in my oem-config.conf here too ... but didnt start up the automatic mode it seems
[17:59] <ogra_> well, not using automatic-oem-config but automatic-ubiquity here atm
[17:59] <ogra_> i suspect the various levels of wrappers swallow it somewhere
[18:00]  * ogra_ gets new coffee and will then track that down
[18:02]  * jodh -> foooooood
[18:03] <infinity> cjwatson: Only two questions.
[18:03] <infinity> cjwatson: In the case where you throw your hands up in the air and exit 0, what if I didn't actually intend to boot from a non-GPT disk?
[18:04]  * bdmurray takes lunch
[18:04] <infinity> cjwatson: And should the debconf templates about BIOS/EFI boot partitions perhaps hint at an appropriate size for them?  I'd have no clue what to do if I got that dialog.
[18:05] <jibel> barry, I added a test case to reproduce bug 792652 in a VM (vbox in my case) but I reproduce it more easily on a crappy laptop.
[18:05] <ubot2`> Launchpad bug 792652 in ubiquity "ubiquity crashed with ValueError in command(): I/O operation on closed file" [High,Incomplete] https://launchpad.net/bugs/792652
[18:05] <cjwatson> infinity: Unfortunately, at the partitioning stage, we can't know.  grub-installer will fail later, which I think is regrettably the best we can do in this case.
[18:05] <cjwatson> infinity: I can add size advice, sure.
[18:06] <jibel> barry, also, while reproducing it I got bug 629321 with similar steps but on first step of the installer.
[18:06] <ubot2`> Launchpad bug 629321 in ubiquity "ubiquity crashed with AttributeError in debconffilter_done()" [Undecided,Confirmed] https://launchpad.net/bugs/629321
[18:06] <infinity> cjwatson: Kay.  The answer to the former is unfortunate, but such is life.  The shell looks otherwise sane to me.  Add a bit telling me WTF goes in a boot partition (or just tell me how big it should be), and I'll be happy.
[18:07] <cjwatson> oh, as for what goes in the boot partition, the "EFI boot partition" and "Reserved BIOS boot area" terms there are things you can select in "Use as:"
[18:07] <barry> jibel: cool.  i want to spend a little more time on my current bug, then i'll look at these again.  i think we have a general problem that it's pretty easy to click on buttons that get the front-end out of sync.
[18:07] <infinity> cjwatson: Well, you tell me, I guess ("boot loader code"), but that doesn't mean much to most people. :)
[18:07] <cjwatson> perhaps I need to spell that out?
[18:07] <barry> jibel: but we'll probably have to fix them one-by-one
[18:07] <infinity> cjwatson: Spelling out the type/use-as a bit more might be nice.  I felt it was obvious, but I understand all of this to start with.
[18:08] <infinity> cjwatson: But size is really the glaring omission.  512 bytes, several blocks, several MB, who knows? ;)
[18:09] <cjwatson> infinity: http://paste.ubuntu.com/892553/ maybe?
[18:10] <infinity> cjwatson: That looks much better, yeah.
[18:10] <infinity> cjwatson: Also, 35MB?  What the heck goes in there?
[18:10] <infinity> cjwatson: (I assume the 1MB one is just a stage2 bootloader or something)
[18:10] <cjwatson> minimum size for fat32 ...
[18:10] <infinity> That's not true.    Tool limitation is a reasonable excuse to waste 35MB on people's enormous disks.  It's not like they care anymore.
[18:12] <cjwatson> for a BBP it's actually 31 KiB, but I didn't want to skate too close to the line and introduce KiB/KB confusion since partman speaks in decimal units, and I have a funny feeling it won't let you go smaller than 1MB anyway (ubiquity's manual partitioner won't, at least)
[18:12] <cjwatson> and if you make it that small you risk grub's core image being a bit bigger in some cases, so I normally recommend 1MB
[18:13] <infinity> Yeah, the 1MB one seemed fine.  It's also a very easy number to communicate. :P
[18:13] <infinity> Was just curious about the 35MB.
[18:13] <stgraber> right, so that keyboard layout problem apparently is a gnome-settings-daemon bug that was hidden by a unity-greeter bug and that people thought was an ubiquity bug ;) now to move to something that's actually ubiquity's fault
[18:13] <cjwatson> yeah, I know it's a slightly bizarre number
[18:13] <cjwatson> I think it was actually 32MiB plus a bit for the tables and then modulo rounding, or something.  I worked it out exactly in sectors.
[18:13] <cjwatson>         if [ "$new_efi_size" ] && longint_le "$new_efi_size" 34091007; then
[18:14] <cjwatson> is what I wrote in partman-efi
[18:14] <infinity> Heh.  Fair enough.  This is why it's good to have the value in the dialog. ;)
[18:14] <cjwatson> yeah
[18:14] <infinity> Cause if I saw "boot loader code", I'd just make it tiny.
[18:15] <infinity> And it would fail later, I assume, when parted tried to format it fat32.
[18:15] <cjwatson> partman-efi would've warned you in a subsequent go-around if you made it too small, but that's tedious
[18:15] <infinity> Unless there's a check in place when you mark it for EFI Boot.
[18:15] <cjwatson> there is (bug 811485
[18:15] <cjwatson> )
[18:15] <ubot2`> Launchpad bug 811485 in partman-efi "EFI SYSTEM PARTITION should be atleast 100 MiB size and formatted as FAT32, not FAT16" [High,Fix released] https://launchpad.net/bugs/811485
[18:15] <infinity> Anyhow.  New text looks good.
[18:16] <CIA-32> partman-partitioning: cjwatson * r913 ubuntu/ (6 files in 3 dirs):
[18:16] <CIA-32> partman-partitioning: On systems with only GPT disks, check that an EFI System Partition or a
[18:16] <CIA-32> partman-partitioning: BIOS Boot Partition exists, as appropriate (LP: #855871).
[18:16] <CIA-32> partman-partitioning: cjwatson * r914 ubuntu/debian/partman-partitioning.templates: add size recommendations, per adconrad
[18:16]  * infinity really goes to find food now.
[18:17] <CIA-32> partman-partitioning: cjwatson * r915 ubuntu/debian/po/ (70 files): debconf-updatepo
[18:19] <CIA-32> partman-partitioning: cjwatson * r916 ubuntu/debian/changelog: releasing version 83ubuntu2
[18:24] <ogra_> heh, as i thought, oem-config-wrapper actually swallows the --automatic
[18:24] <ogra_> err
[18:24] <ogra_> oem-config-firstboot i mean
[18:25] <ogra_> ugh
[18:25] <ogra_> and that looks like it needs a proper option parser too
[18:25] <ogra_> DEBUG=
[18:25] <ogra_> if [ "$1" = '--debug' ]; then
[18:25] <ogra_>         DEBUG=--debug
[18:25] <ogra_> fi
[18:26] <infinity> For just two options, a simple case walk through $@ is enough.
[18:26] <infinity> But it's never too early to use getopts.
[18:26] <ogra_> bah, nah
[18:26] <ogra_> i'm not a getopts fan
[18:27] <ogra_> $@ and case :)
[18:28] <GrueMaster> ogra_: cjwatson had a pastebin earlier that had a fix for that.
[18:28] <ogra_> though ... i dont actually see $DEBUG used in -firstboot, i could just hand $@ through to the actual execution call
[18:28] <ogra_> GrueMaster, nope, that was the same fix i already have for the upstart job
[18:28] <ogra_> this is deeper down the trail
[18:29] <GrueMaster> Ah.  different wrapper.
[18:29] <ogra_> yeah, this is oem-config-firstboot
[18:29] <infinity> ogra_: DEBUG is used.
[18:29] <cjwatson> right, I only fixed part of it
[18:29] <infinity> ogra_: Sets TRY.
[18:29] <GrueMaster> maybe we need another wrapper to fix it?
[18:29] <ogra_> oh, i see
[18:29] <ogra_> yeah
[18:30] <infinity> But a simple case walk and setting AUTOMAGIC as well would work fine.
[18:30] <ogra_> GrueMaster, its two options we want to parse ... we will need two wrappers !
[18:30] <GrueMaster> :P
[18:30] <ogra_> oir five just because its oem-config ...
[18:31] <ogra_> seriously we should have a blueprint to clean that up some day
[18:31] <doko> jodh, are you working on 946663 now?
[18:31] <GrueMaster> Need to use a different language though.  bash, perl, and python have been used.  Need something more obscure.  Logo or Lisp maybe?
[18:31] <ogra_> way to many wrappers in the stack
[18:31] <ogra_> vala !
[18:31] <ogra_> and ruby
[18:32] <infinity> PHP, obviously.
[18:32] <ogra_> only for the lowest level where security matters
[18:32] <infinity> And then we get a whole host of bugs like "I ran the installer with php_safe_mode=on, but it still formatted my disks".
[18:32] <infinity> And I die a little inside.
[18:33] <GrueMaster> Could be an excuse to keep mono in the images.
[18:33]  * GrueMaster hides
[18:33] <ogra_> now thats a good idea and finally a reason to move to full DVD images
[18:33] <cjwatson> I think python is the only language to have the distinction of having formatted people's disks during Ubuntu installation due to a language bug
[18:33] <infinity> cjwatson: *cough*
[18:33] <ogra_> not these lame 1.5G thingies
[18:34] <cjwatson> bug 40464
[18:34] <ubot2`> Launchpad bug 40464 in ubiquity "espresso crashes on partitioning step in Kubuntu 6.06 LTS Beta Live CD" [Critical,Fix released] https://launchpad.net/bugs/40464
[18:43] <cjwatson> jodh: have you had a chance to make those minor adjustments to your branch from earlier today?  If you can do that then I can get it landed.
[18:43]  * cjwatson has yet another go at reproducing bug 745960
[18:43] <ubot2`> Launchpad bug 745960 in grub2 "Cannot boot GRUB after installing to LVM" [High,Incomplete] https://launchpad.net/bugs/745960
[18:45] <ogra_> http://paste.ubuntu.com/892594/
[18:45] <ogra_> coudl someone give that a glance before i commit and push
[18:45] <cjwatson> 'for option in $@; do' can just be 'for option; do' IIRC
[18:46] <cjwatson> which reduces quoting worries
[18:46] <ogra_> oh, and i missed to set AUTOMATIC
[18:46]  * ogra_ fixes
[18:46] <cjwatson> initialise?  yeah
[18:46] <cjwatson> looks fine, anyway - I assume you didn't close a bug because it's only part of Tobin's bug
[18:47] <infinity> cjwatson: Can you give http://paste.ubuntu.com/892595/ a once-over?
[18:47] <ogra_> right, it will need your first fix too
[18:47] <ogra_> after i actually verified it
[18:47] <infinity> cjwatson: The Makefile change is just an optimisation (sha256 while we have a warm cache instead of making cdimage do it later)
[18:47] <cjwatson> we didn't have sha256sum already?  wow.
[18:47] <cjwatson> ah
[18:48] <ogra_> comitted and pushed (damned where is my CIA setup gone :/ )
[18:49] <cjwatson> infinity: that's not quite right for the case where it builds binaries and sources.  (we may not use that, but still)
[18:49] <infinity> cjwatson: No?
[18:49] <cjwatson> because it's important in that case that OUT is changed
[18:49] <cjwatson> 'make imagesums' is dependent on the current value of $OUT
[18:49] <infinity> cjwatson: Oh, indeed.  Bother.
[18:50] <cjwatson> we could move the compression code around instead (and duplicate it :-/)
[18:51] <ogra_> oh, do we have a manpage or any doc i need to add the new option to ?
[18:51] <infinity> cjwatson: Or, I could put the first make imagesums back in (the one in the sub-if).
[18:51] <infinity> cjwatson: Oh, but that's unhelpfully a binary image, not a source image.
[18:51] <cjwatson> ogra_: possibly something on the wiki, can't quite remember ...
[18:51] <cjwatson> *cough*
[18:51] <ogra_> k, i was more about something in the branch :)
[18:52] <infinity> cjwatson: If I inverted that and build the source first, that would work.  Since compress is only for binary images (I think?), and then OUT would always be right for binaries.
[18:52] <cjwatson> oh, what do you know, there's doc/oem-config-firstboot.8
[18:52] <ogra_> heh, ok
[18:52] <cjwatson> that was a bit enthusiastic of me
[18:52]  * ogra_ still waits for bzr to return
[18:52] <cjwatson> infinity: true, yes
[18:53] <cjwatson> it's bin-compress_images so it'd better be just binaries
[18:54] <infinity> You'd think, right?
[18:55] <cjwatson> naivete, I know
[19:09] <ogra_> http://paste.ubuntu.com/892624/
[19:09] <ogra_> cjwatson, .... just pro-forma
[19:09] <ogra_> hmm, probably one "and" to much
[19:09] <cjwatson> also in SYNOPSIS
[19:10] <ogra_> both fixed
[19:11] <cjwatson> (and man -l it to check, of course)
[19:11] <ogra_> hmm, i wonder, shouldnt the manpage also list the kernel cmdline options
[19:11] <ogra_> to have them documented *somewhere*
[19:12] <cjwatson> mm, maybe
[19:12] <cjwatson> wouldn't be totally wrong :)
[19:12] <slangasek> https://code.launchpad.net/~vorlon/update-notifier/lp.876298/+merge/98487
[19:13] <ogra_> hmm., where do i put that, just in the flowing text that describes the option ?
[19:15] <cjwatson> I guess, or maybe a separate section
[19:16] <ogra_> http://paste.ubuntu.com/892639/
[19:18] <infinity> cjwatson: Here, have a completely unreadable diff: http://paste.ubuntu.com/892643/
[19:18] <CIA-32> ubiquity: stgraber * r5283 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py): Mark the quit dialog as transient for the live installer dialog.
[19:20] <cjwatson> infinity: (a) tab damage (b) that looks like it unconditionally generates source images
[19:20] <infinity> cjwatson: Only in the same case when it always did.
[19:20] <infinity> cjwatson: And the tab damage might just be cut and paste damage, that was bzr diff -> X primary buffer -> pastebin.
[19:21] <infinity> cjwatson: (But I'll double check the indenting)
[19:22] <stgraber> ogra_: can you configure CIA?
[19:22] <stgraber> I didn't see 5282 on IRC
[19:22] <infinity> cjwatson: Oh, no, it's vim hating me.
[19:22] <ogra_> stgraber, yeah, sorry, i had it configured, but re-pulled my branches once
[19:22] <cjwatson> I'm totally confused.  pastebinit, maybe?
[19:23] <infinity> cjwatson: http://paste.ubuntu.com/892656/
[19:23] <cjwatson> ogra_: just a bit of Deutschlisch :)
[19:23] <cjwatson> If the option
[19:24] <ogra_> haha
[19:24] <cjwatson> .Ic automatic\-oem\-config
[19:24] <ogra_> k
[19:24] <cjwatson> is set on the kernel command line at boot time, this option is used automatically.
[19:24] <cjwatson> something like that
[19:24] <infinity> cjwatson: It might make a bit more sense with the sane whitespace there. :P
[19:24] <ogra_> let me fix my CIA first
[19:24] <cjwatson> ah, yes, that's much more comprehensible
[19:25] <ogra_> to nao make stephane crazy
[19:25] <ogra_> *not
[19:25] <infinity> cjwatson: Basically, source always happened unconditionally in that block, I just do it first now, instead of second.
[19:25] <stgraber> ogra_: ;)
[19:26] <infinity> cjwatson: The only remaining optimisation would be to not do the final imagesums if it's an ONLYSOURCE build, so it's not done twice.
[19:26] <cjwatson> infinity: I think that's fine, yes, although the log output might make a little more sense if you moved 'make list' to be just before the binary build in the first block
[19:27] <infinity> cjwatson: Doesn't the source build depend on one of "make list" or "make src-list" being run first?
[19:27] <cjwatson> oh, I guess it might
[19:27] <cjwatson> ignore me then
[19:27] <infinity> cjwatson: (I was assuming make list is a superset of make src-list, given the original code)
[19:27] <cjwatson> I forget what all the targets do
[19:27] <ogra_> cia-project for ubiquity is just ubiquity, right ?
[19:27] <cjwatson> list: bin-list src-list
[19:28] <infinity> Check.  The shell implied that make dependency. :)
[19:28] <cjwatson> yeah, ignore me then
[19:28] <cjwatson> ogra_: yes
[19:28] <infinity> Right, I'll just add an ONLYSOURCE guard on the final imagesums, so we don't sum ONLYSOURCE builds twice, and call it good.
[19:29] <ogra_> k, should be set up
[19:30] <bdmurray> barry: I think i've come up with a test case for bug 792652
[19:30] <ubot2`> Launchpad bug 792652 in ubiquity "ubiquity crashed with ValueError in command(): I/O operation on closed file" [High,Confirmed] https://launchpad.net/bugs/792652
[19:32] <bdmurray> barry: its similar to the updated description
[19:32] <barry> bdmurray: awesome.  please add it as a comment; i'm going to look at that one again after i finish with my current bug
[19:34] <CIA-32> ubiquity: ogra * r5284 trunk/ (debian/changelog doc/oem-config-firstboot.8): add an entry for the new option in oem-config-firstboot manpage
[19:34] <cjwatson> e.g. create_or_update_stampfile could be:
[19:35] <cjwatson> with open(file, 'w'):
[19:35] <cjwatson>     pass
[19:35] <ogra_> great, CIA still works :)
[19:35] <cjwatson> and stuff round that
[19:35] <cjwatson> (or 'with open(filename, 'w') as filehandle:')
[19:37] <ogra_> geez !
[19:38]  * ogra_ was just looking for bterm at google (since i suspect it doesnt properly clean up after itself on serial consoles ) ...
[19:38] <ogra_> that gets me "Ballistic Trajectory Extended Range Munition"
[19:43] <cjwatson> jodh: https://code.launchpad.net/~cjwatson/launchpad/refactor-cron-germinate/+merge/84624
[19:43] <jodh> cjwatson: thanks!
[19:43] <cjwatson> you can see comments and commits interleaved quite extensively theere
[19:43] <cjwatson> *there
[19:45] <slangasek> cjwatson: if I do 'with open(file)', do I have to handle exceptions from that?
[19:46] <cjwatson> yes
[19:46] <slangasek> ok
[19:46] <cjwatson> it doesn't really matter in a script this size, but it's good in larger/longer-running programs because it means that you don't have to worry about leaked file objects due to exceptions
[19:46]  * slangasek nods
[19:47] <cjwatson> (and it's more concise than finally handlers)
[19:48] <CIA-32> ubiquity: cjwatson * r5285 trunk/ (debian/changelog scripts/install.py): merge lp:~jamesodhunt/ubiquity/bug-944191
[19:48] <cjwatson> jodh: thank you :)
[19:48] <stgraber> ev: I'm current looking at https://code.launchpad.net/~themuso/ubiquity/indicator-accessible-desc/+merge/50866 but I think you're more familiar with the panel than I am
[19:49] <stgraber> it's a year old but I don't see anything wrong with it, though I'm not sure if it's still relevant (it's not linked to a bug report so doesn't help)
[19:51] <ev> stgraber: will have a look as soon as I'm done with bdmurray's apport question
[20:09]  * ogra_ goes for dinner
[20:10] <cjwatson> Any objections to http://paste.ubuntu.com/892737/ ?
[20:13] <infinity> cjwatson: Seems straighforward.
[20:13] <cjwatson> 's what I thought.  Just came across it in the bug list.
[20:13]  * cjwatson commits and runs through sbuild.
[20:18] <cjwatson> (By the way, if you're still using pbuilder, stop.)
[20:19] <infinity> Still implies that I ever did.
[20:19] <cjwatson> I made the mistake of using it for a while.
[20:19] <cjwatson> Albeit not that long.
[20:19] <infinity> I'd sooner date Oli.
[20:28] <slangasek> is it ok if i just use pbuilder-stop?
[20:28] <infinity> slangasek: What's pbuilder-stop?
[20:29] <slangasek> infinity: it's like stop but it hides all the complexity
[20:29] <slangasek> works nearly as well
[20:29] <infinity> slangasek: That didn't help me. :P
[20:30] <slangasek> infinity: it was a joke, sorry :)
[20:31] <infinity> slangasek: I don't appreciate sarcasm at work, good sir, and I'd prefer you acknowledge that and adjust accordingly.
[20:32]  * infinity goes coffee hunting.
[20:48] <doko> stgraber, trying to run virt-manager, I always get "Error: no active connection to install on", however libvirt-bin is running
[20:49] <ev> stgraber: I suspect it is relevant
[20:49] <ev> s
[20:49] <ev> (sorry for the delay)
[20:49] <ev> best way to check would be firing up orca inside the installer maybe-ubiquity session
[20:49] <ev> (you can access that via the isolinux accessibility menu)
[20:50] <ev> if you can't get it to read option in the panel, try again with luke's patch in place
[20:50] <ev> options even
[20:50] <slangasek> stgraber: ^^ I pointed doko at you for this virt-manager question; dunno if you use v-m but I figure you'd be most likely to know :)  (it works fine for me)
[20:51] <stgraber> doko: are you in the libvirtd group?
[20:53] <doko> stgraber, ahh ...
[20:58] <barry> cjwatson: https://code.launchpad.net/~barry/ubiquity/bug-959724
[20:59] <barry> cjwatson: or better https://code.launchpad.net/~barry/ubiquity/bug-959724/+merge/98515
[21:16] <cjwatson> barry: that looks like a reasonable basic approach to me, yes
[21:17] <cjwatson> well spelunked - that plugin is difficult
[21:17] <barry> cjwatson: it was fun :)
[21:17] <barry> cjwatson: thanks for the sanity check
[21:25] <stgraber> ev: any idea why http://paste.ubuntu.com/892848/ doesn't work?
[21:26] <stgraber> ev: I want to override http://paste.ubuntu.com/892853/ from gtk-widgets.css
[21:28] <ev> looking
[21:33] <ev> stgraber: could I see the full patch?
[21:33] <ev> this isn't applying to trunk
[21:34] <stgraber> stgraber@arkose-tmpOGC54U:~/data/code/ubiquity/ubiquity$ patch -p0 < ~/Desktop/plain
[21:34] <stgraber> patching file src/panel/panel.c
[21:34] <stgraber> ev: applies fine here
[21:34] <ev> hmm
[21:36] <ev> oh, whitespace
[21:55]  * cjwatson works on bug 783295
[21:55] <ubot2`> Launchpad bug 783295 in ubiquity "11.04 install drives itself to an error on '!' in the name" [Medium,Triaged] https://launchpad.net/bugs/783295
[21:56] <stgraber> ev: any idea of what's going on? I'd go look at the gtk3 css documentation but last I checked it was still to be written ...
[21:57] <ev> trying to reproduce it here first, as the panel works fine in a unity session
[21:57] <ev> but offhand, no
[21:58] <ev> Gtk CSS is evil, evil stuff
[21:58] <ev> I'm just amazed it stopped segfaulting when it couldn't parse it
[21:58] <ev> (because things were ordered in a fashion it wasn't expecting)
[21:59] <barry> slangasek: don't know if you were planning on doing a wrap up for today, but i need to take off on time tonight
[21:59] <slangasek> barry: no wrap-up planned
[21:59] <cjwatson> https://code.launchpad.net/~cjwatson/ubiquity/default-username-783295/+merge/98527
[21:59] <barry> slangasek: ok!  see you tomorrow then
[21:59]  * ev looks
[21:59] <slangasek> barry: 'night!
[22:00]  * slangasek converts flashplugin-nonfree from cdbs to dh, thbbt
[22:03] <infinity> Oh hey, I guess it is kinda quittin' time.
[22:03]  * ogra_ is out too ... have a good one everybody
[22:03] <ogra_> (see you at the virtual bar *g*)
[22:04] <ev> :)
[22:04] <infinity> ogra_: If only.
[22:04] <ogra_> heh
[22:04] <slangasek> infinity: ?
[22:05] <bdmurray> at least in my tz I get more happy hour
[22:05] <slangasek> YES
[22:06] <ogra_> in mine i would have to drink in the morning ... i doubt that improves my working that i do in yours later in the day :)
[22:07] <cjwatson> anything else that's pending merge before I start putting a ubiquity upload together?
[22:09] <stgraber> cjwatson: nope, my fix doesn't work and it's far from critical anyway (just making the UI look as it's supposed to) so can wait tomorrow
[22:11] <jodh> ttfn...
[22:15]  * bdmurray wanders off
[22:17] <CIA-32> ubiquity: cjwatson * r5286 trunk/ (3 files in 3 dirs): Strip invalid characters from default username (LP: #783295).
[22:25] <CIA-32> ubiquity: cjwatson * r5287 trunk/ (d-i/manifest debian/changelog):
[22:25] <CIA-32> ubiquity: Automatic update of included source packages: base-installer
[22:25] <CIA-32> ubiquity: 1.122ubuntu6, console-setup 1.70ubuntu4, partman-basicmethods 49,
[22:25] <CIA-32> ubiquity: partman-jfs 35, partman-newworld 26, partman-partitioning 83ubuntu2,
[22:25] <CIA-32> ubiquity: partman-reiserfs 52, partman-xfs 49.
[22:37] <CIA-32> ubiquity: cjwatson * r5288 trunk/debian/changelog: releasing version 2.9.31
[22:46] <cjwatson> OK, I think that's it for today - I'll just check back a bit later to make sure ubiquity hasn't failed to build or anything
[22:46]  * slangasek waves
[22:46] <cjwatson> etherpad's updated and I've let Nick know
[22:53] <slangasek>         db_text medium flashplugin-installer/not_exist || true

[22:58] <infinity> slangasek: Are you sure it isn't time to just re-do the package from scratch?
[22:59] <infinity> slangasek: I mean, really, what does it need to do?  Download something and unpack it.
[22:59] <slangasek> infinity: the plastic surgery I'm doing here might as well be a re-do
[22:59] <infinity> That's not rocket surgery.
[23:00] <slangasek> I particularly like the bit in the .config script where at the top of the script we call sha256sum on the file in the suggested local path *twice*, and then we follow it with a loop in which we check for file *existence* and never checksum it
[23:05] <stgraber> ev: yay for gtk3! http://paste.ubuntu.com/892968/ :)
[23:05] <ev> heh
[23:06] <cjwatson> db_text?  What is this, 1999?
[23:10] <slangasek> was that *ever* a valid debconf command?
[23:10] <slangasek> I thought it was always db_input + Type: text
[23:12] <slangasek> anyway, I've quite thoroughly gutted the package now
[23:13] <stgraber> ev: I'll read all the existing gtk documentation one more time and if I still can't make it to work with the inline css, then I'll just push that diff to ubiquity's trunk and be done with it ;)
[23:13] <ev> :)
[23:14] <stgraber> at least reading ALL the css documentation for gtk only takes a minute or so ;)
[23:15] <ev> hahaha
[23:23] <stgraber> ev: right, so http://paste.ubuntu.com/892989/ works
[23:23] <stgraber> I'm pretty sure I tried something very close to that earlier and it failed, but well, the lack of error message doesn't help...
[23:24]  * ev looks
[23:24] <ev> yeah
[23:25] <ev> as I was saying before, I think the ordering of things breaks it in subtle ways
[23:25] <ev> or whitespace
[23:25] <ev> or the phase of the moon
[23:26] <stgraber> well, thinking of it, it started working after the sunset here, maybe it just doesn't like sunlight :)
[23:28] <CIA-32> ubiquity: stgraber * r5289 ubiquity/ (debian/changelog src/panel/panel.c): panel: Fix the gtk3 css code so that it actually applies and remove .menuitem's padding.


[01:15] <vorlon> xnox: I'm thinking the d-i-requirements seed should just be dropped
[10:29] <Piraty> does ubuntu maintain a list / feed of known bug that are yet to be patched ? think of the one that made containers crash host kernel a few weeks ago, so people consumingt his feed would refrain from upgrade
[10:33] <rbasak> Piraty: there's a public bug tracker: https://bugs.launchpad.net/ubuntu. But many people report bugs that turn out not to be bugs, and there are plenty of low priority bugs that never get patched. So I don't think it'd be useful for the purpose you suggest.
[10:33] <rbasak> Too many people argue about the importance of individual bugs for a list to be useful to someone else with different priorities.
[10:34] <rbasak> But if there's a particular bug that you care about, then the bug tracker will tell you about the status of that bug.
[10:34] <ogra> known bugs are also in the release notes and these are usually getting fixed fast ... but that is indeed only true for all bugs found *before* release ...
[10:38] <Piraty> i'm afraid i'm incompetent on terminology here, regarding "release" . i mean i'm on 22.04 and would like to know before i `apt update && apt upgrade` if possibly run into stuff like https://lwn.net/Articles/899420/ , given it is known / publicly announced and has not yet been patched . (i know , might be unlikely but not impossible)
[10:39] <Piraty> release notes are published once 22.04 tagged / branched i assume. are there release notes mid-lifetime of a release ?
[10:39] <Piraty> or bug announcements ?
[10:40] <Piraty> in a specific plase i could subscribe to
[10:40] <Piraty> * place
[10:41] <Piraty> on bugs.launchpad.net/ubuntu, when clicking on a item to 'order by', i get "Server error, please contact an administrator. OOPS ID:OOPS-8cd4373eb3b28edd752c6a54c7c0d861"
[10:58] <rbasak> Open bugs known to affect 22.04: https://bugs.launchpad.net/ubuntu/jammy/
[10:58] <rbasak> That's a more manageable number. But it's still dependent on people actually marking the bugs, and the accuracy of that list.
[12:05] <Piraty> thanks rbasak
[15:46] <hawk> juliank: I was asking about this in #ubuntu and it was suggested I ask you here, I am seeing this dist-upgrade result today on 22.04, with lots of removals that seem to maybe be a relate to the held back phased updates(?), https://pastebin.com/raw/tztEuqmY
[15:49] <hawk> s/be a//
[15:57] <jbicha> sil2100: ^
[16:48] <bdmurray> oSoMoN: Do you know what 'cannot use snap "firefox": default provider "hunspell-dictionaries-1-7-2004" is missing' from a livefs build failure might be about? https://launchpadlibrarian.net/624942173/buildlog_ubuntu_kinetic_amd64_ubuntu_BUILDING.txt.gz
[16:49] <oSoMoN> bdmurray, yes, that's https://bugzilla.mozilla.org/show_bug.cgi?id=1792006, and we're working on it
[16:50] <bdmurray> oSoMoN: ah, thanks!
[17:25] <bdmurray> oSoMoN: Is there a timeline for getting this sorted? ginggs just reminded me the beta is very soon
[17:49] <fenris> anyone using proposed repo in kinetic kudu?
[17:50] <fenris> The following packages have unmet dependencies:
[17:50] <fenris>  gnome-shell-extension-ubuntu-dock : Depends: gnome-shell (< 43) but 43.0-1ubuntu1 is to be installed
[17:50] <fenris> E: Unable to correct problems, you have held broken packages.
[17:51] <mdeslaur> hopefully not, it's not supposed to be used
[17:51] <fenris> need to remove the 3 packages: gnome-shell-extension-ubuntu-dock ubuntu-desktop ubuntu-desktop-minimal
[17:52] <bdmurray> Using -proposed for the development release of Ubuntu is not recommended
[17:53] <fenris> @bdmurray: for sure we need to accept the consequence before enabled it  .. wink .. but just asking the dev here
[17:53]  * fenris finger cross
[17:54] <bdmurray> fenris: I'm not sure what kind of answer you are looking for but you've heard from two Ubuntu Core Developers not to use -proposed.
[17:57] <fenris> noted @bdmurray , the answer i might or expect is there will be another build with those related packages will support gnome-shell 43
[18:03] <enr0n> I am looking for a MOTU or core dev to review and sponsor bug 1990562
[18:05] <enr0n> ginggs: ^ this resolves the numpy FTBFS in the test rebuild
[18:11] <jbicha> fenris: yes, we already know about the ubuntu-dock issue & will fix it. But even the devs don't run proposed during the development release
[18:15] <oSoMoN> bdmurray, yes, I'm hoping for a fix to land tomorrow, Monday at the latest
[18:16] <oSoMoN> nteodosio is working on the fix
[18:19] <bdmurray> oSoMoN: ack, thanks
[18:20] <fenris> thanks @jbicha
[18:29] <jbicha> oSoMoN: do you want to push an older firefox to the latest/stable/ubuntu-22.10 channel so that we can keep building ISOs until it's fixed?
[18:42] <ginggs> enr0n: nice!  i suspect that will be picked up in debian quickly and we'll be able to sync
[18:46] <enr0n> ginggs: sounds good, I did forward it
[18:48] <oSoMoN> jbicha, I can do that, but that will be an outdated version (CVE-wise)
[19:03] <jbicha> oSoMoN: I just thought it would be interesting practice since I don't think we've used the distro series channel before. But it sounds like the fix will be soon so either way.
[21:04] <jbicha> bdmurray: see the earlier discussion about python3 phased updates causing users problems on jammy. Should we fully phase python3*
[21:07] <jbicha> or set the phasing to 0% temporarily?
[21:08] <jbicha> users can avoid this problem by running `sudo apt upgrade` instead of blindly running `sudo apt dist-upgrade` and not paying attention
[21:08] <jbicha> I was able to reproduce the problem by changing my /etc/machine-id to something that triggered the right mismatched phasing
[21:10] <bdmurray> jbicha: actually modifying the phasing will require an AA e.g. vorlon
[21:14] <bdmurray> fully phasing it seems better than the alternative though
[21:21] <jbicha> I opened bug 1990586
[21:28] <bdmurray> thanks
[22:02] <vorlon> bdmurray, jbicha, juliank: yes, python3.10 / python3-defaults / python3-stdlib-extensions phased to 100%
[23:47] <sarnold> vorlon: this feels like something you might know off the top of your head https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1990326


[00:01] <jbicha> you can kill nemo-fileroller from the new queue as it's already been synced from debian
[05:01] <rsalveti> infinity: sure, thanks
[20:13] <jbicha> http://extras.ubuntu.com/ubuntu/dists/ is missing the devel>saucy symlink that the other official apt repos have
[20:56] <cjwatson> jbicha: Yeah, I know, but I may need to redo the implementation of devel anyway (you get warnings from apt if you actually try to use it), so I'm not worrying about completing coverage just yet.
[21:08] <stgraber> cjwatson: I saw the apt warnings here when testing it too, though I assumed we'd change apt to ignore those rather than change the implementation to generate new Release files
[21:09] <stgraber> cjwatson: doing the latter will make it harder to revert from devel to whatever's the current release since the plan there was to look for the series name in Release
[21:09] <stgraber> cjwatson: (unless we can easily add a new entry in Release to tell us what the real series is)
[22:02] <jbicha> ScottK: could you maybe look at bug 1092719 since Laney's out for a few days?
[22:02] <ubot2`> Launchpad bug 1092719 in gnome-disk-utility (Ubuntu) "FFe: Update gnome-disk-utility to 3.8" [Wishlist,Confirmed] https://launchpad.net/bugs/1092719


[01:35] <Schyken> Heyo!
[01:35] <ted67mustang> hey
[01:36] <Schyken> Slowly working on transitioning my desktop from Fedora to Ubuntu MATE. Waiting for data exports to finish.
[03:23] <chriswere[m]> Hey folks, I'm having a bit of a nightmare with my firewall and I can't work out what the heck is up. I have a connection established via my VPN, I have UFW setup so that it allows in and out through tun0 (and ipv6) , but when I activate it, I get disconnected. It seems to be working fine yesterday, but I'm stumped.
[03:28] <m4t> is it allowing traffic to and from the vpn endpoint (e.g. over eth0)?
[03:32] <chriswere[m]> I'm not sure, how can I check that?
[03:37] <chriswere[m]> These are my current settings https://pastebin.com/3tdhtx7q
[03:50] <m4t> chriswere[m]: allow all outgoing on your lan too. or at least to the vpn server you're connecting to.
[03:54] <chriswere[m]> I only turn the firewall on when the VPN connection is established, shouldn't that be enough?
[03:55] <m4t> if you have related/established it might be
[03:56] <m4t> also need a route to make sure traffic to the vpn endpoint isn't attempted to be routed over the vpn itself..though if it's working w/out firewall enabled i'd say it exists
[03:57] <chriswere[m]> It used to work, just allowing tun0 traffic, I don't know what's changed to cause this issue.
[04:04] <chriswere[m]> Fucking hell! One of my other Discord rooms got hacked and it making noises.  Wrong room.
[06:50] <Schyken> Hey guys, is there a hotkey to send the current window to a particular workspace?\
[06:50] <Schyken> Like, in i3 you can use something like Ctrl+Mod+2 to send the active window to the second workspace
[06:51] <Schyken> Not sure if the window manager in UM supports this, or things kinda like it?
[06:55] <m4t> i dunno https://github.com/mate-desktop/marco/issues/297
[07:40] <mate|19616> Hello. Just installed Ubuntu Mate 18.04, ran updates, but when i try to shutdown, the laptop always just RESTARTS. Secure boot is off. The same happens with command shutdown -h now. Is there some way to fix this? This machine is just about to go to a newcomer.
[07:42] <wuyong> hello everyone
[07:44] <alkisg> mate|19616: what happens if you run sudo poweroff -fp ?
[07:44] <alkisg> Does it shut down?
[07:45] <mate|19616> Ok let me try, be right back...
[07:49] <mate|76727> Same thing happened... a restart
[07:50] <alkisg> mate|76727: did it ever work properly, in any distro/version?
[07:52] <mate|76727> i have not tried other distros, but on live usb shutting down did work. i'm pretty sure before doing any updates too.
[07:54] <mate|76727> i have just installed and put up everything this person needs, is there no way fixing this? could it be a laptop issue? this is Acer E1-470
[07:55] <mate|76727> could not find anyone else having this same problem with 18.04 so...
[07:57] <mate|76727> i was wondering on making a script on desktop with poweroff command or so, but it seems to be in vain in this case as terminal commands do the same: laptop always restarts
[07:58] <gnugr> mate|76727: please try for instance 'systemctl enable halt.service' then try again 'systemctl poweroff'
[08:00] <mate|76727> ok thanks, will try then.... be back
[08:04] <mate|86572> Yep, even still a restart... this must be some hardware issue on this laptop?
[08:04] <gnugr> mate|86572: what connection you use, wifi or cable?
[08:06] <mate|86572> wifi
[08:08] <gnugr> mate|86572: is possible to check it for instance with cable, because i suspect lack of wifimanager.service causes the issue
[08:09] <mate|86572> yes it's possible... will try and report back again...
[08:16] <mate|38641> on ethernet cable, a restart even still....
[08:16] <gnugr> hmmm....
[08:17] <gnugr> i guess a systemd service stucks with ACPI
[08:18] <mate|38641> maybe a non systemd distro such as MX would do it?
[08:19] <mate|38641> this is the only issue though, i wouldnt want to do all the work over again of course
[08:21] <alkisg> mate|38641: didn't you say that it works on the live usb stick?
[08:22] <gnugr> mate|38641: please check if that fix is related https://askubuntu.com/questions/132143/stuck-on-reboot-and-shutdown/135568#135568
[08:22] <mate|38641> yes i said that. i can try again on live usb to make sure...
[08:23] <alkisg> If it works there, then surely there's a way to make it work in the installed system too
[08:24] <alkisg> IF you installed proprietary drivers (nvidia, ati..) maybe some of them is causing that, as the live cd doesn't use those
[08:24] <mate|38641> i did not, intel graphics on this one. maybe i'll just try that grub modification there (12.04 era...) ?
[08:25] <alkisg> If it works on the live cd, it's not an acpi issue
[08:25] <alkisg> Verify the live shutdown first
[08:26] <mate|38641> Ok will do live thing then.... be back again...
[08:32] <mate|25962> Yes! On live usb Mate did shut down
[08:34] <mate|25962> So i guess i'll try this one then? https://askubuntu.com/questions/132143/stuck-on-reboot-and-shutdown/135568#135568
[08:39] <gnugr> mate|25962: please also check if you have 'laptop-mode-tools' installed
[08:40] <mate|25962> ok... modified grub... updating grub... checking those too then
[08:41] <mate|25962> Ok laptop-mode-tools were NOT installed
[08:42] <mate|25962> i guess it's a reboot then again and shutdown attempt after that
[08:42] <mate|25962> brb
[08:50] <mate|1558> Ok it worked, thanks for this alrady! Shuts down properly, but now the WIFI is gone :/
[08:52] <mate|1558> no wifi networks can be found
[08:52] <gnugr> what card you have?
[08:53] <mate|1558> inxi -N gives:
[08:53] <mate|1558> Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
[08:53] <mate|1558>            driver: r8169
[08:53] <mate|1558>            Card-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
[08:58] <gnugr> mate|1558: edit again '/etc/default/grub', remove the 'acpi=noirq', do again 'update-grub' to see if with package 'loaptop-mode-tools' is working
[08:59] <mate|1558> Ok will do... brb...
[09:05] <mate|59552> Yes, the laptop-mode-tools did the trick. Thanks a million. My behind is saved as the person already waits for this laptop... So, should i report this somewhere? A bug or?
[09:07] <gnugr> mate|59552: is wifi visible?
[09:09] <mate|59552> yes, and shuts down correctly
[09:10] <gnugr> OK tho
[10:47] <dmn__> Hi! How do I stick panels to the monitor so it wont move to another when I disconnect one?
[10:47] <dmn__> I have panels on both primary laptop display and external one, and whn I disconnect external I have duplicated panels on primary display
[11:47] <dmn__> https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1714211 :(
[13:21] <Paddy_NI> I am running Ubuntu Mate 18.04 from a live USB on a Macbook Air (mid 2013) and I am trying to mount the internal SSD.  I have installed hfsplus, hfsprogs and hfsutils.  Unfortunately it still will not mount, I am guessing I require a reboot!  This would be pointless with a live usb.  Any ideas?
[13:22] <Paddy_NI> I also tried running "sudo modprobe hfsplus"
[13:33] <sixwheeledbeast> not well up on Mac stuff... but are you using a amd64+mac image and does the drive have journaling enabled?
[18:40] <nzar> hey guys
[18:41] <nzar> just have to note that ukrainian language support in mate is awful
[18:41] <nzar> keep that on note
[18:43] <nzar> @biotim
[18:43] <nzar> wow it's working
[18:51] <nzar> fuck you
[20:40] <Pinkerton> after upgrading to 18.04 has anyone run into issues with some applications not picking up font settings?
[20:41] <Pinkerton> Specifically Evolution and Visual Studio code are ignoring some of my font selections I made in Control Center
[20:41] <Pinkerton> not throughout the application(s), just in a few spots
[20:43] <Pinkerton> In Evolution, for example, my selection is used literally everywhere except for the "From:, To:, Subject:, Date:" header for a selected email
[20:44] <Pinkerton> VS Code picks it up for the menus (presumably because Electron just uses GTK3) but the rest of the UI is still using the default Ubuntu font


[00:08] <cristian_c> roberalz, yeah, I tried to unmount the partitions too
[00:08] <cristian_c> liemon, it turned out it was a silly problem. I did not edited the partition properties, selecting mount point
[00:09] <cristian_c> (in this case: /)
[00:09] <liemon> :o
[00:09] <liemon> so the mounting point was missing?
[00:09] <liemon> of the root partition
[00:09] <cristian_c> this way, Next button is enabled and a dialog warns me I should create an efi partition mounted as /boot/efi and with 'boot' flag enabled
[00:10] <liemon> yes, the thing i was mentioning, then the mount point should be /boot/efi and marking the button that says 'boot'(the boot flag)
[00:11] <cristian_c> liemon, I did not that in manual partitioning screen (it would have been easy to find out since it has always been so since birth of ubuntu)
[00:12] <cristian_c> not selecting mount point I made a dumb mistake, shame on me
[00:12] <liemon> no worries, i have been in that place too ^^
 I can't see who is still around on IRC, going through some of the questions now :)
 (For reference, it's great to idle in here when you have a question. Also, another friendly poke towards Matrix ;) )
 cristian_c: I'm glad you figured yours out :)
 liemon: You made it to 23.10 or you still need assistance? :)
 Anyone know why DVDs will not play on the latest version of lubuntu/ubuntu? It plays audio CDs but none of the DVDs I have that I know work will play
[05:36] <arraybolt3> AngryAutos: These are movie DVDs for major movies, right?
[05:37] <arraybolt3> If so, you're missing libdvdcss, which is omitted from Ubuntu due to legal reasons (what it does can be seen as bypassing DRM measures, which is illegal in some areas even if you're doing it to watch content you have a right to since you purchased it/licensed it/whatever the right term is here'd it). It can be installed, but it takes some effort.
[05:38] <arraybolt3> basically run `sudo apt install libdvd-pkg`, wait for the install to fail (it does so by design), follow the on-screen instructions to finish the installation, and once everything's done try again.
[07:38] <cristian_c> tsimonq2, I've installed 23.10 but since I can't boot that, I've to find a way to install bootloader (and it's not so simple as it appears)
 Yes and I installed that and it still says no disc (re @lubuntu_bot: (irc) <arraybolt3> AngryAutos: These are movie DVDs for major movies, right?)
 When I installed libdvd-pkg it gave me a bunch of microsoft prompts I had to hit ok in terminal which was very different never had to do that in terminal


[04:54] <blag> im trying to get a patch ready for both upstream inclusion and the ubuntu kernel devs for ubuntu-maverick, but checkpatch.pl keep complaining that my patch is unsigned.  how do i sign my patch (creating with git diff)?
[04:54] <blag> *created
[07:15] <blag> i have a patch for the current ubuntu maverick kernel.  should i upstream it directly to the linux kernel devs, or should i upstream it to the ubuntu kernel devs, or both?
[07:19] <blag> nevermind, i just took a look at the linux kernel upstream, and theyve already fixed it.  :-)
[13:00] <penguin42> it might be worth keeping an eye out for other cases of bug 721996
[13:00] <ubot2> Launchpad bug 721996 in linux "CMOS crc error on next boot" [Undecided,New] https://launchpad.net/bugs/721996
[13:01] <penguin42> seems to have started for him in 2.6.38-1
[14:28] <EntropyReduction> Hello.  I think I may have a kernel bug on Maverick kernels post-2.6.35-22.  Reported it at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/719446.  Dave Gilbert as sent out the default request for a test on latest development release of Ubuntu, and the latest upstream kernel.  But he also suggests that at least doing the former has a change of trashing my existing installation, which...
[14:28] <ubot2> Launchpad bug 719446 in linux "systematic freezes on any kernel version post 2.6.35-22 " [Undecided,New]
[14:28] <EntropyReduction> ...I'm not very excited about doing.
[14:30] <EntropyReduction> How dangerous is it to try a development release of Ubuntu?  How about trying latest upstream kernel?  I know these may be "how long is piece of string" questions, but forgive a ubuntu newbie...
[14:30] <penguin42> EntropyReduction: Well, it's difficult to say, but make sure you 1) have a backup 2) Know how to undo it
[14:31] <penguin42> EntropyReduction: You could hit some corruption bug that nuked the whole install - but it's unlikely
[14:32] <EntropyReduction> That's the problem: I don't yet have a way of backing up my partitions yet; on my "to learn how to do" list but not there yet
[14:32] <penguin42> EntropyReduction: Trying a development kernel it should be easy to switch back to using the normal kernel (it'll just be in the grub menu); trying a development release is not really recoverable if it breaks
[14:32] <penguin42> EntropyReduction: OK, stop what  you're doing - NOW - and get yourself a way of doing backups of your most important data
[14:32] <penguin42> EntropyReduction: Backups are good!
[14:33] <EntropyReduction> I got spara empty space n my laptop hard disk; I could install dev release into a new partition, assuming installer would be smart enough to just update existing grub stuff.  That feasible -- and safe?
[14:34] <penguin42> no, installers go wrong and can nuke other partitions - rare but it happens
[14:34] <penguin42> (but still safer than just upgrading)
[14:36] <EntropyReduction> Oh I got data backup, that's not a problem; in fact this laptop is secondary to my main machines (all windoz), so don't even carry up to date copies of my data.  What I'd rather not have to do is wade through all the ubuntu stuff again.  It's fun to install VirtualBox for the first time, I didn;t mind rebuilding my VMs for the third time, but a fifth time would get boring.  Not to mention...
[14:36] <EntropyReduction> ...nautilus scripts, etc etc etc
[14:37] <penguin42> EntropyReduction: OK, so installing a deve kernel is _unlikely_ to destroy anything and is easy to switch back from
[14:37] <penguin42> EntropyReduction: Upgrading to a development release can be a bit of a killer if it doesn't like your machine or it's currently broken, although installing in a seaprate partition is _normally_ ok
[14:41] <EntropyReduction> ok, I think I'll go for dev kernel.
[14:41] <EntropyReduction> I was directed here to find the right one:
[14:41] <EntropyReduction> https://wiki.ubuntu.com/KernelMainlineBuilds
[14:42] <EntropyReduction> which rather confused me.  But looks like maybe what I want is
[14:42] <EntropyReduction> http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
[14:42] <EntropyReduction> ?
[14:45] <penguin42> EntropyReduction: Are you Alan Campbell of bug 719446?
[14:45] <ubot2> Launchpad bug 719446 in linux "systematic freezes on any kernel version post 2.6.35-22 " [Undecided,New] https://launchpad.net/bugs/719446
[14:47] <EntropyReduction> yup
[14:47] <penguin42> EntropyReduction: Dave Gilbert - hi
[14:47] <penguin42> EntropyReduction: So yeh, use the package from that ppa - that should let you try the latest kernel on maverick
[14:48] <penguin42> EntropyReduction: And it'll just add another entropy into grub, so make sure you know how to get into grub to choose your kernel and you can easily flip back to the normal kernel
[14:48] <EntropyReduction> Oh, hi: so penguin42 == Dave Gilbert?
[14:48]  * penguin42 nods
[14:49] <EntropyReduction> Yeah, got that, and have grub configured to default to 2.6.35-22 (although I notice when a new kernel version comes in I gotta remember to reconfigure it) -- but yeah, I'm on top (??) of that
[14:49] <penguin42> if you add a new kernel version it should land in the grub menu
[14:50] <EntropyReduction> OKay, many thanks for hand-holding.  Back to you next week after I've had a go, and will also try to capture console output and forward that as well.
[14:50] <penguin42> good luck
[14:52] <EntropyReduction> Re grub: yeah, new kernel goes in at top of menu, but somehow the pointer that remembers which grub alternative is the default gets thrown off by one, and I have to remember to reset it (I haven;t got down to level of editing grub config file, I use Startup Manager.
[14:53] <EntropyReduction> anyway, many thanks


[06:52] <snappy> Is there a way for upstart to manage spawning N processes of a program, associating them with the same process group?
[13:44] <lnykryn> hi! Is it possible to run initscript with initctl command? My point is that I want pid 1 to actually run the initscript, not user.


[11:43] <beuno> internet isn't very stable at the conference  :(
[11:51] <beuno> Rinchen: anyway, if you have it, can you email it to me?


[08:16] <smb> jdesfossez, Possibly those messages are not of high enough level. You could try dmesg -n <level> (level -> eg. warn|notice|info).
[16:20] <bjf> apw, the rebuild DEP-8 test. that's going to get run all the time now for all kernel packages. is that really what we want?
[16:21] <bjf> apw, i know why that test exists, i'm just wondering why it's in the kernel. if it's to ensure that new toolchain packages properly build the kernel why isn't there a test in the toolchain packages for it rather than the kernel?
[16:24] <apw> bjf, it is in there because it is the kernel test one wants to run when any of the packages we depend on, changes
[16:24] <apw> bjf, unfortuanatly there is no way to know you are testing for "me" rather than a "dependancy"
[16:25] <apw> bjf, which is what we would really want ...
[16:25] <bjf> apw, yeah
[16:25] <apw> bjf, i think there was a proposed way to tell, which would let one work it out
[16:26] <bjf> apw, so it's adding multiple hrs. to the testing and when we start running these on multiple archs is going to get worse
[16:28] <bjf> apw, i guess if it is a problem maybe someone will fix it so it only runs when we want rather than all the time
[16:28] <apw> bjf, yeah i cannot deny it is stupid, just asking pitti ritht now if there is a way
[16:31] <apw> bjf, is this in britney testing or in "bjf" testing btw
[16:32] <bjf> apw, new britney testing that CI is adding
[16:32] <apw> bjf, ok so official, not runnig somewhere where we get to help out
[16:32] <apw> to say UNIT_TESTING_FOR_KERNEL and let that short circuit it
[16:32] <bjf> apw, correct.
[16:34] <apw> bjf, i am getting the "it doesn't know, and it is all very hard" but i do struggle to say why it doesn't know myself
[16:44] <infinity> apw: DEP-8 doesn't know why a test was triggered, just that you decided to run some tests.  The fix belongs one layer above that, I suspect.
[16:44] <infinity> apw: ie: we should only run the test under certain circumstances, but the test itself can't know that, it's the framework calling it (adt-britney, whatever) that needs to be smarter.
[16:45] <apw> infinity, well likley, though it is odd it isn't parameterised with why it is being run
[16:45] <infinity> apw: That implies more intelligence than DEP-8 is meant to have.  It should be entirely framework agnostic.
[16:45] <infinity> apw: You can run tests by hand, you can write infra that runs all your tests in a loop, you can trigger them for $reasons, none of that matters to the tests.
[16:46] <apw> yeah, and i'd be cool with the reason it ran being "run by hand" or "none"
[17:01] <cyphermox> jsalisbury: hey, just curious if you had found anything about bug 1359689
[17:03] <jsalisbury> cyphermox, yes, I backported commits abd69c55d and 144ecb97c.  I should post a link in the bug with a test kernel shortly.
[17:03] <cyphermox> ok
[17:03] <cyphermox> thanks :)
[17:05] <jsalisbury> cyphermox, my test kernel build failed, so I just need to fix up my backports a bit.