[00:57] <jose> a tope!
[01:06] <judgen> i might as well ask here unless i do not get an answer in #kde. "where is the settings for rearrangeing the kwin buttons in kde4?"
[01:21] <Riddell> judgen: right click on border -> configure window behaviour -> window decorations -> configure buttons
[01:26] <judgen> lol i missed that button... i was in that dialogue =D
[01:26] <judgen> thanks
[02:30] <ecinx3> when I wake my laptop from sleep it, the screen doesn't turn back on
[02:30] <ecinx3> anymore
[02:30] <shane4ubuntu> ok, why can't I seem to advance in dragon player?  I try to advance 10 sec (have the button on the bar) and it doesn't work
[02:32] <shane4ubuntu> Can someone recommend another app instead of dragon?  I remain un-impressed with dragon.
[02:32] <shane4ubuntu> for mp4 file, no video, just audio.
[02:34] <shane4ubuntu> hmm, a little slow in here lately. :)
[02:35] <ecinx3> :(
[02:35] <ecinx3> in the the wrong channel
[02:36] <ecinx3> no i'm not
[02:37] <shane4ubuntu> ecinx3: you are in Kubuntu channel.
[02:37] <yofel> shane4ubuntu: vlc or smplayer should work
[02:38] <sobczyk> shane4ubuntu: for audio amarok
[02:38] <yofel> dragon is probably missing some lib for xine
[02:38] <shane4ubuntu> yofel: I was searching through the repos, how about kplyer?
[02:38] <shane4ubuntu> yofel: is xine the backend of dragon?
[02:38] <yofel> xine is the phonon backend, used by dragon
[02:38] <shane4ubuntu> I searched for dragon plugins but didn't see anything
[02:38] <shane4ubuntu> ahh, ok, that helps, now I know where to look, thanks yofel
[02:39] <yofel> kplayer should work too, I just usually use smplayer
[02:39] <shane4ubuntu> yofel: right, I use vlc too, but was trying to give the kde stuff a fair opportunity.
[02:40] <blackl1ght> I have installed qt-sdk, But my hello world program give an error as "QApplication: No such file or directory." What do i do?
[02:40] <yofel> well, you could try a different phonon backend, the vlc one might work, but I didn't like it in maverick. gstreamer will be the default in natty
[02:41] <ecinx3> when I wake my laptop from sleep it, the screen doesn't turn back on anymore
[02:41] <yofel> blackl1ght: are you using qmake? and do you have libqt4-dev installed?
[02:42] <blackl1ght> yofel: Yes, I am using qmake, libqt4-dev is installed.
[02:42] <yofel> ecinx3: sadly I don't know much about debugging suspend issues, you could try #ubuntu or #ubuntu-beginners too, since that's probably a kernel / driver issue
[02:43] <ecinx3> ok thankyou
[02:44] <yofel> blackl1ght: I don't know what you do wrong then, /usr/include/qt4/QtGui/QApplication is part of libqt4-dev
[02:46] <yofel> at least here in qt 4.7
[02:46] <sobczyk> maybe a .pro file error
[02:47] <blackl1ght> The error comes up during "make", i mean qmake -project, qmake, then "make".
[02:48] <blackl1ght> All the header files are present in the directory you mentioned.
[03:36] <juanantonio_> Hello, I got a question
[03:37] <juanantonio_> I've recently updated from hardy 64 to Lucid 64 and now I have KDE4 and plasma and plasmoid
[03:38] <juanantonio_> with all these plasmoids came one of them as a client of Facebook, but I'm not satisfied. Is there a client for facebook similar to Hotpot for Twitter?
[03:41] <Daskreech> what's Hotpot?
[03:41] <juanantonio_> a lightweight twitter client
[03:43] <juanantonio_> Do you use twitter?
[03:44] <juanantonio_> Mmm, no, better, which Facebook clients you know?
[05:42] <blackl1ght> I had a problem with running the Hello world program in Qt.
[05:42] <blackl1ght> I had asked this question earlier.
[05:42] <roasted> so I just installed kubuntu, installed a theme, rebooted, logged in, and now everything is locked up.
[05:42] <blackl1ght> But, to anyone who still has a problem,
[05:43] <blackl1ght> In Kubuntu qmake is replaced by qmake-qt4, so use qmake-qt4 instead of qmake.
[05:43] <Guest690000> http://26.media.tumblr.com/tumblr_lgwsoici6v1qbqt8go1_500.jpg
[05:44] <bazhang> Guest690000, got a support question?
[05:44] <Guest690000> no
[05:44] <Guest690000> sorry
[05:44] <Guest690000> :)
[05:45] <bazhang> dont paste random things here
[05:45] <Guest690000> ok
[07:00] <ruffdog> asdf
[07:00] <ruffdog> asdfasdf
[07:03] <susundberg> Seems like there is something wrong with your keyboard, have you checked your settings? ;)
[07:51] <FloodBotK3> !netsplit
[08:05] <Marina> hello
[09:21] <petre> #please register
[09:36] <Adri2000> hi
[09:37] <Adri2000> what would you recommend as a full-text desktop search tool in lucid?
[09:39] <Eruaran> hello
[09:41] <Eruaran> hello, is there a specific channel for those who are testing natty?
[09:42] <Adri2000> Eruaran: #ubuntu-testing I think, dunno if there is a kde specific one
[09:43] <rork> Eruaran: #ubuntu+1
[09:43] <rork> ah, you've found out :
[09:43] <Adri2000> ah, right, #+1 :)
[09:50] <iflema> Adri2000: more recent versions of dolphin have a search feature... im not sure about the version that ships with lucid
[10:01] <rork> In lucid there's "find file" and a "filter bar" both in the Tools menu
[10:17] <amichair> !partners
[10:23] <alesan> hi do you know if it's possible to use an "audio compressor" in KDE?
[10:23] <alesan> so to artificially augment audio volume?
[10:23] <Adri2000> rork: but are they supposed to use a full-text index or is it just a GUI to /usr/bin/find?
[10:34] <rork> Adri2000: from what I can find they don't use an index, the search toolbar seems to use Nepomuk/Strigi though
[13:15] <shane4ubuntu> ok, I linked ddclient to /etc/init.d/  is there any easy way to make sure it is running on boot?
[13:15] <shane4ubuntu> or any way to make sure it is running right now?
[13:15] <jimkey> i'm loosin bloutooth connection to my headeset
[13:15] <jimkey> how to fix this?
[13:16] <shane4ubuntu> I ran sudo service --status-all and ddclient has a - in front of it, does that mean it isn't running?
[13:24] <BluesKaj> Hey folks
[13:24] <susundberg> Hi!
[13:25] <jimkey> i have bluetooth problem
[13:25] <jimkey> connection to headset is breaking after a while
[13:25] <jimkey> how to fix that?
[13:33] <jimkey> anyone?
[13:55] <dannyLopez> buenas
[13:55] <dannyLopez> tengo un problema con mis efectos de escritorio
[13:56] <nlsthzn> !br
[13:57] <nlsthzn> !es
[13:57] <nlsthzn> lol, just saw he is already gone :/
[14:14] <hyper_ch> anyone got already LibreOffice 3.3.1 running? If so, does  ctrl-shift-v now work for "paste special"?
[14:16] <BluesKaj> do you guys notice flash crashes on chromium,?ok on FF tho
[14:30] <QuarkBomb> hi, i have kubuntu netbook running in a VM, I was planning on putting it on my sister's netbook seen as Windows XP died (shock!) but there's a bug with a package and I don't know what the package is!  basically, some sort of navigator loads that's geared towards netbooks.  the sad fact is that it only loads about 10% of the time! I don't know what the package is so can't report the bug.  plus, I'd either like it to load all the time
[14:30] <QuarkBomb>  or not at all.  does anyone know what this "navigator" is?  thanks
[14:31] <QuarkBomb> i'm used to gnome but I think she'd be better off with KDE - plus KDE does actually look nicer
[14:33]  * nlsthzn strokes KDE and it purrs back at him
[14:37] <BluesKaj> !netbook | QuarkBomb
[14:37] <BluesKaj> bah , useless bot
[14:38] <QuarkBomb> indeed
[14:39] <hyper_ch> yu can also make gnome look nice
[14:39] <hyper_ch> but no clue about that navigator
[14:40] <BluesKaj> QuarkBomb, dunno much about netbook installs , most ppl just use a regular install if they have probs with the netbook versions , an alternate install might be in order if your sister's machine is as old as I think it is with XP and all
[14:40] <BluesKaj> !alernate
[14:40] <BluesKaj> !alternate
[14:41] <QuarkBomb> !minimal
[14:41] <QuarkBomb> hmmm
[14:41] <QuarkBomb> i'll give standard kubuntu another look then.  i wanted a smaller system for this wonderfully slow machine
[14:42] <shane4ubuntu> is kde 4.6 worth upgrading to?
[14:42] <shane4ubuntu> I mean, is it problematic?  or smooth transition?
[14:42] <QuarkBomb> plus it doesn't have a drive, so i'm going to have to play with a usb memory stick. woot
[14:43] <QuarkBomb> optical*
[14:44] <shane4ubuntu> ok, what is the difference between kubuntu-ppa/ppa  and kubuntu-ppa/backports ?   I thought I was good with the kubuntu-ppa  but now I see that 4.6 is out and I have 4.5.5?
[14:44] <nlsthzn> KDE 4.6 looks so good... works really well but I have ran into a few niggles (in both Kubuntu 10.10 with KDE 4.6 and also openSUSE 11.4 RC running KDE 4.6)
[14:45] <shane4ubuntu> nlsthzn: minor?  I mean my plasma-desktop crashes somewhat often, and can never report a bug for lack of info.
[14:46] <shane4ubuntu> not a real big deal since it just restarts itself, no real loss, or anything affected that I can notice, just an annoyance.
[14:46] <nlsthzn> shane4ubuntu: my plasma only crashed when I tried to reboot :p... plus once I got the additional bug reporting packages installed there was emough info to report
[14:47] <nlsthzn> I couldn't get desktop effects to stay on... graphical anomalies if it was on
[14:47] <BluesKaj> shane4ubuntu, more kde
[14:47] <shane4ubuntu> nlsthzn: hmm, perhaps that is my prob, I'm running desktop effects. :)  no anomalies though, just random crashes.
[14:48] <shane4ubuntu> BluesKaj: are you running 4.6?
[14:48]  * nlsthzn is on KDE 4.4.5 now and everything is working pretty and fast :D
[14:49]  * shane4ubuntu is running 4.5.5 and everything seems fine, except random crashing of plasma-desktop
[14:49] <rork> QuarkBomb: I missed the start of your question but in my experience KDE is one of the most heavy desktop environments. You might want to check XFCE, LXDE or just a window manager like FluxBox for (really) slow computers.
[14:50] <Riddell> shane4ubuntu: kubuntu-ppa/ppa is stable updates (no new versions), kubuntu-ppa/backports is backports (new versions)
[14:50] <BluesKaj> shane4ubuntu, yes , but beware there is some flash crashing with it , especially on chromium which doesn't integrate very well with kde or even at all , flash does better with gnome and ealier kde versions
[14:50] <shane4ubuntu> Riddell: my understanding is that backports is not 'un-stable' just version updates then?
[14:51] <Riddell> QuarkBomb: there's no separate install for netbook in 10.10, it'll just load the netbook workspace if you have a netbook, I don't understand what you mean by navigator, maybe a screenshot would help
[14:51] <shane4ubuntu> BluesKaj: I switched to Chrome instead of chromium because chromium was giving me problems in general, I was disappointed with chromium
[14:51] <Riddell> shane4ubuntu: yes, although backports will have had less testing
[14:51] <shane4ubuntu> Riddell: right, that was my basic understanding of backports, figured that probably applied to the kubuntu-ppa as well.
[14:51] <QuarkBomb> rork, I downloaded the lubuntu iso but haven't had a look at it yet.  i assumed KDE would have more support than the others - I could be wrong of course.  I think I'll mess about with other options then to see which is best suited.  I know she'd like the KDE layout but she'll just have to make do
[14:52] <QuarkBomb> Riddell, I'm trying to get it to load rebooting the VM multiple times but it won't
[14:52] <QuarkBomb> like i said, that's the problem: it only loads sometimes
[14:52] <QuarkBomb> and now i have a SS!
[14:52] <shane4ubuntu> Riddell: so I should disable kubuntu-ppa/ppa before enabling kubuntu-ppa/backports?
[14:53] <Riddell> shane4ubuntu: no need to
[14:53] <shane4ubuntu> Riddell: ok, thanks for the inof
[14:53] <shane4ubuntu> *info
[14:53] <QuarkBomb> hmmm, where can i upload an image quickly?
[14:54] <Riddell> QuarkBomb: imagebin.org ?
[14:55] <antares_> Buenas compañeros
[14:55] <Riddell> hola antares_
[14:55] <antares_> ¿Se encuentra alguien que hable español?
[14:55] <antares_> Que tal Riddell
[14:55] <QuarkBomb> Riddell, http://ploader.net/files/9561a2ce24d260f8677ab90cdc3b7a05.png have to pause the VM to get the damned thing to take a screenshot
[14:56] <shane4ubuntu> something tells me I should backup before plunging into 4.6
[14:56] <QuarkBomb> most of the time it's just a blue background with the menu in a different place; presumably the standard Kubuntu desktop - I haven't used it in a number of years
[14:57] <antares_> Estoy viendo el Nuevo Kubuntu 11.04 Alpha 2
[14:57] <antares_> Se ve que traerá muchas cosas buenas
[14:57] <NET||abuse> hey there folks,
[14:57] <Riddell> !es | antares_
[14:57] <NET||abuse> just installed 4.6 as a test on my netbook
[14:58] <NET||abuse> i'm having trouble when i click on the button that zooms out and gives you a running application overview.. i can't get out of it
[14:58] <shane4ubuntu> NET||abuse: and how did it go?
[14:58] <antares_> Gracias, ya ando en el chat español ;)
[14:58] <NET||abuse> it seems to revert itself after a few minutes :)
[14:58] <NET||abuse> but how do you exit ?
[14:58] <Riddell> QuarkBomb: that screenshot is the netbook UI
[14:58] <NET||abuse> clicking on any of the running apps on the screen doesn't get me back anywhere.. doesn't do anything
[14:59] <NET||abuse> there it just jumped back, 60 seconds
[14:59] <NET||abuse> shane4ubuntu, was ok, netbook running 10.10, added the 4.6 ppa, installed, no glitches
[14:59] <NET||abuse> shane4ubuntu, pretty happy with that
[14:59] <NET||abuse> shane4ubuntu, i selected kdm as my default x session so the login uses the kdm setup,
[15:00] <shane4ubuntu> NET||abuse: I was just looking at doing the same, but on desktop
[15:00] <NET||abuse> but if i logout, kdm doesn't restart :P
[15:00] <hyper_ch> on my netbook, it seems Kubuntu KDE 4.6.0 Beta PPA (also previous versions) do not respect the powersettings at all.
[15:00] <NET||abuse> hyper_ch, they use a different backend for power settings
[15:00] <Riddell> QuarkBomb: if the other workspace loads sometimes then something strange is going on with the code detecting whether to run netbook or desktop, but it's probably just cause by the VM being confusing
[15:00] <NET||abuse> so you 'll have to set everything again
[15:00] <NET||abuse> seperate settings registry likely
[15:00] <hyper_ch> NET||abuse: "they"?
[15:00] <NET||abuse> hyper_ch, yes, them upstairs
[15:00] <NET||abuse> fine, it uses
[15:00] <hyper_ch> NET||abuse: I don't know what you mean
[15:01] <hyper_ch> what seperate settings registry?
[15:02] <hyper_ch> NET||abuse: could you elaborate?
[15:03] <QuarkBomb> Riddell, surely the same UI should load no matter what the VM is doing - it shouldn't be dependent on hardware
[15:05] <Riddell> QuarkBomb: it loads the appropriate UI for the machine its running on, so it's very dependent on hardware
[15:06] <NET||abuse> woohoo, just got our google accounts access in work..
[15:06] <NET||abuse> weee, migration of all our email.
[15:07] <QuarkBomb> so i'll have to test it on the actual netbook then?  fair enough - if that's too much for the netbook i'll have a look at lubuntu and xubuntu.  thanks :)
[15:12] <BluesKaj> yes shane4ubuntu , no flash crashes so far with chrome :)
[15:17] <shane4ubuntu> BluesKaj: I found out that chromium seemed to be the testing bed for chrome, and therefore was a little less stable, where chrome seems to be a little more stable
[15:21] <spawn57> just a l'il less stable... a tiny l'il bit
[15:23] <BluesKaj> shane4ubuntu, it's more bleeding edge and doesn't seem to play nice with kde , altho it seemed fine on gnome/gtk ..I still find it arrogant of google not to accomodate font settings in their menu and tab bars to comply with whatever desktop-environment font sertings are used..I'm using a large screen monitor , (our plasma tv) in 1080x1920 res and the fonts are too small to read from a distance
[15:28] <shane4ubuntu> BluesKaj: I ran into problems with pdf stuff, crashed chromium, that is when I started having probs.
[15:41] <surex> hi , how to connect bluetooth in kubuntu 10.10 ?
[15:42] <surex> hi
[15:42] <surex> hi
[15:43] <QuarkBomb> outstanding
[16:06] <surex> How to connect internet using bluetooth in kubuntu10.10?
[16:16] <surex> How to connect internet using bluetooth in kubuntu10.10?
[16:17] <surex> hi
[16:18] <surex> hi
[16:32] <basy> hi , i just update kububtu and i lost network settings... My network adapter disappear form kernel, [ifconfig print only "lo" interface] What should i supose to do ?
[16:33] <ct529> hi! is it possible to find all the files you have been working on a specific date from command line?
[16:33] <ct529> the date search in my dolphin is not working
[16:37] <nerea> k es esto
[16:37] <nerea> la viirgen
[16:37] <basy> cd "rootdir "; ls -lar | grep 2011-02-20
[16:38] <basy> will find list all files in rootdir and its subdirs
[16:49] <surex> How to connect internet through bluetooth in kubuntu10.10??
[16:49] <rahul> hello...
[16:51] <rahul> need help in configuring WINE...!!!
[16:53] <wbsx> what kind of help?
[16:53] <wbsx> oops
[16:56] <basy> networking is not working after last update :( i check dmesg, and there are some lines with "eth0" and its driver, but no error there, i looks as eth0 is loaded. ifconfig still shows only "lo" interface ?? Network management is disabled .. what to do ?
[17:10] <surex> How to connect internet through bluetooth in kubuntu10.10?
[17:18] <Bsims> I am having trouble with usb devices... its autolaunching the gnome apps even though I told the usb manager widget not to...
[17:19] <Bsims> I tried deleting my .kde folder to start over, that solves the issue but I am unable to get icons on my panel the way I want
[17:27] <Roasted> Has anybody ever had any success with Kubuntu 10.10 on an Optiplex 740 by chance? I tested my CD and USB drive which said 0 errors, but it locks up graphics wise when I try to boot to it to install.
[17:47] <ct529> hi! is it possible to find all the files you have been working on a specific date from command line?
[17:47] <ct529> the date search in my dolphin is not working
[18:05] <sobczyk> ct529: read the manual of find
[18:14] <pawel__> hello
[19:24] <TheNeo> Salut
[19:24] <TheNeo> Y'a quelqu'un ,
[19:24] <TheNeo> ,,
[19:24] <TheNeo> ??
[19:24] <nlsthzn> ?
[19:24] <rork> !fr TheNeo
[19:24] <TheNeo> Salut !
[19:24] <rork> !fr
[19:24] <TheNeo> Hello !
[19:24] <rork> Hi
[19:25] <TheNeo> Sorry I am french and my english is ... not very good ^^
[19:26] <rork> That's why I gave you the french channel ;)
[19:53] <iiname> hello
[19:54] <__osh____> I tried starting kubuntu 10.10 with the -xforcevesa option but it still loaded radeon and failed to start X. How do I prevent the live-cd from loading radeon-driver?
[19:57] <__osh____> The card is an ATI4650 so I don't  really see a reason why kubuntu shouldn't manage to handle it.
[19:58] <__osh____> It's not an uncommon card I mean.
[20:00]  * __osh____ is sligthly impressed by PasNox ipv6.
[20:15] <nikitis> How do I change the middle area of the window decorations?  No matter which theme I get it's still gray
[20:17] <Peace-> BluesKaj:
[20:17] <BluesKaj> hi Peace-
[20:18] <nikitis> Anyone?
[20:18] <Peace-> nikitis: ?
[20:18] <nikitis> i just started using kde
[20:18] <nikitis> When i go to change the window decoration
[20:18] <Peace-> nikitis: so?? what's your question
[20:18] <nikitis> the background of a window doesn't change only the outside
[20:19] <Peace-> well  i guess it's right
[20:19] <nikitis> what changes the background?
[20:19] <nikitis> I don't want any light gray windows
[20:19] <Peace-> a moment please
[20:23] <BluesKaj> nikitis, download more colours in system settings/app appearence/colours
[20:23] <Guest53702> Hey, anybody here?
[20:23] <Peace-> nikitis: http://wstaw.org/m/2011/02/23/plasma-desktophP1539.jpg
[20:23] <Guest53702> need some advice bad screwed up with window
[20:23] <Guest53702> s
[20:24] <Peace-> Guest53702: ??
[20:24] <Guest53702> I installed a dodgy driver and now whenever I start up WIndows 7 it disables my keyboard and mouse
[20:24] <Guest53702> I can't use it at all
[20:24] <nikitis> BluesKaj, Doh, that did it
[20:24] <Guest53702> how do I manually uninstall the said driver from kubuntu?
[20:24] <Guest53702> I'm on a dual-boot setup
[20:24] <nikitis> Thanks BluesKaj  and Peace-
[20:25] <Guest53702> I tried cutting and pasting the driver from system32 over to kubuntu, but then it didn't start up at all
[20:25] <Guest53702> I had to run windows repair and that just re-installed the dodgy driver :S
[20:25] <Guest53702> so any help?
[20:25] <BluesKaj> nikitis, there also themes / decorations in system settings /worspace appearance
[20:25] <Peace-> Guest53702: wait a moment i have to read what you did xD
[20:25] <Guest53702> haha okay :)
[20:25] <BluesKaj> err workspace
[20:26] <Peace-> Guest53702: you used a windows driver into linux ?
[20:26] <Peace-> xD
[20:26] <Guest53702> nope
[20:27] <Guest53702> I installed a windows driver into windows 7
[20:27] <Guest53702> the second it was finished pretty much disabled my mouse and keyboard
[20:27] <Peace-> ok
[20:27] <Guest53702> wouldn't take any input at all
[20:27] <Guest53702> so I unplugged it and plugged it back in, still messed it up
[20:27] <Guest53702> restarted the computer, still messed it up
[20:27] <Peace-> Guest53702: so...windows7
[20:28] <Guest53702> tried to system restore about 3 times, each time it failed (restore file was currupt)
[20:28] <Guest53702> yeah windows 7
[20:28] <Peace-> Guest53702: but this is a kubuntu channel xD
[20:28] <Guest53702> so I tried to open up Kubuntu, access the host folder and delete the driver from the system32 folder
[20:28] <Peace-> nope man
[20:28] <Peace-> this is not a kubuntu question
[20:28] <Guest53702> when I started up windows 7 it just froze and I had to do system repair, and that just restored the dodgy driver :S
[20:29] <Guest53702> I know sorry but getting desparate here xD
[20:29] <Guest53702> mind pointing me to the right IRC channel then?
[20:29] <Peace-> #windows
[20:29] <Guest53702> thanks also
[20:29] <Guest53702> what's the best web browser for kubuntu with flash support?
[20:29] <Peace-> Guest53702: guess firefox4 or chromium
[20:29] <Guest53702> thanks
[20:29] <Peace-> i use chromium
[20:30] <BluesKaj> Guest53702, FF, not chromium if you're opn kde 4.6
[20:30] <Peace-> BluesKaj: got some problem on kde 4.6 and chromium ?
[20:32] <BluesKaj> Peace-, yes flash crashes ..so I switched to googlechrome ...it'smore stable
[20:36] <Peace-> BluesKaj: mm maybe you right sometimes i ahve seen crash flash xD but i used konqueror for so long time that it was normal too me xD
[20:37] <BluesKaj> Peace-, google-chrome is ok so far menu fonts are too small tho
[20:37] <BluesKaj> for this 42" tv/monitor at 3M away
[20:42] <Peace-> BluesKaj: xD
[20:43] <nikitis> BluesKaj, I have dual monitors,  is there a way to share one background picture across two monitors?
[21:05] <Irwell> hi... does anyone know about desktop effects? the logout desaturation wasn't working properly (drawing weirdly) so i disabled it and there was no desaturation. when i restarted the effect remained off but log out has started desaturating properly. the problem is that the application launcher doesn't finish hiding before the desktop desaturates and part of it remains visible.
[21:37] <starsprout> hi. I'm running a dual-boot win/kubuntu 10.04 64-bit compaq laptop. suddenly the keyboard and mouse won't work at kubuntu login screen
[21:37] <starsprout> they work fine in windows
[21:38] <starsprout> I can't type or move the mouse on kubuntu login screen at all (or in recovery mode either)
[21:47] <mbai> Hi. on kubuntu 10.10, I have kernel.yama.ptrace_scope = 0 , but I can't use ltrace against a running process.
[21:47] <mbai> gdb attach is working however.
[21:50]  * cirian75 looks around
[22:36] <notslad> I just started using kubuntu.. is there a (somewhat) centralized CLI tool for general configuration?  I'm coming from a SuSE background, so I'm looking for something similar to at least YaST's curses based configuration tool..
[23:40] <phoenix_firebrd> hello everyone
[23:42] <phoenix_firebrd> the volume control adjustment is missing in kmix. not able to bring it back using settings->configure channels. nothing pops up when i select the menu


