The officially official Devuan Forum!

You are not logged in.

#1 Re: Desktop and Multimedia » Switching VT crashes Xorg after upgrade to Daedalus » 2023-09-25 09:10:55

If seatd or logind (elogind) are running as system services they will be able mediate input access for a non-root user running Xorg. If not, then the users must themselves be in input group for accessing the input devices.

The Devuan fork expands the logind method with the seatd alternative, and it includes the "built-in seatd" variant to cater for the legacy use where the Xorg user has sufficient access to both graphics and inputs.

Unfortunately Xorg at daedalus is slightly broken around some VT switch scenarios. It that has got fixed for the current excalibur version and I think/hope this version is going to turn up for daedalus soonish.

I'm not an expert on this but afaiui key logging can't really happen merely with device node access but would be done via event capture within X. Still I believe the idea of restricting device node access for input devices is based on security reasoning.

I don't know whether and how the graphics device separates the displays of different Xorg.

#2 Re: Hardware & System Configuration » bluetooth » 2023-09-25 04:07:55

This was kind of convenient for me as I have very recently migrated to daedalus myself and hadn't yet set up bluetooth here. To do so, I did as follows:

# apt-get install --no-install-recommends alsa-utils blueman bluez-alsa-utils

That provides a virual soundcard named bluealsa for alsa, and this uses dbus to obtain the headphone "sink" from the bluetooth device management (actually bluez) with blueman as a handy GUI tool for operating the bluetooth devices.

bluez-alsa-utils unfortunately installs as if systemd would be around, so some additional hands-on is needed for registering the bluealsa dbus service. You need to add the following text file:

Add /usr/share/dbus-1/system-services/org.bluealsa.service

[D-BUS Service]
Exec=/usr/bin/bluealsa -p a2dp-sink -p a2dp-source -S

and then run

# service dbus reload

Then you run blueman as non-root user for the device management, to pair and connect the headphones. (Keep it running in the background, though if it works well it install a control button in the panel)

Note that you need the mac address for the headphones for playing to them. (E.g, after pairing you can bring up the "info" page for the headphones by right-clicking, and there select and copy the "Address" line for later pasting).

For testing this you may try the following (with your mac address rather than mine):

$ aplay -D bluealsa:30:21:DC:50:9E:89 /usr/share/sounds/alsa/Rear_Center.wav

Next, if you want to direct audio to bluealsa by default, you may state that in your ~/.asoundrc, eg:

pcm.!default headphones

