[03:08] <lotuspsychje> good morning to all
[05:37] <lotuspsychje> !ltsupgrade
[06:12] <lordievader> Good morning
[06:21] <ducasse> good morning
[06:35] <lordievader> Hey ducasse
[06:35] <lordievader> How are you doing?
[06:38] <ducasse> hi lordievader - all well, thanks, and you?
[06:38] <lordievader> Doing good here.
[06:38] <lordievader> Anything interesting planned for today?
[06:39] <ducasse> dark clouds today, maybe we'll get some of the rain we've been promised
[06:40] <ducasse> no major plans, think i'll start reading some books i picked up at the library, and might have to take a quick trip into the city centre
[06:40] <ducasse> how about you?
[08:10] <lordievader> Work, work, work.
[11:42] <pauljw> hi everyone
[11:49] <ELQEYNN> How did the Zulus, of all people, come to develop their own Linux distro?
[11:50] <lotuspsychje> ELQEYNN: please no jokes here
[11:51] <lotuspsychje> yeah he wined same question yesterday too
[11:52] <leftyfb> I know https://pastebin.ubuntu.com/p/nm3CgHj4B7/
[11:53] <lotuspsychje> right
[11:54] <leftyfb> It's ridiculous that the ops love to play the same game every time a troll acts up. Like this time is going to be different.
[11:54] <lotuspsychje> they never change
[11:54] <lotuspsychje> trolss are for life
[11:55] <leftyfb> Not always, but most of the time. And I've been pretty good determining this for the past 20 years I've been op on other channels
[11:55] <lotuspsychje> leftyfb for ops in #ubuntu!
[11:56] <leftyfb> These ops on the other hand don't seem to be able to determine a troll after 200 lines of garbage being posted to a channel or literally begging to be banned
[11:57] <lotuspsychje> yeah
[11:57] <leftyfb> apparently that'll never happen. I've been told by multiple existing ops that I'll never be one. Also I haven't heard any sort of official response to my application
[11:59] <lotuspsychje> leftyfb: UWN says there's a new vote for council
[11:59] <leftyfb> I won't be getting my hopes up.
[11:59] <leftyfb> Though at the very least they certainly need more
[12:00] <leftyfb> It would be great to add a few from here
[12:00] <lotuspsychje> there should be an easy vote system or so
[12:00] <leftyfb> oh, don't assume anyone besides the exiting ops will be voting
[12:56] <BluesKaj> Hiyas all
[13:03] <pauljw> morning BluesKaj
[13:04] <BluesKaj> 'Morning pauljw
[13:04] <pragmaticenigma> 'lo
[13:05] <pauljw> hi pragmaticenigma
[13:13] <ducasse> wb BluesKaj
[13:14] <BluesKaj> hey ducasse
[13:15] <ducasse> how are you today?
[13:15] <BluesKaj> I'm fine, how about you ?
[13:16] <ducasse> all good, still waiting for the rain we were promised today
[13:17] <BluesKaj> no rain predicted here 'til next week
[13:17] <BluesKaj> forest fires all around us
[13:18] <ducasse> scary
[13:20] <BluesKaj> quite a distance away, but it's smokey depending on wind direction
[13:20] <hggdh> only members of the Ubuntu IRC Members team in LP (https://launchpad.net/~ubuntu-irc-members) can vote for the IRCC
[13:20] <JimBuntu> BluesKaj, Good morning... also, please put out your forest fires as we don't need any more smoke over here.
[13:20] <BluesKaj> JimBuntu, send help :-)
[13:21] <JimBuntu> BluesKaj, International aid will go to whoever hasn't finished putting out their own fires first. It seems like NA is on fire.
[13:21] <BluesKaj> most help is probly already in California
[13:22] <BluesKaj> we have 20 firefighters from Mexico helping here
[13:23] <BluesKaj> yeah, British Columbia, Alberta, Northern Ontario , California are burning
[13:23] <JimBuntu> Dear Mexico, please send more firefighters, and ask your neighbors if they can spare some too.
[13:24] <JimBuntu> There was an outbreak in one or more of the North Eastern USA states, but I think they got that under control pretty quick.
[13:25] <ducasse> greetings, JimBuntu
[13:25] <BluesKaj> 143 fires in BC, we have 44 in NOnt
[13:25] <JimBuntu> I saw some interesting pictures the other day where the smoke could be seen stretching basically from the West coast nearly to the East coast.
[13:25] <JimBuntu> Hiya ducasse
[13:26] <JimBuntu> re-open the bigger game season, to get a permit, you have to do 1 day helping the firefighters first. I'm sure the fires are pushing all kinds of animals out of where they should be.
[13:28] <pragmaticenigma> We're getting some interesting sunrises and sunsets because of the fires out west. Most mornings and afternoons have had some vivid red hues because of the smoke in the air
[14:19] <BluesKaj> well, duty calls, doing some cleanup in our garage/studio after a summer of dust and bug infestation...later gents
[16:57] <lotuspsychje> good evening to all
[16:57] <lotuspsychje> xenial box at my aunt has working realtek network card again
[16:58] <lotuspsychje> !info linux-image-generic xenial
[16:59] <lotuspsychje> what current hwe kernel for xenial again?
[17:02] <nacc> !hwe | lotuspsychje
[17:02] <nacc> https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2FSupport.A16.04.x_Ubuntu_Kernel_Support
[17:03] <nacc> specifically
[17:03] <nacc> should be 4.4 and 4.15 only on 16.04 now
[17:03] <lotuspsychje> nacc: same as bionic? saw indeed auto kernel cleanup 4.15..something
[17:04] <nacc> lotuspsychje: yes, typically the case (3 months after each release, LTS get HWE stack)
[17:04] <lotuspsychje> ah tnx
[17:04] <JimBuntu> https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack
[17:05] <nacc> there's also -edge or whatever, but i tend to ignore it
[17:05] <lotuspsychje> so that makes sense, xenial updates made the realtek work again after months on 4.13
[17:05] <lotuspsychje> gonna add it to bug report
[17:08] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386
[17:08] <lotuspsychje> tnx nacc JimBuntu
[17:09] <lotuspsychje> lets hope she can use the realtek a bit longer now
[17:11] <lotuspsychje> bionic upgrade window also showed up, so nicely
[17:33] <tomreyn> what's trhe current workaround for nvidia prima on bionic?
[17:33] <tomreyn> *prime
[17:34] <lotuspsychje> !info nvidia-prime
[17:35] <lotuspsychje> tomreyn: when installing the nvidia driver, prime should also be installed, for cards that allow optimus
[17:36] <lotuspsychje> but we having alot of users with GTX cards getting stuck on black screens on current bionic driver
[17:37] <lotuspsychje> !info nvidia-driver-390
[17:37] <lotuspsychje> .48 gives alot of problems
[17:38] <tomreyn> my understanding (not sure where i have it from or whether it's still correct) is that prime currently doesn't work on bionic (due to the nvidia company not producing drivers which work reliably with current linux versions).
[17:38] <tomreyn> ... or not in time
[17:39] <lotuspsychje> i havent encountered optimus issues yet in main on bionic tomreyn you?
[17:40] <tomreyn> i think a ppa was mentioned, and that there is work under way to enable users to disable the discrete graphics entirely so at least the integrated graphics can be used reliably for now.
[17:40] <lotuspsychje> the main problems on optimus in the past were, they need to match the right nvidia driver for the card (driver working best)
[17:40] <tomreyn> lotuspsychje: yes, someone else had similar issues, we worked around it by making linux ignore the hardware at boot
[17:42] <tomreyn> and i think i've seen a couple more reports about prime setups not working with 18.04 in #ubuntu lately. but not sure how they were solved, or whether.
[17:42] <lotuspsychje> tomreyn: ill keep an eye on those specially ok
[17:42] <tomreyn> i dont run nvidia anywehre, so don't have good experience there
[17:43] <tomreyn> thanks
[17:44] <lotuspsychje> tomreyn: what i have seen most as fixing now is: 390.77 396.48 from graphics ppa & the nvidia drivers from website
[17:44] <tomreyn> what is "graphics ppa"?
[17:44] <lotuspsychje> tomreyn: ubuntu graphics ppa sorry
[17:44] <lotuspsychje> or oibaf
[17:45] <tomreyn> this one? https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa
[17:45] <tomreyn> probably
[17:46] <lotuspsychje> yes
[17:46] <lotuspsychje> and same launchpad for oibaf
[17:48] <tomreyn> thanks, oibaf i know, just didnt know there was a canonical ppa for nvidia
[17:48] <lotuspsychje> handy when default things temporary dotn work
[17:52] <pragmaticenigma> !ltsupgrade
[17:52] <pragmaticenigma> hehe
[17:52] <tomreyn> :-/
[17:54] <lotuspsychje> didnt came tru, dang
[17:54] <lotuspsychje> lemme try again guys
 Your edit request has been forwarded to #ubuntu-ops.  Thank you for your attention to detail
[17:57] <lotuspsychje> tomreyn: remember wich driver version arpad has?
[18:02] <tomreyn> lotuspsychje: no, but it should be somewhere in their two termbin posts
[18:03] <tomreyn> [    73.496] (II) NVIDIA GLX Module  390.48  Wed Mar 21 23:42:56 PDT 2018
[18:03] <lotuspsychje> ok tnx
[18:53] <pragmaticenigma> sucks to be ask... I had the exact same issue with a drive... worked fine until Ubuntu took control of the machine
[18:53] <pragmaticenigma> I solved it... too bad from them
[18:54] <pragmaticenigma> for*
[18:54] <lotuspsychje> he's monologueing
[18:54] <pragmaticenigma> They're impatient and expecting someone to have the answer in an instant
[18:55] <pragmaticenigma> Mom prolly bought 'em a 'puter for their b-day
[18:55] <lotuspsychje> and more, they expect to be how they think
[19:00] <pragmaticenigma> It's not a BIOS issue. And I know they didn't do as I had asked, because the eject command would have given them feed back that would have helped trouble shoot... same with dmesg which they refuse to provide
[19:01] <pragmaticenigma> if only ioria was in here
[19:01] <lotuspsychje> indeed pragmaticenigma just tested on my dvd-less netbook: instant error
[19:21] <lotuspsychje> leftyfb: also known troll ubu..
[19:21] <leftyfb> not really a troll, Just very uneducated
[19:21] <leftyfb> and a bit of a pain
[19:21] <lotuspsychje> lol
[19:25] <pragmaticenigma> Can we turn back on +R again for the room?
[19:26] <lotuspsychje> then it will be even more dead pragmaticenigma
[21:51] <hggdh> nacc: I think this was enough
[21:51] <nacc> hggdh: yeah, sorry if i escalated
[21:52] <nacc> they have most disparaged ubuntu in my interactions with them over a few days
[21:52] <hggdh> nacc: you did not.
[21:52] <nacc> honestly never heard someone say they couldn't find the bug tracker :)
[21:53] <hggdh> I have, but all of them quickly found themselves the correct link, and then it was just trying to learn to report a bug
[21:53] <nacc> yeah
[21:53] <nacc> i could see that, but they weren't even to that point
[21:53] <nacc> they also asked why we couldn't just use what FreeBSD had built for some package
[21:54] <nacc> all rather strange
[21:54] <hggdh> indeed
[21:54] <nacc> and they're back
[21:54] <hggdh> but their questions have almost always been bordering the weird
[21:56] <hggdh> and... I am pretty sure they will add me to their /ignore list. It will be fun
[21:56] <nacc> heh
[22:09]  * hggdh grabs some popcorn
[22:09] <nacc> lol
[22:09] <leftyfb> :)
[22:10] <leftyfb> I'm all riled up from a "discussion" from our makerspace. I might enjoy this a bit
[22:10] <daftykins> https://media.giphy.com/media/dnP2VxYVlW2NW/giphy.gif
[22:10] <daftykins> relevant :) if you can excuse the commonplace illiteracy style
[22:12] <hggdh> :-)
[22:22] <leftyfb> tada
[22:22] <tomreyn> nacc: launchpad new account registration is apparently broken currently. i was able to reproduce what was stated in #ubuntu
[22:22] <nacc> tomreyn: i see
[22:22] <nacc> yeah i saw your comments #lp
[22:22] <tomreyn> oh ok
[22:22] <nacc> hopefully cjwatson or wgrant respond
[22:22] <nacc> i no longer have much power to do anything about it :)
[22:23] <tomreyn> we shall see, earlier or later someone will surely handle it
[22:23] <daftykins> nothing like the irony of a bug in the bug reporting account reg
[22:24] <tomreyn> it's a system, systems fails occasionally, it's unpleasent in this case but it cant be prevented really.
[22:24] <nacc> it's a *complex* system too
[22:24] <nacc> which makes it an invariant that there will be afilures
[22:24] <nacc> it's a long tail of them, arguably
[22:24] <leftyfb> looks like installing from pip is broken too :/
[22:25] <leftyfb> https://pastebin.ubuntu.com/p/N3dMFPGQhY/
[22:25] <daftykins> let's not forget the line of work we're all in when stating the obvious :)
[22:26] <nacc> heh
[22:28] <leftyfb> he's gonna be mad
[22:29] <leftyfb> unless it's just an issue on my end with my container
[22:31] <leftyfb> guess it's just a container issue
[22:33] <leftyfb> https://pastebin.ubuntu.com/p/KhybFYwbBx/
[22:33] <leftyfb> there's some weird order of operations with purging/installing subliminal and it's deps with apt/pip, but it eventually worked
[22:34] <leftyfb> ok, i'm out ... cyas :)
[22:34] <daftykins> o/
[23:24] <tomreyn> quote form #ubuntu-kernel: "I'm seeing files disappearing on my btrfs system on 4.17 (a few each day). I guess I'll revert to 4.15 and see if that is affected too."
[23:24] <tomreyn> i know why i prefer ext4
[23:25] <daftykins> :S pretty much never heard of anyone with a smooth sailing experience with btrfs
[23:25] <nacc> lol
[23:25] <daftykins> i'm gonna start reading it as 'butter file system' from now on, i think
[23:26] <nacc> that's how it was pronounced by most when it was introduced
[23:27] <hggdh> yes. And it seems it is behaving pretty much like warm butter
[23:29] <daftykins> :>


