June 2025 - Arch-general - lists.archlinux.org

Updated on 25th to 6.15.3 + firmware (fine), update tonight to 6.15.4 + firmware, network not up, dhcpd4 fails?
by David C Rankin 28 Jun '25

28 Jun '25

All, I have my Arch server that has been running for a decade, updates weekly, never misses a beat. It has been so long since I've had an issue with it, I thought Arch had finally reached Linux rolling release nirvana. Then, for reasons I can't explain, the update tonight (an hour ago), failed to start dhcpd4. I can't ping the box, I have to log in locally and I find the network interface enp5s0 'down' - that's not happened since Arch was installed. So I bring the interface up: # ip link set enp5s0 up Presto, network is up, and well. So I try starting dhcpd4 and it fails "cannot create /run/dhcpd4/dhcpd.pid". There is no /run/dhcpd4 directory. So I created it and manually started dhcpd4 without -q and all starts fine and it is now happily handing out addresses and updating the bind DNS zone for about 60 clients. What happened? I did not install or uninstall anything new. I simply did a "pacman -Syu" to update the system. The following packages were upgraded: [2025-06-28T01:54:00-0500] [PACMAN] Running 'pacman -Syu' [2025-06-28T01:54:00-0500] [PACMAN] synchronizing package lists [2025-06-28T01:54:01-0500] [PACMAN] starting full system upgrade [2025-06-28T01:54:21-0500] [ALPM] running '60-mkinitcpio-remove.hook'... [2025-06-28T01:54:21-0500] [ALPM] running '71-dkms-remove.hook'... [2025-06-28T01:54:23-0500] [ALPM-SCRIPTLET] ==> dkms remove --no-depmod nvidia/390.157 -k 6.15.3-arch1-1 [2025-06-28T01:54:24-0500] [ALPM-SCRIPTLET] ==> depmod 6.15.3-arch1-1 [2025-06-28T01:54:31-0500] [ALPM] transaction started [2025-06-28T01:54:31-0500] [ALPM] upgraded broot (1.46.5-3 -> 1.47.0-1) [2025-06-28T01:54:31-0500] [ALPM] upgraded util-linux-libs (2.41-4 -> 2.41.1-1) [2025-06-28T01:54:31-0500] [ALPM] upgraded systemd-libs (257.6-1 -> 257.7-1) [2025-06-28T01:54:31-0500] [ALPM] upgraded cryptsetup (2.7.5-2 -> 2.8.0-1) [2025-06-28T01:54:32-0500] [ALPM] upgraded docker (1:28.2.2-1 -> 1:28.3.0-1) [2025-06-28T01:54:32-0500] [ALPM] upgraded libopenmpt (0.8.0-1 -> 0.8.1-1) [2025-06-28T01:54:32-0500] [ALPM] upgraded libjpeg-turbo (3.1.0-1 -> 3.1.1-1) [2025-06-28T01:54:32-0500] [ALPM] upgraded util-linux (2.41-4 -> 2.41.1-1) [2025-06-28T01:54:32-0500] [ALPM] upgraded systemd (257.6-1 -> 257.7-1) [2025-06-28T01:54:36-0500] [ALPM] upgraded firefox (140.0-1 -> 140.0.1-1) [2025-06-28T01:54:36-0500] [ALPM] upgraded freetds (1.5.3-1 -> 1.5.4-1) [2025-06-28T01:54:36-0500] [ALPM] upgraded gstreamer (1.26.2-2 -> 1.26.3-1) [2025-06-28T01:54:36-0500] [ALPM] upgraded gst-plugins-base-libs (1.26.2-2 -> 1.26.3-1) [2025-06-28T01:54:36-0500] [ALPM] upgraded gst-libav (1.26.2-2 -> 1.26.3-1) [2025-06-28T01:54:36-0500] [ALPM] upgraded gst-plugins-bad-libs (1.26.2-2 -> 1.26.3-1) [2025-06-28T01:54:36-0500] [ALPM] upgraded libpipewire (1:1.4.5-1 -> 1:1.4.6-1) [2025-06-28T01:54:36-0500] [ALPM] upgraded gst-plugins-bad (1.26.2-2 -> 1.26.3-1) [2025-06-28T01:54:36-0500] [ALPM] upgraded gst-plugins-base (1.26.2-2 -> 1.26.3-1) [2025-06-28T01:54:36-0500] [ALPM] upgraded gst-plugins-good (1.26.2-2 -> 1.26.3-1) [2025-06-28T01:54:36-0500] [ALPM] upgraded gum (0.16.1-1 -> 0.16.2-1) [2025-06-28T01:54:37-0500] [ALPM] upgraded intel-media-driver (25.2.3-1 -> 25.2.5-1) [2025-06-28T01:54:37-0500] [ALPM] upgraded libmpdclient (2.22-1 -> 2.23-1) [2025-06-28T01:54:37-0500] [ALPM] upgraded libunrar (1:7.1.7-1 -> 1:7.1.8-1) [2025-06-28T01:54:37-0500] [ALPM] upgraded libvoikko (4.3.2-4 -> 4.3.3-1) [2025-06-28T01:54:38-0500] [ALPM] upgraded linux (6.15.3.arch1-1 -> 6.15.4.arch2-1) [2025-06-28T01:54:45-0500] [ALPM] upgraded linux-docs (6.15.3.arch1-1 -> 6.15.4.arch2-1) [2025-06-28T01:54:45-0500] [ALPM] upgraded linux-firmware-whence (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:46-0500] [ALPM] upgraded linux-firmware-amdgpu (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:46-0500] [ALPM] upgraded linux-firmware-atheros (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:47-0500] [ALPM] upgraded linux-firmware-broadcom (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:47-0500] [ALPM] upgraded linux-firmware-cirrus (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:47-0500] [ALPM] upgraded linux-firmware-intel (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:47-0500] [ALPM] upgraded linux-firmware-mediatek (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:49-0500] [ALPM] upgraded linux-firmware-nvidia (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:49-0500] [ALPM] upgraded linux-firmware-other (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:49-0500] [ALPM] upgraded linux-firmware-radeon (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:49-0500] [ALPM] upgraded linux-firmware-realtek (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:49-0500] [ALPM] upgraded linux-firmware (20250613.12fe085f-9 -> 20250627-1) [2025-06-28T01:54:53-0500] [ALPM] upgraded linux-headers (6.15.3.arch1-1 -> 6.15.4.arch2-1) [2025-06-28T01:54:53-0500] [ALPM] upgraded openresolv (3.16.5-1 -> 3.17.0-1) [2025-06-28T01:54:53-0500] [ALPM] upgraded pipewire (1:1.4.5-1 -> 1:1.4.6-1) [2025-06-28T01:54:53-0500] [ALPM] upgraded pkgconf (2.5.0-1 -> 2.5.1-1) [2025-06-28T01:54:53-0500] [ALPM] upgraded python-pygments (2.19.1-1 -> 2.19.2-1) [2025-06-28T01:54:54-0500] [ALPM] upgraded rust (1:1.87.0-2 -> 1:1.88.0-1) [2025-06-28T01:54:54-0500] [ALPM] upgraded systemd-sysvcompat (257.6-1 -> 257.7-1) [2025-06-28T01:54:54-0500] [ALPM] upgraded thin-provisioning-tools (1.1.0-1 -> 1.2.0-1) [2025-06-28T01:54:54-0500] [ALPM] upgraded unrar (1:7.1.7-1 -> 1:7.1.8-1) [2025-06-28T01:54:55-0500] [ALPM] upgraded yt-dlp (2025.06.09-1 -> 2025.06.25-1) I have got to find out why this failed to set the network device up and why dhcpd4 couldn't create /run/dhcpd4 for startup. Most of the time I admin this box remotely. Having it reboot and not reliably come back up isn't an option. Is there some issue with the new firmware and network devices? The network device uses the r8169 driver is that is an issue, it used the r1868 driver in the past. I haven't changed a thing related to it. 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 06) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0, IOMMU group 13 I/O ports at b000 [size=256] Memory at fe100000 (64-bit, non-prefetchable) [size=4K] Memory at dc100000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, IntMsgNum 1 Capabilities: [b0] MSI-X: Enable+ Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Kernel driver in use: r8169 Kernel modules: r8169 What else to check to track down what caused the network not to come up enabled and why couldn't dhcpd4 create its pid file even after the link was brought up? This box is updated and rebooted with each new kernel and has always been bullet-proof. If it helps, the update on June 25 was minimal as well, updating: [2025-06-25T03:44:59-0500] [PACMAN] Running 'pacman -Syu linux-firmware' [2025-06-25T03:44:59-0500] [PACMAN] synchronizing package lists [2025-06-25T03:45:00-0500] [PACMAN] starting full system upgrade [2025-06-25T03:45:38-0500] [ALPM] running '60-mkinitcpio-remove.hook'... [2025-06-25T03:45:39-0500] [ALPM] running '71-dkms-remove.hook'... [2025-06-25T03:45:40-0500] [ALPM-SCRIPTLET] ==> dkms remove --no-depmod nvidia/390.157 -k 6.15.2-arch1-1 [2025-06-25T03:45:41-0500] [ALPM-SCRIPTLET] ==> depmod 6.15.2-arch1-1 [2025-06-25T03:45:47-0500] [ALPM] transaction started [2025-06-25T03:45:47-0500] [ALPM] upgraded linux-firmware-whence (20250508.788aadc8-2 -> 20250613.12fe085f-9) [2025-06-25T03:45:47-0500] [ALPM] installed linux-firmware-amdgpu (20250613.12fe085f-9) [2025-06-25T03:45:47-0500] [ALPM] installed linux-firmware-atheros (20250613.12fe085f-9) [2025-06-25T03:45:47-0500] [ALPM] installed linux-firmware-broadcom (20250613.12fe085f-9) [2025-06-25T03:45:47-0500] [ALPM] installed linux-firmware-cirrus (20250613.12fe085f-9) [2025-06-25T03:45:48-0500] [ALPM] installed linux-firmware-intel (20250613.12fe085f-9) [2025-06-25T03:45:48-0500] [ALPM] installed linux-firmware-mediatek (20250613.12fe085f-9) [2025-06-25T03:45:48-0500] [ALPM] installed linux-firmware-nvidia (20250613.12fe085f-9) [2025-06-25T03:45:48-0500] [ALPM] installed linux-firmware-other (20250613.12fe085f-9) [2025-06-25T03:45:48-0500] [ALPM] installed linux-firmware-radeon (20250613.12fe085f-9) [2025-06-25T03:45:48-0500] [ALPM] installed linux-firmware-realtek (20250613.12fe085f-9) [2025-06-25T03:45:48-0500] [ALPM] installed linux-firmware (20250613.12fe085f-9) [2025-06-25T03:45:48-0500] [ALPM] upgraded btrfs-progs (6.14-1 -> 6.15-1) [2025-06-25T03:45:48-0500] [ALPM] upgraded ca-certificates-mozilla (3.112-1 -> 3.113-1) [2025-06-25T03:45:49-0500] [ALPM] upgraded docker-compose (2.37.1-1 -> 2.37.3-1) [2025-06-25T03:45:49-0500] [ALPM] upgraded libxml2 (2.14.4-1 -> 2.14.4-2) [2025-06-25T03:45:49-0500] [ALPM] upgraded dvisvgm (3.5-1 -> 3.5-2) [2025-06-25T03:45:49-0500] [ALPM] upgraded enchant (2.8.9-1 -> 2.8.10-1) [2025-06-25T03:45:49-0500] [ALPM] upgraded nss (3.112-1 -> 3.113-1) [2025-06-25T03:45:49-0500] [ALPM] upgraded libssh (0.11.1-1 -> 0.11.2-1) [2025-06-25T03:45:49-0500] [ALPM] upgraded xorg-server-common (21.1.18-1 -> 21.1.18-2) [2025-06-25T03:45:49-0500] [ALPM] upgraded xorg-server (21.1.18-1 -> 21.1.18-2) [2025-06-25T03:45:49-0500] [ALPM] upgraded python (3.13.3-1 -> 3.13.5-1) [2025-06-25T03:45:50-0500] [ALPM] upgraded firefox (139.0.4-1 -> 140.0-1) [2025-06-25T03:45:51-0500] [ALPM] upgraded giac (2.0.0.4-1 -> 2.0.0.6-1) [2025-06-25T03:45:51-0500] [ALPM] upgraded gnupg (2.4.7-3 -> 2.4.8-1) [2025-06-25T03:45:52-0500] [ALPM] upgraded iniparser (4.2.6-1 -> 4.2.6-2) [2025-06-25T03:45:52-0500] [ALPM] upgraded liburcu (0.15.1-1 -> 0.15.3-1) [2025-06-25T03:45:53-0500] [ALPM] upgraded linux (6.15.2.arch1-1 -> 6.15.3.arch1-1) [2025-06-25T03:46:01-0500] [ALPM] upgraded linux-docs (6.15.2.arch1-1 -> 6.15.3.arch1-1) [2025-06-25T03:46:05-0500] [ALPM] upgraded linux-headers (6.15.2.arch1-1 -> 6.15.3.arch1-1) [2025-06-25T03:46:05-0500] [ALPM] upgraded parallel (20250522-1 -> 20250622-1) [2025-06-25T03:46:05-0500] [ALPM] upgraded pciutils (3.13.0-2 -> 3.14.0-1) [2025-06-25T03:46:05-0500] [ALPM] upgraded perl-image-exiftool (13.30-1 -> 13.30-2) [2025-06-25T03:46:05-0500] [ALPM] upgraded python-pypdf (5.6.0-1 -> 5.6.1-1) [2025-06-25T03:46:05-0500] [ALPM] upgraded python-scipy (1.15.3-1 -> 1.16.0-1) [2025-06-25T03:46:06-0500] [ALPM] upgraded qt6-base (6.9.1-1 -> 6.9.1-2) [2025-06-25T03:46:06-0500] [ALPM] upgraded seabios (1.16.3-1 -> 1.17.0-1) [2025-06-25T03:46:06-0500] [ALPM] upgraded sundials (7.3.0-1 -> 7.4.0-1) [2025-06-25T03:46:06-0500] [ALPM] upgraded virtiofsd (1.13.1-1 -> 1.13.2-1) [2025-06-25T03:46:06-0500] [ALPM] upgraded xorg-server-devel (21.1.18-1 -> 21.1.18-2) [2025-06-25T03:46:07-0500] [ALPM] transaction completed Absolutely no issue after that update. There have been no config changes to the server. Any idea what changed in the kernel, firmware or otherwise that may lead to these issues now after updates today (June 28)? -- David C. Rankin, J.D.,P.E.

