[00:00] <ObrienDave> abanabee7, how can we help?
[00:00] <ObrienDave> wilsonjl3, open a terminal please
[00:00] <wilsonjl3> got one open already ;)
[00:00] <ObrienDave> cool
[00:00] <abanabee7> Well, as I run Xubuntu the desktop starts messing up, like I start seeing graphics from before, like I was in a video chat at 11pm, and at 10 AM the next day i see those graphics pop up
[00:01] <ObrienDave> abanabee7, do you turn your computer off between times?
[00:01] <abanabee7> and when I switch the workspace, they go away, only to come back. And if I mouse over them they return to the current stuff. No, this is all in one session
[00:02] <ObrienDave> wilsonjl3, copy and paste the following line into the terminal
[00:03] <ObrienDave> sudo add-apt-repository ppa:ehoover/compholio
[00:04] <ObrienDave> abanabee7, sounds like a graphics card driver issue. are you current on the driver?
[00:04] <ObrienDave> wilsonjl3, what that does is add the address to you sources list and import the security key to your system
[00:05] <wilsonjl3> so i update now?
[00:05] <abanabee7> ObrienDave, I don't really use the graphics drivers, I mean I use the opensource ones as that allows the system to be able to boot into other computers, which I often do.
[00:05] <abanabee7> also, this is like a random thing, it will go like a month without doing anything bad, then go thro cycles of it doing this.
[00:05] <ObrienDave> wilsonjl3, now the ALWAYS important sudo apt-get update
[00:06] <wilsonjl3> thought so :) so i did it
[00:06] <ObrienDave> wilsonjl3, ok, look on that page for the package name...
[00:07] <wilsonjl3> ObrienDave help abanabee7 first :) i can wait and it'd probably be easier
[00:07] <ObrienDave> sudo apt-get install netflix-desktop
[00:08] <abanabee7> wilsonjl3, Thank you, i don't mind waiting either, as this is a recurring thing, and it is annoying, but not something that is a desperate thing
[00:08] <ObrienDave> abanabee7, sorry, i am not sure how to help you other than recommend the drivers for your card. someone here can be of better assistance than i can :)
[00:08] <wilsonjl3> aha im just trying to figure out how to use netflix on here :P no big deal
[00:08] <wilsonjl3> (its installed, ObrienDave)
[00:09] <ObrienDave> wilsonjl3, ok, what we installed is a custom WINE and the netflix viewer. it works pretty good
[00:10] <wilsonjl3> we only installed netflix-desktop and put in new repos?
[00:10] <wilsonjl3> didnt we?
[00:10] <ObrienDave> yes, but part of the dependencies for this version of netflix is the custom WINE environment ;P
[00:11] <wilsonjl3> okay :3
[00:11] <ObrienDave> dependencies are almost always automatically installed
[00:12] <wilsonjl3> so i was just supposed to put that into the terminal, right? not click anything on this page?
[00:12] <ObrienDave> abanabee7, you could also ask in #ubuntu about your graphics issue. be sure to mention you're using Xubuntu
[00:12] <ObrienDave> wilsonjl3, yes, we did everything from the terminal
[00:12] <wilsonjl3> ok
[00:13] <wilsonjl3> so it should work now?
[00:13] <ObrienDave> you should see a netflix icon under multimedia or graphics menu. i don't remember which
[00:13] <abanabee7> ObrienDave, true, I could go there. Tho i figured since it was Xubuntu that it was something about how XFCE is running
[00:14] <ObrienDave> ask Unit193, they are our resident XFCE expert :_
[00:14] <Fall> whisker menu fixed for 12.04 yet?
[00:14] <wilsonjl3> not working, its telling me to install, wich im guessing wont run on xubuntu :/
[00:15] <ObrienDave> Fall, not sure
[00:15] <wilsonjl3> install silverlight*
[00:15] <Fall> ObrienDave: it's slightly annoying :(
[00:15] <ObrienDave> wilsonjl3, ok, hang on
[00:15] <wilsonjl3> okay :)
[00:16] <abanabee7> ObrienDave, would this show up in the logs in some way? I mean I wouldn't know exactly what to look for in the logs. Where can I go to talk to Unit193?
[00:16] <wilsonjl3> abanabee7, Unit193 is in this room but i think he's away right now :/
[00:17] <abanabee7> Wilsonjl3, ahhhh, I can wait, I don't mind much. Do you know when he will be back? I don't want to miss him
[00:17] <ObrienDave> wilsonjl3, in terminal...
[00:17] <ObrienDave> sudo add-apt-repository ppa:pipelight/stable
[00:18] <wilsonjl3> abanabee7, no idea sorry :(
[00:18] <ObrienDave> sudo apt-get update
[00:18] <abanabee7> wilsonjl3, that's ok, time is not an issue, i stay up pretty late anyway lol
[00:19] <wilsonjl3> abanabee aha well thats good atleast
[00:19] <wilsonjl3> ObrienDave, its updating now
[00:20] <ObrienDave> k, sec
[00:20] <wilsonjl3> its done but ill brb, sorry! :)
[00:21] <ObrienDave> np
[00:23] <wilsonjl3> imback
[00:25] <ObrienDave> sudo apt-get install pipelight-multi
[00:25] <ObrienDave> brb
[00:26] <wilsonjl3> ok done
[00:26] <wilsonjl3> okay :)
[00:33] <wilsonjl3> im gonna go get some cereal
[00:34] <ObrienDave> k
[00:35] <wilsonjl3> im back
[00:35] <xuboo> me too!
[00:35] <xuboo> no audio :(
[00:35] <wilsonjl3> no audio ?
[00:35] <ObrienDave> wilsonjl3, netflix working?
[00:36] <wilsonjl3> ObrienDave ill chek again
[00:36] <xuboo> I'm back here cause the fix for no audio card did not work
[00:36] <ObrienDave> xuboo, is your volume up? is it muted?
[00:37] <xuboo> its up
[00:37] <xuboo> its a card issue
[00:37] <xuboo> i got a dummy device
[00:37] <wilsonjl3> ObrienDave nope not working :(
[00:37] <ObrienDave> wilsonjl3, dang
[00:37] <wilsonjl3> :'(
[00:37] <xuboo> I ran some commands yesterday on testing that found a sound card, but no card has been installed
[00:38] <ObrienDave> try...
[00:38] <xuboo> I've tried to replicate so many guides online but no dice
[00:38] <ObrienDave> sudo apt-get install wine-compholio
[00:38] <xuboo> bad spelling on package?
[00:38] <wilsonjl3> installing
[00:38] <ObrienDave> k
[00:39] <xuboo> oh im sorry not for me
[00:39] <ObrienDave> xuboo, sorry, that was for wilsonjl3
[00:39] <xuboo> no problem
[00:39] <wilsonjl3> :) help him, ill check it agan
[00:40] <ObrienDave> xuboo, try running in terminal alsamixer
[00:40] <wilsonjl3> or her* (sorry xuboo if you're a female)
[00:40] <xuboo> male
[00:40] <xuboo> no such file or directory
[00:41] <ObrienDave> xuboo, sudo apt-get install alsamixer
[00:41] <xuboo> No command 'alxamixer' found, did you mean:
[00:42] <xuboo>  Command 'alsamixer' from package 'alsa-utils' (main)
[00:42] <xuboo> ops hehe
[00:42] <wilsonjl3> alsamixer :P spelt it wronf
[00:42] <ObrienDave> oops xuboo sec
[00:42] <wilsonjl3> didn't work, ObrienDave :/
[00:42] <ObrienDave> !info alsamixer
[00:43] <ObrienDave> wilsonjl3, what error does it give you?
[00:43] <wilsonjl3> just says i need to install silverlight to watch the movies
[00:44] <ObrienDave> did you install pipelight?
[00:44] <wilsonjl3> i did sudo apt-get install pipelight-multi
[00:47] <ObrienDave> get this file...
[00:47] <ObrienDave> https://launchpad.net/~pipelight/+archive/ubuntu/stable/+build/6175405/+files/wine-compholio-amd64_1.7.22~ubuntu14.10.1_amd64.deb
[00:47] <ObrienDave> wait a sec
[00:48] <wilsonjl3> waiting :)
[00:48] <ObrienDave> https://launchpad.net/~pipelight/+archive/ubuntu/stable/+files/wine-compholio-amd64_1.7.22~ubuntu14.04.1_amd64.deb
[00:48] <ObrienDave> i forgot you have a 64bit system
[00:48] <wilsonjl3> aha no problem
[00:49] <ObrienDave> and this file...
[00:49] <ObrienDave> https://launchpad.net/~pipelight/+archive/ubuntu/stable/+files/pipelight-multi_<IP_ADDRESS>~ubuntu14.04.1_amd64.deb
[00:49] <ObrienDave> install the pipelight first
[00:50] <wilsonjl3> ok, paused the other one
[00:50] <wilsonjl3> oh install
[00:50] <wilsonjl3> not download
[00:50] <wilsonjl3> :3
[00:50] <ObrienDave> you can d/l both
[00:52] <wilsonjl3> wine-silverlight is downloading, pipelight is crashing the software centre :P
[00:54] <ObrienDave> dang
[00:54] <wilsonjl3> keeps going unresponsive
[00:56] <ObrienDave> let me try to install it here.
[00:56] <wilsonjl3> ok
[00:59] <wilsonjl3> ObrienDave, i gotta go to sleep, im about to pass out on my comp. im sorry
[01:00] <wilsonjl3> abanabee7, good luck fixing the graphics glitches, have a good night both of you :)
[01:00] <abanabee7> awww, he quit before I could say goodnight to him
[01:01] <xuboo> :/
[01:01] <ObrienDave> k, dang i hate leaving something unresolved
[01:01] <xuboo> same here :)
[01:04] <xuboo> seems I have alsa-utils installed, and alsamixer, but i get no such file or directory
[01:05] <ObrienDave> xuboo, not sure why alsamixer wont run
[01:07] <xuboo> its odd, lspci -k says I have an audio device
[01:07] <xuboo> but aplay -l or -L says no sound card
[01:07] <ObrienDave> hmm, beyond my knowledge of alsa
[01:07] <xuboo> brb
[01:07] <xuboo> thank you regardless :)
[01:08] <ObrienDave> k
[01:22] <xuboo> didn't work :(
[03:55] <MavKen> I've been using xubuntu for a few months now... everyday I ssh into the same vps... how can I create a shortcut that opens terminal and run "ssh -p 17982<EMAIL_ADDRESS>?
[03:59] <MavKen> nevermind..just figured it out
[14:11] <six86> Hello. What is the proper way to change xfce settings in the terminal? I want to change the number of virtual desktops for example and remove the "dock".
[14:12] <six86> Is the proper way to edit xfwm4.xml?
[14:23] <abanabee7> six86, I doubt the proper way would be to edit that xfwm4.xml, i looked @ mine, and its got all empty settings in it, & i have a pretty customized desktop from default, but i culd b wrong
[14:27] <six86> abanabee7: I just found xfconf-query
[14:27] <six86> seems to be the way to go
[14:28] <abanabee7> six86, ahhh, thats cool. Thanks. when u asked i was like, ooo, i wonder that too, thanks for a tiny new thing :)
[14:29] <six86> abanabee7: Now i just have to find out how to delete items
[14:31] <six86> I have it
[14:31] <abanabee7> six86, i would imagine you change the value from true to false, or from 1 to 0, or something that would tell it that you don't want that value
[14:32] <six86> -rR recursively resets values
[14:32] <six86> abanabee7: It was about removing a panel.
[14:34] <abanabee7> six86, thats cool, i love how things like that can be, a simple command can change your system. Thanks for the new info
[14:34] <six86> abanabee7: Yeah but my panel was not fully removed by this its stuck in the bottom now
[14:35] <six86> abanabee7: "xfce4-panel -r" and after that the panel is gone
[14:41] <abanabee7> six86, wouldn't that mean the panel is returned to the top? cause you reset the value, then restarted it so that the changes show
[14:41] <six86> there is nothing stated about panel-1 in xfconf anymore
[14:42] <six86> but something is stillt here because tha GUI shows 2 panels...
[14:43] <tweghrnjtgthjfx> Where does my porn save to on xubuntu?
[18:15] <Mountain_R> Hi guys I have a problem with the screensaver, previously there were installed the default screensaver but I was unable to stop it to switch off the monitor after few minutes, a user help me to unistall it and install xscreensaver 5.15.  It seems that the problem was fixed but now I have again the same problem, after only some minute The screen goes off. The strage thing is that xscreensaver is set to DOESN'T switch off and blank the scr
[18:15] <Mountain_R> een after 6 minutes. Please give me some advice guys...
[18:24] <MavKen> Mountain_R, sorry, any updates since it last worked?
[18:25] <MavKen> overkill... but run sudo apt-get clean -y && apt-get update -y && apt-get upgrade -y && apt-get dist-upgrade -y && apt-get autoremove -y
[18:28] <Mountain_R> Yes I have often done updates
[18:29] <Mountain_R> MavKen, do I have to run that command as one only command?
[18:29] <MavKen> yes
[18:30] <MavKen> that is my goto command if something is out of whack (lazy man approach)
[18:31] <MavKen> its a series of commands but one string so you dont have to enter separately
[18:31] <Mountain_R> MavKen, I do it now, can u tell me how to copy from Xchat if you know it?
[18:31] <Mountain_R> seems impossible on xchat, don't know why
[18:37] <MavKen> highlight, control + c
[18:37] <MavKen> I hate how chat doesnt have copy in rt click menu
[18:38] <bazhang> shift control c of highlighted
[18:39] <Mountain_R> ctrl+c  worked thanks
[18:39] <bazhang> the right click menu *does * have it, under window
[18:39] <Mountain_R> xchat doesn't have it
[18:41] <bazhang> #xchat will confirm
[18:49] <MavKen> no, not under window
[18:49] <MavKen> ctrl + c always works... just wondered why not included in rt click menu
[18:50] <MavKen> copy/paste are in rt click window when in text entry field. just not on actual chat contents
[18:51] <bazhang> highlighted--->shift control c works perfectly there
[18:51] <MavKen> hahahaha.... when you highlight, it automatically copies
[18:52] <MavKen> no need to cntrl c
[18:52] <MavKen> try it
[18:52] <bazhang> I have
[18:52] <MavKen> just asked on #xchat
[18:52] <Mountain_R> MavKen, I gave that command I will wait to check if worked, thanks. Can you please tell me what   -y   means?
[18:52] <Mountain_R> so I learn
[18:52] <MavKen> just means to answer yes
[18:53] <MavKen> instead of each prompt asking y or n
[18:53] <Mountain_R> ok got it
[19:00] <Mountain_R> MavKen, it doesn't work it switch off again the monitor
[19:00] <MavKen> uninstall then run sudo apt-get autoremove
[19:00] <MavKen> reboot
[19:02] <Mountain_R> from the ubuntu software centre is ok?
[19:04] <Mountain_R> MavKen,  i don't find any screensaver in the Ubuntu software center
[19:04] <MavKen> I dont use a screensaver...so not sure where to go from there
[19:05] <Mountain_R> i could try with: sudo apt-get remove screensaver
[19:05] <Mountain_R> ?
[19:09] <Mountain_R> i found it  it was simply xsceensaver
[19:10] <Mountain_R> to get the superuser I use:  sudo su
[19:10] <Mountain_R> it is ok or not?
[19:10] <bazhang> no
[19:10] <bazhang> just sudo
[19:11] <Mountain_R> just sudo don't gives me the superuser
[19:12] <bazhang> yes it does
[19:12] <bazhang> sudo apt-get remove packagename
[19:13] <Mountain_R> but if i do   sudo su    it ask me 1 time the password forever
[19:14] <Mountain_R> for all the terminal session
[19:14] <bazhang> thats not correct
[19:14] <bazhang> there is no root enabled
[19:14] <bazhang> use sudo -i for a root shell, if you must
[19:16] <Mountain_R> ok
[19:17] <Mountain_R> thanks
[19:18] <bazhang> np
[19:27] <wilsonjl3_> hey guys, anyone know why it keeps telling me to install silverlight when i wanna watch netflix even though i have pipelight and silverlight 5.1 enabled?
[19:28] <BarnabasDK> sudo -i /usr/bash
[19:28] <BarnabasDK> ?
[19:28] <BarnabasDK> seems a bit harsh ..
[19:28] <BarnabasDK> /usr/bin/bash
[19:28] <BarnabasDK> or did I misunderstand?
[19:29] <wilsonjl3_> is that for me?
[19:29] <BarnabasDK> more bazhang
[19:29] <wilsonjl3_> ah
[19:29] <bazhang> !netflix
[19:29] <BarnabasDK> sudo su - will actually run the login shell scripts as well afaik
[19:30] <BarnabasDK> and use the default (for root) shell
[19:30] <bazhang> there's no root enabled
[19:30] <BarnabasDK> so you cannot sudo to root?
[19:30] <BarnabasDK> sudo -u root
[19:30] <Mountain_R> I have uninstalled xscreensaver and the monitor still switch off.. how come?
[19:30] <bazhang> what are you trying to accomplish
[19:31] <BarnabasDK> well nothing I just saw you arguing against sudo su - (for root) which I think is the nice way to get root in a system
[19:32] <bazhang> ubuntu uses sudo alone
[19:39] <Mountain_R> the difference between sudo -i  and sudo su    is that you get these 2 results:  root@mypc:/home/mypc#    and   root@mypc:~#
[19:39] <Mountain_R> inverted results, sorry
[19:40] <Mountain_R> I dunno the difference between the two
[19:41] <Mountain_R> but both works good as root
[19:50] <BarnabasDK> Mountain_R, one will run the login scripts (su method) the other will not
[19:52] <Mountain_R> BarnabasDK, what's the difference
[19:56] <BarnabasDK> Mountain_R, normally when you log in a set of scripts are executed. the global ones, then .profile and perhaps .bashrc
[19:56] <BarnabasDK> su does that , sudo does not
[19:56] <BarnabasDK> afaik
[19:57] <Mountain_R> got it
[20:14] <Mountain_R> i am going crazy, light locker and xscreensaver are uninstalled but still the screen switch off after 1 minute of inactivity, what is it?
[20:15] <Guest25614> guys, i was using external monitor on vga and now when i disconnect it i see blank screen, my initramfs says: http://wdp.elenx.net/zdjecia/IMAG0527.jpg
[20:22] <krytarik> Mountain_R: There is "Power Manager" in the Settings Manager. :)
[21:36] <groja> Hello, I'm trying to create a swapfile for the system using Gparted.  I installed it using the software centre but I can't find the program to run it
[21:42] <bullgard4> What did you install?
[21:44] <bullgard4> groja: What did you install?
[21:44] <groja> Gparted, I think I've found it and linix was a 2Gb swap file.
[21:45] <bekks> What does "linix was a 2GB swap file" mean?
[21:45] <bullgard4> Please click Xubuntu > Applications menu > System > Gparted
[21:48] <groja> Its not listed in the system menu
[21:54] <bullgard4> groja: Please open a terminal. Enter 'sudo gparted'.
[21:58] <snuggyfoo> Is anyone familiar with running commands over ssh from a shell script.
[21:58] <snuggyfoo> ?
[22:08] <snuggyfoo> disregard
[22:17] <adrenaline_> snuggyfoo, do you need help?
[22:18] <snuggyfoo> adrenaline_ I figured out I can do ssh user@domain 'command1; command2'
[22:18] <snuggyfoo> thanks though :)
[23:07] <xubuntu634> hola. Instale un xubuntu en mi maquina y me dejaron de funcionar los parlantes de mi cpu