[02:08] <teej> How does Snappy differ from Flatpak?
[05:46] <mup> PR snapd#4134 closed: interfaces/uhid: unconditionally add existing uhid device to the device cgroup (2.29) <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4134>
[05:46] <mup> PR snapd#4137 closed: cmd/snap-update-ns: fix mount rules for font sharing (2.29) <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4137>
[05:47] <mup> PR snapd#4127 closed: interfaces/uhid: unconditionally add existing uhid device to the device cgroup <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4127>
[05:47] <mup> PR snapd#4132 closed: interfaces/serial-port: udev tag plugged slots that have just 'path' via KERNEL (2.29) <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4132>
[05:47] <mup> PR snapd#4133 closed: interfaces/hidraw: udev tag plugged slots that have just 'path' via KERNEL (2.29) <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4133>
[05:48] <mup> PR snapd#4116 closed: interfaces/hidraw: udev tag plugged slots that have just 'path' via KERNEL <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4116>
[05:49] <mup> PR snapd#4114 closed: interfaces: don't udev tag devmode or classic snaps <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4114>
[05:50] <mup> PR snapd#4123 closed: interfaces: fix incorrect signature of ofono DBusPermanentSlot (2.29) <Critical> <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4123>
[06:07] <mborzecki> morning
[06:25] <mvo> hey mborzecki, good morning
[06:41] <mup> PR snapd#4064 closed: tests: new test for hardware-random-control interface <Created by sergiocazzolato> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4064>
[06:43] <zyga-solus> hey
[06:43] <zyga-solus> mvo: goodmorning
[06:43] <zyga-solus> mvo: man, you're up early
[06:44] <zyga-solus> mvo: btw, about tests being slow: http://autopkgtest.ubuntu.com/running
[06:45] <mvo> zyga-solus: yeah, well, travis is the main issue
[06:51] <mborzecki> zyga-solus: morning
[06:51] <zyga-solus> hey mborzecki
[06:52] <mborzecki> is there a checker in gocheck lib that can verify if something is in a list? something similar to this: https://godoc.org/github.com/stretchr/testify/assert#Assertions.Contains
[06:53] <mborzecki> (disclaimer, i've quite heavily used testify/assert and testify/mock packages before)
[06:54] <zyga-solus> mborzecki: I wrote one
[06:54] <zyga-solus> mborzecki: in testutils/
[06:54] <mborzecki> thx
[06:55] <zyga-solus> mborzecki: ironically this was one of my first patches to snapd :D
[06:55] <zyga-solus> and my first go code
[06:55] <zyga-solus> "where is contains in this language"
[06:56] <mborzecki> zyga-solus: you mentioned that account-control is feeding bad information on arch
[06:57] <mborzecki> i'm fixing this right now (or at least that's what i think i'm doing)
[06:59] <mup> PR snapd#4115 closed: interfaces/serial-port: udev tag plugged slots that have just 'path' via KERNEL <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4115>
[07:00] <zyga-solus> mborzecki: excellent, thank you!
[07:00] <mvo> zyga-solus: 4136 is failing for real it seems
[07:01] <mvo> zyga-solus: the /run/snapd/ns/snapd.test-snapd-desktop.fstab just contains fontconfig three times ?!
[07:02] <zyga-solus> looking
[07:02] <zyga-solus> I wrote that one "dry", without running it
[07:03] <zyga-solus> autopkgtest.ubuntu.com is very slow for me
[07:04] <mvo> zyga-solus: this is available in travis (which is also slow) and I have a local shell in qemu open right now, but it looks strange, almost as if we just mount systemfontconfigcachedir three times instead of systemfontsdir, systemlocalfontsdir
[07:05] <mvo> zyga-solus: aha, no, the fstab file is correct in /var/lib/snapd/mount
[07:06] <zyga-solus> mvo: can you paste both fstab files please
[07:06] <zyga-solus> the one in /var/lib/snapd/mount/ and in /run/snapd/ns
[07:06] <zyga-solus> I'll try localy but it will take some time
[07:07] <mvo> zyga-solus: http://paste.ubuntu.com/25877947/
[07:07] <zyga-solus> ha
[07:07] <zyga-solus> that's very werid
[07:07] <zyga-solus> thanks, I'll dig
[07:08] <zyga-solus> mvo: if you still have the shell
[07:08] <zyga-solus> before I get there
[07:08] <zyga-solus> can you please nsenter and look at mountinfo
[07:09] <mvo> zyga-solus: http://paste.ubuntu.com/25877952/
[07:09] <zyga-solus> thank you
[07:10] <zyga-solus> mounts doesn't show the source correctly
[07:10] <zyga-solus> I'll run locally and debug, no worries
[07:10] <mvo> zyga-solus: mountinfo looks correct, no? so its just the outside that looks fishy?
[07:10] <mborzecki> do you amend/fixup/rebase/reshuffle commits in a PR or just add new ones on top?
[07:10] <zyga-solus> no, mounts doesn't show this at all
[07:11] <zyga-solus> mborzecki: we usually add and squash
[07:11] <zyga-solus> (when merging)
[07:11] <mborzecki> working around github's mess? :)
[07:11] <zyga-solus> mborzecki: optimizing for review flow
[07:12] <zyga-solus> mvo: if you hold the release for 30 minutes until we get a better picture I can help analyze this
[07:14] <mup> PR snapd#4138 opened: release: 2.29.1 <Created by mvo5> <https://github.com/snapcore/snapd/pull/4138>
[07:14] <mvo> zyga-solus: too late for 2.29.1, if its something grave we need a 2.29.2
[07:14] <zyga-solus> k
[07:15] <mvo> zyga-solus: inside the ns I have /usr/share/fonts from the outside afaict ?
[07:15] <zyga-solus> mvo: yes,
[07:16] <mvo> zyga-solus: so what is missing :) ?
[07:16] <zyga-solus> mvo: but please tail mountinfo (not mounts)
[07:16] <zyga-solus> mvo: because the earlier pastebin was inconclusive
[07:16] <zyga-solus> (mounts doesn't show the relevant stuff)
[07:16] <zyga-solus> I worry about why that thing was listed three times, that's very fishy
[07:17] <mvo> zyga-solus: http://paste.ubuntu.com/25877985/
[07:17] <zyga-solus> this is correct
[07:17] <zyga-solus> so
[07:17] <zyga-solus> if this is correct, why was the other file wrong :D ?
[07:18] <zyga-solus> did you just ran the test?
[07:18] <zyga-solus> or experiment in some other way?
[07:18] <mvo> zyga-solus: I did nothing to the system, just ran the spread test in qemu. the output looks consistent with what linode outputs
[07:18] <mborzecki> i probably don't know what i'm doing, but I've updated https://github.com/snapcore/snapd/pull/4135
[07:18] <mup> PR #4135: Workaround unit test failures on Arch <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4135>
[07:19] <zyga-solus> thank you, I'll look now
[07:21] <zyga-solus> mborzecki: that looks very good to me
[07:23] <mborzecki> btw. has anyne seen something like https://paste.ubuntu.com/25878010/ ?
[07:24] <mborzecki> snapSeccompSuite.TestRestrictionsWorkingArgsUidGid failing with 'setuid u:daemon'
[07:25] <zyga-solus> mvo: reproduced now
[07:25] <mvo> mborzecki: not this particular error, this is the seccomp confinement test, it runs on the real (running) kernel
[07:25] <zyga-solus> mborzecki: hmmm
[07:25] <zyga-solus> mborzecki: just checking, you do have an user called daemon on your system, right?
[07:25] <mvo> mborzecki: I assume this is the arch kernel?
[07:25] <mborzecki> suprisingly, i did not see this yday, then ran pacman -Syu in the evening, and rebooted to a new kernel today :)
[07:26] <mborzecki> mvo: yes, it's an arch kernel
[07:26] <mvo> mborzecki: what version is that?
[07:26] <mborzecki> 4.13.10-1-ARCH
[07:26] <zyga-solus> it's curious btw, it seccomp is so well established that this should not fail
[07:27] <mvo> mborzecki, zyga-solus maybe its argument filtering and something with daemon is different on arch?
[07:27] <mborzecki> i'll poke around
[07:27] <zyga-solus> mvo: perhaps
[07:29] <mvo> mborzecki: whats the uid of your daemon user?
[07:29] <mborzecki> daemon:x:2:2:daemon:/:/usr/bin/nologin
[07:29] <mvo> mborzecki: there you go :/ the test assumes "1"
[07:29] <mvo> mborzecki: {"setuid u:daemon", "setuid;native;1", main.SeccompRetAllow},
[07:30] <mvo> mborzecki: i.e. it sends the setuid (native arch) syscall with arg 1 which does not work on arch. silly test !
[07:30] <mborzecki> heh, i can fix that
[07:30] <mvo> mborzecki: thanks
[07:31] <mborzecki> btw. uid 1 is 'bin', interesting
[07:31] <zyga-solus> mborzecki: it's all broken
[07:32] <zyga-solus> distros don't agree on any uid other than root
[07:32] <mborzecki> trying to remember what it was in yocto
[07:41] <zyga-ubuntu> mvo: http://pastebin.ubuntu.com/25878071/
[07:41] <zyga-ubuntu> this is the failure
[07:42] <zyga-ubuntu> something is clearly wrong
[07:42] <zyga-ubuntu> man :/
[07:43] <zyga-solus> mvo: I _think_ I know
[07:43] <mvo> zyga-solus: what are the implications of this bug?
[07:43] <zyga-solus> bad stuff is in the current profile
[07:43] <zyga-solus> but namespace is correct
[07:43] <zyga-solus> it shows up when > 1 entry is present
[07:43] <zyga-solus> but I'm a bit DOH
[07:44] <mvo> zyga-solus: what is the implication of bad stuff in the current profile?
[07:44] <zyga-solus> golang feature
[07:44] <zyga-solus> mvo: we'll undo stuff that's not done
[07:44] <zyga-solus> mvo: it will all fall apart as we try to "mend" it
[07:44] <mvo> zyga-solus: when do we do that? on refresh?
[07:44] <zyga-solus> when we setup security
[07:45] <mvo> zyga-solus: so things will explode when snapd is restarted?
[07:45] <zyga-solus> not really explode
[07:45] <zyga-solus> it will not return a failure code
[07:47] <zyga-solus> mvo: testing a small fix
[07:47] <mvo> zyga-solus: hm, maybe I need to ask differently. this freeze/thaw is something new added, its not in 2.29 iirc. so does this affect 2.29 and if so what are the implications for the users, i.e. is it just internal or are there visialbe regressions?
[07:47] <zyga-solus> mvo: unless I'm mistaken golang does something I didn't expect
[07:48] <mvo> zyga-solus: looking forward to see the diff :)
[07:48] <zyga-solus> mvo: this should not affect freeze/thaw
[07:48] <mvo> zyga-solus: so this affects 2.29?
[07:48] <zyga-solus> mvo: taking the address of a variable on iteration seems to return the same thing over and over
[07:48] <zyga-solus> mvo: as if this was a loop local temporary
[07:48] <zyga-solus> mvo: so :/
[07:49] <zyga-solus> mvo: it's scaryt
[07:49] <zyga-solus> we had this since forever
[07:49] <mvo> zyga-solus: could you paste the diff? just so that I can get an idea
[07:49] <zyga-solus> yes
[07:49] <mvo> zyga-solus: thanks
[07:50] <zyga-ubuntu> http://paste.ubuntu.com/25878114/
[07:50] <zyga-ubuntu> where else are we doing something like this?
[07:50] <mborzecki> zyga-solus: can you point me to the code with this iteration?
[07:50] <zyga-ubuntu> why doesn't golang warn / error on this
[07:50] <zyga-ubuntu> mborzecki: please look at main.go in cmd/snap-update-ns
[07:51] <zyga-ubuntu>         changesMade = append(changesMade, change)
[07:51] <zyga-ubuntu> a variant of this line
[07:51] <zyga-ubuntu> near line 164
[07:51] <zyga-ubuntu> (I applied a helper patch so there may be an offset)
[07:52] <mvo> zyga-ubuntu: if we had this forever and nothing bad happens, is it critical for 2.29.1?
[07:52] <zyga-solus> mvo: nobody noticed / tested >1 mount entry
[07:52] <zyga-solus> mvo: I think .2 is in order now that we know really
[07:52] <mborzecki> zyga-solus: it's always taking the same &change?
[07:52] <zyga-solus> mvo: especially since this will really mess up all the desktop interface snaps over time
[07:53] <zyga-solus> yes
[07:53] <zyga-solus> mborzecki: that's what it looks like
[07:53] <zyga-solus> testing a fix now
[07:53] <mvo> zyga-solus: well, maybe. I want to understand what happens if we don't fix it
[07:53] <zyga-solus> mvo: I can tell you in 20 minutes after another test where I undo this
[07:53] <mborzecki> can you drop _, change := range ... and use for i := range changesNeeded ... { change := changesNeeded[i] .. } ?
[07:53] <zyga-solus> mvo: ok, with the patch it works
[07:54] <zyga-solus> mborzecki: right, I understand that now, I just found it unexpected
[07:54] <mborzecki> hit this myself a couple of times, enough to make me doubt range
[07:56] <mborzecki> typical scenarios is the code inside is calling goroutines or doing syscalls (which are rescheduling points)
[07:57] <zyga-solus> mvo: patch pushed
[07:57] <mvo> zyga-solus: I think I would slightly prefer the minmal diff that mborzecki suggests (using an for i := ... loop). anyway, sorry for being difficult
[07:57] <zyga-solus> mvo: no, please look at the patch
[07:58] <zyga-solus> mvo: the patch is minimal and simpler semantically
[07:58] <mvo> zyga-solus: just trying to understand the implications of this
[07:58] <mvo> zyga-solus: ok, checking
[07:58] <zyga-solus> mvo: 14 lines changed
[07:58] <zyga-solus> one character each
[07:59] <mborzecki> lgtm
[07:59] <zyga-solus> and thank $DIETY for spread tests!
[08:01] <mborzecki> pushed another patch to https://github.com/snapcore/snapd/pull/4135 cmd/snap-seccomp tests are all passing now
[08:01] <mup> PR #4135: Workaround unit test failures on Arch <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4135>
[08:04] <zyga-solus> mvo: will you take that patch?
[08:08] <mvo> zyga-solus: tbh, I'm still on the fence, if its not a regression and it has not yet caused problems yet I'm not sure. but lets prepare a 2.29 PR so that we have it
[08:09] <zyga-solus> mvo: ok
[08:09] <zyga-solus> mvo: if you can take it I'd suggest so
[08:09] <zyga-solus> mvo: it's a clear bug
[08:09] <zyga-solus> mvo: and the more we use content interface the more harm it will cause
[08:09] <zyga-solus> mvo: I'll make a 2.29 PR for you
[08:10] <mvo> zyga-solus: thank you
[08:11] <zyga-solus> done, 4139
[08:11] <mup> PR snapd#4139 opened: cmd/snap-update-ns: fix collection of changes made <Created by zyga> <https://github.com/snapcore/snapd/pull/4139>
[08:21] <mvo> zyga-solus: thank you
[08:35] <mborzecki> FYI 'nogroup' is replaced with 'nobody' in arch
[08:35] <zyga-solus> mborzecki: yeah, I'm afraid some of those tests will look like Swiss cheese
[08:36] <mborzecki> zyga-solus: is 'nogroup' used in other placed in the code?
[08:37] <zyga-solus> mborzecki: I don't think so, we only used it for tests
[08:37] <zyga-solus> (AFAIK I made that change)
[08:37] <zyga-solus> mborzecki: to work around other things that weren't common between ubuntu and solus
[08:37] <mborzecki> good, this is the last unit test that fails here
[08:37] <mborzecki> btw. is there a not-empty checker?
[08:38] <zyga-solus> HasLen, 0 is useful
[08:38] <kalikiana> good morning, snappy
[08:38] <mvo> mborzecki: depends on what you need, there is "HasLen"
[08:38] <zyga-solus> hey kalikiana :)
[08:38] <mborzecki> Not(HasLen), 0 ?
[08:39] <mup> PR snapd#4140 opened: interfaces: add an interface for gnome-online-accounts D-Bus service <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/4140>
[08:44] <zyga-solus> mborzecki: yes
[08:45] <zyga-solus> mborzecki: note that we can add IsEmpty or similar
[08:45] <zyga-solus> mborzecki: it's not hard to add a new checker
[08:45] <zyga-solus> mborzecki: and especially when the error messages are nicer, this could be useful
[08:56] <pedronis> pstolowski: hi,  looking at #4108 again,   do we need Hooks/Apps on ConnectedSlot ?  you didn't implement Hooks
[08:56] <mup> PR #4108: repo: ConnectedPlug and ConnectedSlot types <Created by stolowski> <https://github.com/snapcore/snapd/pull/4108>
[08:59] <pstolowski> pedronis, hi, we don't have Hooks on slots, per comment and implementation in snap/info.go in the existing code
[09:01] <pedronis> pstolowski: but we have apps?  do we use them?
[09:03] <pstolowski> pedronis, we do, they affect SecurityTags()
[09:05] <mborzecki> can this https://github.com/snapcore/snapd/pull/4119 be merged, or should i rebase on top of master?
[09:05] <mup> PR #4119: tests/test-snapd-service: fix shellcheck issues <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4119>
[09:06] <zyga-solus> looking
[09:07] <zyga-solus> mborzecki: yeah, or merge master
[09:08] <mup> PR snapd#4141 opened: snap-update-ns: add missing unit test for desired/current profile handling <Created by mvo5> <https://github.com/snapcore/snapd/pull/4141>
[09:08] <zyga-solus> nice!
[09:09] <mborzecki> rebased and pushed
[09:14] <pedronis> pstolowski: thanks
[09:16] <pedronis> pstolowski: zyga-solus:  shouldn't places  in  interaces  doing   range plug.Apps  ?  also consider plug.Hooks ?
[09:16] <pedronis> *interfaces
[09:16] <zyga-solus> pedronis: yes, do you know of one that does not?
[09:17] <pedronis> they all don't
[09:17] <pedronis> afact
[09:17] <pedronis> I'm not even sure the interface is the best given the issue
[09:17] <zyga-solus> pedronis: hmm
[09:17] <pedronis> zyga-solus: there's a bunch of plug.Apps in interfaces/builtin but not plug.Hooks
[09:18] <pedronis> afaict
[09:18] <pedronis> I suppose we didn't notice because the interfaces that need that are not typical hook plugs
[09:18] <pedronis> but I suppose there is an issue
[09:18] <zyga-solus> indeed
[09:18] <zyga-solus> I see this in common
[09:18] <zyga-solus> and in other places
[09:18] <pstolowski> info.go // NOTE: hooks cannot have slots
[09:19] <pstolowski> ah, sorry, you're asking about plugs
[09:20] <zyga-solus> yes
[09:20] <zyga-solus> pedronis: it's isolated to udev handling, it seems
[09:20] <zyga-solus> pstolowski: do you want to fix it or shall I?
[09:20] <zyga-solus> pedronis: thank you for spotting!
[09:21] <pstolowski> zyga-solus, i'm currently working on cookies issue from yesterday
[09:21] <zyga-solus> ok
[09:21] <zyga-solus> I'll do it
[09:25] <pedronis> pstolowski: also related, I notice that plugJSON has no hooks either
[09:25] <pstolowski> pedronis, thanks, will fix
[09:26] <pedronis> I don't know if it's important, are we still using plugJSON ?
[09:27] <mvo> zyga-solus: 4139 has unit tests failures, fix is trivial http://paste.ubuntu.com/25878484/ - could you please update?
[09:28] <zyga-solus> sure
[09:28]  * zyga-solus wonders how that happened, I go tested this
[09:30] <zyga-solus> done
[09:31] <zyga-solus> mvo: ah, the backport, I must have not tested that one
[09:40] <Chipaca> aw, you can't make an alias into a namespace :-(
[09:41] <Chipaca> - Setup manual alias "xbill-xaw.xbill-xaw" => "xbill-xaw" for snap "xbill-xaw" (cannot enable alias "xbill-xaw.run" for "xbill-xaw", it conflicts with the command namespace of installed snap "xbill-xaw")
[09:41] <Chipaca> gah, mis-paste
[09:41] <Chipaca> - Setup manual alias "xbill-xaw.run" => "xbill-xaw" for snap "xbill-xaw" (cannot enable alias "xbill-xaw.run" for "xbill-xaw", it conflicts with the command namespace of installed snap "xbill-xaw")
[09:41] <Chipaca> (yes that is kinda backwards)
[09:50] <mup> PR snapd#4138 closed: release: 2.29.1 <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4138>
[09:52] <Chipaca> how're you doing, mborzecki ?
[09:52] <mvo> oSoMoN: fwiw, I can reproduce the chromium nvidia black screen issue here
[09:53] <mvo> oSoMoN: I get mknod denials for seccomp
[09:55] <mborzecki> Chipaca: good, fixed all unit tests that were failing on arch, lookign into updating arch package now
[09:55] <mvo> oSoMoN: and manually adding "mknod" to the seccomp profile works
[09:55] <Chipaca> mborzecki: neat
[09:55] <mvo> oSoMoN: well, works in the sense that when i do that, recompile the profile and start chromium it works
[09:56] <mborzecki> Chipaca: there's a PR open https://github.com/snapcore/snapd/pull/4135 in case you want to sake a second look
[09:56] <mup> PR #4135: Workaround unit test failures on Arch <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4135>
[10:02] <oSoMoN> mvo, thanks for the feedback! do the denials indicate which node chromium is trying (and failing) to create?
[10:06] <mvo> oSoMoN: I try to figure this out right now, it does not give me this data currently
[10:06] <oSoMoN> mvo, you'll probably need to strace it to get that info
[10:06] <mvo> oSoMoN: yes
[10:06] <zyga-solus> or run it and look at /tmp
[10:06] <mvo> zyga-solus: /tmp ?
[10:06] <zyga-solus> well, it has to keep the node somewhere
[10:07] <zyga-solus> so /tmp or /run
[10:07] <zyga-solus> or $HOME
[10:15] <pedronis> mborzecki:   we tend to title our PRs   with:  comma-separated relevant packages or dirs or "many"   ":"  lowercase summary
[10:16] <mborzecki> pedronis: noted, thanks
[10:16] <pedronis> mborzecki:   like "cmd/snap,client,daemon: show ignore-validation if set in snap info"
[10:19] <mborzecki> pedronis: I can rename it now, but I'm afraid it might restart the builds
[10:19] <zyga-solus> mborzecki: no need
[10:19] <zyga-solus> mborzecki: just hit edit on GH
[10:21] <mborzecki> updated
[10:21] <pedronis> yes, this is about the PR title and the merge commit, not the commits inside
[10:21] <pedronis> we are not very strict, but this is the idea
[10:22] <mborzecki> ok
[10:23] <Chipaca> mborzecki: git log --oneline --no-merges <- we try to make this readable (it's a struggle)
[10:23] <Chipaca> zyga has a link with more rationale
[10:23] <zyga-solus> me? I don't recall
[10:23] <Chipaca> yus
[10:23] <zyga-solus> now that you said that I do recall
[10:23] <zyga-solus> but I don't recall what it was :)
[10:24] <zyga-solus> I recall _something_ :D
[10:24] <mborzecki> aah, yeah, i'm used to rebasing a lot :) this usually kept the history linear
[10:24] <pedronis> it's a struggle because we aren't as rebase happy as other projects,
[10:25] <pedronis> mborzecki: yea,  general rule we don't rebase after a PR got some comments, we tend not to squash commit either unless the PR is messy, then we do
[10:25] <pedronis> the results are mixed
[10:25] <pedronis> also we have rules how the merge commit should look like but it's a struggle to remember to apply them when clicking in GH
[10:26] <mborzecki> noted :) sorry cause i've rebased both PRs already
[10:27] <mborzecki> some project do merges outside of github just to keep the history linear, iirc zephyr does that
[10:27] <Chipaca> that's ok, we won't burn you alive for the first one
[10:27] <Chipaca> :-)
[10:27] <zyga-solus> mborzecki: github has an option to rebase nowadays
[10:28] <Chipaca> (but really, these are our intentions; then things are on fire and it all goes out the window)
[10:28] <mborzecki> though it's still not particularly review friendly with rebase/fixup workflow :(
[10:28] <mborzecki> small things like ordering commits chronologically rather than using the order from git
[10:42] <pedronis> mmh, I don't this stuff in written in the form or the readmes ?
[10:42] <pedronis> s/form/forum/
[10:44] <mborzecki> any idea why libseccomp is linked statically into snap-seccomp?
[10:44] <zyga-solus> mborzecki: because of re-exec woes
[10:44] <zyga-solus> mborzecki: snapd needs to operate on systems where libseccomp is old/unpatched
[10:45] <pedronis> Chipaca: are you working on aliases? or the private refresh bug?
[10:50] <Chipaca> pedronis: aliases; AIUI refresh needs gustavo (and it's just one more day)
[10:51] <Chipaca> pedronis: if you want to start in it feel free :-) my plate has plenty on it
[10:52] <pedronis> no,  mostly asking if you had time for some reviews
[10:53] <Chipaca> always¹
[10:54] <Chipaca> 1. not always
[10:54] <zyga-solus> LOL
[10:54] <zyga-solus> 1. conditions apply
[10:54] <Chipaca> ;)
[10:56] <pedronis> Chipaca: interested in your feedback on #4112
[10:56] <mup> PR #4112: cmd/snap,client,daemon: show ignore-validation if set in snap info <Created by pedronis> <https://github.com/snapcore/snapd/pull/4112>
[10:57] <Chipaca> pedronis: https://github.com/snapcore/snapd/pull/4112/files?w=1
[10:58] <Chipaca> (ignore whitespace for the github diff)
[10:58] <Chipaca> pedronis: hm, i would've put it in notes
[10:58] <Chipaca> pedronis: then you also get it (for free) in snap list
[10:59] <pedronis> well I asked for feedback,
[10:59] <pedronis> otoh you get notes only with  --verbose
[10:59] <Chipaca> pedronis: no, you get the expanded notes with --verbose
[10:59] <Chipaca> pedronis: without it you get them a la list
[11:00] <pedronis> ah, so seems the right thing to do
[11:01] <pedronis> let me close this
[11:01]  * Chipaca will allow it
[11:01] <Chipaca> :-D
[11:01] <mup> PR snapd#4112 closed: cmd/snap,client,daemon: show ignore-validation if set in snap info <Created by pedronis> <Closed by pedronis> <https://github.com/snapcore/snapd/pull/4112>
[11:03] <pedronis> Chipaca: ah, it's a cmd/snap concept, not a rest api concept
[11:03] <Chipaca> yes, the client side is fine
[11:04] <pedronis> good(tm)
[11:05] <pedronis> Chipaca: is ignore-validation too long for notes?
[11:08] <Chipaca> pedronis: do you have something better?
[11:08] <pedronis> no
[11:08] <mup> PR snapcraft#1652 closed: tests: fork skip into snaps_tests <bug> <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1652>
[11:08] <Chipaca> pedronis: 's fine
[11:10] <pedronis> ah, I still need my code for the verbose case
[11:10] <pedronis> that's a little odd
[11:12] <sergiusens> snappy-m-o autopkgtest 1650 xenial:amd64 xenial:armhf xenial:arm64 zesty:amd64 zesty:armhf zesty:arm64 artful:amd64 artful:armhf artful:arm64 bionic:amd64 bionic:armhf bionic:arm64
[11:12] <snappy-m-o> sergiusens: I've just triggered your test.
[11:20] <zyga-solus> tests are not with me today
[11:24] <mup> PR snapd#4142 opened: cmd/snapd,client,daemon: display ignore-validation flag through the notes mechanism <Created by pedronis> <https://github.com/snapcore/snapd/pull/4142>
[11:25] <pedronis> Chipaca: ^
[11:32] <Chipaca> pedronis: lovely
[11:36] <mborzecki> zyga-solus: you introduce packaging for arch, can you take a look at this patch: https://github.com/bboozzoo/snapd/commit/1ac38e2614cef8e30d17b8800bc18c1abeac9409
[11:37] <zyga-solus> looking
[11:38] <mborzecki> once arch related PRs get merged, i'd like to publish this to AUR as snapd-git
[11:38] <zyga-solus> mborzecki: I merged snap-confine into one package now
[11:38] <zyga-solus> mborzecki: btw, did you see the packaging that was added to 2.27.x releases?
[11:39] <zyga-solus> (on GH release pages)
[11:39] <zyga-solus> ah, I was confused by depends on snap-confine
[11:39] <mborzecki> yes, but the community package is still split into snapd and snap-confine, unless it's listed in conflicts pacman will not try to remove it
[11:39] <zyga-solus> hmm
[11:39] <zyga-solus> mborzecki: I see
[11:39] <zyga-solus> that's unfortunate
[11:40] <zyga-solus> can we do anything about that?
[11:41] <mborzecki> zyga-solus: it's there, snap-confine is listed in conflicts in my patch, this should do the trick
[11:41] <zyga-solus> ah, I see
[11:41] <zyga-solus> +1 then
[11:42] <zyga-solus> not sure if other things are done
[11:42]  * zyga-solus looks
[11:42] <zyga-solus> nope
[11:42] <zyga-solus> look at 2.27.x releases for updated packaging
[11:42] <zyga-solus> things like snap-exec etc are missing
[11:45] <mvo> oSoMoN: I added some info into the forum post, chromium acts a bit strange, maybe its something specific to their code but it tries to create /dev/nvidiactl which is already avialable in the namespace and which the same pid stat()s successfully a couple of times before
[11:48] <oSoMoN> mvo, thanks, that's very useful, I'll dig in chromium code to try and understand why they would do that
[11:49] <mborzecki> zyga-solus: hmm looks like arch packaging was never updated to include snap-exec :/
[11:49] <zyga-solus> mborzecki: not the one in the repo (as it was never upstreamed)
[11:49] <mvo> oSoMoN: thanks, might be an issue on our side too, but from the strace it looks like something strange is happening in the code
[11:49] <zyga-solus> mborzecki: sorry about that, arch situation is a bit unoptimal
[11:51] <mborzecki> can you point me to the code?
[11:51] <zyga-solus> sure
[11:51] <zyga-solus> https://github.com/snapcore/snapd/releases/tag/2.27.5
[11:51] <zyga-solus> there's a source package for arch attached
[11:51] <zyga-solus> https://github.com/snapcore/snapd/releases/download/2.27.5/snapd-2.27.5-1-arch-srcpkg.tar.gz
[11:51] <zyga-solus> a bit crude but :/
[11:51] <pedronis> mvo: did you see my question about default tests for the configure-snapd code?
[11:54] <mvo> pedronis: yes thank you! I started to write one and then $stuff happend :/ (the mount profile chnage bug that zyga-ubuntu found/fixed and an nvidia error)
[11:55] <pedronis> it's ok, just wondered because there was no answer in the PR
[11:56] <pedronis> mvo: on my side a 2nd review of #4106 would be appreciated,  and thansk for reviewing the snap  info/list change
[11:56] <mup> PR #4106: many: lookup and use the URL from a store assertion if one is set for use <Created by pedronis> <https://github.com/snapcore/snapd/pull/4106>
[11:57] <mvo> pedronis: ok, I do that next (probably after lunch though)
[11:58] <mborzecki> zyga-solus: got it, by the looks of it, it's a bit outdated and the build process is so-so (CGO_*FLAGS are not set properly)
[11:58] <zyga-solus> mborzecki: that's the most recent we have, we didn't do arch releases since
[11:58] <mborzecki> what's the plan then? so far there's an outdated version in snapd tree, another one on gh release page (outdated as well) and one in community repo (more outdated than both previous)
[11:58] <zyga-solus> mborzecki: if you merge it with your improvements and merge back to master it should be fairly ok
[11:59] <zyga-solus> ideally, update the community repo but ENOLUCK
[11:59] <zyga-solus> mborzecki: we can update the packaging in master for reference
[11:59] <zyga-solus> mborzecki: but we still don't have arch tests that run on PRs so it's likely to go out of date eventually
[12:00] <zyga-solus> mborzecki: little by little, since you run arch daily it will help a lot in making the package healthy
[12:01] <mborzecki> ok, hmm let's do this, first merge and update all pkgbuilds into master tree, make it a -git package (this should make it easy to test it directly from git)
[12:01] <zyga-solus> +1
[12:01] <mborzecki> then maybe add snapd-git to aur, so that the users are not blocked and  update archwiki page (if there's one)
[12:01] <mborzecki> guess the last step would be getting an image for spread and adding arch to the test suite
[12:02] <oSoMoN> mvo, it might be https://cs.chromium.org/chromium/src/content/gpu/gpu_sandbox_hook_linux.cc?type=cs&sq=package:chromium&l=223 , but I'm still trying to figure out where that call to mknod is issued
[12:02] <mborzecki> zyga-solus: first 2 i can take care of, will need help with the last one :), how does that sound?
[12:03] <zyga-solus> mborzecki: arch is supported on linode already
[12:03] <zyga-solus> mborzecki: but it all sounds like a good plan
[12:07]  * kalikiana coffee vreak
[12:08] <mup> PR snapcraft#1655 opened: lxd: distinguish argless clean from clean -s pull <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1655>
[12:08] <zyga-solus> mvo: can you do a 2nd review of 4136
[12:10] <zyga-solus> this will let us merge 4141 next
[12:22] <mup> PR snapd#4119 closed: tests/test-snapd-service: fix shellcheck issues <Created by bboozzoo> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4119>
[12:29] <mup> PR snapcraft#1646 closed: sources: enforce default language in subversion info <Created by clobrano> <Closed by sergiusens> <https://github.com/snapcore/snapcraft/pull/1646>
[12:30] <pedronis> seen this:  + tar czf /home/gopath/src/github.com/snapcore/snapd/snapd-state.tar.gz /var/lib/snapd /snap /etc/systemd/system/snap-core-3386.mount /etc/environment /etc/systemd/system/snapd.service.d /etc/systemd/system/snapd.socket.d
[12:30] <pedronis> tar: Removing leading `/' from member names
[12:30] <pedronis> tar: /var/lib/snapd: file changed as we read it
[12:30] <pedronis> are we not stopping enough stuff?
[12:30] <pedronis> was on 14.04
[12:30] <zyga-solus> maybe refresh timer (unlikely but maybe?)
[12:39] <zyga-solus> the udev tagging situation is more complex than other backends but I think I have something that will allow us to fix it in a generic way
[12:41] <zyga-solus> hey cachio, how are you feeling?
[12:41] <cachio> zyga-solus, I am in a 35%
[12:42] <zyga-solus> cachio: go away and recharge then
[12:42] <zyga-solus> cachio: take a break, rest, it's friday
[12:42] <cachio> zyga-solus, it is ok, if I feel bad I'll go to bed
[12:44] <cachio> zyga-solus, mvo, the #3378 is the one to validate?
[12:44] <mup> PR #3378: tests: fixes for executions using the staging store <Created by fgimenez> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3378>
[12:44] <cachio> core snap rev 3378
[12:45]  * Chipaca looks at cachio
[12:45] <Chipaca> cachio: this is not how you get better
[12:46] <Chipaca> mvo: i need to go to the school it seems; i'll be missing the standup
[12:47] <Chipaca> mvo: report from me would be: still hating aliases (but still hopeful to finish before eow), and, need to look at how to handle refresh of private (and bought) snaps next week with niemeyer
[12:48] <Chipaca> (via people having trouble with this in the forum)
[12:57] <mvo> Chipaca: thank you
[12:58] <mvo> oSoMoN: indeed, this looks like the right track
[12:59] <mvo> zyga-solus: looking at 4136 in a wee bit, last I looked tests were still running but looks like that is finished now
[12:59] <zyga-solus> thank you
[13:00]  * sergiusens starts making his way to the bank
[13:00] <sergiusens> bbiab
[13:28] <zyga-solus> mvo: I'll push my PR in a moment
[13:31] <mvo> zyga-solus: ta
[13:32] <mup> PR snapd#4136 closed: cmd/snap-update-ns: fix mount rules for font sharing <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4136>
[13:34] <pedronis> pstolowski: for the 2nd part of the issue, I think will need something like   Change.LaneTasks(lanes []int) []*Tasks that gives all the tasks in the change in the given lanes, or all of the them if one of the lanes is 0 (the default lane)
[13:35] <pedronis> heh, sorry, the last bit is wrong
[13:35] <pedronis> about 0
[13:38] <pstolowski> pedronis, will look at snapctl issue next. thanks
[13:38] <pedronis> pstolowski: np
[13:39] <pstolowski> what's the quickest/recommended way of disabling a spread test entirely?
[13:39] <pstolowski> via systems: ?
[13:39] <mvo> pstolowski: manual: true is one way and a comment
[13:40] <pstolowski> mvo, great, thanks
[13:40] <mvo> pstolowski: or exit 0 in execute with an echo with the details why its disabled
[13:43] <pstolowski> mvo, i'm going to propose this only against 2.29, since MR will receive a fix in next few days; makes sense?
[13:43] <pstolowski> s/MR/master/
[13:43] <mvo> pstolowski: yes
[13:44] <mvo> pstolowski: we will still pull it into master to minimize the delta but if you target 2.29 thats great that means we can move faster
[13:44] <mup> PR snapcraft#1412 opened: lxd: snapcraft refresh in containers <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1412>
[13:46] <zyga-solus> offtopic, HasLen checker is particularly unhelpful about saying what the real length was
[13:48] <mup> PR snapd#4106 closed: many: lookup and use the URL from a store assertion if one is set for use <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/4106>
[13:51] <mup> PR snapd#4110 closed: many:  have a timestamp on store assertions <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/4110>
[13:51] <mup> PR snapd#4139 closed: cmd/snap-update-ns: fix collection of changes made <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4139>
[13:58] <mup> PR snapd#4143 opened: snapctl: Disable stop/start/restart (2.29) <Created by stolowski> <https://github.com/snapcore/snapd/pull/4143>
[13:59] <pstolowski> mvo, ^ this should do it
[14:00] <pstolowski> kyrofa, ^ bad news :(
[14:03] <zyga-solus> mvo: now doing common
[14:05] <zyga-solus> mvo: behind one innocent line in common.go there are lots of interfaces that need small tweaks to consts
[14:08] <mborzecki> zyga-solus: there was a template based refactoring tool for go
[14:08] <zyga-ubuntu> mborzecki: uh, not worth it in this case
[14:08] <mborzecki> eg?
[14:08] <zyga-ubuntu> I need to tweak a few constants
[14:08] <zyga-ubuntu> and change type
[14:09] <mborzecki> hm change type can be done with gorename
[14:09] <mborzecki> it'll update all packages that use that type
[14:09] <zyga-ubuntu> mborzecki: I need to do that to about a dozen variables spread around dozen files
[14:10] <zyga-ubuntu> mborzecki: I'll show you the patch and I can learn abou the tool when you see it
[14:10] <mvo> pstolowski: thank you
[14:11] <mvo> mborzecki: anything that needs to go to 2.29?
[14:12] <mborzecki> mvo: don't think that arch fixes are a priority, so nothing from my side
[14:12] <mvo> mborzecki: ta
[14:12] <mvo> zyga-ubuntu: your renames are master, right? or also 2.29?
[14:13] <zyga-solus> mvo: master unless you think it's 2.29 material
[14:13] <zyga-solus> mvo: "renames" are not real renames, just a mental shortcut
[14:18] <mvo> zyga-solus: I will wait for the PR but probably not 2.29 then
[14:18] <mvo> zyga-solus: just trying to avoid a .3 by gathering all potential further changes
[14:19] <zyga-solus> k
[14:23] <zyga-solus> mvo: ok ready
[14:23] <zyga-solus> pushing
[14:27] <zyga-solus> mvo: 4144
[14:27] <zyga-solus> I'll self-review for typos now
[14:28] <mup> PR snapd#4144 opened: interfaces: fix udev tagging for hooks <Created by zyga> <https://github.com/snapcore/snapd/pull/4144>
[14:31] <roadmr> jdstrand: hi! hey question. You approved classic confinement for goby yesterday. Did you by chance also trigger an automated review after doing that?
[14:32] <zyga-solus> mvo: read it, pushed and squashed one trivial unused variable removal
[14:32] <zyga-solus> mvo: I'll check if this applies to 2.29
[14:33] <zyga-solus> mvo: yep, I can propose a 2.29 variant too
[14:33] <zyga-solus> close it if you don't want to take that risk
[14:34] <mvo> zyga-solus: I ponder over it
[14:34] <mvo> roadmr: jdstrand is not around today
[14:35] <mup> PR snapd#4145 opened: Backport/udev hooks 2.29 <Created by zyga> <https://github.com/snapcore/snapd/pull/4145>
[14:35] <roadmr> mvo: darn! mystery will need to wait to be solved :)
[14:35] <zyga-solus> pedronis: can you have a look at 4144
[14:35] <zyga-solus> pedronis: that should fix the issue you found today
[14:36] <mvo> roadmr: yeah :)
[14:36] <roadmr> thanks though mvo
[14:37] <mup> PR snapd#4145 closed:  interfaces: fix udev tagging for hooks (2.29) <Created by zyga> <Closed by zyga> <https://github.com/snapcore/snapd/pull/4145>
[14:38] <mup> PR snapd#4146 opened:  interfaces: fix udev tagging for hooks (2.29) <Created by zyga> <https://github.com/snapcore/snapd/pull/4146>
[14:42] <mborzecki> zyga-solus: you're right, does not look like this could be done with go's refactoring tools
[14:44] <zyga-solus> mvo: I'll make some tea, let me know if I can help you somehow
[14:59]  * sergiusens is back
[15:00] <sergiusens> kyrofa might want to start looking into this https://pastebin.ubuntu.com/25880037/
[15:00] <sergiusens> that is all I have from the error as the log has not been generated/exposed yet
[15:01] <sergiusens> that extract is from running on bionic, which I thought would be a skip for these
[15:03] <mvo> zyga-solus: quick brainstorm, can you check https://github.com/snapcore/snapd/compare/master...mvo5:refactor-ifstate?expand=1 and tell me what names you prefer? do you think overlord/ifacestate/repo is a good name for the package?
[15:03] <mvo> zyga-solus: fwiw, tests for 4143 have not started yet :( so no 2.29.2 until those have run
[15:05] <mborzecki> i'm done for today, gotta go pick up my kids, have a nice weekend guys
[15:06] <elopio> Good morning!
[15:07] <kalikiana> sergiusens: You might like to have a look at snapcraft#1655 this is to avoid `snapcraft -s pull` killing your container
[15:07] <mup> PR snapcraft#1655: lxd: distinguish argless clean from clean -s pull <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1655>
[15:07] <diddledan> build.snapcraft.io isn't letting me sign-into launchpad oauth: Invalid association handle
[15:07]  * kalikiana waves at elopio
[15:08] <diddledan> or rather it redirects back to build.snapcraft.io but reports error
[15:09] <kyrofa> pstolowski, uh oh
[15:09] <kyrofa> pstolowski, what's the background there?
[15:11] <pstolowski> kyrofa, it breaks with an error if run from configure hook as part of snap install/refresh. will also error out in install/refresh hooks.
[15:12] <pstolowski> kyrofa, my spread test was only testing one case
[15:12] <kyrofa> pstolowski, is this a case of the fix being known, just more work than can be done right before a release
[15:12] <kyrofa> ?
[15:13] <pstolowski> kyrofa, more work, but not on time for this .point release
[15:13] <zyga-solus> re
[15:13] <kyrofa> pstolowski, that's fair, I appreciate the heads up. Something you anticipate happening soon, though?
[15:13] <zyga-solus> mvo: sorry, had IRL interrupt
[15:13] <zyga-solus> mvo: checking your branch
[15:14] <pstolowski> kyrofa, yeah, should be fixed soon and in the 2.30 release
[15:15] <kyrofa> pstolowski, alright, thank you :)
[15:15] <om26er> Who is responsible for transfer of snap ownership ?
[15:16] <zyga-solus> mvo: hmm
[15:16] <zyga-solus> mvo: please add repo.go :)
[15:16] <zyga-solus> mvo: and push :)
[15:16] <zyga-solus> mvo: I'll check after I really make that tea
[15:16] <noise][> om26er: there are a few of us here that can do it
[15:16] <kyrofa> sergiusens, huh, that one's not skipped. Maybe it's something we lost as part of the migration into snapd tests, or maybe it's something that used to work, but I'm adding a skip now
[15:16] <noise][> and i'm aware we are a bit behind on the forum requests this week
[15:16] <om26er> noise][: kindly transfer android-studio and sublime-text-3 from my name(om26er) to snapcrafters
[15:17] <kyrofa> Oh, that's not part of the snapd suite, haha
[15:17]  * zyga-solus cannot wait to snap install sublime-text-3
[15:17] <om26er> The packaging was already moved under snapcrafters but the ownership didn't.
[15:17] <ogra_> pfft ... vim rules ...
[15:18] <zyga-solus> ogra_: yeah, but fira code font is amazing
[15:18] <zyga-solus> ogra_: do you know that font?
[15:18] <noise][> om26er: ok, we can get to those today, sorry for the delay
[15:18] <zyga-solus> mvo: travis is starving us so badly I wonder why this is so
[15:19] <mvo> zyga-solus: autsch, sorry, added repo.go now
[15:19] <kyrofa> It must have passed at some point, that test has been there for a while
[15:19] <ogra_> zyga-solus, is that the one with weird arrows and such ?
[15:20] <zyga-solus> ogra_: yes
[15:20] <zyga-solus> well, "weird"
[15:20] <zyga-solus> normal actually
[15:20] <om26er> noise][: thanks :)
[15:21] <zyga-solus> mvo: so, first of repo is not a great name since it clashes with interfaces/repo.go and that Repository, something non-clashing would be better
[15:21] <zyga-solus> mvo: what is the cycle this breaks?
[15:21] <zyga-solus> mvo: I expected that we'd have something outside of ifacestate, not a nested package actually
[15:23] <mvo> zyga-solus: see explaination in the preview, it allows creating a "interfaces.Repository" based on the current state from snapstate
[15:23] <mvo> zyga-solus: which allows to e.g. answer the question if a content interface is already connected
[15:23] <mvo> zyga-solus: that is important to know if the default-provider needs to be downloaded or not
[15:23] <zyga-solus> right
[15:23] <zyga-solus> hmm
[15:23] <kyrofa> sergiusens, wait... that's a duplicate test!
[15:23] <mup> PR snapcraft#1656 opened: integration tests: skip shared ROS test on non-xenial <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/1656>
[15:24] <zyga-solus> I'm a little lsot about how this makes it work (I totally believe it does, just not grok it yet)
[15:24] <kyrofa> Ignore that PR for a sec, it looks like that test became a snapd test, but then was never removed
[15:24] <mvo> zyga-solus: I'm open for other ideas, I'm not super happy about "repo"
[15:24] <zyga-solus> snapstate->ifacestate->snapstate is the cycle that we are breaking?
[15:24] <kyrofa> Man, that's gonna speed travis up so much
[15:24] <zyga-solus> mvo: let me branch and see
[15:24] <zyga-solus> mvo: +1 on the idea, this is just nitpick territory now
[15:25] <mvo> zyga-solus: yes, snapstate imports ifacestate/repo and ifacestate imports ifacestate/repo too
[15:25] <mvo> zyga-solus: we do something similar in configstate/config
[15:25] <kyrofa> sergiusens, wait I lied. It's not, it's closely related
[15:25] <mvo> zyga-solus: yeah, no worries, happy to bikesheed about the name, naming is hard
[15:26] <mvo> zyga-solus: the three most difficult problems in cs:  naming and off-by-one errors
[15:27] <kyrofa> And it's a faster one anyway
[15:28] <zyga-solus> mvo: iterating
[15:30] <kyrofa> mvo, very clever :P
[15:30] <zyga-solus> mvo: and indentation
[15:32] <mvo> zyga-solus: so once we have a name i can add some tests and cleanup around this and then use it in the default provider PR
[15:32] <zyga-solus> I'm tweaking locally, one more moment please
[15:33] <mvo> sure
[15:35] <pedronis> my internet connection is flaky
[15:38] <zyga-solus> ok
[15:41] <kyrofa> sergiusens, shall I queue up a non-xenial run on snapcraft#1656 ? Perhaps not bionic though as it seems the biggest queue
[15:41] <mup> PR snapcraft#1656: integration tests: skip shared ROS test on non-xenial <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/1656>
[15:41] <zyga-solus> mvo: pushed to my branch of the same name
[15:42] <kyrofa> Oh bionic is looking pretty decent for upstream actually
[15:42] <zyga-solus> kyrofa: forever people googling for "bionic libc ..." will curse ubuntu
[15:43] <kyrofa> zyga-solus, I've never once googled "xenial libc" :P
[15:43] <zyga-solus> kyrofa: bionic as the android libc
[15:43] <kyrofa> Oh, the other way around-- I thought you meant they would find android results when they were looking for ubuntu. Gotcha
[15:43] <kyrofa> Yeah they probably will!
[15:43] <zyga-solus> yeah, I think >> android than ubuntu
[15:44] <mvo> zyga-solus: thank you! Not sure I like "Restore", maybe "Load"?
[15:44] <zyga-solus> mvo: sure
[15:44] <zyga-solus> mvo: I was thinking that it should live in overlord
[15:44] <zyga-solus> but that is somewhat black-hole logic
[15:45] <zyga-solus> eventually everything will be in overlord
[15:45] <zyga-solus> so instead I think it makes sense to speak of interfaces and state as interfaces/ifstate
[15:45] <sergiusens> kyrofa just do zesty; bionic and artful will fail adt anyways
[15:46] <mvo> zyga-solus: re overlord> I kept it there mostly because we have all state related things there. beside daemon/ itself all the things that are importing/manipulating state are under overlord afaict
[15:47] <sergiusens> elopio kyrofa can we do that meeting one hour later? This is the time I try to avoid meetings
[15:48] <mvo> zyga-solus: maybe it is one of those - we need gustavo PRs :) - but happy to use your PR as the starting point (except for "Restore" which feels a bit off to me)
[15:48] <kyrofa> sergiusens, yep
[15:48] <zyga-solus> mvo: sure
[15:48] <elopio> sergiusens: no problem.
[15:48] <zyga-solus> mvo: Load is fine, please use that
[15:48] <mvo> zyga-solus: thanks
[15:48] <zyga-solus> mvo: look at the package imports in ifstate.go, we can . import interfaces to almost unify this with the rest of the cod there
[15:48] <kyrofa> snappy-m-o, autopkgtest 1656 zesty:i386
[15:49] <snappy-m-o> kyrofa: I've just triggered your test.
[15:49] <kyrofa> That queue is non-existent
[15:49] <zyga-solus> mvo: some things could move sideways to utils.go (AddImplicitSlot, etc)
[15:50] <zyga-solus> mvo: or elsewhere, as appropriate
[15:50] <zyga-solus> mvo: it would also help to, at least in my eyes, to connect the interfaces.Repository to state handling, at least it would be "close"
[15:52] <mvo> zyga-solus: not sure I understand what you have in mind. " . import interfaces" - what does ". import" mean?
[15:52] <zyga-solus> import ( . "github.com/snapcore/snapd/interfaces" )
[15:52] <zyga-solus> then you can say Load(...) (*Repository, error)
[15:53] <zyga-solus> without having to preprend "interfaces." to most types
[15:55] <mvo> hm, not sure I like that, maybe just because its unfamiliar (and its friday :)
[15:55] <zyga-solus> mvo: we use it to import check.v1 (almost) everywhere
[15:55] <zyga-solus> mvo: anyway, just an idea, since this code mostly deals with interface types
[15:56] <zyga-solus> mvo: what do you think about 4144
[15:57] <mup> PR snapd#4147 opened: ifacestate: refactor and extract ifacestate/repo <Created by mvo5> <https://github.com/snapcore/snapd/pull/4147>
[15:57] <mvo> zyga-solus: ups, sorry, reading now
[15:58] <roadmr> diddledan: hey you requested a bunch of snap transfers from you to snapcrafters. Did snapcrafters agree to this? :)
[16:03] <pedronis> mvo: why is New  is in that package,  btw having a New for a type not defined there is strange
[16:03] <kalikiana> brb
[16:03] <zyga-solus> pedronis: look at my proposal in the same branch under my account
[16:06] <mvo> pedronis: yeah, zyga-solus was suggesting "Restore" we also discussed "Load"
[16:06] <zyga-solus> pedronis: I also moved it to interfaces/ifstate since it's closely coupled to types there
[16:06] <zyga-solus> pedronis: but just more ideas
[16:07] <pedronis> ifstate is a weird name
[16:08] <roadmr> diddledan: also - is build.snapcraft.io still misbehaving? I just registered and built a snap without any issues
[16:09] <zyga-solus> pedronis: I also tried interface/state but then I imported it as ifstate in overlord
[16:12] <pedronis> it's doing very different things
[16:12] <pedronis> I fear we need to think a bit more
[16:12] <pedronis> there's not a stronge relation between repo stuff and conns stuff for example
[16:12] <mup> PR snapd#4143 closed: snapctl: disable stop/start/restart (2.29) <Created by stolowski> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4143>
[16:14] <zyga-solus> no? I think repo is mostly about storing what is connected
[16:14] <mvo> pedronis: yeah, it seems a bit loose right now, the PR is the first discussion point (the most minimal thing I could do to de-couple it)
[16:15] <pedronis> mvo: I really need to understand what you need, because the decoupling as such doesn't make sense to me
[16:15] <pedronis> it feels very arbitrary
[16:16] <mvo> pedronis: my use case is that I want to answer the question "is this content interface connected" in snapstate when I decide if I need to download the default-provider
[16:16] <mvo> pedronis: there is another use case in another branch but that is for later (but also 2.30)
[16:17] <pedronis> I don't see how moving ReloadConnections relates to that
[16:18] <zyga-solus> pedronis: ReloadConnections is really Repository.Import(state)
[16:18] <pedronis> sorry, I don't understand
[16:19] <pedronis> how do you get to repo?
[16:19] <pedronis> do you build a different one in snapstate?
[16:19] <pedronis> I'm probably super confused
[16:19] <zyga-solus> no, sorry
[16:19] <zyga-solus> overlord keeps one repository instance around
[16:19] <pedronis> ?
[16:20] <pedronis> and passes it to snapstate?
[16:20] <zyga-solus> exposes certain functionality, I didn't look exactly if that passes the whole repo or just one method from it
[16:20] <zyga-solus> my desire to keep the ifstate module closer to interfaces/ was because it's really about how the interface repository is serialized
[16:21] <zyga-solus> and "deserialized" from the state
[16:21] <pedronis> this branch doesn't change overload or snapstate
[16:21] <pedronis> afaict
[16:21] <mvo> pedronis: the new code loads a repo from state
[16:21] <pedronis> ?
[16:21] <mvo> pedronis: so it gets a snapshot of the current connection from the state to answer this question (what is connected right now)
[16:21] <zyga-solus> I mean there's nothing new in this, just a way to untangle some cyclic imports
[16:21] <pedronis> mvo: we create repos on teh fly all the time?
[16:22] <pedronis> where?
[16:22] <pedronis> I know how repo is used
[16:22] <pedronis> there was one repo
[16:22] <pedronis> inside ifacemanager
[16:22] <zyga-solus> pedronis: we don't create repos on the fly (fortunately!) :)
[16:22] <mvo> pedronis: we don't do that, my idea was to have code in snapstate that creates a repo on the fly in the future. but happy about alternative ideas
[16:23] <pedronis> mvo: what?
[16:23] <pedronis> that's kind of expensive
[16:23] <pedronis> also remember we are moving to have singletons for connections
[16:23] <pedronis> that's pawel work
[16:23] <pedronis> so that will not work
[16:24] <mvo> pedronis: meh, I was not following that new work, which PR should I look at?
[16:24] <pedronis> mvo:  is not done yet
[16:24] <pedronis> mvo: anyway creating repos on the fly is a  bad idea
[16:24] <zyga-solus> I agree with pedronis
[16:24] <zyga-solus> I wasn't expecting on-the-fly repos
[16:24] <mvo> pedronis: fair enough. what options do we have?
[16:24] <pedronis> mvo: have you looked at how assertstate deals with the assertions db ?
[16:25] <pedronis> we stick it in the cache
[16:25] <pedronis> and then can accessors  that do  state -> cache -> db   ->  answer questions
[16:25] <mup> PR snapd#4147 closed: ifacestate: refactor and extract ifacestate/repo <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/4147>
[16:25] <mvo> pedronis: ok, I check that out, this looks good
[16:26] <mvo> pedronis: I close the PR and look at the alternative approach later (or Monday). thanks for your input!
[16:26] <zyga-solus> I think it's a good idea
[16:27] <pedronis> mvo: sorry if I was bit harsh,  but refactoring without intended uses  are hard to parse
[16:27] <pedronis> it's not about the code as such, it's more how it's going to be used
[16:28] <mvo> pedronis: no worries, I got the input that I needed :) i.e. the important part to me is how snapstate can get data from the repo and I think you pointed to a good solution which is great
[16:28] <pedronis> mvo: you'll probably  need anyway  a subpackage of ifacestate because of circularity but it can be focused on querying
[16:29] <mvo> pedronis: yeah, I think so too
[16:44] <pedronis> spread tests are very flaky again :/
[16:46] <zyga-solus> what failed?
[16:46] <pedronis> lots of different things
[16:46] <pedronis> all a bit random
[16:48] <zyga-solus> worst kind :/
[17:04]  * kalikiana going to wrap up for the day
[17:07] <mthaddon> hi folks, I've been able to install this (classic) snap locally. Any idea why the snapstore doesn't like it? https://pastebin.ubuntu.com/25880784/
[17:08] <zyga-solus> mthaddon: no idea, how did you make it?
[17:09] <roadmr> mthaddon: can you put that somewhere I can get to it? I'll run the review tools on it and see what the boggle is
[17:09] <mthaddon> zyga-solus: I'm not quite sure how to answer that question. Do you want to see the snapcraft.yaml file?
[17:09] <mthaddon> roadmr: will do
[17:09] <roadmr> mthaddon: that message can appear if you try to upload a random file, which does not appear to be your case
[17:09] <zyga-solus> mthaddon: no, just curious if it is hand made
[17:10] <mthaddon> I just ran "snapcraft" in a directory containing lp:codetree, fwiw
[17:19] <ogra_> mthaddon, file codetree_0.1.6_amd64.snap
[17:20] <ogra_> does it talk about being a squashfs file ?
[17:20] <mthaddon> yep, there now (retried at roadmr's request)
[17:24] <cachio> zyga-solus, I am getting this error: cannot snap-exec: cannot read info for "test-snapd-check-fs-access": stat /var/lib/snapd/snaps/test-snapd-check-fs-access_x2.snap: no such file or directory
[17:24] <cachio> zyga-solus, the file snap exists
[17:24] <cachio> any idea why it could happening?
[17:24] <zyga-solus> cachio: hmmm
[17:25] <zyga-solus> cachio: is the snap file mounted?
[17:25] <zyga-solus> any denials
[17:25] <zyga-solus> how did you experience this?
[17:26] <cachio> no denials
[17:26] <cachio> I am testing a new test
[17:26] <cachio> inlinode
[17:26] <cachio> do you want access?
[17:26] <zyga-solus> no, too tired today
[17:27] <zyga-solus> I can look on monday
[17:31] <cachio> zyga-solus, sure
[17:31] <cachio> zyga-solus, enjoy your weekend
[17:31] <zyga-solus> thank you, likewise
[17:52] <kyrofa> snappy-m-o, github subscribe 1656
[17:52] <snappy-m-o> kyrofa: I'll send you a message if a test fails in the pull request #1656 (integration tests: skip shared ROS test on non-xenial).
[17:52] <mup> PR #1656: snap: do not sort the result of `snap find` <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/1656>
[17:52] <kyrofa> snappy-m-o, github subscribe 165
[17:52] <snappy-m-o> kyrofa: I'll send you a message if a test fails in the pull request #165 (Enabling testing with new cli).
[17:52] <mup> PR #165: forgot to git add the tests <Created by chipaca> <Merged by zyga> <https://github.com/snapcore/snapd/pull/165>
[17:52] <kyrofa> snappy-m-o, github subscribe 1650
[17:52] <snappy-m-o> kyrofa: I'll send you a message if a test fails in the pull request #1650 (Release changelog for 2.35).
[17:52] <mup> PR #1650: Merge master onto #1623 to check tests <Created by niemeyer> <Closed by niemeyer> <https://github.com/snapcore/snapd/pull/1650>
[17:53] <kyrofa> That's gonna get old
[17:56] <elopio> sergiusens: kyrofa the other error on zesty was the git snap taking too long.
[17:57] <diddledan> roadmr: does this not count? https://github.com/orgs/snapcrafters/teams/snapcrafters/members
[17:57] <elopio> that's another one to simplify and demote to integration suite.
[17:57] <sergiusens> elopio we could probably just remove that test, does it give us anything? Mind double checking?
[17:57] <kyrofa> elopio, how do timeouts work on the autopkgtests? Is it like Travis, where it watches stdout?
[17:57] <sergiusens> If it is for classic, then I think we already have that in the integration suite
[17:57] <roadmr> diddledan: I saw that... well if you as a member of snapcrafters tell me you're happy with it, then I'll go ahead with the transfers
[17:57] <Chipaca> niemeyer: can we make mup ignore snappy-m-o?
[17:57] <diddledan> I'll move the repos across, too
[17:58] <roadmr> diddledan: I just didn't want to assume, you know what they say about that. As long as you're explicitly OK with it that's fine.
[17:58] <diddledan> I just hadn't got that far :-)
[17:58] <sergiusens> Chipaca or better yet, ignore random numbers like 1111
[17:58] <sergiusens> or #1111
[17:58] <mup> PR #1111: timeout,snap: add YAML unmarshal function for timeout.Timeout <Created by zyga> <Closed by zyga> <https://github.com/snapcore/snapd/pull/1111>
[17:58] <roadmr> diddledan: right, I do consider a repo under snapcrafters as explicit agrement :) which is why I transferred irccloud
[17:58] <Chipaca> #1111 is not a random number though
[17:59] <elopio> kyrofa: it depends. One part is a counter, from the start of the test. The other is what we added on pexpect, to fail earlier adjusting the expected timeout of a command ourselves
[17:59] <kyrofa> elopio, ah ha. Did pexpect timeout, then?
[17:59] <sergiusens> Chipaca no I thought about it twice in a row :-)
[17:59] <sergiusens> is #1234 random?
[17:59] <mup> PR #1234: debian: make snapd get its environ from /etc/environment <Created by chipaca> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/1234>
[17:59] <diddledan> roadmr: thanks for the prudence :-)
[18:00] <diddledan> roadmr: inadyn now in snapcrafters: https://github.com/snapcrafters/inadyn
[18:00] <elopio> sergiusens: that's the one that tests classic confinement. We can replace it with a more simple one that reads /tmp, or something.
[18:01] <elopio> kyrofa: yes: Expected output 'Snapped .*\\.snap' not found.
[18:01] <roadmr> diddledan: thanks! let me wrap up a call and I'll get on the transfers. Will be done today (EDT) for sure
[18:01] <diddledan> I'll note on each topic the new repo location
[18:02] <roadmr> diddledan: much appreciated, that'll help with the bureaucratic side of things.
[18:05] <mvo> cachio: 2.29.2 is available in beta for everything except amd64, that got corrupted and I'm rebuilding it
[18:06]  * Chipaca vanishes into the night
[18:16] <zyga-solus> mvo: corrupted?
[18:20] <mup> PR snapd#4148 opened: Release 2.29.2 <Created by mvo5> <https://github.com/snapcore/snapd/pull/4148>
[18:23] <cachio> mvo, great
[18:23] <cachio> mvo, starting ...
[18:28] <mvo> cachio: \o/
[19:12] <kyrofa> sergiusens, the deprecation notice for `snapcraft pack` is not in place, FYI
[19:22] <sergiusens> kyrofa would be good to get one I'd say.
[19:22]  * sergiusens crafts one up
[19:22] <sergiusens> which other one is missing?
[19:23] <kyrofa> sergiusens, that's it
[19:23] <kyrofa> (just dn6)
[19:28] <sergiusens> kyrofa oh, so the others just didn't make it to the website
[19:28] <kyrofa> sergiusens, yeah deployment is a different issue
[19:30] <sergiusens> kyrofa and I seem to know what it is ;-)
[19:33] <kyrofa> Hmm. noise][ nessita the store is rejecting all my daily uploads with "__all__: The upload does not appear to be a valid package."
[19:34] <zyga-solus> kyrofa: upload valid packages then
[19:34] <zyga-solus> what is this >> thing you are uploading
[19:35] <kyrofa> zyga-solus, yeah either the store is borked or LP is messing up every single build :P
[19:36] <zyga-solus> kyrofa: __all__ your base are belong to us
[19:37] <noise][> kyrofa: weird, can you grab the snap and try to install it locally?
[19:38] <zyga-solus> kyrofa: but one thing is good
[19:38] <zyga-solus> kyrofa: at least the store is not implemented in perl
[19:39] <kyrofa> noise][, yeah, works fine. https://launchpad.net/~nextcloud-snappy-dev/+snap/nextcloud-daily-master/+build/101331
[19:42] <noise][> weird
[19:42] <noise][> can you file a bug and we can get someone to take a look on monday?
[19:44] <sergiusens> kyrofa read this one please https://github.com/canonical-docs/snappy-docs/pull/145
[19:44] <mup> PR canonical-docs/snappy-docs#145: deprecation notice number 6 <Created by sergiusens> <https://github.com/canonical-docs/snappy-docs/pull/145>
[19:47] <sergiusens> kyrofa refresh if you've opened it, I forgot to `git add` my mods to `index.md`
[19:48] <kyrofa> sergiusens, oh good catch on the index
[20:07] <sergiusens> kyrofa ok, I have satisfied your demands!
[20:07] <sergiusens> if you +1 I'll merge
[20:10] <sergiusens> kyrofa oh, my write access has been revoked
[20:10] <kyrofa> Haha, bam!
[20:10] <sergiusens> davidcalle ^
[20:11] <davidcalle> kyrofa: did it? I'm reading the PR
[20:12] <davidcalle> kyrofa: sergiusens: has it been revoked for both of you?
[20:12] <kyrofa> davidcalle, I was never cool enough to have it in the first place
[20:12] <davidcalle> kyrofa: let's fix this
[20:14] <kyrofa> davidcalle, well hey! Thanks!
[20:15] <davidcalle> kyrofa: speaking of PR, how do you feel about these link changes: https://github.com/canonical-docs/snappy-docs/pull/136/files (in language guides: "https://forum.snapcraft.io" -> "https://forum.snapcraft.io/t/process-for-reviewing-aliases-auto-connections-and-track-requests/455 "
[20:15] <mup> PR canonical-docs/snappy-docs#136: Point forum links in guides at requests guidelines topic <Created by caldav> <https://github.com/canonical-docs/snappy-docs/pull/136>
[20:18] <kyrofa> davidcalle, yeah, +1 from me
[20:19] <davidcalle> ty
[20:27] <kyrofa> Oh my gosh the store is so slow today... I'm getting 80k
[20:29] <noise][> kyrofa - API, download from CDN, ??
[20:29] <noise][> "store" is a pretty broad term
[20:29] <kyrofa> noise][, `snap download` whatever that is
[20:32] <noise][> kyrofa: host 068ed04f23.site.internapcdn.net, and then check traceroutes to the IPs
[20:51] <mup> PR snapd#4104 closed: cmd/snap-update-ns: add logging to snap-update-ns <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4104>
[22:34] <mup> PR snapcraft#1656 closed: integration tests: skip shared ROS test on non-xenial <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1656>
[22:35] <sergiusens> snappy-m-o autopkgtest 1650 xenial:amd64 xenial:armhf xenial:arm64 zesty:amd64 zesty:armhf zesty:arm64 artful:amd64 artful:armhf artful:arm64 bionic:amd64 bionic:armhf bionic:arm64
[22:35] <snappy-m-o> sergiusens: I've just triggered your test.
[22:51] <mup> PR snapd#4149 opened: tests: new tests for network setup control and observe interfaces <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/4149>
[23:31] <kyrofa> Huh, the bot didn't tell me that the test failed
[23:31] <kyrofa> snappy-m-o, github subscribe 1650
[23:32] <snappy-m-o> kyrofa: I'll send you a message if a test fails in the pull request #1650 (Release changelog for 2.35).
[23:32] <mup> PR #1650: Merge master onto #1623 to check tests <Created by niemeyer> <Closed by niemeyer> <https://github.com/snapcore/snapd/pull/1650>
[23:38] <kyrofa> Oh man, totally missed that circle CI can do periodic jobs, now!
[23:38] <kyrofa> elopio, FYI ^^
[23:39] <kyrofa> elopio, did you also know you could run a job with SSH enabled for debugging?
[23:50] <elopio> I didn't know.