How old is the Asus monitor? This might also be a hardware problem, bad caps related. Digital equipment is sensitive to power voltage fluctuations, and when bad caps are in the picture, even more so, making the equpment do all sorts of inexplainable things, like how could one thing I do on this monitor reflect on what the other monitor does or doesn’t. In most cases, a small ground loop or a fluctuation caused by one of the monitors draining power when being turned on or off, might affect what the other one does or doesn’t, if it alredy has failing caps. I’ve seen similar things happen on dual monitor setups when one of them has failing caps. One turns on just fine the other one doesn’t, but you power them in reverse order, hey they work 😂.
Very interesting. The Asus monitor is probably only 2 years old. It does work fine standalone with a spare laptop of mine that is running Windows 10 though.
Have you tried to replicate this behavior in Windows? Try it with a spare drive, see if you get the same irrational thing happening in Windows. If it happens, yeah, it’s a hardware problem 😉… most probably bad caps. Bad batch maybe, even though it’s only 2 years old, who knows.
I did not try replicating this behavior with a Windows install on my desktop. I did however perform a fresh install of Fedora 39 and that appeared to have fixed the issue, which is good news.
I have a laptop still with Windows 10. I got it from my late sister about 4 years ago, booted it up, went and installed Ubuntu (18.04 at the time), and never touched Windows again.
I later read somewhere that W10 was forcibly upgrading itself to W11, so I’m afraid to even boot into it. Should probably take some time to copy everything important over and finally nuke it.
For reference, I’ve been using Linux since around 2012.
This little trick bypasses windows passwords btw, booted puppy on my disused win10 machine a while back and mounted my drive without needing my “unlock windows” pin. Used it to rescue files because that win10 install won’t pass that pin screen anymore, just input the pin and then black screen forever like it can’t load.
It doesn’t forcibly update, but it asks in a fullscreen window that looks as if the update started. Just click no thanks/cancel and it will continue to show the desktop. The window returns sometimes, but not always.
Maybe I can just post here and get a good explanation?
I have been using PopOS for a while now and I am super happy with it, but last time it tried to switch from Gnome to KDE I ended up with a black screen after boot and had to reinstall from scratch.
Does anyone have a good writeup on how to do it properly?
Just install KDE (package name is probably something like kde-desktop) and reboot.
Next login there’s a button bottom right for changing the DE. you don’t need to uninstall gnome desktop.
What probably happened, is that you uninstalled your display manager when uninstalling gnome. This causes you to end up in tty when starting PC when there’s no app configured for the login window
I already saw many issues with PopOS, I think they aren’t really that good at Linux and that’s why it’s messed up, you probably uninstalled most of xorg tools. Try Linux Mint, is more stable and serious.
think it more comes down to all the layers they’re having to deal with: (soon: Cosmic DE) on top of Gnome changes on top of Pop!_OS changes on top of Ubuntu changes on top of Debian changes on top of System76 hardware …
My first ever distro was EndeavourOS. I installed it when I was 13 or 14 years old because someone on reddit said it’s customizable. I never felt like I need to switch to anything else.
I often use Arch in a container, when I need a fhs distro. EndeavourOS is great for desktop use if you don’t want to go through the Arch install process.
DeltaChat is an awesome messenger. It’s federated, quick and simple to use. Also, I didn’t realize DC was on the fediverse for so many years.
The first part is about the meme. Arch has it’s (dis-)advantages depending on the use case.
I wrote the second part because OP mentioned they’ve found the meme “at deltachat”, which is a email-based messenger I use. It’s a topic adjacent to linux as it’s open source software with linux support.
Anyways, this probably depends on the application. You’d have to find out if there is a command line option in the application to start it minimised or in tray.
I just tested it and unfortunately it did not fix the problem. Thing is, not Lutris nor Steam is picking up the gamepad. So I don’t see Steam eating the input, since it also doesn’t seem to recognize it.
Sorry, I misunderstood. What controller are you using? It seems odd that only jstest is detecting it. I initially needed to use an enviroment variable for my Steel series Stratus duo, but I think that was a layout issue.
I am really just using some very cheap off brand controller I found at some store. It does work on my RetroPie, but not my Debian pc. I have now switched over to my steam controller (since it works without any problems) and playing with it feels fine too.
So I guess I the problem has been solved for me, but the mystery of what causes this issue remains.
I’d suggest checking section 5.3 of the arch linux wiki gamepad page. Debian probably either has an older version of the related package or retroPie might have extra patches. Could not say what package for certain though. Arch Wiki Gamepad
I had a similar problem, but its not clear what password prompts you are using, as I dont use these software.
But I guess they have different causes.
You have saved Wifi networks and all just working and will not have borked your Kwallet. But for completion, for auto-unlock kwallet needs to
use blowfish
use an empty or your login password
the wallet needs to be set as default in the systemsettings page (really confusing as the rest is done in the apps window)
But discord may use Gnome keyring, and I think there is no integration to autounlock that on KDE which sucks, as Spotube (I think) and some other apps use it too. You may want to disable keystore if that doesnt log you out.
The other thing with gpu-screen-recorder will probably be a polkit prompt because the app wants access to… you know GPU stuff.
I made a script to fix these prompts by automatically allowing certain polkit actions for users in the wheel group when logged in and not over ssh. Thats basic polkit config. You can add more for things like updating the system, opening kde-partitionmanager, opening virt-manager (this is fixed by adding the user to the libvirt group), mounting and unlocking LUKS drives.
You get the name of the process (hopefully not just “sudo do that” by clicking on “details” in the KDE polkit prompt
So yeah so much without any actual description of the problem or just screenshots of the dialogs and a list of the apps.
For easy debug info targeted towards KDE bugs, i created sysinfo, similar to KDEs kinfo but better and with the option to append app names, package manager query etc.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.