Download | Devuan.org | Git | Bugs | Packages

The officially official Devuan Forum!

You are not logged in.

Pages: 1

#1 Re: Devuan » Is Devuan Daedalus Changing to "Stable"? » 2023-08-15 09:35:38

gipi

Migrated to Daedalus, everything seems fine.

#2 DIY » Functioning headset mic with no dbus/pulseaudio? » 2023-04-07 14:37:48

gipi
Replies: 1

I've been using Devuan with no dbus/pulseaudio/policykit/etc. for few years now, and its great for my uses, but I've always been bugged by my mic. I have a headset, with audio input (mic) going into the pink socket (Line) and audio output going into the green one. Audio output is working normally, no issues here, but audio input works only sometimes.
I can go to alsamixer, screw around the Capture tab, and sometimes I'll be in able to record, but sometimes I won't (this option is more often). This is per reboot. Does anyone know why? This inconsistency is totally unclear to me.

#3 Re: Desktop and Multimedia » Alternative browser for Devuan/Debian - Brave » 2022-07-24 09:06:07

gipi

For those who want IceCat, some guy is making deb packages: see here
If you want 78 (like I do, because of ugly proton), then both this and gnuinos repo's work, but for some reason 91 from gnuinos does not install (due to old dependency versions, though all my packages are up to date), but 91 from lousler works perfectly fine.

#4 Other Issues » "Temporary failure resolving 'deb.devuan.org' " » 2022-07-17 13:07:37

gipi
Replies: 18

For the last three days (at least), apt update does not function. I cannot resolve the URL, even though I am connected to the internet and connection works. Worked perfectly fine few days ago, and i did not remove any relevant package in the meantime. Does anyone know what is happening?

#5 Re: Desktop and Multimedia » sometimes I don't have /dev/dri (and consequently X doesn't work) » 2020-08-18 07:33:51

gipi
fsmithred wrote:

And if this is the problem, I'll tell you how to fix it.

Could you post this solution?

#6 Re: Desktop and Multimedia » sometimes I don't have /dev/dri (and consequently X doesn't work) » 2020-08-13 19:47:55

gipi

Update: I just booted my PC and it failed. Running lsmod | wc -l returned 44 (as opposed to 101 normally). Restarting eudev with /etc/init.d/eudev start/stop did the job.

#7 Re: Desktop and Multimedia » sometimes I don't have /dev/dri (and consequently X doesn't work) » 2020-08-13 15:29:34

gipi
fsmithred wrote:

If this is beowulf, it might be a bug in eudev. It sounds like one I've encountered with live-isos. When it happens to you, is /dev/dri the only thing that's missing?

Instead of rebooting when it happens, try the following (as root):

/etc/init.d/eudev stop
/etc/init.d/eudev start

and see if that fixes it.

Another thing you could do to test is to run 'lsmod | wc -l' to see how many modules got loaded at boot. When eudev fails to find all the devices, it usually registers around half as many as when it works correctly.

And if this is the problem, I'll tell you how to fix it.

Thank you for the response. This is indeed beowulf (to which I moved from debian buster). I don't know whether something else is missing, I looked only for /dev/dri so it is possible.

I'll try these out next time when this happens. I don't know how to replicate the situation, so it may take a while, though.

Current output on a working boot of lsmod | wc -l is 101.

#8 Desktop and Multimedia » sometimes I don't have /dev/dri (and consequently X doesn't work) » 2020-08-13 11:27:39

gipi
Replies: 4

I have no idea why this happens, and it appears to be completely random. Sometimes, though rarely (once in few weeks), /dev populates during boot, but without /dev/dri, so I cannot use X or anything like that. I previously thought it may have to do with updates, drivers, virtualbox even, but it just happens randomly even with all the necessary drivers, totally updated system etc. Is this a bug in eudev? Most of the time, it boots normally and I can use everything normally (and even when it fails, its "fixed" with a reboot), but sometimes, for no apparent reason it fails.

#9 Other Issues » [solved?] [buster to beowulf] issues with dbus, dependencies, I think » 2020-06-22 08:33:03

gipi
Replies: 0

