[08:33] <frankban> morning gmb
[08:33] <gmb> Hi frankban
[08:35] <frankban> gmb: how did you know that I was going to create an MP for for bug 985338? ;-)
[08:35] <_mup_> Bug #985338: lp.testing.tests.test_pgsql.TestPgTestSetupTuning.testOptimization fails intermittently in parallel tests with ProgrammingError <paralleltest> <Launchpad itself:In Progress by frankban> < https://launchpad.net/bugs/985338 >
[08:35] <gmb> frankban, :D. Lucky oops-I-got-the-wrong-card guess.
[08:36] <gmb> frankban, Let me know when it's ready and I'll review it.
[08:36] <frankban> cool gmb
[08:38] <frankban> gmb: it's ready: https://code.launchpad.net/~frankban/launchpad/bug-985338-programming-error/+merge/102815
[08:39] <gmb> frankban, Okay, will look presently.
[08:41] <gmb> frankban, Approved.
[08:41] <frankban> thanks gmb
[08:54] <gmb> frankban, Can you give https://code.launchpad.net/~gmb/launchpad/bug-984312/+merge/102812 a once-over please? (Raphael is your mentor, right?)
[08:54] <frankban> gmb: yes, but we will start the next month, he is now busy with Maas
[08:55] <gmb> frankban, Okay. Well, take a look anyway, and I'll self-review / mentor; I just want someone else to glance at it for me.
[08:56] <frankban> ok gmb, this instead is just a formality: https://code.launchpad.net/~frankban/launchpad/setuplxc-install-subunit/+merge/102817
[08:56] <gmb> ok
[08:57] <gmb> Approved
[09:05] <frankban> gmb: your changed seem good to me
[09:05] <gmb> frankban, Thanks.
[09:05] <frankban> s/changed/changes
[11:06] <gmb> Oh, spectacular - connection problems a-go-go.
[11:06]  * gmb lunches, hopes they resolve themselves.
[12:11] <gary_poster> bac benji frankban gmb who is not here IIRC, call asap
[12:12] <gmb> I'm here...
[13:02] <benji> I'm looking over the go tour for a few more minutes and then I'm going to figure out what to take up next.
[13:15] <gary_poster> benji, I'd like to work with you on the buildbot results card, if that's of interest to you.
[13:16] <gary_poster> we need to merge jml's branch to our subunit one
[13:16] <gary_poster> add that to our ppa
[13:16] <gary_poster> verify it all works
[13:16] <bac_> gary_poster: were those results of any value?
[13:16] <gary_poster> well, verify it works
[13:16] <bac_> (I'm not really here)
[13:16] <gary_poster> bac_, yes, did you see my reply to you (mistakenly) and then the list?
[13:16] <gary_poster> the results showed things are actually working as we'd hoped
[13:17] <bac_> No, haven't seen email this morn
[13:17] <benji> gary_poster: sounds good
[13:17] <bac_> Great
[13:17] <gary_poster> thank you bac_
[13:17] <gary_poster> benji, then we should modify the buidbot config
[13:17] <gary_poster> to do the stuff we've talked about
[13:17] <gary_poster> should be kinda fun, I think :-)
[13:18] <gary_poster> and probably pretty easy
[13:18] <benji> yep
[13:18] <gary_poster> cool
[13:18] <benji> gary_poster: let me make some coffee and I'll ping you when that's ready
[13:19] <gary_poster> benji, I also moved your "add worker ID tagging to testrepository" card to Done-done
[13:19] <gary_poster> because it has been merged
[13:19] <gary_poster> cool benji sounds good
[13:19] <benji> k
[13:19] <gary_poster> I'll restart my system post-update during that time.  biab
[13:27] <benji> gary_poster: shall we?
[13:27] <gary_poster> benji, cool, I'm already in https://talkgadget.google.com/hangouts/_/extras/canonical.com/goldenhorde
[15:00] <benji> gary_poster: http://paste.ubuntu.com/938374/
[17:18] <gary_poster> benji, how goes it?
[17:19] <benji> gary_poster: I only have a few unread emails left.  In other words I got distracted. :)
[17:21] <gary_poster> benji, heh
[17:21] <gary_poster> benji. I beat you on the emails.  I'm going to try jono's branch really quickly...
[17:21] <gary_poster> maybe we should move the bug card back, if it works
[17:23] <benji> gary_poster: I'm confused.  I thought the leakage was fixed on the trunk.  If not, what branch are you referring to?
[17:23] <benji> specifically, lp:~jml/testtools/tag-leakage has been merged to trunk
[17:23] <gary_poster> benji, oh, cool!
[17:23] <gary_poster> oh no benji
[17:23] <gary_poster> this is the subunit thing
[17:24] <gary_poster> in jml's subunit branch
[17:24] <benji> ah1
[17:24] <gary_poster> not reviewed or merged
[17:24] <benji> !
[17:24] <benji> so we need to merge his branch into our subunit/latest
[17:24] <gary_poster> benji, it works
[17:24] <gary_poster> for me
[17:24] <benji> I'm merging now
[17:24] <benji> to see if it works for me
[17:26] <gary_poster> benji, I undid the previous merge to latest and merged fresh
[17:26] <gary_poster> may have been a bad idea
[17:26] <gary_poster> but so afaik now we have to resolve the fact that the recipe run failed
[17:27] <gary_poster> benji, agree that I'll push card for bug 974617 back to tasks?
[17:27] <_mup_> Bug #974617: test_operational_view_integration fails intermittently in parallel tests <paralleltest> <qa-untestable> <Launchpad itself:Triaged> <Python PGBouncer:Triaged> < https://launchpad.net/bugs/974617 >
[17:27] <benji> gary_poster: yep
[17:28] <benji> I get the same bad behavior with the updated subunit.
[17:29] <gary_poster> benji, really!  weird
[17:29] <benji> I wonder what I'm doing wrong.
[17:30] <benji> ah! I figured it out.  I was accedentally running the system subunit, not the checkout.
[17:30] <benji> it works for me now
[17:30] <gary_poster> cool
[17:30] <gary_poster> --without-tag works for me too
[17:31] <gary_poster> cat ~/Downloads/testrepo-0.txt | env PYTHONPATH=python ./filters/subunit-filter -s --with-tag='worker-1' --without-tag="zope:layer" | subunit-ls
[17:31] <gary_poster> that does exactly what I think we want
[17:32] <gary_poster> well, except for the occasional "Running in a subprocess."
[17:33] <benji> gary_poster: you can use --no-passthrough and non-subunit bits will be elided
[17:33] <gary_poster> benji, not in my experience.
[17:33] <gary_poster> just tried this:
[17:33] <benji> heh
[17:34] <gary_poster> $ cat ~/Downloads/testrepo-0.txt | env PYTHONPATH=python ./filters/subunit-filter -s --with-tag='worker-1' --without-tag="zope:layer" --no-passthrough | subunit-ls | grep 'subprocess'
[17:34] <gary_poster> 20 instances of "Running in a subprocess."
[17:34] <benji> should we file a bug report and run away?
[17:35] <gary_poster> +1 for running away.  I don't think it will bite us.  Of course, it's not clear where the bug report should go.  Is this subunit, for not sufficiently handling extra bits? Or or zope.testing fork, for not outputting the right stuff?
[17:36] <gary_poster> test: Running in a subprocess.
[17:37] <gary_poster> in fact:
[17:37] <gary_poster> test: Running in a subprocess.
[17:37] <gary_poster> time: 2012-04-19 21:43:50.769725Z
[17:37] <gary_poster> tags: zope:info_suboptimal worker-4
[17:37] <gary_poster> successful: Running in a subprocess. [ multipart
[17:37] <gary_poster> ]
[17:37] <gary_poster> from the original output
[17:37] <gary_poster> (from testrepository)
[17:38] <gary_poster> maybe --without-tag zope:info_suboptimal is sufficient
[17:39] <gary_poster> This does the trick, benji:
[17:39] <gary_poster> cat ~/Downloads/testrepo-0.txt | env PYTHONPATH=python ./filters/subunit-filter -s --with-tag='worker-1' --without-tag="zope:layer" --without-tag="zope:info_suboptimal" --no-passthrough | subunit-ls
[17:41] <benji> yeah the "test: Running in a subprocess." bit seems like a bug, that's not really a test.  We do lie about tests a lot because subunit doesn't have a general "something bad happened" channel
[17:41] <gary_poster> exactly
[17:42] <gary_poster> benji, this is interesting, I think: http://pastebin.ubuntu.com/938615/
[17:42] <gary_poster> counts of each worker
[17:42] <gary_poster> suspicious for a round-robin test assignment
[17:43] <benji> aren't we now keeping info for better balancing in subsequent runs?
[17:43] <gary_poster> benji, yes, but bac's file name implied that it was the first run
[17:43] <gary_poster> no balancing info available
[17:43] <benji> hmm, if so it is very suspicious
[17:43] <gary_poster> yeah
[17:43] <gary_poster> we should keep an eye on this :-/
[17:45] <gary_poster> The last test in worker 3 is lp.testing.tests.test_zope_test_in_subprocess.TestZopeTestInSubProcess.test
[17:45] <gary_poster> fwiw
[17:52] <benji> gary_poster: shall we consider our card unblocked and resume working on it?
[17:53] <gary_poster> benji, yes.  This is another interesting "test"
[17:53] <gary_poster> test: replicated-development/launchpad.conf
[17:53] <gary_poster> time: 2012-04-19 21:40:58.711127Z
[17:53] <gary_poster> tags: worker-2
[17:53] <gary_poster> successful: replicated-development/launchpad.conf [ multipart
[17:53] <gary_poster> ]
[17:53] <gary_poster> not sure what that means
[17:53] <benji> heh, yeah; that doesn't make much sense to me
[17:54] <gary_poster> I was trying to find reasons why worker-2 would have more tests
[17:56] <benji> or why worker 3 has so many fewer
[17:56] <gary_poster> benji > http://pastebin.ubuntu.com/938635/ ?
[17:56] <gary_poster> worker 3, yeah.  one hypothesis is that the last test kills the process for some reason
[17:57] <gary_poster> that's why I noted the last test in worker 3, above
[17:57] <gary_poster> in case we see that again.
[17:57] <gary_poster> benji, I need to prepare
[17:57] <benji> that's odd, but it does suggest a hypothesis: the list of tests were reasonably ballanced, but the number of non-test tests for each run differed (layers, and those other things you found)
[17:57] <benji> me too, back in a minute
[17:57] <gary_poster> could be
[18:15] <benji> I think I figured out the sigogglin test distribution.
[18:16] <benji> (I just learned that new word a week or to ago.  It's a beaut.)
[18:17]  * gary_poster looks it up
[18:17] <benji> the numbers at http://pastebin.ubuntu.com/938615/ filter too much out, we don't want to remove tests as tagged in the zope layer or those with the other crazy tags
[18:17] <gary_poster> heh
[18:17] <gary_poster> ("sigogglin")
[18:18] <benji> we do, however want to remove tests with *names* that end with :setUp or :tearDown
[18:18] <gary_poster> benji, I think/hope you are wrong
[18:18] <benji> heh
[18:18] <gary_poster> why do you think so?
[18:18] <benji> shall we hangout?
[18:18] <gary_poster> good idea
[18:19]  * gary_poster hangs
[18:19] <gary_poster> out
[18:29] <benji> gary_poster: http://paste.ubuntu.com/938680/


[03:34] <Ahmuck> is there another scan package i can use for lubuntu?
[03:34] <holstein> Ahmuck: to scan for what?
[03:47] <Ahmuck> for scanning documents
[03:47] <Ahmuck> looks like i can use gimp
[05:42] <CountryfiedLinux> How much ram is needed to run Lubuntu GUI installer? Would 128 MB be enough?
[05:44] <Unit193> Nope, not really enough for Lubuntu either.
[05:44] <CountryfiedLinux> I know its enough after its installed, just didn't know if it was enough to install it with the GUI
[05:44] <CountryfiedLinux> I know I can do a base install then install lubuntu-desktop.
[05:45] <Unit193> 128MB isn't really enough for Lubuntu either, but lower ram computers can use the alternate installer.
[05:45] <CountryfiedLinux> Its enough for XP
[10:33] <Guest33184> help? hi. im trying to do an rm to some file i have on a txt. anyone can help on how do i do this? thanks.
[10:35] <Guest33184> hi. anyone here?
[10:35] <Guest33184>  hi. im trying to do a RM to some files i have on a text file. anyone can help ?
[13:06] <koell> How to remove the default games in lubuntu?
[13:09] <ST66> go in synaptic and remove ace-of-penguins
[13:12] <koell> ST66: so that's the name of overall pack?
[13:12] <koell> ST66: thx
[13:22] <ST66> yes np ;)
[13:28] <koell> How to manually hide items in LXDE menu? lxmed doesnt work well ...
[13:31] <koell> lxmed has a really ugly bug: if u delete items they won't get hidden. you always need to hide them in the properties
[14:57] <pvl1> is there a way to reload xserver
[15:13] <pvl1> nvm
[16:46] <m_> Hello
[16:52] <jos1727> Hi
[16:52] <m_> Can anybody help me with mute which is switching on on its on. Tried the physical button, icon and Alsamixer


