Not able to Add any new Widgets, Package Type "Plasma/Applet" not found

Hello Garuda Community! I recently switched after nuking my Windows partition and wondering if I even need anything specific to it. So here I am.

I had to switch from Wayland to X11 because my Nvidia drivers bork everything, especially my go-to Browser brave which behaves beautifully so long as I don’t switch to Wayland. Not sure if this is of any importance but I thought I should add it.

I’m currently on the dr460nized version of Plasma. I have been trying to get GCal Sync to work with calendar applications on the menu bar. For that I have heard that the Event Calendar widget is the way to go. However, trying to either download or install it via a link does not work.

The Context Menu “Add Widgets” and respectively “Get new Widgets” is missing from my Desktop environment.
When I start Edit Mode and select “Add Widgets”, no window or anything pops up. I can only really select the alternative widgets on the digital clock widget but not add anything else.

I tried installing the plasmoid via Konsole, only to get the following output:

kf.package: Invalid metadata for package structure "Plasma/Applet"
Package type "Plasma/Applet" not found
kf.coreaddons.desktopparser: Unable to find service type for service "Plasma/Applet" listed in "/tmp/kpackagetool5-fTNmop/metadata.desktop" - service type search directories were ("/home/dschib/.local/share", "/usr/local/share", "/usr/share")
Successfully installed /home/dschib/Downloads/eventcalendar.plasmoid

It said successfully installed but seemingly did not realize what it was actually installing.
Trying to run it via Browser gives me this error:

Could not read file ocs://install?url=https%3A%2F%2Ffiles04.pling.com%2Fapi%2Ffiles%2Fdownload%2Fj%2FeyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpZCI6IjE2NTE1ODkwMDE…dWxsfQ.a5xoYdL9vJ8BOFFGiAhPiM1TFCsTlCwF3jvkeBl8TCI%2Feventcalendar-v76-plasma5.13.plasmoid&type=plasma5_plasmoids&filename=eventcalendar-v76-plasma5.13.plasmoid.

What am I missing? I did not find any hints on how to resolve this issue because the most I see is how to right-click the desktop to add widgets.

EDIT: Even if the Widget itself might not be updated for Plasma 6, this seems to be a general issue? Or does it have to do with changes to Plasma 6 that prevent me from getting new widgets? Any hint here would be appreciated so I know what to do or simply to wait.

Please post your garuda-inxi as requested by the template.

The Event Calendar widget does not work with Plasma 6.

This is for the reason mentioned above.

Do not install Plasmoids via terminal!

Welcome to the community :slight_smile:

