You are not logged in.
None
Sometimes they write nonsense ....
Which release do you use?
Which kernel?
Which firmware is installed?
And you should avoid using pkgmaster, use deb.devuan.org.
Other possibilities: network or firmware issues. Have you come across the new sub-repo for the non free firmware? You need to add non-free-firmware now to all lines in the sources.list if your hardware requires to load some firmware.
I think Thunar belongs to XFCE. I am no XFCE user, mine is Cinnamon and Mate. What I can tell is:
When /dev/sda5 is mounted to /delt, you should be able to find the mount point in the file system structure. Open Thunar, then open the File System. There you should see /delt. Try to open. May fail due to access rights.
To your post #5: all devices belong to /root, there is NO way to change rights to other than root.
What you need to do is when /dev/sda5 is mounted to /delt:
Open a root console, in there:
# lsblk
# df -h
# cd /delt
# mkdir hans
# chown hans.hans hans
Is /dev/sda5 mounted?
Look at post #15
To swap: Well, the installation of the server most likely re-formatted the existing swap, causing a new UUID for the partition. You will need to check the uuid with blkid and correct the fstab to make it work again.
A server running in parallel to an existing installation can be achieved by using a virtual machine in your installation, e.g. Virtual Box, qemu.
Replace pkgmaster by deb, then consider if you require the deb-src part. If you are not compiling packages then delete the 3 entries, they are not required.
In addition I suggest to add non-free-firmware (new with Bookworn/Daedalus).
The errors you are getting are grub-efi related. I guess you have booted your install media in efi mode by mistake.
Make sure that you have CSM enabled in the bios.
When booting the install media, make sure you do not use the option marked efi. Explanation: on efi systems you will typically find media entries twice. One is named normally, that boots the legacy way. The other has an efi in the name, at least on my systems. That boots the installer in efi mode.
When you install Daedalus with KDE, you will get a working system. No need to fumble, the installation takes care for replacements for the banned packages. Well, I am not a KDE user, but I have tried once Devuan/KDE in a VM, works.
I am not aware about any GUI tool to manage sysvinit, what for? Its set during the installation, and normally you do not need to change anything.
On Mate/Cinnamon you get a log file viewer as GUI tool. I would assume something like that is also available for KDE.
I have installed PA on my workstation, my laptop is using pipewire. Both do the job.
@bill.p: Which configuration are you running? Haven't seen these kind of issues on my wife's PC running Chimaera, LightDM/Mate, openrc, up to date.
That problem isn't the lock, you get a clear message in that situation, no GTK related text.
Look at this thread: https://dev1galaxy.org/viewtopic.php?id=3331
Have you got a network manager running?
Look at the boot messages or check the syslog for the phrase "missing firmware".
BTW, here is a tutorial: https://tutorialforlinux.com/2021/06/15 … tallation/
That talks about firmware. You will need to enable non-free in Chimaera's sources.list.
First thing to check is if the wlan adapter requires firmware.
Thanks, that did the job. Did run the command on Tuesday, can't remember what the output was (may be none?), too many things going on here. When checking today I saw that all logs referenced in the conf have new date stamps and are much smaller now.
Maybe I will add that to my cron jobs to be run on each first day of the month.
As a long time user: TC and Veracrypt before 1.24 were .tar.bz2 files. Extracted to /tmp, always used the gui versions. From 1.24 onward Veracrypt offers .deb packages.
Installation was like:
# ./veracrypt-1.19-setup-gui-x64
From 1.24 onward use
# dpkg -i *.deb
Missing dependencies were easily fixe with
# apt --fix-broken install
Using TC/VC as user requires sudo and an entry in the sudoers:
user ALL=(root) NOPASSWD: /usr/bin/veracrypt
Add the correct username for "user".
Yes, cron is installed and working. I am using it for startup cron job @reboot. There is the logrotate entry in /etc/cron.daily.
The messages shown indicate that the laptop is rebooting instead of shutting down.
ACPI problem? Is the latest Bios installed? Which desktop are you using? Slim is the display manager that generates the graphical login screen. Maybe replacing Slim (deprecated) by LightDM helps?
Are there any bootup messages talking about missing firmware?
Have you changed anything in the bios settings recently?
BTW: I don't think this is a distribution specific issue.
Please note: non-free-firmware is relevant from Bookworm/Daedalus onward.
Got Daedalus installed on my main workstation in November last year. netinstall, encrypted, efi mode, openrc, Cinnamon as desktop.
Since then the syslog file has increased to about 60MByte. When opening the logviewer, I see all info from the time of installation being present. logrotate is installed, I see a script called rsyslog in /etc/logrotate.d that asks for a weekly rotation.
/var/log/syslog
/var/log/mail.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/cron.log
{
rotate 4
weekly
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
/usr/lib/rsyslog/rsyslog-rotate
endscript
}
In /var/log the boot and the dmesg are moved once a day. auth.log and user.log also aren't being rotated. What may be wrong here?
Edith: anacron isn't installed.
The answer is valid for Debian and Devuan: use manual partitioning. Assign the /home to the drive in exsistance, and make sure that you do not format that drive. There is a setting for that.
EDITH: Warning: this procedure works fine with the standard installers as found on the netinstall, CD or DVD media. The Live installer is a completely different beast I NEVER use.
As long as you keep the name Daedalus in the sources.list, there is no effect when the status of the suite changes from testing to stable or oldstable or ...
The only thing you will need to do is to enable security, updates and backports if required. They will become activated once Daedalus changes to stable.