[19:40] <Tumie> how's the UWN this week?
[19:40] <tyche> Clost to done
[19:40] <Tumie> say it when he's ready :)
[19:40] <johnc4510-laptop> k
[20:12] <LirazSiri> good evening fellow Ubunteros!
[20:18] <johnc4510-laptop> hey, are you out of the edit now?
[20:18] <johnc4510-laptop> :)
[20:19] <johnc4510-laptop> LirazSiri: ^^^^?
[20:19] <LirazSiri> no I'm in the middle of an edit
[20:19] <LirazSiri> I'm rewriting the section on ubuntu-fr. It really needs the work
[20:20] <LirazSiri> just a couple of minutes
[20:20] <johnc4510-laptop> was just getting to that
[20:20] <johnc4510-laptop> but go ahead
[20:25] <LirazSiri> alright I'm out of the edit (reading and taking down notes for things to correct in my next edit session)
[20:26] <johnc4510-laptop> k, i'm just starting on the proof reading now
[20:43] <LirazSiri> The OpenSolaris bit "in other news" has nothing to do with Ubuntu. Ubuntu seems to be mentioned only as an artificial instrument to drum up interest...
[20:44] <LirazSiri> I hate it when PR plants try to manipulate readership like that...
[20:44] <LirazSiri> should we really be covering this?
[20:49] <johnc4510-laptop> sorry, i'm not down that far yet
[20:50] <johnc4510-laptop> and i really need to be in the edit to finish up if possibly
[20:50] <johnc4510-laptop> thx
[20:50] <LirazSiri> alright, I'm done
[20:50] <johnc4510-laptop> k
[20:50] <johnc4510-laptop> thx
[20:50] <LirazSiri> gotta run, cheers
[20:50] <johnc4510-laptop> cya
[21:33] <johnc4510-laptop> Tumie: ping
[21:33] <Tumie> thanks
[21:33] <johnc4510-laptop> it's ready for you now
[21:33] <johnc4510-laptop> np
[21:33] <johnc4510-laptop> thx for your patients
[21:34] <johnc4510-laptop> Tumie: btw, we won't be publishing an issue right after xmas
[21:34] <johnc4510-laptop> next wk as usual, the following we'll skip
[21:34] <Tumie> ok,
[21:34] <Tumie> so,, next sunday, no issue :)
[21:35] <johnc4510-laptop> no
[21:35] <johnc4510-laptop> next sunday there will be an issue
[21:35] <johnc4510-laptop> the following wk there won't
[21:35] <johnc4510-laptop> ok?
[21:36] <johnc4510-laptop> Tumie: ^^^^^^^^^^
[21:37] <Tumie> :P
[21:37] <johnc4510-laptop> k
[21:37] <Tumie> sunday the 28th,, no issue :p
[21:37] <johnc4510-laptop> right
[21:37] <johnc4510-laptop> :)
[21:38] <Tumie> next sunday starts my christmasvacation,, so i wass a little confused..
[21:38] <Tumie> but it comes at the right time.. 30th december i have an operation..
[21:41] <johnc4510-laptop> ah, good luck with that
[21:41] <johnc4510-laptop> hope it works out ok
[21:41] <johnc4510-laptop> we'll be thinking of you
[21:43] <Tumie> it's just something with my toe..
[21:44] <Tumie> it's my left big toe,, the right already had the operation and it's oke now :)
[21:44] <Tumie> google translate says: "inflamed toe"..
[21:44] <Tumie> but i'm going to sleep now..
[21:45] <Tumie> bye
[21:55] <johnc4510-laptop> new issue of the Ubuntu Weekly Newsletter is out: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue121