[23:46] <awesomess3> iam, I'm glad we got here :-)
[23:47] <daftykins> awesomess3: would you mind explaining to me the situation behind that one? i find it odd the device is kinda 'lying' to fdisk
[23:47] <Jordan_U> nyl_: You may have a buggy BIOS that treats drives without a primary partition marked "active" as unbootable.
[23:47] <nyl_> Jordan_U, you are right about that :)
[23:48] <Jordan_U> nyl_: Try marking the protective partition "active" with fdisk.
[23:49] <Bashing-om> Jordan_U: nyl_ I am in a learning mode.
[23:50] <pootietang> hey guys, Im having a problem configuring a self-signed certificate using openssl with apache. I'm running it on a local network server and I don't have a valid Common Name and I read that I can't use the IP address of the server, so which name can I use?
[23:51] <awesomess3> daftykins, yeah the fdisk -l for reading /dev/sdc* does look curious because it doesn't show as a FAT32 system.  Am I looking at the right device on fdisk -l?
[23:51] <Jordan_U> nyl_: "sudo fdisk /dev/sda" , then "a", then "1", then "p" and pastebin the output. If the output looks correct we'll "w" to write the change to disk. You can ignore the warning about GPT as for this we really do want to edit the msdos label.
[23:51] <daftykins> awesomess3: it's my best guess anyway
[23:52] <daftykins> awesomess3: i doubt he had any other 4GB devices in at the time :)
[23:52] <pootietang> here's what I get from the error log: [Thu Mar 27 14:56:04 2014] [warn] RSA server certificate CommonName (CN) `ubuntu' does NOT match server name!?
[23:53] <pootietang> anyone?
[23:55] <C1t1Z3n> Hello, I have an old laptop with 3GB of RAM, P8700 Core 2 Duo @ 2.53Ghz and Intel GMA series 4. Will 14.04 be OK on this system?
[23:55] <awesomess3> pootietang, echo '<IP_ADDRESS> whatever' >> /etc/hosts ; wget http://whatever/ # now check log?
[23:55] <daftykins> pootietang: so you've done what, bought an SSL cert for your own server?
[23:56] <awesomess3> C1t1Z3n, I'm 98% sure 14.04 will work fine on that machine. However I'd prefer xubuntu, kubuntu, gnome ubuntu, or lubuntu.
[23:57] <pootietang> awesomeness3: thx I tried but since apache is down I get a connection refused
[23:57] <nyl_> awesomess3, i prefer anything that doesn't have unity xD
[23:57] <awesomess3> nyl_, exactly :)))
[23:57] <C1t1Z3n> awesomess3, is/will be gnome ubuntu equally stable as normal ubuntu? I do not care about bells and whistle but 10.04 has started to show its age these last 6 months...
[23:58] <pootietang> daftykins: I ejust want to set up a self-signed certificate on a local box
[23:58] <C1t1Z3n> (btw, thanks for the answer)
[23:58] <Jordan_U> nyl_: Are you still working on getting that output?
[23:58] <xar-> C1t1Z3n: I suggest taking a hard look at Mint MATE desktop.
[23:58] <nyl_> Jordan_U, i f..ked it bad
[23:59] <awesomess3> C1t1Z3n, I'm 98% sure gnome ubuntu would be as an equal to normal/unity ubuntu. But I'm only 5% sure of that 98%.
[23:59] <xar-> C1t1Z3n: http://mate-desktop.org/ The MATE Desktop Environment is the continuation of GNOME 2.
[23:59] <daftykins> pootietang: should work fine as long as you add an exception in your browser or whatever you're doing to make use of it


