tyvm
Another section of the log when this happened:
Aug 15 18:00:48 arch kwin_wayland[3328]: This plugin does not support raise()
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_VALUE in glTexStorage2D(width, height or depth < 1)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glBindFramebuffer(non-gen name)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)
It seems that a namespace only has access to process that originates inside itself
systemctl --user list-units
Failed to connect to bus: No medium found
as we can see, the same user doesn’t have access to other processes so we would need to duplicate every process above the namespace until we could acess the media
would duplicate of everything - pulsewire, dbus, etc - even work ?
IP is like an address to a big skyscraper where a company operates. You are the delivery man and must go to 201.154.76.19 and deliver something. When you get at the reception, you tell them you have a package to deliver to Mrs HTTPS, at room (port) 443. Since Mrs HTTPS is well known and has cleared your entry before, you’re allowed to enter this room and only this room.
If you were to get at the same address and try to access other rooms you would either get refused because they are closed, or if open, someone would specifically need to be in the room so you can deliver something
Malicious actors that wanted access to the building could try to disguise their deliveries and enter the building, that’s why the default policy of most firewalls is “reject” and you specifically need to open a port and have a program listening to it if you want incoming connections.
Mind sharing whhich situations would a timecard be useful ? Probably something that requires enhanced time precision, I just can’t figure it out
Already switched to AMD to enjoy it
I figured the root cause of the problem and a workaround. Journalctl shows this info when starting SVP:
this thread says rusticl is broken
https://www.svp-team.com/forum/viewtopic.php?id=3167&p=17
therefore disabling hardware acceleration, for now, makes svp work again
AMD is the gold standard for general user PCs in the last 5+ years. Intel simply cannot compete at the same energy expenditure/performance. At the same/close price/performance, Intel either burn a small thermonuclear power plant to deliver comparable performance, or simply is worse compared to similar Ryzens
Ryzens are like aliens compared to what AMD used to be before them
So I’d go with them
As for the GPU, if you want to use Linux forget Nvidia
Yeah, it’s advertised as 160hz and even amdgpu_top (which uses xrandr or something like it) says 159.96hz is the first preferred mode, the second being 100hz
I had this problem before with a Nvidia card which reset to 144hz after an update and I could never enable it again. However it’s a mystery as to why it boots up at 160hz in systemd-boot console, and goes back to 144hz when entering KDE or turning the display off
lol my cat actually meows and asks to be vacuumed
How does it differ from arch install + choosing the DE?
My most paranoid config is disabling Ipv4
That’s it. If someone wants to attack me, they will need to adopt IPv6!
…no ?
years ago I couln’t even dream of using bluetooth in linux; few weeks ago I found an old bluetooth dongle and now my usb speakers work just fine - even better than connecting via smartphone because plasma has sbc-xq codec easily selectable. It auto connects everytime I boot the pc, I just had to add btusb.enable_autosuspend=0
to kernel cmdline parameters
make sure you follow these guides, whicever distro you use
if it crashes, try sudo systemctl stop bluetooth.service
and sudo systemctl start bluetooth.service
remember, bluetooth is a very cursed embrace-it-all protocol and may randomly crash/refuse to pair/connect unless you reset the devices manually, and this may happen with any hardware/software
Just don’t upgrade for a while and you become debian
It’s not like windows forcing you to reboot every Tuesday so Edge can come back
"A qsort vulnerability is due to a missing bounds check and can lead to memory corruption. It has been present in all versions of glibc since 1992. "
This one amazes me. Imagine how many vulnerabilities future researchers will discover in ancient software that persisted/persist for decades.
Tyvm for this very well structured guide, I didn’t even realize I was on lemmy until I hit the bottom of it
I thoroughly backup up my slow nvme before installing a new faster one. I actually didn’t even want to reuse the installation, just the files at /home.
So I mounted it at /mnt/backupnvme0n1, 2, etc and rsynced
The first few dry runs showed a lot of data was redundant, so I geniously thought “wow I should delete some of these”. And that’s when I did a classic sudo rm -rf in the /mnt root folder instead of /mnt/dirthathadthoseredundantfiles
Sir, you’re awesome! Thank you a lot for taking your time and explaining what you have found I will try these steps when I have some free time to tinker, and the info and script you have provided has cleared a lot of questions that I had
so it seems that without any config, the traffic passes from wlan1 to wlan0’s network flawlessly; but traffic from wlan0 network stops at the Android device, even with
iptables -P FORWARD ACCEPT
, so I’m clueless on what to do next