pcm.headphones {
    type bluealsa
    device 30:21:DC:50:9E:89
    profile a2dp

There's a lot to be known about alsa configuration....

#3 Re: Installation » apt install kde-plasma-desktop recommends systemd » 2023-09-24 20:36:45

Yeah; just like all cats turn left together when you try to herd them smile

#4 Re: Installation » Nvidia Problem (again) » 2023-09-24 20:31:08

If "Installed Daedalus" actually means "dist-upgraded to Daedalus" there is the possibility that you overlooked adding the (new) non-free-firmware section onto the sources.list lines.

Other than that, I don't know much about nvidia cards.

#5 Re: Packaging for Devuan » Can not install "qemu-system-x86" » 2023-09-24 11:18:53

Yeah. It's something to look at when excalibur is going stable.

#6 Re: Hardware & System Configuration » bluetooth » 2023-09-24 11:14:55

You need firstly to install bluez. This package and it's sub packages handles the actual connectivity between the computer and the headphones. Conceptually bluez represents the computer endpoint for the "wireless wiring' to your headphones.

In addition to that, you need the pieces of software that links the sound system with the bluez device management. This part depends on which sound system you are using.

Plain alsa or pulsaudio are possibly the two main alternatives for audio setup, but there are others.

For plain alsa you would need the bluez-alsa-utils package which implements the "virtual soundcard" that plays to and records from bluethooth headsets. It will also need manual configuration changes to tell the sound system how to channel audio through it.

For pulsaudio you instead would need the pulsaudio-module-bluetooth package. Upon installation it updates the pulseaudio configuration to some extent but there might also still be additional hands-on needed. I no longer use pulsaudio though so someone else will need to guide you for that.

#7 Re: Installation » Daedalus ISOs don't boot » 2023-09-24 10:43:00

@fchk, if a 5.0.2 ISO with proper GPT saw the light of day, would you prefer it being netinstall, server or desktop?

#8 Re: Desktop and Multimedia » Switching VT crashes Xorg after upgrade to Daedalus » 2023-09-23 23:28:55

@fsmithred, your second user doesn't have access to graphics, and you also need to direct Xorg to the VT concerned as it otherwise will try to use "the next free", an action that requires root permission (or more specifically access to /dev/ttyN for VT N).

Thus, with graphics access, you might have success with startx -- :1 vt$(tty|tr -c -d '[0-9]')
That last bit is vtN where N is the number in the output of the tty command.

#9 Re: Desktop and Multimedia » Switching VT crashes Xorg after upgrade to Daedalus » 2023-09-23 23:19:26

There are a couple of issues at play here.

Firstly, that the Xserver was modified to obtain its input streams via a mediating process, either logind or seatd. When neither is available, there is a builtin seatd implementing mediation, and that requires the running user to have access to the input devices (typically group "input") and graphics (typically group video"). (Or being root).

Secondly, there is a bug in the daedalus Xserver version concerning USB keyboards. #793. This was recently fixed and published in version 21.1.8-1devuan2, which is available in excalibur but not yet backported to daedalus.

Note that the introduction of input access mediation in Debian brought in systemd (systemd-logind) to X, and that caused a fair bit of work to handle. In particular to untie the bind to logind and offer seatd as alternative, including the built-in variant that in principle should offer the legacy use (where the Xorg user has direct access rights to both graphics and inputs). Notably seatd is only concerned with input mediation and it does not extend to any of the other functions provided by logind (login manager, lid switch action, etc etc).

Thus, in short, Xorg is now forked and the daedalus version (2:21.1.7-3devuan1) is the first fork release. It has issues with VT switching and this might be resolved in the upcoming version 2:21.1.8-1devuan2 which should find its way to daedalus fairly soon.

#10 Re: Installation » Archiving it -all- » 2023-09-23 09:13:00

Everything that is available for a sources.list point is described in its "Packages" file that is downloaded to your computer with the "apt-get update" command. All the Packages files are held in /var/lib/apt/lists/. To download all daedalus packages you could do something like the following:

awk '$1=="Package:"{P=$2}$1=="Version:"{print P "=" $2}' \
    /var/lib/apt/lists/deb.devuan.org_merged_dists_daedalus_*_binary-amd64_Packages | \
   xargs -n1 apt-get download 

It's a lot.

#11 Re: Hardware & System Configuration » [SOLVED] Dell Inspiron 14 (2 in 1) » 2023-09-22 09:56:45

Actually you can also use the Devuan installer-iso to investigate the modules.

Just add "emerg" (without quotes) to the boot command line: this will make it interrupt its boot with a busybox shell in the Devuan boot preamble. You may there investigate which modules it has loaded, and even mount the target disk for hands-on. Or possibly even switch_root to the installed filesystem (I haven't tried this).

#12 Re: Hardware & System Configuration » [SOLVED] Dell Inspiron 14 (2 in 1) » 2023-09-22 09:06:59

Firstly you should confirm that the nvme module is duly included and loaded in the initrd.

If you choose the "generic" option for initramfs modules, the required modules would likely be included but it might still be necessary to mention them in /etc/initramfs-tools/modules to make sure they are loaded (in case auto-detection doesn't work). Check in your artix linux which modules are need.

#13 Re: Installation » Daedalus ISOs don't boot » 2023-09-21 21:28:49

1) make another thread for this, and use code tags.

2) use partition UUID or filesystem labels.

#14 Re: Installation » Daedalus ISOs don't boot » 2023-09-20 23:08:04

1. If the hardware works with Debian 12 it should work with Devuan 5 since that's the same software apart from the squashing of the systemd infestation. You will need to analyse more in detail which software was used in the working setup and make sure the same software is used, possibly in later versions.

2. How come your nvme drive is not named /dev/nvmen0?

#16 Re: Hardware & System Configuration » Default dhcp client floods my syslog » 2023-09-17 02:28:54

Apparently your machine runs multiple dhclient processes competing about the interfaces.

Which networking do you use? Do you use ifupdown (which primarily is configured with /etc/network/interfaces) or something else, or several?

#17 Re: DIY » Question, about dd and/or qemu, for disk cloning » 2023-09-15 23:25:33

You can use dd to create a 500G "empty" sparse file:

dd if=/dev/zero of=/mysparsefile bs=1G count=0 seek=500

Though after that you still have the problem of identifying which blocks on /dev/sda are in use so as to copy those. If you have run zerofree, i.e. made all unused blocks be zeroed, then another dd would do the job, e.g.

dd if=/dev/sda2 of=/mysparsefile conv=sparse,notrunc

Obviously mysparsefile needs to be somewhere with enough space but not on /dev/sda (as it then will fill up the 500G by copying its own blocks)

#18 Re: Installation » Daedalus ISOs don't boot » 2023-09-15 13:42:13

Note that the updated Devuan daedalus installer ISO set 5.0.1 now also handles the use case of booting from CDROM on UEFI.

The issue indeed was that the boot loader got confused about the iso9660 block size (2k) differing from the expected block size (512) for the EFI filesystem. To fix that we forked syslinux, added a corrective patch and published to Devuan experimental. The patched software was next used for building the updated ISO set.

#19 Re: Desktop and Multimedia » Input/output error with EasyCap capture card on VLC and OBS » 2023-09-14 22:12:35

Yes;  expanding on @alexkemp's note, the file mode string starts which a marker character to tell whether it's a block device (b), a character device (c, as here), a directory (d), a symbolic link (l) or a normal file (-). Next it shows three triplets to indicate the access mode setting for user, group and other (plus some special meanings depending in type).

In this case root is the user and root is the group, with read and write access, while all other users or groups only have read acccess. In other words, you only have read access (unless you are running this as root or your user is in root group)

Quite possibly the lack of write access to the USB device has been the cause here.

You change that, but only as root, and in this case you could use the command

# chmod o+w /dev/bus/usb/001/015

to add write access to other.

#20 Re: Other Issues » no update » 2023-09-14 12:31:24

@yemuyin presumably the computer clock is off by 51.5 hours. You'll need to correct that.

#21 Re: DIY » Question, about dd and/or qemu, for disk cloning » 2023-09-13 23:07:47

@zapper, I think you can use the zerofree program for ext[234] filesystems to get all unused blocks of their partitions to be zeroed. Perhaps similar tools exist for other filesystems, if that's what you have.

Then according to its man page,  qemu-img has the -S size argument whereby it translates contiguous runs of zeros as holes.

And dd can do something similar with the conv=sparse argument, though only into a sparse raw image file.

#22 Re: Desktop and Multimedia » Input/output error with EasyCap capture card on VLC and OBS » 2023-09-13 22:48:20

@hunter0one, did you verify read-write access to the USB device node concerned?

Obviously you have read access but you do need write access right as well. Use e.g. lsusb to figure out which "bus id" it has, en then chech that /dev/bus/usb/xxx/yyy.

#23 Re: Desktop and Multimedia » Input/output error with EasyCap capture card on VLC and OBS » 2023-09-13 01:06:47

Other things at system level would be to ensure you have rw access to the usb dev-node.. (/dev/bus/usb/00?/0??) and make sure the dongle is on a USB 2 port.

#24 Re: Desktop and Multimedia » Input/output error with EasyCap capture card on VLC and OBS » 2023-09-12 13:58:32

I guess you've confirmed file access mode for /dev/videoN .. you need rw I think.

#25 Re: Desktop and Multimedia » Input/output error with EasyCap capture card on VLC and OBS » 2023-09-12 13:44:51

seems the URL should have been .. I was fooled by the javascript when expanding that article... anyhow, the first tak-out is the qv4l2 tool.

Board footer

Forum Software