3 6

Hi, how does this work?
by Adrián Novella 27 Jun '25

27 Jun '25

It's my first time on an email list

3 2

Re: # pacman -Rdd linux-firmware # pacman -Syu linux-firmware
by u34＠net9.cf 22 Jun '25

22 Jun '25

"Arch Linux: Recent news updates: Jan Alexander Steffens" <arch-announce(a)lists.archlinux.org> wrote: > With `20250613.12fe085f-5`, we split our firmware into several vendor-focused packages. `linux-firmware` is now an empty package depending on our default set of firmware. > > Unfortunately, this coincided with upstream reorganizing the symlink layout of the NVIDIA firmware, resulting in a situation that Pacman cannot handle. When attempting to upgrade from `20250508.788aadc8-2` or earlier, you will see the following errors: > > linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad103 exists in filesystem > linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad104 exists in filesystem > linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad106 exists in filesystem > linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad107 exists in filesystem > > To progress with the system upgrade, first remove `linux-firmware`, then reinstall it as part of the upgrade: > > # pacman -Rdd linux-firmware > # pacman -Syu linux-firmware > > URL: https://archlinux.org/news/linux-firmware-2025061312fe085f-5-upgrade-requir… What I see now in http://archlinux.org , not in https://archlinux.org/news/linux-firmware-2025061312fe085f-5-upgrade-requir… , only in arch-linux home page, is # pacman -Rdd linux-firmware # pacman -Syu linux-firmware That is, a concatenation of the two suggested commands into a single line. Should that be fixed? -- u34

