[06:39] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668771 sigh [06:39] Launchpad bug 1668771 in systemd (Ubuntu) "systemd-resolved negative caching for extended period of time" [Undecided,Confirmed] [06:40] I wonder if I can just turn off systemd-resolved completely [06:47] Success, but doesn't look like networkmanager passes DNS server info to resolvconf any more :-/ [06:51] - Disable resolvconf support because it is broken with DNS plugins other [06:51] than "dnsmasq". [06:51] boo :-( [07:01] Best thing about PPAs: being able to self-fix things and get them across all your Ubuntu installations with ease === schmidtm_ is now known as schmidtm [10:16] 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] 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? === JanC_ is now known as JanC === Guest43186 is now known as jk^ [21:39] @valorie thank you for your help [21:40] so I did see your posting in here earlier, but you were gone by then [21:40] so: any reason for atom editor in particular? [21:41] it seems you have a mix of unity and kubuntu [21:41] and atom isn't acting well with either [21:41] just because i'm used to it and has the plugins i want. i'm just learning [21:41] ah [21:42] kate is my favorite [21:42] in general, you get the best "well-tested behavior" by sticking with the applications that go along with your environment [21:42] although of course you can choose what you like [21:43] 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] I can't think of anything that kate *lacks* [21:43] it doesn't happen if i use in window menu [21:43] what do you need from it that it doesn't have? [21:44] ok, I know nothing about the global menu or blacklisting, since this is not KDE software [21:44] sass and tpl hylighting and autocompletion [21:44] ok.....can you help me to troubleshoot my touchpad? [21:45] do you have synaptics installed? [21:45] apt-cache policy synaptics [21:45] in the cli [21:45] how can i test that in the console? [21:46] if it is installed: synaptics & [21:46] if not, sudo apt install synaptics [21:47] wow ....it's not installed. i didnt aspect that [21:47] not sure what unity uses [21:48] anyway, that should give you to the option to turn down or off the sensitivity while you are typing [21:48] unable to find synaptics.....give me a sec. i'm triyng to install it through the package manager [21:50] but xserver-xorg-input-synaptics is installed [21:50] hmmm [21:50] that should be it, yes [21:50] it's older, so might have changed names over time [21:51] I suppose that means it won't work under wayland [21:51] sigh [21:52] 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] i heard something about lib-input somewhere and some kind of change related to that but i cant pin point that [21:57] @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] oh [21:58] faffy [21:58] but doable [21:58] so my info is out-of-date; sorry about that [21:59] lol what do you know about xinput? [21:59] and its settings? [21:59] well, I would just `man xinput` [21:59] and then try stuff [22:00] * valorie doesn't know much, truth be told [22:00] or: xinput --help [22:01] thank you for your help anyway