[00:00] <santa_> sgclark: I hope so
[00:00] <sgclark> excellent :) I can hold off on the new stuff
[00:14] <yofel> FYI: I'm on a trip until sunday, so don't expect me to reply as I won't be checking IRC
[00:14] <yofel> nini
[00:16] <sgclark> yofel: ok have a great trip!
[00:17] <santa_> +1
[00:17] <santa_> pushed the add/remove ppa suffix scripts, so it should be ready for a first test run now
[00:20] <sgclark> ok, still fixing CI builds. Should be ready to test tomorrow morning.
[00:25] <santa_> sgclark: please give me a ping before proceeding so I can assist you with doubts or bugs in the scriptery ;)
[00:26] <sgclark> santa_: will do :) thanks for doing this!
[00:26] <santa_> yw, since its the first time we would be using this I would like to keep an eye on how you use it :)
[07:03] <soee_> good morning
[07:04] <soee_> some good news: http://linux.softpedia.com/blog/new-usb-startup-creator-is-being-made-for-ubuntu-16-04-lts-495794.shtml
[07:39] <sgclark> oh   bloody hell it is 2400  for me.  Vacation!  Or some such. Jens neeeds to be  involed.... Hense Sweden!
[07:46] <soee_> hiho sgclark
[07:48] <sgclark> hey
[07:49] <soee_> sgclark: i had not time yet to watch last podcast, how is teh situation with the build server. Rick mentioned DO could sponsor it ?
[07:50] <sgclark> way late. must sleep.. 
[07:50] <soee_> ok, have a good night
[07:51] <sgclark> I can  try. Suceeed?  dunno
[07:52] <sgclark> I need a job sorry
[08:47] <ovidiu-florin> sitter: I've installed powerline and started it
[08:47] <ovidiu-florin> but it's ugly as hell
[08:47] <ovidiu-florin> why does it not look like in the pictures?
[08:49] <sitter> wrong font? rtfm? :P
[08:50] <ovidiu-florin> I'm RTFMing
[08:50] <sitter> use the right font then :P
[08:50] <ovidiu-florin> I don't think it's the font
[08:50] <ovidiu-florin> I think it's the theme
[08:50] <ovidiu-florin> and I can't figure out how to change it
[08:52] <lordievader> Good morning.
[08:53] <sitter> I am not sure how I can help
[08:53] <sitter> lordievader: good morning
[08:54] <lordievader> Hey sitter 
[08:56] <ovidiu-florin> sitter: do you have a custom config for it?
[08:57] <sitter> I have an ohmyzsh with a .zshrc that configures it to use the bullet-train theme
[08:58] <ovidiu-florin> where did you get that theme from
[08:58] <ovidiu-florin> ?
[08:59] <sitter> comes bundled I think
[09:00] <ovidiu-florin> sitter: https://github.com/caiogondim/bullet-train-oh-my-zsh-theme ?
[09:00] <sitter> yeah
[09:06] <lordievader> zsh :D
[09:44]  * ovidiu-florin is trying out zsh
[09:57] <allee> Is there a known workaround with -dbg pkgs not found (libqxcb) or partialy missing (libglib, libQt5Core, libQt5Quick ...) in crash report asistant.  krunner crash but no dbg for lib{qxcb.  SomeQt5core
[10:03] <sitter> fixing the lookup algorithm is the workaround
[10:07] <allee> :-)    So no bug report :-(   I even ponder if it makes sense at all to report 2 monitor related bugs, given that we use qt 5.4 and not 5.5
[10:10] <allee> sitter: but wait, this why libqxcb.so symbols are not found, but why are some in symbols in e.g. libQt5 resolved and other not.
[10:10] <sitter> I do not know
[10:10] <allee> *this explains
[10:10] <allee> k
[10:12] <Blizzz> is it expected that akonadictl consumes cpu constantly? just put an issue upstream https://bugs.kde.org/show_bug.cgi?id=354937
[10:15] <allee> Blizz: add process list which akonadi proc.  E.g.  konsole as wide as possible.  Start top, quit and c&p the process that consume to much CPU 
[10:15] <allee> ^ s/top/htop/
[10:16] <allee> Blizzz: check ~/.xsession-error is akonadi resource constantly log something
[10:17] <allee> I've no akonadi cpu problems currently but does akonadictl stop   and restarting help in your case?
[10:19] <Blizzz> allee: i added a screenshot of htop
[10:20] <Blizzz> allee: yes, akonadi writes to .xsession-errors
[10:20] <Blizzz> i'll add to the bug report
[10:21] <allee> Blizzz: is your qt5.5 self compiled?  Or which deb repo?
[10:21] <Blizzz> allee: from http://ppa.launchpad.net/canonical-qt5-edgers/backup-qt551/ubuntu/
[10:22] <Blizzz> https://launchpad.net/~canonical-qt5-edgers/+archive/ubuntu/backup-qt551
[10:22] <Blizzz> i have seen this in 5.4 as well, but did not investigate… went to 5.5 because of issues with multiple monitors
[10:23] <allee> Blizzz: you read my mind ;-) I was pondering about 5.5 because of (minor but anoying) mult. monitor problems too.  Did it fix some mult monitor
[10:24] <allee> for you?
[10:25] <Blizzz> allee: at office, i connect via VGA to an external one. With 5.5.1 it does it smoothly. Without, i needed to restart plasmashell manually after plugging in, and it crashed when unplugging. this is all good now.
[10:25] <Blizzz> in the .xsession-errors you see, it's always the same two items 149472 and 112251 that are mentioned
[10:31] <allee> Blizzz: much luck! KDEPIM is unfortunatly hopelessly understaffed.
[10:32] <allee> I would try adonadictl and try to find the item.  Maybe the content show you why they are special.  But for most of my akonadi problem I had to give up :-(
[10:32] <vip> anybody heard about resolution of bug about logging in lag?
[10:33] <Blizzz> allee: yes… and it took ages until the  Qt4/KDE4 version became usable. I took me three attempts to go back to it, until it was good enough for professional use. Okay,  thanks so far!
[10:33] <allee> vip: no news about akondi delay on login. :-(
[10:34] <vip> allee: i've heard it is more networkmanager/bluetooth bug
[10:34] <vip> allee: https://bugs.launchpad.net/ubuntu/+source/plasma-nm/+bug/1509334
[10:34] <allee> vip: ah yes, these are two differ beast.  Here it was akonadi
[10:34] <vip> found it
[10:35] <soee_> vip i think it is not released yet for wily
[10:36] <soee_> vip: ut you can download and install package with fix: https://launchpad.net/~clivejo/+archive/ubuntu/wily/+packages
[10:36] <Blizzz> another thing: in my KDE menu there are several applications without Icon, like Dolphin or Firefox. Known?
[10:36] <allee> Blizzz: yes.
[10:37] <allee> Path changed between kde 4 and 5 version of apps :-(
[10:37] <vip> soee_: thanks, both nm and akonadi bugs are patched?
[10:37] <soee_> nm only
[10:47] <allee> Blizzz: btw.  how long does login take for you?  Here ~ 30s  with  ln -s /bin/true /usr/local/bin/akonadiserver  ~ 4 sec.
[10:50] <vip> allee: btw, how do you then start akonadi after login?
[10:52] <allee> vip: that just to measure and prove delay is akonadis fault.  (like remove plasma-nm to prove delay is caused by the app)
[10:52] <vip> ah, ok
[11:12] <jmux> Riddell: so do we have a LibreOffice KDE5 meeting on Monday? When and where?
[11:13] <Riddell> jmux: yes, 14:00CET in #libreoffice-something
[11:13] <Riddell> jmux: -design?
[11:15] <jmux> Riddell: #libreoffice-design is fine. I'll block one hour
[11:15] <jmux> Riddell: Or do you expect we need longer?
[11:15] <Riddell> jmux: nah an hour is fine
[11:23] <Blizzz> allee: login does not take long, definitely not half a minue
[11:23] <Blizzz> 4 sec, if at all. I have session restore disabled
[11:26] <allee> Blizzz: thx for the info.  Interesting.  How may akonadi related proc. have you running? ps x | grep akonad[i] | wc -l   (here 25 proc)
[11:29] <Blizzz> allee: 21
[11:30] <Blizzz> with 3 email, one carddav and one caldav account
[11:30] <allee> hmm, so what the hell is different for soee_ and me that akondi uses so much time.  Grr..
[11:56] <Blizzz> allee: maybe not using disconnect imap?
[11:57] <clivejo> allee: have you the plasma-nm patch?
[12:00] <clivejo> before the patch was applied plasma-nm was delaying login by 30 seconds
[12:01] <clivejo> allee: what version have you installed "dpkg -s plasma-nm"
[12:02] <clivejo> and what version of Kubuntu?
[12:07] <ovidiu-florin> sitter: please help me
[12:07] <sitter> 42
[12:07] <ovidiu-florin> I've looked throught he manual and cannot fix it
[12:09] <ovidiu-florin> sitter: http://imgur.com/qgTarmB
[12:09] <ovidiu-florin> compared to this image: https://github.com/caiogondim/bullet-train-oh-my-zsh-theme
[12:09] <ovidiu-florin> I have zsh installed and set as defaul
[12:09] <ovidiu-florin> and set it's theme to ^^
[12:09] <ovidiu-florin> like it sais in it's readme
[12:10] <ovidiu-florin> but no powerline
[12:10] <ovidiu-florin> why doesn't the theme look the same?
[12:10] <ovidiu-florin> I have the fonts installed in ~/.fonts
[12:10] <ovidiu-florin> and I've installed ttf-ancient-fonts
[12:10] <ovidiu-florin> and rebooted
[12:11] <BluesKaj> Hiyas all
[12:12] <sitter> ovidiu-florin: you have to set the font as your konsole font
[12:12] <sitter> what you are seeing is exactly what happens when it's not useing a powerlined font
[12:14] <ovidiu-florin> fixed
[12:14] <ovidiu-florin> thanks
[12:49] <ovidiu-florin> sitter: do you use powerline with python 2 or 3?
[12:50] <ovidiu-florin> because I've installed and use it with python 3
[12:50] <ovidiu-florin> and the vim we ship does not support python3
[12:53] <allee> clivejo: ii  plasma-nm                                           4:5.4.2-0ubuntu1
[12:54] <allee> clivejo: but I was not affected by plasma-nm delay (mac air with bt).  Replacing akonadi with /bin/true I could login in 4-5 sec
[12:58] <allee> clivejo,soee_: I've found out that with akonadictl stop, then logout, the login need ~ 7 sec. Without akonadictl stop before logout it's 30 sec. See #akonadi. thx to Blizzz for the inspiration to try this :-)
[13:00] <soee_> allee: ood to know, thanks ! :)
[13:00] <soee_> *good
[13:01] <allee> clivejo: ah, forgot: I'm using wily
[13:02] <Blizzz> wow, strange. sounds like it's not stopping by itself probably on logout/shutdown
[13:04] <allee> Blizzz: akonadi not running after logout.  but something goes wrong how it's stopped. See proc list: https://paste.kde.org/ptfptwcvo
[13:05]  * allee wonders why every logout gives an additional kuiserver5 process that runs until shutdown
[13:05] <Blizzz> more is better?
[13:06]  * allee notes: only sometimes konsole is not resotored
[13:06] <allee> Blizzz: lol.  Wenn ich einmal reich waere,didel...
[13:08] <Blizzz> meanwhile i wonder where the debug symbols for akonadi_davgroupware_resource are. they should be in kdepim-runtime-dbg, but apparently are missing.
[13:09] <Blizzz> once upon a time it was possible to open a bug in launchpad, no?
[13:10] <allee> Blizzz: me too.  I've asked the same today. response: [11:03:47] <sitter> fixing the lookup algorithm is the workaround
[13:10] <allee> but this does not explain why sometimes some symbols are resolved and other missing :-(
[13:11] <Blizzz> yeah…
[13:11] <Blizzz> how to do this anyway?
[13:12] <allee> Usually I checked which pkg a lib was in (dpkg -S /path/to/lib) and added -dbg to pkg name and installed it.  But this didn't work today for the first time.
[13:13] <allee> with the some symbols resolved some not.  I'm totally glueless.  Must be a bug during -dbg generation IMHO.
[13:16] <Blizzz> ok
[13:16] <Blizzz> i fought launchpad and filed this now: https://bugs.launchpad.net/ubuntu/+source/kdepim-runtime/+bug/1513830
[13:43] <ovidiu-florin> sitter: I can't find how to set powerline to use bullet-train. Please advise
[13:44] <sitter> that sentence makes no sense
[13:44] <sitter> bullet-train is an implementation of the powerline style
[13:44] <ovidiu-florin> oh
[13:44] <ovidiu-florin> I thought bullet-train is a theme for zsh
[13:44] <sitter> which implements the powerline style
[13:45] <ovidiu-florin> ah
 I have an ohmyzsh with a .zshrc that configures it to use the bullet-train theme
[13:47] <ovidiu-florin> where does powerline come in this scenario?
[14:04] <soee_> http://www.mattermost.org/
[14:05] <soee_> inegrates with http://www.mattermost.org/community-applications/
[14:58] <shadeslayer> where did we keep our packaging in bzr?
[14:59] <shadeslayer> ah nvm
[15:00] <shadeslayer> packagers, not packaging is the team
[15:00] <clivejo> what you looking for shadeslayer
[15:00] <shadeslayer> clivejo: nothing in particular
[15:34] <pursuivant> muon (master) v5.4.2-173-gc56fba8 * Aleix Pol: muon (20 files in 6 dirs)
[15:34] <pursuivant> Preparation for the split
[15:34] <pursuivant> Move the required classes within libMuonApt into muon
[15:34] <pursuivant> http://commits.kde.org/muon/c56fba86f6850effca3c146f75e66b0154ad5994
[15:34] <pursuivant> muon (master) v5.4.2-174-g60e429d * Aleix Pol:  (16 files in 5 dirs)
[15:34] <pursuivant> Move libmuonapt within the ApplicationsBackend
[15:34] <pursuivant> http://commits.kde.org/muon/60e429d4e6d3b5a04a2a35fbd371b33a9bb053f0
[16:35] <jmux> Riddell: https://wiki.debian.org/BSP/2015/11/Munich
[16:37] <jmux> shadeslayer, yofel, everybody else: ^^^
[16:50] <nluxton> Hi - I can't set the window manager in Kubuntu 15.10 - I have a set_window_manager.sh in the plasma-workspace/env/ dir but it doesn't set KDEWM - however, if I chang 'startkde' like the following: https://paste.kde.org/p2hzjumog -- then it starts working.
[16:53] <nluxton> Anyone got any idea what might be happening to cause this to go wrong in the 'vanilla' case?
[16:55] <shadeslayer> well, you've just removed the exception handling there
[16:56] <shadeslayer> I would recommend asking in #kde
[16:56] <nluxton> I tried that to no avail - I'll try again next week
[16:56] <shadeslayer> ah 
[16:57] <shadeslayer> yeah :)
[16:57] <nluxton> :)
[16:57] <shadeslayer> I'm not sure honesty :)
[16:57] <shadeslayer> nluxton: perhaps you can set +x on startkde and check .xsession-errors
[16:57] <shadeslayer> to see why your script doesn't work
[16:57] <nluxton> I ran it interactively in order to figure it out thus far
[16:58] <nluxton> I mean, my script seems fine ... it's just export KDEWM=/usr/bin/xmonad
[16:58] <nluxton> It was working fine until I upgraded to 15.10 today
[16:58] <shadeslayer> nluxton: maybe check what running (test -r "$file" && . "$file") || : gives you
[16:59] <shadeslayer> nluxton: perhaps it's too late in the startup sequence and kwin has already taken over
[16:59] <shadeslayer> I also recall there being a option somewhere to set your custom wm
[16:59] <nluxton> Well, it works without the || :   bit
[16:59] <nluxton> Just like it used to
[17:00] <shadeslayer> nluxton: yeah but run that in your shell
[17:00] <shadeslayer> with the ||
[17:00] <nluxton> And it seems like kwin gets set as the default later on if it's blank
[17:00] <nluxton> Yeah it works fine in the shell
[17:00] <shadeslayer> nluxton: ok, maybe make your file touch a script somewhere
[17:00] <nluxton> Unless I use the || :  bit - and then everything works fine, except that KDEWM stays blank 
[17:00] <nluxton> Good shout
[17:00] <nluxton> Make sure it's actually sourced
[17:00] <shadeslayer> correct
[17:02] <nluxton> Yep
[17:02] <nluxton> Definitely running
[17:02] <shadeslayer> nluxton: that's with the ||: ?
[17:02] <nluxton> Yep
[17:02] <nluxton> I just reset startkde to vanilla (and set the 'is kde running?' check to 1 so that it tries everything anyway lol)
[17:02] <shadeslayer> ok, well, try dumping the env into a file before and after the import
[17:03] <shadeslayer> er, export
[17:03] <shadeslayer> I mean
[17:03] <shadeslayer> from your script
[17:03] <shadeslayer> perhaps even a pidof kwin_x11
[17:03] <shadeslayer> that way we'll know if kwin_x11 gets started before KDEWM gets set
[17:03] <shadeslayer> then that'd be the problem
[17:03] <nluxton> Well I echod it to the screen before, before and after, and again when it checks if KDEWM is blank later on in the startkde script, and they were all blank
[17:04] <shadeslayer> oh, then isn't that the issue?
[17:04] <shadeslayer> nluxton: you could also try putting it in /etc/environment
[17:04] <nluxton> Yeah - I'm attempting to understand why that's happening
[17:04] <shadeslayer> I mean, it /should/ work there
[17:05] <shadeslayer> and when debugging bash scripts, +x is your friend ;)
[17:05] <nluxton> Because it's a change in behaviour since 15.04 ... why should a simple source op stop working?
[17:05] <nluxton> >.<
[17:05] <shadeslayer> so you probably want to do that in startkde
[17:05] <shadeslayer> nluxton: well, maybe startkde changed
[17:06] <nluxton> Yeah that was my next step is to start figuring it all out myself - and then potentially raising bug reports etc - I just hoped I might short-circuit that ;)
[17:06] <nluxton> Someone could say "It's because || : doesn't work in dash" or something like that haha
[17:07] <nluxton> What is the " || :" construct anyway?
[17:07] <shadeslayer> not sure
[17:08] <shadeslayer> well
[17:08] <shadeslayer> : is true
[17:08] <shadeslayer> so as I understand it, it's exception handling
[17:09] <shadeslayer> if (test -r "$file" && . "$file") evaluates to false, OR it with true?
[17:09] <nluxton> Yeah it seems like a way of ignoring failures
[17:09] <shadeslayer> yeah I guess
[17:09] <nluxton> http://stackoverflow.com/questions/16357755/meaning-of-colon-in-bash-after-a-double-pipe
[17:09] <nluxton> Rather than having the whole script fail
[17:09] <shadeslayer> indeed
[17:09] <nluxton> The weird thing is, if I remove it, it works fine - if I add it, something breaks
[17:09] <nluxton> >.<
[17:10] <nluxton> Computers, honestly
[17:11] <nluxton> Wow
[17:12] <nluxton> The test + source has an exit code of 1
[17:12] <nluxton> If I remove the double quotes, it's fine
[17:13] <nluxton> Nope
[17:13] <nluxton> I had a typo
[17:14] <nluxton> OH MY
[17:14] <nluxton> It's the parentheses
[17:14] <shadeslayer> what about the parentheses
[17:14] <nluxton> With them, it doesn't set the variable
[17:14] <nluxton> Without them, it works fine
[17:15] <nluxton> (in both cases, without the || :)
[17:15] <shadeslayer> huh
[17:15] <shadeslayer> I wonder why
[17:15] <nluxton> Is it starting a subshell or something weird?
[17:15] <shadeslayer> I honestly don't know
[17:15] <shadeslayer> lets see
[17:16] <shadeslayer> yes
[17:16] <shadeslayer> nluxton: (export FOO="bar")
[17:16] <shadeslayer> does not give me a foo var :P
[17:16] <nluxton> whoa
[17:16] <shadeslayer> I think because () evaluates everything inside
[17:16] <nluxton> OK, I think that constitutes a bug, right?
[17:16] <shadeslayer> no, that's interesting bash stuff :P
[17:17] <nluxton> Haha, I mean a bug in kdestart ;)
[17:17] <shadeslayer> nluxton: try this
[17:17] <nluxton> Maybe someone switching between langs and thinking "Yeah, this will be fine"
[17:17] <shadeslayer> eval export KDEWM
[17:17] <nluxton> oooh
[17:18] <nluxton> nope
[17:18] <nluxton> Damn, I have to leave work now
[17:19] <shadeslayer> oh :(
[17:19] <nluxton> I'll do it Monday - thanks for being my rubber duck! :D
[17:19] <shadeslayer> yw
[17:19] <nluxton> Have a great weekend
[17:23] <shadeslayer> you know, I never thought about it, but computers are bigger on the inside :O
[17:23] <shadeslayer> some of them are also blue
[17:46] <pursuivant> muon (master) v5.4.2-175-gb8bb3a1 * Aleix Pol:  (395 files in 47 dirs)
[17:46] <pursuivant> Remove discover
[17:46] <pursuivant> And the whole abstraction layer as it's being moved into a separate
[17:46] <pursuivant> repository.
[17:46] <pursuivant> With it, also the notifier plasmoid, updater and exporter.
[17:46] <pursuivant> http://commits.kde.org/muon/b8bb3a144ee1b7bb560f09777d5c5966a3c9ac39