[00:23] <RoadRunner> ... or will I need an outside booter like Super Grub2 Disk to find the new partition and boot from it?
[00:51] <GeekDude> RoadRunner: IIRC you have to run 'sudo update-grub' from your main partition
[00:51] <GeekDude> That should make it pick up on any new partitions
[00:59] <RoadRunner> GeekDude: so: make a new partition, intall the backup image onto it with the app that made it, reboot into original partition, run 'sudo update-grub', reboot and look for a new entry.  Will the new "Ubuntu" be labeled "2" or something to differentiate it from the first?
[00:59] <pencilandpaper> Hi RoadRunner ..sorry about the other day. I was afk man.
[01:00] <GeekDude> RoadRunner: I'm not entirely sure, I haven't done multiple partitions in a while. I would think it'd have the partition name listed somewhere (e.g. sda2)
[01:01] <RoadRunner> pencilandpaper: no worries, I'd like to touch bases with you on some fine tunning of BleachBit but we better do this later, cause I am almost out of time now
[01:02] <RoadRunner> GeekDude: is there a way to change how the choices of bootable options are named?
[01:02] <RoadRunner> ... in grub?
[01:02] <GeekDude> I'm honestly not sure. I'm a far cry from an expert
[01:04] <RoadRunner> GeekDude: but you are sure that 'sudo update-grub' is enough to pick up the new boot option right?
[01:06] <GeekDude> Fairly sure
[01:07] <GeekDude> Google probably knows better than I
[01:07] <gtn> Google always does.
[01:07] <RoadRunner> GeekDude: thanks for taking the time to answer :)
[01:08] <GeekDude> RoadRunner: Glad to help!
[01:15] <xubuntu32d> new to linux downloaded sound converter from software center and it opens fine but when i hit convert it just closes
[03:12] <GeekDude> On a scale of one to ten, how bad would it be to use a generic 32Gig flash drive as a main drive?
[03:13] <xangua> 11
[03:16] <GeekDude> Supposing I got rid of the page file, and had /tmp on a ram disk
[03:16] <DrCool> is 1 bad and 10 good
[03:16] <DrCool> ?
[03:16] <GeekDude> 10 is bad
[17:29] <jwash> hi everyone, i have a firewall problem and i'm hoping someone can assist me.
[17:29] <jwash> i have a computer which receikves local traffic fine, no internet traffic
[17:29] <jwash> the router is setup correctly for port forwarding, other computers on my network receive inbound traffic fine
[17:30] <jwash> it was a gradual thing too, one day my znc stopped working but ftp was fine, then ftp went away, till all of my services died
[22:08] <xubuntu56w> anyone knows how to disable the dock magnification effect on Voyager 14.04?
[22:09] <Unit193> xubuntu56w: Hello, Voyager is a deriv of Xubuntu and not Xubuntu itself, for support please see their own support mediums.
[22:09] <xubuntu56w> where?
[22:09] <Unit193> I'd guess it lists them on their website.
[22:10] <xubuntu56w> it forwards from their website to you guys
[22:10] <xubuntu56w> never mind I will look further
[22:10] <xubuntu56w> thanks
[22:14] <knome> ...yeah, they do.
[22:21] <Heist> What dock does 14.04 have? Im on 15.10 and I don't have a dock
[22:21] <knome> it's all xfce4-panel
[22:21] <knome> set to autohide, with a translucent background
[22:21] <Heist> ahh
[22:29] <xangua> Or just use whatever "dock" you prefer
[22:56] <monkey_> With the file search program in Xubuntu, is it possible to search for all files except for ones containing a particular string?


[10:52] <elacheche> https://ds9a.nl/articles/posts/spectre-meltdown/
[10:52] <elacheche> nzoueidi: Take a look ;-)
[11:22] <nzoueidi> Good article, I like it :D
[16:26] <elacheche> nzoueidi: You'll join the meeting tonight?
[16:29] <nzoueidi> Yep, elacheche I will what time exactly?
[16:29] <nzoueidi> I didn't forget about the acheivement section too btw
[16:30] <elacheche> Should be 9pm.. You have the wiki page, and have edit permission, you hack whatever you like/need..
[16:34] <nzoueidi> Sure, I will.
[18:04] <elacheche> o/
[18:09] <nzoueidi> \o
[21:06] <elacheche> So folks, we just got re-approved as an official LoCo Team, that was extreemly hard! But we did it.. I'll share the news and the logs in a minute via the ML