[04:19] <miken> I've just pulled the snappy-examples and built the hello-world, but get a bunch of errors and warnings about files which don't exist: http://paste.ubuntu.com/11488439/ Is that expected, or related to my env?
[04:20] <miken> (it does build the snap, but unsure why I see those errors/warnings)
[07:28] <dholbach> good morning
[07:40] <fgimenez> hi mvo, i'm trying the examples at https://code.launchpad.net/~snappy-dev/snappy-hub/snappy-examples
[07:40] <mvo> hey fgimenez, good morning
[07:41] <fgimenez> mvo, morning :)
[07:41] <fgimenez> mvo, on rolling/edge i'm getting the same aa_change_on_exec error you just reported for every snap
[07:42] <mvo> fgimenez: yeah, please use 15.04/edge for now, the rolling images are literally only ~30min old :) I enabled wily this morning on them and this was the first bug I noticed
[07:42] <mvo> fgimenez: I have not investigated further but it appears the apparmor profiles are not created
[07:42] <fgimenez> mvo, ok thx :) on 15.04/stable i'm getting this http://paste.ubuntu.com/11491522/ when trying to use the config hook, have you seen that before?
[07:43] <fgimenez> mvo, in the config-example snap
[07:44] <fgimenez> mvo, didn't try 15.04/edge though, doing it now
[07:44] <mvo> fgimenez: does the directory /var/lib/apps/config-example/1.0.6  exist?
[07:44] <mvo> fgimenez: it does not ring a bell, I will have to install/test in a VM to debug further
[07:45] <fgimenez> mvo, no, the one that exists includes the origin /var/lib/apps/config-example.sideload/1.0.6
[07:52] <dholbach> mvo, ogra_, asac: http://ubucon.de/2015 :)
[07:52] <mvo> woah, berlin
[07:55] <dholbach> the cfp has started and they'd be happy if we could talk about all the new stuff we're doing and maybe do a workshop or two
[07:57] <mvo> fgimenez: aha, thanks. thats the bug then, the .sideload is not taken into account :/
[07:57] <mvo> fgimenez: would you mind to file a short bug (this irc log is enough) so that its not forgoten?
[07:57] <mvo> fgimenez: should be easy to fix :)
[07:57] <fgimenez> mvo, of course thx :)
[08:08] <elopio> good morning.
[08:25] <davidcalle> Morning all
[08:33] <beowulf> morning
[09:04] <D_Cent> hi - i have trouble connecting to wi-fi with snappy ubuntu on a raspi2. i followed the wifi tutorial and installed the wireless-tools, etc. but if i connect the wifi dongle via usb, dmesg only shows that a new device was connected without loading any drivers or firmware. the interface wlan0 or similar also doesn't exist. how can i make it work? i had it running previously on an older image, so it should be working
[09:06] <JamesTait> Good morning all; happy Monday, and happy Say Something Nice Day! 😃
[10:43] <ogra_> mvo, beuno, hulp ! ... can one of you let chatroom through ? seems the review tools seem to be messed up ("ports is pbsolete in package.yaml")
[10:43] <ogra_> *obsolete
[10:52] <beowulf> ogra_: do you need this asap?
[10:52] <ogra_> beowulf, mectors does i think ... i'm just trying an upload with changed ports directive though
[11:07] <ogra_> mvo, could you take a look at https://myapps.developer.ubuntu.com/dev/click-apps/1526/ ?
[11:08] <ogra_> i dont get why it spits out the two warnings (my snap overview page tells me 0.1-8 is published btw ... only the details page tells me it isnt)
[11:18] <zyga> can I freely change the hostname of a snappy core system?
[11:36] <beuno> om26er, on it
[11:36] <beuno> er
[11:36] <beuno> ogra, on it
[11:36] <beuno> (who is not in the channel :))
[12:06] <mvo> ogra_: hi, you can ignore those warnings for now, we need to stop generating those .snappy-systemd files, they are no longer needed
[12:06] <beuno> ogra_, I approved it
[12:07] <beuno> the fix is on the store side
[12:07] <beuno> I have it pending
[12:07] <ogra_> beuno, ok, thanks ... if now the snap would actually work :/
[12:07] <ogra_> beuno, btw, where do i file store bugs ?
[12:08] <beuno> ogra_, https://bugs.launchpad.net/software-center-agent/
[12:08]  * ogra_ has 5 pairs of identical mails for the last uploads ... no mention which version which mail belongs to
[12:09] <ogra_> and my front apps page said the whoile time that 0.1-8 was accepted
[12:09]  * beuno nods
[12:10] <ogra_> now why the heck does the chatroom not work anymore :/
[12:23] <sergiusens> ogra_: maybe seccomp
[12:23] <ogra_> sergiusens, hmm, i dont see any special messages about syscalls
[12:24] <ogra_> what i see is:
[12:24] <ogra_> Jun  1 12:23:01 localhost kernel: [ 2188.201850] audit: type=1400 audit(1433161381.662:146): apparmor="DENIED" operation="open" profile="chatroom.sideload_chatroom_0.1-8" name="/" pid=2356 comm="nodejs" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[12:24] <ogra_> but that has always been there
[12:24]  * ogra_ has an old install around that works fine on an old snappy
[12:24] <sergiusens> ogra_: why would you want to read / anyways ;-)
[12:24] <ogra_> node does for whatever reason
[12:24] <sergiusens> ogra_: amd64 or armhf, I can try and install to see
[12:25] <ogra_> but that never did any harm
[12:25] <ogra_> this is currently amd64
[12:25] <ogra_> in kvm
[12:25] <Chipaca> mvo: any luck reproducing the issue wrt install not working?
[12:25] <ogra_> my RPi is using a messed up image because i try to fix it :P
[12:26]  * ogra_ tries an older node-snapper tarball
[12:29] <mvo> Chipaca: no, but I didn't try further, sorry, I will try again in a little bit
[12:30] <sergiusens> ogra_: the one on the store works fine on 1.8
[12:30] <sergiusens> ogra_: err
[12:30] <Chipaca> sergiusens: does 'snappy install' work for you in a vm?
[12:30] <sergiusens> ogra_: the one on the store, 1.8, works fine on bbb
[12:30] <ogra_> ARGH !!!
[12:31] <ogra_> sergiusens, because i'm the super idiot today
[12:31]  * ogra_ tested with firefox :P
[12:31] <sergiusens> ogra_: no binary for amd64?
[12:31] <ogra_> (only works with chromium)
[12:31] <ogra_> sure, it is multi arch
[12:32] <sergiusens> ogra_: ah, I tried on chrome fwiw
[12:32] <ogra_> yeah, man, i wasted 2h on that :/
[12:34]  * ogra_ adds that info to readme.md for next time :P
[12:36]  * ogra_ takes a break, phew ...
[12:39]  * Chipaca realises he hasn't updated in ages
[12:45] <rsalveti> hm, our builders are in a funny state
[12:48] <ogra_> rsalveti, which ones ? images ?
[12:48] <rsalveti> normal lp builders
[12:48] <rsalveti> some are busy with the haskell uploads
[12:48] <rsalveti> but at our ppa all I get is 'start on'
[12:48] <rsalveti> no estimation at all
[12:50] <ogra_> hmm
[12:50] <rsalveti> like https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+build/7492026
[12:51] <rsalveti> mvo: hm, ubuntu-snappy is also ftbfs on i386 for vivid
[12:51] <rsalveti> https://launchpadlibrarian.net/207810741/buildlog_ubuntu-vivid-i386.ubuntu-snappy_1.0.1-1%2B443~ubuntu15.04.1_BUILDING.txt.gz
[12:51] <ogra_> yeah, i just saw the mail
[12:51] <mvo> rsalveti: I noticed but couldn't make sense of the failure yet
[12:52] <ogra_> rsalveti, for the hanging build we should poke cjwatson i think
[12:52] <ogra_> oh, thats a different error ...
[12:52]  * ogra_ had some with dependency issues on the weekend
[12:52] <rsalveti> ogra_: yeah, let's wait a bit more and ping him if still stuck
[12:52] <ogra_> yup
[12:53] <rsalveti> yeah, why TestUpdateTimestamp would fail
[12:54] <rsalveti> wonder if a rebuild will make any difference
[12:55] <ogra_> 2015-05-30 02:46:51 ERROR snappy logger.go:199 hello-app.potato failed to install: a package by that name is already installed
[12:55] <ogra_> what about that one ?
[12:55] <rsalveti> wonder if that is testing the error itself
[12:55] <ogra_> does it re-run the test in a loop or some such ?
[12:55] <rsalveti> since the test passed
[12:55] <ogra_> ah
[12:56] <rsalveti> just a guess, didn't yet see the code :-)
[12:56] <rsalveti> let me open a bug for this guy
[12:56]  * ogra_ sighs ... i upgraded my laptop to vivid on the weekend ... got close to unusable now :(((
[12:57] <ogra_> constantly to hot (80-90°C)
[13:01] <rsalveti> https://bugs.launchpad.net/snappy/+bug/1460650
[13:01] <rsalveti> ogra_: any process in particular eating your cpu?
[13:01] <rsalveti> maybe new browsers
[13:01] <ogra_> no, not at all
[13:02] <rsalveti> vivid is mostly fine for me
[13:02] <ogra_> but starting chromium with no page open bumps the load to 12.00 ... while chromium only takes ~20% of one of the cpu cores (the rest is idle)
[13:02] <ogra_> the frequesncy scaling seems pretty messed up
[13:10] <mterry> mvo, you should open up ownership of lp.net/ubuntu-core-launcher
[13:10] <mterry> Wanted to configure its bug tracker to show its bugs (right now I can't see bugs assigned to it because it's not set up)
[13:10] <sergiusens> nessita: what's the difference between price and prices, if the answer is, 'price' is legacy it's a good answer already :-)
[13:11] <Chipaca> so
[13:11] <Chipaca> on my system
[13:11] <sergiusens> mterry: I just ubuntu bug'ed it
[13:11] <Chipaca> snappy is bailing because it can't read /etc/localtime?
[13:11] <Chipaca> ah, no, it's before that
[13:11] <Chipaca> rats
[13:11] <nessita> sergiusens, correct! (price is legacy and is the price for the default currency(
[13:11]  * Chipaca carries on
[13:11] <nessita> __
[13:11] <nessita> ))
[13:11] <mterry> sergiusens, you did...?
[13:12] <rsalveti> mvo: mterry: just put ubuntu-core-launcher under https://launchpad.net/~snappy-dev
[13:12] <mvo> rsalveti: excellent, thanks
[13:13] <Chipaca> i don't understand this failure :(
[13:17] <ogra_> BAH ... i seem to have half a mobile desktop installed ... no wonder that laptop misbehaves !
[13:21] <rsalveti> mvo: oh, sorry, I wanted to say that you could put it under ~snappy-dev :-)
[13:21] <rsalveti> only you can change it
[13:23] <sergiusens> nessita: I did.... nothing?
[13:23] <mvo> rsalveti: ups, sure
[13:23] <sergiusens> Chipaca: what's the issue?
[13:23] <sergiusens> Chipaca: btw, can you review my u-d-f change?
[13:23] <Chipaca> sergiusens: snappy internal unpack dies with "operation not supported"
[13:24] <Chipaca> and the strace shows no syscall failure
[13:24] <sergiusens> Chipaca: amd64 or bbb?
[13:24] <Chipaca> sergiusens: mad64
[13:24] <mvo> rsalveti: updated, the project is now owned by ~snappy-dev
[13:24] <nessita> sergiusens, you meant mterry?
[13:24] <rsalveti> mvo: cool, thanks (mterry ^)
[13:25] <sergiusens> nessita: I did!
[13:25] <mterry> mvo, thanks!  :)
[13:25] <sergiusens> mterry: ubuntu-bug ubuntu-core-launcher
[13:25] <rsalveti> but that will use the package bug
[13:26] <sergiusens> rsalveti: yes
[13:28] <Chipaca> the setuid/setgid fails
[13:29] <Chipaca> the setgid, in particular
[13:29] <Chipaca> can i say WAT?
[13:29] <mvo> Chipaca: uh, hope its not something silly as setuid and then setgid :/ in this particular revision
[13:29] <mvo> (i.e. order wrog)
[13:29] <Chipaca> no, it does setgid and then setuid
[13:29] <mvo> wrong even
[13:29] <mvo> ok
[13:30] <Chipaca> and the setgid fails
[13:30] <Chipaca> this is beyond weird, because the snappy we ship works
[13:31] <mterry> mvo, I also see that someone subscribed snappy-dev to snappy bugs.  Maybe snapcraft and ubuntu-core-launcher should get the same treatment?
[13:33] <sergiusens> Chipaca: hmm, I face this problem when locally building snappy (I think)
[13:34] <rsalveti> mterry: I did that, yup, makes sense
[13:34] <mterry> rsalveti, thanks!
[13:35]  * Chipaca files bug #1460658
[13:35] <Chipaca> sergiusens: and how did you fix it?
[13:41] <sergiusens> Chipaca: I haven't, sorry
[13:50]  * Chipaca -> school run
[14:08] <sergiusens> nessita: can I use the 'id' for a package to get results for it?
[14:09] <sergiusens> nessita: as in using 2277 (id) instead of https://search.apps.ubuntu.com/api/v1/package/beagleblack
[14:13] <nessita> sergiusens, nopes, ID is retured by mistake,never rely on that
[14:27] <mvo> jdstrand: do you know why livecd-rootfs uses the "-M /var/cache/apparmor/.features" flag in ubuntu-touch? this file is not available in our chroot it seems
[14:30] <sergiusens> nessita: so the resource name is always the package_name.origin or alias, correct?
[14:30] <jdstrand> mvo: what is -M an argument to?
[14:30] <mvo> jdstrand: apparmor_parser -M (--features-file) I think
[14:31] <mvo> jdstrand: I'm not sure why its there for touch when they pre-build the /etc/apparmor.d/cache
[14:32] <jdstrand> ah, that is not in the manpage it seems
[14:32] <mvo> yes, I only found it with apparmor_parser -h and have no idea what its doing
[14:33] <jdstrand> mvo: iirc, if you specify a different --cache-loc (-L), then you need to have a .features file in it
[14:33] <mvo> ok
[14:34] <jdstrand> since there is /etc/apparmor.d/cache for system and /var/cache/apparmor for apps, we have a .features file in both
[14:34] <ogra_> echo "I: precompiling click apparmor policies"
[14:34] <ogra_> /sbin/apparmor_parser -M ${FEATURES} -Q --write-cache --cache-loc=/var/cache/apparmor/ `find /var/lib/apparmor/profiles/ -maxdepth 1 -type f -not -path '*/\.*'`
[14:34] <ogra_> (thats from the code)
[14:34] <ogra_> looking in the last image build log it seems to run fine without complaints
[14:34] <ogra_> (touoch that is)
[14:35] <jdstrand> perhaps it is putting a .features file in place so that the compiler will use it instead of querying the kernel?
[14:35] <ogra_> https://launchpadlibrarian.net/207811375/buildlog_ubuntu_wily_armhf_ubuntu-touch_BUILDING.txt.gz
[14:35] <ogra_> i wouldnt know what would put that file there
[14:35] <jdstrand> I think rsalveti and/or jjohansen would know
[14:36] <jdstrand> I know that a .features file is put in place on the running system in each cache directory
[14:36] <jdstrand> the running non-livecd system that is
[14:36] <mterry> tedg, we should try to define a minimal set of snapcraft bits that we think we can move forward with this week
[14:37] <ogra_> jdstrand, what puts it there ? the upstart job ?
[14:37] <jdstrand> and I know you can specify a different features file to adjust cache output
[14:37] <jdstrand> so you could compile caches for another kernel
[14:38] <ogra_> there is definitely no code in livecd-rootfs putting that file in place
[14:38] <ogra_> and i doubt it actually exists in the chroot after bootstrapping
[14:39] <nessita> sergiusens, yes
[14:42] <jdstrand> I'm not sure. I think the parser might
[14:42] <tedg> mterry, Yes, I haven't looked at the current code. I would like to get some stuff starting to work-ish
[14:42] <tedg> mterry, I think we can do that even if all the spec parts aren't perfected.
[14:43] <jdstrand> yes
[14:43] <jdstrand> If cache/.features is missing, create it if --write-cache
[14:44] <mterry> tedg, current code is an empty branch
[14:45] <jdstrand> I'm still going to defer to jjohansen
[14:45] <ogra_> that makes it at least bugfree
[14:45] <tedg> mterry, tabula rasa
[14:45] <ogra_> jdstrand, well, it doesnt seem to do any harm
[14:45] <ogra_> (not sure what mvo's prob is with it)
[14:51] <Chipaca> sergiusens: mvo: it fails when compiled with golang 1.4 (!)
[14:52] <Chipaca> mvo: does this match the failures you were seeing in arm64?
[14:52] <Chipaca> or gogcc
[14:53] <Chipaca> maybe i just need to rebuild my go 1.4
[14:53] <Chipaca> or switch to wily already
[14:53] <mvo> Chipaca: ohhhh, I have not tried that
[14:53] <mvo> Chipaca: in a meeting right now :/ so can't help just yet
[14:53] <Chipaca> mvo: is this the "15.04.1 release" meeting?
[14:54] <mvo> Chipaca: yes, I almost missed it fighting with gccgo
[15:00] <sergiusens> Chipaca: right, I'm using 1.4 here (locally installed)
[15:01] <Chipaca> sergiusens: vivid's 1.3 worked
[15:02] <Chipaca> sergiusens: locally installed 1.3 also works
[15:25] <Chipaca> I guess I won't be running snappy on my http://wiki.openwrt.org/toh/kingston/mlw221 any time soon
[15:27] <mvo> 16mb flash is going to be hard
[15:28] <ogra_> pfft
[15:29] <ogra_> just write a proper compression that allows pushing 4G into 16M ...
[15:30] <mvo> 4gb of /dev/zero surely
[15:33] <Chipaca> mvo: so, the manifest branch is the one causing the apparmor failures
[15:44] <mvo> Chipaca: the reduce-manifest one?
[15:44] <Chipaca> mvo: yaarp
[15:44] <mvo> ok
[15:46] <elopio> fgimenez: tomorrow I can escape at 11:30, london time.
[15:46] <Chipaca> mvo: still trying to understand why, but i'll get there :)
[15:46] <tedg> Where are the package lists for the default core image?
[15:46] <tedg> seed I guess?
[15:47] <tedg> Is it this? https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu-core.wily
[15:51] <fgimenez> elopio, fine, that is 10:30 my time. i'm already taking a look at the doc
[15:51] <fgimenez> elopio, ping me when you are ready
[15:53] <jdstrand> mvo, Chipaca: if I were to hazard a guess, I would think it has something to do with the 'namespace' changes in click.go
[15:54] <Chipaca> jdstrand: nope :)
[15:54] <jdstrand> oh, what is it?
[15:57] <elopio> fgimenez: great, thanks.
[16:00] <Chipaca> jdstrand: in revision 465 i switched some bits to use the yaml manifest instead of the click manifest
[16:01] <Chipaca> jdstrand: without noticing that things that appeared equal were not so
[16:02] <Chipaca> in my defence, in build we assign the click manifest's Hooks to be the yaml's Integration
[16:03] <Chipaca> but before doing that we do add some things to Integration that are not in the package.yaml
[16:04] <Chipaca> so, I *think* what we want is to grow Integration in the same way every time we load it
[16:05] <Chipaca> I need to check though :)
[16:17] <jdstrand> mvo: fyi, and this doesn't have anything to do with snappy internals, I have adjust the review tools to error if a snap uses 'integration' in its yaml
[16:17] <jdstrand> adjusted*
[16:58] <jdstrand> sergiusens: hey, I'm reflashing my bbb, is udf 0.21-1+174~ubuntu15.04.1 ok to use?
[17:09] <sergiusens> jdstrand: let me check
[17:11] <sergiusens> jdstrand: yes
[17:18] <tedg> So, I thought I'd go to the docs, didn't find my answer there either :-)
[17:18] <tedg> Where is the script/tool/etc that builds the core snap?
[17:19] <jdstrand> sergiusens: thanks
[17:19] <jdstrand> df
[17:19] <tedg> 1243 GB
[17:20] <ogra_> 640k are enough for everyone !
[17:20] <jdstrand> heh
[17:31]  * ogra_ upgrades ubuntu-device-flash
[17:31]  * jdstrand hrms
[17:33] <jdstrand> rsalveti, mvo: hello-dbus-app is broken on edge r72. is this the candidate for promotion?
[17:33] <jdstrand> rsalveti, mvo: (on bbb)
[17:46] <damjan> what would it take to port UbuntuCore to the Kindle Paperwhite
[17:49] <ogra_> damjan, depends what bootloader it uses ... if the specs would work etc
[17:50] <damjan> hardware specs?
[17:50] <ogra_> yes
[17:51] <ogra_> you need 4G diskspace and the ability to partition it the right way... we currently only support u-boot on arm as bootloader ...
[17:53] <damjan> it's an 1Ghz imx 508
[17:53] <damjan> 256MB ram
[17:53] <damjan> there's the 2GB and 4GB flash versions
[17:53] <ogra_> that might eb a little low on ram ... but givenn that there is no UI support in any way yet, perhaps not
[17:54] <ogra_> (i guess for plain cmdline 256M would work)
[17:56] <damjan> afaik it's u-boot
[17:56] <damjan> why does it matter btw?
[17:57] <ogra_> because the automation for rollbacks lives in the bootloader
[17:57] <ogra_> (if you upgrade and something goes wrong the system automatically rolls back to the last working setup)
[18:00] <damjan> it's uboot
[18:43] <jdstrand> rsalveti, mvo: fyi, there is a trello card to add hello-dbus-* to the self tests. if is in 'snappy core stackholders backlog' 'incoming propposals'. I just now added instructions on what to do (should be a very simple test)
[18:43] <jdstrand> rsalveti, mvo: s/if is/it is/
[19:34] <rroy> Trying to do basic install of docker app on snappy.    Installation completes w/o error however a simple `docker ps` fails:
[19:34] <rroy> ubuntu@localhost:~$ sudo snappy install docker Installing docker Starting download of docker.canonical 8.36 MB / 8.36 MB [[19:34] <rroy> Ugh ... sorry about the formatting.
[19:36] <rroy> As you can see the complaint is regarding a missing "profile" file.    I'm guessing I can get away w/ an empty profile file but ... what is the file name/location?
[19:50] <kgunn> seb128: you around ?
[19:51] <seb128> kgunn, yes
[19:56] <rsalveti> jdstrand: ogra_: we only have the features file for touch
[19:56] <rsalveti> ubuntu-touch/includes.chroot/var/cache/apparmor/.features
[19:57] <rsalveti> so I'd guess the pre-cached apparmor stuff is kind of useless for core atm
[19:58] <rsalveti> jdstrand: broken on 15.04/edge?
[20:00] <jjohansen> rsalveti: that does sound broken
[20:05] <jdstrand> rsalveti: yes, r72
[20:06] <jdstrand> rsalveti: I think it is surrounding the unshare in the launcher because I am getting a disconnected path apparmor denial
[20:07] <rsalveti> jdstrand: and thanks for updating the card, will move it around later today
[20:07] <jdstrand> but it is weird, because it is on run/
[20:07] <rsalveti> but iirc it was working a few days ago
[20:07] <jdstrand> rsalveti: cool, thanks
[20:07] <jdstrand> I wonder what landed
[20:07] <rsalveti> now don't remember if that was indeed stable or edge
[20:07] <jdstrand> do we have a clear way to see what has changed?
[20:08] <rsalveti> not an easy way, no, ogra_ was working on that
[20:08] <rsalveti> we only got the manifest, but from a few images
[20:08] <jdstrand> I just reflashed my bbb today with edge and got this denial: audit(1433179950.388:19): apparmor="DENIED" operation="connect" info="Failed name lookup - disconnected path" error=-13 profile="hello-dbus-app.canonical_client_1.0.1" name="run/dbus/system_bus_socket" pid=1215 comm="dbus_message.ar" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0
[20:09] <jdstrand> notice 'name=run/...'
[20:09] <jdstrand> that should have a '/' in front of it
[20:09] <rsalveti> indeed
[20:09] <jdstrand> so, we knew we would need to adjust the apparmor template to use 'attach_disconnected'
[20:09] <jdstrand> and in fect, that is done in wily
[20:10] <jdstrand> fact*
[20:10] <jdstrand> but, I wasn't expecting this on 15.04, so I'm curious about the changes that went in
[20:14] <jdstrand> rsalveti: so, the launcher hasn't changed in vivid...
[20:15] <jdstrand> rsalveti: ah, 1.0.2~ppa1 is on the image
[20:16] <rsalveti> right
[20:16] <jdstrand> rsalveti: 'Set up a private mount namespace for /tmp'
[20:16] <jdstrand> so, this means we need a policy update
[20:16] <rsalveti> we use vivid + https://launchpad.net/~snappy-dev/+archive/ubuntu/image
[20:17] <jdstrand> yep, that is where I'm looking
[20:17]  * jdstrand sees the old unused libseccomp and deletes it
[20:18] <rsalveti> also noticed we're over the repo size limit in there
[20:18] <rsalveti> maybe because of gcc
[20:18] <jdstrand> oh yeah
[20:19] <jdstrand> rsalveti: so, at this point there is a choice, pull the launcher or have me do a policy update. I'm fine with doing an ubuntu-core-security update-- I can do it tomorrow. this was the other part of the sru I was talking about
[20:19] <jdstrand> rsalveti: but if we go that route, you should block the promotion on that
[20:20] <rsalveti> yeah
[20:20] <rsalveti> jdstrand: that same version is also available in wily (core-launcher)
[20:20] <rsalveti> so I guess we'd need a policy update for both
[20:20] <jdstrand> rsalveti: wily has 1.0.2
[20:21] <jdstrand> wily already has the policy update
[20:21] <rsalveti> got it
[20:21] <jdstrand> 15.10.1 has: "add attach_disconnected for default policy in preparation of new /tmp
[20:21] <jdstrand>       handling"
[20:22] <rsalveti> guess it'd be fine to get this in the ppa and then work on getting the official src in place
[20:22] <jdstrand> that is what I was thinking
[20:23] <rsalveti> cool
[20:23] <rsalveti> jdstrand: do we have a bug for this already?
[20:23] <rsalveti> just so I can put at the milestone
[20:24] <jdstrand> no
[20:24] <jdstrand> I'll file one
[20:24] <rsalveti> awesome, thanks
[20:26] <jdstrand> rsalveti: bug 1460810
[20:27] <rsalveti> jdstrand: thanks
[21:06] <jdstrand> rsalveti: fyi, ubuntu-core-security - 15.04.12~ppa1 uploaded to the ppa
[21:06] <rsalveti> jdstrand: awesome, thanks for that
[21:07] <jdstrand> np
[21:07] <rsalveti> got the extra ppa space just in time
[21:33]  * Chipaca looks at sys/unix/syscall_linux_arm64.go
[21:33]  * Chipaca goes to bed
[21:56] <nessita> sergiusens, so, I have this item to sync with you, about snappy oauth-signing every single request to the index. Any pointers who should I ping about this?
[22:20] <Chipaca> nessita: for snappy?
[22:28] <beowulf> Chipaca: is your snap removed from the store?
[22:28] <Chipaca> beowulf: unpublished
[22:28] <Chipaca> beowulf: should i republish?
[22:28] <Chipaca> people seemed to not like it being there
[22:28] <beowulf> Chipaca: no, it exposed some wonderful errors :)
[22:28] <Chipaca> hee hee :)
[22:29] <beowulf> Chipaca: so i was using it in webdm, then it was unpublished, then i tried to uninstall...
[22:29] <Chipaca> beowulf: webdm doesn't like things disappearing from the store?
[22:29] <beowulf> Chipaca: no sir
[22:29] <Chipaca> *shock*
[22:29] <beowulf> Chipaca: i'm wondering if the store should dissappear metadata, or should webdm handle it, or should i go to bed
[22:30] <beowulf> i think the latter
[22:30] <Chipaca> jdstrand: is https://01.org/intel-kgt relevant to us?
[22:30] <Chipaca> beowulf: the magic 8-ball says "go to bed already"
[23:56] <sergiusens> Chipaca: beowulf this is a similar error to the offline case; I need to fix it
[23:58] <sergiusens> nessita: how soon is that timeline? I think you want to sync with beuno first on the whole concept for ssl/tls


 I don't think IRC can see telegram messages (re @guiverc: Lubuntu is a Ubuntu flavor, so all mirrors are just Ubuntu mirrors.)
