[07:02] <lordievader> Good morning
[11:00] <BluesKaj> Hi folks
[11:48] <michaelv> hello
[11:48] <BluesKaj> hi michaelv
[13:14] <turbo64> is there a fix for gtk tray icons having black square backgrounds
[13:15] <turbo64> transparency doesnt work on the hexchat icon
[13:16] <BluesKaj> which gtk tray icons ?
[13:16] <turbo64> https://bugs.kde.org/show_bug.cgi?id=356937
[13:16] <BluesKaj> besides hexchat
[13:17] <turbo64> i dont know if the new skype client is gtk or not but it has that problem as well
[13:18] <BluesKaj> turbo64, which desktop theme in system settings ?
[13:20] <turbo64> breeze
[13:20] <turbo64> there was a package called xembed-sni-proxy that supposedly fixed this but its not in the ubuntu 17 repos
[13:21] <turbo64> the code may have been merged into plasma
[13:21] <turbo64> yeah it was
[13:21] <turbo64> and it doesnt fix it
[13:22] <BluesKaj> have you tried different themes ?
[13:23] <turbo64> yeah i tried air and oxygen and its the same
[13:25] <acheronuk> xembedsniproxy is not package
[13:25] <acheronuk> it's in plasma-workspace
[13:28] <BluesKaj> onversation shows a normal icon in the system try using oxygen theme, I don't use breeze
[13:28] <BluesKaj> konversation
[13:29] <BluesKaj> tray even
[13:30] <acheronuk> hexchat is ok here: https://i.imgur.com/JcMi3lb.png
[13:33] <turbo64> http://i.imgur.com/XyWpbLw.png
[13:34] <turbo64> what version of kubuntu are you running
[13:34] <turbo64> and plasma
[13:41] <acheronuk> that is zesty 17.04 with plasma 5.9.4
[13:57] <zztopless> has anyone encoutered the svga related irretrievable error when running kubuntu 17.04 in vmware?
[14:04] <kjd_> I am new to anything linux and installed kubuntu 17.04, when I did I didn't select the proprietary drivers option and now am having trouble with wifi, playing audio and video files. If I reinstall and select proprietary drivers may that help
[14:05] <acheronuk> kjd_: you can install them post install as well
[14:07] <acheronuk> kubuntu-restricted-extras package pull them in
[14:10] <kjd_>  I am an average user of windows and don't know any coding and have tryed to do post install with no luck and thought to just let the machine do all the work lol
[14:12] <BluesKaj> kjd_, run lspci | grep VGA for your graphics chip ID then you can find the driver for it in the package manager id available
[14:12] <BluesKaj> if available
[14:15] <BluesKaj> if it's an onboard then the driver is most likely already installed
[14:37] <kjd_> thanks BluesKaj I will give it a try
[16:15] <delphin> what's the status of KDE on wayland?
[16:18] <EvilRoey> borKed ?
[16:18]  * EvilRoey ducks
[16:18] <BluesKaj> delphin, depends on your gpu, if it's nvidia , don't even bother
[16:19] <EvilRoey> delphin: was under the impression that a distro like Debian or Ubuntu switching over to Wayland is imminent
[16:21] <BluesKaj> fedora already has
[16:22] <BluesKaj> delphin, https://community.kde.org/KWin/Wayland
[21:31] <sete_> ..
[23:07] <generation2> hi
[23:08] <generation2> on a computer without KDE with only console when I try to connect to android 5.1 phone I run "bluetoothd -n" then "./bluez-source/test/simple-agent" then "sudo pand -n -c 50:AE:F6:23:E0:A6 -i hci0" and it connects to a phone and creates interface "bnep0" so I can ssh to a phone now
[23:08] <generation2> now, on a computer with KDE I'm trying to do the same, first "bluetoothd -n" then when I run "./bluez-source/test/simple-agent" it says: "dbus.exceptions.DBusException: org.bluez.Error.AlreadyExists: Already Exists" so looks like KDE is allrady running some sort of "agent", because when I do
[23:08] <generation2> "sudo pand -n -c 50:AE:F6:23:E0:A6 -i hci0" there is window pops up with buttons: "PIN is correct" and "PIN is incorrect" and when I press "PIN is correct" the connection is established and I can ssh to a phone
[23:08] <generation2> so the question is, can I disable that KDE's "agent" so I can just use "./bluez-source/test/simple-agent" ?
[23:31] <generation2> ps shows that there is process running:
[23:31] <generation2> "polkit-kde-authentication-agent-1", it may be what I need to disable, so what if I kill it ? will it crash entire KDE ? what is it for ?
[23:53] <mparillo> generation2: I have that process running myself. It is described as "Daemon providing a polkit authentication UI for KDE" See: https://wiki.archlinux.org/index.php/Polkit#Authentication_agents
[23:54] <mparillo> If you are worried about crashing Plasma, I recommend you exit all programs, save data, ctrl alt f3, and login to a tty.
[23:57] <generation2> it could be bluetoothd's thing that is doing it, not KDE thing