[16:57] <digirak> hey
[16:57] <maco> hello
[16:58] <digirak> I wanted to work on the gimp bugs
[16:58] <digirak> i guess i could help with some triaging
[16:58] <maco> gimp has their own irc server:  irc.gimp.net
[16:59] <digirak> na #ubuntu-bugs told me u guys had adopted the gimp bugs for bug hug day
[16:59] <maco> oh...thatd be bcurtiswx
[16:59] <maco> im a kde person ;-)
[16:59] <digirak> maco: hahaah ;)
[16:59] <digirak> hey bcurtiswx: would you be looking for some bug help?
[17:00] <bcurtiswx> digirak, i'm cooking lunch, but I can help you in a little while.  Meanwhile pick a GIMP bug you want to work on
[17:00] <bcurtiswx> bbs
[17:00] <digirak> bcurtiswx: sounds good
[17:14] <bcurtiswx> digirak, which bug have you chose?
[17:14] <bcurtiswx> haha
[17:14]  * bcurtiswx runs while he can
[17:28] <digirak> I guess id do that large file-gimp crashj
[17:28] <digirak> i managed to reproduce that
[17:32] <bcurtiswx> whats the bug #?
[17:32] <digirak> Bug #408317
[17:38] <bcurtiswx> digirak, OK, so the reason it's incomplete is that there's still information required in order to help the devs fix it.  Do you see that this is?
[17:39] <digirak> yes
[17:39] <digirak> what kind of info are u looking at?
[17:39] <bcurtiswx> what does pedro request?
[17:40] <digirak> oh ok u want a backtrace?
[17:40] <bcurtiswx> well, i don't.. bug the bug report does
[17:40] <digirak> ok...
[17:40] <bcurtiswx> since you can reproduce the issue, you can provide this information
[17:40] <digirak> sounds good


[01:34] <sinak> hello. I have installed upstart in debian using apt-get
[01:34] <sinak> the pc didn't boot any faster
[01:34] <sinak> do I have to do an extra configuration?
[02:02] <Md> the debian upstart package is obsolete and more or less useless
[02:02] <Md> installing it will not provide any real benefit
[02:03] <sinak> I understood that
[02:03] <sinak> is there any way to configure it to boot faster?
[02:04] <Md> reinstall sysvinit and enable parallel boot
[02:04] <sinak> mm ok
[02:09]  * sinak bbz
[03:20] <mbiebl> Md: what do you mean by obsolete?
[03:20] <mbiebl> It's still using the sysv compat layer, yes
[03:21] <mbiebl> but I wouldn't call upstart obsolete because of this ;-)
[22:18] <unbuntucanuck> I have 8.04 Hardy Heron unbuntu and can't find any docs on upstart. I'm told i have it in the distro - what's up?
[22:24] <ion_> /usr/share/doc/upstart/README.Debian.gz, http://upstart.ubuntu.com/ and the comments in the source.
[22:25] <unbuntucanuck> cheers ion, I'm check the docs out!
[22:25] <ion_> The state of documentation could be better. :-)


[14:57] <micahg> could we please get a bot reload in #ubuntu-mozillateam (ubot4)?
[14:58] <jpds> micahg: How do you mean?
[14:58] <micahg> jpds: oh, I thought it was just our channel, fta tells me ubot4 is broke everywhere
[15:04] <micahg> jpds: thanks
[15:05] <micahg> jpds: oops, still broke
[15:14] <micahg> bug 584959
[15:14] <micahg> ah, works now :)
[15:15] <micahg> oh, wait, that's probably ubot2
[15:15] <micahg> ubot2: are you there?
[15:15] <ubot2> Factoid 'are you there?' not found
[15:15] <micahg> ubot4: are you there?
[15:15] <ubot4> Factoid 'are you there?' not found
[15:16] <micahg> jpds: in #ubuntu-mozillateam and #ubuntu-packaging ubot4 isn't responding to bugs
[15:20] <jpds> micahg: Now it's working.
[15:34] <micahg> jpds: thanks :)
[16:38] <jussi> jpds: we should be encouraging people to join #ubuntu-bots-team for bot issues.
[16:39] <jpds> jussi: Oh, sorry; forgot.
[16:39] <jussi> jpds: no probs. its a small thing I know, just helps get the word out when people see it happening.
[19:56] <micahg> ubot4 is broke again :)
[19:56] <ubot4> micahg: Error: I am only a bot, please don't think I'm intelligent :)
[22:06] <roxy1> hi


[01:18] <charlie-tca> hmm, can I upgrade Xubuntu to Natty already?
[01:40] <kklimonda> charlie-tca: yeah, but you have to edit sources.list manually
[01:41] <charlie-tca> Gotta try. I have never tried it with xubuntu before alpha1
[03:42] <FFForever> I am toying with 11.04 on my dev machine. Is it possible to hook into the device event handler to call a bash script when an external usb drive with a udev id xxxxxxx is plugged in?
[12:17] <ikonia> arvut: /topic
[12:17] <ikonia> p[s
[12:17] <ikonia> oops
[13:43] <patdk-wk> whoa, talking :)
[17:41] <Volkodav> anybody has sopcast working in maverick ?
[17:46] <IdleOne> Volkodav: maverick support in #ubuntu
[20:31] <yofel> nice to be back again :D
[20:56] <BUGabundo> evening
[21:14] <charlie-tca> Good evening.
[21:14] <BUGabundo> hey charlie-tca
[21:15] <BUGabundo> FYI I have a friend running xubuntu natty
[21:15] <charlie-tca> and it works this early in the cycle?
[21:18] <BUGabundo> I guess
[21:18] <BUGabundo> he upgraded yesterday


[18:18] <willwh> hey guys :)
[18:18] <willwh> anyone alive? could use a hand to talk something through :)
[18:18] <willwh> I have a VPS that is running iptables
[18:19] <willwh> I think my host are idiots and something is misconfigured
[18:19] <willwh> let me save my iptables rules and I'll link em, 2min
[18:21] <willwh> http://willwh.com/iptables.txt
[18:21] <willwh> so my port 80 traffic == np
[18:21] <willwh> the app I have bound to 3000 is not accessable remotely
[18:21] <willwh> I can hit it like so; lynx localhost:3000
[18:21] <willwh> ont he host
[18:21] <willwh> can't connect externally
[18:22] <willwh> iptables looks good to me
[18:22] <willwh> and I think my host has something misconfigured
[18:22] <willwh> they want me to pay them to investigate further (hah)
[18:22] <willwh> but they are slow / poor in response
[18:22] <willwh> so
[18:27] <DarwinSurvivor> willwh: do you have a copy of the actual iptables rules file (or script/etc)?
[18:28] <willwh> DarwinSurvivor: I think I figured it out
[18:28] <willwh> my host are just being cheeky bastards
[18:28] <DarwinSurvivor> willwh: double firewalled you?
[18:31] <willwh> no
[18:31] <willwh> they're telling me "INPUT" chain
[18:31] <willwh> if you look at that iptables output
[18:31] <willwh> it's PUB_IN
[18:31] <DarwinSurvivor> I would recommend moving your ESTABLISHED line to the top, then blocking all non-syn tcp packets immediately after. that will drastically cut down on the amount of illegitimate traffic that hits your server
[18:31] <willwh> that rules should be added to
[18:31] <willwh> ah
[18:32] <willwh> DarwinSurvivor: I'm a little confused still though
[18:32] <willwh> I am not sure how I ended up with so many chains
[18:33] <willwh> and the fact that adding stuff to INPUT was useless
[18:33] <willwh> I'm not making a lot of sense, hag
[18:33] <willwh> hah*
[18:33] <willwh> but trying to understand how a chain is applied
[18:33] <DarwinSurvivor> line 14 is useless as line 13 will prevent ANYTHING from getting to it
[18:34] <willwh> yes
[18:34] <willwh> but like I say - the INPUT chain rules seem to have almost no effect
[18:34] <willwh> it's all the PUB_IN
[18:34] <DarwinSurvivor> and you don't need a drop rule at the end of INPUT if your default policy is to drop
[18:34] <DarwinSurvivor> hmm
[18:34] <DarwinSurvivor> yeah, i see that
[18:34] <willwh> I don't understand the difference
[18:34] <willwh> or how they relate at all
[18:35] <DarwinSurvivor> do you know which network adapter is your external?
[18:35] <DarwinSurvivor> if it's anything but eth0, then 3 will not trigger and it will get blocked in PUB_IN
[18:35] <DarwinSurvivor> *rule 3
[18:35] <willwh> you mean rule 3 in INPUT?
[18:36] <DarwinSurvivor> yes
[18:36] <willwh> ahhh
[18:36] <DarwinSurvivor> if your external connections are not coming in through eth0, that rule will not work
[18:36] <willwh> right
[18:36] <willwh> eurka
[18:36] <willwh> I understand
[18:36] <willwh> :)
[18:36] <DarwinSurvivor> ifconfig should tell you which ones you have
[18:36] <willwh> yup
[18:36] <willwh> thanks mate
[18:36] <DarwinSurvivor> no problem
[18:36] <willwh> lo and 2 virtual interfaces
[18:36] <willwh> so that kinda explains that ;]
[18:36] <DarwinSurvivor> bingo
[18:38] <DarwinSurvivor> when I saw all the FOO+, I figured you had a non-standard setup
[18:41] <willwh> DarwinSurvivor> I would recommend moving your ESTABLISHED line to the top, then blocking all non-syn tcp packets immediately after. that will drastically cut down on the amount of illegitimate traffic that hits your server
[18:41] <willwh> how do I do that exactly? :)
[18:43] <DarwinSurvivor> do you have direct access to the iptables rules file?
[18:43] <willwh> DarwinSurvivor: yeah I have root on the box
[18:44] <DarwinSurvivor> ok
[18:44] <willwh> gotta take a call, back asap
[18:44] <DarwinSurvivor> first move rule 5 to right after rule 1 (so that banned ips are blocked even if they had already connected)
[18:44] <DarwinSurvivor> k
[18:46] <DarwinSurvivor> brb
[18:53] <DarwinSurvivor> back
[19:23] <willwh> DarwinSurvivor: yo
[19:23] <willwh> is it possible to move rules?
[19:23] <willwh> like #2 -> #7
[19:25] <DarwinSurvivor> willwh: what do you use to set the firwall rules? (iptables.rules file, bash script, web interface, etc)?
[19:26] <willwh> just command line
[19:26] <willwh> and services iptables save
[19:26] <willwh> ther eis a web interface
[19:26] <willwh> too
[19:27] <DarwinSurvivor> what distribution?
[19:27] <willwh> debian :D
[19:28] <willwh> I don't really like the route ubuntu has gone recently :(
[19:28] <DarwinSurvivor> see if there is an iptables.rules (or similar) file in /etc/
[19:29] <DarwinSurvivor> there may be 2 files (iptables.up.rules and iptables.down.rules)
[19:29] <willwh> /etc/iptables: rules & iptables.conf
[19:30] <DarwinSurvivor> is rules a file or directory?
[19:30] <willwh> file
[19:30] <willwh> and it's generated by iptables --save
[19:30] <willwh> sorry
[19:30] <willwh> iptables-save
[19:30] <willwh> argh - another call
[19:30] <willwh> :(
[19:31] <DarwinSurvivor> yes, that is a saved copy of all the iptables rules (which can be loaded with iptables-restore)
[19:31] <DarwinSurvivor> an easy way to modify the running firewall is to edit that file, then run iptables-restore again
[19:35] <DarwinSurvivor> if you don't want to mess with the system files, you could also use iptables-restore to create a new copy, then modify that
[19:41] <DarwinSurvivor> One hint: add an ACCEPT for your personal IP address at the very beginning of the INPUT chain so that you can always log back in if you mess up the firewall!
[19:55] <willwh> roger
[19:55] <willwh> so one more question DarwinSurvivor
[19:55] <willwh> it seems that I don't need all these chains
[19:55] <willwh> I should just use an INPUT / OUTPUT / FORWARD?
[20:00] <willwh> got it all ironed out
[20:00] <willwh> I really appreciate the advice, thanks very much DarwinSurvivor :)
[20:09] <DarwinSurvivor> no problem
[20:11] <DarwinSurvivor> using chains can simplify some things (like with fail2ban), but can also over-complicate things if you don't understand what they are doing
[22:55] <willwh> key Kip :D
[22:55] <willwh> how's it going man?!
[22:55] <willwh> DarwinSurvivor: you still around?
[22:55] <willwh> got an odd one
[22:55] <willwh> this works: ssh -i .ssh/ec2netro.pem<EMAIL_ADDRESS>[22:55] <willwh> this in my .ssh/config - does not
[22:56] <willwh> Host ec2netro
[22:56] <willwh> Hostname ec2-23-21-37-13.compute-1.amazonaws.com
[22:56] <willwh> User ubuntu
[22:56] <willwh> PreferredAuthentications publickey
[22:56] <willwh> IdentityFile "/home/willwh/.shh/ec2netro.pem"
[22:56] <willwh> which is VERRRY strange
[22:56] <willwh> I don't understand :[


 Thanks in advance. :)