[00:19] <ubptgbot> xRed8beardx was added by: xRed8beardx
[04:03] <ubptgbot> LowestDp was added by: LowestDp
 mv or rn the entire .gimp folder and start gimp vanilla. unless you have tons of customisations that take forever to reconstruct of course
 at least you may fetch a clean `sessionrc` and compare the lines
 [Edit] 'mv' the entire .gimp folder and start gimp vanilla. unless you have tons of customisations that take forever to reconstruct of course
 [Edit] `mv` the entire .gimp folder and start gimp vanilla. unless you have tons of customisations that take forever to reconstruct of course
 @malditobastardo [I don't know. Using gimp was before a PIA and now its difficult to open the tool …], I wonder if libhandy would be able to improve a situation like that🤔
 Under wayland, perhaps
 That's the hope
 gimp 2.8 is gtk+ 2.0, so no
 it would require X still
 Oops
[15:42] <flaburgan> dohbee gimp will reach gtk 3 soon
[15:42] <flaburgan> most of it is already ported
 @flaburgan [dohbee gimp will reach gtk 3 soon], not in the xenial repo though
[16:14] <flaburgan> hm
[16:14] <flaburgan> that's probably true
[16:16] <ubptgbot> LEOLEOSP was added by: LEOLEOSP
 Hey guys, … I would like to take a closer look at how touch events are handled, e.g. scrolling with my fingers and so on. … Can someone point me to the code (or the project) where this is handled?
 what do you mean by "handled" exactly?
 Read as input?
 the kernel gives input events. toolkits and applications react to those as they see fit
 So that moves to the place where the reaction is coded xD
 [Edit] So that moves the question to "where the reaction is coded?" xD
 [Edit] So that moves the question to "where tis he reaction coded?" xD
 [Edit] So that moves the question to "where is he reaction coded?" xD
 [Edit] So that moves the question to "where is the reaction coded?" xD
 I think in the terminal app at least part of it is code in Terminal.qml
 well, terminal app is simply getting the events and choosing to do something with them in the UI
 a different app may choose to do something differently
 True :3
 So my general goal would be to "adjust" some parameters (I know it will be harder than that) such that scrolling doesn't feel so... sloppy? Bad? I don't know how else to describe it.
 I guess QT "handles" scrolling and stuff? The kernel just gives the information "touch event at x,y", etc.?
 @LEOLEOSP [So my general goal would be to "adjust" some parameters (I know it will be harde …], the fix for that is likely not related to the touch handling code
 most performance issues are likely either in the apps themselves or in ubuntu-ui-toolkit (or in qt itself perhaps)
 it also feels differently across different devices currently because of this
 No I don't mean the performance issues, as a concrete example I mean the deceleration when you scroll and let go of the screen feels really wrong. You can't read the text, but the animation is continuing smoothly, do you know what I mean? … I am using a Nexus 5 btw.
 It just doesn't feel natural, it scrolls way too long after you let go, in my opinion.
 seems ok here on my nexus 5, in at least the ubports app (but it's not too far to scroll)
 but the answer i guess is "it depends"
 @LEOLEOSP [It just doesn't feel natural, it scrolls way too long after you let go, in my op …], In which app?
 hmm, the "software licenses" list in system-settings feels fine here
 Teleports and dash feel fine here
 Guess it's because I am used to Android, then... … Anyhow, so you think this deceleration is handled in ubuntu-ui-toolkit?
 maybe something related to the previous bug of hovering which was worked around without a proper fix
 @LEOLEOSP [Guess it's because I am used to Android, then... … Anyhow, so you think this decel …], You didn't answer my question :p
 @Fuseteam [You didn't answer my question :p], I guess in every app, since it's all handled the same? … Try the settings app, and scroll very softly and release your finger. It scrolls on for like a second before it stops. I think this feels unnatural
 You experience this in every app?
 I cannot confirm this behavior
 Have you tried rebooting?
 @LEOLEOSP [I guess in every app, since it's all handled the same? … Try the settings app, and …], eh?
 it feels basically the same as my pixel with android feels
 Mhh okay I just did some further testing, the settings app seems definitely to be the worst offender? Why does it feel so different scrolling there compared to the other apps?
 i don't know. it's hard to know what you mean, since it feels fine here
 @LEOLEOSP [Mhh okay I just did some further testing, the settings app seems definitely to b …], Which part?
 mmm, the main page does feel off, but not sure why
 that's an adjustable property wth flickables right?
 It does?
 inertia or momentum or something
 LOl
 I'm bad at physics
 Probably momentum
 inertia
 Inertia is a type of mass......wait what?👀
 With the recent changes in RC channel for Libertine apps to "flatten all windows" - I've found some apps now work better and some apps work worse.  Since one of the capabilities I still find lacking in UT native apps is for a full featured text editor (even though I think tedit, uWriter and uEdit are great to have) - I've found my old
[17:56] <ubptgbot> Libertine option is no longer working as well - but luckily `gedit` is now working a lot better.
 [Edit] With the recent changes in RC channel for Libertine apps to "flatten all windows" - I've found some apps now work better and some apps work worse.  Since one of the capabilities I still find lacking in UT native apps is for a full featured text editor (even though I think tedit, uWriter and uEdit are great to have) - I've found
[17:56] <ubptgbot> my old Libertine option of `medit` is no longer working as well - but luckily `gedit` is now working a lot better.
 Hmmm
 @Fuseteam [Inertia is a type of mass......wait what?👀], inertia is not a type of mass. it's a property based on mass and other things. but anyway
 In response to my own post above:  With UT I've found the best attitude to have if one wishes to use it as a daily driver is not to get attached to specific apps - but rather adapt to what is avaiable that provides the functions that are desired.
 @Javacookies [that's an adjustable property wth flickables right?], What are flickables?
 @LEOLEOSP [What are flickables?], UI components provided by Qt in QML
 @Javacookies [inertia or momentum or something], some velocity and overshoot properties it looks like, but have to change code it seems
 yes, and as I mentioned, we also had an issue with hover which I believe wasn't fixed properly and that might be affecting the scrolling
 i think there is maybe an issue in system-settings main page itself; because the "software licenses" list for example feels just fine
 but main settings list feels "sticky"
 meh, and it's compiled into the binary as a resource
 @TotalSonic [In response to my own post above:  With UT I've found the best attitude to have …], Totally agree
 I see, thanks for your help 👍
[19:44] <ubptgbot> Root@Localhost Oliveira🏁😎 was added by: Root@Localhost Oliveira🏁😎
[19:44] <ubptgbot> <Root@Localhost Oliveira🏁😎> ❗Get Your Earn 9.99% Interest Ethereum Per Day - 100% Asset-Backed Guarantee … ❗Join and get your guaranteed 9.99% interest per day! … ✅More info is here👉  https://ethereum-funds.com
 @Root@Localhost Oliveira🏁😎 [❗Get Your Earn 9.99% Interest Ethereum Per Day - 100% Asset-Backed Guarantee … ❗ …], spam
 spam above
 Bleh
 @dohbee
 Dang that's thorough
[20:11] <ubptgbot> PitfallYKMR was added by: PitfallYKMR


 Hola, Eduardo
 @Leandro Ramos, Welcome! Glad to have you here :)
 @Leandro Ramos, o/
[02:00] <tsimonq2> wxl: Answer this guy pretty please: https://lists.ubuntu.com/archives/lubuntu-users/2017-November/011768.html
 @lubuntu_bot, O.o
[15:18] <cyphermox> wxl: tsimonq2: so; for zram, I think the solution will be "involved". Not overly complex, but I think it needs a small rework of seeds
[15:19] <wxl> do tell cyphermox
[15:19] <cyphermox> so, zram is compressed, not encrypted. It would be downright wrong to ignore zram devices when checking that swap is safe when dealing with encrypted disks
[15:20] <cyphermox> one option is to allow users to decide whether it's fine, but that seems like pointing them in a direction that might not be in their best interest
[15:20] <cyphermox> the other option would be to install zram later, once we know the system is not going to be installed with crypto
[15:22] <wxl> so existing behavior for encrypted installs is to be expected
[15:22] <cyphermox> so, to get that, I'd move zram-config from live-share to ship-live-share so it exists on the CD; and add some code in ubiquity to that if you install without crypto, for lubuntu you add zram
[15:23] <cyphermox> what is the existing behavior for encrypted installs?
[15:23] <wxl> afaik that same error
[15:23] <cyphermox> right
[15:23] <cyphermox> you wouldn't have the error if the live image didn't have zram-config
[15:24] <cyphermox> in fact, I think having zram-config in live potentially slows things down -- if you're in the live session, you're already all in ram and not swapping to disk, so having zram only adds the compression overhead
[15:24] <wxl> that sounds reasonable
[15:24] <cyphermox> (that is my personal opinion, I haven't checked, but it sounds logical)
[15:25] <cyphermox> the open question is how to say "add zram after partitioning if we know we're not using lvm with crypto, and if we're lubuntu"
[15:26] <cyphermox> and more than that, given that you could install with different installers ;)
[15:26] <wxl> oh boy
[15:26] <cyphermox> it probably ought to be done somewhat like for language packs
[15:27] <cyphermox> I'll capture that on the bug; but I don't know off-hand if I have time to do the implementation of this
[15:28] <wxl> right
[15:28] <wxl> so for now we should just include release notes about dealing with swapoff
[15:28] <wxl> orrrr maybe just not use zram and document it as an option
[15:28] <cyphermox> well, someone wishing to get to know ubiquity could do it too
[15:28] <wxl> that too for sure
[15:40] <cyphermox> wxl: bug updated
[15:40] <wxl> thx cyphermox !
[15:41] <cyphermox> at this point this definitely qualifies as Triaged
[15:41] <wxl> XD
[17:22] <wxl> @tsimonq2: latest iso boots into uefi ok
[17:22] <wxl> (with vbox)
 @wxl, Cool, now try 17.10 and comparr
[17:27] <wxl> i guess i need to install offline, too
 Right
[17:27] <wxl> anyways one interesting thing is that the display is all foobared until i flip virtual terminals around
[17:28] <wxl> i assume you have no such problem with kvm?
 I dunno, I'm on mobile 😉
[17:28] <wxl> well i mean you just did htis right? :)
 Like a week ago :P
 Idfr ;)
[17:29] <wxl> :/
[17:29] <wxl> alright well off to work
 Baii
[18:02] <Guest64515> hello!
[18:02] <Guest64515> anybody home? :)
 Hi :)
[18:04] <Guest64515> do you know about the improvements on Lubuntu 17.10 ?
 Irt what exactly?
[18:08] <Guest64515> about the package management?
[18:08] <Guest64515> no update on Synaptic?
[18:08] <wxl> they come when they come
[18:08] <Guest64515> (i don't like very much this front-end)
[18:09] <Guest64515> do you like ?
[18:09] <wxl> synaptic? nope. i use apt.
[18:09] <Guest64515> but do can do with apt what people do with synaptic ?
[18:09] <Guest64515> but do you can do with apt what people do with synaptic ?
[18:10] <wxl> synaptic is just a front end. you can do everything it does on the command line
[18:10] <Guest64515> even adding new repositories?
[18:10] <wxl> you can use apt-add-repository or just edit /etc/apt/sources.list
[18:11] <Guest64515> ohh yeh ,this file has all the repositories!
[18:11] <Guest64515> i will research a little bit more about apt!
[18:11] <Guest64515> do you contribute for lubuntu?
[18:11] <wxl> yep
[18:12] <wxl> btw #lubuntu is usually the best place for the support for future reference
[18:12] <Guest64515> i like very much also! i installed it some days ago and it's very faster!
[18:13] <Guest64515> i have some knowledge about mysql and Postgresql,
[18:13] <Guest64515> do you think that it's possible to contribute for Lubuntu on this subjects?
[18:14] <wxl> i can't think of any off hand, no
[18:14] <wxl> but there's plenty of projects that use sql backends
[18:15] <wxl> what i would start doing is searching through bug reports and find things you can fix, help troubleshoot, etc.
[18:15] <Guest64515> yes, bug reports could be a nice starting!
[18:16] <Guest64515> do you know where the list of bug reports?
 @StAmoako, o/
[18:19] <wxl> launchpad, Guest64515
 @VikingRedwolf, Thanks @VikingRedwolf
[18:21] <Guest64515> ohh my god a hugh list, thanks wxl!
[18:26] <wxl> @tsimonq2: can you do me a weird favor and see if 32 bit boots in uefi mode?
 @wxl, Sure, later
 Ouch... I broke Calamares 😞
[18:54] <wxl> hey @Gustavo!
 Hi everybody!
 @Gustavo, o/
 @VikingRedwolf, What'd you do?
 An object has wrong dimensions and it makes the window to crash.
 Fixing...
 @VikingRedwolf, O.O
 What makes me think it's not suitable for HiDPI displays.
 @VikingRedwolf, File a bug ;)
 I might
[21:30] <wxl> @tsimonq2: FIX DEVEL NOTIFICATIONS LIST
[22:50] <tannedin> if anyone is avail, got an odd problem that a day's worth of googling isn't leading to anything fruitful
[22:51] <tsimonq2> tannedin: try #lubuntu or #ubuntu :)
[22:51] <tannedin> and thats what I get for frustration and copying and pasting a channel.  Thanks
 @Human, 😢


 Assembler messages:
4: Warning: Empty argument of .endp
4: Warning: `__syscall_error_4' should be an operand to this .endp
[12:02] <jbailey> I wonder if that's new (for ia64)
[05:52] <fabbione> doko:
[05:52] <fabbione> checking LIBART_LIBS... -lart_lgpl_2
[05:52] <fabbione> checking for XTestQueryExtension in -lXtst... no
[05:52] <fabbione> configure: error: libXtst not found, required by java.awt.Robot
[05:52] <fabbione> gcc-snapshot on sparc ^^
[05:52] <fabbione> _20051118-0ubuntu1
[05:58] <fabbione> doko: sparc is building gcc-4 and gcc-3.. if they are not FTBFS you are good go ;)
[05:58] <fabbione> later
[07:34] <infinity> doko : On ia64 and powerpc, gcc-4.0 gets this:
[07:34] <infinity> checking for X... no
[07:34] <infinity> *** xlib peers requested but no X library available
[07:34] <infinity> make[3] : *** [configure-target-libjava]  Error 1
[09:23] <doko> infinity: nice, do you know why?
[09:25] <doko> infinity: on i386 and amd64 as well?
[12:35] <infinity> doko : No, i386 and amd64 built fine, just ppc and ia64 choked.  I'll rety them in a bit to see if it was a transient build-dep issue.
[12:37] <infinity> Oh, wait.
[12:37] <infinity> Did I need a specific newer version of something that might be stuck in the chroots?
[12:38] <infinity> Nevermind, the chroots are up to date anyway.
[12:41] <doko> it's strange, that the generice test for X fails. please keep the build, so you have a look at the config.log file
[12:41] <infinity> Meh.  Too late to keep the build, already started it.
[12:42] <infinity> (sbuild on our buildds is configured to remove failed trees, so we don't eat disk insanely)
[12:42] <infinity> But if it fails again, I'll muck with it again and keep the tree.
[02:47] <Riddell> doko: so libstdc++ transition has happened?
[02:48] <doko> Riddell: no, no powerpc packages yet
[02:49] <Riddell> doko: so I shouldn't start uploading?
[02:57] <doko> no
[02:59] <jbailey> doko: What's blocking PPC?
[03:06] <doko> a strange build failure, no X found. infinity is currently rebuilding
[03:09] <jbailey> Feh, I hope it's not some part of the X transition.
[03:09] <jbailey> I have ppc and amd64 building.  i386 and ia64 fail for glibc right now.
[03:09] <jbailey> I'll be back to hacking on that in an hour or so, I think.
[03:15] <doko> X transition?
[03:26] <jbailey> To modular X, blocked by glibc.
[03:39] <infinity> doko : Around?
[03:42] <infinity> doko : conftest.c:23:27: error: X11/Intrinsic.h: No such file or directory
[03:47] <doko> that's in libxt-dev?
[03:47] <infinity> In theory.
[03:48] <doko> strange that his breaks on only two architectures
[03:48] <fabbione> it might as well be that the other 2 chroots are dirty :)
[03:49] <infinity> They're not.
[03:49] <infinity> I already checked that.
[03:49] <doko> fabbione: but then, my own chroots are dirty as well
[03:49] <infinity> I wonder if another -dev lib used to depend on libxt-dev, and your upload happened at just the right time to catch that changing.
[03:50] <fabbione> doko: we all know you like "dirty" stuff :P
[03:50] <fabbione> is that only on gcc-4.?
[03:50] <fabbione> or also 3.4?
[03:51] <doko> no, 3.4 doesn't build java
[03:51] <fabbione> i saw that error yesterday on -snapshot
[03:51] <fabbione> (pasted the log here)
[03:51] <fabbione> on sparc
[03:51] <infinity> I blame GTK.
[03:52] <infinity> Anyhow.
[03:52] <infinity> doko : Your configure test explicitely includes that header (it's not pulled in through a transient dep in another header), so you may as well just build-dep on libxt-dev and call it a day.
[03:53] <jbailey> I like how even GCC can say "Iz gtk bug" and possibly be right.
[03:53] <doko> :)
[03:53] <doko> infinity: that configure test comes directly from autoconf ...
[03:54] <infinity> doko : And autoconf is wrong, because it assume a monolithic X, but whatever.  One battle at a time. :)
[03:54] <infinity> I believe changes are going into autoconf upstream to make the X tests more correctly modular.
[03:55] <doko> ok, thanks for figuring that out ...
[03:56] <infinity> Can you upload ASAP, or should I just pre-seed the chroots with xt-dev and rebuild?
[03:58] <doko> uploading now ...
[03:59] <fabbione> doko: you also want to reupload gcc-snapshot
[03:59] <fabbione> for the same reason
[03:59] <doko> fabbione: not now ...
[03:59] <infinity> It's hardly urgent.
[03:59] <fabbione> fabbione doko:
[03:59] <fabbione> fabbione checking LIBART_LIBS... -lart_lgpl_2
[03:59] <fabbione> fabbione checking for XTestQueryExtension in -lXtst... no
[03:59] <fabbione> fabbione configure: error: libXtst not found, required by java.awt.Robot
[03:59] <fabbione> fabbione gcc-snapshot on sparc ^^
[03:59] <fabbione> fabbione _20051118-0ubuntu1
[03:59] <fabbione> fabbione doko: sparc is building gcc-4 and gcc-3.. if they are not FTBFS you are good go ;)
[03:59] <fabbione> no
[03:59] <fabbione> just FYI
[03:59] <infinity> xtst-dev != xt-dev
[03:59] <infinity> If Java really needs xtst-dev too, you just found another build-dep. :)
[04:00] <doko> no, that's something else. xtst-dev is needed for something called JavaRobot
[04:03] <doko> but it's interesting, that the build did succeed on i386 and amd64
[04:04] <infinity> Oh, cock.
[04:04] <infinity> doko : Do you disable logwatch on ubuntu, or is it just breaking?
[04:05] <infinity> doko : gcc-3.4 on ia64 timed out in the testsuite.
[04:05] <doko> no, it was never enabled on ia64
[04:06] <infinity> Ahh.  I assumed it was enabled on all arches.
[04:06] <infinity> Silly me.
[04:07] <infinity> Maybe if it was, the odd bugs with it occasionally hanging would have been found sooner. :)
[04:07] <infinity> (I still need to look into that some day... I had to kill logwatch on kullervo the other day for gcc-3.4... And lamont had to kill it on hppa, I think)
[04:09] <lamont-away> infinity: this time I just had to kill of an expect from 3.4
[04:09] <lamont-away> interesting... said find started after findutils sbuild started.
[04:09] <infinity> Ahh.
[04:10] <infinity> ARGH.
[04:10] <infinity> buildd-watcher on floe is racing AGAIN.
[04:10] <infinity> Why just floe?  Have you hand-hacked something there?  <stafre>
[04:10] <infinity> s/starfe/stare/
[04:10] <lamont-away> not to the best of my knowledge...
[04:11] <infinity> Same buildd-watcher as on hooker...

[04:12] <infinity> I'm going to shut down the buildd on floe for now, and look into it tomorrow when my plate's not so full.
[04:12] <infinity> Having several buildds running and competing with each other for chroots is kinda.  Uhm.  Bad.
[04:13] <infinity> (Yes, that happened earlier today)
[04:13] <infinity> Though right now, we only seem to have one buildd/sbuild, thankfully.  Many buildd-watchers, though.
[04:13] <lamont-away> buildd-watcher backs up sometimes, yes.
[04:14] <lamont-away> there might be a window where it assumes that it's find (build-tree cleaning/reporting, etc) will finish before another buildd-watcher starts.
[04:14] <lamont-away> this is not always the case...
[04:14] <fabbione> hey lamont-away
[04:15] <infinity> Oddly enough, this never seems to happen on m68k, despite my running buildd-watcher several times per hour and having really, really, really slow I/O.
[04:15] <infinity> I guess I should check your diffs against Ryan's tree.
[04:17] <infinity> doko : I see you're getting pressure from vorlon for the system compiler split.
[04:17] <infinity> (or, at least splitting java out)
[04:18] <infinity> doko : You really should have put it in big blinking letters in your toolchain roadmap so you could do it on paid time.  It's totally justifiable for Ubuntu as well.
[04:21] <doko> infinity: it should be in JavaRoadmap
[04:24] <elmo> infinity: our insane number of distros doesn't help, most m68k buildds only have one chroot to traverse
[04:24] <elmo> at least, whenever I look at a buildd they tend to sit their in io wait for a rather pointless find over the chroots
[04:24] <infinity> elmo : Well, 6.
[04:25] <infinity> But yeah, we have more than 6.
[04:26] <jbailey> What's happening with a core compiler split?
[04:27] <elmo> ?
[04:28] <doko> gcc-4.0 sucks in the whole archive as b-d's while completing libgcj  ...
[04:28] <doko> jbailey: and even in ubuntu it would be nice to get rid of the x dependencies, as you can see
[04:29] <fabbione> jbailey: i think it all goes back to modular gcc...
[04:29] <fabbione> that i did propose not too long ago to $icantrememberwhoinhere
[04:29] <infinity> Ah-ha.
[04:30] <infinity> lamont : I'll fix the "buildd-watcher takes too effin' long" bug tomorrow when I have time to test it.
[04:30] <doko> fabbione: I can't remember, did you?
[04:30] <infinity> But it's pretty obvious.
[04:30] <infinity> Original code:
[04:30] <fabbione> doko: i don't think it was to you actually
[04:30] <infinity>         next if $file =~ m#^build/chroot-[^/] +$#;
[04:30] <fabbione> doko: more likely jbailey
[04:30] <infinity> Ours kinda.  Uhm.  Doesn't do that.
[04:30] <elmo> hahaha
[04:30] <elmo> more to the point ours doesn't match 'build/'
[04:30] <infinity> Stupid build-* split.
[04:31] <infinity> elmo : Yes, we explicitely name all the build-$DIST targets in ours... Then don't exclude the chroots.
[04:31] <infinity> I'd blame lamont, but this is a public channel, and I'm a nice person.
[04:31] <infinity> Oops, gthat was my out loud voice. :)
[04:31] <infinity> s/gthat/that/
[04:31] <fabbione> ahaha
[04:32] <lamont-away> infinity: oops. :)
[04:32] <lamont-away> infinity: sigh
[04:33] <infinity> I'll fix it tomorrow.
[04:33] <lamont-away> was that in our original base, or just merged in from upstream?
[04:33] <infinity> For bonus points, I'll actually run a full watcher run, with no report-ed-old-files cache and actually clean everything up, so I can stop ignoring cron's whining.
[04:34] <lamont-away> ok
[04:34] <infinity> Heh, but if chroot is properly ignored (and ~/ccache as well), that's a non issue.
[04:34] <infinity> elmo : floe should stop setting off alarms for you.
[04:35] <infinity> Though I'm curious why floe is the only one that races this badly.  Either it has one mother of a huge chroot somewhere (that should be removed and rebuilt), or something's desperately wrong with that box.
[04:36] <infinity> I'm going to assume the former, cause it seems well behaved otherwise.
[04:36] <lamont-away> fwiw, pitti picks really ugly version numbers
[04:37] <lamont-away> inkscape_0.42-1build1ubuntu0.1 is now in breezy-security
[04:37] <infinity> foo_1.2.3-1ubuntu05.10?
[04:37] <infinity> Oh, eww.
[04:37] <lamont-away> 'zactly
[04:38] <infinity> Someone should point out to him that 'u' is higher than 'b'.
[04:38] <elmo> did you guys get my mail about b-backports btw?
[04:38] <elmo> [nb: I'm not chasing, I don't care when it's done, just checking]
[04:38] <lamont-away> elmo: when did you send it?
[04:38] <infinity> elmo : Yes, and I'll enable it tomorrow, if the world doesn't come to an end first. :)
[04:39] <lamont-away> there it is
[04:39] <elmo> infinity: kthx
[04:39] <infinity> Unless lamont feels the urge.
[04:39] <fabbione> can't we forget about -backports by ... let say.. mistake?
[04:40] <fabbione> i mean
[04:40] <fabbione> that would comply with the specs
[04:40] <lamont-away> infinity: I'll go ahead and create the chroots - that's the easy part.
[04:41] <lamont-away> then it should autostart when the nightly chroot update runs
[04:41] <fabbione> quoting: https://wiki.ubuntu.com/BackportsPromotion
[04:41] <infinity> Such faith you have in your automated tools.  I like it.
[04:41] <fabbione> "Make people more aware of backports, and make the backport request process LESS transparent"
[04:42] <lamont-away> adare is now launchpad, yes?
[04:42] <fabbione> i can't see anything more hidden than not creating the chroots ;)
[04:42] <infinity> lamont-away : In theory.  Not sure it's being used as such, but it's definitely not hooked into w-b either.
[04:42] <infinity> fabbione : Hah.  Nice thinko.
[04:43] <fabbione> infinity: when i read that at UBZ i was >< this close to approve the specs :D
[04:43] <infinity> Sadist.
[04:43] <fabbione> oh yeah
[04:44] <fabbione> I LOVE TO SEE PEOPLE SUFFER IN ENDLESS PAIN
[04:44] <infinity> What I wouldn't give for a nasty case of narcolepsy in my old age.
[04:45] <infinity> Man, HP really makes you start at the bottom of the ladder when you're a new hire again, don't they? :)
[04:58] <lamont-away> elmo: chroots are created everywhere
[04:58] <lamont-away> infinity: nah - this is house work... and the more I procrastinate, the deeper the sludge in the tank.  Hence, todya
[04:59] <lamont-away> the damage was discovered friday when the nice people pumped the tank for me.
[04:59] <lamont-away> but I fear I shall be buying hip-waders before the day is out.
[05:00] <infinity> And throwing them out tomorrow.
[05:00] <lamont-away> nah - you just put trash bags on them first. :-)
[06:53] <Riddell> infinity: are you going to upload subversion with new libdb ?
[06:58] <doko> Riddell: he has to ... it's not buildable otherwise
[06:59] <Riddell> and neither is large chunks of KDE
[09:34] <lamont-away> checking for XTestQueryExtension in -lXtst... no
[09:34] <lamont-away> configure: error: libXtst not found, required by java.awt.Robot
[09:34] <lamont-away> interestingly, libxt-dev is in build-depends
[09:45] <doko_> lamont-away: which architecture?
[10:04] <lamont-away> that was -2 on ppc
[10:05] <lamont-away> is -3 the end of it?
[10:43] <fabbione> i told ya that we needed more :)
[10:43] <fabbione> gcc-snapshot rules!
[10:45] <fabbione> doko: still around?
[10:59] <doko> fabbione: yes
[10:59] <fabbione> doko: ok-- gcc-4.0 is going to build in 10/15 minutes of sparc
[10:59] <fabbione> 3.4 is up
[11:00] <fabbione> do we need gcj before we start the transition?
[11:00] <doko> no
[11:00] <doko> hmm, but gettext depends on it ...
[11:00] <fabbione> is gettext a pkg that needs transition?
[11:03] <fabbione> well i guess it's going to stall the others
[11:04] <fabbione> we will see tomorrow
[11:04] <fabbione> doko: thanks for the info
[11:04] <fabbione> i am off to sleep
[11:04] <doko> no, it doesn't need a transition, but a working libgcj
[11:04] <fabbione> ok
[11:06] <lamont> gcc-4.0 (-3) will start building on hppa momentarily
[11:08] <doko> note that I did separate the build of the gcj packages into a separate source package, so you need to build that as well. that's currently stuck in NEW
[11:09] <lamont> can we get that unstuck please?
[11:09] <lamont> or does that not need to happen before the transition starts?
[11:09] <lamont> avg-pkg-build-time gcc-4.0
[11:09] <lamont> gcc-4.0:                06:31:36 (3 entries, sigma 00:46:59)
[11:11] <doko> the build time will drop, it doesn't build java anymore


[00:25] <ianorlin> is this a new hard disk?
[00:25] <ianorlin> like you bought it from a store or online DutchC64
[01:21] <DutchC64> hey...sorry for the late response, the harddrive isn't new...
[02:34] <wxl> so changing the NetworkManager.policy settings.modify.system to allow_active yes allows all users whether admins or not to connect to different wifi access points. this is good, but is there not a gui way to do this?
[07:41] <cristian_c> Hi
[07:42] <cristian_c> I've purchased a Rii mini i8 bluetooth keyboard
[07:42] <cristian_c> How can i enable the keyboard in lubuntu?
[07:42] <cristian_c> Any ideas?
[07:42] <cristian_c> I've paired it
[09:29] <cristian_c> The server has disconnected me
[09:30] <cristian_c> Has anyone answered to me?
[09:36] <hateball> cristian_c: Sadly no
[09:36] <cristian_c> ok
[09:36] <hateball> (and I don't know)
[15:33] <wllrt> Anyone know of a good screenshot tool? Running Lubuntu 13.10.
[15:42] <ianorlin> w11rt scrot works from the command line still and is installed and you can put a slight delay on with the d optoin if you don't want the terminal or run dialog
[15:44] <wllrt> ianorlin: Thanks. I was just reading about scrot. I am googling on how to select area for screenshot.
[15:44] <ianorlin> scrot -s
[15:44] <ianorlin> if you want a place to look back to type man scrot
[15:44] <wllrt> Thank you. Much obliged :).
[15:44] <wllrt> Alright. I will.
[17:54] <sadfasdfsadf> hello, can someone help me autostart a graphical application at login
[18:02] <ianorlin> try using default apps for lxession under prefrences in the menu
[18:07] <sadfasdfsadf> ianorlin: added an entry there, rebooting
[18:08] <sadfasdfsadf> awesome, that works perfectly
[18:08] <sadfasdfsadf> thanks so much
[19:40] <raalex> I am experiencing problems with the Keepass autotype feature.
[19:40] <raalex> Meaning, that it often misses letters, which of course leads to passwords/usernames being incorrect.
[19:41] <raalex> Did anyone in here run into that problem already and figured out a solution?
[19:42] <silverlion> hey raalex i did. re-installed the xdotool and everything works fine since then
[19:42] <raalex> Cool, thanks. I'll give it a try.
[19:43] <silverlion> raalex: kk
[23:14] <deleted_> team


[02:32] <ging> is there any documentation on post_scripts for maas?
[04:51] <Lord_Set> I haven't found any. There doesn't currently seem to be much public documentation on a lot of the scripting and aspects of MAAS.
[05:14] <ging> i just need to be able to run a single command as sudo / root after all the packages have installed, adding the line to post_scripts in the generic preseed file seems to get it trying to run it, but it fails with error code 127 which is command not found, which is odd because the package should be installed at that point
[05:18] <ging> some of the commands in the normal post_script say in-target before the command
[05:19] <Lord_Set> which command are you trying to run?
[05:20] <ging> trying to get it to enable puppet
[05:20] <ging> puppet agent --enable
[05:42] <ging> ah adding in-target was what i needed
[05:42] <ging> it now runs
[13:16] <Lord_Set> morning everyone
[21:25] <sv2241_> hi following https://maas.ubuntu.com/docs/install.html on a Ubuntu 12.04 vmguest
[21:25] <sv2241_> root@ubunt1204LTS:~# maas my-maas-session node-groups import-boot-images
[21:25] <sv2241_> Unknown command: 'my-maas-session'
[21:25] <sv2241_> Type 'django-admin help' for usage.
[21:25] <sv2241_> root@ubuntu1204LTS:~#
[21:26] <sv2241_> wtf?!
[22:35] <bigjools> sv2241_: the docs are for trunk; we are aware of the mess
[22:36] <bigjools> use "maas-cli"
[22:36] <bigjools> where it says "maas"
[22:36] <bigjools> hello Lord_Set.  We are all in Australia this week doing a code spike, so we are unlikely to be particularly responsive to questions