[02:19] <thedoctar> Oh I guess they can!
[02:19] <arraybolt3> alzhou10: IRC guy here, I can see it just fine.
[02:20] <arraybolt3> (There's a Telegram-to-IRC bridge here set up specifically for the #lubuntu channel IIUC.)
[02:21] <arraybolt3> And there's also an IRC-to-Matrix bridge, so since a Telegram message creates an IRC message, that will also create a Matrix message, so anyone on any supported chat program can see all the messages.
[02:23] <teward[m]> alzhou10 and thedoctar: yes, Telegram to IRC bridge is bidirectional.  There's also an IRC-Matrix bridge bot handled by things that also relay to Matrix clients
[02:23] <teward[m]> as arraybolt3 said.  (teward[m] indicates my matrix client connected via IRC)
[02:23] <teward[m]> (but you will also see teward on the IRC bridge side, and teward001 onthe Telegram side, depending which clientI'm working with at the moment LOL)
[02:24] <thedoctar> Technology these days... amazing!
[02:24] <arraybolt3> teward[m]: All our messages may be getting missed on Telegram - lubot is having some connection problems.
[02:24] <teward[m]> that'dbe because i had a pfSense HA event
[02:25] <teward[m]> primary went unresponsive, secondary kicked in, then primary cameback up a bit later, and switchedback
[02:25] <arraybolt3> Oh. No clue what that means but it sounds bad.
[02:25] <teward[m]> i'll punt the client
[02:25] <teward[m]> HA means High Availability
[02:25] <teward[m]> i.e. redundancy
[02:25] <arraybolt3> Oh nice.
[02:25] <teward[m]> if the primary firewall (pfSense) goes down, I have a second pfSense VM with a config sync on it to come online in that event
[02:25] <teward[m]> and when the first comes back it puts the second into standby
[02:25] <teward[m]> so ye i'll punt the bot shortly
 bot's punted and i see the flood here on Telegram
[02:29] <teward[m]> just like i see it here on Matrix and IRC
[02:29] <teward[m]> returns to the shadows
 theonly thing I don't like about matrix is it doesn't send asterisks >.<
[02:31] <teward> ... well it did here, interesting.
[02:32] <teward> unless...... that's just hte Telegram bridge being stupid...
 *shrugs* I'll figure that out later.
 bot's back for now
[02:33] <arraybolt3> Glad it's working.
[02:34] <arraybolt3> (Matrix turns * into italics if you have two of them.)
[02:34] <arraybolt3[m]> Like this.
[02:34] <arraybolt3> The astrisks aren't showing up on IRC either.
[02:34] <arraybolt3> s/astrisks/asterisks/
[02:37] <teward[m]> i think i just disabled markdown and rich so that might just send normal
[02:37] <teward[m]> i'm in the middle of poking something anyways
[02:39] <arraybolt3[m]> *does this work?*
[02:39] <arraybolt3> Yep, works. I used the /plain command first.
[02:40] <arraybolt3> (So it was "/plain *does this work?*")
[03:18] <f73> sorry i quit
[03:18] <f73> lubuntu box icons ppa for jmy
[10:08] <Tiber> if i turn SATA IDE Combined Mode off in bios i can't find bootable driver
[10:34] <tomreyn> Tiber: then i huess you better keep it on
[10:37] <tomreyn> https://forums.anandtech.com/threads/what-is-sata-ide-combined-mode.2263780/ "I figured that out through trial and error. What it does, if you enable it, I believe, is to make AMD SATA6G port 4 and 5, act like IDE ports. If you disable it, all six AMD SATA6G ports act as native SATA ports."
[10:37] <tomreyn> another instance of "i came up with this awesome label which no one will understand what it means"
[10:43] <Tiber> some how i member when i got linux last time on that laptop i turned that off and then that ssd worked right
[15:46] <Tiberi> damn i don't have any ideas what should i do with my sdd


[01:31] <phillw> tsimonq2: ping ...
[01:37] <tsimonq2> phillw: what?
[01:41] <phillw> tsimonq2: can you crawl over https://wiki.ubuntu.com/XenialXerus/Beta2/Lubuntu and compare to https://wiki.ubuntu.com/XenialXerus/ReleaseNotes/Lubuntu and correct the latter one to where we currently are at? Thanks
[01:42] <tsimonq2> I reviewed all the bugs on Sunday...
[01:42] <tsimonq2> you have a list of the bugs I confirmed
[01:43] <phillw> tsimonq2: I may have, but the release notes do not... So, would you please update it :)
[01:45] <phillw> it is a balance to let people know of an issue that may bite them on the bum when installing / upgrading .. and not spook new people out who see a list of the hundreds of bugs in ubuntu and run away :)
[01:50] <phillw> tsimonq2: and then next time you are bored, have a read of https://wiki.ubuntu.com/Lubuntu/Developers/PrePostReleaseTODO and chase up the other 3 pages as where needed. I have some edits to make, from emails about specific stuff that I'm happy to forward to you so that we are in sync..
[02:41] <phillw> wxl: now that we have a devel ML, I will ensure in future that any emails from me to Julien are cc'd to that ML as well. This should ensure there is no mis-communication in the future.
[23:52] <tsimonq2> for people reading the logs: https://lists.ubuntu.com/archives/lubuntu-devel/2016-April/000352.html
[23:52] <tsimonq2> I have a Lubuntu Xenial Daily Live amd64 image, 20160409
[23:53] <tsimonq2> confirmed that AbiWord is installed
[23:55] <tsimonq2> bug 1432271 is a Unity-only bug, it seems
[23:55] <tsimonq2> confirmed bug 1484785 is still present