[16:34] <holstein> !password
[16:34] <holstein> you can just open a termina and use passwd command
[16:34] <holstein> terminal*
[16:34] <sydney> oops,I mean User name. ;)
[16:34] <holstein> i wouldnt
[16:35] <holstein> http://www.ubuntututorials.com/change-username-ubuntu-12-04/ should help
[16:37] <sydney> Thanks, Also Do any of you know how to disable the password on resume from standby function?
[16:38] <holstein> i found it in the power menu, iirc
[16:59] <sydney> How do I get to the Power menu? I am new to lxde and having a little bit more truble finding stuff. :) Also I installed LXDE from Ubuntu Software Center,so I am running ubuntu with the LXDE skin.
[17:08] <Phil42> (curious)  what is the power menu?
[17:09] <sydney> What is it,And Where is it?
[17:16] <sydney>  How do I get to the "Power menu"? I am new to lxde and having a little bit more truble finding stuff. :) Also I installed LXDE from Ubuntu Software Center,so I am running ubuntu with the LXDE skin.
[17:18] <holstein> sydney: usually, what i do when going to a new operating system is.. i'll load up the live installer cd, and not install, but run it live.. then i'll check out *everything* and see what does what
[17:19] <holstein> sydney: i typically find those settings in either the screensaver, or the power settings
[17:19] <sydney> I understand that,and I did that,but It is a little bit different than the cd,and I dont rember where it was in the cd.
[17:19] <holstein> the power settings being, what happens with you close the lid and whatnot.. power related
[17:20] <holstein> sydney: the live CD will be an analog to the stock installed system
[17:20] <sydney> I did look in the screensaver settings,and found nothing.
[17:20] <holstein> the live CD is handy, becuase you wont break anything permenantly
[17:22] <Phil42> oh
[22:03] <tytan> hey
[22:03] <tytan> Do you think the mini.iso will help me install lubuntu on  non PAE system?
[22:08] <Unit193> Pentium M?
[22:15] <phillw> that was a short visit!
[22:15] <phillw> he he... and there's us looking for people with non pae machines to test!