I am having some issues which I do not know how to label or what they even are. I noticed I have libselinux1 package, and since I dont use selinux, I wanted to remove it, however, that prompts for huge amount of other packages to be removed. I then snooped around libselinux1's pages on debian and I got to libpcre3, a package I also dont seem to need but which prompts large amount of other packages to be removed. The package which is the connection is libc6, which yields the same results when attempting to apt purge it.
Another package connected to libselinux1 is libsepol1, which when I attempt to purge gives to following:

# apt purge libsepol1
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:
 gsettings-desktop-schemas : Depends: dconf-gsettings-backend but it is not going to be installed or
                                      gsettings-backend
 libgtk-3-common : Depends: dconf-gsettings-backend but it is not going to be installed or
                            gsettings-backend
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

I looked a bit into gsettings, and trying to remove gsettings-desktop-schemas or libgtk-3-common results in similar situation libselinux1 removal does, except they prompt less packages to be removed and offer these packages to be installed:

libproxy-tools libreoffice-avmedia-backend-vlc libutempter0 libvlc-bin libvlc5 libvlccore9 xterm

Needless to say, packages prompted to be removed are quite important to a functioning system, such as xinit and xorg.

I did a bit of more digging and thought this may have to do with dbus and I attempted to remove dbus, but following happens:

# apt purge dbus
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:
 glib-networking : Depends: gsettings-desktop-schemas but it is not going to be installed
 libgtk-3-common : Depends: dconf-gsettings-backend but it is not going to be installed or
                            gsettings-backend
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

I did dpkg --configure -a but there was no output.
Happened on fully updated beowulf to which I recently migrated from debian buster

Edit: grammar

Edit 2: I have installed gconf-gsettings-backend which enabled me to remove dbus (and stuff that depends on it, including dconf packages). Using aptitude I saw that a lot of important packages depend on libselinux1 and libsepol1, so they're staying. BUT, attempting to purge libselinux1 with apt gives some dependency issues with adduser, dconf-service and libglib2.0-0. Trying to purge libsepol1 prompts the removal of 65 packages (including apt). apt -f install and dpkg --configure -a report not packages. So, I guess it is solved

#10 Re: Other Issues » [SOLVED] libsystemd0 remains » 2020-06-13 07:42:48

gipi

UPDATE

After upgrading the linux kernel image (from 4.19.0-8 to 4.19.0-9), I had to move to libelogind0 because X would break, thus removing libsystemd0.
In relation to my previous post, consolekit and policykit-1 didnt have anything to do with fixing the error.

#11 Re: Other Issues » [SOLVED] libsystemd0 remains » 2020-06-04 20:03:07

gipi
golinux wrote:

Why are systemd files present in Devuan?

That was before elongind replaced libsystemd.  There shouldn't be any libsystemd0 in beowulf.

Technically, there isn't, its a dummy package, but its there as a package.

#12 Re: Other Issues » [SOLVED] libsystemd0 remains » 2020-06-04 18:14:20

gipi
Head_on_a_Stick wrote:

Yeah, that looks fine — the only package slated for removal is libsystemd0, which is replaced by libelogind0.

Go ahead and run that command as root and without the --simulate switch.

