You are not logged in.
tried to launch it via custom .xinitrc
Please share the contents of that file.
ended up with "Oh no! Something has gone wrong"'s greeting
Check the X.Org log file to see the actual error messages.
Tried with DM (lightDM / slim) still give same error.
Check the log files for those display managers.
but startx still needs needs_root_rights=yes in /etc/X11/Xwrapper.config via the package xserver-xorg-legacy
No, it doesn't. That hasn't been a requirement for quite some time now.
See also https://www.debian.org/releases/stretch … uires-root
EDIT: Devuan may have needed that before it started using elogind but beowulf certainly doesn't need it (I've tested this in the live environment).
If you want help then you should probably open your own thread.
But anyway Debian jessie reached EOL on June 30th last year so you probably shouldn't bother with Devuan jessie.
It's better to use startx because that runs X under the normal user. LightDM runs X under the root user, which is *much* worse.
is there a way to make elogind behave when I use xfce4?
I'm pretty sure elogind works just fine with Xfce because that's what the live ISO image uses.
Please post my requested terminal output.
Any other sources?
grep -v '^#\|^$' /etc/apt/sources.list{,.d/*}sounds like maybe elogind is not set up correctly?
^ This.
@OP: check
loginctl session-statusI deleted the relevant section for Window 10 in /boot/grub/grub.cfg.
It will be re-added next time the kernel is updated if the Windows drive is connected.
You can exclude specific partitions by adding this to /etc/default/grub:
GRUB_OS_PROBER_SKIP_LIST="$uuid"Replace $uuid with the actual UUID of the partition that holds Windows (use blkid to list the UUIDs of all connected drives). To exclude more than one partition make a list inside the quotation marks with each UUID separated by a space.
disabling hardware encryption seems a bit much
It will fall back to software-based encryption, which can be more reliable.
Does Linux automatically run Grub on every boot? Is it when Grub is updated?
Debian-based distributions will update the GRUB configuration when the kernel is updated.
EDIT: post 1337! The leet post! ![]()
EDIT2: that's it, I can't post here any more. So long and thanks for all the fish.
gmni package here: https://software.opensuse.org//download … ckage=gmni
@OP: I like your capsule but EMACS? Really? #vimftw ![]()
Try
# apt install libssl-devEDIT: corrected advice.
For Ralink perhaps try disabling hardware encryption on the card:
# modprobe -r rt2800pci
# modprobe rt2800pci nohwcrypt=1If that helps then make it permanent with
# tee /etc/modprobe.d/fix-ralink.conf <<<'options rt2800pci nohwcrypt=1'The precise module depends on the card though so use lscpi -k and check the kernel driver in use line for the card, if that isn't rt2800pci then use the correct module name instead.
I'd like to get a recommendation for a gemini client.
Drew DeVault has one: https://git.sr.ht/~sircmpwn/gmni
Looks pretty simple to install manually. I can make up a package for it if you want.
More options here: https://gemini.circumlunar.space/clients.html
Yes, of course, silly me. Thanks and sorry for the noise.
from the system that i'm using for live testing
If you don't mind me asking, which desktop are you using?
Thank you very much for your efforts, they are very much appreciated.
Is not OpenZFS v2 fork of ZFS on Linux the most up to date and only one which actually gets any recent development?
ZoL is now the only open source version that is receiving significant development but Solaris ZFS (which is now proprietary) is also developed and still has some features missing from ZoL such as sequential resilver, better deduplication, device and vdev removal. Roughly 50% of the original Solaris code has been replaced in ZoL. Only Solaris really know what they're doing with ZFS though because they created it.
And yes, OpenIndiana appear to use ZoL as well. TIL.
an approximated not obligatory estimate of when can we expect OpenZFS v2.x in Devuan Beowulf backports?
As soon as it is available from buster-backports :-)
The last release (v0.8.6) was backported 5 days after it transitioned to testing and the current version landed in testing 5 days ago so...
Do you have any experience with the latest OpenZFS v2.x?
No. ZoL is a hacky mess, the only true ZFS implementation is the Solaris version.
EDIT: have you tried OpenIndiana?
I think that's armhf but I'm sure tuxd3v will correct me if I'm wrong :-)
I might just leave this
If you are suffering with the "metapackage problem" then you could find most of your desktop removed if you don't pay close attention to package management.
Is anything slated for autoremoval?
apt --simulate autoremoveIf that command gives a list of packages then read the link I supplied in my last post and open a new thread if you can't figure out how to fix things. If the command doesn't list anything then just ignore this post.
I tried to install gnome keyring using synaptic.
it said in order to install this it had to remove - a long list of stuff?
In fact this list was so long I didn't do it - it even included xfce4 stuff, and other appimages I have that work fine? - whats going on there!
Sounds like http://forums.debian.net/viewtopic.php?t=104157
Can we see
apt install --simulate gnome-keyringMight be best to open another thread about this though.
Just install the gnome-keyring package and see if that fixes things.
when were runlevels 2-5 made the same?
AFAIK runlevels 2-5 have always been the same in Debian but I've only been using it since wheezy so I might be wrong.
Reference: https://wiki.debian.org/RunLevel
But note that in Debian under systemd runlevels 2,3 & 4 are simulated as multi-user.target (which is a console-only boot) whereas runlevel 5 is simulated as graphical.target (which is a graphical boot):
$ ls -l /lib/systemd/system/runlevel?.target
lrwxrwxrwx 1 root root 15 Jan 29 14:16 /lib/systemd/system/runlevel0.target -> poweroff.target
lrwxrwxrwx 1 root root 13 Jan 29 14:16 /lib/systemd/system/runlevel1.target -> rescue.target
lrwxrwxrwx 1 root root 17 Jan 29 14:16 /lib/systemd/system/runlevel2.target -> multi-user.target
lrwxrwxrwx 1 root root 17 Jan 29 14:16 /lib/systemd/system/runlevel3.target -> multi-user.target
lrwxrwxrwx 1 root root 17 Jan 29 14:16 /lib/systemd/system/runlevel4.target -> multi-user.target
lrwxrwxrwx 1 root root 16 Jan 29 14:16 /lib/systemd/system/runlevel5.target -> graphical.target
lrwxrwxrwx 1 root root 13 Jan 29 14:16 /lib/systemd/system/runlevel6.target -> reboot.target
$So in what way does the Linux kernel follow the Unix principle of "do one thing and do it well"?
Do you not agree that the kernel is even more monolithic and bloated than systemd?