Based on the way they handled this, and their replies here, you won’t be seeing it ever. This is TOP DOWN community at it’s finest.
Maybe we should all just blame the time zone difference and stick our heads in the sand. It seems to work for those in charge.
You’re the same troll that started all this last time. Concern trolling is shameful behavior.
You’re the same troll from last time.
At least this time, you provided a handy sign-up list that can be shared far and wide. Kudos to you for linking to and sharing piracy resources with the general public. I sure hope you don’t get banned for breaking the new rules.
The decisions you make are one thing. The way you keep handling them so incredibly poorly is quite another.
A problem as old as the hills. I solved that problem many years ago by moving away from KDE, lol. Sorry I have no applicable advice.
Cover/remove any brand name labels. Duct tape and spray paint are ugly. Use them.
Lock it to something solid. Use multiple, high quality locks if you can. Lock it where there is video surveillance if possible. Never leave it long. Never ever leave it outside overnight.
Greetings from Berlin, where more than 25,000 bikes are stolen each year. That’s 70 per day, or 3 per hour.
Despite following my own advise above as best I could, I have lost 3 bikes in the last 20 years. I still ride a bike everywhere though, 100% of the time, averaging over 5000 km a year.
Get out there and explore your city!
If memtest is showing errors, something is wrong with the RAM. Either the voltage or timing are incorrectly set in BIOS, or maybe overclocked, or one of the sticks isn’t seated properly, or defective. Try memtest with one RAM stick at a time with recommended voltage/timing to rule out a defective stick.
Hier sind zwei drei, die mir sofort einfallen:
I have had random issues for the last 2 years where the active bluetooth adapter just vanishes suddenly and cannot be revived without a reboot (or oddly sometimes sleeping and re-awakening works). Some kernels are better than others, but it has never completely gone away. Often it is fine for days or even weeks of uptime, then it will occasionally crash within minutes or hours of booting. I use it for a mouse, which simply stops working mid-use.
In my case it’s a built-in adapter that’s tied to an internal USB hub, and it is the entire USB hub that is crashing and vanishing. When it happens dmesg says the hub is no longer accepting the address assigned. Error 62 and or 110.
This is on a Lenovo Thinkpad currently running anywhere from kernel 5.15 to 6.5 with the same random issue.
That’s what I have done too. New account, new donation - elsewhere. Just deleting all my old posts and comments here now, aside from the ones pertaining to this topic.