Kalarm broke after latest update

Kalarm wont launch after installing all of the latest updates.

 sudo inxi --admin --verbosity=7 --filter --no-host --width                                                                                                                                                                                   ✔ 
[sudo] password for (null): 
System:
  Kernel: 6.1.90-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=ca7fd84c-5967-473c-a2d8-bb37fb208f2e rw quiet
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A wm: kwin_x11 with: krunner
    tools: avail: xscreensaver dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: B450M Pro4 serial: <filter>
    uuid: ffc28570-eccc-0000-0000-000000000000 UEFI: American Megatrends v: P5.00
    date: 03/08/2021
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  System RAM: total: 32 GiB available: 30.74 GiB used: 14.33 GiB (46.6%)
  Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 2667 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK32GX4M4Z2933C16 serial: N/A
  Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 2667 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK16GX4M2Z2933C16 serial: N/A
  Device-3: Channel-B DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 2667 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK32GX4M4Z2933C16 serial: N/A
  Device-4: Channel-B DIMM 1 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 2667 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK16GX4M2Z2933C16 serial: N/A
CPU:
  Info: model: AMD Ryzen 5 5600G with Radeon Graphics socket: AM4 bits: 64
    type: MT MCP arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
    process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA50000B
  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: 16 MiB
    desc: 1x16 MiB
  Speed (MHz): avg: 1608 high: 3900 min/max: 1400/3900 boost: enabled
    base/boost: 3900/4450 scaling: driver: acpi-cpufreq governor: schedutil
    volts: 1.4 V ext-clock: 100 MHz cores: 1: 1400 2: 1400 3: 1400 4: 1400
    5: 1400 6: 3900 7: 1400 8: 1400 9: 1400 10: 1400 11: 1400 12: 1400
    bogomips: 93640
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms extapic
    extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt ht
    hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni popcnt
    pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor
    svm svm_lock syscall tce topoext tsc tsc_scale umip v_spec_ctrl
    v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq wbnoinvd wdt
    xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: safe RET, no microcode
  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: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: Micro-Star MSI
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: DP-1,HDMI-A-1 empty: DP-2,DP-3 bus-ID: 03:00.0 chip-ID: 1002:73ff
    class-ID: 0300
  Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    driver: N/A alternate: amdgpu arch: GCN-5 code: Vega process: GF 14nm
    built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 0a:00.0 chip-ID: 1002:1638 class-ID: 0300
  Display: server: X.Org v: 21.1.13 with: Xwayland v: 23.2.6
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4480x1440 s-dpi: 96 s-size: 1185x381mm (46.65x15.00")
    s-diag: 1245mm (49.01")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,top-right
    model: LG (GoldStar) ULTRAGEAR serial: <filter> built: 2022 res: 2560x1440
    hz: 120 dpi: 93 gamma: 1.2 size: 697x392mm (27.44x15.43")
    diag: 800mm (31.5") ratio: 16:9 modes: max: 2560x1440 min: 640x350
  Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: bottom-l model: BenQ GL2480
    serial: <filter> built: 2020 res: 1920x1080 dpi: 92 gamma: 1.2
    size: 531x298mm (20.91x11.73") diag: 609mm (24") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.6-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6600 (radeonsi navi23
    LLVM 17.0.6 DRM 3.49 6.1.90-1-MANJARO) device-ID: 1002:73ff
    memory: 7.81 GiB unified: no
  API: Vulkan v: 1.3.279 layers: 4 device: 0 type: discrete-gpu name: AMD
    Radeon RX 6600 (RADV NAVI23) driver: mesa radv v: 24.0.6-manjaro1.1
    device-ID: 1002:73ff surfaces: xcb,xlib
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28
    class-ID: 0403
  Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 0a:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-3: AMD Family 17h/19h HD Audio vendor: ASRock driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 0a:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.1.90-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.0.5 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: pipewire-media-session status: active
    3: pipewire-alsa type: plugin tools: pactl,pw-cat,pw-cli
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: e000 bus-ID: 07:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: mld, NetworkManager, systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:2
    chip-ID: 0b05:17cb class-ID: fe01 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 3.18 TiB used: 1.42 TiB (44.5%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 500GB
    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: 2B2QEXE7 temp: 33.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 1y 136d 15h cycles: 248
    read-units: 53,805,159 [27.5 TB] written-units: 278,085,737 [142 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Smart Modular Tech.
    model: SHGS31-1000GS-2 family: SATA SSDs size: 931.51 GiB block-size:
    physical: 4096 B logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: SSD
    serial: <filter> fw-rev: 0Q00 temp: 32 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 133d 8h cycles: 136
    Old-Age: threshold: 1
  ID-3: /dev/sdb maj-min: 8:16 vendor: Smart Modular Tech.
    model: SHGS31-1000GS-2 family: SATA SSDs size: 931.51 GiB block-size:
    physical: 4096 B logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: SSD
    serial: <filter> fw-rev: 0Q00 temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 122d 9h cycles: 136
    Old-Age: threshold: 1
  ID-4: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT1000MX500SSD4
    family: Micron Client SSDs size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B sata: 3.3 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 023 temp: 57 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 244d 23h cycles: 128
    written: 2.21 TiB
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 465.46 GiB size: 457.09 GiB (98.20%)
    used: 233.87 GiB (51.2%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p2
    maj-min: 259:2 label: N/A uuid: ca7fd84c-5967-473c-a2d8-bb37fb208f2e
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 312 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:1 label: NO_LABEL uuid: 4D0D-8D3C
  ID-3: /run/media/ziward/btc raw-size: 931.51 GiB size: 915.82 GiB (98.31%)
    used: 652.76 GiB (71.3%) fs: ext4 block-size: 4096 B dev: /dev/sdb1
    maj-min: 8:17 label: btc uuid: 06fcec6d-12b0-43c3-a429-875af300ad78
  ID-4: /run/media/ziward/data raw-size: 931.51 GiB size: 915.82 GiB (98.32%)
    used: 438.37 GiB (47.9%) fs: ext4 block-size: 4096 B dev: /dev/sda1
    maj-min: 8:1 label: data uuid: 075c599c-8985-4f56-aed0-6955f7a5f131
  ID-5: /run/media/ziward/ilmwlod raw-size: 931.51 GiB
    size: 915.82 GiB (98.31%) used: 127.28 GiB (13.9%) fs: ext4
    block-size: 4096 B dev: /dev/sdc1 maj-min: 8:33 label: ilmwlod
    uuid: bbcc533f-8082-4922-b434-00d26ee5dd65
Swap:
  Alert: No swap data was found.
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-2:2 info: ASUSTek Broadcom BCM20702A0 Bluetooth type: Bluetooth
    driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 0b05:17cb class-ID: fe01 serial: <filter>
  Device-2: 1-6:3 info: Logitech Unifying Receiver type: keyboard,mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c52b class-ID: 0300
  Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-6: 6-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 59.8 C mobo: N/A gpu: amdgpu temp: 54.0 C
    mem: 66.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Processes: 350 Power: uptime: 1d 23h 39m states: freeze,mem,disk
    suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 12.29 GiB
    services: org_kde_powerdevil,upowerd Init: systemd v: 255
    default: graphical tool: systemctl
  Packages: 1812 pm: pacman pkgs: 1780 libs: 493 tools: pamac pm: flatpak
    pkgs: 32 Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: Sudo (sudo) v: 1.9.15p5
    default: Bash v: 5.2.26 running-in: yakuake inxi: 3.3.34

I tried uninstalling and reinstalling. Not really much else to try when the app gets broke by update and wont even launch :man_shrugging:

EDIT:: Issue was resolved by manually clearing files by searching within folders indicated in post marked as solution.

Post the outputs of:

pacman -Qs kalarm
pacman -Qi kalarm

This may be helpful to someone.

in my up to date VM, when I open a terminal and type
kalarm
and then hit enter

I get this:

kalarm
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
glx: failed to create drisw screen
org.kde.pim.kalarm: Kernel alarm timers not available (no CAP_WAKE_ALARM capability)

and the thing starts

Start via menu works as well.

1 Like
    ~  pacman -Qs kalarm                                                                                                                                                    ✔  27s  
local/kalarm 24.02.2-1 (kde-applications kde-pim)
    Personal alarm scheduler
    ~  pacman -Qi kalarm                                                                                                                                                            ✔ 
Name            : kalarm
Version         : 24.02.2-1
Description     : Personal alarm scheduler
Architecture    : x86_64
URL             : https://apps.kde.org/kalarm/
Licenses        : GPL-2.0-or-later
Groups          : kde-applications  kde-pim
Provides        : None
Depends On      : akonadi-contacts  akonadi-mime  gcc-libs  glibc  kauth  kcalendarcore  kcalutils  kcodecs  kcolorscheme  kcompletion  kconfig  kconfigwidgets  kcontacts  kcoreaddons
                  kcrash  kdbusaddons  kglobalaccel  kguiaddons  kholidays  ki18n  kidentitymanagement  kio  kitemmodels  kmailtransport  kmime  knotifications  knotifyconfig
                  kstatusnotifieritem  ktextaddons  ktextwidgets  kwidgetsaddons  kwindowsystem  kxmlgui  libakonadi  libcanberra  qt6-5compat  qt6-base
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 13.86 MiB
Packager        : Antonio Rojas <arojas@archlinux.org>
Build Date      : Tue 09 Apr 2024 06:36:27 PM UTC
Install Date    : Wed 22 May 2024 03:25:34 PM UTC
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

I have kalarm installed; KDE6 fully updated; running on Wayland; and experience no issues such as you describe.

The update hasn’t broken kalarm. It’s more likely a condition that has arisen due to your configuration; something is broken or missing on your machine that kalarm depends on (referred to as a dependency). You might for example check that optional dependencies (such as qt6-declarative) are the correct versions.

You might also consider checking your Linux volume(s) for consistency using fsck to rule out possible damage to the filesystem; and by extension, files that may be needed for kalarm to function.

That is all. Good luck.

I got a slightly later build: Wed 10 Apr 2024 01:36:27 +07

It’s probably my most essential app at this point, so I can testify that it’s running fine and hasn’t skipped a beat yet.

Did you test with a new user?

Maybe it’s time for a cleanup.

1 Like

Well. You are wrong, incorrect, out of place. The update DID break it and other things. No task manager launches with ctrl+esc anymore.

Kalarm worked before the update, it does not after. The update broke it. Idk how you can say it didnt LOL. It did, maybe not for you but it did.

Yeah. Time for complete re-install, something I thought I was avoiding by choosing linux. O well. Time to deal with changing to all new programs and a complete different environment. And then back to NOT updating UNLESS something breaks. But My system would break if I DIDNT update so Ive been forced to for about 2 years.

Its so great that the OS is so complex (I guess) that forums are of very little help unless you share a clone of someone elses system.

I am not sure about a reinstall - just cleaning up Home removed all my bugs after recent updates.

Initially, moving .config seemed to remove most of them, but then later on I needed to clean the cache also.

There are many guides in the forums about updating to Plasma 6. Even just creating a new user would tell you if it’s your system or just your user data.

Again - the forums can’t be much help for something that is actually not broken, it’s an issue with your system, and if you created some kind of issue with your User data, then it’s a User error - and the forum can help a great deal fixing this.

Check out this topic - lots of solutions in there:
https://forum.manjaro.org/t/plasma-6-update-how-did-it-go-for-you/162024

If the update was at fault, then mine would also be in the same state as yours. To argue any differently is ludicrous; or to use your vernacular, “LOL”.

Deciding that it’s “time for a complete re-install” as a resolution also supports my stance. There were guidelines in the respective Update announcement which would have helped you to avoid your current situation. I’m guessing you didn’t read that, and performed this major update without any recommended preparation; rest assured, you’re not the only one.

Manjaro is a rolling release which does indeed require the user to perform ongoing maintenance beyond simply updating. From what you have written, it seems you might be more comfortable with a point release Linux distribution.

There are plenty to choose from, and this could also be an advantage for you. Updates are less frequent: 3-monthly, 6-monthly, or yearly (depending on the distribution), and there’s generally no expectation to learn anything new.

Perhaps you need something like that; only you can be the judge.

Good luck.

1 Like

Yeah. Wow. I understand the hostile language. I was completely unaware of this upgrade to plasma 6 … I was also unaware of how involved running Manjaro actually is. I only update when I see them in the pack mngr due to the issue I had that broke everything whenever there was an update, until I shutdown, restarted, updated, restarted again.

Lucky me it only seems to be one program that broke (and various minor issues like sys vol going in steps of 5’s when it would go single digits before this update)

Many many people using Manjaro should not be but last I checked, it’s not marketed as such and so ya get the million inquires which annoy the regulars and cause hostile language to be thrown around from the different perspectives butting heads CZ they are both right and both wrong but no one is to blame except everyone.

I’ve always had minor hiccups that occur from time to time with updates but they iron themselves out by themselves or I’m able to find a suitable solution within a handful hours of searching. I’ve been using Manjaro for a decade +/- and have been running the current install since … I can’t recall but I want to say at least 2 years, maybe 4.

For me, the update broke kalarm. The update is the event time horizon that delineates between kalarm functioning properly and it not functioning properly. The update broke kalarm. I get your perspective but it’s not the only correct one. To any reasonable user that isn’t super techie, they are going to say the same thing. “Hey, I updated and this program doesn’t work. The update broke the program.” To someone not involved in the tech development space, what else are they suppose to think. Something occurred during update that has resulted in this program not working …but it surely wasn’t the major operation the system just went thru.

Manjaro worked so well for so many years I stopped paying attention to anything.

This update may have only broken kalarm. If that’s the case, which I imagine I’ll figure out within the next few days, then I’d say I managed to make it thru this major update almost unscathed. And I even updated with the package manager while logged in. Honestly not sure if I’ve restarted after the update yet :grimacing: *I restarted and nothing else seems broke.

I appreciate the resources and tips.
I intentionally upgraded to wayland last year, I think; maybe to more well informed individuals that statement doesn’t make sense, idk.
Anyway, if that does make sense and I did, maybe its why im not getting totally sauced by this upgrade.

1 Like

kalarm does actually launch and runs … and uses almost 10% of CPU

It shows up in taskbar for a few seconds and then disappears but stays running.

kalarm runs properly under a new user I just created to test it.

I have not run into any other issues besides this kalarm thing (and the very minor ones that are nothing to complain about but for transparency im mentioning them.)

kclock does not allow vlc playlist files to be used for alarm, neither does qtalarm.

Is it easy to guide me to a resource that will show me how to get kalarm working again under my user, now that I verified it works under a new user? I already deleted what config files I was able to find but it didnt help.

1 Like

This links doesnt work for me. Its gives oops not found

It is in the Member Hub. It looks like you haven’t spent enough time on the forum to be elevated to Trust Level 2, which gives access to the Member Hub:

Understanding Discourse Trust Levels

Trust Level 2 – Member

Members keep coming back to your community over a series of weeks; they have not only read, but actively participated long and consistently enough to be trusted with full citizenship.

Get to trust level 2 by…

  • Visiting at least 15 days, not sequentially
  • Casting at least 1 like
  • Receiving at least 1 like
  • Replying to at least 3 different topics
  • Entering at least 20 topics
  • Reading at least 100 posts
  • Spend a total of 60 minutes reading posts

Users at trust level 2 can…

  • Use the “Invite others to this topic” button for one-click onboarding of new users to participate in topics
  • Invite outside users to PMs making a group PM
  • Daily like, edit, and flag limits increased by 1.5×
  • Ignore other users
  • Edit their own posts for up to 30 days after posting
2 Likes

wow, thats f**ed

Is there a page in profile somewhere that shows these metrics? Or just when you get it, you get it??

Who thought it was a good idea to block new users from viewing posts?
Versus barring new users from replying to certain posts. Amazing!

Well, that sure indicates the problem is with your configuration. I don’t know of any guide that might help. The obvious kalarm-related files (under ~/.config) seem to be:

  • kalarm.notify.rc
  • kalarmrc
  • kalarmresources

Deleting those and rebooting might help; though it seems you tried that. There is also the kalarm directory (under ~/.local/share) which could be moved elsewhere before rebooting (a damaged calendar file might be the culprit).

Otherwise, nothing jumps out screaming “I did it… it was me!”.

Your profile related pages should help:

I imagine it was done to avoid zombie accounts - those who only create an account for the purpose of generating unsolicited spam or otherwise creating havoc with the forum.

Looking at the list of methods posted by @scotty65 it’s not that difficult to achieve TL2; it really just takes some active participation; while taking care not to present oneself as a complete moron.

I just added a like (the heart symbol) to one of your previous posts, so that will likely help to some extent. Cheers.

2 Likes

If KAlarm works on a new user, then it’s your $USER data.

I think you’ll find ALL the files pertaining to KAlarm configuration in the ~/.config and ~/.local` folders…

This is messy, as there are a TON of KDE config files… but if you scroll past the folders in the config folder, you’ll find some that look relevant.

Now, if you do F3 to get a new pane in Dolphin, then CtrlShiftN for a new folder and type the name kalarm-backup

Then you can select (Kalarm) stuff and MOVE it across. I found ‘kalarmrc’ which I’d test on it’s own first.

Make sure you learn how to use ‘filter’ in Dolphin - press / and type ‘alar’ - and everything else vanishes :wink:


Then:
Alt+F2
LogSpaceOutEnter

Then log in and try it again.

As far as the ‘new member’ thing goes - yes, it’s f@rked up… but it does cut down on spam.

We all complained a lot when the OLD forum died, and a NEW forum was created… but relax, it passes. On balance, it does mostly make things better - but it does (as with many other forums) cause issues if you just jump in a forum and want to start posting.

What you end up with is a better experience.

You also never again assume that EVERYTHING should be automatic, just a mindless ‘click to upgrade’.

If you want that, then move on and invest in an Apple phone.

1 Like