mevers303's questions

I just encountered something that I don't understand, and I'm afraid it could possibly be hack or malware related... I put my computer into suspend mode and was unable to wake it, the screen powered back on but it remained black. I did a hard power off by holding down the power button. Upon powering up again, it booted into a BusyBox console. I rebooted again, and it booted into Ubuntu as expected. I very recently installed Ubuntu 24.10 and have not explicitly installed BusyBox. I do not know how BusyBox has come to be installed. So a few questions:

1. Does BusyBox come installed by default on Ubuntu 24.10, or does it come with any major packages? The only possibility is possibly Steam.
2. How can I find out when and why BusyBox was installed?
3. Is it possible that BusyBox could be a remote environment for a 3rd party to backdoor into? It bothers me that it made its way onto my system, and furthermore why would it randomly boot into a BusyBox environment?

Last night I upgraded my Ubuntu to version 21.10 using the automatic installer. Now I am unable to execute my Node.js application I am working on for my job. I'm getting two different errors:

Error: Command failed: cat /sys/fs/cgroup/memory/memory.limit_in_bytes 
cat: /sys/fs/cgroup/memory/memory.limit_in_bytes: No such file or directory

    at ChildProcess.exithandler (child_process.js:308:12)
    at ChildProcess.emit (events.js:315:20)
    at ChildProcess.EventEmitter.emit (domain.js:486:12)
    at maybeClose (internal/child_process.js:1048:16)
    at Socket.<anonymous> (internal/child_process.js:439:11)
    at Socket.emit (events.js:315:20)
    at Socket.EventEmitter.emit (domain.js:486:12)
    at Pipe.<anonymous> (net.js:673:12)
    at Pipe.callbackTrampoline (internal/async_hooks.js:129:14) {
  killed: false,
  code: 1,
  signal: null,
  cmd: 'cat /sys/fs/cgroup/memory/memory.limit_in_bytes '
}
Error: Command failed: cat /sys/fs/cgroup/memory/memory.stat 
cat: /sys/fs/cgroup/memory/memory.stat: No such file or directory

    at ChildProcess.exithandler (child_process.js:308:12)
    at ChildProcess.emit (events.js:315:20)
    at ChildProcess.EventEmitter.emit (domain.js:486:12)
    at maybeClose (internal/child_process.js:1048:16)
    at Socket.<anonymous> (internal/child_process.js:439:11)
    at Socket.emit (events.js:315:20)
    at Socket.EventEmitter.emit (domain.js:486:12)
    at Pipe.<anonymous> (net.js:673:12)
    at Pipe.callbackTrampoline (internal/async_hooks.js:129:14) {
  killed: false,
  code: 1,
  signal: null,
  cmd: 'cat /sys/fs/cgroup/memory/memory.stat '
}

Obviously those two files, /sys/fs/cgroup/memory/memory.stat and /sys/fs/cgroup/memory/memory.limit_in_bytes no longer exist and the Node.js framework needs them to open a socket. I haven't been able to find a solution on Google. I have tried reinstalling Node and the npm package.

Can anyone help?

I just got a new laptop (ASUS GX501G), and Ubuntu 19.10 is having sound problems. It will not play sound through the speakers or through the headphones. The microphone does not work either. In the 'Sound' portion of the settings, it seems to be recognizing the speakers as an output device properly. Additionally, when I plug in headphones or connect a bluetooth speaker, it recognizes the device change and swaps the icon, name, and settings profile. When I dual boot back into Windows 10, the sound works as expected.

Strangely, the speakers will work briefly for roughly 2-3 seconds after I disconnect a bluetooth headphone device. The bluetooth headset powers off and the speakers play music while it decides where to route the audio next.

I have tried opening alsamixer in the terminal and raising the volume and un-muting the different channels with no success.

Another very odd thing: when I plug in my over-the ear headphones it is picking up a very faint signal to a local Mexican radio station, not sure of the exact frequency or if it's FM or AM. The high production value makes me guess FM. I've never experienced that in a computer before...