[00:41] <D-rex> trying to ppa-purge the backports ppa but I'm getting the following errors when I do http://pastebin.com/YJXKefje
[00:41] <D-rex> anyone want to take a stab at what's wrong?
[03:54] <[Relic]> any clue if wayland works on k16.10 with backports?
[07:04] <negi> jp2gmd
[07:04] <negi> #jp2gmd
[09:08] <assmith> I have made some iptable changes (bridge utils) and some ip changes to an interface, what is the recomended way of making those changes persistent?
[09:12] <lordievader> assmith: What version of Kubuntu are you using?
[09:16] <assmith> 14.04
[09:19] <lordievader> Oh... I thought bridge configs went in /etc/network/interfaces before systemd.
[09:19] <lordievader> For the firewall, I'd write a service wich loads the rules from file.
[10:01] <excognac> hi all. I'm trying on 16.10, trying to run Partition editor. Once the KDE su window pops up and asks for my root password it freezes. I can type it in ut then I have to close the window. Also, the eye icon appears so I can make root password visible, which i find weird.
[10:05] <excognac> Any ideas why is this happening? http://pasteboard.co/qhim9ar7h.png
[10:06] <hateball> excognac: if you run "partitionmanager" from a terminal, do you get any output?
[10:07] <excognac> hateball: it runs perfectly https://paste.kde.org/pkonks6pd
[10:09] <hateball> excognac: you got prompted for sudo password etc?
[10:09] <excognac> hateball: yep
[10:10] <hateball> I'd take a look at the launcher then
[10:10] <hateball> the .desktop file you are using, that is
[10:11] <hateball> perhaps it says "kdesudo partitionmanager" which shouldnt be needed, polkit should handle that
[10:11] <hateball> it should still work, but...
[10:12] <excognac> what is weird it has worked fine until now (although i ran it last time a month ago or so)
[10:14] <hateball> Well things tend to work until they break
[10:17] <excognac> haha
[10:18] <excognac> in the meanwhile I'm looking for the .desktop with locate
[10:19] <excognac> is it this one? /usr/share/kservices5/plasma-containmentactions-applauncher.desktop
[10:23] <hateball> excognac: how do you launch partition manager via the gui? using krunner or clicking the kicker?
[10:24] <excognac> hateball: clicking the kicker
[10:25] <hateball> excognac: rightclick kicker and edit the menu, look under system for the partition editor entry
[10:25] <hateball> and have a look how it is configured
[10:25] <hateball> it should just be "partitionmanager" and be set to run as a different user (blank)
[10:26] <excognac> it is exactly like that
[10:26] <hateball> otherwise the real .desktop file is /usr/share/applications/org.kde.PartitionManager.desktop
[10:26] <hateball> excognac: does kdesudo work for anything else?
[10:26] <hateball> like if you "kdesudo kate"
[10:31] <excognac> you mean from cli? yes, they do work
[10:32] <hateball> very strange
[10:32] <hateball> I am on 16.04 here so cant replicate
[10:33] <hateball> I use 16.10 at home and I cant recall having an issue there either... but I dont remember the last time I used kdesudo either so :|
[10:35] <excognac> hateball: does this help to clarify? https://paste.kde.org/pvnmkrsvd
[10:35] <hateball> excognac: no that looks fine (same as mine)
[10:37] <excognac> hateball: the ibus thing is not a problem?
[10:39] <hateball> excognac: That is more than I know. I get the ibus errors as well, but not the QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed
[10:39] <hateball> nor QFileSystemWatcher: failed to add paths:
[10:39] <hateball> so perhaps that is something to google
[10:39] <excognac> yeah I'm on it
[10:43] <excognac> I'll try this https://ubuntuforums.org/showthread.php?t=1485667
[11:06] <BluesKaj> Hi folks
[11:47] <R13ose> Is there a way to get better wireless connection?
[11:49] <hateball> R13ose: begin by describing your problem, and what chipset/driver you are using
[11:49] <hateball> R13ose: otherwise the answer will be "Yes."
[11:49] <hateball> You can always make everything better
[11:50] <R13ose> Not sure on the chipset.  I am not able to get a wireless connection where I am but others are from further away
[11:51] <hateball> Right, so here one might have asked "how can I find out what chipset I have?"
[11:51] <hateball> And then the reply would have been something like run "lspci -k" in a terminal
[11:53] <R13ose> hateball: how do I only show wireless chipset?
[11:54] <hateball> !paste | R13ose
[11:54] <hateball> just look for the network related bits
[11:54] <R13ose> Okay
[11:58] <R13ose> hateball: paste.kde.org/penm5uq7s
[12:00] <hateball> R13ose: and what does "iwconfig" say?
[12:01] <hateball> also, wifi is black magic
[12:01] <hateball> R13ose: when you say others get signal, do they get signal in the same spot as you?
[12:01] <hateball> as there could be a number of factors affecting wifi signal
[12:01] <R13ose> hateball: yes I am on wireless now on phone
[12:03] <hateball> R13ose: right, so share the output from iwconfig
[12:04] <R13ose> hateball: added to same paste url
[12:05] <hateball> nope
[12:07] <R13ose> hateball: paste.kde.org/papyljcym
[12:09] <hateball> R13ose: you cant see any networks at all when scanning with "sudo iwlist scan" ?
[12:10] <hateball> R13ose: any interesting output when running "dmesg" ?
[12:13] <R13ose> hateball: I see the wireless network when I do scan.  The dmesg is super long, how do I only show the parts you want to know?
[12:14] <hateball> R13ose: dont worry about that, just pastebin it all
[12:15] <hateball> R13ose: and this network you are trying to connect to, is it run by you?
[12:15] <hateball> I mean, do you have any control over its configuration
[12:15] <hateball> if you have a phone connected to it you should be able to see some details at any rate
[12:15] <R13ose> Yes I control that
[12:16] <R13ose> how do I do sudo with a normal user?
[12:19] <R13ose> hateball: ^
[12:23] <hateball> I dont even understand the question
[12:23] <hateball> You run "sudo <command>"
[12:23] <hateball> obviously the user needs to be a member of sudoers
[12:24] <R13ose> Okay
[12:24] <hateball> which by default your first user will be
[12:30] <R13ose> hateball: paste.kde.org/ptc2n7hyn
[12:33] <hateball> R13ose: are you in the US?
[12:33] <hateball> or more importantly, what channel is your router broadcasting on?
[12:34] <R13ose> Canada
[12:34] <hateball> I think that is the same, but I am not sure. anyhow line 767 says the card is using US domain, so then you wouldnt be able to use channel 13 that is allowed in the EU, iirc
[12:35] <R13ose> Channel 12
[12:35] <R13ose> 11*
[12:37] <hateball> R13ose: and when you run iwlist scan, did it show your network or ntot?
[12:37] <R13ose> hateball: wireless one yes
[12:37] <hateball> Seems US and Canada are the same, channel 11 max
[12:39] <hateball> R13ose: and if you try connecting to the network, what happens?
[12:39] <hateball> R13ose: if it fails for whatever reason, there should be output in dmesg
[12:41] <R13ose> hateball: on normal user, the wireless connection doesn't show up
[12:42] <hateball> R13ose: What does that mean?
[12:42] <hateball> R13ose: If you run iwlist scan without sudo? or when using network-manager?
[12:44] <R13ose> hateball: when a normal user in network-manager
[12:53] <R13ose> hateball: thoughts?
[12:54] <hateball> R13ose: was this broken on install?
[12:54] <R13ose> hateball: I don't think so
[12:55] <hateball> well if the kernel loads the modules and you can see networks with iwlist, there should be nothing wrong there
[12:55] <hateball> so then the problem would be with network-manager
[12:55] <hateball> And I dont really know how to troubleshoot that
[12:58] <R13ose> hateball: yet, if I am closer to the box, I can see this
[13:29] <mixxit_> please help me
[13:29] <mixxit_> my pc is about to crash i think any minute
[13:30] <mixxit_> i clicked a link in chat and its opening thousands of endless winebrowser windows
[13:32] <mixxit_> Aggfafasdsa
[13:34] <mixxit_> cant click kde bar any more