[06:39] <maxb> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668771 sigh
[06:40] <maxb> I wonder if I can just turn off systemd-resolved completely
[06:47] <maxb> Success, but doesn't look like networkmanager passes DNS server info to resolvconf any more :-/
[06:51] <maxb>   - Disable resolvconf support because it is broken with DNS plugins other
[06:51] <maxb>     than "dnsmasq".
[06:51] <maxb> boo :-(
[07:01] <maxb> Best thing about PPAs: being able to self-fix things and get them across all your Ubuntu installations with ease
[10:16] <brunch875> Did the volume bar in the indicator get stepped? I used to fine-tune the system volume there because the keyboard shortcuts lack precision.
[15:17] <flo_> hello to everyone. i'm using kubuntu 17.04 and i'm triyng to use the global menu but every time i start atom text editor the cpu goes up to 60 % of use. is there any way i can blacklist atom?
[21:39] <robotics_flo> @valorie thank you for your help
[21:40] <valorie> so I did see your posting in here earlier, but you were gone by then
[21:40] <valorie> so: any reason for atom editor in particular?
[21:41] <valorie> it seems you have a mix of unity and kubuntu
[21:41] <valorie> and atom isn't acting well with either
[21:41] <robotics_flo> just because i'm used to it and has the plugins i want. i'm just learning
[21:41] <valorie> ah
[21:42] <valorie> kate is my favorite
[21:42] <valorie> in general, you get the best "well-tested behavior" by sticking with the applications that go along with your environment
[21:42] <valorie> although of course you can choose what you like
[21:43] <robotics_flo> atom on unity/gnome works well....works well on kde also. it's the only app tough that makes the cpu fly with the global menu
[21:43] <valorie> I can't think of anything that kate *lacks*
[21:43] <robotics_flo> it doesn't happen if i use in window menu
[21:43] <valorie> what do you need from it that it doesn't have?
[21:44] <valorie> ok, I know nothing about the global menu or blacklisting, since this is not KDE software
[21:44] <robotics_flo> sass and tpl hylighting and autocompletion
[21:44] <robotics_flo> ok.....can you help me to troubleshoot my touchpad?
[21:45] <valorie> do you have synaptics installed?
[21:45] <valorie> apt-cache policy synaptics
[21:45] <valorie> in the cli
[21:45] <robotics_flo> how can i test that in the console?
[21:46] <valorie> if it is installed: synaptics &
[21:46] <valorie> if not, sudo apt install synaptics
[21:47] <robotics_flo> wow ....it's not installed. i didnt aspect that
[21:47] <valorie> not sure what unity uses
[21:48] <valorie> anyway, that should give you to the option to turn down or off the sensitivity while you are typing
[21:48] <robotics_flo> unable to find synaptics.....give me a sec. i'm triyng to install it through the package manager
[21:50] <robotics_flo> but xserver-xorg-input-synaptics is installed
[21:50] <valorie> hmmm
[21:50] <valorie> that should be it, yes
[21:50] <valorie> it's older, so might have changed names over time
[21:51] <valorie> I suppose that means it won't work under wayland
[21:51] <valorie> sigh
[21:52] <robotics_flo> the strange thing is that gestures work on the touchpad a thing that a mouse can't do....so it must load some kind of wright driver but its not recognised in the kde settings center so i cant configure it
[21:53] <robotics_flo> i heard something about lib-input somewhere and some kind of change related to that but i cant pin point that
[21:57] <robotics_flo> @valorie i found this: KDE's Touchpad KCM has libinput support for Xorg, but not all GUI settings are available yet. You may find that a setting such as Disable touchpad when typing has no effect and other options are greyed out. Until the support is extended, a workaround is to set the options manually with xinput set-prop.
[21:58] <valorie> oh
[21:58] <valorie> faffy
[21:58] <valorie> but doable
[21:58] <valorie> so my info is out-of-date; sorry about that
[21:59] <robotics_flo> lol what do you know about xinput?
[21:59] <robotics_flo> and its settings?
[21:59] <valorie> well, I would just `man xinput`
[21:59] <valorie> and then try stuff
[22:00]  * valorie doesn't know much, truth be told
[22:00] <valorie> or: xinput --help
[22:01] <robotics_flo> thank you for your help anyway