this post was submitted on 13 Feb 2024
637 points (96.1% liked)

linuxmemes

21172 readers
984 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 71 points 8 months ago* (last edited 8 months ago) (1 children)

    This. Fucking this. Wobbling windows were around in the early days of Ubuntu's existence which was a long ass time ago and it was probably possible to get them even before that. Surely they've figured out a good way to make them work without fucking up your entire system by now.

    Edit: oh, turns out KDE already has that option on my system.

    Edit 2: Shit. How do you unfuck KDE? Asking for a friend.

    [–] [email protected] 25 points 8 months ago (2 children)

    KDE always gives you enough rope to hang yourself. Like, set the transparency of all windows to 100% and wonder why the system is fucked, or whatever haha.

    Working blind, and from memory (I didn't check my system): depending on your system, there will be a kwin config file in .local or .config or .kde or similar in your home directory. Assuming you have console access, df -h | grep kwin will probably find it for you. Take a peak in the file first to make sure it's reasonable that this is the right file to nuke. Rename it something like kwinrc-backup and restart KDE.

    [–] [email protected] 4 points 8 months ago (1 children)

    Not OP (OC? Not the person you were helping, you get what I mean), are you sure you meant df -h? fd -H seems more useful for to me when trying to find a specific file in a dotfolder, though even that didn't work on my system. fd ignores ~/.config by default, so you need to use fd -u (which is an alias for fd -I -H) to find the correct files.

    Anyways, from your description it seems like the correct file would be ~/.config/kwinrc, which exists on my system.

    [–] [email protected] 7 points 8 months ago

    It's probable there are better ways at finding things, but sometimes these commands are sort of muscle memory and I don't even think to explore what else is out there once I have something that works for me ;)

    It's hard to teach an old dog like myself new tricks. I still think git was a mistake and long for centralized revision control systems... Because that's what I grew up with ;)

    [–] [email protected] 1 points 8 months ago

    Normally, you shouldn't be able to set the transparency to 100% anymore. I remember reporting it as a bug years ago and it getting fix a bit afterwards.

    I've always had my desktops set so that I could scroll on the windows borders to set the transparency. It's very convenient.