[00:11] <mup> PR snapcraft#1942 closed: Release changelog for 2.39.2 <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1942>
[01:54] <niemeyer> Why is every test failing with uboot-go now? Something changed behavior recently
[04:17] <elopio> snappy-m-o autopkgtest 1943 bionic:armhf bionic:amd64 bionic:arm64
[04:17] <snappy-m-o> elopio: I've just triggered your test.
[06:03] <mborzecki> morning
[07:27] <mborzecki> arch package updated to 2.31.1
[07:30] <mvo> mborzecki: yay, thank you
[07:31] <mborzecki> mvo: morning :)
[07:31] <mvo> mborzecki: and good morning to you as well :)
[07:31] <brett__> Need some advice on remote parts I've just built a snap on build.snapcraft.io more specifically its intended to be used as a part. I'm now building the snap that will use the above part. So the question is how does snapcraft find the part when its building my snap.  My understanding is that my part will be on the 'edge' channel until approved. Does that mean I need to swich snapcraft to the edge channel in order to find my part? Al
[07:31] <brett__> to find a local copy of the part?
[07:53] <kalikiana> good morning, snappy
[07:57] <brett__> Need some advice on remote parts I've just built a snap on build.snapcraft.io more specifically its intended to be used as a part. I'm now building the snap that will use the above part. So the question is how does snapcraft find the part when its building my snap.  My understanding is that my part will be on the 'edge' channel until approved. Does that mean I need to swich snapcraft to the edge channel in order to find my part? Al
[07:58] <brett__> to find a local copy of the part?
[07:58] <brett__> looks like it must be 9am somewhere in the world
[08:07] <kalikiana> hey brett__
[08:07] <kalikiana> Do you know about he parts wiki?
[08:07] <kalikiana> https://wiki.ubuntu.com/snapcraft/parts
[08:15] <pstolowski> morning!
[08:19] <brett__> I know about the parts wiki, but I assumed that its controlled.
[08:20] <brett__> I also note that there is only a very small no. of parts visible on the wiki, which makes me think that is not actually the primary parts source.
[08:20] <brett__> my part is still beta so I'm not certain its ready to be visible publicly
[08:21] <brett__> how can I make it available locally?
[08:22] <brett__> If I can make it available locally to the snap I'm building then I can confirm that it works correctly as a part.
[08:28] <kalikiana> brett__: just include the part in your snap's snapcraft.yaml directly for testing
[08:29] <kalikiana> or you could set SNAPCRAFT_PARTS_URI
[08:29] <kalikiana> (the default value is https://parts.snapcraft.io/v1/parts.yaml)
[08:31] <brett__> I don't understand what you mean by 'just include the part in your snap's snapcraft.yaml'
[08:31] <brett__> do you mean copy each of the  sections of the parts yaml into the snaps yaml.
[08:32] <brett__> This is likely to be messy as its a moderatley complex part, also what about all of the files scripts?
[08:32] <brett__> If you change the SNAPCRAFT_PARTS_URI can I point it at a local file system?
[08:34] <brett__> kalikiana - if I point it to a local file system, exactly what should it point to.
[08:35] <brett__> I've been googling the URI but can't find any useful doco.
[08:37] <kalikiana> brett__: see the URL above, that's what contents should look like
[08:41] <kalikiana> brett__: by include it in the yaml what I mean is, you can add it to parts: like a local part. it works the same way. you can do that with any remote part, the syntax is the same.
[08:47] <brett__> kalikiana, sorry but I don't understand what you mean
[08:47] <brett__> a local part defined a plugin to build it
[08:47] <brett__> what plug do I use when referencing a local part
[08:48] <brett__> also its not clear what you mean by: see the URL above, that's what contents should look like
[08:48] <brett__> clearly the uri points to a url with a 'parts.yaml' file.
[08:49] <kalikiana> brett__: say you have something like this `parts:
[08:49] <kalikiana>   foo:
[08:49] <kalikiana>     plugin: python3
[08:49] <kalikiana>     source: some-github-url`
[08:49] <brett__> I have no idea what a parts.yaml looks like and if it requires a url then that implies I need set up a private webserver
[08:49] <brett__> why 'python3'
[08:49] <kalikiana> brett__: "foo" is the name of the part. you can use it directly in your snapcraft.yaml
[08:49] <kalikiana> or, you get it from a remote part, where it's instead in the snapcraft.yaml of the remote part
[08:50] <brett__> my part is built with java, or is python3 the 'its a part' plugin
[08:50] <kalikiana> in both cases the definitoin looks the same
[08:50] <brett__> sorry which definition are you referring to.
[08:50] <kalikiana> brett__: I don't know what your part looks like, this is an example to explain it better :-)
[08:50] <brett__> I current have:
[08:51] <brett__> parts:   # build the web app   orion-monitor-webapp:     plugin: maven     source: git@bitbucket.org:sbsutton/orionmonitor.git     maven-options:       [-DskipTests=true]     organize:       war/orionmonitor-1.0-SNAPSHOT.war : webapps/orionmonitor.war     after: [tomcat-with-ssl]
[08:51] <brett__> ok, that wasn't helpful
[08:51] <brett__> this is the part
[08:51] <brett__> https://github.com/bsutton/tomcat-with-ssl-snap
[08:51] <brett__> currently in the snap I just have after: [tomcat-with-ssl]
[08:52] <brett__> so I've just tried your suggestion of including the part directly
[08:53] <brett__> Failed to pull source: unable to determine source type of 'https://github.com/bsutton/tomcat-with-ssl-snap'.
[08:53] <brett__> tomcat-with-ssl:     plugin: python3     source: https://github.com/bsutton/tomcat-with-ssl-snap
[08:53] <brett__> how do I tell it what the 'source type' is?
[08:53] <kalikiana> brett__: source-type: git
[08:54] <brett__> ok, it appears to be building :))
[08:55] <brett__> I think we need some more doco on this. I've re-read the user guide multiple times and it really doesn't explain how this works.
[08:55] <brett__> the python3 plugin was particularly non-obvious
[08:57] <brett__> I will put some notes on a forum post for others that might be interesed.
[08:57] <kalikiana> brett__: You can try `snapcraft help plugins` or more specifically `snapcraft help python3` to get docs
[08:57] <brett__> I have seen one warning that didn't make much sense
[08:57] <brett__> You must give at least one requirement to install (maybe you meant "pip install /home/bsutton/git/orionmonitor/snap-projects/installer/parts/tomcat-with-ssl/python-packages"?)
[08:59] <brett__> just looked at the doco for python3 plugin and it certainly wouldn't have led me to use it as you suggested.
[08:59] <brett__> the doco basically says to use it for python3 projects and my part is java so I would have just sailed past it.
[09:16] <mvo> hm, I'm getting "snap install hello\nerror: unable to contact snap store" - is that just me/my connection?
[09:19] <mborzecki> mvo: same here
[09:21] <pstolowski> mvo, and here
[09:21] <mvo> just asked in #snapstore and they know and work on it
[09:21] <mvo> fallout from the DDoS we introduced with the strict timeout handling
[09:21] <mvo> eh, strict schedule
[09:21] <mvo> time
[09:22] <mvo> and back
[09:23] <mborzecki> sorry :(
[09:24]  * mvo hugs niemeyer for his review
[09:24]  * niemeyer hugs mvo back
[09:27] <pstolowski> mvo, ack, thx
[09:34] <pedronis> mvo: you haven't yet changed to not wait for in progress default provider in prereq, right? I saw niemeyer, sadly we have a bit of the complication that what we need for bases vs default providers is a bit different, bases need to be ther much earlier, I suppose to run any hook
[09:34] <pedronis> s/niemeyer/niemeyer's comment/
[09:36] <mvo> pedronis: I changed it so that new snaps getting installed (base,default-providers) will be waited upon by the original snap only
[09:37] <pedronis> what is the original snap?
[09:37] <mvo> pedronis: snap install "foo" might pull in base,prepreq1,prepreq2, then foo will wait for these three but no waiting between the three new ones
[09:38] <mvo> pedronis: but you are right, I thing we only need the waits for bases, everything else now does not need any waits at all
[09:38] <pedronis> yes, we should need to avoid adding multiple tentative to install for other stuff
[09:38] <pedronis> but we need ot wait only for bases
[09:39] <pedronis> otoh it destroys the simplicity of comment's pov, life is complicated
[09:39] <mvo> pedronis: yeah, let me fix that, it will only wait for bases, the rest will be done in parallel. if you are looking at this, please let me know what further tests you would like to see
[09:41] <pedronis> mvo: I think the new code can support things that are default provider of each other, otoh it's a complicated contrived scenario
[09:41] <niemeyer> mvo, pedronis: In the future, we may be able to drop the requirement to wait on install altogether, and bake that logic in the "ready" feature
[09:41] <pedronis> s/complicated/competely/
[09:41] <niemeyer> I hope this is one of the things we'll be able to tackle in that next round of polishings
[09:42] <mvo> pedronis: yeah, I think so as well, I can build a test case for that if you want, I think the ciruclar case is handled now
[10:10] <Chipaca> I'm seeing snapd not release the unix socket when built with 1.10
[10:10] <Chipaca> on success; on error it releases it fine
[10:13] <mwhudson> Chipaca, mvo: i'm thinking of making go 1.10 the default for bionic btw
[10:13] <Chipaca> mwhudson: not 1.11? tsk
[10:13] <Chipaca> :-D
[10:14] <mwhudson> Chipaca: well i could shove git master in whatever state it's in into the archive the day before release, that's a sound plan, right?
[10:14] <Chipaca> mwhudson: well, it certainly rings a bell
[10:14] <mwhudson> i'm just happy we don't have a new architecture having its first release in an LTS this time...
[10:15] <Chipaca> mwhudson: seriously, 1.10 is fine for 18.04, but by 20.04 it'll be just as old as 1.6 is today
[10:15] <mwhudson> yeah i know
[10:15] <mwhudson> something else i also know: it's time for bed
[10:16]  * mwhudson zzz
[10:25] <mborzecki> FYI master is currently broken on Arch, can't start snaps, one user brought it up in snapd-git comments, i'm looking into it, otoh 2.31.1 works just fine
[10:26] <ogra_> cjwatson, is there something like "set -x" i can use in grub.cfg (i got u-boot->grub working but it falls over when loading the initrd (i think at least))
[10:32] <pstolowski> mborzecki, commented on one of your timer PRs
[10:32] <mborzecki> pstolowski: thanks
[10:35] <pstolowski> niemeyer, hey, thanks for the review of limitedbuffer! will you have a moment to take a look at #4551?
[10:35] <mup> PR #4551: ifacestate: do not auto-connect manually disconnected interfaces <Created by stolowski> <https://github.com/snapcore/snapd/pull/4551>
[10:39] <niemeyer> pstolowski: Is this a requirement for auto-connect to land?
[10:39] <niemeyer> pstolowski: Sorry, I meant interface hooks more generally
[10:40] <cjwatson> ogra_: set debug=<various things>.  set debug=all gives you everything though will be pretty noisy, but if you have a serial console so that you can capture the full dump it's the easiest way to start.  https://www.gnu.org/software/grub/manual/grub/grub.html#debug
[10:40] <ogra_> cjwatson, perfect, thanks !
[10:51] <pstolowski> niemeyer, no, it's independent
[10:52] <niemeyer> pstolowski: So I'd prefer to hold that back if you don't mind
[10:52] <niemeyer> pstolowski: Marking as blocked until the other features have landed, are working fine, and were released in stable
[10:52] <mup> PR snapd#4713 opened: cmd/snap: add self-strace to `snap run` <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4713>
[10:53] <niemeyer> pstolowski: Otherwise this is one more change piled up on that already complex space
[10:53] <pstolowski> niemeyer, ok
[11:04] <mborzecki> any idea what's happening here? https://paste.ubuntu.com/p/JCMTRnG3PQ/ snapd from master
[11:04] <mborzecki> the last thing is: execve("/usr/lib/snapd/snap-device-helper", ["/usr/lib/snapd/snap-device-helpe"..., "add", "snap_ohmygiraffe_ohmygiraffe", "/sys/class/mem/null", "1:3"], 0x7fff4eff7858 /* 0 vars */) = -1 ENOENT (No such file or directory)
[11:05] <mborzecki> that's tough luck because /usr/lib/snapd/snap-device-helper is there in the filesystem
[11:08] <pstolowski> mborzecki, hmm this snap works here (core from beta)
[11:12] <mborzecki> pstolowski: i'm running 2.31.r470.g8fd74f718 (latest master), without reexec, that would make it ahead for --edge and --beta
[11:23] <cachio_> mvo, hey
[11:24] <cachio_> mvo, did you see the email that I sent you?
[11:24] <pstolowski> mborzecki, are you using core from edge? i think this helper needs to exist in core. it doesn't exist in beta core image, only in edge, so if you're running master you may have an incompatibility
[11:26] <mborzecki> pstolowski: yeah, i think it runs in the mount namespace of the snap, probably edge will work
[11:27] <mborzecki> pstolowski: .. and it does
[11:27] <mvo> cachio_: that i386 is unhappy? I saw it, could you point me to a log with the failures please?
[11:27] <pstolowski> good
[11:29] <cachio_> mvo, https://paste.ubuntu.com/p/mdJgCbyqnR/
[11:30] <cachio_> mvo, could be related to the problem that you mentioned yesterday?
[11:38] <mvo> cachio_: hm, that looks unreleated, strange, can you see with `snap changes` what is actually going on?
[11:41] <cachio_> mvo, it shows there is an auto-refresh
[11:42] <cachio_> mvo, I canceled it
[11:42] <cachio_> mvo, then the tests continues
[11:42] <cachio_> but , I tried 3 times and alwaut I saw the same problem
[11:43] <cachio_> mvo, I'll try again
[11:47] <mvo> cachio_: strange, I will try after lunch
[11:49] <cachio_> mvo,
[11:49] <cachio_> np
[11:52] <Facu> hi! where are snapd logs? I want to see what it's currently doing in my system (thanks!)
[11:53] <mborzecki> Facu: try `journalctl -u snapd`
[11:55] <Facu> mborzecki, last thing I see is "Started Snappy daemon.", 1h80m before, and it's been hammering a couple of CPUs since... maybe I should enable debug logs or something?
[11:55] <Facu> *1h20m
[11:57] <mborzecki> Facu: you can add SNAPD_DEBUG=1 its environment file, `systemctl cat snapd` to find the right path
[11:58] <Facu> mborzecki, done, and restarted, let's give it some minutes, thanks!
[12:05] <mup> PR snapcraft#1944 closed: tests: split the plugins tests in the same directory <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1944>
[12:20] <sergiusens> o/
[12:21] <sergiusens> mvo: fyi https://pastebin.ubuntu.com/p/Svkx2KZ8jG/
[12:23] <mvo> sergiusens: is this inside lxd? is it a new thing?
[12:23] <sergiusens> mvo:  inside lxd, yes
[12:24] <sergiusens> mvo: it looks like the same thing (except I used to trigger it on garbage collection)
[12:25] <mvo> sergiusens: hrm, drat - zyga will want to know about this once he is back
[12:42] <mup> PR snapd#4707 closed: tests: spread test for broadcom-asic-control interface <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4707>
[12:57] <sergiusens> snappy-m-o: autopkgtest 1943 bionic:amd64 bionic:arm64 bionic:armhf
[12:57] <snappy-m-o> sergiusens: I've just triggered your test.
[12:57] <sergiusens> mvo: we sort of need that working to make this https://forum.snapcraft.io/t/per-project-containers/388/16 a thing
[13:00] <Chipaca> sergiusens: is this running snapd in a snapped snapcraft inside a snapped lxd ?
[13:00] <diddledan> snapception
[13:01] <Chipaca> one day we're going to find we've completely melted the bits of the kernel that handle mount namespaces
[13:01] <Chipaca> it'll just be a 20MB array of half-bits
[13:12] <mvo> seb128: please invite pedronis for the install state.json call too
[13:13] <seb128> mvo, done
[13:16] <Son_Goku> I guess I'm spending lunch today updating snapd and snapd-glib
[13:16] <popey> \o/
[13:17] <Son_Goku> kyrofa, ping
[13:23] <kalikiana> Son_Goku: you'll have better luck next week, since he's taking care of a kid that just came out of the oven
[13:23] <Son_Goku> oh jeez, okay
[13:24] <kalikiana> Son_Goku: anything I could potentially help with?
[13:24] <sergiusens> Chipaca: all correct except the snapped snap, this is snapcraft in venv but installing what it snapped in the env (the forum post however is the full deal, snapcraft snap, any build-snaps entry installed running inside a container created by lxd as a snap or whatever mechanism)
[13:24] <Son_Goku> kalikiana, I'm looking to try to make some time to bang out an initial prototype of rpm-based snaps in snapcraft
[13:25] <Son_Goku> I wanted to know if there were any major changes to how snapcraft's backends work since we last looked at it in October
[13:26] <pedronis> Chipaca: was your question about errors in the new api?
[13:28] <Guest28851> hello, is there a way to specify the python interpreter to use on the package ?
[13:29] <Guest28851> instead of "python3", y want /usr/bin/python3.6
[13:29] <Guest28851> instead of "python3", I want /usr/bin/python3.6
[13:29] <kalikiana> Son_Goku: Not really, no.
[13:29] <kalikiana> Son_Goku: Also, awesome to hear that :-D
[13:29] <Guest28851> So it will always use the default python3 of the system?
[13:32] <Son_Goku> Guest28851: yes
[13:33] <Guest28851> Ok, thanks
[13:36] <Guest28851> Also, I think it doesn't support py3.6
[13:46] <mvo> seb128: ta!
[13:47] <jdstrand> mvo: hi! thinking about the OOM issue
[13:48] <jdstrand> mvo: with spread tests, how many squashfs are mounted?
[13:51] <jdstrand> mvo: I ask cause while we can trigger the issue and jjohansen is looking into it, it seems (to me) to trigger too quickly with the amount of ram the system is supposed to have (1.5G)
[13:52] <jdstrand> mvo: I'm kinda wondering if there are lingering squashfs mounts (but they seem to be cleaned up on snap remove, so not sure why that would be the case)
[13:55] <mvo> jdstrand: I need to investigate how many but I also see it when this test runs in isolation
[13:56] <mvo> jdstrand: its also not 1.5G - its 400M on i386 because it eats LowMem
[13:56] <mvo> jdstrand: so its ~400/15 steps before it dies
[13:56] <mvo> (that is my rought esitmate)
[14:06] <jdstrand> jjohansen: fyi ^
[14:11] <jdstrand> mvo: there is LowTotal and LowFree. in /proc/meminfo. in my i386 VM with artful release kernel (no spectre/meltdown) and -updates kernels, I see that LowTotal is approaching the total ram (768M in the VM I'm using).
[14:12] <jdstrand> mvo: I realize LowFree is going down because there is a leak, but, for example, I only have 200M in LowFree here, but it takes a few loops to hit the condidition
[14:13] <jdstrand> mvo: as opposed to load, connect, oom
[14:14] <jdstrand> mvo: which you observe with twice the ram and twise the LowFree
[14:14] <jdstrand> twice*
[14:24]  * kalikiana lunch
[14:28] <jdstrand> jjohansen: fyi, note my followup ^
[14:29]  * pstolowski lunch
[14:39] <mup> PR snapcraft#1945 opened: elf: clear execstack by default <bug> <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1945>
[14:39] <sergiusens> jdstrand: when you have time, mind reviewing https://github.com/snapcore/snapcraft/pull/1945 ?
[14:39] <mup> PR snapcraft#1945: elf: clear execstack by default <bug> <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1945>
[14:45] <jdstrand> sergiusens: sure
[14:46] <sergiusens> thanks
[14:53] <mup> Bug #1750840 opened: [Enhancement] Please show (optionally) size consumed by snap in snap list <enhancement> <Snappy:New> <https://launchpad.net/bugs/1750840>
[14:57] <mup> PR snapcraft#1877 closed: tests: move test files out of the snapcraft dir <Created by elopio> <Closed by elopio> <https://github.com/snapcore/snapcraft/pull/1877>
[15:42] <mup> PR snapcraft#1892 closed: meta: parse float version as string <Created by kalikiana> <Closed by sergiusens> <https://github.com/snapcore/snapcraft/pull/1892>
[15:50] <xnox> mvo, 2.31.1+18.04	snapd/2.31.1+18.04 systemd/237-3ubuntu3 still red on s390x, but passes on other arches =(
[15:50] <xnox> this is latest snapd, triggered together with latest systemd.
[15:50] <xnox> + [[ ubuntu-18.04-s390x == ubuntu-14.04-* ]]
[15:50] <xnox> + systemctl stop dbus-provider
[15:50] <xnox> Failed to stop dbus-provider.service: Unit dbus-provider.service not loaded.
[15:50] <xnox> hm... something interesting is expected on s390x?
[15:50] <xnox> what is "location-control"?
[15:50] <xnox> 2018-02-21 14:31:31 Failed task prepare: 1
[15:50] <xnox>     - autopkgtest:ubuntu-18.04-s390x:tests/main/interfaces-location-control
[15:50] <xnox> 2018-02-21 14:31:31 Failed task restore: 1
[15:50] <xnox>     - autopkgtest:ubuntu-18.04-s390x:tests/main/interfaces-location-control
[15:50] <xnox> error: unsuccessful run
[15:58] <pedronis> xnox: an interface to control locationd  I think
[16:02] <xnox> pedronis, is that available on s390x?
[16:02] <xnox> $ apt search locationd -> gives me nothing
[16:02] <xnox> pedronis, what is locationd?
[16:04] <mvo> xnox: yeah, s390x used to be virtual and now is (more) real so the tests run for the first time
[16:05] <mvo> xnox: all sorts of test snaps missing, we are making progress there
[16:05] <mvo> xnox: thanks for including my systemd "fix" (workaround) for the apparmor label issue!
[16:06] <pedronis> xnox: sorry locationd is the name of a snap, I think the deb is ubuntu-location-service-*
[16:07] <pedronis> it's for GPS access basically
[16:08] <xnox> ok, source package is location-service and that does not exist for s390x
[16:08] <xnox> and has been removed everywhere post-xenial
[16:09] <xnox> pedronis, mvo, none of the location service tests should be running on bionic+, no? and definately not on s390x
[16:09] <pedronis> xnox: well the snap still exists
[16:09] <pedronis> for core
[16:09] <pedronis> so they need to run somewhere
[16:09] <pedronis> but for sure not s390x
[16:09] <xnox> true
[16:09] <xnox> location-service is in dep-wait state since xenial
[16:10] <xnox> Missing build dependencies: libubuntu-platform-hardware-api-headers, libubuntu-platform-hardware-api-dev
[16:10] <xnox> i don't think you will be able to build location-service on s390x ever.
[16:15] <xnox> mvo, pedronis - so i think we should open a bug; badtest snpad on s390x; and release current systemd & snapd.
[16:16] <mvo> xnox: yeah, lets put snapd on s390x in the "ignore" list for promotion for now, we work towards fixing it
[16:17] <mvo> xnox: and we will skip this particular test on s390x as a start (I'm sure there are more)
[16:17] <mvo> (more that will need fixing)
[16:19] <xnox> https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1750856
[16:19] <mup> Bug #1750856: snapd on s390x tried to run locationd tests, which does not exist on s390x <snapd (Ubuntu):New> <snapd (Ubuntu Bionic):New> <https://launchpad.net/bugs/1750856>
[16:19] <sergiusens> niemeyer: https://forum.snapcraft.io/t/fixing-the-snapcraft-cache-lp-1582469/4127 (for when you have time)
[16:20] <mup> Bug #1750856 opened: snapd on s390x tried to run locationd tests, which does not exist on s390x <britney:New> <Snappy:New> <snapd (Ubuntu):New> <snapd (Ubuntu Bionic):New> <https://launchpad.net/bugs/1750856>
[16:27] <xnox> slangasek, https://code.launchpad.net/~xnox/britney/badtest-snapd-s390x-locationd/+merge/338446 please =) based on above conversation and bugs
[16:48] <slangasek> xnox: done
[16:51] <mvo> cachio__: what are the chances for 2.31.1 for candidate? is i386 still give you trouble?
[16:51] <mvo> xnox: thank you!
[16:55] <cachio__> mvo, I am researching the last failure
[16:56] <cachio__> mvo, after that we can go to candidate
[16:57] <mvo> cachio__: thank you!
[17:01] <niemeyer> sergiusens: Noted and replied (a while ago, just for the record)
[17:01] <niemeyer> jdstrand: ping
[17:02] <jdstrand> niemeyer: hey
[17:02] <niemeyer> jdstrand: Heya, do you
[17:02] <niemeyer> have a moment for a call?
[17:02] <jdstrand> niemeyer: yes
[17:03] <niemeyer> jdstrand: https://hangouts.google.com/hangouts/_/canonical.com/snap-interfaces
[17:03] <cachio__> mvo, 2.31.1 is in candidate now
[17:08] <mvo> cachio__: \o/
[17:08] <mvo> cachio__: thank you
[17:08] <cachio__> mvo, np
[17:11] <sergiusens> niemeyer: thanks
[17:21] <Chipaca> unnnh
[17:21] <Chipaca> why are weekdays in timeutils called weeks?
[17:21] <Chipaca> that is very confusing
[17:25]  * kalikiana wrapping up for the day
[17:26] <kalikiana> Chipaca: I vote for calling them years, much clearer that way :-P
[17:27] <kalikiana> Chipaca: Actually sounds like a Japanese thing. Like saying "convenience" when you mean a shop, or saying "work" when you mean a part-time job.
[17:28] <kalikiana> You add the missing word in your head
[17:30] <mup> PR snapcraft#1946 opened: errors: add ability to send stack traces to sentry <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1946>
[17:31] <Chipaca> kalikiana: my problem isn't with synecdoche per se
[17:31] <Chipaca> or would this be metonymy
[17:31] <Chipaca> darn it
[17:32] <Chipaca> anyway, my problem isn't with the figure of speech :-)
[17:33] <mup> PR snapcraft#1946 closed: errors: add ability to send stack traces to sentry <Created by sergiusens> <Closed by sergiusens> <https://github.com/snapcore/snapcraft/pull/1946>
[17:33] <mup> PR snapcraft#1947 opened: errors: add ability to send stack traces to sentry <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1947>
[17:36] <cachio__> jdstrand, hey
[17:37] <cachio__> I am making an update on the interface tests, and removing part of the connection checks
[17:37] <cachio__> asi we are already checking that in the interfaces-many test
[17:38] <cachio__> jdstrand, do you have any idea about how to check that the autoconnection is done or not as part of this test?
[17:38]  * Chipaca -> walk
[18:13] <mvo> pedronis: we still want  4599 for 2.32, right?
[18:16] <pedronis> mvo: yes
[18:17] <pedronis> mvo: I was having dinner
[18:18] <mvo> pedronis: np, I see what I can do tonight about the review, otherwise tomorrow early
[18:18] <mvo> pedronis: looks like 2.32 can will be branched tomorrow morning(ish)
[18:19] <pedronis> mvo: I'm trying to see if I can re-review your branch still tonight
[18:23] <popey> Is there any way to switch a snap to devmode without removing it (and thus losing all my data)?
[18:23] <popey> snap refresh doesn't seem to take any notice of the --devmode flag
[18:30] <pedronis> mvo: left some comments still
[18:30] <pedronis> mvo: did we lose waiting for the base case?
[19:04] <mup> PR snapcraft#1948 opened: tests: move test files out of the snapcraft dir <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1948>
[19:04] <mvo> pedronis: hm, iirc I added code that would make everything in the change wait for the base snap, let me double check
[19:06] <mvo> pedronis: thanks for your comments, I'm looking now
[19:08] <mvo> pedronis: aha, I see what you mean now, checking
[19:18] <pedronis> mvo: it's called setup-profiles  not setup-profile I think
[19:20] <mvo> pedronis: indeed, thanks. I re-added the wait, the test is still missing, I look into this next
[19:29]  * pedronis eods
[19:38] <jdstrand> xnox: hehe "And mainframes don't usually change their
[19:38] <jdstrand> GPS location ;-)
[19:38] <jdstrand> "
[20:43] <pat-s> Hi guys, does anyone know why the LD paths of my binary are altered during the prime stage? Everythings fine during build/install/stage until it gets primed..
[20:49] <mup> PR snapd#4563 closed: tests: new spread test for gpio-memory-control interface <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4563>
[23:17] <mup> PR snapd#4714 opened: interfaces/apparmor,system-key: add upperdir snippets for strict snaps on livecd <Created by jdstrand> <https://github.com/snapcore/snapd/pull/4714>


[02:51] <hudsonkem> kubuntu 15.04 high swap, but I already set swappiness to 10.
[06:04] <sigma_> hi there
[06:05] <sigma_> is anyone here available to help me build a i386 package for the application here - http://kde-apps.org/content/show.php/Kup+Backup+System?content=147465
[06:05] <sigma_> i tried and failed miserably!
[06:08] <sigma_> sorry located here - https://build.opensuse.org/package/show/home:simper:kup/kup-kf5
[06:08] <sigma_> kup-0.6.0.tar.gz is the source file
[06:08] <sigma_> i still dont get why kubuntu doesnt include this as a standard app - its an amazing backup utility
[06:30] <redbul> ciao
[07:48] <lordievader> Good morning.
[07:59] <hudsonkem> anybody there?
[07:59] <lordievader> hudsonkem: See /names ;)
[08:01] <hudsonkem> '-', I'm getting high swap, but I already set swappiness to 10.
[08:01] <hudsonkem> so, any idea?
[08:01] <lordievader> hudsonkem: What is the output of 'free -m'?
[08:01] <lordievader> !paste | hudsonkem
[08:03] <amichair> Hi, I'm in the middle of upgrading 14.10 to 15.04, and at ~75% the distribution upgrade gui window is simply frozen (after minimizing+maximizing the window is blank, so it's hung). How should I proceed?
[08:03] <hudsonkem> https://paste.kde.org/p7zzuo6df
[08:03] <lordievader> amichair: Is apt-get/dpkg still running?
[08:03] <amichair> I saw in htop that cups was taking 100% cpu for quite a while, so killed it, but that didn't help
[08:04] <lordievader> hudsonkem: Heh, that is odd... Could you pastebin the output of 'vmstat 1 5'?
[08:04] <amichair> lordievader: I see a /usr/bin/dpkg process with very long command line
[08:05] <lordievader> amichair: Does it use any resources? (top -p `pidof dpkg`)
[08:06] <amichair> lordievader: looks idle
[08:07] <lordievader> amichair: Hmm, kill the upgrade gui, and dpkg if it still runs after that. Then run 'sudo apt-get install -f'.
[08:07] <amichair> lordievader: although looking at htop I see there's a /tmp/ubuntu-release-upgrader process that's around 2% cpu
[08:07] <lordievader> That is still idle ;)
[08:07] <amichair> lordievader: oh my. great software :-)
[08:08] <hudsonkem> https://paste.kde.org/p3bajnbey
[08:09] <lordievader> hudsonkem: That is quite different output than what I expected...
[08:09] <amichair> lordievader: I killed the gui, and dpkg disappeared
[08:10] <lordievader> hudsonkem: I got something like: https://paste.kde.org/pjr0qu059
[08:10] <lordievader> amichair: Right, good. Run 'sudo apt-get install -f'.
[08:10] <hudsonkem> .-. just vmstat and out 1 and 5 yeah?
[08:10] <amichair> lordievader: apt-get install -f fails with error about dpkg being interrupted
[08:10] <amichair> lordievader: should I run the recommended 'sudo dpkg --configure -a'
[08:10] <lordievader> amichair: Do what it says ;)
[08:11] <lordievader> hudsonkem: 'vmstat 1 5'
[08:12] <hudsonkem> sorry did now about this :D
[08:12] <hudsonkem> https://paste.kde.org/pfkhdzeq3
[08:12] <hudsonkem> I thought "vmstat -as" -.-'
[08:12] <lordievader> hudsonkem: I see no swap usage.
[08:13] <hudsonkem> just a minute, up screenshot
[08:13] <amichair> lordievader: ok, it's running. btw, is this a known issue?
[08:14] <lordievader> amichair: Not to me.
[08:15] <hudsonkem> http://i.imgur.com/2lGyZic.png
[08:16] <lordievader> hudsonkem: The 468Mb swap usage you mean? That ain't strange. If swap is used it is not cleared. It ain't efficient to clear the swap. It is more efficient to leave the data but disregard the pointer.
[08:17] <netrunner_> Hatsukawa
[08:17] <netrunner_> my friend's favorate japanese porn star
[08:18] <lordievader> netrunner_: Please keep this channel family friendly.
[08:18] <hudsonkem> but it make my pc more heavy, when I was using xfce it was working good
[08:19] <lordievader> hudsonkem: In what way does it make you pc more heavy?
[08:19] <lordievader> It was running out of ram, it needed to store a few pages somewhere.
[08:19] <hudsonkem> -.-' many lagg
[08:19] <lordievader> KDE is heavier than XFCE ;)
[08:20] <amichair> lordievader: ok, dpkg is done, now what?
[08:20] <lordievader> amichair: sudo apt-get install -f
[08:20] <amichair> lordievader: nothing to do (only a lot to autoremove)
[08:20] <hudsonkem> yeah, but to activate swap the ram must to be around 1.7-8gb
[08:20] <lordievader> amichair: Okay: sudo apt-get dist-upgrade
[08:21] <lordievader> hudsonkem: True.
[08:21] <amichair> lordievader: same result
[08:21] <lordievader> hudsonkem: Keep vmstat running (vmstat 1) and check if swap is actively being used.
[08:22] <lordievader> amichair: Hmmm. How do your sources look like?
[08:22] <hudsonkem> okay, thx for help
[08:22] <amichair> lordievader: if I do apt-get upadte it shows vivid, is that what you meant?
[08:23] <hudsonkem> about xrender, I got same window tearing, ideas? :)
[08:23] <lordievader> hudsonkem: Enable vsync?
[08:23] <lordievader> amichair: Err, somewhat. Actually I'd like to see /etc/apt/sources.list
[08:23] <hudsonkem> yep but nothing happen
[08:25] <amichair> lordievader: http://paste.ubuntu.com/11515765/
[08:25] <lordievader> hudsonkem: Hmm, what videocard and driver are you using?
[08:25] <amichair> lordievader: but nowadays there are lots of sources.list.d too no?
[08:26] <lordievader> amichair: That looks good. The sources.list.d things should be disabled. "sudo apt-get update&&sudo apt-get dist-upgrade"
[08:28] <amichair> lordievader: only *.list in that dir are considered? if so, they are indeed disabled. lots of other backup files in the dir too though.
[08:28] <hudsonkem> intel i915, no driver.
[08:28] <lordievader> hudsonkem: No driver? Wut... What is the output of 'lspci -k|grep -A2 VGA'?
[08:28] <amichair> lordievader: update & dist-upgrade same as before - nothing to do, only a bunch to autoremove
[08:29] <lordievader> amichair: Yes, but the first thing do-release-upgrade does is disable ppa's.
[08:29] <lordievader> amichair: Is plasma-dekstop installed?
[08:29] <amichair> apt-cache policy plasma-desktop says Installed: 4:5.2.2-0ubuntu4
[08:30] <lordievader> amichair: I guess you are all set then ;)
[08:30] <hudsonkem> https://paste.kde.org/pmsjhywez
[08:30] <amichair> lordievader: pray and reboot?
[08:31] <lordievader> amichair: Precisely :P
[08:31] <hudsonkem> hahah
[08:31] <amichair> lordievader: ok, thanks for ur help. if you don't hear from me soon, it didn't work :-)
[08:31] <lordievader> I hope I do hear from you ;)
[08:34] <hudsonkem> with xubuntu 15.04 +xfwm I got tearing, after, installed compton and solved that, without drivers. but I would like to solve that with kwin_x11
[08:35] <amichair> lordievader: I didn't even make it as far as the restart dialog. if I select restart from k-menu, the screen fades out, but no dialog appears
[08:35] <hudsonkem> and I don't like compiz
[08:35] <amichair> actually I'll try waiting 30 secs
[08:35] <lordievader> amichair: sudo reboot?
[08:35] <hudsonkem> amichair try, go to tty and press ctrl+alt+del
[08:36] <lordievader> hudsonkem: https://wiki.archlinux.org/index.php/Intel_graphics#Tear-free_video
[08:37] <amichair> lordievader: well waiting didn't work. sudo reboot kills kde (session etc.) vilently, no? is there any way to do a graceful shutdown?
[08:37] <lordievader> Meh, it is a bit crude. But it does the job.
[08:38] <amichair> lordievader: ok then, here it goes.
[08:40] <hudsonkem> lordievander I tried something like that but it a little different, let me see if this work here :D
[08:42] <hudsonkem> lordievander I dont have graphic driver installed, but yeah!, 01.org not realized yet
[08:42] <amichair> lordievader: well my desktop and all settings/widgets are gone, but at least I'm back here. I suppose plasma 5 resets everything?
[08:43] <lordievader> amichair: Thought so. Never done an upgrade from Plasma4 to Plasma5. Or at least not in its current state.
[08:44] <amichair> lordievader: I've been doing upgrades since dapper. sometimes big things break, sometimes little things break.
[08:48] <amichair> lordievader: adding back ppas, it says kubuntu-ppa not found, does that still exist?
[08:48] <hudsonkem> amichair why not made clear install of 15.04 and upgrade plama? its more security
[08:48] <lordievader> Perhaps not for vivid. There is a backports ppa, if that is what you mean.
[08:48] <lordievader> The backports has Plasma 5.3.1.
[08:48] <hudsonkem> yep
[08:48] <amichair> lordievader: I had both ppas, backports seems ok, kubuntu-ppa says not found
[08:49] <amichair> hudsonkem: there's too much configuration to do, running servers etc.
[08:49] <amichair> maybe for the next LTS I'll do a clean install. I've got time to think about it :-)
[08:49] <hudsonkem> :O. u're on server.
[08:50] <amichair> hudsonkem: it's both
[08:50] <hudsonkem> rebooting here, I will be back :3
[08:50] <hudsonkem> amichair got it
[08:50] <lordievader> amichair: KDE on a server? Blegh.
[08:51] <hudsonkem> lordievader as I thought '-'
[08:51] <amichair> lordievader: nono, it's just web/mail/etc servers running on a desktop :-)
[08:53] <amichair> are the Windows theme designers moonlighting for KDE now?
[08:54] <amichair> even taking it a step futher, with 1-bit color icons
[08:54] <amichair> color depth, that is
[08:59] <hudsonkem> '-' yeah, just when intel graphics driver 1.0.9 realise, tried something but plasma not start more.
[09:01] <amichair> well, there's the first plasma crash, in less than 20 minutes.
[09:01] <amichair> let's try 5.3.1 on for size...
[09:29] <amichair> after the upgrade, a driver manager notification pops up with a checkbox for  intel processor microcode (proprietary). Should I select it? (never saw this in previous versions)
[09:30] <lordievader> Err, you might want to read more about it.
[09:30] <lordievader> !info intel-microcode
[09:32] <amichair> lordievader: how would I know if I should enable it or not? Any way to tell what's in it?
[09:32] <lordievader> amichair: apt-cache show intel-microcode
[09:33] <amichair> lordievader: any reason one should not enable it?
[09:33] <lordievader> Can't really think of any.
[09:34] <amichair> done.
[09:34] <amichair> the notification icon doesn't seem to disappear though
[09:37] <__dan__> i enabled it, along with nvidia proprietary drivers, haven't seen the notification since - you'll almost certainly need to reboot for it to take effect tho
[09:38] <amichair> any idea why the battery icon is red and blink-zooms every few seconds? (I'm on a desktop)
[09:39] <amichair> and how do I close the instant messaging icon?
[09:40] <amichair> I see missing pidgin icon is still not fixed
[09:40] <amichair> clock date still unusable
[09:41] <amichair> taskbar can't be manually reordered
[09:41] <amichair> is there any estimate on when plasma 5 will get back the plasma 4 functionality? 5.4.0 maybe?
[09:42] <__dan__> no idea on the battery, instant messenger you should be able to right click and remove that way (may have to unlock widgets first), some taskbar icons don't appear anymore because those apps use a taskbar API from the 60's (i've had this happen with dropbox) i have a workaround if you're interested
[09:43] <amichair> __dan__:  yeah there was some replacement tray applet for those... do u remember what it's called?
[09:43] <__dan__> wmsystemtray
[09:44] <amichair> man that's ugly
[09:45] <__dan__> some apps need to be updated for tne new millennium unfortunately
[09:46] <__dan__> personally I've only seen this happen with dropbox so far
[09:46] <__dan__> in the meantime, wmsystemtray does accept some parameters you may be able to tweak it more to your tastes
[09:47] <__dan__> but yeah, lipstick on a pig
[09:48] <__dan__> wmsystemtray --non-wmaker --bgcolor white
[09:48] <__dan__> put it where you want and tell KWin not to draw the window decorations, a reasonable starter for 10
[09:52] <__dan__> taskbar can be manually reordered, right click on taskbar, "Task Manager Settings", under "Grouping and Sorting" set Sorting to Manually
[09:57] <lordievader> amichair: Your battery indicator seems like a bug.
[09:58] <amichair> __dan__: thanks
[09:58] <__dan__> amichair: yw :)
[09:58] <amichair> any way to make the clock date readable? it's 3px or so
[09:59] <amichair> I understand iso-formatted date functionality has been removed
[10:00] <__dan__> amichair: either increase the vertical width of the taskbar, or right click, "Digital Clock Settings" and turn the date off
[10:26] <amichair> __dan__: I'd like to see the date, but how can I enlarge it?
[10:29] <amichair> also, is there a way to remove the underline on each task button on the panel?
[10:30] <__dan__> amichair: increase the size of the taskbar
[10:30] <__dan__> amichair: no idea on the underline
[10:31] <amichair> __dan__: increasing the taskbar height to a point where the clock is readable makes all other icons ridiculously large...
[10:34] <__dan__> amichair: other than playing with the settings available I'm not sure what else to suggest, maybe set taskbar to two rows etc
[10:34] <amichair> btw any idea how to restore the original height?
[10:35] <yossarianuk> I recently tried out Gnome 3.6 (Fedora)
[10:35] <yossarianuk> I can safely say KDE is so far ahead its untrue.
[10:35] <__dan__> amichair: same way you changed it in the first place
[10:35] <s_20> yossarianuk: to be fair, so is gnome (3.16)
[10:36] <amichair> __dan__: but I don't know what the original size was, or what the size is as I'm dragging
[10:36] <amichair> is it possible to restore the default?
[10:37] <__dan__> not sure tbh
[10:45] <canis_> Are KDE guys and GNOME guys rivals?
[10:45] <s_20> uuuh.. i suppose not really
[10:46] <canis_> So is there anyone who has worked for both KDE and GNOME?
[10:47] <Roland__> yes?
[10:48] <Roland__> canis_: sorry, worked with.. not worked for :P
[10:48] <canis_> Roland__: Yeah I meant with
[10:49] <s_20> it certanily felt different though a few years back
[10:49] <canis_> s_20: what are you referring to?
[10:50] <Roland__> it seems to me that GNOME is for first time users, KDE is more a poweruser thing
[10:50] <s_20> canis_: well, gnome users making fun of kde users and vice versa
[10:51] <lordievader> canis_: Dbus is a Gnome thing that is heavily used in KDE.
[10:51] <s_20> lordievader: once again, didn't use to be that way
[10:51] <s_20> remember dcop?
[10:51] <lordievader> Nope.
[10:52] <s_20> so it seems like there's more of a spirit of cooperation between *nix desktop environments
[10:52] <s_20> "Desktop COmmunication Protocol (DCOP) was an inter-process communication (IPC) daemon by KDE used in K Desktop Environment 3. "
[10:52] <canis_> I never knew that GNOME guys made fun of KDE guys
[10:52] <s_20> essentially what kde used for exactly that purpose before they switched to dbus
[10:53] <lordievader> Ah, I see. Anyways, dbus is quite nice.
[10:53] <s_20> canis_: it's been a few years, it was like vim vs. emacs
[10:53] <s_20> maybe not quite as bad, but still
[10:53] <Roland__> most gnome apps work nicely on KDE and KDE apps on gnome, so there's not really much of a competition, everybody can use whichever Desktop Environment they want... GNOME / KDE / or LXDE (for slower computers)
[10:54] <Roland__> they can even be set up on the same computer, so you could switch and work with any of those
[10:54] <s_20> Roland__: well, now - but sometimes you still hear people moaning like "ugh, i have to install *all* these packages and run *all* these services to run $random_kde_app"
[10:54] <s_20> but yah, it's better than it ever was before, no sarcasm there
[10:55] <Roland__> there are always people, who aren't happy with the work other people have done... for free
[10:55] <s_20> certainly
[10:55] <s_20> for the most part, i'm a happy camper
[10:56] <s_20> been using kde for about 10 years now
[10:56] <Roland__> I've been using it at work for 7+ years
[11:34] <rharish> is this channel logged ? if not can anyone pass me last night's logs ?
[11:35] <lordievader> rharish: http://irclogs.ubuntu.com/2015/06/01/%23kubuntu.html
[11:36] <rharish> lordievader: thanks :)
[11:38] <lordievader> ;)
[12:06] <ejay> hi, did any of you noticed that, when opening multiple windows of same application, little triangle that indicates that multiple windows are open is out of place? http://imgur.com/kP1T5jM breeze theme, kubuntu 15.04
[12:10] <ejay> this bug is rare tho
[12:22] <BluesKaj> Hey all
[13:05] <amichair> is there a plasma 5 panel widget that can show a folder as a simple list, like there was in plasma 4?
[13:07] <soee> amichair: what about Folder View widget ?
[13:07] <amichair> soee: I can't get it to show a list, is it possible?
[13:08] <amichair> soee: i.e. it's a window filled with rows and columns of icons, not a simple list with one line per file. unusable as it is.
[13:08] <amichair> I'm not sure if in plasma 4 it was folder view or quick view or something like that
[13:08] <amichair> but I used it all the time
[13:08] <soee> amichair: i dont think so
[13:09] <amichair> man it's frustrating, so much funcionality gone in plasma 5.
[13:10] <amichair> and in 5.3.1 too, not 5.0.0
[13:11] <amichair> how about a resource load viewer that can show individual core utilization, like the System Load Viewer did in plasma 4?
[13:59] <amichair> does anyone know if there's a way to remove those wierd underlines from all panel taskbar buttons?
[14:07] <yossarianuk> amichair: change plasma theme perhaps ?
[14:08] <amichair> sounds like overkill... I'm hoping there's a setting somewhere for it
[15:18] <nfk|laptop> does anyone know how to access wm console from plasma2?
[15:21] <ds_> guys ... i turned my laptop on today and there are like 30% Icons missing in the menu (example: http://i.imgur.com/wfLFJqL.png) ... when i switch to oxygen icons in settings everything is fine, with breeze or breeze dark icons, it looks like in the picture)
[15:21] <ds_> i would like to have my breeze icons back, any suggestions?
[15:23] <BluesKaj> yeah ihave problems with breeze too, so I use oxygen instead, but I think there is a bug filed, ds_
[15:25] <BluesKaj> breeze dark desktop theme doesn't work at all here
[15:28] <nfk|laptop> i'm fine with breeze dark so far
[15:28] <nfk|laptop> though it is missing some icons but not 30%
[15:31] <ds_> nfk|laptop: i was fine with it too, it just changed today after login. Did nothing special last time using this laptop. I hope watching netflix and surfing a little bit dont make my icons go away :P
[16:23] <WhiteEyeDoll> afk
[16:24] <WhiteEyeDoll> unafk
[16:32] <gr00v3r> On Kubuntu 15.04 i386 with full disk LVM and Home encryption it asks disk password 3 times. 1 for crypt sd5 and twice for swap. It is known behavior?
[16:34] <gr00v3r> The disk was completely wiped off and slow formated. It was a clean install
[16:35] <Bronze> gr00v3r; what are you really asking?
[16:36] <Bronze> gr00v3r: Are you asking if that set of password prompts is the way that is supposed to work ?
[16:37] <gr00v3r> Bronze: I newbie to Kubuntu, should I file a bug or  this is the way it is supposed to work?
[16:37] <Bronze> gr00v3r: Are you asking if that set of password prompts is the way that is supposed to work ?
[16:37] <gr00v3r> Bronze: exactly
[16:38] <Bronze> I personally have no idea. But I do want to suggest asking question directed specifically at the issue you are having. don't be indirect.   The way you asked, originally, it couldbe a bug, or it could be proper operatiion and people could answer yes either way.
[16:39] <gr00v3r> Bronze: OK
[16:48] <mozafar> hi, suspend-to-ram not work in my kubunu (latest version). After resuming, all things just hangs. Machine is Lenovo Z510.
[16:49] <mozafar> It did worked on kde 4.
[16:54] <hudsonkem> is it a good idea install zram-config in kubuntu 15.04?
[17:25] <hudsonkem> once again:: is it a good idea install zram-config in kubuntu 15.04?
[17:28] <lordievader> !info zram-config
[17:28] <lordievader> !info zram
[17:28] <lordievader> hudsonkem: Do you need it?
[17:30] <hudsonkem> dont know
[17:31] <lordievader> I take that as a no ;)
[17:31] <hudsonkem> now I really dont think so
[17:31] <hudsonkem> because im using systemd so .. :)
[17:31] <hudsonkem> thx man
[17:32] <hudsonkem> lordievader thx for tearing help I fixed that
[17:33] <lordievader> hudsonkem: How?
[17:38] <hudsonkem> well just create a folder "/etc/X11/xorg.conf.d/"
[17:40] <hudsonkem> and create a file named "20-intel.conf". echo>>https://paste.kde.org/pjzqu0vap
[17:40] <hudsonkem> so just reboot and works is a bird
[17:41] <lordievader> Right, thanks :)
[17:41] <hudsonkem> as*
[17:41] <lordievader> hudsonkem: Logout -> login should have done the trick too ;)
[17:41] <hudsonkem> yeah! but I really like reboot :P
[17:45] <lordievader> ...
[17:59] <hudsonkem> yeah! without zram-config, my swap is better
[18:00] <hudsonkem> lordievader any alternatives to zram-config?
[18:01] <lordievader> Err, no idea? Buying more ram?
[18:01] <hudsonkem> '-' hahah, thats a good joke
[18:02] <hudsonkem> hold me one the dollar :P
[18:04] <hudsonkem> reading here>> a zram feature is already in the kernel
[18:04] <hudsonkem> so dont need anymore :)
[19:15] <NeuhNeuh> Hello :)
[19:21] <BluesKaj_> hey NeuhNeuh
[19:22] <zamazan4ik> hi
[19:22] <BluesKaj_> hi zamazan4ik
[19:22] <zamazan4ik> who can tell me about stability of plasma 5.2?
[19:24] <zamazan4ik> because i want to install kubuntu 15.04 on my work machine, but i am afraid of bugs
[19:24] <BluesKaj_> it's under still under development, so not as stable as expected on an official release, but it's working quite well for me
[19:24] <Etriaph> zamazan4ik: Do you have a spare drive to test the hardware with an install?
[19:24] <zamazan4ik> and i don't want to see a plasma's crash reports every hour
[19:25] <BluesKaj_> zamazan4ik:  not recommended for a work machine yet IMO
[19:25] <Etriaph> Plasma hasn't crashed on me for about 2.5 months.
[19:25] <zamazan4ik> no, i have not any drives to test
[19:26] <zamazan4ik> i want to upgrade because now i use a kubuntu 14.04
[19:26] <BluesKaj_> plasma doesn't crash , but the kde 4 apps that run on it sometimes do
[19:27] <zamazan4ik> and my laptop(asus k55) with touchpad, of course. and 14.04 have some troubles with touchpades
[19:29] <zamazan4ik> thanks :)
[19:29] <zamazan4ik> and maybe you know
[19:30] <zamazan4ik> when can we upgrade to plasma 5.3? and when can we upgrade to linux-kernel 4.0.0 ?
[20:33] <eXistenZe> Hey guys
[20:33] <eXistenZe> Good evening
[20:43] <rharish> Etriaph: hey
[20:43] <Etriaph> rharish: Hi.
[20:43] <rharish> I was rhn yesterday
[20:43] <Etriaph> Ah, how's it going?
[20:44] <rharish> yeah, so all fine now. I didn't have to use the backports ppa afterall
[20:44] <rharish> from what I understand, the daily ppa, for kubuntu-ci gives 5.2 with editions before 15.04 and 5.3 on 15.04 onwards
[20:45] <rharish> so right now, daily ppa + 15.04 = 5.3 :)
[20:49] <Etriaph> rharish: Now to write some code! :D
[20:49] <rharish> yup, finally :)
[20:49] <rharish> Etriaph: thanks for your time and help though
[20:51] <Etriaph> Hey no problem.
[20:52] <eXistenZe> any kvm user here?
[22:13] <mparillo> I am not a kvm user (VMware Player for me), but there is a virtualization forum at: http://ubuntuforums.org/forumdisplay.php?f=308
[23:18] <JR2573> Hi, I just installed Kubuntu, and was wondering how I can change the settings in Dolphin to display device sizes in decimals (19.2 GB) instead of commas (19,2 GB)?


