[00:48] Lol [00:49] You think by changing topic it will get done faster ?!? === nameless is now known as Guest91236 === greyback is now known as greyback|away [10:08] mamarley: so how did the FW5.22 installation go? [10:09] clivejo: It went fine. The systems seems to function fine. I launched several applications and played around with them without any apparent problems. [10:09] Good job :) [10:10] Im still fighting with this router [10:10] stopped working over night [10:12] I was using it on my laptop fine last night, but when my phone connects it says internet not connected and disconnects [10:13] how do you remove just one icon from the panel? [10:14] I keep dragging and dropping the browser and creating a permanant shortcut [10:15] The way with which I am familiar is to unlock the panel, mouse over the undesired icon, and click the "X" on the popup that appears. [10:17] ah [10:17] have to click the hamburger menu and put it into edit mode [10:18] mamarley: activities work fine on 5.22 ? [10:18] LOL Ive removed the entire panel numberous time to get rid of it! [10:18] soee: I don't use activities and don't know how to test them. [10:18] clivejo: ... :D [10:20] looks like the networkmanager-qt got some movement [10:22] patch has made it into yakkety [10:24] Is there anything else to be done before FW5.22 can be backported to Xenial? [10:26] mamarley: there are some major changes to the way things are structured [10:26] Between 5.21 and 5.22? [10:26] It looks like FW and Plasma will have to be shipped together otherwise there will be major breakage [10:26] KDE have moved stuff about [10:27] Ah, I see where you rebuilt Plasma in the staging-frameworks PPA too. I didn't notice that when I upgraded the VM. [10:27] split packages up, new ones going into FW [10:28] Oh wait, I was actually looking at staging-plasma. [10:28] I havent rebuilt Plasma on FW5.22 [10:28] there was a release about kwallet needing to be respun due to a regression [10:29] Im basically waiting on that (i cant find the respun tarball) [10:29] Yeah, sorry, I was looking at staging-plasma, not staging-frameworks. Clicked the wrong link. [10:30] oh [10:30] they have named it the same! [10:31] I was looking for kwallet v5.22.0-rc2 [10:31] duh! [10:31] tarball names do not change until tarballs go public [10:31] ah, I didnt know that! [10:32] thanks sitter [10:32] sitter: how is Jon? [10:32] he back to work? [10:38] clivejo: still alive ^^ [10:38] sore I bet [10:40] sitter: whats going on with translations, are they being shipped with the actual packages now? [10:44] Italian Military to Save Up to 29 Million Euro by Migrating to LibreOffice :) [10:47] clivejo: frameworks/plasma always shipped translations in the package [10:47] I do not have the faintest idea why apps doesn't [10:48] very strange why they shipping them in two packages [11:28] bleh, Nextbuttons still does not work in installer === greyback|away is now known as greyback [11:52] Hiyas all [12:04] wgrant: FYI archive.ubuntu has /ubuntu/ ad infinitum http://archive.ubuntu.com/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ :) [12:07] wgrant: [14:06] after http://archive.ubuntu.com/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ ubuntu disappears [12:07] xD [12:08] I find it suspicious that you actually tried that :P [12:08] and then it have http://archive.ubuntu.com/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/Archive-Update-in-Progress-ubuntu-economy [12:08] which have 0 [12:08] xD [12:09] that's a transient file I think, 404s now [12:09] no.. is crazy.. [12:10] shows up once and gives 404 other times [12:10] :P [12:23] hey, did you disable drkonqi in favor of apport in the 16.04 release? [12:30] That's a shame :( http://scarlettgatelyclark.com/2016/kubuntu-farewell-my-friends/ [12:34] clivejo: is there a fix for activities in plasma 5.6.3 ,? I had to revert to 5.5.5 [13:41] Anyone using YY and plasma 5.6.3 done a system upgrade today? [13:41] mamarley: ^ ? [13:42] clivejo: Yeah, I upgraded earlier this morning on Yakkety with both FW5.22 and Plasma 5.6.3. [13:42] I think I had a kernel upgrade and I'm not able to get login screen [13:43] Cliv what kernel are you running now ? 4.6 ? [13:43] Hmm, let me try it again. [13:45] Oops, I just remembered that I can't remotely access the laptop with the VM due to a network configuration thing I was testing. It will have to wait until later, sorry. [13:45] Yup seems to be the kernel [13:45] soee: on 4.4.0-21-generic now, but wont load Nvidia driver in 4.4.0-22-generic [13:46] clivejo: Try reinstalling the NVIDIA driver? Perhaps it just didn't get compiled for 4.4.0-22 for some reason. [13:47] well 4.4.0-22 works fine for me on Xenial with latest nvidia driver [13:49] removing [13:50] going for reboot [14:04] This is something more serious [14:05] oh ? [14:05] Removed nvidia driver [14:05] And reinstalled [14:05] Can't build the driver [14:06] what? [14:06] Which driver version? What error was made? [14:06] And I removed the one for .21 [14:06] So I cant get into my desktop now [14:07] 361.42 builds OK here on kernel 4.4.0-22 [14:10] I noticed a GCC update [14:10] Kernel package headers not supported [14:11] acheron88: Are you on Xenial or Yakkety? [14:14] mamarley: xenial, so toolchain may be different clive's thinking upon it [14:14] This is yakkety [14:14] Yeah, that's probably it. -22 is not a major kernel upgrade, so I would be surprised if it broke NVIDIA compilation. [14:14] I did not see the problem because, of course, my VM does not have an NVIDIA graphics card. [14:15] I hesitating over yakkety upgrade ATM [14:16] I'm fed up. Not having a good day today [14:16] Have a Nvidia card here as well, so may be a consideration [14:17] may have to try in a VM/chroot to see, if it will build in those [14:25] Router is fecked so have to rely on mobile data which is pathetic here [14:29] CLiv new router is not an option? [14:30] * mamarley would recommend something on which OpenWRT/LEDE could be installed. [14:49] I'm in middle of no where. Things have to be ordered and mailed out [14:50] (Photo, 1280x720) https://irc-attachments.kde.org/O9zUJq7M/file_20.jpg [14:50] Yeah, definitely looks to be toolchain-related. [14:52] * mamarley wonders if it might be a good idea to bring KF5/Plasma/etc. to Xenial first for a while until a little farther along in the development process when this sort of thing is less likely to happen. [14:52] It would facilitate easier and more thorough testing. [14:55] 340 driver version, so old ? [14:55] Maybe he has a 8xx0/9xx0 card? [15:20] Sorry guys. Running out of patients with this. I'll be out of action for a bit until I get this sorted out [15:21] * mamarley slaps clivejo's router around a bit with a large trout. [15:22] Yeah just the prefect storm. Cant fix it without a decent connection to down the packages [15:27] BTW can some report this to ubuntu-devel about the errors compiling drivers [15:27] perhaps try going back to nouveau as a stopgap? [15:29] I've tried. Can't get sddm to start [15:29] kwin/plasma runs OK here with that, albeit a bit laggy [15:29] Just black screen [15:29] ummmm... [15:31] Just having a bad day! [15:34] just seeing if I can get it to compile on yak's toolchain [15:42] clivejo: I get http://paste.ubuntu.com/16364083/ [15:49] my network-manager widget no longer loads the icon or the associated VPN list, I canopen the nm-connection-editor but the context menu to make a connection isn't loading with right click,....I have this huge error message popup that starts with ERROR loading QML file .... [15:50] wonder if anyone else has this issue [15:56] someone else said they had issues configuring vpn with that? [15:58] not sure if same issue though... [16:25] clivejo: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574982 [16:25] Launchpad bug 1574982 in dkms (Ubuntu) "Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler" [High,Confirmed] [16:31] sgclark: Just saw your post? whats happening? [16:46] So if I install that updated package gcc-defaults I should be able to compile kernel modules again? [16:53] that i do not know [16:55] *clivejo shakes a trout at soee* [16:58] clivejo: trying to get the gist of that, and think it could be new patched kernel from the kernel team that is needed? [16:59] Looks like a setting needs to be passed to compiler [17:03] yes, sounds like that would fix in short term. While new kernel with revised headers is the more permanent fix? [17:16] clivejo: adding 'EXTRA_CFLAGS += -fno-pie -fno-stack-protector' to /usr/src/nvidia-340-340.96/nvidia-modules-common.mk after line 40 seems to fix compile in a chroot here [17:17] then do 'dkms build nvidia-340/340.96 -k 4.4.0-21-generic' [17:17] and 'dkms install nvidia-340/340.96 -k 4.4.0-21-generic' [17:18] I've no data plan left to download the driver again [17:18] is it not in your apt cache? [17:18] Nope [17:19] And even 52mb on 2g is like watching paint dry [17:20] *clivejo throws router out the window* [17:21] when I tried in chroot it used packages - libcuda1-340 nvidia-340 nvidia-opencl-icd-340 [17:22] I see them in /var/cache/apt/archives/ of my chroot still [17:28] :) [17:28] It built the module [17:28] How do I make the system install it?!? [17:29] should auto install with dkms [17:29] if not, then those 2 dkms commands earlier will do [17:30] Oooooo [17:31] That looks better [17:31] Fingers crossed [17:32] may build. big question is does it load and work on boot though [17:32] Nope driver won't load [17:32] Still blank screen [17:32] rebooted? [17:33] Yup [17:33] after a 'update-initramfs -u -k all' [17:34] may need that ^^^ [17:35] then reboot [17:36] whenever I've had to rebuild the nvidia driver for some reason [17:36] I always do the [17:36] dkms build [17:36] dkms install [17:37] update-initramfs [17:37] then reboot [17:37] If it doesn't work after that, it fubar in some other way [17:45] See the nvidia installer is there any way to hack it to add the extra flags [17:47] the one invoked by dpkg in the debs? or the binary .run one from nvidia's site? [17:47] .run [17:47] I have an old driver in a backup folder [17:48] you can run the nvidia website one as extract only, then hack the nvidia module code and run the installer from the extracted folder I think [17:49] You happen to know how to extract it? [17:49] make it executable and run with a flag I think? 2 secs [17:50] Sorry everything is so slow on my phone [17:51] run the .bin file from command line with '--extract-only' flag [17:54] should give you a 'NVIDIA-Linux-x86_64-340.96' folder with and executable called 'nvidia-installer' in that [17:54] and the mudule code to add the compiler flags to in a 'kernel' subfolder [17:56] I've only had variable luck with that method in the past though, so good luck if you try it [17:56] acheron88: so the kernel module for the nvidia 340 is corrupted then. I got an error message to that effect earlier whe i was trying to install it on 16.10 [17:58] not corrupted, but doesn't work well with the GCC/toolchain and kernel headers currently in yakkety I think? [17:58] yeah this kerenel, 4.4.0-22-generic [17:59] Can't get -21 or -22 to work [17:59] It compiles the modules with no errors [17:59] But just a blank screen [18:00] It should flash the nvidia logo for like a second [18:00] I have to use nouveau with Xrender backend , OpenGL just cause allkinds of problems [18:00] Before dropping into plasma login screen [18:00] Yep, compiling and installing is one thing. Working on runtime is another completely [18:01] Shame I purged the working one for -21 [18:02] I was pondering whether to risk yakkety. Now I know to avoid on this Nvidia machine for a bit [18:02] and NM widget errors out inwith some QML not loadinhg message [18:02] Looks like I'll be out of action for a few days! [18:03] I had the same nvidia problems yesterday with 16.04 [18:04] The problem experience by clivejo is caused by the gcc in Yakkety and therefore does not affect Xenial. You probably had some other problem. [18:04] linux (4.4.0-22.39) buid witch gcc-5 (5.3.1-14ubuntu2)... in YY gcc-5 (5.3.1-19ubuntu1) with --enable-default-pie. [18:04] the 340 driver is getting long in the tooth anyway...may need to invest in a better gpu if this keeps up [18:05] KurousagiMK2: is that a fixed -22 build? [18:07] I should have done a clean install of Xenial instead of just installing to / and setting the mountpoint for /home when I regressed from Yakkety [18:07] oh. no. [18:07] yeah [18:09] but i did totally clean Yakkety install this morning so at least nouveau works ok with Xrender [18:11] try kernel 4.6-rc7 for YY from this ppa https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa [18:11] BluesKaj: yes, I did a cleanup with a fresh install of xenial on this machine a couple of weeks ago, and nouveau works well enough if you don't want OpenGL fancy stuff [18:13] o/ [18:29] KurousagiMK2: does the kernal work ok for you [18:31] on YY yes. [18:44] aha: http://kernel.ubuntu.com/git/kernel-ppa/mirror/unstable.git/commit/?id=c1613c321d28bf3f180e3b34ed1c82b4f7d90503 [18:45] and nvidia module builds, loads and runs to sddm login with that? [18:51] should, bun for nvidia-graphics-drivers-364 need patch to add support for Linux 4.6. https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa/+sourcepub/6403042/+listing-archive-extra [19:10] hello folks, I've been called to my dad's bedside - taking my travel computer, but the wifi is awful there so no irc. I should have telegram, but unknown whether I'll even open the laptop there [19:10] ttyl [19:14] yofel clivejo so I take it that the SRU for the networkmanager-qt went through? [19:14] I see the bug is fixed released [19:19] clivejo: has bad day [19:19] his router is dying and system not working :) [19:21] That's why I suggested that it might be a good idea to package the new stuff for Xenial for a while until Yakkety has time to become more stable. [19:42] mamarley: yup but usual way to do stuff is current -> previous [19:43] But that won't work if problems with the system prevent packagers from packaging and testers from testing.