[03:37] the heck is going on with this "Flames_in_Paradise" mparillo ? [04:45] yofel: removed patch from kubuntu_unstable as that doesn't apply anymore after mck182's change got in. you will probably want new release for xenial (tar is already redone) [06:53] hmm, right click on desktop not working, right click in other apps seems to be a bit laggy [06:54] krunner can't find anything so as application lanuncher [06:55] in wily, or xenial? [06:55] valorie: xenial [06:55] ok, I've not updated that laptop yet [06:55] :) [06:56] Plasma 5.5 is pretty cool, except some small issues [06:56] but i see some randomness here [06:58] I saw you in #plasma, helping out [06:58] thank you for that [07:02] yup devs helped and we found faulty code :) and Philip removed it from Frameworks 5.18 so it looks pretty stable now [07:03] i'm happy looking at what is done now = new plasma, new frameworks and apps are wip [07:04] and from what i see Plasma 5.6 is scheduled on 17 March so it should get into Xenial before release in april [07:05] so to sum it up, 16.04 schould be damn cool release :) [07:05] have we done enough streamlining to make that possible? [07:05] what exactly ? [07:06] getting this all done has been a pretty heavy life [07:06] lift [07:07] If I want to poke around the new hotness in Kubuntu and don't mind stuff breaking, where would I be looking? xenial's repositories or add a PPA on top of that? [07:07] (and if I have bugs with your answer, do you want them tagged/filed a special way?) [07:08] rww: we don't have plasma 5.4.3 backported to wily yet [07:08] and not sure we'll get it [07:08] valorie: it is for Wily :) [07:08] http://kubuntu.org/news/plasma-5-4-3-and-applications-15-08-3-for-kubuntu-15-10/ [07:09] Plasma 5.5 is no backported though [07:09] So xenial? [07:09] rww: i'm using xenial on my laptop like few weeks already [07:10] soee: have you been filing bugs in launchpad for xenial? [07:10] I've not been [07:10] oops, I meant 5.5.3 sheesh [07:10] I honestly saw very few differences with 5.4.3 [07:10] if you want to help testing new stuff use Xenial [07:10] Just file bugs the usual-way using ubuntu-bug? [07:10] valorie: not yet, i was waiting for Plasma 5.5 and new Frameworks [07:10] rww: my travel laptop is xenial [07:10] haven't upgraded for a few weeks though [07:11] rww: i always advise that [07:11] i usually try to find someone here who can confirm some bugs and than i'm reporting them [07:11] it's the best [07:12] but there are bugs in Plasma, Applications that are not our job [07:12] sounds good. any mailing list in particular I should be on? kubuntu-devel? [07:12] so then best to consult with Plasma devs [07:13] for doing that on IRC, #kde-devel or somewhere better? [07:13] sorry for all the questions, it's been a while [07:13] rww: yes, on this list often some stuff to test is announced etc. [07:13] rww: also #plasma [07:13] plasma is for desktop environment - panel, widgets, kcms etc. [07:14] kde-devel for applications [07:15] rww: I usually default to here first [07:15] *nod* [07:16] those other chans second, and an ML next -- sometimes even when I get a good answer [07:16] everybody's on the list, and not everybody uses IRC [08:18] i have fixed the right click [09:10] yofel: ping me when you have 2 min [10:32] ahoneybun: You talking about the bug reporter who originally reported https://bugs.launchpad.net/kubuntu-website/+bug/1532157 with two separate bugs in two separate components, who split out the second (more of a request actually) into Launchpad bug 1532372 [10:32] Launchpad bug 1532157 in Kubuntu Website "Link to release notes Kubuntu-Trusty throws 404" [Low,Fix released] [10:32] Launchpad bug 1532372 in Kubuntu Website "Kubuntu Release-Notes Wily-Werewolf 15.10 are missing link to RN-Ubuntu" [Undecided,New] https://launchpad.net/bugs/1532372 [10:32] I fixed the first, and was asking for website permissions to fix the second [11:00] soee: ping [11:04] yofel: i had problems with right click on desktop today. After some checks o noticed that not all Frameworks packages were updated to 5.18. Now i wonder why: yesterday i'v downgraded all to 5.17 than some packages where upgraded to 5.18 (when i was testing them). But after we wound faulty package i run upgrade with frameworks staging ppa enabled, so i thought all packages should be updates to 5.18 but they were not. Any idea why ? [11:05] not without knowing what exactly you told apt to do.. [11:06] :/ [11:06] I did the same, but for me a dist-upgrade upgraded everything [11:07] * yofel uploads new kwallet [11:09] again ? [11:09] the new tarball [11:09] ah so mck182 fixed it ? [11:10] yep, and devid did a respin [11:10] *david [11:10] cool [11:15] and let me rename discover again [11:17] Riddell: with https://git.reviewboard.kde.org/r/126680/ - would you also name the source plasma-discover please? We already have a 'discover' in the archive so we need to rename anyway [11:19] Hi folks [11:20] hey [11:21] hi yofel , how goes the battle ? :-) [11:22] making progress, after I'm done renaming discover again I can start testing plasma 5.5 on wily [11:22] right [11:22] apps OTOH, will probably take another week or so [11:22] (including the merges) [11:24] why do we have an amarok beta release in wily backports ppa o.O? [11:24] ok yofel , good to know [11:28] yofel: do you have machine with Xenial maybe ? [11:28] soee: yes? [11:29] with 5.5.3 and 5.18 ? [11:29] yes [11:30] please take a look how clipboard icon is rendered for me after reboot: https://www.youtube.com/watch?v=fN69H_HpSzQ [11:30] clivejo: I committed your amarok beta packaging to bzr, but that needs cleanup before it can be uploaded to xenial [11:30] it was ok again when i moved back to 5.17 yesterday [11:30] After upgrading to Plasma 5.5.3 on Xenial, Muon Update Manager seems to list updates available, but does nothing when I click on apply updates. Maybe I caught some things in progress. Using apt now and will report back next time updates are available. [11:30] but after upgrading to 5.18 it happens again [11:31] my icon is fine here, but I have some other item that's completely invisible [11:31] so it looks like it starts rendering - scaling up - but hangs in some moment [11:31] hm, could be panel size dependent then [11:32] there are also some rendering problems when moving panel [11:32] task manager items get strange size, loose spaces [11:32] etc. [11:33] so i'm sure that in 5.18 there was some other change that has influance on rendering [11:33] that's upstream bugs IMO [11:34] yup, just wanted to find someone who can confirm them [11:40] I did amarok beta packaging? [11:41] sometime in august it looks like [11:41] :/ [11:41] maybe just practising [11:41] possibly, but it ended up in the stable backports ppa, so now we kind of have to support it [11:42] is amarok on alioth? [11:42] no [11:42] and I wouldn't bother moving the qt4 version [11:43] or moving anything until we've decided what to do with our git stuff [11:43] http://anonscm.debian.org/cgit/pkg-kde/kde-extras/amarok.git/ [11:43] cant use that then? [11:43] no [11:43] :( [11:43] can we convert the bzr to a git archive? [11:44] well, you can on LP if you want to. But if we keep our own repo then preferably migrate the history [11:44] there was some bzr-git-import plugin IIRC [11:44] as you know Im not fan of bzr [11:45] I'm not particulary a fan of it either, but for simply packaging branches it does the job just fine [11:45] *simple [11:45] but as I said, feel free to migrate the repo to git [11:45] so why dont we use debian got? [11:46] git [11:46] we talked about moving our stuff away, didn't we? So for now I wouldn't use alioth for stuff where we have our own repo [11:47] ok :( [11:47] LP can do git just fine now. So use that if you really can't work with bzr [11:49] amarok looks so unmaintained that I really wouldn't bother investing much time in it anyway.. [11:49] I have a bad memory, its hard enough learning one batch of commands, but my brain just refuses to work with certain things [11:49] did you never use svn? [11:49] nope [11:50] ah ok [11:50] then bzr and git will feel very different indeed [11:51] I learned to program in Minux while at uni. It put me off programming and I ended up in building management [11:51] I havent really looked into programming since [11:51] I have on and off days [11:52] some days I can read and write code like it is second nature, other days its like some kind of alien language [11:53] even professionals have that, there it's called developaralysis [11:53] http://techcrunch.com/2014/10/18/you-too-may-be-a-victim-of-developaralysis/ [11:54] I prefer physical challeges now, plumbing, electrical, anything involving hands I guess [11:55] get yourself a raspi and start automating your house, then you get both sides :P [11:55] I do :P [11:55] :D [11:55] come to think of it, our l10n stuff would benefit a lot from a git migration.. [11:55] that uses a bazillion branches [11:57] grrr my pup is possessed [11:57] what?! [11:58] he ripped his bed apart this morning, I took him for a walk and stopped at my mothers house for breakfast. Left him outside for 10mins and he ripped out all my motthers pot plants [11:58] . . . [11:58] hes eating my welly at the moment [12:00] while trying to sweep up the soil and clean the mess up he was trying to bite and run away with the brush [12:03] I need to run into town for some supplies. Need some flux ASAP [12:05] has kwallet been fixed now? [12:05] aye [12:05] uploaded? [12:06] no idea.. [12:06] <- not a ~kubuntu-dev [12:06] yes [12:06] clivejo: yofet tooked care of it [12:06] is it in landing? [12:07] ah yes [12:07] kwallet-kf5 - 5.18.0a-0ubuntu1~ubuntu16.04~ppa1 [12:08] bah, my epoch hackery isn't working [12:08] has anyone tested this version ? [12:09] only 44mins old [12:10] Besides 16.04 are there other versions of Kubuntu that frequently require testing? [12:11] lordievader: backports to wily? [12:11] hi sick_rimmit, are you still sick? [12:11] what do you mean with frequently? [12:12] Well, I can image that there are times to test something on 14.04 but not frequently anymore. Basically I am trying to figure out which installs I should have on my test box. [12:12] Yes :-( [12:12] yofel: with kwallet fixed is Plasma5.5 ready for wily? [12:13] I am improving, but it really given me a hard time [12:13] clivejo: not until I'm done with discover - where I'm a bit stuck right now [12:13] stuck? [12:13] isnt it just a rename? [12:14] * clivejo says "just" like he knows the process of renaming a package [12:14] lordievader: generally, we "support" last LTS, current stable and dev. As we're currently developing the next LTS, the last one doesn't really recieve any attention anymore [12:15] clivejo: there's epochs involved... [12:15] I would like to drop those with the rename, but I didn't really want to rename the binaries *right now*, as the app itself only gets renamed for 5.6 [12:16] yofel: So, it is best for testing to have 15.10 (with backports) and 16.04 installed? [12:16] but the libdiscover is new and should not carry an epoch, but e.g. muon-discover depends on libdiscover (= ${binary:Version}) which needs an epoch that libdiscover doesn't have [12:16] -> boom [12:16] so I might go and rename the binaries after all :/ [12:17] and just leave the epoch on the transitional packages with loose deps [12:17] lordievader: yes [12:17] Check, thanks :) [12:18] I have muon on xenial by installing libmuon first then muon itself [12:19] talking about that.. [12:19] bbl [12:19] sick_rimmit: how's muon maintenance working out? [12:23] I applied the updates to Xenial with Plasma 5.5.3, and after rebooting, I no longer needed to enter my WEP password, but now I have to enter my kwallet password to connect to WiFi. [12:24] mparillo: did you remove pam_kwallet.so from the pam config? [12:24] *kwallet5 [12:28] No, is that they way we will eventually ship 16.04? [12:28] mparillo: hello [12:29] can that card be closed? [12:29] mparillo: no, I just remembered us talking about it. But that really should work.. [12:29] I'll test it in a bit [12:30] In general, I prefer to remain pretty vanilla, (not to mention I do not know how to change my pam config), but I would be happy to test with you. [12:30] ovidiu-florin: Which card, the Wikipeadia card? [12:33] sudo nano /etc/pam.conf ? [12:33] Mine is all comments. [12:34] /etc/pam.d/sddm should have 2 lines with pam_kwallet5.so [12:36] So I comment out by: # -auth optional pam_kwallet5.so [12:37] that shouldn't be commented out [12:37] # -session optional pam_kwallet5.so auto_start [12:37] mparillo: yes the wikipedia card [12:39] So, after editing, cat /etc/pam.d/sddm | grep pam_kwallet5.so shows both lines as commented out [12:40] ovidiu-florin: I am content with the wikipedia card being closed, assuming nobody else has any suggestions. After 16.04, I would want to update Wikipedia again, but that can be a new card if you prefer. [12:40] re-booting to test the kwallet for wifi password. [12:42] mparillo: they should NOT be commented out [12:44] ok, discover building, let me try out kwallet [12:48] yofel: what heppend to the Trello->IRC bot? [12:48] that was implemented in kubotu, whose server seems to be dead [12:50] mparillo: kwallet works fine for me now [12:56] OK, that was way too painful [12:57] I removed the comments and reverted [12:59] discover rework finished, my last couple commits could do with a review if someone wants to (sgclark, clivejo ?) [12:59] plasma 5.5 users might have to force-downgrade libdiscover [13:01] oopsie.. yet another version downgrade.. [13:01] hmmm [13:02] sorry about that [13:05] ovidiu-florin: something I just realized for the packaging docs, I strongly recommend every packager to have a ~/.dput.cf with this content: [13:05] [DEFAULT] [13:05] default_host_main = ppa [13:05] this isn't that important for beginners, but really important for every person with primary archive upload permissions [13:06] and by that time, you can easily forget to add that [13:35] hm, kwallet-pam is missing transitional packages [13:36] or updating the recommends in plasma-desktop should work as well [13:47] testing from landing? [13:48] that's what I'm doing [13:48] still finding stuff to fix, but slowly running out [13:49] just woke up, need at least a cup of coffee lol [13:49] you say that like its a bad thing! [13:49] well, the first part is the bad thing [13:49] but I think we can do a public tester call this evening [13:50] sorry whats going on? [13:50] * clivejo cheers and does happy dance [13:50] sgclark: talking about plasma [13:50] * sgclark scrolls [13:53] mm bouncer did not keep enough to be useful. I will look at the notes. [13:54] sgclark: mailing list might be more helpful, basically KDE have respun a tarball for kwallet [13:54] ahhh [13:54] sgclark: I would appreciate it if you could review my discover rename [13:54] the rest we pretty much took care of [13:55] yofel: how do I review? [13:55] just look at the last 5 commits in kubuntu_xenial_archive [13:56] the idea was to rename to the coming 5.6 name, drop the epoch and only add the epoch for the transitional packages [13:56] does the debian git branch get renamed too? [13:56] no, git matches the upstream source name [13:57] thinking about it, my changes probably screwed up the CI [13:57] oh well [13:57] yofel: in rules $(overridden_command) --dbg-package=muon-discover-dbg [13:58] lots of broken merges I see, I can work on those today [13:58] rename there too or no? [13:58] clivejo: that's fixed in some other commit [13:58] is it? [13:58] I thought I was current [13:58] It's fixed here and I have no diff and nothing to push.. [13:59] ah I see it now [13:59] what does muon.postinst do? [14:00] nothing useful, delete [14:00] I forgot to do that [14:00] I cant seem to find the repo [14:00] * sgclark needs more coffee [14:00] plasma/discover.git [14:00] ah [14:00] http://anonscm.debian.org/cgit/pkg-kde/plasma/discover.git [14:01] the language files arent installed? [14:02] oh muon-exporter, what ever that is [14:02] I have no idea what muon-exporter is supposed to be [14:02] will upstream rename too? [14:03] clivejo: https://git.reviewboard.kde.org/r/126680/ [14:03] that's where I got the names from [14:04] I see [14:06] if you have custom wallpaper does plasma change it back to default? [14:06] it shouldn't [14:06] only if you use the default already? [14:07] yep [14:08] where is the updated kwallet tarball? [14:08] depot? [14:08] yes [14:10] yofel: the lintain-overrides still contain conent for muon, is that on purpose? [14:10] whats the tool that scans for orphaned files? [14:10] sgclark: the binaries are still called muon-* for now, so I just fixed the package names in the lintian-override files [14:10] clivejo: orphaned files? [14:11] ok [14:11] files that apt may have left behind? [14:11] there is a tool for that?! [14:11] apt never leaves stuff behind, except config files [14:11] or I installed manually [14:11] there was a tool for it [14:11] compared the physical files to apt [14:11] and if config files are left then the package is still in the dpkg DB as uninstalled/configured or so [14:12] there is debsums, but that's checksum checking for installed packages [14:12] I had a problem with kde theme for sddm [14:13] I used a tool before called fluff or lint or something like that [14:14] /lib/x86_64-linux-gnu/security/libpam_kwallet5.so [14:15] that probably won't work if our sddm profile says "pam_kwallet5.so" which was the lib name in the old package [14:15] and as all other files in there are called pam_*, I wonder why kwallet is suddenly called libpam_* [14:15] anyway [14:15] * yofel out shopping, bbl [14:16] yofel: http://pastebin.com/uJRLKugs [14:16] are you working on discover and it causes some problems ? [14:17] yofel: looks good to me. [14:22] I think I prefered the old plasma icons for shutdown/reboot etc :/ [14:23] clivejo: you mean the colourful ones or the monochromatic ones? [14:23] mono ones [14:24] eakk [14:24] me too, the mono ones seem to be there on the default app launcher, but the ugly colourful ones on the menu launcher (this is on plasma 5.4.3 sorry, seem to be same for plasma 5.5.3 IINM) [14:25] just switch the them [14:25] theme [14:25] I no likey! [14:25] theme to what? [14:25] can someone test one thing: if you create new user account and login there, it will use old oxygen icons [14:25] dark breeze [14:26] yuck yuck yuck [14:28] I liked the old ones too, new ones dont seem to fit [14:30] soee: seem to be regular breeze icons in new account for me [14:30] hmmmm [14:30] soee: oh wait, yeah, the right click menu seems to be old oxygen icons, same on buttons etc [14:31] Im gonna have to look for a new theme [14:31] any suggestions? [14:31] can't the breeze theme be modified to use the old mono icons (if the mono icons are still in there) ? [14:32] iconset or desktop theme ? [14:32] vishalrao: ok thanks for checking [14:35] I like the dark breeze kickoff menu and taskbar, but the light breeze for windows and rest of system [14:36] ok, I am confused, I still see alot of red, but we are ready for testing? [14:37] red for what? [14:38] apps [14:38] plasma and frameworks shoudl be ready [14:38] apps are not [14:38] oh [14:38] ok [14:38] yofel: said 1 week is needed for finieh the, :) [14:38] plasma 5.5.3 is ready for testing [14:39] cool ok [14:39] apps 15.12.0 still needs work [14:39] It seems as if the muon changes (muon-discover muon-notifier muon-updater) are held back [14:39] got it, I am clear now thanks [14:39] ovidiu-florin: you still want to finish okular? [14:40] mparillo: confirmed here [14:44] BTW does kubuntu not brand the kickoff menu icon? [14:44] yofel: http://paste.ubuntu.com/14447156/ [14:45] clivejo: yes, but I'm still kind of tired [14:45] and it's hard for me to focus on reading the symbols documentation for packaging [14:46] and my keyboard looks backwards [14:47] if you can explain it to me in a few simple words, I might get it faster [14:47] kubuntu does not brand much of anything. [14:48] ovidiu-florin: as you probably know there is nothing simple about symbols. But you can run that command in the README I pointed out yesterday for a quick start. [14:55] sgclark: but I'm not sure I understand the prboblem yet [14:56] ovidiu-florin: sorry I don't understand [14:58] soee: sudo apt install libdiscover=5.5.3a-0ubuntu1~ubuntu16.04~ppa1 [14:58] the rest should figure itself out after that [15:01] mparillo: for you too: sudo apt install libdiscover=5.5.3a-0ubuntu1~ubuntu16.04~ppa1 [15:01] BluesKaj: ^ [15:03] yofel: but i don't want muon discover, I'll stick with plain muon, but thanks anyway :-) [15:03] ah right [15:04] hm, I really don't get why our kwallet modules are called libpam suddenly [15:05] sgclark: I'm not sure I understand the symbols problem with the okular package [15:06] ovidiu-florin: did you kind of get the point of having symbol files yet? [15:06] I understand teh point of having them [15:07] ok, so the problem right now with okular is that the symbol table in the packaging doesn't match with the one generated at build time from the built binary [15:07] yofel: worked [15:07] https://paste.kde.org/pvgywrux2 [15:08] yofel: that seems pretty obvious, that they would not match, since it's a newer version of the software. [15:08] Why are the symbol files stored in the packaging? [15:09] if you look into the file, you will see that every symbol has the okular version that it appeared in appended to it [15:10] that information is used by dpkg-shlibdeps to generate properly versioned library dependencies for packages that use libokularcore [15:11] it is also used to make sure that no symbols disappear between releases without upstream updating the so version of the library [15:12] that would be an ABI break and would cause applications to fail to run like this: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5: undefined symbol: _ZTIN7Akonadi8Protocol7CommandE [15:13] that's why the package actually fails to build when a symbol goes missing [15:13] (for C++, that's not sufficient actually and you need abi-compliance-checker, but that's a different topic) [15:14] now okular did change the soversion from 6 to 7, and clive updated the packaging to reflect this, he just didn't get to update the symbol files [15:14] so you now need to update the symbol files in the packaging, remove any #MISSING# lines from them and you're done [15:15] ok [15:15] I understand what needs to be done [15:16] but still I don't understand why it is the package's responsibility to make sure backwards compatibility is not broken? [15:16] because the software authors cannot be trusted [15:17] so this is a very basic saftey measure, as well as information for dpkg-shlibdeps to generate proper deps [15:17] latter was what the file was really meant for when it was introduced for C applications [15:22] " because the software authors cannot be trusted" - This seems like a very big issue to me [15:22] well, C++ ABI rules are so mental, that most developers don't even know all of them and end up breaking them by accident [15:22] and KDE CI still has no ABI check AFAIK [15:23] still has no what? [15:23] sgclark: does build.kde.org run abi-compliance-checker yet? [15:23] yet? I have heard nothing about this requirement [15:24] I'm pretty sure that was talked about a while ago, but ben either didn't seem interested or didn't have time as usual [15:24] but without kde upstream validating ABI, we have to [15:24] well no one told me... it is my ci now [15:25] I will add a workitem for it, now that I am aware.. [15:25] it's not a requirement. It's just a good-to-have thing for the kde parts that guarantee a stable ABI [15:25] yep, agreed, I will work on it [15:26] ovidiu-florin: regarding the c++ rules, enjoy the read: https://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B [15:26] * yofel -> lunch [16:02] wtf [16:02] if I compile kwallet-pam by hand I get pam_kwallet5.so [16:04] eeeeeeeeeeehm [16:04] debian/patches/fix_install_location.diff [16:04] -set_target_properties (${library_name} PROPERTIES PREFIX "") [16:10] * yofel talks to maxy.. [17:21] anyone using activites? [17:27] On Plasma 5.5.3 I have a few activities for different tasks. I have one for Kubuntu and I added an icon. I want to add an icon for OSM but the select file dialogue box wont work. Can anyone confirm? [17:50] Hmmm.. The file picker comes up below the preceding 2 dialogue boxes here, and so is unusable [17:50] same here acher88 [17:50] I guess that makes it a bug [17:52] I can close the other 2 as well, but not the file picker. [17:52]