The officially official Devuan Forum!

You are not logged in.

#2 Re: Hardware & System Configuration » Chimaera fresh installation: Issues with fingerprint authentication » 2021-10-24 19:40:04

Head_on_a_Stick wrote:

Does the "freeze" unstick if you wiggle the mouse (or touchpad) repeatedly? It could be waiting for entropy (pointlessly).

If that helps then see http://dev1galaxy.org/viewtopic.php?pid=32269#p32269 for a potential solution.

The above suggested action did not have any effect on my case.

mmaglis wrote:

How can I debug this?

Check the logs.

EDIT: lsusb command shows:

Bus 005 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor

Putting fprintd in debug mode

env G_MESSAGES_DEBUG=all /usr/libexec/fprintd -t

and run until interrupted with Ctrl+C

fprintd-enroll -f right-index-finger <USERNAME>

I get the following debug information:

(fprintd:9225): fprintd-DEBUG: 21:16:53.750: About to load configuration file '/etc/fprintd.conf'
(fprintd:9225): fprintd-DEBUG: 21:16:53.751: Launching FprintObject
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.760: No driver found for USB device 0CF3:9271
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0002
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 046D:C31C
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 0461:4D81
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0001
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0001
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0001
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0002
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0001
(fprintd:9225): libfprint-context-DEBUG: 21:16:53.761: No driver found for USB device 1D6B:0001
(fprintd:9225): fprintd-DEBUG: 21:16:53.766: entering main loop
(fprintd:9225): fprintd-DEBUG: 21:16:53.767: D-Bus service launched with name: net.reactivated.Fprint

(fprintd:9225): fprintd-DEBUG: 21:18:28.872: Requesting device 'AuthenTec AES2501' authorization for method Claim from :1.289
(fprintd:9225): fprintd-DEBUG: 21:18:28.874: Getting authorization to perform Polkit action net.reactivated.fprint.device.setusername
(fprintd:9225): fprintd-DEBUG: 21:18:28.877: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:9225): fprintd-DEBUG: 21:18:28.882: Authorization granted to AuthenTec AES2501 to call method 'Claim' for device :1.289!
(fprintd:9225): fprintd-DEBUG: 21:18:28.882: user '<USERNAME>' claiming the device: 0
(fprintd:9225): libfprint-image_device-DEBUG: 21:18:28.979: Image device open completed
(fprintd:9225): libfprint-device-DEBUG: 21:18:28.979: Device reported open completion
(fprintd:9225): libfprint-device-DEBUG: 21:18:28.979: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(fprintd:9225): fprintd-DEBUG: 21:18:28.979: claimed device 0
(fprintd:9225): fprintd-DEBUG: 21:18:28.982: Requesting device 'AuthenTec AES2501' authorization for method EnrollStart from :1.289
(fprintd:9225): fprintd-DEBUG: 21:18:28.982: Getting authorization to perform Polkit action net.reactivated.fprint.device.enroll
(fprintd:9225): fprintd-DEBUG: 21:18:28.989: Authorization granted to AuthenTec AES2501 to call method 'EnrollStart' for device :1.289!
(fprintd:9225): fprintd-DEBUG: 21:18:28.989: start enrollment device 0 finger 7
(fprintd:9225): libfprint-image_device-DEBUG: 21:18:28.989: Activating image device
(fprintd:9225): libfprint-image_device-DEBUG: 21:18:28.989: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(fprintd:9225): libfprint-SSM-DEBUG: 21:18:28.989: [aes2501] ACTIVATE_NUM_STATES entering state 0
(fprintd:9225): libfprint-aeslib-DEBUG: 21:18:28.989: write 38 regs
(fprintd:9225): libfprint-aeslib-DEBUG: 21:18:28.994: all registers written
(fprintd:9225): libfprint-SSM-DEBUG: 21:18:28.994: [aes2501] ACTIVATE_NUM_STATES entering state 1
(fprintd:9225): libfprint-aes2501-DEBUG: 21:18:28.994: read data 1
.......

/var/log/syslog shows

