Packages

Description:

1) kaccounts-integration: Option to add NextCloud/OwnCloud accounts in ‘Online Accounts’ section of System Settings not appearing.

3) kdenetwork-kopete: Clicking to add an Jabber Account opens a dialog with no fields to enter information.

Additional info:
* package version(s)
kaccounts-integration 17.04.0-1
kdenetwork-kopete 17.04.0-3.hyperbola1

* config and/or log files etc.
N/A

Steps to reproduce:

Happens all the time. Both re-installing and re-booting/re-starting did not fix the problem.

Description:
Screen locking does not work in GNOME, either with keyboard shortcuts or from the menu, while using LightDM.

Additional info:
* According to this thread[1] this bug has been patched in Ubuntu. Please consider applying this patch.[2]

Steps to reproduce:
# pacman -S gnome lightdm lightdm-gtk-greeter
# rc-update add lightdm default
Reboot, log in to a GNOME session and attempt to lock screen.

[1] https://www.reddit.com/r/gnome/comments/9klvej/is_there_a_way_to_get_the_screen_to_lock_with/ [2] https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-shell/tree/debian/patches/ubuntu/lightdm-user-switching.patch

Description:
I install plasma and xorg to my Hyperbola GNU/Linux-libre in Arch-way.
However, after reboot, everything is fine except mouse curse.

I attempt to reinstall plasma-desktop and reboot. But nothing changes.

In attachment, the mouse stop at backward, however it is invisible.

Additional info:
* package version(s)
plasma-desktop == 5.9.5-1
xorg-server == 1.19.6-2.hyperbola1
sddm == 0.14.0-2.hyperbola6

* config and/or log files etc.

Steps to reproduce:

Description: Concurrent package ossp in version 1.3.2-15 has got dependencies to systemd, which is contradicting the whole distribution and the used INIT-system. Therefore my request to port this to OpenRC!

Additional info:
* package version(s) 1.3.2-15

Hello Hyperbola!

GPA gives out the following errors upon opening the app.

First:

```
The GPGME library returned an unexpected
error at confdialog.c:1459. The error was:

    Unsupported protocol

This is either an installation problem or a bug in GPA.
GPA will now try to recover from this error.
```

Second:

```
Fatal Error in GPGME library
(invoked from file options.c, line 302):

    Unsupported protocol

The application will be terminated

What can I do to overcome these errors?
```
As this issue makes gpa app completely unusable, I have set this bug report’s severity as high.

I also request the admin to set priority to high due to it’s severity.

Thank you!

Regards,
RG.

Description:
I believe the arm-unknown-linux-gnueabi-gcc package to be broken as described here.

Additional info:
* package version(s) - arm-unknown-linux-gnueabi-gcc - all versions

Steps to reproduce:
I don’t think “steps to reproduce” to be relevant in this case. My forum topic linked above already contains all the necessary info on the subject :) However, one could try compiling glibc and busybox as described here. Yes, these are instructions for debian-like systems. They have to be adapted accordingly

Description:

Additional info:
* package version(s)

$ pacman -Si gufw
Repositorio               : community
Nombre                    : gufw
Versión                   : 17.04.1-3.hyperbola1
Descripción               : Uncomplicated way to manage your GNU/Linux firewall
Arquitectura              : any
URL                       : https://gufw.org/
Licencias                 : GPL-3
Grupos                    : Nada
Provee                    : Nada
Depende de                : gtk3  polkit  python-gobject  ufw  webkit2gtk  net-tools  desktop-file-utils  gtk-update-icon-cache
Dependencias opcionales   : Nada
En conflicto con          : Nada
Remplaza a                : Nada
Tamaño de la descarga     : 886,27 KiB
Tamaño de la instalación  : 3827,00 KiB
Encargado                 : HyperBuilder <hyperbuilder@hyperbola.info>
Fecha de creación         : mar 01 oct 2019 14:35:51 -05
Validado por              : Suma MD5  Suma SHA-256  Firma

* config and/or log files etc.

==== AUTHENTICATING FOR com.ubuntu.pkexec.gufw ===
Authentication is required to run the Firewall Configuration
Authenticating as: freedom
Password: 
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.

Steps to reproduce:
- install gufw

Additional info:
* package version(s)

# pacman -Si firewalld
Repositorio               : community
Nombre                    : firewalld
Versión                   : 0.4.4.4-1.hyperbola1
Descripción               : Firewall daemon with D-Bus interface, with OpenRC support
Arquitectura              : any
URL                       : https://github.com/t-woerner/firewalld
Licencias                 : GPL2
Grupos                    : Nada
Provee                    : Nada
Depende de                : dbus-glib  dconf  ebtables  hicolor-icon-theme  ipset  iptables
                            python-slip
