The officially official Devuan Forum!

You are not logged in.

#1 Re: Hardware & System Configuration » VBox virtual machine error in dmesg » 2021-11-22 20:01:28

Altoid wrote:

Have you tried the latest one from the virtual box repository or was that the one that locked up?

No, not yet. I am reluctant to do so since I don't have much hope that it will work, and since what I have now is working, I really don't want to mess with it. I probably won't try it until after I upgrade to Chimaera.

#2 Re: Hardware & System Configuration » VBox virtual machine error in dmesg » 2021-11-22 01:43:22

My experience has been that VirtualBox 6.1 is messed up and doesn't work right on Beowulf. I had VMs completely lock up, multiple times. The latest version that has been working reliably for me is 6.1.22 r144080 (Qt5.6.1). And in case it matters, I am also using a kernel (and headers) from backports (on the host system). Hopefully this problem will disappear when I upgrade to Chimaera.

Just thought I'd pass along this information in case it's helpful.

#3 Re: Other Issues » [SOLVED] ungoogled-chromium, Iridium, or LibreWolf, please » 2021-11-05 00:16:53

Head_on_a_Stick wrote:

Debian does not supply Chrome, and they never will. But I do agree that the chomium package in the repositories is in a pretty poor state. Google don't provide an LTS version (unlike Mozilla) and Debian just can't keep up with the steady stream of vulnerabilities:

https://security-tracker.debian.org/tra … e/chromium

So the chromium package is outdated and riddled with potential security holes. Not good.

When I want a Chromium-based web browser, I install Vivaldi:

https://vivaldi.com/


The first time I installed it, the UI was kind of weird, and it wasn't long before I uninstalled it. However, I gave Vivaldi a second chance later on, and they had clearly improved it a lot.

#4 Re: Other Issues » [SOLVED] ungoogled-chromium, Iridium, or LibreWolf, please » 2021-11-02 22:07:49

I believe that MX Linux has Iridium (package name: iridium-browser). I no longer have any packages from MX Linux installed, but I did in the past. The tricky part was setting up the apt-pinning so that only the packages I wanted from MX Linux were installed, and nothing else.

#5 Re: Installation » Status of lilo » 2021-10-24 19:56:31

Head_on_a_Stick wrote:

If a package is marked obsolete then it has already been removed from the repositories[1].

That's a pity, because I have run into cases where GRUB did not work, or refused to install, but LILO installed and worked just fine. I'd rather use GRUB, but it's nice to have an alternative to fall back on when needed.

Note: It appears that LILO is still in Sid.

https://packages.debian.org/sid/lilo

#6 Re: Installation » When did Legacy BIOS cease to exist? » 2021-09-30 10:24:57

PedroReina wrote:

Agreed. But, how could us know if a motherboard is compatible or not? I dig in the technical specifications of some of them I cannot find if I can disable Secure Boot.

Here's a start:

https://coreboot.org/status/board-status.html
https://www.mail-archive.com/coreboot@c … 38710.html

I wish I had some better suggestions for you, but I am just beginning to research this topic.

#7 Re: Installation » When did Legacy BIOS cease to exist? » 2021-09-29 06:37:03

In the future, I am going to use Libreboot or coreboot as much as possible. If a computer or motherboard isn't compatible with either of those, I simply won't buy it.

#8 Re: Desktop and Multimedia » Wicd in Chimaera (It's not, but...) » 2021-08-30 10:01:50

NetworkManager works fine, and I prefer it over wicd because it has plugins that make setting up and using a VPN fairly easy.

Based on the packages I have installed, I believe that this is the way I installed it:

aptitude install network-manager-gnome network-manager-openvpn-gnome

I only mention this because, based on a tutorial I saw that mentions replacing NetworkManager with wicd, it appears that some people believe that NetworkManager doesn't work in Devuan. That is not the case. Although I'm not certain about Chimaera, because I haven't used it, NetworkManager definitely works fine in Refracta/Beowulf.

Phil

#9 Re: Installation » Minimal KDE install in Beowulf » 2021-07-02 00:46:16

I would use a slightly different approach:

# aptitude install -R kde-plasma-desktop plasma-nm kwin-x11 sddm xserver-xorg 2>&1 | tee KDE-desktop-installation-log.txt

This installs KDE without recommended packages. That's why I save a log of the installation. After the installation, I would open the log file and look to see which recommended packages weren't installed because I may want to install some of them.

Disclaimer: I haven't actually tried this because I don't use KDE anymore. However, this is the general approach I would use to install any desktop environment, and I have used it to install Xfce.

#10 Re: Installation » low memory installation » 2021-05-20 01:33:29

