Bug#1010576: akonadi-server: Akonadi/Kontact hangs after resuming from standby

2022-05-30 Thread Frank Mehnert
I really wonder if this hang has something to do with a dedicated setup
because not many users seem to be affected. Nevertheless the bug is really
annoying.



Bug#1010576: akonadi-server: Akonadi/Kontact hangs after resuming from standby

2022-05-07 Thread gis-w
Exactly, but be careful with kill -9. I once broke my database with it such 
that mariadb would not even start anymore. I had to delete the entire directory 
and let akonadi recreate it from scratch.



Bug#1010576: akonadi-server: Akonadi/Kontact hangs after resuming from standby

2022-05-06 Thread Frank Mehnert
Exact same behavior here. I have this behavior for about 6-8 weeks. After each 
resume I have to stop akonadi and then kill mariadb (normal kill is nossible 
due to apparmor, only kill -9 works). After that, akonadi works again.

Thanks!



Bug#1010576: akonadi-server: Akonadi/Kontact hangs after resuming from standby

2022-05-04 Thread CH
Package: akonadi-server
Version: 4:21.12.3-2
Severity: normal
X-Debbugs-Cc: gi...@leonde.de

Dear Maintainer,

kontact reliably gets unusable after resmuing from standby. I've been using
kontact for years, and I think this started with the update of KDE Framework to
5.90,
The UI is still responsive, but accessing mails or switching folders does not
have any effect. Switching to a different folder will display a progress page
and a spinning cog as the folder icon, but nothing else will ever happen, even
after hours. Quitting Kontact also doesn't work in this situation, I have to
kill it.

To get kontact working after resuming, I have to
- kill kontact
- stop akonadi
- kill mariadb
- start kontact

What does not help is:
- kill kontact
- start kontact
(same situation as before)

Neither:
- kill kontact
- stop akonadi
- start kontact

(This fails because akonadictl stop does not terminate mariadb. It does delete
the socket file though, so the new akonadi instance cannot talk to it).

Note that when kontact/akonadi hangs after resume, I can access mariadb just
fine. It's just that the chain mariadb <-> akonadi <-> kontact is somehow
broken.

Thanks!


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages akonadi-server depends on:
ii  akonadi-backend-mysql4:21.12.3-2
ii  libaccounts-qt5-11.16-2
ii  libc62.33-7
ii  libgcc-s112-20220428-1
ii  libkf5akonadiprivate5abi2 [libkf5akonadiprivate5-21.12]  4:21.12.3-2
ii  libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-21.12]  4:21.12.3-2
ii  libkf5configcore55.90.0-1
ii  libkf5coreaddons55.90.0-1
ii  libkf5crash5 5.90.0-1
ii  libkf5i18n5  5.90.0-1
ii  libqt5core5a 5.15.2+dfsg-16+b1
ii  libqt5dbus5  5.15.2+dfsg-16+b1
ii  libqt5gui5   5.15.2+dfsg-16+b1
ii  libqt5network5   5.15.2+dfsg-16+b1
ii  libqt5sql5   5.15.2+dfsg-16+b1
ii  libqt5widgets5   5.15.2+dfsg-16+b1
ii  libqt5xml5   5.15.2+dfsg-16+b1
ii  libstdc++6   12-20220428-1

akonadi-server recommends no packages.

Versions of packages akonadi-server suggests:
ii  akonadi-backend-mysql   4:21.12.3-2
pn  akonadi-backend-postgresql  
pn  akonadi-backend-sqlite  

-- no debconf information