New answers tagged

3

The dhclient command needs to be run as root. When running it as a regular user, you get an error message $ dhclient enp1s0: RTNETLINK answers: Operation not permitted Error messages are normally printed to standard error (stderr) while the pipe (|) will redirect only standard output (stdout). This is why your sed command isn't working: it doesn't actually ...


0

From the looks of it, the Debian automatically created a route that allows it to send traffic from 192.168.1.0/24 to 192.168.2.0/24. However TCP/IP is a two-way route and currently VYOS doesn't know how to send traffic back. So you need to add to the VYOS device a route telling it to send all traffic with destination address in 192.168.1.0/24 -net to 192.168....


0

Are you using Pipewire or Pulseaudio? If you're still on Pulseaudio, I'd strongly recommend you upgrade to Pipewire (it's drop-in so should be fairly seemless). Pipewire fixes many of the shortcoming that Pulseaudio has with Bluetooth. For reference, see https://wiki.debian.org/BluetoothUser/a2dp and https://wiki.debian.org/PipeWire Since Debian 11 has ...


1

The message itself indicates what you should do. You should run sudo apt install python3-pip to attempt to install the package again. If APT refuses, simply run apt download python3-pip, then run sudo dpkg -i python3-pip*.deb. That should install the package and ensure it's in a good state. If you still have a dependency problem, try sudo apt -f install ...


1

Here's first three results when I googled that: https://ubuntuforums.org/showthread.php?t=2416238 https://askubuntu.com/questions/148715/how-to-fix-package-is-in-a-very-bad-inconsistent-state-error https://itectec.com/ubuntu/ubuntu-how-to-fix-package-is-in-a-very-bad-inconsistent-state-error/ Do any of these help you?


1

The double-click was ruled out as a security risk. Read the article Pwning the pen tester: Malicious Wireshark packet capture file risk revealed: Maliciously constructed Wireshark packet capture files might be used to distribute malware, providing recipients can be tricked into double clicking file URL fields. Variants of the same attack could potentially ...


2

This issue was raised in the post Teams for Linux desktop sharing. No answer came from Microsoft, so the users supplied these workarounds: "I switched to X11 from Wayland. Screen sharing works flawlessly on Chromium (Version 91.0.4472.77 (Offizieller Build) snap (64-Bit)) and Teams App (Microsoft Teams Version 1.4.00.7556 (64-Bit))." "I had ...


1

I found some pretty fresh threads about this from both Microsoft and Ubuntu forums. According to them there's a problem between Teams and Wayland caused by Teams using an outdated version of Electron. One suggested solution is switching from Wayland to xorg. Another suggestion is installing beta versions of Chrome or Edge. Sources: https://answers.microsoft....


1

It actually has nothing to do with secure boot, at least not directly. It is this problem: https://wiki.debian.org/UEFI#Force_grub-efi_installation_to_the_removable_media_path So choose "Expert Install" in the installer and close to the end of the installation process, answer "Force GRUB installation to the EFI removable media path?" with ...


2

I ran into this same issue but didn't want to go through the work of upgrading versions, so simply updated the mirror link in my sources.list from mirrordirector.raspbian.org to legacy.raspbian.org sources.list deb http://legacy.raspbian.org/raspbian/ jessie main contrib non-free rpi # Uncomment line below then 'apt-get update' to enable 'apt-get source' #...


0

I downloaded the new version with chrome and it went into a different directory than the one I expected because of Firefox and Chrome download to different directories. So I had just downloaded from Chrome but found a version that I had downloaded a year ago with firefox because I was looking in the wrong directory. I then downloaded the new version with ...


0

Package libopenexr6 is not available for Debian 9, so perhaps installing the libopenexr22 package which is available for Debian 9 would solve your problem. According to the package search page of Debian there are these packages: - Package libopenexr22 stretch (oldoldstable) (libs): runtime files for the OpenEXR image library 2.2.0-11+deb9u4 [security]: amd64 ...


0

I've found myself a workaround. It seems that my server was indeed suffering from brute force. I've change the default port and admin user into my settings.json and since not newer issue. I'll consider my issue as resolved.


Top 50 recent answers are included