[00:00] valorie: I'm still not finding Muon on the system. [00:00] install it then? [00:00] we no longer provide it by default [00:01] That's not good. :/ [00:01] well, we can't provide everything by default [00:01] and it was unmaintained for awhile [00:02] now it has a maintainer again [00:02] I understand that. But Muon was a good package manager. Why switch to Discover? *Pbbbtt.* [00:02] LINKSWORD2: You should also be able to upgrade from the command line [00:03] well, the KDE Store is providing a lot more stuff now, from free wallpapers to plugins, and snaps of various applications [00:03] I believe it's do-release-upgrade [00:03] mgolden_: that's correct [00:03] do-release: command not found [00:03] `sudo do-release-upgrade` [00:04] however, ensure that you have fully upgraded before you do that [00:04] so `sudo apt update && sudo apt full-upgrade && sudo do-release-upgrade` [00:04] Also uninstall your PPAs with ppa-purge [00:04] if you want to do it via the commandline [00:05] Alright. Looks like I have to close Konversation for the upgrade to work. [00:10] Hello [07:33] Hi, does anyone know which of the plasma config files under ~/.kde/share/config/ or ~/.config/ are still relevant? there seems to be some duplication between the two folders [08:02] how to set up my desktop, so settings wouldnt be reset after logging out and logging in back? [08:03] i change wallpaper, change desktop to folder view [08:03] log out, log in and i have default desktop [08:04] newke: you can save state at logout [08:04] Desktop Session Login and Logout in System settings [08:05] or I just typed session into krunner which alt+f2 [08:05] ok ill try [08:07] Good morning. [08:29] hello ? === zero is now known as Guest23595 [10:33] exit [11:18] hi everybody! What client do you use for google doc? [11:20] o/ [11:23] lordievader: hi [11:24] Hi, does anyone know which of the plasma config files under ~/.kde/share/config/ or ~/.config/ are still relevant? there seems to be some duplication between the two folders [11:29] yocs0000: How are you doing today? [11:29] amichair: For plasma5, the ones in ~/.config. [11:30] Plasma 4 used ~/.kde. This has been changed. [11:30] lordievader: OK .... you? I am tryin to find a working client for google drive / google doc .... [11:30] lordievader: all of .kde is no longer relevant? can it be deleted? or just the plasma config files? [11:31] amichair: There might still be plasma4 applications around, they might make use of it. [11:31] yocs0000: Doing good. I use grive I believe for google drive syncing. [11:31] lordievader: ok, so ~/.kde/share/config/plasma* can be deleted? they're all unused? [11:32] amichair: Not sure. [11:32] I wouldn't remove them if I where you. [11:32] What you can do is rename the folder and see if things break/get reset. [11:32] That way you'll know if something makes use of it. [11:33] lordievader: true [11:33] lordievader: I hope at some point the upgrade scripts will clean up old unused config files [11:37] lordievader: does it work well? I thought it had been abandoned! [11:37] amichair: please use apt-file find to see whether the file is referred to by a package [11:38] yocs0000: nice, I'll try it out [11:39] amichair: remember that if cancel a file that is referred, then you break the package .... not a good idea. [11:40] amichair: so sudo apt-ge install apt-file, sudo apt-file update , sudo apt-file find === divadsn_ is now known as divadsn [11:42] yocs0000: thanks, I haven't heard of apt-file before [11:43] amichair: it work well [11:43] amichair: llet me know whether it solves your problem, but I suggest you do not remove confirguraton files manually, even if they seem to be unused [11:46] yocs0000: it shows them to be unused... but then again, it also shows ~/.config/plasma-org.kde.plasma.desktop-appletsrc to be unused even though I know for a fact that modifying it does change plasma behavior [11:47] yocs0000: perhaps they are generated files rather than ones installed by the package or something like that [11:52] amichair: oh, sorry, you are talking about the files in the home directory of the user? [11:54] amichair: my fault .... if you cancel those, you only screw up the user configuration, and if you remove the entire directory they will be recreated in default state at the next boot .... [11:54] amichair: the important thing is that you do not remove the "originals" [12:07] yocs0000: is there any way to check which of those user config files are really used, and which are remnants of old versions that didn't clean up after themselves properly? [12:12] yocs0000: It works for my purposes. [12:13] yocs0000: Don't think apt-file will work for config files, since these are usually generated and not shipped with the package (talking about user config, not system config here). [12:14] lordievader: yeah, that's what I was thinking [12:18] lordievader: yes, you are correct .... as I was saying to amichair these are generated at boot if they are not there .... so you can essentilly do whatever you want with them really .... [12:18] amichair: but keep in mind if you remove them without a backupand then they have important configuration information you lose it .... [12:19] yocs0000: of course [12:19] Hence the suggestion of moving/renaming the folder ;) [12:19] I was just wondering if there's a proper way to check what's used and what's not, other than deleting everything and checking every app and widget to try to detect if it broke in some subtle way [12:20] lordievader: completely agree with you .... make a good backup and stove it away first of all. [12:21] lordievader: there is also an interesting trick: look at modification and access times .... those files that have not been modified or accessed since installtion are probably not in use anymore.. [12:21] amichair: If there is a config in both ~/.kde and ~/.config probably only the latter is in use. [12:21] yocs0000: nice idea, though some of them I accessed myself while trying to figure out what they are and if they're being used :-) [12:24] amichair: well, then you cannot use that trick anymore :) [13:08] How come QtWebEngine is not packaged for Kubuntu? [13:13] You are not talking about the QtWebKit libraries? [13:38] Hiyas all [13:44] afiefh: is that not what libqt5webkit5:amd64 is? [13:44] yocs0000: as far as I understand it that's qtwebkit, the predecessor to qtwebengine [13:46] afiefh: OIC [13:46] I see an ebuild on my Gentoo box. Don't see a package for Debian though (don't have access to Kubuntu). Guess it is too new for Debian/Kubuntu. [13:47] afiefh: https://wiki.qt.io/How_to_Try_QtWebEngine <-- you could build it, there is a very good tutorial here. === efm__ is now known as efm === mgolden is now known as mgolden_ === morgan_ is now known as yossarianuk [15:01] hi - is there a ppa to download multimarkdown for (k)ubuntu ? [15:05] I've found this -> https://github.com/fletcher/peg-multimarkdown/wiki/How-do-I-install-MultiMarkdown%3F [15:05] to compile from git (insstructions are out of date slightly) [15:05] but anyone know of a repo ? [15:06] going to ask in #ubuntu (if that's not against the rules) [15:07] yossarianuk, why not ask in #kubuntu-devel === Haudegen is now known as Guest39619 === dilfridge is now known as gollum [15:14] ok BluesKaj: thanks === Guest39619 is now known as Haudegen [15:32] !kodi [15:32] !info kodi [15:32] kodi (source: kodi): Open Source Home Theatre (executable binaries). In component universe, is optional. Version 16.1+dfsg1-2 (yakkety), package size 12 kB, installed size 62 kB === gollum is now known as EMH-1 [16:31] BluesKaj: tried to install Kodi, I had o clean the system afterward .... it is fairly disruptive!! [16:32] yocs0000, what did you have to clean up ? [16:34] I haven't had a problem with kodi, some of it's servers are a bit flaky in terms of disconnecting them, but otherwise kodi itself is quite stable [16:35] for kubuntu 16.10 install kodi-jarvis, don't muck about with the dev version , it's not ready for everyday use [16:42] BluesKaj: it completely froze my plasma .... I had to unisntall, and autoreove everything it had dragged in .... [16:42] BluesKaj: I did sudo apt-ge install kodi [16:42] yocs0000, which kodi version? [16:43] BluesKaj: the oe in the repository of 16.10 64 bit [16:43] then which Kubuntu version? [16:43] ok [16:44] hmm, odd because I've removed and reinstalled a few times without any trouble [16:46] BluesKaj: when it started everything froze, then when I rteid to switch it off it took some time, but after switching off the application all lost their windows decoration and menu bars, and the browsers were not usable anymore .... [16:49] yocs0000, that's the first time I've heard of that happening , unless something else froze the desktop that affected your systemsettings themes etc [16:49] which is what i suspect [16:50] because kodi is quite self contained [16:53] BluesKaj: maybe too much running at the same time .... [17:06] BluesKaj: Is there a home theater based on VLC? === lethu_ is now known as lethu [17:16] yocs0000, I used VLC as my HTPC player for many yrs since it's so configurable untill I figured out the settings on kodi were actually more relaible anbd stable...but as a Home Theater Suite it's streaming capabilties aren't as wide ranging as Kodi [17:18] yocs0000, however VLC as a media player is still near the top of the list ...I still use it occasionally === zippy is now known as Guest92374 [19:57] BluesKaj I did that autoremove [19:57] but I still have gnome metacity [19:58] How do I take that out [19:58] clean it back to kubuntu only [19:58] apt remove gnome-desktop iirc [19:59] !purekde [19:59] If you want to remove all !Gnome packages and have a default !Kubuntu system follow the instructions here « http://www.psychocats.net/ubuntu/purekde » [19:59] Dr_Coke, ^ [19:59] thanks [20:07] That didn't work for me [20:07] so I went into synaptic package manager [20:07] and looked for cinnamon and gnome-desktop [20:08] and removed [20:08] and it removed a bunch and install a bunch [20:08] let me reboot and see if it went ok [20:10] That's fixed it [20:10] Because it was a broken install [20:11] and somethings I installed after the ppa finished installing what it could and then i tried to install things anyway it's gone thank goodness === ahoneybun_ is now known as ahoneybun [22:49] How do I auto update Opera Browser? [23:14] r1 [23:14] oops [23:20] !info Qupzilla [23:20] qupzilla (source: qupzilla): lightweight web browser based on libqtwebkit. In component universe, is extra. Version 1.8.9~dfsg1-3 (yakkety), package size 830 kB, installed size 5639 kB [23:37] back [23:48] morning... Any ideas how to resolve this: https://paste.kde.org/pwjdow38y [23:50] Is it a common output for 16.10? [23:51] EventHorizon: sounds like your mirror is not answering [23:51] do you have a particular mirror configured? [23:51] I habe tried different servers... common and other??? [23:52] valorie: ...It's for the Kubuntu PPA.. [23:52] not intentionally... [23:52] Unit193: also The repository 'http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu yakkety Release' does not have a Release file. [23:52] Exactly. [23:52] which is why I suspect a mirror [23:52] PPAs don't have mirrors. [23:52] oops [23:53] its a funny one... [23:53] Usually that means that specific PPA isn't publishing for that series. [23:53] right, there is no yakkety on LP [23:54] backports is just being staged now, then there will be something to serve [23:54] http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu/dists/ <-- no yakkety [23:55] I wonder why and how you have that in your repository list, EventHorizon? [23:56] good question.... I cant tell you (been playing around with the system lately). [23:56] I would comment that out in Discover/Muon or whatever you use to manage your repos [23:57] sorry which one??? [23:58] kubuntu-ppa [23:58] when we have backports ready to go, we'll announce it on Kubuntu.org [23:58] and I assume in the /topic here