[16:09] <rbasak> Can an AA please review monitoring-plugins languishing in Xenial NEW? It's a merge of a Debian source package rename.
[20:24] <doko> arges, gccgo-go isn't in the archive anymore for wily and xenial
[20:26] <arges> doko: which bug are you refering to?
[20:27] <doko> arges, https://bugs.launchpad.net/bugs/1361946
[20:28] <arges> doko: ah yes! ok I'll mark as invalid
[20:28] <arges> doko: thanks!
[20:28] <arges> invalid for gccgo-go/xenial
[20:52] <cjwatson> publishers and various other bits of Soyuz will be stopped for a bit while we create s390x
[21:06] <Logan> cjwatson: whaaaaaaat
[21:06] <Logan> did I miss something?
[21:07] <cjwatson> perhaps.  it's been mentioned in a few places
[21:07] <cjwatson> https://www-03.ibm.com/press/us/en/pressrelease/47474.wss
[21:55] <Pici> bug 100000
[21:55] <Pici> okay, good.
[22:21] <cyphermox> Logan: it's going to be amazing. I'm waiting to receive my own to heat my house... at the cost of blocking off the basement because too much noise.
[23:07] <arges> cjwatson: do you know when publishing will resume?
[23:17] <cjwatson> arges: shortly


 should I add the debian wheezy repo to my sources.list or dpkg it