[03:15]  * guiverc started scanning gdoc.. I thought i was going crazy.. first two summaries I could make no sense of...  finally realize they're not english.. alas I'm outta time for now.
[03:18] <Bashing-om> guiverc[m]: LOL - we still have time for the proofing - ^ Portuguese :D
[03:18] <Bashing-om> guiverc: LOL - we still have time for the proofing - ^ Portuguese :D
[03:20]  * guiverc got offer to go elsewhere for family lunch... that beats here on computer & whatever I make etc..
[03:21] <Bashing-om> guiverc: Quality time is family time :D
[13:58] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: Four Challenges for ML data pipeline @ https://ubuntu.com//blog/four-challenges-for-ml-data-pipeline
[20:40] <Bashing-om> UWN: Issue782 up for review and final edits: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue782 :D
[21:27] <krytarik> Bashing-om: "(p-pisati )" - there is an excess space here, also I'd maybe just call it "DKMS uploader" or "DKMS upload rights"
[21:28] <Bashing-om> krytarik: Missed that spare space .. and will make DKMS so :D
[21:32] <krytarik> "Ubuntu Portugal : Encontro Ubuntu-pt Abril @ Sintra - Festa de lançamento do Lunar Lobster" - I think "Ubuntu Portugal" is redundant here.. but why do we feature a link to a scheduled event in the LoCo section alongside what seems like the actual post about it?
[21:34] <Bashing-om> krytarik: My thought was to encouage the LOCOs to post their events of we give greater exposure.
[21:38] <Bashing-om> krytarik: Yup -- ^^ same same event(s) -- pulling that 1st one.
[21:41] <krytarik> Bashing-om: Doesn't seem like to me though, since both the date and location seem to defer..
[21:42] <Bashing-om> krytarik: Ouch - Good that you caught that - will but the article back in place :)
[21:43] <krytarik> Still though, I don't think we should just promote an item from the LoCo Events section to LoCo News without an actual post.
[21:49] <krytarik> Also, there is "UbuntuTeam" in the LoCo Events section that needs escaped.
[21:58] <Bashing-om> krytarik: The citation in question is but the monthly meeting - I now have no heartburn to pull that from the LoCo News section.
[22:13] <krytarik> What?  Camelcase etc etc..  But yeah, please drop the Sintra event from LoCo News.
[22:20] <Bashing-om> krytarik: Camel case addressed - and dropped Ubuntu-pt Abril @ Sintra . Next edits ?
[22:22] <krytarik> None from me.. thanks!
[22:23] <Bashing-om> guiverc: Easter Sunday: interruptions and thought processes not the best. Be good to have another look-see at what we will present.
[22:24] <guiverc> I'll look at wiki in due course (likely a couple of hours if okay)
[22:24] <Bashing-om> guiverc: Thanks - no hurry :P