3 2

xdg-desktop-portal does not start
by Radosław Kintzi 18 Jun '25

18 Jun '25

Hi, For some time, I have had a problem with screen sharing/capturing in Sway. I tested it using both Firefox and Chromium with Google Meet and this test page: https://mozilla.github.io/webrtc-landing/gum_test.html. I went through the troubleshooting checklist (available here: https://github.com/emersion/xdg-desktop-portal-wlr/wiki/%22It-doesn't-work%22-Troubleshooting-Checklist) to find out that xdg-desktop-portal.service is not started. Not that it fails. It is not even being attempted. How can I make it start? Below is what I tried. I noticed that xdg-desktop-portal.service is a "PartOf" graphical-session.target, so I configured my sway.target to bind to the graphical session. The Sway target is started in the Sway configuration, which includes a slightly modified 50-systemd-user.conf available in the Arch package: --- 50-systemd-user.sh --- # Upstream refuses to set XDG_CURRENT_DESKTOP so we have to. exec systemctl --user set-environment XDG_CURRENT_DESKTOP=sway exec systemctl --user import-environment DISPLAY \ SWAYSOCK \ WAYLAND_DISPLAY \ XDG_CURRENT_DESKTOP exec hash dbus-update-activation-environment 2>/dev/null && \ dbus-update-activation-environment --systemd DISPLAY \ SWAYSOCK \ XDG_CURRENT_DESKTOP=sway \ WAYLAND_DISPLAY \ PATH exec systemctl --user start sway.target --- The sway.target is very simple: --- (~)$ cat .config/systemd/user/sway.target [Unit] Description=Sway target AllowIsolate=yes BindsTo=graphical-session.target --- This changed nothing, so I tried to start xdg-desktop-portal manually to find out that it ends with a core dump. Logs attached. Not sure if this is related to the problem that the service is not started or if it is an unrelated issue. Any advice? Thanks, Radek

