https://bugs.kde.org/show_bug.cgi?id=477700
--- Comment #16 from alanve...@gmail.com --- Well, after my latest pacman update, the bug is back again. :/ These are the packages that were updated: upgraded hwdata (0.377-1 -> 0.378-1) upgraded at-spi2-core (2.50.0-1 -> 2.50.1-1) upgraded autoconf (2.71-4 -> 2.72-1) upgraded c-ares (1.24.0-1 -> 1.25.0-1) upgraded firewalld (2.0.2-1 -> 2.1.0-1) upgraded imagemagick (7.1.1.24-1 -> 7.1.1.25-1) upgraded libfdk-aac (2.0.2-1 -> 2.0.3-1) upgraded libssh (0.10.6-1 -> 0.10.6-2) upgraded libxmlb (0.3.14-1 -> 0.3.15-1) upgraded linux (6.6.8.arch1-1 -> 6.6.9.arch1-1) upgraded linux-g14 (6.6.6.arch1-1 -> 6.6.8.arch1-1) upgraded linux-g14-headers (6.6.6.arch1-1 -> 6.6.8.arch1-1) upgraded linux-headers (6.6.8.arch1-1 -> 6.6.9.arch1-1) upgraded luit (20230201-1 -> 20240102-1) upgraded noto-fonts (1:23.12.1-1 -> 1:24.1.1-1) upgraded oath-toolkit (2.6.9-1 -> 2.6.10-1) upgraded pacman-contrib (1.9.1-1 -> 1.10.1-1) upgraded poppler (23.12.0-1 -> 24.01.0-1) upgraded poppler-glib (23.12.0-1 -> 24.01.0-1) upgraded poppler-qt5 (23.12.0-1 -> 24.01.0-1) upgraded ppp (2.5.0-2 -> 2.5.0-3) upgraded python-psutil (5.9.6-1 -> 5.9.7-1) upgraded runc (1.1.10-1 -> 1.1.11-1) upgraded rust (1:1.74.1-1 -> 1:1.75.0-1) upgraded suitesparse (7.3.1-1 -> 7.4.0-1) upgraded vim-runtime (9.0.2167-1 -> 9.1.0000-1) upgraded vim (9.0.2167-1 -> 9.1.0000-1) upgraded welcome (3.85-1 -> 3.85-2) upgraded stremio (4.4.164-1 -> 4.4.165-1) upgraded google-chrome (120.0.6099.129-1 -> 120.0.6099.199-1) -- You are receiving this mail because: You are watching all bug changes.
