

deleted by creator


deleted by creator
I have no idea what this is, and there’s no links. Second.
From the features talked about, I’m guessing a browser.


Honestly don’t know why people are up in arms and even posting about it. They aren’t saying they are removing the capability, just the default. Big whoop.


And if you’re new to this world, my point stands exactly as you’re describing: you don’t buy hardware that is wildly incompatible with everything, and then complain when it doesn’t work. Which is what he’s doing here.
Yes, I understand he’s familiar with this world through his FOSS efforts, and yes, I get that it worked under X11 (only the display server and not most apps at the time, but I digress), but my point still stands.
The tone of the writing is an impatient “I’M STILL WAITING OVER HEEEERE”, and the response should be “Valid, but you’re going to continue waiting, so deal with it.” because UNLESS you intend to help contribute and fix the problem yourself, you’re at the whim of capacity of the project that is working on whatever features you need working. You’re getting it for free, not contributing, and still complaining.
I find nothing more insufferable than people who do this exact same thing, and are extreme outliers to begin with. You know how many people have 8k monitors even to this day? Less than 1%, and I’ll wager that the vast majority of them don’t run in 8k resolution, because why? Literally nothing you’re going to touch - even in video production - is going to use it.


It’s literally the framing of the article. It’s in the setup of the article. You want to pick and choose the content of the writing to have your point come true, go ahead and be that pathetic. I won’t even try and stop you. 🤣


It’s literally part of the same article. Right there. Click above. Second paragraph. Link right there. Talking about buying the hardware I years ago. The framing of the entire article. The point of the thing. The point of my comment. Don’t know how much more clear it could possibly be.
Are you trying to just ignore it? Revisionist history of a blog entry? Lololz. Sad, kid.


If you’re too stupid to click a fucking link at the top of the article, then read my very simple comment detailing his history with this from 2017—not 2025—then it is you can’t read, and are just flailing and pathetic here. Can’t help you, kid.


Depends on when you deleted it and how much activity time on that drive has passed. If it’s just an ext4 drive and you haven’t had a large number of changes to that partition since it’s been deleted, some different recovery tools may find it.
Photorec is pretty capable though, so if it’s not finding it, that’s probably the end of that.


Wow, you must be really bad at everything then.
What I’m saying is you don’t by a fucking car before they build the roads to the area you want to drive to. Using your analogy which even you can’t make work 🤣


Your comment to me is that he was NOT buying hardware incompatible with anything but Wayland, and you were responding to my point that he most definitely was…because we quite literally wrote about it himself in 2017 when he got said hardware.
Not sure where your entitled sarcasm comes from when you’re just not reading anything in the first place. His assertions, not even mine.


Pi-hole is fine.
You don’t need DNS forwarding from your modem, just your router. You could also just assign clients on your network your pi-hole address as DNS to block as much as you can.


Then you didn’t read it. He linked it right at the top of the post.
Anything immediately in the position after for is an assignment of whatever you put there as a temporary variable inside the loop. You can call it whatever you want. The “i” is just used a lot in examples in programming for “item” or “iterate”, but you can literally call it anything. Anything that refers to it later will have a single item from the list in $LIST assigned to it for each run through the loop.


Apparently you didn’t read his own referenced write-up on that: https://michael.stapelberg.ch/posts/2017-12-11-dell-up3218k/
Exactly as I described.


/etc/fstab on your root drive (not the LveUSB filesystem) to ensure they match as the ones detected while in LiveUSBReport changes here.


No, it’s actually the opposite. He has an 8k monitor. Get rid of that, and then he has no blockers to using things the way he wants. Pretty simple solution.
If you buy hardware that is wildly incompatible with almost everything, then there’s your problem. You don’t buy things knowing it’s incompatible, and then wait for compatibility to come around whilst complaining about it UNLESS you intend to buy it to put some effort into making it work on your own.
That’s the entire point of this ecosystem and being able to upstream fixes.


Dude…I’m not even eating my time with y’all who have zero clue as to how QA/CI/UAT works. It’s such a waste of time.
Steam/Proton is only tested for KDE/GNOME, and that’s it. Hands down. Not even up for fucking debate. It’s a FACT.
You can read the docs, repos, GitHub Issues, forums, and everything else you want. That’s the facts, and it’s not going to change. Just because it’s OSS doesn’t mean they have all the time in the world to make sure your edge cases work FFS.


2nd paragraph:
Unfortunately, the driver support situation remained poor for many years. With nVidia graphics cards, which are the only cards that support my 8K monitor, Wayland would either not work at all or exhibit heavy graphics glitches and crashes.
So answering the headline question: it would work if you just stopped using the 8k monitor


deleted by creator
I got it working under both Wine and Bottles for someone that needed it, but it was a real pain in the ass, and the reports on actually successfully doing so are hit or miss.
Found this solid write up on various options and results though, which sounds like it could be helpful for you while investigating: https://gist.github.com/eylenburg/38e5da371b7fedc0662198efc66be57b