Oct 24 21:28:16 localhost dbus-daemon[1472]: [system] Activating service name='net.reactivated.Fprint' requested by ':1.291' (uid=0 pid=9300 comm="fprintd-enroll <USERNAME> ") (using servicehelper)
Oct 24 21:28:16 localhost dbus-daemon[1472]: [system] Successfully activated service 'net.reactivated.Fprint'

/var/log/messages shows

Oct 24 21:30:52 localhost kernel: [24125.054482] fprintd[9343]: segfault at 8 ip 00007fe5b949231d sp 00007ffd3f0a9780 error 4 in libfprint-2.so.2.0.0[7fe5b946a000+41000]
Oct 24 21:30:52 localhost kernel: [24125.054501] Code: 56 41 55 49 89 fd 41 54 55 48 89 f5 53 48 83 ec 28 89 54 24 04 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 e8 c3 81 fd ff <4c> 8b 75 08 48 8b 5d 00 48 89 44 24 08 4d 85 f6 74 61 31 ed 41 bc

#3 Hardware & System Configuration » Chimaera fresh installation: Issues with fingerprint authentication » 2021-10-24 09:28:48

mmaglis
Replies: 3

I need help to configure my laptop to authenticate using the fingerprint device in Devuan 4.0 Chimaera.
The device ID is supported by libfprint and listed in https://fprint.freedesktop.org/supported-devices.html

I have installed packages fprintd, libfprint-2-2, libpam-fprintd from main repository.
I have tried to follow documentation and information found on the internet, but it does not work.

Command 

fprintd-enroll -f right-index-finger <USERNAME>

is stuck for ever on below messages, despite scanning my fingerprint several times.
It is only interrupted by Ctrl+C.

Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed

Package fprint-demo, used to test the fingerprint device, is no longer available in Devuan 4.0.

What is missing? How can I debug this?

#4 Re: Installation » How to have updated firefox-esr in Chimaera? » 2021-10-23 08:24:39

andyprough wrote:

It would be a terrible shame if you had the unstable version of your favorite browser running perfectly on your stable installation. That would be just awful. Do not try this.

Besides the humor/irony, it all depends how much you value your system and what you are using it for.

If it is only for Firefox, one can simply download and run the desired version directly from upstream source (https://www.mozilla.org/en-US/firefox/a … op-release).
You don't need to mess your system by mixing stable with unstable or resorting to foreign scripts to do it for you.
There are also the updates, proposed-updates and backports repositories that were designed to cover precisely such needs:
https://www.devuan.org/os/packages

That's the sensible and safe thing to do. But you can also skip advise and learn from your own mistakes.
Please make sure you are having fun doing it and no pain ;-)

#5 Re: Installation » How to have updated firefox-esr in Chimaera? » 2021-10-22 11:40:53

I do not recommend mixing package repositories from different releases. It will mess and eventually destroy your system.

This fine page https://www.devuan.org/os/packages explains the use of backports package source.
It is advised to disable backports and only enable to install specific packages.
More advanced users may be able to give backports a lower priority (apt pinning) and install packages by specifying the target release (-t).
Please consult the apt documentation (e.g. man apt-get)

Check if the required Firefox version is in backports.
Alternatively, you can always download and use the latest Firefox version from upstream:
https://www.mozilla.org/en-US/firefox/a … op-release

#6 Re: ARM Builds » Raspberry Pi 2 Model B does not boot » 2020-04-12 10:24:55

tuxd3v wrote:

Does you have a usb-serial cable to do some debug on that Image?
Does you experimented the image here: http://arm-files.devuan.org/

I probably have a usb-serial cable somewhere, but I do not know how to debug. Is there any guide somewhere?
I checked these new beowulf images, but there is none for RPi 2 yet. Nevertheless, I expected an older/tested image on an older RPi version to work smoothly.

#7 ARM Builds » Raspberry Pi 2 Model B does not boot » 2020-04-11 12:08:45

mmaglis
Replies: 4