3 4

[arch-general] Now that wine is actually wine-wow64, should wine-mono be moved from from multilib to extra?
by Javier 16 Jun '25

16 Jun '25

Hello ! Currently wine-mono [1] is still under the multilib repo, I guess now wine has actually become wine-wow64 [2], and the AUR package is now just a meta package installing wine [3], so I'm wondering if wine-mono should then be moved to extra instead. Perhaps the process is not complete yet. But as wine-mono is not on AUR, then if one doesn't include the multilib repo then wouldn't be able to find wine-mono... Greetings ! -- Javier [1] https://archlinux.org/packages/multilib/x86_64/wine-mono [2] https://archlinux.org/news/transition-to-the-new-wow64-wine-and-wine-staging [3] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=wine-wow64

1 0

[arch-general] jami consuming too much cpu and jami packages issues
by Javier 16 Jun '25

16 Jun '25

Hello ! I would file an issue on the Arch jami related packages, because they're not only outdated, but I believe due to that jami consumes way too much CPU, you listen to the fans working extra, and top shows 95% usage or more, no matter how fast your PC is. The reason I don't is that my phone broke and I didn't have my aegis data backed somewhere and I can no longer login to Arch gitlab, and as long time ago it happened he same to me and I was warned they wouldn't help me out a 2nd time, oh well. Anyone experiencing the same? I see jami-qt marked as out of date, but I see no issues filed against it, same for jami-daemon. opendht is not marked out of date, and the only issues is about C bindings, however opendht currently has a dependency problem, Arch moved to llhttp 9.3.0, however opendht was linked against llhttp 9.2: > % ldd /usr/lib/libopendht.so > linux-vdso.so.1 (0x00007ff662064000) > libfmt.so.11 => /usr/lib/libfmt.so.11 (0x00007ff661ffa000) > libllhttp.so.9.2 => /usr/lib/libllhttp.so.9.2 (0x00007ff661fe8000) So the only way to currently support opendht is: > % grep IgnorePkg /etc/pacman.conf > # Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup > IgnorePkg = llhttp libgit2 bat Meaning avoid updates on those 3 packages given their dependency chain related to llhttp, since both libgit2 and bat new versions on Arch depend on llhttp 9.3 already except for opendht, which then requires a re-build. BTW, current upstream opendht release is v3.4.0, meaning the Arch "1:3.2.0-2" ought an update anyways, meaning is also out of date, and by upgrading one gets the re-build required, :) So all jami related packages out of date, jami the application consumes too much CPU, and opendht besides out of date requires a re-build to link against current repos llhttp. Not sure how to notify the developers to deal with the jami current issues, perhaps someone could file issues on the packages, particularly opendht which doesn't even have an out of date mark. Thanks a lot ! -- Javier

