[00:00] <valorie> what, juggling is offtopic? lol
[07:28] <ovidiu-florin> clivejo: pong
[09:21] <lordievader> Good morning.
[10:49] <mikkle> Is the upgrade from 15.10 to 16.04 reasonably safe and reliable?
[10:50] <soee> mikkle: hey, yes. I did it some time ago
[10:51] <mikkle> how did you do a distribution upgrade, might I ask?
[10:51] <soee> but if it is your production machine i suggest to stay on 15.10
[10:51] <mikkle> it is
[10:51] <soee> so keep in mind that you might have some problems as 16.04 is a development version
[10:52] <mikkle> I have problems now that I was hoping an update to the latest plasma and frameworks would fix.
[10:52] <mikkle> I know backports in the works, but I'm impatient
[10:52] <soee> :)
[10:52] <soee> well you were warned
[10:53] <soee> if you want to upgrade, you are doing it on your own risk
[10:53] <lordievader> mikkle: I did it yesterday, no problems so far.
[10:53] <soee> hiho lordievader
[10:53] <lordievader> But indeed, if it is a production machine wait with the upgrade.
[10:53] <lordievader> soee: o/
[10:54] <mikkle> thanks for the tip!
[10:54] <mikkle> I'll probably just wait it otu
[10:54] <mikkle> cheers, and by!
[10:54] <mikkle> bye
[11:11] <soee> yofel: ping
[11:11] <yofel> hm?
[11:13] <soee> if new user account uses in various places old Oxygen incons (now breeze) that it is bug on our side or upstream?
[11:18] <yofel> I would assume upstream, if breeze actually ships the relevant icon
[11:18] <yofel> otherwise oxygen might just be used as a fallback
[11:25] <soee> if someone also can confirm: https://bugs.kde.org/show_bug.cgi?id=357835 please leave a comment
[11:27] <clivejo> wow, plasma just restarted, thats the first time its done that since moving to xenial
[11:28] <acher88> soee: Has same bug yesterday trying to resize a default panel that had been moved to the top
[11:28] <acher88> *had
[11:28] <soee> acher88: please add comment of you can and mention that it was at top etc.
[11:29] <soee> clivejo: on 5.5.x ?
[11:29] <clivejo> my panel moved to my second screen for some reason ?
[11:29] <clivejo> yes 5.5.3
[11:30] <soee> clivejo: are you sure it wasn't checking updates and the crash isn't die to discover notifier issue ?
[11:30] <acher88> Need to re-register with bugs.kde later as email I originally had is now defunct
[11:30] <acher88> But, yes I will later
[11:30] <soee> thanks
[11:31] <soee> oh Kernel 4.4 has been released
[11:32] <clivejo> I dont know soee, its not displaying any crash info
[11:32] <soee> ah so it's not it
[11:32] <clivejo> just my panels and wigets all disappear and come back a few seconds later
[11:35] <soee> yofel: http://paste.ubuntu.com/14468502/
[11:38] <yofel> o.O
[11:39] <yofel> oops
[11:39] <yofel> soee: thanks
[11:42] <yofel> wgrant: could you please increase the size of kubuntu-ppa/backports-landing to 20G or even 30? That's taking a lot more space than I expected
[11:57] <bshah> :q
[11:58] <bshah> err
[11:58] <soee> orr
[11:58] <yofel> ^^
[11:58] <bshah> ^.^
[12:06] <wgrant> yofel: Done.
[12:07] <vip> hola
[12:09] <soee> hiho vip
[12:14] <yofel> wgrant: thanks a lot!
[12:20] <clivejo> soee: got a crash report this time
[12:21] <soee> crashed again ?
[12:21] <clivejo> yup
[12:21] <soee> i see
[12:21] <clivejo> QEventDispatcherGlib::processEvents mean anything to you?
[12:22] <clivejo> Im running an update and upgrade in konsole
[12:22] <clivejo> see it that stops it
[12:23] <soee> clivejo: there is bug in discover notifier when running update (or system running it in the background)
[12:24] <soee> and yofel already reported it upstream
[12:24] <clivejo> crashes plasma shell?
[12:24] <soee> yes
[12:25] <soee> yofel: do you rememebr the bug ID ?
[12:25] <clivejo> any work around? remove the package or disable updates?
[12:25] <clivejo> the new discover looks quite nice
[12:25] <yofel> removing the notifier might help
[12:26] <yofel> kde 357704
[12:26] <yofel> disabling updates doesn't help because the apt trigger to show notifications crashes it, so even an "apt update" in konsole will crash plasma
[12:27] <clivejo> yofel: yes, Ive noticed that
[12:28] <clivejo> but seems to have settled down since I installed the updates
[12:28] <clivejo> !info krita
[12:29] <clivejo> thats quite an old version of calligra
[12:30] <clivejo> surely we should have the most up-to-date versions if we are "showcasing" them on Discover?
[12:30] <yofel> that's what was there for wily
[12:30] <yofel> nobody updated xenial yet
[12:30] <clivejo> Ive them in my PPA
[12:31] <clivejo> https://launchpad.net/~clivejo/+archive/ubuntu/calligra
[12:32] <clivejo> Can someone load Discover and click on the KDE "Discover all possibilites" banner in the slideshow
[12:32] <clivejo> Im getting an SSL error
[12:33] <clivejo> The certificate authority's certificate is invalid
[12:33] <clivejo> The certificate cannot be verified for internal reasons
[13:46] <BluesKaj> Hey folks
[13:52] <sgclark> morning
[13:54] <BluesKaj> 'Morning sgclark
[13:54] <BluesKaj> up early
[13:55] <pursuivant> muon (master) v5.4.3-174-g8f21836 * Carlo Vanini: src (4 files in 2 dirs)
[13:55] <pursuivant> add keyboard shortcut to focus search box
[13:55] <pursuivant> Add keyboard shortcut to move focus to the search box, and give it focus at startup.
[13:55] <pursuivant> If the box is hidden, e.g. by changes preview, the focus is not changed. Otherwise you could change the content of the search box without seeing it.
[13:55] <pursuivant> http://commits.kde.org/muon/8f21836cff78f9834f9052e301363f106d5d1ded
[13:56] <pursuivant> muon (master) v5.4.3-175-g8b92ce3 * Carlo Vanini: src/icons (9 files)
[13:56] <pursuivant> rename icons
[13:56] <pursuivant> Rename icon files to solve CMake (ECM) warnings.
[13:56] <pursuivant> ```
[13:56] <pursuivant> http://commits.kde.org/muon/8b92ce38f08ec5789b27747851beb4421f0cffef
[15:02] <soee> yofel: current updates make pam-kwallet4 removed so i think now all is fine
[15:02] <yofel> right, I made it break the wrong thing
[15:44] <clivejo> yofel or sgclark: any idea what this CMake error is about? https://paste.kde.org/p9yru3zlg
[15:44] <yofel> are you build-depending on e-c-m?
[15:45] <yofel> oh, if you are, then qtbase5-dev might be missing
[15:45] <clivejo> yes I am
[15:45] <sgclark> yeah looks like qt5 dep missing
[15:45] <sgclark> what yofel said
[15:46] <clivejo> do I have to set the QT version as 5?
[15:46] <yofel> you at least have to install qt 5
[15:46] <yofel> setting the version isn't necessary
[15:47] <clivejo> what is kdelibs5-dev?
[15:47] <yofel> kde4libs
[15:47] <clivejo> !info kdelibs5-dev
[15:49] <clivejo> why does it say 5 :/
[15:49] <sgclark> yeah I know, that through me off for a long time
[15:52] <yofel> the SOVERSION of the libraries in kde4libs is 5
[15:53] <yofel> e.g. libkdecore5, hence 5
[15:53] <yofel> version 4 was kde-3-libs
[15:53] <yofel> dunno why the guys went with the 5 for the dev package though
[15:54] <clivejo> ok libkdcraw builds not but its failing due to the install file
[15:54] <clivejo> the install file is libkdcraw23.install
[15:55] <clivejo> but the file being built is usr/lib/x86_64-linux-gnu/libKF5KDcraw.so.5.0.0
[15:55] <clivejo> should the package not have the same name?
[15:55] <yofel> sure
[15:56] <clivejo> libkf5kdcraw
[15:56] <clivejo> .install etc
[15:56] <yofel> there's no lib with soversion suffix?
[15:57] <clivejo> I guess this is the KF5 port?
[15:58] <yofel> well, there should be a file called libKF5KDcraw.so.X
[15:58] <yofel> where X is a number
[15:58] <clivejo> the old install file is usr/lib/libkdcraw.so.23.*.*
[15:58] <yofel> o.O
[15:58]  * yofel looks
[16:00] <yofel> clivejo: that is NOT the old install file
[16:00]  * yofel looks up an old lib packaging guide
[16:00] <yofel> you are misunderstanding something
[16:01] <yofel> clivejo: https://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
[16:02] <yofel> read that sometime soon
[16:02] <yofel> that's not official debian documentation, but even if a bit old, probably still the best lib packaging guide
[16:02] <yofel> clivejo: so for now, what's in the old install file?
[16:03] <yofel> btw. add that link to your packaging docs
[16:04] <clivejo> I dont know, Im confused as hell
[16:04] <clivejo> nothing in this package is matching up
[16:04] <sgclark> kf5 port maybe?
[16:04] <yofel> well yes, the packaging is for the qt4 one, the kf5 port looks completely different
[16:05] <clivejo> so its the wrong packaging?
[16:05] <yofel> you have to pretty much redo the package from scratch
[16:05] <clivejo> this is the new files being built - https://paste.kde.org/pb0wzz7gl
[16:07] <yofel> ok, that looks good. Now as you don't know what to look for, look at chapter 5.3 of the link I just gave you
[16:07] <yofel> that talks about how to find out the proper package name
[16:13] <clivejo> libKF5KDcraw5
[16:14] <yofel> 9 of 10 points, package names are always all lowercase
[16:15] <clivejo> I copy and pasted, I keep spelling the stupid thing wrong
[16:15] <clivejo> my brain is convinced its call kdraw
[16:16] <clivejo> but how has it jumped from 23 to 5?
[16:16] <clivejo> I dont unstand that
[16:17] <yofel> usually you always go upwards, but as the lib got renamed - resulting in a different filename - it reset it's version to the default for frameworks
[16:18] <yofel> not quite sure why they went with 5 instead of 1 as they usually bump the soname version every release, but whatever
[16:21] <yofel> hm, I tried installing plasma5.5 on wily, and after the update I have no favorites in kickoff o.O
[16:22] <yofel> and reboot-after-update doesn't work at all. We need a solution for that before that gets released to users
[16:23] <yofel> diff: wily stuff is in backports-landing now
[16:35] <clivejo> I can understand framework being bumped to 5
[16:35] <clivejo> but isnt this an app?
[16:35] <clivejo> release as part of apps 15.12.0
[16:35] <yofel> *shrug*, seems like they're calling all qt5 libs libKF5*
[16:36] <yofel> gpgmepp is also in apps and called libFK5something
[16:36] <clivejo> its so confusing!
[16:36] <clivejo> my head hurts
[16:36] <yofel> well, I'll agree with that
[16:38] <clivejo> yofel: have you called from testers for plasma on wily?
[16:39] <clivejo> for
[16:39] <clivejo> I cant type today
[16:39] <BluesKaj> I left wily behind a while back
[16:40] <yofel> not yet, still thinking about whether we want to do that just yet
[16:40] <clivejo> whats your thinking?
[16:40] <clivejo> not happy about something?
[16:41] <yofel> I did the test myself: 1) After the upgrade there is no functional way to reboot, so most users will probably powerbutton out. Not nice. 2) The muon issue 3) The upgrade somehow wiped my kickoff favorites. Also not nice.
[16:42] <yofel> so with 3 issues staring me in the face after a basic upgrade test, I think we have debugging to do before we let people find even more issues
[16:43] <yofel> The only positive thing I can say is that there were no file conflicts during the upgrade, so we did a good job at finding those.
[16:43] <yofel> and well, plasma *does* work mostly after the upgrade
[16:48] <marco-parillo> 1) I was able to open a konsole and sudo poweroff
[16:49] <marco-parillo> 2) Yes, the plasma crashes everytime I apt update upgrade are ugly, but has not really interrupted my workflow.
[16:49] <marco-parillo> 3) That happened sometime during wily daily updates also. Testers need to be warned to remove from favorites and re-add them.
[16:51] <yofel> true, konsole will work which is enough for testers I guess
[16:51] <yofel> 3) is really bad if that was done even by a regular update :(
[16:52] <yofel> but ok, I guess some people will appreciate using it on wily
[16:53] <yofel> !testers
[16:53] <yofel> for those still on wily and/or using wily, plasma 5.5 is in kubuntu-ppa/backports-landing for testing. For known issues so far see above
[17:10] <sgclark> ok, I think I still have wily somewhere
[17:10] <yofel> meh, found another issue after all
[17:10] <yofel> Unpacking plasma-framework (5.18.0-0ubuntu1~ubuntu15.10~ppa1) over (5.15.0-0ubuntu1) ...
[17:10] <yofel> dpkg: error processing archive /var/cache/apt/archives/plasma-framework_5.18.0-0ubuntu1~ubuntu15.10~ppa1_amd64.deb (--unpack):
[17:10] <yofel>  trying to overwrite '/usr/share/kdevappwizard/templates/qml-plasmoid.tar.bz2', which is also in package kapptemplate 4:15.08.3-0ubuntu0.1~ubuntu15.10~ppa1
[17:15] <ScottK> yofel: Unpack order is not deterministic so one success us not enough to say there's no file overwrite issues.  One gives you about 50% chance of that.
[17:16] <yofel> ScottK: I know, I was just happy that I didn't hit something already in my first test..
[17:16] <ScottK> OK.  Just making sure.
[17:16] <yofel> thanks for caring :)
[17:23] <mamarley> I actually haven't had a working GUI way to shutdown any of my Kubuntu systems since the first KF5/Plasma5 release.  If I tell it to shudown from Kickoff, Plasma dies but then it just sits there and does nothing.
[17:25] <shadeslayer> how do you start your session?
[17:25] <shadeslayer> SDDM or manually?
[17:26] <mamarley> SDDM
[17:27] <yofel> try quitting quassel before that
[17:27] <shadeslayer> huh 0.o
[17:27] <yofel> that seems to be the cause for that for me
[17:27] <mamarley> yofel: OK, but I suspect there is still a Bug somewhere.
[17:28] <yofel> it keeps running in the background unless I either do another shutdown from krunner (which is still there), or do something more forceful like killing ksmserver or so
[17:28] <yofel> only happens on 2 of 3 systems here, which makes me rather clueless what to look for...
[17:28] <mamarley> I usually just Ctrl+Alt+F1 and momentarily press the power button.
[17:35] <denza242> hi guys, I got an idea for KDE Docs. Basically, to increase readability and make it easier for newbies to understand, I think that the docs should be ported to the MarkDown format
[17:35] <denza242> I have even made a (rather quick and dirty) example using pandoc
[17:36] <denza242> (the docs I used are for konversation)
[17:37] <sgclark> I randomly get it. sudo shutdown -h now always works though. I thought it was my mix match of ppas and packaging cruft haha. We should probably start a bug? or is there one?
[17:37] <mamarley> I do have tons of PPAs on my systems too, but I have also reproduced the issue on systems that don't have many PPAs.
[17:38] <sgclark> denza242: we have no control over that, please try #kde-docs (it might be a hard sell though)
[17:38] <denza242> sgclark: ah, thanks
[17:39] <denza242> (I was merely pointed here by someone else)
[17:39] <BluesKaj> namely me :-)
[17:39] <BluesKaj> well, now we know 
[17:44] <sgclark> no worries :) just pointing to the place that handles kde docs
[17:46] <denza242> sgclark: posted there 
[17:57] <_Groo_> hello all
[17:57] <_Groo_> have been away for a few weeks
[17:57] <_Groo_> how can i help testing 5.5.3 in wily?
[18:01] <_Groo_> ok, backports-landing, ill test tonight and report back here
[18:03] <lordievader> Hehe, I just upgraded to backports, lets go one step further \o/
[18:30] <lordievader> clivejo, yofel: Upgraded to backports-landing without problem.
[18:30] <lordievader> Rebooting through the menu works.
[18:40] <genii> Yay sddm-kcm
[18:55] <janmalte> Are there some simple tasks which help out testing Plamsa 5.5 for Willy?
[18:56] <clivejo> janmalte: just use it
[18:57] <janmalte> well, i dont feel very comfortable to use it for daily work at the moment ;) 
[18:57] <clivejo> understandable
[18:57] <clivejo> but thats the best way to test it :)
[18:58] <clivejo> and report any bugs, no matter how small they seem
[19:50] <ovidiu-florin> hello people
[19:50] <clivejo> hi ovidiu-florin
[19:50] <clivejo> hows you?
[19:51] <ovidiu-florin> better
[19:51] <ovidiu-florin> I've had some problems
[19:51] <clivejo> glad to hear that
[19:51] <ovidiu-florin> but I hope I'm on the right path to solve them now
[19:51] <clivejo> glad to hear you are better :P
[19:51] <ovidiu-florin> building okular in pbuilder now
[19:51] <clivejo> did you do a batchpatch?
[19:52] <clivejo> okular is building fine on LP, its just the symbols are throwing warnings
[19:52] <ovidiu-florin> and I can't test localy to see that I can solve the symbols issue?
[19:53] <ovidiu-florin> or I can do that only on launchpad?
[19:53] <clivejo> well you can, but its kinda wasting your time
[19:53] <clivejo> you need to grab the two buildlogs from LP
[19:53] <clivejo> and patch the symbols file with the diffs
[20:16] <ovidiu-florin> clivejo: done
[20:17] <ovidiu-florin> I'm testing in pbuilder now
[20:19]  * clivejo crosses fingers
[20:21] <ovidiu-florin> clivejo: the missing symbols have not updated
[20:22] <ovidiu-florin> clivejo: https://paste.kde.org/pcusi5k79/5sjxr4
[20:23] <ovidiu-florin> how do I solve those?
[20:23] <ovidiu-florin> manual patch?
[20:23] <clivejo> remove them manually
[20:24] <ovidiu-florin> the pbuilder prints them being replaced
[20:24] <ovidiu-florin> not just removed
[20:24] <clivejo> basically you should check the symbols before you remove them
[20:24] <ovidiu-florin> api.kde.org?
[20:24] <clivejo> its like a to be sure, to be sure
[20:25] <yofel> reading the upstream git log is usually more meaningful
[20:26] <yofel> except that in case of okular you may skip that as all removals are safe
[20:26] <ovidiu-florin> so... how should I check the symbols?
[20:26] <yofel> first of all, the (optional) ones are always ok to be removed
[20:26] <yofel> that's usually internal GCC symbols that leak into the public namespace
[20:27] <ovidiu-florin> ok, how do I remove them?
[20:27] <ovidiu-florin> manual edit ?
[20:27] <yofel> yes
[20:28] <ovidiu-florin> yofel: first one is not optional
[20:28] <ovidiu-florin> how do I check it?
[20:29] <yofel> ovidiu-florin: it indeed is not, what you missed this time is that the soname version of libokular was changed from 6 to 7
[20:29] <yofel> so as the interface version changed, any kind of changes are OK
[20:29] <yofel> clive took care of that before you took over okular
[20:30] <yofel> otherwise your best bet is to run c++filt on the symbol to look where it likely came from
[20:30] <yofel> then look up the source history to find out what happened to it and/or talk to upstream
[20:30] <clivejo> yofel: does that happen much?
[20:31] <yofel> esp. the libs shipped in applications like to change the version every release, i.e. libmarblewidget, kdcraw, kipi, etc.
[20:32] <yofel> frameworks and some other cases have an ABI stability guarantee, there you need to watch out
[20:33] <yofel> and in the worst case, when upstream messes up we can still work around it by using the DebianAbiManager, but that's something for another day
[20:36] <_Groo_> k, ive upgraded to 5.5 from 5.4 with backports-landing
[20:36] <_Groo_> only 2 errors
[20:37] <_Groo_> https://www.irccloud.com/pastebin/awGwt7xG/
[20:38] <_Groo_> also, is anyone able to search documents, images, etc with dolphin: baloo works because i can search from the search anid launch widget, but the options in dolphin are greyed out
[20:39] <yofel> thanks for testing
[20:39]  * yofel wonders how to fix the l10n mess -.-
[20:39] <ovidiu-florin> I have to go
[20:39] <ovidiu-florin> I've updated the docs
[20:39] <ovidiu-florin> with what I've learned now
[20:39] <ovidiu-florin> and will continue tomorrow
[20:40] <ovidiu-florin> thanks for your help clivejo and yofel
[20:41] <yofel> hm, let me make l10n ubuntu1 just the new release and ubuntu2 the conflict resolution
[20:41] <yofel> and I'll need to fix the version in plasma-desktop-data 
[20:42] <_Groo_> also, i have some strange behaviour in kf5-nm
[20:42] <ovidiu-florin> see you tomorrow guys :-D
[20:42] <yofel> nini
[20:42] <_Groo_> it shows me an empty icon in systray alongside the proper icon
[20:42] <_Groo_> anyone else seeing this?
[20:42] <ovidiu-florin> sorry for such a short presence
[20:42] <mck182> I have a question about kci-unstable, quite often a newer package is available but it will not upgrade to it, here's an example of plasma-framework:
[20:42] <mck182>  *** 4:5.17.0+git20160104.1118+15.10-0 0
[20:42] <mck182>         100 /var/lib/dpkg/status
[20:42] <mck182>      5.18.0+git20160111.1839+15.10-0 0
[20:42] <mck182>         500 http://ppa.launchpad.net/kubuntu-ci/unstable/ubuntu/ wily/main amd64 Packages
[20:42] <mck182> ...why is that happening (every now and then)?
[20:43] <yofel> mck182: because we mess up during development and the CI builds broken packages
[20:43] <mck182> oh
[20:44] <yofel> _Groo_: not with NM, on my other notebook I have an invisible device manager though
[20:45] <mck182> yofel: how can I recover from this? ie. upgrade to the newest version available?
[20:46] <yofel> mck182: you'll have to force-install the older version: apt install plasma-framework=5.18.0+git20160111.1839+15.10-0
[20:46] <yofel> might need the same for a couple libs
[20:46] <mck182> ah /me tries
[20:47] <mck182> slow internet, that will take a while ._.
[20:48] <_Groo_> yofel: go to system tray settings, disable network > apply, enable network > apply
[20:48] <_Groo_> yofel: nm comes back
[20:48] <yofel> sorry about that. We currently have no concept of feature branches, so by the time we notice that we messed up the CI already built the mess
[20:50] <mck182> yofel: np, it's called "unstable" for a reason :)
[20:51] <_Groo_> anyone able to "see" documents in dolphin (using the search documents option)?
[20:51] <_Groo_> want to make sure its not my machine alone
[20:55] <sgclark> yofel did you put 5.18.0 kf5 in staging-applications on purpose?
[20:55] <yofel> sgclark: yes
[20:55] <yofel> apps don't build with 5.15
[20:55] <sgclark> ah ok
[20:56]  * yofel wonders what to do with those file conflicts
[20:56] <yofel> cripple the 15.08 packages to work with plasma or make plasma uninstallable until 15.12 is done...
[20:56] <sgclark> having lib so version problems with pim, trying to sort out what I need to rebuild
[20:57] <yofel> yeah, Dan said that they're not paying attention to ABI right now :/
[20:57] <sgclark> ugh
[20:58] <yofel> apt-cache rdepends is probably the most useful tool here
[20:58] <sgclark> think I will go through the list and rebuild all deps
[20:58] <sgclark> oh
[20:58] <sgclark> that works to thanks
[21:01] <clivejo> hummmm my clipboard history has gone :/
[21:02]  * yofel makes jedi-like gestures
[21:02] <yofel> It was not important to you!
[21:02] <clivejo> It is very important to me!
[21:02] <sgclark> lol
[21:10]  * clivejo gives up
[21:12] <_Groo_> clivejo: you mean the clipboard widget in systray?
[21:12] <clivejo> I mean libkipi and trying to understand it
[21:13] <clivejo> oh yeah, the systray icon is gone
[21:13]  * yofel has the systray icon
[21:13] <clivejo> my systray looks a mess :(
[21:13] <yofel> but yeah, some icons seem to randomly go missing..
[21:13] <clivejo> took me ages to realise what the paper between two rollers was
[21:14] <clivejo> dropbox icon is bearly visable
[21:14]  * yofel thinks the new battery widget looks ridiculous
[21:14] <yofel> that's a white box. end.
[21:14] <clivejo> and 3-4 arent even showing
[21:16] <clivejo> so I got my clipboard icon back by removing it and adding it again
[21:17] <_Groo_> clivejo: yep
[21:17] <_Groo_> clivejo: same problem with wifi for me
[21:17] <_Groo_> clivejo: systray is always 'finicky" between versions
[21:18] <_Groo_> clivejo: can you test dolphin search for me?
[21:18] <clivejo> do KDE not have a PACKAGERS file to give an indication on where files hould go?
[21:18] <clivejo> _Groo_: what do I need to do?
[21:18] <_Groo_> open dolphin
[21:18] <clivejo> done
[21:18] <_Groo_> on the left you have the search for" panel
[21:19] <_Groo_> with documents,images,audio files, videos?
[21:19] <clivejo> yup
[21:19] <_Groo_> click on it
[21:19] <_Groo_> does it work?
[21:19] <clivejo> which one?
[21:19] <_Groo_> advanced icons are greyed out?
[21:19] <_Groo_> none of them works for me
[21:19] <clivejo> same#
[21:19] <_Groo_> bummer
[21:20] <_Groo_> baloo works
[21:20] <_Groo_> if you use the search widget it works just fine
[21:20] <clivejo> clicked on images in my pic folder and nothing
[21:20] <_Groo_> but "search:/"inside dolphin is broken
[21:20] <_Groo_> says missing protocol
[21:20] <_Groo_> but timeline:/ works
[21:20] <_Groo_> click on "recently saved" today,yesterday
[21:20] <_Groo_> if you have baloo indexing stuff, you should see it working
[21:21] <_Groo_> but not search
[21:21] <_Groo_> maybe it was fixed in 15.12?
[21:21] <_Groo_> yofel: any eta for landing 15.12?
[21:21] <yofel> _Groo_: a week if I'm optimistic. There's the debian merges left as well for apps
[21:22] <_Groo_> yofel: k
[21:22] <yofel> currently trying to figure out those file conflicts
[21:22] <yofel> i love it when two current versions ship the same thing *-.-
[21:23] <_Groo_> yofel: yeah its a pain
[21:28] <_Groo_> but overall its a solid release
[21:28] <_Groo_> working as intended anyway
[21:31] <_Groo_> although i believe we need to see why plasma-nm is acting strange
[21:33] <_Groo_> im gonna update network-manager to 1.0.10 and see if it fixes anything (backport)
[21:35] <yofel> *blink* what happened to the trello board
[21:35] <yofel> are old cards now withering? ^^
[21:44] <yofel> hm, our list-missing pbuilder hook is broken as it uses the old syntax
[21:46] <soee> hi, anything important happend while i was sleeping ? :)
[21:47] <yofel> we found more bugs? ^^
[21:50] <soee> yofel: with recent updates these are marked to be removed: kde-l10n-engb kde-l10n-pl language-pack-kde-en language-pack-kde-pl ?
[21:51] <yofel> they shouldn't be...
[21:52] <soee> http://paste.ubuntu.com/14472763/
[21:53] <soee> maybe due to plasma-desktop changes ?
[21:53] <yofel> yes, but there should be updated so kde-l10n as well
[21:54] <yofel> *updates
[21:54] <yofel> *to
[22:05] <soee> i see people already testing staging-backports: https://plus.google.com/u/0/100972376182361138544/posts/YPnbzRtNYQ9
[22:16] <soee> yofel: is it possible that -l10n-* files were replaced by language-pack* files ?
[22:17] <yofel> no
[22:19] <yofel> soee: are you sure there are no updates? I did make a change in plasma-desktop that breaks l10n, but uploaded a compatible l10n set at the same time
[22:20] <yofel> hm, looks like kde-wallpapers is gone from apps
[22:22] <valorie> I think they moved it to plasma?
[22:22] <valorie> memory fuzzy on that
[22:23] <yofel> yes, I wonder where the note for that is...
[22:24] <soee> yofel: i run 3 times apt update, no new l10n
[22:25] <yofel> strange, can you please run apt with -o debug::pkgproblemresolver=true
[22:27] <soee> yofel: http://paste.ubuntu.com/14472977/
[22:28] <yofel> soee: do you have ppa-landing enabled?
[22:29] <soee> only staging frameworks and plasma i thin
[22:30] <yofel> add ppa-landing please, that's where l10n is in
[22:33] <soee> but this isn't any official ppa that will be available by default ?
[22:35] <yofel> no, but that's where stuff ends up that's supposed to get uploaded to the archive
[22:37] <soee> ok, now it works fine
[22:38] <soee> can someone confirm that discover dos not allow removing software sources (ppas) ?
[22:50]  * yofel goes merging some apps
[22:50] <yofel> akonadi, I love you - not
[22:51] <yofel> brrrrrr, libkf5akonadiprivate5.symbols has tons of MISSING lines in git..
[22:52] <sgclark> after merge or ?
[22:53] <yofel> someone "fixed" CI by just committing the comments
[22:54] <sgclark> what comments?
[22:54]  * sgclark is lost
[22:55] <yofel> #MISSING is technically a comment
[22:56] <sgclark> is this in any way related to the pim that I am working on the we decided to do rebuilds?
[22:57] <sgclark> if so  am stopping now and you can take over. 
[22:57] <yofel> nono, this is already in the PPA
[22:57] <yofel> I'm just working out file conflicts. Won't have an effect on the binary result
[23:15] <_Groo_> yofel: just a word of advice
[23:15] <yofel> hm?
[23:15] <_Groo_> yofel: it might be a good idea to see if theres a fix or a workaround for the missing network icon when plasmashell starts
[23:15] <_Groo_> yofel: or we will have some angry customers :D
[23:15] <yofel> probably, I haven't checked yet
[23:16] <yofel> well, that's why the packages are not in backports yet ;)
[23:16] <_Groo_> the stupid icon (and funcionality) only shows up if you disable/reenable in systray settings or do systemctl restart NetworkManager.service
[23:16] <_Groo_> yofel: i know, just talking
[23:17] <_Groo_> every single time you restart plasmashell
[23:17] <_Groo_> no fun :P
[23:17] <yofel> nah, it is a good idea
[23:17] <yofel> which totally doesn't happen all the time thanks to muon >.>
[23:18] <_Groo_> im gonna check plasma-nm git to see if i can create a patch from 5.6
[23:18] <_Groo_> so we wont have at least this bug to worry about
[23:18] <yofel> ack, thanks
[23:21] <_Groo_> yofel: prolly this one :P http://quickgit.kde.org/?p=plasma-nm.git&a=commit&h=190e27a1acaa4469aaeca0653fd0a4368f730ecc
[23:23] <yofel> possibly..
[23:23] <_Groo_> yofel: hmmpf... nope...
[23:23] <yofel> heh
[23:23] <_Groo_> yofel: nope, prolly not reported yet
[23:25] <_Groo_> yofel: more likely we need to revert this one: https://quickgit.kde.org/?p=plasma-nm.git&a=blobdiff&h=60b3843e8da0f907fdbd69db3233dcb678275453&hp=62fd7a9dea996f6a7257c2275ed5fd34dbfba6f1&hb=1e840b9877286592a20cfba1f91b676d178e5ae8&f=libs%2Fdeclarative%2Fconnectionicon.cpp
[23:25] <yofel> FWIW, for me the wifi icon works fine at least. Both connected and disconnected
[23:25] <_Groo_> yofel: if not, its not fixed yet
[23:25] <yofel> don't have a cable to test that
[23:26] <_Groo_> yofel: if you do a kquitapp plasmashell
[23:26] <_Groo_> an then run plasmashell
[23:26] <_Groo_> does the icon shows up?
[23:26] <_Groo_> wifi?
[23:26] <yofel> yes
[23:26] <_Groo_> im not on cable either
[23:26] <_Groo_> really?
[23:26] <_Groo_> cause it stays invisible here
[23:26] <_Groo_> yofel: is it a fresh install? or an upgrade from 5.4.x?
[23:26] <yofel> upgrade
[23:26] <_Groo_> same as mine
[23:27] <yofel> we don't have any 5.5 install media yet
[23:28] <_Groo_> interesting
[23:28] <_Groo_> i do have a vpn
[23:28] <yofel> I don't. At least not on this notebook
[23:32] <_Groo_> removed, didnt made a difference
[23:32] <_Groo_> anyway ill dig more later
[23:32] <_Groo_> seeya all later
[23:33] <yofel> cya
[23:52] <bluesabre> Hello Kubuntu developers!  This is a bit of a followup from a discussion we had back in September (http://irclogs.ubuntu.com/2015/09/20/%23kubuntu-devel.html) in regards to shimmer-themes, the Orion GTK theme, and the breeze package...
[23:55] <bluesabre> Would you like to take the orion theme into your package/care?  It's no longer maintained, but may still be used by kubuntu.  If at all possible, we would like to remove it from the shimmer-themes package (since it is unmaintained, and prevents our uploaders from being able to upload new versions of the shimmer-themes package)
[23:55] <yofel> bluesabre: just go ahead and remove it, we'll be switching to breeze-gtk this cycle
[23:56] <bluesabre> yofel: Cool, we'll start to get that rolling then
[23:56] <bluesabre> Thanks for the quick response!
[23:56] <yofel> thank you for asking :)