Packages

Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .

Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .

Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .

Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .

Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .

Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .

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

Multiple vulnerabilities have been located in Irssi.

Access remote: yes

References links:

• https://irssi.org/security/irssi_sa_2018_02.txt

This morning while I was working on my X200, I noticed that my CPU was kept 100% busy for a long time by some process which was obvioulsy eating up the battery life. The culprit was pacman-key, triggered by logrotate.

To stop this, I did ‘chmod -x /etc/cron.daily/pacman-key’ and I rebooted.

Later on, it was impossible to install a new package as it was impossible to get over the step marked as “checking keys in keyring...”

So I tried to do again ‘pacman-key –refresh-keys’: the overall process took more than an hour—behind a fast and robust internet connection. I finally got three lines, saying that about 1,000 keys were updated but I never got the prompt back. So I hit Ctrl-C.

At the time of writing, I am still trying to refresh the keys—a quite desperate attempt, if I may say so.

Although I tagged this report as a “Feature request”, it is in my opinion of quite some importance. I understand very well the absolute necessity to always have the keys updated, but in this particular case, with so many keys and so frequent updates, I begin to wonder if losses are not beginning to prevail over benefits.

Unless I am doing something wrong or missing something I should do?

Any help would be strongly appreciated.

Robert

Python 2.7.14 is vulnerable to a Heap-Buffer-Overflow as well as a Heap-Use-After-Free. Python versions prior to 2.7.14 may also be vulnerable and it appears that Python 2.7.17 and prior may also be vulnerable however this has not been confirmed. The vulnerability lies when multiply threads are handling large amounts of data. In both cases there is essentially a race condition that occurs. For the Heap-Buffer-Overflow, Thread 2 is creating the size for a buffer, but Thread1 is already writing to the buffer without knowing how much to write. So when a large amount of data is being processed, it is very easy to cause memory corruption using a Heap-Buffer-Overflow. As for the Use-After-Free, Thread3→Malloc→Thread1→Free’s→Thread2-Re-uses-Free’d Memory. The PSRT has stated that this is not a security vulnerability due to the fact that the attacker must be able to run code, however in some situations, such as function as a service, this vulnerability can potentially be used by an attacker to violate a trust boundary, as such the DWF feels this issue deserves a CVE.

https://security-tracker.debian.org/tracker/CVE-2018-1000030

Geth 1.6.x contains possible denial of service attacks “DoS Attack”, however it has been solved in 1.7.2 [0] instead. Since 1.6.x needs many modifications spread across multiple files of the code and it is inefficient to be backported, the newer version (eg. 1.7.x) could replace the current version package as exception, but repackaged with the appropriate suffix “-backports”.

We seem to have a very old version of xscreensaver... Could you possibly update it?

this may be a security issue/privacy issue.

### 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 ?

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.

Description:

Hi guys, there have been minor changes in firetools GUI, we have also published iceweasel-uxp. Given this case, here I publish the relevant updates of the files.

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:

• replace deprecated Python 2 to Tauthon for Canis Major

Additional info:

• python 2.7.14-2.hyperbola1
• Python 2.7 is the end of the Python 2 line of development. [0]
• There never will be an official Python 2.8 release.

Steps to reproduce:

• Broken python2 packages.

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

Octopi 0.9.0 is uploading system logs to ptpb.pw without confirmation through :

Tools
→ SysInfo → ptpb.pw

I think it should be either disabled or add at least a patch to ask for a confirmation.
An other way could be to patch this :

src/globals.cpp
240: * Generates SysInfo file and paste it to ptpb site
255:  QString ptpb = UnixCommand::getCommandOutput("curl -F c=@- https://ptpb.pw/?u=1", tempFile->fileName());
256:  return ptpb;

to :

src/globals.cpp
240: * Generates SysInfo file and paste it to ptpb site
255:  QString ptpb = UnixCommand::getCommandOutput("curl -F c=@- **https://ptpb.pw/", tempFile->fileName());
256:  return ptpb;

This way, you can at least ask for log deletion with the help of log uuid as explained here : https://ptpb.pw/#id10

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