[00:20] <bazhang> is that a trick question
[00:21] <k1l_> i am wondering why its the a "can i install .deb on ubuntu" again in one hour
[00:21] <bazhang> and the you can with rpm from robotadillo
[00:44] <k1l_> channelspam for #br-ubuntu ?!
[01:46] <stevendale> Hi
[01:47] <stevendale> Could somebody unban me from #ubuntu-offtopic please
[01:49] <stevendale> I do think I've been under punishment long enough
[01:54] <Flannel> stevendale: Hi.
[01:55] <stevendale> Hi Flannel
[01:57] <Flannel> stevendale: Bans are not about punishment of you, they aren't "time out". They're about keeping the channel reasonably disruption free.
[01:58] <stevendale> I am assuring you I'm not a disruption
[02:00] <Flannel> stevendale: And do you understand our difficulty with that?  You've said it in the past, we've had this conversation in the past.  You "understand" that what you do is not acceptable, and that if you do it again, you'll be banned.  Yet here we are again.  Not the second time, not the third time, but I don't even know how many times.
[02:04] <stevendale> I do
[02:04] <Flannel> That's good.  So, what do you think we should do about this?
[02:08] <stevendale> That's up to you, not me, you're the operators. But out of personal preference, I would appreciate it if you didn't tell me to find somewhere else to chat
[02:08] <Flannel> No, it's really up to you.
[02:08] <Flannel> What do you think is a good way to handle this situation?
[02:11] <Flannel> And to be brutally honest, this would go much easier (and faster) if I got a response more frequently than once every five minutes.  If this is a bad time for you, we can handle it later.
[02:12] <stevendale> I think unbanning me would handle this situation, so we wouldn't have to keep having this conversation
[02:14] <Flannel> stevendale: And what is going to happen when you're unbanned?
[02:16] <stevendale> I'm going to follow the channel guidelines/TOS?
[02:18] <Flannel> stevendale: Including no harassing folks and no frequent nick changes?
[02:18] <stevendale> Yes
[02:18] <stevendale> And no destructive commands or code
[02:19] <Flannel> stevendale: Alright.  And what should we do if you then have problems following those things?
[02:20] <stevendale> Ban me
[02:21] <Flannel> stevendale: right.  And since this isn't the first time.  Does banning you for, say, six months, seem fair?
[02:21] <stevendale> Yes
[02:21] <Flannel> (Which shouldn't be a big deal, since you're going to not have any issues anyway).
[02:22] <Flannel> Plus, whenever, during those six months, you won't be coming in here every few days to talk about your ban, because you understand that it's for six months?
[02:22] <Flannel> (again, this is academic, as we won't ever get to this point)
[02:23] <stevendale> Yes
[02:24] <Flannel> Alright. I think we can agree to that.  And we're happy to have you back as a non-disruptive participant.
[02:24] <Flannel> stevendale: Your ban should be lifted.  I admit that there may still be some I missed, please let us know if there are in the future.
[02:24] <stevendale> Ok
[03:27] <phunyguy> @login
[03:27] <phunyguy> @btlogin
[06:05] <absklb> hi
[06:05] <absklb> may I please have anyones attention please?
[06:08] <Flannel> Hi absklb, how can we help you?
[06:10] <absklb> Flannel: i typed "!ops" in #ubuntu. one user by name of stenchfoodtz pmed me and typed bad words. i even shhared screenshot in that channel.
[06:10] <absklb> Flannel: I have set mode +R now. I forgot to do so initially.
[06:11] <Flannel> absklb: yes, we saw.
[06:11] <Flannel> Someone handled it, and actually, the user isn't around anymore either.
[06:11] <absklb> ok. Thanks.
[06:12] <absklb> Sinnce I did not gott any reply in that channel from ops I thought ops did not noticed and he was continueing typing  in pm hence....
[06:12] <absklb> anyway Thanks for resolving Flannel . Have a good day. bye.
[07:38] <DJones> You can tell the schools are back in session, just wish their primary school IT/computer lessons wouldn't autoconnect to #ubuntu
[12:05] <k1l> @mark #ubuntu j0sh1 trolling and racists part-msg
[14:56] <hggdh> zombie- (#ubuntu) seems to be a bot announcing warez
[16:16] <bazhang> or a webscale channel
[16:16] <bazhang> !webscale
[16:16] <bazhang> waht!
[16:16] <Pici> !web3.0
[16:16] <Pici> !web3.0-#ubuntu-offtopic
[16:16] <bazhang> hehe
[16:18] <bazhang> dissed the bot!
 CodeChris: my antigogle phone is being monitored by some u.f.o.thing to prevent thr phone turns back ubuntu again
[16:41] <bazhang> we have a winner
[16:49] <bazhang> chanserv lag k skip
[17:03] <bazhang> luks on an antigoogle phone
[17:04] <bazhang> he wants help with luks on android,as linux is android!
 teward: your link is good. Thanks. So, think i am on android
[18:06] <bazhang> called it
[18:13] <bazhang> he's not using any form of ubuntu on that android phone
[18:14] <bazhang> but android and linux are the same, so same commands!
[18:14] <Pici> !
[18:17] <bazhang> we should warn popey


[00:56] <wgrant> speakman: Why wouldn't that build be successful?
[07:10] <ricotz> hi :), the trusty recipe builds are getting the wrong version suffix, "~ubuntu13.10.1" instead of "~ubuntu14.04.1"
[07:12] <ricotz> e.g. https://launchpadlibrarian.net/154204927/buildlog.txt.gz
[07:28] <wgrant> ricotz: That's because trusty isn't quite set up yet.
[07:28] <wgrant> base-files etc. still say it's saucy
[07:28] <wgrant> Because we got the name so late on Friday night.
[07:29] <wgrant> It'll hopefully be updated this weekend some time.
[07:29] <wgrant> But a trusty system will currently call itself saucy.
[07:31] <ricotz> wgrant, ah, i see, never mind then -- i was kind of hoping there is some special method for recipes to get this
[07:32] <wgrant> ricotz: It actually changed recently.
[07:32] <wgrant> We used to pass in the series name from the outside, but when we transitioned to using the version instead we opted to use lsb_release.
[07:32] <wgrant> But it's not normally a problem, since base-files gets updated for the new release almost immediately.
[07:33] <ricotz> i guess will do it then https://launchpad.net/ubuntu/+source/base-files/6.12ubuntu5
[07:33] <wgrant> Right, it is currently in -proposed.
[07:33] <wgrant> But recipes don't use -proposed.
[07:34] <ricotz> yeah, so hoping it transitions soon
[07:35] <ricotz> thanks
[12:10] <teolemon> wgrant https://translations.launchpad.net/ubuntumanualautomated/ to maintainer Ubuntu French Translators (https://launchpad.net/~ubuntu-l10n-fr) , ideally
[12:11] <teolemon> that would solve our woes :-)
[14:47] <nKf> hi. i can't copy a source package from raring to saucy. launchpad complains about the same name. is this intentional? however, at least in the wine ppa there are three packages with the same name (1.7.4-0ubuntu4) for different series.
[15:06] <ricotz> nKf, try to binary-copy them
[20:56] <nKf> ricotz, this works, indeed. thanks.
[23:13] <DarylXian> Are there any launchpad sysadmins here?


