The officially official Devuan Forum!

You are not logged in.

#1 Re: Other Issues » gnome compile issue » 2020-12-09 14:30:52

anticapitalista wrote:

Sorry, I meant this problem you are having with;

libelogind0 : Conflicts: libsystemd0

not the brightness issue.

It worked after I used equivs to "install" libsystemd-dev, even though I gave it elogind's older version number. GNOME won't compile with elogind anyway, and when running the binary in Ceres/Sid several things are broken. It is getting harder and harder to like GNOME and not like systemd sad

#2 Re: Other Issues » gnome compile issue » 2020-12-09 14:21:19

Ok, so the reason is that elogind's header files are in /usr/include/elogind instead of /usr/include/systemd, meaning that anything that compiles against systemd needs to be modified, and even then it might not work. I don't know why I didn't think of it.

I think this is by design; applications are supposed to build
against the systemd headers and then, if they only use functions
also exposed by libelogind0 they can also run with that.

As Thorsten has already suggested, this is by design. Debian packages are only
built against libsystemd-dev. The libelogind0/libsystemd0 compatibility is a
*runtime* option, not compile-time. We don't even know (and can't test) if all
of the source packages depending on libsystemd-dev will compile against
libelogind-dev.

> Please add Provides: libsystemd-dev to control.

This would be both unwise and counter-productive. Having libelogind0 provide
libsystemd0 was a very controversial move and getting it accepted into Bullseye
a hard won victory. I am very reluctant to do anything that might jeopardise
that.

If you have an libelogind0 system and need to compile against libsystemd-dev,
please use one of the various build chroots or containers. This requirement is
already documented in libelogind0's README.Debian.

#3 Re: Other Issues » gnome compile issue » 2020-12-08 20:12:20

also, this is unrelated but while chrooting into debian, I noticed package init now depends on systemd-sysv | sysvinit-core? where did runit-init go?

#5 Re: Other Issues » gnome compile issue » 2020-12-08 18:06:59

Ok, I am reporting bug into libelogind-dev from chroot.

#6 Re: Other Issues » gnome compile issue » 2020-12-08 17:43:09

I have QEMU machine. Will that work?

#7 Re: Other Issues » gnome compile issue » 2020-12-08 17:32:57

Head_on_a_Stick wrote:

I've just unpacked the .deb in my Alpine Linux system and checked tongue

ah, good idea. I also checked antiX and it has the same issue. I file bug report into Debian BTS?

#8 Re: Other Issues » gnome compile issue » 2020-12-08 17:19:41

Thank you for helping, the problem is now I left that laptop alone and when I came back I cannot get it to boot.

# apt update
apt source gnome-settings-daemon

Yes, this is what I am doing. (although I am using apt-get)

You shouldn't have to do that at all, the libelogind0 package has Provides: libsystemd0.

Hmm, maybe libelogind-dev does not provide libsystemd-dev? I am unable to check currently because this computer is using antiX. EDIT: or libeudev-dev does not provide libudev-dev?

Also, I forgot to mention, that was on Devuan Ceres. I believe brightness control is working in Beowulf.

#9 Other Issues » gnome compile issue » 2020-12-08 16:13:38

dzhigit
Replies: 16

I am trying to compile gnome-settings-daemon with this patch to fix brightness control issue, but it gives this error

../meson.build:96:0: ERROR: Dependency "gnome-desktop-3.0" not found, tried pkgconfig

so I tried

$ LANG=C apt-get install libgnome-desktop-3-dev -s
NOTE: This is only a simulation!
      apt-get needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libelogind0 : Conflicts: libsystemd0
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

How can I change dependency on libsystemd-dev and libudev-dev to libelogind-dev and libeudev-dev?

#10 Re: Installation » two questions, new to Devuan » 2020-11-12 22:23:16

caieng wrote:

SOLVED:  sound works now, after reading RELEASE NOTES, and editing the obscure, incomprehensibly named file "00-disable-autospawn.conf", to REMOVE (unintuitive--why would anyone have to comment out a line of code to enable something to work, normal software engineering works in just the opposite fashion, edit a file to add something desired--here we are removing a constraint which prevents what we NORMALLY expect, from happening.) Devuan demands that every user insert a pound sign, " # " in a line of code in a configuration file, to be able to hear sound as expected. 
That's just too much 1960's architecture for my taste.  I am seeing cold rooms with big tape drives, and heavy security to access the wonderful IBM hardware.  NOT for me.

(Editing this silly file is certainly not required to hear music, in running Cinnamon on any other distro, that I have used, e.g. Mint 17.1, Debian Squeeze.)