A RPi 2 Model B does not boot using image file devuan_ascii_2.0.0_armhf_raspi2.img.xz

It shows the initial color screen and then goes blank and stops.
There is no green led activity after this.

Can anyone point me to the right direction?

#8 Re: Off-topic » HyperbolaBSD Roadmap relevance to Devuan » 2020-02-19 15:29:40

Kelsoo wrote:

I believe in 10 years time assimilation in all but name will be complete. (This is the main reason I don't run Devuan as my main system.) There needs to be somewhere for distros to go when this happens.

I am not sure I fully understand your argument here.
Do you mean you do not run Devuan because it will be assimilated in 10 years?
Do you mean Devuan is too close to the "evil" or too small to undo the "evil"?
Where do you see distros going to when this happens?

#9 Re: Off-topic » HyperbolaBSD Roadmap relevance to Devuan » 2020-02-16 18:59:01

mmaglis wrote:

forcing adaptation of software or features without any option to alternatives or the ability to disable them.

By this I do mean hard-coded dependencies in software, but it goes beyond this. Pushing for agendas and platforms, setting default core system software that re-define what GNU+Linux is, without considering interoperability to others. Their interest is to dominate the Linux world with their platforms, tools and architecture.

mmaglis wrote:

It is the effect of commercial interests and the  influence they excercise on so many vital projects for their commercial needs and targets.

I believe this article from Forbes expresses it in more detail: The Impact Of The Tech Giants On Open Source

#10 Re: Off-topic » HyperbolaBSD Roadmap relevance to Devuan » 2020-02-15 21:25:06

chillfan wrote:

It's better for us to just keep releasing Devuan as we have been.

By sharing the information on HyperbolaBSD I wanted mostly to provoke some discussion on the reasons cited by Hyperbola project for their decision; more than the use of a BSD kernel as a viable alternative for Devuan.

Re-reading them (and the thread) after some days, made me realise that the problems that Hyperbola, and many in Devuan, are facing, are not just related to specific misbehaving software packages. It looks to me it is a general trend in the free software world: forcing adaptation of software or features without any option to alternatives or the ability to disable them.

IMHO, this is not something a distribution can solve alone downstream. One would need to not only deactivate some features, but re-engineer/fork an increasing number of problems in an increasing number of projects to continue to support choice and alternatives.

This is a cultural trend permeating a lot of projects and is changing the world of free software as we knew it. It is the effect of commercial interests and the  influence they excercise on so many vital projects for their commercial needs and targets. That is not necessarily a problem by itself. Deliberately excluding others and choice or simiply ignoring the wider community of individual volunteers and users or even smaller commercial contributors is a problem. They are often degrated to just unpaid contributors from being the valued users/customers or members of the volunteer based free software projects.

But I believe not all is lost; far from it. We, the free software users and volunteers, produce the work and can pressure all these upstream projects to change. We must also initiate and contribute to forks and alternative projects when this proves to be the easier or necessary path.

#11 Re: Devuan » Debian considering going systemd init only » 2020-02-12 10:34:47

ChuangTzu wrote:

What's the emoji for broken by design?

Broken by design

#12 Re: News & Announcements » Sources.list broken » 2020-02-06 09:13:20

La riga 1 nel file /etc/apt/sources.list non è corretta (type)
Impossibile leggere l'elenco dei sorgenti.

translates to:

Line 1 in the /etc/apt/sources.list file is incorrect (type)
Unable to read the source list.

Check

  • what is the file's first line. Any funny character?

  • the permissions of the file /etc/apt/sources.list

#13 Re: Off-topic » HyperbolaBSD Roadmap relevance to Devuan » 2020-02-06 09:04:00

I guess such a re-base would have to track a Debian GNU/kFreeBSD distribution.
But that is not even officially supported (dead?) from Debian.

Nevertheless, what is the view on the reasons cited for HyperbolaBSD?
What other ways could be taken to address them if not a "drastic" fork of a BSD distribution?
I feel some of the reasons are important to the Devuan community as well and I would like to know your views or of any existing discussions on these topics.

#14 Off-topic » HyperbolaBSD Roadmap relevance to Devuan » 2020-02-05 13:21:20

mmaglis
Replies: 26

I just came across this announcement from the Hyperbola project to re-base itself on BSD.

https://www.hyperbola.info/news/announc … d-roadmap/

citing the following reasons:

  • Linux kernel forcing adaption of DRM, including HDCP.

  • Linux kernel proposed usage of Rust (which contains freedom flaws and a centralized code repository that is more prone to cyber attack and generally requires internet access to use.)

  • Linux kernel being written without security and in mind. (KSPP is basically a dead project and Grsec is no longer free software)

  • Many GNU userspace and core utils are all forcing adaption of features without build time options to disable them. E.g. (PulseAudio / SystemD / Rust / Java as forced dependencies)

To what extend does Devuan project or members of this forum share the same views on these topics?
Would re-basing Devuan on BSD derived kernel a viable or indeed a desirable move?

#15 Re: News & Announcements » sources.list confusion. » 2020-01-29 20:06:00

golinux wrote:

A better place for that discussion would probably be the devuan-dev mail list.

For completeness of this thread it is worth to mention the below email from devuan-dev list back in 2017:
https://lists.dyne.org/lurker/message/2 … 9d.en.html

Evilham wrote:

We gave the TLS issue a lot of thought and it's not quite doable without
having some sort of control of the servers.

As I suspected, it looks more of an organisational topic rather than technical.
And I also suspect it will not be of higher priority now compared to then...

#16 Re: News & Announcements » sources.list confusion. » 2020-01-28 21:41:28

golinux wrote:

Talk is easy and cheap.   Perceived problems do not magically solve themselves.

Study amprolla3.  When you understand it thoroughly, suggest a solution for consideration.

I found the information in this file (http://pkgmaster.devuan.org/devuan_mirr … hrough.txt) more useful.

6) ENTERING THE deb.devuan.org DNS ROUND-ROBIN

We have put in place a DNS Round-Robin for the domain deb.devuan.org,
which points to all the available package mirrors which can serve
requests for the domanin "deb.devuan.org".

The easiest to have your mirror added to the Round-Robin is to add a
named VirtualHost to your web server conf to serve files for
deb.devuan.org. Sample configuration files for apache and nginx are
available under Section 6.1) and 6.2) below. Please amend them as
necessary, and incorporate them in your webserver configuration. In
particular, be careful in setting the document root and rewrite rules
appropriately.

  *** IMPORTANT: THE DNS ROUND-ROBIN WILL NOT WORK FOR HTTPS ***