[23:16] <salih-emin> Hi to all ! Ι want a cloak as ubuntu member. Here is my launchad page : https://launchpad.net/~salih-emin
[23:17] <k1l_> looks good, congrats for membership salih-emin
[23:17] <salih-emin> thnx !
[23:17] <k1l_> we just need someone from the IRCC to confirm and then somone from staff to set the cloak :)
[23:18] <salih-emin> OK is there anything that I should do ? or this is recorded and will be processed  later ?
[23:20] <k1l_> when someone from the ircc looks in here he will confirm. just sit and wait, maybe AlanBell takes a look (since he is not marked away)
[23:20] <salih-emin> ok thank !


[01:14] <mmikowski> RikMills[m]: I have downloaded, inspected, modified, and tested kdenetwork-filesharing (recall https://libera.ems.host/_matrix/media/v3/download/kde.org/6e9190dc97e45eb3ace9b396b19c2df171caf85c/image.png). I have confirmed that the samba object is being created with Samba.install being compiled-in, and it's still broken. I can keeps poking at it,
[01:14] <mmikowski> but do you have any thoughts on what could be causing this? I'd hate to go down too many rabbit holes if I don't have to!
[12:15] <BluesKaj> Hi all
[18:11] <RikMills> mmikowski: not really. filing a kde bug would probably be good idea. I think it is broken in Neon also
[18:12] <RikMills> though Neon does not install kdenetwork-filesharing by default, so it may not have been picked up
[18:50] <RikMills> the logs say that packagekit tried to obtain auth to install samba, but failed
[18:51] <RikMills> that should initiate a polkit password dialogue, but it never appears
[18:52] <RikMills> the same process in discover does launch a polkit dialog, so that works fine
[18:53] <RikMills> I'll test in Neon shortly and file a bug
[22:30] <mmikowski> RikMills: That alone is good direction. What logs are you looking at? If you do file a bug, please let me know and I may be able to contribute to it.
[22:41] <RikMills[m]> mmikowski: just the output of journalctl
[22:41] <RikMills[m]> https://bugs.kde.org/show_bug.cgi?id=472145
[22:41] -ubottu:#kubuntu-devel- KDE bug 472145 in kdenetwork-filesharing "Install samba feature/button fails to install samba via packagelkit" [Major, Unconfirmed]
[22:46] <mmikowski> RikMills[m]: That's what I was thinking, filtered for kde, but I thought I'd ask :)
[22:49] <RikMills[m]> if you filter/grep just for kde you will miss some of it I thing. best to just look at the end of the output ASAP after trying it
[22:49] <RikMills[m]> *I think
[23:29] <mmikowski> Thanks Rik. Good point.