Pulseaudio
- If you have no sound, make sure the following line in
   /etc/pulse/client.conf.d/00-disable-autospawn.conf is commented as
   shown here:
   #autospawn=no

In other words, the much vaunted, highly touted "RELEASE NOTES", illustrate how that line in the file must look, AFTER editing, by each user of Devuan.   BEFORE editing, that line of text reads like this:
   autospawn=no

To listen to music, with Devuan, but not other Cinnamon versions, one must insert a pound sign into a line of text, to disable that text.

I am very keen to learn which page of Donald Knuth's "The Art of Computer Programming, volume I", corresponds to this notion, demanding that users comment out a line of code in order for a particular function to work as one normally would anticipate, upon successfully completing an installation of Devuan.

Why would several forum participants request/demand "relevant troubleshooting information", to solve this problem?

What is the difference between ADDING a pound sign in front of a line of code not required, vs, changing the code to read:
   autospawn=yes

?
What is it about "system D" that enables that collection of code to permit the user to hear music at once, upon completing the installation, vs whatever it is that Devuan uses to replace "system D", i.e. why should "system D" enable sound, but not whatever it is that Devuan is using?

caieng

PulseAudio needs to be started for it to work. Most distributions, including Debian, are using systemd to start PulseAudio. This is not an option in Devuan. The alternative is PulseAudio's in-built autospawn feature, which automatically starts PulseAudio when audio is played, if PulseAudio is not already running. Debian sets autospawn=no because it is using systemdumb. Most of the packages in Devuan are copied from Debian. Therefore, Devuan inherits autospawn=no from Debian. Devuan's small team of volunteers only makes the necessary changes to remove systemd. If you want autospawn=no to be commented, or autospawn=yes by default, you can persuade one of the volunteers to fork PulseAudio and repackage with that setting, or do it yourself. There is no difference between autospawn=yes and a commented autospawn=no because PulseAudio's default is autospawn=yes. That is why you comment something out in order to enable a feature, because the feature was explicitly disabled, so you are setting it back to the implied setting. In order to prevent any update from overriding that file, I created a new file, /etc/pulse/client.conf.d/01-enable-autospawn.conf, with the single line autospawn=yes. This file overrides whatever is in 00-disable-autospawn.conf because it starts with a higher alphanumeric character. AFAIK, most Devuan and anti-systemd users are using ALSA instead, and apulse can be used as a compatibility layer.

#11 Re: Desktop and Multimedia » High CPU by PulseAudio » 2020-11-12 21:57:18

Copper36 wrote:

2. A bunch of smaller things, that still might be very important. For example, you one needs PA in order to share sound in ZOOM.

There is a package called apulse which provides a partial implementation of the PulseAudio API for ALSA. The command looks like

apulse zoom

maybe it will fix the issue.

#12 Re: Desktop and Multimedia » Firefox outdated » 2020-11-09 19:35:06

The latest version of the firefox-esr package in beowulf is also 78.4

Hmm, I wonder why the site says he is running version 68.0. Then the options are to install Firefox (non ESR) from mozilla.org, antiX/MX, or upgrade to Ceres.

#13 Re: Desktop and Multimedia » Firefox outdated » 2020-11-09 02:39:27

You are using Firefox ESR from Beowulf. The latest version of Firefox ESR in Ceres and from mozilla.org is 78.4. You could download from mozilla.org, manually copy the files over and make the .desktop entry. Firefox (non ESR) is packaged in the antiX Linux and MX Linux Debian-compatible stable releases, as well as in Flathub which works with any distribution. I use Ceres anyway but in your situation I would choose from one of these options or compile GNU IceCat from source. And see the Debian wiki page for Firefox: https://wiki.debian.org/Firefox/.

#14 Desktop and Multimedia » gnome-software and plasma-discover not working » 2020-11-08 17:24:26

dzhigit
Replies: 0

We discussed this issue on #devuan freenode IRC on 2020-11-04 (Wednesday) and 2020-11-07 (Saturday). It can be viewed in the public archives. gnome-software and plasma-discover are the software centres for GNOME and KDE respectively. They are working in Debian but not in Devuan. Neither one has been forked by Devuan, so these are unmodified Debian versions. The packagekit backend that they use is working, as well as GNOME's alternative software center gnome-packagekit. The issue seems to be with appstream, which is the freedesktop.org software responsible for the application details, like the name, icon, screenshots, description, etc. Apparently this metadata is missing from Devuan. Both app centres are able to show information for installed applications, but they are not able to search for other applications. Also in GNOME, right clicking an application and then clicking "Show Details" opens software center and says "No Application Data Found," but selecting an application from within the software center shows all of its details, although some screenshots are missing.

Board footer

Forum Software