[00:04] <akgraner> crap forgot In this issue  fixing that now
[00:04] <akgraner> DOH!
[00:07] <pleia2> I need to run some errands, then come back and work more (boo, overtime is no fun)
[00:13] <akgraner> no worries just fixed the In this issue :-)
[00:13] <akgraner> have fun
[00:33] <akgraner> ok everything but the Fridge is up :-)
[00:34] <akgraner> The new edition of the Ubuntu Weekly Newsletter is now available here:
[00:34] <akgraner> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue237
[00:34] <akgraner> thanks everyone!
[00:46] <akgraner> and it's on the Fridge now :-)
[01:50] <akgraner> ahhhh - I can't get the re-direct to redirect....for current release on the /UbuntuWeeklyNewsletter page
[01:51] <akgraner> I changed the current redirect page to issue 237 but it still shows up as 236 grrrrr
[01:57] <pleia2> akgraner: it's working, chrome just over-aggressively caches
[01:57] <pleia2> I test with an incognito window :)
[01:57] <akgraner> ahh ok
[01:57] <akgraner> whew I couldn't figure out what I was doing wrong
[02:21] <holstein> yeah, AFAIK, its wordpress
[02:22] <holstein> knome is helping ubuntustudio with a new site like the xubuntu and haiku ones
[19:38] <akgraner> pleia2, I'll start summarizing some of those thinks tonight
[19:38] <akgraner> other wise this weekend we will be busy busy busy
[19:39] <pleia2> ok great :)
[19:39] <pleia2> I'm just tossing in lots of news/blogosphere stuff, so feel free to prune/re-sort as needed
[19:39] <pleia2> and I'll actually be at home this weekend!
[19:39] <akgraner> yay - then get some rest you deserve it
[19:39] <pleia2> saturday is shockingly plan-free
[19:40] <akgraner> whoa that's a first in a while for you
[19:40] <pleia2> yeah
[19:40] <pleia2> we're flying out to orlando a few days early to do disney, so the two weekends after this are away too
[19:40] <akgraner> I went through canonical voices, canonical blog and the planet and added stuff as well
[19:40] <akgraner> oh cool :-)
[19:40] <pleia2> I wonder if we should propose having canonical add the canonical blog to planet
[19:41] <pleia2> maybe ask one of jono's community guys what they think
[19:41] <pleia2> (and if one of them would be the "owner" of it)
[19:41] <akgraner> I brought that up once...I forget who was opposed to it though
[19:41] <pleia2> ah
[19:41] <pleia2> we've got a fair number of project and even a corporate blog policy now
[19:41] <akgraner> b/c not all canonical bloggers are members
[19:42] <pleia2> do you remember how long ago this was?
[19:42] <pleia2> we now have team blogs feeding to planet and not all bloggers on those are members
[19:42] <jono> pleia2, I think the Canonical blog would be fine on planet, but I seem to remember some folks got rubbed up the wrong way when discussed
[19:42] <akgraner> it's been long enough for me to forget the deatils
[19:42] <pleia2> the canonical design blog is on planet now
[19:42] <pleia2> and it's awesome
[19:42] <jono> I would +1 the Canonical blog
[19:43] <jono> maybe we can raise it as an item for the next CC meeting
[19:43] <jono> I think the CC can evaluate this well
[19:43] <pleia2> jono: I'll add it to the agenda now
[19:43] <jono> thanks pleia2
[19:43] <jono> I am happy to own the topic in my team
[19:43] <akgraner> pleia2, I think the Canonical blog would be fine as well
[19:43] <akgraner> I mean we pull info for it all the time (speaking from the news team perspective not the CC one)
[19:44] <pleia2> yeah, and it would be nice to be able to add it to the planet section rather than the "other news" one :)
[19:44] <akgraner`> and my proxy just came back
[19:44] <akgraner`> yep
[19:46] <akgraner> pleia2, sorry was changing to my proxy - you said you were going or did add it to the CC agenda?
[19:46] <jono> akgraner, she added it
[19:46] <pleia2> I did
[19:46] <jono> :-)
[19:46] <akgraner> ahh ok
[19:46] <akgraner> thanks
[19:47] <akgraner> jono I subscribed to /BuildingCommunity.* looks like people are working on it already
[19:47] <jono> akgraner, indeed, great to see :-)
[19:48] <akgraner> I thought so too


