Packages

$ service php-fpm start
 * service: No such file or directory

$ pacman -Ql php-fpm | less

php-fpm /etc/
php-fpm /etc/init.d/
php-fpm /etc/init.d/php-fpm
php-fpm /etc/php/
php-fpm /etc/php/php-fpm.conf
php-fpm /etc/php/php-fpm.d/
php-fpm /etc/php/php-fpm.d/www.conf
php-fpm /usr/
php-fpm /usr/bin/
php-fpm /usr/bin/php-fpm
php-fpm /usr/lib/
php-fpm /usr/lib/tmpfiles.d/
php-fpm /usr/lib/tmpfiles.d/php-fpm.conf
php-fpm /usr/share/
php-fpm /usr/share/man/
php-fpm /usr/share/man/man8/
php-fpm /usr/share/man/man8/php-fpm.8.gz
php-fpm /usr/share/php/
php-fpm /usr/share/php/fpm/
php-fpm /usr/share/php/fpm/status.html

Possibly the problem is the removal of runscript.
runscript conflicted in [minicom] with [openrc], detailed in https://issues.hyperbola.info/index.php?do=details&task_id=122 and was removed in openrc https://git.hyperbola.info:50100/packages/core.git/tree/openrc/PKGBUILD#n137

/etc/init.d/dhcpd failed to run and use chroot by default

The MATE Session Handler lacks elogind support to handle session options from MATE since it is adapted for systemd only. There is a patch of elogind support for gnome-session [0] that could be adapted to mate-session-manager.

$ pacman -Si mate-session-manager
Repository      : community
Name            : mate-session-manager
Version         : 1.18.1-1.hyperbola1
Description     : The MATE Session Handler, without systemd support
Architecture    : x86_64
URL             : https://mate-desktop.org
Licenses        : GPL
Groups          : mate
Provides        : None
Depends On      : dbus-glib  gtk3  libsm  mate-desktop
Optional Deps   : gnome-keyring: keyring support
                  xdg-user-dirs-gtk: manage user directories
Conflicts With  : mate-session-manager-gtk3
Replaces        : mate-session-manager-gtk3
Download Size   : 284.77 KiB
Installed Size  : 2347.00 KiB
Packager        : André Silva <emulatorman@hyperbola.info>
Build Date      : Fri 08 Sep 2017 03:03:18 AM -03
Validated By    : MD5 Sum  SHA-256 Sum  Signature

gvfs uses some features from systemd-logind that can be provided by elogind. There is an implementation made from Gentoo [0] to add libelogind support.

filename:       /lib/modules/4.9.77-gnu-1-lts/extramodules/vhba.ko
license:        GPL
description:    Virtual SCSI HBA
version:        20161009
author:         Chia-I Wu
srcversion:     E5A3E6F70DFD436A6B1C8D6
depends:        scsi_mod
vermagic:       4.9.27-gnu-1-lts SMP mod_unload modversions

Can’t insert module vhba

Error :

modprobe: ERROR: could not insert ‘vhba’: Exec format error