[00:19] <pleia2> knome: sorry, been sick, I'll post and try to review
[03:04] <bluesabre> knome: typos in the window manager keyboard shortcuts, had horizontal and vertical reversed... fixed
[03:33] <bluesabre> knome: screenshots don't work too well with keyboard shortcut posts, but I put together a demo video here: https://www.youtube.com/watch?v=kCfZ8XPDPOk -- its taking forever to process, and I'm going to bed, but here's the link at least :)
[03:35] <bluesabre> nighty all
[03:36] <Unit193> G'nighty.
[06:31] <flocculant> bluesabre: yes - must say I was surprised ...
[08:47] <knome> pleia2, np :)
[08:47] <knome> bluesabre, lol, k
[09:48] <knome> pleia2, we also have the status tracker article mostly ready since september; i tweaked it a bit now and am fine with publishing it too after a quick review from somebody
[12:24] <knome> dkessel, Unit193: the plugin tells me you both have one submissions left unvoted
[12:24] <knome> flocculant, ^ and you have 2
[12:25] <knome> if this is intentional, dismiss
[12:25] <Unit193> You sure?
[12:25] <knome> of course it might be a bug too, but that's what i'm seeing here
[15:22] <knome> jjfrv8, hey! what's the state of th xfce power manager settings 1.4.4 docs?
[15:23] <knome> bluesabre, do we have a shortlist of the xubuntu-related packages that need appstream updating?
[15:39] <jjfrv8> knome, xfpm is just waiting for review.
[15:40] <jjfrv8> knome, I don't seem to be able to vote on the contest site.
[15:42] <knome> jjfrv8, when you logged in, did you allow it to see that you're on ~xubuntu-team ?
[15:43] <jjfrv8> what do you mean "allow it to see"?
[15:44] <knome> when you log in, you should see the ubuntu one confirmation screen that tells you the site is requiring some information
[15:44] <knome> from that list you need to check the checkbox next to xubuntu-team
[15:44] <jjfrv8> oic, the checkbox.
[15:45] <knome> :)
[15:45] <jjfrv8> ok, I'll try to complete my votes later this evening.
[15:45] <knome> no hurry :)
[15:46] <knome> by wednesday midnight i mean the midnight after wednesday
[15:46] <knome> i think the midnight deadline is always a bit ambiguous
[18:19] <knome> https://xubuntu.org/news/my-media-manager-gmusicbrowser/ is published
[18:20] <pleia2> g+ and fb done
[20:09] <Unit193> mhall119: Thanks for the email, dropped it to the rest of the core team.
[20:09] <mhall119> thanks
[20:09] <mhall119> pleia2: did you tell me that Xubuntu is going to use Gnome Software?
[20:10] <Unit193> Already is.
[20:10] <knome> yep, and should be for the release too
[20:10] <knome> unless it blows up in 1000 little pieces
[20:10] <mhall119> cool, thanks
[20:10] <Unit193> We're not thrilled with it, but there it is.
[20:11] <knome> we weren't thrilled with USC either, but there it was ;)
[20:11] <mhall119> Unit193: it's faster than USC was at least :)
[20:11] <Unit193> mhall119: It just can't find things well. :P
[20:11] <Unit193> knome: Truth
[20:11] <mhall119> no?
[20:11] <knome> mhall119, nope.
[20:12] <Unit193> mhall119: It's designed to only find graphical programs, can be a bit of a pain.
[20:12] <knome> mhall119, try to install a library!
[20:12] <mhall119> oh, well USC had the same problem didn't it? being application-centric
[20:12] <knome> unfortunately
[20:13] <Unit193> Pretty sure you could find screen in it though, no?
[20:13] <mhall119> but using Gnome Software from the archives means you get the Snappy Store automatically too
[20:15] <flocculant> mhall119: it leaves dependencies behind too
[20:16] <mhall119> flocculant: ?
[20:16] <mhall119> Gnome Software does?
[20:16] <flocculant> yup
[20:16] <flocculant> unless it's been fixed - pretty sure not - or not read that in changelog
[20:17] <flocculant> as far as usc not seeing the same things as g-s > https://launchpadlibrarian.net/249956293/missing%20package.png
[20:17] <flocculant> I guess not the case for everything
[20:18] <flocculant> bug 1552792 for dependencies
[20:18] <mhall119> yeah, I think usc would find non-app packages during a search, but not browsing
[20:18] <mhall119> but GS is built around the AppStream spec, which is application only
[20:19] <flocculant> wouldn't be able to give a definitive answer - didn't much like USC either :)
[20:19] <flocculant> yea I understand that - pretty much a case of making sure everyone knows that if they want to be able to install anything from the repos then g-s isn't the tool for them ;)
[20:22] <flocculant> works for most people - like USC did - I would expect
[20:22] <Unit193> Exactly, I can't comment on it too much as I like apt, a lot.
[20:23] <flocculant> yup
[20:23] <flocculant> well I tend to use ye olde worlde synaptic a lot
[21:25] <flocculant> bluesabre: I guess that this late - the best we're going to be able to do with thunar is make sure as many of the real issues are properly highlighted in the notes
[21:25] <flocculant> and sru/backport fixes when they eventually surface
[21:27] <flocculant> rc next week
[21:27] <knome> rollercoaster
[21:27] <flocculant> yea
[21:27] <knome> and hello!
[21:28] <flocculant> bluesabre: so unless I hear different I'll get that rolling before next week
[21:28] <flocculant> knome: hi and night ...
[21:28] <knome> ha, nighty :)
[23:05] <bluesabre> knome: packages that have appstream errors are:
[23:06] <bluesabre> http://appstream.ubuntu.com/xenial/universe/issues/xfce4-settings.html
[23:06] <bluesabre> http://appstream.ubuntu.com/xenial/universe/issues/xfce4-notifyd.html
[23:06] <bluesabre> http://appstream.ubuntu.com/xenial/universe/issues/libxfce4ui-utils.html
[23:06] <bluesabre> http://appstream.ubuntu.com/xenial/universe/issues/xfce4-power-manager-data.html
[23:06] <bluesabre> from http://appstream.ubuntu.com/xenial/universe/issues/
[23:07] <Unit193> \o/
[23:07] <bluesabre> "icon-not-found" errors are usually because there is no 64px or higher icon in the package or humanity icon theme
[23:16] <knome> night everybody
[23:59] <jjfrv8> knome, my wallpaper votes are in.