The officially official Devuan Forum!

You are not logged in.

#1 Re: Desktop and Multimedia » In search of a privacy oriented browser » 2018-09-19 16:23:31

miroR wrote:

Another one would be: I want SSL-logging, as I always want to check what happened online.

Anybody knows that would be workable with Otter?

You should ask Emdek about that on Otter's IRC channel.

miroR wrote:

Linux users can use the official AppImage version available on SourceForge. It is a single executable file that doesn’t need any dependencies to be installed. The AppImage version should run under any system installed after 2012 provided it has OpenSSL 1.0.x (not 1.1.x) and GStreamer 1.x (with codecs). The browser is also available in the repositories of a wide range of Linux distributions and *BSD systems. Read more on the dedicated wiki page.

(but I haven't reproduced all the links of the text)

And, I have:

# apt-cache policy openssl
  Installed: 1.1.0h-4
  Candidate: 1.1.0h-4
  Version table:
 *** 1.1.0h-4 500
        500 tor+http://devuanfwojg73k6r.onion/merged testing/main amd64 Packages
        100 /var/lib/dpkg/status

UPDATE: I actually downloaded:
1d7058c1972442c72f0904c6b7f3ad9f25dbb11c257d918c857eb74ccb8031fe  otter-browser-
(the SHA256 is in view of verification; how do AppImage's verify?)
and only then took notice my openssl is too new. A no go for me, not messing with such important packages as openssl.

The bigger problem is that Otter Browser requires at least Qt 5.10, which is not in ASCII. But if you had that, it would be possible to built it against openssl 1.1 as well, says the main developer. (I haven't tried that, though.)

miroR wrote:

But why are there no Debian packages?

One reason is probably that, up to now, the project has only published release candidates.

On a non-privacy-related side note: Otter also doesn't depend on Pulseaudio.

#3 Re: Hardware & System Configuration » How to install nvidia CUDA on ASCII? » 2018-06-27 13:43:52

Dutch_Master wrote:

@msi: he'd already stated he's on Ascii, as per the title of the thread tongue

Must have been concentrating on the small stuff so much that I totally overlooked that... big_smile

#4 Re: Hardware & System Configuration » How to install nvidia CUDA on ASCII? » 2018-06-26 20:59:23



First, please use [ code ] tags instead of just [ c ] for code blocks. Thanks.

On topic:

1. Which Devuan distribution are you using? Jessie, ASCII, Beowulf, Ceres?

2. What does apt-cache search cuda give you?

#5 Re: Hardware & System Configuration » basic_config » 2018-06-25 15:03:46

msi wrote:

I assume this is because mate-power-manager is currently not available. But that should be fixed soonish.

There you go: … 89.en.html

Running apt-get update will make the package available. Please report if installing it solves your problem.


#6 Re: Hardware & System Configuration » basic_config » 2018-06-24 13:33:55

teaman wrote:

My sources.list shows:

deb ascii main
deb ascii-updates main
deb ascii-security main
deb ascii-backports main

Is this correct?

If not, why did it install that way?

It's not wrong, but as the release notes state, you should rather use It will enable Devuan to do some load balancing. See:

How did you install?

teaman wrote:

I read in the release notes at

Starting from Devuan 2.0 ASCII, users should use exclusively
"" or ""{CC}" in their 'sources.list'
file, e.g.:

deb ascii main
deb ascii-security main
deb ascii-updates main
deb ascii-proposed main

So do I need to change my sources.list at this time and if so, what about backports?

You don't have to change that, obviously. But, for the reason mentioned above, it would be nice if you did. Use backports only if you need a particular package to be newer than the one coming with the stable distribution. If you don't, it's probably the best to comment that line.

I have no idea what thus ascii-proposed is ... will give you a clue.

teaman wrote:

Puzzle(2) My screen keeps going black.

I have to repeatedly shake my mouse whilst I am watching a film, which is most distracting and irritating.

On Devuan Jessie with Mate desktop, I went to System/Preferences/Look and Feel/Screensaver and set: "Regard the computer as idle after 2 hours" and there was no problem.
Now on Devuan ascii with Mate desktop, this screensaver function does not work.

I assume this is because mate-power-manager is currently not available. But that should be fixed soonish.

teaman wrote:

Is there a command-line remedy to stop the screen going black?

There is:

/usr/bin/xset s off && /usr/bin/xset -dpms

man xset gives an explanation of what that does.

#7 Re: Off-topic » Music » 2018-06-20 22:18:05


Ok, here's another one:

Smashing Pumpkins – Doomsday Clock

Definitely one of my all-time favorites of their songs. I especially like this live performance. It's a lot more powerful than the album recording.

#8 Re: Devuan » Devuan ASCII reviewed on DistroWatch Weekly » 2018-06-19 16:39:04


A few comments on this:

On the desktop are icons for opening the file manager, reading the distribution's release notes, launching the installer and changing the desktop font sizes. [...] Unfortunately, the text labels under the desktop icons do not handle being resized well. When we first start using Devuan, the text under the icons reads "Small", "Large" and "_Release Notes". Increasing the size one notch makes the text read "SM", "LA" and "_RE".

Can this be confirmed by anyone?

Devuan has its own system installer.

That's not exactly right. Devuan installation images use a modified version of the Debian Installer. But this will probably change in the future as there are plans to create a new installer for Devuan.

Installing from a Devuan live system, you will, however, be using Refracta Installer[1]. So, all the installer-related issues mentioned in that review apply to Refracta Installer only, not to Devuan's version of the Debian installer.

Devuan supports working with just the ext2/3/4 file systems.

Untrue. The installer used by the installation images also offers Btrfs, JFS and XFS. You can even format drives and partitions with FAT16 and FAT32. Refracta Installer might, however, have some limitations here.

We are asked which language locales should be set up, with options being pulled from a cryptic list with entries like "en_US.UTF-8". We then select our keyboard layout from a similar set of lists.

Again, this is not true if you don't install from within a live system. Just like the original, Devuan's version of the Debian Installer will let you choose your language and locale in a straightforward and totally non-cryptic manner.

Devuan ships with an unusual combination of popular open source applications and some less common programs. Popular items include Firefox, LibreOffice, the GNU Image Manipulation Program and the VLC media player. But then we are also given the lesser known Quod Libet music player, the Ex Falso media tag editor and the mutt terminal e-mail client. The Orage Calendar application, a PDF document viewer and printer manager are present too. The Thunar file manager is included along with a tool to rename groups of files and there is a process monitor. Devuan ships with the Wicd network manager to help us get on-line.

Devuan ships whatever Debian ships, except that packages dependent on systemd are either rebuilt to work without it or simply banned.

Devuan ships Firefox, but then its counterpart is the mutt console e-mail program which feels entirely out of place with the rest of the desktop software.

Well, that's apparently because task-xfce-desktop will not install an e-mail client and mutt being in the default install. Not a big deal, IMO.

Having a fairly large repository of software available along with Flatpak support provided a solid collection of applications on a conservative operating system foundation.

I think it's kind of wrong to name Devuan a "conservative" distribution. It's not about just keeping everything as it is. If it was, why would it offer OpenRC as an alternative to SysVinit, for example?

Richard wrote:

The choice is to decide whether to create a base system for distro developers, a sys admins system or a system that might please everyone. Or something in between whatever that might be.

I'd say there is no decision to be made here, since, just like Debian, Devuan aims to provide a "universal operating system".

1 … README.txt

#9 Devuan » Devuan ASCII reviewed on DistroWatch Weekly » 2018-06-18 22:37:49

Replies: 15

Issue 768 of DW Weekly brings a review of Devuan 2.0 ASCII, but one that's kind of odd: … 618#devuan

#10 Re: Installation » [Solved] Ascii upgrade (also) messed up this Devuan Jessie » 2018-06-18 13:03:54

Altoid wrote:
msi wrote:

How about reading those ASCII release notes?

I have read them.
But have not been able to identify anything specific that would help me solve this.
At least not with my level of exposure to Linux.

Perhaps you could point out anything I may have (surely) missed?

Well, you wrote that using startx, you get "the full desktop but still no Kb or mouse". This could simply be because the Xserver freezes on start-up and may have nothing to do with your keyboard and mouse at all. You need to read the section "Starting X from a console (TTY)".

#11 Re: Devuan Derivatives » Refracta no-dbus experiment » 2018-06-17 19:35:58

fsmithred wrote:

The subject of running without dbus comes up from time to time in various places.

One of those places being the Friends of Devuan Wiki: … e_software

#12 Re: Desktop and Multimedia » MATE 1.20 on devuan ascii » 2018-06-17 19:22:08

colby wrote:
msi wrote:

So, mate-power-manager here is a third-party package that has apparently been rebuilt so it won't depend on systemd and network-manager is a genuine Devuan package that has been forked from Debian in order to eliminate the systemd dependency.

I have not looked at the source code or queried the maintainers for these packages, therefore I can not give you an authoratative answer to your question.

Just to clarify: I wasn't asking a question there. I just wrote „apparently“ because I didn't have time to check the changelog for AntoFox's mate-power-manager package and therefore be absolutely sure about my statement. But then, it's pretty obvious that it's providing a modified version of mate-power-manager that doesn't depend on systemd. I've also looked at the changelog now to verify that.

#13 Re: Installation » [Solved] Ascii upgrade (also) messed up this Devuan Jessie » 2018-06-17 19:01:54

Altoid wrote:
Altoid wrote:

I was able to start X, got the full desktop but still no Kb or mouse (it's plugged into the USB Kb).
So the problem persists.  =^/


How about reading those ASCII release notes?

#14 Re: Desktop and Multimedia » MATE 1.20 on devuan ascii » 2018-06-14 15:25:57

colby wrote:

Both power manager and network manger run on devuan Mate-1.20. I installed them from devuan repositories and hezeh, as listed in my source.list file which follows.


These are the packages I have installed and running on my system:

gnome-power-manager                       3.22.2-2
mate-power-manager                          1.20.0-1+hezeh1
mate-power-manager-common           1.20.0-1+hezeh1

network-manager                                1.6.2-3+devuan1.1
network-manager-gnome                    1.4.4-1

So, mate-power-manager here is a third-party package that has apparently been rebuilt so it won't depend on systemd and network-manager is a genuine Devuan package that has been forked from Debian in order to eliminate the systemd dependency.

#15 Re: Desktop and Multimedia » MATE 1.20 on devuan ascii » 2018-06-13 16:30:54

colby wrote:

I've read that both mate-power-manager and mate-network-manager are dependent upon systemd.

Neither of those packages exist in Devuan. The latter doesn't even exist in Debian. AntoFox should be able to explain how network configuration and power management for MATE are being handled in Devuan.

colby wrote:

Systemd is not running on my system. There is an /etc/systemd directory with a few entries none of which concern mate-power-manager. There is some networking window dressing, but how these files are used without systemd is unclear to me. Systemd became a Gnome project dependency in 2011. All I know about systemd is I don't want to run on a system that is dependent on it.

I think you should read

#16 Re: Installation » [Solved] Ascii upgrade (also) messed up this Devuan Jessie » 2018-06-13 00:03:15

Altoid wrote:

Thanks a lot.  8^)

Normally, you would have an entry for booting into runlevel 1 in your GRUB boot menu as well. But from your description it seemed like it's not there on your system.

Altoid wrote:

In contrast to what I was used to with MS OSs, I've never had to do go to recovery mode with my Linux installations.
It's actually the first time.

It's actually called "single-user mode". Ubuntu calls it "recovery mode"... (mea culpa)

devuser wrote:

Beyond that it might be an idea to try narrowing the problem down. I'd try disabling slim (i guess this should work: update-rc.d slim disable) and see if your keyboard works after a normal boot. If it does try startx. If it still works clearly slim is the culprit.

I would have suggested the same. However, you might want to do yourself the favor of reading the section on "Starting X from a console (TTY)" in the ASCII release notes before you use startx to start X.

#17 Re: Installation » [Solved] Ascii upgrade (also) messed up this Devuan Jessie » 2018-06-12 20:30:59

Altoid wrote:

Can't see how to get into recovery mode, the keyboard is not responsive.

When the GRUB menu shows up, select Devuan, but don't hit Return. Type e instead. Now you should see a bunch of text containing a line somewhere reading somehting like:

linux   /vmlinuz-4.9.0-6-686-pae root=UUID=810cd705-55b6-4ce2-a414-76e16ce125f4 ro  quiet

It may be wrapped if it's too long to fit the screen. Anyway, navigate to the end of that line, then insert 1. Then hit F10 to boot. The boot process should pause at a certain point and you should be asked to enter your root password for manitenance (or type Ctrl+D to continue). Enter your root password and hit Return. There you are in runlevel 1 or "recovery mode". You won't have to change that GRUB configuration back because it's not permanent.

Altoid wrote:

I'm not complaining but as it is a default Jesse (SLiM and XFCE) installation upgrade I expected no major hickups save maybe the Nvidia drivers acting up.

What do you mean by "upgrade"?

#18 Re: Hardware & System Configuration » Problems with NTP and network config after upgrade » 2018-06-12 17:39:38

msi wrote:

I temporarily replaced the current verison of the file with that from Jessie to see if it would make any difference and it didn't. So, the root of the problem must be somewhere else.

Well, maybe not. I've found that throwing out /etc/dhcp/dhclient-exit-hooks.d/ntp will make both of the error messages mentioned above go away. So, the one on boot is obviously also triggered by it. There will, of course, be no automatic handling of ntp restarts on DHCP events if the file is missing.

I've been trying to understand what this script really does and I kind of do. But the ntp_servers_setup function is still a mystery to me. Where does it get the value for $reason? It's simply not defined within the script. And neither are $new_ntp_servers and $old_ntp_servers, which are used in the ntp_servers_setup_add function.

Here's the entire file:


ntp_server_restart() {
	invoke-rc.d ntp try-restart

ntp_servers_setup_remove() {
	if [ ! -e $NTP_DHCP_CONF ]; then

ntp_servers_setup_add() {
	if [ -e $NTP_DHCP_CONF ] && [ "$new_ntp_servers" = "$old_ntp_servers" ]; then

	if [ -z "$new_ntp_servers" ]; then

	tmp=$(mktemp "$NTP_DHCP_CONF.XXXXXX") || return
	chmod --reference=$NTP_CONF $tmp
	chown --reference=$NTP_CONF $tmp

	  echo "# This file was copied from $NTP_CONF with the server options changed"
	  echo "# to reflect the information sent by the DHCP server.  Any changes made"
	  echo "# here will be lost at the next DHCP event.  Edit $NTP_CONF instead."
	  echo "# NTP server entries received from DHCP server"
	  for server in $new_ntp_servers; do
		echo "server $server iburst"
	  sed '/^[[:space:]]*\(server\|peer\|pool\)[[:space:]]/d' $NTP_CONF
	) >>$tmp
	mv $tmp $NTP_DHCP_CONF


ntp_servers_setup() {
	case $reason in


#19 Re: Installation » Black Screen on Devuan Ascii - acpi=off solves it (undesirable) » 2018-06-12 15:46:03


As far as starting X from a TTY goes, there's some important info in the ASCII release notes:

### Starting X from a console (TTY)

In Devuan 2.0 ASCII, the X server no longer requires to be run with
root privileges. As a consequence, there are some additional
requirements to be met when launching X directly from a TTY (i.e.,
through 'xinit' or 'startx'), especially on systems upgraded from
Devuan Jessie.

In Devuan 2.0 ASCII it is sufficient to install 'elogind' and
'libpam-elogind', and then use either 'startx' or 'xinit' as usual
from a regular user account. In this case, the Xorg log file will be
available under '~/.local/share/xorg/'.

The system still needs to support Kernel Mode Setting (KMS).
Therefore, this solution may not work in some virtualization
environments (e.g.  virtualbox) or if the kernel has no driver that
supports your graphic card.

Alternatively, it is still possible to run X with setuid root. In this
case, you need to install `xserver-xorg-legacy` and ensure that the
file '/etc/X11/Xwrapper.config' contains the (uncommented) line:


If you have neither of the above configurations, X will freeze immediately after you start it.

#20 Re: Installation » [Solved] Ascii upgrade (also) messed up this Devuan Jessie » 2018-06-12 15:19:53


Does the keyboard respond when you boot the system in recovery mode?

What login manager are you trying to use?

#21 Re: Installation » Installation failure for specific locale (gr) [SOLVED]. » 2018-06-12 15:10:52



a few questions about this:

1. At which point exactly did the installation fail?

2. Was there an error message?

3. Can you reproduce the problem?

#22 Re: Hardware & System Configuration » Problems with NTP and network config after upgrade » 2018-06-06 08:42:12


That script seems to be there to make sure NTP is being restarted automatically when bringing up and down network interfaces that get their IP address through DHCP.

I've dug a little deeper and found that it has been part of the ntp package at least since Debian Wheezy. Also, it's identical in the Wheezy and Jessie packages, but has seen minor changes in Stretch.

These are:

1. Line 2 was changed from




2. Line 43 was changed from

sed -r -e '/^ *(server|peer).*$/d' $NTP_CONF


sed '/^[[:space:]]*\(server\|peer\|pool\)[[:space:]]/d' $NTP_CON

I temporarily replaced the current verison of the file with that from Jessie to see if it would make any difference and it didn't. So, the root of the problem must be somewhere else.

#24 Hardware & System Configuration » Problems with NTP and network config after upgrade » 2018-06-04 20:08:08

Replies: 4

Since I have upgraded from Jessie to ASCII, I'm getting the following warning about NTP on shutdown, which is apparently somehow connected to network device configuration:

DHCPRELEASE on wlan0 to port 67
invoke-rc.d: -----------------------------------------------------
invoke-rc.d: WARNING: 'invoke-rc.d ntp try-restart' called
invoke-rc.d: during shutdown sequence.
invoke-rc.d: enabling safe mode: initscript policy layer disabled
invoke-rc.d: -----------------------------------------------------

I hadn't heard of invoke-rc.d before, so I looked it up. The manual page says it's "a generic interface to execute System V style init script /etc/init.d/name actions" and that "all access to the init scripts by Debian packages' maintainer scripts should be done through invoke-rc.d".

I had initially tried to solve the problem by editing /etc/init.d/ntp. But that doesn't seem right, so I restored the original file from backup.

How can I find out now what is calling invoke-rc.d ntp try-restart during shutdown and why?

As for this issue being connected to the network device settings, I've found the following: When I use auto wlan0 instead of allow-hotplug wlan0 in /etc/network/interfaces (where I do all my network configuration), I'll get this during boot:

DHCPDISCOVER on wlan0 to port 67 interval 5
DHCPREQUEST of on wlan0 to port 67
DHCPACK of from
invoke-rc.d: could not determine current runlevel
bound to -- renewal in 400249 seconds.

First, these messages are not shown when using the allow-hotplug configuration. In that case, all that is shown of the network device configuration during boot is:

Configuring network interfaces...ifup: waiting for lock on /run/network/ifstate.wlan0
ifup: interface wlan0 already configured

Second, there's an error message in there. And even though I understand what it says, I have no clue what to do about that.

The warning message displayed on shutdown is the same in both cases.

Any ideas?

#25 Re: Installation » Ascii upgrade messed up the devuan jessie » 2018-06-04 18:51:53

golinux wrote:
msi wrote:

Btw, it's a good idea to use code tags when posting config files. That makes it more readable.

Done (for the second time).

Looks like something to mention in a forum code of conduct to be. wink

Board footer

Forum Software