Since latest update, many of my service do not start automatically. (I can start them manually though)
This cause multiple errors at shutdown as well.

 udev                                                                                          [  started  ]
 localmount                                                                                    [  started  ]
 dbus                                                                                          [  started  ]
 elogind                                                                                       [  started  ]
 NetworkManager                                                                                [  started  ]
 syslog-ng                                                                                     [  started  ]
 acpid                                                                                         [  started  ]
 dhcpcd                                                                                        [  started  ]
 avahi-daemon                                                                                  [  started  ]
 netmount                                                                                      [  started  ]
 lightdm                                                                                       [ starting  ]
 alsasound                                                                                     [  stopped  ]
 avahi-dnsconfd                                                                                [  stopped  ]
 cronie                                                                                        [  stopped  ]
 cupsd                                                                                         [  stopped  ]
 fuse                                                                                          [  stopped  ]
 ntpd                                                                                          [  stopped  ]
 libvirtd                                                                                      [  stopped  ]
 openrc-settingsd                                                                              [  stopped  ]
 sshd                                                                                          [  stopped  ]
 thinkfan                                                                                      [  stopped  ]
 local                                                                                         [  stopped  ]
 agetty.tty5                                                                                   [  stopped  ]
 agetty.tty3                                                                                   [  stopped  ]
 agetty.tty6                                                                                   [  stopped  ]
 agetty.tty4                                                                                   [  stopped  ]
 agetty.tty2                                                                                   [  stopped  ]
 agetty.tty1                                                                                   [  stopped  ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed/wanted
 modules-load                                                                                  [  started  ]
 lvmetad                                                                                       [  started  ]

Before dbus update, everything was working fine.

Thanks for your help

Explicit error

when executing the command:

$ gpg --receive-keys [key]

output:

gpg: WARNING: Tor is not properly configured
gpg: Failed key server reception: Denied permission

when executing the command [disable service Tor]:

$ gpg --receive-keys [key]

output:

gpg: WARNING: Tor is not running
gpg: recepción del servidor de claves fallida: Conexión rehusada

Possible solution

These are the patches from debian that may be causing the problem, we must check:

• 0016-gpg-Print-a-warning-on-Tor-problems.patch
• 0019-dirmngr-New-option-no-use-tor-and-internal-changes.patch

References:
- http://daniel.gnoutcheff.name/2017-02-05-gpg-ipv6-tor-error/

Package information:

$ pacman -Ql gnupg
gnupg /usr/
gnupg /usr/bin/
gnupg /usr/bin/addgnupghome
gnupg /usr/bin/applygnupgdefaults
gnupg /usr/bin/dirmngr
gnupg /usr/bin/dirmngr-client
gnupg /usr/bin/gpg
gnupg /usr/bin/gpg-agent
gnupg /usr/bin/gpg-connect-agent
gnupg /usr/bin/gpg2
gnupg /usr/bin/gpgconf
gnupg /usr/bin/gpgparsemail
gnupg /usr/bin/gpgscm
gnupg /usr/bin/gpgsm
gnupg /usr/bin/gpgtar
gnupg /usr/bin/gpgv
gnupg /usr/bin/gpgv2
gnupg /usr/bin/kbxutil
gnupg /usr/bin/symcryptrun
gnupg /usr/bin/watchgnupg
gnupg /usr/lib/
gnupg /usr/lib/gnupg/
gnupg /usr/lib/gnupg/dirmngr_ldap
gnupg /usr/lib/gnupg/gpg-check-pattern
gnupg /usr/lib/gnupg/gpg-preset-passphrase
gnupg /usr/lib/gnupg/gpg-protect-tool
gnupg /usr/lib/gnupg/gpg-wks-client
gnupg /usr/lib/gnupg/scdaemon
gnupg /usr/share/
gnupg /usr/share/doc/
gnupg /usr/share/doc/gnupg/
gnupg /usr/share/doc/gnupg/DCO
gnupg /usr/share/doc/gnupg/DETAILS
gnupg /usr/share/doc/gnupg/FAQ
gnupg /usr/share/doc/gnupg/HACKING
gnupg /usr/share/doc/gnupg/KEYSERVER
gnupg /usr/share/doc/gnupg/OpenPGP
gnupg /usr/share/doc/gnupg/README
gnupg /usr/share/doc/gnupg/TRANSLATE
gnupg /usr/share/doc/gnupg/examples/
gnupg /usr/share/doc/gnupg/examples/README
gnupg /usr/share/doc/gnupg/examples/debug.prf
gnupg /usr/share/doc/gnupg/examples/gpgconf.conf
gnupg /usr/share/doc/gnupg/examples/pwpattern.list
gnupg /usr/share/doc/gnupg/examples/scd-event
gnupg /usr/share/doc/gnupg/examples/trustlist.txt
gnupg /usr/share/doc/gnupg/examples/vsnfd.prf
gnupg /usr/share/gnupg/
gnupg /usr/share/gnupg/distsigkey.gpg
gnupg /usr/share/gnupg/help.be.txt
gnupg /usr/share/gnupg/help.ca.txt
gnupg /usr/share/gnupg/help.cs.txt
gnupg /usr/share/gnupg/help.da.txt
gnupg /usr/share/gnupg/help.de.txt
gnupg /usr/share/gnupg/help.el.txt
gnupg /usr/share/gnupg/help.eo.txt
gnupg /usr/share/gnupg/help.es.txt
gnupg /usr/share/gnupg/help.et.txt
gnupg /usr/share/gnupg/help.fi.txt
gnupg /usr/share/gnupg/help.fr.txt
gnupg /usr/share/gnupg/help.gl.txt
gnupg /usr/share/gnupg/help.hu.txt
gnupg /usr/share/gnupg/help.id.txt
gnupg /usr/share/gnupg/help.it.txt
gnupg /usr/share/gnupg/help.ja.txt
gnupg /usr/share/gnupg/help.nb.txt
gnupg /usr/share/gnupg/help.pl.txt
gnupg /usr/share/gnupg/help.pt.txt
gnupg /usr/share/gnupg/help.pt_BR.txt
gnupg /usr/share/gnupg/help.ro.txt
gnupg /usr/share/gnupg/help.ru.txt
gnupg /usr/share/gnupg/help.sk.txt
gnupg /usr/share/gnupg/help.sv.txt
gnupg /usr/share/gnupg/help.tr.txt
gnupg /usr/share/gnupg/help.txt
gnupg /usr/share/gnupg/help.zh_CN.txt
gnupg /usr/share/gnupg/help.zh_TW.txt
gnupg /usr/share/gnupg/sks-keyservers.netCA.pem
gnupg /usr/share/info/
gnupg /usr/share/info/gnupg.info-1.gz
gnupg /usr/share/info/gnupg.info-2.gz
gnupg /usr/share/info/gnupg.info.gz
gnupg /usr/share/locale/
gnupg /usr/share/locale/ca/
gnupg /usr/share/locale/ca/LC_MESSAGES/
gnupg /usr/share/locale/ca/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/cs/
gnupg /usr/share/locale/cs/LC_MESSAGES/
gnupg /usr/share/locale/cs/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/da/
gnupg /usr/share/locale/da/LC_MESSAGES/
gnupg /usr/share/locale/da/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/de/
gnupg /usr/share/locale/de/LC_MESSAGES/
gnupg /usr/share/locale/de/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/el/
gnupg /usr/share/locale/el/LC_MESSAGES/
gnupg /usr/share/locale/el/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/en@boldquot/
gnupg /usr/share/locale/en@boldquot/LC_MESSAGES/
gnupg /usr/share/locale/en@boldquot/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/en@quot/
gnupg /usr/share/locale/en@quot/LC_MESSAGES/
gnupg /usr/share/locale/en@quot/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/eo/
gnupg /usr/share/locale/eo/LC_MESSAGES/
gnupg /usr/share/locale/eo/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/es/
gnupg /usr/share/locale/es/LC_MESSAGES/
gnupg /usr/share/locale/es/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/et/
gnupg /usr/share/locale/et/LC_MESSAGES/
gnupg /usr/share/locale/et/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/fi/
gnupg /usr/share/locale/fi/LC_MESSAGES/
gnupg /usr/share/locale/fi/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/fr/
gnupg /usr/share/locale/fr/LC_MESSAGES/
gnupg /usr/share/locale/fr/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/gl/
gnupg /usr/share/locale/gl/LC_MESSAGES/
gnupg /usr/share/locale/gl/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/hu/
gnupg /usr/share/locale/hu/LC_MESSAGES/
gnupg /usr/share/locale/hu/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/id/
gnupg /usr/share/locale/id/LC_MESSAGES/
gnupg /usr/share/locale/id/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/it/
gnupg /usr/share/locale/it/LC_MESSAGES/
gnupg /usr/share/locale/it/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/ja/
gnupg /usr/share/locale/ja/LC_MESSAGES/
gnupg /usr/share/locale/ja/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/nb/
gnupg /usr/share/locale/nb/LC_MESSAGES/
gnupg /usr/share/locale/nb/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/pl/
gnupg /usr/share/locale/pl/LC_MESSAGES/
gnupg /usr/share/locale/pl/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/pt/
gnupg /usr/share/locale/pt/LC_MESSAGES/
gnupg /usr/share/locale/pt/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/ro/
gnupg /usr/share/locale/ro/LC_MESSAGES/
gnupg /usr/share/locale/ro/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/ru/
gnupg /usr/share/locale/ru/LC_MESSAGES/
gnupg /usr/share/locale/ru/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/sk/
gnupg /usr/share/locale/sk/LC_MESSAGES/
gnupg /usr/share/locale/sk/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/sv/
gnupg /usr/share/locale/sv/LC_MESSAGES/
gnupg /usr/share/locale/sv/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/tr/
gnupg /usr/share/locale/tr/LC_MESSAGES/
gnupg /usr/share/locale/tr/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/uk/
gnupg /usr/share/locale/uk/LC_MESSAGES/
gnupg /usr/share/locale/uk/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/zh_CN/
gnupg /usr/share/locale/zh_CN/LC_MESSAGES/
gnupg /usr/share/locale/zh_CN/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/locale/zh_TW/
gnupg /usr/share/locale/zh_TW/LC_MESSAGES/
gnupg /usr/share/locale/zh_TW/LC_MESSAGES/gnupg2.mo
gnupg /usr/share/man/
gnupg /usr/share/man/man1/
gnupg /usr/share/man/man1/dirmngr-client.1.gz
gnupg /usr/share/man/man1/gpg-agent.1.gz
gnupg /usr/share/man/man1/gpg-connect-agent.1.gz
gnupg /usr/share/man/man1/gpg-preset-passphrase.1.gz
gnupg /usr/share/man/man1/gpg-wks-client.1.gz
gnupg /usr/share/man/man1/gpg-wks-server.1.gz
gnupg /usr/share/man/man1/gpg.1.gz
gnupg /usr/share/man/man1/gpgconf.1.gz
gnupg /usr/share/man/man1/gpgparsemail.1.gz
gnupg /usr/share/man/man1/gpgsm.1.gz
gnupg /usr/share/man/man1/gpgv.1.gz
gnupg /usr/share/man/man1/scdaemon.1.gz
gnupg /usr/share/man/man1/symcryptrun.1.gz
gnupg /usr/share/man/man1/watchgnupg.1.gz
gnupg /usr/share/man/man7/
gnupg /usr/share/man/man7/gnupg.7.gz
gnupg /usr/share/man/man8/
gnupg /usr/share/man/man8/addgnupghome.8.gz
gnupg /usr/share/man/man8/applygnupgdefaults.8.gz
gnupg /usr/share/man/man8/dirmngr.8.gz

### Some context ###

I use hdajackretask on my G41M-ES2L motherboard (Libreboot)

Alsamixer doesn’t offer automute feature so every time I plug my headphones, the sound is playing by my speakers.
So to work around this, I use hdajackretask from alsa-tools package.

It allows to install a boot override to solve the issue.

Yesterday, I reinstalled Hyperbola on my system and the boot override because of missing /lib/firmware directory. (Although it was present before, something changed ?)

The error message was (I translate)

/mv: can't move '/tmp/hda-jack-retask-VH3KIZ/hda-jack-retask.fw' to /lib/firmware/hda-jack-retask.fw' No file or folder of this type

So I created a folder “firmware” in /lib/
and copied hda-jack-retask.fw in it.

Then I rebooted, 100% working.

I don’t know if the fix should apply to the PKGBUILD of alsa-tools (to create a /lib/firmware directory) or something else ?

Message error:

Cowardly refusing to concatenate a logfile into self.

Please change rc_log_path to something other than /var/log/rc.log to get rid of this message

Warning init:

 * Setting hardware clock using the system clock [UTC] ... 
hwclock: Cannot access the Hardware Clock via any known method. 
hwclock: Use the --debug option to see the details of our search for an access method. 
 * Failed to sync clocks 
 [ !! ] 
 * ERROR: hwclock failed to stop

Restart init:

[root@hyperbola heckyel]# /etc/init.d/hwclock restart 
 * WARNING: you are stopping a boot service
 * WARNING: you are stopping a boot service
 * Stopping rsyslog ...                                                                                                                                                                    [ ok ]
 * Setting hardware clock using the system clock [UTC] ...
hwclock: Cannot access the Hardware Clock via any known method. 
hwclock: Use the --debug option to see the details of our search for an access method. 
 * Failed to sync clocks                                                                                                                                                                   [ !! ]
 * ERROR: hwclock failed to stop

References:

• https://serverfault.com/questions/851996/hwclock-cannot-access-the-hardware-clock-via-any-known-method/852008

Description:
The light-locker package returns error while tries load shared library libsystemd.so.0.

Additional info:
* package version(s): light-locker-1.6.0-3

Steps to reproduce:

1. Install the package:

  $ sudo pacman -S light-locker
  

1. Run it:

  $ light-locker
  

1. Then, you get the following message:

  light-locker: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory
  

Firetools sandbox list shows nothing whenever I use icedove-hardened or iceweasel-uxp-hardened. or vlc, or anything at this point.

Firejail still works, but the sandbox list on the applet, shows nothing.

I don’t really know why though. may need to updated.

dunno. I can wait on this one if need be, but it is kind of annoying.

Neither iceweasel-uxp, nor icedove nor hexchat, nor vlc show up as being sandboxed in sandbox list.

I also check and see that firejail isn’t running also.

I think it might be wise to upgrade firetools. and also to make sure hardened packages such as icedove-hardened/iceweasel-uxp-hardened work properly.

This should be considered a high level priority due to firetools being a security application. Wouldn’t you say?

I get this error when trying to run it:

$ utox
utox: error while loading shared libraries: libtoxencryptsave.so.1: cannot open shared object file: No such file or directory

Description:
Since the update to 0.3.9 (or the update of girara to 0.2.9), zathura-pdf-poppler returns the following error:

error: Could not load plugin '/usr/lib/zathura/ps.so' (libgirara-gtk3.so.2: cannot open shared object file: No such file or directory).

Description:

• Segmentation fault after start by terminal emulator but elinks does not crash in console. After that, it prints characters when mouse buttons pressed so it can not copy its output.

Additional info:
* package version(s)

• links 2.14-2
• elinks 0.13-18

* config and/or log files etc.

• gdb output for links 2.16:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff4295e43 in strchrnul () from /usr/lib/libc.so.6

• gdb output for elinks 0.13-18:

[New Thread 0x7ffff4dfb700 (LWP 8393)]
Thread 1 "elinks" received signal SIGSEGV, Segmentation fault.
0x00007ffff5fa3e43 in strchrnul () from /usr/lib/libc.so.6

Steps to reproduce:

• Run links and elinks by terminal emulator

Description:

• The filesystem package contains systemd files (/etc/profile.d/locale.sh and /usr/share/factory/) and references in /usr/share/man/man7/hyperbola.7.gz

Additional info:
* package version(s)
* config and/or log files etc.

• Proposal patch to fix the Hyperbola basic configuration man page:

diff --git hyperbola.7.txt hyperbola.7.txt.new
index 842e532..927cf6a 100644
--- hyperbola.7.txt
+++ hyperbola.7.txt.new
@@ -24,14 +24,12 @@ To view available services, use 'rc-status --all'.
 
 HOSTNAME[[H]]
 -------------
-The hostname of the machine can be set using 'hostnamectl set-hostname <hostname>'.
+The hostname of the machine can be set using 'hostname <hostname>' or 'sysctl -w kernel.hostname=<hostname>'.
 It will then be written to /etc/hostname.
 
 LOCALIZATION[[L]]
 -----------------
 Various locales may be enabled in /etc/locale.gen and are generated by 'locale-gen'.
-The system-wide locale to be used can be configured in /etc/locale.conf.
-These settings can be overridden on a per-user basis by keeping a user-specific locale.conf in $HOME/.config/locale.conf.
 The user-specific file will take precedence if it exists.
 
 VIRTUAL CONSOLE[[V]]
@@ -72,15 +70,16 @@ Syslinux is configured in /boot/syslinux/syslinux.cfg.
 MODULES[[M]]
 ------------
 Most modules should be loaded on-demand.
-Modules to be unconditionally loaded at boot can be specified in /etc/modules-load.d/,
+Modules to be unconditionally loaded at boot can be specified in /etc/conf.d/modules,
 and modules to be blacklisted from automatically loading can be configured in /etc/modprobe.d/.
 
 SEE ALSO
 --------
 
-*hostname*(5), *locale.conf*(5), *timezone*(3), *hwclock*(8),
-*fstab*(5), *crypttab*(5), *mkinitcpio*(8), *pacman*(8), *pacman.conf*(5),
-*grub-mkconfig*(8), *syslinux*(1), *modules-load.d*(5), *modprobe.d*(5)
+*hostname*(5), *timezone*(3), *hwclock*(8),
+*fstab*(5), *cryptsetup*(8), *mkinitcpio*(8), *pacman*(8), *pacman.conf*(5),
+*grub-mkconfig*(8), *syslinux*(1), *modprobe.d*(5),
+*openrc*(8), *rc-service*(8), *rc-status*(8), *rc-update*(8)
 
 AUTHORS
 -------

Steps to reproduce:

* Run:

~ man hyperbola

Here is the terminal output:

$ electrum
Error: No module named ‘aiorpcx’. Try ‘sudo python3 -m pip install <module-name>

I think a newer python version (e.g. 3.7) might be needed in order to get it to work as well as even after installing missing modules via pip locally the package does not run.

gufw 17.04.1-3

Impossible to start application, error message :

FileNotFoundError: [Errno 2] Aucun fichier ou dossier de ce type: '/usr/sbin/ufw': '/usr/sbin/ufw'

Description:
Postfix is a mess, first it failed to start (running ‘postfix start’) with the following:

  postfix: fatal: chdir(/usr/lib/postfix/bin): No such file or directory

Then, to solve this, I symlinked /usr/libexec/postfix to /usr/lib/postfix/bin, because there were the binaries, but then it came with the following:

  # postfix start
  /usr/lib/postfix/bin/postfix-script: line 89: /usr/bin/postconf: No such file or directory
  /usr/lib/postfix/bin/postfix-script: line 90: /usr/bin/postlog: No such file or directory

Because all the post* bins where now in /usr/sbin, so I symlinked them to /usr/bin, and it could finally run, but with many warnings

  # postfix start
  postfix/postfix-script: warning: symlink leaves directory: /usr/lib/postfix/./bin
  postfix/postfix-script: warning: not owned by group postdrop: /usr/bin/postqueue
  postfix/postfix-script: warning: not owned by group postdrop: /usr/bin/postdrop
  postfix/postfix-script: warning: not set-gid or not owner+group+world executable: /usr/bin/postqueue
  postfix/postfix-script: warning: not set-gid or not owner+group+world executable: /usr/bin/postdrop
  postfix/postfix-script: starting the Postfix mail system

Additional info:
* postfix 3.2.2-1.hyperbola6

Description: Configuration file “syslinux.cfg” under /boot/syslinux/ has to be adjusted. Problem with kernel-images loaded and the concurrent booting device is per default configured to /dev/sda3. Kernel-images are named as “linux-libre” not “linux-libre-lts”.

There are issues with the current sndio-package as it seems not possible to get this to work with ALSA.

Description:

Wireless connection does not work

Additional info:
* package version(s)

- wpa_supplicant 2:2.9-1
- libressl 3.2.2-1

* config and/or log files etc.

Successfully initialized wpa_supplicant
OpenSSL: Failed to set cipher string 'DEFAULT@SECLEVEL=1'
SSL: Failed to initialize TLS context.
Failed to initialize EAPOL state machines.
nl80211: deinit ifname=wlp0s18f2u1 disabled_11b_rates=0

Steps to reproduce:

$ wpa_supplicant -B -i device-name -c <(wpa_passphrase “ssid” “psk”)

/sbin/openrc-run: bad interpreter: No such file or directory

I get this error whenever I try to start dhcpcd with sv /etc/runit/

And for sndiod I get this doing the same guide,

warning: sndiod: unable to open supervise/ok: file does not exist

Although rather ironically, If I type sndiod or dhcpcd into root, it works just fine.

Maybe its an FHS issue or possibly, I am screwing up? I am not sure. Feedback is welcome.

This is what I did:

=⇒ Add a service:

ln -s /etc/sv/<service> /var/service
==> Start/stop/restart a service:
sv <start/stop/restart> <service>

more or less, I used this guide.

Require package: android-udev

* Add to /etc/udev/rules.d/51-android.rules

GROUP="uucp"

* Add the user to the group uucp

gpasswd -a username uucp

* Reboot

Package Information

$ pacman -Ql android-udev
android-udev /usr/
android-udev /usr/lib/
android-udev /usr/lib/udev/
android-udev /usr/lib/udev/rules.d/
android-udev /usr/lib/udev/rules.d/51-android.rules