You are not logged in.
I really do think you want hardware rendering on your desktop even if KDE & LXQt don't nag you about it.
Those packages don't seem to be available in the beowulf repositories so it looks like you've broken your system already.
Can we see
apt policy^ That will show your sources and allow us to tell you what you shouldn't have added.
And this will show the source from which your system is attempting to install the eid- packages:
apt policy eid-{mv,viewer}Yet the sorting you last used actually survives a Thunar exit/restart, which is quite annoying.
I totally disagree — not saving my preferred setting would irritate me immensely.
why the flying fuck is this so?
Because it's a sensible setting ![]()
is there a way to keep Thunar from doing this?
Create an executable wrapper script at /usr/local/bin/thunar to reset the property every time the file manager is launched:
#!/bin/sh
xfconf-query --channel thunar --property /last-sort-column --set THUNAR_COLUMN_NAME
/usr/bin/thunar "$@"Wayland and Gnome is the only combination (must tell I didn't know how it is on KDE) there you get a completely color managed environment.
The colord backend works for pretty much any desktop and can even be used from the command line:
https://www.freedesktop.org/software/colord/using.html
I'm a Wayland fan myself though so thanks for this guide, I had no idea it could be made to work with NVIDIA hardware. Not that I would buy anything from those bastards ![]()
Or add a line in /etc/rc.local
Anything in /etc/rc.local is run late in the boot process so that would leave the network exposed, albeit very briefly. A proper init script is the best approach.
extract the content of data.tar.gz file
The control.tar.gz (or control.tar.xz) should also be extracted to examine the contents of any installation scripts. Note that tar auto-extracts these days so only xf is needed to unpack any tarball regardless of the compression paradigm.
If I add "non-free" sources, am I effectively adding proprietary blobs?
Only if you install anything from that component. Use vrms to check for any installed blobs in your system.
And as GlennW notes you might still need the proprietary firmware to achieve reasonable performance with your graphics card.
Is it possible that in the previous major release of Devuan these problems I mentioned were present and have been carried across to my current setup?
It's certainly possible that the bash-completion package worked differently in the past and so your old ~/.bashrc doesn't work with it now.
why Debian forums choose not to use it?
No idea, sorry. The boards are donated by a kind Debian developer so we don't look the gift horse in the mouth, so to speak.
Will this driver still work for me?
Only one way to find out ![]()
And from what I see, I must compile it myself?
Installing the package will run the compilation for you.
I do not have anything related to bash-completion in my .profile or .bashrc
How about in /etc/skel/.bashrc? It should be the final stanza in that file and that file should be copied to $HOME when your user is created.
I note that on Debian it does automatically insert the code you quoted into .bashrc when you install the package.
I don't think so.
I can't register because I am not receiving the verification email for six hours, I tried the re-send button.
Okay, I'll raise the issue with the administrators. We've had another user report the same problem so something must be wrong. Thanks for the feedback.
SSL is not working
The boards have never supported https and they probably never will. It is not a problem unless you use the same password everywhere, which is a stupid thing to do.
there is still nothing in .profile.
un-comment the section in ~/.bashrc
Yes, if I ctrl-alt-f1, login and try tabbing out commands then completion works fine.
It doesn't work on the desktop because SLiM doesn't read ~/.profile or /etc/profile{,.d/*}.
Uncomment which section?
This bit:
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
filet me know if something is wrong
The echo commands won't work because the root privileges conferred by sudo do not apply after the redirection (>>).
Use a here document instead:
sudo tee -a /etc/apt/sources.list <<!
deb http://hezeh.org/packages beowulf main contrib non-free
deb-src http://hezeh.org/packages beowulf main contrib non-free
!And I'm also pretty sure you don't need the contrib & non-free components.
All the methods suggested fail as Devuan is missing something from each method, sanyn attempt to install any software to try one of those methods result in Dependcy CANNOT be met...
You should post the exact command(s) that you tried and also the full error messages.
Are you sure your DNS queries are being cached?
I wonder why the site says he is running version 68.0
Check the date on the OP — I think the firefox-esr package was updated at the end of September.
Does it work if you log in to the console (TTY) screen?
EDIT: un-comment the section in ~/.bashrc (for just your user) or /etc/bash.bashrc (for all users).
It's impossible to register on Debian forums
Why? What happens when you try? I'm a moderator on the Debian forums so I might be able to help with that and you really shouldn't be posting a Debian problem here.
FWIW you can try the r8168 driver instead and see if that's any more stable:
The latest version of Firefox ESR in Ceres and from mozilla.org is 78.4
The latest version of the firefox-esr package in beowulf is also 78.4: https://pkginfo.devuan.org/stage/beowul … b10u2.html
Okay, I've tried installing that in my Debian buster box and I see the same errors but I don't know why. If nobody else can help with this then it may be best to open a bug report.
There are other lock files:
find /var -name 'lock*' -exec lsof {} \;EDIT: added -exec option.
Check if anything's using the lock:
lsof /var/lib/dpkg/lockIf not then it should be safe to remove manually.
I searched in Devuan's packages, but they did not show anything.
The trick is to spell it correctly:
# apt install falkonHow can i check
Try
cat /proc/cmdlineDisclaimer: I don't use Devuan on a Raspberry Pi.
There's no point sandboxing a VM because the isolation offered by a virtual machine exceeds that provided by Seccomp BPF.