Cannot switch Desktop layouts

Issues & Assistance KDE
1

Problem

I'm getting error message, I'm unable to change the desktop layouts kinda locked :frowning:

I got this error message :
Layout Changes have been restricted by the system administrator

Also I cannot use :
Enter Edit Mode

Garuda-INXI

╭─calculus_learner@Computer in ~
╰─λ garuda-inxigaruda-inxi
System:
  Kernel: 5.16.11-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=28b9bda0-b454-461f-9c95-d6e1a406bed4 rw rootflags=subvol=@
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1 loglevel=3
  Desktop: KDE Plasma 5.24.2 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
    vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: H61M-CS v: Rev X.0x
    serial: <superuser required> BIOS: American Megatrends v: 0402
    date: 02/28/2014
CPU:
  Info: model: Intel Pentium G2030 bits: 64 type: MCP arch: Ivy Bridge
    family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB
    desc: 1x3 MiB
  Speed (MHz): avg: 2944 high: 2956 min/max: 1600/3000 scaling:
    driver: intel_cpufreq governor: performance cores: 1: 2932 2: 2956
    bogomips: 11972
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
    IBRS_FW, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics
    vendor: ASUSTeK driver: i915 v: kernel ports: active: VGA-1
    empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0152 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 compositor: kwin_x11 driver: X:
    loaded: intel unloaded: modesetting alternate: fbdev,vesa gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0")
    s-diag: 414mm (16.3")
  Monitor-1: VGA1 mapped: VGA-1 model: LG (GoldStar) 16M35 serial: <filter>
    built: 2014 res: 1366x768 hz: 60 dpi: 102 gamma: 1.2
    size: 340x190mm (13.4x7.5") diag: 395mm (15.5") ratio: 16:9 modes:
    max: 1366x768 min: 640x480
  OpenGL: renderer: Mesa DRI Intel HD Graphics 2500 (IVB GT1)
    v: 4.2 Mesa 21.3.7 compat-v: 3.0 direct render: Yes
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:1c20 class-ID: 0403
  Sound Server-1: ALSA v: k5.16.11-zen1-1-zen running: yes
  Sound Server-2: sndio v: N/A running: no
  Sound Server-3: PulseAudio v: 15.0 running: no
  Sound Server-4: PipeWire v: 0.3.47 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK P8 series driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
Drives:
  Local Storage: total: 465.76 GiB used: 181.91 GiB (39.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD5000AZRX-00L4HB0 size: 465.76 GiB block-size: physical: 4096 B
    logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 1A01 scheme: MBR
Partition:
  ID-1: / raw-size: 128 GiB size: 128 GiB (100.00%) used: 31.62 GiB (24.7%)
    fs: btrfs dev: /dev/sda5 maj-min: 8:5
  ID-2: /home raw-size: 128 GiB size: 128 GiB (100.00%)
    used: 31.62 GiB (24.7%) fs: btrfs dev: /dev/sda5 maj-min: 8:5
  ID-3: /var/log raw-size: 128 GiB size: 128 GiB (100.00%)
    used: 31.62 GiB (24.7%) fs: btrfs dev: /dev/sda5 maj-min: 8:5
  ID-4: /var/tmp raw-size: 128 GiB size: 128 GiB (100.00%)
    used: 31.62 GiB (24.7%) fs: btrfs dev: /dev/sda5 maj-min: 8:5
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 3.71 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 190 Uptime: 1h 34m wakeups: 0 Memory: 3.71 GiB
  used: 2.01 GiB (54.1%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 1822 lib: 377 Shell: fish
  v: 3.3.1 running-in: konsole inxi: 3.3.13
Garuda (2.5.5-1):
  System install date:     2022-05-10
  Last full system update: 2022-03-11
  Is partially upgraded:   Yes
  Relevant software:       NetworkManager
  Windows dual boot:       <superuser required>
  Snapshots:               Snapper
  Failed units:            preload.service systemd-guest-user.service

Links

I have contacted KDE devs. But I got no help from them, I think they are busy in handling things. whatever it is I don't have much problem.

I also read the
https://userbase.kde.org/KDE_System_Administration

But I can't find the desktop layout section or any ways to enable it.
I don't know anything is messed I also tried to reset configs through Garuda-Assistat

2

I see you restored a snapshot from March, i think you'd better update now.
If that doesn't help, I'd try creating a new user, to see if this issue lays somewhere in your home.

2 Likes
3

Or should I compare with guest user

Everything works in guest_user

4

You can try, for sure.
But with the new user then you could gradually move your stuff.
And don't forget garuda-update, you're also in a partial upgrade status.

2 Likes
5

delete (rename)

~/.config/plasmashellrc

3 Likes
6

Done, after I rebooted works fine, you saved my time
THANKS @filo

2 Likes
7

Yes, although a logoff logon might be enough i think

2 Likes
8

I don’t know who’ve sent this message, but you should know your SysAdmin very well!!
It is… YOU!! :rofl: :rofl: :rofl:

3 Likes
9

Off course, System should belive me only if I tell that via configs or super user access. While resetting configs comes to rescue

Something I messed up while creating chroot jails that messed my config I think

10

:rofl: This reminds me of when you are first setting up a box and you run a sudo command before you’ve added yourself to the sudoers file, it tells you something like “So-and-so is not in the sudoers file. This incident will be reported.”

…:face_with_raised_eyebrow: Reported to who?! It’s my computer! :joy:

5 Likes
11

Incidents will be reported to the person in my avatar! :wink:

7 Likes
12

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