2 5

Pacman lite?
by Pocket 14 Jun '25

14 Jun '25

Is it possible to build a neutered version of pacman? A pacman lite if you will.... I need to cut down on the dependencies pacman requires. Without key signing and package signing. I would like to only have package building and package management and pull from an http respository. This is for a custom built OS that I would like to use pacman on an ARM SBC. it currently uses rpm as a package manager. I would also like to build them using makepkg. -- Hindi madali ang maging ako

5 6

Pacman/icu conflict: error while loading shared object
by Jeanette C. 09 Jun '25

09 Jun '25

Hey hey, I just updated icu, which broke pacman. I then used pacman-static to install the latest pacman version, using pacman-static, but no change. icu version: 76.1-1 pacman version: 7.0.0.r6.gc685ae6-6 Error message: pacman: error while loading shared libraries: libicuuc.so.75: cannot open shared object file: No such file or directory Can anyone suggest a workaround? Best wishes, Jeanette -- * Website: http://juliencoder.de - for summer is a state of sound * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g * Audiobombs: https://www.audiobombs.com/users/jeanette_c * GitHub: https://github.com/jeanette-c Just hang around and you'll see, There's nowhere I'd rather be <3 (Britney Spears)

4 11

Issues with Viewers for "special" images
by Ralf Mardorf 09 Jun '25

