KDE Plasma Dragonized windows have no menu

Hello, it is me, your friendly noob!
OK, so, i installed the dragonized KDE gaming edition Garuda, personally, i do not like dragons, but the performance is very, very good, and it has a lot of fancy features :slight_smile:
There is only one issue i am having with it, personalization…
I am struggling to give it a more classical appearance, i am sorry, i know it is functional and sleek, i AM using it and i can easily navigate it, but i still do not like the way to operate stuff, it is too macos-ish for me, and i am a sworn enemy of apple,
I managed to change many things to appeal to my liking, but i can not, and i can NOT, get the windows of most applications to be ¨ normal" when maximized, they all become ¨fullscreen¨ with no menues or even traditional open/close buttons.
Now, i know what you guys said, and i have been searching around and trying to find the proper answers, but i must say that they do not work, they appear to be made for a different/older version, i did find a lot of other info that really helped me to better understand and configure KDE/Plasma though.
Thank you very much for the help!
-----garuda-inxi-----
System:
Kernel: 6.5.6-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=3db864a1-d307-4cea-b8b8-e25163eaa31a rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.27.8 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-F GAMING II v: Rev 1.xx
serial: UEFI: American Megatrends v: 4007
date: 12/08/2020
CPU:
Info: model: AMD Ryzen 7 2700X bits: 64 type: MT MCP arch: Zen+ gen: 2
level: v3 note: check built: 2018-21 process: GF 12nm family: 0x17 (23)
model-id: 8 stepping: 2 microcode: 0x800820D
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 768 KiB desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB
L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 3997 high: 4000 min/max: 2200/4000 boost: disabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3991 2: 4000
3: 4000 4: 3992 5: 4000 6: 4000 7: 4000 8: 4000 9: 4000 10: 4000 11: 3992
12: 4000 13: 4000 14: 3992 15: 4000 16: 4000 bogomips: 127751
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2080 Rev. A] vendor: Micro-Star MSI
driver: nvidia v: 535.113.01 alternate: nouveau,nvidia_drm non-free: 535.xx+
status: current (as of 2023-09) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 08:00.0
chip-ID: 10de:1e87 class-ID: 0300
Device-2: NVIDIA TU104 [GeForce RTX 2080 Rev. A] vendor: ZOTAC
driver: nvidia v: 535.113.01 alternate: nouveau,nvidia_drm non-free: 535.xx+
status: current (as of 2023-09) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 4
link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 09:00.0
chip-ID: 10de:1e87 class-ID: 0300
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.1
compositor: kwin_x11 driver: X: loaded: modesetting,nouveau,nvidia
alternate: fbdev,nv,vesa gpu: nvidia,nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 101 s-size: 483x272mm (19.02x10.71")
s-diag: 554mm (21.82")
Monitor-1: HDMI-0 pos: primary res: 1920x1080 dpi: 102
size: 480x270mm (18.9x10.63") diag: 551mm (21.68") modes: N/A
Monitor-2: None-2-1 size-res: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: gbm: drv: nvidia
API: OpenGL v: 4.6.0 vendor: nvidia v: 535.113.01 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2
memory: 7.81 GiB
API: Vulkan v: 1.3.264 layers: 10 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 2080 driver: nvidia v: 535.113.01
device-ID: 10de:1e87 surfaces: xcb,xlib device: 1 type: discrete-gpu
name: NVIDIA GeForce RTX 2080 driver: nvidia v: 535.113.01
device-ID: 10de:1e87 surfaces: N/A device: 2 type: cpu name: llvmpipe
(LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM
16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 1102:0012 class-ID: 0403
Device-2: NVIDIA TU104 HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
link-max: lanes: 16 bus-ID: 08:00.1 chip-ID: 10de:10f8 class-ID: 0403
Device-3: NVIDIA TU104 HD Audio vendor: ZOTAC driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 4 link-max: lanes: 16
bus-ID: 09:00.1 chip-ID: 10de:10f8 class-ID: 0403
API: ALSA v: k6.5.6-zen2-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.81 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:
Drives:
Local Storage: total: 2.81 TiB used: 22.87 GiB (0.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKNW020T8
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: fw-rev: 004C temp: 39.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: fw-rev: T1.3 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD5000AAKS-00TMA0 size: 465.76 GiB block-size: physical: 512 B
logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
tech: N/A serial: scheme: MBR
ID-4: /dev/sdd maj-min: 8:48 vendor: A-Data model: USB Flash Drive
size: 57.81 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial:
fw-rev: 1100 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 1.86 TiB size: 1.86 TiB (100.00%) used: 22.87 GiB (1.2%)
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 1.86 TiB size: 1.86 TiB (100.00%)
used: 22.87 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 1.86 TiB size: 1.86 TiB (100.00%)
used: 22.87 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 1.86 TiB size: 1.86 TiB (100.00%)
used: 22.87 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.51 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 48.1 C mobo: 40.0 C gpu: nvidia temp: 36 C
Fan Speeds (rpm): cpu: 2836 case-1: 0 case-2: 0 case-3: 0 gpu: nvidia
fan: 26%
Power: 12v: 10.08 5v: N/A 3.3v: N/A vbat: 3.25
Info:
Processes: 404 Uptime: 5h 58m wakeups: 2 Memory: total: 16 GiB
available: 15.51 GiB used: 3.24 GiB (20.9%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1964 libs: 563 tools: octopi,paru Shell: fish v: 3.6.1
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.30
Garuda (2.6.17-1):
System install date: 2023-10-08
Last full system update: 2023-10-09 ↻
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut nvidia-dkms
Windows dual boot: No/Undetected
Failed units:
-----garuda-inxi-----

In ~/.config/kwinrc, the property you’re looking for is under the group Windows named
BorderlessMaximizedWindows. You can edit this value to be false in your case.

Then you can do either of the following (depending on your WM) to activate the changes

 kwin_x11 --replace
 kwin_wayland --replace

The easier method, though, is to change it via the terminal directly using

kwriteconfig5 --file ~/.config/kwinrc --group Windows --key BorderlessMaximizedWindows false
qdbus org.kde.KWin /KWin reconfigure

This method will auto reload for you as well.

If you’re having trouble finding answers to something, sometimes it helps to search the question in reverse. By searching how to remove, I was able to find this answer.

In the future, someone like you might be searching the forum for this answer. With a title named “Dragonized KDE woes :S”, they are more unlikely to find the relevant information inside. Please consider making your titles related to the issue for the benefit of others.

Also, always post garuda-inxi or SGS is going to come get you! :rofl: Had I had that information, I would have been able to give a more personalized answer based on your WM.

5 Likes

OK, thank you a lot for the help! i do prefer to use CLI commands, and your answer was tailor-made for me.
I will post the inxi results, but i had no idea it was so necessary.

1 Like

Please post always your terminal in- and output as text like
~~~
garuda-inxi
System:
Kernel: 5.18.15-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
parameters:
~~~

looks like

garuda-inxi
System:
  Kernel: 5.18.15-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters:

in forum.

Seems you do not read the template:


Please read the following template before requesting assistance:

Please post the terminal/konsole input and output as text (no pictures) from the following command:

garuda-inxi

Refusing to post the output of the required “garuda-inxi” on a help request will likely result in you not receiving any help from the Garuda team. A failure to provide your system specs may also result in your thread being closed without notice, (as without this information providing assistance is often next to impossible).

Before opening a new help request, please search the Arch and Garuda Wiki’s, and read any relevant sections related to your issue. Also, thoroughly search any error messages in the forum’s search engine and on the web. For in depth information on how to search for answers to Linux issues effectively, read the tips on the Garuda Wiki:

Please report in detail everything you have already attempted to solve your problem.

The template above should be deleted before posting your help request.

2 Likes

Yes i read that, but i was not understanding that this kind of issue required me to post the inxi results, i mean, there is nothing broken, at least, not that i had detected, this was just a request for assistance on personalizing the UI.
Still, this is not the first time i have issues with inxi, so i will just post my inxi results by default on any new threads i open from now on.
Again, thank you very much for the help and patience.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.