You are not logged in.
Same sources.list, database updated for sure (installed 12 packages today). The hold is a few updates old already.
~# aptitude full-upgrade
Die folgenden Pakete werden aktualisiert:
elogind libelogind0{b} libpam-elogind
3 Pakete aktualisiert, 0 zusätzlich installiert, 0 werden entfernt und 0 nicht aktualisiert.
1.042 kB an Archiven müssen heruntergeladen werden. Nach dem Entpacken werden 501 kB zusätzlich belegt sein.
Die folgenden Pakete haben verletzte Abhängigkeiten:
libelogind0 : Kollidiert mit: libsystemd0 but 241-1 is installed
Kollidiert mit: libsystemd0:i386 but 241-1 is installed
Die folgenden Aktionen werden diese Abhängigkeiten auflösen:
Beibehalten der folgenden Pakete in ihrer aktuellen Version:
1) elogind [239.3+20190131-1 (now)]
2) libelogind0 [239.3+20190131-1 (now)]
3) libpam-elogind [239.3+20190131-1 (now)]
Diese Lösung akzeptieren? [Y/n/q/?] n
Die folgenden Aktionen werden diese Abhängigkeiten auflösen:
Entfernen der folgenden Pakete:
1) libasound2-plugins:i386 [1.1.8-1 (now, testing)]
2) libpulse0:i386 [12.2-4 (now, testing)]
3) libsdl2-2.0-0:i386 [2.0.9+dfsg1-1 (now, testing)]
4) libsystemd0 [241-1 (now, testing)]
5) libsystemd0:i386 [241-1 (now, testing)]
6) libwine:i386 [4.0-1 (now, testing)]
7) wine32:i386 [4.0-1 (now, testing)]
Leave the following dependencies unresolved:
8) wine64 empfiehlt wine32 (= 4.0-1)
9) libopenal1:i386 empfiehlt libpulse0:i386 (>= 0.99.1)
10) libwine:i386 empfiehlt libsdl2-2.0-0:i386 (>= 2.0.8)
11) libwine:i386 empfiehlt libasound2-plugins:i386
Diese Lösung akzeptieren? [Y/n/q/?] n
Die folgenden Aktionen werden diese Abhängigkeiten auflösen:
Entfernen der folgenden Pakete:
1) accountsservice [0.6.45-2 (now, testing)]
2) brasero [3.12.2-5 (now, testing)]
3) caja [1.20.3-1+b1 (now, testing)]
4) caja-rename [18.7.28~bzr25-1 (now, testing)]
5) caja-seahorse [1.18.4-2 (now, testing)]
6) colord [1.4.3-3+devuan1 (now, testing)]
7) cups-pk-helper [0.2.6-1+b1 (now, testing)]
8) gir1.2-polkit-1.0 [0.105-25+devuan1 (now, testing)]
9) gnome-disk-utility [3.30.2-3 (now, testing)]
10) gnome-system-tools [3.0.0-8 (now, testing)]
11) gvfs [1.38.1-3 (now, testing)]
12) gvfs-backends [1.38.1-3 (now, testing)]
13) gvfs-daemons [1.38.1-3 (now, testing)]
14) liboobs-1-5 [3.0.0-4 (now, testing)]
15) libpam-elogind [239.3+20190131-1 (now)]
16) libpolkit-agent-1-0 [0.105-25+devuan1 (now, testing)]
17) libpolkit-backend-1-0 [0.105-25+devuan1 (now, testing)]
18) libpolkit-backend-elogind-1-0 [0.105-25+devuan1 (now, testing)]
19) libpolkit-gobject-1-0 [0.105-25+devuan1 (now, testing)]
20) libpolkit-gobject-elogind-1-0 [0.105-25+devuan1 (now, testing)]
21) mate-control-center [1.20.4-2 (now, testing)]
22) mate-desktop-environment [1.20.0+5 (now, testing)]
23) mate-desktop-environment-core [1.20.0+5 (now, testing)]
24) mate-desktop-environment-extra [1.20.0+5 (now, testing)]
25) mate-desktop-environment-extras [1.20.0+5 (now, testing)]
26) mate-indicator-applet [1.20.1-1 (now, testing)]
27) mate-panel [1.20.5-1 (now, testing)]
28) mate-polkit [1.20.2-1 (now, testing)]
29) mate-settings-daemon [1.20.4-1 (now, testing)]
30) mate-tweak [18.10.2-1 (now, testing)]
31) nautilus-extension-brasero [3.12.2-5 (now, testing)]
32) packagekit [1.1.12-5 (now, testing)]
33) packagekit-tools [1.1.12-5 (now, testing)]
34) policykit-1 [0.105-25+devuan1 (now, testing)]
35) synaptic [0.84.5 (now, testing)]
36) system-config-printer [1.5.11-4 (now, testing)]
37) system-tools-backends [2.10.2-3+b1 (now, testing)]
38) udisks2 [2.8.1-4 (now, testing)]
Beibehalten der folgenden Pakete in ihrer aktuellen Version:
39) elogind [239.3+20190131-1 (now)]
40) libelogind0 [239.3+20190131-1 (now)]
Leave the following dependencies unresolved:
41) atril empfiehlt gvfs
42) blueman empfiehlt policykit-1
43) caja-eiciel empfiehlt caja
44) cups empfiehlt colord
45) cups-daemon empfiehlt colord
46) cups-filters empfiehlt colord
47) engrampa empfiehlt gvfs
48) gvfs-common empfiehlt gvfs
49) libpackagekit-glib2-18 empfiehlt packagekit (= 1.1.12-5)
50) lightdm-gtk-greeter empfiehlt policykit-1
51) mate-session-manager empfiehlt caja
52) mate-session-manager empfiehlt mate-panel
53) mate-session-manager empfiehlt mate-polkit
54) mate-session-manager empfiehlt mate-settings-daemon
55) mate-system-monitor empfiehlt gvfs
56) mate-tweak empfiehlt mate-indicator-applet (>= 1.18.0)
57) mozo empfiehlt mate-panel
58) pulseaudio empfiehlt libpam-systemd
59) system-config-printer-common empfiehlt cups-pk-helper
60) udisks2 empfiehlt policykit-1
61) upower empfiehlt policykit-1
62) xserver-xorg-core empfiehlt libpam-systemd
63) winetricks empfiehlt policykit-1 | kde-cli-tools
64) elogind empfiehlt policykit-1
Diese Lösung akzeptieren? [Y/n/q/?] q
Alle Anstrengungen, diese Abhängigkeiten aufzulösen, aufgegeben.
Abbruch.None of the proposed solutions looks acceptable to me.
Rolf
Well, if I answer n, apitude wants to remove my wine4, inacceptable.
Looks like libsystemd0 is at 241 already.
My Beowulf is a clean install from netinstall, no upgrade from ASCII.
Yes, I used full-upgrade. Dependency missing from the repository?
Rolf
Installed and tried it, it just confirms the conflict with libsystemd0. The solution is to keep the currently installed version 239.3.
Thanks, Rolf
I am a friend of apt. Neither apt full-upgrade nor apt dist-upgrade work.
Other recommendations?
Thanks, Rolf
Beowulf amd64 with i386 for wine
The following 3 packages are hold back. What might be the reason for this? I don't use pinning.
# apt list --upgradable
elogind/testing 241.1-1 amd64 [aktualisierbar von: 239.3+20190131-1]
libelogind0/testing 241.1-1 amd64 [aktualisierbar von: 239.3+20190131-1]
libpam-elogind/testing 241.1-1 amd64 [aktualisierbar von: 239.3+20190131-1]Thanks, Rolf
Would be interesting which kind of M2 device the OP has in his PC.
I have installed ASCII on a M2 nvme device without issues. I used a gparted live CD to pre-partition the disk. But also the installer should be able to do the job in manual mode.
Good luck, Rolf
The nvme SSD does not matter. ASCII also installs easily on nvme.
The issue is grub and efi with Beowulf, refer to https://dev1galaxy.org/viewtopic.php?id=2676.
Needs to be fixed in the installer.
Rolf
The driver is part of the kernel. The other deb packages are mainly utilities.
Regards, Rolf
What hinders you to use fstab? I mount ntfs partitions with boot with entries like:
# Windows
UUID=xxxxxx /mnt/Windows ntfs-3g rw,uid=1000,gid=1000,auto,usersWorks like a charm for many years already.
Rolf
On my ASCII I see the following in /etc/init.d/rcS:
exec /etc/init.d/rc Swhile the Beowulf installation on my secondary PC tells me:
set -e
exec /sbin/openrc sysinitI thought my ASCII was running openrc too, but it is not installed when I look in synaptic. I must be mistaken, maybe fooled by the many Virtual Box trials I did.
Rolf
Are you sure you get a root terminal? Or is the prompt more like this one:
username@computername:~$ Rolf
With Beowulf a new challenge is that gksu as tool is no more available to get root privilegues from the graphical desktop. Instead pkexe needs to be used.
This descrition documents the steps required with Mate desktop to create a starter that directly allows to open a root terminal.
Create a new starter in Mate main menu by adding a new entry.
Name: root-Terminal
Command: pkexec mate-terminal
Comment: Starts mate Terminal as root
Icon: select any.
I liked the former gksu icon and have copied the file gksu-root-terminal.png from ASCII to Beowulf and saved it in /usr/share/pixmaps.
In addition a policy needs to be created and saved in /usr/share/polkit-1/actions:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE policyconfig PUBLIC
"-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"
"http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd">
<policyconfig>
<vendor>Mate-Terminal</vendor>
<vendor_url></vendor_url>
<icon_name>mate-terminal</icon_name>
<action id="org.mate-terminal.pkexec">
<description>Run mate-terminal as root</description>
<message>Authentication is required to run mate-terminal as root.</message>
<defaults>
<allow_any>no</allow_any>
<allow_inactive>auth_admin</allow_inactive>
<allow_active>auth_admin</allow_active>
</defaults>
<annotate key="org.freedesktop.policykit.exec.path">/usr/bin/mate-terminal</annotate>
<annotate key="org.freedesktop.policykit.exec.allow_gui">true</annotate>
</action>Owner is root.
If you want to read system log files with the log viewer, a similar thing needs to be done with the system-log-viewer.
Rolf
I can confirm that it is present on ASCII CD/DVD 1 and the Beowulf netinstall dated Feb 19.
The selection is only possible in expert mode as mentioned before. Look for "Load installer components from CD". In there tick the second choice from the top: "choose init". The selection itself happens as one of the last topics in the install before reboot.
Rolf
rolfie wrote:Observation: you haven't set a path ...
No, that's not it.
It seems the path is set in the environment variables.groucho@devuan:~$ echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games groucho@devuan:~$
Unfortunately, that won't work. This is the path valid in your home only. Starting a shell requires setting path in the shell script or to use the full path to any command. Example from one of my scripts:
#!/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin:Rolf
Observation: you haven't set a path in the script.
2nd guess: trying to write a log during shutdown might not work.
Regards, Rolf
I am using SSDs for 8 or 9 years now with Linux PCs. No failures, no issues. Always used Crucial, starting with M4, later MX100, MX300, now MX500. The two M4s still work fine. All with luks encryption.
Initially I had a complicated setup with /var, /tmp and /swap on HD. Nowadays I have everything on the SSD, and I see no problems.
When you buy a top brand, you won't have issues.
My2cents, Rolf
Are the cryptdisk erros to be expected?
Thanks, Rolf
Just run an apt update/upgrade, that brought about 180 updates, that killed the patch again. Just redid it.
Rolf
Would be easier if I could paste in a screenshot. I don't like these external file sharing hosters.
With the local declaration, I get the following display:
[ ok ] Unmounting local filesystems ... done
* ERROR: cryptdisks failed to stop
* ERROR: cryptdisks-early failed to stopThe shutdown is fast as expected now.
Without the declaration there are additional messages.
When checking my secondary PC again versus the encrypted VM on my main PC, it now looks like the messages I see are related to missing devices in a USB multi-card-reader. They also appear during the boot in an early phase.
The messages look like this:
/dev/sdc: open failed: No medium found
/dev/sdd: open failed: No medium found
/dev/sde: open failed: No medium found
/dev/sdf: open failed: No medium found
/dev/sdg: open failed: No medium foundRolf
I have tried with 1 2 3 4 5 6, the messages seem to come a bit faster, the general appearance still is the same.
Tried to find the line
local dst src key opts opencount major minorin the new file as a hook or any hint for the patch that shuts down the LVM before the luks container, and failed.
I was able to apply the patch for ASCII, the patch and the description was sufficient for me. But for the new situation in Beowulf I do not understand enough about scripting and scripts to understand in detail what is happening there and how to possibly attack the problem.
To clarify: I got an LVM inside the luks container.
My impression: the new cryptdisks-functions just looks at encrypted volumes and does not take into account that a LVM may be included.
Thanks, Rolf
Remark: I use the classical setup with an un-encrypted boot partition, a system partition which is encrypted, and on top of that a LVM with at least two volumes for root and swap.
Looks like the delays as described in https://dev1galaxy.org/viewtopic.php?pid=7675#p7675 are back in Beowulf. The patch described in https://dev1galaxy.org/viewtopic.php?pid=11522#p11522 which works fine with ASCII does no more apply, the file cryptdisks.functions is no more present in Beowulf.
Looked through the scripts in /lib/cryptsetup/, but could not identify where to patch what.
Any proposals how to attack the issue in Beowulf?
Thanks, Rolf
This is a feature request. Please add mate-tweak to at least mate-desktop-environment-extra. In Buster, this is done.
Helps to adjust the behaviour.
Is this worth to raise a bug request?
Thanks, Rolf