Turns out it wasn't ok. I rand the command and rebooted and X wouldn't work (Can't run in framebuffer mode).
I ended up reinstalling libsystemd0, which installed consolekit and some other libraries (consolekit libcgmanager0 libck-connector0 libnih-dbus1 libnih1 libpam-ck-connector libpolkit-agent-1-0 libpolkit-backend-consolekit-1-0 libpolkit-gobject-consolekit-1-0, I think - got these by seeing what happens when I attempt to purge policykit-1) which removed elogind.
I will just stick with this now.

#13 Re: Other Issues » [SOLVED] libsystemd0 remains » 2020-06-04 17:43:27

gipi
Head_on_a_Stick wrote:
gipi wrote:

However, when attempting to install elogind (or packages dependent on it, such as pulseaudio), apt states that libsystemd0 will be removed.

The elogind package replaces systemd-logind and provides libelogind0 so that should be fine.

If you're not sure then check (or post) the full output of

apt install --simulate elogind

I ran the command. Here is the output:

# apt install --simulate elogind
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libelogind0 libpam-elogind libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-backend-elogind-1-0 libpolkit-gobject-1-0 libpolkit-gobject-elogind-1-0
  policykit-1 policykit-1-gnome
The following packages will be REMOVED:
  libsystemd0
The following NEW packages will be installed:
  elogind libelogind0 libpam-elogind libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-backend-elogind-1-0 libpolkit-gobject-1-0
  libpolkit-gobject-elogind-1-0 policykit-1 policykit-1-gnome
0 upgraded, 10 newly installed, 1 to remove and 0 not upgraded.
Remv libsystemd0 [241-7~deb10u4] [xserver-xorg-core:amd64 sane-utils:amd64 libapt-pkg5.0:amd64 libprocps6:amd64 rsyslog:amd64 samba-libs:amd64 xserver-xephyr:amd64 libpulse0:amd64 ]
Inst libelogind0 (241.4-2 Devuan:3.0/stable [amd64])
Conf libelogind0 (241.4-2 Devuan:3.0/stable [amd64])
Inst elogind (241.4-2 Devuan:3.0/stable [amd64])
Inst libpam-elogind (241.4-2 Devuan:3.0/stable [amd64])
Inst libpolkit-gobject-elogind-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Inst libpolkit-gobject-1-0 (0.105-25+devuan8 Devuan:3.0/stable [all])
Inst libpolkit-agent-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Inst libpolkit-backend-elogind-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Inst libpolkit-backend-1-0 (0.105-25+devuan8 Devuan:3.0/stable [all])
Inst policykit-1 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Inst policykit-1-gnome (0.105-7 Devuan:3.0/stable [amd64])
Conf elogind (241.4-2 Devuan:3.0/stable [amd64])
Conf libpam-elogind (241.4-2 Devuan:3.0/stable [amd64])
Conf libpolkit-gobject-elogind-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Conf libpolkit-gobject-1-0 (0.105-25+devuan8 Devuan:3.0/stable [all])
Conf libpolkit-agent-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Conf libpolkit-backend-elogind-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Conf libpolkit-backend-1-0 (0.105-25+devuan8 Devuan:3.0/stable [all])
Conf policykit-1 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Conf policykit-1-gnome (0.105-7 Devuan:3.0/stable [amd64])
#

I don't actually need elogind (or at least I think I don't), I don't use GNOME, KDE or Wayland. I do however use some gnome icon themes (gnome-extra-icons, gnome-icon-theme, gnome-themes-extra and libsoup-gnome2.4-1), is that related? I can't remove these either because they too pull xorg with them (nor do I want to, I am using arc-theme which depends on gnome-themes-extra).

#14 Other Issues » [SOLVED] libsystemd0 remains » 2020-06-04 15:59:25

gipi
Replies: 11

I have migrated from Buster to Beowulf, but before I migrated, I already had systemd replace by sysv-init. When I migrated, I managed to remove most of remaining systemd related stuff, but libsystemd0 can't be removed directly because it pulls with itself 54 other packages, including (but not limited to) xorg, xinit and apt.
However, when attempting to install elogind (or packages dependent on it, such as pulseaudio), apt states that libsystemd0 will be removed. I have not followed through with installing elogind, so I don't know if removing libsystemd0 this way would have the same effect as directly attempting to remove it.

#15 Re: Other Issues » Grub entry stays as debian after migrating from buster » 2020-06-03 20:42:30

gipi
larsH wrote:

Hi

This is because the kernel is signed with the debians secureboot key. If you are using secure boot do NOTHING. If you are NOT using secure boot I am sure it is safe to do the following. Edit /etc/default/grub and change the name to whatever you prefer update your initrd. (in a terminal run as root update-initramfs -u) and on next boot it will have that name even if it is Donald Duck.

Have a nice day
lars H

Just checked, and yes I do have secure boot enabled.

Thank you for the response.

- me

#16 Other Issues » Grub entry stays as debian after migrating from buster » 2020-06-03 19:13:51

gipi
Replies: 2

Not really much of an issue, but after migrating from Buster, GRUB lists the boot option as Debian GNU/Linux.
Anyone know why?
This doesn't cause any issues otherwise, selecting Debian boots normally into Devuan.

Pages: 1

Board footer

Forum Software