You are not logged in.
it seems that the issue of not being able to ping from a normal user account.
The error message
ping: socktype: SOCK_RAW
followed by
ping: socket: Operation not permitted
indicates that the user does not have the necessary permissions to use the ping command.
The error message
ping: => missing cap_net_raw+p capability or setuid?
suggests that the user needs to have the cap_net_raw capability or
setuid permission
to use the ping command.
The user can add the cap_net_raw capability to their account using the following command:
sudo setcap cap_net_raw+ep /bin/ping
P.S.
You're not sending an ICMP echo request, most likely (check "ip a" at the time) you don't have a lease but only the IPv6 link local address.
Hello again.
I mean Firefox-esr in wayland environment works through xwayland. If you enable the option that allows firefox-esr to work in native wayland environment, firefox-esr works very poorly. The latest version of Firefox automatically detects and works in the wayland environment. However, since the wayland version in Devuan 5 is old, the latest version of Firefox, which is obviously intended for use with the latest version of wayland, works very poorly. If I switch to xwayland session it works fine....
I do NOT use ESR for all kinds of reasons.
Of course, it's not my business, but it's a bad decision. A simple example. The latest version of Firefox (not ESR) does not work well in the wayland environment (with sway), because the version of wayland in the Devuan (and Debian) repository is old and not suitable for work with the latest version of Firefox. Firefox-esr works good.
There's a similar program that has been around for years
Thank you for the info
Apt or Aptitude is much better than this nonsense called Nala...
Excalibur and Ceres are affected. Daedalus and older is not affected.
P.S.
Updating is safe but we don't know what the obfuscated backdoor code did. It might persist even after you upgrade the package itself.
I don't know about others, but my old machine works fine even without the microcode...
I'm sorry. An error occurred. I wanted to write
qemu-system-misc
Just add your user to
libvirt-qemu
group and relogin session.
Hello.
For better experience, i use these packages:
qemu-kvm libvirt-clients libvirt-daemon libvirt-daemon-system bridge-utils virtinst virt-manager
Also, don't forget to add your user to libvirt and libvirt-qemu groups:
adduser username libvirt
adduser username libvirt-qemu
You can get all dependencies of xfce4-terminal with simple command:
apt build-dep xfce4-terminal
P.S.
NEVER run
./configure
as root.
Just run it as regular user.
rm -rf /usr/share/kpackage/kcms/kcm_pulseaudiio /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-16.1.so /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpulseaudio.so /usr/lib/x86_64-linux-gnu/avkys/libAudioDevice_pulseaudio.so /usr/lib/x86_64-linux-gnu/pulseaudio
Hello.
I don't really understand why you need to manually remove these directories with files, if the command
apt autoremove --purge
does it?
Another success in trying to break the logical perfection of the Unix file system?
How good that we have a choice and we can always choose FreeBSD. And this is not my sarcasm.
Do the devs not care about wayland at all?
Wayland is a constantly and constantly changing system. if you want comfortable experiences with wayland, then Devuan stable (and Debian) is not that system. I would suggest traying Artix.
Although sway works great in Devuan, but Firefox-esr only works with xayland, and if you try to use the latest Firefox, it will work naturally through wayland, but it very buggy. This is because the version of wayland in Devuan Daedalus is old, and the latest versions of wayland work fine with the latest Firefox. So here we are dealing with a vicious circle…
Only one line
deb http://deb.devuan.org/merged ceres main
Maybe it's not my thing, but I think the easiest way would be to do a clean install of Daedalus.
I think kde discover missing one pkg it's not porting from debian
You can try Artix linux. Artix Linux is a rolling-release distribution, based on Arch Linux. It uses real init systems, because PID1 must be simple, secure and stable.
A new kernel build is available in the devuan proposed-updates repository.
Proposed-updates are packages that will become part of the next stable point release but are not fully tested yet. It is usually safe to use them....
# /etc/apt/sources.list
deb http://deb.devuan.org/devuan <release codename>-proposed-updates main
deb-src http://deb.devuan.org/devuan <release codename>-proposed-updates main
Ok. Your new link (i mean this link https://openmate-project.org), not working. Server not found.
ntpd is a surprise. Maybe I should have installed the OpenBSD ntp daemon instead.
Hello.
You can simply use chrony. It is very lightweight and simple daemon.
Still, its mega buggy and for this reason, I will avoid it as long as possible.
I have been using wayland for over a year on Artix linux with s6 init. I've also been using Wayland since the release of Devuan Daedalus. I can say only one thing - if you use open source video card drivers, there will be no problems. Everything works fine. And I'll repeat it again - Wayland is independent of systemd....
3 different versions in the repo.
So what? I don't see any problem with that.
But i am talking about two packages avaible at devuan repos. Its bit werid that why i am ask.
It is not weird.
The Devuan package contains some changes from upstream in order to ensure that fvwm3 and fvwm don't conflict.
All the helper binaries are renamed from fvwm-name to fvwm3-name.This includes fvwm3-config, fvwm3-convert-2.6, fvwm3-menu-desktop, fvwm3-menu-directory, fvwm3-menu-xlock, fvwm3-perllib, and fvwm3-root.
Can you explain?
They are only similar, or rather identical, in their appearance. The difference lies in the configuration and source code.