It is nevertheless recommended to keep your mirror reachable in
*both* ways, i.e., directly through your own URL and via deb.devuan.org,
since we will also advertise a list of existing mirrors with their                                                                   
corresponding URL (and HTTPS is not supported through deb.devuan.org). 

As usual, please shout if you need help with this configuration.

6.1) Sample apache conf for a deb.devuan.org named virtual host


<VirtualHost *:80>                                                                                                                   
                                                                                                                                     
        ServerName deb.devuan.org                                                                                                     
#### the root must be the folder containing "amprolla.txt"                                                                           
        DocumentRoot /home/mirror/devuan                                                                                             
                                                                                                                                     
        RewriteEngine on                                                                                                             
                                                                                                                                     
        RewriteRule /merged/pool/DEVUAN/(.*) /devuan/pool/$1                                                                         
        RewriteRule /merged/pool/DEBIAN-SECURITY/(.*) http://deb.debian.org/debian-security/pool/$1                                   
        RewriteRule /merged/pool/DEBIAN/(.*) http://deb.debian.org/debian/pool/$1                                                     
                                                                                                                                     
</VirtualHost>

So it looks HTTPS is recommended for direct mirror connections only, but not supported by the DNS round-robin.
The only reasons, I can see, for this are:

  • reaching HTTP or FTP ONLY mirrors via https://deb.devuan.org

  • the mirror does not serve deb.devuan.org through HTTPS due to lack of proper certificate. An Alternative name of deb.devuan.org does not exist in the certificate.