I would use a window manager like fluxbox, IceWM, or JWM. Up until 2013, I used Debian with IceWM on a 300 MHz Pentium II laptop with 256 MB of RAM. It was slow (the web browser, mainly), but usable.

For the web browser I would use SeaMonkey along with NoScript "Classic" (version 5.1.x). I would also disable the ChatZilla and Lightning extensions if you aren't going to use them. Using NoScript may seem annoying and inconvenient at first, but it really helps speed up web browsing by preventing a lot of unnecessary JavaScript from running. Some websites are loaded up with so much third-party JavaScript it's ridiculous.

The best way to install SeaMonkey is to use the Ubuntuzilla repository. Despite the name, the packages are compatible with Debian and Debian derivatives.

#11 Re: Other Issues » [SOLVED] Security update delays (again) » 2021-05-16 00:11:30

I received this notification more than 48 hours ago:

- -------------------------------------------------------------------------
Debian Security Advisory DSA-4915-1                   security@debian.org
https://www.debian.org/security/                       Moritz Muehlenhoff
May 13, 2021                          https://www.debian.org/security/faq
- -------------------------------------------------------------------------

Package        : postgresql-11
CVE ID         : CVE-2021-32027 CVE-2021-32028 CVE-2021-32029

Multiple security issues have been discovered in the PostgreSQL database
system, which could result in the execution of arbitrary code or
disclosure of memory content.

For the stable distribution (buster), these problems have been fixed in
version 11.12-0+deb10u1.

We recommend that you upgrade your postgresql-11 packages.

For the detailed security status of postgresql-11 please refer to
its security tracker page at:
https://security-tracker.debian.org/tra … tgresql-11

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/

Mailing list: debian-security-announce@lists.debian.org


This does not look right:

$ apt policy postgresql-11
postgresql-11:
  Installed: (none)
  Candidate: 11.11-0+deb10u1
  Version table:
     11.11-0+deb10u1 500
        500 http://deb.devuan.org/merged beowulf/main amd64 Packages
     11.7-0+deb10u1 500
        500 http://deb.devuan.org/merged beowulf-security/main amd64 Packages

#12 Re: Other Issues » [SOLVED] Security update delays (again) » 2021-05-10 17:09:22

It finally came through some time earlier today.

$ apt policy exim4
exim4:
  Installed: 4.92-8+deb10u5
  Candidate: 4.92-8+deb10u6
  Version table:
     4.92-8+deb10u6 500
        500 http://deb.devuan.org/merged beowulf-security/main amd64 Packages
 *** 4.92-8+deb10u5 500
        500 http://deb.devuan.org/merged beowulf/main amd64 Packages
        100 /var/lib/dpkg/status

#13 Re: Other Issues » [SOLVED] Security update delays (again) » 2021-05-09 19:06:52

In case it helps, this is the last security update that came through in a timely manner:

- -------------------------------------------------------------------------
Debian Security Advisory DSA-4911-1                   security@debian.org
https://www.debian.org/security/                          Michael Gilbert
May 03, 2021                          https://www.debian.org/security/faq
- -------------------------------------------------------------------------

Package        : chromium
CVE ID         : CVE-2021-21227 CVE-2021-21228 CVE-2021-21229 CVE-2021-21230
                 CVE-2021-21231 CVE-2021-21232 CVE-2021-21233

Several vulnerabilities have been discovered in the chromium web browser.

CVE-2021-21227

    Gengming Liu discovered a data validation issue in the v8 javascript
    library.

CVE-2021-21228

    Rob Wu discovered a policy enforcement error.

CVE-2021-21229

    Mohit Raj discovered a user interface error in the file downloader.

CVE-2021-21230

    Manfred Paul discovered use of an incorrect type.

CVE-2021-21231

    Sergei Glazunov discovered a data validation issue in the v8 javascript
    library.

CVE-2021-21232

    Abdulrahman Alqabandi discovered a use-after-free issue in the developer
    tools.

CVE-2021-21233

    Omair discovered a buffer overflow issue in the ANGLE library.

For the stable distribution (buster), these problems have been fixed in
version 90.0.4430.93-1~deb10u1.

We recommend that you upgrade your chromium packages.

For the detailed security status of chromium please refer to
its security tracker page at:
https://security-tracker.debian.org/tracker/chromium

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/

Mailing list: debian-security-announce@lists.debian.org

From aptitude's log file:

