https://bugs.kde.org/show_bug.cgi?id=460389
--- Comment #19 from ali_deda <ali_d...@gmx.com> --- sudo downgrade libical loading packages... warning: downgrading package libical (3.0.15-2 => 3.0.14-1) resolving dependencies... looking for conflicting packages... Packages (1) libical-3.0.14-1 Total Installed Size: 7.11 MiB Net Upgrade Size: -0.06 MiB :: Proceed with installation? [Y/n] y (1/1) checking keys in keyring [##################################] 100% (1/1) checking package integrity [##################################] 100% (1/1) loading package files [##################################] 100% (1/1) checking for file conflicts [##################################] 100% (1/1) checking available disk space [##################################] 100% :: Processing package changes... (1/1) downgrading libical [##################################] 100% :: Running post-transaction hooks... (1/2) Arming ConditionNeedsUpdate... (2/2) Refreshing PackageKit... add libical to IgnorePkg? [y/N] y [dragan@dragan-arch ~]$ II chose option 19 libical (3.0.15-2 => 3.0.14-1) Another method to downgrade is to downgrade the entire distribution Edit pacman.conf [core] SigLevel = PackageRequired Server=https://archive.archlinux.org/repos/2022/10/08/$repo/os/$arch [extra] SigLevel = PackageRequired Server=https://archive.archlinux.org/repos/2022/10/08/$repo/os/$arch [community] SigLevel = PackageRequired Server=https://archive.archlinux.org/repos/2022/10/08/$repo/os/$arch [multilib] SigLevel = PackageRequired Server=https://archive.archlinux.org/repos/2022/10/08/$repo/os/$arch sudo pacman -Syyuu Another method to downgrade is to downgrade the entire distribution. Pacman.conf is being edited on the date of return, specifically I returned to 10.08.2022 when everything was ok. Then I returned to 09.10 when nothing worked. I found out that I had a breakdown on 09.10. I returned the distro to 08.10 and after that did a total update of the distribution. You gave a solution, but it doesn't help because now a new problem has appeared and the alarm does not exist in the panel and does not work, it is empty -- You are receiving this mail because: You are watching all bug changes.