[00:17] <supercool> I am trying to make a shared folder persistent as https://gist.github.com/estorgio/1d679f962e8209f8a9232f7593683265
[00:17] <supercool> The item 2 Add the following line to fstab (separated by tabs) and press Ctrl+O to Save.
[00:18] <supercool> As shared /home/<username>/shared vboxsf defaults 0 0
[00:18] <supercool> Is blocking the boot process
[00:18] <supercool> Any ideas what could be happening?
[00:20] <sarnold> supercool: sagrawal-idrc's comments seem likely to be in the right direction
[00:24] <supercool> sarnold: alright, checking it.
[07:57] <lordievader> Good morning
[08:03] <jamespage> coreycb, sahid: reminder to us all - when removing py2 support, remember to drop all maintainer scripts that deal with alternatives only.
[08:10] <sahid> jamespage: ack
[09:25] <friendlyguy> hi i am trying to get ubuntu 18.04.2 LTS to resolve .local hostnames
[09:41] <friendlyguy> its just ignoring my dns settings from netplan
[09:41] <friendlyguy> how can i make sure the nameservers i set in the netplan config are actually being used?
[09:42] <friendlyguy> netplan --debug apply show the correct nameservers
[09:43] <friendlyguy> but i cant resolv hostnames that have a .local domain
[09:43] <blackflow> btw, .local shouldn't be used outside of mDNS. iirc resolved would refuse resolving those
[09:46] <friendlyguy> well, not an option to change that
[09:47] <friendlyguy> i need to fix the server so its asking the dns server for those hostnames
[09:47] <blackflow> then you shouldn't be using systemd-resolved, if you're going against the standards and specs.
[09:47] <friendlyguy> i think its very common to have .local domains in ad
[09:49] <blackflow> .local is reserved for mDNS via RFC <number forgotten> so whoever is using .local for regular DNS is doing it wrong, "common" or not.
[09:49] <blackflow> your options are either to employ mDNS in your network for .local, or don't use systemd-resolved.
[09:51] <friendlyguy> okay, what do i need to do to remove systemd-resolved?
[09:53] <blackflow> stop the service, disable it, mask it. set up resolv.conf manually for your upstream resolver. unlink it first, as it's a symlink into /run/...
[09:54] <blackflow> oh also, iirc you shouldn't then use DNS config in netplan. I think that thing only talks to resolved. I'm not using netplan anywhere, so I can't test for you.
[09:54] <friendlyguy> what do you mean by "mask it"
[09:55] <friendlyguy> i disabled and removed the service, i removed the resolv.conf symlink
[09:55] <blackflow> `systemctl mask systemd-resolved.service`
[09:55] <blackflow> if you just disable it, other processes like netplan, NM, ...   can start it
[09:56] <friendlyguy> ah. thanks for explaining that
[09:56] <friendlyguy> i did it and saw a symlink to /dev/null was created
[09:58] <blackflow> right.
[10:01] <friendlyguy> okay, this looks much better
[10:01] <friendlyguy> ping to host works, ping to host.local works
[10:01] <friendlyguy> btw. interesting to read: https://en.wikipedia.org/wiki/.local
[10:02] <friendlyguy> there are examples for the "confusing" recommendations microsoft gave its customers
[10:02] <friendlyguy> i know plenty of HUGE (80000 servers+) domains that are on .local
[10:04] <blackflow> nothing wrong with .local if it's done via mDNS tho
[10:05] <friendlyguy> well, they are not :)
[10:08] <blackflow> gtg, good luck.
[11:38] <jamespage> coreycb: yuck - https://launchpadlibrarian.net/427745205/buildlog_ubuntu-eoan-amd64.python-oslo.log_3.44.0-0ubuntu3_BUILDING.txt.gz
[11:38] <jamespage> oslo.config -> oslo.log -> oslo.config
[11:49] <jamespage> nicely wedged
[12:06] <coreycb> jamespage: thanks for fixing that
[12:29] <Koopz> https://gist.github.com/Koopzington/dacef5d2b76890a5d2f6c386e9bf9124 would you say that HDD needs to be replaced after spamming syslog with those messages for about a week?
[12:32] <jamespage> coreycb: not fixed yet - trying to figure out how to unpick
[13:48] <rbasak> ahasenack, bryce, paride, rafaeldtinoco: I just noticed that if we mark a bug Won't Fix and the reporter responds, that won't reappear for triage.
[13:48] <rbasak> I can fix this easily enough, but the question is: exactly which statuses, if any, should we exclude for retriage?
[13:49] <rbasak> For example: do we want a comment on a bug where are tasks are marked "Fix Released" to reappear for triage?
[13:49] <rafaeldtinoco> rbasak: well, won't fix sounds appropriate to revisit (maybe by another person)
[13:49] <rbasak> rafaeldtinoco: right - so I think we should at least add "Won't Fix" to the list of "bugs that reappear for triage if there is activity"
[13:49] <rafaeldtinoco> rbasak: fix committed could appear again (for proposed migrations check)
[13:50] <rafaeldtinoco> it would remind us to check regressions during triage (? makes sense ?)
[13:50] <rbasak> Proposed migration isn't really part of our triage process - we check the excuses list separately to make sure we cover that.
[13:50] <paride> rbasak, we recently discussed this for the curtin/cloud-init triage and agreed to look only at active bugs with the following statuses:
[13:50] <rafaeldtinoco> alright
[13:51] <rbasak> For triage purposes what I want to make sure is that we don't miss useful community communication by accident.
[13:51] <rafaeldtinoco> makes sense
[13:51] <paride> New Incomplete Confirmed Triaged In Progress
[13:52] <paride> so no wontfix, with the idea that the bug reporter should set the status back to New if they want to reopen the discussion
[13:52] <rafaeldtinoco> paride: should we leave a msg warning about that ?
[13:52] <rafaeldtinoco> i wouldn't know :\
[13:52] <rbasak> paride: I noticed through bug 1832110, where I explicitly asked the reporter to do that but they didn't. I'm not sure how I could have made it clearer.
[13:53] <rafaeldtinoco> reporter might be afraid of changing that after a maintainer/core dev changes it to wontfix.. i would give the argument but not change the flag
[13:55] <paride> rafaeldtinoco, I think that most of the time we explicitly tell the reporter to change the status back to New if they think the issue is not actually solved -- at least I do, and I mostly took rbasak's replies as my reference :)
[13:57] <rbasak> Perhaps, if we always do that (I do, and it sounds like paride does), then we can accept that the kind of occurrence in this bug today will get missed, and that's OK.
[13:57] <rafaeldtinoco> yep, if explicitly said, i would
[13:58] <rafaeldtinoco> "could you double check because of X, Y, z" -> change back to new.. sounds okay
[13:59] <blackflow> Koopz: I definitely would, yes. Also check its S.M.A.R.T attributes log, via smartmontools.
[14:01] <paride> rafaeldtinoco, that's what I'd personally stick to, but I don't oppose adding wontfix to the list of statuses we watch, unless it adds too much noise
[14:02] <bryce> rbasak, due to all these considerations, I've generally avoided applying wontfix to bugs except in extreme cases where I know there's going to be more feedback but the decision is final.  So I generally would agree with paride that it should be omitted.  It depends a lot though on the team's policy for when wontfix is applied; if it's done more liberally then revisiting may make sense
[14:04] <bryce> and yes, people tend to be very reticent about changing bug states or tags, even when you invite them to
[14:05] <coreycb> jamespage: any luck with oslo.log? i'm not clear on how they are wedged. looking now
[14:06] <jamespage> coreycb: no been re-doing some upstream reviews for neutron
[14:07] <jamespage> coreycb: python3-oslo.log in proposed fails to install; I tried to update to fix that but oslo.log->oslo.config->oslo.log (which fails to install from proposed)
[14:07] <jamespage> coreycb: if we can quickest solution might be to get python-oslo.log removed from proposed
[14:08] <coreycb> jamespage: ok i think i'll put that request in. and it seems like the new version with your updates should work.
[14:08] <rbasak> bryce: I tend to Won't Fix more liberally, because I feel that anything else perpetuates the expectation that the work in in some queue somewhere waiting to be done, when in fact we have no intention of doing anything.
[14:08] <rafaeldtinoco> Warning /!\ the following status changes are restricted to members of UbuntuBugControl or package maintainers:
[14:08] <rafaeldtinoco> Moving from Won't Fix.
[14:08] <rafaeldtinoco> does a regular user can change from won't fix ?
[14:09] <rafaeldtinoco> (ubuntu wiki bugs/bug statuses)
[14:09] <rbasak> rafaeldtinoco: good point. I thought they could because I've seen enough status fights over Won't Fix. But perhaps not everyone.
[14:09] <rbasak> In that case perhaps we should add this status to the search list.
[14:09] <rbasak> cpaelzer: you weren't hear earlier - please see above discussion
[14:09] <rbasak> here
[14:10] <rbasak> I swear I have a "typing part" of my brain now that hears words sans grammar.
[14:12] <rbasak> Going back to the above discussion, I don't think bugs should ever be considered to be in a "terminal state" as it were.
[14:12] <rbasak> It should always be possible for them to be "rescued" from that by an interested community member who can provide an appropriate justification
[14:12] <rbasak> However the bug status does set expectations conclusively, and I'd like to retain the ability for us to do that.
[14:13] <rbasak> (without eliminating the possibility of discussion of changing our minds)
[14:13] <rafaeldtinoco> rbasak: like rescuing wont fix for newer releases (after years)
[14:13] <rafaeldtinoco> instead of opening new ones (and having history)
[14:14] <rbasak> Yes, if it's truly the same issue and not a new one.
[14:14] <rafaeldtinoco> yep
[14:14] <rbasak> (which is subjective of course)
[14:14] <TJ-> ^^^ had one of those today from 2009 !
[14:14] <rafaeldtinoco> TJ-: yep, i proposed a merge to CTDB (from 2011)
[14:14] <rafaeldtinoco> i mean, can happen!
[14:14] <TJ-> I asked the user to start a new bug but left a comment on the original
[14:15] <rbasak> I think it's fine to leave that choice up to whoever is driving the bug.
[14:16] <TJ-> rbasak: I think it's as you said; if W.F. is not used liberally to close off things prematurely, then additional comments (often arguments ad-nausium) don't need to be seen
[14:17] <cpaelzer> yep, all is a case-by-case decision - but we should not filter them out in e.g. triage
[14:17] <cpaelzer> rbasak: do we filter them atm?
[14:17] <TJ-> Bug Squad can always change status if its glaringly wrong too
[14:18] <rbasak> cpaelzer: accidentally we do, yes. I can provide a PR to fix easily - I just need to know which statuses we want to appear in triage. Am I right in thinking that you're advocating "all of them"?
[14:19] <bryce> rbasak, part of my opinions were shaped working on X.org bugs, where a given bug could have scores or hundreds of commenters who think they have the same issue but aren't even on the same video driver ;-)  Setting a bug to wontfix could really bring the rats out of the woodwork sometimes.
[14:21] <bryce> rbasak, long ago ctrl-alt-backspace used to be a shortcut to terminate the X session, and when I disabled it by default in the distro it generated a lot of discussion that ended with wontfixes.  ;-)
[14:21] <rbasak> bryce: yeah - I call those "pileon" bugs. Where people think they have the same bug because they share some common symptom. Impossible to "fix" because the same symptoms can be caused by multiple root causes, and it is sometimes impossible to eliminate all of them (especially when some root causes are user misconfigurations rather than bugs, but others were actually bugs that got fixed)
[14:24] <bryce> rbasak, yeah I called them me-too storms.  Got a lot of them for video driver bugs, where each was specific to a given piece of hw but had the same general symptoms (e.g. black screen of death) so whatever one got best billing in google got all the subscribers, regardless of drivers
[14:29] <cpaelzer> rbasak: never the less I think for server bugs we better should see them (and quickly call them done) than missing them
[14:29] <cpaelzer> we do not have a lot of those "me too" bugs
[14:31] <bryce> yeah server is in a much better situation.  Reporters also seem to be more technically inclined which is nice.
[14:35] <rafaeldtinoco> well, the burden of reading 1 or 2 last comments to figure out we should keep it as a wontfix, or call it done, is not big.. and possibly reporter would get very satisfied with one last comment or confirmation.. so +1 on what cpaelzer said
[14:37] <hggdh> rbasak, rafaeldtinoco: you could get the server team added to BugControl -- this would give all in the team the ability to set/reset status
[14:38] <cpaelzer> hggdh: youmean https://launchpad.net/~ubuntu-bugcontrol?
[14:38] <hggdh> cpaelzer: yes
[14:39] <cpaelzer> yeah rbasak, bryc, andreas and myself likely are in there by being core-dev's
[14:39] <rafaeldtinoco> "The Bug Control team is a subset of the Bug Squad and has the ability to set the Importance of bug reports regarding Ubuntu."
[14:39] <cpaelzer> thanks for the hint
[14:39] <rafaeldtinoco> fits the description =)
[14:39] <cpaelzer> https://launchpad.net/~canonical-server already is a member
[14:40] <ahasenack> note that ubuntu-server is an open team iirc
[14:40] <rbasak> hggdh: yes we already have that
[14:40] <cpaelzer> yeah that would be open, but the one I posted is not
[14:40] <cpaelzer> and it already is in there
[14:40] <rbasak> via ~canonical-server
[14:40] <ahasenack> is tinoco in there?
[14:40] <cpaelzer> and rafaeldtinocois a member
[14:40] <hggdh> so rafael is not a member of this team?
[14:40] <rafaeldtinoco> ahasenack: im here
[14:40] <hggdh> oops
[14:40] <rafaeldtinoco> ah nm
[14:40] <rafaeldtinoco> lol
[14:40] <ahasenack> ¯\_(ツ)_/¯
[14:40] <rbasak> hggdh: the question about not being able to change from Won't Fix to New is about community contributors, eg. if they want reconsideration of that status.
[14:41] <hggdh> rbasak: oh, OK. Yes, only BugControl (and drivers) can move from terminal status.
[14:42] <hggdh> our experience with having all changing status was... rather bad, with people randomly changing status
[14:42] <ahasenack> rafaeldtinoco: ubuntu-fan is green, should migrate any moment
[14:42] <rafaeldtinoco> \o/
[14:42] <ahasenack> I'm not stalking it specifically, I'm looking for my munin retry ;)
[14:42] <ahasenack> but you know, it's one big page
[14:42] <rafaeldtinoco> O.o
[14:43] <rafaeldtinoco> ahasenack: on the ctdb merge, ill go ahead and merge those 2 patches (non upstream)
[14:43] <rafaeldtinoco> i think it will be better to maintain if needed, when you merge samba again
[14:43] <ahasenack> yep
[14:44] <ahasenack> and I also don't think we need that huge description about versions < 4.10, which doesn't matter for eoan
[14:44] <ahasenack> the fix is simple, it's about using the correct service names
[14:44] <ahasenack> when samba gets updated, the patch will be refreshed or removed, just business as usual
[14:44] <rafaeldtinoco> k
[17:38] <bryce> I'm noticing there are two "styles" of lxc, one provided by the lxd-client, another from lxc-utils.  I've got both installed (i.e. lxc list and sudo lxc-ls produce different container listings).  I prefer the former, but I've only gotten autopkgtest to work with the latter.
[17:39] <bryce> I notice there's also an actual 'lxc' installable package from universe, although I haven't tried it
[17:40] <bryce> `autopkgtest <whatever>.dsc -- lxc -sed <container>` seems to expect lxc-utils.  Is there a way to make it use lxd-client instead?
[17:40] <bryce> ahasenack, are you using lxc with autopkgtest runs?  How are you doing it?
[17:41] <ahasenack> bryce: so
[17:41] <ahasenack> bryce: short answer: yes
[17:41] <ahasenack> but let's qualify "lxc"
[17:42] <ahasenack> there is old style lxc, the lxc-something commands (like lxc-ls), and that is the only one in debian afaik
[17:42] <ahasenack> and there is lxd, where the daemon is lxd, but the command line is just lxc (no dash to a subcommand)
[17:42] <ahasenack> I'm using lxd then
[17:42] <ahasenack> and I also use qemu, depending on the test
[17:43] <ahasenack> you should not use lxc-ls & friends, that is old and done
[17:43] <ahasenack> you'll notice there is autopkgtest-build-lxc (don't use this)
[17:43] <ahasenack> and autopkgtest-build-lxd (that's the one)
[17:43] <bryce> ok
[17:44] <ahasenack> likewise, there is autopkgtest-virt-lxc
[17:44] <ahasenack> and autopkgtest-virt-lxd
[17:44] <ahasenack> the latter is used when you specify autopkgtest .... -- lxd <imagename>
[17:45] <ahasenack> bryce: lxd in later ubuntu releases (don't remember since when right now) is only available as a snap
[17:46] <ahasenack> there is a wrapper deb package, but it will install the snap in postinst
[17:46] <bryce> ahasenack, aha  autopkgtest .... -- lxd  seems to be working and looks like what I'm after, thanks!
[17:46] <ahasenack> cool!
[19:44] <bryce> ahasenack, zookeeper has the same problem with adduser as the other thing
[19:44] <bryce> adduser: Warning: The home directory `/var/lib/zookeeper' does not belong to the user you are currently creating.
[19:47] <bryce> --> https://bugs.launchpad.net/ubuntu/+source/zookeeper/+bug/1832400
[20:00] <sdeziel> cyphermox: I'm setting up a sit tunnel with HE using netplan and following https://netplan.io/examples#connecting-an-ip-tunnel. I tried to skip the 'local' param as I do on ifupdown setups but netplan doesn't let me. This can be annoying for setup where the IPv4 is dynamic in nature.  AFAIK this is a limitation of networkd we need to deal with
[20:24] <sdeziel> cyphermox: thx
[20:34] <bryce> ahasenack, seems to be.  found there was another zookeeper bug reported years ago suggesting the same things we found
[20:38] <sdeziel> cyphermox: https://bugs.launchpad.net/ubuntu/+source/plan/+bug/1832404
[20:39] <ahasenack> bryce: did you get a set -x run yet in autopkgtest?
[20:46] <bryce> ahasenack, I'm poking around inside the container trying to see how to trigger it to start building the .dsc
[20:47] <ahasenack> bryce: which container? The one spawned by autopkgtest?
[20:47] <bryce> yeah
[20:47] <bryce> seems to not have javahelper installed
[20:47] <ahasenack> it's in a stopped state because the test failed, and you logged in?
[20:47] <bryce>  dpkg-source --before-build src
[20:47] <bryce> dpkg-checkbuilddeps: error: Unmet build dependencies: javahelper
[20:47] <bryce> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
[20:47] <bryce> dpkg-buildpackage: warning: (Use -d flag to override.)
[20:47] <bryce> root@autopkgtest-lxd-zgynnm:/tmp/autopkgtest.5vcQz7/build.xKm/src# apt-get install javahelper
[20:47] <bryce> + apt-get install javahelper
[20:47] <ahasenack> (the test run is stopped, not the container)
[20:47] <bryce> Reading package lists... Done
[20:48] <bryce> Building dependency tree
[20:48] <bryce> Reading state information... Done
[20:48] <bryce> E: Unable to locate package javahelper
[20:48] <bryce> r
[20:48] <bryce> looks like it stopped before it got to the test, like around line 757 on http://paste.ubuntu.com/p/QJ92bP6Bn9/
[20:48] <ahasenack> is it the right ubuntu relesae?
[20:49] <ahasenack> I see the same error as before, the postinst failing at the bottom of the paste
[20:50] <bryce> javahelper is a universe package so needed to enable that
[20:50] <ahasenack> 757 says Setting up javahelper (0.72.1~18.04.1) ...
[20:50] <ahasenack> I don't see an error around line 757
[20:50] <ahasenack> I suggested the -x to see what exactly failed in the postinst in line 1718
[20:51] <bryce> ahasenack, oh I meant, that's how far along it got before it logged me in
[21:04] <Ussat> I present to you:  Linux Ubuntu-1804LE 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:27:02 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
[21:04] <Ussat> \o./
[21:21] <ahasenack> Ussat: new box?
[21:49] <Ussat> I am doing a POC with IBM......Thats a POwer8 box running Ubuntu
[21:50] <Ussat> We are debating and testing, might move all our *nix off of esxi on to Power Hardware
[21:50] <Ussat> I am running the POC
[21:50] <Ussat> the test lab is in NY, I am in Iowa :)
[22:05] <sarnold> Ussat: woo, shiny :)
[22:06] <Ussat> Been struggling with rsct and dlparing, have an email to a IBM dev out
[22:07] <Ussat> Have it working with RHEL and Cent...its close w/Ubunnntu...but just not there yet...we will see what tomorrow brings
[22:08] <sarnold> "did you mean .. despairing .. ?"  :)
[22:08] <Ussat> heh
[22:32] <bjonnh> I'm trying to automate installs of ubuntu server using virt-install
[22:32] <bjonnh> virt-install --name test_vm --vcpus 2 --ram 256 --location http://archive.ubuntu.com/ubuntu/dists/disco/main/installer-amd64/ --disk vm.qcow2,bus=virtio,cache=none,size=5 --graphics none --console pty,target_type=serial --extra-args 'console=ttyS0,115200n8 serial' --network user,model=virtio
[22:32] <bjonnh> when I do that I get a --[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--
[22:35] <bjonnh> (tried without virtio as well)
[22:42] <bjonnh> (my purpose here is to provision VMs on a libvirt enabled server)
[22:43] <Ussat> \o/ dynamic LPARS workiong, was missing dynamicrm_2.0.1-3_ppc64el.deb


[00:06] <tgm4883> imaginal, what do you mean it says it's misconfigured
[00:19] <imaginal> tgm4883, " It appears that your backend may be misconfigured.  Check your backend logs..."
[00:19] <imaginal> From the frontend log
[00:20] <tgm4883> can you pastebin your backend log
[00:24] <imaginal> pastebin.com/PzQMWEPE
[00:24] <Zinn> [pastebin.com] Apr 30 11:14:39 starla-7426GX mythbackend[2279]: C thread_unknown mythcommandlin - Pastebin.com
[00:24] <imaginal> Timestamp 16:10:15
[00:25] <tgm4883> imaginal, looks like you set your backend to listen on <IP_ADDRESS>
[00:26] <tgm4883> you need to set it to it's actual IP address
[00:26] <tgm4883> and also enable the mythtv/mysql service in mythbuntu-control-centre
[00:27] <imaginal> That is strange. The local backend ip is set to <IP_ADDRESS>
[00:27] <imaginal> Enabling sql now
[00:34] <imaginal> Sql enabled, but both the local backend ip and master backend ip on the first page of general settings are set to the static IP. Is this supposed to go somewhere else?
[00:43] <imaginal> Also, the time stamp I provided was for 5/1.
[13:55] <samba35> ubuntu tv and myth+ubuntu is same thing ?
[14:01] <superm1> samba35: no ubuntu tv is a canonical concept that's not yet ready to go
[14:02] <samba35> ok
[14:02] <superm1> tgm4883 is working on a plugin that will be possible to include with ubuntu tv that lets it talk to mythtv backend though
[14:02] <superm1> there is a "scope" as it's called available right now
[14:02] <superm1> that lets ubuntu unity find and play videos and recordings using the new HTTP live streaming feature of mythtv 0.25
[14:03] <samba35> i am planning to buy a good tv + computer system for home  what are the  best options  i should explore
[14:03] <superm1> that's more of a mythtv-users type question
[14:04] <superm1> this channel is more for stuff pertaining specifically to mythtv on ubuntu
[14:04] <samba35> superm1, are you from ubuntu team ?
[14:04] <superm1> yeah
[14:05] <samba35> i am sorry can you please recommand what i should do and should not  for building computer and  tv from 1 box for home use
[14:07] <superm1> i mean there are some general things i can mention: get something w/ a video card that supports NVIDIA VDPAU, dual core is probably a good basis, want at least a gig of ram (http://mythbuntu.org/requirements)
[14:07] <Zinn> [mythbuntu.org] System Requirements | Mythbuntu
[14:08] <superm1> but you'll probably get more people's opinions from the mythtv-users mailing list if you pick something out /spec something out and send an email saying, does this sound good for this price?
[14:08] <samba35> ok
[14:11] <samba35> which is good tv tunner /external setup box i should use ,i have download 12.04 mythbuntu
[14:13] <superm1> if you are in the US, HDHomerun is very popular
[14:13] <superm1> or HD-PVR
[14:13] <samba35> ok
[14:13] <samba35> i am from india
[14:17] <superm1> i'm not sure the best for your availability then out there
[14:25] <samba35> ok
[16:50] <imaginal> I have 2 systems. One is running the primary backend with the tv tuner. The other with the secondary backend and a front. I'm unable to watch live tv from the second system
[16:50] <imaginal> The log file from the frontend trying to run:
[16:51] <imaginal> http://pastebin.com/pgAArHYQ
[16:51] <Zinn> [pastebin.com] Frontend - Pastebin.com
[16:51] <imaginal> Line 100 is about where the request was made
[16:52] <imaginal> The log file on the primary backend:
[16:52] <imaginal> http://pastebin.com/vBtD00Mi
[16:52] <Zinn> [pastebin.com] Backend - Pastebin.com
[16:52] <imaginal> Line 1917 is about where that request is made
[16:54] <imaginal> The computer with the primary backend can run a frontend and view live tv.
[16:55] <imaginal> The second computer looks like it makes the requests to the first computer properly, but the backend has an issue
[16:57] <imaginal> If anyone has advice on getting Live TV to the second computer, let me know. I appreciate all suggestions. :)
[20:48] <imaginal> After a few days, I figured out the issue. I had previously run MythTV on the second computer, and therefore generated a different sql database. I changed the IP address to the new master backend, but did not change the sql password
[20:49] <imaginal> Thanks to all for the guidance!