Aptitude 0.8.11: log report
Tue, May  4 2021 10:27:13 -0400

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 3 packages, and remove 0 packages.
4096 B of disk space will be used
========================================
[UPGRADE] chromium:amd64 90.0.4430.85-1~deb10u1 -> 90.0.4430.93-1~deb10u1
[UPGRADE] chromium-common:amd64 90.0.4430.85-1~deb10u1 -> 90.0.4430.93-1~deb10u1
[UPGRADE] chromium-sandbox:amd64 90.0.4430.85-1~deb10u1 -> 90.0.4430.93-1~deb10u1
========================================

Log complete.

#14 Re: Other Issues » [SOLVED] Security update delays (again) » 2021-05-08 14:04:45

It has now been over 96 hours, and there is still no sign of the update.

$ apt policy exim4
exim4:
  Installed: 4.92-8+deb10u5
  Candidate: 4.92-8+deb10u5
  Version table:
 *** 4.92-8+deb10u5 500
        500 http://deb.devuan.org/merged beowulf/main amd64 Packages
        100 /var/lib/dpkg/status
     4.92-8+deb10u4 500
        500 http://deb.devuan.org/merged beowulf-security/main amd64 Packages

By the way, in case it matters, I am using Refracta based on Devuan Beowulf. I forgot to mention that in my original post.

#15 Other Issues » [SOLVED] Security update delays (again) » 2021-05-05 18:22:07

pcalvert
Replies: 8

I received this notification more than 24 hours ago:

- -------------------------------------------------------------------------
Debian Security Advisory DSA-4912-1                   security@debian.org
https://www.debian.org/security/                     Salvatore Bonaccorso
May 04, 2021                          https://www.debian.org/security/faq
- -------------------------------------------------------------------------

Package        : exim4
CVE ID         : CVE-2020-28007 CVE-2020-28008 CVE-2020-28009 CVE-2020-28010
                 CVE-2020-28011 CVE-2020-28012 CVE-2020-28013 CVE-2020-28014
                 CVE-2020-28015 CVE-2020-28017 CVE-2020-28019 CVE-2020-28021
                 CVE-2020-28022 CVE-2020-28023 CVE-2020-28024 CVE-2020-28025
                 CVE-2020-28026

The Qualys Research Labs reported several vulnerabilities in Exim, a
mail transport agent, which could result in local privilege escalation
and remote code execution.

Details can be found in the Qualys advisory at
https://www.qualys.com/2021/05/04/21nails/21nails.txt

For the stable distribution (buster), these problems have been fixed in
version 4.92-8+deb10u6.

We recommend that you upgrade your exim4 packages.

For the detailed security status of exim4 please refer to its security
tracker page at:
https://security-tracker.debian.org/tracker/exim4

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/

Reference:
https://www.debian.org/security/2021/dsa-4912


I've run apt update multiple times since then, and it hasn't shown up yet.

$ apt policy exim4
exim4:
  Installed: 4.92-8+deb10u5
  Candidate: 4.92-8+deb10u5
  Version table:
 *** 4.92-8+deb10u5 500
        500 http://deb.devuan.org/merged beowulf/main amd64 Packages
        100 /var/lib/dpkg/status
     4.92-8+deb10u4 500
        500 http://deb.devuan.org/merged beowulf-security/main amd64 Packages

Although I could be mistaken, this does not seem like normal behavior to me.

#16 Re: Hardware & System Configuration » Firewall on laptop with Chimaera » 2021-05-02 23:15:31

I like FireHOL. It uses a simple, human-readable configuration file.

Package name: firehol

More info:
https://firehol.org/
https://packages.debian.org/stable/firehol

For a laptop, the default configuration would probably be sufficient.

Phil

#17 Re: Devuan Derivatives » Issues installing VirtualBox on Refracta » 2021-03-24 15:13:36

fsmithred wrote:

I don't have any ideas for the usb. Yes I do. Not a fix; just a workaround. Someone I know used shared folders with a usb mounted on the host system.

Good idea. That might help some people. Unfortunately, that won't work for a printer or scanner.

Since version 5.2 worked just fine on Devuan ASCII, I figured I would go back to using that version even though it's no longer supported. Imagine my surprise when I encountered the same error messages when I tried to install version 5.2 on Beowulf-based Refracta.

This was my final attempt to get VirtualBox working:

$ wget https://download.virtualbox.org/virtualbox/6.1.18/VirtualBox-6.1.18-142142-Linux_amd64.run
$ wget https://www.virtualbox.org/download/hashes/6.1.18/SHA256SUMS
$ sha256sum VirtualBox-6.1.18-142142-Linux_amd64.run
[Then check to make sure that the sha256sum value is correct.]

$ su
[Enter root password.]

# chmod u+x VirtualBox-6.1.18-142142-Linux_amd64.run
# ./VirtualBox-6.1.18-142142-Linux_amd64.run install

I was quite surprised when those same error messages appeared again.


This is what I did to try to repair (complete) the installation:

# update-rc.d vboxdrv defaults
# rcvboxdrv setup

I then tested USB passthrough to see if it was working, and it was not. At this point I almost gave up. In fact, I did a minimal installation of QEMU and started researching the different utilities and GUI tools that are available for QEMU.

I then had a hunch that I should try rebooting the system. I didn't think it would help, but I went ahead and did it anyway. That worked -- USB passthrough is now working.

#18 Devuan Derivatives » Issues installing VirtualBox on Refracta » 2021-03-19 21:00:01

pcalvert
Replies: 11

I ran into some problems when installing VirtualBox 6.1.18 on Beowulf-based Refracta.

Here's the relevant info:

$ cat /etc/apt/sources.list.d/virtualbox.list
deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian buster contrib
# aptitude install virtualbox-6.1 -r
The following NEW packages will be installed:
  libqt5opengl5{a} libqt5printsupport5{a} libsdl-ttf2.0-0{a} virtualbox-6.1 
0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/88.7 MB of archives. After unpacking 215 MB will be used.
Do you want to continue? [Y/n/?] y
Preconfiguring packages ...              
Selecting previously unselected package libqt5opengl5:amd64.
(Reading database ... 158142 files and directories currently installed.)
Preparing to unpack .../libqt5opengl5_5.11.3+dfsg1-1+deb10u4_amd64.deb ...
Unpacking libqt5opengl5:amd64 (5.11.3+dfsg1-1+deb10u4) ...
Selecting previously unselected package libqt5printsupport5:amd64.
Preparing to unpack .../libqt5printsupport5_5.11.3+dfsg1-1+deb10u4_amd64.deb ...
Unpacking libqt5printsupport5:amd64 (5.11.3+dfsg1-1+deb10u4) ...
Preparing to unpack .../virtualbox-6.1_6.1.18-142142~Debian~buster_amd64.deb ...
Unpacking virtualbox-6.1 (6.1.18-142142~Debian~buster) ...
Selecting previously unselected package libsdl-ttf2.0-0:amd64.
Preparing to unpack .../libsdl-ttf2.0-0_2.0.11-6_amd64.deb ...
Unpacking libsdl-ttf2.0-0:amd64 (2.0.11-6) ...
Setting up libqt5printsupport5:amd64 (5.11.3+dfsg1-1+deb10u4) ...
Setting up libqt5opengl5:amd64 (5.11.3+dfsg1-1+deb10u4) ...
Setting up libsdl-ttf2.0-0:amd64 (2.0.11-6) ...
Setting up virtualbox-6.1 (6.1.18-142142~Debian~buster) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
insserv: FATAL: service dbus is missed in the runlevels S to use service bluetooth
insserv: exiting now!
insserv: FATAL: service vboxdrv has to be enabled to use service vboxballoonctrl-service
insserv: FATAL: service dbus is missed in the runlevels S to use service bluetooth
insserv: exiting now!
insserv: FATAL: service vboxdrv has to be enabled to use service vboxautostart-service
insserv: FATAL: service dbus is missed in the runlevels S to use service bluetooth
insserv: exiting now!
insserv: FATAL: service vboxdrv has to be enabled to use service vboxweb-service
insserv: FATAL: service dbus is missed in the runlevels S to use service bluetooth
insserv: exiting now!
Processing triggers for mime-support (3.62) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for shared-mime-info (1.10-1) ...
Processing triggers for desktop-file-utils (0.23-4) ...

I believe that this may be a solution (or partial solution):

# update-rc.d vboxdrv defaults

Reference:
Instalando VirtualBox 6.0 en Devuan Beowulf
https://www.linuxito.com/cloud/1269-ins … an-beowulf

VirtualBox runs and appears to (mostly) work. However, at least one function (USB passthrough) does not. The extension pack and guest additions have been installed, so that isn't the problem.

Anyone have any ideas? And what about those error messages regarding dbus?


P.S.  Don't tell me not to use VirtualBox. I'm not ready to switch just yet.

#19 Re: Other Issues » [SOLVED] Security update delays » 2020-06-13 04:31:45

I found some evidence that this problem is back (or maybe it's a new, but related problem):

DSA-4701-1 intel-microcode -- security update
[Date Reported: 11 Jun 2020]

The update hasn't shown up for me yet, so I did some checking:

$ apt policy intel-microcode
intel-microcode:
  Installed: (none)
  Candidate: 3.20200609.2~deb9u1
  Version table:
     3.20200609.2~deb9u1 500
        500 http://deb.devuan.org/merged ascii-security/non-free i386 Packages
     3.20191115.2~deb9u1 500
        500 http://deb.devuan.org/merged ascii/non-free i386 Packages

When I first looked at that, I was a little confused. And then I remembered that I am using a 64-bit kernel (it's a multi-arch system).

So I checked again:

$ apt policy intel-microcode:amd64
intel-microcode:amd64:
  Installed: 3.20191115.2~deb9u1
  Candidate: 3.20191115.2~deb9u1
  Version table:
 *** 3.20191115.2~deb9u1 500
        500 http://deb.devuan.org/merged ascii/non-free amd64 Packages
        500 http://deb.devuan.org/merged ascii-security/non-free amd64 Packages
        100 /var/lib/dpkg/status

Okay, so that explains (partially) why I am not seeing the update. I then wondered, "Is this a Devuan problem, or is the problem on Debian's end?" To help answer that question, I added the repository for Debian Stretch security updates.

And here's the result that gave me:

$ apt policy intel-microcode:amd64
intel-microcode:amd64:
  Installed: 3.20191115.2~deb9u1
  Candidate: 3.20200609.2~deb9u1
  Version table:
     3.20200609.2~deb9u1 500
        500 http://deb.debian.org/debian-security stretch/updates/non-free amd64 Packages
 *** 3.20191115.2~deb9u1 500
        500 http://deb.devuan.org/merged ascii/non-free amd64 Packages
        500 http://deb.devuan.org/merged ascii-security/non-free amd64 Packages
        100 /var/lib/dpkg/status

That tells me that the problem is not on Debian's end.


Phil

#20 Re: Other Issues » [stable] security update delay for firefox-esr » 2020-06-06 15:13:14

What result does this give you?:

apt policy firefox-esr

Here's mine:

$ apt policy firefox-esr
firefox-esr:
  Installed: 68.9.0esr-1~deb9u1
  Candidate: 68.9.0esr-1~deb9u1
  Version table:
 *** 68.9.0esr-1~deb9u1 500
        500 http://deb.devuan.org/merged ascii-security/main i386 Packages
        100 /var/lib/dpkg/status
     68.4.1esr-1~deb9u1 500
        500 http://deb.devuan.org/merged ascii/main i386 Packages
     60.6.3esr-1~deb9u1 500
        500 http://deb.devuan.org/merged ascii-updates/main i386 Packages

That's on Devuan ASCII.


And here's a little more info:

$ ls -l /var/cache/apt/archives |grep firefox
-rw-r--r-- 1 root root 51238698 May  6 00:02 firefox-esr_68.8.0esr-1~deb9u1_i386.deb
-rw-r--r-- 1 root root 51256908 Jun  2 23:44 firefox-esr_68.9.0esr-1~deb9u1_i386.deb

Phil

#21 Re: Devuan » Why apt still links to libsystemd0? » 2020-06-04 23:07:41

criminalscum wrote:

Does it link to libsystemd0 because apt in Devuan is build from older source code or is that because apt in Devuan is built on Debian that has systemd?

The apt package in Devuan comes directly from Debian; it is an unmodified Debian package.

Phil

#22 Re: Devuan » Why apt still links to libsystemd0? » 2020-06-04 22:24:22

criminalscum wrote:

It's installed by libelogind0.

$ ldd $(which apt) | grep -i systemd
$ dpkg -S /usr/lib/x86_64-linux-gnu/libsystemd.so.0

That's not a problem. It's essentially a "fake" systemd component -- libelogind0 put that there because some software expects libsystemd0 to be present. The software "thinks" it's "talking" to libsystemd0, but it's really "talking" to libelogind0.


Phil

#23 Re: Devuan » Why apt still links to libsystemd0? » 2020-06-04 22:14:15

anticapitalista wrote:

Isn't it a symbolic link to libelogind.so.0?

Yes, you are correct.

Phil

#24 Re: Off-topic » Debian Buster with SysVinit as PID 1 [from FDN] » 2020-06-03 19:55:40

Just so people here know, here's why (in part) I chose to engage in what may seem, to some people, like a pointless endeavor:

1. To see what's currently possible.
2. To show others some of what's currently possible.
3. To (hopefully) increase the number of people using sysvinit-core and elogind -- Devuan may benefit from this since an increased number of people using those packages may help expose bugs more quickly.

Also, some people don't particularly like systemd, but they also don't want to leave Debian. Hopefully my post will help some of those people.


Phil

#25 Re: Forum Feedback » Forum notifications » 2020-05-28 00:02:29

I'm subscribed to this thread, and I didn't receive any notifications regarding replies.

Phil

Board footer

Forum Software