In anticipation of the Steam frame, I bought a VR headset from Pico and installed the Steam Link VR app on it.

But Steam VR on linux appears quite unstable to me. Once I initiate the connection from the headset, Steam VR crashes with this error:

SteamVR failed initialization with error code VRInitError_IPC_CompositorConnectFailed: "Shared IPC Conpositor Connect failed (306)"

It works if I try it a few times, restart steam, restart the headset, but this always takes a few minutes and isn't really fun.

I tried searching for this error, but couldn't find much about this issue except some github issues ( #623, #835).

Does anybody here know how to fix this or at least reduce the number of crashes?

My system:

• bazzite-gnome:stable
• Bazzite
• linux 6.17.7-ba22.fc43.x86_64
• B650M-HDV/M.2
• AMD Ryzen 5 8400F (12) @ 4.76 GHz
• AMD Radeon RX 6600 XT [Discrete]
• 7.57 GiB / 30.92 GiB (24%)
• Steam VR 2.14.5
• Pico 4

I hope this community is the right place to ask this question.

This popup was recently introduced in PR-2174.

I don't know exactly why, but voyager prompting me that I'm about to lose my progress was sort of strange to me in the context of scrolling on lemmy.

I understand why someone wants such a feature, but IMO this should be turned off by default and available as an option.

Hello,

As graphene dropped the QBR update this week, I gave the new desktop mode a try. However, I couldn't find an option to set the screen resolution. Everything looks really "pixelated" and text is hard to read.

Does anyone know how to set the external screen resolution to 3440*1440p?

(Pixel 8a, Graphene OS)

Sometimes I wonder whether all this "security awareness training" has any effect at all.

In his groundbreaking new research, HTTP/1.1 Must Die: The Desync Endgame, Kettle challenges the security community to completely rethink its approach to request smuggling. He argues that, in practical terms, it's nigh on impossible to consistently and reliably determine the boundaries between HTTP/1.1 requests, especially when implemented across the chains of interconnected systems that comprise modern web architectures. Mistakes such as parsing discrepancies are inevitable, and when using upstream HTTP/1.1, even the tiniest of bugs often have critical security impact, including complete site takeover.

This research demonstrates unequivocally that patching individual implementations will never be enough to eliminate the threat of request smuggling. Using upstream HTTP/2 offers a robust solution.

I just read this article in a marketing blog from portswigger, the maker of the penetration testing tool burp suite.

Can someone with more insight explain what we're supposed to do? Completely disabling HTTP/1.1 is probably not doable for many organisations.

Context

Made with Mistral / Le Chat.

create a funny 4 panel comic, how to draw a lion. panels 1-3 contain extremely basic shapes of the lion, panel 4 the finished, colored lion. this comic should be fun because the step from 3 to 4 will be ridiculously hard.

Love it when someone falls for phishing, gives away their login, and just… says nothing. Really helpful.

As a fun experiment, I asked ChatGPT to create an image of me based on my chat history. I've been chatting with it for a while, so it has some ideas. Here is an example prompt that you could use to try this too:

Create an image of how you imagine me to look based solely on our chat history. Estimate my age, gender, hairstyle, skin tone, body type, clothing, and background scene. Use clues from my personality, interests, and writing style to visualize a realistic portrait.

If you use ChatGPT, feel free to share how the AI imagines you to look - based solely on your conversations!

Context