Installing this driver destroys a already installed one
See original GitHub issue1.: Thank you for this very helpful driver!
Describe the bug Installing this driver destroys a already installed one.
To Reproduce Steps to reproduce the behavior:
- working dbus-mqtt-devices driver
- installing this driver
- reboot
- dbus-mqtt-devices driver doesn’t work anymore
Expected behavior Installing this driver should not influence other drivers.
Solution Reinstalling dbus-mqtt-devices helped
What could I find
Your installation script replaced a already existing entry in /data/rc.local
Reentering it did not help. I had to reinstall dbus-mqtt-devices
Issue Analytics
- State:
- Created a year ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Installing the Wrong Drivers - Ways to Destroy your PC
This video shows what happens if you change your hard disk driver into an SD card one. System restore can fix it, but...
Read more >Windows 10 destroyed itself. Can I get it back? Should I?
One of the important things to do after updating your operating system is to install the latest updates and drivers.
Read more >Windows keeps installing older version for Display drivers
First I'd DDU the driver in safe mode and tick disable updates in DDU options (Prevent download of drivers from "Windows update" when...
Read more >Doesn't this program "destroy" PC's? :: Driver Booster 5 for ...
By installing outdated/incorrect drivers? the idea behind this is really neat, ... ALWAYS INSTALL DRIVERS 1 BY 1, AND REBOOT AFTER EACH ONE, ......
Read more >How to Fix if Windows 10 Destroyed after Installing Updates
This method is Resetting Windows Updates, Remove Incompatible driver and then install fresh windows updates. Step 1: Reset Windows Updates.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

That’s going to work if nobody puts an exit 0 at the end of their script or runs any command which doesn’t either fork or finish immediately, but we are at the point where people have to guess what other scripts are going to do.
It’s still a very fragile system whichever way it is cut. The best approach would probably be for someone to build a standard rc.local mux system that allows custom modules to coexist and everyone to plug into that.
Hm, sadly the installation deleted my rc.local without any backup. so i lost many settings…