[00:08] <mup> PR snapcraft#2897 opened: meta: include environment in hook wrappers <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2897>
[00:14] <mup> PR snapcraft#2893 closed: [legacy] meta: include environment in hook wrappers <Created by kyrofa> <Closed by cjp256> <https://github.com/snapcore/snapcraft/pull/2893>
[01:17] <mup> PR snapcraft#2898 opened: meta: remove dead code from snap packaging <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2898>
[06:01] <mborzecki> morning
[06:03] <mvo> hey mborzecki ! good morning
[06:04] <mborzecki> mvo: hey!
[06:04] <mup> PR snapd#8049 closed: tests: fix revisions leaking from snapd-refresh test <Test Robustness> <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8049>
[06:19] <mup> PR snapd#8032 closed: boot, cmd/snap, cmd/snap-bootstrap: move run mode and system label detection to boot <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/8032>
[06:23] <mup> PR snapd#8040 closed: gadget: skip update when raw structure content is unchanged <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8040>
[06:48] <mup> PR snapd#7993 closed: devicestate: enable encryption based on model grade <UC20> <Created by cmatsuoka> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/7993>
[07:26] <zyga> Hey guys
[07:27] <zyga> I’m going to check my wrist
[07:27] <zyga> I have a visit at 9:30
[07:27] <zyga> I’ll be back later
[07:36] <mvo> zyga: good luck
[07:38] <mborzecki> zyga: hey
[07:49] <mborzecki> btw. played a little with gnome-builder yesterday, it'd be nice to have some snap integration there, looks like it supports building flatpaks ootb
[07:57] <jamesh> mborzecki: I did some work on that ages ago.  I set it aside, as I couldn't get things to work the way upstream wanted without changes to Snapcraft, and couldn't get buy-in to get those Snapcraft features done.
[08:00] <mborzecki> jamesh: interesting, thanks for the insight!
[08:01] <jamesh> mborzecki: my patch essentially introduced "Snapcraft" as a new build system.  What they wanted was to keep the underlying build system visible (i.e. automake, meson, etc), and allow Builder to invoke it
[08:03] <jamesh> The idea is that build system plugins could support operations like "add newfile.c to library X", and they would update the appropriate makefile or equivalent
[08:05] <jamesh> you also want to be able to determine compile flags for each source file in order to properly parse them for completion
[08:05] <jamesh> so if Snapcraft was build system, it would need to reimplement all of this for each of its supported build systems
[08:06] <mborzecki> jamesh: yeah, makes sense when you're working on your piece of software and snapcraft is really just a packaging method
[08:07] <mborzecki> jamesh: btw. have you worked with builtstream too?
[08:09] <jamesh> mborzecki: IIRC, the Flatpak plugin adds an early build step to download dependencies, and provides the appropriate environment to run the underlying build system.  There's also an extra step at the end to package up the result
[08:09] <jamesh> There is the risk that this could produce different results to a standard build, but it means you have incremental builds and all the IDE features
[08:09] <jamesh> I haven't looked at Buildstream
[08:23] <mup> PR snapd#8054 opened: snap: add `snap pack --compression=<comp>` options <Performance 🚀> <Created by mvo5> <https://github.com/snapcore/snapd/pull/8054>
[09:05] <Chipaca> mo'in, all
[09:07] <mvo> hey Chipaca and pedronis ! good morning
[09:07] <pedronis> hi
[09:07] <Chipaca> mvo: had an adequate amount of rest? :-)
[09:09] <Chipaca> pedronis: I set up a short meeting to go over some things about manpages, either to clear the path for me to push a PR with it this week, or to spread the knowledge around of what needs doing later
[09:09] <pedronis> Chipaca: yes, saw it
[09:10] <Chipaca> mvo: pedronis: it just struck me that postUserCreateData's ForceManaged flag might be deprecated as well, I'm not clear what the use case was for it (ie should I leave it behind in the to-be-deprecated endpoint or carry it forwards as is currently done)
[09:11] <pedronis> Chipaca: it's a bit of an orthogonal concern, I think we do want to carry it forward
[09:11] <pedronis> even it's hopefully low usage
[09:12] <Chipaca> k
[09:14] <mvo> Chipaca: people seems to use the flag to create additional users on devices which seems to be a valid use-case. the name is a bit confusing though :/
[09:14] <mvo> Chipaca: thanks for setting up that meeting
[09:14] <Chipaca> mvo: should I add you to it? so far it's me, zyga, pedronis
[09:15] <Chipaca> mvo: working on the assumption that you don't love meetings _that_ much :-p
[09:16] <mvo> Chipaca: I'm fine not being part of it
[09:31] <zyga> I’ll be back soon
[09:31] <zyga> Hey pedronis, welcome back :-)
[09:31] <mborzecki> Chipaca: pedronis: hey
[09:32] <zyga> Hey mborzecki :-)
[09:33] <pedronis> mvo: zyga: shouldn't the disabling in<PHONE_NUMBER>cbf containt TODO:UC20 ?
[09:35] <zyga> If that is the patch I think it is there was a follow up that adds the todo core 20 marker
[09:36] <zyga> (I’m still afk for a short while)
[09:38] <pedronis> mborzecki: in the doc comment for ModeAndRecoverySystemFromKernelCommandLine "returns the current run mode", I think we need to s/run/operating/
[09:39] <mvo> pedronis: I had the same comment about the todo:uc20 and it was added in pr 8050
[09:39] <mup> PR #8050: tests: add marker tag for core 20 test failure <Simple 😃> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/8050>
[09:39] <pedronis> ah ok
[09:39] <pedronis> good
[09:41] <mborzecki> pedronis: ack
[09:45] <mup> PR snapd#8055 opened: boot: tweak kernel cmdline helper docstring <Simple 😃> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/8055>
[09:45] <mborzecki> hm, it'd be cool if we could indicate that full spread run is unnecessary for PRs like that
[09:57] <pedronis> mborzecki: maybe there's a way to read via the api if a given label is applied to the PR
[09:59] <mborzecki> pedronis: that or just scrape the page, like we did with the PR title, as the API had limitations and required api key
[10:03] <mup> PR snapd#8056 opened: client: move user-related things to their own files <Simple 😃> <Created by chipaca> <https://github.com/snapcore/snapd/pull/8056>
[10:06] <Chipaca> mborzecki: pedronis: FWIW, https://gist.github.com/chipaca/911a8a4905b091c10caa9854bf7ea4b4 looks at labels on PRs
[10:06] <Chipaca> they're reasonably straightforward to get
[10:06] <Chipaca> (but yes without an api key we'd hit rate limits very fast)
[10:10] <pedronis> mvo: did you see this: https://forum.snapcraft.io/t/auto-import-assert-fails/15181
[10:11] <mvo> pedronis: have not seen it, will followup
[11:13] <zyga> brb
[11:27] <mup> PR snapd#8057 opened: overlord/auth: add RemoveUserByName <Simple 😃> <Created by chipaca> <https://github.com/snapcore/snapd/pull/8057>
[11:32] <zyga> Chipaca: reviewed
[11:32] <popey> Hm, anyone built an image with series:: "18"? ubuntu-image doesn't seem to like it
[11:32] <popey> https://tutorials.ubuntu.com/tutorial/create-your-own-core-image
[11:33] <zyga> popey: series 18 is not a thing
[11:33] <zyga> series is always 16
[11:33] <popey> oh
[11:33] <zyga> popey: and hi :)
[11:33] <popey> thats odd :)
[11:33] <Chipaca> popey: series is the restart-the-world generation switch
[11:34] <Chipaca> popey: if we change the series it's because we're starting over
[11:34] <zyga> we should have called it multiverse
[11:34] <Chipaca> popey: as in, nothing from series X works on series Y
[11:34] <Chipaca> popey: granted in retrospect we should've made it more internal-only, but we hadn't learned how to make things co-habitate back then
[11:34] <Chipaca> we thought we'd have to bump the series every lts
[11:34] <Chipaca> or something like that
[12:05] <popey> Is it possible to seed something to stop me having to do the U1 SSO dance on first boot of a core device?
[12:07] <mup> PR snapd#8058 opened: run-checks, travis: allow skippng spread jobs by adding a label <Skip spread> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/8058>
[12:10] <mborzecki> anyone remember when cachio is coming back?
[12:10] <zyga> next week
[12:10] <mborzecki> ah, ok
[12:13] <zyga> focal with zfs
[12:13] <zyga> oh mhy
[12:14] <mup> PR snapd#8053 closed: osutil: implement deluser <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/8053>
[12:16] <mborzecki> zyga: is the oracle police already banging at your door trying to extort a fee? :)
[12:16] <mup> PR snapd#8055 closed: boot: tweak kernel cmdline helper docstring <Simple 😃> <Created by bboozzoo> <Merged by cmatsuoka> <https://github.com/snapcore/snapd/pull/8055>
[12:18] <zyga> popey: you might know - nvidia experimental drivers for ubuntu?
[12:18] <zyga> popey: how do I get some
[12:19] <mup> PR snapd#8056 closed: client: move user-related things to their own files <Simple 😃> <Created by chipaca> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8056>
[12:20] <popey> Possibly https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa  zyga
[12:26] <zyga> popey: thank you! :)
[12:31] <Chipaca> hmm, shouldn't ubuntu-20.04 no longer be unstable?
[12:35] <mup> PR snapd#8057 closed: overlord/auth: add RemoveUserByName <Simple 😃> <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/8057>
[12:36] <mup> PR snapd#8059 opened: daemon: implement user removal <Created by chipaca> <https://github.com/snapcore/snapd/pull/8059>
[12:36]  * Chipaca goes out for a while
[13:03] <zyga> brb
[13:03] <zyga> need to make tea for Iza
[13:08] <mup> PR snapd#8060 opened: gadget: skip update when mounted filesystem content is identical <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/8060>
[13:11] <mborzecki> off to pick up the kids from school
[13:44] <mborzecki> re
[13:44] <zyga> o/
[14:16] <zyga> ijohnson: without the window reflection https://twitter.com/zygoon/status/1177917609783808001/photo/1
[14:32] <ijohnson> zyga: very nice, it's so cleanly organized
[14:32] <ijohnson> my desktop has cables running everywhere and looks very messy generally
[14:34] <Chipaca> zyga: https://i.redd.it/4c9udy915qyy.jpg
[14:35] <mborzecki> ijohnson: had to address a similar problem, otherwise my vega 56 would run really hot (still runs quite warm under load, but UV keeps the temps in check)
[14:35] <Chipaca> zyga: (via https://www.reddit.com/r/cablefail/comments/6ccwaq/looked_tidy_until_the_side_fell_off_in_the_wind/ )
[14:35] <zyga> Chipaca: just add fire :D
[14:36] <ijohnson> Chipaca: how did you get a picture of the inside of my desktop ?!?! :-)
[14:36] <zyga> ijohnson: the other PC is also pretty tidy but not to that level
[14:36] <Chipaca> ijohnson: i had to resverse the polarity on your webcam, and the rest was easy
[14:37] <Chipaca> reverse*
[14:37] <Chipaca> tachion flux*
[14:37] <ijohnson> Chipaca: ah I knew I shouldn't have installed that 1.21 gigawatts power generator on my webcam
[14:38] <zyga> https://twitter.com/zygoon/status/1222166974802878464 :)
[14:38] <zyga> ugly cables going everywhere
[14:41] <ijohnson> https://usercontent.irccloud-cdn.com/file/MVvajfu5/IMG_20200128_083935.jpg
[14:42] <ijohnson> zyga: do you have a noctua cpu cooler on that? looks very similar to mine
[14:42] <zyga> with that carpet you could get great results buy just having feet and a dust filter
[14:42] <zyga> yeah
[14:42] <zyga> it's a 10+ year old PC
[14:42] <zyga> with a new case
[14:42] <zyga> 1st gen core i7
[14:43] <zyga> for the xmas refresh I will get a mobo/ram/gpu and go with something newer
[14:43] <zyga> but keep the outside the same
[14:43] <ijohnson> yeah mine could do better, but it works well enough, just need to blow out the dust every once and a while
[14:44] <ijohnson> there's a big fan on the top and on the side panel that aren't in the picture that keep the whole system quite cool
[14:44] <zyga> yeah, cooling in PCs is really hard to get wrong :)
[14:44] <zyga> lots of space
[14:45] <ijohnson> I wanted to do a water cooled system but I was a bit lazy
[14:48] <ijohnson> pedronis: do you have a minute to chat about snap-bootstrap re-execing into the snapd snap on first-boot? I agree that it is complicated but I think it would be very good to have
[14:48] <ijohnson> pedronis: I tried to make it work quickly, the most difficult thing I ran into was picking which snapd snap to mount snap-bootstrap from
[14:49] <zyga> degville: you didn't tell me you are making the corsair link snap!
[14:51] <degville> zyga: aha, yeah. I use it personally. I think there may be a permission issue I've not sorted out with the one I've pushed though, so it's not made it to stable (I've not looked at it in a while).
[14:51] <degville> zyga: I use it set my own fan profile for silent operation :)
[14:56] <zyga> degville: what are you controlling with it?
[14:56] <zyga> degville: the PSU?
[14:58] <degville> zyga: HX750i PSU and H100i GT v2 CPU water cooler.
[14:58] <zyga> mmm
[14:58] <zyga> I have the fan controller only
[14:59] <zyga> actually, no fan and RGB controller
[14:59] <zyga> and fan controller has more rgb and temp
[15:01] <degville> zyga: it does use a poorly documented syntax. I don't set the RGB (my box is under the table), but the syntax for my cooling profile is --device 1 --fan channel=1,mode=6,temps=0:35:45:50:55:60,speeds=0:0:55:60:75:100.
[15:22] <pedronis> ijohnson: that's why it's hard, we would need to put a snapd copy into ubuntu-boot
[15:22] <pedronis> with all that entails in terms of state and checks
[15:22] <ijohnson> pedronis: oh also I just realized that in the fde case ubuntu-data is encrypted too
[15:22] <pedronis> ijohnson: yes, ubuntu-data is encrypted
[15:23] <ijohnson> pedronis: okay I see why you would want snapd in ubuntu-boot too
[15:23] <ijohnson> pedronis: maybe this is too much, but maybe for the snapd snap specifically we could have a "extract snapd assets" function which would copy things like snap-bootstrap to ubuntu-boot when a snapd snap is installed?
[15:24] <pedronis> ijohnson: how do we check that that binary is good
[15:24] <pedronis> we don't sign single binaries that way
[15:25] <pedronis> ijohnson: I understand the appeal, I don't see a way to keep the complexity cost vs benefit under control
[15:25] <ijohnson> pedronis: hmm I suppose currently snap-bootstrap is part of the initramfs which is part of the kernel.efi and so thus is measured, but if it was just ran directly then it wouldn't be measured
[15:27] <ijohnson> yeah I guess I don't see a way to easily do it then without possibly waiting to re-exec until after ubuntu-data is decrypted perhaps, but that kind of defeats the purpose
[15:32] <pedronis> ijohnson: it needs to get stable and stay relatively simple
[15:32] <ijohnson> pedronis: yes another thing I just thought about is perhaps for our tests, we could re-build the initramfs for spread tests that way we can test changes in the PR without needing to wait for a new kernel snap?
[15:33] <pedronis> ijohnson: that should be possible in some way
[15:33] <pedronis> mvo: ^  thoughts on on that?
[15:33] <pedronis> patching initramfs in tests
[15:33] <zyga> pedronis: initramfs may need to be signed - is that a problem?
[15:33]  * zyga needs a coffee
[15:34] <pedronis> zyga: well , we'll special certs that we use in tests
[15:34] <ijohnson> zyga: not a problem for tests
[15:34] <pedronis> so that's should be the main problem for tests
[15:34] <pedronis> shouldn't be
[15:34] <zyga> in that case it feels okay
[15:34] <zyga> just like rebuilding core/snapd snaps
[15:34] <ijohnson> well it would be a problem if we do try to test FDE via spread
[15:35] <ijohnson> but I think we have other, related problems with testing that anyways
[15:35] <pedronis> ijohnson: we actually discussed some to have some kind unpack/repack mechanism for it
[15:35] <pedronis> not sure there was progress on that
[15:35] <ijohnson> yes I remember mvo mentioning that in SU a few weeks/months ago
[15:37]  * zyga goes upstairs for a while
[15:37] <ijohnson> well I think it's a reasonable suggestion so I'm gonna prototype out building a kernel snap for uc20 in the spread test with the right initramfs
[15:41] <Chipaca> raaahhh
[15:41]  * Chipaca rages a little
[15:41] <Chipaca> why do we have an endpoint that returns things or lists of things depending on the phase of the moon
[15:42]  * Chipaca spends a PR to fix it
[15:49] <pedronis> Chipaca: which one?
[15:49] <Chipaca> pedronis: /v2/create-user
[15:49] <pedronis> I wasn't aware of that
[15:49] <Chipaca> yeah
[15:50] <Chipaca> pedronis: it's got two modes, create a user, or create all known users
[15:50] <pedronis> ah
[15:50] <Chipaca> pedronis: so i'm changing users to return a list always, and hacking create-users to preserve behaviour
[15:50] <pedronis> Chipaca: +1
[15:51] <Chipaca> i'll also change remove from returning true to returning nil as the result, for the same reason
[15:52] <Chipaca> pedronis: at some later point you might want to consider login also being an action on users
[16:15] <mvo> ijohnson, pedronis rebuilding the initramfs sounds appealing to me. if it's not too much hassle I would love to have this. we have snakeoil signing keys so we can even make this work in the tpm case (sorry for the slow reply, was in a ad-hoc meeting)
[16:17] <ijohnson> mvo: ack I'll work on this then, not entirely sure how to use the snake oil keys for tpm, but I can just do the non-fde case right now easily enough
[16:18] <mvo> ijohnson: yeah, one step at a time :)
[16:18] <ijohnson> :-)
[16:20] <mup> PR snapd#8061 opened: daemon: make users result more consistent <Created by chipaca> <https://github.com/snapcore/snapd/pull/8061>
[16:21] <Chipaca> much nicer now :)
[16:47] <mvo> zyga: the release/2.43 is a bit of a nightmare because of all the conflicts in "mount-ns" PER-SNAP-* files. any hints for me, it looks like this changed quite a bit between 2.43 and master and the revert of the /writable view that needs to be undone in the merge again makes this all a bit messy
[16:51] <mvo> zyga: nevermind, I will just revert manually
[16:53] <zyga> mvo: hmm
[16:53] <zyga> mvo: re
[16:54] <zyga> mvo: I'm confused - I merged the 2.43 revert
[16:54] <zyga> mvo: in master it's good and we should not bring that patch to master
[16:55] <mvo> zyga: yes, that's my point :) but we merge the release/* branches into master so that was a bit of pain
[16:55] <mvo> zyga: it's all fine again
[16:55] <zyga> resolve with --theirs or --ours or whatever was the option
[16:55] <zyga> (don't take changes to that directory)
[16:55] <mup> PR snapd#8062 opened: release: 2.43.2 <Created by mvo5> <https://github.com/snapcore/snapd/pull/8062>
[16:56] <zyga> or just cp it back from master :)
[16:56] <zyga> mvo: thank you for doing this; I'm sorry for the annoying merge
[16:56] <mvo> zyga: no worries
[16:56] <zyga> and that I didn't respond faster, I was having dinner
[16:56] <mvo> zyga: also no worries :)
[16:56] <zyga> there's a changelog conflict
[16:56] <mvo> zyga: oh, silly me
[16:57] <zyga> resolved
[16:57] <mvo> zyga: thank you!
[17:01] <Chipaca> current status of user work is https://github.com/snapcore/snapd/compare/master...chipaca:client-deluser … one more commit to go (in cmd/snap!) and it's Done(tm)
[17:01] <Chipaca> (if it all comes together without needing to go back and tweak things I'll be giving myself a putty medal)
[17:02] <Chipaca> now going to take a break
[17:02] <mvo> Chipaca: nice!
[17:03] <Chipaca> mvo: each of those commits becomes a PR, but I don't want to push them stacked (although i did do that for the last one)
[17:03] <Chipaca> actually, i lie, the first two commits are a PR, the others are a pr each
[17:03] <Chipaca> anyway, break time
[17:19] <Chipaca> travis is all kinds of sad
[17:20] <Chipaca> lots of 503s from the store
[17:20] <noise][> yeah, we are troubleshooting CDN issues
[17:20]  * Chipaca hugs noise][
[17:47] <Chipaca> hmm, hmm, hm
[17:47]  * Chipaca broke things
[17:47]  * Chipaca fixes things
[20:27] <mup> PR snapd#8062 closed: release: 2.43.2 <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/8062>
[20:29] <mup> PR snapcraft#2893 opened: [legacy] meta: include environment in hook wrappers <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/2893>
[20:29] <mup> PR snapcraft#2899 opened: ci: publish the CI built snap to the Snap Store <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2899>
[20:31] <Chipaca> chipaca@jan282010-194967:~$ sudo snap remove-user chipaca
[20:31] <Chipaca> error: cannot delete user "chipaca": userdel: user chipaca is currently used by process 4865
[20:31]  * Chipaca counts that as winning
[20:49] <zyga> Chipaca: woot
[20:53]  * zyga installs a round of mac updates
[22:48] <mup> PR snapd#8063 opened: Remove users [DRAFT] <Created by chipaca> <https://github.com/snapcore/snapd/pull/8063>


[13:43] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: Design and Web team summary – 15 July 2022 @ https://ubuntu.com//blog/design-and-web-team-summary-15-july-2022
[19:43] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Ubuntu Devs Fix Another Frustrating Firefox Snap Flaw: Native Messaging @ https://www.omgubuntu.co.uk/2022/07/ubuntu-devs-fix-another-frustrating-firefox-snap-flaw (by Joey Sneddon)


 We used to get bats flying into the house :-_)
