WiFi update issue

[meanruse]

git clone https://aur.archlinux.org/linux-wifi-hotspot.git
cd linux-wifi-hotspot
edit the PKGBUILD like this:

# Maintainer: Mark Wagie <mark dot wagie at proton dot me>
# Contributor: Dimitris Kiziridis <ragouel at outlook dot com>
pkgname=linux-wifi-hotspot
pkgver=4.7.1
pkgrel=1
pkgdesc="Feature-rich wifi hotspot creator"
arch=('x86_64' 'aarch64')
url="https://github.com/lakinduakash/linux-wifi-hotspot"
license=('BSD')
depends=('gtk3' 'hostapd' 'iproute2' 'iw' 'procps-ng' 'qrencode')
optdepends=("dnsmasq: For 'NATed' or 'None' Internet sharing method"
            "iptables: For 'NATed' or 'None' Internet sharing method"
            'haveged: For random MAC generation'
            'wireless_tools: if iw cannot recognize your adapter')
provides=('wihotspot' 'create_ap')
conflicts=('wihotspot' 'create_ap')
backup=('etc/create_ap.conf')
install="$pkgname.install"
source=("git+https://github.com/lakinduakash/linux-wifi-hotspot.git")
sha256sums=('SKIP')

build() {
  cd "$pkgname"
  make
}

package() {
  cd "$pkgname"
  make DESTDIR="$pkgdir" install

  install -Dm644 LICENSE -t "$pkgdir/usr/share/licenses/$pkgname/"
}

(only differences are source=(...), sha256sums=(...), cd "$pkgname")

then makepkg -i

no idea if it solves any problem but it builds successfully in a few seconds

[Colin]

@filo

If you downgraded, you shouldn`t update, or at least you should put iw in IgnorePkg in /etc/pacman.conf.

I had a thought a few minutes ago and it probably explains things. When I downgraded iw it asked in the terminal if I wanted to IgnorePkg, and I typed ‘y’.

When you asked the above question I simply replied that I’d done as you suggested, but I actually hadn’t.

Just to be thorough I decided to dig out /etc/pacman.conf and see if it had been updated.

Well, I’ve looked and i’ve looked, and just to make sure I’ve looked again, but I am unable to find the etc directory or pacman.conf. In fact, there are a load of missing directories and I’m wondering id they disappeared when I gave my laptop a big clear out a couple of months ago.

I know these directories were there 6 months ago, now they are AWOL.

It seems I’ve found the problem.

@meanruse

edit the PKGBUILD like this:

Many thanks for the guide but I won’t be needing it, my laptop is in need of complete update.

[tbg]

@Colin

I am unable to find the etc directory or pacman.conf. In fact, there are a load of missing directories

I’m not familiar with Gnome’s file manager, but be sure the option to display hidden directories/files is enabled.

[Colin]

Yep, it’s enabled.

[tbg]

Post:

ls /etc

[Colin]

I ran the terminal command and it showed /etc does exist, but it can’t be found with Nautilus even with no files hidden.

If nothing else it shows that my OS is due for a refresh.

[BluishHumility]

You can fix your issue in the terminal:

micro /etc/pacman.conf

Look for a line near the top like this:

IgnorePkg = iw

Delete the whole line, then save and exit with Ctrl+Q.

Probably the file manager cannot find /etc because you are lower down in the directory tree.

---

Edit just to clarify what I mean by that:

When you open your file explorer, usually it opens to your home directory and you can see the folders inside of it, like this:

Colin
├── stuff_1
├── stuff_2
└── stuff_3

From here, when you search for something in the file manager, it is going to look through all that stuff, and anything inside that stuff, but it isn’t going to look backward, above where the file explorer is open. You cannot find /etc/, because it is back closer to / (root).

If you back up to root, this is what that (roughly) looks like:

/
├── boot
├── dev
├── etc
│  └── pacman.conf
├── home
│  └── Colin
│     ├── stuff_1
│     ├── stuff_2
│     └── stuff_3
├── mnt
├── opt
├── proc
├── root
├── run
├── share
├── srv
├── sys
├── tmp
├── usr
└── var

If you want to search for files under / with your file manager, you first will need to navigate “up” in the directory tree and start the search at or closer to /.

Some file managers also need to be run a special way to be able to interact with root-owned files (like stuff in /etc). In my opinion, if you need to do some maintenance on any of the “root” files (i.e. anything “above” your home directory) it’s generally easier if you just do it from the terminal.

All that to say: probably you do not need to reinstall the OS. You are welcome to if you would like of course, but most likely searching for files from the file manager will work the same way on the fresh install.

[Colin]

Many thanks for all of the words of wisdom given to me in this thread. Unfortunately my laptop became increasingly problematic, so it has had a reinstall of Garuda Gnome. This has fixed the above problem along with a couple of others.