Then you get an error like the one I got:

SSL: certificate subject name (ftp.fau.de) does not match target host name 'deb.devuan.org'

How does Debian work? Some info available if you reach https://deb.debian.org/
Compare to https://deb.devuan.org/

I may be wrong, but it looks to me the problem could be solved by either DNS reconfiguration or by mirror policy change (request suitable certificates?).
I do not see another technical reason for not supporting https with dns round-robin.
Perhaps someone from the authors of the above document can enlighten my ignorance :-)

#17 Re: News & Announcements » sources.list confusion. » 2020-01-28 12:22:58

Jens wrote:

That sounds more like a https proxy.

This solution implies that:

  • the proxy to mirror communication may be unencrypted.

  • the proxy then becomes the bottleneck

To sum up, the problems I want to solve at the same time are:

  • use a mirror round-robin to avoid load on pkgmaster or specific mirrors

  • use HTTPS end-to-end for security and privacy

Current Devuan infrastructure does not allow this.
Any work-around mentioned so far solves either one or the other of my above problems.

If there is some low cost idea of how to achieve both, I can contribute to the extent of my time and abilities.
Thank you for your contributions anyway.

#18 Re: Installation » SOLVED: Stop printers from being added - kill Bluetooth » 2020-01-28 10:34:08

nobodyuknow wrote:

I realize I'm in the minority, however.

By not using avahi you are not in minority by far.
And in fact it does not matter. Everyone has individual needs and with free software and a system like Devuan GNU+Linux you can simply choose what runs in your computer and how.

#19 Re: News & Announcements » sources.list confusion. » 2020-01-28 10:29:09

Jens wrote:

In doubt: there are too few developers to do the work. Though IMHO you are right, https is better.

fsmithred wrote:

We don't have control over the mirrors' choice of providing https or not.

mmaglis wrote:
I think in this day and age HTTPS is a must.
I am suggesting the Devuan project to restrict the round-robin to an "official" list of HTTPS enabled, properly configured and quality checked mirrors and leave all others in an unofficial list.
Is this feasible?

So why not control the mirrors served by round-robin deb.devuan.org and demand HTTPS?
Or alternatively have two round-robins one serving HTTPS only and the other HTTP only.
Is this really a lot of work and not currently feasible?
Are there additional reasons?

#20 Re: News & Announcements » sources.list confusion. » 2020-01-26 15:02:13

fsmithred wrote:
We don't have control over the mirrors' choice of providing https or not.

I think in this day and age HTTPS is a must.
I am suggesting the Devuan project to restrict the round-robin to an "official" list of HTTPS enabled, properly configured and quality checked mirrors and leave all others in an unofficial list.
Is this feasible?

#21 Re: Installation » SOLVED: Stop printers from being added - kill Bluetooth » 2020-01-26 10:47:00

It sounds like your avahi-daemon is picking up networked printers.

From the https://avahi.org

Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. This enables you to plug your laptop or computer into a network and instantly be able to view other people who you can chat with, find printers to print to or find files being shared. Compatible technology is found in Apple MacOS X (branded "Bonjour" and sometimes "Zeroconf").

On a GNU+Linux system look for

man avahi-daemon.conf
man avahi-daemon

The avahi configuration should be found under /etc/avahi directory.

It could be that your CUPS print server is picking avahi discovered printers and creates available print queues for you.
You have a couple of options to handle your issue:

  • disable or remove avahi-daemon, but then you will also loose other discovered services

  • reconfigure CUPS to not pick up any printers discovered by avahi

The CUPS configuration change, should be in the file /etc/cups/cups-browsed.conf

look for and change

BrowseRemoteProtocols dnssd cups 

to

BrowseRemoteProtocols none

Alternatively or additionally you can add the following in the avahi-daemon.conf

use-ipv4=no
use-ipv6=no

but then I am not sure what avahi-daemon will be good at :-)

#22 Re: News & Announcements » sources.list confusion. » 2020-01-26 10:27:07

