Here is a patch that brings back LMB actions when the applets are locked.
With unlocked applets LMB is needed for editing, and I didn't want to spend
too much time on it.
Read here for some discussion:
https://phabricator.kde.org/D24748
But better than nothing, isn't it? ;)
Place it into
Okay, I removed /etc/init.d/NetworkManager and now I have a wireless
connection after reboot.
Incidentally, in pursuing that, I proved to my satisfaction that the
output of the rc-status -a command is from /etc/runlevels with this script:
cd /etc/runlevels
diff -wy <(rc-status -a | sed -n
> IMO the best thing to do, which is also what I think can be
> called "fix" without unethically redefining words in the
> English language, is to silently unmerge all KDE's fluff,
> and install i3 + dmenu + i3status + i3lock, and call it a
> day.
LOL I remember going through that phase as well.
On Fri, Jan 3, 2020 at 8:51 AM Spackman, Chris wrote:
>
> udisksctl power-off --block-device /dev/sdx
>
> I didn't see that command mentioned in the thread yet. I've been using
> it, after umount, for about 8 months for roughly weekly backups and
> some misc storage. So far, I've not seen any
On 2020/01/01 at 08:00pm, Dale wrote:
> Grant Taylor wrote:
> > On 1/1/20 5:09 PM, Dale wrote:
> > Note: umount will normally block until buffers are flushed to disk.
> >
> >> Is it safe to turn it off even tho it is doing whatever it is doing?
> >
> > I wouldn't.
> >
> >> Should I wait?
> >
> >
On Fri, Jan 3, 2020 at 5:57 AM Dale wrote:
>
> Can you post a ls -al /boot for both kernels and images? That way I can
> see how it names them when doing it your way. If I can make sense of
> it, I may try doing it that way. Thing is, it'll change eventually
> too. lol
I use the standard
On Friday, 3 January 2020 01:37:49 GMT Dale wrote:
> I'll try to reboot the new kernel in a bit. It's building at the
> moment. Thanks for posting about this. I did not see it in other
> replies. I thought it might be in Rich's but didn't see it. The extra
> nudge was helpful.
>
> Dale
>
>
Neil Bothwick wrote:
> On Fri, 3 Jan 2020 01:27:22 -0600, Dale wrote:
>
I name my kernels and such this way:
root@fireball /usr/src/linux # ls -al /boot/kernel*
-rw-r--r-- 1 root root 7061552 Oct 14 2018 /boot/kernel-4.18.12-1
-rw-r--r-- 1 root root 7082032 May 15 2019
John Covici wrote:
> On Fri, 03 Jan 2020 02:27:22 -0500,
> Dale wrote:
>> John Covici wrote:
>>> On Thu, 02 Jan 2020 21:57:29 -0500,
>>> Dale wrote:
Howdy,
I'm trying to rebuild a kernel to include new options, see other
thread. I got the kernel built but dracut is giving me
What do I have to do to prevent NetworkManager from running?
I am running a prepared gentoo image which has openrc and NetworkManager
configured. The wpa_gui app doesn't see my wireless (but starting the
wpa_supplicant from rc-service does).
So, I removed NetworkManager with:
rc-update
Hello
For some time I've been wondering why I had a difference on
dev-python/olefile-0.46 between 2 machines : one was installed with
python_targets_python3_7, the other wasn't.
And I finally pinpointed it to package.accept_keywords containing
"dev-python/olefile ~amd64" on one of the machines
On Fri, 3 Jan 2020 01:27:22 -0600, Dale wrote:
> >> I name my kernels and such this way:
> >>
> >> root@fireball /usr/src/linux # ls -al /boot/kernel*
> >> -rw-r--r-- 1 root root 7061552 Oct 14 2018 /boot/kernel-4.18.12-1
> >> -rw-r--r-- 1 root root 7082032 May 15 2019 /boot/kernel-4.19.40-1
>
On 30/12/19 19:18, Daniel Frey wrote:
> 2. On all NFS clients, including the NFS server which mounted other NFS
> mounts, all NFS client options had to be selected or the mount would
> fail. It didn't matter specifying nfsvers=4.0 as a mount option, it
> failed if there was no NFS client kernel
13 matches
Mail list logo