Dependencias opcionales   : bash-completion: bash completion
                            gtk3: firewall-config
                            libnm-glib: firewall-config and firewall-applet
                            libnotify: firewall-applet
                            python-pyqt5: firewall-applet
En conflicto con          : Nada
Remplaza a                : Nada
Tamaño de la descarga     : 532,05 KiB
Tamaño de la instalación  : 4865,00 KiB
Encargado                 : André Silva <emulatorman@hyperbola.info>
Fecha de creación         : lun 25 sep 2017 21:00:50 -05
Validado por              : Suma MD5  Suma SHA-256  Firma

* config and/or log files etc.

# tail -F /var/log/firewalld

2019-10-02 22:09:45 DEBUG1: Loading zone file ‘/usr/lib/firewalld/zones/internal.xml’
2019-10-02 22:09:45 DEBUG1: Loading zone file ‘/usr/lib/firewalld/zones/public.xml’
2019-10-02 22:09:45 DEBUG1: Loading zone file ‘/usr/lib/firewalld/zones/trusted.xml’
2019-10-02 22:09:45 DEBUG1: Loading zone file ‘/usr/lib/firewalld/zones/work.xml’
2019-10-02 22:09:45 DEBUG1: Using default zone ‘public’
2019-10-02 22:09:45 ERROR: Failed to read file “/proc/sys/net/netfilter/nf_conntrack_helper”: [Errno 2] No existe el fichero o el directorio: ‘/proc/sys/net/netfilter/nf_conntrack_helper’
2019-10-02 22:09:45 WARNING: Failed to get and parse nf_conntrack_helper setting
2019-10-02 22:09:45 FATAL ERROR: No IPv4 and IPv6 firewall.
2019-10-02 22:09:45 ERROR: Raising SystemExit in run_server

Steps to reproduce:

- Install package
- rc-service firewalld start
- firewalld –debug

Current VLC version (3.0.4-3.hyperbola1.backports1) fails to play DVB stream using a RTL2832 usb dongle.

I start the playlist like this :

vlc channels.conf

but it returns the following error :

cache_block stream error: cannot pre fill buffer

Also, it asks the user to be in “video” group to access DVB device, this was not needed before with Hyperbola 0.2.9. User being in “wheel” was enough.
Anyway, even after adding my user to video group, it still fails with “cache_block stream error: cannot pre fill buffer”

This is not an issue with my DVB adapter or driver. rtl2832 is correctly loaded. And I can play the channels.conf playlist just fine with “mpv” or “mplayer”.
Also, the channels.conf used works just fine with a more recent version of VLC on an other system (Manjaro) so something is broken with the current VLC used.

Maybe a package bump would fix the issue.

Description:
The sshguard package should have its /usr/bin/sshguard executable in /usr/sbin, has systemd service files and no OpenRC init script

Additional info:
* sshguard-2.0.0-4
* when I run `sshguard`:

# sshguard
/usr/bin/sshguard: line 87: /usr/bin/journalctl: No such file or directory

* default /etc/sshguard.conf

LOGREADER="LANG=C /usr/bin/journalctl -afb -p info -n1 -t sshd -o cat"
BLACKLIST_FILE=120:/var/db/sshguard/blacklist.db
BACKEND="/usr/lib/sshguard/sshg-fw-iptables"

(commenting the first line temporally solves the issue)

Description:

I saw errors in logs because fail2ban couldn’t find /usr/bin/sendmail, and discovered this:

