You are not logged in.
Step 1:
Check that
libpam-elogind, elogind, libelogind0, libpolkit-backend-elogind-1-0,
libpolkit-gobject-elogind-1-0 and policykit-1 is *installed*.
I am using LightDM and I don't have those packages installed, except for policykit-1. I am also using Xfce, and the "Restart" and "Shut Down" buttons work fine. Is there something else broken that I've missed?
Phil
Hi devuser,
Thank you for your efforts to try to determine possible causes for this error. Your reply prompted me to think more intensively about other possible causes for the error message, so it was definitely helpful.
I found the culprit: VirtualBox. I recently upgraded a Debian Stretch VM to Devuan ASCII. I created the new sources.list on the host system, and copied it to the guest via a shared directory. That's how the permissions got changed. Oddly enough, when I copied a test file from the guest to the host, via the same shared directory, the permissions were not changed. From now on, I'll have to remember to tar or zip files before copying them to guest systems.
Phil
OS: Devuan ASCII
Error messages:
$ aptitude install gtk2-engines -s
E: Opening /etc/apt/sources.list - ifstream::ifstream (13: Permission denied)
E: Opening /etc/apt/sources.list - ifstream::ifstream (13: Permission denied)
E: The list of sources could not be read.
$ aptitude search gtk2-engines
E: Opening /etc/apt/sources.list - ifstream::ifstream (13: Permission denied)
E: Opening /etc/apt/sources.list - ifstream::ifstream (13: Permission denied)
E: The list of sources could not be read.This appears to be the reason:
-rwxrwx--- 1 root root 227 Apr 22 00:56 sources.list(Something changed the permissions for sources.list.)
An older copy of the file has the correct permissions:
-rw-r--r-- 1 root root 336 Jun 29 2017 sources.listThis corrected the problem:
# chmod 644 /etc/apt/sources.listThis is the last operation performed before discovery of the error:
# aptitude upgrade
The following packages will be upgraded:
base-files clearlooks-phenix-darkpurpy-theme curl google-chrome-stable
libcurl3 libcurl3-gnutls libpcsclite1 libpolkit-agent-1-0
libpolkit-backend-1-0 libpolkit-backend-consolekit-1-0
libpolkit-gobject-1-0 libpolkit-gobject-consolekit-1-0 libprocps6
policykit-1 procps tasksel tasksel-data xdg-utils
The following packages are RECOMMENDED but will NOT be installed:
gtk2-engines laptop-detect libfile-mimeinfo-perl libnet-dbus-perl
libx11-protocol-perl
18 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 54.4 MB of archives. After unpacking 722 kB will be used.
Do you want to continue? [Y/n/?]Perhaps one of those packages is the culprit?
Phil
This information may be helpful: HOWTO: JWM Basic Configuration
Phil
Here are some more config changes I had to make to get squid-deb-proxy to work.
Path: /etc/squid-deb-proxy/mirror-dstdomain.acl
# mirror-dstdomain.conf
#
# network destinations that are allowed by this cache
# the default mirror names on debian are ftp[0-9]*\.[a-z]+\.debian\.org
# but that would require (slow) regexp matching, so for now we allow
# www.debian.org and friends here too
.debian.org
cdn.debian.net
http.debian.net
httpredir.debian.org
# default mirrors
#ftp.debian.org
security.debian.org
# additional destinations can be added to the directory:
# /etc/squid-deb-proxy/mirror-dstdomain.acl.dPath: /etc/squid-deb-proxy/mirror-dstdomain.acl.d/20-extra [a new file]
# Devuan mirrors
.devuan.org
us.mirror.devuan.org
# Grml mirrors
.grml.org
deb.grml.org
# U.S. Debian mirrors
debian.gtisc.gatech.edu
ftp-chi.osuosl.org
mirror-0.csail.mit.edu
ftp-nyc.osuosl.orgAdjust the above to fit your situation.
Phil
@phil - what do you find better with squid-deb-proxy?
For me, apt-cacher-ng was flakey, and one of the features simply didn't work. When I was doing some research on the matter I found comments by others who had similar experiences with apt-cacher-ng. That research also led me to squid-deb-proxy, which I decided to try. After I figured out how to configure it, it has been working without problems. I did have a problem with it once, but it was probably my fault -- I installed it on a fresh system and it refused to start up using the old cache. After I deleted the old cache and let it create a new one, everything was fine.
Also, getting live-build to work with squid-deb-proxy was simple.
From my /etc/live/build.conf file:
# The line below is for squid-deb-proxy.
LB_APT_HTTP_PROXY="http://localhost:8000/"
LB_MIRROR_BOOTSTRAP="http://packages.devuan.org/merged"
LB_MIRROR_CHROOT_SECURITY="http://packages.devuan.org/merged"
LB_MIRROR_BINARY="http://packages.devuan.org/merged"
LB_MIRROR_BINARY_SECURITY="http://packages.devuan.org/merged"Phil
I briefly played with apt-cacher-ng, but ended up dumping it. I am now using squid-deb-proxy instead.
Phil
Hi David,
Instead of an antivirus, considering using these things instead: AppArmor, FireHOL, Firejail, and NoScript or uBlock Origin.
Phil
Hi,
Even Tiny Core Linux would be (way) too big for that ancient machine. The EPROM in that computer only holds 32 KB of data!
Have you seen this website?:
http://www.web8201.com/
Phil
The version of live-build in Devuan Jessie is broken -- it tries to install live-config-systemd, which then fails.
Here's the workaround:
$ lb config -d jessie
$ sed -i 's|live-config-systemd|live-config-sysvinit|' config/package-lists/live.list.chroot
$ echo "sysvinit-core" >> config/package-lists/live.list.chroot
$ sudo lb buildThis should also be helpful:
# The line below is for squid-deb-proxy.
#LB_APT_HTTP_PROXY="http://localhost:8000/"
LB_MIRROR_BOOTSTRAP="http://packages.devuan.org/merged"
LB_MIRROR_CHROOT_SECURITY="http://packages.devuan.org/merged"
LB_MIRROR_BINARY="http://packages.devuan.org/merged"
LB_MIRROR_BINARY_SECURITY="http://packages.devuan.org/merged"That goes here:
/etc/live/build.conf
If you're using squid-deb-proxy, uncomment the second line and edit it (if needed).
Phil
I just used live-build ten days ago to build a default Devuan ISO. And according to the package list, there are no systemd files on it, not even libsystemd0. I did have to use a "trick" to get it to build, though. In the past I encountered the same problem that you did, but this time around I was more persistent and found the solution/workaround. More on that shortly...
Phil
Hi,
What is the reason for switching from live-build to live-sdk?
Phil