3 Likes
Kernel: 6.8.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=4a466e50-60d7-4073-b8c9-b66e1af59a62 rw rootflags=subvol=@
quiet resume=UUID=3ffce4e8-7a4f-4b8c-bdbd-112904b36efa loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.1.0
wm: kwin_x11 with: krunner vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: B450M PRO-VDH MAX (MS-7A38) v: 8.0
serial: <superuser required> uuid: <superuser required> BIOS: American
Megatrends LLC. v: B.G0 date: 07/26/2022
CPU:
Info: model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 3763 high: 4106 min/max: 2200/4208 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3600 2: 4099
3: 3646 4: 3717 5: 4106 6: 3600 7: 3829 8: 3600 9: 3600 10: 4101 11: 3569
12: 3693 bogomips: 86401
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2060] driver: nvidia v: 550.78
alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current (as of
2024-04; EOL~2026-12-xx) arch: Turing code: TUxxx process: TSMC 12nm FF
built: 2018-2022 pcie: gen: 2 speed: 5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s ports: active: none off: DP-1 empty: DVI-D-1,HDMI-A-1
bus-ID: 29:00.0 chip-ID: 10de:1e89 class-ID: 0300
Device-2: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-2.1:5
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 23.2.6
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3440x1440 s-dpi: 109 s-size: 802x333mm (31.57x13.11")
s-diag: 868mm (34.19")
Monitor-1: DP-1 mapped: DP-0 note: disabled model: Huawei ZQE-CBA
serial: <filter> built: 2022 res: 3440x1440 hz: 100 dpi: 110 gamma: 1.2
size: 797x334mm (31.38x13.15") diag: 864mm (34") modes: max: 3440x1440
min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2
memory: 5.86 GiB
API: Vulkan v: 1.3.279 layers: 11 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 2060 driver: nvidia v: 550.78 device-ID: 10de:1e89
surfaces: xcb,xlib
Audio:
Device-1: NVIDIA TU104 HD Audio driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 29:00.1 chip-ID: 10de:10f8 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 2b:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-2.1:5
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Device-4: SteelSeries ApS Arctis 7
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 5-2.3.1:9 chip-ID: 1038:12ad class-ID: 0300
Device-5: fifine Microphone driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 5-2.3.3:11
chip-ID: 3142:a601 class-ID: 0300 serial: <filter>
Device-6: Creative Sound Blaster Play!
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 5-2.3.4:12 chip-ID: 041e:30d3 class-ID: 0300
serial: <filter>
API: ALSA v: k6.8.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.5 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: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 25:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp37s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-2.2:6
chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
IF: enp43s0f3u2u2 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:2
chip-ID: 0a12:0001 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
lmp-v: 6 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 3.07 TiB used: 1.7 TiB (55.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SA2000M8500G
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: S5Z42105 temp: 41.9 C
scheme: MBR
ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: Extreme 55AE
size: 465.73 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 3000 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD20SDRW-11VUUS0 size: 1.82 TiB 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: HDD rpm: 5400 serial: <filter> fw-rev: 1028 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: SanDisk model: USB 3.2Gen1
size: 114.6 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 1.00 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-5: /dev/sdd maj-min: 8:48 vendor: Intenso model: SSD SATAIII
size: 238.47 GiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 0506 scheme: MBR
Partition:
ID-1: / raw-size: 448.67 GiB size: 448.67 GiB (100.00%)
used: 179.2 GiB (39.9%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-2: /home raw-size: 448.67 GiB size: 448.67 GiB (100.00%)
used: 179.2 GiB (39.9%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /var/log raw-size: 448.67 GiB size: 448.67 GiB (100.00%)
used: 179.2 GiB (39.9%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /var/tmp raw-size: 448.67 GiB size: 448.67 GiB (100.00%)
used: 179.2 GiB (39.9%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.54 GiB used: 4.15 GiB (26.7%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12
dev: /dev/zram0
ID-2: swap-2 type: partition size: 17.09 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p2 maj-min: 259:2
Sensors:
System Temperatures: cpu: 64.5 C mobo: N/A gpu: nvidia temp: 55 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
Memory: total: 16 GiB available: 15.54 GiB used: 7.23 GiB (46.5%)
Processes: 487 Power: uptime: 2h 20m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.17 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2043 libs: 557 tools: octopi,pamac,paru
Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi default: fish
v: 3.7.1 running-in: konsole inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2024-05-03
Last full system update: 2024-05-05 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       <superuser required>
Failed units:

My bad about garuda-inxi, here is the output.

Not being able to install event calendar due to Plasma 6 makes sense. Did Plasma 6 also change the way that you can get Widgets in general? I did expect there to at least the context menu that (apparently) still was present on Plasma 5.

Do not install Plasmoids via terminal!

Sorry it was a last-ditch effort before realizing that it was probably due to the newer version of Plasma. :see_no_evil:
Should I try removing what was installed or did it simply not do anything because it didn’t recognize the package type?

No, the path is still the same. But it doesn’t work for you. Plasma 6 is currently a bit buggy for some users.

Yep, remove it again. The same way you installed it, just the other way around.

Edit: A quick search of the KDE bug list was unsuccessful, but it is definitely a KDE bug.

If you haven’t done so by now, reboot and check again.

1 Like

It’s not so much Plasma 6, but mostly AUR scripts that have not been updated to accomodate the Plasma 6 upgrade by their developers/maintainers. To be fair, they have had plenty of warning and the time of do so.

But in their defense, their developers are just people users humans, some of whom have moved on to greener other pastures. So to speak.

Some will be updated, some will not, but sooner or later somebody–could it be you?–will step in to fill the void with a new, functioning Plasmoid! :smiley: :wink:

1 Like

Yea, I agree with you for the most part. But the issues with the panels in plasma 6 are present in all Linux distros.

Nope, I don’t need these gimmicks. I run Vanilla Arch w/o a desktop environment…only tty :grin:

1 Like

Of course they’re also in vanilla Arch + Plasma, since, you know, “vanilla”… :wink:

Are you bragging or complaining? Lynx must suck. :wink: :smiley:

1 Like

Both. Unfortunately, I only have Windows + Lynx in a Powershell, so every day I sit at my hack_o_mat - wearing a black hoodie and sunglasses - and infiltrate all the Linux forums :sob:

1 Like

6 posts were merged into an existing topic: Off Topic Chit Chat - (Silliness factor 5)

If you fresh installed kde 6 they did change “Add Widget” to not show in the R click menu. If you upgraded from 5 it should still be there.

You have to right click empty desktop - click “Enter Edit Mode”
Then it will be at the top of the screen.

You have to right click empty desktop - click “Enter Edit Mode”
Then it will be at the top of the screen.

I moved that bar to the bottom of the screen so it doesn’t get obscured by the top bar, but clicking on “Add Widget” does not open anything. Neither a window nor any kind of other context menu.

I’m away from my device for the next two days, but I did reboot quite a few times on Sunday without there being any kind of change. I made a fresh install with Plasma 6.

got ya the only thing I can think of your missing a package of some kind. maybe kdeplasma-addons

1 Like

Should be able to get added via Octopi right? Will take a look once I can get back to my desk.

@Bro: I have no idea how you come up with something like that. This has nothing to do with arch, the problems with plasma 6 also affect fedora and kde neon, for example.

@Kresimir: Says someone who has an empty gitlab account and was banned from the endeavour forum.
How about you contribute something constructive, for example here:

or these two topics:

and go through all the logs chronologically and give your opinion? A second opinion is always helpful and contributes to finding a solution.
But these are just examples. I know that you are not stupid and could help with many problems.
The entire community would benefit from this.

Personally, I have nothing against having fun. But if you have nothing better to do in a topic - where someone is looking for a solution to a problem - than trolling, you should register on reddit.
There’s too much OT here again btw.


@dschibster: You can also try reinstalling Plasma, maybe helps:

sudo pacman -S plasma-workspace plasma-desktop

reboot.

Another option would be to change the global theme to “breeze” and check whether the “add widgets page” works.

You can also try creating a new user account to check if it works without any issues.

Or you wait for the next version of Plasma and hope that the bugs have been fixed :slight_smile:

I was agreeing with you. I apologize for the misunderstanding. I must have been THC-deficit. :wink:

1 Like

After I got back to my desk and tried it again, the widget window opened up to the left. Nothing I did differently per se, but it seems like this is now resolved. Now to only hope someone else gets on a calendar widget with Google Calendar integration. :smiley:

2 Likes

Spontaneous self-healing for the win :sweat_smile:

3 Likes

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