[/etc/fail2ban] [0]
$ grep /usr/bin/sendmail */*
action.d/sendmail-buffered.conf:              Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail-buffered.conf:                 Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail-buffered.conf:             Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail-buffered.conf:                Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail-common.conf:              Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail-common.conf:             Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail.conf:            Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail-geoip-lines.conf:            Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail-whois.conf:            Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail-whois-ipjailmatches.conf:            Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail-whois-ipmatches.conf:            Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail-whois-lines.conf:            Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
action.d/sendmail-whois-matches.conf:            Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>

Please, also check for other binaries with wrong locations

As of now, the solution is as simple as removing this line → https://git.hyperbola.info:50100/packages/community.git/tree/fail2ban/PKGBUILD#n79

Additional info:
* fail2ban-0.9.6-2.hyperbola3

Description:

default configuration is /etc/auto.master instead of /etc/autofs/auto.master

admin→ sudo /usr/bin/automount -v -f -p /run/autofs.pid
Starting automounter version 5.1.2, master map /etc/auto.master
using kernel protocol version 5.02
lookup(file): file map /etc/auto.master missing or not readable
no mounts in table

The IDE codelite is an excellent development environment, continuously updated, has a clear vision and active support.
Would be nice to have this one within the repositories in upcoming releases, perhaps 0.5?

Description:
linphonec is unusable because a error produce a continuous log

Additional info:
linphone 3.11.1-1.hyperbola1

Steps to reproduce:
linphonec

Log:
linphonec> 2019-12-15 19:25:58:010 ortp-error-Error in connect: Network is unreachable
2019-12-15 19:26:03:012 ortp-error-Error in connect: Network is unreachable
2019-12-15 19:26:08:018 ortp-error-Error in connect: Network is unreachable
2019-12-15 19:26:13:013 ortp-error-Error in connect: Network is unreachable
2019-12-15 19:26:18:016 ortp-error-Error in connect: Network is unreachable
2019-12-15 19:26:23:014 ortp-error-Error in connect: Network is unreachable
2019-12-15 19:26:28:010 ortp-error-Error in connect: Network is unreachable
2019-12-15 19:26:33:010 ortp-error-Error in connect: Network is unreachable
2019-12-15 19:26:38:012 ortp-error-Error in connect: Network is unreachable
2019-12-15 19:26:43:015 ortp-error-Error in connect: Network is unreachable
2019-12-15 19:26:48:010 ortp-error-Error in connect: Network is unreachable
2019-12-15 19:26:53:010 ortp-error-Error in connect: Network is unreachable

The current version of the package icewm within the Hyperbola-repositories is 1.3.8. The latest version is 1.6.3!
An update would be helpful as this window-manager follows absolutely the principles of the distribution Hyperbola itself, being simple and fast.

These two options could be enabled :

Kernel hacking → [*] Filter access to /dev/mem
[*] Filter I/O access to /dev/mem

Security options → [*] Restrict unprivileged access to the kernel syslog

When using the package for wireless connections no further icon is displayed without having the package [b]network-manager-applet[/b] installed.

CVE-2020-5260 has been fixed very recently in Debian, so I thought I would apply this patch. However, I found out that security patches have not been applied for quite a while (I could account for at least 6 CVEs).

Considering that the version in Debian stretch (2.11.0) is the nearest version with security patches released by Debian and that git project oldest supported version is 2.17, I have used patches from Debian stretch to apply on 2.12.2 currently in Milky Way.

But I have the following error on check():

 |  *** prove ***
 |
 |  Test Summary Report
 |  -------------------
 |  t5570-git-daemon.sh                              (Wstat: 256 Tests: 20 Failed: 10)
 |    Failed tests:  3-7, 15-19
 |    Non-zero exit status: 1
 |  t5811-proto-disable-git.sh                       (Wstat: 256 Tests: 26 Failed: 16)
 |    Failed tests:  2-6, 9-11, 15-19, 21-23
 |    Non-zero exit status: 1
 |  Files=769, Tests=14137, 1101 wallclock secs ( 8.08 usr  1.12 sys + 144.48 cusr 63.42 csys = 217.10 CPU)
 |  Result: FAIL
 |  make[1]: *** [Makefile:45: prove] Error 1
 |  make[1]: Leaving directory '/build/git/src/git-2.12.2/t'
 |  make: *** [Makefile:2291: test] Error 2
 |  ==> ERROR: A failure occurred in check().
 |      Aborting...

This does not seem to be related to my change as the current version in Milky Way produces the same error (IOW the package currently in Milky Way is not rebuidable).

Description:
There is an issue with Christian Rebischke key, i’ve tried to delete /etc/pacman.d/gnupg/ and repopulate it but it doesn’t fix the issue.

error: ascii: signature from “Christian Rebischke (Arch Linux Security Team-Member) Chris.Rebischke@archlinux.org” is unknown trust
File /var/cache/pacman/pkg/ascii-3.15-2-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).

Steps to reproduce:

sudo pacman -S ascii

Description:

Init script is missing for this package.

I think has some systemd dependecies.

/tmp/alpm_sYmHUS/.INSTALL: line 7: systemd-sysusers: command not found
error: command failed to execute correctly

package version: varnish-5.1.2-1

Any attempt to load Nouveau in X server results in the following error:

nouveau_drv.so: undefined symbol: exaDriverAlloc

Additional info

Steps to reproduce

Users must need DjView to read any DjVu file if it isn’t present on the repository in this distro, so here’s a link about it during the pending process.

• djview: https://git.hostux.net/HarvettFox96/hyperbola-packages-extra/src/commit/028e13cd6fc8731852598646e09045a124965a6a/pending/djview/

• OS name and version: Hyperbola GNU/Linux-libre 0.4
• Kernel name and version: Linux-libre 5.10.103-gnu1-1-lts
• Package name and version: yeahwm 0.3.5-2

The title says it above.

Using both methods to launch YeahWM with SLiM and xinit doesn’t work as it keeps crashing over the segmentation fault.

$ gnome-shell
gnome-shell: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory

I opened up (and customised) the menu box, but edit and zoom control button icons are gone missing, except in toolbars.

Also, what about developer button (wrench icon)?