Afaik the X11 standard says that this shouldn’t be done and that workspaces should span all monitors (or something along the lines of that), thus most DEs don’t do this (I’ve read this in the gnome issue tracker), don’t ask me why cause I also hate this behaviour. Most window managers will do that however and luckily it’s super easy to replace xfwm with another window manager. I use i3 inside xfce on my work laptop, this guide describes how to set it up with ease
I pretty new to Linux gaming but I love it. Currently playing games directly from Steam and Blizzard games via Bottles. Please help me out with a few questions. What is the use case for gamescope? What is the use case for Heroic? Is it instead of Bottles/Lutris?
Game scope is a micro-compositor, it’s how the Steamdeck handles games and probably steam. Basically the settings there, you can have the game in 1080p but upscaled by FSR/DLSS to 4k. The difference is that only the game is upscaled, not the whole system
Heroic is a launcher for Epic, Amazon, and GOG
Yes, it can be seen as an alternative to Bottles/Lutris but the stores and libraries are baked in
X11 and Wayland are just protocols. These protocols are used to abstract the window drawing from the actual hardware and runtime environment as much as reasonably possible - because nobody wants to maintain 3215 versions of their app for different runtime environments. So in order to be shown on the screen an app needs to implement either the X11 or the Wayland protocol (or both!).
The piece of software that is on the other side depends on whether the app is using X11 or Wayland. For the sake of simplicity let's assume that the app does only support one of those. If the app supports Wayland then it will try to connect to a Wayland compositor. The compositor implements every part of the protocol and makes sure that the window is rendered on the screen and that user input is forwarded to the app. If the app supports X11 then it will try to connect to a X server and take the role of an X client. This is (on Linux, essentially) always X.org*. X.org also implements every part of the protocol and makes sure that the window is rendered on the screen and that user input is forwarded to the app.
Unless you're running a Wayland compositor, then it will connect to XWayland which passes through the window to your compositor.
Wayland compositors have full control over the apps while the abilities of apps are purposefully restricted.
A window manager is just another regular, boring, old X client connecting to the X server. It doesn't actually abstract anything. It can move windows because the X11 protocol allows it to, but any other X client could just as well move all other windows around, read all user input to all other windows and even move the mouse around as it pleases.
So, to be specific, there is no mouse pointer bug in Virtualbox while using Wayland. There is a mouse pointer bug affecting specific Wayland compositors, likely because they enforce GPU hardware acceleration that is lacking in either your VM or the Linux kernel because of missing drivers. Try using a different compositor, (re)installing Virtualbox Guest Additions with the correct version on the guest system and/or check whether hardware acceleration is enabled for the VM and has enough video memory.
What makes you say Intel sucks? The A730M should be somewhere between an RTX 3060 and 3070 but with 12GB of VRAM. From my experience with Intel iGPUs, the software experience is very nice, so I just expect the same thing but with faster performance.
I’ve tried an A730M laptop last year when they were new, and the drivers worked fine, everything was working out of the box. The only issue was that performance was not stable and power usage was high, but I’m assuming performance will only have improved with 12 months of driver engineering from Intel.
The Intel discrete cards are fantastic value for money. There’s plenty of folks on the internet who can attest to this. Intel’s support story in general (so not just graphics cards) on Linux has been nothing less than sterling. If you’re using any Linux kernel you can expect Intel stuff to just work. It’s been this way for at least a decade.
When is the last time you tried Intel hardware and with what software? I ask because your links do not really tell the same story as your post.
The first link says that Mesa got “more Intel optimizations”. That sounds like a good thing. It basically says the same thing about AMD and NVIDIA. The only GPU “crash” that was addressed was for AMD which is widely regarded as the best option for Linux. I would not read that article and come away with any concerns about Intel.
The second link says that kernel 6.2 added “full Intel support”. We are now in kernel 6.7. I use a rolling release and how a much newer kernel than 6.2. A brief Google leads me to believe that 6.5 ships with both Ubuntu 23.10 and Fedora 39.
I have not used these cards myself so I do it know but others have said the experience was decent now. The OP does not seem that demanding. If it ok now and actively improving, he may be quite happy. It sounds better than nouveau for sure. Is it really as bad as you say?
Any chance there’s a Debian repo for bcachefs? I’d want to see how it does on an extra drive in my server. Or will I have to compile it the old fashioned way?
For bcache, it is available in apt, I think. You just need to set the ppa. For bcachefs, I think you need to wait for 6.7 to land on Debian or compile it yourself.
Also Brodie’s podcast Tech Over Tea. I was on the podcast so I’m a bit biased, but he has a lot of open source developers from different projects on and they are always interesting.
The ultimate couch laptop will be an M1 MacBook Air as it has no fans and a suped up phone chip so it doesn’t heat. It also has amazing battery life… But it’s still pretty expensive and it cannot be repaired. Otherwise old MacBooks should be pretty good because most of the Intel models used relatively low end chips because their thermal design was so limited
Can confirm, I use an old HP elitebook from work. Battery life is great, beats my wives new lenovo. More than powerful enough to browse the web and play in the terminal. Also only gets hot if I run a game on it; I wouldnt advise that though.
From a developer’s standpoint, one of the bigger pain points of Wayland is window embedding.
If you want to embed from an external process, the only way to do this is to have your application expose its own Wayland compositor and then have the embedded process use that Wayland compositor. No one has made a library for this as of yet.
If you want to embed from the same process, it shouldn’t be too difficult; you just need a wl_subsurface. However, this doesn’t work too well with most GUI toolkits.
Wayland is just radically different from every other windowing API, and I’m hoping that the GUI toolkits can adapt.
Hopefully they’ll build in support for disroot, fastmail, posteo, protonmail, tutanota, and other opensource encrypted mail agends that don’t provide a bridge.
Edit: so the summary of the video is “marketing”. Linux, KDE, and opensource projects in general need way better marketing. If Linux could rebrand itself as anything but “the geek thing”, I bet it would be much more successful.
Encrypted mail providers should require a bridge in order to be able to pull or send emails with. Protonmail has “Proton Bridge”, tutanota has nothing. I see now that disroot, fastmail and posteo have direct SMTP access 🤔 That leads me to question: what actually is encrypted? Direct SMTP and IMAP access probably means they can read your mail.
There is encryption at rest (storage encryption), transport encryption and end-to-end encryption. E.g. Posteo has transport encryption and optional storage encryption. With activated storage encryption, Posteo cannot read your mail because the encryption key on their server is only usable with your password (which they do not store). Proton Bridge adds end-to-end encryption to Protonmail
it’s certainly more streamlined. I think ‘better’ is a more reletive term here. Certainly for non-problem games that will simply work under proton GE, it’s better.
I use NixOS but I don’t bother with automatic deployment or even automatic formatting. I don’t feel it’s necessary in a homelab setting as hardware failure rarely happens at such small scale and the manual steps left aren’t that significant.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.