[15:48] <czajkowski> jose: ping my mail to the LC was rejected
[17:32] <jose> czajkowski: pong, I didn't reject it
[17:34] <elfy> hi jose
[17:35] <jose> hello, elfy :)
[17:43] <dholbach> have a great rest of your day :)


[17:46] <brianflakes> Hi, I've noticed that the ubuntu IRC logs (irclogs.ubuntu.com) appear to be using incorrect string encoding. Special characters are completely mangled (e.g.   ¯\_(ツ)_/¯    ->     Â¯\_(ãƒ„)_/Â¯    ). Is this the right place to report this issue?
[18:37] <brianflakes> Nevermind, I've found a solution.


[16:23] <astraljava> scott-work: Did you want a meeting for the weekend? I'm already having one on Sunday at 1600 UTC. Before that I'll be traveling for a few hours. Everything outside of that works for me.
[16:23] <holstein> i need to schedule a pow-wow kind of thing
[16:24] <holstein> just a few of us
[16:24] <holstein> sundays are never going to work for me anymore i dont think
[16:25] <holstein> not that you guys need me for heavy lifting.. but i feel like 2 or 3 of us could knock out whatever it is that needs to happen with the site
[16:36] <astraljava> holstein: Of course we need you. The whole team should get together. We're just slacking off here without an aim now.
[16:39] <scott-work> astraljava: i'm good for whatever and i have forgotten that sunday is also father's day
[16:39] <scott-work> astraljava: holstein:  maybe sometime saturday?
[16:39] <scott-work> i'll make time tonight or any time on saturday
[16:42] <astraljava> scott-work: Saturday sounds great to me.
[16:44] <scott-work> astraljava: any particular time is good for you? around normal meeting time perhaps?
[16:45] <astraljava> scott-work: Can I get back to you on that? I should know in about an hour. :)
[16:45] <scott-work> sure
[17:00] <holstein> nah.. i cant do anything til maybe tuesday day, early
[18:33] <astraljava> ScottL: Well I'm not sure yet, so if you can suggest a few times tomorrow, let's pick one when I'm available. I need to go run a few errands, it seems.
[19:28] <len-dt> astraljava, I think I said it earlier, but I don't know if Scott got it. I won't be around most of the week end. I'll read the irc logs when I get back.
[19:31] <astraljava> len-dt: It's  fine, we can also have a meeting during the working week.
[19:32] <len-dt> if we can find a time when no one is sleeping/working ;-)
[19:36] <astraljava> Probably can't, but it's not much use either to have just me and Scott in one either. :)
[20:29] <astraljava> ScottL: So before 1500 UTC I'm really not available, sadly. But from then on, I should be.
[20:49] <len-dt> Hmm, still no new ISO.
[20:49] <astraljava> libav-extra isn't building.
[20:50] <len-dt> always something :)
[20:53] <astraljava> Sure is. :)
[21:09] <micahg> astraljava: yeah, I know :),it's on my list for this weekend
[21:17] <astraljava> micahg: That was just an explanation for Len why the ISO isn't building. :)
[21:18] <astraljava> I'm not pointing fingers or anything here. :)
[21:19] <micahg> there are a few reasons, that's on
[21:19] <micahg> *one


