Many of you have faced issue of wifi connection when you suspend your laptop and resume on Ubuntu 16.04 LTS, specifically after upgrade from Ubuntu 14.04 LTS to Ubuntu 16.04 LTS, I have found this from Ubuntu Forums, Thought to share with you so that It will be helpful for you guys.
16.04 runs on systemd. Try the following:
sudo systemctl restart network-manager.service
If this works, you can create a script to automate it.
Open a terminal and type the following:
sudo nano /etc/systemd/system/wifi-resume.service
Now paste the script in there with a right click. Exit with CTRL + X and press Y to save. Now to activate it:
Today I have tried to Install Virtualbox 5.0.x on my Newly Installed Fedora 24. I expected it to run smoothly as expected but It failed in kernel module compilation with following error
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
Then After I tried to reload module again with command sudo modprobe vboxdrv and failed again with following error
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
Second try hinted me that there is nothing wrong in VirtualBox but something related to “key”, So I tried to search for a solution and landed to Official VirtualBox ticket which confirmed the same https://www.virtualbox.org/ticket/11577
Now I have tried find the way to Sign the key and received many links and started following Red Hat link to sign Module, Never thought it would be this much easy, Only Few steps and You are done.
You will need root access or root equivalent access to follow this.
First you will have to generate keys for the module with following command
1. To make it work Properly, You will have to sign all modules of VirtualBox with generated keys. 2. Everytime you run “/sbin/rcvboxdrv setup” after following step 3, Signed Modules will be removed and You will again need to follow Step 11 and 12 , Only step 11 and 12 not from beginning. (This was not the case in Fedora 18 to 21)
Restart vboxdrv service with following command
[root@tejasbarot ~]# systemctl restart vboxdrv
[root@tejasbarot ~]# systemctl status vboxdrv
NOTE: If you find this line “Starting VirtualBox kernel modules [ OK ]”, You are done, Start launching Virtual Machines.
REPEATING ONCE AGAIN, DO NOT EXECUTE “sudo /etc/init.d/vboxdrv setup” or “/sbin/rcvboxdrv setup” otherwise you will have to follow repeat Step No 11. and 12
DISABLE MOK Validation using following command
[root@tejasbarot ~]# mokutil --disable-validation
Switch to Legacy Mode from UEFI by Disabling SecureBoot from BIOS
First of all extremely sorry for not being active as I was busy with some work, Now back to the blogging.
This article will show you how to disable rsyslog rate-limiting, But You can also use rate-limiting according to your requirement.
How to use rate limiting in rsyslog?
This article is tested with rsyslog 5.7.1 on Fedora 13. It will not work with version of rsyslog prior to 5.7.1.
In rsyslog 5.7.1 we introduced rate limiting. This is a option for the Unix Socket Input module called imuxsock. In short, this option limits the amount of messages written into logfiles by a process, if the process tries to write huge amounts of messages in a short period of time.
LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at http://donate.libreoffice.org. Money collected will be used to grow the infrastructure, and support marketing activities to increase the awareness of the project, both at global and local level.