Mailinglist Archive: opensuse-factory (439 mails)

< Previous Next >
Re: [opensuse-factory] Latest TW: akonadi crashes
  • From: Axel Braun <axel.braun@xxxxxx>
  • Date: Tue, 02 Apr 2019 18:20:49 +0200
  • Message-id: <5271772.sEntA0KA90@southpole>
Am Montag, 1. April 2019, 23:02:23 CEST schrieb Patrick Shanahan:
* Axel Braun <Axel.Braun@xxxxxx> [04-01-19 15:26]:
Updated yesterday to latest TW, and see akonadi crashing since then:

docb@T520:~> akonadictl start
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-docb'
D-Bus session bus is not available!
KCrash: Application 'akonadictl' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
sock_file=/tmp/runtime-docb/kdeinit5__0
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-docb'

[1]+ Angehalten akonadictl start
docb@T520:~> Unable to start Dr. Konqi
Re-raising signal for core dump handling.

-> this results in some empty kcrash files in /tmp/runtime-docb

Search for dbus:
docb@T520:/tmp/runtime-docb> ps ax | grep dbus

1327 ? Ss 0:03 /usr/bin/dbus-daemon --system
--address=systemd: --nofork --nopidfile --systemd-activation
--syslog-only 3252 ? S 0:00 dbus-launch --autolaunch
80aebf79d908490c8d56b7d561a2aae0 --binary-syntax --close-stderr 3253 ?
Ss 0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5
--print-address 7 --session 3410 ? Sl 0:00
/usr/bin/gmenudbusmenuproxy
4466 pts/0 S+ 0:00 grep --color=auto dbus

several have been offered in the last few days

The thread you mentioned: in opensuse-kde beginning
31-03-19 Subj: akonadiserver and kmail are leaking memory

deals with akonadi consuming all memory. This is in fact a different issue
than the missing connection to dbus. Other things are not working properly as
well in KDE, like (no change of volume via hotkeys, no on-screen display for
the same) so I guess KDE is not necessarily the originator of the problem

Thanks
Axel


--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups