Posts by rbit

rbit · Other Issues

`apt-cache policy zfsutils-linux` should show:
Version table:
2.3.1-1~bpo12+1 100
2.1.11-1+deb12u1 500
...
(note this requires "contrib" on your daedalus-backports apt sources line)
`apt install zfsutils-linux -t=daedalus-backports` should install version 2.3.1-1

rbit · DIY

Scraper script is pretty complex now, and takes quite a while to run, it's only a one-time run needed for this,

Next step, rewrite the scraper in C
:-)

rbit · Hardware & System Configuration

What use do you give it?

I run a postfix mail server on it, as well as pihole. my local network uses it for dns. that's pretty much it. sometimes I'll use it as backup or to transfer files when it's convenient.

As I posted earlier, I downloaded two images but neither of them will boot my RPi. (see my previous two posts)
Can you boot from any one of them?

I have not tried either of the installer files you listed (from https://arm-files.devuan.org/Devuan-Arm64-Installer/ ?)
I had been able to boot an image from https://arm-files.devuan.org/RaspberryP … %20Builds/ and that was what I was recommending to use (since I knew they had worked for me previously).
I can give one of the installer images a try and see what happens here, but if the hardware's the same the result will probably be the same.

rbit · Hardware & System Configuration

I have a RPi3b+ running devuan. (actually, 2- one of them I manage remotely but can gain physical access to it if needed). Like you, I believe I started with ascii on it, some image obtained from https://arm-files.devuan.org/ written directly to SD card (since then, I've moved to external USB storage). Never tried an installer (don't think it was around then for arm).
Is there any particular reason for staying on ascii? I've upgraded mine, one to chimaera the other to daedalus. The first upgrade I think I had to resize the boot partition because the original one was too small. If you're setting it up new and don't have anything important already set up that you need to keep, it's probably easiest to download a more current image and dd it to your RPi media.

rbit · Installation

DevArch:

neither Excalibur nor Daedalus netinstall .iso images have WiFi support; they all require iwlwifi-ty* on an external USB drive. However, even when I provide it, Devuan is unable to find and use the driver.

The iwlwifi firmware issue is a bug on that iso. A new iso should be making its way to the mirrors soon. The problem was there was a newer firmware (firmware-iwlwifi_20250410-2_all.deb) but Contents-firmware listed an older one (firmware-iwlwifi_20241210-1_all.deb).

I'm not sure why the installer would not use the driver you provided, I'll take a look at that part. Could you tell me the steps you took so I can reproduce it?

Then "The system can be set up to symlink /bin and /sbin to /usr/bin and /usr/sbin, respectively. ....If unsure, the safe choice is "No".
However, the default choice was Yes.
So,Yes.

That seems like an odd question, it should probably be removed from excalibur due to usrmerge being required now.

rbit · Desktop and Multimedia

dDepending on your needs, Genymotion (https://www.genymotion.com/product-desktop/download/) may work. I used it in the past, seems like it's gotten a bit worse in later versions though from my perspective. It's something you could try, but it seems a bit hit-and-miss as far as app compatibility is concerned. It gives the option of using VirtualBox or QEMU for hypervisor.

rbit · Installation

(slightly off-topic, I know)
The excalibur (testing) netinstall iso should boot from ventoy.
I did confirm today the published daedalus netinstall iso will not boot form ventoy.
However there have been some changes to installer-iso project (https://git.devuan.org/devuan/installer-iso), if you build a new daedalus netinstall iso it will boot from ventoy. Just another option to put out there.

rbit · Hardware & System Configuration

I just noticed this problem yesterday on a VPS that I use. But it does not affect a different one. Both on the same kernel, 6.1.0-37 (amd64). May have something to do with the hosts. Thanks for tracking it down and finding a solution!

rbit · Installation

 dd if=/dev/zero of=zero.img ;  rm zero.img

would just zero-out the unused space on the partition. Probably so it compresses better with zip.

rbit · Other Issues

Not sure why backports kernel wouldn't work in your case. But to remain on a specific kernel version you could try this,
create a file in /etc/apt/preferences.d - you could call it pin-kernel or something
The contents would be:

Package: linux-image-amd64
Pin: version 6.1.137-1
Pin-Priority: 1001

You didn't mention architecture, so I'm assuming amd64. After creating that file, run `apt update`. I haven't actually used this with a kernel so not 100% sure on it. Keep an eye out for later kernel updates, once there's one past 6.1.0-37, you may want to try it out. To do so, remove the pin-kernel file and run `apt update` again. (or apt-get, or whatever you use to upgrade).

rbit · Installation

first thing that comes to mind is, ensure the boot partition has the "boot" flag - if /boot is not a separate partition, then make sure the root partition has the boot flag

rbit · Off-topic

You were on the wrong archive page. Try this one https://web.archive.org/web/20250209214 … mail/cups/

rbit · Hardware & System Configuration

As a workaround, I'd make a script to do this
/etc/pm/sleep.d/50_resolution (make it executable)

#!/bin/bash

case $1 in
  suspend|suspend_hybrid|hibernate)
    :
    ;;
  resume|thaw)
    xrandr --output HDMI-0 --mode 1920x1080 --rate 60 --primary
    ;;
esac

Obviously, change the "HDMI-0" to your device's correct output, and make any other adjustments to the xrandr line to fit your desired setting. If this doesn't work, try putting a short sleep command before the xrandr command.

rbit · Desktop and Multimedia

well that didn't work so well.
screen went black during boot (instead of showing scrolling text and eventually login prompt). I waited until a login prompt should have been there, then logged in, attempted startx. eventually the screen came back, X did not start. some errors in Xorg.0.log:

[    81.998] (EE) NVIDIA: Failed to load module "glxserver_nvidia" (module does not exist, 0)
[    81.998] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[    81.998] (EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
[    81.998] (EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
[    81.998] (EE) NVIDIA(0):     you continue to encounter problems, Please try
[    81.998] (EE) NVIDIA(0):     reinstalling the NVIDIA driver.
[    81.999] (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.
[    81.999] (EE) NVIDIA(0): Failing initialization of X screen
[    82.000] (EE) Screen(s) found, but none have a usable configuration.
[    82.000] (EE) 
Fatal server error:
[    82.000] (EE) no screens found(EE) 
[    82.000] (EE)

So... I removed the /etc/modprobe.d/nvidia_drm.conf file, rebooted, and put export WEBKIT_DISABLE_COMPOSITING_MODE=1 in my .profile. good enough, it's working at least. Not going to worry about the modesetting thing. Thanks again :-)

rbit · Desktop and Multimedia

Very promising information, thank you both.
Today I updated to kernel 6.11.10+bpo-amd64 6.11.10-1~bpo12+1 and also updated the nvidia driver to NVIDIA-Linux-x86_64-550.142.run - and it still wasn't working.
Following the suggestions on the linked pages, I tried statring midori as follows:

$ env WEBKIT_DISABLE_COMPOSITING_MODE=1 midori
src/nv_gbm.c:288: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

src/nv_gbm.c:288: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

Those errors were still in the console, but this time the error "KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied" wasn't present, and the window frame correctly showed the information.

I've now added the file /etc/modprobe.d/nvidia_drm.conf with the contents options nvidia_drm modeset=1 as suggested in the first link; I'll reboot in a little while and see if that fixes the issue without needing to set an env variable.

rbit · Desktop and Multimedia

A related post by someone else, with no answers: https://dev1galaxy.org/viewtopic.php?id=6540

Basically, there are some programs I use / would like to use that are not working properly on my system.

I don't recall when exactly the issue started; I'm thinking it may have been when I upgraded to daedalus, but that may not be accurate. The weird thing is, it was working correctly for a while somewhat recently, but now has gone wrong again. I don't use the affected programs often enough to pinpoint what has changed - that is, there are several kernel upgrades and possibly video driver updates in between.

The issue: when I open some programs, the main window is blank. I've had to start from a terminal to see any kind of error. The main programs I've noticed this affecting are midori and xiphos. There were some other webkit browsers I recently tried that were all affected also.

Here's a sample output from the terminal:

$ xiphos
src/nv_gbm.c:288: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

src/nv_gbm.c:288: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

src/nv_gbm.c:288: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

src/nv_gbm.c:288: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

src/nv_gbm.c:288: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

src/nv_gbm.c:288: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

src/nv_gbm.c:288: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Failed to create GBM buffer of size 995x836: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Failed to create GBM buffer of size 398x158: Permission denied
$ midori
src/nv_gbm.c:288: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

src/nv_gbm.c:288: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Failed to create GBM buffer of size 1440x780: Permission denied

The windows get created. midori shows the tab title "speed dial" and other buttons for the ui, but the main window is blank. xiphos shows the main ui elements, open tabs, etc, but again the main text window is blank. I found something on an ubuntu forum that suggested updating the video driver. I use the driver from nvidia.com. I had been using NVIDIA-Linux-x86_64-550.107.02, and have now updated it to NVIDIA-Linux-x86_64-550.135 but that didn't help.

Any suggestions?

further system information:
Linux hostname 6.11.5+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.11.5-1~bpo12+1 (2024-11-11) x86_64 GNU/Linux
desktop: xfce
video card: geforce gtx 1050 ti
i have 3 monitors in case that matters
all installed packages up-to-date
if it matters, I boot into text mode, using startx to start x. Xorg runs as my user, not as root.

After initially posting this, I also tried the same programs under a different user account. That did not help (the same errors showed).

Any help would be most appreciated.

rbit · Installation

Thanks for that, golinux. (btw your link is off, but I found the post from the title. just add a "2" to the end of your link -- id=6842).

:-)

rbit · Installation

I know this topic's "solved." I just have a comment related to something that you brought up a few times in this thread, and that's wicd. A few weeks ago (maybe a month, it's hard to keep track of time), during some periods of spare time, I attempted to get wicd to run on python3 with devuan daedalus. Made a fair amount of progress, but as of yet it is still nonfunctional. Haven't messed with it for probably 2 weeks now, but I may return to it, if/when I have the time. There's a lot of things that have changed with python and gtk... and I'm not a python programmer so some parts are a bit confusing. I primarily use my desktop on wired network anyway, no real need for network-manager or connman or wicd there.

rbit · Off-topic

It's its, not it's, unless you mean it is, in which case it's it's.

rbit · Off-topic

A man was injured by an explosion that blew off his left side.

Don't worry, he's all right.

rbit · Devuan

If you've got a bit of patience (it can several hours depending on machine and connection) you can build your own installer iso(s)

https://git.devuan.org/devuan/installer-iso

rbit · Other Issues

OK, so after installing seatd, and re-upgrading xserver-common and xserver-xorg-core, awaking the computer from suspend did not properly wake up the monitors [no input signal]. Today, I've downgraded xserver-common and left xserver-xorg-core upgraded (weird, I know) to try to see which of those 2 packages is causing this. I know, I could save the xfce session and shut down as a workaround. I'd like to get this working properly, though :-)

rbit · Other Issues

OK, so...yesterday I downgraded xserver-xorg-core and xserver-common to the versions on the installation media (as suggested by semil).

apt-cache policy xserver-common xserver-xorg-core
xserver-common:
  Installed: 2:21.1.7-3devuan1
  Candidate: 2:21.1.7-3devuan2
  Version table:
     2:21.1.7-3devuan2 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages
 *** 2:21.1.7-3devuan1 100
        100 /var/lib/dpkg/status
xserver-xorg-core:
  Installed: 2:21.1.7-3devuan1
  Candidate: 2:21.1.7-3devuan2
  Version table:
     2:21.1.7-3devuan2 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages
 *** 2:21.1.7-3devuan1 100
        100 /var/lib/dpkg/status

I rebooted (maybe not necessary) and restarted X. Suspended the computer last night; upon waking it up this morning, the screens came back up as they should. So one of those packages is the culprit. I can be content using the older versions of these and leave things alone.
Other info:
This system has been upgraded over and over since Jessie. I don't use a gui login (such as slim) anymore, nor do I run X as root. Some things that are installed are (or were) defaults and I'm not that knowledgeable about what's best. When I do apt search seat I find that I have the following installed: elogind, libelogind-compat, libelogind0, libseat1. I do not have seatd installed. Does this replace elogind? Could installing seatd fix the issue I'm having with the latest xserver? I just might try that anyway and find out...

rbit · Other Issues

semil wrote:

you could get the old debs out of installation media.

Thanks for the suggestion. Again, I'm not sure what started the problem, but at least I can roll back these updates and try to narrow it down, hopefully :-)

rbit · Other Issues

I'm running Daedalus amd64 with xfce and sysvinit, kernel 6.1.0-13.
The problem just started happening some time in the week or so. I regularly suspend my PC overnight and awaken it in the morning. Now, when I awaken it, the monitors are all blank for about a minute, and then show some strange patterns on them. My suspend script (which has not changed recently) calls /usr/bin/xflock4 followed by /usr/sbin/pm-suspend . The computer, upon awakening, is not completely frozen; I can use the SysRq keys to force a reboot, or even switch to a vt (ctrl-alt-function key) and then ctrl-alt-delete to reboot. But it is annoying; I generally have some (or many) things open and ready to resume work with in the morning. From browsing through my apt history.log, I am suspecting it may be the recent updates to xserver-xorg-cor and xserver-common, but I don't have the older debs to downgrade those packages. I have tried a few things, in an attempt to narrow down the problem. 1st, I tried booting into an older kernel (6.1.0-12), that made no difference. I tried re-installing my nvidia driver (470.199.02; the card is GeForce GTX 650), that made no difference. I tried closing X down, logged into a VT, and ran pm-suspend. In the morning, blank screen on the VT, but I could type startx and had the GUI working, but all the VTs (ctrl-alt-function keys) were blank. So that was weird. And not really a solution because I would like to have things open in X when I suspend/resume. The very latest package I had installed before this started was arandr; but I purged that and it didn't help. Other than that, there were several package upgrades around that time, but nothing seemed suspicious to me. Any ideas / what else can I check?

Start-Date: 2023-10-07  14:06:37
Commandline: apt upgrade
Install: linux-headers-6.1.0-13-amd64:amd64 (6.1.55-1, automatic), linux-image-6.1.0-13-amd64:amd64 (6.1.55-1, automatic), linux-headers-6.1.0-13-common:amd64 (6.1.55-1, automatic)
Upgrade: telnet:amd64 (0.17+2.4-2, 0.17+2.4-2+deb12u1), libcups2:amd64 (2.4.2-3+deb12u1, 2.4.2-3+deb12u4), libcurl4-openssl-dev:amd64 (7.88.1-10+deb12u1, 7.88.1-10+deb12u3), qemu-system-x86:amd64 (1:7.2+dfsg-7+deb12u1, 1:7.2+dfsg-7+deb12u2), libcurl4:amd64 (7.88.1-10+deb12u1, 7.88.1-10+deb12u3), libxnvctrl0:amd64 (525.85.05-1, 525.85.05-3~deb12u1), libpam-runtime:amd64 (1.5.2-6, 1.5.2-6+deb12u1), libvpx7:amd64 (1.12.0-1+deb12u1, 1.12.0-1+deb12u2), krb5-locales:amd64 (1.20.1-2, 1.20.1-2+deb12u1), libgssapi-krb5-2:amd64 (1.20.1-2, 1.20.1-2+deb12u1), libcurl3-gnutls:amd64 (7.88.1-10+deb12u1, 7.88.1-10+deb12u3), openssh-client:amd64 (1:9.2p1-2, 1:9.2p1-2+deb12u1), calibre-bin:amd64 (6.13.0+repack-2, 6.13.0+repack-2+deb12u1), libkf5plasmaquick5:amd64 (5.103.0-1, 5.103.0-1+deb12u1), libnftables1:amd64 (1.0.6-2+deb12u1, 1.0.6-2+deb12u2), libgtk-4-common:amd64 (4.8.3+ds-2, 4.8.3+ds-2+deb12u1), cups-bsd:amd64 (2.4.2-3+deb12u1, 2.4.2-3+deb12u4), libx11-xcb1:amd64 (2:1.8.4-2+deb12u1, 2:1.8.4-2+deb12u2), cups-common:amd64 (2.4.2-3+deb12u1, 2.4.2-3+deb12u4), libldb2:amd64 (2:2.6.2+samba4.17.10+dfsg-0+deb12u1, 2:2.6.2+samba4.17.11+dfsg-0+deb12u1), mariadb-client-core:amd64 (1:10.11.3-1, 1:10.11.4-1~deb12u1), libqt5positioning5:amd64 (5.15.8+dfsg-3, 5.15.8+dfsg-3+deb12u1), libc++1:amd64 (1:14.0-55.6, 1:14.0-55.7~deb12u1), libbrlapi0.8:amd64 (6.5-7, 6.5-7+deb12u1), grub-pc-bin:amd64 (2.06-13, 2.06-13+deb12u1), libgs10-common:amd64 (10.0.0~dfsg-11+deb12u1, 10.0.0~dfsg-11+deb12u2), cups-client:amd64 (2.4.2-3+deb12u1, 2.4.2-3+deb12u4), cups-ppdc:amd64 (2.4.2-3+deb12u1, 2.4.2-3+deb12u4), cups-daemon:amd64 (2.4.2-3+deb12u1, 2.4.2-3+deb12u4), linux-compiler-gcc-12-x86:amd64 (6.1.52-1, 6.1.55-1), libgs10:amd64 (10.0.0~dfsg-11+deb12u1, 10.0.0~dfsg-11+deb12u2), pandoc-data:amd64 (2.17.1.1-1.1, 2.17.1.1-2~deb12u1), transmission-gtk:amd64 (3.00-2.1+b1, 3.00-2.1+deb12u1), mariadb-server-core:amd64 (1:10.11.3-1, 1:10.11.4-1~deb12u1), debianutils:amd64 (5.7-0.4, 5.7-0.5~deb12u1), libwbclient0:amd64 (2:4.17.10+dfsg-0+deb12u1, 2:4.17.11+dfsg-0+deb12u1), linux-headers-amd64:amd64 (6.1.52-1, 6.1.55-1), openssh-server:amd64 (1:9.2p1-2, 1:9.2p1-2+deb12u1), libkrb5support0:amd64 (1.20.1-2, 1.20.1-2+deb12u1), libsmbclient:amd64 (2:4.17.10+dfsg-0+deb12u1, 2:4.17.11+dfsg-0+deb12u1), libimlib2:amd64 (1.10.0-4+b1, 1.10.0-4+deb12u1), gir1.2-gtk-3.0:amd64 (3.24.37-2, 3.24.38-2~deb12u1), libxpm4:amd64 (1:3.5.12-1.1, 1:3.5.12-1.1+deb12u1), linux-kbuild-6.1:amd64 (6.1.52-1, 6.1.55-1), cups-ipp-utils:amd64 (2.4.2-3+deb12u1, 2.4.2-3+deb12u4), debian-archive-keyring:amd64 (2023.3, 2023.3+deb12u1), qemu-utils:amd64 (1:7.2+dfsg-7+deb12u1, 1:7.2+dfsg-7+deb12u2), libx11-data:amd64 (2:1.8.4-2+deb12u1, 2:1.8.4-2+deb12u2), inetutils-ping:amd64 (2:2.4-2, 2:2.4-2+deb12u1), ghostscript:amd64 (10.0.0~dfsg-11+deb12u1, 10.0.0~dfsg-11+deb12u2), libssl3:amd64 (3.0.9-1, 3.0.11-1~deb12u1), libkrb5-3:amd64 (1.20.1-2, 1.20.1-2+deb12u1), libpam-modules:amd64 (1.5.2-6, 1.5.2-6+deb12u1), libhwy1:amd64 (1.0.3-3, 1.0.3-3+deb12u1), linux-image-amd64:amd64 (6.1.52-1, 6.1.55-1), libvte-2.91-common:amd64 (0.70.6-1~deb12u1, 0.70.6-2~deb12u1), inetutils-telnet:amd64 (2:2.4-2, 2:2.4-2+deb12u1), libk5crypto3:amd64 (1.20.1-2, 1.20.1-2+deb12u1), libssl-dev:amd64 (3.0.9-1, 3.0.11-1~deb12u1), libx11-xcb-dev:amd64 (2:1.8.4-2+deb12u1, 2:1.8.4-2+deb12u2), calibre:amd64 (6.13.0+repack-2, 6.13.0+repack-2+deb12u1), libcupsimage2:amd64 (2.4.2-3+deb12u1, 2.4.2-3+deb12u4), mariadb-common:amd64 (1:10.11.3-1, 1:10.11.4-1~deb12u1), libpam-modules-bin:amd64 (1.5.2-6, 1.5.2-6+deb12u1), grub2-common:amd64 (2.06-13, 2.06-13+deb12u1), qemu-system-common:amd64 (1:7.2+dfsg-7+deb12u1, 1:7.2+dfsg-7+deb12u2), libx11-dev:amd64 (2:1.8.4-2+deb12u1, 2:1.8.4-2+deb12u2), libx11-doc:amd64 (2:1.8.4-2+deb12u1, 2:1.8.4-2+deb12u2), openssh-sftp-server:amd64 (1:9.2p1-2, 1:9.2p1-2+deb12u1), libpam0g:amd64 (1.5.2-6, 1.5.2-6+deb12u1), grub-common:amd64 (2.06-13, 2.06-13+deb12u1), libgtk-3-0:amd64 (3.24.37-2, 3.24.38-2~deb12u1), libgtk-4-1:amd64 (4.8.3+ds-2, 4.8.3+ds-2+deb12u1), cups-core-drivers:amd64 (2.4.2-3+deb12u1, 2.4.2-3+deb12u4), samba-libs:amd64 (2:4.17.10+dfsg-0+deb12u1, 2:4.17.11+dfsg-0+deb12u1), libmariadb3:amd64 (1:10.11.3-1, 1:10.11.4-1~deb12u1), transmission-common:amd64 (3.00-2.1, 3.00-2.1+deb12u1), gtk-update-icon-cache:amd64 (3.24.37-2, 3.24.38-2~deb12u1), libgtk-3-common:amd64 (3.24.37-2, 3.24.38-2~deb12u1), libkf5plasma5:amd64 (5.103.0-1, 5.103.0-1+deb12u1), libvpx-dev:amd64 (1.12.0-1+deb12u1, 1.12.0-1+deb12u2), libgtk-3-bin:amd64 (3.24.37-2, 3.24.38-2~deb12u1), libmariadb-dev:amd64 (1:10.11.3-1, 1:10.11.4-1~deb12u1), libgtk-3-dev:amd64 (3.24.37-2, 3.24.38-2~deb12u1), cups:amd64 (2.4.2-3+deb12u1, 2.4.2-3+deb12u4), curl:amd64 (7.88.1-10+deb12u1, 7.88.1-10+deb12u3), libgs-common:amd64 (10.0.0~dfsg-11+deb12u1, 10.0.0~dfsg-11+deb12u2), libx11-6:amd64 (2:1.8.4-2+deb12u1, 2:1.8.4-2+deb12u2), transmission:amd64 (3.00-2.1, 3.00-2.1+deb12u1), cups-server-common:amd64 (2.4.2-3+deb12u1, 2.4.2-3+deb12u4), libvte-2.91-0:amd64 (0.70.6-1~deb12u1, 0.70.6-2~deb12u1), qemu-system-data:amd64 (1:7.2+dfsg-7+deb12u1, 1:7.2+dfsg-7+deb12u2), plasma-framework:amd64 (5.103.0-1, 5.103.0-1+deb12u1), grub-pc:amd64 (2.06-13, 2.06-13+deb12u1), qemu-system-gui:amd64 (1:7.2+dfsg-7+deb12u1, 1:7.2+dfsg-7+deb12u2), openssl:amd64 (3.0.9-1, 3.0.11-1~deb12u1), pandoc:amd64 (2.17.1.1-1.1, 2.17.1.1-2~deb12u1), nftables:amd64 (1.0.6-2+deb12u1, 1.0.6-2+deb12u2), linux-libc-dev:amd64 (6.1.52-1, 6.1.55-1)
End-Date: 2023-10-07  14:08:07

Start-Date: 2023-10-07  16:54:29
Commandline: apt upgrade --fix-missing
Upgrade: dbus-daemon:amd64 (1.14.6-1devuan1, 1.14.10-1~deb12u1devuan1), libdbus-1-3:amd64 (1.14.6-1devuan1, 1.14.10-1~deb12u1devuan1), dbus-bin:amd64 (1.14.6-1devuan1, 1.14.10-1~deb12u1devuan1), dbus-x11:amd64 (1.14.6-1devuan1, 1.14.10-1~deb12u1devuan1), eudev:amd64 (3.2.12-1, 3.2.12-4+deb12u1), dbus-session-bus-common:amd64 (1.14.6-1devuan1, 1.14.10-1~deb12u1devuan1), libeudev-dev:amd64 (3.2.12-1, 3.2.12-4+deb12u1), libdbus-1-dev:amd64 (1.14.6-1devuan1, 1.14.10-1~deb12u1devuan1), dbus-system-bus-common:amd64 (1.14.6-1devuan1, 1.14.10-1~deb12u1devuan1), dbus:amd64 (1.14.6-1devuan1, 1.14.10-1~deb12u1devuan1), libeudev1:amd64 (3.2.12-1, 3.2.12-4+deb12u1)
End-Date: 2023-10-07  16:54:40

Start-Date: 2023-10-07  17:00:58
Commandline: apt autoremove
Purge: linux-image-6.1.0-11-amd64:amd64 (6.1.38-4), linux-headers-6.1.0-11-common:amd64 (6.1.38-4), linux-headers-6.1.0-11-amd64:amd64 (6.1.38-4)
End-Date: 2023-10-07  17:01:07

Start-Date: 2023-10-08  17:18:56
Commandline: apt upgrade
Upgrade: python2.7-minimal:amd64 (2.7.18-13ubuntu2, 2.7.18-13ubuntu2), xserver-xorg-core:amd64 (2:21.1.7-3devuan1, 2:21.1.7-3devuan2), palemoon:amd64 (32.4.0.1-1.gtk2, 32.4.0.1-1.gtk2), xserver-common:amd64 (2:21.1.7-3devuan1, 2:21.1.7-3devuan2)
End-Date: 2023-10-08  17:19:00

Start-Date: 2023-10-08  17:20:25
Commandline: apt remove python2.7 python2.7-minimal libpython2.7-minimal libpython2.7-stdlib
Purge: python2.7-minimal:amd64 (2.7.18-13ubuntu2), python2.7:amd64 (2.7.18-13ubuntu2), libpython2.7-minimal:amd64 (2.7.18-13ubuntu2), libpython2.7-stdlib:amd64 (2.7.18-13ubuntu2)
End-Date: 2023-10-08  17:20:27

Start-Date: 2023-10-13  00:00:03
Commandline: apt upgrade --fix-missing
Upgrade: libcurl4-openssl-dev:amd64 (7.88.1-10+deb12u3, 7.88.1-10+deb12u4), libcurl4:amd64 (7.88.1-10+deb12u3, 7.88.1-10+deb12u4), libcurl3-gnutls:amd64 (7.88.1-10+deb12u3, 7.88.1-10+deb12u4), chromium-sandbox:amd64 (117.0.5938.149-1~deb12u1, 118.0.5993.70-1~deb12u1), libldb2:amd64 (2:2.6.2+samba4.17.11+dfsg-0+deb12u1, 2:2.6.2+samba4.17.12+dfsg-0+deb12u1), libjavascriptcoregtk-4.1-0:amd64 (2.40.5-1~deb12u1, 2.42.1-1~deb12u1), gir1.2-javascriptcoregtk-4.0:amd64 (2.40.5-1~deb12u1, 2.42.1-1~deb12u1), gir1.2-webkit2-4.0:amd64 (2.40.5-1~deb12u1, 2.42.1-1~deb12u1), libwbclient0:amd64 (2:4.17.11+dfsg-0+deb12u1, 2:4.17.12+dfsg-0+deb12u1), libsmbclient:amd64 (2:4.17.11+dfsg-0+deb12u1, 2:4.17.12+dfsg-0+deb12u1), chromium:amd64 (117.0.5938.149-1~deb12u1, 118.0.5993.70-1~deb12u1), libjavascriptcoregtk-4.0-18:amd64 (2.40.5-1~deb12u1, 2.42.1-1~deb12u1), libwebkit2gtk-4.1-0:amd64 (2.40.5-1~deb12u1, 2.42.1-1~deb12u1), chromium-common:amd64 (117.0.5938.149-1~deb12u1, 118.0.5993.70-1~deb12u1), samba-libs:amd64 (2:4.17.11+dfsg-0+deb12u1, 2:4.17.12+dfsg-0+deb12u1), libwebkit2gtk-4.0-37:amd64 (2.40.5-1~deb12u1, 2.42.1-1~deb12u1), curl:amd64 (7.88.1-10+deb12u3, 7.88.1-10+deb12u4)
End-Date: 2023-10-13  00:00:14

Start-Date: 2023-10-13  22:05:50
Commandline: apt install arandr
Install: arandr:amd64 (0.1.11-1)
End-Date: 2023-10-13  22:05:53

Start-Date: 2023-10-16  08:30:57
Commandline: apt purge arandr
Purge: arandr:amd64 (0.1.11-1)
End-Date: 2023-10-16  08:31:00

The officially official Devuan Forum!

#1 Re: Other Issues » [SOLVED] zfsutils-linux backport not showing via apt » 2025-06-29 03:31:15

#2 Re: DIY » Working on a new app, the learning curve continues... » 2025-06-27 17:13:47

#3 Re: Hardware & System Configuration » Installer *.iso problems - again ... » 2025-06-26 18:35:23

#4 Re: Hardware & System Configuration » Installer *.iso problems - again ... » 2025-06-26 15:45:58

#5 Re: Installation » No live devuan or refracta will boot on a new AMD Ryzen AI 9 HX370 » 2025-06-17 16:50:13

#6 Re: Desktop and Multimedia » Android in a VM - recommendations? » 2025-06-13 15:22:21

#7 Re: Installation » Minimalist/selective installation? » 2025-06-11 23:36:24

#8 Re: Hardware & System Configuration » [SOLVED] Non-root-users cannot ping in devuan5-based lxc-container » 2025-06-07 15:03:30

#9 Re: Installation » [SOLVED] accidentally deleted (EFI) partition - how recover? » 2025-06-07 14:47:55

#10 Re: Other Issues » Daedalus kernel upgrade from 6.1.0-35 to 6.1.0.37 breaks hibernate » 2025-06-07 14:46:14

#11 Re: Installation » [SOLVED] MBR and efi booting issue » 2025-05-09 02:58:13

#12 Re: Off-topic » Access to CUPS archives denied » 2025-04-23 23:24:34

#13 Re: Hardware & System Configuration » Resolution » 2025-02-07 02:02:23

#14 Re: Desktop and Multimedia » [SOLVED] window /frame content not displaying » 2024-12-26 04:04:38

#15 Re: Desktop and Multimedia » [SOLVED] window /frame content not displaying » 2024-12-26 03:47:30

#16 Desktop and Multimedia » [SOLVED] window /frame content not displaying » 2024-12-09 16:48:46

#17 Re: Installation » [SOLVED] Very strange: is it connman or network-manager? » 2024-09-26 14:33:45

#18 Re: Installation » [SOLVED] Very strange: is it connman or network-manager? » 2024-09-26 01:26:07

#19 Re: Off-topic » Thread derailing detritus » 2024-09-08 02:43:58

#20 Re: Off-topic » The Joke Thread » 2024-09-07 22:56:45

#21 Re: Devuan » Devuan Excalibur ISO » 2024-09-07 22:29:36

#22 Re: Other Issues » video not waking up after suspend » 2023-10-22 16:56:50

#23 Re: Other Issues » video not waking up after suspend » 2023-10-21 14:03:25

#24 Re: Other Issues » video not waking up after suspend » 2023-10-21 00:14:06

#25 Other Issues » video not waking up after suspend » 2023-10-20 02:43:08

Board footer