[05:54] <wolter> Hi, can somebody teach me how to reprofile my ubuntu karmic koala system
[05:55] <nigelb> wolter: please ask in #ubuntu, that is the main support channel.
[05:55] <wolter> ok, thanks... nobody has replied to me, but ill keep the persistence going
[20:57] <stasi_> hello!


[00:23] <Rich4> Hey
[00:24] <jrib> hi
[00:24] <jrib> rhythmbox is the troublemaker right?
[00:25] <Rich4> well, it was amarok until I uninstalled it
[00:25] <Rich4> but yes, the problem now is rhythmbox
[00:25] <jrib> so it is all music players?
[00:25] <Rich4> yup
[00:25] <jrib> erm
[00:26] <Rich4> ?
[00:26] <Rich4> What do I do?
[00:26] <jrib> lets do a test
[00:27] <jrib> go to Preferred Applications in your preferences menu
[00:27] <Rich4> ok?
[00:28] <Rich4> multimedia preferred is set to rhythmbox
[00:28] <jrib> make it gedit
[00:31] <Rich4> do I check 'run in terminal' ?
[00:31] <jrib> sure
[00:32] <Rich4> what now
[00:32] <jrib> now try closing rhythmbox
[00:33] <Rich4> I have another problem--windows are stuck.
[00:33] <Rich4> cant be dragged or anything
[00:33] <jrib> we haven't fixed this one yet
[00:34] <Rich4> youre right
[00:34] <jrib> or is this new problem the result of closing rhythmbox?
[00:34] <Rich4> rhythmbox just opens
[00:34] <jrib> ok
[00:34] <jrib> revert the changes to Preferred Applications
[00:36] <Rich4> revert = re-select rhythmbox?
[00:37] <jrib> yeah
[00:37] <jrib> new theory...
[00:38] <jrib> well, first, you are using desktop effects right?
[00:50] <Rich4> jrib: I have another problem there
[00:54] <Rich4> jrib: I was using 'wobble' effects. I turned off effects and rhythmbox still stays open
[00:54] <jrib> ok, so now you have window borders right?
[00:55] <jrib> Rich4: go to system -> preferences -> keyboard shortcuts  and disable all shortcuts for the music player
[00:56] <Rich4> there are none
[00:57] <jrib> "Media Player"
[00:57] <jrib> "Play"
[00:57] <jrib> "Pause"
[00:57] <jrib> etc...
[00:58] <Rich4> so pretty much all the sound shortcuts
[00:58] <jrib> sure
[01:02] <Rich4> done
[01:03] <jrib> close rhythmbox
[01:04] <Rich4> it reopens
[01:04] <jrib> ugh
[01:04] <jrib> ok
[01:04] <jrib> open a terminal
[01:05] <Rich4> ok
[01:06] <jrib> we are going to temporarily move rhythmbox
[01:06] <Rich4> coding?
[01:06] <jrib> sudo mv /usr/bin/rhythmbox{,.backup}
[01:08] <Rich4> ok.. thats done
[01:08] <jrib> close rhythmox
[01:09] <Rich4> its closed.
[01:09] <jrib> so now nothing reopens?
[01:11] <Rich4> :)
[01:11] <jrib> ok now pastebin ~/.xsession-errors
[01:11] <Rich4> what will that do
[01:11] <jrib> it will show me errors
[01:12] <jrib> !pastebin
[01:12] <ubotu> pastebin is a service to post large texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu-nl.org (make sure you give us the URL for your paste - see also the #ubuntu channel topic)
[01:12] <jrib> since right now you cannot open rhythmbox
[01:17] <Rich4> bash: pastebin: command not found
[01:17] <jrib> it is not a command, see what ubotu said
[01:19] <Rich4> no I posted "pastebin ~/.xsession-errors"
[01:19] <Rich4> err. used that and that was my result
[01:20] <jrib> url?
[01:20] <jrib> you open /.xsession-errors in a text editor and pastebin the contents
[01:21] <Rich4> so this isnt console?
[01:21] <jrib> no
[01:28] <Rich4> ok Its open
[01:29] <jrib> pastebin it
[01:30] <jrib> copy and paste it into the http://paste.ubuntu-nl.org site
[01:33] <Rich4> what syntax?
[01:35] <jrib> any
[01:35] <Rich4> what about ------- ?
[01:36] <Rich4> what do I do now?
[01:36] <jrib> tell me the url
[01:37] <Rich4> http://paste.ubuntu-nl.org/43199/
[01:39] <jrib> Rich4: run 'rhythmbox.backup' in a termial
[01:41] <Rich4> coding?
[01:42] <jrib> just what is inside the ''
[01:43] <Rich4> ok its open
[01:43] <jrib> close it
[01:43] <Rich4> done
[01:44] <jrib> does it open again?
[01:44] <Rich4> no
[01:45] <jrib> Rich4: before we go on, rhythmbox is not in cron job right?
[01:45] <Rich4> cron job?
[01:45] <jrib> what is the output of 'crontab -l' and 'cat /etc/crontab'?
[01:50] <Rich4> "no crontab for rich"
[01:50] <Rich4> and
[01:50] <Rich4> "# /etc/crontab: system-wide crontab
[01:50] <Rich4> # Unlike any other crontab you don't have to run the `crontab'
[01:50] <Rich4> # command to install the new version when you edit this file
[01:50] <Rich4> # and files in /etc/cron.d. These files also have username fields,
[01:50] <Rich4> # that none of the other crontabs do.
[01:50] <Rich4> SHELL=/bin/sh
[01:50] <Rich4> PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
[01:50] <Rich4> # m h dom mon dow user  command
[01:50] <Rich4> 17 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
[01:50] <Rich4> 25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
[01:50] <Rich4> 47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
[01:50] <Rich4> 52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
[01:50] <Rich4> #"
[01:51] <jrib> pastebin next time Rich4
[01:52] <Rich4> sry
[01:52] <Rich4> I'll remember that
[01:52] <jrib> ok, do 'sudo mv /usr/bin/rhythmbox{.backup,}
[01:52] <jrib> ok, do 'sudo mv /usr/bin/rhythmbox{.backup,}'
[01:53] <Rich4> now it has the opening problem
[01:53] <jrib> wait
[01:53] <jrib> did you open it yourself first or did it open on its own?
[01:54] <Rich4> I pressed [enter] in konsole
[01:54] <Rich4> then it prompted pw which I entered
[01:56] <jrib> and then rhythmbox opened on its own, right?
[01:56] <Rich4> yes
[01:56] <Rich4> I believe the same problem began again
[01:56] <Rich4> what did that command do..?
[01:56] <jrib> yes, we haven't changed anything
[01:57] <jrib> we moved rhythmox back
[01:57] <Rich4> kk
[01:57] <jrib> ok, do 'sudo mv /usr/bin/rhythmbox{.backup,}'
[01:57] <jrib> and open up a text editor
[01:58] <Rich4> the same line again?
[01:59] <Rich4> # /etc/crontab: system-wide crontab
[01:59] <Rich4> # Unlike any other crontab you don't have to run the `crontab'
[01:59] <Rich4> # command to install the new version when you edit this file
[01:59] <Rich4> # and files in /etc/cron.d. These files also have username fields,
[01:59] <Rich4> # that none of the other crontabs do.
[01:59] <Rich4> SHELL=/bin/sh
[01:59] <Rich4> PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
[01:59] <Rich4> # m h dom mon dow user  command
[01:59] <Rich4> 17 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
[01:59] <Rich4> 25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
[01:59] <Rich4> 47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
[01:59] <Rich4> 52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
[01:59] <Rich4> #
[01:59] <jrib> ...
[01:59] <Rich4> sry :(
[02:00] <Rich4> It said:
[02:00] <Rich4> mv: cannot stat `/usr/bin/rhythmbox.backup': No such file or directory
[02:00] <jrib> it is a different command
[02:00] <jrib> oh you are right, my mistake
[02:00] <jrib> ok, do 'sudo mv /usr/bin/rhythmbox{,.backup}'
[02:01] <Rich4> ok and you wanted me to open it in a txt editor
[02:02] <jrib> Rich4: what does 'echo ~' return for you?
[02:03] <Rich4> /home/rich
[02:04] <jrib> Rich4: we are going to replace rhythmbox with http://paste.ubuntu-nl.org/43207/
[02:05] <jrib> Rich4: verify for me that 'ls /usr/bin/rhythmbox' says it does not exist?
[02:09] <Rich4> ls: /usr/bin/rhythmbox: No such file or directory
[02:09] <jrib> Rich4: now do: sudo wget -O /usr/bin/rhythmbox http://paste.ubuntu-nl.org/43207/plain/
[02:10] <Rich4> ok
[02:10] <Rich4> what now
[02:10] <jrib> Rich4: now in your HOME, do you see a file called /home/rich/jrib_rhythmbox_debug?
[02:11] <jrib> Rich4: now in your HOME, do you see a file called /home/rich/jrib_rhythmbox_debug?
[02:11]  * jrib pummels the arrow key
[02:13] <Rich4> no, I dont think so
[02:14] <jrib> oh
[02:14] <jrib> try 'sudo chmod +x /usr/bin/rhythmbox'
[02:15] <Rich4> ok
[02:16] <Rich4> then?
[02:17] <jrib> Rich4: now in your HOME, do you see a file called /home/rich/jrib_rhythmbox_debug?
[02:20] <Rich4> nothing
[02:22] <jrib> do 'sudo mv /usr/bin/rhythmbox{,.fake} && sudo mv /usr/bin/rhythmbox{.backup,}'
[02:22] <jrib> then open rhythmbox
[02:23] <jrib> then do 'sudo mv /usr/bin/rhythmbox{,.backup} && sudo mv /usr/bin/rhythmbox{.fake,}'
[02:23] <jrib> then minimize rhythmbox
[02:30] <Rich4> done. rhythmbox is actually staying minimized
[02:30] <Rich4> what did that cmd do?
[02:30] <jrib> Rich4: now in your HOME, do you see a file called /home/rich/jrib_rhythmbox_debug?
[02:31] <Rich4> I see nothing
[02:31] <jrib> Rich4: it is the same as before, we just moved the executable (and replaced with the script)
[02:31] <jrib> what does 'cat ~/jrib_rhythmbox_debug' return?
[02:32] <Rich4> cat: /home/rich/jrib_rhythmbox_debug: No such file or directory
[02:33] <jrib> Rich4: any ideas on why that is.  To me that does not make sense
[02:33] <jrib> s/./?
[02:34] <jrib> it's clear that /usr/bin/rhythmbox is being called since without, your rhythmbox does not respawn
[02:36] <jrib> Rich4: what does 'md5sum /usr/bin/rhythmbox*' return?
[02:39] <Rich4> pastebin won't let me paste. claims I'm spamming
[02:39] <jrib> paste it here
[02:39] <Rich4> its 3 lines of text
[02:39] <Rich4> 2c06b471fda1c559910dfc953b0aa028  /usr/bin/rhythmbox
[02:39] <Rich4> 259905b6d61715a6c8a9152410d833f3  /usr/bin/rhythmbox.backup
[02:39] <Rich4> e98a31675b61f0f774748ae726ea83a3  /usr/bin/rhythmbox-client
[02:41] <jrib> Rich4: what does 'cat /usr/bin/rhythmbox' return?
[02:43] <Rich4> wont let me paste due to spam
[02:44] <jrib> use pastebin.com
[02:44] <Rich4> yeah thats what I mean
[02:44] <Rich4> oh nvm
[02:45] <Rich4> http://pastebin.com/d65bc6f92
[02:47] <jrib> ok, I don't know why it doesn't run then
[02:47] <jrib> I have one more thing to try and then I am out of ideas
[02:47] <jrib> lets get rid of the changes we made, do: sudo mv /usr/bin/rhythmbox{.backup,}
[02:51] <jrib> Rich4: done with that?
[02:55] <Rich4> uh
[02:56] <Rich4> yeah
[02:56] <Rich4> but now rhythmbox just opens again
[02:57] <jrib> yes, you don't understand what we have been doing?
[02:57] <Rich4> yes this replaced the backup, correct?
[02:58] <Rich4> err.. used the backup TO restore it
[02:58] <jrib> when we move rhythmbox, it can't open
[02:59] <jrib> ok, last thing to try, run: metacity --replace
[03:01] <Rich4> huh?
[03:01] <Rich4> go to ctrl+f2 and run that?
[03:01] <jrib> in a terminal
[03:01] <Rich4> alt+f2*
[03:01] <Rich4> oh
[03:02] <Rich4> what did that do?
[03:02] <Rich4> because rhythmbox still just opens
[03:02] <jrib> just ran the window manager in a terminal
[03:02] <jrib> do you get output?
[03:07] <Rich4> yes
[03:08] <Rich4> http://pastebin.com/d46fab613
[03:24] <jrib> Rich4: well that's what you want to google and look into it seems
[03:25] <jrib> good luck, I have to go in a bit
[04:20] <bazhang> very nice transcripts--thank you all.
[22:22] <MikeMeilleur> hi
[23:32] <rainwalker> jrib?
[23:32] <jrib> hi
[23:32] <jrib> rainwalker: do you have a preferred scripting language
[23:32] <rainwalker> hey
[23:32] <rainwalker> um...one that I can understand
[23:33] <rainwalker> unfortunately, I don't know any
[23:33] <jrib> alright
[23:33] <jrib> well we need to right a basic if then script that will check what the handedness is and change it appropriately
[23:34] <rainwalker> ooh I do know if/then scripts
[23:34] <rainwalker> vaguely
[23:34] <rainwalker> in C++
[23:34] <jrib> yeah, that would be overkill
[23:34] <jrib> imo
[23:34] <jrib> but a good exercise I suppose
[23:34] <rainwalker> I'll take your word for it
[23:35] <jrib> give me a minute to write it up
[23:35] <rainwalker> alright
[23:35] <rainwalker> in what? python?
[23:37] <jrib> nah, I'll do it in bash
[23:37] <rainwalker> oh ok
[23:37] <rainwalker> I think I've seen bash before
[23:38] <jrib> http://paste.ubuntu-nl.org/43350/
[23:39] <rainwalker> yeah that looks familiar
[23:39] <jrib> that should work
[23:40] <rainwalker> lets find out...
[23:41] <rainwalker> yep!
[23:41] <jrib> haha, I found http://sarbayes.org/ctwardy/toggle-mouse on google
[23:42] <rainwalker> but I have to choose if I want to run it or display it's contents every time
[23:42] <jrib> nah
[23:42] <rainwalker> I do
[23:42] <jrib> make it executable and create a launcher for it
[23:43] <rainwalker> sweet!
[23:43] <rainwalker> thank you!
[23:43] <jrib> np
[23:43] <jrib> if you do want to learn some scripting, python is very nice, check it out
[23:43] <rainwalker> alright, I think I might
[23:43] <rainwalker> what about bash?
[23:44] <nalioth> python allows more freedom
[23:44] <jrib> It helps to pick up the basic bash stuff like conditionals and loops, but for anything more than a couple of lines, run to python
[23:44] <rainwalker> ah ok


[05:43] <doc_holiday2112[> How can I reformat my Galaxy Tab A to be able to install Ubuntu??
[14:00] <brazil2023[m]> Hello everyone!
[14:00] <brazil2023[m]> Are there notebooks for sale with Ubuntu Studio already installed?
[15:56] <OvenWerks> brazil2023[m]: I do not expect there are any computers with ubuntustudio already installed. However, Eickmeyer would know about laptops with kubuntu already installed which is more than half already done.
[15:59] <OvenWerks> brazil2023[m]: Ubuntu Studio starts from a Kubuntu base and adds software and tweaks to the base. There is a utility called ubuntustudio-installer which will add these tweaks in an easy manner. Do be aware that it seems to be pretty tiny on today's hi dpi screens but it is still very usable.
 "doc_holiday2112: Unlikely, sadly..." <- OK, Thank you for confirming that, and also, for the info about where to look for more help as well.


[14:54] <_MMA_> newz2000: While using the wiki I got this message:
[14:54] <_MMA_> "Warning: You triggered the wiki's surge protection by doing too many requests in a short time. Please make a short break reading the stuff you already got. When you restart doing requests AFTER that, slow down or you might get locked out for a longer time! "
[14:54] <_MMA_> Now, can this be triggered by having too many attachments displayed on a page?
[14:55] <thorwil> newz2000: same happened to me with the countdown banner submissionspage
[14:55] <newz2000> I have triggered surge protection before but not in that way
[14:55] <newz2000> however it is definitely possible
[14:55] <newz2000> do you have a page your working on?
[14:55] <_MMA_> https://wiki.ubuntu.com/Artwork/BreatheIconSet/Submissions
[14:56] <_MMA_> The PNG attachments aren't being displayed here for me anymore. Just the attachment text. I have to remove some anyway, but I thought this odd.
[14:57] <newz2000> yeah, that is odd
[14:57] <newz2000> let me look... going into a conference call in just a min though
[14:57] <_MMA_> k
[14:58] <_MMA_> Yep. I bet that's it. I removed some that have been added to the set already and they pop back up again. :)


[08:11] <Rhonda> Hey, who can I bug about a but in bug-watch-updater? :)
[08:11] <Rhonda> s/but/bug/
[08:12] <Rhonda> bug-watch-updater changes a debian bug to "Fix Released" even though when the bug was closed unversioned in Debian - which means that it's either not a bug or invalid.
[08:13] <wgrant> Rhonda: Is that a valid assumption now?
[08:13] <wgrant> When it was written, there was no version tracking :)
[08:16] <micahg> bug 701186 is similar, but not the same
[08:28] <Rhonda> wgrant: It's valid as long as noone does stupid things. ;)
[08:28] <wgrant> That's *not* a valid assumption :(
[08:29] <Rhonda> heh
[08:29] <Rhonda> To understand my statement better, I do regularly go through wrongly closed bugreports which hinder getting them archived in Debian, so …  "in theory" it's a valid assumption.
[08:30] <Rhonda> It just made me jump that one of my bugreports got marked as "Fix Released" when I was sure that it was an invalid bugreport in the first place.
[11:06] <idnar> I would say it's valid when the status of the bug in the Debian BTS is correct
[11:07] <idnar> and if you're going to assume that it's not correct, then obviously you can't rely on any information at all
[14:48] <mrjazzcat> bac: Do I need a LOSA to set the Release Manager for a commercial subscription project?  Can't find a link for that on ...project/trunk
[14:48] <bac> mrjazzcat: what project?
[14:49] <mrjazzcat> bac: https://launchpad.net/ness/trunk -- Want to set RM to Albert Stone ~ahs3
[14:49]  * bac looks
[14:50] <bac> mrjazzcat: next to "Release Manager" do you see the little pencil icon?
[14:50] <mrjazzcat> bac: no
[14:50] <mrjazzcat> bac:  perhaps I setup the empty branch wrong.
[14:51] <bac> mrjazzcat: i can edit and set the RM for you.  i'm surprised you cannot.
[14:52] <mrjazzcat> bac: I do have peon powers, after all ;-)
[14:53] <bac> mrjazzcat: but you are in pmteam, no
[14:53] <mrjazzcat> bac:  Yes, I certainly hope so
[14:53] <bac> mrjazzcat: :)  -- the RM has been set
[14:54] <mrjazzcat> bac:  Thanks.  I'll go double check that I'm in pmteam, but I can't imagine I could do anything without that.
[14:54] <mrjazzcat> bac:  have a great day
[14:54] <bac> thanks mrjazzcat
[16:10] <Laney> I asked this the other day but got no reply: Do packages have to be in the Ubuntu primary archive to be able to have PPU uploaders set?
[16:45] <bigjools> Laney: PPU?
[16:46] <Laney> per package uploader
[16:46] <bigjools> and bac, are you asleep?
[16:46] <bigjools> Laney: yes, you can't set an upload permission for a non-existent package
[16:46] <Laney> I mean, is being in a PPA enough?
[16:47] <Laney> I don't know if this is the right terminology, but does that create a SPPH record? Is that what it needs?
[16:47] <bigjools> Laney: it has to be in the archive that you want to set the upload permission for
[16:47] <Laney> ok then, thanks
[16:48] <bigjools> Laney: I see what you're driving at - this is a known bug I think, it was filed the other day
[16:48] <bigjools> not sure how to get around it
[16:48] <Laney> I think I remember hearing that you could upload to a PPA and then add PPU bits
[16:48] <bigjools> Laney: that *might* work.
[16:48] <bigjools> I've never tested it
[16:48] <Laney> no I'm not asking for any particular fix, just wondering what the situation is
[16:49] <Laney> wgrant: since you know everything, do you know this? :-)
[16:52] <bigjools> Laney: I think it will work - LP just needs to know that the package exists
[16:53] <bigjools> having checked the code... :)
[16:53] <Laney> :P
[16:53] <Laney> thanks then, now I get to ask the TB to implement this change
[16:54] <Laney> (this is #562451 :P)
[17:17] <mpoirier> When uploading a kernel ppa to my project page, the process hangs after the kernel.tar.gz was tranferred - can someone help ?
[17:18] <mpoirier> bac: ping
[17:18] <bac> hi mpoirier
[17:18] <mpoirier> bac: the header claims you're hte guy to talk to...
[17:18] <bac> mpoirier: yep
[17:19] <bac> what's up?
[17:19] <mpoirier> bac: cool
[17:19] <mpoirier> I'm trying to get my kernel ppa to https://launchpad.net/~linaro-landing-team-ste/+archive/st-ericsson-u8500-public/+packages
[17:19] <mpoirier> bac: the command dput ppa:mathieu.poirier/st-ericsson-u8500-public linux-ux500_2.6.38-1001.5_source.changes
[17:19] <mpoirier> hangs after the kernel got tranferred.
[17:19] <mpoirier> bac: ood signature on /home/mpoirier/work/linaro/lag/linux-ux500_2.6.38-1001.5.dsc.
[17:19] <mpoirier> Uploading to ppa (via ftp to ppa.launchpad.net):
[17:19] <mpoirier>   Uploading linux-ux500_2.6.38-1001.5.dsc: done.
[17:19] <mpoirier>   Uploading linux-ux500_2.6.38-1001.5.tar.gz: 98274k/98275k
[17:20] <mpoirier> bac: it's stuck there and won't move.
[17:20] <mpoirier> bac: can you help me ?
[17:20] <bac> mpoirier: i can try
[17:22] <bac> mpoirier: this has failed repeatedly the same way?
[17:22] <mpoirier> yes, repeatedly.
[17:23] <mpoirier> I'm thinking that if it was releated to permissions, the dsc file would be rejected...
[17:23] <bac> mpoirier: let me see if i can find some answers for you.
[17:23] <mpoirier> bac: very cool.
[18:21] <bac> mpoirier: the log files look as if the upload succeeded.  are you certain it didn't?
[18:22] <mpoirier> bac: All I'm certain of is that I don't get a prompt back.
[18:22] <mpoirier> bac: it hangs there...
[18:22] <mpoirier> bac: did all the files make it ?
[18:27] <Darxus> Is there a tutorial that will tell me the basics of launchpad lib so I can repeat what is done here?  http://ftagada.wordpress.com/2011/01/05/ppa-stats-initial-impressions/
[18:27] <Darxus> Something that starts with "run the command 'python'" would probably be good.
[18:28] <Darxus> I'm reading https://help.launchpad.net/API/launchpadlib
[18:28] <Darxus> But it there seems to be a gap between the two, so I run python, load launchpadlib, and type "ppa", and it doesn't work.
[18:29] <bac> hi darxus
[18:30] <Darxus> Hi.
[18:30] <Darxus> It should not be so much freaking work just to see if anybody's using my packages :)
[18:33] <bac> Darxus: actually you're probably very close
[18:33] <bac> the blog entry you referenced takes some shortcuts
[18:33] <bac> they show the use of a ppa object but don't show how they got it.  'ppa' isn't a command, in there example it is an object
[18:34] <bac> you can look you your ppas via the 'ppas' method on a person object
[18:34] <Darxus> I suspected something like that.
[18:34] <Darxus> Ahh, thanks.
[18:34] <bac> Darxus: so you could do
[18:34] <bac> ppa = lp.me.ppas[0]
[18:35] <bac> where 'lp' is your launchpad object
[18:35] <bac> Darxus: does that make sense?
[18:35] <Darxus> Almost, trying...
[18:36] <Darxus> Can I do that without authenticating in launchpadlib?
[18:36] <bac> i doubt it
[18:36] <bac> you certainly can't refer to the lp.me object
[18:37] <Darxus> Right.
[18:37] <bac> Darxus: here's a tip: the package ubuntu-dev-tools has a script called 'lp-shell' and it is great for interactively playing with launchpadlib
[18:37] <Darxus> Thanks.
[18:37] <bac> it'll log you in and give you a lp object right off the bat
[18:37] <Darxus> Ahh, good, thanks.
[18:38] <bac> you have to do the authentication dance the first time, of course
[18:38] <bac> anyway, ping me here if you have more questions.  be sure to use my nick though or i might not notice
[18:41] <Darxus> Authentication seems to be failing because lynx isn't providing a referer.  Don't see anything related in my .lynxrc.
[18:42] <Darxus> Ah, system wide default.  Ugh.
[18:50] <Darxus> Huh, I verified through my own webserver logs that lynx is reporting a referrer, but I'm still getting "Launchpad requires a REFERER header to perform this action. There is no REFERER header present. This can be caused by configuring your browser to block REFERER headers."
[18:53] <Darxus> Changed my browser to links and that can't even get past the login prompt.
[18:56] <Darxus> >>> ppa
[18:56] <Darxus> <archive at https://api.edge.launchpad.net/1.0/~darxus/+archive/autopano-sift-c>
[18:56] <Darxus> Woo.
[18:57] <Darxus> Had to resort to running lp-shell locally, which used chrome instead of text browsers.
[19:04] <Darxus> NameError: name 'binary_package_publishing_history' is not defined
[19:04] <Darxus> Where do I get that from?
[19:06] <Darxus> And how do I get to a ppa that I don't own, specifically https://launchpad.net/~spamassassin/+archive/spamassassin-daily ?
[19:17] <bac> hi Darxus:
[19:18] <bac> Darxus: you can get the object for 'spamassassin' and then get their ppas
[19:18] <bac> Darxus: http://paste.ubuntu.com/664467/
[19:24]  * Darxus screams.
[19:24] <Darxus> I was trying to do something like that... this example didn't have the quotes, and apparently that matters:  "    team = launchpad.people[team]
[19:24] <Darxus> " from https://help.launchpad.net/API/Examples
[19:24] <Darxus> Thanks.
[19:25] <lifeless> Darxus: you will get better response from the non-edge servers
[19:26] <Darxus> I don't know what an edge or non-edge server is in this context.
[19:26] <lifeless> 06:56 < Darxus> <archive at https://api.edge.launchpad.net/1.0/~darxus/+archive/autopano-sift-c>
[19:27] <lifeless> get rid of the 'edge.' in that url.
[19:28] <Darxus> >>> binary_package_publishing_history
[19:28] <Darxus> NameError: name 'binary_package_publishing_history' is not defined
[19:28] <Darxus> How do I get binary_package_publishing_history to work?
[19:28] <Darxus> lifeless: Ah, I'm not doing anything with that url, as far as I'm concerned it's just telling me which ppa I'm looking at.
[19:29] <Darxus> Unless I'm more confused than I thought.
[19:29] <lifeless> you're using a web api
[19:29] <lifeless> that url is the url the data for the python object came from.
[19:29] <lifeless> so you're using the web url pointing to the edge servers - servers we are in the process of decomissioning
[19:32] <Darxus> lifeless: Are you suggesting I run lp-shell with an argument of "production" or something?
[19:33] <bac> Darxus: lp-shell should connect to production
[19:34] <bac> Darxus: 'binary_package_publishing_history' is not an object but a method call
[19:35] <lifeless> Darxus: where did you get lp-shell from ?
[19:35] <bac> lifeless: ubuntu-dev-tools
[19:36] <bac> lifeless: it is pretty handy
[19:37] <lifeless> bac: care to file a bug about it using edge ?
[19:37] <lifeless> bac: or, well we should check oneiric doesn't
[19:37] <lifeless> Darxus: are you running oneiric ?
[19:37] <bac> lifeless: well, we need to see what he's using.  the one for natty does not
[19:40] <bac> lifeless: here is the output from the natty version of the package: http://paste.ubuntu.com/664476/
[19:42] <lifeless> ok, thats encouraging
[19:42] <lifeless> I *thought* it had been fixed (and that was why I asked where he got it from :P)
[19:42] <Darxus> No, I'm running Maverick on the machine where lp-shell is working.
[19:43] <Darxus> So, I got hit counts from the latest package versions in the PPA I care about.
[19:43] <Darxus> Using https://bugs.launchpad.net/launchpad/+bug/139855/comments/42
[19:45] <Darxus> Cool, looks like removing the "status='Published'," is giving me exactly what I want.
[19:50] <Darxus> Thanks for the help.
[20:11] <tgm4883> Is there somewhere we should be reporting spam comments? https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/606598/comments/7
[20:23] <bac> hi tgm4883
[20:24] <bac> tgm4883: i'll take care of it.  usually people open a question against the launchpad project
[21:07] <tgm4883> bac, good to know, thanks
[22:19] <komputes> PROBLEM: Can't open attachment on this bug - oops: https://bugs.launchpad.net/ubuntu/+bug/722078
[22:28] <cody-somerville> Is there way to see all the bugs in a project a person or team is *not* subscribed to?


[00:34] <tiemonster> anyone lingering tonight?
[00:58]  * mhall119 lingers
[00:58] <tiemonster> mhall119: are the BSD and MIT licenses similar/compatible?
[00:59] <mhall119> Compatible at least, I'm not sure how similar
[00:59] <tiemonster> hmm
[00:59] <tiemonster> I'm not an expert in licensing
[01:00] <mhall119> me either
[01:00] <tiemonster> MIT seems like a good purpose "do whatever the heck you want with it" license, but a lot of Node.js stuff is BSD
[01:00] <mhall119> those are called lawyers
[01:00] <tiemonster> very specialized lawyers
[01:00] <mhall119> BSD is pretty much "do whatever the heck you want with it, just make sure you let everybody know where you got it from"
[01:05] <tiemonster> k
[02:30] <RoAkSoAx> mhall119: ping
[14:33] <mhall119> RoAkSoAx needs an always-on client
[14:41] <katyl> Anyone go to the Melbourne Lug?
[14:43] <mhall119> itnet7 probably
[14:45] <katyl> Moving down there sometime soon, wondering if I should go.
[14:45] <katyl> Never been a lug type'o guy.
[23:53] <greiser> hey


[15:00] <rbalint> o/
[15:00] <cyphermox> o/
[15:01] <waveform> o/
[15:01] <sil2100> o/
[15:02] <xnox> \o
[15:03] <rbalint> #startmeeting Weekly Ubuntu Foundations team
[15:03] <meetingology> Meeting started Thu Aug  8 15:03:07 2019 UTC.  The chair is rbalint. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:03] <meetingology> Available commands: action commands idea info link nick
[15:03] <rbalint> #topic Lightning rounds
[15:03] <rbalint> echo $(shuf -e vorlon bdmurray xnox tdaitx sil2100 rbalint cyphermox mwhudson juliank waveform)
[15:03] <rbalint> sil2100 mwhudson juliank bdmurray waveform cyphermox tdaitx xnox vorlon rbalint
[15:03] <sil2100> Oh no
[15:04] <sil2100> - SRU reviews and releases
[15:04] <sil2100> - A few quick kernel reviews
[15:04] <sil2100> - 18.04.3:
[15:04] <sil2100>   * Preparing and formatting the changelog
[15:04] <sil2100>   * Poking people for testing
[15:04] <sil2100>   * Fixing download urls for netboot images on the isotracker
[15:04] <sil2100>   * Spinning ubuntu-core 16 and 18 images, iterating on testing
[15:04] <sil2100>   * Linked core release process wiki to the PointReleaseProcess
[15:04] <sil2100> - Moved libpwquality in l-o-m from gnome to the common langpack packages
[15:04] <sil2100> - NEW review of ibus-avro
[15:04] <sil2100> - disk-space-estimate for snaps: change ready, finishing writing basic tests
[15:04] <sil2100> - Proposed an MP for livecd-rootfs to add the system-boot NoCloud datasource for all ubuntu-image images
[15:04] <sil2100> - Investigating reports of slow pi bootup time - we might want to consider backporting livecd-rootfs changes to bionic
[15:04] <sil2100> (done)
[15:04] <sil2100> (and I'm out the next 2 weeks)
[15:05]  * sil2100 pokes juliank
[15:05]  * juliank is poked
[15:06] <juliank> but desktop buggy
[15:06] <juliank>  * Hack around broken procenv in eoan breaking sbuild and pbuilder autopkgtest everywhere
[15:06] <juliank>  * hotfix python-apt so snapd builds in eoan (LP: #1837926), needs a cleaner fix, but that needs work in bindings
[15:06] <juliank>  * Released apt  1.9.2
[15:06] <juliank>  * Verify dpkg SRUs
[15:06] <juliank>  * Answered questions about which apt binary packages need upgrading needed for trusty ESM
[15:06] <juliank>  * Some initial analysis and workarounds in autopkgtest for the i386 autopkgtest queue being stuck, which turned out to be a gnutls bug (LP: #1839354)
[15:06] <juliank> (done)
[15:06] <waveform> * Worked on pi4 kernel patches; got a cleanly building tree under armhf (currently building arm64) which works on pi3 but not pi4 yet, still stripping out irrelevant patches
[15:06] <waveform> * Further testing on pi4-compatible u-boot; found it's semi-compatible across pi versions but we *may* still need conditional boot sections
[15:06] <waveform> * Built patches for u-boot postinst & pi gadget to handle conditional boot sections
[15:06] <waveform> * Investigating boot issue on arm64 pi images (appears to be kernel framebuffer)
[15:06] <waveform> (done)
[15:06] <cyphermox> I'll be off tomorrow, and Monday-Tuesday next week
[15:06] <cyphermox> libuv1 shepherding from -proposed: uploaded new nodejs with upstream fix
[15:06] <cyphermox> Rerunning various node-* autopkgtests
[15:06] <cyphermox> Writing the OpenVSwitch support spec for netplan
[15:07] <cyphermox> trying to get review for the NM plugin spec for netplan
[15:07] <cyphermox> Looked into no-writable-files-in-/etc for UC20
[15:07] <cyphermox> shim update: didn't get reviewed get, will do a new snapshot
[15:07] <cyphermox> preparing netplan release with the recently merged PRs
[15:07] <cyphermox> 🀄
[15:07] <xnox> tdaitx not in the channel?
[15:07] <xnox> * sprint last week
[15:07] <xnox> * prepared openvpn-server update for trusty / esm / #is
[15:07] <xnox> * prepared initrd updates for microcode handling on core16/18
[15:07] <xnox> * patches to linux-snap to use the right microcode packages
[15:07] <xnox> * expenses / notes / post-sprint jetlag (more to do)
[15:07] <xnox> * core20 snap, it build! it boots! console-conf fails!
[15:07] <xnox> * fixing console-conf... as it was not touched for like 2+ years
[15:07] <xnox> * lots of s390x tickets to work on
[15:08] <xnox> * attempt to unbreak unattended-upgrades pyflakes adt regression
[15:08] <xnox> * refreshed ubiquity
[15:08] <xnox> * new upstream release of s390-tools
[15:08] <xnox> done...
[15:08] <xnox> vorlon:
[15:08] <vorlon>  * worked with juliank and mwhudson to fix a gnutls28 bug on i386 that was breaking autopkgtests (LP: #1839354)
[15:08] <vorlon>  * proposed-migration curling
[15:08] <vorlon>  * preparation for kicking off public i386 discussion
[15:08] <vorlon>  * reviews of netplan PRs
[15:08] <vorlon>  * off tomorrow
[15:08] <vorlon> (done)
[15:09] <rbalint> * uploaded wslu 2.3.0
[15:09] <rbalint> * reopened MIR for libnftnl
[15:09] <rbalint> * verified and announced new WSL tarballs
[15:09] <rbalint> * uploaded unattended-upgrades 1.14 fixing a few recent issues
[15:09] <rbalint> * merged systemd 242-rc1, poking it to migrate
[15:09] <rbalint> * other proposed migration work
[15:09] <rbalint> (done)
[15:09] <rbalint> any questions?
[15:09] <cyphermox> rbalint: fwiw, libnftnl approved.
[15:09] <cyphermox> (it had already been MIRed, etc. etc.)
[15:09] <rbalint> cyphermox, thanks!
[15:10] <cyphermox> rbalint: carry on I guess :)
[15:10] <gaughen> what is that picture cyphermox ?
[15:10] <cyphermox> what picture?
[15:10] <rbalint> #topic Release incoming bugs
[15:10] <gaughen> 🀄
[15:10] <rbalint> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html#foundations-bugs
[15:10] <cyphermox> gaughen: a mahjong tile
[15:10] <gaughen> aaaah
[15:10] <gaughen> I couldn't tell
[15:10] <sil2100> It's a red dragon I guess?
[15:10] <gaughen> I put glasses on to try and see if that would help
[15:11] <gaughen> I thought it was a bow/arrow
[15:11] <gaughen> and he was indicating doneness by shooting an arrow at the next person
[15:11] <rbalint> hmm, no high or unclassified there.
[15:11] <rbalint> Bionic does not have new bugs either
[15:11] <sil2100> rbalint: guess we can move on then
[15:12] <rbalint> #topic Team proposed-migration report
[15:12] <rbalint> #link http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#foundations-bugs
[15:12] <rbalint> imagemagick is blocked on libheif mir
[15:12] <rbalint> i fixed unattended-upgrades regression for debconf
[15:14] <vorlon> rbalint: are you retrying the tests against new unattended-upgrades in -proposed?
[15:14] <rbalint> vorlon, yep
[15:15] <vorlon> ok
[15:15] <vorlon> xnox: btrfs-progs still blocked on curtin, and your comment to me on IRC did not give me clarity
[15:15] <rbalint> prometheus-blackbox-exporter is still sad, and i faced 404 in other tests from ftpmaster.internal
[15:15] <rbalint> i think there is something with ftpmaster.internal
[15:15] <vorlon> xnox: are you reverting this btrfs-progs change again, or are you teaching the curtin maintainers about or'ed dependencies?
[15:16] <vorlon> rbalint: if that's only on i386, that's the gnutls28 ubg
[15:16] <vorlon> bug
[15:17] <rbalint> vorlon, ok
[15:17] <vorlon> because systemd-resolved links against libgnutls, confinement means text relocations were rejected at startup time, name resolution fails if your env pulled gnutls from -proposed
[15:17] <vorlon> so yeah, I've retried that one now
[15:17] <vorlon> (the log clearly shows it trying to pull all packages from -proposed and then falling over)
[15:22] <rbalint> debconf: i'll retry with new u-u
[15:22] <rbalint> any taker for openssh?
[15:23] <vorlon> it's i386, I'm retrying it
[15:23] <vorlon> (and reading the logs afterwards)
[15:24] <vorlon> but I'll follow up
[15:24] <rbalint> u-u is mine
[15:24] <vorlon> it looks, at best, a flaky test
[15:24] <sil2100> livecd-rootfs - looks like it just needs a re-run, apparently the tests were running at a wrong moment
[15:25] <sil2100> Let me re-run it
[15:25] <vorlon> golang-1.12-race-detector-runtime seems to be just plain missing from the archive
[15:25] <cyphermox> I have been looking into netplan. I guess I better check what's up with pyyaml
[15:25] <vorlon> (so, golang-defaults blocked on the Debian maintainers)
[15:26] <rbalint> vorlon, ack
[15:26] <rbalint> cyphermox, do you take pyyaml then?
[15:26] <cyphermox> yessir.
[15:26] <rbalint> cyphermox, thanks!
[15:27] <rbalint> libvpx looks ok
[15:27] <vorlon> libvpx is a lib transition
[15:27] <vorlon> I'll kick off some rebuilds
[15:27] <rbalint> vorlon, ok, thanks!
[15:27] <rbalint> #topic AOB
[15:29] <gaughen> rbalint, did we finish the proposed-migration list?
[15:29] <rbalint> gaughen, yes
[15:30] <sil2100> No AOB from me
[15:30] <rbalint> so if there is no AOB, i'm closing the meeting in 1m :-)
[15:30] <sil2100> Well, there is one thing...
[15:30] <sil2100> It's international cat day
[15:30] <sil2100> I guess that's important enough to discuss as AOB?
[15:31] <rbalint> sil2100, i should have used shuf | cat
[15:31] <sil2100> !
[15:31] <sil2100> ;)
[15:31] <sil2100> 🐈
[15:31] <sil2100> (but seriously, no other AOB here)
[15:31] <rbalint> #endmeeting
[15:31] <meetingology> Meeting ended Thu Aug  8 15:31:53 2019 UTC.
[15:31] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2019/ubuntu-meeting.2019-08-08-15.03.moin.txt
[15:31] <juliank> I'm going to visit my parents and cat soon
[15:31] <rbalint> thank you all!
[15:32] <juliank> re: cat day
[15:32] <sil2100> rbalint: thanks for chairing!
[15:32] <juliank> CATURDAY++
[15:32] <gaughen> thanks rbalint
[15:32]  * waveform will go look for his tac
[15:33] <gaughen> who's the next chair?
[15:33]  * juliank
[15:33] <juliank> ?
[15:33] <gaughen> yes


[11:32] <rbasak> https://help.launchpad.net/Code/Git says "https://code.launchpad.net/~OWNER/PROJECT/+git/REPOSITORY This identifies a repository for an upstream project.
[11:32] <rbasak> "
[11:32] <rbasak> I'm a little confused by this. To create and push from the git client, do I "git remote add lp lp:~OWNER/PROJECT/+git/REPOSITORY"?
[11:33] <Faux> git remote add lp https://code.launchpad.net/~OWNER/PROJECT/+git/REPOSITORY
[11:33] <rbasak> Because for example we've been pushing to https://code.launchpad.net/~ubuntu-server-dev/ubuntu/+source/logwatch/+git/logwatch, but in that case the git push URL is git+ssh://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/logwatch and +git doesn't appear there.
[11:33] <Faux> In that case, totally ignore me.
[11:34] <rbasak> So I tried git remote add lp lp:~racb/drain
[11:34] <rbasak> Where drain is not a probject but just a random unrelated repository
[11:34] <rbasak> But I get fatal: remote error: Project 'drain' does not exist.
[11:35] <rbasak> So what is the git push URL for a "personal" repository with no particular connection to any project or package?
[11:36] <cjwatson> lp:~racb/+git/drain
[11:36] <cjwatson> +git is not present in all git URLs
[11:36] <rbasak> cjwatson: OK, so that makes sense to me from the docs. But then why does the logwatch package in ~ubuntu-server-dev example not have +git in it?
[11:36] <rbasak> (because the docs do)
[11:36] <cjwatson> rbasak: alias
[11:37] <rbasak> Ah, OK.
[11:37] <rbasak> Thanks
[11:37] <cjwatson> rbasak: ~ubuntu-server-dev/ubuntu/+source/logwatch identifies the default repository for that distribution source package, the fully-qualified unique name of which is ~ubuntu-server-dev/ubuntu/+source/logwatch/+git/logwatch
[11:37] <cjwatson> rbasak: personal (like +junk in bzr) repositories don't have the concept of a default repository, so they always contain +git
[11:41] <rbasak> cjwatson: I see. That helps me make a mental model of what's going on, thanks.
[11:41] <rbasak> (I pushed to ~racb/+git/drain successfully)
[11:43] <cjwatson> the web UI tries to shorten git push URLs and such when it can, but it currently doesn't do that for its own URLs (i.e. those on code.launchpad.net) for complicated reasons
[11:50] <rbasak> Got it, thanks. BTW, thanks again for the git support. It's been solid for me so far, and our team has just started using git merge proposals for merge reviews.
[11:53] <cjwatson> Ah, excellent.  OLS is using it a bit more for some new projects, and hopefully we'll get LP itself onto it soon.
[13:49] <su_v> on-going spam wave in https://answers.launchpad.net/inkscape (~950 spam questions) - TIA for suspending the accounts and hiding their questions.
[16:38]  * cjwatson catches up with the spam attack


[04:21] <mup> Bug #1815843 changed: pod kvm fails to boot for install, boot-kernel transfer size is wrong <cdo-qa> <MAAS:Expired> <https://launchpad.net/bugs/1815843>
[11:06] <mup> Bug #1863597 opened: rack controller fails to register because of failure updating interfaces <MAAS:Triaged> <https://launchpad.net/bugs/1863597>
[11:15] <mup> Bug #1863597 changed: rack controller fails to register because of failure updating interfaces <MAAS:Triaged> <https://launchpad.net/bugs/1863597>
[11:22] <mup> Bug #1863597 opened: rack controller fails to register because of failure updating interfaces <MAAS:Triaged> <https://launchpad.net/bugs/1863597>


[22:58] <purencool> Good Morning Ubuntu lovers have been play with Nginx as everyone says its the new hotness. What do others think?


[00:12] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #994: SUCCESS in 12 min: https://kci.pangea.pub/job/mgmt_merger/994/
[00:22] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #11: FAILURE in 8 min 50 sec: https://kci.pangea.pub/job/bionic_unstable_kget/11/
[00:22] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kscd build #11: FAILURE in 9 min 0 sec: https://kci.pangea.pub/job/bionic_unstable_kscd/11/
[00:23] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kscd build #57: FAILURE in 10 min: https://kci.pangea.pub/job/artful_unstable_kscd/57/
[00:27] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_babe build #12: STILL FAILING in 13 min: https://kci.pangea.pub/job/bionic_unstable_babe/12/
[00:27] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_babe build #135: STILL FAILING in 14 min: https://kci.pangea.pub/job/artful_unstable_babe/135/
[00:28] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #82: FAILURE in 35 sec: https://kci.pangea.pub/job/artful_unstable_kget/82/
[00:44] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kimagemapeditor build #13: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/bionic_unstable_kimagemapeditor/13/
[00:45] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kolf build #11: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/bionic_unstable_kolf/11/
[00:45] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_sddm build #11: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/bionic_unstable_sddm/11/
[00:50] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kmix build #12: STILL FAILING in 37 min: https://kci.pangea.pub/job/bionic_unstable_kmix/12/
[01:05] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kalzium build #11: STILL UNSTABLE in 51 min: https://kci.pangea.pub/job/bionic_unstable_kalzium/11/
[01:05] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_elisa build #11: STILL UNSTABLE in 51 min: https://kci.pangea.pub/job/bionic_unstable_elisa/11/
[01:05] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_palapeli build #11: STILL UNSTABLE in 52 min: https://kci.pangea.pub/job/bionic_unstable_palapeli/11/
[01:05] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_cantor build #11: STILL UNSTABLE in 52 min: https://kci.pangea.pub/job/bionic_unstable_cantor/11/
[01:07] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmix build #71: STILL FAILING in 22 min: https://kci.pangea.pub/job/artful_unstable_kmix/71/
[01:27] <mparillo> Upgraded a VM from 5.11.2 which had been installed via backports-landing to 5.11.3 from backports. No dead kittens
[01:30] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:30] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_ktp-desktop-applets build #11: FIXED in 1 hr 16 min: https://kci.pangea.pub/job/bionic_stable_ktp-desktop-applets/11/
[01:30] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kscd build #58: STILL FAILING in 45 sec: https://kci.pangea.pub/job/artful_unstable_kscd/58/
[01:30] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kscd build #12: STILL FAILING in 49 sec: https://kci.pangea.pub/job/bionic_unstable_kscd/12/
[01:30] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #83: STILL FAILING in 46 sec: https://kci.pangea.pub/job/artful_unstable_kget/83/
[01:30] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #12: STILL FAILING in 1 min 10 sec: https://kci.pangea.pub/job/bionic_unstable_kget/12/
[01:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_trojita build #11: STILL UNSTABLE in 1 hr 20 min: https://kci.pangea.pub/job/bionic_unstable_trojita/11/
[01:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ark build #166: STILL UNSTABLE in 48 min: https://kci.pangea.pub/job/artful_unstable_ark/166/
[01:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_sddm build #61: STILL UNSTABLE in 51 min: https://kci.pangea.pub/job/artful_unstable_sddm/61/
[01:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ksirk build #11: STILL UNSTABLE in 1 hr 20 min: https://kci.pangea.pub/job/bionic_unstable_ksirk/11/
[01:34] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_falkon build #12: STILL UNSTABLE in 1 hr 20 min: https://kci.pangea.pub/job/bionic_unstable_falkon/12/
[01:34] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_k3b build #157: STILL UNSTABLE in 43 min: https://kci.pangea.pub/job/artful_unstable_k3b/157/
[01:34] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #11: STILL UNSTABLE in 1 hr 21 min: https://kci.pangea.pub/job/bionic_unstable_kstars/11/
[01:34] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ark build #11: STILL UNSTABLE in 1 hr 20 min: https://kci.pangea.pub/job/bionic_unstable_ark/11/
[01:34] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ksirk build #78: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/artful_unstable_ksirk/78/
[01:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_babe build #136: STILL FAILING in 11 min: https://kci.pangea.pub/job/artful_unstable_babe/136/
[01:42] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmix build #72: STILL FAILING in 8 min 48 sec: https://kci.pangea.pub/job/artful_unstable_kmix/72/
[01:45] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_babe build #13: STILL FAILING in 16 min: https://kci.pangea.pub/job/bionic_unstable_babe/13/
[01:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kmix build #13: STILL FAILING in 15 min: https://kci.pangea.pub/job/bionic_unstable_kmix/13/
[01:52] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_palapeli build #125: STILL UNSTABLE in 47 min: https://kci.pangea.pub/job/artful_unstable_palapeli/125/
[01:52] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_elisa build #148: STILL UNSTABLE in 47 min: https://kci.pangea.pub/job/artful_unstable_elisa/148/
[02:14] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_k3b build #13: STILL UNSTABLE in 40 min: https://kci.pangea.pub/job/bionic_unstable_k3b/13/
[02:14] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kphotoalbum build #146: STILL UNSTABLE in 40 min: https://kci.pangea.pub/job/artful_unstable_kphotoalbum/146/
[02:14] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kphotoalbum build #14: STILL UNSTABLE in 41 min: https://kci.pangea.pub/job/bionic_unstable_kphotoalbum/14/
[02:15] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #214: STILL UNSTABLE in 1 hr 10 min: https://kci.pangea.pub/job/artful_unstable_kstars/214/
[02:33] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kstars build #13: STILL UNSTABLE in 2 hr 20 min: https://kci.pangea.pub/job/bionic_stable_kstars/13/
[02:34] -kubuntu-ci:#kubuntu-devel- Project artful_stable_cantor build #61: STILL UNSTABLE in 1 hr 29 min: https://kci.pangea.pub/job/artful_stable_cantor/61/
[02:34] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_ark build #13: STILL UNSTABLE in 2 hr 21 min: https://kci.pangea.pub/job/bionic_stable_ark/13/
[02:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:54] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-desktop build #174: FIXED in 40 min: https://kci.pangea.pub/job/artful_unstable_plasma-desktop/174/
[03:18] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_plasma-desktop build #26: STILL FAILING in 24 min: https://kci.pangea.pub/job/bionic_stable_plasma-desktop/26/
[03:35] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_plasma-desktop build #27: STILL FAILING in 11 min: https://kci.pangea.pub/job/bionic_stable_plasma-desktop/27/
[03:42] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:42] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-desktop build #19: FIXED in 47 min: https://kci.pangea.pub/job/bionic_unstable_plasma-desktop/19/
[08:03] <blaze> cmake dies on LP with "failed to execute: No child processes"
[08:03] <blaze> odd
[08:04]  * blaze is really confused
[09:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1893: SUCCESS in 1 min 1 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1893/
[09:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1893: SUCCESS in 1 min 4 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1893/
[09:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1893: SUCCESS in 3 min 52 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1893/
[11:58] <BluesKaj> Hey folks
[12:46] <someone_> Hi
[12:47] <someone_> I have downloaded kubntu 17.10 through torrent but after I checked from sha265sum of the file it is not the same as on kubuntu's website , why ?
[12:47] <someone_> Could anyone download "kubuntu-17.10-desktop-amd64.iso" from torrent file which on this page https://kubuntu.org/alternative-downloads and check from what I say ?
[12:48] <someone_> This is my sha265 of my file that I have:
[12:48] <someone_>  fc2b000346117b644d19277d8d6546fbf6d244651230cc5d3074aaadc5b25465  kubuntu-17.10-desktop-amd64.iso
[12:49] <someone_>  Is not this a weird problem ? Does not that mean that torrent file has been corrupted or something happened to it?
[12:51] <someone_> ?
[13:08] <blaze> someone_: some torrent clients are able to re-check downloaded chunks, please do so
[13:14] <someone_> The problem has been solved , Thank you .
[14:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kget build #161: FAILURE in 6 min 5 sec: https://kci.pangea.pub/job/xenial_unstable_kget/161/
[14:15] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #84: STILL FAILING in 6 min 7 sec: https://kci.pangea.pub/job/artful_unstable_kget/84/
[14:15] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #13: STILL FAILING in 6 min 7 sec: https://kci.pangea.pub/job/bionic_unstable_kget/13/
[14:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kget build #162: STILL FAILING in 4 min 43 sec: https://kci.pangea.pub/job/xenial_unstable_kget/162/
[14:24] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #14: STILL FAILING in 4 min 49 sec: https://kci.pangea.pub/job/bionic_unstable_kget/14/
[14:25] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #85: STILL FAILING in 5 min 49 sec: https://kci.pangea.pub/job/artful_unstable_kget/85/
[14:41] <mparillo> I just installed yesterday's BB ISO to a VM. Took the defaults, and got a clean install. Applied today's updates with Discover. No dead kittens.
[14:44] <clivejo> any dead beavers?
[14:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kget build #163: STILL FAILING in 4 min 42 sec: https://kci.pangea.pub/job/xenial_unstable_kget/163/
[14:48] <BluesKaj> clivejo, mine's still swimming :-)
[14:49] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #15: STILL FAILING in 7 min 49 sec: https://kci.pangea.pub/job/bionic_unstable_kget/15/
[14:49] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #86: STILL FAILING in 7 min 50 sec: https://kci.pangea.pub/job/artful_unstable_kget/86/
[14:50] <acheronuk> clivejo: pausing KCI for 2 mins. ok?
[14:51] <clivejo> no prob
[14:51] -kubuntu-ci:#kubuntu-devel- Starting build #83 for job mgmt_pause_integration (previous build: ABORTED)
[14:51] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #16: STILL FAILING in 1 min 24 sec: https://kci.pangea.pub/job/bionic_unstable_kget/16/
[14:51] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #87: STILL FAILING in 1 min 26 sec: https://kci.pangea.pub/job/artful_unstable_kget/87/
[14:52] <acheronuk> if NOCI worked, wouldn't need to do this :(
[14:57] -kubuntu-ci:#kubuntu-devel- Project mgmt_pause_integration build #83: ABORTED in 6 min 26 sec: https://kci.pangea.pub/job/mgmt_pause_integration/83/
[14:57] <acheronuk> done
[14:58] <clivejo> still holding off uploading to bionic
[14:58] <clivejo> ?
[14:58] <acheronuk> clivejo: yeah. archive, transitions, and test queus are still a complete ####fest
[14:59] <clivejo> :(
[15:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kget build #164: STILL FAILING in 11 min: https://kci.pangea.pub/job/xenial_unstable_kget/164/
[15:14] <clivejo> when did NOCI stop working?
[15:15] <acheronuk> I honestly don't think I could pin it down now :/
[15:17] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #17: STILL FAILING in 5 min 50 sec: https://kci.pangea.pub/job/bionic_unstable_kget/17/
[15:26] <clivejo> acheronuk: do you know the difference in libgpgme-dev and libgpgmepp-dev ?
[15:27] <acheronuk> pp
[15:27] <clivejo> shoot, really?
[15:27] <acheronuk> I forget ATM
[15:28] <blaze> c and c++
[15:29] <acheronuk> yeah, pp=++ I think
[15:29] <clivejo> are they totally different?
[15:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kget build #165: STILL FAILING in 9 min 43 sec: https://kci.pangea.pub/job/xenial_unstable_kget/165/
[15:30] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #18: STILL FAILING in 9 min 49 sec: https://kci.pangea.pub/job/bionic_unstable_kget/18/
[15:30] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #88: STILL FAILING in 9 min 50 sec: https://kci.pangea.pub/job/artful_unstable_kget/88/
[15:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kget build #166: STILL FAILING in 7 min 42 sec: https://kci.pangea.pub/job/xenial_unstable_kget/166/
[15:43] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #89: STILL FAILING in 7 min 45 sec: https://kci.pangea.pub/job/artful_unstable_kget/89/
[15:45] -kubuntu-ci:#kubuntu-devel- Project merger_mailcommon build #466: FAILURE in 8.2 sec: https://kci.pangea.pub/job/merger_mailcommon/466/
[15:47] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:47] -kubuntu-ci:#kubuntu-devel- Project merger_mailcommon build #467: FIXED in 19 sec: https://kci.pangea.pub/job/merger_mailcommon/467/
[15:48] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_mailcommon build #81: FAILURE in 2 min 53 sec: https://kci.pangea.pub/job/xenial_stable_mailcommon/81/
[15:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #272: FAILURE in 3 min 54 sec: https://kci.pangea.pub/job/xenial_unstable_mailcommon/272/
[15:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #273: STILL FAILING in 5 min 37 sec: https://kci.pangea.pub/job/xenial_unstable_mailcommon/273/
[15:57] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_mailcommon build #82: STILL FAILING in 4 min 39 sec: https://kci.pangea.pub/job/xenial_stable_mailcommon/82/
[15:59] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #19: STILL FAILING in 17 min: https://kci.pangea.pub/job/bionic_unstable_kget/19/
[16:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kget build #167: STILL FAILING in 16 min: https://kci.pangea.pub/job/xenial_unstable_kget/167/
[16:00] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #90: STILL FAILING in 16 min: https://kci.pangea.pub/job/artful_unstable_kget/90/
[16:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #274: STILL FAILING in 4 min 43 sec: https://kci.pangea.pub/job/xenial_unstable_mailcommon/274/
[16:04] <mparillo> clivejo: No dead beavers either. I just think AA with backports beats BB. But *somebody* had to install from the ISO. So far, everybody else is using magic sed scripts.
[16:05] <clivejo> yeah, I upgraded via sed method
[16:06] <mparillo> I think that is kind of the Debian way.
[16:07] <clivejo> don't have the patients to wait for an iso to download!
[16:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kget build #168: STILL FAILING in 7 min 40 sec: https://kci.pangea.pub/job/xenial_unstable_kget/168/
[16:08] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #91: STILL FAILING in 7 min 46 sec: https://kci.pangea.pub/job/artful_unstable_kget/91/
[16:08] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #20: STILL FAILING in 8 min 55 sec: https://kci.pangea.pub/job/bionic_unstable_kget/20/
[16:09] <mparillo> Well, I renamed my AA ISO to BB, then zsynced.
[16:11] <clivejo> you run it on VM?
[16:11] <nameless> hi. there's a Russian guy who "tests" 32-bit Kubuntu, incl. dev versions, and all he can say is 'everything works'. is there anything he can test specifically in BB?
[16:13] <clivejo> nameless: it would be more to fill out the tracker when we start having milestone testing
[16:13] <clivejo> so the tests can be signed off so to speak
[16:13] <clivejo> or the milestone
[16:14] <clivejo> has he a Launchpad account?
[16:14] <nameless> let me ask him
[16:20] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #92: STILL FAILING in 6 min 46 sec: https://kci.pangea.pub/job/artful_unstable_kget/92/
[16:20] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #21: STILL FAILING in 6 min 44 sec: https://kci.pangea.pub/job/bionic_unstable_kget/21/
[16:21] <mparillo> clivejo: Yes, VM. We do need folks with hardware to spare.
[16:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kget build #169: STILL FAILING in 10 min: https://kci.pangea.pub/job/xenial_unstable_kget/169/
[16:24]  * clivejo nods
[16:32] <mparillo> When I first caome to this channel, there was somebody (forget who), with posted a picture of a tower case with an open front and an array of bare HDD's, each labled with a different distro / release.  kind of ha
[16:35] <clivejo> nice :)
[16:36] <clivejo> that's a dedicated tester!
[16:47] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #22: NOW UNSTABLE in 22 min: https://kci.pangea.pub/job/bionic_unstable_kget/22/
[16:47] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #93: NOW UNSTABLE in 22 min: https://kci.pangea.pub/job/artful_unstable_kget/93/
[16:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1894: SUCCESS in 54 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1894/
[16:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1894: SUCCESS in 1 min 1 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1894/
[16:51] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1894: SUCCESS in 3 min 52 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1894/
[17:02] <nameless> clivejo: his English is not that good. i'm still trying to convince him his help is needed.
[17:03] <clivejo> are you human being?
[17:03] <nameless> yup
[17:03] <clivejo> ah, nice to meet you :)
[17:03] <nameless> aka flamboyant
[17:03] <nameless> me too
[17:03] <ejat> AI bot :)
[17:05] <nameless> nice to meet you too, bot ;-)
 who's calling who a bot?
[17:06] <clivejo> regarding the Russian forum, none of us speak Russian and don't know what people are saying on it
[17:06] <nameless> i do
[17:06] <clivejo> it would need someone like yourself to feedback problems, issues to the team
[17:07] <clivejo> and answer user questions etc
[17:07] <nameless> issues with what?
[17:07] <clivejo> Kubuntu
[17:08] <nameless> there are enough people there answering questions
[17:08] <nameless> it's kind of kubuntuforums.net in Russian
[17:08] <clivejo> we have a lot of different portals across the internet, many of which are not up to scratch when it comes to user support
[17:10] <clivejo> http://www.kubuntu-de.org/ is worrying out of date
[17:12] <nameless> that would be better than nothing for those who don't speak English. the Russian forum is more active than the German one.
[17:13] <clivejo> are there many users on that Russian forum?
[17:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:13] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kget build #94: FIXED in 22 min: https://kci.pangea.pub/job/artful_unstable_kget/94/
[17:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kget build #170: FIXED in 22 min: https://kci.pangea.pub/job/xenial_unstable_kget/170/
[17:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:14] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kget build #23: FIXED in 22 min: https://kci.pangea.pub/job/bionic_unstable_kget/23/
[17:16] <clivejo> nameless: have to go for a bit, but would like to chat with you later
[17:17] <blaze> local communities are full of switchers and are in lack dramatically of people from the linux world, developers etc
[17:19] <nameless> you can see for yourself: https://kubuntu.ru/tracker/facet/author%3A1/count/
[17:20] <nameless> switchers?
[17:21] <blaze> people with strong windoze background
[17:24] <nameless> well, i guess most of them have to use Window$ at work. is that a problem?
[17:25] <blaze> nope, not a bad thing at all they're trying something different
[17:31] <nameless> i saw threads about how they were switching their offices to Kubuntu. today i asked them to tell a bit about their success stories but no reply as of now.
[17:34] <nameless> blaze: do you have an account at KFN?
[17:35] <blaze> kfn? don't think so
[17:37] <nameless> kubuntuforums.net
[17:38] <nameless> are you a developer?
[17:44] <blaze> no, I was invited to kubuntu ninjas at some point but never finished the procedure
[17:45] <nameless> what do ninjas do?
[17:46] <acheronuk> https://community.kde.org/Kubuntu/Policies#.7Ekubuntu-ninjas
[17:48] <nameless> hi, Rik. thanks.
 @acheronuk, :)
[17:49] <acheronuk> np. that page has a lot of info on how we are organised, so useful :)
[17:49] <nameless> how is it going with the reminder fix for akonadi?
[17:50] <acheronuk> nameless: if it from -proposed to -release in bionic, I can then upload as a SRU for artful. just very slow going in bionic at the moment
[17:50] <nameless> okay, i'll read that
[17:50] <acheronuk> *if I can get it
[17:51] <acheronuk> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#akonadi
[17:51] <acheronuk> still many tests queued :(
 Too many tests queued!
[17:53]  * acheronuk blames inconsiderate people uploading Qt
[17:54] <nameless> i don't know much about the procedure yet
[18:06] <acheronuk> neither did I 18 months ago!
[18:07] <nameless> just 18? wow, you've made real progress ;-)
[18:08] <acheronuk> yeah, rather scary how quick things happen
[18:13] <nameless> alright, it's getting late here. nice talking to you, guys. see you.
[18:32] <genii> clivejo: Will there be a Xenial backport of Falkon?
[18:38] <acheronuk> https://zoltanp.github.io/2017/11/ktechlab-0-40-0.html
[18:38] <acheronuk> O_O
[18:42] <genii> So when Qt6 arrives, maybe they'll port it to Qt5
[18:43]  * genii ducks
[18:44] <blaze> yeah, development is moving slowly
[18:44] <blaze> but
[18:45] <blaze> Qt5/KDE5 migration is much easier
[19:13] <clivejo> genii: I doubt it, there are a few missing deps
[19:14] <clivejo> you could use the snap if you wanted it in Xenial though
[19:14] <genii> OK, thanks for the answer
[19:15] <clivejo> it would need libssl1.0 backported
[19:17] <clivejo> and probably a list of frameworks
[19:18]  * clivejo owes acheronuk a drink if he ever gets to meet face to face
[19:18] <blaze> it doesn't depend on kf, except kwallet api
[19:18] <acheronuk> clivejo: ???
[19:18] <clivejo> your contribution over this past 18months
[19:19] <acheronuk> oh. right
[19:19] <acheronuk> has been fun
[19:19] <clivejo> you deserve a pat on the back, in my opinion
[19:20] <clivejo> blaze: are they not planning to integrate more with KF5?
[19:21] <blaze> it is very unlikely
[19:22] <clivejo> oh, kinda got the impression they were
[19:22] <blaze> maintainer wants to keep everything that way in order to build easily on multiple platforms
[19:23] <clivejo> makes sense
[19:23] <clivejo> but would also be nice to integrate with KDE apps
[19:26] <blaze> any proposals? I can think of implementing something as a plugin, khelpcenter integration for example
[19:26] <clivejo> do you know if it supports plugins?
[19:27] <clivejo> Id kinda like to use LassPass with it
[19:27] <blaze> do you hate KWallet? :D
[19:28] <clivejo> yeah :/
[19:28] <clivejo> like the two factor with my phone
[19:29] <blaze> it has some extensions, and a repo with additional ones (not migrated to falkon yet)
[19:29] <clivejo> and the Last Pass implementation of Google Authenticator
[19:31] <clivejo> acheronuk: are you planning to package ktechlab-0-40-0 and add to KCI?
[19:32] <acheronuk> no
 @clivejo, Dibs
 Unless you want to
[19:32] <blaze> do they have a kf5 branch at least?
[19:33] <acheronuk> just got an email on the<EMAIL_ADDRESS>list
[19:33] <clivejo> blaze: good question
 @blaze, Probably not but I can work on that upstream if needer
[19:33] <clivejo> I would like to think it is KF5!
[19:34] <clivejo> https://cgit.kde.org/ktechlab.git/tree/CMakeLists.txt
[19:34] <clivejo> nope
 Then dibs, I'll take on this package
[19:35] <clivejo> tsimonq2: maybe take it on upstream?
 @clivejo, That's what I mean
[19:37] <clivejo> k, no need to add it to KCI then
[19:37] <clivejo> doesn't seem to be much development on it
[19:38] <clivejo> acheronuk: you using KCI?
[19:38] <acheronuk> not right now
[19:38] <clivejo> gonna take it offline then
[19:43] <acheronuk> byebye KCI
[19:43] <blaze> :(
[19:48] <clivejo> up and down like a yoyo
[19:50] <clivejo> ok, think I'm done
[19:51] <clivejo> what is kscd?
[19:54] <blaze> a player that plays only cds from the cd drive
[19:54] <acheronuk> little cd player app
[19:55] <acheronuk> https://c1.staticflickr.com/3/2189/32456470140_bec56a3630_b.jpg
[19:56] <acheronuk> 'KCI is alive?'
[19:57] <clivejo> I hope so
[19:57] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kscd build #59: STILL FAILING in 32 sec: https://kci.pangea.pub/job/artful_unstable_kscd/59/
[19:58] <mparillo> It doesn't go up to 11.
[19:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kscd build #187: FAILURE in 28 sec: https://kci.pangea.pub/job/xenial_unstable_kscd/187/
[20:00] <clivejo> 19:58:40 /usr/lib/ruby/2.3.0/drb/drb.rb:745:in `rescue in block in open': druby://<IP_ADDRESS>:9991 - #<Errno::ECONNREFUSED: Connection refused - connect(2) for "<IP_ADDRESS>" port 9991> (DRb::DRbConnError)
[20:02] <acheronuk> clivejo: you broke KCI?
[20:02] <clivejo> :/
[20:03] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kscd build #60: STILL FAILING in 31 sec: https://kci.pangea.pub/job/artful_unstable_kscd/60/
[20:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kscd build #188: STILL FAILING in 26 sec: https://kci.pangea.pub/job/xenial_unstable_kscd/188/
[20:06] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_k3b build #158: FAILURE in 45 sec: https://kci.pangea.pub/job/artful_unstable_k3b/158/
[20:11] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_k3b build #159: STILL FAILING in 34 sec: https://kci.pangea.pub/job/artful_unstable_k3b/159/
[20:15] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:15] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kscd build #13: FIXED in 17 min: https://kci.pangea.pub/job/bionic_unstable_kscd/13/
[20:19] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ksirk build #12: FAILURE in 47 sec: https://kci.pangea.pub/job/bionic_unstable_ksirk/12/
[20:24] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ksirk build #13: STILL FAILING in 39 sec: https://kci.pangea.pub/job/bionic_unstable_ksirk/13/
[20:26] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ark build #12: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/bionic_unstable_ark/12/
 @clivejo> 19:58:40 /usr/lib/ruby/2.3.0/drb/drb.rb:745:in `rescue in block in open': druby://<IP_ADDRESS>:9991 - #<Errno::ECONNREFUSED: Connection refused - connect(2) for "<IP_ADDRESS>" port 9991, clivejo!!!
[20:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ksirk build #14: STILL FAILING in 41 sec: https://kci.pangea.pub/job/bionic_unstable_ksirk/14/
[20:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kscd build #61: FIXED in 23 min: https://kci.pangea.pub/job/artful_unstable_kscd/61/
[20:46] <clivejo> tsimonq2: why would the interface be failing randomly?
 @clivejo, Because you broke it
 Try turning it off and turning it back on again
[20:47] <clivejo> last failure was 10mins ago
 Fwd from tsimonq2: Try turning it off and turning it back on again
[20:48] <clivejo> gonna do it again
[20:48] <clivejo> link is not ready
[20:48] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_k3b build #160: STILL FAILING in 36 sec: https://kci.pangea.pub/job/artful_unstable_k3b/160/
[20:48] <clivejo> and fails
[20:48] <clivejo> WTF
[20:50] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_k3b build #161: STILL FAILING in 36 sec: https://kci.pangea.pub/job/artful_unstable_k3b/161/
 Try turning it off and on again and then use HTTPS
[20:58] <acheronuk> turn it off and on again. rarely fails :P
[20:58] <clivejo> well k3b didn't fall over
[20:58] <clivejo> it reached dput
[20:59] <clivejo> feck
[20:59] <clivejo> ksirk tripped it
[20:59] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ksirk build #16: STILL FAILING in 43 sec: https://kci.pangea.pub/job/bionic_unstable_ksirk/16/
[21:01] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ksirk build #17: STILL FAILING in 38 sec: https://kci.pangea.pub/job/bionic_unstable_ksirk/17/
 @acheronuk, Right, then once it works do it again for good measure :P
 still broke :/
[21:17] <acheronuk> it was fine before the upgrades, so just revert
[21:17] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_k3b build #162: NOW UNSTABLE in 21 min: https://kci.pangea.pub/job/artful_unstable_k3b/162/
[21:18] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1895: SUCCESS in 51 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1895/
[21:19] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1895: SUCCESS in 1 min 1 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1895/
[21:21] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1895: SUCCESS in 3 min 47 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1895/
[21:27] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_babe build #14: STILL FAILING in 32 sec: https://kci.pangea.pub/job/bionic_unstable_babe/14/
[21:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_babe build #15: STILL FAILING in 31 sec: https://kci.pangea.pub/job/bionic_unstable_babe/15/
[21:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_babe build #16: STILL FAILING in 30 sec: https://kci.pangea.pub/job/bionic_unstable_babe/16/
[21:40] <acheronuk> yofel: you about?
[21:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ksirk build #18: NOW UNSTABLE in 21 min: https://kci.pangea.pub/job/bionic_unstable_ksirk/18/
[21:48] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_babe build #17: STILL FAILING in 7 min 27 sec: https://kci.pangea.pub/job/bionic_unstable_babe/17/
[21:59] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_babe build #18: STILL FAILING in 5 min 45 sec: https://kci.pangea.pub/job/bionic_unstable_babe/18/
[22:04] <ghostcube> 17.10 with beta und backport active ppa is flowy <3
[22:04] <acheronuk> flowy?
[22:05] <ghostcube> working fine... so it has flow aka flowy
[22:05] <ghostcube> :)
[22:05] <acheronuk> :)
[22:22] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kscd build #189: FIXED in 11 min: https://kci.pangea.pub/job/xenial_unstable_kscd/189/
[22:36] -kubuntu-ci:#kubuntu-devel- Starting build #84 for job mgmt_pause_integration (previous build: ABORTED)
[22:59] -kubuntu-ci:#kubuntu-devel- Project merger_akonadi-calendar build #818: FAILURE in 8.8 sec: https://kci.pangea.pub/job/merger_akonadi-calendar/818/
[22:59] -kubuntu-ci:#kubuntu-devel- Project merger_akonadi-contacts build #433: FAILURE in 25 sec: https://kci.pangea.pub/job/merger_akonadi-contacts/433/
[22:59] -kubuntu-ci:#kubuntu-devel- Project merger_akonadi-search build #798: FAILURE in 13 sec: https://kci.pangea.pub/job/merger_akonadi-search/798/
[23:00] -kubuntu-ci:#kubuntu-devel- Project merger_akonadiconsole build #318: FAILURE in 12 sec: https://kci.pangea.pub/job/merger_akonadiconsole/318/
[23:00] <clivejo> acheronuk: ^ real failures
[23:01] <acheronuk> yep.
[23:01] <clivejo> nout to do with me :P
[23:01] -kubuntu-ci:#kubuntu-devel- Project merger_calendarsupport build #440: FAILURE in 12 sec: https://kci.pangea.pub/job/merger_calendarsupport/440/
[23:01] <acheronuk> clivejo: I thought might be some conflicts to unstable in the changelogs
[23:02] <clivejo> eakk that could be my fault :/
[23:02] -kubuntu-ci:#kubuntu-devel- Project merger_incidenceeditor build #437: FAILURE in 15 sec: https://kci.pangea.pub/job/merger_incidenceeditor/437/
[23:02] <tsimonq2> acheronuk: Where are we at irt Debian merges?
[23:03] <acheronuk> tsimonq2: need to start them
[23:03] -kubuntu-ci:#kubuntu-devel- Project merger_juk build #416: FAILURE in 20 sec: https://kci.pangea.pub/job/merger_juk/416/
[23:04] <acheronuk> tsimonq2: I hope debian would be more up to date by now then they are, which is a pain :/
[23:04] -kubuntu-ci:#kubuntu-devel- Project merger_kalarmcal build #779: FAILURE in 22 sec: https://kci.pangea.pub/job/merger_kalarmcal/779/
[23:04] <acheronuk> * I hoped
[23:04] <clivejo> where are they up to?
[23:05] <acheronuk> frameworks 5.27 and plasma 5.10.5 I think?
[23:05] <acheronuk> 5.37
[23:06] -kubuntu-ci:#kubuntu-devel- Project merger_kcalutils build #815: FAILURE in 9.5 sec: https://kci.pangea.pub/job/merger_kcalutils/815/
[23:07] -kubuntu-ci:#kubuntu-devel- Project merger_kdepim-addons build #453: FAILURE in 12 sec: https://kci.pangea.pub/job/merger_kdepim-addons/453/
[23:07] -kubuntu-ci:#kubuntu-devel- Project merger_kdepim-runtime build #866: FAILURE in 12 sec: https://kci.pangea.pub/job/merger_kdepim-runtime/866/
[23:08] -kubuntu-ci:#kubuntu-devel- Project merger_kget build #424: FAILURE in 10 sec: https://kci.pangea.pub/job/merger_kget/424/
[23:09] -kubuntu-ci:#kubuntu-devel- Project merger_kidentitymanagement build #790: FAILURE in 9.5 sec: https://kci.pangea.pub/job/merger_kidentitymanagement/790/
[23:09] -kubuntu-ci:#kubuntu-devel- Project merger_kimagemapeditor build #243: FAILURE in 11 sec: https://kci.pangea.pub/job/merger_kimagemapeditor/243/
[23:11] <tsimonq2> acheronuk: Any chance you could pass me your ~/.gitconfig? This is a new machine and I don't have access to my old one right now...
[23:11] -kubuntu-ci:#kubuntu-devel- Project merger_kmix build #411: FAILURE in 16 sec: https://kci.pangea.pub/job/merger_kmix/411/
[23:11] -kubuntu-ci:#kubuntu-devel- Project merger_kmouth build #412: FAILURE in 13 sec: https://kci.pangea.pub/job/merger_kmouth/412/
[23:11] -kubuntu-ci:#kubuntu-devel- Project merger_kolf build #421: FAILURE in 16 sec: https://kci.pangea.pub/job/merger_kolf/421/
[23:13] <acheronuk> tsimonq2: https://paste.kde.org/pndbwpq8v
[23:13] -kubuntu-ci:#kubuntu-devel- Project merger_krfb build #634: FAILURE in 9.7 sec: https://kci.pangea.pub/job/merger_krfb/634/
[23:13] -kubuntu-ci:#kubuntu-devel- Project merger_ksirk build #426: FAILURE in 13 sec: https://kci.pangea.pub/job/merger_ksirk/426/
[23:13] <tsimonq2> acheronuk: Thanks
[23:17] -kubuntu-ci:#kubuntu-devel- Project merger_libkdepim build #440: FAILURE in 14 sec: https://kci.pangea.pub/job/merger_libkdepim/440/
[23:19] -kubuntu-ci:#kubuntu-devel- Project merger_mailcommon build #468: FAILURE in 11 sec: https://kci.pangea.pub/job/merger_mailcommon/468/
[23:19] -kubuntu-ci:#kubuntu-devel- Project merger_messagelib build #523: FAILURE in 11 sec: https://kci.pangea.pub/job/merger_messagelib/523/
[23:19] -kubuntu-ci:#kubuntu-devel- Project merger_palapeli build #417: FAILURE in 11 sec: https://kci.pangea.pub/job/merger_palapeli/417/
[23:20] -kubuntu-ci:#kubuntu-devel- Project merger_pimcommon build #444: FAILURE in 12 sec: https://kci.pangea.pub/job/merger_pimcommon/444/
[23:21] -kubuntu-ci:#kubuntu-devel- Project merger_sweeper build #408: FAILURE in 8.9 sec: https://kci.pangea.pub/job/merger_sweeper/408/
[23:21] -kubuntu-ci:#kubuntu-devel- Project merger_zeroconf-ioslave build #412: FAILURE in 12 sec: https://kci.pangea.pub/job/merger_zeroconf-ioslave/412/
[23:22] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:22] -kubuntu-ci:#kubuntu-devel- Project merger_ksirk build #427: FIXED in 15 sec: https://kci.pangea.pub/job/merger_ksirk/427/
[23:23] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:23] -kubuntu-ci:#kubuntu-devel- Project merger_messagelib build #524: FIXED in 14 sec: https://kci.pangea.pub/job/merger_messagelib/524/
[23:26] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:26] -kubuntu-ci:#kubuntu-devel- Project merger_zeroconf-ioslave build #413: FIXED in 14 sec: https://kci.pangea.pub/job/merger_zeroconf-ioslave/413/
[23:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:29] -kubuntu-ci:#kubuntu-devel- Project merger_sweeper build #409: FIXED in 18 sec: https://kci.pangea.pub/job/merger_sweeper/409/
[23:31] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:31] -kubuntu-ci:#kubuntu-devel- Project merger_palapeli build #418: FIXED in 26 sec: https://kci.pangea.pub/job/merger_palapeli/418/
[23:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:34] -kubuntu-ci:#kubuntu-devel- Project merger_krfb build #635: FIXED in 19 sec: https://kci.pangea.pub/job/merger_krfb/635/
[23:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:36] -kubuntu-ci:#kubuntu-devel- Project merger_kmouth build #413: FIXED in 16 sec: https://kci.pangea.pub/job/merger_kmouth/413/
[23:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:39] -kubuntu-ci:#kubuntu-devel- Project merger_kolf build #422: FIXED in 15 sec: https://kci.pangea.pub/job/merger_kolf/422/
[23:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:40] -kubuntu-ci:#kubuntu-devel- Project merger_kget build #425: FIXED in 17 sec: https://kci.pangea.pub/job/merger_kget/425/
[23:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:43] -kubuntu-ci:#kubuntu-devel- Project merger_kmix build #412: FIXED in 19 sec: https://kci.pangea.pub/job/merger_kmix/412/
[23:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:45] -kubuntu-ci:#kubuntu-devel- Project merger_juk build #417: FIXED in 25 sec: https://kci.pangea.pub/job/merger_juk/417/
[23:47] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:47] -kubuntu-ci:#kubuntu-devel- Project merger_pimcommon build #445: FIXED in 12 sec: https://kci.pangea.pub/job/merger_pimcommon/445/
[23:49] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:49] -kubuntu-ci:#kubuntu-devel- Project merger_mailcommon build #469: FIXED in 13 sec: https://kci.pangea.pub/job/merger_mailcommon/469/
[23:52] -kubuntu-ci:#kubuntu-devel- Project mgmt_pause_integration build #84: ABORTED in 1 hr 15 min: https://kci.pangea.pub/job/mgmt_pause_integration/84/
[23:57] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_bomber build #11: FAILURE in 4 min 22 sec: https://kci.pangea.pub/job/bionic_stable_bomber/11/
[23:58] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_jovie build #30: FAILURE in 4 min 56 sec: https://kci.pangea.pub/job/xenial_stable_jovie/30/
[23:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kanagram build #306: FAILURE in 5 min 0 sec: https://kci.pangea.pub/job/xenial_unstable_kanagram/306/
[23:58] -kubuntu-ci:#kubuntu-devel- Project artful_stable_bovo build #67: FAILURE in 5 min 27 sec: https://kci.pangea.pub/job/artful_stable_bovo/67/


 Hello. When I leave my PC unattended, the screensaver starts (eg random colors). When I press a key, the screensaver asks me the password. The problem is, there is one second (between the screensaver animation and the login dialog) during which the screen can be seen "unprotected", ie it can be seen however you were doing when you left your computer, like a personal email, or inbox, or note, etc.
 Is this the intended behavior? Can it be configured or it is just like that?
[09:00] <guiverc> @Rodrigo, you've not mentioned what release, however it is not intended behavior.  I'm aware of people reporting this before; it's related to graphics module from memory; but release details (& kernels stack being used if a LTS release) are starting point
 Thanks. I am still using focal
 20.04
 Kernel: Linux 5.4.0-113-generic
[10:56] <arraybolt3> Rodrigo: FYI, problems such as these might count as security vulnerabilities, and everyone in the world can see what goes on in IRC, so it might be better to report bugs like these on Launchpad and mark them as a security vulnerability. If it's not that serious, it will be made public at that point.
 ok thanks <arraybolt3>