Saumya

Seems like a known bug.

Upgrade from 22.04 LTS to 24.04 LTS and the connection to internet is broken

In my case, I upgraded to 24.04.1. The bug still is there. The fix I do is from this place. I have to do it almost every time I open the OS.

sudo rm /etc/resolv.conf
sudo dhcpcd

Now as mentioned in the post internet is back but the icon on the taskbar is still broken. To fix this UI, this is the command.

The latest LTS release of Ubuntu, 24.04 is having a very unstable installer.

I could install it from the installer in some machines without any problem.

However, the installer simply is a UI only update. On the UX side it fails completely. Seems there is no error handling done. On simplest of things, the installer just shuts down.

On one of my laptops, I find it is very difficult to go forword with installation. Made an attempt to install the previous version of Ubuntu, which is 22.04 and it went smooth.

React Native still is and better than ever the toolchain for crossplatform application development. As usual the new version React Native toolchain keeps on changing. The documentation of the toolchain also keeps on changing(they call it evolving, not me).

Starting a new project is now done as this

npx @react-native-community/cli init MyNewReactNativeApp

For a particular version of React Native, the command is like this.

npx @react-native-community/cli init MyApp --version "0.75"

This is basically using the community cli

In package.json there is a script section. From here one can run NPM Scripts.

"scripts": {
	"one": "scriptOne.js",
	"two": "scriptTwo.js"
}

These can be run like this.

npm run one

This particular line will run scriptOne.js. This is powerful as we could take Node’s power and run any automated task for ourselves.

At first this seemed simple to me. Soon I came across cross-platform bugs. Since we are writing this in JS, it could be run anywhere Node is available. Now that could be a tricky thing. Some environments deal with certain things in a certain way. This is not a big thing if the script is written to handle those situations. Another thing is Node versions. If the script is written using certain API of a particular Node version, it is better to keep an eye on new releases of Node and update the script if there are breaking changes.

We will be talking about Windows 11 and NeoVIM. It can be seen as general Windows not specific to Windows 11, since I have done it in Windows 11, thought would mention it here in order to avoid the confusion.

On Windows machines I avoided configuring or even using NeoVIM. Thought it would be much more painful here as compared to Linux. So started using NeoVIM on WSL. Configured and ready within a couple of minutes as that is basically all Linux. Then I thought, let me try on Windows once and that would be final. If it runs fine if not better. It seemed the people at NeoVIM has made it clear that this thing is for everyone, including Windows people.