09 Jun '25

Hi, yesterday after the latest updates I tried to view some "special" images. I tried to view a JPEG 2000 with extra/geeqie and with extra/krita and I tried to view some FITS {,demo} images with extra/stellarsolver and extra/kstars. I don't know if this worked before, it was the first time I tried to view those kinds of images by my Arch Linux install. It was impossible to view the JPEG 2000 and more or less impossible to view FITS images. Just extra/stellarsolver was able to view a FITS demo image, but failed most of the times, too. I was able to view the JPEG 2000 image on an iPad Pro. I don't want to troubleshoot those issues, I'm just interested if somebody was ever able to view JPEG 2000 and/or FITS images with applications from the official repos. Regards, Ralf

6 11

Akonadi / KMail broken imap resource
by Bennett Piater 09 Jun '25

09 Jun '25

Hi, My IMAP resources broke in Kontact/KMail this week. My first idea was to try akonadictl restart, followed by fsck and vacuum. The restart triggered a mariadb migration, which was successful (shouldn't that have happened automatically before...?). However, it didn't change much. The logs were full of errors like these - the imap resource crashes, with no clear cause: org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/ akonadi_imap_resource" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed! 0 restarts left. org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fe4b02b4f00) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fe4b02b4f00) identified as "AgentBaseChangeRecorder - 93936498547840" org.kde.pim.akonadiserver: Subscriber "AgentBaseChangeRecorder - 93936498547840" disconnected org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/ akonadi_imap_resource" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed too often. Giving up! I then tried deleting the mariadb and having akonadi re-create it, which helped me once in the past (should be fine since it's only an indexed cache). Finally, I tried deleting and re-adding the account in kontact. None of the above worked. Any ideas how to proceed? Is there more that I could try to reset? Are there more detailed logs somewhere? I'm hoping arojas has an idea - you're a heroic maintainer, thank you in any case! Cheers, Bennett

1 0