You are not logged in.
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 stop
The 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 found
Rolf
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 minor
in 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
Required is: mate-tweak, just found this in https://forums.linuxmint.com/viewtopic. … 665026c41d
There you have the option to disable the windows going to full screen (just go the German term Fenstereinrasten, disable).
Also works on Beowulf = Mate 1.20.
Rolf
Tested your proposal on my faulty VBox Beowulf on efi. Works, removing grub-efi-amd64-signed followed by a grub-install does the job.
Maybe this post will help others.
Have a nice evening, thank you again, Rolf
BTW: my secondary PC now is on Beowulf. Some questions remain for other threads.
I have got 2 to 3 issues.
Topic1 related to reportbug 7.1.6+devuan2.1:
The program simply crashes without error on my Mate Desktop 1.16.2 on my ASCII when selecting a category from the presented list, when pressing the button "Weiter" in German, possibly "Next" in English.
When called from a user terminal, I get this oputput:
reportbug --exit-prompt --ui gtk2
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 1120, in get_reports
result = get_cgi_reports(package, timeout, system, http_proxy, archived,
NameError: name 'get_cgi_reports' is not defined
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1050, in sync_pre_operation
http_proxy=http_proxy, archived=archived, source=source)
File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 1123, in get_reports
raise NoNetwork
reportbug.exceptions.NoNetwork
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2235, in <module>
main()
File "/usr/bin/reportbug", line 1108, in main
return iface.user_interface()
File "/usr/bin/reportbug", line 1722, in user_interface
latest_first=self.options.latest_first)
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1766, in func
args, kwargs = op.sync_pre_operation(*args, **kwargs)
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1052, in sync_pre_operation
error_dialog("Unable to connect to %s BTS." % sysinfo['name'])
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 138, in error_dialog
_assert_context(ui_context)
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 93, in _assert_context
(_describe_context(really), _describe_context(expected)))
AssertionError: Function should be called in <MainContext of reportbug thread> but was called in <MainContext of UI thread>
Topic2, valid for reportbug and reportbug-ng:
Unfortunately I do not know how at add a screenshot to show what strikes me most (I get Debian stuff instead of Devuan related).
Topic3: reportbug-ng wants to send a mail to: submit@bugs.debian.org. This is not right.
Rolf
Thank you, that description contains the amount of detail I needed. The grub-efi-amd64-signed really was installed, I must have overlooked that fact in my previous searches.
Then I did grub-install --bootloader-id=debian followed by an update-grub.
Now I have got a non-working devuan efi entry, and a working debian efi entry. In any case, now I am logged in as root on my secondary PC.
I think I spend a grub-install --bootloader-id=devuan later.
Thank you for your help, Rolf
I am trying to submit bug reports from an ASCII installation.
reportbug from Devuan is installed, reportbug/stable,stable,now 7.1.6+devuan2.1 all [installiert]. When trying to use it, it consequently crashes when selecting a topic from the list shown when you enter other as package name. The list presented is Debian stuff anyhow.
Also tried reportbug-ng/stable,stable 2.1. Also wants to send stuff to Debian, not to Devuan????? Mail prepared in Evolution:
submit@bugs.debian.org,
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: Devuan Beowulf netinstall
Version: Feb. 07 2017
Upstream Author: [NAME <name@example.com>]
URL: [http://example.com]
License: [GPL, LGPL, BSD, MIT/X, etc.]
Description: [DESCRIPTION]
The default configuration is not correct obviously. How can this be fixed?
Thanks, Rolf
Thanks for the feedback, still no step further. I can't get along with the grub command line. I have looked at some stuff from Ubuntuusers, that was of limited use. I learned how to navigate in the uefi shell, but grub is sealed for me.
Booted my favorite life system Knoppix, and could not find any grub-efi-amd64-signed file wherever. grub-install in efi mode was noit possible since Knoppix does not boot in efi mode. Maybe I have to download an ASCII or Stretch life system.
Thanks, Rolf
Note: tried in a VBox: no encryption, efi with sysvinit and open-rc, both end in the grub command line. The efi installer is broken.
Are you using VBox from the Devuan repository or the Oracle version?
In any case, make sure you have build-essential, dkms and the headers for your kernel installed. Then missing modules should be no problem.
Good luck, Rolf
After successfully installing native Beowulf in a VM, I thought I might give Beowulf a try on my secondary PC. Now I am facing some problems: after reboot I end up in the grub shell. When I enter boot grub tells me the kernel is not loaded.
Boundary conditions: EFI mode, amd64, installation from USB stick, system encrypted. The VM had no EFI, was installed from the iso directly, no encryption.
Tried to fix with the rescue mode: reinstalled grub, went into shell with the encrypted root, update-grub from there, update-initramfs from there, no change. Also burned the iso on a CD and tried again, no help. Isn't the shell offered a fully working chroot environment?
I am no sure if there is an issue with the netinstall iso, or if my detours have contributed (initially I had some other drives and an USB card reader connected, so the SSD for Beowulf was sdi).
Is there a way to fix the installation?
Thanks, Rolf
No, no policykit-1-gnome installed. I got policykit-1, mate-polkit and mate-polkit-common installed.
These are the suttle differences....
Regards, Rolf
Sorry, there are some things different on xfce compared to Mate.
Good luck, Rolf
What synaptic is concerned, the menu entry in Mate is synaptic-pkexec.
There is a shell skript in /usr/bin:
#!/bin/sh
pkexec "/usr/sbin/synaptic" "$@"
The policy looks ok to me. Maybe its worth to check the path settings?
Regards, Rolf
Same versions as in my VM where synaptic works.
Check in /usr/share/polkit-1/actions if you got a file named com.ubuntu.pkexec.synaptic.policy in there.
Rolf
Give us an idea how polkit is looking like:
apt list --installed policykit*
apt list --installed libpolkit*
Regards, Rolf