Jens wrote:

* If you used https:// before, please change to http://.

Noted. I changed my sources.list from HTTPS to HTTP and I confirm package updates work correctly now with deb.devuan.org URL.

This, to a degree, is not secure/private.
Is there any plan to ever make HTTPS round-robin work with all mirrors?

Why is pkgmaster.devuan.org allowing connections from non-mirrors (e.g. clients)?
Isn't there or shouldn't be a kind of mirror registration process that would additionally check the quality of mirror configuration (e.g. certificate)?

#23 Re: News & Announcements » sources.list confusion. » 2020-01-25 19:41:09

I get an error when I switch to deb.devuan.org. It seems besides country codes not working properly so do some of the mirrors...
That was the reason I switched back to pkgmaster.devuan.org at some point in the past.

My sources.list entries:

# Devuan repositories
deb https://deb.devuan.org/merged ascii main
deb https://deb.devuan.org/merged ascii-security main
deb https://deb.devuan.org/merged ascii-updates main
#deb https://deb.devuan.org/merged ascii-backports main

# Devuan sources
deb-src https://deb.devuan.org/merged ascii main
deb-src https://deb.devuan.org/merged ascii-security main
deb-src https://deb.devuan.org/merged ascii-updates main
#deb-src https://deb.devuan.org/merged ascii-backports main

Result of apt-get update:

Ign:28 https://deb.devuan.org/merged ascii-security i386 Contents (deb)
Err:29 https://deb.devuan.org/merged ascii-updates/main Sources
  SSL: certificate subject name (ftp.fau.de) does not match target host name 'deb.devuan.org'
Ign:30 https://deb.devuan.org/merged ascii-updates/main i386 Packages
Ign:31 https://deb.devuan.org/merged ascii-updates/main all Packages
Ign:32 https://deb.devuan.org/merged ascii-updates/main amd64 Packages
Ign:33 https://deb.devuan.org/merged ascii-updates/main Translation-en
Ign:34 https://deb.devuan.org/merged ascii-updates/main i386 Contents (deb)
Ign:35 https://deb.devuan.org/merged ascii-updates/main all Contents (deb)
Ign:36 https://deb.devuan.org/merged ascii-updates/main amd64 Contents (deb)
Ign:37 https://deb.devuan.org/merged ascii-updates i386 Contents (deb)
Ign:38 https://deb.devuan.org/merged ascii-updates amd64 Contents (deb)
Ign:39 https://deb.devuan.org/merged ascii-updates all Contents (deb)
Reading package lists... Done
W: The repository 'https://deb.devuan.org/merged ascii Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://deb.devuan.org/merged ascii-security Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://deb.devuan.org/merged ascii-updates Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://deb.devuan.org/merged/dists/ascii/main/source/Sources  SSL: certificate subject name (ftp.fau.de) does not match target host name 'deb.devuan.org'
E: Failed to fetch https://deb.devuan.org/merged/dists/ascii-security/main/source/Sources  SSL: certificate subject name (ftp.fau.de) does not match target host name 'deb.devuan.org'
E: Failed to fetch https://deb.devuan.org/merged/dists/ascii-updates/main/source/Sources  SSL: certificate subject name (ftp.fau.de) does not match target host name 'deb.devuan.org'
E: Some index files failed to download. They have been ignored, or old ones used instead.

#24 Re: Installation » SOLVED: Stop printers from being added - kill Bluetooth » 2020-01-25 19:28:20

How did you conclude these printers showing up are Bluetooth and not WiFi printers?
Without bluez installed, I do not think any user-space utility will pick up any bluetooth device.

Try reconfiguring avahi or uninstalling the

avahi-daemon

package or disabling the service..

#25 Re: Devuan » Noob wish to help » 2020-01-24 09:03:31

Hi both.

Please also take a look at this thread in this forum for guidance:

https://dev1galaxy.org/viewtopic.php?id=589

It all depends on your skills and desires. Contributing to documentation is a good idea for a newbie without any technical/programming skills.

Board footer

Forum Software