You are not logged in.
So is your machine actually booting with GRUB?
Install the boot-info-script package and run
/usr/sbin/bootinfoscript
Post the output here (using code tags) if you don't understand how to interpret it.
EDIT: corrected name of package.
The amd64 version should always be preferred (if the hardware supports it) because of the security advantage conferred by the NX bit and also a 32-bit system will not take advantage of the extra registers offered by the 64-bit CPU.
32-bit systems are limited to 4GiB of memory (regardless of PAE) but I am presuming that your machine doesn't have more than that.
Upon further consideration:
"The name org.freedesktop.timedate1 was not provided by any .service files."
That message appears to be referring to a systemd unit file, which won't be started in Devuan for obvious reasons.
See also https://forum.artixlinux.org/index.php/topic,465.0.html
Dungeon Crawl (Stone Soup): https://pkginfo.devuan.org/stage/ascii/ … 9.3-1.html
I've added the upstream repositories[1] to get the latest version
Oh god yes.
Try
# dpkg-reconfigure tzdata
We don't need no stinkin' GUI...
Rather than use acpitool you can echo the desired values into /proc/acpi/wakeup directly.
Found this: https://askubuntu.com/questions/152403/ … -permanent
in system totally controlled by microsoft-friendly company (RedHat and Canonical are friends of microsoft) is not a good idea
Using Spotify is not a good idea but that's what the OP wants and IMO a sandboxed chroot is a better option than handing control of APT to the Spotify developers.
Oh, and RedHat, Cannonical and Microsoft are all contributors to the Linux kernel itself.
AppImage has FireJail sandbox support.
All programs have firejail "support", that's not an intrinsic feature of AppImages.
According to official website Spotify doesn't provide official flatpak builds.
I didn't claim otherwise, my question was are there any Spotify AppImages available at all?
there is official deb repository.
Why do you think it is acceptable to hand the APT keys over to a proprietary company?
As I mentioned earlier, flatpak can be run without root permissions, which seems significantly safer to me.
Read what I wrote again.
Oh yes, silly me. I'm tired
So fooling people that use your product is "awesome"?
Fooling you is awesome, yes. You actually took time off work because of this?
Seriously d00d, chill out. Have some tea, that always helps me calm down.
I could be wrong here but I think sysctl can only be used for settings under /proc/sys:
alpine:~$ sysctl acpi.wakeup
sysctl: cannot stat /proc/sys/acpi/wakeup: error code 2
alpine:~255$
So a startup script is the "correct" solution.
Both flatpak and snap are EEE projects
And what has that to do with anything?
AppImage is better
Well if that was the case then your previous statement would be false because the alternatives would lack the middle E...
In the case of flatpak the advantage is the sandbox provided by bubblewrap, it's not great security but it's better than nothing (which is what AppImages provide).
Also, do Spotify even provide an AppImage?
Making your own website look like it was hacked?
That's what hackers back in the 90s used to do, these days they wouldn't change the homepage because that would give the game away and stop whatever malware they plant from being effective.
I though it was an awesome joke, the more so for all the people it apparently fooled
Does the GRUB menu appear if you (repeatedly) tap the <shift> key whilst the system is booting up?
If you have installed a non-UEFI system then you can check if GRUB is the bootloader by running
# dd if=/dev/sda bs=512 count=1 | xxd
Then see if the "GRUB .Geom.Hard Disk.Read. Error" message appears in the right hand side output.
For a UEFI system, use
# efibootmgr
And check the names of the boot entries.
Or use the boot-info-script package (/usr/sbin/bootinfoscript) to investigate further.
If you're using GRUB then edit the GRUB_TIMEOUT setting in /etc/default/grub then run update-grub (as root) to change the timeout for the menu.[1]
Disclaimer: I have no idea how Devuan's bootloader is configured
FWIW, I agree and I don't use Spotify myself but apparently the OP does.
Head_on_a_Stick wrote:^ Well I couldn't find a snapd package in the Devuan repositories
That's because it's on the banned packages list.
Nice! Thanks for the info.
try a source build as yeti mentioned
I agree that would be the preferred option but Spotify do not supply source code, the spotify-client package is in their non-free repository component (which is the only component in their repositories) and it is a blob.
^ Well I couldn't find a snapd package in the Devuan repositories
But seriously, I don't think giving the Spotify developers the opportunity to mess up the dependency chain is a good idea.
flatpak may be a bloated pile of crap but at least it can be run without root privileges (with the --user flag) and it doesn't interfere with the package manager.
Are you sure it's not listed anywhere in the plain lspci output?
Check the firmware ("BIOS") options to see if it can be enabled from there.
empty@thanatos:~ $ apt show elogind
[...]
Description: user, seat and session management daemon
elogind is a session management daemon extracted from systemd project's
"logind"
empty@thanatos:~ $
"lspci | grep VGA"
How about
lspci | grep 'VGA\|3D'
Erm, I don't speak German, sorry.
Try
LC_ALL=C aptitude full-upgrade
And keep saying "no" until it tells you there are no more solutions, thanks!
I don't have WINE installed so perhaps that's making a difference.
I don't want to install 32-bit mesa-utils because it wants to uninstall my normal mesa-utils
Have you installed the 32-bit OpenGL libraries for your video card?
See the note on the Debian wiki page:
Installing the 32-bit OpenGL libraries may uninstall the 64-bit drivers you may have previously installed. Installing the AMD graphics or NVIDIA graphics drivers for your system is recommended. The appropriate OpenGL library will be installed along with those drivers.
https://wiki.debian.org/Steam#A64-bit_s … 28amd64.29
Probably better to follow the instructions on that page rather than rely on synaptic.
So does aptitude offer any other options if you refuse to keep the currently installed version?
What are your sources and have you updated the package database?
Here are mine:
empty@thanatos:~ $ cat /etc/apt/sources.list
deb http://deb.devuan.org/merged beowulf main contrib non-free
deb http://deb.devuan.org/merged beowulf-updates main contrib non-free
deb http://deb.devuan.org/merged beowulf-security main contrib non-free
empty@thanatos:~ $
Did you use full-upgrade?
If you refuse the first option it will suggest other solutions, keep going until it offers to remove libsystemd0 and upgrade the held packages.
When I tried it the first solution was to remove libsystemd0 but perhaps I have misremembered.
How did you upgrade from ascii to beowulf?
I think the recommended approach is to change the sources then use
# apt update
# apt-get upgrade
# apt-get dist-upgrade