[01:58] <pleia2> ok, publishing time
[01:58] <pleia2> jose: around to help out?
[02:10] <pleia2> Welcome to the Ubuntu Weekly Newsletter, Issue 433 for the week August 31 - September 6, 2015 https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue433
[02:16] <pleia2> all done
[02:19] <jose> pleia2: sorry! just opened irc :(
[02:19] <pleia2> is ok :)
[16:14] <PaulW2U> pleia2: looks like to didn't finish the release process
[16:14] <PaulW2U> fixed main wiki page and current issue :)
[16:15] <pleia2> PaulW2U: thank you :)
[21:14] <pleia2> jose: btw, I'll be around all weekend, but will be offline on Monday the 14th, will you be around to publish?


[04:10] <ppisati> yo
[06:46] <smb> ppisati, no! (too early)
[07:49] <apw> yeah that is far toooo early
[07:50] <RAOF> But not too early for the BEES!
[07:55] <amitk> apw: any chance of this patch getting into trusty? https://bugs.freedesktop.org/show_bug.cgi?id=58378
[07:55] <ubot2> Freedesktop bug 58378 in Driver/nouveau "[NV86] Distorted graphics on NVIDIA GeForce 8400M G after upgrade the kernel to 3.5.x (and RHEL 6.5) or later" [Normal,Resolved: fixed]
[07:56] <amitk> apw: I've not been able to use the ubuntu dashboard (switched to i3) due to corruption issues since 12.04
[07:56] <amitk> the patch made it into 3.14-rc1
[07:59] <amitk> related ubuntu bug I filed (and ignored eventually): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1158689
[07:59] <ubot2> Launchpad bug 1158689 in linux (Ubuntu) "10de:0422 bringing up dash causes screen corruption on nouveau" [Medium,Incomplete]
[08:01] <amitk> or perhaps you look into graphics RAOF?
[08:02] <RAOF> If you need a kernel patch, you need apw!
[08:02] <apw> well there is little change for the release kernel, but ... for an sru i can have a look
[08:02] <RAOF> (Or someone else on the kernel team ☺)
[08:02] <apw> amitk, could you add the details to the bug as well
[08:02]  * smb wonders whether amitk remembers that deadline thing in general
[08:03] <amitk> apw: what details do you need? I'll link to the freedesktop bug
[08:03] <apw> amitk, that'll do i recon
[08:03] <amitk> smb: its done when its done ;) I can't promise deadlines for scheduler changes ;)
[08:04] <smb> amitk, Just wondering about a patch that you say made it into 3.14-rc1. Thought that was a bit ago.
[08:06] <amitk> smb: I haven't tracked this bug for a while since I don't use the ubuntu dashboard anymore. This came up again when I was testing out Trusty images over the weekend and I decided to look if it was fixed anywhere
[08:06] <amitk> smb: and I knew you were getting close to a release, but no I didn't know when exactly
[08:07] <amitk> :)
[08:07] <smb> amitk, So quick to forget. :)
[08:09] <amitk> smb: hardly forgotten, more like I don't upgrade my devbox on a 6-monthly cadence anymore ;)
[08:10] <amitk> apw: done linking against the upstream bug
[08:15] <apw> amitk, this is going to be a hard ask, it is rather large:
[08:15] <apw>  33 files changed, 500 insertions(+), 308 deletions(-)
[08:18] <amitk> apw: did you look at commit 4019aaa2b314a5be9886ae1db64ff8c6d3c060ed?
[08:19] <amitk> apw: I only see  17 files changed, 287 insertions(+), 35 deletions(-)
[08:19] <amitk> apw: or is there a dependency patch that I missed?
[08:20] <apw> amitk, yes, there are two, one of which 'rewrites most of the quirk init code'
[08:20] <amitk> apw: aah
[08:20] <apw> though even the 17 is pretty invasive
[08:20] <amitk> apw: true
[08:22] <amitk> apw: the patch itself is important for nouveau users that are currently seeing errors in their logs because the driver tries to use HW blocks that aren't even present
[08:23] <amitk> apw: I'll just switch to mainline kernels
[08:27] <apw> amitk, i'll spin a test kernel and you can test it, at least we will know for sure it is the fix
[08:27] <apw> i can then propose it and see what happens
[08:32] <amitk> apw: thanks
[09:15] <jpds> Can someone take a look at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1303419 ? I found a workaround but it'll be nice to have it as default.
[09:15] <ubot2> Launchpad bug 1303419 in linux (Ubuntu) "Brightness keys don't work on HP Elitebook Folio 1040 G1" [Undecided,Confirmed]
[09:18] <apw> jpds, will have a look
[09:35] <jpds> apw: Thanks.
[09:56] <apw> amitk, test kernels linked in the bug
[10:11] <amitk> apw: will test soon and get back, thanks again
[10:35] <apw> jpds, possible fix applied to test kernels, urls in the bug
[10:37] <jpds> apw: Testing...
[10:40] <apw> jpds, it is not 100% clear from the description which ids are covered, so it may not, we shall see
[10:41] <jpds> apw: It worked.
[10:45] <jpds> \o/
[10:45] <apw> jpds, ok ta, put that in the bug for me
[10:46] <jpds> apw: Already done.
[10:50] <apw> jpds, submitted to our list for consideration, shame you didn't get this in before freeze, but hey
[10:51] <jpds> apw: I got the laptop yesterday!
[10:51] <jpds> ;-)
[11:21] <apw> jpds, heh
[13:14] <apw> rtg, i just slammed head to fix a bug number in one of my patches
[13:16] <rtg> apw, ack
[13:16] <rtg> apw, did I mark the wrong bug fix committed then ?
[13:17] <apw> rtg, you did on my error, i fixed that up as well
[13:17] <rtg> cool
[13:17] <apw> rtg, you seem to have skipped over "rds: prevent dereference of a NULL device in rds_iw_laddr_check", i was going to apply that if you arn't doing it ... its a big heap of applying i don't want to duplicate :)
[13:18] <rtg> apw, I just haven't gotten to it yet, but go ahead.
[13:18] <apw> rtg, ack
[13:18] <rtg> I was busy updating kernels and such.
[13:18] <rtg> in fact, I'm about to reboot now.
[14:54] <brendand> is there a difference between checking for 'mem' in /sys/power/state vs using pm-is-supported --suspend?
[14:54] <brendand> i'm sure there is a difference, but i'd like to know what that is
[14:55] <brendand> if mem exists but pm-is-supported fails, does that mean suspend *can't* work on that system, or might it mean there's a bug?
[14:56] <brendand> similarly, if mem doesn't exist, might it be possible for pm-is-supported to succeed?
[15:10] <apw> brendand, it checks mem in /sys/power/state as one of the options, there are two others, so to answer your questions, yes and yes
[15:11] <apw> it is not clear how pm-is-supports --suspend could fail if mem is in /sys/power/state however
[15:14] <rtg> apw, when installing from the server ISO having a driver referenced in d-i/modules/nic-modules should be sufficient for network access, right ? For example, 'debian.master/d-i/modules/nic-modules:mlx4_en ?'.
[15:14] <apw> rtg, i believe so indeed
[15:15] <rtg> apw, and it _should_ get bundled into the initrd when the kernel is installed on the target disk.
[15:15] <apw> the criteria there are unrelated, networking is not normally seen as boot essential is it ?
[15:16] <rtg> apw, Infiniband might be. Guess I'd better find out.
[15:16] <apw> nor would it normally be, given you open the real disk, and find the drivers there
[15:16] <apw> yeah ... that
[15:16] <smb> apw, netboot?
[15:16] <brendand> oh dear, if pm-suspend can't do real hybrid sleep then it cheats :/
[15:17] <apw> smb, that has a different initrd
[15:17] <apw> brendand, "oh dear" ?
[15:17] <smb> apw, hopefully one that considers networking as boot essential
[15:17] <apw> hopefully nideed
[15:18] <brendand> apw, from the point of view of someone testing that hybrid sleep works, yes
[15:19] <apw> smb, i just updated "clark" and rebooted, on startup i can now seem my old VMs, good, but they do not start
[15:19] <apw> Error starting domain: internal error: libxenlight failed to create new domain 'grovel-r64'
[15:20] <smb> apw, Would be nice to have some more useful messages. Unfortunately those hide usually in /var/log/libvirt/libxl/... on the host
[15:21] <rtg> tseliot, have you heard any howling about 4K monitor support getting broken with this last nVidia-331 update ?
[15:21] <apw> smb, yeah that is crap, it may be an old VM with "pre VG rename" paths in it
[15:22] <bjf> rtg, i don't think it's 4k support. i think nvidia is borked
[15:22] <bjf> rtg, i'm guessing you are in low-res mode
[15:22] <smb> apw, True. Well it could be anything. Sadly the error reporting through virt-manager is... suboptimal
[15:22] <bjf> rtg, and your jumbo-tron doesn't have a low-res support
[15:22] <tseliot> rtg: the driver we have in Ubuntu is not the latest from Nvidia. I haven't tested it with 4K but 2560x1440 works fine here
[15:22] <rtg> bjf, oh, you mean altogether borked ? I'm in "no mode" black screen
[15:23] <apw> rtg, is your monitor "black" or "off", mine seems to be off
[15:23] <apw> smb, ok this was "my fault"
[15:23] <rtg> apw, black
[15:23] <apw> they seem converted just fine
[15:23] <bjf> rtg, i'm in low-res on a "normal" monitor which might be different on the jumbo-tron
[15:23] <tseliot> rtg: in the latest update I only added support for Linux 3.14
[15:23] <smb> apw, Uh, what kept them from starting then?
[15:24] <apw> somewhen back in the mists of time (read more than 2 weeks back) i renamed my datavg to clarkvg
[15:24] <apw> and this had the old, you cannot have inserted the wrongo path
[15:25] <smb> apw, Ah! Ok, makes some sense then. Just not the nicest thing on earth when it comes to errors. As much as a python stackrace can ever be called nice
[15:26] <apw> ok this was a raring machine, that makes sense being as it isn't supported any mroe, /me tries an s instance
[15:26] <smb> apw, No the convertion should not change anything there
[15:26] <apw> smb, ok my S which i had fixed previously appears correctly and starts correctly.  i'd say that is success, got a bug # i can report that testing in ?
[15:29] <smb> apw, No, I probably should open one... and maybe ... hm... just occured to me that re-creating those VMs that are in the old path but not the new may be annoyingly bringing back things on every upgrade
[15:30] <apw> smb, you have to mark that you have done it and do it just once indeed
[15:30] <smb> apw, except maybe when adding a '--force'
[15:31] <apw> smb, or rename the previous ones to .old sort of thing
[15:31] <apw> so you can rename them back if you need to but only process the ones not .old
[15:32] <smb> apw, I would be careful there. As I cannot be 100% sure what the old xend does with those.
[15:34] <apw> smb, move them from like /foo/bar/machines/* to /foo/bar/machines.old/*
[15:36] <smb> apw, If I do that, and someone switches back to the old toolstack, the domains are gone there.
[15:38] <apw> smb, yes but i may have changed them anyhow, so you need to convert them back
[15:38] <apw> smb, which is why i think we should convert them, pop somethign up to tell you that, so you arn't supprised they are gone when you downgrade
[15:39] <apw> smb, but overall they work well so that at least is good
[15:39] <smb> apw, it already tells you about the conversion in the log. And I rather won't go on a reverse. Thats deprecated anyhow
[15:40] <smb> And adds too much complexity
[15:40] <apw> smb, right that is why i don't think we care that they are gone if you go back, that can be documented on something the log points to perhaps
[15:40] <apw> like a wiki for downgraders
[15:40] <apw> or something
[15:41] <apw> smb, though your bug should have a release notes task so we can warn people this is going to happen to them in advance as well
[15:42] <smb> apw, Hm, I am rather adding something preventing a second convertion. Feels more straight forward
[15:44] <apw> we should still release note the conversion so people can think about the risks, as they will be higher than normal for xen use, which is almost noone of course
[15:46] <smb> apw, Agreed. I think that bug I am reporting right now can also get a release-notes task
[15:51] <apw> smb, yeah agree
[15:52] <smb> apw, bug 1303886 created
[15:52] <ubot2> Launchpad bug 1303886 in xen (Ubuntu) "[Trusty] Xend managed domains disappear after upgrade" [Undecided,New] https://launchpad.net/bugs/1303886
[15:54] <smb> apw, Oh one thing that prevents the renaming. Unfortunately I have to take care about xen only and xen with libvirt and I would not know in the postinst which case
[15:55] <apw> smb, i've added the release notes task
[15:55] <smb> apw, ok
[15:55] <apw> smb, if you can only "do it" once ever that seems fine, and safer
[16:00]  * cking drops in to listen to the canonical "plan" via icecast..
[16:00] <cking> oops
[16:01] <smb> cking, New level of annoying elevator musak
[16:01] <cking> arggh
[16:34] <amitk> apw: bugfix confirmed and commented on bug
[16:34] <amitk> apw: thanks
[18:45] <bjf> zequence, BenC new SRU cycle just started
[18:58] <zequence> bjf: Yep. I'm all done except for testing.


[00:11] <BUGabundo> kklimonda: reboot?
[00:11] <kklimonda> nah, just lost connection..
[10:14] <markgsaye> jcastro: I'd like add my name as help contact into the channel topic, but do not have op rights - can you help?
[10:19] <markgsaye> jussi01: can you help? ^^
[11:18] <jussi01> markgsaye: who are you?
[11:18] <markgsaye> Hi jussi01: I am a Senior Software Developer for Canonical
[11:19] <jussi01> markgsaye: can you somehow give me some sort of verification for that?
[11:19] <rodrigo_> jussi01: I can certify he is what he says, if that serves :)
[11:20] <markgsaye> jussi01: my LP profile is at https://launchpad.net/~markgsaye - does that help?
[11:20] <jussi01> markgsaye: 1 moment please
[11:28] <SteveA> sladen: hi
[11:28] <SteveA> sladen: we were just talking about oauth
[11:28] <SteveA> sladen: and I pointed you at http://oauth.net
[11:28] <SteveA> sladen: aquarius here is very familiar with how the ubuntu one systems use oauth, and how the dbus service works
[11:28] <aquarius> hey
[11:28] <sladen> SteveA: okay
[11:28] <aquarius> hey sladen
[11:29] <SteveA> and I happen to know he's got 15 mins spare to give a quick overview ;-)
[11:29] <sladen> aquarius: is that Aq under a more verbose name?
[11:29] <sladen> SteveA: fantastic, ta
[11:29] <aquarius> sladen: it is indeed :)
[11:30] <sladen> aquarius: can you sum up in two-three lines what actually happens.  Something is running, that exposes com.ubuntuone.Authenication, which is it?
[11:31] <aquarius> sladen: /usr/bin/ubuntuone-client-applet  exposes the com.ubuntuone.Authentication D-Bus interface
[11:31] <sladen> can (bearing in mind that I have not accepted the T&C, so can't run this), what component(s) pops up the password box
[11:32] <sladen> aquarius: so, that means that the gnome-applet is _required_.  It's not possible to use just syncdaemon and it's u1sdsdsdtool
[11:33] <aquarius> ubuntuone-client-applet pops up the password box. that component handles the OAuth exchange for you, fetching an access token (which you authorise in the web browser). ubuntuone-client-applet then stores that access token in the gnome-keyring, and that storage action is what requires the password.
[11:34] <aquarius> sladen: If you want to, you can fetch an authorised access token and store it in the gnome-keyring yourself; if that happens, then the d-bus interface is never called
[11:34] <aquarius> (because the syncdaemon looks for an access token and successfully finds it)
[11:35] <sladen> aquarius: okay, I'd like to document the manual method, as that is likely to (very accurate) show  the procedure
[11:35] <aquarius> sladen: but I confess I've not actually *tried* that; I'm just reasoning from how it should work.
[11:36] <sladen> aquarius: but the basic premise is that the remote authenication (to get the token) is all done via the browser and a standard login to launchpad?
[11:36] <aquarius> sladen: yes
[11:38] <aquarius> sladen: that's the stock OAuth procedure; the way OAuth works is 1. program makes a request to get a request-token; 2. program pops up the user's browser to authenticate that request-token; 3. tell the program you've done it; 4. program uses the (now authenticated) request-token to get an access-token; 5. program stores the access-token and can from then on use it to access resources without having to ask the user
[11:38] <aquarius> sladen: (possibly you already know this!)
[11:39] <sladen> aquarius: no, oauth is so recent that I haven't had to use it in anger for any projects yet
[11:40] <jamesh> aquarius: the bits that the OAuth spec doesn't define is the actual URLs and supported signing methods.  I suppose we should publish them somewhere.
[11:40] <sladen> aquarius: how does -applet get the actual return code (token) from the browser?
[11:41] <jamesh> sladen: it makes a call to the OAuth "access token URL"
[11:41] <jamesh> passing in the request token
[11:42] <aquarius> sladen: it doesn't. The browser just authorises the request token. The applet then calls the access-token url and says "you authorised this request-token; give me a corresponding access-token, please"
[11:42] <aquarius> jamesh: they should be published, indeed; it looks like the docs that sladen's putting together may do that quite nicely though :-)
[11:43] <jamesh> sladen: think of the request token as a "session identifier" for the authentication process.  While it has a similar name to the access token, it has quite a different purpose
[11:43] <sladen> so there's a new session token (access token) each time the user logs in
[11:43] <sladen> it's not setup once when the Share is shared and kept
[11:44] <sladen> so the username and password get saved only in the Firefox keyring (normal launchpad login)
[11:44] <jamesh> sladen: the access token is stored in the keyring long term
[11:44] <sladen> and the token, that get stashed in the gnome-keyring is saved long-term, but is only useable for this session
[11:44] <jamesh> (at least for our client)
[11:45] <sladen> or should that this s/this session/this share/
[11:45] <jamesh> sladen: the request token is a session identifier for the user authentication/authorisation process
[11:45] <jamesh> the access token that results from that process can be used long term
[11:46] <aquarius> sladen: the access token that gets stashed in the keyring -- think of it like a login cookie for a website, so you don't have to log in every time you go back there.
[11:46] <sladen> who exchanges the session identifier for the long-term access token?  Is that syncdaemon, or -applet/
[11:47] <jamesh> sladen: the applet -- it stuffs the access token in the keyring and then notifies anyone interested that it is available
[11:47] <sladen> so the -applet is effectively doing write-through cacheing.  The first time (it's empty) it fires up the browser and saves the result, and returns it
[11:48] <sladen> and thereafter, -applet returns it straight away (to syncdaemon)
[11:49] <sladen> syncdaemon then includes this identifier as part as every single u1storage-based connection setup to the ubuntuonestoragefsapiserver
[11:51] <aquarius> I'm not sure whether syncdaemon calls the d-bus api to get the token. or whether syncdaemon actually looks in the keyring itself. jamesh?
[11:53] <jamesh> sladen: syncdaemon checks the keyring for the access token first.  If no token is found, it asks the applet to acquire a token via DBus
[11:53] <jamesh> sladen: there is a fairly loose coupling between the two components
[11:54] <jamesh> that's how I remember it working ...
[12:08] <facundobatista> Hi all
[12:11] <CardinalFang> hiya, facundo.
[12:18] <jdobrien> hi facundo
[12:20] <facundobatista> Hi CardinalFang, jdobrien
[16:39] <jblount> Hiya people! Anyone have access to a Windows Xp vm or similar that can test logging in with Opera 9.64 for me?
[16:44] <facundobatista> jblount, I am
[16:44] <facundobatista> jblount, I need to install Opera, though
[16:47] <jblount> facundobatista: Thanks! If you could install the current build (not the 10.x beta recently announced) and try to log in, I just need to confirm if someone can get through our LP SSO :)
[16:47] <facundobatista> god, how many steps to install something in Windows!
[16:47] <jblount> heh, 1241251
[16:58] <facundobatista> jblount, it just work
[16:59] <facundobatista> jblount, I tried it not being logged in Launchpad, *and* already being logged in
[17:39] <facundobatista> jblount, I also commmented the bug about what you asked
[17:56] <toros> hi
[18:02] <jblount> facundobatista: gracias
[18:03] <facundobatista> jblount, de nada, :)
[19:46] <days_of_ruin_> I dragged a tarball into my Ubunto One/My Files directory
[19:46] <days_of_ruin_> but it doesn't upload it.
[19:49] <days_of_ruin_> icon is rotating
[19:50] <days_of_ruin_> but system monitor is showing that its not uploading.
[19:53] <facundobatista> days_of_ruin_, what the log says?
[19:54] <days_of_ruin_> where is the log?
[19:54] <facundobatista> days_of_ruin_, ~/.cache/ubuntuone/syncdaemon.log
[19:55] <days_of_ruin_> 2009-06-09 13:50:37,395 - ubuntuone.SyncDaemon - WARNING - Another instance     is running
[19:55] <days_of_ruin_> thats there because I tried to start another.
[19:59] <facundobatista> days_of_ruin_, try to remove all instances from memory and try again
[20:11] <days_of_ruin_> still not working
[20:16] <toros> I have problems with the Ubuntu One client to
[20:17] <toros> and a guy on IRC had the same problem this afternoon too
[20:18] <facundobatista> days_of_ruin_, log?
[20:19] <Chipaca> days_of_ruin_: something is wrong with the service right now
[20:19] <days_of_ruin_> its not just me?
[20:19] <days_of_ruin_> its happening to everyone?
[20:20] <Chipaca> days_of_ruin_: correct
[20:20] <Chipaca> days_of_ruin_: or it might be; still diagnosing the problem
[20:20] <toros> ohh, an upgrade for the ubuntu one client
[20:40] <Chipaca> days_of_ruin_: any change?
[20:41] <days_of_ruin_> I removed my computer from my ubuntu one account...
[20:41] <days_of_ruin_> to see if that would help. How do I get it back?
[20:42] <days_of_ruin_> The page isn't poppin up in my browser:|
[20:42] <facundobatista> days_of_ruin_, through the web page, I guess
[20:43] <dobey> days_of_ruin_: you'll need to delete the token from your local computer in Accessories->Passwords and Encryption Keys, under the Passwords tab
[20:44] <jblount> days_of_ruin_: ^^ and quit / reopen the applet. When it sees the token gone, it will help you setup a new one :)
[21:04] <days_of_ruin_> When I try to reopen it it never shows up.
[21:05] <facundobatista> days_of_ruin_, reopen what?
[21:06] <days_of_ruin_> when I click on Applications>Internet>Ubuntu One
[21:06] <days_of_ruin_> or run it from a terminal
[21:06] <days_of_ruin_> nothing happens
[21:07] <facundobatista> days_of_ruin_, did you follow the dobey and jblount instructions to get there?
[21:10] <toros> re
[21:10] <toros> it seems ubuntu one is working again \o/
[21:10] <toros> do we know what was the problem?
[21:12] <facundobatista> toros, a frozen database connection that never timed out
[21:12] <facundobatista> toros, we're trying to see why that happened, but now it should work ok
[21:12] <toros> thanks for the info
[21:13] <toros> did somebody test the unshare feature? does it work?
[21:17] <toros> I rejected a directory shared with me - now I don't see it in the web interface, but according to u1sdtool it's still shared
[21:26] <days_of_ruin_> yes I followed the instructions. But it worked just now :)
[21:30] <days_of_ruin_> everything is working now
[21:32] <facundobatista> days_of_ruin_, great!
[21:32] <days_of_ruin_> thanks for the help.
[22:41] <days_of_ruin_> hrm. it seems to be happening again.
[22:43] <Chipaca> days_of_ruin_: let me see...
[22:43] <Chipaca> days_of_ruin_: nope, it's working here
[22:47] <days_of_ruin_> I disconnected and reconnected and now its just "idle" and doesn't notice any new files.
[22:47] <medeshago> how can I change the ubuntuone folder?
[22:53] <Chipaca> days_of_ruin_: hmmm
[22:53] <Chipaca> days_of_ruin_: and there are new files?
[22:53] <Chipaca> medeshago: not yet, sorry
[22:53] <medeshago> Chipaca: thanks
[22:56] <Chipaca> days_of_ruin_: if you open a terminal and do "killall ubuntuone-syncdaemon; ubuntuone-syncdaemon --debug" you should get to "see" it working
[22:58] <days_of_ruin_> Chipaca: I ran that, what am i supposed to see.
[22:58] <Chipaca> days_of_ruin_: copious output :)
[22:59] <Chipaca> days_of_ruin_: you should see it "noticing" new files, for one
[23:01] <days_of_ruin_> I right-clicked the icon now and connected it. Now its working again.
[23:02] <Chipaca> ah :)
[23:57] <Ng> woo, working client in karmic \o/
[23:58] <Ng> the spinny applet thing is spinning reeeeally fast :o


[19:07] <pavlushka> zaki: o/
[19:17] <zaki> hey pavlushka
[19:18] <pavlushka> zaki: how are you?
[19:18] <zaki> pavlushka, I'm good
[19:18] <zaki> how are you ?
[19:23] <pavlushka> I was exhausted testing coreboot for my desktop, but am recharged now and will provide a meaningful result/output InshaAllah
[19:25] <pavlushka> zaki: you can read my comments on patch 60 here , https://review.coreboot.org/c/coreboot/+/34603/60
[19:25] <zaki> is it complete now?
[19:26] <pavlushka> zaki: and the summery, https://pastebin.com/7VKvLM7j, will test again, I can boot into CLI mode using coreboot. Tha's the progress so far.
[19:26] <u-la-la> [ Coreboot test cases. - Pastebin.com ] - pastebin.com
[19:26] <zaki> pavlushka, great
[19:27] <pavlushka> zaki: you haven't read any of that I guess :|
[19:27] <zaki> pavlushka, I'm reading
[19:29] <zaki> pavlushka, upload some screenshot
[19:32] <pavlushka> zaki: https://imgur.com/a/QZj6EHJ
[19:32] <u-la-la> [ Coreboot on ASUS h110m machine - Album on Imgur ] - imgur.com
[19:32] <pavlushka> https://i.imgur.com/VyQ7PrI.jpg
[19:33] <pavlushka> https://imgur.com/VyQ7PrI
[19:33] <u-la-la> [ Tianocore_with_GOP - Imgur ] - imgur.com
[19:33] <zaki> pavlushka, there was some gui while booting your lenovo
[19:33] <zaki> oh okay
[20:15] <pavlushka> zaki: night night


[00:43] <vychune> linuxman410
[01:33] <chris4585> wrst, yes
[01:33] <chris4585> its not default though


[14:16] <hiatus> I was looking in /user/share/themes and came across ambiance and radiance and noticed they were png's. I thought svg was preferred for icons since resizing