[00:18] I have upgraded my system from 15.10 to 16.04 . There is a clear improvement in performance. I am very happy to see some updates in muon. [00:18] Thanks everyone for the hard work! [00:30] +1 murthy [00:31] ovidiuflorin, download page looks nice [00:47] : Sgclark: could you help tux|dude with a black screen on login problem [00:47] : Almost 2am here and I can hardly seen my screen any more! [00:47] : I am on a train with only a phone sorry [00:48] : Ah I'm in bed on telegram! [00:48] : Lol [00:49] : Google may help. Sounds like something I have heard before. Don't know fix though. [00:49] : Should been zzzz two hours ago [00:49] : I've seen yofel help fix it [00:49] : Yes indeed :) [00:50] : Blacklisting nouveau? Gosh dunno sorry. Try google. [00:51] : Never thought about asking what graphics card! [00:51] : My mind has gone to sleep without the rest of me! [00:52] : Anyways night all [00:52] : I have spent many a night fighting with graphics drivers [00:52] : Sleep well clivejo. Awesome work this release! ! You rock. [00:58] Hey so ive been told to ask this here but after updating to 16.04 im having issues with sddm not starting. I just get no login screen at all [01:05] : I am on a train without access to my laptop. Sorry. I recall something like that before. Terminal screen systemctl start sddm? Can't be of much more help on my phone sorry [01:07] Ill try that [01:07] Oh huh [01:08] Rc—local.service loaded failed failed [01:09] : There was also systemctl sddm enable? But that looks to bigger problems? [01:10] : Was this an upgrade that went from init to systemd? Definitely not something I can debug on my phone... [01:10] I just used the updater program to update to 16.04 i didnt do anything fancy [01:12] : Sorry can't be of anymore help on a phone. [01:12] Dont worry bout it [01:17] hi [01:21] tuxdude143: hi [01:25] Hi [01:25] Can you help with my issue at all? [01:30] Sddm isnt starting correctly at all [01:35] tuxdude143: Ya i can try [01:35] tuxdude143: can you come to #kubuntu channel? [01:43] Yup [01:43] tuxdude143: use my nick so that i will get desktop alert and respond to you soon [01:44] tuxdude143: you upgraded from which version? [05:31] : Yakkety Yak :) [06:50] : ahoneybun if it looks just nice, then I failed === thelionroars1337 is now known as thelionroars [09:00] heya! do-release-upgrade sill shows no new release has been found :( [09:27] what i did was change the server from Poland to Global and now it does upgrade ;) [09:28] :) [09:28] sgclark: ping [09:35] * sheytan wonders if ssdm will start automatically after upgrade [09:36] * soee suggest to prepare some hammer [09:37] soee: I startx for like 3 month now :D [09:38] https://youtu.be/otCpCn0l4Wo?t=14s [09:38] rofl [09:39] sitter's link says all :D you cant touch sddm [09:39] sitter: HA HA HA, do you always have a video by hand for each problem? :D [09:40] the internet puts things at your fingertips you know :P [09:40] i sure do :D [09:45] * sheytan goes for a reboot [09:46] * soee_ cu in 3 months :D [10:21] seems to be a lot of issues with MySQL upgrade :( [10:23] and switching it off and back on again isnt fixing it :( [10:23] and that fixes everything [10:47] anyone alive?!? [10:49] * mamarley dead. [10:50] * clivejo is itching to get staging! [10:50] clivejo: Sounds like a great idea! [11:01] * soee_ supports clivejo [11:30] Howdy all === ovidiuflorin is now known as telegram === telegram is now known as teleirc === teleirc is now known as telegram-sync [11:43] Quintasan: core was dead [11:44] hm, the log has an alerting amount of QPSQL errors.. [11:47] like syntax errors on executing prepared statements o.O [11:48] hi yofel [11:48] hey [11:48] how are you today? [11:48] me, so far so good. My quasselcore, not so much [11:48] well, it's resurrected for now [11:49] upgrade problems? [11:50] hard to say, the first time this happened was after I upgraded my server to 15.10. After I installed the Qt5.5 backports it's been running for a long time without issues again, just to die again now [11:50] the DB errors seem unrelated to it dying though, as they seem to have been happening for a while now [11:51] the core didn't write a crash log either though, it just froze [11:59] Skuggen: Hi all. After upgrading to 16.04 mysqld process is eating 1gb of ram (it was ~150mb before upgrading). Why? [12:01] yofel: maybe we could stage Frameworks and Plasma ? :) [12:01] if you can do it without git, sure [12:01] or make a throw-away stage [12:02] ha ;) [12:02] or hm [12:03] the script could be changed to operate on kubuntu_xenial_backports [12:03] then later we do a forward-merge into whatever dev will be called [12:03] yakkety yak [12:03] 16.10 [12:03] yup [12:04] release guys are uploading the toolchain [12:05] wait, seriously? :D [12:05] yup :) [12:06] deadly serious :P [12:06] would I lie to you! [12:06] wow, that was his shortest release codename blogpost ever [12:07] must have been late for an appointment [12:07] he already left the codename unknown for like 2 weeks post-release once, which made people unhappy, so I doubt that... [12:08] still, maybe work on the backports branch until we moved to LP, which will need some compatiblity changes in CI [12:08] well there are uploads going into yakkety [12:08] sure, but we have no git branches, and I don't intend to create any [12:09] : clivejo care to elaborate on this? https://trello.com/c/1VADoFoT/28-make-better-use-of-header-space-on-kubuntu-org [12:10] ovidiuflorin: there used to be a large gap at the top of the page [12:11] but the menus have now moved into it [12:11] that should be closed [12:11] : I still see that gat sometimes on mobile [12:11] : that should be reported as an issue in the theme repo [12:11] my thoughts where to maybe put social media links [12:12] clivejo: could you start the backporting ? [12:12] : that would be above the nav bar? [12:12] soee_: Im not comfortable doing that [12:12] Id rather work on dev then backport [12:13] so ubuntu 16.10 has 2 packages in the repos , "yakety yak" ;-) [12:13] which is the way our workflow is designed [12:15] yofel: any thoughts on where you want the git on LP? [12:16] I could maybe work on moving frameworks over [12:16] and create yakkety archive branches [12:19] we might want to try to do a small packager hangout before we do anything. As esp. for frameworks was to not package them ourselves at all [12:19] *frameworks the plan [12:20] just stage directly from master? [12:20] because I think we need to choose between "fork from debian, and maybe sync again for the next LTS, or whenever sensible" or "take as much from debian and do as little packaging ourselves" [12:21] if we do *anything* outside master, we will probably again do something where debian goes "yes, you did that, and it was stupid, and we won't be compatible to that" [12:21] and in the end we again need to maintain a diff for a year [12:22] FWIW, our current workflow of syncing with debian every release won't work, maybe every LTS, or we need a different plan [12:23] debian seem to be getting faster at packaging new releases [12:25] yofel: Most of the time, the PostgreSQL errors are nothing to worry about. If you pastebin them somewhere, I can check to see for sure though. [12:26] mamarley: right, though I'm pretty sure it fails to insert stuff in those cases [12:27] and I would really like to know how a very simple select statement can have a syntax error [12:27] unless there's quoting missing... but this is a prepared statement... [12:27] Some of the error messages are erroneous. [12:28] If you show me the errors, I can tell you if something is wrong. [12:29] mamarley: stuff like https://paste.kde.org/pjudxrl82 [12:30] yofel: Yeah, that shouldn't be happening. What core version are you running? [12:31] 0.12.2 with postgres 9.4.6 and Qt 5.5.1 [12:32] yofel: Ah, yes. There was a bug in 0.12.2 pertaining to missed messages and SQL query errors caused by multiple core users in the same channel. You can upgrade to 0.12.3 using ppa:mamarley/quassel which will solve the problem. [12:32] well then, let me do that [12:33] 0.12.4 should be coming out before too much longer with even more bugfixes. [12:38] done, so far so good [12:38] with ? :) [12:38] yofel: I apologize; that particular bug was actually my fault. I introduced it accidentally when modifying the PostgreSQL backend to handle database outages better. [12:39] nah, happens. Now let me attach strace to all quassel threads again in case it freezes next time [12:48] acutally.. we might want to SRU that.. [12:49] I agree, but 0.12.4 should be released very soon. I think it would be better to wait and get that., [12:49] good pint [12:49] *point [12:50] Sput said it would be sometime this weekend. If it is Saturday, I can help get it ready, but on Sunday I will be on a historic train trip all day and won't have a computer with me. [12:54] nah, take your time [12:54] in any case, thanks for the ppa package, works fine so far :) [12:55] No problem :) [13:36] : yofel the 15.04 and 15.10 trello boards can be closed. I'm not an admin, can you please close them? [13:37] @ovidiuflorin: done [13:39] : thank you [14:02] yofel: is there anything we can do to fix discover? [14:02] what's broken? [14:03] http://s31.postimg.org/641fcu721/Discover.png [14:03] the text [14:03] looks a mess :( [14:03] where is that image still used? [14:04] its a screenshot of my current discover [14:04] well, my screenshot is on the release notes page, and looks fine [14:04] what version of discover are you running? [14:04] clivejo: http://people.ubuntu.com/~yofel/pics/Screenshot_20160421_184138.png [14:05] 5.6.2-1ubuntu1 [14:05] hummm [14:05] * clivejo scratches head [14:06] looks fine in 5.5.5 http://s31.postimg.org/5jxguo0u1/Discover555.png [14:06] but when I go to 5.6.2 it looks bad [14:09] what's weird is that discover shows me " " as test for a couple seconds until the real text appears [14:10] *as text [14:11] here too [14:14] clivejo, did you install 5.6 from neon ? [14:15] no [14:15] from where then? ..I d like to try it, clivejo [14:16] I dont understand what you are asking me? [14:16] plasma 5.6 [14:17] or am I offbase [14:17] BluesKaj: we have only muon or something used with verion 5.6 [14:17] ok thanks , clivejo [14:18] we are using plasma 5.5.5 but uploaded 5.6.2 version of plasma-discover to fix a bug [14:18] I'm bored , since there doen't seem to be anything new with 16.04 atm :-) [14:19] but Im seeing a weird corruption in discover with text going everywhere [14:20] FWIW, the "too small folderview widget" on our image is a general plasma problem [14:20] try that on any installed system, and it's initially too small everytime [14:21] could that install link not be converted into an icon on the "desktop" ? [14:22] Don't you need your own widget for that? (no idea) [14:22] or hm, maybe an application launcher widget with a custom config file.. [14:23] yeah app launcher [14:23] big install button [14:24] we could look into that for 16.10, for now fixing the folderview init would benefit more people [14:27] Maybe that is what you are suggesting, but could install be the first item on the Favorites in the Kicker Applications Launcher on a live ISO? It is strange that my VM and one of my physical laptops dumped me straight into the live environment, but my other laptop gave me the try / install option. === Quintasan_ is now known as Quintasan [14:37] there was one person that complained about the live session not working for him at all when he was using nouveau, so there seem to be a buch of factors playing a role here [14:38] we could probably make it a favorites entry too.. [14:39] clivejo: Not sure what would make it suddenly start eating ram. Will need to look into it [14:39] (re: mysql-question) [14:40] I was going to install Senile on an old laptop, but when I powered it up there is no screen :( [14:40] was hoping to have it running for tomorrow === nodoubleg is now known as nodoubleg-lunch === nodoubleg-lunch is now known as nodoubleg === telegram-sync is now known as ovidiu-florin [17:58] the telegram sync service will experience some down time, in the next hour, while I restart the service to use the new authenticated username. If all goes well, this shouldn't take more than 5 minutes. Thank you for your understanding. [18:15] What do they do in #kde-soc ? === ovidiu-florin is now known as telegram === telegram is now known as ovidiuflorin [18:22] genii: talk about KDE SoC [18:22] :P [18:23] System on Chip? [18:23] <@ovidiuflorin>: Summer of Code [18:23] <@ovidiuflorin>: either Google or KDE variant [18:23] aaaaaaaah! OK [18:29] I briefly imagined it was where they were working on getting KDE running on tiny embedded devices like smartwatches [18:34] <@ovidiuflorin>: that's not a bad idea [18:38] The Telegram sync service is back online. Please keep in mind that it is still running from my personal server, so rare and random interruptions due to power failure and/or ISP decides to go crazy. [19:01] Hi folks [19:31] <@Clifford>: So what do you all think of the +1 release name? [19:32] <@Clifford>: I'm not even sure what a Yak is! [19:32] Yakety Yak (Don't talk back!) [19:32] I think it is funny. [19:32] https://en.wikipedia.org/wiki/Yak [19:33] heh, we have a voip service here called Yak [19:33] <@Clifford>: Like a buffalo? [19:33] like vonage [19:34] <@Clifford>: Yeah yak is slang here for talking rubbish [19:34] yeah, here too [19:34] <@Clifford>: That ejit yaks on [19:36] <@Sick_Rimmit>: How about one of these [19:36] yeah asian bison/buffalo [19:37] <@Sick_Rimmit>: I wonder where we have to put our pictures and stuff to get it looking like Haralds [20:02] <@sgclark2>: yofel if you want work on the lp move magic, I can work on branches for clivejo and I to use in the meantime. Not near my laptop atm tho. [20:19] is there any other discussions/3rd parties/considerations need to be looking into before we move to LP? [20:21] <@sgclark2>: I have been quite vocal on the subject and have heard no objections. [20:22] how do debian feel about it? [20:22] <@sgclark2>: We just need to do it. I will take care of any changes we would need for ci [20:23] <@sgclark2>: This is about us being productive, deian still has access to our work should they want it, and vice versa. [20:24] <@sgclark2>: Debian rather. [20:24] yeah, but does it mean we start to fork away from debian? [20:24] <@sgclark2>: Git a a great tool like that. [20:25] <@sgclark2>: Um. No. We still have to debian merges. [20:25] in theory LP users will be able to sync to the packaging, but will they actually do it? [20:25] <@sgclark2>: Same as italawys was, only on laubchpad. [20:25] when we are staging will LP handle the load? [20:25] <@sgclark2>: I do not understand your last statement [20:26] using scripts to automate 20-30 packages [20:26] debian git was sometimes timing out [20:26] <@sgclark2>: We were on LP formuch longer than debian git. Worked fine. [20:27] <@sgclark2>: Ugh fat phone fingers. [20:27] I thought the git feature was newish? [20:27] used to be bzr? [20:27] <@sgclark2>: Right, it was bzr back then. But still. [20:29] <@sgclark2>: Do you not want to move? [20:30] Im just want to know all the pros/cons [20:31] <@sgclark2>: Biggest pro is relieving the barrior of entry [20:31] <@sgclark2>: Nothing really changes technical [20:32] will it be one big LP archive, or attached to each package in LP? [20:32] <@sgclark2>: We can still help wach other out. And I encourage we still collaborate. [20:33] will we loose our current Debian Alioth rights? [20:34] <@sgclark2>: I think that was already happening because someone messed up a few times. No name bombs. [20:37] can we control access to the LP git? [20:37] I plan to put the repositories under https://launchpad.net/~kubuntu-packagers/+git, so yes [20:38] that's kind of the biggest reason to do this ^^ [20:38] so to commit you need to be a member of kubuntu-packagers [20:39] or indirectly via a related group [20:40] right [20:40] that was how our bazaar branches worked [20:41] so all the VCS fields in the control files would have to be changed to point to the git archive in question? [20:42] yes (you want to script that ^^) [20:42] I guess the move would be automated, copying from debian, updating the control file and commiting to LP [20:43] then automation scripts need updated to find the new git repos [20:44] same with CI [20:44] the move is one of the big things, the CI update for the new triggers another one. Updating the repositories and automation is trivial [20:44] address update in theory is all we need [20:44] oh [20:44] triggers [20:45] does LP have triggers? [20:45] do we have control over git hooks on lp? [20:45] the docs say it can send HTTPS POST commit notifications [20:45] no idea what's in them [20:46] what branches will you move? [20:46] we have no hook control in launchpad. It supports webhooks, which should be enough for the CI [20:46] and what becomes master? [20:46] \o/ so happy to hear discussion about easing the workflow [20:46] y'all worked way too hard this cycle [20:47] everything, and master should be $dev. Which will obsolete kubuntu_yakkety_archive I guess.. [20:47] we'll need to remember to branch that on release day though [20:47] * valorie hands out champagne and chocolate for all you hard workers [20:47] thanks :) [20:47] lost ne on that last statement [20:47] lost me [20:47] new dev release is called Kakkety Yak [20:48] which will be master branch on LP [20:48] I know that. but what do you mean $dev and obsolete stuff? [20:48] oh [20:48] I think I see the light sorry [20:48] will need some thinking [20:48] when we move to 17.04 we need to branch master to kubuntu_yakkety_archive [20:48] right I got it now [20:49] clickety clack huh? [20:49] *ideally* we would use a branching scheme that's directly compatible with gbp [20:49] as master follows dev [20:49] gbp? [20:49] git buildpackage [20:49] git build package [20:49] ah [20:49] so we don't have to pass a dozen options to it so it works [20:49] yeah [20:50] could CI merge master and kubuntu_yakkety_archive [20:50] keep them in sync [20:50] so obviously this will eed some thought and coding, we don't want to fall dreadfully behind. Should clivejo and I work in a backports branch and start the merges? backports.. [20:50] what would need fixing for that is the CI merge cascade, or _archive would have to be a mirror for marster [20:51] yeah, feel free to work on backports, just don't tag anything [20:51] ok [20:53] what do you branch backports from? xenial_archive? [20:53] then merge in master? [20:53] well obviously I am not at home and probably will not get this done till monday. [20:53] hm, so jenkins has a built-in remote trigger. So the question if launchpad is flexible enough with the target URI [20:54] hmm good question, unstable has latest changes I think. What versions are debian on? [20:54] plasma etc [20:55] frameworks 5.19 [20:55] isnt 5.20 out? [20:55] yup [20:55] meh yeah I want to work on the latest an greatest [20:55] * sheytan removing the nvidia driver fixes the problem with sddm and black screen after upgrade [20:55] but why? :( [20:56] nvidia and sddm have had issues since forever [20:56] file a big with nvidia please [20:56] bug [20:56] it was working fine :( [20:56] oh debian are still only on Plasma 5.5.4 [20:57] I want 5.6 :P [20:57] ok so lets make backport branch from archive, then merge debian, then package newests on top of that [20:58] I expect we are not allowed to skip debian merges :( [20:58] need to start with frameworks 5.20 then? [20:58] well, the original idea was to sync 5.19 from debian. But if you folks want to do it yourselves.. [20:58] sgclark: well yofel said earlier that maybe we should only do it on LTS releases [20:58] and we really might want to skip that [20:58] <@ovidiuflorin>: @Sick_Rimmit don't add me as maintainer [20:58] oh! super. [20:59] would essentially mean forking (permanently?), but what we did this time does not work [20:59] Then lets just branch archive to backports and bump to newest version and fix as we go [20:59] I agree [20:59] I thought debian were ahead of us [20:59] absolutely did not work [20:59] they are regarding frameworks [20:59] but appears not [21:00] question is what we'll do with the copyright files if we don't merge. In that case we would have to update those ourselves [21:00] oh no :( [21:01] well, you can parse the changes out from the upstream diff [21:01] whats about copyright files? [21:01] sgclark: they should match the actual code we ship? [21:01] <@ovidiuflorin>: can someone please send the current IRC topic of this channel? [21:01] not sure I know what youo are talking about :( [21:02] * sgclark does not know everything [21:02] Kubuntu - Friendly computing | Xenial is out, why are you not drinking yet? | Plasma 5.5.5: X/archive, Apps 15.12.3: X/archive, FW 5.18: X/archive | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | Package Docs (WIP) https://notes.kde.org/p/kubuntu-packaging [21:04] do you need it from Telegram account to pin it? [21:04] <@Clifford>: Kubuntu - Friendly computing | Xenial is out, why are you not drinking yet? | Plasma 5.5.5: X/archive, Apps 15.12.3: X/archive, FW 5.18: X/archive | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | Package Docs (WIP) https://notes.kde.org/p/kubuntu-packaging [21:05] love kde-connect! [21:06] ok so are we talking about the copyright file that I use copyright-helper to parse and match kde src copyrights? Or am I missing something? [21:06] * keithzg has never been able to make kde-connect work, alas [21:06] I love it too, when it works. [21:06] yofel: ^ [21:07] brilliant for copying stuff to and from phone [21:07] debian/copyright, yes [21:07] ah ok cool, that is not so bad with copyright-helper [21:09] k3b still doesnt work [21:10] why 16.04 doesn't come with plasma 5.6? [21:11] nobody had time for that [21:12] or rather the priority wasn't high enough [21:14] Also, it was one thing file exceptions to go from 5.5.x to 5.5.5 to grab the latest bugfixes, but to add new features so close to the release would have been more risky. [21:15] yofel: any dates when it comes as update? [21:15] no.5.6 was in beta when freeze hit [21:16] sheytan: "soon" [21:16] we absolutely cannot put beta software in after freeze [21:16] was nothing to do with lack of interest or time. [21:16] well technically we can, it's just a bad idea [21:17] Well I will not put beta software in after release. [21:17] period. [21:17] I mean freeze [21:17] ugh [21:17] anyway, it will get done. [21:17] eventually [21:18] anyone else welcome to join the team and make things come faster! [21:23] it's funny how canonical always breaks things just before release [21:24] k3b doesn't rip, or burn, or what? sheytan [21:32] <@ovidiuflorin>: undefined [21:32] valorie: burn [21:32] and this pisses me off, cause my computer boots from USB whenever it wants [21:32] not always [21:32] sheytan: Plasma 5.6 was only released on the 22nd March, and Xenial UI freeze was on the 10th March ( https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule ) so how could we be expected to get it into Xenial? [21:33] clivejo: I don't follow all dates of what and when was released :) [21:33] it usually is so taht major release of Kubuntu comes with a newer ver. of plasma [21:33] sheytan: well thats why 5.6 isnt in Xenial :) [21:33] hope it comes as soon as possible [21:34]